Debian Bug report logs - #126505
dpkg-statoverride : add 'recursive', 'dirs', and 'files' options in rules-file

Reply or subscribe to this bug.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Sean Champ <junctionxyz@mediaone.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: dpkg-statoverride : add 'recursive', 'dirs', and 'files' options in rules-file

Date: Wed, 26 Dec 2001 06:07:47 -0800

Package: dpkg
Version: 1.9.18
Severity: wishlist


dpkg-statoverride is looking like it'll be fairly useful; however, in the
rules file [ /var/lib/dpkg/statoverride ], it looks like each entry is only
for one file or dir; this feature-request is made in the understanding that
there is not yet a means for making a rule that will be applied, recursively,
to all the contents of a given directory. 


Perhaps an additional parameter can be added on the command-line interface,
and on each line of the rules-file, for allowing the admin to say which of the
following should be done, if a directory is referenced in the rules file: 

  [let the term "stamp" refer to the set of ownership rules and permissions,
   as given for a directory] 

  - apply the stamp to all files and directories under the stated directory
     (e.g.: fd)

  - apply the stamp only to directories under the stated directory
     (e.g.: d)

  - apply the stamp only to files under the stated directory
     (e.g.: f)


 with a seperate parameter for saying either of:

  - apply the stamp only to sub-directories
      (e.g.: so that only root will be allowed to remove the directory, but
             anyone in the stated group could remove its subdirectories)

  - apply the stamp to the directory, and its sub-directories
      (e.g.: 's' for 'self, too')

  - apply the stamp only to the nth immediate sub-directories
      (e.g.: '1' for immediated sub-directories, '2' for immediate subdirs
			 and their immediate subdirs, etc; in usage, this would be similar
			 to the '-maxdepth' argument on 'find')  
       

 and, the default behaviors:
  If no extra parameters are specified, just apply the stamp  to the dir
  itself, as if it was an ordinary file; this is the current behavior of
  dpkg-statoverride. 

  If any of the extra parameters are given on a file, apply the stamp as
  usual, and emit a non-fatal warning message, stating the  path on which 
  the parameters are given, and the parameters themselves. [e.g.:
  "dpkg-statoverride :  /bin/bash is a file, unable to use parameters 'ds'"]
  If one or more such warnings are emitted while dpkg or apt is running,
  perhaps a  mail could also be sent to root, with texts of the warnings.  



The order in which the modified lines occur, in /var/lib/dpkg/statoverride,
should not be important. 


as an example, here's an excerpt from a hypothetical rules-file, with the
extra parameters: 

   root perl /usr/lib/perl/ 2775 d
   root xfile /usr/lib/secret/roswell 2700 df
   root fbi /usr/lib/secret 2700 dfs
   root whoever /usr/lib/misc 2775 d1s

   

...with which:

  1)  the 'perl' group would have rwx permissions on all subdirectories 
      of /usr/lib/perl, but not necessarily on files in and under
	  /usr/lib/perl , and not neccessarily on /usr/lib/perl itself; all
	  directories under /usr/lib/perl would be setgid perl

  2) the 'xfile' group would have rwx permissions on all directories and files
	 under /usr/lib/secret/roswell, but not necessarily on the directory
	 itself; all files and directories under /usr/lib/secret/roswell would be
	 setgid xfile 

  3) the 'fbi' group would have rwx permissions on all directories and files 
     under  /usr/lib/secret -- except /usr/lib/secret/rowsell --  and on
     /usr/lib/secret itself; /usr/lib/secret, and all files and directories
	 under it, would be setgid fbi

  4) /usr/lib/misc, and its immediate subdirectories, would be
	 marked with the  'whoever' group; the stated permissions would be
	 applied only to /usr/lib/misc and its immediate sub-directories



if these features were added, it could save the admin from having to run

  find /usr/lib/perl/* -type d -exec chmod g+s {} \;

each time that a new perl module is installed or upgraded with dpkg.



hopefully this explanation isn't too contorted.



-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux tokamak.dtdns.net 2.4.17-rc1 #1 Fri Dec 14 05:03:41 PST 2001 i586
Locale: LANG=C, LC_CTYPE=C

Versions of packages dpkg depends on:
ii  libc6                  2.2.4-5           GNU C Library: Shared libraries an
ii  libncurses5            5.2.20010318-3    Shared libraries for terminal hand
ii  libstdc++2.10-glibc2.2 1:2.95.4-0.011006 The GNU stdc++ library

Message #10 received at 126505-close@bugs.debian.org (full text, mbox, reply):

From: Debian Archive Maintenance <ftpmaster@ftp-master.debian.org>

To: 126505-close@bugs.debian.org

Subject: Bug#126505: fixed

Date: Thu, 10 Jan 2002 16:15:46 +0100

We believe that the bug you reported is now fixed; the following
package(s) have been removed from stable, unstable:

  gpg-idea |          2 | m68k
  gpg-idea |      2.1.1 | alpha, i386, powerpc, sparc
  gpg-idea |        2.2 | alpha, arm, i386, m68k, powerpc, sh, sparc, s390
   gpg-rsa |          2 | m68k
   gpg-rsa |      2.1.1 | alpha, i386, powerpc, sparc
gpg-rsaidea |      2.1.1 | source
gpg-rsaidea |        2.2 | source

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (non-us.debian.org) and will not propagate to any
mirrors (non-us.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 126505@bugs.debian.org.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@debian.org.

Debian distribution maintenance software
pp.
James Troup (the ftpmaster behind the curtain)

Message #15 received at 126505@bugs.debian.org (full text, mbox, reply):

From: Martin Michlmayr <tbm@cyrius.com>

To: control@bugs.debian.org

Cc: 126505@bugs.debian.org

Subject: Re: Bug#126505: fixed

Date: Thu, 10 Jan 2002 17:26:19 +0100

reopen 126505
thanks

Typo in the bug number (should've been #126506).

* Debian Archive Maintenance <ftpmaster@ftp-master.debian.org> [20020110 16:15]:
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from stable, unstable:
> 
>   gpg-idea |          2 | m68k
>   gpg-idea |      2.1.1 | alpha, i386, powerpc, sparc
>   gpg-idea |        2.2 | alpha, arm, i386, m68k, powerpc, sh, sparc, s390
>    gpg-rsa |          2 | m68k
>    gpg-rsa |      2.1.1 | alpha, i386, powerpc, sparc
> gpg-rsaidea |      2.1.1 | source
> gpg-rsaidea |        2.2 | source

-- 
Martin Michlmayr
tbm@cyrius.com

Message #22 received at 126505@bugs.debian.org (full text, mbox, reply):

From: Sean Champ <junctionxyz@mediaone.net>

To: 126505@bugs.debian.org

Subject: Re: Bug#126505 acknowledged by developer (Bug#126505: fixed)

Date: Sat, 12 Jan 2002 16:22:20 -0800

eh ... this is a bit confusing.

1) the attatched explanation does not address the problem mentioned in
   the feature-request.

2) this feature-request was not filed against any  of the pacakges
   mentioned in the attached explanation.

was the bug closed so that it could be reassigned to something else?


On Thu, Jan 10, 2002 at 09:48:08AM -0600, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #126505: dpkg-statoverride : add 'recursive', 'dirs', and 'files' options in rules-file,
> which was filed against the dpkg package.
> 
> It has been closed by one of the developers, namely
> Debian Archive Maintenance <ftpmaster@ftp-master.debian.org>.
> 
> Their explanation is attached below.  If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact the developer, by replying to this email.
> 
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
> 
> Received: (at 126505-close) by bugs.debian.org; 10 Jan 2002 15:38:03 +0000
> >From troup@pandora.debian.org Thu Jan 10 09:38:03 2002
> Return-path: <troup@pandora.debian.org>
> Received: from pandora.debian.org [132.229.137.249] (mail)
> 	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
> 	id 16OhHH-0004du-00; Thu, 10 Jan 2002 09:38:03 -0600
> Received: from troup by pandora.debian.org with local (Exim 3.12 1 (Debian))
> 	id 16Ogvi-0007Mg-00; Thu, 10 Jan 2002 16:15:46 +0100
> From: Debian Archive Maintenance <ftpmaster@ftp-master.debian.org>
> To: 126505-close@bugs.debian.org
> X-Melanie: $Revision: 1.20 $ 
> Subject: Bug#126505: fixed
> Message-Id: <E16Ogvi-0007Mg-00@pandora.debian.org>
> Sender: James Troup <troup@pandora.debian.org>
> Date: Thu, 10 Jan 2002 16:15:46 +0100
> Delivered-To: 126505-close@bugs.debian.org
> 
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from stable, unstable:
> 
>   gpg-idea |          2 | m68k
>   gpg-idea |      2.1.1 | alpha, i386, powerpc, sparc
>   gpg-idea |        2.2 | alpha, arm, i386, m68k, powerpc, sh, sparc, s390
>    gpg-rsa |          2 | m68k
>    gpg-rsa |      2.1.1 | alpha, i386, powerpc, sparc
> gpg-rsaidea |      2.1.1 | source
> gpg-rsaidea |        2.2 | source
> 
> Note that the package(s) have simply been removed from the tag
> database and may (or may not) still be in the pool; this is not a bug.
> The package(s) will be physically removed automatically when no suite
> references them (and in the case of source, when no binary references
> it).  Please also remember that the changes have been done on the
> master archive (non-us.debian.org) and will not propagate to any
> mirrors (non-us.debian.org included) until the next cron.daily run at the
> earliest.
> 
> Packages are never removed from testing by hand.  Testing tracks
> unstable and will automatically remove packages which were removed
> from unstable when removing them from testing causes no dependency
> problems.
> 
> Bugs which have been reported against this package are not automatically
> removed from the Bug Tracking System.  Please check all open bugs and
> close them or re-assign them to another package if the removed package
> was superseded by another one.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 126505@bugs.debian.org.
> 
> This message was generated automatically; if you believe that there is
> a problem with it please contact the archive administrators by mailing
> ftpmaster@debian.org.
> 
> Debian distribution maintenance software
> pp.
> James Troup (the ftpmaster behind the curtain)

Message #27 received at 126505@bugs.debian.org (full text, mbox, reply):

From: Wichert Akkerman <wichert@wiggy.net>

To: Sean Champ <junctionxyz@mediaone.net>, 126505@bugs.debian.org

Subject: Re: Bug#126505: acknowledged by developer (Bug#126505: fixed)

Date: Sun, 13 Jan 2002 13:17:32 +0100

Previously Sean Champ wrote:
> eh ... this is a bit confusing.

It was a typo and the bugreport was already reopened.

Wichert.

-- 
  _________________________________________________________________
 /wichert@wiggy.net         This space intentionally left occupied \
| wichert@deephackmode.org            http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |

Message #39 received at 126505@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Debian Bug Tracking System <owner@bugs.debian.org>, 126505@bugs.debian.org

Subject: reopen, closed by spam, please cleanup (was Re: Bug#126505: marked as done (dpkg-statoverride : add 'recursive', 'dirs', and 'files' options in rules-file))

Date: Thu, 6 Oct 2016 21:47:34 +0000

[Message part 1 (text/plain, inline)]

control: reopen -1

On Wed, Oct 05, 2016 at 06:33:05PM +0000, Debian Bug Tracking System wrote:
> Date: Wed, 5 Oct 2016 20:30:35 +0200
> From: "FedEx 2Day A.M." <mark.curry@sanfabianocalcinaia.it>
> To: 126505-close@bugs.debian.org

closed by spam…


-- 
cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message #51 received at 126505@bugs.debian.org (full text, mbox, reply):

From: camaraco@server414.webhostingpad.com

To: 126505@bugs.debian.org

Subject: Please recheck your delivery address (UPS parcel 9520059)

Date: Fri, 24 Feb 2017 21:13:18 -0600

[Message part 1 (text/plain, inline)]

Dear Customer,

We can not deliver your parcel arrived at February 22.

Download postal receipt attached to e-mail!

Thank you for making business with us,
Jesse Horner,
UPS Parcels Delivery Agent.

[UPS-Delivery-Details-9520059.zip (application/zip, attachment)]

Send a report that this bug log contains spam.