July 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 756923] New: Lists markup in the openSUSE blog
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=756923 https://bugzilla.novell.com/show_bug.cgi?id=756923#c0 Summary: Lists markup in the openSUSE blog Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: openSUSE 12.1 Status: NEW Severity: Minor Priority: P5 - None Component: Infrastructure AssignedTo: mrueckert(a)suse.com ReportedBy: victor.dubiniuk(a)gmail.com QAContact: lrupp(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.151 Safari/535.19 There is a minor issue with markers on the detailed post page. Reproducible: Always Steps to Reproduce: 1. open http://news.opensuse.org/2012/03/19/opensuse-to-be-part-of-gsoc-2012/ 2. 3. Actual Results: List markers are pushed out of the content part http://static.opensuse.org/themes/bento/css/base.css line #111 .main ul, .main ol{list-style-position: outside;} This rule overrides the correct 'inside' position that is defined in the line #16 of the same file -- 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 8

[Bug 763687] New: Yast partitioner can't assemble a RAID in one step
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=763687 https://bugzilla.novell.com/show_bug.cgi?id=763687#c0 Summary: Yast partitioner can't assemble a RAID in one step Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: royak.antifeixista(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.3 (KHTML, like Gecko) Chrome/19.0.1066.0 Safari/536.3 SUSE/19.0.1066.0 Hello, It would be a good thing If you could assemble an RAID from previous components in one step. It currently needs to be done in two steps because the file system of the previous components can't be detected by yast partitioner. Thus, you have to open yast partitioner a second time so that It can detect the file systems of the components. Regards. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 730179] New: zypper dup from 12.1RC1 to 12.1 final (?) left system in unbootable state due to non-existent Pod/Usage.pm
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=730179 https://bugzilla.novell.com/show_bug.cgi?id=730179#c0 Summary: zypper dup from 12.1RC1 to 12.1 final (?) left system in unbootable state due to non-existent Pod/Usage.pm Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: d.a.van.delft(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; nl; rv:1.9.2.23) Gecko/20110920 SUSE/3.6.23-0.2.1 Firefox/3.6.23 During installation of packages kernel-desktop, kernel-default, bootsplash, and suspend, zypper dup gave the following error message: # Can't locate Pod/Usage.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.14.2 /usr/lib/perl5/vendor_perl/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.14.2 /usr/lib/perl5/5.14.2/x86_64-linux-thread-multi /usr/lib/perl5/5.14.2 /usr/lib/perl5/site_perl .) at /sbin/update-bootloader line 5. and a *warning* like # warning: %post(suspend-1.0-10.1.2.x86_64) scriptlet failed, exit status 2 At the end of the zypper dup, there was no indication of a serious problem, in fact all above packages initially were flagged as "installed ok". As I had by chance seen above messages, I decided to inspect the system, without rebooting first; luckily as it would probably have been impossible to boot. It showed that in /boot all the old (rc1) kernels were gone and the new 3.1.0-1.2.1 kernels installed, but /boot/grub/menu.lst had only references to the rc1 kernels (which no longer were present)! I did a zypper in -f on all above failed packages, after wich at least the menu.lst contained the references to the new kernels. The entries to the no longer present ones were also still there, however the default had been changed to the new kernel, so at least it would (and later did) boot. The fault is a wrong order of install of above packages, before the package that contains Pod/Usage.pm was done. Contents of /boot, both before and after the manual forced reinstall: total 50652 drwx------ 2 root root 12288 Oct 8 17:45 lost+found -rw------- 1 root root 512 Oct 8 18:33 backup_mbr -rw-r--r-- 1 root root 1236 Oct 25 19:07 boot.readme -rw-r--r-- 1 root root 128888 Nov 5 11:30 config-3.1.0-1.2-desktop -rw-r--r-- 1 root root 128730 Nov 5 11:31 config-3.1.0-1.2-default -rw-r--r-- 1 root root 2547268 Nov 5 12:28 System.map-3.1.0-1.2-desktop -rw-r--r-- 1 root root 4977392 Nov 5 12:28 vmlinuz-3.1.0-1.2-desktop -rw-r--r-- 1 root root 5807889 Nov 5 12:45 vmlinux-3.1.0-1.2-desktop.gz -rw-r--r-- 1 root root 515 Nov 5 12:45 sysctl.conf-3.1.0-1.2-desktop -rw-r--r-- 1 root root 212271 Nov 5 12:45 symvers-3.1.0-1.2-desktop.gz -rw-r--r-- 1 root root 2445966 Nov 5 13:42 System.map-3.1.0-1.2-default -rw-r--r-- 1 root root 4704816 Nov 5 13:42 vmlinuz-3.1.0-1.2-default -rw-r--r-- 1 root root 5501786 Nov 5 14:04 vmlinux-3.1.0-1.2-default.gz -rw-r--r-- 1 root root 404 Nov 5 14:04 sysctl.conf-3.1.0-1.2-default -rw-r--r-- 1 root root 212358 Nov 5 14:05 symvers-3.1.0-1.2-default.gz lrwxrwxrwx 1 root root 1 Nov 13 21:18 boot -> . -rw-r--r-- 1 root root 441856 Nov 13 21:31 message lrwxrwxrwx 1 root root 25 Nov 13 21:47 vmlinuz -> vmlinuz-3.1.0-1.2-default drwxr-xr-x 2 root root 1024 Nov 13 21:48 grub -rw-r--r-- 1 root root 12544103 Nov 13 21:51 initrd-3.1.0-1.2-default lrwxrwxrwx 1 root root 24 Nov 13 21:51 initrd -> initrd-3.1.0-1.2-default -rw-r--r-- 1 root root 12189855 Nov 13 21:51 initrd-3.1.0-1.2-desktop Contents of /boot/grub/menu.lst, after the forced re-install. After the zypper dup, the first four entries were not present: # Modified by YaST2. Last modification on Sun Nov 13 21:48:23 CET 2011 # 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 2 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,0)/message ##YaST - activate ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 12.1 - 3.1.0-1.2 (default) root (hd0,0) kernel /vmlinuz-3.1.0-1.2-default root=/dev/system/root resume=/dev/system/swap splash=silent quiet showopts vga=0x314 initrd /initrd-3.1.0-1.2-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.1 - 3.1.0-1.2 (default) root (hd0,0) kernel /vmlinuz-3.1.0-1.2-default root=/dev/system/root showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314 initrd /initrd-3.1.0-1.2-default ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 12.1 - 3.1.0-1.2 root (hd0,0) kernel /vmlinuz-3.1.0-1.2-desktop root=/dev/system/root resume=/dev/system/swap splash=silent quiet showopts vga=0x314 initrd /initrd-3.1.0-1.2-desktop ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.1 - 3.1.0-1.2 (desktop) root (hd0,0) kernel /vmlinuz-3.1.0-1.2-desktop root=/dev/system/root showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314 initrd /initrd-3.1.0-1.2-desktop ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 12.1 RC 1 - 3.1.0-rc9-1 (default) root (hd0,0) kernel /vmlinuz-3.1.0-rc9-1-default root=/dev/system/root resume=/dev/system/swap splash=silent quiet showopts vga=0x314 initrd /initrd-3.1.0-rc9-1-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.1 RC 1 - 3.1.0-rc9-1 (default) root (hd0,0) kernel /vmlinuz-3.1.0-rc9-1-default root=/dev/system/root showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314 initrd /initrd-3.1.0-rc9-1-default ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 12.1 RC 1 - 3.1.0-rc9-1 root (hd0,0) kernel /vmlinuz-3.1.0-rc9-1-desktop root=/dev/system/root resume=/dev/system/swap splash=silent quiet showopts vga=0x314 initrd /initrd-3.1.0-rc9-1-desktop ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.1 RC 1 - 3.1.0-rc9-1 (desktop) root (hd0,0) kernel /vmlinuz-3.1.0-rc9-1-desktop root=/dev/system/root showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314 initrd /initrd-3.1.0-rc9-1-desktop ###Don't change this comment - YaST2 identifier: Original name: floppy### title Diskette rootnoverify (fd0) chainloader +1 Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Actual Results: Probably an unbootable system Expected Results: Well, at least a bootable system. In case the kernel install fails, it should not remove the old kernel. -- 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 743218] New: Install + updates result in a hang
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=743218 https://bugzilla.novell.com/show_bug.cgi?id=743218#c0 Summary: Install + updates result in a hang Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)opensuse.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:8.0.1) Gecko/20100101 Firefox/8.0.1 I installed a new Xen guest, and also ran the update at the end - the update seems to be hanging - the last message is Installing ./i586/cronie-1.4.7-31.3.1.i586.rpm: "Cron Daemon" I know I have seen this before, and I don't think it is xen related. The system isn't busy, it appears to be hung trying to do: systemctl try-restart cron.service I kill the task, and the update continues. Reproducible: Always -- 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 17

[Bug 450196] ext3 - recovering journal on / on first boot on new kernel/fresh system updates
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=450196 https://bugzilla.novell.com/show_bug.cgi?id=450196#c85 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO CC| |werner(a)suse.com InfoProvider| |mrmazda(a)earthlink.net --- Comment #85 from Dr. Werner Fink <werner(a)suse.com> 2012-07-04 07:40:26 UTC --- (In reply to comment #84) No I do not have any idea otherwise this would be fixed, only a broken system setup like wrong CMOS clock not in UTC and/or strange file system setup causing such recovering due wrong timestamps and/or broken unmount chain. As no one here can reproduce this here on any system it is up on the reporter to provide more informations. (In reply to comment #67) Beside this killall5 will not touch any tool accessing /dev/fuse otherwise the file system umount chain is broken. Also it will not topuch any process from its parent process group othwise the /etc/init.d/boot.localfs script would fail. -- 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 751070] New: Crash in YaST Snapper
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=751070 https://bugzilla.novell.com/show_bug.cgi?id=751070#c0 Summary: Crash in YaST Snapper Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rauhmaru(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=480153) --> (http://bugzilla.novell.com/attachment.cgi?id=480153) Crash in snapper User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 when I click the right mouse button on the window, it closes and gives error. Error: Command failed (IO error). See log for more information. terminate called after throwing an instance of 'snapper::IllegalSnapshotException' what(): illegal snapshot YaST got signal 6 at YCP file Snapper.ycp:72 /sbin/yast2: line 427: 4831 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Snapshot inválido ''. Reproducible: Always Steps to Reproduce: 1.open yast 2.click in snapper 3.right click in window Actual Results: crash! Command failed (IO error). See log for more information. terminate called after throwing an instance of 'snapper::IllegalSnapshotException' what(): illegal snapshot YaST got signal 6 at YCP file Snapper.ycp:72 /sbin/yast2: line 427: 4831 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Snapshot inválido ''. Expected Results: nothing openSUSE 12.1 Gnome Linux linux-3b6q 3.1.9-1.4-default #1 SMP Fri Jan 27 08:55:10 UTC 2012 (efb5ff4) i686 i686 i386 GNU/Linux S | Nome | Tipo | Versão | Arquitetura | Repositório --+---------------------+--------+-----------------+-------------+--------------------- i | libsnapper1 | pacote | 0.0.7-13.2.2 | i586 | openSUSE-12.1-Oss i | snapper | pacote | 0.0.7-13.7.1 | i586 | openSUSE-12.1-Update i | snapper-zypp-plugin | pacote | 0.0.7-13.7.1 | i586 | openSUSE-12.1-Update i | yast2-snapper | pacote | 2.21.16.1-2.3.1 | i586 | openSUSE-12.1-Update -- 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 4

[Bug 561963] New: openvas server fails with "gpgme_new failed: User defined source 1/Not operational"
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=561963 http://bugzilla.novell.com/show_bug.cgi?id=561963#c0 Summary: openvas server fails with "gpgme_new failed: User defined source 1/Not operational" Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: dr(a)baileynet.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 Trying to start openvas-server with "/etc/init.d/openvas-server start" causes error [20409]() gpgme_new failed: User defined source 1/Not operational. This appears to be reported and fixed in this bug report. https://wald.intevation.org/tracker/index.php?func=detail&aid=1079&group_id… Using the patch and compiling the package myself appears to resolve the issue. Reproducible: Always Steps to Reproduce: 1. Install stable version of openvas-server and openvas-plugins 2. You may have to update the openvas-plugins using /usr/sbin/openvas-nvt-sync first. 3. Attempt to start service. Actual Results: Get error: [20409]() gpgme_new failed: User defined source 1/Not operational. Expected Results: Service should start normally. Packages: openvas-server-2.0.3-4.1.x86_64 libopenvas_hg2-2.0.4-3.1.x86_64 openvas-client-2.0.5-3.1.x86_64 openvas-plugins-1.0.7-3.1.x86_64 libopenvasnasl2-2.0.2-3.1.x86_64 libopenvas2-2.0.4-3.1.x86_64 -- Configure bugmail: http://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 766421] New: User account not created following install of openSUSE 12.2 beta 1 (dvd)
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=766421 https://bugzilla.novell.com/show_bug.cgi?id=766421#c0 Summary: User account not created following install of openSUSE 12.2 beta 1 (dvd) Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bgoodall(a)hotmail.co.uk QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) After installing openSUSE 12.2 beta 1 and rebooting and finally reaching the login, unable to login using the user credentials given during installation. Only able to login as root, then create your user account manually, and relogin that way. It is also necessary to select your session type manually at login or login refuses to proceed, even for root. Looks like there is no default option automatically setup for you. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 757229] New: ccid: unknown ccid version 10.00 supported only 1.00, 1.10
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=757229 https://bugzilla.novell.com/show_bug.cgi?id=757229#c0 Summary: ccid: unknown ccid version 10.00 supported only 1.00, 1.10 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8 Trying to play with my Reiner SCT "cyberJack RFID komfort" ("ITSEC E2" certified) chip card terminal, I found out that it doesn't work with the software supplied with openSUSE: The "cyberJack" driver wouldn't work, and the CCID driver also would not. At least the last one seemed to talk with the SCT: ifdhandler[3271]: skipped 1 class/vendor specific interface descriptors ifdhandler[3271]: ccid: unknown ccid version 10.00 supported only 1.00, 1.10 ifdhandler[3271]: usb:/dev/bus/usb/006/005: initialization failed (driver ccid) Now what made me wonder is that my SCT obviously supports CCID version 10, while the software support only version 1.10 at most. I feel worried about the huge gap. The USB device ID is: Bus 006 Device 005: ID 0c4b:0501 Reiner SCT Kartensysteme GmbH (Product: cyberJack RFID komfort) There is not much documentation in the manuals on getting things done, either. Reproducible: Always Steps to Reproduce: 1. Configure ID "usb:0c4b/0501" for "ccid" in /etc/openct.conf 2. Connect cyberJack RFID komfort 3. "openct-tool list" Actual Results: No card reader is found Expected Results: Card reader should be found. Preferrably it should be working. -- 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 758447] New: zlib.error: Error -3 while decompressing: invalid distance code
by bugzilla_noreply＠novell.com 04 Jul '12

04 Jul '12

https://bugzilla.novell.com/show_bug.cgi?id=758447 https://bugzilla.novell.com/show_bug.cgi?id=758447#c0 Summary: zlib.error: Error -3 while decompressing: invalid distance code Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: doiggl(a)velocitynet.com.au QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Hello I get an error when I run this command # time createrepo /media/disk/factory/rpms Result: Saving Primary metadata Saving file lists metadata Saving other metadata Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 263, in <module> main(sys.argv[1:]) File "/usr/share/createrepo/genpkgmetadata.py", line 241, in main mdgen.doRepoMetadata() File "/usr/lib64/python2.7/site-packages/createrepo/__init__.py", line 896, in doRepoMetadata while data.read(zfo, 2**16): File "/usr/lib64/python2.7/site-packages/yum/misc.py", line 237, in read data = fo.read(size) File "/usr/lib64/python2.7/gzip.py", line 252, in read self._read(readsize) File "/usr/lib64/python2.7/gzip.py", line 303, in _read uncompress = self.decompress.decompress(buf) zlib.error: Error -3 while decompressing: invalid distance code lib.error: Error -3 while decompressing: invalid distance code real 23m56.941s user 6m41.521s sys 0m53.911s Reproducible: Always Steps to Reproduce: 1.Run command # time createrepo /media/disk/factory/rpms # generates error Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 263, in <module> main(sys.argv[1:]) File "/usr/share/createrepo/genpkgmetadata.py", line 241, in main mdgen.doRepoMetadata() File "/usr/lib64/python2.7/site-packages/createrepo/__init__.py", line 896, in doRepoMetadata while data.read(zfo, 2**16): File "/usr/lib64/python2.7/site-packages/yum/misc.py", line 237, in read data = fo.read(size) File "/usr/lib64/python2.7/gzip.py", line 252, in read self._read(readsize) File "/usr/lib64/python2.7/gzip.py", line 303, in _read uncompress = self.decompress.decompress(buf) zlib.error: Error -3 while decompressing: invalid distance code lib.error: Error -3 while decompressing: invalid distance code Actual Results: Saving Primary metadata Saving file lists metadata Saving other metadata Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 263, in <module> main(sys.argv[1:]) File "/usr/share/createrepo/genpkgmetadata.py", line 241, in main mdgen.doRepoMetadata() File "/usr/lib64/python2.7/site-packages/createrepo/__init__.py", line 896, in doRepoMetadata while data.read(zfo, 2**16): File "/usr/lib64/python2.7/site-packages/yum/misc.py", line 237, in read data = fo.read(size) File "/usr/lib64/python2.7/gzip.py", line 252, in read self._read(readsize) File "/usr/lib64/python2.7/gzip.py", line 303, in _read uncompress = self.decompress.decompress(buf) zlib.error: Error -3 while decompressing: invalid distance code lib.error: Error -3 while decompressing: invalid distance code real 23m56.941s user 6m41.521s sys 0m53.911s Expected Results: save metadata # rpm -qa | grep -i python | sort apache2-mod_python-3.3.1-167.1.2.x86_64 dbus-1-python-0.83.2-7.1.3.x86_64 evolution-python-plugins-3.2.1-2.2.2.x86_64 gimp-plugins-python-2.6.11-28.23.2.x86_64 libboost_python1_46_1-1.46.1-8.1.3.x86_64 libpeas-loader-python-1.2.0-3.1.2.x86_64 libpyglib-gi-2_0-python0-3.0.2-2.3.1.x86_64 libpython2_7-1_0-2.7.2-7.1.2.x86_64 libpython2_7-1_0-32bit-2.7.2-7.1.2.x86_64 libvirt-python-0.9.6-3.1.2.x86_64 libxml2-python-2.7.8+git20110708-3.1.2.x86_64 patterns-openSUSE-devel_python-12.1-25.21.1.x86_64 python-2.7.2-7.1.3.x86_64 python-32bit-2.7.2-7.1.3.x86_64 python-Louie-1.1-2.1.2.noarch python-M2Crypto-0.21.1-4.1.2.x86_64 python-Twisted-11.0.0-3.1.3.x86_64 python-atspi-2.2.1-2.1.2.noarch python-base-2.7.2-7.1.2.x86_64 python-base-32bit-2.7.2-7.1.2.x86_64 python-beautifulsoup-3.0.8.1-8.1.1.noarch python-bonobo-2.28.1-12.1.2.x86_64 python-brlapi-4.2-16.1.2.x86_64 python-cairo-1.10.0-3.1.3.x86_64 python-ccm-0.9.5.94-2.1.2.noarch python-coherence-0.6.6.2-8.1.2.noarch python-compizconfig-0.9.5.94-2.1.2.x86_64 python-cups-1.9.59-2.1.3.x86_64 python-cupshelpers-1.3.7-2.2.2.noarch python-curses-2.7.2-7.1.3.x86_64 python-devel-2.7.2-7.1.2.x86_64 python-distribute-0.6.21-6.1.1.noarch python-gconf-2.28.1-12.1.2.x86_64 python-gdata-2.0.14-3.1.2.noarch python-gnome-2.28.1-12.1.2.x86_64 python-gnome-menus-3.0.1-10.1.2.x86_64 python-gnomecanvas-2.28.1-12.1.2.x86_64 python-gnomekeyring-2.32.0-11.1.2.x86_64 python-gnomevfs-2.28.1-12.1.2.x86_64 python-gobject-3.0.2-2.3.1.x86_64 python-gobject-cairo-3.0.2-2.3.1.x86_64 python-gobject2-2.28.6-9.1.3.x86_64 python-gstreamer-0_10-0.10.21-5.1.2.x86_64 python-gtk-2.24.0-3.1.2.x86_64 python-gtk-vnc-0.4.3-6.1.2.x86_64 python-httplib2-0.7.1-3.1.1.noarch python-kde4-4.7.2-2.1.2.x86_64 python-kdebase4-4.7.2-6.4.1.x86_64 python-libproxy-0.4.7-7.1.3.noarch python-louis-2.3.0-3.1.2.x86_64 python-lxml-2.3-6.1.3.x86_64 python-notify-0.1.1-20.1.2.x86_64 python-numpy-1.6.1-3.1.2.x86_64 python-optcomplete-1.2_devel-6.1.1.noarch python-orbit-2.24.0-11.1.2.x86_64 python-pam-0.5.0-79.1.2.x86_64 python-pyOpenSSL-0.12-3.1.2.x86_64 python-pycrypto-2.3-3.1.2.x86_64 python-pycurl-7.19.0-2.1.3.x86_64 python-pyserial-2.5-2.1.3.noarch python-pyudev-0.12-2.1.2.noarch python-qt4-4.8.5-5.2.2.x86_64 python-satsolver-0.44.3-2.1.3.x86_64 python-simplejson-2.2.1-2.1.3.x86_64 python-sip-4.12.4-5.1.3.x86_64 python-smbc-1.0.11-3.1.3.x86_64 python-speechd-0.7.1-7.1.2.x86_64 python-telepathy-0.15.19-7.1.2.noarch python-urlgrabber-3.9.1-2.1.2.noarch python-vte-0.28.2-4.1.2.x86_64 python-xdg-0.19-10.1.1.x86_64 python-xlib-0.14-96.1.1.noarch python-xml-2.7.2-7.1.2.x86_64 python-zope.interface-3.8.0-2.1.1.noarch rpm-python-4.9.1.2-1.2.x86_64 xchat-python-2.8.8-8.3.2.x86_64 -- 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 6