[Bug 773575] New: texlive update takes ages
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c0 Summary: texlive update takes ages Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: werner@suse.com ReportedBy: jslaby@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Now that mostly every texlive class is in a separate package, an update of factory takes ages. Every update of RPM is followed by /usr/lib/texmf/texconfig/update in %postconfig. This is evil and should be done only once at the very end I think. Or solved differently so that the update is not so painful. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c1 --- Comment #1 from Jiri Slaby <jslaby@suse.com> 2012-07-29 21:09:06 UTC --- But it is in the %posttrans script which should happen once, right? Is this rather a zypper bug? I'm doing zypper dup. posttrans scriptlet (using /bin/sh): VERBOSE=false /usr/lib/texmf/texconfig/update || : -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c2 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@suse.com, mls@suse.com, | |werner@suse.com Component|Other |Installation AssignedTo|werner@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Summary|texlive update takes ages |libzypp does not handle | |%posttrans scriptlets well | |(was: texlive update takes | |ages) QAContact|qa-bugs@suse.de |jsrain@suse.com --- Comment #2 from Dr. Werner Fink <werner@suse.com> 2012-07-30 07:25:39 UTC --- It *is* a %posttrans problem as in %post and %postun I'll do most times simply
/var/run/texlive/run-fmtutil /var/run/texlive/run-fmtutil.language /var/run/texlive/run-mktexlsr /var/run/texlive/run-updmap
to handle time consuming texhashes in the /usr/lib/texmf/texconfig/update script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |schubi@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c4 --- Comment #4 from Michael Andres <ma@suse.com> 2012-08-07 13:46:38 CEST --- (In reply to comment #1)
But it is in the %posttrans script which should happen once, right?
But zypp uses many small rpm transactions and not a single big one. libzypp-11.8.0 will provide the environment variable $ZYPP_IS_RUNNING, so the texlive scripts can behave differently in this case. * Using the /var/adm/update-scripts mechanism as substitute for %posttrans is possible, but it was not designed for this use, so it lacks efficiency: The scripts need to follow a naming convention to get executed. As it's name needs to start with '<package>-<version>-<release>' of the package which was installed, so the 6000 texlive packages will install 6000 scripts which will all be executed. The script should also be part of the packages filelist (at least as %ghost), so it gets removed together with the package. I'd at least improve libzypp to run identical scripts (e.g same MD5) only once. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c5 Stanislav Brabec <sbrabec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com --- Comment #5 from Stanislav Brabec <sbrabec@suse.com> 2012-08-07 16:15:52 CEST --- I was originally thinking about a different (and maybe simpler) implementation of one-time-per-transaction scripts: - Application that needs the target (e. g. application that needs the cache file) will install script with smart name to say /usr/lib/zypper/scripts. (e. g. /usr/lib/zypper/scripts/gtk-update-icon-cache. I can even imagine /usr/lib/zypper/scripts/feature.d/package - e. g. /usr/lib/zypper/scripts/icon-file-changed.d/gtk3.) - Application that provides contents for the target (e. g. file that should appear in the cache) will need to know name of the target to rebuild, and touch an equally named file (either empty or containing raising list of requesting packages). (e. g. /var/adm/zypp/scripts/icon-file-changed). - ZYPP will call scripts that have new content (or have non-empty list of requesters). If there is no script for the target, nothing is don. - There will be a tool to call script from outside ZYPP (if admin uses RPM directly, it will be useful for script authors together with $ZYPP_IS_RUNNING). Use case examples: Package provides icon file, GTK+ (if installed), needs to run gtk-update-icon-cache to update icon cache. Package provides desktop file, GLib (if installed), needs (currently) SuSEconfig.glib2 to update desktop cache and smart defaults. Font is installed, several application may need to rebuild their font caches. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c6 --- Comment #6 from Stanislav Brabec <sbrabec@suse.com> 2012-08-07 16:26:35 CEST --- I forgot to write, that the touch files will be removed after successful call of scripts. I can imagine simple use inside spec files: %zypp_run_once icon-file-changed %zypp_run_once tex-font-installed Use strings without "installed"/"changed"/"updated" could look well as well: %zypp_run_once icon-file %zypp_run_once tex-font %zypp_run_once truetype-font etc. It is upon programmers, whether ZYPP_IS_RUNNING logic will be hidden inside %zypp_run_once or inside the tool it calls. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c7 --- Comment #7 from Michael Andres <ma@suse.com> 2012-08-08 13:51:17 CEST --- Nice idea, though I don't think any package related scripts should be installed below /usr/lib/zypp. My maybe favorite solution would be if packages would start their %posttrans with test -n "$ZYPP_IS_RUNNING" && exit 0 using this line as an indicator for zypp that the %posttrans was not executed. Zypp could then collect those scripts and execute them at the end after unsetting ZYPP_IS_RUNNING. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c8 --- Comment #8 from Petr Gajdos <pgajdos@suse.com> 2012-08-08 12:20:36 UTC --- Just quick questions without much thinking about them: 1. Do zypp expand rpm macros? We do %reconfigure_fonts_scriptlets for all font packages and some more, which expands thanks to %reconfigure_fonts_scriptlets(c,n:) \ %post %{-n:-n %{-n*}} \ %reconfigure_fonts_post c \ \ %postun %{-n:-n %{-n*}} \ %reconfigure_fonts_postun c \ \ %posttrans %{-n:-n %{-n*}} \ %reconfigure_fonts_posttrans c \ \ %nil rpm macro. 2. How zypp will recognize "same" %posttrans script? Would we use some e. g. %posttrans_* macros for this purpose? Package 1 %posttrans %posttrans_foo %posttrans_bar Package 2 %posttrans %posttrans_foo Package 3 %pottrans %posttrans_bar Would be this merged into one call of %posttrans_foo and %posttrans_bar when installing all three packages at once? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c9 --- Comment #9 from Michael Andres <ma@suse.com> 2012-08-08 14:49:03 CEST --- (In reply to comment #8)
1. Do zypp expand rpm macros? We do
Those macros are used in the specfile and expanded by rpm at build time. The final package contains just the plain (shell)script; no rpm macros.
2. How zypp will recognize "same" %posttrans script? Would we use some e. g. %posttrans_* macros for this purpose?
"same" would be 'literally the same'. I suppose rpm does it similarly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c10 --- Comment #10 from Stanislav Brabec <sbrabec@suse.com> 2012-08-08 21:29:10 CEST --- IMHO rpm does not recognize literally the same %posttrans scripts. Otherwise comment 0 would never be an issue. Yes, "test -n "$ZYPP_IS_RUNNING" && exit 0" should exist, but it should be hidden for packagers somewhere inside the macro. I would prefer zypp not collecting %posttrans scripts, but only scripts created/triggered/ordered by %posttrans scripts. Comparing and running unique %posttrans scripts would be more work from your side with less benefits. (Imagine that the %posttrans script will need to do more than a simple one cache rebuild. For example rebuild two caches (e. g. icons and desktop files, icons and fonts) or do something unrelated to typical one-shot-script tasks (e. g. post upgrade fine tuning, call of gconftool etc.). Tool comparing %posttrans scripts directly will never see that it does the same work as other scripts do as well.) I think that /usr/lib/zypp/scripts-post or so may be a good place. /etc/zypp/scripts-post may be another location. My idea just requires two directories on your choice (one for files packaged in packages, second in var). The typical one-shot-post-transaction-scripts is triggered by some action (typically file installed to or removed from some directory) and requested by some package (typically package or library that requires a cache of this directory). My idea just reflects to the proposal: - The package that needs to use such cache would provide and install script that builds the cache. - Packages that provide files that may appear in that cache will just let know to ZYPP that the script should be started (or start it directly, if rpm is called standalone). You would not need to compare scripts, you would not have problem if the script needs to do more than one action. The code in ZYPP may look: shopt -s nullglob cd /var/zypp/scripts-post for ACTION in * ; do # Only one of following ifs is needed, second allows more packages to react to the same type of change if test -x "/usr/lib/zypp/scripts-post/$ACTION.sh" ; then "/usr/lib/zypp/scripts-post/$ACTION.sh" $(<"/var/zypp/scripts-post/$ACTION") fi if test -d "/usr/lib/zypp/scripts-post/$ACTION.d" ; then for PACKSCRIPTS in /usr/lib/zypp/scripts-post/$ACTION.d/* ; do "$PACKSCRIPTS" $(<"/var/zypp/scripts-post/$ACTION") done fi rm "/var/zypp/scripts-post/$ACTION" done The %posttrans code may look (expanded; this could be hidden to packagers inside macro %zypp_run_once): ACTION={action_we_need} if test $ZYPP_IS_RUNNING = true ; then echo {this_package_name} >>"/var/zypp/scripts-post/$ACTION" else # The same as above, only $(<"/var/zypp/scripts-post/$ACTION") is replaced by {this_package_name} if test -x "/usr/lib/zypp/scripts-post/$ACTION.sh" ; then "/usr/lib/zypp/scripts-post/$ACTION.sh" {this_package_name} fi if test -d "/usr/lib/zypp/scripts-post/$ACTION.d" ; then for PACKSCRIPTS in /usr/lib/zypp/scripts-post/$ACTION.d/* ; do "$PACKSCRIPTS" {this_package_name} done fi fi As you can see, parts of this code are nearly the same and may be optionally moved to helper script. (But they are short, so it might be an overkill.) And the package that wants action will do: %files /usr/lib/zypp/scripts-post/{action_we_need}/{this_package_name} (The script will get list of triggering packages as arguments. I do not see much use of that list now, but it may be useful for some future scripts.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c11 --- Comment #11 from Michael Andres <ma@suse.com> 2012-08-09 09:31:08 CEST --- (In reply to comment #10)
IMHO rpm does not recognize literally the same %posttrans scripts. Otherwise comment 0 would never be an issue.
It is an issue because zypp does one rpm call per package. As we have single package transactions, we have more %posttrans invocations than expected.
Yes, "test -n "$ZYPP_IS_RUNNING" && exit 0" should exist, but it should be hidden for packagers somewhere inside the macro.
Yes, but that's a packaging issue ;)
I would prefer zypp not collecting %posttrans scripts, but only scripts created/triggered/ordered by %posttrans scripts.
Package installation should work rpm-only! It's not intended to create a new zypp-only feature here. The solution four you would IMO be to put the logic into some /usr/bin/eval-post-trans-triggers script; to package it; to prerequire it in your packages and to call it from their %posttrans: test -n "$ZYPP_IS_RUNNING" && exit 0 /usr/bin/eval-post-trans-triggers ThIS will work -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c12 --- Comment #12 from Michael Andres <ma@suse.com> 2012-08-09 09:32:23 CEST --- ...rpm only and also if zypp collects the rpm %posttrans. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c13 --- Comment #13 from Stanislav Brabec <sbrabec@suse.com> 2012-08-09 16:27:27 CEST --- (In reply to comment 11)
It is an issue because zypp does one rpm call per package. As we have single package transactions, we have more %posttrans invocations than expected.
So you say that rpm alone checks %posttrans scripts of packages on a single command line for identity? I never tested it nor looked into the source code. (Well, it does not help for ZYPP anyway, but if it works in this way, the script design should take it in account to take benefit even for rpm-only installation with more packages on the command line (it means not mentioning package name explicitly in the script).)
Package installation should work rpm-only! It's not intended to create a new zypp-only feature here.
The solution four you would IMO be to put the logic into some /usr/bin/eval-post-trans-triggers script; to package it; to prerequire it in your packages and to call it from their %posttrans:
test -n "$ZYPP_IS_RUNNING" && exit 0 /usr/bin/eval-post-trans-triggers
ThIS will work
Yes. And this script should be probably part of rpm, filesystem or any other low level package. (Well, I can imagine Requires: post-trans-triggers in all packages that use it. openSUSE 12.3 will have Provides: pot-trans-triggers in (say) rpm. We could create compatibility package, that would allow to use this feature in older on non-SUSE distros. We did it in past for gconftool scripts and it saved lot of work to packagers, as they did not need %if %suse_version in their scripts in OBS packages.) Now I agree that /usr/lib/zypp/scripts-post is a bad name. So proposing new names: Helper: /usr/bin/(run OR eval)-post-install-triggers Trigger scripts: /usr/lib/post-install-triggers (directory owned by package that owns Trigger stamps: /var/lib/post-install-triggers Note to the more complicated structure $ACTION.d/$PACKAGE: I remember potential user case from past: Several desktop environments did (or do) not support desktop menu specification (it was WindowMaker in past). These environments may need dedicated scripts to be called whenever any desktop file is installed/removed/changed. So the same action may trigger more scripts. The list of packages that need action is not known in time of packaging. That is why I would like to propose to support only two part paths (probably without trailing ".d"), even if most (if not all) these directories will contain only one script. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c14 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |myBoss@gmx.de --- Comment #14 from Michael Andres <ma@suse.com> 2012-09-27 11:03:49 CEST --- *** Bug 774358 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=774358 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c15 Jan Engelhardt <jengelh@inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh@inai.de --- Comment #15 from Jan Engelhardt <jengelh@inai.de> 2013-01-05 22:51:39 CET ---
(In reply to comment #1)
But zypp uses many small rpm transactions and not a single big one.
And why is that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c16 --- Comment #16 from Michael Schröder <mls@suse.com> 2013-01-09 12:25:04 UTC --- #15: Because it's safer and more flexible than running one transaction in case installation of a package fails. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c17 --- Comment #17 from Michael Andres <ma@suse.com> 2013-01-09 13:33:24 CET --- #15: Also required in download-as-needed mode where we download one package and remove it immediately after it got installed and before the next package is processed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c18 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #18 from Michael Andres <ma@suse.com> 2013-01-24 10:50:55 CET --- *** Bug 799489 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=799489 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c19 Atri Bhattacharya <badshah400@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |badshah400@gmail.com --- Comment #19 from Atri Bhattacharya <badshah400@gmail.com> 2013-01-26 11:51:53 UTC --- Hi! Sorry for the noise, but is it possible to have this fixed for 12.3 by release date? Texlive installation is really a mess otherwise (just try sudo zypper in texlive-scheme-full and forget about using the computer for 5-6 hours!) If I can help with something to get this fixed, I would be more than happy to do so. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c20 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joschibrauchle@gmx.de --- Comment #20 from Dr. Werner Fink <werner@suse.com> 2013-02-04 08:10:14 UTC --- *** Bug 801874 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=801874 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c21 --- Comment #21 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-02-05 20:00:10 CET --- This is an autogenerated message for OBS integration: This bug (773575) was mentioned in https://build.opensuse.org/request/show/151321 Factory / texlive-filesystem https://build.opensuse.org/request/show/151322 Factory / texlive https://build.opensuse.org/request/show/151326 Factory / texlive-specs-a https://build.opensuse.org/request/show/151327 Factory / texlive-specs-b https://build.opensuse.org/request/show/151328 Factory / texlive-specs-c https://build.opensuse.org/request/show/151329 Factory / texlive-specs-d https://build.opensuse.org/request/show/151330 Factory / texlive-specs-e https://build.opensuse.org/request/show/151331 Factory / texlive-specs-f https://build.opensuse.org/request/show/151332 Factory / texlive-specs-g https://build.opensuse.org/request/show/151333 Factory / texlive-specs-h https://build.opensuse.org/request/show/151334 Factory / texlive-specs-i https://build.opensuse.org/request/show/151335 Factory / texlive-specs-j https://build.opensuse.org/request/show/151336 Factory / texlive-specs-k https://build.opensuse.org/request/show/151337 Factory / texlive-specs-l https://build.opensuse.org/request/show/151338 Factory / texlive-specs-m https://build.opensuse.org/request/show/151339 Factory / texlive-specs-n https://build.opensuse.org/request/show/151340 Factory / texlive-specs-o https://build.opensuse.org/request/show/151341 Factory / texlive-specs-p https://build.opensuse.org/request/show/151342 Factory / texlive-specs-q https://build.opensuse.org/request/show/151343 Factory / texlive-specs-r https://build.opensuse.org/request/show/151344 Factory / texlive-specs-s https://build.opensuse.org/request/show/151345 Factory / texlive-specs-t https://build.opensuse.org/request/show/151346 Factory / texlive-specs-u https://build.opensuse.org/request/show/151347 Factory / texlive-specs-v https://build.opensuse.org/request/show/151348 Factory / texlive-specs-w https://build.opensuse.org/request/show/151349 Factory / texlive-specs-x https://build.opensuse.org/request/show/151350 Factory / texlive-specs-y https://build.opensuse.org/request/show/151351 Factory / texlive-specs-z https://build.opensuse.org/request/show/151360 Factory / texlive-specs-a https://build.opensuse.org/request/show/151361 Factory / texlive-specs-b https://build.opensuse.org/request/show/151362 Factory / texlive-specs-c -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c22 --- Comment #22 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-02-05 21:00:08 CET --- This is an autogenerated message for OBS integration: This bug (773575) was mentioned in https://build.opensuse.org/request/show/151363 Factory / texlive-specs-d https://build.opensuse.org/request/show/151364 Factory / texlive-specs-e https://build.opensuse.org/request/show/151365 Factory / texlive-specs-f https://build.opensuse.org/request/show/151366 Factory / texlive-specs-g https://build.opensuse.org/request/show/151367 Factory / texlive-specs-h https://build.opensuse.org/request/show/151368 Factory / texlive-specs-i https://build.opensuse.org/request/show/151369 Factory / texlive-specs-j https://build.opensuse.org/request/show/151370 Factory / texlive-specs-k https://build.opensuse.org/request/show/151371 Factory / texlive-specs-l https://build.opensuse.org/request/show/151372 Factory / texlive-specs-m https://build.opensuse.org/request/show/151373 Factory / texlive-specs-n https://build.opensuse.org/request/show/151374 Factory / texlive-specs-o https://build.opensuse.org/request/show/151375 Factory / texlive-specs-p https://build.opensuse.org/request/show/151376 Factory / texlive-specs-q https://build.opensuse.org/request/show/151377 Factory / texlive-specs-r https://build.opensuse.org/request/show/151378 Factory / texlive-specs-s https://build.opensuse.org/request/show/151379 Factory / texlive-specs-t https://build.opensuse.org/request/show/151380 Factory / texlive-specs-u https://build.opensuse.org/request/show/151381 Factory / texlive-specs-v https://build.opensuse.org/request/show/151382 Factory / texlive-specs-w https://build.opensuse.org/request/show/151383 Factory / texlive-specs-x https://build.opensuse.org/request/show/151384 Factory / texlive-specs-y https://build.opensuse.org/request/show/151385 Factory / texlive-specs-z -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c23 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |libzypp Product|openSUSE 12.2 |openSUSE 12.3 Target Milestone|--- |Final --- Comment #23 from Dr. Werner Fink <werner@suse.com> 2013-02-07 11:02:16 UTC --- Fo all those having the timing problem installing a lot of texlive packages in one transaction: please test out the last commit of texlive. Here the packages should skip the execution of the update script in the %posttrans scriptlet but trigger zypper/libzypp to execute the zypper update-scripts after all rpm packages. And only the first of them will ultimately run the update script. This bug should stay open upto the point where rpm had obtained the --noposttrans option and enables libzypp/zypper to handle %posttrans scriptlets at its own. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c24 --- Comment #24 from Atri Bhattacharya <badshah400@gmail.com> 2013-02-07 23:27:01 UTC --- Hi! First thanks a lot for the attention toward the problem. I tried install the texlive-scheme-full from Publishing:TeXLive repository. This pulls in some 2600 packages. The installation is really fast now, it takes less than an hour for the installation to happen as against the 5-6 hours it was taking earlier! However, uninstallation is still very slow, and it seems as though the postun scripts are running after every package transaction during uninstallation yet. Is this something that can be improved upon? Thanks again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c25 --- Comment #25 from Dr. Werner Fink <werner@suse.com> 2013-02-08 13:38:50 UTC --- This will not work even with plain rpm, see e.g. a standard %postun scriptlet with: %postun if test $1 = 0; then %{_bindir}/mktexlsr 2> /dev/null || : exit 0 fi mkdir -p /var/run/texlive
/var/run/texlive/run-mktexlsr
the first branch with `test $1 = 0' is the remove case. In this case the %posttrans scriptlet as well as the zypper update script had already been removed (from rpm data base or the /var/adm/upate-scripts directory). For the second branch, that is the update case, it will work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c26 --- Comment #26 from Neil Rickert <nrickert@ameritech.net> 2013-02-09 23:56:01 UTC --- ( reply to comment #23 ) I have just finished installing under RC1. Yes, this is a lot better than it was with Beta1. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c27 Vinzenz Bargsten <vbargsten@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vbargsten@freenet.de --- Comment #27 from Vinzenz Bargsten <vbargsten@freenet.de> 2013-03-23 14:56:22 UTC --- I have started a "zypper dup" to update from 12.2 to 12.3. Due to the installation of texlive packages the update already runs for more than a half day. I use the 12.3 update repos with higher priority, then the oss/non-oss repositories. Can this behavior still be caused by this bug? Since I want to update another machine, what would I have to do to avoid this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c28 --- Comment #28 from Michael Schröder <mls@suse.com> 2013-03-25 12:46:01 UTC --- I think you should have updated the zypp stack first, IMHO the "ZYPP_IS_RUNNING" workaround does not work with the 12.2 libzypp. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c29 --- Comment #29 from Michael Andres <ma@suse.com> 2013-03-25 14:34:05 CET --- (In reply to comment #28)
"ZYPP_IS_RUNNING" workaround does not work with the 12.2 libzypp.
JFYI: Available in libzypp-11.8.0 as oS12.2 update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:planned:update -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c30 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmeeks@suse.com --- Comment #30 from Dr. Werner Fink <werner@suse.com> 2013-04-22 07:03:25 UTC --- *** Bug 814048 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=814048 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c31 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:planned:update | maint:running:52835:low --- Comment #31 from Swamp Workflow Management <swamp@suse.de> 2013-06-05 09:15:17 UTC --- The SWAMPID for this issue is 52835. This issue was rated as low. Please submit fixed packages until 2013-07-03. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/52835 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c32 --- Comment #32 from Michael Schröder <mls@suse.com> 2013-07-15 14:18:47 UTC --- FYI: Base:System's rpm (4.11.1) supports a --noposttrans option. It will soon be in Factory. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c33 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| maint:running:52835:low | maint:running:52835:low | |maint:released:sle11-sp2:53 | |562 --- Comment #33 from Swamp Workflow Management <swamp@suse.de> 2013-07-19 13:52:13 UTC --- Update released for: PackageKit, PackageKit-debuginfo, PackageKit-debugsource, PackageKit-devel, PackageKit-gstreamer-plugin, PackageKit-lang, libpackagekit-glib10, libpackagekit-glib10-devel, libpackagekit-qt10, libpackagekit-qt10-devel, libzypp, libzypp-debuginfo, libzypp-debugsource, libzypp-devel, zypper, zypper-debuginfo, zypper-debugsource, zypper-log Products: SLE-DEBUGINFO 11-SP2 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP2 (i386, x86_64) SLE-SDK 11-SP2 (i386, ia64, ppc64, s390x, x86_64) SLE-SERVER 11-SP2 (i386, ia64, ppc64, s390x, x86_64) SLES4VMWARE 11-SP2 (i386, x86_64) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| maint:running:52835:low | |maint:released:sle11-sp2:53 |maint:released:sle11-sp2:53 |562 |562 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=773575 https://bugzilla.novell.com/show_bug.cgi?id=773575#c34 --- Comment #34 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-07-22 15:00:09 CEST --- This is an autogenerated message for OBS integration: This bug (773575) was mentioned in https://build.opensuse.org/request/show/183983 Maintenance / texlive-specs-a.openSUSE_12.3_Update -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com