0755 files after install, 0644 before.
martin f krafft
i am packaging an internal package and experiencing something funny.
my debian/rules installs a couple of files to /usr/share/package and
rather than using install(1) for each operation, I just cp(1) them and
then later `chmod -R u=rwX,og=rX /usr/share/package`.
this works just fine. i mean, almost. the files in
./debian/package/usr/share/package are all 0644 as they should be,
except for the scripts and directories, which are 0755. `dpkg
--contents` lists the files as -rw-r--r-- as it should.
However, when I proceed to install the package, the /usr/share/package
hierarchy will have a couple of files with 0755 permissions, even
though they had 0644 in the package. there is no postinst script or
anything of that sort involved. and there is no pattern as to which
scripts change their mode. they are just always the same, even if
I purge and reinstall the package.
any clues on what's going on?
--
Please do not CC me! Mutt (www.mutt.org) can handle this automatically.
.''`. martin f. krafft <mad...@debian.org>
: :' : proud Debian developer, admin, and user
`. `'`
`- Debian - when you have better things to do than fixing a system
NOTE: The pgp.net keyservers and their mirrors are broken!
Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc
Matt Zimmerman
> However, when I proceed to install the package, the /usr/share/package
> hierarchy will have a couple of files with 0755 permissions, even though
> they had 0644 in the package. there is no postinst script or anything of
> that sort involved. and there is no pattern as to which scripts change
> their mode. they are just always the same, even if I purge and reinstall
> the package.
Perhaps they are being overwritten by a later command? Or changed by
dh_fixperms?
(debian-mentors is the place for this, btw)
--
- mdz
--
To UNSUBSCRIBE, email to debian-dev...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Steve Greenland
>
> Perhaps they are being overwritten by a later command? Or changed by
> dh_fixperms?
Not if 'dpkg --contents foo.deb' shows the correct permissions. Mr.
krafft is claiming that the running 'dpkg -i foo.deb' results in
installed files with different permissions than what is in the deb.
You might want to see what 'dpkg-statoverride --list' shows. Also, extract
the .deb (dpkg-deb --control and dpkg-deb --extract) and see what the result
is there -- maybe debhelper is creating install scripts?
Steve
--
Steve Greenland
The irony is that Bill Gates claims to be making a stable operating
system and Linus Torvalds claims to be trying to take over the
world. -- seen on the net
martin f krafft
> > However, when I proceed to install the package, the /usr/share/package
> > hierarchy will have a couple of files with 0755 permissions, even though
> > they had 0644 in the package. there is no postinst script or anything of
> > that sort involved. and there is no pattern as to which scripts change
> > their mode. they are just always the same, even if I purge and reinstall
> > the package.
>
> Perhaps they are being overwritten by a later command? Or changed by
> dh_fixperms?
dh_fixperms is called without arguments, so I doubt it, and there is
no later command changing the permissions.
what's even more funny is that this only occurs when I used dpkg -i to
install the package from the .deb file. if i use apt-get from
a repository, it works...
> (debian-mentors is the place for this, btw)
why? this is about development, isn't it?
Matt Zimmerman
> what's even more funny is that this only occurs when I used dpkg -i to
> install the package from the .deb file. if i use apt-get from
> a repository, it works...
This is hard to believe...apt invokes dpkg to install packages; it never
touches any files belonging to other packages. Are you sure that you are
getting exactly the same package in both instances? Does dpkg --contents on
/var/cache/apt/archives/package.deb show the correct permissions?
As far as I know, the only things that should be able to cause different
permissions on the system than in the .deb are statoverrides and
interference from other packages (diversions, shared directories, etc.).
> > (debian-mentors is the place for this, btw)
>
> why? this is about development, isn't it?
I misinterpreted your original message; I thought the permissions were
simply wrong in the .deb.
martin f krafft
> This is hard to believe...apt invokes dpkg to install packages; it never
> touches any files belonging to other packages. Are you sure that you are
> getting exactly the same package in both instances? Does dpkg --contents on
> /var/cache/apt/archives/package.deb show the correct permissions?
i am as surprised as you are! let me try to work on this and possibly
reproduce this...
Junichi Uekawa
> hierarchy will have a couple of files with 0755 permissions, even
> though they had 0644 in the package. there is no postinst script or
> anything of that sort involved. and there is no pattern as to which
> scripts change their mode. they are just always the same, even if
> I purge and reinstall the package.
I'd first try to track it down with installing that specific
package inside a new chroot, to see what may be the problem.
regards,
junichi