Description of problem: p11-kit has a dependency on /bin/sh which prevents creation of docker containers with rpmbootstrap Version-Release number of selected component (if applicable): 0.20.1 How reproducible: Everytime Steps to Reproduce: 1. use rpmbootstrap to create a mageia 4 chroot 2. when using urpmi a dep on /bin/sh is required which doesn't exist and is now incorrect (/usr/bin/sh would be better) 3. Reproducible: Steps to Reproduce:
Linked to Requires(pretrans): /bin/sh at build time.
Seems to be linked to http://comments.gmane.org/gmane.linux.mageia.devel/39074 THe fact the pretrans creates a dependency on /bin/sh should be changed to /usr/bin/sh now that we have a non separate /usr where all bins are.
CC: (none) => bruno
In mga 5 it has been changed to lua script: %pretrans -p <lua> file = io.open("/etc/pkcs11/pkcs11.conf","r") if (file) then size = file:seek("end") file:close() if (size == 0) then os.remove("/etc/pkcs11/pkcs11.conf") end end Is it something we could backport to mga4 as well to solve the issue ?
/usr/bin/sh would just be incorrect. bash has an explicit provides of /bin/sh, so the problem isn't that the dependency can't be met, it's just that having that dependency on something needed by the core set of packages can cause dependency loops, which can cause non-deterministic dependency failures when installing a chroot. Using lua for the pretrans script causes no additional dependencies, so that fixed the issue in Cauldron. Pascal confirmed on the dev ml that the same fix would work in Mageia 4.
Update pushed into updates_testing
Thanks. Please write an advisory and assign this bug to the QA team. There's instructions on the wiki for doing this if you need it.
Done.
Assignee: bugsquad => qa-bugsStatus: NEW => ASSIGNED
Here is the advisory Bruno uploaded: type: bugfix subject: Updated p11-kit package fixes pretrans issue src: 4: core: - p11-kit-0.20.1-3.3.mga4 description: | backport the %pretrans lua script to mga4 in order to fix dependency issues when trying to build a mga4 chroot (in particular with rpmbootstrap) references: - https://bugs.mageia.org/show_bug.cgi?id=14299
Whiteboard: (none) => advisoryCC: (none) => remi
Manuel just noticed that the release tag on this update candidate is the same as the one already in core/updates. You'll need to increase the subrel and rebuild this, and fix the release tag in the advisory in SVN.
Whiteboard: advisory => advisory feedback
I made the modification that you suggested. Hopefully this is now good to go.
Status: ASSIGNED => NEW
Whiteboard: advisory feedback => advisory
Should I do somethig else to have the package upmloaded ?
For testing the removed dependency, it's quite straightforward with urpmq, but if you could give some instructions to test that p11-kit still works as expected, it would help :-)
Sorry for the delay Bruno, we have been a bit busy with Beta 1. See https://bugs.mageia.org/show_bug.cgi?id=6502#c2 for previous testing. Also p11-kit was previously found to cause problems for programs such as kwrite, kdenlive, digikam, xbmc, claws-mail on nvidia systems so ensure these can still start/run. Bruno may be able to give directions for more thorough testing but IINM p11-kit -l shows it basically works.
Whiteboard: advisory => advisory has_procedure
(In reply to Bruno Cornec from comment #10) > I made the modification that you suggested. Hopefully this is now good to go. in rev 795993, you increased the rel instead of the subrel http://svnweb.mageia.org/packages?view=revision&revision=795993 http://svnweb.mageia.org/packages/updates/4/p11-kit/current/SPECS/p11-kit.spec?r1=795993&r2=795992&pathrev=795993
Grumph :-( My mistake, sorry for that. I reverted release to 3 and subrel to 4 but now I can't submit it anymore :-( Submission errors, aborting: - p11-kit-0.20.1-3.4.mga4: - Current or newer revision(s) already exists in core/updates_testing for 4: 0.20.1-4.3.mga4 Can someone with the right level of power repair my mistake and push the new version ? TIA Bruno.
Adding sysadmin to CC, please see Bruno's comment 15 Thanks
CC: (none) => sysadmin-bugs
Whiteboard: advisory has_procedure => advisory has_procedure feedback
Sysadmins, could you please nuke p11-kit-0.20.1-4.3.mga4 from core/updates_testing ? Thanks in advance.
p11-kit has finally been removed from updates_testing. Feel free to re-push when it's ready.
CC: sysadmin-bugs => (none)
Assigning back to Bruno until this is ready for testing. (just to clear it off our list)
CC: (none) => qa-bugsAssignee: qa-bugs => bruno
New package submitted into core/updates_testing Assigned back to QA.
Assignee: bruno => qa-bugs
Whiteboard: advisory has_procedure feedback => advisory has_procedure
Please also remember to give the complete package list for testers. I'll do it for this one: p11-kit-0.20.1-3.4.mga4 p11-kit-trust-0.20.1-3.4.mga4 lib(64)p11-kit0-0.20.1-3.4.mga4 lib(64)p11-kit-devel-0.20.1-3.4.mga4 From SRPM: p11-kit-0.20.1-3.4.mga4
Testing on mga4 x86_64 real hardware Installed p11-kit-0.20.1-3.4.mga4 p11-kit-trust-0.20.1-3.4.mga4 lib64p11-kit0-0.20.1-3.4.mga4 lib64p11-kit-devel-0.20.1-3.4.mga4 As user $ p11-kit -l p11-kit-trust: p11-kit-trust.so library-description: PKCS#11 Kit Trust Module library-manufacturer: PKCS#11 Kit library-version: 0.20 token: System Trust manufacturer: PKCS#11 Kit model: p11-kit-trust serial-number: 1 hardware-version: 0.20 flags: write-protected token-initialized gnome-keyring: gnome-keyring-pkcs11.so library-description: GNOME Keyring Daemon Core library-manufacturer: GNOME Keyring library-version: 1.1 token: SSH Keys manufacturer: Gnome Keyring model: 1.0 serial-number: 1:SSH:HOME flags: write-protected user-pin-initialized protected-authentication-path token-initialized token: Secret Store manufacturer: Gnome Keyring model: 1.0 serial-number: 1:SECRET:MAIN flags: login-required user-pin-initialized protected-authentication-path token-initialized token: Gnome2 Key Storage manufacturer: Gnome Keyring model: 1.0 serial-number: 1:USER:DEFAULT flags: login-required protected-authentication-path token-initialized token: User Key Storage manufacturer: Gnome Keyring model: 1.0 serial-number: 1:XDG:DEFAULT flags: protected-authentication-path token-initialized
CC: (none) => tarazed25
System has nvidia graphics. Logged in to KDE and launched some of the programs from list in comment 13. kwrite with simple text file kdenlive launched OK digikam ditto xbmc took over the screen. Went as far as looking for Videos. Failed to find any of the mp4 files located in my TV directory and abandoned it. It looks like it works if you know what you are doing. Tentatively marking the update as OK.
Whiteboard: advisory has_procedure => advisory has_procedure MGA4-64-OK
I was able to use urpmi --root to create a chroot with basesystem-minimal (including p11-kit) just fine with no deps issues with the existing packages. Can you give instructions on using rpmbootstrap to do this to demonstrate the issue (and test the fix)? Preferrably if possible allowing for the use of a local mirror and maybe a local path for the testing packages for testing with the update.
MGA4-32 on Acer D620 Xfce. No installation issues. Confirm output of "p11-kit -l" as per Comment 22. xbmc runs and I could open the dialogue to look for files. Stopped there. Trying to close xbmc apparently froze the screen. Maybe I did not wait long enough, but I resorted to Alt-Ctl-Backspace to get back on track. OK for me.
Whiteboard: advisory has_procedure MGA4-64-OK => advisory has_procedure MGA4-64-OK MGA4-32-OKCC: (none) => herman.viaene
Validating. Advisory already uploaded and current with comment 21. Please push to 4 updates Thanks
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0002.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED