August 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] [tumbleweed] aaa_base/insserv: syntax error
by Melchior FRANZ 22 Aug '11

22 Aug '11

Just made a "zypper dup" and got this: Installing: aaa_base-12.1-107.1 [done] Additional rpm output: insserv: Note: sysvinit service boot.cleanup is shadowed by systemd cleanup.service, Forwarding request to '/bin/systemctl --root (null) enable cleanup.service'. sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `/bin/systemctl --root (null) enable cleanup.service' insserv: Forward service request to systemctl returned error status : 256 insserv: Note: sysvinit service boot.rootfsck is shadowed by systemd rootfsck.service, Forwarding request to '/bin/systemctl --root (null) enable rootfsck.service'. sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `/bin/systemctl --root (null) enable rootfsck.service' insserv: Forward service request to systemctl returned error status : 256 Updating /etc/sysconfig/language... m. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 5

[opensuse-factory] Fwd: [apparmor] AppArmor 2.7-beta1
by Christian Boltz 22 Aug '11

22 Aug '11

Hello, AppArmor 2.7 beta1 has been released and contains various bugfixes, for example a working ;-) aa-notify and systemd support. (See release announcement at the end of this mail and http://wiki.apparmor.net/index.php/ReleaseNotes_2_7 for details) Jeff, can you please update the package in Factory? As you know, I commited many patches upstream. The following patches are in 2.7 beta1 and can be removed from the openSUSE package: apparmor-2.5.1-ntpd-sys_nice apparmor-2.5.1-ssl-fix apparmor-2.6.0-dhcpd apparmor-compat-routines apparmor-profiles-cupsd-fix apparmor-profiles-dhclient apparmor-profiles-sshd-fix (enhanced version with additional fixes) apparmor-profiles-syslog-ng-fix apparmor-profiles-usr.sbin.dnsmasq apparmor-scripts apparmor-securityfs-systemd.patch apparmor-startproc.patch apparmor-utils-add-log-types apparmor-utils-filenames-in-slash genprof-whitespace-in-profile-fix klog-needs-CAP_SYSLOG apparmor-remove-repo was implemented upstream in a different way and can most probably be removed. Some of your patches that were "hidden" in the 11.4:Update package (but not in the Factory package) did not make it into 2.7 beta1: - apparmor-profiles-dovecot (updated version that applies cleanly is attached, but the new link permissions are still discussed upstream) - apparmor-profiles-samba (updated version attached, with an additional fix for bnc#679182#c8) - apparmor-profiles-traceroute (still applies) Please include these patches in the Factory package. apparmor-2.5.1-ldapclient-profile and apparmor-2.5.1-edirectory-profile are waiting for an answer from you on the AppArmor mailinglist (see Steve's mail from 2011-08-08, "openSUSE profile patches - part 1"). The apparmor-utils-string-split patch wasn't liked too much because it would hardcode the line length into the translations. Kees thinks that the wrapping should be done by the code displaying the message. (Feel free to discuss this on the AppArmor mailinglist.) Some patches are intentionally not upstreamed. For example, apparmor-utils-subdomain-compat should stay openSUSE-only and be removed when it's no longer needed for YaST. I have also attached "osc-diff" that adds some notes to the remaining patches. It should apply to security:apparmor:factory without problems. That all said, here's the upstream release announcement: ---------- Weitergeleitete Nachricht ---------- Betreff: [apparmor] AppArmor 2.7-beta1 Datum: Samstag, 20. August 2011 02:25 Von: John Johansen <john.johansen(a)canonical.com> An: apparmor <apparmor(a)lists.ubuntu.com> The AppArmor development team is pleased to announce the 2.7-beta1 of the AppArmor user space components. This release is an incremental improvement over the AppArmor 2.6.2 release, focusing on fixing bugs in the userspace code. The release is available from http://launchpad.net/apparmor/2.7/2.7.beta1/+download/apparmor-2.7.0~beta1.… or http://kernel.org/pub/linux/security/apparmor/AppArmor-2.7/apparmor-2.7.0~b… and has the following md5sum 1f543d99868d640b1c4574ee33493087 A detached gnupg signature is available at http://launchpad.net/apparmor/2.7/2.7.beta1/+download/apparmor-2.7.0~beta1.… which should indicate it was signed with the john johansen's signing key having the fingerprint D926 7844 5CD9 BFA5 6C74 EC8E C405 7122 C10A 23E6 The release notes for the 2.7-beta1 release are available at http://wiki.apparmor.net/index.php/ReleaseNotes_2_7 Please report any bugs you may find via the Launchpad AppArmor project on Launchpad at https://launchpad.net/apparmor/ . Thanks! -- John Johansen <john.johansen(a)canonical.com> -- AppArmor mailing list AppArmor(a)lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor ------------------------------------------------------- Regards, Christian Boltz -- Zu meiner Entschuldigung: Ich konnte es nicht nochmal durchlesen, weil meine Kippenschachtel leer war und ich also schnell das Haus verlassen musste. Das neue Jahr - keine 11 Tage alt und die (guten) Vorsätze schon alle über Bord.... [Rüdiger Meier in suse-linux]

2 3

[opensuse-factory] Well known /var/log/boot.msg even with systemd
by Dr. Werner Fink 22 Aug '11

22 Aug '11

Hi, during debugging I've missed the /var/log/boot.msg therefore I've written a replacment for /etc/init.d/boot.klog as well as for the current symbolic link /lib/systemd/system/klog.service which currently points forward to /dev/null. I'd like to suppose the attached replacment for this link. With this service file the well known /var/log/boot.msg will be created. By using dmesg(1) the normal kernel and boot messages handled by systemd will not disappear. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr

2 3

[opensuse-factory] no menu.lst write on kernel installation
by Felix Miata 21 Aug '11

21 Aug '11

Today I did a 32 bit zypper dup from Factory repos with kernel locked, then rebooted, then did zypper in kernel-desktop. I recall seeing an error message similar to expected end of file. A usable initrd was generated, but menu.lst was untouched after the kernel installation. Does this look the same as https://bugzilla.novell.com/show_bug.cgi?id=713041 mkinitrd-2.7.0-26.4@x86_64 -sh: -c: line 0: syntax error near unexpected token `(' ? Anyone else have this happen lately? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] How to find reasons for osc build failure
by Larry Finger 21 Aug '11

21 Aug '11

I'm updating the code for b43-fwcutter. I have checked out the package, made the changes, and get no errors for 'osc build'. When I use 'osc commit', the results are all "failed". What to I do to get the reason for that failure? Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] nothing provides python-gobject2-devel
by Ilya Chernykh 21 Aug '11

21 Aug '11

What is instead? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] windows dynamic partitionning
by jdd 21 Aug '11

21 Aug '11

Hello, I just discover this windows special partionning. https://bugzilla.novell.com/show_bug.cgi?id=713325 is there a strategy to cope with this at install time (other than removing completly windows)? I will also ask the parted list thanks jdd -- http://www.dodin.net http://www.youtube.com/user/jdddodinorg http://jdd.blip.tv/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] [Tumbleweed] Possibly a udev bug.
by Manu Gupta 21 Aug '11

21 Aug '11

Hi All A few days back I posted about my atheros card. Ref http://lists.opensuse.org/opensuse-factory/2011-08/msg00293.html It seems that it is a udev issue. At boot time I get a message udev[211]: /etc/sysconfig/networks/scripts/ifup-sysctl not fount /etc/sysconfig/networks/scripts/ifup-sysctl -lo hotplug not executable The error is some what like this. I did not where I can find the udev boot log so I am writing whatever I could remember. Should I open a bug for it and if so against which component should I open it for openSUSE 11.4 or 12.1 -- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] glibc 2.14 coming to Factory
by Andreas Jaeger 20 Aug '11

20 Aug '11

I've submitted yesterday glibc 2.14 to Base:System and was surprised that all packages build fine there. The most significant change in glibc 2.14 was the disabling of the sunrpc code - and I had reverted this change since libtirpc is not a full replacement for sunrpc yet. libtirpc works for many applications but I could not get others working. The NEWS file for 2.14 reads. Our glibc has additional bug fixes * The following bugs are resolved with this release: 386, 6420, 7101, 9730, 9732, 9809, 10138, 10149, 10157, 11099, 11257, 11258, 11487, 11532, 11558, 11578, 11634, 11653, 11668, 11697, 11724, 11781, 11799, 11820, 11837, 11857, 11869, 11892, 11895, 11901, 11945, 11947, 11952, 11987, 12052, 12083, 12158, 12178, 12200, 12346, 12350, 12393, 12420, 12432, 12445, 12449, 12453, 12454, 12460, 12469, 12489, 12509, 12510, 12511, 12518, 12527, 12541, 12545, 12551, 12582, 12583, 12587, 12597, 12601, 12611, 12625, 12626, 12631, 12650, 12653, 12655, 12660, 12671, 12681, 12684, 12685, 12711, 12713, 12714, 12717, 12723, 12724, 12734, 12738, 12746, 12766, 12775, 12777, 12782, 12788, 12792, 12795, 12811, 12813, 12814, 12841 * New Linux interfaces: clock_adjtime, name_to_handle_at, open_by_handle_at, syncfs, setns, sendmmsg * New locales: os_RU, bem_ZA, en_ZA, ff_SN, sw_KE, sw_TZ, lb_LU, wae_CH, yue_HK, lij_IT, mhr_RU * New encodings: CP770, CP771, CP772, CP773, CP774 * New program sotruss to trace calls through PLTs Implemented by Ulrich Drepper. * The malloc hook implementation is marked deprecated and will be removed from the default implementation in the next version. The design never worked ever since the introduction of threads. Even programs which do not create threads themselves can use multiple threads created internally. I don't expect any program breakage but if you notice some, tell me, please! Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 4

[opensuse-factory] IPv6 (privacy) in openSUSE
by Freek de Kruijf 20 Aug '11

20 Aug '11

Ludwig Nussel wrote on Fri, 14 Jan 2011 13:41:27 +0100, > > Andreas Jaeger wrote: > > > > So, my proposal is to do the following two changes: > > * Use 2 instead of 1 in /etc/rc.d/boot.ipconfig for enabling the privacy > > extensions > > * Set IPV6_PRIVACY=yes in /etc/sysconfig/sysctl > > > If at all leave IPV6_PRIVACY empty by default and assume 2 in that > case in boot.ipconfig. However, I'd rather suggest to drop > boot.ipconfig completely and have the kernel itself start with a > sane default value. About a month ago I got a new modem from my ISP which offers native IPv6. After a lot of experimenting I have the following recommendations. The default for the dynamic IP address should not be DHCP both 4 and 6, but DHCP version 4 only. The reason is that most likely an IPv6 router will not have support for DHCP6, mine does not offer a DHCP6 service. It means that enabling IPv6 by default relies on Stateless Address Autoconfiguration (SAA), which is a perfect choice. When there is no DHCP6 server available and the address of an interface depends on SAA it takes up to 10 minutes before the interface gets its global IPv6 address. Disabling DHCP6 in this case provides the address in 2 seconds. The subject of privacy in IPv6 is only relevant when you use a mobile device. For a rather static device or privacy is no concern, the above method is sufficient or rather required. In Linux the host part of the IPv6 address, the lower 64 bits, is always the same; it is derived from the MAC address of the interface, but in the very unlikely case of duplication, this will be prevented, because the IPv6 protocol always checks for duplicated addresses. So in case one wants to communicate between devices using IPv6, this is possible. One could set these more or less static addresses in the /etc/hosts file or manually introduce them in a DNS server. So in the case of a privacy concern in a mobile device, one has to set IPV6_PRIVACY=yes. This means that the host part of the IPv6 address will be generated randomly after which a check for a duplicated address will be made. This host part will even be regenerated after 24 hours, if the device is active that long. When a DHCP6 server is present in the network, and a dynamic address is required, one has to enable DHCP both for version 4 and 6, but this should not be a default setting. Also in this case SAA is still available and should work. Using DHCP6 is called Stateful Address Autoconfiguration In case of a static IPv6 address, some more information should be provided in the Help about how and what to do. In that case one has to set the IPv6 address of the default gateway. However this could be avoided by searching for this address when the network starts. Currently this is not done. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 14