Re: [opensuse-factory] Summary: Games on openSUSE 10.2
Stefan Dirsch [EMAIL PROTECTED] writes: Hi I try to summarize the discussion on Games on openSUSE 10.2. Thanks. I think we agree, that we should still include games in our default installation and provide a Games pattern for all games (check for RPM group 'games', Andreas) on our distribution. Additionally there are some games which would be nice to have on our distribution or in the buildservice. Games for default Installation: --- GNOME:gnome-games KDE:kdegames (kmines,kpat) KDE:knights KDE:ksudoku chromium frozen-bubble freeciv lbreakout supertux xmoto We can also add to the pattern a list of suggestions, meaning packages that will not get installed but users can choose from, so the other recommendations could be added as suggestions. I'll create the above pattern the next days (after Alpha4), Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpKNOoZmsiYj.pgp Description: PGP signature
Re: [opensuse-factory] dist meeting 2006-08-31: Minutes
Juan Erbes [EMAIL PROTECTED] writes: 2006/9/4, Andreas Jaeger [EMAIL PROTECTED]: Juan Erbes [EMAIL PROTECTED] writes: Do You will to continue supporting KDE? Yes. Why did you ask in this context? I asked in this context, because I do'nt see any mention about kde. There was no need to discuss anything related to KDE in that meeting. We only discuss specific topics as they arise. We do support both and continue working on both. I'm sorry, because my english is so poor! No problem - most of us are not native speakers, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpPRvoD83dZ3.pgp Description: PGP signature
[opensuse-factory] Packages in default installation
Hi, during one of our IRC meetings, I've been asked to discuss the size of our core distribution. I'm appending the list below and would like to hear your concrete suggestions. Some of the packages are needed by dependencies, we could split some packages into separate (optional) patterns, Andreas Required (must have): aaa_base aaa_skel acl ash attr audit-libs autoyast2 autoyast2-installation autoyast2-utils bash bzip2 checkmedia coreutils cpio cpp cracklib cups-client cups-libs curl cyrus-sasl cyrus-sasl-saslauthd db db-utils dbus-1 device-mapper diffutils e2fsprogs ed eject ethtool evms file filesystem fillup findutils glibc gnome-icon-theme grep groff gzip hwinfo insserv iproute2 iptables iputils kbd klogd krb5 ksymoops ldapcpplib less libacl libattr libcap libcom_err libgcc libnscd libxcrypt liby2util libzypp limal limal-bootloader limal-perl logrotate lvm2 m4 mailx make mdadm mingetty mkinitrd mkisofs mktemp module-init-tools multipath-tools ncurses net-tools netcfg openssh openssl pam pam-config pam-modules parted perl permissions procps psmisc pwdutils reiserfs rpm sed openSUSE-release suse-build-key sysconfig sysfsutils syslog-ng sysvinit tar tcpd util-linux vim w3m wget yast2 yast2-bootloader yast2-core yast2-country yast2-dhcp-server yast2-dns-server yast2-firewall yast2-hardware-detection yast2-installation yast2-instserver yast2-ldap yast2-ldap-client yast2-mail-aliases yast2-mouse yast2-ncurses yast2-network yast2-nfs-client yast2-nfs-server yast2-nis-client yast2-nis-server yast2-ntp-client yast2-online-update yast2-online-update-frontend yast2-packager yast2-pam yast2-perl-bindings yast2-pkg-bindings yast2-printer yast2-runlevel yast2-samba-client yast2-samba-server yast2-schema yast2-security yast2-storage yast2-storage-lib yast2-support yast2-sysconfig yast2-tftp-server yast2-theme-SuSELinux yast2-transfer yast2-tune yast2-update yast2-users yast2-xml zlib #ifdef __ia64__ elilo efibootmgr ia32el #endif #if defined(__i386__) || defined (__x86_64__) microcode_ctl grub lilo #endif #ifdef __powerpc__ lilo #endif Recommended (should have): qlogic-firmware OpenIPMI SuSEfirewall2 acpid at autofs bc bind-libs bind-utils binutils blocxx bootcycle bootsplash bootsplash-theme-SuSE compat compat-libstdc++ compat-openssl097g convmv cpufrequtils cron dbus-1-glib delayacct-utils deltarpm dhcpcd dmraid dos2unix dosfstools expat fbset finger freetype2 gawk gdb gdbm gettext glib2 glibc-i18ndata glibc-locale gnome-filesystem gpart gpg gpm hal hdparm hfsutils ifplugd info initviocons ipmitool ivman jfsutils joe ksh libevent libgcrypt libgpg-error libgssapi libidn libjpeg liblcms libmng libpcap libpfm libpng librpcsecgss libstdc++ libtiff libtool libusb libxml2 libxslt libzio linux32 log4net lsof lukemftp man man-pages master-boot-code mcelog mono-core mono-data mono-web mpt-status netcat nfs-utils nfsidmap nscd ntfsprogs numactl openct openldap2-client opensc openslp openslp-server patch pax pciutils pcre pcsc-lite pdisk pfmon pmtools popt portmap postfix powerpc32 powersave powersave-libs ppp pptp prctl procinfo procmail providers readline recode release-notes resmgr rsh rsync rug salinfo sash scpm screen scsi sharutils siga smartmontools smpppd sqlite star strace sudo suseRegister suspend syslinux tcpdump tcsh telnet terminfo timezone udev unzip usbutils utempter vlan wireless-tools wol wvdial wvstreams xfsprogs xinetd xntp yast2-backup yast2-boot-server yast2-bootfloppy yast2-cd-creator yast2-heartbeat yast2-http-server yast2-inetd yast2-irda yast2-iscsi-client yast2-iscsi-server yast2-kerberos-client yast2-mail yast2-power-management yast2-powertweak yast2-profile-manager yast2-repair yast2-restore yast2-slp yast2-slp-server yast2-vm yp-tools ypbind zip zisofs-tools zmd zsh Suggested (optional): exim sendmail Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpjbFPc9d4M7.pgp Description: PGP signature
Re: [opensuse-factory] Packages in default installation
Felix Miata [EMAIL PROTECTED] writes: Which from that list is an OFM? What do you mean with OFM? Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpfI0f5r8BiC.pgp Description: PGP signature
Re: [opensuse-factory] Packages in default installation
vetter [EMAIL PROTECTED] writes: On Tue, 5 Sep 2006, Andreas Jaeger wrote: Recommended (should have): postfix ... Suggested (optional): exim sendmail should be: Recommended (should have): Required ;-) mta where postfix, exim or sendmail provide mta And we would need to preselect one, so add postfix to recommended. Yes, doable, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp5OiST1AhMW.pgp Description: PGP signature
[opensuse-factory] dist meeting 2006-08-31: Minutes
Here're my minutes from the last meeting. PolicyKit / ResMgr == PolicyKit is a control instance that can be asked before performing an action and therefore can restrict what a user can do on a desktop. It's a system wide daemon, currently running as root. Problems: * Another daemon * possible code quality * overlaps in parts with resmgr Resmgr grants access via ACL to logged in users which is something that PolicyKit does not handle. The consensus was that the features of PolicyKit are liked. We would like to implement the features of resmgr in PolicyKit and drop resmgr so that we have only one daemon running. This needs further evaluation. In 10.2 only hal mounter will use PolicyKit. We plan to have the integration with resmgr done for 10.3. Cryptofs We currently use crypto-loop to setup crypt-partitions. It has been proposed to use the new dm-cryptoloop with LUKS extensions. Since this needs changes in YaST and the boot scripts, it might not be doable for 10.2. We'll investigate this now. Removing Build Dependencies === The minimal set of packages to bootstrap the by default added packages (those that will be added if BuildRequires is empty) consists of 209 packages. The added packages contain some convenience packages like vim and strace for debugging. We discussed the goal to identify a small set of core packages for bootstrapping or for a core distribution. The discussion will continue on mailing lists, the people at the meeting did not see that any directly needed action. GNOME 2.16 and /usr === Currently factory has three bugs, the major one is a broken metacity which has just been fixed. The goal is to get everything this until 2006-09-01 into the distribution so that we can do basic tests and then have Alpha4 with GNOME 2.15.92. Once GNOME 2.16 is working properly, the team plans to move from /opt/gnome to /use. This is done in separate steps to make debugging easier. This move has to be done by the end of september - in time for Alpha5. If not, it will be done for 10.3. GNOME will use the %configure and %install rpm macros. No objections from anybody. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpSrKbZ36NsR.pgp Description: PGP signature
Re: [opensuse-factory] Package Manager Update 3: Call for Testing
I updated the repository with some additional fixes for those issues that were reported. Thanks for your testing! Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp8uvWqQW5if.pgp Description: PGP signature
Re: [opensuse-factory] dist meeting 2006-08-31: Minutes
Juan Erbes [EMAIL PROTECTED] writes: Once GNOME 2.16 is working properly, the team plans to move from /opt/gnome to /use. This is done in separate steps to make debugging easier. /use complains Posix standar? Typo: /usr - this is in accordance with the Filesystem Hierarchy Standard, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpmhvQvtwpj7.pgp Description: PGP signature
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
Terje J. Hanssen [EMAIL PROTECTED] writes: Missing Xen: Maybe this is not the right place, but I really miss Xen on the announced Features and Roadmap for openSUSE 10.2. The Status of Xen3 on SUSE Linux 10.0, which is the only and latest I still can see, is http://en.opensuse.org/Xen3_Status_and_Updates Xen will be improved as usual. The last line in that table, Other Operating System support on top of Xen and VT not tested is especially of interest to follow up now. XenSource is also just releasing their XenEnterprise with support Linux guest operating systems with Windows support following before the end of 2006 in alignment with the broad availability of Intel and AMD server systems designed to support Xen. XenEnterprise is promises to make it very easy for an organization to install, configure, manage and monitor virtualized Windows and Linux operating systems running across multiple physical servers. What I really wish is that openSUSE 10.2 will offer some smaller Xen workstation solution that with YaST tools can ease the installation, configuration and administration of Xen and typical and actual i.e Ubuntu Linux and Windows XP as additional guest operating systems on Intel-VT and AMD-V workstations. We have some improvements in this area already in our current tree but I'm not sure what exactly you have in mind. Please look at Alpha4 and give some more details. If this features is possible to include, I think it will further power openSUSE 10.2 ? Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpGowObAGFy3.pgp Description: PGP signature
Re: [opensuse-factory] Package Manager Update 3: Call for Testing
Andreas Hanke [EMAIL PROTECTED] writes: Andreas Jaeger schrieb: That one was fixed in the meantime, so there's no general problem in adding it to our tree. But let's look at the details, I've reopened it now. It's this commit: http://lists.opensuse.org/archive/opensuse-commit/2006-08/msg00846.html And from there, basically +Requires: unzip in package yast2-installation. Thanks - this is getting added now, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpPGi6n5Kddv.pgp Description: PGP signature
Re: [opensuse-factory] Package Manager Update 3: Call for Testing
Andreas Hanke [EMAIL PROTECTED] writes: Hi, Andreas Jaeger schrieb: We do not plan to add further fixes, our goal is to get this update out and find any regressions introduced. Is that a final decision? No ;-) That's the plan. I prefer to not hold up the release because of extra fixes that people like to see. What about the missing unzip bug: https://bugzilla.novell.com/show_bug.cgi?id=195911 That one shouldn't be too risky and it had 3 dupes in a month. That one was fixed in the meantime, so there's no general problem in adding it to our tree. But let's look at the details, I've reopened it now. I think that users of a minimal installation would appreciate it if YaST could fix itself during an online update without manual intervention. Yeah... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpcyuED79Vhw.pgp Description: PGP signature
Re: [opensuse-factory] Adding SBIG CCD camera support to SUSE?
Jasem Mutlaq [EMAIL PROTECTED] writes: With such an unclear license situation, we cannot take these for openSUSE at all. I'll get back to the vendor and ask them for the license details regarding the firmware. Yes please do so. Please also ask for permission to distribute the firmware with commercial SUSE Linux Products. Hello, I contacted SBIG regarding the _distribution_ of their firmware in SUSE and they have no problem with it. They also have no problem in packaging their binary library in a SUSE non-OSS RPM, which I will release later. Now regarding the firmware, what sort of licence/agreement do you require from SBIG to release/sign so we can bundle their firmware in SUSE? Let's handle this offline - thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpVbvg0g9kG8.pgp Description: PGP signature
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
Azerion [EMAIL PROTECTED] writes: --- Thu, Oct 26 openSUSE 10.2 Beta1 release (feature complete) --- Thu, Nov 9 openSUSE 10.2 Beta2 release --- Thu, Nov 23 openSUSE 10.2 RC1 release --- Thu, Nov 30 openSUSE 10.2 GM release --- Thu, Dec 7 openSUSE 10.2 public release Hello? Hello? What did we learn from the last SUSE Linux edition? 1.) Never change features in beta 3 2.) Work until everything is fixed despite stores waiting 1.) It can't happen again, we have planned 2 beta's. Is this a real solution? We have put freezes in place so that this will not happen. Alpha5 could be called Beta0 ;-) I would rather see a list as followed: Thu, Oct 26 openSUSE 10.2 Beta1 release (feature complete) Thu, Nov 9 openSUSE 10.2 Beta2 release Thu, Nov 16 openSUSE 10.2 Beta3 release notice only 1 week Thu, Nov 30 openSUSE 10.2 RC1 release Thu, Dec 7 openSUSE 10.2 RC2 release notice only one week Thu, Dec 21openSUSE 10.2 GM release (or the 14th) Thu, Dec 28 openSUSE 10.2 public release (or the 21th) 2-3 more weeks dev-time and 1 extra beta and 1 extra RC. It will probably come to that after all so let's just plan it right away. I know we won't have All releases before 10.1 were delivered on time. zen-shit this time but we don't have to hurry. If there are no blockers/showstoppers anymore there are little things that can be fixed. This kind of schedule would not work due to christmas for us. The only alternative would be a release in february and that one does not work for scheduling reasons in our team. Vista will come out around begin 2007 and websites will compare both. Let's make sure we win the contest by having all those irritating little bugs smashed also (and certainly the big ones). We don't have to hurry, we have to deliver quality. That's what we're working already on, the Alphas help with those, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpL5W1FjnDzM.pgp Description: PGP signature
[opensuse-factory] Agenda for tomorrow's distribution meeting
Here're the agenda itmes that we plan to discuss tomorrow. Please send input/ask questions etc and I'll bring your input into the meeting. Note that not everything discussed is something that will end automatically in 10.2 - we might reject or postpone some stuff. * PolicyKit/resmgr Continuing discussion from last time. * crypto FS Kay proposes to replace cryptsetup with: http://luks.endorphin.org/dm-crypt LUKS is a standardized media encryption key handling and on-disk metadata format. Usually it's used with a dm-crypt device-mapper device. The cryptseup-luks tools are intended as a complete, backwards-compatible replacement for the original cryptsetup. LUKS stores a crypto-volume header at the beginning of the volume, so it can be safely probed and detected. Keys and encryption metadata are stored in the header of the volume. For details, see: http://luks.endorphin.org/about http://luks.endorphin.org/LUKS-on-disk-format.pdf The complete LUKS crypto Desktop support is already fully implemented in HAL and GNOME (including password-prompt, automount, password storage in gnome-keyring). The SUSE repository only misses an official version of the low-level tools, every other major distribution already ships it. * Removing build dependencies, speeding up the build process Richard proposes to remove dependencies so that building of a complete distribution can be speed up. * GNOME 2.16 and /usr Schedule/plan * /dev/hd removal: http://lkml.org/lkml/2006/8/9/285 * Building distribution for i386/x86-64 with -mtune=generic Proposal: Build distribution with these flags. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpIshrHTSfYT.pgp Description: PGP signature
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
Azerion [EMAIL PROTECTED] writes: This is a mail that I send to Andreas some days ago: It is a reply so the start is not like a normal startpost. Thanks for resending it here. Sorry, personal email sometimes takes time to answer :-( People are confused by seeing Httpserver, DNS-server and so on in YaST. YaST is great but at this moment it becomes 'unorganised' (posted a bugzilla on that some month ago) in the way that it offers to much that is not needed (and not properly bundeld). Same thing is the case at this moment in SL 10.1 with ZEN (not in one screen but 3 apps) Another thing about YaST is the following: At this moment YaST is used to install SL/oS. Looking at other distro's and OS's it is great and it works. But it is not _that_ good looking and not _that_ simple and fast to use. Maybe an idea for 10.3 to pimp the install and change some things Idea 1: Do not use 'windows' like we do use it now. It should be a fullscreen 'background'. That way you can change the background of the installer every release and that would be nice. Look at the links and scoll that page. That looks nice to mr. Joe Average! http://wiki.freespire.org/index.php/Screenshot_Submissions#Freespire_Welcome_Screen Something I liked - we even discussed this over a year ago and then other things become more important :-(. Could you add this to the wishlist, please? Idea 2: Let the user select what screens he/she wants to use default: default/expert. On every screen in default there will be an option to see expert-options but you don't have to make the choice every time. The problem is that most people want one expert option but not all. So, allowing the choice is needed - but on the other hand I think that with our proposals we do something similar as well. Idea 3: This one is stolen from Vista. Drop those radiobuttons (round things) and replace it with an nice arrow that directly reponse. Idea 4: Do not show more information the needed in default. I don't care what step I have had and which one will come next. So the progress-tree can be dropped in default (maybe a little button to show and give the opportunity to go back some steps to change a setting). When SL is installing you see stats This is controversial - usability tests show that the progress bar is important. about each disk, packages, size and so on. The only thing the customer wants to now is : - how far are we in total? - how long will it take from now on? - when do I need to insert another cd? []no numbers! Estimated: 12 minutes Next CD: 2 minutes Under that there is a lot of space for a slideshow I guess. We do have the slideshow. Idea 5: Take care of that you show a lot of nice things in the slideshow. 3 buttons: prev, next, diashow. It uses some space on the disk but new users will welcome it What exactly do you suggest here? Do you have some comments on it. Some point have reached the ML and bugzilla before but I guess this time I want to make a mockup if there is a chance that it will be redesigned. No chance for 10.2 to do fundamental changes but a mockup is something I would like to see. Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpIyW5zsrGPv.pgp Description: PGP signature
Re: [opensuse-factory] Package Manager Update 3: Call for Testing
Azerion [EMAIL PROTECTED] writes: WARNING! WARNING! Fine, ZEN-updater did not abort because of dependencies problems. Not so fine, it did not complain and suggested to delete X11-xorg! As noob-user ;-) I just clicked okey hoping that ZEN would say: no you can't do that. As you can guess after reading my first line: it did not complain and delete X11-xorg! Gald I am not a noob-user and yast did the job well. And this was supposed to be released this week? Probably a bad idea huh Could you file a bugreport, please? Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpbtGX5ZbqGY.pgp Description: PGP signature
Re: [opensuse-factory] Agenda for tomorrow's distribution meeting
Boyd Lynn Gerber [EMAIL PROTECTED] writes: On Wed, 30 Aug 2006, Robert Schiele wrote: On Wed, Aug 30, 2006 at 03:48:28PM +0200, Richard Guenther wrote: This basically boils down to first identifying the dependency sets for - the install-time dependencies of a minimal install - the build-requirements to build the minimal install system - the build and install-time requirements of the minimal build-root and so identify the current CORE system. From that prune out things that we do not want in that CORE system (like emacs) by fixing package install and build time dependencies. Do not remove emacs. I use it. Do you need it in the CORE build system? Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp0gBv5W5ka8.pgp Description: PGP signature
Re: [opensuse-factory] Agenda for tomorrow's distribution meeting
Boyd Lynn Gerber [EMAIL PROTECTED] writes: Do you need it in the CORE build system? Maybe I look at core wrong. I feel a core system should have vi and emacs as the default editors. I do not want to cause a vi/emacs debate. So they should be in core. In the context of Richard's suggestion, we speak about the CORE build system for automatically building packages and that one does not need an editor at all. The CORE install systems needs one - and both emacs and vi should be in it. Hope that solves the confusion here, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp3NFpjgNEF9.pgp Description: PGP signature
[opensuse-factory] Package Manager Update 3: Call for Testing
Our developers are continuing to improve the package manager stack. We'd like to release some of their changes for 10.1 now and I'd like to ask for testers. Please report all bugs you find in bugzilla (http://bugzilla.novell.com, component libzypp and include in the summary Package Manager Update 3). We plan to release on friday, 2006-09-01 an update to the test repository with anything that has been found so far and plan to release the final update next week officially. This update contains the following new features: * support for patch/delta RPMs in YUM sources (#168844) in YOU but not yet in the ZENworks tools This update includes fixes for the following bugs: * various performance enhancements * 190163 - *-kmp-* dependencies match multiple kernel packages * 176568 - Evaluate possible xml parser optimizations * 195567 - 100 /var/tmp/TmpFile.x in 3 Days * 193584 - cut-off package description in zen-updater * 194424 - Online update setup creates unusable cron job * 191676 - zen installer/updater cannot add an FTP YUM repository * 190295 - zen-updater/zmd/rug does not install update stack patches first * 193212 - zmd does not unblock transactions after transaction preparation failure * 191506 - zen-updated showing updates from non-subscribed catalog * 183656 - mono needed for YaST package management since last update openSUSE 10.2 will see further improvments that need even better testing. If you like to test, please read below the details - otherwise wait for the online update that we will release soon. Until the online update has been installed, I advise to run as root yast2 online_update for patch installation. If you have never updated the stack, then use yast to do the following, otherwise use either ZENworks tools or YaST: * Add the following (or one of the mirrors) as installation source: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test * Run an online update and install the new libzypp patch * Test whether YOU installs patches using patch/delta RPMs. Note patch and delta RPMs are smaller than full RPMs. Therefore download is faster but assembly of them takes longer. If anything looks broken, please contact myself and Stano visnov at suse.cz. Feel free to add him as visnov at novell.com in your bugzilla report, so that we do not lose track of any issues with this update. We do not plan to add further fixes, our goal is to get this update out and find any regressions introduced. openSUSE 10.2 will see further improvments that need even better testing and the ongoing progress can be tested using the openSUSE 10.2 Alpha releases - with Alpha4 next week. Thanks for your help, Stano and Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpzVtE8Fp1C3.pgp Description: PGP signature
Re: [opensuse-factory] kernel-default vs. kernel-smp
Andreas [EMAIL PROTECTED] writes: a couple of days ago there was a discussion about merging the rpm's for kernel-default and kernel-smp. Did that already happen? I don't see kernel-smp in the factory-repository anymore. It did happen last week. kernel-smp was dropped, we now have only the kernel-default one which has the settings from kernel-smp, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp3XxyhxV2UG.pgp Description: PGP signature
Re: [opensuse-factory] Adding SBIG CCD camera support to SUSE?
Jasem Mutlaq [EMAIL PROTECTED] writes: Hello, Sorry if this is not the appropiate list to discuss this issue. Santa Barbara SBIG CCD camera is one of the most popular cameras used in astronomy. In order to operate, the CCD requires a firmware to be uploaded upon detection on the USB port. Otherwise, you can't establish any further communications at all. What is the license of this firmware? Is it possible to re-distribute it? If this is not the case, then we cannot include it, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpzJRtiOPoOb.pgp Description: PGP signature
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
Joerg Mayer [EMAIL PROTECTED] writes: On Fri, Aug 25, 2006 at 01:36:19PM +0200, Andreas Jaeger wrote: - Kernel 2.6.18 Desktop Productivity Software - support for rt2500 wlan card, Bug 149141 Why is this considered Desktop/Prod instead of kernel? No idea why Michael sorted it this way ;-( - adding Broadcom WLAN support Please add the devicescape wireless stack into 2.6.18 (you might just be one release early ;) The reason why is, that some wireless drivers are only maintained (or usable) for the devicescape wireless stack, not the regulare one. Let's see what our mobile devices team think what is needed, I would prefer to not add a complete new stack :-( Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpx1C3af7dFK.pgp Description: PGP signature
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
Lenz Grimmer [EMAIL PROTECTED] writes: Hi, Andreas Jaeger wrote: The upcoming openSUSE 10.2 will basically have similar content like its predecessor but comes of course with latest and stable Open Source packages available at that time. We went through Bugzilla, the feature list and package wishlist and try to accomodate your wishes and suggestions. You missed some :) See the quoted text just below of this ;-) Note that the list below is neither complete - it's just some of the highlights - nor a commitment. Here an overview about areas we like to enhance, change or add things: [SNIP] Please give feedback and of course if there's something missing - tell us. Looks promising! The performance improvements in Software Management are dearly needed, I guess. Here is my little wishlist: - Please consider using LVM by default instead of plain disk partitions for new installations (BUG#180762): http://lists.opensuse.org/opensuse-factory/2006-06/msg4.html For later... - Get Bluetooth Support in KDE fixed (BUG#171120) and improved in general, e.g. by supporting Bluetooth Headsets out of the box (important for better VoIP support) (BUG#76782) - Support first Installation via WLAN: (BUG#149113) This is getting evaluated. - Better support the merged framebuffer modes in SaX2 when using dual-screen setups (make it easier to configure cloned and large desktops and how to switch between these modes at runtime) - Something I really liked about Kubuntu: the Installation CD can be used as either a live demo CD (without installation) and for easy installing on hard disk. I'll put it on my list to consider for future, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpv0oWK6i2Do.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Marc Collin [EMAIL PROTECTED] writes: that could be nice if somebody could post the pattern for gnome, kde... suse use and we could said what package is not really used Check the files in: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/setup/descr/ Just look at i586.pat, e.g.: kde-10.2-15.i586.pat kde_basis-10.2-15.i586.pat ... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpKwFjhMvSjY.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Andreas Hanke [EMAIL PROTECTED] writes: Hi, Andreas Jaeger schrieb: I don't like Experienced user - this should be split into several patterns... What about a pattern for console users instead? A pattern that includes software which is rarely used or unnecessary on desktops, but handy for the console. Yes, this is an idea. I'll work on it the next days and take your list as first proposal, Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpqy2cPoNFnu.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Lukas Ocilka [EMAIL PROTECTED] writes: Andreas Jaeger wrote: Check the files in: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/setup/descr/ Just look at i586.pat, e.g.: kde-10.2-15.i586.pat kde_basis-10.2-15.i586.pat I'd love to have a yast-development pattern :) Feel free to create it yourself and add it in a private repository ;-) Or start proposing it here... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp1pB01sLr29.pgp Description: PGP signature
Re: [opensuse-factory] Announcing Yast-GTK (forw)
Joerg Mayer [EMAIL PROTECTED] writes: And while you are at it: Can the next SoC project please remove the gnome dependencies from zen (and other system services) and offer qt/kde alternatives for those who only want to run a kde desktop? This is already worked on in parts. zen-updater can be replaced by a kde program - this was a SoC project. zmd itself as a daemon should IMO - I didn't check, so this might be what needs to be done - not require a graphical toolkit at all, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpVIGSrZYEyu.pgp Description: PGP signature
Re: [opensuse-factory] SL-Factory vs. SL-Factory-debug
Andreas Hanke [EMAIL PROTECTED] writes: [...] For Factory, the ratio of people who need them is probably larger than for a released version. The proposal was primarily intended for the released versions. OK, now we have it for Factory, too. You have it for factory first ;-) Future repositories will have it, so expect it for 10.2 ... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpdJO0L3CYNo.pgp Description: PGP signature
Re: [opensuse-factory] SL-Factory vs. SL-Factory-debug
Peter Czanik [EMAIL PROTECTED] writes: [...] Related question: do you know anything about when fixes introduced here: https://bugzilla.novell.com/show_bug.cgi?id=201164 will hit the factory repository? Installer files are still from 18th August, and thus severely broken... With the next sync - Timo and myself briefly tested yesterday evening the packages and it worked fine, so expect it anytime now... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpIGLqedtlmW.pgp Description: PGP signature
[opensuse-factory] openSUSE 10.2 Features and Roadmap
documentation available (English only). * Milestone: Last fixes for localization found during testing incorporated. -- Thu, Nov 30 openSUSE 10.2 GM release * Only showstopper and security bugfixes get integrated. * Milestone: All documentation available (translations also). -- Thu, Dec 7 openSUSE 10.2 public release * Release on the ftp server Michael Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpNOa8osdWFb.pgp Description: PGP signature
Re: [opensuse-factory] openSUSE 10.2 Features and Roadmap
Martin Schlander [EMAIL PROTECTED] writes: Fredag 25 august 2006 13:36 skrev Andreas Jaeger: The upcoming openSUSE 10.2 will basically have similar content like its predecessor but comes of course with latest and stable Open Source packages available at that time. We went through Bugzilla, the feature list and package wishlist and try to accomodate your wishes and suggestions. Note that the list below is neither complete - it's just some of the highlights - nor a commitment. Sounds great to me. Looks like all significant issues are being adressed, this could turn out to be a distro so great that it'll more than compensate for the horrors we've been going through with 10.1 ;) Just a couple of quick questions.. KDE 3.5.5 (October 10th, 2006: Expected release date of KDE 3.5.5)? I should have looked better - yes, this is an option and I assume it goes in. Narayans KDE zmd-updater applet? Yes, considered. The list is really not complete. Aiglx? Not planned. YaST-gtk? It might be in Alpha4 but I consider it too early to announce it. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpChsfdHBvXM.pgp Description: PGP signature
Re: [opensuse-factory] SL-Factory vs. SL-Factory-debug
Andreas Hanke [EMAIL PROTECTED] writes: [...] This makes me seriously doubt that rpm-md is designed or even suitable for such huge repositories. It's not surprising that parsing this beast is slow, even with a fast parser. It also makes me doubt that improving the parser is the only way of approaching the problem. I agree with this conclusion. xml is nice but it shows it limits here. So I thought how to reduce the number of packages: - Separate repositories per architecture - not possible because SUSE repositories have always been multiarch. We could - no problem at all. It would increase the space since all source and noarch packages would need to be duplicated. We love to have one ;-) - Separate repositories for source packages - bad idea IMHO. - Reducing the number of packages - not possible, people want to have more software and not less. The debuginfo packages sounded like a reasonable candidate to me because their number is always proportional to the number of binary packages. If we get a new architecture like ia64, we get more debuginfo packages as well, which means we can also save proportionally by splitting them from the rest. Note also that we already have performance workarounds. Using the old susetags metadata instead of rpm-md during initial installation is one of them. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpKJ5N9qU5ek.pgp Description: PGP signature
Re: [opensuse-factory] Cannot install openSUSE 10.2 Alpha 3 on Itanium (hwinfo-related crash)
Émeric Maschino [EMAIL PROTECTED] writes: Hi, I tried a network installation of current openSUSE build (hosted on oss.sgi.com) on my hp workstation zx6000 but the installation process crashes just after downloading the root image. Here are the logs that I captured with a camera since this display is quickly replaced by a big red square telling me that the installation process failed: starting hald... ok starting syslogd (logging to /dev/tty4)... ok Starting ia32el starting yast... hal.1: read hal data/usr/lib/YaST2/startup/First-Stage/F02-hwinfo: line 10: 2388 Segmentation fault (core dumped) /usr/sbin/hwinfo --special=x11 Probing connected terminal... Initializing virtual console... Unfortunately, once the red square replaces this screen, the keyboard is disabled, so I'm not able to swith to console tty4 to see the logs. I've performed several attempts. No luck. Using the safe settings or a textmode install didn't help. IIRC, the last working root image was dated around Aug. 15th. Is this problem also noticed on other architectures? If not, what can I try to help debug the installation process on Itanium? Yes, seen on other archs as well - hope to be fixed with installation images from 2006-08-23 or newer, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpO5aymOiaBR.pgp Description: PGP signature
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.gdm SuSEconfig.wdm
Dominique Leuenberger [EMAIL PROTECTED] writes: What are other Distros doing? Why don't they need anything alike? What is so much more special about the SuSE way that others don't need anything alike? The have similar problems - or force you to run scripts manually AFAIK. Is it just because of a 'lazy' coding stile for YaST? As YaST is reading / modifyng most of these files afaik. So: why not fix these tools? The user changes a file but the change needs to be propagated to others... Fixing tools is one option, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpyMBM4lk0An.pgp Description: PGP signature
[opensuse-factory] distmeeting minutes
)CLASS-A SuSEconfig.perl (perl) CLASS-B SuSEconfig.permissions (permissions) CLASS-A (special ...) SuSEconfig.postfix (postfix)CLASS-A SuSEconfig.prelink (prelink)CLASS-B SuSEconfig.scim (scim) CLASS-A SuSEconfig.scpm (scpm) ?? (- rcscript .. ?) SuSEconfig.scrollkeeper (scrollkeeper) CLASS-B SuSEconfig.sendmail (sendmail) CLASS-A SuSEconfig.susehelp (susehelp) CLASS-A(?) SuSEconfig.syslog-ng (syslog-ng)CLASS-A SuSEconfig.tetex (tetex)CLASS-B SuSEconfig.tuxpaint (tuxpaint) CLASS-C SuSEconfig.wdm (wdm)CLASS-A SuSEconfig.words (words)CLASS-A/CLASS-D SuSEconfig.xdm (xorg-x11) CLASS-A SuSEconfig.xjdic (xjdic-indices)CLASS-B SuSEconfig.xpdf (xpdf-tools)CLASS-B(?) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpJ8NS00gLXD.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Per Jessen [EMAIL PROTECTED] writes: Andreas Jaeger wrote: I only made a minimal list of patterns - and now want to open a new discussion on what kind of patterns we should have. I can add everything I find usefull - but please tell me what you find usefull ;-) Without having thought a lot about it - the initial selection by patterns/groupings is meant to give the user a system with a set software suitable for the primary purpose(s) of the machine being installed. So what are the typical main roles of an openSUSE system? Desktop | +--- Desktop for/with multimedia +--- Desktop for development +--- Desktop for office/backoffice +--- etcetera I added for now - and did this only for KDE, GNOME will come later - a generic KDE desktop pattern and a few sub patterns: * KDE-BASIS * KDE-Devel * KDE-Edutainment * KDE-Games * KDE-Help * KDE-IMAGE * KDE-Internet * KDE-Multimedia * KDE-Office * KDE-System * KDE-Utilities | Laptop +--- (not sure how to divide this) I don't know either. | Server | +--- Fileserver +--- Internetserver (DNS, web etc.) +--- Database +--- Directory +--- Firewall, network server +--- etcetera I have now: * Directory (LDAP) * Fileserver * Mailserver * LAMP * XEN * Internet Gateway | [other roles?] Development - not sure how to structure this. This is only a proposal - I really just wrote it up in five minutes. Maybe it's entirely in appropriate. Maybe the selection is 1-2-3 step: Primary qualifier, secondary qualifier, plus add-ons (things you might want to do regardless of which type of system): Experienced User, Kernel development, I don't like Experienced user - this should be split into several patterns... Primary and secondary qualifier could fit into one page/window in a tree-style display as the above, and going to the 2nd window for add-ons could be made optional, such that new-bies or non-techies would have a fast-path, whereas techies and/or experienced users would still have the option of a detailed selection etc. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpoRHdaF4J3w.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
Marcel Hilzinger [EMAIL PROTECTED] writes: Am Montag, 21. August 2006 17:11 schrieben Sie: [...] I did not add Artwork, that's in the base for me. Yes, but there are tonns of icon themes, window decos etc. Also the screensaver modules are not mandatory. Some more fonts for a default install would also be nice (see Ubuntu/Mandriva). What about the pictures in /usr/share/wallpapers are they Gnome/KDE only? Perhaps one wallpaper package would be enugh for both desktops. Ok, I'm considering it now ;-). [...] Have a look at factory by the end of the week (or at Alpha4) and then let's refine them together... OK. That's a better way. You're doing the work, we will complain ;-) Mmmh :-(. I'll have to figure something out so that it works the other way round ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpqIxMTSkx3M.pgp Description: PGP signature
Re: [opensuse-factory] Re: new discussion on what kind of patterns we should have
-server yast2-inetd yast2-irda yast2-iscsi-client yast2-iscsi-server yast2-kerberos-client yast2-mail yast2-power-management yast2-powertweak yast2-profile-manager yast2-repair yast2-restore yast2-slp yast2-slp-server yast2-vm yp-tools ypbind zip zisofs-tools zmd zsh -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpFVFJftLSN6.pgp Description: PGP signature
Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.automake
Andreas Hanke [EMAIL PROTECTED] writes: [...] Maybe SuSEconfig is not that bad after all ;-) There are cases where SuSEconfig is useable - but there are also cases where developers were lazy. SuSEconfig is slow and everybody complains about it - the easy way to remove it (doing everything in post-install scripts) will make package installation much slower (running scripts each time instead of once at the end). So, we might end with some scripts in the end - but only the bare minimum... What about just hard-coding /opt/gnome/share/aclocal into the dirlist, so that it's in the dirlist even if gnome-filesystem is not installed at all? Would that work? It looks ugly, but /etc/ld.so.conf has the same, it also references directories that might not exist at all on certain installations. If this is specific script currently only used to add /opt/gnome, then this will be obsolete once we switch from /opt/gnome to /usr - and therefore we should remove it directly before others start using it. ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpAQ4JQnisQH.pgp Description: PGP signature
Re: [opensuse-factory] distribution meeting - introduction and agenda
Christian Boltz [EMAIL PROTECTED] writes: Hello, Am Mittwoch, 16. August 2006 16:44 schrieb Andreas Jaeger: Will this work? It depends on some points: - you should give some more background information about the topics - I'll insert some questions regarding this below. I don't know everything and would like to have expert advice ;-) - you should mail some days earlier the next time ;-)) Will try to ;-) The planned topics for tomorrow's meeting are: * D-Bus 0.91 and PolicyKit/resmgr We just switched to D-Bus 0.91 and the question arises whether to continue to use resmgr or switch to PolicyKit. What are the advantages and disadvantages of each? That's what we try to figure out in the meeting. * Move to GNOME 2.16 The packagers have started already with the first packages, we want to discuss the timeframe for the move and the move of GNOME to /usr (from /opt/gnome). Hmm, what's the reason for this? Requests by e.g. lsb. BTW: Will KDE be moved also? With the next major KDE update: Yes, we will. * SuSEconfig removal SuSEconfig is currently run after each package installation by YaST and is a huge bottleneck. Some scripts have already been removed and we have to discuss how to move on. What's the replacement for config files that are _generated_ by SuSEconfig? (as in: including /etc/sysconfig/foo is impossible for the respective application) - You won't be able to do this in rpm postinstall scripts or alike ;-) We have to figure this out for each script. It might be done in the postinstall of the packages that need it - but only there. Not for unrelated stuff. [...] Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpoBzqZOHkCY.pgp Description: PGP signature
Re: [opensuse-factory] distribution meeting - introduction and agenda
Christian Boltz [EMAIL PROTECTED] writes: My proposal: KMail, evolution and Thunderbird [1] should come with the local mailbox account /var/spool/mail/username preconfigured so that system mails will be received automatically. Please add this as a feature request on the wiki, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp5zUmg8nkHb.pgp Description: PGP signature
Re: [opensuse-factory] distribution meeting - introduction and agenda
Mauricio Teixeira (netmask) [EMAIL PROTECTED] writes: Em Qui, 2006-08-17 às 13:04 +0200, Andreas Hanke escreveu: At least rug runs SuSEconfig after each transaction, and it's _painful_ compared to YaST because other than YaST, it doesn't show what it does, Well, I've never used rug, so I was not sure about it. Regarding smart, it's an old request to run SuSEconfig at the end, but looks like we'll wait for this discussion here to reach a decision so we would make ours on smart. :) And sure running the needed scripts on %post would do the trick, but it would require a lot of documentation so that the packagers would know if/when/how/why would they need to do that. We already noticed that we have a lot of scripts that are not needed anymore - just historic garbage :-(. Those can be removed. Let's see which scripts we still need and what technical solution is needed. If in the end out of 20 scripts, we keep 2 - and the runtime for these is not anymore 20s on my machine but 1s, then I'm fine ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp9irbW6s4K4.pgp Description: PGP signature
Re: [opensuse-factory] distribution meeting - introduction and agenda
Christian Boltz [EMAIL PROTECTED] writes: Hello, Am Donnerstag, 17. August 2006 13:57 schrieb Andreas Jaeger: Christian Boltz [EMAIL PROTECTED] writes: My proposal: KMail, evolution and Thunderbird [1] should come with the local mailbox account /var/spool/mail/username preconfigured so that system mails will be received automatically. Please add this as a feature request on the wiki, OK, it's on http://en.opensuse.org/Feature_Wishlist/Misc now. BTW: Thanks for the (probably not intentional) reminder to propose a better handling for the wishlists. IMHO it's just painful to use the wiki for this... Yes, I know, we're looking into alternatives already, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpArN0yajO6e.pgp Description: PGP signature
Re: [opensuse-factory] Current x86_64 Factory: Problem with hal/dbus?
Alex [EMAIL PROTECTED] writes: In addition to my previous post: Simply throwing out PolicyKit.rpm and reverting hal.rpm to the Version as shipped with 10.1 solves the problem. Please file a bugreport using bugzilla.novell.com, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpaY5ppcztCV.pgp Description: PGP signature
[opensuse-factory] distribution meeting - introduction and agenda
We have an internal meeting every few weeks called dist meeting that discusses major technical changes in our distribution. Since it's not possible for most of you to attend it, I'd like to try an experiment and share the agenda before the meeting - and the meeting minutes afterwards with you. I'm asking for your feedback on the agenda and any comments that you have and will bring those comments into the meeting and raise the points you've made. Will this work? The planned topics for tomorrow's meeting are: * D-Bus 0.91 and PolicyKit/resmgr We just switched to D-Bus 0.91 and the question arises whether to continue to use resmgr or switch to PolicyKit. * Move to GNOME 2.16 The packagers have started already with the first packages, we want to discuss the timeframe for the move and the move of GNOME to /usr (from /opt/gnome). * SuSEconfig removal SuSEconfig is currently run after each package installation by YaST and is a huge bottleneck. Some scripts have already been removed and we have to discuss how to move on. * update messages general/conditional (e.g. bind) During update of packages they could notify users about changes via email and/or the SuSEplugger (until 10.0, this is not anymore in 10.1). Most of these are outdated and not really usefull anymore and should be removed. The question is how to handle situations like bind where config files get rewritten and the user should be informed if this fails. * Dropping UP Kernel on i386/x86-64 The proposal by the kernel team is to use only SMP kernels and no UP kernel. It's already this way on Xen - there is no Xen UP kernel. Advantages: One less kernel rpm. On 64bit there will be only two kernel rpms then, kernel-default and kernel-xen; and with some luck if paravirt ops works out as designed we can then later drop kernel-xen too and only ship a single 64bit kernel. 32bit could go down to two. Less QA. Less space on ftp servers. Less build time. Avoids a lot of problems with install kernel being different from final kernel. The i386 UP kernel e.g. doesn't support advanced APIC modes, which broke i386 installation of SLES10 on some systems. We've had quite a lot of bugs in this area over the years. Disadvantages: Will be slightly slower and bigger on UP systems. Most of the performance difference is fixed up by kraxel's LOCK prefix runtime patch. Memory usage will be up a bit on UP systems We would lose a few drivers which are BROKEN_ON_SMP. Usually these are long unmaintained drivers which are broken for other reasons anyways so it's not a big loss. Also we never had them in the SMP kernel and most modern systems run SMP kernels. There might be other bugs caused by this, but Fedora has done this before us and they didn't seem to have regretted it so far. * Linker Options and Optimizations We plan to use the recently developed linker optimizations for the GNU hashstyle and use the readonly relocations: LDFLAGS=-Wl,-O1 -Wl,--hash-style=both (http://lwn.net/Articles/192082/ ) LDFLAGS=-Wl,-z relro (see http://people.redhat.com/drepper/nonselsec.pdf) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp9E2RdkQjvY.pgp Description: PGP signature
Re: [opensuse-factory] 10.2a3 - first impression
Per Jessen [EMAIL PROTECTED] writes: When changing the software selection, I find the initial list of groupings to be a little too coarse - there isn't even a tickbox for Experienced User any more ... This is desired. See the previous discussion on the list. I only made a minimal list of patterns - and now want to open a new discussion on what kind of patterns we should have. I can add everything I find usefull - but please tell me what you find usefull ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpLrQs0Idoov.pgp Description: PGP signature
Re: [opensuse-factory] Re: [opensuse-announce] openSUSE 10.2 Alpha3 Release
Guillermo Ballester Valor [EMAIL PROTECTED] writes: Hello, El Viernes, 11 de Agosto de 2006 09:16, Andreas Jaeger escribió: I'm glad to announce the third alpha release of our 10.2 product. ... * We now have a gcc package and a gcc41 package in such a way that in the future a gcc42 package might be available as well, giving you the chance to use different gcc versions at the same time. Glad to read this, then I will not have to build my gcc_4x rpm packages anymore :-) It's not there yet - we just put the infrastructure in place. But you could build those in the build service for everybody. Kudos for openSUSE! Kudos to Richi ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp3v4FpiUmOS.pgp Description: PGP signature
Re: [opensuse-factory] Re: [opensuse-announce] openSUSE 10.2 Alpha3 Release
houghi [EMAIL PROTECTED] writes: On Fri, Aug 11, 2006 at 09:16:54AM +0200, Andreas Jaeger wrote: * Using patterns instead of selections in the package manager (think of patterns as package groups with some semantics). We have currently only a basic set of patterns and will enhance them. Could I (an others) have the new autoyast2-utils containing the new create_package_descr to make these patterns? I looked on factory and the old version is still there. Please open a bugreport so that this does not get forgotten, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpAicOZkUASq.pgp Description: PGP signature
Re: [opensuse-factory] feature freeze dates for 10.2
jdd [EMAIL PROTECTED] writes: In order not to do again the mistakes made with the zen update and 10.1, I think we should have _two_ feature freeze dates... One for the _new things_ (patterns, Xorg 7...) and one for the _new releases_ of already used things (Kde, Gnome) We had basically so far: * A toolchain freeze some weeks before beta1: Minor updates that do not break stuff are allowed but no more major updates for gcc, binutils, etc. * The big freeze with beta1 for everything. I think the latter are already tested by they developpers when the first seems already in a very early stage. My plan is more to integrate risky stuff as early as possible, e.g. patterns now and X11R7 now ;-) I'm disquieted by the most annoying bugs list and the _may be_ delayed Alpha 3. We'll release tomorrow. I really want to give you a distribution that you can install without hand-editing the grub files and where you cannot make any changes to the patterns ;-) I personnally think that a stable distribution is better than the very most up to date one. an other solution should be to use a debian like calendar (I speak of the three distros, stable, unstable and testing, not of the delay between releases :-) jdd Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpdS9MIjgeBv.pgp Description: PGP signature
Re: [opensuse-factory] feature freeze dates for 10.2
Dominique Leuenberger [EMAIL PROTECTED] writes: I was also very concerned when I saw the 'most annoying bugs' list today (as I epxected Alpha 3). The worst that can happen to openSUSE is having (again) a release with bugs like the updater in 10.1. Even though they are fixed now, it's still around and poeple installing without an internet connection most obviosuly run into it. For me Alphas have a lower quality than Betas have and I they might be broken sometimes in ways that would never be acceptable for a final release. If the schedule for 10.2 should be kept like this (which I think it should) then we should try to put bugs away instead of adding last-minute-features and packages. Some might be solved with new packages, some might not. The X11 change was planned for a long time but it was indeed a bit tight at the end. Btw. in general my plan is: * Release AlphaN * Break everything;-) (I mean: put new stuff in that could be broken) * Stabilize again in time for our AlphaNplus (after two weeks) * Stabilize furthr for the next public Alpha Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpZWaDv87iLf.pgp Description: PGP signature
Re: [opensuse-factory] feature freeze dates for 10.2
jdd [EMAIL PROTECTED] writes: Andreas Jaeger a écrit : My plan is more to integrate risky stuff as early as possible, e.g. patterns now and X11R7 now ;-) I would say X11R7 yes (we are not the only ones to test it), but Pattern... we are not even sure of what they are :-() - so be extremely carefull. May make them optional for 10.2 and keep the good old system we use for years :-) That's not possible with patterns ;-(. Download Alpha3 CD1 and boot from it - no need to install. You can then look at what we have right now and continue discussing. We'll release tomorrow. I really want to give you a distribution that you can install without hand-editing the grub files and where you cannot make any changes to the patterns ;-) honestly, for Factory I don't care :-) just how many time was them between zen updater inclusion and 10.1 release? and what is the final release fixed for 10.2? if we want it before the end of the year, we have 4 month. it's fairly short. some enhancements are expected by many (I think of Kde or Gnome versions) so we are nearly obliged to give some. others are brand new and are not that urgent (btw I don't know what the others distributions do) KDE 3.5.4 (already in) and GNOME 2.16 (started), yes. may be we should have somewhere a discussion of the far future of openSUSE (not 10.2 but 11 or 12), some sort of brainstorming to make the next century Linux :-) Yes, good idea... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpGei0RqD4vz.pgp Description: PGP signature
Re: [opensuse-factory] Factory miniiso dies during startup
Joerg Mayer [EMAIL PROTECTED] writes: I just downloaded the factory miniiso. After I booted it I selected netinstall http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/ The installation repository in factory is broken right now, we're working on fixing it. For now I advise to use the Alpha2 tree, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpctOAk4ZLdA.pgp Description: PGP signature
Re: [opensuse-factory] Factory miniiso dies during startup
Joerg Mayer [EMAIL PROTECTED] writes: On Mon, Aug 07, 2006 at 01:23:29PM +0200, Andreas Jaeger wrote: Joerg Mayer [EMAIL PROTECTED] writes: I just downloaded the factory miniiso. After I booted it I selected netinstall http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/ The installation repository in factory is broken right now, we're working on fixing it. For now I advise to use the Alpha2 tree, How do I do a network install of the Alpha2 tree? It looks like there are only isos available. Argh - you're right :-( Sorry. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgps6PueW5Bm2.pgp Description: PGP signature
Re: [opensuse-factory] Test updates for SUSE Linux 10.1
Andreas Jaeger [EMAIL PROTECTED] writes: Andreas Jaeger [EMAIL PROTECTED] writes: James Oakley [EMAIL PROTECTED] writes: On Tuesday 11 July 2006 9:22 am, Andreas Jaeger wrote: [...] That's a bug in the spec file which triggers a strange behaviour in libzypp. :- Install novfs-kmp-default and be happy, We fixed this issue now - somebody come up with the right idea how to do it ;-) I've just updated my repositories: * package management: Fix the bug James had with e.g. installation of kdump kernel * kernel: Add some additional fixes, especially security fixes. The package management will go out today if our last tests passed, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpAt1Prric5L.pgp Description: PGP signature
Re: [opensuse-factory] Can not access taskbak after new installation
The Nice Spider [EMAIL PROTECTED] writes: 1. after fresh install 10.2 aplha 2 and come to gnome, i can not access the taskbar. 2. so, i am logout (ctrl-alt-del) and login again but this error message appear: ... panel already running...exit (something like this message). 3. after click the message box and login again my computer hang. 4. then i reset my pc... and this message appear (continously): - Trans replayed: mount 11, transid 129.. above text appear about 500 lines! 5. now, gnome work fine. Please file this as a CRITICAL bugreport in bugzilla against GNOME, Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgposvyeJzkcT.pgp Description: PGP signature
Re: [opensuse-factory] Packagage Groupings - From Selections in 10.1 to Patterns in 10.2
jdd [EMAIL PROTECTED] writes: [...] * this can be very powerfull, but for the very same reason must be very carefully examined. I wonder if it's not risky to 10.2 (don't do again the libzypp error), we must fine tune the definitions and scenarii before going to the implementation. That's why I start early and asked directly for feedback ;-). We *now* have enough time to do it and fine tune it... I just added only some example basic patterns so that installation is possible while we continue discussing. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpxRJxFwaIYC.pgp Description: PGP signature
Re: [opensuse-factory] adding an installation server is too slow
James Li [EMAIL PROTECTED] writes: Adding an installation server is very slow on my mechine. I look into /var/log/Yast2/y2log and find that the same file (eg. packages) will be downloaded at least three times . First at the time adding the installation server, second at the time applying installation source and these will be repeat when doing software management. These cause the software management is very lag. Is there any update for these method? We have an online update available for the update stack, install it with yast2 online_update. It does improve in this case, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpvU1vZjZgtQ.pgp Description: PGP signature
Re: [opensuse-factory] Re: [opensuse-announce] SUSE Linux 10.2 Alpha2 Release - and distribution rename
houghi [EMAIL PROTECTED] writes: On Thu, Jul 13, 2006 at 01:21:03PM +0200, Andreas Jaeger wrote: It's downloadable from today on and will be the last community/consumer distribution called SUSE Linux. We'll rename SUSE Linux into openSUSE. Great news. Not so much the name, but taking away the confusion. SUSE Linux 10.2 Alpha2 is slowly moving to 10.1. We have not done any real major updates yet but lots of minor changes, I list some below: Towards 10.2 is suppose you mean. ;-) Yes. Let the testing commence. Thanks for reporting this bug - I'll close it as WONTFIX ;-) Cheers, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpjr2bH35nTu.pgp Description: PGP signature
[opensuse-factory] Packagage Groupings - From Selections in 10.1 to Patterns in 10.2
Currently in SUSE Linux 10.1 (and earlier releases) we use selections in YaST to group software and easily enable installation of related software. Our developers have enhanced the concept of selections and call it patterns. What are patterns? * patterns include a list of software packages to install * the list of software packages contains packages that are - required (must-have) - recommended (should-have) - suggested (may-have) * Patterns define a functionality the system should have. They do this by either directly naming required packages or by grouping of sub-patterns, or a combination thereof. This partitions the huge list of installed rpms into building blocks which can be combined (almost) at will. By listing each and every rpm in a (ideally: exactly one) pattern, this related rpms to functionalities. This in turn finally gives an answer to the often asked question: Why is this package installed ? * in the future we like to drive workflow with patterns as well, e.g. if you select the (imaginary) LDAP server pattern, the LDAP configuration workflow will be called during installation. * Patterns can be grouped into roles, like Development or Desktop. * Patterns can require other patterns They have the same set of (possible) dependencies as packages have. So they can also obsolete (replace) or conflict other patterns. Or have language dependencies, etc. * Add-on products can have additional patterns * Patterns can be differentiated between top-level/user-visible and internal/non-user-visible patterns (a pattern might require others that are not visible) - these are implementation details of the patterns. Directly after 10.2 Alpha2, I'd like to switch to patterns. Instead of simply rewriting the existing selections to patterns, I would like to start basically from scratch and define with you which patterns we should have. Currently we have the following selections: * Graphical Base System * KDE Desktop Environment * All of KDE * GNOME System * Help and Support Documentation * Office Applications * Games * Multimedia * Voice over IP * Xen Virtualization * Simple Web Server with Apache2 * LDAP Server and Tools * Network and Server * Laptop * Mobile Computing * C/C++ Compiler and Tools * Kernel Development * KDE Development * GNOME Development * Tcl/Tk Development System * Java * Experienced User * LaTeX, SGML and XML * Fonts * Mono/CLR * Non-Open Source Packages As a first step for discussion I propose these roles and patterns: * Graphical Environments - GNOME Desktop Environment - KDE Desktop Environment - X Window System (with fvwm2) * Base Technologies - Base System (always installed) - AppArmor - Xen Virtual Machine Host Server * Development - C/C++ Compiler and Tools - GNOME Development - KDE/QT3 Development - Qt 4 Development - Linux Kernel Development - Version Control Systems * Primary Functions - File Server - Print Server - Mail and News Server - Web and LAMP Server - Internet Gateway - DHCP and DNS Server - Directory (LDAP) Server This misses some of the selections and introduces new ones. This is really a first step for discussion. I would like you to come up with better high-level proposals! Let's not discuss we need this pattern as well - but let's discuss and agree on the general framework and then let's discuss adding further patterns. Btw. we have a nice way of adding new, third-party patterns: Basically all you need is to have a lightweight add-on product that only has patterns, but no RPMs. So one could create his or her favourite package collections and make them available as an add-on source. Every repository can add patterns. Btw. I've put the above on the wiki at: http://en.opensuse.org/Patterns Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpkLfIOLP7cE.pgp Description: PGP signature
Re: [opensuse-factory] Packagage Groupings - From Selections in 10.1 to Patterns in 10.2
Glenn Holmer [EMAIL PROTECTED] writes: On Wednesday 12 July 2006 04:18, Andreas Jaeger wrote: * Patterns can be grouped into roles, like Development or Desktop. * Patterns can require other patterns Will there be a way to have alternate choices, e.g. if you select Database Server you can choose between MySQL and Postgres, or either if you select Java Development you can choose between NetBeans and Eclipse? It really depends how fine granular we make the patterns. We could have a * MySQL Database Server * Postgres Database Server * Java Development with NetBeans * Java Development with Eclipse ... And then end with 1000 different patterns ;-) That's why I'm asking here on your ideas - and on complete proposals. Will there be a way to save your selections to e.g. memory stick for doing multiple installs? (do the selection on the first machine, then read it in for the rest of the machines)? Something to discuss separately, interesting idea, I'll pass it on, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpwI0hg6hjqN.pgp Description: PGP signature
Re: [opensuse-factory] Packagage Groupings - From Selections in 10.1 to Patterns in 10.2
Kenneth Schneider [EMAIL PROTECTED] writes: Also why not eliminate the duplication of packages in the patterns. When looking at and selecting KDE packages I should _not_ be presented with GNOME packages for selection as well. I have not ever understood why a package shows up in numerous places. We currently have packages and dependicies in the selections, we plan to have only packages in it - and a package in the KDE selection might then have as dependency some GNOME packages/libraries but we'll not listen them explictely, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpSVSAtARr1N.pgp Description: PGP signature
Re: [opensuse-factory] Packagage Groupings - From Selections in 10.1 to Patterns in 10.2
James Oakley [EMAIL PROTECTED] writes: On Wednesday 12 July 2006 9:41 am, Klaus Kaempf wrote: * Glenn Holmer [EMAIL PROTECTED] [Jul 12. 2006 12:54]: On Wednesday 12 July 2006 04:18, Andreas Jaeger wrote: * Patterns can be grouped into roles, like Development or Desktop. * Patterns can require other patterns Will there be a way to have alternate choices, e.g. if you select Database Server you can choose between MySQL and Postgres, or either if you select Java Development you can choose between NetBeans and Eclipse? Yes, this could be done. However, depending on whom you ask, people will love or hate such questions. Actually, I think this can be used to take some of the drudgery out of the package selections. I end up going through all of groups to make sure that I get all of the packages I need, but if a pattern can select packages based on other selected patterns, I could spend far less time on it. If I select Database/PostgreSQL alone, it will install the server and client, but if I also have Development/C and C++ and Development/Python selected, postgresql-devel and postgresql-python will also be installed. Similarly, if I select Desktop Environments/KDE it will install a basic KDE system, but if I also have Hardware/TV Capture it will also install kwintv. You could also use this to select tasks independently of the desktop environment. If you select Productivity/Chat and you have KDE and GNOME selected, you would get Konversation and XChat, but if you just have KDE, you would just get Konversation. I think that could be very powerful. You got it ;-). It's really powerful and you could do such stuff. The question is do we want to do it this way? It makes it difficult to maintain them... If people like this, let's make a full proposal... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpOj4Mum6SAU.pgp Description: PGP signature
Re: [opensuse-factory] factory vs alpha2
Peter Czanik [EMAIL PROTECTED] writes: Hello, 10.2 Alpha2 is just around the corner, it's synced out to mirrors. If I sync my home factory mirror now, will it be the same as Alpha2? Or it's older/newer or any other way different? Bye, Alpha2 and factory are in sync right now, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpqtyFZLk1X0.pgp Description: PGP signature
Re: [opensuse-factory] second-libzypp-update-test
Martin Schlander [EMAIL PROTECTED] writes: Tirsdag 04 juli 2006 10:45 skrev Andreas Jaeger: I will move them to the old place once I'm happy with them - those are the packages from last week. I'm testing the packages dated July 7th. Seems to work nicely. I believe performance would be the focal point of these patches, correct? No - correctness. We're still fixing bugs :-( Only tested on my 900 mhz/512 mb ram laptop thus far - but it still seems rather slow - at resolving, installing, running suseconfig etc. - slower than 10.0-yast and a lot slower than Smart. Though there seems to pe significant improvement in the parse-metadata department - only tested it briefly thus far. I'm wondering how much more potential is there for improvement? Is this considered satisfactory? How much work will be put into it after this round of updates is put out? Is this the level of performance we can expect, say, when 10.2 rolls around? We continue working on performance and that needs some major refactoring, so it will need extensive testing. One of the reasons I'm asking is that it was communicated earlier that the packagemanagement issues would be fixed in two rounds of patching. It will be more I fear :-( Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpqfpAFQJkdX.pgp Description: PGP signature
[opensuse-factory] Test updates for SUSE Linux 10.1
I've published two repositories for SUSE Linux 10.1: * An updated packagemanagement stack * New kernel 2.6.16.21 We plan to release this soon (this week!) as official update and appreciate any testing, please report bugs you find on bugzilla.novell.com and CC me on the report (as aj at novell dot com). The packages and the changes itself have been tested intensively during the last weeks inside Novell. Since these are large updates, we like to have additional testing of these as a patch and on a variety of systems and environments. Package Management Stack Update === In addition to the already released fixes for the package management stack, we have now fixed further bugs. The most important changes are: * Fixes for autorefresh (#186115, #181613, #181182) * Do not leave stall tmp files (#178292) * Empty catalogs before filling them (#181602) * Handle passwords in URLs (#186978, #186842, #186804) * Handle signing in zen-updater, zmd * Fix some bugs in interaction of libzypp and zmd The repository URL is: ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test (please use a mirror of ftp.suse.com if possible.) Kernel Update = Please apply the package management stack before applying the kernel update. This is an update to Kernel 2.16.21 together with a number of bug fixes that we developed during the last weeks. The kernel changes its ABI completely, so all the kernel-module-packages (kmp) that you have installed, need to be updated as well. The interface between kernel and AppArmor has been changed as well, and therefore you have to update AppArmor as well (or disable it). Xen is updated as - as well as udev, open-iscsi, multipath-tools and mkinitrd. The repository URL is: ftp://ftp.suse.com/pub/people/aj/10.1-kernel-update-test (please use a mirror of ftp.suse.com if possible.) Note on AppArmor Since the update adds new flags to the profile syntax, you likely should review and adapt your profiles. - If a profile allowed unconfined execution (quot;uxquot;) of a child binary it was possible to inject code via LD_PRELOAD or similar environment variables into this child binary and execute code without confiment. We have added new flag Ux (and Px for px) which makes the executed child clear the most critical environment variables (similar to setuid programs). Special care needs to be taken nevertheless that this interaction between parent and child programs can not be exploited in other ways to gain the rights of the child process. - If a resource is marked as r in the profile it was possible to use mmap with PROT_EXEC flag set to load this resource as executable piece of code, making it effectively ix. This could be used by a coordinated attack between two applications to potentially inject code into the reader. To allow mmap() executable access, supply the m flag to the applications profile. Please also review the updated documentation. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpZPSXUjNOjh.pgp Description: PGP signature
Re: [opensuse-factory] Test updates for SUSE Linux 10.1
James Oakley [EMAIL PROTECTED] writes: On Tuesday 11 July 2006 9:22 am, Andreas Jaeger wrote: I've published two repositories for SUSE Linux 10.1: * An updated packagemanagement stack * New kernel 2.6.16.21 The zen update worked perfectly. However, the kernel update did not:: xen:~ # rug up aj-kernel Resolving Dependencies... Do you have novfs-kmp-default installed? That package needs to be installed... ERROR: Dependency resolution failed: Unresolved dependencies: Establishing novfs-kmp-default-1.2.0_2.6.16.13_4-10.x86_64 [SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060707-164613] Installing novfs-kmp-default-1.2.0_2.6.16.13_4-10.x86_64 [SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060707-164613] Establishing atom:novfs-kmp-default-1.2.0_2.6.16.21_0.6-9.2.x86_64[aj-kernel] kernel-default-2.6.16.13-4.x86_64 [SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060707-164613] provides kernel(kernel) == f6bd6270900c24b7, but another version of that package is already installed. There are no installable providers of kernel(kernel) == f6bd6270900c24b7 for novfs-kmp-default-1.2.0_2.6.16.13_4-10.x86_64 [SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060707-164613] xen:~ # rpm -q kernel-default kernel-default-2.6.16.20-2 xen:~ # rpm -e novfs-kmp-default error: package novfs-kmp-default is not installed If novfs-kmp-default is not installed, why is it considered in the dependency resolution? That's a bug in the spec file which triggers a strange behaviour in libzypp. :- Install novfs-kmp-default and be happy, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpIIsgAvxFLt.pgp Description: PGP signature
Re: [opensuse-factory] second-libzypp-update-test
Martin Schlander [EMAIL PROTECTED] writes: Tirsdag 11 juli 2006 13:40 skrev Andreas Jaeger: No - correctness. We're still fixing bugs :-( We continue working on performance and that needs some major refactoring, so it will need extensive testing. It will be more I fear :-( Well, what's with the sad smileys? That was just what I wanted to hear! It means that we are not confident that we fixed all bugs in the code ;) But of course it means a lot of work still left for you guys. :) Exactly. It gets a better each time - I'm actually starting to believe it'll end up being really good and nice. Must admit I've had doubts before... Thanks for believing in us, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpg3pJTRo63M.pgp Description: PGP signature
Re: [opensuse-factory] Test updates for SUSE Linux 10.1
Jürgen Mell [EMAIL PROTECTED] writes:
On Tuesday 11 July 2006 14:22, Andreas Jaeger wrote:
I've published two repositories for SUSE Linux 10.1:
* An updated packagemanagement stack
* New kernel 2.6.16.21
Some good news and some bad news regarding the package management:
The update process worked, although during the process an error was
detected (this happened with most of the updates during the last weeks -
the installation process ran always to the end and everything was fine.)
This time, the program complained that the ZMD service was not running
(ok, that makes sense). Unfortunately, it opened 627 windows telling me
so, which stopped nearly the whole system. But after some (long) time, the
package management update was installed, the tray icon vanished and all
627 windows with the error message were closed.
Could you open a bugreport for this, please?
After reboot, the updates for KDE which were available at that time were
detected and now installed without any error messages. Fine :-)
Now the bad news: One of my installation sources is a local copy of the
Packman archive, which also contains some updated packages. When
right-clicking the tray icon and selecting 'update' ('Aktualisieren') I
get an error message window:
Refresh failed. Failed to parse XML metadata: Unsigned
file '/repodata/repomd.xml (dir:///akira/space/SuSE_Update/packman/10.1)'
So it seems that the handling of unsigned repositories still does not work
or even worse it does not work anymore. Before the update, the
repositories were not refreshed automatically, but at least after a manual
refresh the packages were detected and installed.
Change in Preferences the setting security-level to checksum.
There is still some work for you ;-)
I know :-(. I just want to be sure we do not introduce regressions
while we continue fixing bugs...
Andreas
--
Andreas Jaeger, [EMAIL PROTECTED], 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
pgpCxYwUbF0nQ.pgp
Description: PGP signature
Re: [opensuse-factory] second-libzypp-update-test
Andreas Hanke [EMAIL PROTECTED] writes: Hi, at http://ftp.suse.com/pub/people/aj/second-libzypp-update-test/ there are currently some RPMs which look like they might become a YOU soon. I don't remember any announcement, but installed them anyway ;) I will move them to the old place once I'm happy with them - those are the packages from last week. We found already that you cannot install them with zen-updater - and therefore currently investigate this, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpBTcHHEurRK.pgp Description: PGP signature
Re: [opensuse-factory] Idea for SuSEfirewall2
With the feedback seen, I suggest we evaluate this for 10.2. could you add it to the feature wishlist? I've added it already to our internal feature tool so that we can start evaluating ourselves, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpHUwQSPRvsG.pgp Description: PGP signature
Re: [opensuse-factory] control.xml info
jdd [EMAIL PROTECTED] writes: Klaus Kaempf wrote: * houghi [EMAIL PROTECTED] [Jun 28. 2006 18:55]: Is there any info availble on control.xml? I have found many references to the file, but not one explaining anythiong about the file. This should help you further: http://forgeftp.novell.com/yast/doc/SL10.0/tdg/yast2-installation.html#control_configuration I noted several times that there are very valuable info in forgeftp. Can we link freely the wiki to this site? or is that somewhat private? forge*.novell.com is public, if we put something there it's meant to be freely available ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp7Q9wTzSAXL.pgp Description: PGP signature
[opensuse-factory] Updated Software Management Test Repository
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 [EMAIL PROTECTED] (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, [EMAIL PROTECTED], 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 pgps8teliz9Hj.pgp Description: PGP signature
Re: [opensuse-factory] Updated Software Management Test Repository
Lenz Grimmer [EMAIL PROTECTED] writes: Hi! Andreas Jaeger wrote: * You can now remove the software catalog you added in the first step. Use yast2 inst_source and delete the catalog. Here a popup window appeared, stating: Error: Cannot stop '/etc/init.d/novell-zmd' service. I clicked OK, and the inst_source module finished. Not sure if this is critical. Are there any logs that would help here? Bugzilla? Bugzilla - with /var/log/zmd-messages.log appended. OK, this is now filed as BUG#181126 - hope it helps. Thanks. * Restart the zen-updater applet on your desktop (it will stop itself since zmd gets stopped during the update). Hmm, the applet stayed in the KDE panel for me. To be safe, I restarted it manually. Strange, before I restarted it, I stated that 11 patches are available. After the restart, these are gone (no orange exclamation mark anymore). Bugzilla? Check with rug patches what it outputs - and then it might be worth a report. It really depends. I guess I need to get used to the output of this tool first. rug patches lists a number of patches, but I guess none of these apply for me, hence the applet is silent: [...] [EMAIL PROTECTED]:~ rug patches Catalog | Name | Version | Category| Status - +---+-+-+--- SUSE-Linux-10.1-Updates | aaa_skel | 1444-0 | recommended | Not needed SUSE-Linux-10.1-Updates | avahi | 1399-0 | security| Not Applicable A Needed would have meant something but those are all fine, you do not need them. So, this looks ok, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpikFAPtpIHg.pgp Description: PGP signature
Re: [opensuse-factory] Update stack test build
Andreas Hanke [EMAIL PROTECTED] writes: Hi, I'd like to know if / propose that the following bugs are candidates for inclusion in the package management update: - Option to disable missing signature complaints is not persistent https://bugzilla.novell.com/show_bug.cgi?id=175845 It will go in since it's fixed. Not because of its severity - it's actually labelled as Minor in Bugzilla - but because of the number of duplicates. It seems to annoy quite a lot of people. Fix available - can it be included? Yes, already in my internal test build. We just wait for a fix for zen-updater that crashes on some systems in a reliable way (we had to take another update for it). As soon as that is fixed, we release new packages for testing - and mark them official. The current packages are good - but do not refresh with the ZENworks tools, so if something is newer on the server you will not notice it. Workaround: Run yast online_update. This is fixed now, so these fixes will also go out: * 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) I did not list each bugzilla number in my README. - Too many YaST/zmd related directories left behind in /var/tmp https://bugzilla.novell.com/show_bug.cgi?id=178292 Probably rather cosmetic, but ugly. No fix available so far according to Bugzilla, and not that important. But maybe later? We're working on it, it might go out as well. - Taboo flag is not persistent in the package manager https://bugzilla.novell.com/show_bug.cgi?id=164445 https://bugzilla.novell.com/show_bug.cgi?id=153337 This one has several duplicates which are not yet marked as such. Doesn't seem to be implemented at all right now, but is a needed feature. Later? Yes, will come later, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpLfqDPVHZbQ.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
Bjørn Lie [EMAIL PROTECTED] writes: Doesn't this exit now? munin:/home/blie # rug set cache-cleanup-enabled False Preference 'cache-cleanup-enabled' changed from 'True' to 'False' Does it work with service zypp? Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpE36mQpjcxm.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
Here's one comment from my side: Repositories are handled differently in yast and zmd: * They have different attributes (name, autorefresh,...) * yast does not allow names but zmd does * syncing sources between yast and zmd is complex We should have a common view on repositories. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpvXPU6n26j2.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
Marcus Meissner [EMAIL PROTECTED] writes: One question we have is how the new tools rug, zen-updater and zmd compare to what we had before with YaST Online Update and suseWatcher. We are interested in every feedback ranging from architecture, design or used standards and their enhancements. It should be possible to disable and remove the whole ZMD stuff and still be able to work from commandline. For this is missing: - commandline installation source management (installation_sources equiv.) - commandline package installation (basically the yast -i pkg thing) - commandline online update (online_update equiv.) I think the question here is even greater: Do we really need a daemon? Pros: + daemon helps with remote management + is fast (not the case with zmd if zmd is sleeping) Cons: + needs resources running (zmd needs less resources if it's sleeping) What else? Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgperJbbuTgr9.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
Marcus Meissner [EMAIL PROTECTED] writes: One question we have is how the new tools rug, zen-updater and zmd compare to what we had before with YaST Online Update and suseWatcher. We are interested in every feedback ranging from architecture, design or used standards and their enhancements. It should be possible to disable and remove the whole ZMD stuff and still be able to work from commandline. Why? What is the reason behind this? For this is missing: - commandline installation source management (installation_sources equiv.) - commandline package installation (basically the yast -i pkg thing) - commandline online update (online_update equiv.) Do you like the user interface of rug, so would rug as *interface* work for you? Or is that broken? Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpzFPJUBu7gs.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
Marcus Meissner [EMAIL PROTECTED] writes: [...] - Also a update management system agnostic YOU watcher. The old one just ran online_update and parsed its output. Only for the actual update it required the root password. We could port the old one to run rug, or whatever other equivalent. The ZMD permissions handling is too permissive and too difficult to understand in my eyes. So, what do you propose for permissions? Always root password for the update? I've seen positive feedback about needing the root password only initially when granting the permissions. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpTnD98F2Jx7.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
houghi [EMAIL PROTECTED] writes: On Sat, May 27, 2006 at 04:05:18PM +0200, Andreas Jaeger wrote: Edit /etc/zmd/zmd.conf and change the sleep-interval: [Server] sleep-interval=1800 Change 1800 to something larger... Is there a maximum? Are there disadvantages if you use an extreme large sleep-interval? e.g. what happens if you do a sleepinterval of 24 hours and then use crontab to do a forced update at a moment where it does not matter, like at 04:00 or whenever you least likely are going to use it. You want to restart zmd at least once a week since there were definiteyl and might still be some resource leaks in mono that make it wise to restart, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp4J8JA4li7w.pgp Description: PGP signature
[opensuse-factory] Package Management Design and Experience
As discussed last week, I wanted to continue the discussion about the package management changes - but not concentrating on the real bugs we're fixing now but on general issues: With SUSE Linux 10.1 we have redesigned the way we handle software. We are proud to be able to announce our new software management backend which is based on the so-called library libzypp and which also integrates Novell's ZENworks technology. Also we decided to follow the repomd standard (sometimes known as YUM repository) for our new software repositories. In fact we are now able to manage more than packages only. We have integrated flavors like patches, patterns and even products all of which are defined and handled equivalently to packages. This new framework allows for new ways to define system dependencies and to build more complex application stacks also considering certain patch levels, patterns or even products to depend on. Also we were able to fix the well known issue where one could compromise a system installation by installing outdated packages after already having applied patches. Using the new technology the system is now able to detect these kinds of package-patch dependency violations. By integrating Novell's ZENworks technology we enriched our distribution by a new command line tool called 'rug' and a daemon called 'zmd' which are able to keep your system up-to-date. Also we invented a new easy-to-use patch management user interface which is called 'zen-updater'. These new tools are also able to tie into a ZENworks Linux Management infrastructure in order to allow for centralized remote management. As these changes are also impacting the user experience regarding package and patch management we'd very welcome to start a discussion thread whether and how we still can further improve the current toolchain. One question we have is how the new tools rug, zen-updater and zmd compare to what we had before with YaST Online Update and suseWatcher. We are interested in every feedback ranging from architecture, design or used standards and their enhancements. As this topic is not a very easy one I guess we'll need several iterations for this discussion. Therefore I'll try to summarize the first discussion outcomes on http://en.opensuse.org/Libzypp/Design. After a couple of weeks we can then continue the discussion after everybody had the chance to work with - and love/hate - the new toolchain, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgplyltIxYHWQ.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
houghi [EMAIL PROTECTED] writes: On Mon, May 29, 2006 at 05:03:03PM +0200, jdd wrote: may be better not advertise this before all the bugs are closed :-)) I disagree. Especially on this list we should look at the future. There are two processes. One is debugging or looking at the past. Another is features and looking at the future. Dragging this thread back to include bugs is not the way to go. It will suffocate the thread about current issues. Please don't go there. (No matter if the points are valid or not) Take it to another thread. Thanks Houghi - I agree with these points. We need to fix bugs and that's clear and discussed in far too many places - but we need to start thinking what can be done better for 10.2 and later. [...] Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp8DHHuCv81S.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
houghi [EMAIL PROTECTED] writes: [...] The most important thing for me at this moment would be that I can use YaST also to download packages I install and that it make an installation source I can use. Why would this be usefull for a single machine? I understand that somebody adminstrating lots of machines might like it. This means running createrepo or create_package_descr and do that in such a way that it does the signing automagicaly. The way I do it now is download things to /usr/src/packages/RPMS/*, do a createrepo and then use YaST to install it. At least for the stuff that is not on any of the installation sources. Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp22Olo0bDjn.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
Thomas Meindl [EMAIL PROTECTED] writes: Andreas Jaeger wrote: With SUSE Linux 10.1 we have redesigned the way we handle software. We are proud to be able to announce our new software management backend which is based on the so-called library libzypp and which also integrates Novell's ZENworks technology. That's a point that takes me aback. You all put so much work into the new package manager and its integration into 10.1 . Now there are some problems with it, and everybody rants about it (I'm too ;-)) - but I know that you are working on the issues and therefore I strongly believe that they will be solved soon. In fact we are now able to manage more than packages only. We have integrated flavors like patches, patterns and even products all of which are defined and handled equivalently to packages. This new framework allows for new ways to define system dependencies and to build more complex application stacks also considering certain patch levels, patterns or even products to depend on. What I really, really need is the possibility that all downloaded packages can be stored in a local repository on my hd. That's for several reasons: Fristly, I like to have a backup - in case of a broken distribution, I don't need to download all again (and again, and again). Secondly, this saves a lot of bandwidth and time. Thirdly, local repository can transferred to a media which can be used as a source for computers with no internet/ethernet connection... To make a long story short, I hope that zmd/rug gets some backup mode like it was integrated in YOU. Now I understand Houghi's wish as well and understand it, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpb5NitoyU3c.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
Thomas Meindl [EMAIL PROTECTED] writes: Andreas Jaeger wrote: With SUSE Linux 10.1 we have redesigned the way we handle software. We are proud to be able to announce our new software management backend which is based on the so-called library libzypp and which also integrates Novell's ZENworks technology. That's a point that takes me aback. You all put so much work into the new package manager and its integration into 10.1 . Now there are some problems with it, and everybody rants about it (I'm too ;-)) - but I know that you are working on the issues and therefore I strongly believe that they will be solved soon. In fact we are now able to manage more than packages only. We have integrated flavors like patches, patterns and even products all of which are defined and handled equivalently to packages. This new framework allows for new ways to define system dependencies and to build more complex application stacks also considering certain patch levels, patterns or even products to depend on. What I really, really need is the possibility that all downloaded packages can be stored in a local repository on my hd. That's for several reasons: Fristly, I like to have a backup - in case of a broken distribution, I don't need to download all again (and again, and again). Secondly, this saves a lot of bandwidth and time. Thirdly, local repository can transferred to a media which can be used as a source for computers with no internet/ethernet connection... To make a long story short, I hope that zmd/rug gets some backup mode like it was integrated in YOU. Now I understand Houghi's wish as well and understand it, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpJNtF5tZSvO.pgp Description: PGP signature
Re: [opensuse-factory] Package Management Design and Experience
jdd [EMAIL PROTECTED] writes: Andreas Jaeger wrote: Thanks Houghi - I agree with these points. We need to fix bugs and that's clear and discussed in far too many places - but we need to start thinking what can be done better for 10.2 and later. sorry, but I have to desagree. Your can't ask us to talk of a broken system we can't have used. I don't think we can ever end the discussion. I want to get some first comments back for our future development - and we'll keep on asking until the bugs are fixed and you can really use it... I don't ming to talk about bugs, only to have a working system to try it, judge it, see what is good what is not... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpRxwFskkPtL.pgp Description: PGP signature
Re: [opensuse-factory] Feedback for test-update
Martin Schlander [EMAIL PROTECTED] writes: I assume the point of releasing the updates for testing was to get feedback - so here goes.. Yes, exactly. I haven't done heavy testing - but I've had Zen updater running for a few days - added some repos with rug, zen and YaST etc. I must say that I don't feel much of a difference. Performance wise it still takes a lot of time to parse metadata and update-status on my amd64 3000+ Performance was not addressed in those. They fixe a couple of bugs. with inst-source, non-oss, kde-update, guru, packman. And it often ends up using about 150-250 megs of swap - I have 1 gig of ram, and normally don't swap at all. But I guess no promises were made in this department. I was under the impression that the unsigned repo warning-issue would be fixed by these updates - but I still get those. There's still one bugreport open. But I definitely haven't noticed any new bugs or worsening in any area - so good. for all I can say the updates are ready to go. I Think some people will be dissapointed though - when they see the updates they're probably going to think all the issues will be fixed. ;-) Btw., to finish up on a positive note, I had a look at the changelog for the packages, using the new changelog-feature in YaST - I really love how YaST SW gives me huge amounts of information and control. Also gives insight to the huge amount of work that's being done on the packagemanagement stuff. Cheers, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpdOc25PXKeg.pgp Description: PGP signature
Re: [opensuse-factory] Update stack test build
Graham Anderson [EMAIL PROTECTED] writes: 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. Please move it to bugzilla as commented below. 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... It was quite fast for me, if you know why it's slow, it's worth a report otherwise I guess we cannot do much. 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. Please report a bug with yum - it might even be a design decision right now. 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. Good. 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. Please file a bug against the component ZENworks, Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpkSILSqjy2I.pgp Description: PGP signature
Re: [opensuse-factory] Update stack test build
Rafael E. Herrera [EMAIL PROTECTED] writes: To add quick observations after updating the update stack posted by Andreas. 1. The Yast2 online updater hanged while trying to download the updated packages (it stopped downloading one of the packages mid-way and just sat there for a while.) Killed the process, downloaded and installed the packages manually. Not good. 2. After update, now the Installation Source panel shows all catalogs I test added before via rug, they did not show with the previous update stack. Good. 3. Updating the causes one of the cpu cores to be used close to 100% by an update-status process. It completed in about 4 minutes. I've 4 online catalogs and one local. 4 minutes for update-status is long - we have to speed it up. 4. Loading the Software Management panel takes a couple of minutes and uses up to close to 100% cpu. Please file a bug report with more information. 5. The installer now notifies of automatically selected packages for installation. 6. When you select the changelog of a package, it is not clear which one you are looking at, if there is a new version available, the installed one or the available one. Also, sometimes it takes a significant amount of time to load the changelog into the GUI. Try to load the changelog for the kernel-source package. Might be worth a bugreport, Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpK6nfNnzKQp.pgp Description: PGP signature
Re: [opensuse-factory] Update stack test build
Rafael E. Herrera [EMAIL PROTECTED] writes: To add quick observations after updating the update stack posted by Andreas. 1. The Yast2 online updater hanged while trying to download the updated packages (it stopped downloading one of the packages mid-way and just sat there for a while.) Killed the process, downloaded and installed the packages manually. Not good. 2. After update, now the Installation Source panel shows all catalogs I test added before via rug, they did not show with the previous update stack. Good. 3. Updating the causes one of the cpu cores to be used close to 100% by an update-status process. It completed in about 4 minutes. I've 4 online catalogs and one local. 4 minutes for update-status is long - we have to speed it up. 4. Loading the Software Management panel takes a couple of minutes and uses up to close to 100% cpu. Please file a bug report with more information. 5. The installer now notifies of automatically selected packages for installation. 6. When you select the changelog of a package, it is not clear which one you are looking at, if there is a new version available, the installed one or the available one. Also, sometimes it takes a significant amount of time to load the changelog into the GUI. Try to load the changelog for the kernel-source package. Might be worth a bugreport, Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpQ1rCwJpHIW.pgp Description: PGP signature
Re: [opensuse-factory] Update stack test build
[EMAIL PROTECTED] writes: = Bugzilla? Done and reported as #179018. Thanks - and I've just updated my packages on the ftp server to include this one as well, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpM8jrL32M8w.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Andras Mantia [EMAIL PROTECTED] writes: On Tuesday 23 May 2006 12:24, Anders Norrbring wrote: Apparently it's the wake-up of Zen that takes forever.. Yeah: AMD64 3200+, 1GB RAM: Waking up ZMD takes minutes (4 minutes ) and the top processes are parse-metadata and gpg: - gpg something like: gpg --no-default-keyring --quiet --no-tty --no-greeting --no-permission-warning --status-fd 1 --homedir /var/tmp/TmpDir.9ivB2c --import /var/lib/zypp/cache/Source.aDBK1K/DATA/content.key - parse-metadata is: I *did not* used an FTP source and when I started rlug sl my internet connection was down (dial-up...): zmd does not store everything, so for every wakeup we have to parse the xml data. This still takes a long time :-( rug sl Waking up ZMD...Done # | Status | Type | Name | URI --++--+---+--- 1 | Active | ZYPP | SUSE-Linux-CD-OSS-x86_64-10.1-0-20060414-082827 | cd:///?devices=/dev/hdc,/dev/hdd;alias=SUSE-Linux-CD-OSS-x86_64-10.1-0-20060414-082827 2 | Active | ZYPP | SUSE-Linux-add-on-CD-10.1-0-20060423-180936 | cd:///?devices=/dev/hdc,/dev/hdd;alias=SUSE-Linux-add-on-CD-10.1-0-20060423-180936 3 | Active | ZYPP | 20060516-193554 | ftp://ftp.iasi.roedu.net/mirrors/ftp.suse.com/pub/suse/update/10.1 4 | Active | ZYPP | SUSE-Linux-10.1-Updates | ftp://ftp.suse.com/pub/suse/update/10.1/ 5 | Active | ZYPP | SUSE-Linux-10.1-CD-download-x86_64-10.1-0-20060517-172513 | dvd:///?alias=SUSE-Linux-10.1-CD-download-x86_64-10.1-0-20060517-172513 6 | Active | ZYPP | 20060517-180334 Before you tell me about the dups, in Yast Installation Sources (which again takes quite some time to show up completely) I have the following: On Off SUSE Linux 10.1 dvd:/// Off On YUM ftp://ftp.iasi.roedu.net/mirrors/ftp.suse.com/pub/suse/update/10.1 On On YUM dir:///media/extra/data/data/opensuse/packman/10.1 On On YUM ftp://ftp.suse.com/pub/suse/update/10.1 The first update was added manually, while during registration it added the last one (it failed to detect a mirror for me). So in this case it cannot be about downloading a huge XML file or something like that. So, remove the dups to speed up... The system is an update from 10.0 in several steps through some beta's and RC's. We have to handle that better, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpU5GAO5YV9E.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Vahis [EMAIL PROTECTED] writes: # rug sa Add: --type=yum or: --type=zypp both should work. ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/ ERROR: Could not add 'ftp://ftp.suse.com/pub/people/aj/10.1-packagemanagement-update-test/': No suitable service types could be found I added that with YaST and it worked. The stuff appeared as updates (the Globe went orange) in updater. Updates were then installed. At this stage I'm so mixed up with all these adding and removin that I'm not sure what those updates did or didn't. ;-) Restart zmd and zen-updater and you're current again, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpaTbWGT7ope.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Frank-Michael, have you done an update from a previous beta/RC on these machines? What's the output of: * rug sl * rug ca Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpXKc8Wk2llB.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Frank-Michael Fischer [EMAIL PROTECTED] writes: Problem is: during beta test I have been busy reporting and detailling other bugs so I did not participate in the zen buddism here. And I'd agree with you that it will be solved etc. I just did not know (did you?) that it takes up to half an hour to get a 2.xGHz machine booted into a proper functioning state. For me this order of magnitude of slow down is unexpected, I am not even sure it was there with beta versions. It's unexpected for me as well, I wouldn't have shipped it if we had seen this with new installation. I got some reports from people doing an update from Beta7 where zmd took ages and those where a result of old repositories. Btw. I'm currently working on releasing an update of the package management stack. It will not solve the performance issues in general but fixes a couple of bugs so if the problem you have comes from such a bug, it might be fixed... Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpLADaBmQZrc.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Frank-Michael Fischer [EMAIL PROTECTED] writes: Thanks a lot, I will watch for these fixes. And I am available for such discussions. Meanwhile I did reinstall rug (just 4u ;-) What do you mean by: * rug sl * rug ca I never used rug before so I wouldn't know how to interpret your mnemonics. Those are commands that you can run, on my system, sl is the same as service-list, and ca as catalogs, they show the installation sources in your system. On my test system right now: [EMAIL PROTECTED]:~ rug sl # | Status | Type | Name | URI --++--++--- 1 | Active | ZYPP | SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060522-041628 | ftp://10.10.0.100/%2finstall/SLP/SUSE-10.1-DVD9-RC5/i386/DVD1?alias=SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060522-041628 2 | Active | ZYPP | SUSE-Linux-10.1-Updates| http://ftp.leo.org/pub/comp/os/unix/linux/suse/suse/update/10.1/ [EMAIL PROTECTED]:~ rug ca Sub'd? | Name | Service ---++--- Yes| SUSE-Linux-10.1-Updates| SUSE-Linux-10.1-Updates Yes| SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060522-041628 | SUSE-Linux-10.1-DVD9-x86-x86_64-10.1-0-20060522-041628 Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpVOuytRi45O.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Anders Norrbring [EMAIL PROTECTED] writes: Andreas Jaeger skrev: Frank-Michael, have you done an update from a previous beta/RC on these machines? What's the output of: * rug sl * rug ca Andreas Apparently it's the wake-up of Zen that takes forever.. It loads both CPUs to 100% while coming to life. When alive sommands go instantly, no more than 0.3 seconds to execute just about anything that doesn't involve checking sources online, while doing the same things with zmd.exe in sleep state takes between 1.5 and 10 minutes. Note that /etc/zmd/zmd.conf has a config option when zmd goes to sleep again: ~~ [Advanced] run-transaction-test=False [Server] bind-ip=127.0.0.1 refresh-interval=86400 inventory-enabled=True remote-enabled=false require-verified-certs=True sleep-interval=1800 ~~ sleep-interval=1800 means it sleeps after 30 minutes of inactivy - which is fine for me. You can increase those values if you like. Once zmd sleeps it needs some time to wake up again since it does not store everything in its database :-( Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpFfpP7ShqOr.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Frank-Michael Fischer [EMAIL PROTECTED] writes: Andreas Jaeger wrote: Frank-Michael, have you done an update from a previous beta/RC on these machines? What's the output of: * rug sl * rug ca Andreas Now this is interesting: After reinstalling rug, running rug sl rug ca and rebooting the system, bug 177758 does not show anymore. Could it be that everyone who started rug at least once explicitely or implicitely gets rid of the bug? Not sure - but before you test further, wait for the test packages that I plan to release tomorrow, they fix a couple of bugs, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgp6rBtKkOB8T.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
houghi [EMAIL PROTECTED] writes: On Tue, May 23, 2006 at 01:38:56PM +0200, Andreas Jaeger wrote: Frank-Michael Fischer [EMAIL PROTECTED] writes: The reason why I am assuming it's libzypp's fault is: when I filed the bug it was for the Zen component, then Nat Budin changed the component to libzypp and connected this bug with bug 176301. This bug I am not supposed to view. So it's fair to guess there is something rotten in the state of libzypp. And we should not participate, just sit and wait. Why is everybody thinking there's something rotten going on if a bug is closed? I believe you misread it. The bug was moved. Because it was originaly was reported as a lybzypp bug, the one where it is moved to will also be a libzypp bug. I'm talking about 176301. It was never public. Let's leave that one as reported against SLES - that way it will get highest priority ;-). If anybody likes to be CC'ed on it, tell me offline and I add you to it. This most likely means that there is an issue with libzypp, because otherwise the bug would have been closed and not noted as a duplicate. Bug 177758 was connected to 176301 as bug 177758 must be first fixed before we can close 176301. All is giuessing, because we are not allowed to see #176301 even though it was first a public one. It never was. So the conclusion of Frank-Michael is correct: It must be a libzypp issue. Those are totally unrelated - but since 176301 is not public, you can just speculate ;-) Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpyNzvuHAQjy.pgp Description: PGP signature
Re: [opensuse-factory] Bug 177758
Frank-Michael Fischer [EMAIL PROTECTED] writes: Andreas Jaeger wrote: Frank-Michael Fischer [EMAIL PROTECTED] writes: The reason why I am assuming it's libzypp's fault is: when I filed the bug it was for the Zen component, then Nat Budin changed the component to libzypp and connected this bug with bug 176301. This bug I am not supposed to view. So it's fair to guess there is something rotten in the state of libzypp. And we should not participate, just sit and wait. Why is everybody thinking there's something rotten going on if a bug is closed? Not because it's closed. I could not even know that. It's because I am not supposed to know the bug. This creates the rotten suspicion. closed was meant in the sense of private/non-public, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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 pgpfWrGU14Cm0.pgp Description: PGP signature
