[SLE] Updated Software Management Test Repository for SUSE Linux 10.1
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions. For testing the update stack do the following steps as root: * 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. IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one: * 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. * You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog. * Restart zmd with "rczmd restart". * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). * 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. We will really soon release now this as official update and therefore need your testing. The only fix I'm waiting for is the following: Bug 180698 - zen-updater always shows patch dhcp (basically if a patch has been issued twice, it is always shown in zen-updater) IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC hmuelle@novell.com (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02. The update contains the following packages (basically the complete package stack): * autoyast2 * libzypp * libzypp-zmd-backend * ruby-zypp * rug * suseRegister * yast2 * yast2-installation * yast2-instserver * yast2-ncurses * yast2-online-update * yast2-packager * yast2-perl-bindings * yast2-pkg-bindings * yast2-qt * zen-updater * zmd The most important changes are: * Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * Optimize and fix downloading of type zypp * Fix refreshing repositories of type zypp (#154990) * Add support for key handling to zmd, rug, zen-updater (#173920) * Fix zen-updater to handle installation of patch and package together (#178015) * Option to disable missing signature complaints is not persistent (#175845) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Fri, Jun 2, 2006 at 3:45 am, in message
, Andreas Jaeger wrote:
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions. For testing the update stack do the following steps as root: * 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. IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one: * 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. * You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog. * Restart zmd with "rczmd restart". * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). * 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.
Following the above steps I was able to use the Zen Updater on two 10.1 systems. I only had one issue and that was one of the machines had packman and suser-guru listed as installation sources and when I tried to run the updater I got an exception error. I removed the two additional sources and it worked fine on this machine. The other machine worked without a hitch. Can we still have packman and suser-guru listed as sources and use the new software management update? Thanks for your work. Brian -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"Brian Blater (BBList)"
Following the above steps I was able to use the Zen Updater on two 10.1 systems. I only had one issue and that was one of the machines had packman and suser-guru listed as installation sources and when I tried to run the updater I got an exception error. I removed the two additional sources and it worked fine on this machine. The other machine worked without a hitch.
Can we still have packman and suser-guru listed as sources and use the new software management update?
Yes, this is shouldwork - please add them again and if you get the error file a bugreport at bugzilla.novell.com and attach /var/log/zmd-messages.log and /var/log/zmd-backend.log - we need to investigate why it does not work, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hi, i've made all requested changes! however using directly the updating application it's not working I get the message Media Change is Required Please insert 'http://software.opensuse.org/download/repositories/KDE:/Backports/SUSE_Linux...' on media 1 nevertheless using directly online upade from yast works (it was also working without zen and previous to the yast update) furthermore trying to edit the preference in the update tool killed the process. best regards António Tomé On Friday 02 June 2006 08:45, Andreas Jaeger wrote:
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions.
For testing the update stack do the following steps as root:
* 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.
IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one:
* 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.
* You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog.
* Restart zmd with "rczmd restart".
* Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update).
* 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.
We will really soon release now this as official update and therefore need your testing.
The only fix I'm waiting for is the following: Bug 180698 - zen-updater always shows patch dhcp (basically if a patch has been issued twice, it is always shown in zen-updater)
IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC hmuelle@novell.com (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02.
The update contains the following packages (basically the complete package stack):
* autoyast2 * libzypp * libzypp-zmd-backend * ruby-zypp * rug * suseRegister * yast2 * yast2-installation * yast2-instserver * yast2-ncurses * yast2-online-update * yast2-packager * yast2-perl-bindings * yast2-pkg-bindings * yast2-qt * zen-updater * zmd
The most important changes are:
* Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * Optimize and fix downloading of type zypp * Fix refreshing repositories of type zypp (#154990) * Add support for key handling to zmd, rug, zen-updater (#173920) * Fix zen-updater to handle installation of patch and package together (#178015) * Option to disable missing signature complaints is not persistent (#175845)
Andreas
-- António Rodrigues Tomé artome@ubi.pt <---official e-mail address artome@gmail.com <---alternative security e-mail address http://www.dfisica.ubi.pt/~artome http://www.cgul.ul.pt/curric/cgul_tome.htm -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
António Rodrigues Tomé
Hi,
i've made all requested changes! however using directly the updating application it's not working I get the message
Media Change is Required
Please insert 'http://software.opensuse.org/download/repositories/KDE:/Backports/SUSE_Linux...' on media 1
Please file a bugreport in bugzilla.novell.com and add the files /var/log/zmd-{messages,backend}.log .
nevertheless using directly online upade from yast works (it was also working without zen and previous to the yast update)
furthermore trying to edit the preference in the update tool killed the process.
Did you restart it? If not, please create another bugreport for this, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Friday 02 June 2006 16:04, António Rodrigues Tomé wrote:
i've made all requested changes! however using directly the updating application it's not working I get the message
Media Change is Required
Please insert 'http://software.opensuse.org/download/repositories/KDE:/Backports/SUSE_Lin ux_10.1/' on media 1
Erm.. Is that a typo when you wrote the email, or is that message cut and pasted? You've got a colon in there that shouldn't be. ..tories/KDE:/Back... -- Steve Boddy -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 02 June 2006 14:22, Stephen Boddy wrote:
http://software.opensuse.org/download/repositories/KDE:/Backports/SUSE_Lin
ux_10.1/' on media 1
Did you try the URI in Konqueror? Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
It works a lot better but it failed at its first Update (dhcp patch) with "Dependency Resolution Failed - Unknown failure" I'm always worried when i see "Unknown failure" - some return codes not trapped perhaps? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 02 June 2006 19:32, Carl Hartung wrote:
On Friday 02 June 2006 14:22, Stephen Boddy wrote:
http://software.opensuse.org/download/repositories/KDE:/Backports/SUSE_Li n
ux_10.1/' on media 1
Did you try the URI in Konqueror?
No, my bad. It's just the first time I've come across colons in any of the SUSE package trees. Chalk one up for the knee-jerk throw-away e-mail :-) Although in fairness at least I asked if it was a typo, and didn't say, "Hey a*hole! Learn how to type a URL!!!" :-D What with the 10.0 -> 10.1 changes, and repositeries shuffling, and moving about it seems to be becoming more and more confusing to follow how to get a system set up, and optimised and tweaked for your needs. There's bits and pieces of info all over the place, but I think someone (not me, because I'm obviously too confused?!?) needs to sit down and write an end to end of how SUSE retail and openSUSE are connected, where all the various repositories are, and which ones will give you what on your system. A kind of "Hitchhikers Guide To SUSE". It should also follow the convention of having 'Don't Panic' written in large friendly letters on the cover. It may already exist, but I've not encountered it yet. -- Steve Boddy -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 02 June 2006 21:02, Stephen Boddy wrote:
No, my bad. It's just the first time I've come across colons in any of the SUSE package trees.
I only knew it wasn't a typo because I checked it out, first. ;-)
Chalk one up for the knee-jerk throw-away e-mail :-) Although in fairness at least I asked if it was a typo, and didn't say, "Hey a*hole! Learn how to type a URL!!!" :-D
Very true... you are to be commended for your restraint!
... It may already exist, but I've not encountered it yet.
I've been collecting bits and pieces of threads on the updater / package management fixes. The latest I'm aware of posted today by AJ said this: We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions. For testing the update stack do the following steps as root: * 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. IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one: * 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. * You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog. * Restart zmd with "rczmd restart". * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). * 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. Good luck & regards, Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 03 June 2006 02:17, Carl Hartung wrote:
I've been collecting bits and pieces of threads on the updater / package management fixes. The latest I'm aware of posted today by AJ said this:
<big snip>
Yeah, I was aware of all that. But of my three systems one is on 9.3, one is on 10.0, and my laptop is on 10.1. I've spent an age getting the laptop set up and talking to my new dive computer, and I go on my suba'ring jollies in a week. I'm not prepared to fiddle with the lappy until after that. The HTPC is vital to my very existence. God forbid I miss Lost, or any of my other TV fixes because of downtime. My desktop is where all my user data is, so I'll be very cautious about upgrading that one as well. Cheers for the info anyway. -- Steve Boddy -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 06/06/02 03:45 (GMT-0400) Andreas Jaeger apparently typed:
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions.
For testing the update stack do the following steps as root:
* 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.
IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one:
* 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.
* You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog.
* Restart zmd with "rczmd restart".
* Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update).
* 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.
Everything worked for me up to this point. If I try yast2 online_update, which lists all the packages below, I get an immediate crash on clicking on accept. After trying that 3 times, I logged out, then back in, at which point the updater was back in the panel. I opened that, and the updater found 5 packages, which I let it install. After it was done, I tried yast2 online_update again, which appeared to list the same packages to update, and got the same crash. /var/log/YaST2/y2log is currently 2.5M in size. I then realized online update configuration had never been run. From that, I get error occurred while connecting to the server "no products to register", whether I choose configure later or now for product registration, so I can't procede with configuration. No help topics match rug. How do I tell rug to install all patches it can find?
We will really soon release now this as official update and therefore need your testing.
The only fix I'm waiting for is the following: Bug 180698 - zen-updater always shows patch dhcp (basically if a patch has been issued twice, it is always shown in zen-updater)
IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC hmuelle@novell.com (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02.
The update contains the following packages (basically the complete package stack):
* autoyast2 * libzypp * libzypp-zmd-backend * ruby-zypp * rug * suseRegister * yast2 * yast2-installation * yast2-instserver * yast2-ncurses * yast2-online-update * yast2-packager * yast2-perl-bindings * yast2-pkg-bindings * yast2-qt * zen-updater * zmd
The most important changes are:
* Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * Optimize and fix downloading of type zypp * Fix refreshing repositories of type zypp (#154990) * Add support for key handling to zmd, rug, zen-updater (#173920) * Fix zen-updater to handle installation of patch and package together (#178015) * Option to disable missing signature complaints is not persistent (#175845) -- "All have sinned & fall short of the glory of God." Romans 3:23 NIV
Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Felix Miata wrote:
I then realized online update configuration had never been run. From that, I get error occurred while connecting to the server "no products to register", whether I choose configure later or now for product registration, so I can't procede with configuration.
How did you install? If you downloaded the isos and used an older version of makeSUSEdvd to make a DVD and install from that, this is a known problem with the makeSUSEdvd script that has since been fixed. Sorry, not enough info to peg your problem, but with more info we might be able to help. -- Joe Morris Registered Linux user 231871 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Felix Miata
On 06/06/02 03:45 (GMT-0400) Andreas Jaeger apparently typed: [...]
* 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.
Everything worked for me up to this point. If I try yast2 online_update, which lists all the packages below, I get an immediate crash on clicking on accept. After trying that 3 times, I logged out, then back in, at which point the updater was back in the panel. I opened that, and the updater found 5 packages, which I let it install. After it was done, I tried yast2 online_update again, which appeared to list the same packages to update, and got the same crash. /var/log/YaST2/y2log is currently 2.5M in size.
Please compress the file and open a bugreport at bugzilla.novell.com and attach the log file. This should not happen, we have to investigate this.
I then realized online update configuration had never been run. From that, I get error occurred while connecting to the server "no products to register", whether I choose configure later or now for product registration, so I can't procede with configuration.
Please open a separate bug for this.
No help topics match rug. How do I tell rug to install all patches it can find?
"man rug" works,
[...] Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
ianseeks
It works a lot better but it failed at its first Update (dhcp patch) with "Dependency Resolution Failed - Unknown failure"
I'm always worried when i see "Unknown failure" - some return codes not trapped perhaps?
Please report this in bugzilla.novell.com and attach /var/log/zmd-{messages,backend}.log Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 6/2/06, Andreas Jaeger
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions.
For testing the update stack do the following steps as root:
I followed the instructions and everything worked fine. x86_64 platform updated from SUSE 10.0 to 10.1 with downloaded non-oss DVD for x86_64. (Only got my boxed set yesterday - will add Pro DVD to sources now) My zen updater now works. Thanks! -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre_tux@jabberafrica.org | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 06/06/03 01:43 (GMT-0400) Joe Morris (NTM) apparently typed:
Felix Miata wrote:
I then realized online update configuration had never been run. From that, I get error occurred while connecting to the server "no products to register", whether I choose configure later or now for product registration, so I can't procede with configuration.
How did you install?
FTP from factory back in January. Last update IIRC was about a week before 10.1 release, but might have been before that. -- "All have sinned & fall short of the glory of God." Romans 3:23 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 06/06/03 03:28 (GMT-0400) Andreas Jaeger apparently typed:
Felix Miata
writes:
No help topics match rug. How do I tell rug to install all patches it can find?
"man rug" works,
:-P # rug list-updates No updates are available. # :-( # rug packages 3ddiag ... ZynAddSubFX # When I want to update Mandriva, it takes only two commands: urpmi-update -a # find available updates urpmi --auto-select # install available updates for all installed packages What does 10.1 have that corresponds to this? -- "All have sinned & fall short of the glory of God." Romans 3:23 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jaeger wrote:
Felix Miata
writes: * 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. Everything worked for me up to this point. If I try yast2 online_update, which lists all the packages below, I get an immediate crash on clicking on accept. After trying that 3 times, I logged out, then back in, at which point the updater was back in the panel. I opened that, and the updater found 5 packages, which I let it install. After it was done, I
On 06/06/02 03:45 (GMT-0400) Andreas Jaeger apparently typed: [...] tried yast2 online_update again, which appeared to list the same packages to update, and got the same crash. /var/log/YaST2/y2log is currently 2.5M in size.
Please compress the file and open a bugreport at bugzilla.novell.com and attach the log file. This should not happen, we have to investigate this.
I then realized online update configuration had never been run. From that, I get error occurred while connecting to the server "no products to register", whether I choose configure later or now for product registration, so I can't procede with configuration.
Please open a separate bug for this.
No help topics match rug. How do I tell rug to install all patches it can find?
"man rug" works,
[...] Andreas The problem I have is that yast won't let me register the ftp site! This must be the worst version since SuSE 6.0 when I started and I have had everyone since.
If you cannot even do an update via online update how are we going to get a fix when it eventually comes out? SuSE needs to put out one RPM that covers all the bugs and all of package management not just provide more ftp sites that I cannot register or log onto or don't exist. Nick -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFEgaK+GFC6dsTXU2kRAkbtAJ9zwTsZ1Y+EaptUR6Rx/Laa0o+oMACeOhzv /Ja/mp8yb3f4QuQuLyO9aTw= =wwnc -----END PGP SIGNATURE----- -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Nick Murphy
The problem I have is that yast won't let me register the ftp site! This must be the worst version since SuSE 6.0 when I started and I have had everyone since.
What are you doing exactly? Please write a bug report and explain exactly what needs to be done to reproduce it - and attach the yast2 log files. I'm not aware of such a bug, this works for me - therefore we need exact information from you so that we can reproduce and then fix it.
If you cannot even do an update via online update how are we going to get a fix when it eventually comes out? SuSE needs to put out one RPM that covers all the bugs and all of package management not just provide more ftp sites that I cannot register or log onto or don't exist.
Read the subject, this is a "Test Repository". We do make it public for those brave enough to test it in real live. And then we release it as an online update. Thanks for helping us to get this fixed, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Felix Miata
On 06/06/03 03:28 (GMT-0400) Andreas Jaeger apparently typed:
Felix Miata
writes: No help topics match rug. How do I tell rug to install all patches it can find?
"man rug" works,
:-P
# rug list-updates No updates are available. #
rug patches shows the patches.
:-(
# rug packages 3ddiag ... ZynAddSubFX #
These are packages, this has nothing to do with updates.
When I want to update Mandriva, it takes only two commands: urpmi-update -a # find available updates urpmi --auto-select # install available updates for all installed packages
What does 10.1 have that corresponds to this?
yast2 online_update - and zen-updater. zen-updater is just a single click after start, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 06/06/03 11:08 (GMT-0400) Andreas Jaeger apparently typed:
Felix Miata
writes:
On 06/06/03 03:28 (GMT-0400) Andreas Jaeger apparently typed:
# rug list-updates No updates are available. #
rug patches shows the patches.
:-(
# rug packages 3ddiag ... ZynAddSubFX #
These are packages, this has nothing to do with updates.
This is terminology confusion. YaST used to hide this terminology. When I want want bug fixes from a distro builder, I expect them to be called updates, like every other RPM distro I've ever used else does. To me, patches are what programmers feed a compiler to add or remove features or fix bugs, not what an end user does to bring his OS and installed apps up to the latest fix levels. # rug patches Catalog | Name | Version | Category | Status --------+---------+---------+-------------+-------- System | libzypp | 1455-0 | recommended | Applied # This seems to be inconsistent with yast2 online_update which when opened (and crashes on accept - bug 181575) shows me the whole list of packages from your Fri, 02 Jun 2006 09:45:53 +0200 post in this thread. I can't tell whether there are available fixes I need to apply (yast2 online_update says yes) or not (rug seems to say no).
When I want to update Mandriva, it takes only two commands: urpmi-update -a # find available updates urpmi --auto-select # install available updates for all installed packages
What does 10.1 have that corresponds to this?
yast2 online_update - and zen-updater. zen-updater is just a single click after start,
Don't those require X to be running? I can run those Mandriva commands from runlevel 3, and not infrequently need to to fix a broken X in Cooker. -- "All have sinned & fall short of the glory of God." Romans 3:23 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Andreas Jaeger wrote:
* Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update).
* 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.
I did all of the steps in your email and it all worked. But this brings up something I've been curious about, namely: - How does one get the Zen-Updater icon to always appear in the system notification area? When I first installed 10.1 the icon was there. At some point it stopped appearing however it did reappear after doing all of the steps in your email. It said I had 14 updates, which instead of applying I rebooted as I wanted to see if the missing icon problem was fixed or not. It is not fixed and once again I must run zen-updater by hand to get it back. Or is this normal? :) - Bruce -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 03 June 2006 17:18, Bruce A. Mallett wrote:
When I first installed 10.1 the icon was there. At some point it stopped appearing however it did reappear after doing all of the steps in your email. It said I had 14 updates, which instead of applying I rebooted as I wanted to see if the missing icon problem was fixed or not. It is not fixed and once again I must run zen-updater by hand to get it back.
Hi Bruce, After you launch it, right-click on the icon in the system tray, select configure, select 'Preferences' in the 'Configuration' window and check the "Start the software updater on login" checkbox. regards, Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Carl: Thank you very much for that. I'm sorry to have missed that setting in the config! All: I'm experimenting with doing the updates (since I'm in this same thread I suppose this is appropriate to continue here) and find a couple "interesting" problems .. 1) One of the updates had something to do with starting or not starting ypbind based on whether or not an NIS server was designated with DHCP. I only skimmed through a couple of the descriptions so I don't recall which update it was. HOWEVER after I did the update the next reboot took about 10 minutes because suddenly the ypbind service had gotten enabled and the system was just sitting there trying to find an NIS server. The login to disable NIS also took a long time (probably while it tried to contact the non-existant NIS server). Anyway eventually I got in back to un-enabled and all is well. 2) Proving that life on the bleeding edge can result in some blood-loss, :) .. I've got the following as one of my YAST sources: http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.0/ As a result some 53 packages show up in the Zen-updater list. Taking the default of all-selected, I click on the "Update" button and get a "Dependency Resolution Failed" pop-up box containing: ----------- Unresolved dependencies: Updating kdesdk3-3.5.2-2.i586 to kdesdk3-3.5.3-2.8.i586[20060603-173124] Updating kdemultimedia3-video-3.5.2-4.i586 to kdemultimedia3-video-3.5.3-15.1.i586[20060603-173124] Updating kdemultimedia3-mixer-3.5.2-4.i586 to kdemultimedia3-mixer-3.5.3-15.1.i586[20060603-173124] Updating kdeutils3-3.5.2-4.i586 to kdeutils3-3.5.3-3.7.i586[20060603-173124] There are no installable providers of libnetsnmp.so.5 for kdeutils3-3.5.3-3.7.i586[20060603-173124] There are no installable providers of libexpat.so.0 for kdemultimedia3-mixer-3.5.3-15.1.i586[20060603-173124] There are no installable providers of libexpat.so.0 for kdemultimedia3-video-3.5.3-15.1.i586[20060603-173124] There are no installable providers of libexpat.so.0 for kdesdk3-3.5.3-2.8.i586[20060603-173124] ------------- At this point Zen-Updater starts to exhibit some un-friendly-like behavior. I click "OK" to dismiss the warning box and go back to the Zen-Updater and disable "kdesdk3" and both of the kdemultimedia entries (but leave the kdeutils enabled). I then click the Update button and sure enough get a warning on kdeutils. So now I go back and uncheck kdeutils, click Update again and again get a warning on kdesdk3, kdemultimedia-video, and kdemultimedia-mixer! Zen-Updater has quietly re-selected the entries that I deselected. Bug? 3) This is probably a packaging error so maybe I'm now in the wrong thread but .. why do the above show up as referencing packages for which there are no providers? True-enough, searching Yast sw_single for something that provides libexpat.so.0 finds nothing (the "expat" package only provides libexpat.so.1 and libexpat.so.1.5.0). - Bruce Carl Hartung wrote:
On Saturday 03 June 2006 17:18, Bruce A. Mallett wrote:
When I first installed 10.1 the icon was there. At some point it stopped appearing however it did reappear after doing all of the steps in your email. It said I had 14 updates, which instead of applying I rebooted as I wanted to see if the missing icon problem was fixed or not. It is not fixed and once again I must run zen-updater by hand to get it back.
Hi Bruce,
After you launch it, right-click on the icon in the system tray, select configure, select 'Preferences' in the 'Configuration' window and check the "Start the software updater on login" checkbox.
regards,
Carl
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Saturday 03 June 2006 19:07, Bruce A. Mallett wrote:
Carl: Thank you very much for that. I'm sorry to have missed that setting in the config!
You're welcome. That isn't all you've missed, however... <snip>
... I've got the following as one of my YAST sources: http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.0/
This is the wrong version... "10.0" /= "10.1" Wrong repository. regards, Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Ah-man! When I get stupid I go all the way! Thanks <he says sheepishly> Carl Hartung wrote:
On Saturday 03 June 2006 19:07, Bruce A. Mallett wrote:
Carl: Thank you very much for that. I'm sorry to have missed that setting in the config!
You're welcome. That isn't all you've missed, however... <snip>
... I've got the following as one of my YAST sources: http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.0/
This is the wrong version... "10.0" /= "10.1" Wrong repository.
regards,
Carl
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andreas Jaeger wrote:
Nick Murphy
writes: The problem I have is that yast won't let me register the ftp site! This must be the worst version since SuSE 6.0 when I started and I have had everyone since.
What are you doing exactly? Please write a bug report and explain exactly what needs to be done to reproduce it - and attach the yast2 log files.
I'm not aware of such a bug, this works for me - therefore we need exact information from you so that we can reproduce and then fix it.
If you cannot even do an update via online update how are we going to get a fix when it eventually comes out? SuSE needs to put out one RPM that covers all the bugs and all of package management not just provide more ftp sites that I cannot register or log onto or don't exist.
Read the subject, this is a "Test Repository". We do make it public for those brave enough to test it in real live. And then we release it as an online update.
Thanks for helping us to get this fixed, Andreas Thanks Andreas
I was being a dumb-ass, I have now managed to get it working. Nick -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFEgrq8GFC6dsTXU2kRAj79AJ0SvRKPGkVf34fEuio4A9vyCQQW8gCfdPZD 0b1g83qI/J7P2mTKnNy8VfY= =34jz -----END PGP SIGNATURE----- -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 02 June 2006 03:45, Andreas Jaeger wrote:
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing.
Just reporting back my "test" results thus far. The executive summary is "Success!" PC Chips M810LMR* / Duron 900 / 512MB/150GB *SiS 730 chipset I installed the package/patch management stack update per the instructions and the major symptoms (excruciating delays / apparent hangs / excessive cpu consumption) disappeared. Sync, at initial login, does *not* "throttle" my system nor does it "hog" the cpu. It runs in the background for several minutes but is otherwise very unobtrusive and well tamed. There /are/ issues on the package management integration side, but AFAICS the bugs I've encountered have already been entered into bugzilla. The *patch* side worked perfectly last night, at least as reliably as SUSEWatcher ever did and even a bit more conveniently: * noticed the red exclamation point alert icon, which I clicked * reviewed the immediately presented list of available patches (no need for a follow-up click and wait to "Run YOU") * the two patches were already 'checked', so I clicked "Install" * the patches installed uneventfully * the progress bar and status message title bar were informative * when done, the tray icon regained it's normal appearance Very nice! Thanks & regards, Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Andereas:
Just went through the "procedure". All appeared to work well. After
the "procedure" was complete tried to update with the updater and
there is a dhcp package that, even though the popup says the update
was successful, keeps popping itself back into the updater and the
yellow updater will not become normal. The dhcp package will not
disappear from the updater.
Chuck Davis
On 6/5/06, Carl Hartung
On Friday 02 June 2006 03:45, Andreas Jaeger wrote:
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing.
Just reporting back my "test" results thus far. The executive summary is "Success!"
PC Chips M810LMR* / Duron 900 / 512MB/150GB *SiS 730 chipset
I installed the package/patch management stack update per the instructions and the major symptoms (excruciating delays / apparent hangs / excessive cpu consumption) disappeared. Sync, at initial login, does *not* "throttle" my system nor does it "hog" the cpu. It runs in the background for several minutes but is otherwise very unobtrusive and well tamed.
There /are/ issues on the package management integration side, but AFAICS the bugs I've encountered have already been entered into bugzilla.
The *patch* side worked perfectly last night, at least as reliably as SUSEWatcher ever did and even a bit more conveniently:
* noticed the red exclamation point alert icon, which I clicked * reviewed the immediately presented list of available patches (no need for a follow-up click and wait to "Run YOU") * the two patches were already 'checked', so I clicked "Install" * the patches installed uneventfully * the progress bar and status message title bar were informative * when done, the tray icon regained it's normal appearance
Very nice!
Thanks & regards,
Carl
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
"Chuck Davis"
Andereas:
Just went through the "procedure". All appeared to work well. After the "procedure" was complete tried to update with the updater and there is a dhcp package that, even though the popup says the update was successful, keeps popping itself back into the updater and the yellow updater will not become normal. The dhcp package will not disappear from the updater.
In my announcement I mentioned one more bug that needs to be fixed - and that's the one ;-). It's fixed now. Adrian will push updates out the next days at the usual place since I'm offline the next days, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
ok, tried a new x86-64 install from the downloaded 10.1 dvd. This time it went much better. after i copied over parts of the 10.0 xorg.conf and installed the latest nvidia driver the lcd displays at1600x1200. The updates started working just fine without any changes, but after the kde repository was added, things sort of went south and there is no synchronization especially after the kde upgrade died. now i must go to the start of the updated softeware management test thread to find and apply the recommended fix. Also, a right click on a downloaded rpm to "install using Yast" still fails to find the file, yast forgets where it started and looks for the file in the configured installation sources. Another potential trouble spot seems to be with winbind. after starting a simple server and running the windoze domain membership in yast, opening a doze machine fails. another computer on the network, with 32 bit suse 10.0 installed, does see the doze machines. trying 'rcwinbind restart" results in 'daemon not running' error while 'a winbind pid exists in /var/run/samba'. in other oddities, vmware installed after i ran make modules_prepare, not just make prepare and mplayer considers gcc 4.10 'invalid'! disk access seems a bit too high, especially when firefox is running, that's with 2gb ram installed. zen etc were *not* removed. usb seems just fine. printing ( a problem with 10.0) seems fine or at least much improved. At this rate 10.1 will be ready for my main root partition before the end of this week. I do plan on keeping my /home partition intact. any suggestions? -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 05 June 2006 15:11, kanenas wrote:
ok, tried a new x86-64 install from the downloaded 10.1 dvd. This time it went much better. after i copied over parts of the 10.0 xorg.conf and installed the latest nvidia driver the lcd displays at1600x1200. The updates started working just fine without any changes, but after the kde repository was added, things sort of went south and there is no synchronization especially after the kde upgrade died. now i must go to the start of the updated softeware management test thread to find and apply the recommended fix. Also, a right click on a downloaded rpm to "install using Yast" still fails to find the file, yast forgets where it started and looks for the file in the configured installation sources. Another potential trouble spot seems to be with winbind. after starting a simple server and running the windoze domain membership in yast, opening a doze machine fails. another computer on the network, with 32 bit suse 10.0 installed, does see the doze machines. trying 'rcwinbind restart" results in 'daemon not running' error while 'a winbind pid exists in /var/run/samba'. in other oddities, vmware installed after i ran make modules_prepare, not just make prepare and mplayer considers gcc 4.10 'invalid'! disk access seems a bit too high, especially when firefox is running, that's with 2gb ram installed. zen etc were *not* removed. usb seems just fine. printing ( a problem with 10.0) seems fine or at least much improved. At this rate 10.1 will be ready for my main root partition before the end of this week. I do plan on keeping my /home partition intact. any suggestions?
Hi kanenas, Would you please split this large block of text up into meaningful paragraphs? These sentences just run together into one very long text string and I'm finding it very difficult to decipher. Second, you "hijacked" a thread. This means you hit 'Reply' to a message, changed the subject line then replaced the content to start a new thread (think "conversation.") What this does, in my in-box and many others, is cause a situation like this: [SLE] Re: Updated Software Management Test Repository... [SLE] Re: Updated Software Management Test Repository... [SLE] Re: Updated Software Management Test Repository... [SLE] 10.1 take 2 ** your post 'lands' here, mid-thread ** [SLE] Re: Updated Software Management Test Repository... [SLE] Some YaST2 problems in 10.1 [SLE] SaX2 problem in 10.1 [SLE] 10.1 take 2 ** your new topic post should land here ** As a suse-linux-e subscriber, the correct way to post a question (which starts a new thread) is to create a new message from scratch in your e-mail client. Thanks! Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 6/5/06, Andreas Jaeger
"Chuck Davis"
writes: Andereas:
Just went through the "procedure". All appeared to work well. After the "procedure" was complete tried to update with the updater and there is a dhcp package that, even though the popup says the update was successful, keeps popping itself back into the updater and the yellow updater will not become normal. The dhcp package will not disappear from the updater.
In my announcement I mentioned one more bug that needs to be fixed - and that's the one ;-). It's fixed now. Adrian will push updates out the next days at the usual place since I'm offline the next days,
The dhcp problem disappeared magically for me, along with a few other things after I added the boxed set DVD to my repositories. I originally upgraded using the download DVD (could not wait for my boxed set to arive) and then I applied the patch in this thread and I had the dhcp patch stuck as expected. I just ignored it. I also could not get my atiixp sound driver to work. Then my boxed set arrived, so I replaced the download DVD as source with the boxed set as source in YaST. The next day zen showed a number of updates. From the summaries it looked like it came from the boxed set DVD, so I let it upgrade. Suddenly the dhcp patch was not listed anymore, and my sound worked! Interesting.. At first I was a bit disappointed with the package management, but after applying the patch I felt more positive and now I am very happy. Thanks for the great work! -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre_tux@jabberafrica.org | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
<<<clip of large text block>>>
Hi kanenas,
Would you please split this large block of text up into meaningful paragraphs? These sentences just run together into one very long text string and I'm finding it very difficult to decipher.
Second, you "hijacked" a thread.
Sorry, I apologize. Can this be frozen or something?
This means you hit 'Reply' to a message, changed the subject line
yup, did that, i thought it avoided just what i actually accomplished.
then replaced the content to start a new thread (think "conversation.") What this does, in my in-box and many others, is cause a situation like this:
[SLE] Re: Updated Software Management Test Repository... [SLE] Re: Updated Software Management Test Repository... [SLE] Re: Updated Software Management Test Repository... [SLE] 10.1 take 2 ** your post 'lands' here, mid-thread ** [SLE] Re: Updated Software Management Test Repository... [SLE] Some YaST2 problems in 10.1 [SLE] SaX2 problem in 10.1 [SLE] 10.1 take 2 ** your new topic post should land here **
As a suse-linux-e subscriber, the correct way to post a question (which starts a new thread) is to create a new message from scratch in your e-mail client.
Thanks!
Carl
thanks for letting me know about the thread hijacking. something to learn every day. Now about those long sentences... it's an attempt to condense shtuff. sometimes it works, sometimes ...the bull wins:) dimitris -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Jun 5, 2006, at 7:09 PM, kanenas wrote:
This means you hit 'Reply' to a message, changed the subject line
yup, did that, i thought it avoided just what i actually accomplished.
some email clients are more friendly for this than others. thanks, george
On Tuesday 06 June 2006 01:20, suse_gasjr4wd@mac.com wrote:
On Jun 5, 2006, at 7:09 PM, kanenas wrote:
This means you hit 'Reply' to a message, changed the subject line
yup, did that, i thought it avoided just what i actually accomplished.
some email clients are more friendly for this than others.
In this respect KMail is extremely friendly: just click on the address in the "To:" field. That starts an empty message. ;) Cheers, Leen -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 05 June 2006 19:09, kanenas wrote:
thanks for letting me know about the thread hijacking. something to learn every day. Now about those long sentences... it's an attempt to condense shtuff. sometimes it works, sometimes ...the bull wins:)
Hi Dimitris, Thanks for taking the time to understand the problem. If you stay active on SLE, you'll find threading is very helpful. So... what was your original question or problem? ;-) Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Content-Disposition: inline
On Monday 05 June 2006 15:11, kanenas wrote:
ok, tried a new x86-64 install from the downloaded 10.1 dvd. This time it went much better. after i copied over parts of the 10.0 xorg.conf and installed the latest nvidia driver the lcd displays at1600x1200. The updates started working just fine without any changes, but after the kde repository was added, things sort of went south and there is no synchronization especially after the kde upgrade died. now i must go to the start of the updated softeware management test thread to find and apply the recommended fix. Also, a right click on a downloaded rpm to "install using Yast" still fails to find the file, yast forgets where it started and looks for the file in the configured installation sources. Another potential trouble spot seems to be with winbind. after starting a simple server and running the windoze domain membership in yast, opening a doze machine fails. another computer on the network, with 32 bit suse 10.0 installed, does see the doze machines. trying 'rcwinbind restart" results in 'daemon not running' error while 'a winbind pid exists in /var/run/samba'. in other oddities, vmware installed after i ran make modules_prepare, not just make prepare and mplayer considers gcc 4.10 'invalid'! disk access seems a bit too high, especially when firefox is running, that's with 2gb ram installed. zen etc were *not* removed. usb seems just fine. printing ( a problem with 10.0) seems fine or at least much improved. At this rate 10.1 will be ready for my main root partition before the end of this week. I do plan on keeping my /home partition intact. any suggestions?
Hi kanenas,
Would you please split this large block of text up into meaningful
At 06:31 PM 6/5/2006 -0400, Carl Hartung wrote: paragraphs?
These sentences just run together into one very long text string and I'm finding it very difficult to decipher.
/snip/ Have you ever had to try and read Cicero's Orations? --doug -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.394 / Virus Database: 268.8.1/355 - Release Date: 6/2/2006 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 05 June 2006 19:26, Doug McGarrett wrote:
Have you ever had to try and read Cicero's Orations?
Hi Doug, Don't tell me you read historical books, too? I haven't dug into Cicero's Orations, yet, but my current late night reading starts here: http://www.perseus.tufts.edu/cgi-bin/ptext?lookup=Plin.+Nat.+toc Check the timeline chart here: http://www.perseus.tufts.edu/cgi-bin/timevis?[split here manually] dheight=500&id=Perseus%3Atext%3A1999.02.0137 Fascinating stuff! Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Doug McGarrett wrote:
Have you ever had to try and read Cicero's Orations?
Does he run SUSE? ;-) -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
At 07:39 PM 6/5/2006 -0400, Carl Hartung wrote:
Content-Disposition: inline
On Monday 05 June 2006 19:26, Doug McGarrett wrote:
Have you ever had to try and read Cicero's Orations?
Hi Doug,
Don't tell me you read historical books, too? I haven't dug into Cicero's Orations, yet, but my current late night reading starts here: http://www.perseus.tufts.edu/cgi-bin/ptext?lookup=Plin.+Nat.+toc /snip/
Some 50 years ago I had to try and read that in the original language. I fully remember the page-full of single paragraph, sometimes single sentence. I never studied any more Latin. Cicero was a blow-hard, who thought he was above the common people. Most Romans would have had a great deal of difficulty understanding him. My mother had been a Latin student in college, with 8 years and a professor who taught in Latin, and she had trouble with Cicero, having been beyond him for quite some time. (I guess my professor, a Brother Anthony at Manhattan College understood it, but he was one of the most erudite men I ever met, may he rest in peace.) --doug -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.394 / Virus Database: 268.8.1/355 - Release Date: 6/2/2006 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Jerry Westrick wrote:
On Friday 02 June 2006 09:45, Andreas Jaeger wrote:
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions.
For testing the update stack do the following steps as root:
* 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.
IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one:
* 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.
* You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog.
* Restart zmd with "rczmd restart".
* Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update).
* 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.
We will really soon release now this as official update and therefore need your testing.
The only fix I'm waiting for is the following: Bug 180698 - zen-updater always shows patch dhcp (basically if a patch has been issued twice, it is always shown in zen-updater)
IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC hmuelle@novell.com (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02.
The update contains the following packages (basically the complete package stack):
* autoyast2 * libzypp * libzypp-zmd-backend * ruby-zypp * rug * suseRegister * yast2 * yast2-installation * yast2-instserver * yast2-ncurses * yast2-online-update * yast2-packager * yast2-perl-bindings * yast2-pkg-bindings * yast2-qt * zen-updater * zmd
The most important changes are:
* Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * Optimize and fix downloading of type zypp * Fix refreshing repositories of type zypp (#154990) * Add support for key handling to zmd, rug, zen-updater (#173920) * Fix zen-updater to handle installation of patch and package together (#178015) * Option to disable missing signature complaints is not persistent (#175845)
Followed your instructions. Worked as described. (I also have the DHCP package remaining after update).
No Problems here:
Sony VGN-A197VP, (I686, 768mb, SUSE 10.1 Pay)
Thx.
Jerry P.S. Amazing how much better I feel about 10.1 after that patch...
You are not alone, and there will be more. I know for at least one, as Xinerama works now :-) BTW, that was Xorg 6.9 problem, not SUSE. -- Regards, Rajko. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 05 June 2006 21:27, Rajko M wrote:
Jerry Westrick wrote:
P.S. Amazing how much better I feel about 10.1 after that patch...
You are not alone, and there will be more. I know for at least one, as Xinerama works now :-) BTW, that was Xorg 6.9 problem, not SUSE.
There has been a steady stream of positive feedback after the patch was released. This is precisely the point I was trying to make with the "pair" of anonymous "posters" who, in very troll-like fashion, went to great lengths to repeatedly criticize 10.1 while ignoring the progress being made. I'm very pleased with the way 10.1 has come into form and I'm particularly happy to see this steady stream of well deserved positive feedback continue! regards, Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 02 June 2006 09:45, Andreas Jaeger wrote:
We're currently pushing out an update to the package/patch management stack and I'm asking for additional testing. The previous repository did not show any new bugs but we fixed a couple of more bugs and made this time a repository with a real patch in it for testing. Please read the text below for instructions.
For testing the update stack do the following steps as root:
* 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.
IMPORTANT: If you tested my old sources already, you need to download the metadata again (this is not needed afterwards anymore, it's one of the fixes in this new update). Skip this step and go to the next one:
* 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.
* You can now remove the software catalog you added in the first step. Use "yast2 inst_source" and delete the catalog.
* Restart zmd with "rczmd restart".
* Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update).
* 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.
We will really soon release now this as official update and therefore need your testing.
The only fix I'm waiting for is the following: Bug 180698 - zen-updater always shows patch dhcp (basically if a patch has been issued twice, it is always shown in zen-updater)
IMPORTANT: Please report *all* bugs in bugzilla.novell.com and *always* CC hmuelle@novell.com (Harald Müller-Ney) on the bugreport and mention that you're using AJ's updated package stack from 2006-06-02.
The update contains the following packages (basically the complete package stack):
* autoyast2 * libzypp * libzypp-zmd-backend * ruby-zypp * rug * suseRegister * yast2 * yast2-installation * yast2-instserver * yast2-ncurses * yast2-online-update * yast2-packager * yast2-perl-bindings * yast2-pkg-bindings * yast2-qt * zen-updater * zmd
The most important changes are:
* Do not create anymore /.gnupg (the directory can be removed) (#171055) * Handle daemons launched in rpm %post that do not close filedescriptors (#174548) * Really get all package descriptions (#159109) * Support large files, e.g. DVDs as installation source (#173753) * Handle update source setup after installation (#172665) * Do not add duplicate update sources (#168740) * Fix yast2 instserver module so that it works with 10.1 (#171157) * Do not exit in online_update when only packages (and no patches) are selected for installation or deletion (#175668) * Improve syncronising sources between yast and zmd (#168740, 175174, 175159, 175173) * Fix segmentation fault with non-signed repositories (#173291) * Handle system proxy setting with zmd (#160830) * Fix zen-updater bugs when installing packages (#171171, 174740) * Update packages to follow ABI change in libzypp. * Optimize and fix downloading of type zypp * Fix refreshing repositories of type zypp (#154990) * Add support for key handling to zmd, rug, zen-updater (#173920) * Fix zen-updater to handle installation of patch and package together (#178015) * Option to disable missing signature complaints is not persistent (#175845)
Followed your instructions. Worked as described. (I also have the DHCP package remaining after update). No Problems here: Sony VGN-A197VP, (I686, 768mb, SUSE 10.1 Pay) Thx. Jerry P.S. Amazing how much better I feel about 10.1 after that patch... -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 05 June 2006 1:07 pm, Chuck Davis wrote:
Andereas:
Just went through the "procedure". All appeared to work well. After the "procedure" was complete tried to update with the updater and there is a dhcp package that, even though the popup says the update was successful, keeps popping itself back into the updater and the yellow updater will not become normal. The dhcp package will not disappear from the updater.
It's broken......all of us, as far as I know have the same problem. Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 05 June 2006 9:27 pm, Rajko M wrote: [snip]
You are not alone, and there will be more. I know for at least one, as Xinerama works now :-) BTW, that was Xorg 6.9 problem, not SUSE.
The updater might work here now, except that there are 3 files showing for update.....one is kdebase-3-SUSE that has UNresolved dependancies, so the others won't install.....even when I deselect the file. :( Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Fred A. Miller wrote:
On Monday 05 June 2006 9:27 pm, Rajko M wrote:
[snip]
You are not alone, and there will be more. I know for at least one, as Xinerama works now :-) BTW, that was Xorg 6.9 problem, not SUSE.
The updater might work here now, except that there are 3 files showing for update.....one is kdebase-3-SUSE that has UNresolved dependancies, so the others won't install.....even when I deselect the file. :(
Fred
I can't get any of this stuff to work. More than just frustrating. One thing I am concerned about is the list of INSTALLATION SOURCES which should be used. I have been looking at all the responses in this and other related threads and have seen a pletora of installation sources which ought to be used to get the system updated. I think it may now be the time to review this list and get a "the most desirable" list of sources for use with the ZMD and and/or YOU update facilities. I am not talking here about what is needed for apt or smart. These can wait for a later time. All I care about is getting what is officially recognised by SUSE in 10.1. The list I am using and which I gleaned from the various messages is: 1. cd:///?device=/dev/hdb,/dev/hdd 2. http://mirror.pacific.net.au/suse/update/10.1 3. http://packamn.iu-bremen.de/suse/10.1 4. http://mirrors.kernel.org/opensuse/distribution/SL-10.1/inst-source 5. http://mirrors.kernel.org/opensuse/distribution/SL-10.1/non-oss-inst-source 6. ftp://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.1 7. http://software/opensuse.org/download/repositories/KDE:/KDE3/SUSE_Linux_10.1 8. http://software.opensuse.org/download/repositories/KDE:/Backports/SUSE_Linux... The first 2 (1 and 2) are sources which from the installation process of 10.1. The rest I added. No. 3 produces a "Failed Signature" error which I ignore, and I think, from memory, the same happens for 6. Are the above installation sources what one should use? Or is there a list of what MUST be used - with a list of some additional "these could also be used" sources? Cheers. -- Indecision is the key to flexibility. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 08 June 2006 2:39 am, Basil Chupin wrote:
Fred A. Miller wrote:
On Monday 05 June 2006 9:27 pm, Rajko M wrote:
[snip]
You are not alone, and there will be more. I know for at least one, as Xinerama works now :-) BTW, that was Xorg 6.9 problem, not SUSE.
The updater might work here now, except that there are 3 files showing for update.....one is kdebase-3-SUSE that has UNresolved dependancies, so the others won't install.....even when I deselect the file. :(
Fred
I can't get any of this stuff to work. More than just frustrating.
One thing I am concerned about is the list of INSTALLATION SOURCES which should be used. I have been looking at all the responses in this and other related threads and have seen a pletora of installation sources which ought to be used to get the system updated. I think it may now be the time to review this list and get a "the most desirable" list of sources for use with the ZMD and and/or YOU update facilities.
I am not talking here about what is needed for apt or smart. These can wait for a later time. All I care about is getting what is officially recognised by SUSE in 10.1.
The list I am using and which I gleaned from the various messages is:
1. cd:///?device=/dev/hdb,/dev/hdd
[snip] Use Yast2 to get these.....choose packages, then "zzz" that is "all", then choose the files one by one, and update. Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 08 June 2006 2:39 am, Basil Chupin wrote:
Fred A. Miller wrote:
On Monday 05 June 2006 9:27 pm, Rajko M wrote:
[snip]
You are not alone, and there will be more. I know for at least one, as Xinerama works now :-) BTW, that was Xorg 6.9 problem, not SUSE.
The updater might work here now, except that there are 3 files showing for update.....one is kdebase-3-SUSE that has UNresolved dependancies, so the others won't install.....even when I deselect the file. :(
Fred
I can't get any of this stuff to work. More than just frustrating.
Sorry....the address is: (http) software.opensuse.org and dir. is: download/KDE:/KDE3/SUSE_Linux_10.1 Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Fred A. Miller wrote:
Use Yast2 to get these.....choose packages, then "zzz" that is "all", then choose the files one by one, and update.
or even better, after choosing Package Groups, then zzz to get all, then in the Package menu at the top, choose All in this list, then Update if newer version available. Then, Go back to the filter drop down and choose Installation summary to double check all that will be done. Hit the Check button to check dependencies. Then accept to do everything. Works great without going through all those packages one by one. -- Joe Morris Registered Linux user 231871 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Joe Morris (NTM) wrote:
Fred A. Miller wrote:
Use Yast2 to get these.....choose packages, then "zzz" that is "all", then choose the files one by one, and update.
or even better, after choosing Package Groups, then zzz to get all, then in the Package menu at the top, choose All in this list, then Update if newer version available. Then, Go back to the filter drop down and choose Installation summary to double check all that will be done. Hit the Check button to check dependencies. Then accept to do everything. Works great without going through all those packages one by one.
Many thanks for this suggestion!. Cheers. -- Indecision is the key to flexibility. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Fred A. Miller wrote:
On Thursday 08 June 2006 2:39 am, Basil Chupin wrote:
Fred A. Miller wrote:
On Monday 05 June 2006 9:27 pm, Rajko M wrote:
[snip]
You are not alone, and there will be more. I know for at least one, as Xinerama works now :-) BTW, that was Xorg 6.9 problem, not SUSE. The updater might work here now, except that there are 3 files showing for update.....one is kdebase-3-SUSE that has UNresolved dependancies, so the others won't install.....even when I deselect the file. :(
Fred I can't get any of this stuff to work. More than just frustrating.
One thing I am concerned about is the list of INSTALLATION SOURCES which should be used. I have been looking at all the responses in this and other related threads and have seen a pletora of installation sources which ought to be used to get the system updated. I think it may now be the time to review this list and get a "the most desirable" list of sources for use with the ZMD and and/or YOU update facilities.
I am not talking here about what is needed for apt or smart. These can wait for a later time. All I care about is getting what is officially recognised by SUSE in 10.1.
The list I am using and which I gleaned from the various messages is:
1. cd:///?device=/dev/hdb,/dev/hdd
[snip]
Use Yast2 to get these.....choose packages, then "zzz" that is "all", then choose the files one by one, and update.
Fred
Thanks Fred. Cheers. -- Indecision is the key to flexibility. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (21)
-
Andre Truter
-
Andreas Jaeger
-
António Rodrigues Tomé
-
Basil Chupin
-
Brian Blater (BBList)
-
Bruce A. Mallett
-
Carl Hartung
-
Chuck Davis
-
Doug McGarrett
-
Felix Miata
-
Fred A. Miller
-
ianseeks
-
James Knott
-
Jerry Westrick
-
Joe Morris (NTM)
-
kanenas
-
Leendert Meyer
-
Nick Murphy
-
Rajko M
-
Stephen Boddy
-
suse_gasjr4wd@mac.com