Thanks.

anything more which needs to be cleaned up?
server:/etc/logrotate.d# dpkg -L gnunet-daemon
/var/log/gnunetd
/etc
/etc/logrotate.d
/etc/logrotate.d/gnunet-daemon
/etc/init.d
/etc/init.d/gnunet-daemon
server:/etc/logrotate.d# dpkg -L gnunet
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/gnunet
/usr/share/doc/gnunet/changelog.gz
/usr/share/doc/gnunet/AUTHORS
/usr/share/doc/gnunet/changelog.Debian.gz
/usr/share/doc/gnunet/README.fr.gz
/usr/share/doc/gnunet/README.gz
/usr/share/doc/gnunet/copyright
/etc/logrotate.d/gnunet
/etc/init.d/gnunet
/etc/default/gnunet
server:/etc/logrotate.d#

BTW how to get rid of the files?
(rm might work, but is dpkg happy with it? I'm not very familiar withthe
debian packages)

Thanks

Achim


Daniel Baumann wrote:
> Achim Schaefer wrote:
>   
>> gnunet is:
>> #
>> #       Logrotate fragment for frox.
>> #
>>
>> /var/log/gnunetd/gnunetd.log {
>>         weekly
>>         size=100k
>>         rotate 7
>>         compress
>>         copytruncate
>>         delaycompress
>>         notifempty
>>         missingok
>> }
>>     
>
> this file was is from a previous gnunet package (from etch).
>
>   
>> gnunet-daemon is:
>> /var/log/gnunetd/gnunetd.log {
>>         weekly
>>         size=100k
>>         rotate 7
>>         compress
>>         copytruncate
>>         delaycompress
>>         notifempty
>>         missingok
>> }
>>     
>
> this file should have been removed when you were upgrading from the
> (post-etch but already deprecated) gnunet-daemon package to the
> (post-etch and current) gnunet-server package.
>
>   
>> gnunet-server is:
>> /var/log/gnunetd/gnunetd.log {
>>         weekly
>>         size=100k
>>         rotate 7
>>         compress
>>         copytruncate
>>         delaycompress
>>         notifempty
>>         missingok
>> }
>>     
>
> ...and that's the only one you should keep.
>
> I'm unsure why does files do not get replaced/removed when doing package
> upgrades.
>
>   



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to