Bug 21018

Summary:	Several scriptlet failures when building mock chroots
Product:	Mageia	Reporter:	Neal Gompa <ngompa13>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, marja11, shlomif
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Neal Gompa 2017-06-03 15:42:04 CEST

Description of problem:

When building chroots/containers, there are several scriptlet failures that occur:

Non-fatal POSTIN scriptlet failure in rpm package gawk
Non-fatal POSTIN scriptlet failure in rpm package gawk
Non-fatal POSTIN scriptlet failure in rpm package sed
Non-fatal POSTIN scriptlet failure in rpm package sed
Non-fatal POSTIN scriptlet failure in rpm package lib64idn11
Non-fatal POSTIN scriptlet failure in rpm package lib64idn11
Non-fatal POSTIN scriptlet failure in rpm package findutils
Non-fatal POSTIN scriptlet failure in rpm package findutils
Non-fatal POSTIN scriptlet failure in rpm package gzip
Non-fatal POSTIN scriptlet failure in rpm package gzip
Non-fatal POSTIN scriptlet failure in rpm package cpio
Non-fatal POSTIN scriptlet failure in rpm package cpio
Non-fatal POSTIN scriptlet failure in rpm package diffutils
Non-fatal POSTIN scriptlet failure in rpm package diffutils
Non-fatal POSTIN scriptlet failure in rpm package lib64nss3
Non-fatal POSTIN scriptlet failure in rpm package lib64nss3
Non-fatal POSTIN scriptlet failure in rpm package dirmngr
Non-fatal POSTIN scriptlet failure in rpm package dirmngr
Non-fatal POSTTRANS scriptlet failure in rpm package lockdev
Non-fatal POSTTRANS scriptlet failure in rpm package lockdev
Non-fatal POSTTRANS scriptlet failure in rpm package pam
Non-fatal POSTTRANS scriptlet failure in rpm package pam

How reproducible:
Always

Steps to Reproduce:
1. mock -r mageia-cauldron-x86_64 </path/to/package.src.rpm>

Comment 1 Marja Van Waes 2017-06-05 09:44:42 CEST

Hi Neal,

I don't understand whom to assign this bug report to. 

If there's something wrong with those packages, then each package should have a separate bug report.

If there is something wrong with mock, then this bug should be assigned to you, since you're it's registered maintainer.

Assuming the latter and assigning to you ;-)

Feel free to assign back to BugSquad and explain, if I'm wrong.

Assignee: bugsquad => ngompa13
CC: (none) => marja11
Source RPM: (none) => mock

Comment 2 Neal Gompa 2017-06-05 13:46:33 CEST

Mock is the easiest way to reproduce this, which I why I used it as an example. But this happens whenever someone tries to build a Mageia chroot by hand using urpmi or DNF, too.

Basically, a bunch of packages in the base system have scriptlet failures that they shouldn't have when creating a chroot (which also implies something might be wrong during initial installation processes, too).

Resetting back to BugSquad.

Assignee: ngompa13 => bugsquad
Source RPM: mock => (none)

Comment 3 Marja Van Waes 2017-06-05 14:10:44 CEST

Thanks for the explanation, Neal.

gawk, sed, libidn, findutils, gzip, nss, locdev and pam are all maintained by "nobody"
cpio and dirmngr are maintained by shlomif
diffutils is maintainerd by blino

Assigning to all packagers collectively and CC'ing Shlomi and Olivier. 

@ all packagers

Tell me if you want to have seperate reports for some or all of those packages.

Or feel free to clone this report ;-)

Assignee: bugsquad => pkg-bugs
CC: (none) => mageia, shlomif