November 2012 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] systemd status in Factory : WAIT BEFORE UPGRADING TO CURRENT FACTORY
by Frederic Crozat 12 Nov '12

12 Nov '12

Le mercredi 07 novembre 2012 à 10:58 +0100, Jiri Slaby a écrit : > On 11/07/2012 09:34 AM, Frederic Crozat wrote: > > Le mercredi 07 novembre 2012 à 09:09 +0100, Jiri Slaby a écrit : > >> On 11/05/2012 11:42 AM, Frederic Crozat wrote: > >>> Until all those issues are fixed (I'll sent a follow-up mail > >>> here), please DON'T UPGRADE YOUR FACTORY INSTALLATION. > >> > >> Hi, I tried in a VM though. Installing systemd 195 kills process > >> 1 (init) which indeed causes a panic: Installing: systemd-195-4.1 > >> ....................................<100%> Kernel panic - not > >> syncing: Attempted to kill init! exitcode=0x00007f00 > > > > And unfortunately, this is something I can't reproduce reliably: > > got it one time while doing a full upgrade with 195-3.1 and I > > thought fixing the various udev instances running when upgrading > > would fix it but apparently, it doesn't. > > > > From which state did you upgrade your VM ? > > Just factory before the systemd update: systemd-44. I think it is > related to libudev. libudev0 is removed, systemd is reexec'ed => boom. > Or maybe other way around. systemd 195 is installed while libudev1 is > not installed yet; reexec => boom. Is that a possible scenario? systemd reexec is supposed to happen in %post of systemd, and systemd is upgraded only after both udev and libudev1 has been upgraded so it shouldn't be a problem. I'll try again to duplicate this issue. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] X11:Enlightenment:Released as devel project
by Tomas Cech 12 Nov '12

12 Nov '12

Hi, I'd like to add X11:Enlightenment:Released project as devel project and start pushing packages from this project to Factory. This project contains released versions of Enlightenment 17 and Enlightenment Foundation Libraries and I believe that is in quite good shape already. Enlightenment 17 reached alpha stage recently, so I believe it would be beneficial to support E17 as next officialy supported option for next openSUSE release (but that is still far future). I'd like to to ask for help with the package review, testing and changing the project to devel one. TIA, Tomas Cech Sleep_Walker

2 3

[opensuse-factory] udev package problem?
by Sid Boyce 11 Nov '12

11 Nov '12

Looks like the / before usr is missing in some file as all those files are in /usr/lib/udev/rules.d/. Kernel image: /boot/vmlinuz-3.6.0-1-desktop Initrd image: /boot/initrd-3.6.0-1-desktop Root device: /dev/disk/by-id/ata-WDC_WD20EARS-07MVWB0_WD-WCAZA4270277-part1 (/dev/sda1) (mounted on / as ext4) cp: cannot stat 'usr/lib/udev/rules.d/10-dm.rules': No such file or directory cp: cannot stat 'usr/lib/udev/rules.d/13-dm-disk.rules': No such file or directory cp: cannot stat 'usr/lib/udev/rules.d/95-dm-notify.rules': No such file or directory Kernel Modules: thermal_sys thermal processor fan pata_atiixp ata_generic sata_nv pata_amd sata_sil24 scsi_dh scsi_dh_rdac scsi_dh_emc scsi_dh_hp_sw scsi_dh_alua pata_efar pata_ns87415 pata_sis pata_cmd64x pata_rz1000 sata_inic162x pata_serverworks pata_ali sata_svw pata_cs5530 pata_it821x sata_uli pata_rdc pata_pdc2027x sata_qstor ata_piix pata_pdc202xx_old ahci_platform pata_marvell pata_netcell pata_it8213 pata_cs5520 pata_cypress sata_promise pata_atp867x pata_arasan_cf pata_via sata_via sata_sx4 pata_oldpiix pata_radisys acard-ahci pata_sc1200 pata_cmd640 pata_ninja32 pata_triflex sata_mv pdc_adma pata_optidma sata_sis pata_jmicron pata_cs5536 pata_sl82c105 pata_opti pata_hpt3x2n pcmcia_core pcmcia pata_pcmcia pata_sil680 pata_sch pata_mpiix pata_artop pata_hpt366 sata_sil pata_acpi sata_vsc pata_hpt3x3 pata_hpt37x pata_piccolo pata_ns87410 xhci-hcd hid-logitech-dj Features: acpi plymouth block usb resume.userspace resume.kernel Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] Issues with Factory repo for pwdutils
by Raymond Wooninck 11 Nov '12

11 Nov '12

Hi, I have cross posted this message in both Factory and Packaging, as that I am not sure where exactly it belongs. Since this weekend I am seeing issues when a package is build against Factory snapshot and the %pre/%post scripts are trying to create a group/user. (The example is from lightdm) The script executed is: %pre /usr/sbin/groupadd -r lightdm 2> /dev/null || : /usr/sbin/useradd -r -o -g lightdm -s /bin/false -c "LightDM daemon" \ -d /var/lib/lightdm lightdm 2> /dev/null || : /usr/sbin/usermod -g lightdm -G lightdm -s /bin/false lightdm 2> /dev/null But the output when build against Factory snapshot is: [ 232s] configuration error - unknown item 'MOTD_FILE' (notify administrator) [ 232s] configuration error - unknown item 'ENV_ROOTPATH' (notify administrator) [ 232s] configuration error - unknown item 'PASS_MIN_LEN' (notify administrator) [ 232s] configuration error - unknown item 'GROUPADD_CMD' (notify administrator) [ 232s] configuration error - unknown item 'USERADD_CMD' (notify administrator) [ 232s] configuration error - unknown item 'USERDEL_PRECMD' (notify administrator) [ 232s] configuration error - unknown item 'USERDEL_POSTCMD' (notify administrator) [ 232s] useradd: group '1000' does not exist [ 232s] useradd: the GROUP= configuration in /etc/default/useradd will be ignored [ 232s] useradd: -o flag is only allowed with the -u flag [ 232s] Usage: useradd [options] LOGIN [ 232s] useradd -D [ 232s] useradd -D [options] [ 232s] [ 232s] Options: [ 232s] -b, --base-dir BASE_DIR base directory for the home directory of the [ 232s] new account [ 232s] -c, --comment COMMENT GECOS field of the new account [ 232s] -d, --home-dir HOME_DIR home directory of the new account [ 232s] -D, --defaults print or change default useradd configuration [ 232s] -e, --expiredate EXPIRE_DATE expiration date of the new account [ 232s] -f, --inactive INACTIVE password inactivity period of the new account [ 232s] -g, --gid GROUP name or ID of the primary group of the new [ 232s] account [ 232s] -G, --groups GROUPS list of supplementary groups of the new [ 232s] account [ 232s] -h, --help display this help message and exit [ 232s] -k, --skel SKEL_DIR use this alternative skeleton directory [ 232s] -K, --key KEY=VALUE override /etc/login.defs defaults [ 232s] -l, --no-log-init do not add the user to the lastlog and [ 232s] faillog databases [ 232s] -m, --create-home create the user's home directory [ 232s] -M, --no-create-home do not create the user's home directory [ 232s] -N, --no-user-group do not create a group with the same name as [ 232s] the user [ 232s] -o, --non-unique allow to create users with duplicate [ 232s] (non-unique) UID [ 232s] -p, --password PASSWORD encrypted password of the new account [ 232s] -r, --system create a system account [ 232s] -R, --root CHROOT_DIR directory to chroot into [ 232s] -s, --shell SHELL login shell of the new account [ 232s] -u, --uid UID user ID of the new account [ 232s] -U, --user-group create a group with the same name as the user [ 232s] -Z, --selinux-user SEUSER use a specific SEUSER for the SELinux user mapping [ 232s] [ 232s] usermod: user 'lightdm' does not exist [ 232s] error: %pre(lightdm-1.4.0-17.1.x86_64) scriptlet failed, exit status 6 [ 232s] error: lightdm-1.4.0-17.1.x86_64: install failed Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] mkinitrd from Kernel:stable breaks 12.2 and below
by Andrey Borzenkov 09 Nov '12

09 Nov '12

There are massive reports from users on forum in the last days. Similar to Kernel image: /boot/vmlinuz-3.6.6-1-desktop Initrd image: /boot/initrd-3.6.6-1-desktop Kernel Modules: <not available> Could not find map /boot/System.map, please specify a correct file with -M. There was an error generating the initrd (9) mkinitrd from Kernel:stable does not work on 12.2 and below due to changed path to /sbin/get_kernel_version. May we let it check *both* locations? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] opensuse theme for awesome windowmanager
by Togan Muftuoglu 09 Nov '12

09 Nov '12

Hi, For those following the factory know that awesome windowmanager is now available in the factory. At its' current stage it provides just the upstream version, however my intention is to provide an opensuse theme along with customized rc.lua If any of you are using awesome, must be 3.4.13 not the git version, and have a customized rc.lua or a customized theme and would like to share it with the rest of the community this might be the right time. I am preparing awesome-opensuse theme package along with the customized rc.lua and I would be happy to incorporate all or parts of your settings as it fits. However if nothing shows up well hope you enjoy what is offered ;) So if you are interested please provide a link, paste address where your settings can be retrieved and make sure you provide a license for your work so I can include your work in the package. Thanks Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: [opensuse-factory] systemd status in Factory : WAIT BEFORE UPGRADING TO CURRENT FACTORY
by Frederic Crozat 09 Nov '12

09 Nov '12

Le mercredi 07 novembre 2012 à 09:09 +0100, Jiri Slaby a écrit : > On 11/05/2012 11:42 AM, Frederic Crozat wrote: > > Until all those issues are fixed (I'll sent a follow-up mail here), > > please DON'T UPGRADE YOUR FACTORY INSTALLATION. > > Hi, I tried in a VM though. Installing systemd 195 kills process 1 > (init) which indeed causes a panic: > Installing: systemd-195-4.1 ....................................<100%> > Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 And unfortunately, this is something I can't reproduce reliably: got it one time while doing a full upgrade with 195-3.1 and I thought fixing the various udev instances running when upgrading would fix it but apparently, it doesn't. >From which state did you upgrade your VM ? -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 8

[opensuse-factory] New package: ghc
by Peter Trommler 08 Nov '12

08 Nov '12

I will submit ghc (The Glorious Glasgow Haskell Compilation System) as a new package to Factory. GHC's main web page is: http://www.haskell.org/ghc/ Package ghc is developed at OBS in devel:languages:haskell Description: GHC is a state-of-the-art, open source, compiler and interactive environment for the functional language Haskell. It is part of Haskell Platform. Maintainability: The compiler has about 3-5 releases per year. Reasons to have it in Factory: Needed for Haskell Platform FATE #314446 (https://features.opensuse.org/314446) and pandoc FATE #312777 (https://features.opensuse.org/312777) Hints for package reviewers: We need to bootstrap the compiler. Therefore we need to bring a binary compiler in with a source file. That binary compiler will only be used to bootstrap a stage 0 compiler and will not be included in the resulting binary rpm. After bootstrap is done in Factory I will submit the package again with all bootstrap code removed. Lines that I will remove are marked with comments # remove after initial bootstrap and # end bootstrap. See the following package in my home project: https://build.opensuse.org/package/show?package=ghc&project=home%3Aptrommler %3Abranches%3Adevel%3Alanguages%3Ahaskell If you have further questions or requests, please drop me a line. Thanks, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 7

[opensuse-factory] Liberation-2.0 appears broken
by Ilya Chernykh 08 Nov '12

08 Nov '12

I installed Liberation-2.0 on an openSUSE 12.2 system. The font appears with broken hinting with vertical lines not aligned with pixels, "soap" and "rainbow" effects. With the same settings Liberation-1 appears correctly. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] systemd status in Factory : WAIT BEFORE UPGRADING TO CURRENT FACTORY
by Frederic Crozat 08 Nov '12

08 Nov '12

Hi all, as some people noticed, despite testing new systemd release in a Staging repository for some weeks, some bugs went into the upgrade. Those bugs are due to both systemd and udev being moved to /usr. What does it means for packagers : - systemd will continue to check its .service from /lib/systemd/system, in addition to /usr/lib/systemd/system (and /etc/systemd/system) but packagers should change their package to use the new location for Factory (an rpmlint rule to detect that will be enabled soon) - udev will only check /usr/lib/udev/rules.d. The udev package has been modified to migrate /lib/udev/ to /usr/lib/udev and replace /lib/udev by a symlink to /usr/lib/udev. So, packages installing rules in /lib/udev should still be ok but they should be fixed to use the new rules (I've fixed all known broken packages in Factory already). Again, an rpmlint rule for this will be enabled soon in Factory - RUN+="socket:..." rules are not longer supported by udev 195. The only remaining package using it is multipath and Hanne is fixing it. Current issues - filesystem upgrade: this one is still under investigation (fortunately, Robert has a VM exhibiting the bug so I'll be able to test this one). For M1, filesystem was reverted to its previous state and we'll see on re-doing the changes after M1 is out. - mkinitrd needed to be modified to correctly handle udev new path but unfortunately, I missed one directory in my patch to handle this. Fixed package should be pushed in Factory pretty soon. - udev was supposed to move /lib/udev to /usr/lib/udev but one test in the install script in udev package was wrong, which was preventing the /lib/udev move. This will be also fixed soon. Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION. Thanks. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 30

[opensuse-factory] OBS supports constraints now
by Adrian Schröter 08 Nov '12

08 Nov '12

After updating build.opensuse.org to current OBS code we have now support for build job constraints now. This means you can tell OBS to build a certain package, repository or project to build only on build hosts which grant a certain hardware or software feature. Just to name two examples, you can require a certain amount of memory or storage space. Or you can build on a special kind of build host which guarantees you that benchmark result can be compared between the build jobs. Please note that you limit your package to be dispatched to a subset of hosts. So it may dispatched way later or in worst case not at all when we do not have such a build host. This means it stays in "scheduled" state. We do _NOT_ have a "dispatchstatus" yet which would tell if a job is dispatchable at all or not. Please find details about this feature in our book chapter: http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_… Just as an example, you may want to require a VM memory size of 2GB. You need add a "_constraints" file into your package source with this syntax: <constraints> <hardware> <memory unit=G>2</memory> </hardware> </constraints> Or you want to run on a specific new host, which we have to have comparable benchmarks. There is only running one build job on this hardware and it will always have the same hardware configuration. You need to use the hostlabel "benchmark" in our build.opensuse.org instance: <constraints> <hostlabel>benchmark</hostlabel> </constraints> -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Status: Distribution
by Stephan Kulow 08 Nov '12

08 Nov '12

Hi, This week we have Milestone1 scheduled and I'm really trying everything to stabilize factory to a point of being able to release it. The biggest problem we see at the moment is udev moving to /usr (in the arms of systemd) causing all kind of problems. Additionally we broke the sysvinit compat, but this should be repaired already, but it caused some hickups. Before I close my laptop today, you will know if we release M1 or not, if it's not on the horizon today, there is no point to continue this week. I thought > 7 days after the conference would be enough to get it going, but I didn't take into account how tired we would be :) The good news is that we have way more helping hands than in the late past, so I'm still confident. Give us some more hours :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 11

[opensuse-factory] The KDE Desktop is looking for maintainers (or not.....)
by Raymond Wooninck 07 Nov '12

07 Nov '12

Dear List mates, Some time ago it was announced that each devel project should have a number of maintainers that are doing the work and supporting each other. I would like to raise the issue that the KDE repositories (KDF and KR49) are currently being maintained by a lower number of people than was indicated. In other words, lately most of the packaging work and supporting KDF/KR49 was done just by me. Looking forward than I won't be able to spend that much time anymore on supporting KDE within openSUSE and therefore I would like to call for volunteers that would like to support the KDE desktop within openSUSE and doing the packaging, bugfixing, etc. The future of the KDE desktop within openSUSE depends on your support and it would be ashame to see the KDE desktop disappearing due to lack of maintainership. In my heart I know that the KDE community within openSUSE is big and definitely capable of keeping the KDE desktop alive. If you do not feel experienced enough to take this task upon you, then be asured that there are experienced people willing to help and guide you. Let's make KDE the best desktop within openSUSE Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] OBS Downtime Tomorrow
by Adrian Schröter 07 Nov '12

07 Nov '12

OBS will have a downtime of 1-2hours tomorrow (thursday) during our regular maintenance window. We will start at 08:00 UTC to move our servers physically and do also a larger OBS version update (details will follow on that later). This will affect the hosts build.opensuse.org api.opensuse.org Software.opensuse.org will not have the package search during the OBS downtime. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] boost 1.52.0
by Alin Marin Elena 07 Nov '12

07 Nov '12

Dear All, I am trying to update the boost library to 1.52.0 branched it here https://build.opensuse.org/project/show?project=home%3Aealin%3Abranches%3Ad… There are two issues I need help with... 1. the generation of the docs fails. I deactivate it the lib builds fine... and I updated the spec to add the new libs added... I have already removed the patches which are applied upstream and made sure the remaining ones apply... 2. shall we ship python3? fedora already does it...but they use a different approach to build boost... Alin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] XFCE : Purpose of /.cache/tracker/meta.db ??
by ellanios82 07 Nov '12

07 Nov '12

Hello List - what please is the Purpose of /home/user/.cache/tracker/meta.db ?? ........ thanks Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] What is Network repository and can i do without it for Tumbleweed?
by Trent Hawkins 07 Nov '12

07 Nov '12

This is going to sound like a noob question but... I am in the process of switching over to Tumbleweed from openSUSE12.2 base. Somewhere along the line i gathered a bunch of repos which i don't know if i actually need anymore. This includes: Network12.2 - http://download.opensuse.org/repositories/network/openSUSE_12.2/ I googled search a bit for what exactly it was, but couldn't unearth anything. Does anyone know what its for? The only package i have installed from it (what i can tell using YAST) is one called "cyrus-sasl-devel" - v2.1.25-55.1. Looks to be a newer version than the one in Current Oss. Also i have KDE Extra repo enabled because of Dropbox. Is this going to create a conflict with Tumbleweed when i zypper dup? Is Dropbox in Factory (therefore can make it into Tumbleweed)? Thanks in advance, Trent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 8

[opensuse-factory] sparsehash is looking for a new home
by Mariusz Fik 06 Nov '12

06 Nov '12

Hi, I just updated clementine package to 1.1.0. One of the new feature is integration with Google Drive - but to get this working, sparsehash package is required. I prepared it as well in my branch[1]. I want to push this package to Factory to get it included in 12.3 but first we need a new home (aka devel project) for sparsehash. Which project should be the most accurate? I think devel:libraries:c_c++ looks fine. Any opinions? [1]- https://build.opensuse.org/package/show?package=sparsehash&project=home%3AF… -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

1 0

[opensuse-factory] A line in openSUSE:Factory: systemd-mini.spec and systemd.spec I don't understand
by Joop Boonen 06 Nov '12

06 Nov '12

Hi all, I saw a line in openSUSE:Factory: systemd-mini.spec and systemd.spec I don't understand. %if 0%{?bootstrap} Requires: this-is-only-for-build-envs %else Because of this line ARM Factory JeOS images aren't build any more due to: nothing provides this-is-only-for-build-envs needed by systemd-mini Is this Requirement in the spec file for a specific reason? Regards, Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Re: systemd and hardware clock
by Frederic Crozat 06 Nov '12

06 Nov '12

Le mardi 06 novembre 2012 à 12:01 +0100, Dr. Werner Fink a écrit : > Hi, > > due several bug reports, I'm currently reading the code of systemd-195 > as found in oS:Factory. I'm a bit surprised about some missing features > and bottlenecks: > > * There is no --adjust functionality to handle systematic drift of the > HW/RTC clock of the BIOS > * There is no --badyear functionality for broken some Award BIOS > * It ignores s390 as well as XEN clients > * It does not provide --systohc functionality which had lead to several > bug reports about the fact that the system clock is not written back > to RTC at shutdown/reboot > * It does not check for the SUSE /dev/shm/warpclock ... OK this does not > cause a problem as settimeofday(2) with its timezone is sealed within > the kernel after warpclock has been called in the initrd. > I'm wondering how the timestamps of the root file system will be > repaired if the timezone correction would not be done in the initrd. > > ... the question rises if we should try to implement this in the C source > of systemd (src/shared/hwclock.c and src/timedate/timedated.c) or is there > a way to avoid the systemd-timed service with a more complete but shell code > script executed by a systemd service unit at boot as as at shutdown/reboot. It would be much better to raise those points directly on upstream mailing list, since they are not openSUSE specific (and I don't know how they are handled by other distributions either). -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] A line in openSUSE:Factory: systemd-mini.spec and systemd.spec I don't understand
by Joop Boonen 06 Nov '12

06 Nov '12

Hi all, I saw a line in openSUSE:Factory: systemd-mini.spec and systemd.spec I don't understand. %if 0%{?bootstrap} Requires: this-is-only-for-build-envs %else Because of this line ARM Factory JeOS images aren't build any more due to: nothing provides this-is-only-for-build-envs needed by systemd-mini Is this Requirement in the spec file for a specific reason? Regards, Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] systemd and hardware clock
by Dr. Werner Fink 06 Nov '12

06 Nov '12

Hi, due several bug reports, I'm currently reading the code of systemd-195 as found in oS:Factory. I'm a bit surprised about some missing features and bottlenecks: * There is no --adjust functionality to handle systematic drift of the HW/RTC clock of the BIOS * There is no --badyear functionality for broken some Award BIOS * It ignores s390 as well as XEN clients * It does not provide --systohc functionality which had lead to several bug reports about the fact that the system clock is not written back to RTC at shutdown/reboot * It does not check for the SUSE /dev/shm/warpclock ... OK this does not cause a problem as settimeofday(2) with its timezone is sealed within the kernel after warpclock has been called in the initrd. I'm wondering how the timestamps of the root file system will be repaired if the timezone correction would not be done in the initrd. ... the question rises if we should try to implement this in the C source of systemd (src/shared/hwclock.c and src/timedate/timedated.c) or is there a way to avoid the systemd-timed service with a more complete but shell code script executed by a systemd service unit at boot as as at shutdown/reboot. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] tp_smapi/hdaps(d) in openSUSE
by Dominik Schmidt 06 Nov '12

06 Nov '12

Hey opensuse-factory, everytime I decide to play neverball on my Thinkpad with the accelerometer as joystick, I'm overwhelmed by the amount of unofficial tp_smapi packages and really can't decide which one to take.. I feel there should be a package in the official repos... :D To give this a little more serious sense: tp_smapi is a kernel module for accessing the HDAPS ( http://www.thinkwiki.org/wiki/Active_Protection_System ) system in Thinkpads which can be used to park the hard-drive when the laptop is moved (or especially to protect the disk when the laptop is falling down while it's running etc). In addition to that module the hdapsd daemon is needed. Is there any reason those two packages are not in any official repo? As long as that repo existed the module seems to have been in the :Contrib repo. Of course I'm not suggesting that simply anyone should add this but I'm volunteering to do the work :-) But I do need some hints where to start: 1.) Which devel repo would I submit the kernel module to? 2.) Which devel repo would I submit the daemon to? 3.) How do I correctly package kernel modules? As I said, there are a lot of packages already. This one looks fairly reasonable: https://build.opensuse.org/package/files?package=tp_smapi-kmp&project=home%… Could that be submitted as is? Best regards, Dominik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] KDE menus and gitorious
by Cristian Morales Vega 06 Nov '12

06 Nov '12

I created a merge request for desktop-data three weeks ago. It's just a minor patch that doesn't really fix anything but a warning from kbuildsycoca4. I'm not sure about how Gitorious works, maintainers are supposed to notice the "1" in the merge requests section or they receive an email notifying it? And since I'm on it. Since I updated my 11.3 system to KDE to 4.5 the "inline" part of the menu is not honored... Expected behavior? Known problem? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 6

[opensuse-factory] New package: Nitrogen background setter for X windows
by Togan Muftuoglu 06 Nov '12

06 Nov '12

Hi, Shortly I will be submitting nitrogen from X11:Utilities to factory. Information regarding nitrogen is given below, and this package although not required can be used as wallpaper changer for awesome and sawfish windowmanagers which are on their route to factory (just waiting buildrequires for these two be in factory) Nitrogen is a background browser and setter for X windows. It is written in C++ using the gtkmm toolkit. It can be used in two modes: browser and recall. Some of the features are: * Multihead and Xinerama aware. * Recall mode to used via startup script. * Uses freedesktop.org standard for thumbnails. * Can set GNOME background. * Command line set modes for script use. * Inotify monitoring of browse directory. * Lazy loading of thumbnails - conserves memory . * "Automatic" set mode - determines best mode to set an image based on its size. * Display preview images in a tiled icon layout Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] rtkit-daemon
by Constant Brouerius van Nidek 05 Nov '12

05 Nov '12

On my system I found the following erroor message: : Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: No such file or directory How could I solve this error? -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.3 Milestone 0 (i586) Kernel: 3.6.3-1-default KDE Development Platform: 4.9.2) 13:33pm up 0:37, 4 users, load average: 0.81, 0.74, 1.04 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] today's update broke 12.3 m0
by Patrick Shanahan 05 Nov '12

05 Nov '12

12.3 m0 in VB update hung, rebooted after 30 min boots to grub rescue prompt with no help and does not accept any commands I try ??? repeatable -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 14

[opensuse-factory] Secure Boot again
by Greg Freemyer 05 Nov '12

05 Nov '12

All, I'd like to suggest that the openSUSE 12.3 boot/install media have the new Linux Foundation pre-boot Secure Boot utility as the first stage of booting. That is in addition to the already discussed plans for handling UEFI secure boot after the initial install. == details There is a new Linux Foundation pre-boot Secure Boot utility available. http://www.linuxfoundation.org/news-media/blogs/browse/2012/10/linux-founda… Interesting and I'm glad to see it, but it doesn't fundamentally change things for UEFI Secure Boot systems running openSUSE 12.3 and newer. But it does for non-compliant systems that don't have a way to disable Secure Boot during OS installs. As it strongly implies, a pre-boot loader is being created by the Linux Foundation and they are going through the process of getting it signed by an official Microsoft Key. That means all UEFI Secure Boot systems will see this new pre-boot loader as being properly signed. (The new pre-boot loader is going to require a human is at the keyboard before it advances to the boot sequence, so it is not a panacea, especially for servers.) Thus the mechanism to boot non-Microsoft signed media like the openSUSE install media becomes: - Disable Secure Boot in the bios, either one time or permanently OR - Boot via the new Linux Foundation pre-boot loader, confirm you are physically present, then continue boot process to non-signed CD/OS/etc. It seems the openSUSE 12.3 install/boot media should have the new pre-boot loader as the first stage of booting. That would also mean that people using those media won't have to disable secure boot in the bios during installs. It will make the install process much more seemless if the user doesn't have to go into the bios prior to doing the install. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] Status of systemd vs sysvinit, xinetd, syslog
by Marcus Meissner 05 Nov '12

05 Nov '12

Hi, As development group maintainer I start to see requests (mostly from Cristian Rodriguez) that remove sysvinit, xinetd support completely from packages and also remove syslog dependencies. What is the current status? Is the total sysvinit removal and total xinetd removal now fact and the future plan? Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 12

Re: [opensuse-factory] Firefox 16.0.2 : Maximum number of clients reached : cannot connect to X server :0
by ellanios82 05 Nov '12

05 Nov '12

my System : Tumbleweed kdebase4-workspace-4.8.5-2.10.1.i586 _________________ Hello List, - new development : presently i am not able to start firefox at all : from Konsole, just get the message : ______________ /usr/bin/firefox Maximum number of clients reachedMaximum number of clients reachedError: cannot open display: :0 .................... what please can i try to Fix this ?? ......... best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 10

[opensuse-factory] mkinitrd or dracut ?
by Raymond Wooninck 05 Nov '12

05 Nov '12

Unfortunately it is a public holiday in Austria and therefore I have too much time to play around with the system and come up with stupid ideas :-) But as I am used to live on bleeding edge technology and software, I have been using the 3.7 kernel from Kernel:HEAD and faced some issues with it. At the moment I am running the rc3 version and my previous issues seemed to have been resolved and the kernel is flying :-) However due to another bug in Factory regarding mkinitrd, I had to find another way of creating the required initrd to be able to boot the system with the new kernel. All my attempts with mkinitrd ended either without an initrd image or with a non-bootable image. On IRC I got the indication that openSUSE also has the dracut package which is an alternative to mkinitrd. I installed the required dracut packages and could very easily generate the initrd and bring it into grub. When I booted, I was somehow surprised how fast it actually was and I am wondering if this is due to dracut or the new kernel. Again based on the current status of mkinitrd (and the fact that the above bug somehow seems to take quite some time to be resolved) I really wonder if we have to keep the old mkinitrd functionality or that we should go with a newer technology which is used by more distributions. Especially as that we are already providing working packages for dracut. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 10

[opensuse-factory] To PackageKit or not to PackageKit
by Raymond Wooninck 05 Nov '12

05 Nov '12

Hello listmates.... I know that most likely I will be causing another flamewar on this mailinglist, but I hope that we can keep the discussion to facts and to the point. As the subject already indicates I would like to know what the openSUSE community plan is for PackageKit. At this moment we have version 0.7.4 in Factory, despite that upstream already delivered version 0.8.5. I have tried to package 0.8.5, but it seems that in this version the zypp backend is not maintained ( My assumption here is that openSUSE did the maintainance for this part as that libzypp is only used by openSUSE). Based on the above status and also seeing discussions on the opensuse-kde ml regarding how Apper is working as an update notifier, I have the feeling that we as a community should take a decision. At this moment I don't see anything that is offered as a small package update notifier (nor on KDE nor on GNOME side) that works directly with zypper or with yast. Both desktops have been using PackageKit for this (or tools based using PackageKit), but it seems that PackageKit is not really supported by our zypp/YaST community. So the question is will we keep PackageKit in our openSUSE distro or not ? If yes, then the zypp/YaST community should have a look at the latest version and make the zypp backend build and work again. If not, do we have alternatives that we can offer to the users as a small systray utility that notifies them when updates are available ? Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

14 22

[opensuse-factory] Is KDE on the near horizon for Tumbleweed?
by Roman Bysh 05 Nov '12

05 Nov '12

Hello List mates, Can we see KDE for Tumbleweed available by the end of October? Cheers! Roman --------------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! --------------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6

Re: [opensuse-factory] Firefox 16.0.2 : Maximum number of clients reached : cannot connect to X server :0
by ellanios82 04 Nov '12

04 Nov '12

my System : Tumbleweed kdebase4-workspace-4.8.5-2.10.1.i586 _________________ Hello List, when attempting to start gimp , i get : /usr/bin/gimp Maximum number of clients reachedxcb_connection_has_error() returned true Maximum number of clients reached (screenshot:11711): Gtk-WARNING **: cannot open display: :0.0 ................ best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Firefox 16.0.2 : Maximum number of clients reached : cannot connect to X server :0
by ellanios82 04 Nov '12

04 Nov '12

my System : Tumbleweed kdebase4-workspace-4.8.5-2.10.1.i586 _________________ Hello List, upon trying start ksnapshot : KDEInit could not launch '/usr/bin/ksnapshot' ................ best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Firefox 16.0.2 : Maximum number of clients reached : cannot connect to X server :0
by ellanios82 04 Nov '12

04 Nov '12

On 11/04/2012 08:58 AM, DenverD wrote: > on the other hand, if using Tumbleweed or 12.3, post again to the list > and include that info as well as the desktop environment and its > version.. my System : Tumbleweed kdebase4-workspace-4.8.5-2.10.1.i586 _________________ Gimp. ksnapshot, and ktorrent have recently been having problems : Maximum number of clients reached : cannot connect to X server :0 - when starting at konsole , errors like this appear : << KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work Maximum number of clients reachedktorrent: cannot connect to X server :0 unnamed app(8809): Communication problem with "ktorrent" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " >> ............................. # killall firefox command seems to bring things back to normal - could this be a trouble of Firefox 16.0.2 ?? best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] today's update broke 12.3 m0
by Cristian Rodríguez 04 Nov '12

04 Nov '12

On Sun, Nov 4, 2012 at 12:57 AM, Alin Marin Elena <alinm.elena(a)gmail.com> wrote: > the only failure i have is this... > [root@abbaton:/home/alin]: systemctl status irqbalance.service Uninstall package irqbalance, unless you have a machine with hundreds of cores it is useless. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

Re: [opensuse-factory] today's update broke 12.3 m0
by Alin Marin Elena 04 Nov '12

04 Nov '12

---------- Forwarded message ---------- From: Alin Marin Elena <alinm.elena(a)gmail.com> Date: 4 November 2012 00:57 Subject: Re: [opensuse-factory] today's update broke 12.3 m0 To: Cristian Rodríguez <crrodriguez(a)opensuse.org> On 4 November 2012 00:44, Cristian Rodríguez <crrodriguez(a)opensuse.org> wrote: >> There are still some minor issues with the installation (missing syslog), but >> the system should at least be working and usable. > > I am looking into the fallout.. now if someone checks the packages in > I will be happy ;) > -- > To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org > the only failure i have is this... [root@abbaton:/home/alin]: systemctl status irqbalance.service irqbalance.service - irqbalance daemon Loaded: loaded (/lib/systemd/system/irqbalance.service; enabled) Active: failed (Result: resources) CGroup: name=systemd:/system/irqbalance.service Nov 03 20:39:13 linux.site systemd[1]: Starting irqbalance daemon... Nov 03 20:39:13 linux.site systemd[1]: Failed to load environment files: No such file or directory Nov 03 20:39:13 linux.site systemd[1]: Failed to start irqbalance daemon. Nov 03 20:39:13 linux.site systemd[1]: Unit irqbalance.service entered failed state [root@abbaton:/home/alin]: cat /lib/systemd/system/irqbalance.service [Unit] Description=irqbalance daemon After=syslog.target [Service] EnvironmentFile=/path/to/irqbalance.env ExecStart=/usr/sbin/irqbalance --foreground $IRQBALANCE_ARGS [Install] WantedBy=multi-user.target probably related to this systemctl status syslog.service syslog.service - System Logging Service Loaded: error (Reason: No such file or directory) Active: inactive (dead) A -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Firefox 16.0.2
by ellanios82 03 Nov '12

03 Nov '12

Hello List Gimp. ksnapshot, and ktorrent have recently been having problems : Maximum number of clients reached : cannot connect to X server :0 - when starting at konsole , errors like this appear : << KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work Maximum number of clients reachedktorrent: cannot connect to X server :0 unnamed app(8809): Communication problem with "ktorrent" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " >> ............................. # killall firefox command seems to bring things back to normal - could this be a trouble of Firefox 16.0.2 ?? best regards Ellan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] an error generating the initrd with kernel 3.6.rc7-1.1
by constant＠indo.net.id 03 Nov '12

03 Nov '12

After the todays update, I got the following information and the downloaded kernel -3.6.rc7-1.1 is not properly installed. Had a look in /boot and found that the previous kernel was not yet deleted.Did I do something wrong? Is my system missing something? ______________ Installing: kernel-default-3.6.rc7-1.1 ...........................................................................................[done] Additional rpm output: Kernel image: /boot/vmlinuz-3.6.0-rc7-1-default Initrd image: /boot/initrd-3.6.0-rc7-1-default Kernel Modules: <not available> Could not find map /boot/System.map, please specify a correct file with -M. There was an error generating the initrd (9) Installing: kernel-desktop-3.6.rc7-1.1 ...........................................................................................[done] Additional rpm output: Kernel image: /boot/vmlinuz-3.6.0-rc7-1-desktop Initrd image: /boot/initrd-3.6.0-rc7-1-desktop Kernel Modules: <not available> Could not find map /boot/System.map, please specify a correct file with -M. There was an error generating the initrd (9) Installing: xtables-addons-kmp-default-1.46_k3.6.0_rc7_1-1.3 .....................................................................[done] Additional rpm output: Kernel image: /boot/vmlinuz-3.6.0-rc7-1-default Initrd image: /boot/initrd-3.6.0-rc7-1-default Kernel Modules: <not available> Could not find map /boot/System.map, please specify a correct file with -M. There was an error generating the initrd (9) warning: %post(xtables-addons-kmp-default-1.46_k3.6.0_rc7_1-1.3.i586)scriptlet failed, exit status 1 Installing: xtables-addons-kmp-desktop-1.46_k3.6.0_rc7_1-1.3 ..................................................................<100%>[/]Installing:xtables-addons-kmp-desktop-1.46_k3.6.0_rc7_1-1.3 .....................................................................[done] Additional rpm output: Kernel image: /boot/vmlinuz-3.6.0-rc7-1-desktop Initrd image: /boot/initrd-3.6.0-rc7-1-desktop Kernel Modules: <not available> Could not find map /boot/System.map, please specify a correct file with -M. There was an error generating the initrd (9) warning: %post(xtables-addons-kmp-desktop-1.46_k3.6.0_rc7_1-1.3.i586)scriptlet failed, exit status 1 -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.3 Milestone 0 (i586) Kernel: 3.6.0-1-desktopKDE Development Platform: 4.9.2) 13:46pm up 2:18, 3 users, load average: 1.11, 1.99, 1.88 ___________________________________________________________ indomail - Your everyday mail - http://indomail.indo.net.id -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] Updating of 'filesystem' package (to 12.3-3.1) fails
by Patrick Shanahan 03 Nov '12

03 Nov '12

* Sid Boyce <sboyce(a)blueyonder.co.uk> [11-02-12 19:20]: > It's back again > Installation of filesystem-12.3-7.1 failed: > (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: > unpacking of archive failed on file /var/lock: cpio: rename failed - Is a > directory > error: filesystem-12.3-7.1.x86_64: install failed > error: filesystem-12.3-6.1.x86_64: erase skipped > > > Abort, retry, ignore? [a/r/i] (a): r > Installing: filesystem-12.3-7.1 ........................................................................................................................................................................................................................................[error] > Installation of filesystem-12.3-7.1 failed: > (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: > unpacking of archive failed on file /var/lock: cpio: rename failed - Is a > directory > error: filesystem-12.3-7.1.x86_64: install failed > error: filesystem-12.3-6.1.x86_64: erase skipped > > > Abort, retry, ignore? [a/r/i] (a): i I see the same: Computing upgrade... The following NEW package is going to be installed: bundle-lang-common-ko 12.2-5.5 The following package is going to be upgraded: filesystem 12.3-6.1 -> 12.3-7.1 1 package to upgrade, 1 new. Overall download size: 291.7 KiB. After the operation, additional 969.6 KiB will be used. Continue? [y/n/?] (y): committing Retrieving package bundle-lang-common-ko-12.2-5.5.noarch (1/2), 224.3 KiB (969.6 KiB unpacked) Retrieving: media ................................................................................................................[done] Retrieving: bundle-lang-common-ko-12.2-5.5.noarch.rpm ..............................................................[done (257.7 KiB/s)] Installing: filesystem-12.3-7.1 .................................................................................................[error] Installation of filesystem-12.3-7.1 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /var/lock: cpio: rename failed - Is a directory error: filesystem-12.3-7.1.x86_64: install failed error: filesystem-12.3-6.1.x86_64: erase skipped Abort, retry, ignore? [a/r/i] (a): Problem occured during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. Checking for running processes using deleted libraries... And I have no idea why zypper wants to install bundle-lang-common-ko, not my doing. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Fwd: [opensuse-factory] mkinitrd or dracut ?
by Marguerite Su 02 Nov '12

02 Nov '12

+1 for dracut! I knew it and tried it after the release of the well known 2sec boot lizard post, Although it speeds your boot just a little bit mesured by systemd plot, it gave you an illusion that it is roket science because it postpones the start of plymouth and just quickly blank twice before you get a KDM. And I am happy to get rid of mdam,multipath,mdraid from my initd without removing half of yast thanks to dracut's module system. I even wrote a long wiki at zh.opensuse.org/sdb:dracut (I am a little busy these days, so no time to translate it into English) I think one shortcoming of change to dracutb is, it lacks documentation. You never know the meaning of every module. You never know which ones are included by default and which ones are not. So it makes the official tweak methods like adding module or masking module useless. Marguerite // sorry to forget cc factory...it was sent from android which always don't reply all. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 8

[opensuse-factory] Any reason libreoffice is taking a long time to build in factory
by doiggl＠velocitynet.com.au 02 Nov '12

02 Nov '12

Hello, Any reason libreoffice is taking a long time to build in factory [1] - Glenn [1] https://build.opensuse.org/package/show?package=libreoffice&project=LibreOf… https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libre… >From the log: [34353s] [ build CXX ] sw/source/ui/misc/glshell.cxx [34356s] [ build CXX ] sw/source/ui/misc/numberingtypelistbox.cxx [34363s] [ build CXX ] sw/source/ui/misc/redlndlg.cxx [34365s] [ build CXX ] sw/source/ui/ribbar/conarc.cxx [34367s] [ build CXX ] sw/source/ui/ribbar/concustomshape.cxx -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] NO initrd-3.6.0-1-desktop file from openSUSE-KDE-LiveCD-x86_64-Build0135-Media.iso
by doiggl＠velocitynet.com.au 02 Nov '12

02 Nov '12

Hello, After installation from openSUSE-KDE-LiveCD-x86_64-Build0135-Media.iso it does NOT boot at all from the hard disk. Question: It seems I have NO initrd-3.6.0-1-desktop file installed , How can I install it [to the hard disk] from the livecd install process?. Thanks Glenn Content of following are listed. [1] grub.conf [2] device.map [3] menu.lst [1]/etc/grub.conf setup --stage2=/boot/grub/stage2 --force-lba (hd0,1) (hd0,1) quit [2] /boot/grub/device.map (hd0) /dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767 [3] /boot/grub/menu.lst # Modified by YaST2. Last modification on Wed Oct 31 17:12:33 EST 2012 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader default 0 timeout 8 gfxmenu (hd0,1)/boot/message ##YaST - activate terminal gfxterm ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 12.3 root (hd0,1) kernel /boot/vmlinuz-3.6.0-1-desktop root=/dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767-part2 resume=/dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767-part4 splash=silent quiet showopts initrd /boot/initrd-3.6.0-1-desktop ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: hard_disk### title Hard Disk rootnoverify (hd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.3 root (hd0,1) kernel /boot/vmlinuz-3.6.0-1-desktop root=/dev/disk/by-id/ata-CRUCIAL_CT64M225_P609410-MIBY-124A767-part2 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe initrd /boot/initrd-3.6.0-1-desktop [4]file listing # ll boot total 14297 -rw-r--r-- 1 root root 2557685 Oct 11 10:13 System.map-3.6.0-1-desktop -rw------- 1 root root 512 Oct 31 06:12 backup_mbr lrwxrwxrwx 1 root root 1 Oct 30 01:41 boot -> . -rw-r--r-- 1 root root 1236 Oct 23 17:53 boot.readme -rw-r--r-- 1 root root 135368 Oct 11 09:00 config-3.6.0-1-desktop -rw-r--r-- 1 root root 0 Oct 30 01:39 do_purge_kernels drwxr-xr-x 2 root root 568 Oct 31 06:12 grub drwxr-xr-x 3 root root 72 Oct 30 01:42 grub2 lrwxrwxrwx 1 root root 22 Oct 30 01:39 initrd -> initrd-3.6.0-1-desktop -rw-r--r-- 1 root root 176760 Oct 8 06:16 memtest.bin -rw-r--r-- 1 root root 581632 Oct 31 06:12 message -rw-r--r-- 1 root root 235526 Oct 11 10:28 symvers-3.6.0-1-desktop.gz -rw-r--r-- 1 root root 520 Oct 11 10:28 sysctl.conf-3.6.0-1-desktop -rw-r--r-- 1 root root 5866801 Oct 11 10:27 vmlinux-3.6.0-1-desktop.gz lrwxrwxrwx 1 root root 23 Oct 30 01:39 vmlinuz -> vmlinuz-3.6.0-1-desktop -rw-r--r-- 1 root root 5044848 Oct 11 10:13 vmlinuz-3.6.0-1-desktop # ll initrd-3.6.0-1-desktop ls: cannot access initrd-3.6.0-1-desktop: No such file or directory # find . | grep -i initrd-3.6.0-1-desktop # -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Complain about conditional used run_permissions macro
by Lars Müller 01 Nov '12

01 Nov '12

Hi, we're using %{?run_permissions:%{run_permissions}} in the post scriptlet of the samba-krb-printing package. While building for opensuse-factory we get this warning [ 1762s] WARNING: run_permissions is obsolete and will be removed january 2013 As we execute %{run_permissions} only if it is defined all looks good from our side. Therefore we consider to simply ignore the warning. But I fear we'll come to the point where the package sources will not get accepted for openSUSE Factory. Our goal is to use the same spec file also for older products like SUSE Linux Enterprise 10 and 11. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

3 2

[opensuse-factory] Re: [opensuse] Support and repairtools: A laughing stock! (was:Unnecessary Packages in Yast: Can they be removed without consequence?)
by Oddball 01 Nov '12

01 Nov '12

Op 01-11-12 09:53, Oddball schreef: > Op 01-11-12 09:34, Hans Witvliet schreef: >> On Wed, 2012-10-31 at 23:53 +0100, Oddball wrote: >> >>> The other thing is a mistake i made: i never use lvm. >>> This time i thought ok, lets try it. >>> Lvm is not supported yet in Knoppix, so the partitions could not get >>> mounted, only windows and /boot were visible. >>> >> Instead of kroppix, >> you can use either the KDE-live-cd, or the install-12.2-DVD and choose >> "live-KDE". LVM and soft raid are recognized there... >> And do the repair work hence on. > > That is an opportunity, but it is the question if it would boot at all. > Install the bootloader and mkinitrd might be done if the system is > mounted... > I think new install will be better. > Maybe keep /home, and lvm for now, or use kde to transfer /home to an > external hdd, and get rid of lvm. > Nope, lvm is not recognised there... And this was the first and last time i was ever gonna use it. So backing up my files is not an option. I think some serious rethinking should be done about what is the aim on opensuse? Create an os that is useless always broken but looks sometimes shiny? Or a system that uses only tools that work, and that are supported? A repair kit that is usable?, or just something that looks like it, but it is not even good enough to wipe your ass with? (difficult with a laptop or pc i agree.. :-D) I think, if opensuse continous, to go on, on this road, the userbase will shrink further. What is the use of an update tool, if the system is broken? First :1) repair the system, 2) support it, and 3) create a working repairkit, so people who test, do not have use their valuable time on re-installing their system. This is the formula for openSUSE 123. -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3