RE: dpkg, non-root user, and chown
> -----Original Message-----
> From: Ian Jackson [mailto:firstname.lastname@example.org]
> Sent: 18 December 2007 21:22
> To: BRIAND, Michel M (EKITO)
> Cc: email@example.com
> Subject: Re: dpkg, non-root user, and chown
> BRIAND, Michel M writes ("dpkg, non-root user, and chown"):
> > Inside data.tar.gz file are owned by the (special) user who did the
> > build (not a user, but a administrative account in our service).
> > Dpkg shall then install those files with that particular owner.
> I think you are confused.
> dpkg will insist on setting the ownership of the files on-disk to that
> specified in the package. If you want to run it in the way you are
> doing (which I'm not convinced is an entirely good idea) then you must
> make the files in the package be owned by the user which is going to
> do the extraction.
> > I've read the dpkg-statoverride man page.
> > But is there a method to install files like they are in
> package, without
> > using dpkg-statoverride ? A simple option to dpkg ?
> dpkg is trying to install the files like they are in the package.
Thank you for the info on this point.
Indeed, I was thinking I've built the package with my user,
but I've built it with fakeroot. So in the .deb, files are owned by root...
I'll redo the whole process to check all that.
This e-mail is intended only for the above addressee. It may contain privileged information.
If you are not the addressee you must not copy, distribute, disclose or use any of the information in it.
If you have received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of security reasons.
This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises.