On Fri, Sep 29, 2006 at 11:10:56PM +0300, Cougar wrote:
On Fri, 29 Sep 2006, Anders Norrbring wrote:
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?
Specify user and group in SPEC file in %files section like this:
%defattr(644,root,root,755)
or for each file like this:
%attr(755,root,root) %{_datadir}/mythtv/mythvideo/scripts/allocine.pl
This will not work, as this is about .src.rpms. I've patched rpm to support a "_srcdefattr" macro, this is how build does it. It's probably a bug in y2pmbuild that it doesn't use _srcdefattr. CCing Ludwig. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org