[opensuse] Package manager update tomorrow ...
Hi, we will most likely do a first big package manager update tomorrow. The update does include a large number of bugfixes and some first performance improvements. We will do for sure another update later, with further performance optimizations and patch rpm support. You can test it already, when you add the following URL in the YaST "Installation Sources" module and run the YaST "Online Update" module afterwards: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/ The online update will only update the package manager at the first run. The second run will apply all other patches. You should also temporary disable your existing update source in this module, since we know that the current repository meta data is broken. This will be fixed with this update tomorrow as well. All existing updates are in the test repository as well. You can find a README inside the directory above with more details how to test this. Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :) bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hi, Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
One thing I noticed when I try to install the libzypp update: among the many packages that are listed as part of this patch, one of them is "rug". And it wants to keep it (rug-7.1.1.0-18) even though a newer version is available (rug-7.1.1.0-18.9). See screenshot: http://hmeyer.dyndns.org/beta/libzypp-update.png Greetings from Stuhr hartmut -- Hartmut Meyer, NTS EMEA Partner Relationship Manager SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 421 3064385 - M: +49 179 2279480 F: +49 421 3064387 - hartmut.meyer@novell.com ---------------------------------------------------- http://www.novell.com/open
Hi, Am Donnerstag, 8. Juni 2006 16:34 schrieb Hartmut Meyer:
Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
A question about the README: --- snip ----- * You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog. --- snap ----- After only installing libzypp? And without re-activating the old update catalog? Greetings from Stuhr hartmut -- Hartmut Meyer, NTS EMEA Partner Relationship Manager SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 421 3064385 - M: +49 179 2279480 F: +49 421 3064387 - hartmut.meyer@novell.com ---------------------------------------------------- http://www.novell.com/open
On Thu, Jun 08, 2006 at 04:53:38PM +0200, Hartmut Meyer wrote:
Hi,
Am Donnerstag, 8. Juni 2006 16:34 schrieb Hartmut Meyer:
Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
A question about the README:
--- snip ----- * You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog. --- snap -----
After only installing libzypp? And without re-activating the old update catalog?
The old one should be added and activated again. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hi, Am Donnerstag, 8. Juni 2006 16:34 schrieb Hartmut Meyer:
Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
One thing I noticed when I try to install the libzypp update: among the many packages that are listed as part of this patch, one of them is "rug".
And it wants to keep it (rug-7.1.1.0-18) even though a newer version is available (rug-7.1.1.0-18.9).
See screenshot:
More oddities (after installing the libzypp update and restarting zmd as described in the readme): YaST2 online_update and the ZEN updater do not show consistent results when looking for available updates: http://hmeyer.dyndns.org/beta/libzypp-update-new.png BTW: regarding the only update (ifolder3) that is offered through YaST2 online_update, YaST2 online_update complained that there is no source available to fetch the suggested ifolder3 update (someting about "atom:ifolder3..."). I then compared the installation sources in YaST2 with what rug is reporting ("rug sl") and sure enough this isn't in sync. E.g. the 10.1-packagemanagement-update-test catalog is listed as active by rug but as inactive in YaST2. And all the available updates that are listed by zen-updater but are not listed by online_update are from that 10.1-packagemanagement-update-test catalog. Should we not expect that YaST2 and zen-updater/rug are completely in sync as far as the installation sources are concerned? Greetings from Stuhr hartmut -- Hartmut Meyer, NTS EMEA Partner Relationship Manager SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 421 3064385 - M: +49 179 2279480 F: +49 421 3064387 - hartmut.meyer@novell.com ---------------------------------------------------- http://www.novell.com/open
On Thu, Jun 08, 2006 at 05:37:06PM +0200, Hartmut Meyer wrote:
Hi,
Am Donnerstag, 8. Juni 2006 16:34 schrieb Hartmut Meyer:
Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
One thing I noticed when I try to install the libzypp update: among the many packages that are listed as part of this patch, one of them is "rug".
And it wants to keep it (rug-7.1.1.0-18) even though a newer version is available (rug-7.1.1.0-18.9).
See screenshot:
More oddities (after installing the libzypp update and restarting zmd as described in the readme):
YaST2 online_update and the ZEN updater do not show consistent results when looking for available updates:
http://hmeyer.dyndns.org/beta/libzypp-update-new.png
BTW: regarding the only update (ifolder3) that is offered through YaST2 online_update, YaST2 online_update complained that there is no source available to fetch the suggested ifolder3 update (someting about "atom:ifolder3...").
I then compared the installation sources in YaST2 with what rug is reporting ("rug sl") and sure enough this isn't in sync. E.g. the 10.1-packagemanagement-update-test catalog is listed as active by rug but as inactive in YaST2.
And all the available updates that are listed by zen-updater but are not listed by online_update are from that 10.1-packagemanagement-update-test catalog.
Should we not expect that YaST2 and zen-updater/rug are completely in sync as far as the installation sources are concerned?
rug sl .... it will likely show 2 update sources. Please use only _one_ update source, either the test repo or the public repo. Ciao, marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hi, Am Donnerstag, 8. Juni 2006 17:52 schrieb Marcus Meissner:
Please use only _one_ update source, either the test repo or the public repo.
Sure. But my question was/is: if I deactivate a catalog in YaST2, shouldn't I expect that this change is also honoured by rug? I reactivated the old update catalog (official) and deactivated the new (test) update catalog in yast2. But "rug sl" shows both of them as active. Bug or working as designed? Greetings from Stuhr hartmut -- Hartmut Meyer, NTS EMEA Partner Relationship Manager SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 421 3064385 - M: +49 179 2279480 F: +49 421 3064387 - hartmut.meyer@novell.com ---------------------------------------------------- http://www.novell.com/open
On Thu, Jun 08, 2006 at 06:19:04PM +0200, Hartmut Meyer wrote:
Hi,
Am Donnerstag, 8. Juni 2006 17:52 schrieb Marcus Meissner:
Please use only _one_ update source, either the test repo or the public repo.
Sure. But my question was/is: if I deactivate a catalog in YaST2, shouldn't I expect that this change is also honoured by rug?
I reactivated the old update catalog (official) and deactivated the new (test) update catalog in yast2. But "rug sl" shows both of them as active.
Bug or working as designed?
This is a bug, you need to remove it in yast the hard way, not just disable it. I do not know if it is bugzillaed yet. Once we release the update this switching around repos is not necessary. ;) Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Thursday 08 June 2006 17:03, Adrian Schröter wrote:
You can test it already, when you add the following URL in the YaST "Installation Sources" module and run the YaST "Online Update" module afterwards:
ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/
Yast -> installation source -> add -> specify url -> add the one above -> click finish. There is only one other source active (standard update one) and yet, 'installation source' module exits in mere 4 minutes. So, it's slow but works. Online update -> hmm, shows only zypp to be updated? -> click finish and it begins updating all yast packages and finishes ok. Wohoo! rczmd restart -> alt+f2 -> zen-installer -> getting install list -> shows gazillion packages to be updated -> click select all -> install. After a while of resolving we're greeted with this: Unresolved dependencies: Installing NetworkManager-devel-0.6.2-32.11.i586[SUSE-Linux-10.1-Updates] Can't install NetworkManager-devel-0.6.2-32.11.x86_64 [SUSE-Linux-10.1-Updates], since NetworkManager-devel-0.6.2-32.11.i586 [SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid. OK, so this hasn't been fixed and its again attempting to install i586 and x86-64 packages at the same time. So, to the menu to remove all i586 packages manually. After manually clicking away 66 (!) i586 packages we're once again greeted with: Unresolved dependencies: Installing netbeans-5.0-14.1.noarch[SUSE-Linux-10.1-Updates] Can't install patch:netbeans-1451-0.noarch[SUSE-Linux-10.1-Updates] since it is does not apply to this system. Can't install netbeans-5.0-14.1.noarch[20060608-183539], since netbeans-5.0-14.1.noarch[SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid. AH OK. Where did this ghost package come from? Let's remove it and go on. Now we get: Unresolved dependencies: Installing patch:kdeadmin3-1439-0.noarch[SUSE-Linux-10.1-Updates] Can't install patch:kdeadmin3-1439-0.noarch[20060608-183539], since patch:kdeadmin3-1439-0.noarch[SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid. OK; I get it. You don't like supplementary KDE. Let's remove all that. Wohoo! I think it started to do something, it's saying 'installing software'! Only after 20 minutes of vigorous clicking. Hmm, 5 minutes of waiting and progress bar is not moving? Hmm. What's it doing? Let's check with gdb. ps -ef | grep zen-installer jmk 14076 4563 2 18:50 ? 00:00:27 zen-installer /usr/lib/zen-updater/ZenInstaller.exe EXE? EHHHEH. Ok, shall we attach gdb to it. (gdb) attach 14076 Attaching to program: /usr/lib/zen-updater/ZenInstaller.exe, process 14076 0x366d8136 in ?? () (gdb) thread apply all bt (gdb) quit (detached gracefully) Uh, no stack ?? What is this thing? file /usr/lib/zen-updater/ZenInstaller.exe /usr/lib/zen-updater/ZenInstaller.exe: PE executable for MS Windows (console) Intel 80386 32-bit, Mono/.Net assembly Sure thing. How am I supposed to debug this? Anyhoo, let's give it at least half an hour to do what ever it's doing. Will let you know if it ever resumes. -- // Janne --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Thursday 08 June 2006 18:16 schrieb Janne Karhunen:
On Thursday 08 June 2006 17:03, Adrian Schröter wrote:
You can test it already, when you add the following URL in the YaST "Installation Sources" module and run the YaST "Online Update" module afterwards:
ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/
Yast -> installation source -> add -> specify url -> add the one above -> click finish. There is only one other source active (standard update one) and yet, 'installation source' module exits in mere 4 minutes. So, it's slow but works.
Online update -> hmm, shows only zypp to be updated? -> click
yes, that is a feature, so that the other packages do get installed with the new package manager.
finish and it begins updating all yast packages and finishes ok. Wohoo! rczmd restart -> alt+f2 -> zen-installer -> getting install list -> shows gazillion packages to be updated -> click select all -> install. After a while of resolving we're greeted with this:
With zen-updater ?
Unresolved dependencies: Installing NetworkManager-devel-0.6.2-32.11.i586[SUSE-Linux-10.1-Updates] Can't install NetworkManager-devel-0.6.2-32.11.x86_64 [SUSE-Linux-10.1-Updates], since NetworkManager-devel-0.6.2-32.11.i586 [SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid.
That should not happen. Does the same happen when you also use the YaST Online Update module in the second run ?
OK, so this hasn't been fixed and its again attempting to install i586 and x86-64 packages at the same time. So, to the menu to remove all i586 packages manually. After manually clicking away 66 (!) i586 packages we're once again greeted with:
Unresolved dependencies: Installing netbeans-5.0-14.1.noarch[SUSE-Linux-10.1-Updates] Can't install patch:netbeans-1451-0.noarch[SUSE-Linux-10.1-Updates] since it is does not apply to this system. Can't install netbeans-5.0-14.1.noarch[20060608-183539], since netbeans-5.0-14.1.noarch[SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid.
I don't have the conflict with YaST Online Update. Can you check this also please ?
AH OK. Where did this ghost package come from? Let's remove it and go on. Now we get:
Unresolved dependencies: Installing patch:kdeadmin3-1439-0.noarch[SUSE-Linux-10.1-Updates] Can't install patch:kdeadmin3-1439-0.noarch[20060608-183539], since patch:kdeadmin3-1439-0.noarch[SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid.
OK; I get it. You don't like supplementary KDE. Let's remove all that.
oh, okay, I will retest with the Build Service KDE3 tomorrow. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Thursday 08 June 2006 19:23, Adrian Schröter wrote:
finish and it begins updating all yast packages and finishes ok. Wohoo! rczmd restart -> alt+f2 -> zen-installer -> getting install list -> shows gazillion packages to be updated -> click select all -> install. After a while of resolving we're greeted with this:
With zen-updater ?
Yep. Just stated yast online_update. On try one it crashed instantly after clicking 'accept'. But hey, I think I saw this before, and at that time second run helped. Let's try .. click accept. Yes, it did help this time as well, and now its updating packages. It updated 3 packages .. hmm, i thought there were more on the list? Zen shows gazillions of packages to be updated, and this updated just 3..
Unresolved dependencies: Installing NetworkManager-devel-0.6.2-32.11.i586[SUSE-Linux-10.1-Updates] Can't install NetworkManager-devel-0.6.2-32.11.x86_64 [SUSE-Linux-10.1-Updates], since NetworkManager-devel-0.6.2-32.11.i586 [SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid.
That should not happen. Does the same happen when you also use the YaST Online Update module in the second run ?
No, yast seems to be 'ok'. Flaky, but it at least did something after shaking.
Unresolved dependencies: Installing netbeans-5.0-14.1.noarch[SUSE-Linux-10.1-Updates] Can't install patch:netbeans-1451-0.noarch[SUSE-Linux-10.1-Updates] since it is does not apply to this system. Can't install netbeans-5.0-14.1.noarch[20060608-183539], since netbeans-5.0-14.1.noarch[SUSE-Linux-10.1-Updates] is already marked as needing to be installed Marking this resolution attempt as invalid.
I don't have the conflict with YaST Online Update. Can you check this also please ?
Check were? Notice the weird channel named with dates.. -- // Janne --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Thursday 08 June 2006 19:16, Janne Karhunen wrote:
Will let you know if it ever resumes.
It did. It greeted me after 20 minutes with this: System.Runtime.Remoting.RemotingException: Requested service not found. No receiver for uri 5496586a_7bba_46be_ab19_85f7a1bc09b4/-1268504894_33.rem Server stack trace: in <0x001d0> System.Runtime.Remoting.Messaging.MethodCall:ResolveMethod () in <0x000a7> System.Runtime.Remoting.Messaging.MethodCall:.ctor (System.Runtime.Remoting.Messaging.Header[] headers) in <0x00863> System.Runtime.Serialization.Formatters.Binary.MessageFormatter:ReadMethodCall (System.IO.BinaryReader reader, Boolean hasHeaders, System.Runtime.Remoting.Messaging.HeaderHandler headerHandler, System.Runtime.Serialization.Formatters.Binary.BinaryFormatter formatter) in <0x000ff> System.Runtime.Serialization.Formatters.Binary.BinaryFormatter:NoCheckDeserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler) in <0x00024> System.Runtime.Serialization.Formatters.Binary.BinaryFormatter:Deserialize (System.IO.Stream serializationStream, System.Runtime.Remoting.Messaging.HeaderHandler handler) in <0x0035d> System.Runtime.Remoting.Channels.BinaryServerFormatterSink:ProcessMessage (IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, System.IO.Stream requestStream, IMessage responseMsg, ITransportHeaders responseHeaders, System.IO.Stream responseStream) Exception rethrown at [0]: in <0x00a63> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception exc, System.Object[] out_args) -- // Janne --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
I'am new to Suse and I'm not familiar with setting up catolog in Yast2. I'm trying to setup to update my x86_64 box, how do you add the below URL in yast and the following headings, Server Name: Directory of Server: Jim ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Thu, Jun 08, 2006 at 03:55:13PM -0400, jim tate wrote:
I'am new to Suse and I'm not familiar with setting up catolog in Yast2. I'm trying to setup to update my x86_64 box, how do you add the below URL in yast and the following headings, Server Name: Directory of Server:
Jim
ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/
In this case please do not test this Beta patch but wait for the official release. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Adrian Schröter wrote:
Hi,
we will most likely do a first big package manager update tomorrow. The update does include a large number of bugfixes and some first performance improvements. We will do for sure another update later, with further performance optimizations and patch rpm support.
You can test it already, when you add the following URL in the YaST "Installation Sources" module and run the YaST "Online Update" module afterwards:
ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/
The online update will only update the package manager at the first run. The second run will apply all other patches.
You should also temporary disable your existing update source in this module, since we know that the current repository meta data is broken. This will be fixed with this update tomorrow as well. All existing updates are in the test repository as well.
You can find a README inside the directory above with more details how to test this.
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
bye adrian
Hi, just tested the workflow. Here goes the feedback/work done. The PC used was a P4, 2.4GHz, 512 RAM. Tests began at around 23:40 UTC, finished around 01:00 UTC. This in the case of you changing files during this timeframe. ( Work in accordance to the README file at ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/ ) As root: 1. * start yast2 installation source via the yast2 control center or directly as "yast2 inst_source". Add as additional software catalog: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test (or use one of the mirrors once they are updated) and then leave the module via "Finish". It will take some minutes to download data and setup the catalog. Added catalog, with Refresh&Enabled. Base catalog "No Refresh&Disabled". Clicked "Finish" and hang for maybe 20mn. Had to kill the process. Zen-updater was active. Anyhow, it detected 28 software updates. (libzypp update was there, though) So i shut zen-updater not to interfere. Added again the catalog, and now, it took some time, but "yast2 inst_source" closed nicely, apart saying the catalog was already added. 2. * start yast2 online update via the yast2 control center or directly as "yast2 online_update". The patch summary should show a couple of patches and select only the "libzypp update" (with a black mark). Press "Accept" to apply the update. It will take some time to download packages and install them. OK. just installed "libzypp update". Went fine after some time. It installed the following updates: Retrieving autoyast2-installation...OK Installing ./rpm/noarch/autoyast2-installation-2.13.65-0.2.noarch.rpm: "YaST2 Automated Installation" OK Retrieving libzypp...OK Installing ./rpm/i586/libzypp-1.1.0-1.11.i586.rpm: "Package, Patch, Pattern, and Product Management" OK Retrieving yast2-perl-bindings...OK Installing ./rpm/i586/yast2-perl-bindings-2.13.4-17.1.i586.rpm: "YaST2 - Perl Bindings" OK Retrieving yast2-ncurses...OK Installing ./rpm/i586/yast2-ncurses-2.13.36-1.2.i586.rpm: "YaST2 - Character Based User Interface" OK Retrieving autoyast2...OK Installing ./rpm/noarch/autoyast2-2.13.65-0.2.noarch.rpm: "YaST2 Automated Installation" OK Retrieving libzypp-zmd-backend...OK Installing ./rpm/i586/libzypp-zmd-backend-7.1.1.0-42.21.i586.rpm: "ZMD backend for Package, Patch, Pattern, and Product Management" OK Retrieving yast2-pkg-bindings...OK Installing ./rpm/i586/yast2-pkg-bindings-2.13.82-1.2.i586.rpm: "YaST2 Package Manager Access" OK Retrieving yast2-qt...OK Installing ./rpm/i586/yast2-qt-2.13.60-0.2.i586.rpm: "YaST2 - Graphical User Interface" OK Retrieving suseRegister...OK Installing ./rpm/noarch/suseRegister-1.0-63.3.noarch.rpm: "Registration tool" OK Retrieving yast2...OK Installing ./rpm/i586/yast2-2.13.61-0.2.i586.rpm: "YaST2 - Main Package" OK Retrieving zmd...OK Installing ./rpm/i586/zmd-7.1.1.0-39.15.i586.rpm: "Novell ZENworks Linux Management daemon" OK Retrieving zen-updater...OK Installing ./rpm/i586/zen-updater-7.1.0-51.13.i586.rpm: "Novell ZENworks Linux Management daemon" OK Retrieving yast2-online-update...OK Installing ./rpm/noarch/yast2-online-update-2.13.40-0.2.noarch.rpm: "YaST2 - Online Update (YOU)" OK Retrieving yast2-packager...OK Installing ./rpm/i586/yast2-packager-2.13.125-0.2.i586.rpm: "YaST2 - Package Library" OK Retrieving yast2-installation...OK Installing ./rpm/noarch/yast2-installation-2.13.119-1.2.noarch.rpm: "YaST2 - Installation Parts" OK Retrieving yast2-online-update-frontend...OK Installing ./rpm/noarch/yast2-online-update-frontend-2.13.40-0.2.noarch.rpm: "YaST2 - Online Update (YOU)" OK Installation finished. OK till now. 3. * You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog. Done. But with an error message: "Cannot stop 'etc/init.d/novell-zmd' service". Just clicked OK. 4. * Restart zmd with "rczmd restart". Done. 5. * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). Zen-updater appeared OK, but without patches (using zen first before YOU as it is the move). Refreshed zen: 12 software updates awaiting, and *not* dhcp!! Installed them: "The update was successful" :-) 6. * Everything is set now. You can now install further patches with: - the desktop applet zen-updater - the command line tool rug (via rug patches;rug in -t patch <patchname>) - yast2 online_update zen-updater will inform you about new patches. As it's done with "zen-updater", let's see how behaves YOU: YOU had 3 more patches (around 00:50 UTC) not(?) seen by "zen-updater": postgresql security update (security) Everybody using iFolder should update (recommended) Fix "User Administration" not working (recommended) Installed, OK. After more than an hour everything seems to be running fine. I cross-checked again zen vs YOU: no updates at this moment. Did not try rug. If i can, will try tomorrow, as it's a bit late, on a laptop. Hope the feedback can provide useful info. Final word: did not bugzillaed or CC as the intuit was just to provide feedback and follow the workflow. The system seems to run nicely :-) Thanks :-) Kind Regards, PatrickM --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Hi,
we will most likely do a first big package manager update tomorrow. The update does include a large number of bugfixes and some first performance improvements. We will do for sure another update later, with further performance optimizations and patch rpm support. [...] Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
Hello Adrian The Yast Package Module is starting much faster now, the same with the Installation Source Modul, wich also remembers my wish not to be remindet about unsigned Sources...this helps a lot ;-) But the zen-updater is still not productiv enough. First of all, it still takes a long time to get a working desktop after starting KDE. It now not longer calls "parsing...." , but it still takes to long and to much CPU. And then, the Updater does not remember my suggestions. When i unselect a Update, it will not be updatet this time, but next time i start the updater it is selectet to update again. Security... If i wanne add Packman and guru it tells me it could not add the sources because of missing signatures. OK But i can only disable signatur check complitly, not for a singel source which i probably trust. And then the kind of sources, is this a feature. When i add packman ass zypp source with the zen-updater, it is then addet as yum source into yast (?) Then i attempted to disable the SuSE Update Source (leo.org), but after this i still had the unwantet kdebase Package in the Update List. Hmm... So far, greets Michael
bye adrian
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
Hm, suseRegister depends on mono-core, yast2-installation depends on suseRegister (that's new now), yast2-restore, yast2-vm, yast2-update, yast2-sysconfig and yast2-storage depends on yast2-installation. I had no mono installed before and package management worked fine without all the new tools simply in YaST. Do I realy have to uninstall yast2 package management, if I don't want to have mono on my computer? -- Machs gut | http://www.iivs.de/schwinde/buerger/tremmel/ | http://packman.links2linux.de/ Manfred | http://www.knightsoft-net.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hm, suseRegister depends on mono-core, yast2-installation depends on suseRegister (that's new now), yast2-restore, yast2-vm, yast2-update, yast2-sysconfig and yast2-storage depends on yast2-installation. I had no mono installed before and package management worked fine without all the new tools simply in YaST. Do I realy have to uninstall yast2 package management, if I don't want to have mono on my computer?
Probably you can savely ignore the suseRegister dependency. YaST does not use Mono but suseRegister probably setup rug/mono and YaST at the same time so they dependencied it. You can always try. Just YaST and overrule SuseRegister/mono Azerion *not official, just beta-user/stable-user) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Freitag, 9. Juni 2006 23:47 schrieb Azerion:
Probably you can savely ignore the suseRegister dependency. YaST does not use Mono but suseRegister probably setup rug/mono and YaST at the same time so they dependencied it. You can always try. Just YaST and overrule SuseRegister/mono
Ok, I've solved it my way: http://packman.links2linux.org/?action=832 I don't want to have unresolved dependencies on my system ;-) -- Machs gut | http://www.iivs.de/schwinde/buerger/tremmel/ | http://packman.links2linux.de/ Manfred | http://www.knightsoft-net.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hi, Azerion schrieb:
YaST does not use Mono but suseRegister probably setup rug/mono and YaST at the same time so they dependencied it.
No, the Mono dependency of suseRegister doesn't have anything to do with rug and zmd. suseRegister doesn't use rug/zmd at all, it depends on Mono because it contains a tiny little C# app. create-guid.cs is exactly 11 lines of C# code: using System; public class CreateGuid { public static void Main() { string guid = Guid.NewGuid ().ToString ("N"); Console.WriteLine(guid); } } If someone rewrites this sophisticated and highly complex code in a different language, the Mono dependency will be gone. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hi, Manfred Tremmel schrieb:
Do I realy have to uninstall yast2 package management, if I don't want to have mono on my computer?
No, create an empty package that provides suseRegister and you're done. The Online Update Configuration will of course not work without suseRegister, but it didn't work without suseRegister before either, that's why the explicit dependency was added. Just in case you fear a slowdown of your system because Mono is installed: This will not happen, suseRegister is not a daemon, it does not use zmd and is executed exactly once under normal circumstances. Alternatively, ask someone at Novell to rewrite 173 bytes resp. 11 lines of C# code in C, C++, Perl or whatever you prefer. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Samstag, 10. Juni 2006 01:17 schrieb Andreas Hanke:
Hi,
Manfred Tremmel schrieb:
Do I realy have to uninstall yast2 package management, if I don't want to have mono on my computer?
No, create an empty package that provides suseRegister and you're done.
That's what I've done.
The Online Update Configuration will of course not work without suseRegister, but it didn't work without suseRegister before either, that's why the explicit dependency was added.
I don't need it, I only have to add the update directory to my install sources in yast and the updates will be installed.
Just in case you fear a slowdown of your system because Mono is installed: This will not happen, suseRegister is not a daemon, it does not use zmd and is executed exactly once under normal circumstances.
That's not the problem. I don't like mono, it's the MS way. I know it's free software and I can't give you arguments for it, but I've a bad feeling with it.
Alternatively, ask someone at Novell to rewrite 173 bytes resp. 11 lines of C# code in C, C++, Perl or whatever you prefer.
The question is, what is it used for. For myselve, I don't need it, like it looks like. -- Machs gut | http://www.iivs.de/schwinde/buerger/tremmel/ | http://packman.links2linux.de/ Manfred | http://www.knightsoft-net.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hi, Manfred Tremmel schrieb:
That's what I've done.
OK, fine, but could you please remove the line Obsoletes: suseRegister from Kick-suseRegister.spec ASAP? The line Provides: suseRegister is more than enough. Currently Kick-suseRegister will remove the real suseRegister on all systems without being explicitly selected, because Obsoletes tells rpmlib that Kick-suseRegister is "newer" than any version of the real suseRegister. Obsoletes is not the solution for cases where two packages provide the same rpm symbol without being identical. Obsoletes is intended for cases where two packages are functionally identical and one of them is to be considered "newer" than the other one, only.
I don't need it, [...]
OK, you don't need it, but others might want to add an update source without knowing the URL, and SUSE did it like it did for a reason. Putting out a package which obsoletes a part of the default package management system, knowing that thousands of people including less experienced ones have it in their configuration and trust it, is a tiny little bit too "aggressive" IMHO. Please remember that YaST does not warn the user about automatically removed packages! Let's at least wait until someone from SUSE tells us why C# was chosen here and what the community can do in order to get rid of it if it's considered unacceptable. Maybe a little Google SoC project will do to create a C/C++ replacement for these 11 lines of C# code. By the way, nobody needs to remove suseRegister in order to use a SUSE system without registration, not using this feature or using the "Cancel" button works just fine. Until then I propose that Kick-suseRegister provides suseRegister without obsoleting it. It serves the same purpose - being able to uninstall suseRegister and Mono after installing Kick-suseRegister - but in a less automagical way. And getting rid of Mono requires manual intervention anyway, so there's no point in removing suseRegister silently if the real purpose is getting rid of Mono. Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Samstag, 10. Juni 2006 02:46 schrieb Andreas Hanke:
Hi,
Manfred Tremmel schrieb:
That's what I've done.
OK, fine, but could you please remove the line
Obsoletes: suseRegister
from Kick-suseRegister.spec ASAP? The line
Provides: suseRegister
is more than enough. Currently Kick-suseRegister will remove the real suseRegister on all systems without being explicitly selected, because Obsoletes tells rpmlib that Kick-suseRegister is "newer" than any version of the real suseRegister.
I don't see any technical difference, but ok, yast asks befor removing, wihtout Obsoletes.
I don't need it, [...]
OK, you don't need it, but others might want to add an update source without knowing the URL, and SUSE did it like it did for a reason.
I don't want to tell SUSE to remove suseRegister. But people should have the posibility.
Putting out a package which obsoletes a part of the default package management system, knowing that thousands of people including less experienced ones have it in their configuration and trust it, is a tiny little bit too "aggressive" IMHO. Please remember that YaST does not warn the user about automatically removed packages!
Ok, but therefore I've added the description on the webpage and into the package description. If anybody installs packages without any knowledge, what is it good for, he's doing something wrong.
Let's at least wait until someone from SUSE tells us why C# was chosen here and what the community can do in order to get rid of it if it's considered unacceptable. Maybe a little Google SoC project will do to create a C/C++ replacement for these 11 lines of C# code.
As far as I understand the code, it generates a guid for registration. Why should we register a free system what most of us hate at non free systems like Windows?
By the way, nobody needs to remove suseRegister in order to use a SUSE system without registration, not using this feature or using the "Cancel" button works just fine. Until then I propose that Kick-suseRegister provides suseRegister without obsoleting it. It serves the same purpose - being able to uninstall suseRegister and Mono after installing Kick-suseRegister - but in a less automagical way. And getting rid of Mono requires manual intervention anyway, so there's no point in removing suseRegister silently if the real purpose is getting rid of Mono.
Ok. -- Machs gut | http://www.iivs.de/schwinde/buerger/tremmel/ | http://packman.links2linux.de/ Manfred | http://www.knightsoft-net.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Hi, Manfred Tremmel schrieb:
I don't see any technical difference, but ok, yast asks befor removing, wihtout Obsoletes.
Manfred, the technical difference is _huge_. Really. Try apt or smart or yum, they all evaluate Obsoletes as being "newer" and want to perform an "upgrade" as if Kick-suseRegister-1.0 were identical to suseRegister-<infinity> even of Kick-suseRegister was never selected explicitly, where the only way to prevent it is blocking/pinning the package altogether.
Ok, but therefore I've added the description on the webpage and into the package description. If anybody installs packages without any knowledge, what is it good for, he's doing something wrong.
This is very true, but do you know how many people setup apt, smart, yum, whatever by copying other people's scripts without having the slightest idea of what they are doing, because they think they have to in order to be cool? Another scenario where descriptions are typically not read is an automatic update. Cron jobs cannot read descriptions, they just evaluate Obsoletes in a certain way and perform the upgrade non-interactively.
As far as I understand the code, it generates a guid for registration. Why should we register a free system what most of us hate at non free systems like Windows?
This is unrelated to the Obsoletes tag, not sending the GUID can be achieved without it by either installing the new Kick-suseRegister - thanks for adjusting it - or by actually reading the Privacy Policy before hitting "Send". Thanks again for removing the Obsoletes tag, it's much better now, Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Friday 09 June 2006 22:12 schrieb Manfred Tremmel:
Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
Please give us any kind of feedback. We know that we are the package manager is not yet yet perfect, but this update should improve the situation a lot :)
Hm, suseRegister depends on mono-core, yast2-installation depends on suseRegister (that's new now), yast2-restore, yast2-vm, yast2-update, yast2-sysconfig and yast2-storage depends on yast2-installation. I had no mono installed before and package management worked fine without all the new tools simply in YaST. Do I realy have to uninstall yast2 package management, if I don't want to have mono on my computer?
Can you please create a bugreport to track it down ? We should of course obsolete any dependencies which are really needed. thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Samstag, 10. Juni 2006 12:47 schrieb Adrian Schröter:
Can you please create a bugreport to track it down ?
Bug 183656
We should of course obsolete any dependencies which are really needed.
Would be nice, harddisks get big and bigger, but we shouldn't waste it. -- Machs gut | http://www.iivs.de/schwinde/buerger/tremmel/ | http://packman.links2linux.de/ Manfred | http://www.knightsoft-net.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
HI! The online update seems to work now after that update. However, I have 2 issues left: 1. Please run the parsing metadata and other stuff at login time nice'd. 2. On a laptop (maybe because of slower hard disk) during boot, there is a long time between entering runlevel 5 (screen turns black) and appearing of the login screen. During that time, "zmd" and "kdm" processes (two of each) are eating CPU time, according to "htop". Thanks! Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
participants (12)
-
Adrian Schröter -
Andreas Hanke -
Azerion -
Hartmut Meyer -
Janne Karhunen -
Janne Karhunen
-
jim tate -
Manfred Tremmel -
Marcus Meissner -
Michael Schueller -
PatrickM -
Thomas Börkel