June 2006 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Software Updater
by Kenneth Schneider 07 Jun '06

07 Jun '06

Would it be possible/feasible to change the messages presented in Software Updater to read "Getting update list..." while fetching the info then change to "Parsing medadata..." and finally "Incorporating medadata..." before is shows whether there are updates? This would at lease show that it is doing something. On slower hardware you cannot tell if it has hung or just simply taking an enormous amount of time. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

3 2

[opensuse-factory] drpmsync hangs
by factory.22.anomalyst＠xoxy.net 06 Jun '06

06 Jun '06

It was running successfuly from a script, but now it prints "getting file list..." and sits there for hours if I let it. Eyeballing the switch activity indicates no traffic is flowing. Is anyone else seeing this? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

2 1

[opensuse-factory] Updated Software Management Test Repository
by Andreas Jaeger 04 Jun '06

04 Jun '06

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(a)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) Thanks for testing and bug reporting, Andreas -- Andreas Jaeger, aj(a)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

6 10

[opensuse-factory] hello
by Harry ten Berge 03 Jun '06

03 Jun '06

Hi, Anybody here? Regards Harry --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

3 3

[opensuse-factory] Using LVM by default for new installations?
by Lenz Grimmer 03 Jun '06

03 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I noticed that Fedora seems to have switched to using Logical Volumes for installing on the hard disk since FC4. I personally am using LVM myself for a very long time and must say I am very fond of it. It provides much more flexibility than using plain partitions, especially when it comes to resizing or moving file systems or taking backups. I'd like to propose that SUSE Linux considers switching to this scheme for new installations by default, too - I now filed this as an enhancement request in Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=180762 What do others think about that? Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz(a)grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr(a)jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEfuaxSVDhKrJykfIRAqBHAJ4jgzPdUys0twki8wipgJusPNPPRwCggGDp yxrMT4gLKr/QsCOiYIFFhX8= =BW9y -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

10 33

[opensuse-factory] High Utilization with zen components
by Chad Groneman 02 Jun '06

02 Jun '06

Hello everyone, This has probably been addressed somewhere in a thread somewhere, but I can't see it. Anyway, I've noticed that whenever I do anything with the new software management tools (ZEN tools), my system's fans crank up. I check top and see that my utilization is in the high 90's or even 100. I don't know if it's a bug or not, but it bothers me a great deal. I don't like my system to have to crank up the fans to do something as simple as check to see if there are updates available, or install an RPM. I have a desktop, but I think laptop users would be screaming about this, as it's gonna kill their batteries a lot sooner. -Chad --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

3 2

Bug handling
by Andras Mantia 02 Jun '06

02 Jun '06

Hi, Can someone from SUSE tell me how bug handling is done there? I mean, if there is a bug reported for some version and is not fixed in that version, is it taken in account for upcoming versions or it is just forgotten? An example: - a bug (like #176249 and previously #148638) is reported for 10.0 - it was closed with WONTFIX as the change cannot be made to a released product - the bug is still present in 10.1 (somebody reports again) - the bug is closed again as "it's too late and risky to do it" - the bug is still present and will be possibly present in 10.2 (unless it's "fixed" upstream) (The upcoming possible scenario is: - somebody reports "still present in 10.2" in a new bug - it get's closed as "too late now for 10.2, maybe 10.3) The problem I have is not the fact that is not fixed, but the fact that the bug report is closed even if it is present (and gets forgotten). In KDE we do the following: if a bug is reported for version X it is considered to be present in all versions > X unless somebody says otherwise, but in case of SUSE this doesn't seem to be the case. Please enlighten me. ;-) Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org

9 9

[opensuse-factory] packages in the future to be added or deleted
by houghi 02 Jun '06

02 Jun '06

I know that there will always be packages that can't make it. How does the team that decides what goes on and what not do this? e.g. does it only listen to customer feedback (e.g. bugzilla) or does it also look at how often certain packages are downloaded? I understand thatSUSE does not have control over all mirrors (or over any), yet I couild imagine that some mirrors could share the numbers of packages for this purpose. Not that they must. It would just be nice if they did so. If these numbers are known, it might be easier to determine what is needed and what not. Just curious. For me you made an almost excelent choice. -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html > > Today I went outside. My pupils have never been tinier... --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

1 0

Update stack test build
by Graham Anderson 02 Jun '06

02 Jun '06

Morning folks, Would this list be the best place to post feedback regarding the test build of the update stack packages you posted yesterday Andreas? Or is it better moved to bugzilla...? If so I can move all this to bugzilla with logs etc. Here are my observations so far anyway. 1. The 10.1 release update stack successfully installed the test builds after I added the URL as a YUM service via zen-updater. However the whole upgrade took an extremely long time ( 15 minutes approx ). I was unable to determine why it was taking so long, i dont *think* it was the downloading... 2. Adding services via rug is just fine, and as per the 10.1 release builds ZYPP services are synced with YaST, YUM services are not. Adding services via zen-updater, same as rug, it works and the synching is the same. 2. Adding a larger service such as main online installation from mirror( inst-sources ) is much smoother. The service itself was added to the list in yast inst_sources almost instantaneously and unlilke the 10.1 release the catalog was not immediately downloaded but was only fetched when the finish button was pressed. At a rough guess I would say the whole process of adding the main installation source is 50% quicker now. 3. ZMD scheduling seems to be a bit broken now. It appears that the service refresh happens at the same time as the hourly maintenance, even though it is scheduled for the next day. Once the full service refresh and maintenance has run ( hourly by default it seems ) the schedule is reset with an updated time for the service refresh 24 hours later and 1 hour later for the maintenance. Of course the service refresh still happens one hour later and another new time i scheduled for it. This has the side effect of a full service refresh will run if my system is booted outside of the hourly maintenance window, parse-metadata and update-status hogging 100% CPU for a few minutes on boot. If i reboot my system inside the hourly maintenance window this does not happen.

7 13

my XML project
by houghi 01 Jun '06

01 Jun '06

As some will remember, I had a talk about an xml project. I have decided to drop this due two two reasons. Partly because of my limited knowledge of XML. but mostly because of the great work and better solution that was given with download.suse.com and download.opensuse.org. I believe the solution as it is now is much better and will only improve an there is no need to re-invent a tool that already exists and is made people who actually know what they are doing (thanks for that) I will (probably today) test what 10.1 sources can be added and which ones still give problems from the external repo's from http://en.opensuse.org/Additional_YaST_Package_Repositories -- houghi http://houghi.org http://www.plainfaqs.org/linux/ http://www.netmeister.org/news/learn2quote.html > > Today I went outside. My pupils have never been tinier...

3 4