April 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 613962] New: macros in buildrequires cause issues
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

http://bugzilla.novell.com/show_bug.cgi?id=613962 http://bugzilla.novell.com/show_bug.cgi?id=613962#c0 Summary: macros in buildrequires cause issues Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pzb(a)novell.com QAContact: adrian(a)novell.com CC: aj(a)novell.com Found By: --- Blocker: --- In a RPM specfile, one can use macros in almost any location. One of these is BuildRequires. However, the build service gets confused and does not expand these, resulting in an "unresolvable" state. Example: BuildRequires: %{_bindir}/perl The build service looks for a package or provide literally named "%{_bindir}/perl". The build service should expand macros using the same rules used in rpmbuild invocation. -- 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 5

[Bug 626876] New: Many or all the PGP keys of the OBS are expired.
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

http://bugzilla.novell.com/show_bug.cgi?id=626876 http://bugzilla.novell.com/show_bug.cgi?id=626876#c0 Summary: Many or all the PGP keys of the OBS are expired. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- Download keys - two repos choosen randomly: http://download.opensuse.org/repositories/GNOME:/STABLE:/2.30/openSUSE_11.3… http://download.opensuse.org/repositories/Apache:/Modules/openSUSE_11.3/rep… Both keys the gpg command, after importing them, say they are expired - months ago. pub 1024D/BD6D129A 2008-01-22 [expired: 2010-04-01] uid Apache OBS Project <Apache(a)build.opensuse.org> pub 1024D/6B9D6523 2006-05-24 [expired: 2008-05-23] uid openSUSE Build Service <buildservice(a)opensuse.org> pub 1024D/9C800ACA 2000-10-19 [expired: 2010-05-05] uid SuSE Package Signing Key <build(a)suse.de> Syncing from internet keys servers, fails to update those. In the forum it has been commented that when attempting to add _any_ repo, it complains about expired keys. All repos. -- 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 16

[Bug 627321] New: The RPM database gets frequently corrupted, so it is impossible to instal or uninstall any package, or update the current ones.
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

http://bugzilla.novell.com/show_bug.cgi?id=627321 http://bugzilla.novell.com/show_bug.cgi?id=627321#c0 Summary: The RPM database gets frequently corrupted, so it is impossible to instal or uninstall any package, or update the current ones. Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: publio.escipion.el.africano(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=379720) --> (http://bugzilla.novell.com/attachment.cgi?id=379720) YaST2 Install's More Informationoutput User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.1.11) Gecko/20100714 SUSE/3.5.11-0.1.1 Firefox/3.5.11 The RPM database gets frequently corrupted, so it is impossible to instal or uninstall any package, or update the current ones. It is the third time that I have this most unusual issue with openSuSE 11.2 since December 2009, and I never had it with SuSE before. Fortunately, it seems to be solved through rpm --rebuilddb as root, but, however, I had to reinstall once all my system to get the package system to work earlier this year. It is annoying and worrying at last. Thrice is too much! I do not know how to reproduce it, and I was worrier by other issues, so I did not reported before. However, the recurrence compels me to do it. This time the issue took place while updating bundle-lang-gnome-en and bundle-lang-gnome-es (bundle-lang-gnome-en-11.2-20.23.5.noarch.rpm and bundle-lang-gnome-es-11.2-20.23.5.noarch.rpm from the openSuSE 11.2's Update repository), but it could be any else package from any else repository, although currently I can not remember precisely which ones I had this before. Reproducible: Sometimes Steps to Reproduce: 1. (See above.) 2. 3. Actual Results: (See above and attachment.) Expected Results: Not a fourth. The above attachment is what YaST2 Install showed about what happened. -- 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 4

[Bug 636042] New: rpm should install src.rpm on ~/rpmbuild
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=636042 https://bugzilla.novell.com/show_bug.cgi?id=636042#c0 Summary: rpm should install src.rpm on ~/rpmbuild Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lmedinas(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.6 SUSE/7.0.501.0 (KHTML, like Gecko) Chrome/7.0.501.0 Safari/534.6 Currently openSUSE rpm installs src.rpm on /usr/src/packages but it should install on ~/rpmbuild just like does Fedora and Mandriva. It would be much safer to build binaries because it won't need root to build it. 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 4

[Bug 733699] New: OBS builds wrong xUbuntu_11.10 packages
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=733699 https://bugzilla.novell.com/show_bug.cgi?id=733699#c0 Summary: OBS builds wrong xUbuntu_11.10 packages Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.3 Platform: 64bit OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: build process AssignedTo: mls(a)suse.com ReportedBy: posix.ru(a)googlemail.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 Hello. I get such build_error every time using my own OBS (tested on v2.1 and v2.3). -------------------------------- installing base-files rmdir: failed to remove `/var/run': Directory not empty dpkg: error processing base-files (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for install-info ... Errors were encountered while processing: base-files exit ... -------------------------------- It happend for xUbuntu 11.10 only. The same package (using same sources) external OBS (build.opensuse.org) builds well. Please fix it so quick as possable, or tell me how to debug build process or something like this... Thanks, Alex Reproducible: Always Steps to Reproduce: 1. just start build process for xUbuntu 11.10 2. wait for installing base-files 3. Expected Results: same results like for another versions of xUbuntu -- 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 749828] New: Publisher data for released products
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=749828 https://bugzilla.novell.com/show_bug.cgi?id=749828#c0 Summary: Publisher data for released products Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: mls(a)suse.com ReportedBy: tschmidt(a)suse.com QAContact: adrian(a)suse.com CC: adrian(a)suse.com, coolo(a)suse.com Found By: --- Blocker: --- For released products it's not possible to fetch the description via the published api, for example: https://api.opensuse.org:443/published/openSUSE:11.2/standard/i586/kopete-4… This makes the search results look uninformative, see: http://software.opensuse.org/search?q=%22kopete%22+4.7.2&baseproject=openSU… also for the new web view on packages which we were doing in our current sprint it would be good to have a consistent api here. Currently I fall back to the first package the provides a description which might be an unofficial one. -- 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 748690] New: python 2.7: add_option in optparse no longer accepts unicode string
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=748690 https://bugzilla.novell.com/show_bug.cgi?id=748690#c0 Summary: python 2.7: add_option in optparse no longer accepts unicode string Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Development AssignedTo: pth(a)suse.com ReportedBy: j-engel(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 Python bug #9161: Fix regression in acceptance of unicode strings in add_option calls. (http://hg.python.org/cpython/rev/705869d1bdf0/) This makes applications crash that depend on non-ASCII arguments (e.g. frescobaldi). The bug is fixed in 2.7.1, the patch is a one-liner that can be backported easily. I made a submit request against python in openSUSE:11.4:Test (https://build.opensuse.org/request/show/106694) with the simple patch to fix this. 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 2

[Bug 741468] New: mkinitrd script "setup-luks_final" asks for non-existent module "kernel", causes confusing warning
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=741468 https://bugzilla.novell.com/show_bug.cgi?id=741468#c0 Summary: mkinitrd script "setup-luks_final" asks for non-existent module "kernel", causes confusing warning Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: All Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Yarny(a)public-files.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 When I call mkinitrd on a system with luks-encrypted root, the mkinitrd script "setup-luks_final.sh" asks mkinitrd to include the non-existing kernel module "kernel": > modprobe: Module kernel not found. > WARNING: no dependencies for kernel module 'kernel' found. setup-luks_final.sh parses /proc/crypto to get a list of all needed crypto kernel modules. Crypto algorithms compiled directly into the kernel are listed with "Module: kernel". setup-luks_final.sh should remove the entry "kernel" from that list before going on. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 12.1 with encrypted lvm partition scheme 2. $ mkinitrd Actual Results: mkinitrd complains about the module "kernel". Expected Results: mkinitrd should not complain about this. This bug also exists in openSUSE 11.4. This patch fixes it: --- a/setup-luks_final.sh +++ b/setup-luks_final.sh @@ -27,7 +27,7 @@ if use_script luks; then luks_lang="$LANG" ;; esac - cryptmodules=`sed -ne '/^module/s/.*: //p' < /proc/crypto` + cryptmodules=`sed -ne '/ kernel$/d;/^module/s/.*: //p' < /proc/crypto` fi check_cryptomgr_needed -- 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 757489] New: kiwi: boot.scr should default to generic kernel image name
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=757489 https://bugzilla.novell.com/show_bug.cgi?id=757489#c0 Summary: kiwi: boot.scr should default to generic kernel image name Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: ms(a)suse.com ReportedBy: agraf(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- When running on an ARM system, kiwi creates the boot.scr to get the system in a working state. That boot.scr boots the one installed kernel by using its exact file name. When an update occurs, we don't have perl-bootloader code yet that would also update the boot.scr, so we render our system unbootable. The easy fix for this is to use the symlink names uImage and uInitrd for kernel/initrd respectively. As soon as perl-bootloader code is available to create a working boot.scr on updates, it will rewrite the boot.scr. But until then, we should try to have something that works for users. -- 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 2

[Bug 757529] New: home:fmherschel/ncc_reset: Bug - ncc_reset does not handle ncc credentials file
by bugzilla_noreply＠novell.com 17 Apr '12

17 Apr '12

https://bugzilla.novell.com/show_bug.cgi?id=757529 https://bugzilla.novell.com/show_bug.cgi?id=757529#c0 Summary: home:fmherschel/ncc_reset: Bug - ncc_reset does not handle ncc credentials file Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: fabian.herschel(a)suse.com ReportedBy: fabian.herschel(a)suse.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Unfortunately the credentials file is not deleted/reset when using the ncc_reset script. Found in version 0.2 -- 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