April 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 872250] New: metamail (and munpack) fails to recognize filename of attachments from MS-multipart/alternative
by bugzilla_noreply＠novell.com 05 Apr '14

05 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=872250 https://bugzilla.novell.com/show_bug.cgi?id=872250#c0 Summary: metamail (and munpack) fails to recognize filename of attachments from MS-multipart/alternative Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: SLES 11 Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software AssignedTo: opensuse-communityscreening(a)forge.provo.novell.com ReportedBy: guenther.pommer(a)tkl.at QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=585237) --> (http://bugzilla.novell.com/attachment.cgi?id=585237) contains patch and example to reproduce / verify the problem User-Agent: Mozilla/5.0 (X11; Linux i686; rv:27.0) Gecko/20100101 Firefox/27.0 Short story for explanation ahead, will give my intention below. On our SLES11 I've tried to automize the extraction of mail-attachments and found, that the attachment's name is not recognized on certain mails from some broken mailer (M$), that leaves away the "name=" parameter, if it is a multipart/alternative mail with attached "Content-Type: application/vnd.ms-excel" - but at least the "filename=" parameter is provided in the "Content-Disposition:" tag - but unfortunately metamail does not use the later. Then I tried munpack (source mpack-1.6-2.1.src.rpm) from OpenSuSE build service, but the result was the same. I had a look into the source and found, that in cases where an e-mail-message did not contain a "name=" parameter with it's "Content-Type:" tag, then munpack was not able to pick the (existing) "filename=" parameter from the "Content-Disposition:" tag either, because of just a tiny lapsus (see patch-lines below). As a solution, I appended the lines below, to the patch-file "mpack-1.6.diff", which is shipped with the package "mpack-1.6-2.1.src.rpm" (from OpenSuse build service). After running rpmbuild again, munpack would use the attachment's given filename instead of generated names like "part1". #======= appended the following lines to "mpack-1.6.diff" =============== diff -ubrN mpack-1.6/decode.c mpack-1.6-1/decode.c --- mpack-1.6/decode.c.old 2014-04-04 23:54:57.000000000 +0200 +++ mpack-1.6/decode.c 2014-04-04 23:55:13.000000000 +0200 @@ -546,8 +546,8 @@ SkipWhitespace(&disposition); if (!disposition) return 0; - /* If we're looking at a ";", we found what we're looking for */ - if (*disposition++ == ';') break; + /* If we're NOT looking at a ";", we found what we're looking for */ + if (*disposition++ != ';') break; } SkipWhitespace(&disposition); Additional change: For overwrite protection, munpack was using a numeric count as file-name suffix, which distorts file-extensions (.xls1, .csv2,...) and confuses M$-office. So I also added the following patch, that changes the suffix to a prefix, thus leaves the file-extension recognizeable. #======= appended the following lines to "mpack-1.6.diff" =============== diff -ubrN mpack-1.6/unixos.c.old mpack-1.6/unixos.c --- mpack-1.6/unixos.c.ori 2014-04-05 13:49:57.000000000 +0200 +++ mpack-1.6/unixos.c 2014-04-05 13:59:26.000000000 +0200 @@ -163,7 +163,7 @@ FILE *os_newtypedfile(char *fname, char *contentType, int flags, params contentParams) { char *p; - static int filesuffix=0; + static int filesuffix=0, fileprefix=0 ;; char buf[128], *descfname=0; FILE *outfile = 0; @@ -203,7 +203,7 @@ else if (!overwrite_files && (outfile = fopen(fname, "r"))) { do { fclose(outfile); - sprintf(buf, "%s.%d", fname, ++filesuffix); + sprintf(buf, "%d-%s", ++fileprefix, fname); } while (outfile = fopen(buf, "r")); fname = buf; These slight modifications make munpack ways more practical for non interactive usage. So for now my problem is solved, but here's my intention: Is there any chance, to get this tool shipped with SLES one day ? Thanks in advance kind regards Günther Pommer ( guenther.pommer(a)tkl.at ) Attachment: unpack-modification.tar.gz containing: mail.raw - the problematic raw-mail to re-produce "my" problem mpack-1.6.diff - patch-file including all previous and new changes chk_att_name - temporary perl-workaround, while still using metamail bug-report.txt - again Reproducible: Always Steps to Reproduce: reproducible with the example mail-body in the attachment Actual Results: see bug-report.txt -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 852024] New: virt-manager cpu settings window does not fit on screen
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=852024 https://bugzilla.novell.com/show_bug.cgi?id=852024#c0 Summary: virt-manager cpu settings window does not fit on screen Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KVM AssignedTo: kvm-bugs(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: jdouglas(a)suse.com Found By: Outsourced Testing Blocker: --- Created an attachment (id=568844) --> (http://bugzilla.novell.com/attachment.cgi?id=568844) Screenshot from 2013-11-24 20:49:24.png 13.1 virt-manager even with a large display, the cpu settings with all settings expanded does not fit on screen to also show the cancel/ok buttongs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 872202] New: susestudio live image does not work on kernel tree 3.14
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=872202 https://bugzilla.novell.com/show_bug.cgi?id=872202#c0 Summary: susestudio live image does not work on kernel tree 3.14 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: bgerz(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:28.0) Gecko/20100101 Firefox/28.0 I´m allways testing the newest kernela on live images in susestudio. In the past all kernels include version 3.13.7 did work(on opensuse 12.3 and 13.1) but beginning with 3.14RC it didn`t. Now we have a stable kernel 3.14 and it`s also not running. After starting it on susestudio testdrive I get messages like Can`t mount root fs rw Reboot exception: reboot in 120 seconds I think it`s a problem of missing overlay fs modules for live systems. Reproducible: Always Actual Results: Kernels from http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ http://download.opensuse.org/repositories/Kernel:/stable/standard/ do not work on susestudio livecd images. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 828859] New: AutoYaST documentation regarding "Printer" is outdated for openSUSE
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=828859 https://bugzilla.novell.com/show_bug.cgi?id=828859#c0 Summary: AutoYaST documentation regarding "Printer" is outdated for openSUSE Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: All OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)suse.com ReportedBy: jsmeix(a)suse.com QAContact: ke(a)suse.com CC: rsalevsky(a)suse.com Found By: Development Blocker: --- Rick Salevsky found the following documentaion: http://doc.opensuse.org/projects/autoyast/configuration.html I don't know for what exact openSUSE version that documentation is nor do I know from what sources that documentation is generated. Therein section "4.21.1 Printer" contains mostly the right text except some minor adjustments. I will attach later a corrected text for current openSUSE versions. But below the "Example 4.37: Printer configuration" is plain wrong for current openSUSE versions. It is the outdated XML that was valid for SLE11 which is no longer valid since something like openSUSE 11.3 when I made the AutoYaST "Printer" stuff completely anew, (see bnc#588679 and bnc#582680 if you like all details ;-) Regarding "the new AutoYaST control file structure" see https://bugzilla.novell.com/show_bug.cgi?id=588679#c10 ----------------------------------------------------------- <printer> <client_conf_content> <file_contents><![CDATA[ .. verbatim content of /etc/cups/client.conf ... ]]></file_contents> </client_conf_content> <cupsd_conf_content> <file_contents><![CDATA[ .. verbatim content of /etc/cups/cupsd.conf ... ]]></file_contents> </cupsd_conf_content> </printer> ----------------------------------------------------------- Therefore the "Example 4.37: Printer configuration" should be exchanged by "the new AutoYaST control file structure" above. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 862182] New: Dynamic DNS Updates from DHCP doesn't work anymore since last patch.. & manual DNS Updates were not saved
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=862182 https://bugzilla.novell.com/show_bug.cgi?id=862182#c0 Summary: Dynamic DNS Updates from DHCP doesn't work anymore since last patch.. & manual DNS Updates were not saved Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: franzmatthies(a)arcor.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 systemd[1]: Reloading LSB: Domain Name System (DNS) server, named. named[12439]: Reloading name server BIND tput: No value for $TERM and no -T specified named[12439]: Error: tput: No value for $TERM and no -T specified named[12439]: Can not find /lib/YaST/SuSEconfig.functions! named[12439]: This should not happen. Exiting. named[12439]: server reload successful named[12439]: ..done Reproducible: Always Steps to Reproduce: 1.open yast2 dns-server 2.open a forward-lookup zone 3.edit the entrys, add a new one or delete one 4.save and exit Actual Results: 1.cat /var/lib/named/dyn/"FORWARD-LOOKUP-ZONE" 2.no changes where happend 3.look in to the last rows from /var/log/messages to see the posted message. Expected Results: It have to perform the changes, and add or delete entry in the bind database. I tried this on mutiple systems, everytime the same. At one system DynamicDNS with DHCP worked, the I do the last updates, "zypper update". After this I got the same mistake like everywhere. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 805421] New: calibre 0.9.20-120.1 install fails, cpio: is a directory
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=805421 https://bugzilla.novell.com/show_bug.cgi?id=805421#c0 Summary: calibre 0.9.20-120.1 install fails, cpio: is a directory Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pat(a)indy.rr.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Installation of calibre-0.9.20-120.1 failed: Installing: calibre-0.9.20-120.1 .................................[error] Installation of calibre-0.9.20-120.1 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: /etc/bash_completion.d/calibre saved as /etc/bash_completion.d/calibre.rpmsave error: unpacking of archive failed on file /usr/share/calibre/fonts/liberation: cpio: rename failed - Is a directory error: calibre-0.9.20-120.1.x86_64: install failed error: calibre-0.9.20-15.1.x86_64: erase skipped Reproducible: Always Steps to Reproduce: 1.zypper -v in calibre-0.9.20-120.1.x86_64.rpm 2. 3. Actual Results: Installing: calibre-0.9.20-120.1 .....................................[error] Installation of calibre-0.9.20-120.1 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: /etc/bash_completion.d/calibre saved as /etc/bash_completion.d/calibre.rpmsave error: unpacking of archive failed on file /usr/share/calibre/fonts/liberation: cpio: rename failed - Is a directory error: calibre-0.9.20-120.1.x86_64: install failed error: calibre-0.9.20-15.1.x86_64: erase skipped Expected Results: complete install -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 835993] New: kernel error msg: No irq handler for vector (irq -1)
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=835993 https://bugzilla.novell.com/show_bug.cgi?id=835993#c0 Summary: kernel error msg: No irq handler for vector (irq -1) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: pat(a)indy.rr.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=553599) --> (http://bugzilla.novell.com/attachment.cgi?id=553599) output from hwinfo --all User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 Third time in last 2 days: Message from syslogd@Crash at Aug 21 14:53:29 ... kernel:[150387.099045] do_IRQ: 5.41 No irq handler for vector (irq -1) kernel-desktop-3.10.7-23.2.g771dec3.x86_64 Reproducible: Always Steps to Reproduce: 1.sit and wait 2. 3. Actual Results: Message from syslogd@Crash at Aug 21 14:53:29 ... kernel:[150387.099045] do_IRQ: 5.41 No irq handler for vector (irq -1) Expected Results: no message Tumbleweed did not receive msg with kernel-desktop-3.10.7-23.1.g771dec3.x86_64 which is three days older -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 862076] New: use_lvmetad = 1 in lvm.conf triggers systemd to get into emergency target on boot
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=862076 https://bugzilla.novell.com/show_bug.cgi?id=862076#c0 Summary: use_lvmetad = 1 in lvm.conf triggers systemd to get into emergency target on boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: thomas.blume(a)suse.com ReportedBy: thomas.blume(a)suse.com QAContact: qa-bugs(a)suse.de CC: systemd-maintainers(a)suse.de Found By: Development Services Priority: 1000 Blocker: --- lvm2-2.02.98-0.28.5.1.x86_64 introduced the following change in lvm.conf: - set use_lvmetad = 1 as default of lvm.conf(bnc#854413) This creates a failure on activating non-root lvm mounts. In my test system I'm using lvm devices for /home and /var: [ ***] (1 of 2) A start job is running for dev-nonroot-var.device [** ] (2 of 2) A start job is running for dev-mapper-nonroot\x2dhome.device systemd tries for a while to mount them, then times out and starts the emergency target: Job dev-nonroot-var.device/start finished, result=timeout [ TIME ] Timed out waiting for device dev-nonroot-var.device. Job var.mount/start finished, result=dependency [DEPEND] Dependency failed for /var. Job local-fs.target/start finished, result=dependency [DEPEND] Dependency failed for Local File Systems. Triggering OnFailure= dependencies of local-fs.target. Trying to enqueue job emergency.target/start/replace Installed new job emergency.target/start as 125 Installed new job emergency.service/start as 126 But the emergency target doesn't provide a shell either, it seems to loop somewhere. The reason why the start jobs fail, is apparently that lvmetad is not runnig. I've tried to enable it (it was disabled) via: systemctl enable lvm2-lvmetad.service but it didn't have any effect on the behaviour. As a workaround, one can mount system root via, e.g. the rescue system and set: use_lvmetad = 0 in lvm.conf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 56

[Bug 871873] New: squid[4116]: Error Directory /usr/share/squid/errors/English: (2) No such file or directory
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=871873 https://bugzilla.novell.com/show_bug.cgi?id=871873#c0 Summary: squid[4116]: Error Directory /usr/share/squid/errors/English: (2) No such file or directory Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mpluskal(a)suse.com QAContact: qa-bugs(a)suse.de CC: yast2-maintainers(a)suse.de Found By: --- Blocker: --- Created an attachment (id=584930) --> (http://bugzilla.novell.com/attachment.cgi?id=584930) y2logs When trying to configure squid via yast2 squid (current factory), error appears: /sbin/yast2: line 429: 3959 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS # systemctl status squid.service squid.service - Squid caching proxy Loaded: loaded (/usr/lib/systemd/system/squid.service; enabled) Active: failed (Result: exit-code) since Thu 2014-04-03 17:24:47 CEST; 40s ago Process: 4109 ExecStop=/usr/sbin/squid -F -f /etc/squid/squid.conf -k shutdown (code=exited, status=0/SUCCESS) Process: 4112 ExecStartPre=/bin/sh -c test -d "`sed -n 's/^cache_dir \+[[:alnum:]]\+ \+$[[:graph:]\/]\+$ .*/\1/p' /etc/squid/squid.conf | sed '1 q'`/00" || /usr/sbin/squid -z -F -N -S -f /etc/squid/squid.conf (code=exited, status=1/FAILURE) Main PID: 4051 Apr 03 17:24:47 theseus squid[4116]: Error Directory /usr/share/squid/errors/English: (2) No such file or directory Apr 03 17:24:47 theseus sh[4112]: 2014/04/03 17:24:47| ERROR: Error Directory /usr/share/squid/errors/English: (2) No such file or directory Apr 03 17:24:47 theseus sh[4112]: FATAL: Error Directory /usr/share/squid/errors/English: (2) No such file or directory Apr 03 17:24:47 theseus sh[4112]: Squid Cache (Version 3.4.4): Terminated abnormally. Apr 03 17:24:47 theseus sh[4112]: CPU Usage: 0.004 seconds = 0.004 user + 0.000 sys Apr 03 17:24:47 theseus sh[4112]: Maximum Resident Size: 25200 KB Apr 03 17:24:47 theseus sh[4112]: Page faults with physical i/o: 0 Apr 03 17:24:47 theseus systemd[1]: squid.service: control process exited, code=exited status=1 Apr 03 17:24:47 theseus systemd[1]: Failed to start Squid caching proxy. Apr 03 17:24:47 theseus systemd[1]: Unit squid.service entered failed state. from y2log: 2014-04-03 17:24:46 <1> theseus(3959) [Ruby] modules/Service.rb:502 Enabling service squid 2014-04-03 17:24:46 <3> theseus(3959) [bash] ShellCommand.cc(shellcommand):78 ln -s '/usr/lib/systemd/system/squid.service' '/etc/systemd/system/multi-user.target.wants/squid.service' 2014-04-03 17:24:47 <1> theseus(3959) [Ruby] modules/Service.rb:528 Restarting service squid 2014-04-03 17:24:47 <1> theseus(3959) [Ruby] modules/Service.rb:370 Running service initscript squid restart 2014-04-03 17:24:47 <3> theseus(3959) [bash] ShellCommand.cc(shellcommand):78 Job for squid.service failed. See 'systemctl status squid.service' and 'journalctl -xn' for details. 2014-04-03 17:24:47 <3> theseus(3959) [Ruby] modules/Service.rb:379 Error while running initscript /bin/systemctl restart squid.service : $["exit":1, "stderr":"Job for squid.service failed. See 'systemctl status squid.service' and 'journalctl -xn' for details.\n", "stdout":""] 2014-04-03 17:24:47 <3> theseus(3959) [Ruby] modules/Squid.rb:1430 Cannot restart 'squid' service 2014-04-03 17:24:47 <2> theseus(3959) [qt-ui] YQUI.cc(qMessageHandler):716 <libqt-warning> QCssParser::parseHexColor: Unknown color name '#b9dc8cf' 2014-04-03 17:24:47 <2> theseus(3959) [qt-ui] YQUI.cc(qMessageHandler):716 <libqt-warning> QCssParser::parseHexColor: Unknown color name '#ffff' 2014-04-03 17:24:47 <2> theseus(3959) [qt-ui] YQUI.cc(qMessageHandler):716 <libqt-warning> QCssParser::parseHexColor: Unknown color name '#ffff' 2014-04-03 17:24:47 <1> theseus(3959) [ui] YPushButton.cc(setFunctionKey):202 Guessing button role YOKButton for YPushButton "OK" at 0x7f8f08357950 from function key F10 2014-04-03 17:24:48 <1> theseus(3959) [Ruby] clients/squid.rb:105 Squid module finished 2014-04-03 17:24:48 <1> theseus(3959) [Ruby] clients/squid.rb:106 ---------------------------------------- 2014-04-03 17:24:48 <1> theseus(3959) [liby2] genericfrontend.cc(main):778 Finished YaST2 component 'y2base' 2014-04-03 17:24:48 <1> theseus(3959) [liby2] genericfrontend.cc(main):783 Exiting with client return value '`abort' 2014-04-03 17:24:48 <5> theseus(3959) [zypp] ZYppFactory.cc(sigsegvHandler):53 Error: signal 11 #zypper info squid|grep Version Version: 3.4.4-1.1 #zypper info yast2-squid|grep Version Version: 3.1.2-1.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 872037] New: devel:languages:python/python-python-daemon-1.5 incompatible with python-lockfile-0.9
by bugzilla_noreply＠novell.com 04 Apr '14

04 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=872037 https://bugzilla.novell.com/show_bug.cgi?id=872037#c0 Summary: devel:languages:python/python-python-daemon-1.5 incompatible with python-lockfile-0.9 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request AssignedTo: speilicke(a)suse.com ReportedBy: sascha.lucas(a)gisa.de QAContact: adrian(a)suse.com Found By: Community User Blocker: --- Using OBS repo devel:languages:python for SLES11-SP3 points out, that python-python-daemon-1.5 is not updated to reflect the new api of python-lockfile-0.9. Debian uses python-lockfile-0.8, fedora upgrade to python-daemon-1.6, which can be downloaded[1], but is not mentioned at the homepage. Would be nice to get a working python-daemon... Thanks, Sascha. [1] https://pypi.python.org/packages/source/p/python-daemon/ # Step to reproduce # python -c "import daemon.runner" Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/daemon/runner.py", line 25, in <module> import pidlockfile File "/usr/lib64/python2.6/site-packages/daemon/pidlockfile.py", line 33, in <module> class PIDLockFile(LinkFileLock, object): TypeError: Error when calling the metaclass bases function() argument 1 must be code, not str -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0