Anders Norrbring skrev:
Anders Norrbring skrev:
I've been thinking a little.. What's the differencies between building packages with y2pmbuild and build?
I'd like the best of the worlds.. I'd like to build several architectures in one run (build), but I'd also like to have the packages signed and dumped to the repositary I'm building.
One problem is that it appears as the rpm's doesn't get signed.. I have to dig into that a bit more, I'm setting some traps in the y2pmbuild script to see if I can find something out..
I guess a script running 'y2pmbuild-10.1' and then 'linux32 y2pmbuild' would do the trick, but I'd like to know which exit codes y2pmbuild generates for failure and success.
Nope, there are no signing taking place.. I just built postfix, and checked the rpm;
rpm -Kv my_repositary/x86_64/postfix-2.3.3-6.x86_64.rpm my_repositary/x86_64/postfix-2.3.3-6.x86_64.rpm: Header SHA1 digest: OK (d086df6a323df558af7aabc456a86ea3a33b01b9) MD5 digest: OK (4e4b35914f16bf7e11442d500028261b)
It looks like it's a right problem somehow, I just haven't isolated it yet. Another highly annoying thing is that if I build a package with y2pmbuild, it contains rights for the user 'compiler' which of course doesn't exist on any system. So, the result is that when I run rpm -i on a source rpm created, I get these annoying messages: rpm -ivh amavisd-new-2.4.3_rc2-2.src.rpm 1:amavisd-new warning: user compiler does not exist - using root warning: user compiler does not exist - using root warning: user compiler does not exist - using root warning: user compiler does not exist - using root warning: user compiler does not exist - using root warning: user compiler does not exist - using root warning: user compiler does not exist - using root ########################################### [100%] warning: user compiler does not exist - using root warning: user compiler does not exist - using root My question is, how do I get around that, so I get "decent" behaving packages? -- Anders Norrbring Norrbring Consulting