Adam Heath wrote:
> libapache-mod-jserv stored data into /etc/apache
Yes, but it also depended on apache so you could not remove apache without
breaking dependencies.
--
Stefan Gybas
On 1 Feb 2000, Manoj Srivastava wrote:
> __> zgrep /usr/share/apache/icons
> /var/spool/mirror/dists/potato/Contents-i386.gz
IIRC the contents files do not have leading /'s - particularly now that my
patch to remove the ./ has been applied.
Jason
On Wed, Feb 02, 2000 at 09:19:26AM +1100, Brian May wrote:
> Raul> The simple solution to letting the administrator know the
> Raul> package which created the file (which you already see in
> Raul> place here) is to ensure that the path name has the package
> Raul> name clearly embe
>>"Brian" == Brian May <[EMAIL PROTECTED]> writes:
> "Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
Raul> And what about files that "belong" to multiple packages?
Raul> [And, how do you ensure the fresh install of a new such
Raul> package when the old one has been running for some time?]
> "Adam" == Adam Heath <[EMAIL PROTECTED]> writes:
Adam> What if another pkg installs files into
Adam> /var/{log,lib}/apache, or, /etc/apache? Apache's postinst
Adam> does an rm -rf on those dirs, and this will wipe out the
Adam> files owned by the other pkg. libapache-mod-js
On 2 Feb 2000, Brian May wrote:
> dpkg --purge dhcpd-beta
>
> of course!
>
> WRONG! When purging dhcpd-beta, it automatically deletes
> /var/lib/dhcpd, hence breaking the copy og dhcpd that was previously
> installed.
Ok, lets apply this to apache again.
What if another pkg installs files into
> "Falk" == Falk Hueffner <[EMAIL PROTECTED]> writes:
Falk> Usually (always?) this warning is wrong and it will be
Falk> deleted in the purge process later.
Should I report filing bugs against packages which don't?
I know when I upgraded my computers to potato there were a number of
> "Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
Raul> And what about files that "belong" to multiple packages?
Raul> [And, how do you ensure the fresh install of a new such
Raul> package when the old one has been running for some time?]
Well, I already experience problems when
Brian May <[EMAIL PROTECTED]> writes:
> This is why I particular hate the bug in dpkg that warns the
> administrator that empty directories have not been deleted.
Usually (always?) this warning is wrong and it will be deleted in the
purge process later.
Falk
On Tue, Feb 01, 2000 at 12:44:11AM +0200, Brock Rozen wrote:
> If I understand correctly, remove removes the binaries. Leaves docs, etc.
>
> Right?
No. Remove removes everything which is replaceable, that is,
everything which appears in the original .deb except for files listed
as conffiles. It
On 31-Jan-00, 16:44 (CST), Brock Rozen <[EMAIL PROTECTED]> wrote:
> If I understand correctly, remove removes the binaries. Leaves docs, etc.
>
> Right?
Wrong. More explicitly: dpkg removes everything
in /var/lib/dpkg/info/foo.list that isn't also in
/var/lib/dpkg/info/foo.conffiles. The maintai
On Sun, 30 Jan 2000 at 14:28, Steve Greenland wrote about "Re: [RFD]:...":
> > Well, the logs weren't created upon installation -- then why do they get
> > automatically removed upon "purge" ? That's the difference between the
> > config files (with even 100 hours of work put into them...they were
On Mon, Jan 31, 2000 at 07:10:02PM +1100, Brian May wrote:
> *Any* file that is owned by a package must be declared by that package
> to dpkg, this includes any log files, database files or configuration
> files that the package might create. So, for instance, dpkg -S
> /var/log/apache/access.log w
> "Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
Raul> On the other hand, I can certainly understand that rm -rf
Raul> /var/log/apache is both simple and robust.
IMHO, it is the best thing. When I purge a program, I want
to get rid of *everything*.
I do not want to come back in 1
On 30-Jan-00, 01:15 (CST), Brock Rozen <[EMAIL PROTECTED]> wrote:
> On Sat, 29 Jan 2000 at 22:14, Steve Greenland wrote about "Re: [RFD]:...":
> > No, "purge" means what it says in dpkg(8):
> >
> > purge The package is selected to be purged (i.e. we want
> > to remove everything, even
On Sat, 29 Jan 2000 at 22:14, Steve Greenland wrote about "Re: [RFD]:...":
> No, "purge" means what it says in dpkg(8):
>
> purge The package is selected to be purged (i.e. we want
> to remove everything, even configuration files).
>
> Note the use of the word "everything".
Well, the
On Fri, Jan 28, 2000 at 11:03:27PM -0600, Adam Heath wrote:
> Jump forward a few weeks, and now the client wants to start running hit
> reports on the apache log data. Well, it seems that during the apache purge,
> it deleted(rm -rf) /var/log/apache(also a few other dirs).
While it was not your q
On 29-Jan-00, 15:29 (CST), Brock Rozen <[EMAIL PROTECTED]> wrote:
> Obviously there is a need. The problem is that purge means something else
> to different people.
No, "purge" means what it says in dpkg(8):
purge The package is selected to be purged (i.e. we want
to remove everything
On Sat, 29 Jan 2000 at 12:06, Steve Greenland wrote about "Re: [RFD]:...":
> Please, no. If I said purge, I meant purge. Purge removes all files that
> belong to the package, which includes log files. If you want to keep
> them, don't purge, or copy them somewhere. (Logically, this makes sense:
>
Steve Greenland <[EMAIL PROTECTED]> writes:
> On 29-Jan-00, 01:57 (CST), Fumitoshi UKAI <[EMAIL PROTECTED]> wrote:
> > At Fri, 28 Jan 2000 23:03:27 -0600 (CST),
> > Adam Heath <[EMAIL PROTECTED]> wrote:
> > > At least pkgs that do this should prompt.
> > Hm, it might be good idea.
> Please, no.
On 29-Jan-00, 01:57 (CST), Fumitoshi UKAI <[EMAIL PROTECTED]> wrote:
> At Fri, 28 Jan 2000 23:03:27 -0600 (CST),
> Adam Heath <[EMAIL PROTECTED]> wrote:
> > At least pkgs that do this should prompt.
>
> Hm, it might be good idea.
Please, no. If I said purge, I meant purge. Purge removes all file
At Fri, 28 Jan 2000 23:03:27 -0600 (CST),
Adam Heath <[EMAIL PROTECTED]> wrote:
> Is data created during the running of a package removable upon purging?
> Policy is unclear on this. I think it should not remove data that was created
> during runtime, as other packages(and also localy installed s
> "Adam" == Adam Heath <[EMAIL PROTECTED]> writes:
Adam> My question is why is this nescessary? The pkg created the
Adam> files, but who owns them? The pkg, or the admin of the
Adam> machine?
Adam> If the pkg owns the files, then why doesn't gnome, upon
Adam> purging, do
Currently, in various debian documention(policy, packaging manual), purging of
a package says that all files belonging to a pkg are removed, and also its
configuration files.
Recently, when upgrading apache, my boss, Ean, purged apache, so that he could
remove its config files, and start anew(it w
24 matches
Mail list logo
