Re: [tpkg-users] directory permissions not persisting

[Ian Y. <Ian...@me...>]

Oops, disregard that last message.  I accidentally installed the wrong revision number that time.  The postinstall script works so that will solve the problem for now, but I can't figure out what's overwriting the directory attributes after tpkg.yml is applied but before the postinstall script is run.

From: Ian Young [mailto:Ian...@me...]
Sent: Tuesday, August 09, 2011 6:24 PM
To: tpk...@li...
Subject: Re: [tpkg-users] directory permissions not persisting

I tried creating a postinstall script to run chown apache on 3 directories but that didn't have any effect.  I put it at the same level as the tpkg.yml file and gave it execute permission.  After installation the directories were still owned by the user specified in the tpkg.yml file.  Could there be anything that runs after the postinstall script?

From: Ian Young [mailto:Ian...@me...]
Sent: Monday, August 08, 2011 5:36 PM
To: tpk...@li...
Subject: Re: [tpkg-users] directory permissions not persisting

The simple packages I create work as expected; it's the actual package to be used for production that has issues and, unfortunately, that can't be disseminated.  There is no postinstall directory for this package.  I modified the file_defaults in the yml file to see if it was respecting those settings.  I changed owner to root and perms to 0650.  Everything ended up owned by root, however, the 0650 permissions were only applied to files, not directories.  Directory permissions were set to 0755.

From: Darren Dao [mailto:dar...@gm...]
Sent: Monday, August 08, 2011 5:01 PM
To: Ian Young
Cc: tpk...@li...
Subject: Re: [tpkg-users] directory permissions not persisting

I can't reproduce the problem using the yml files you provided. I used the tpkg-prod.yml file you attached and create a test package from it (see attachment). Here's my output

ck3.np.dc1.eharmony.com<http://ck3.np.dc1.eharmony.com> $ tar xvf  mypackage2.tar
mypackage2/
mypackage2/root/
mypackage2/root/var/
mypackage2/root/var/www/
mypackage2/root/var/www/applications/
mypackage2/root/var/www/applications/kingdom/
mypackage2/root/var/www/applications/kingdom/cache/
mypackage2/tpkg.yml
ck3.np.dc1.eharmony.com<http://ck3.np.dc1.eharmony.com> $  cat mypackage2/tpkg.yml
name: kingdom
version: 0.2011.8.3.2-1
maintainer: ian...@me...<mailto:ian...@me...>
description: Kingdom build 0.2011.8.3.2-1
files:
  file_defaults:
    posix:
      owner: ddao
      group: roleusers
      perms: 0755
  files:
  - path: /var/www/applications/kingdom/cache
    posix:
      owner: apache
      group: apache
      perms: 0777
ck3.np.dc1.eharmony.com<http://ck3.np.dc1.eharmony.com> $ tpkg -m mypackage2
Package is ./kingdom-0.2011.8.3.2-1.tpkg
ck3.np.dc1.eharmony.com<http://ck3.np.dc1.eharmony.com> $ tpkg -i kingdom-0.2011.8.3.2-1.tpkg
Executing with sudo
The following packages will be installed:
kingdom-0.2011.8.3.2-1.tpkg
Confirm? [Y/n]
ck3.np.dc1.eharmony.com<http://ck3.np.dc1.eharmony.com> $ ls -al /var/www/applications/kingdom/
total 12
drwxr-xr-x 3 ddao   roleusers 4096 Aug  8 16:38 .
drwxr-xr-x 4 ddao   roleusers 4096 Aug  8 16:38 ..
drwxrwxrwx 2 apache apache    4096 Aug  8 16:38 cache

As you can see, the directory shows up as 0777 and is owned by apache.

My guess is that there are other places where you might be touching that directory. Maybe in postinstall?

It would help us troubleshoot this problem if you can create/attach a simple package (not just the yml file).

-Darren


On Mon, Aug 8, 2011 at 3:52 PM, Ian Young <Ian...@me...<mailto:Ian...@me...>> wrote:
I installed it using the -debug option and I can see the permission metadata in the output.  Once the installation is complete, however, the files/directories have the default attributes set.

From: Ian Young [mailto:Ian...@me...<mailto:Ian...@me...>]
Sent: Monday, August 08, 2011 2:38 PM
To: tpk...@li...<mailto:tpk...@li...>
Subject: [tpkg-users] directory permissions not persisting

We have a tpkg.yml file that is supposed to change the ownership and permissions of some directories but they only retain the default attributes.  I created a very simple test package with a few files and a directory and the yml file successfully changed the owner and group of the directory to apache, so there appears to be something wrong with the production package's configuration.  I've attached the two yml files for comparison.

------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at:  http://p.sf.net/sfu/wandisco-dev2dev

_______________________________________________
tpkg-users mailing list
tpk...@li...<mailto:tpk...@li...>
https://lists.sourceforge.net/lists/listinfo/tpkg-users