Re: Owner/group while building SRPMs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok.. which I then must ask the question, if you are building RPMs as a 
non-root user, why do you want the ownership to be set to root?  Is it 
because you don't want people to see your username? This sounds like just 
a cosmetic thing.

James S. Martin, RHCE
Contractor
Administrative Office of the United States Courts
Washington, DC
(202) 502-2394

rpm-list-bounces@xxxxxxxxxx wrote on 10/13/2004 01:43:12 PM:

> A non-root user can set the ownership permissions when creating a
> tarball (using --owner and --group options) and I would assume they
> could with cpio as well.  Since the %files section only applies to
> binary RPMs, that solution won't do what I want.
> 
> I would like the following output:
> -----------------------------------------------------------------------
> $ rpm -qlvp dsh-2.0.1-aspen1.src.rpm
> -rw-rw-r--    1 bryans  bryans          24936 Oct 13 11:14 
dsh-2.0.1.tar.bz2
> -rw-rw-r--    1 bryans  bryans           1295 Oct 13 11:14 dsh.spec
> -----------------------------------------------------------------------
> 
> To be this instead:
> -----------------------------------------------------------------------
> $ rpm -qlvp dsh-2.0.1-aspen1.src.rpm
> -rw-rw-r--    1 root    root            24936 Oct 13 11:14 
dsh-2.0.1.tar.bz2
> -rw-rw-r--    1 root    root             1295 Oct 13 11:14 dsh.spec
> -----------------------------------------------------------------------
> 
> 
> That way I don't get warnings like this during a rebuild of the SRPM as
> a different user:
> -----------------------------------------------------------------------
> warning: user bryans does not exist - using root
> warning: group bryans does not exist - using root
> -----------------------------------------------------------------------
> 
> 
> Bryan
> 
> -- 
> Aspen Systems, Inc.    | http://www.aspsys.com/
> Production Engineer    | Phone: (303)431-4606
> bryans@xxxxxxxxxx      | Fax:   (303)431-7196
> 
> On Wed, Oct 13, 2004 at 01:33:09PM -0400, James_Martin@xxxxxxxxxxxxxxx 
wrote:
> >Non-root users can't change ownership of files by default.. What you 
could 
> >do is specify the ownership in the %files section of your spec file.
> >
> >
> >James S. Martin, RHCE
> >Contractor
> >Administrative Office of the United States Courts
> >Washington, DC
> >(202) 502-2394
> >
> >rpm-list-bounces@xxxxxxxxxx wrote on 10/13/2004 01:27:06 PM:
> >
> >> Is there a way while building an SRPM as a non-root user to change 
the
> >> ownership information of files taken from the SOURCES directory?  My
> >> initial ideas of adding the following to my ~/.rpmmacros file didn't
> >> work:
> >> 
> >>   %__cpio   /bin/cpio --no-preserve-owner
> >> 
> >> also tried:
> >> 
> >>   %__cpio   /bin/cpio --owner=root:root
> >> 
> >> 
> >> I didn't see any options in the rpmbuild man page that made sense
> >> either.
> >> 
> >> Thanks,
> >> Bryan
> >> 
> >> -- 
> >> Aspen Systems, Inc.    | http://www.aspsys.com/
> >> Production Engineer    | Phone: (303)431-4606
> >> bryans@xxxxxxxxxx      | Fax:   (303)431-7196
> 
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/rpm-list

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux