Hi, On Sat, 18 Feb 2006, Martin Schlander wrote:

On Saturday 18 February 2006 14:14, Karl Lattimer wrote:

...

now I'm using opensuse 10.1

Could someone please advise what is the correct or best procedure to update opensuse 10.1 using an internet service with working mirrors.

First of all - opensuse is the project, suse linux is the distro. This cannot be repeated too often.

Secondly - SuSE distinguishes between security updates and "normal" package updates. What you're trying to do is getting security updates - and none exist for beta3 - I'm not sure if security update mirrors exist for beta4.

If what you're looking for is package updates you want too add Factory (I believe the Fedora-project equivalent is called Rawhide) as a source to YaST - and update the packages with the yast software management module.

For instance.. http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/

But maybe you should consider getting beta4 which will be announced later today.

Factory is in the state of beta4 currently. But users have to consider this (from SL-10.1-beta4/README.IMPORTANT.txt): Beta4 is really for the adventureous experts and not for anybody without a good Linux experience: * The CD 1 needs to remain in the cd drive after installing from it. Do not remove it during the reboot and wait for YaST to request CD 2. Otherwise the installation of packages from CD 2-5 will fail afterwards. * Due to the integration of the new package manager which is not complete, note the following non working pieces: o Only a fresh installation is supported. Update from a previous installation is not working! o ncurses installation is not supported right now o Some statistics do not work, e.g. you see "Size of packages to install: 0" - or "Number of packages to install: 0", or "Software: Default system (0)". o The graphical package manager frontend has only a limited list of "views", currently you get a list of all the packages and can only search in them. o Only adding of selections works. If you want to remove a selection, remove all packages in that selection and run the resolver manually with the "Check" button. o Language dependend packages are not handled correctly. This results in the installation of one package-$lang package but not necessarily the one for the languages asked for. o It is not possible to abort installation while installing packages. o Network Installations: smb/cifs does not work, http, nfs and ftp should work. * The partitioning proposal looks broken in some cases. * There are no Release Notes shown - and the download of them fails. Summing up: The installer is in a rather bad shape, only INSTALLATION is supported. The rest of the system should be stable. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)

Christoph Thiel wrote:

On Sat, 18 Feb 2006, Eberhard Moenkeberg wrote:

...

Beta4 is really for the adventureous experts and not for anybody without a good Linux experience:

* The CD 1 needs to remain in the cd drive after installing from it. Do not remove it during the reboot and wait for YaST to request CD 2.

Otherwise the installation of packages from CD 2-5 will fail afterwards.

* Due to the integration of the new package manager which is not complete, note the following non working pieces:

o Only a fresh installation is supported. Update from a previous installation is not working!

o ncurses installation is not supported right now

o Some statistics do not work, e.g. you see "Size of packages to install: 0" - or "Number of packages to install: 0", or "Software: Default system (0)".

o The graphical package manager frontend has only a limited list of "views", currently you get a list of all the packages and can only search in them.

o Only adding of selections works. If you want to remove a selection, remove all packages in that selection and run the resolver manually with the "Check" button.

o Language dependend packages are not handled correctly. This results in the installation of one package-$lang package but not necessarily the one for the languages asked for.

o It is not possible to abort installation while installing packages.

o Network Installations: smb/cifs does not work, http, nfs and ftp should work.

* The partitioning proposal looks broken in some cases.

* There are no Release Notes shown - and the download of them fails.

Summing up: The installer is in a rather bad shape, only INSTALLATION is supported. The rest of the system should be stable.

For those of you who don't want to do a fresh installation, just use y2pmsh to upgrade ot the latests beta. It (still) uses the (old) YaST2 package manager backend and therefore is very stable and useable for an upgrade. (I'v used it successfully for the last 3 betas ;))

Here is a short guide on "how to upgrade with y2pmsh":

1.) Get the latests y2pmsh and yast2-packagemanager from Factory and install them using "rpm -Uvh y2pmsh*.rpm yast2-packagemanager*". Run SuSEconfig.

2.) Fire of y2pmsh by calling "y2pmsh".

# y2pmsh Welcome to the YaST2 Package Manager! This tool is meant for debugging purpose only.

initializing installation sources ... refreshing [... bla bla bla] initializing target ... reading RPM database .............ok

[some more info]

type help for help, ^D to exit

==> make sure you don't have any source active, if there are some, call "source -R <numberofsource>" to remove them:

[0] y2pm > source -ls Known sources: [0] y2pm > source --add <url to factory mirror> refreshing SUSE LINUX Version 10.0.42... ok (already up to date) [0] y2pm > upgrade

==> ... lot's of info

===[sum]============================================ Packages checked 1119

totalToInstall 1115 totalToDelete 0 totalToKeep 3 -------------------------- sum 1118 ==================================================== ====================================================

==> looks OK!

[0] y2pm > solve

==> hopefully you don't get to many conflicts... ;) this is just an example how to resolve a conflict

Name: evolution-sharp Edition: 0.10.2-7 From-Input-List: yes Unresolvable: evolution-sharp-0.10.2-7 requires libedataserver-1.2.so.4

Packages with errors: 2 Packages to install: 1117 Packages to keep: 3 Packages to delete: 1 Download size: 1.27 GB Needed Space: -5.2 MB [1] y2pm > remove evolution-sharp [1] y2pm > solve

[...]

Packages with errors: 0 Packages to install: 1116 Packages to keep: 3 Packages to delete: 2 Download size: 1.27 GB Needed Space: -5.8 MB [0] y2pm > commit

==> get yourself a cup of coffee and relax ;)

[0] y2pm > quit

# SuSEconfig # insserv -r novell-zmd # ;)

==> You might want to check with

# rpm -qa --last | tail -200

if there are some packages that haven't been updated (the virtual gpgkey packages are fine), but others might need some manuall interaction. This is e.g. the case if packages have been dropped. Just remove those packages with

# rpm -e <packagename>

# reboot

Regards Christoph

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

There are so many things not working in the Betas, I want to install on a x86_64 box, I installed beta 3. I'am just going to wait for the final release, will it be called 10.1 or 10.2 . Jim

On Sat, Feb 18, 2006 at 04:37:47PM +0100, Christoph Thiel wrote:

[0] y2pm > source --add <url to factory mirror> refreshing SUSE LINUX Version 10.0.42... ok (already up to date) [0] y2pm > upgrade

Thanks for this procedure, but have you read the following: <quote> We have received bugreports that our current installer does not handle the FACTORY ftp tree correctly and installs packages for other platforms. [Bug 151933 and Bug 151954] I suggest to not use the tree for now, Andreas -- Andreas Jaeger<snip> </quote> Although interesting, I see the installing of the Beta also part of the testing procedure. houghi -- Nutze die zeit. Sie ist das Kostbarste was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Wert und Arbeit, und das Sein wichtiger als das tun. Johannes Müller-Elmau

It seems to me, as a fedora user that the suse beta methodology is a little counter productive. With fedora rawhide, you install a test cd, or enable the development repo in yum, then run your update. You can continue to get the latest packages simply by running yum update. I've upgraded from FC4 -> FC5t1, FC5t2 and now test 3 is due out in a few days and all i need to do is run yum update! It'll only download the latest packages, and as most of the OS stays the same as yesterdays updates it is only a small download size. I installed a beta of opensuse to see what was different between the up and coming FC5 release and the up and coming suse release. From the installed CD there is no way to continue to test the newest packages as they are released, with yast online updates broken and no channels/repos for smart/yum as per default. Wouldn't it be sensible to keep the beta users up to date with the (b)leading edge of package builds regularly so they can provide real feedback to what works, what doesn't what is good/bad etc... This will reduce the amount of duplication of work with bug tracking, where your users aren't able to see what is fixed. From what I've seen as a beta user of opensuse is that there is very little community support, very disparate documentation of the update system, difficult to find mirrors which include factory updates and difficult to configure update mechanisms. SuSE was a leading distribution a few years ago, with 8.1 beating the hell out of RH9 with a pointy stick. Using a standard line like "Since OSS 10.1 is still in beta, there ARE no updates yet." or 'this is not intended for users' is not helpful. How does "still in beta" imply that there are no updates? Do you just release the same packages as the beta in the final? Is there actual movement between betas or does your distribution team keep updates secret until the release of an entirely new beta installer (which is broken to the extent of having to replace your previous install). By saying things like this you are excluding a community of passionate users who would like to be involved in making a distribution better. These users, as the fedora project has found are invaluable in quality assurance. Simply put, I'd imagine there are updates daily to the makeup of the distribution, updates to GTK or Cairo which need wider testing, but to beta test the distribution seems about as useful as testing a gnome live CD rather than actually seeing and contributing to the development of the distribution during the testing phase. Daily rebuilds and package updates should be made readily available via the internet to beta users. Thanks to Christoph Thiel for giving a working method of achieving what is necessary, please post this to a suse wiki page so other web users can locate it without having to join a mailing list and ask the same question as has previously been asked. I hope my views don't upset anyone, I hope that the differences between the fedora and suse beta methodologies are apparent and that the short comings of suse in this respect are highlighted enough for something to be done about it. Kind regards, Karl

Karl Lattimer schrieb:

Simply put, I'd imagine there are updates daily to the makeup of the distribution, updates to GTK or Cairo which need wider testing, but to beta test the distribution seems about as useful as testing a gnome live CD rather than actually seeing and contributing to the development of the distribution during the testing phase. Daily rebuilds and package updates should be made readily available via the internet to beta users.

What's wrong with http://en.opensuse.org/Factory_Distribution ? It should fulfill all your requirements. The Betas are simply snapshots of the Factory Distribution. You can install a Beta (unchanging, fixed source), then change your installation source to Factory. This will give you daily updates to the Beta relase in an incremental way and you can stay up-to-date regardless of when the next Beta is released. Regards, Carl-Daniel -- http://www.hailfinger.org/

On Sat, Feb 18, 2006 at 05:38:24PM +0000, Karl Lattimer wrote:

I think novell have done some great things for suse but they also seem to have broken the community somewhat, there is growing disrespect for the way novell are doing things they seem to have lost connectivity with the community and concentrated on what linux can do for them, rather than what they can do for linux, the two aren't mutually exclusive.

I think that the SUSE users were used to get a clean SUSE every 6 months. We never saw a beta, so we had no idea what was going on. Suddeenly we DO see what is going on. Not only that, we get to see the working in general. Very mch Novell and especially openSUSE want to get the 'lost souls' who think they are left behind to join openSUSE and tell what they want. That is what openSUSE is all about. Saying they are no longer heard anymore is perhaps due to the reason that they do not know how to get this list. Yes, SUSE and Novell need to get the comunication a bit better. Many things need improvement and everybody is working hard on that. The fact that they launched the beta on a saturday and not on next monday is already proof of that. :-) The fact that we are discussiong this is the best proof that they DO listen to their comunity and are interested in them. houghi -- Nutze die zeit. Sie ist das Kostbarste was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Wert und Arbeit, und das Sein wichtiger als das tun. Johannes Müller-Elmau

On Sat, Feb 18, 2006 at 02:09:59PM -0500, SOTL wrote:

There are a lot of other issues but the easiest current major issue to fix would connection and user GUIs for databases.

That would indeed be nice to have. This is however more a Linux issue then a SUSE issue.

...

Saying they are no longer heard anymore is perhaps due to the reason that they do not know how to get this list. Yes, SUSE and Novell need to get the comunication a bit better. Many things need improvement and everybody is working hard on that.

If you think SuSE is bad you should join the Mandriva group to find out what bad is.

I said it needs improvement, not that it is bad.

...

The fact that they launched the beta on a saturday and not on next monday is already proof of that. :-)

Launching on a Saturday allows mirrors to update without heavy user load.

That is not the reason. Normaly launches are planned on thursday. What I was getting at is that they are working on a saturday. houghi -- Nutze die zeit. Sie ist das Kostbarste was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Wert und Arbeit, und das Sein wichtiger als das tun. Johannes Müller-Elmau

Am Samstag, 18. Februar 2006 21:33 schrieb Richard Bos:

Op zaterdag 18 februari 2006 20:09, schreef SOTL:

...

There are a lot of other issues but the easiest current major issue to fix would connection and user GUIs for databases.

Did you try knoda (I did not, so I can't say how good it is). In my oppinion it's (one of) the best database GUIs for Linux. But the SuSE-version usually sucks (sorry...). If built in, Knoda has support for MySQL, PostgreSQL, ,ODBC sqlite, access (tables only), Paradox, Firebird and Dbase/Xbase. You should use version 0.8 now

The great thing with Knoda is, that is't database independent. You can use it for several db types. You can convert a MySQL-database in a Postgres one via drag & drop. Knoda can store databases locally ore remotely. You can make a local copy from a MySQL-database as SQLite e.g and so on. The only thing, which is missing: there is no user administrtion, as here the databases differ too much from each other. If you did not found a good database GUI yet, you must have a look at knoda. http://www.knoda.org -- Üdvözlettel -- Mit freundlichen Grüssen, Marcel Hilzinger

Am Sonntag, 19. Februar 2006 16:49 schrieb Andreas Jaeger:

Marcel Hilzinger writes:

...

Am Samstag, 18. Februar 2006 21:33 schrieb Richard Bos:

...

Op zaterdag 18 februari 2006 20:09, schreef SOTL:

...

There are a lot of other issues but the easiest current major issue to fix would connection and user GUIs for databases.

Did you try knoda (I did not, so I can't say how good it is).

In my oppinion it's (one of) the best database GUIs for Linux. But the SuSE-version usually sucks (sorry...). If built in, Knoda has support for

What is broken in our package? It supports odbc, mysql, postgres and sqlite3 "only". But actually there were other problems. With 9.1 it didn't work, because hk_classes installed the database drivers in the wrong directory. With 9.2(?) knoda was dropped in RC2, because of a bug in the antialiasing system of KDE. When Knoda 0.7.2 was stable (first version with GUI for queries, SL 9.3), Suse shipped 0.6.4 and I remember, that it crashed often. With 10.0 it's 0.7.4, that's OK, but without support for reading Access-DBs.

Not the fault of Suse only, but a sad story ;-( -- Üdvözlettel -- Mit freundlichen Grüssen, Marcel Hilzinger

On Saturday 18 February 2006 19:09, SOTL wrote:

On Saturday 18 February 2006 01:00 pm, houghi wrote:

...

Very mch Novell and especially openSUSE want to get the 'lost souls' who think they are left behind to join openSUSE and tell what they want. That is what openSUSE is all about.

There are a lot of other issues but the easiest current major issue to fix would connection and user GUIs for databases.

I've been working with Tora - http://sourceforge.net/projects/tora - and its looking pretty good. Shame about the huge Oracle client installation, but it supports Oracle, MYSQL and Postgres. Licensing is probably another matter for more astute heads than mine, but it appears to be GPL, so should be OK. Cheers Pete

On Saturday 18 February 2006 22:56, Fred A. Miller wrote:

On Saturday 18 February 2006 5:20 pm, Pete Connolly wrote:

...

On Saturday 18 February 2006 19:09, SOTL wrote:

...

On Saturday 18 February 2006 01:00 pm, houghi wrote:

...

Very mch Novell and especially openSUSE want to get the 'lost souls' who think they are left behind to join openSUSE and tell what they want. That is what openSUSE is all about.

There are a lot of other issues but the easiest current major issue to fix would connection and user GUIs for databases.

I've been working with Tora - http://sourceforge.net/projects/tora - and its looking pretty good. Shame about the huge Oracle client installation, but it supports Oracle, MYSQL and Postgres.

Licensing is probably another matter for more astute heads than mine, but it appears to be GPL, so should be OK.

YES.....it IS GPL.

Fred

Thanks Fred, thought it was but sometimes these things bite you. It looks like Tora has been favoured by Novell/SuSE before: http://ftp.novell.com/partners/oracle/sles-8/unsupported/ Not quite a ringing endorsement, but encouraging. For MYSQL, there's also the MySQL administrator which I've used in the past. Works well for creating databases. This is dual licence including GPL: http://dev.mysql.com/downloads/administrator/index.html As well as a query tool: http://dev.mysql.com/downloads/query-browser/1.1.html Which again is dual licence with GPL. In fact, I'd say that the database GUI part of opensuse is looking pretty good. Plenty for me to get working with. Cheers Pete

On Sat, Feb 18, 2006 at 02:23:12PM -0500, Mathieu Chouinard wrote:

Yup this give you the weekend to update all the computers at your workplace without loosing productivity ;)

The workers will be thrilled when they come in on monday and see all the errors produced by the Beta installation. :-D houghi -- Nutze die zeit. Sie ist das Kostbarste was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Wert und Arbeit, und das Sein wichtiger als das tun. Johannes Müller-Elmau

Hi, On Saturday, February 18, 2006 at 17:38:24, Karl Lattimer wrote:

...

What's wrong with http://en.opensuse.org/Factory_Distribution ? It should fulfill all your requirements. The Betas are simply snapshots of the Factory Distribution. You can install a Beta (unchanging, fixed source), then change your installation source to Factory. This will give you daily updates to the Beta relase in an incremental way and you can stay up-to-date regardless of when the next Beta is released.

I'd like to see either yum/smart/yast preconfigured on beta install disks to include repos for continued update, and possibly instead of setting the default home page in firefox to a novell page you could try setting a beta testing howto page located within the distribution as the default home page enabling beta testers to get started using/testing the distribution.

Hooray. You found your first two bugs in SUSE Linux. Please report them to bugzilla.novell.com :)

I think novell have done some great things for suse but they also seem to have broken the community somewhat, there is growing disrespect for the way novell are doing things they seem to have lost connectivity with the community and concentrated on what linux can do for them, rather than what they can do for linux, the two aren't mutually exclusive.

Sorry but thats a rather bold statement. Novell is part of the community so there is no way to loose connectivity. Novell employs more than a hundred top linux/opensource developers. Like more than 20 kernel developers, more than 30 KDE/GNOME developers, more than 10 toolchain (gcc, glibc, binutils) developers, more then 40 individuals that are lead developers in other major projects like OpenOffice, AppArmor, SAMBA, X.org, alsa, mono, hal/udev, Hula, gphoto, wine, pam, swamp, mlmmj, screen. Just to name a few. So there is no distinction between Novell and "the community". Novell is a big part of "the commnuity" not something that stands aside. Henne -- Henne Vogelsang, http://hennevogel.de "To die. In the rain. Alone." Ernest Hemingway

On Sat, Feb 18, 2006 at 08:02:39PM +0100, jdd wrote:

may I copy this into the wiki? it's very interesting and data I rarely see...

Sure. The Wiki is yours to edit. If this is wrong in any way, people can change it. ;-) houghi -- Nutze die zeit. Sie ist das Kostbarste was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Wert und Arbeit, und das Sein wichtiger als das tun. Johannes Müller-Elmau

On Saturday 18 February 2006 01:00 pm, Henne Vogelsang wrote:

Hi,

On Saturday, February 18, 2006 at 17:38:24, Karl Lattimer wrote:

...

...

What's wrong with http://en.opensuse.org/Factory_Distribution ? It should fulfill all your requirements. The Betas are simply snapshots of the Factory Distribution. You can install a Beta (unchanging, fixed source), then change your installation source to Factory. This will give you daily updates to the Beta relase in an incremental way and you can stay up-to-date regardless of when the next Beta is released.

I'd like to see either yum/smart/yast preconfigured on beta install disks to include repos for continued update, and possibly instead of setting the default home page in firefox to a novell page you could try setting a beta testing howto page located within the distribution as the default home page enabling beta testers to get started using/testing the distribution.

Hooray. You found your first two bugs in SUSE Linux. Please report them to bugzilla.novell.com :)

...

I think novell have done some great things for suse but they also seem to have broken the community somewhat, there is growing disrespect for the way novell are doing things they seem to have lost connectivity with the community and concentrated on what linux can do for them, rather than what they can do for linux, the two aren't mutually exclusive.

Sorry but thats a rather bold statement. Novell is part of the community so there is no way to loose connectivity. Novell employs more than a hundred top linux/opensource developers. Like more than 20 kernel developers, more than 30 KDE/GNOME developers, more than 10 toolchain (gcc, glibc, binutils) developers, more then 40 individuals that are lead developers in other major projects like OpenOffice, AppArmor, SAMBA, X.org, alsa, mono, hal/udev, Hula, gphoto, wine, pam, swamp, mlmmj, screen. Just to name a few. So there is no distinction between Novell and "the community". Novell is a big part of "the commnuity" not something that stands aside.

Henne

Having fought the good fight and consistently loosing I have only one set of advice. If it don't work report it. If it may not work report it. If you think it don't work report it. If you believe that it might not work when there is a blue moon and the plantest don't aline report it. Sorting out the mess and proofing their product is what all those engineers are for. Think of it this way when you buy a box set of SuSE you are not buying Linux, Gnome, KDE et. what you are buying is the quality from having a company proof the distribution. That is all. Just their proof that the distribution AS A WHOLE functions correctly. So report what the issues are so that they may be corrected. SOTL

Op zaterdag 18 februari 2006 18:08, schreef Karl Lattimer:

How does "still in beta" imply that there are no updates? Do you just release the same packages as the beta in the final? Is there actual movement between betas or does your distribution team keep updates secret until the release of an entirely new beta installer (which is broken to the extent of having to replace your previous install).

There are over 112 new packages for 10.1 in the last 2 days and 1812 in the last 10: http://linux01.gwdg.de/apt4rpm/freshrpms/ Well, happy updating :) -- Richard Bos Without a home the journey is endless

Hi, On Sat, 18 Feb 2006, Christoph Thiel wrote:

For those of you who don't want to do a fresh installation, just use y2pmsh to upgrade ot the latests beta. It (still) uses the (old) YaST2 package manager backend and therefore is very stable and useable for an upgrade. (I'v used it successfully for the last 3 betas ;))

Here is a short guide on "how to upgrade with y2pmsh":

1.) Get the latests y2pmsh and yast2-packagemanager from Factory and install them using "rpm -Uvh y2pmsh*.rpm yast2-packagemanager*". Run SuSEconfig.

yast2-packagemanager is missing in factory. Only yast2-packagemanager-devel is present, and yast2-packagemanager-2.13.15-3.src.rpm. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)

Hi, On Sat, 18 Feb 2006, Christoph Thiel wrote:

For those of you who don't want to do a fresh installation, just use y2pmsh to upgrade ot the latests beta. It (still) uses the (old) YaST2 package manager backend and therefore is very stable and useable for an upgrade. (I'v used it successfully for the last 3 betas ;))

Here is a short guide on "how to upgrade with y2pmsh":

1.) Get the latests y2pmsh and yast2-packagemanager from Factory and install them using "rpm -Uvh y2pmsh*.rpm yast2-packagemanager*". Run SuSEconfig.

I've learned that yast2-packagemanager is not needed - only y2pmsh.

2.) Fire of y2pmsh by calling "y2pmsh".

# y2pmsh Welcome to the YaST2 Package Manager! This tool is meant for debugging purpose only.

initializing installation sources ... refreshing [... bla bla bla] initializing target ... reading RPM database .............ok

[some more info]

type help for help, ^D to exit

==> make sure you don't have any source active, if there are some, call "source -R <numberofsource>" to remove them:

[0] y2pm > source -ls Known sources: [0] y2pm > source --add <url to factory mirror> refreshing SUSE LINUX Version 10.0.42... ok (already up to date) [0] y2pm > upgrade

==> ... lot's of info

===[sum]============================================ Packages checked 1119

totalToInstall 1115 totalToDelete 0 totalToKeep 3 -------------------------- sum 1118 ==================================================== ====================================================

==> looks OK!

[0] y2pm > solve

==> hopefully you don't get to many conflicts... ;) this is just an example how to resolve a conflict

Name: evolution-sharp Edition: 0.10.2-7 From-Input-List: yes Unresolvable: evolution-sharp-0.10.2-7 requires libedataserver-1.2.so.4

Packages with errors: 2 Packages to install: 1117 Packages to keep: 3 Packages to delete: 1 Download size: 1.27 GB Needed Space: -5.2 MB [1] y2pm > remove evolution-sharp [1] y2pm > solve

[...]

Packages with errors: 0 Packages to install: 1116 Packages to keep: 3 Packages to delete: 2 Download size: 1.27 GB Needed Space: -5.8 MB [0] y2pm > commit

==> get yourself a cup of coffee and relax ;)

[0] y2pm > quit

# SuSEconfig # insserv -r novell-zmd # ;)

==> You might want to check with

# rpm -qa --last | tail -200

if there are some packages that haven't been updated (the virtual gpgkey packages are fine), but others might need some manuall interaction. This is e.g. the case if packages have been dropped. Just remove those packages with

# rpm -e <packagename>

# reboot

I did it this way. Now I have: turion:0 21:56:47 ~ # cat /etc/SuSE-release SUSE LINUX 10.0.42 (X86-64) OSS Beta4 VERSION = 10.0.42 turion:0 21:57:03 ~ # But yast2 does not work: turion:0 21:57:03 ~ # yast2 /sbin/yast2: line 207: 12414 Speicherzugriffsfehler $ybindir/y2controlcenter $Y2QT_ARGS "$@" turion:0 21:58:28 ~ # Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)

On Sun, 19 Feb 2006, Christoph Thiel wrote: [ update with y2pmsh ]

...

I did it this way. Now I have:

turion:0 21:56:47 ~ # cat /etc/SuSE-release SUSE LINUX 10.0.42 (X86-64) OSS Beta4 VERSION = 10.0.42 turion:0 21:57:03 ~ #

But yast2 does not work:

turion:0 21:57:03 ~ # yast2 /sbin/yast2: line 207: 12414 Speicherzugriffsfehler $ybindir/y2controlcenter $Y2QT_ARGS "$@" turion:0 21:58:28 ~ #

Please mail me the output of "rpm -qa --last" (gzipped) off-list and I'll try to come up with an explanation ;)

Just a short update for the list: The update seemed to have worked out well => the YaST segfault is most likely unrelated (YaST2 is started via ssh + X11-forwarding). Regards Christoph