Your message dated Sun, 15 Jun 2008 16:02:34 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#428022: fixed in sbackup 0.10.5
has caused the Debian Bug report #428022,
regarding sbackup: leaves complied .pyc file behind
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
428022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428022
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: sbackup
Severity: normal

Hello,

I am not sure if this is against the policy, but anything in /usr/bin
(AFAIK) must be owned by a package. Please remove pyc files from the
system on remove:


# aptitude install sbackup
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following NEW packages will be installed:
  sbackup
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 61.1kB of archives. After unpacking 475kB will be used.
Writing extended state information... Done
Get:1 http://ftp.ro.debian.org etch/main sbackup 0.10.3-0.1 [61.1kB]
Fetched 61.1kB in 6s (8997B/s)
Selecting previously deselected package sbackup.
(Reading database ... 139613 files and directories currently installed.)
Unpacking sbackup (from .../sbackup_0.10.3-0.1_all.deb) ...
Setting up sbackup (0.10.3-0.1) ...

localepurge: Disk space freed in /usr/share/locale: 68K
# ls /usr/sbin/upgrade_backups.py*
/usr/sbin/upgrade_backups.py
# sbackupd

Traceback (most recent call last):
  File "/usr/sbin/sbackupd", line 555, in ?
    do_backup( adir2 )
  File "/usr/sbin/sbackupd", line 313, in do_backup
    do_backup( adir+"/"+child )
  File "/usr/sbin/sbackupd", line 313, in do_backup
    do_backup( adir+"/"+child )
  File "/usr/sbin/sbackupd", line 313, in do_backup
    do_backup( adir+"/"+child )
  File "/usr/sbin/sbackupd", line 313, in do_backup
    do_backup( adir+"/"+child )
  File "/usr/sbin/sbackupd", line 311, in do_backup
    for child in os.listdir( adir ):
KeyboardInterrupt
# ls /usr/sbin/upgrade_backups.py*
/usr/sbin/upgrade_backups.py  /usr/sbin/upgrade_backups.pyc
# aptitude purge sbackup
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Reading task descriptions... Done
Building tag database... Done
The following packages will be REMOVED:
  sbackup{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 475kB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 139643 files and directories currently installed.)
Removing sbackup ...
Purging configuration files for sbackup ...
# ls /usr/sbin/upgrade_backups.py*
/usr/sbin/upgrade_backups.pyc



-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (900, 'stable'), (50, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)


--- End Message ---
--- Begin Message ---
Source: sbackup
Source-Version: 0.10.5

We believe that the bug you reported is fixed in the latest version of
sbackup, which is due to be installed in the Debian FTP archive:

sbackup_0.10.5.dsc
  to pool/main/s/sbackup/sbackup_0.10.5.dsc
sbackup_0.10.5.tar.gz
  to pool/main/s/sbackup/sbackup_0.10.5.tar.gz
sbackup_0.10.5_all.deb
  to pool/main/s/sbackup/sbackup_0.10.5_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aigars Mahinovs <[EMAIL PROTECTED]> (supplier of updated sbackup package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 14 Jun 2008 22:53:10 +0100
Source: sbackup
Binary: sbackup
Architecture: source all
Version: 0.10.5
Distribution: unstable
Urgency: medium
Maintainer: Aigars Mahinovs <[EMAIL PROTECTED]>
Changed-By: Aigars Mahinovs <[EMAIL PROTECTED]>
Description: 
 sbackup    - Simple Backup Suite for desktop use
Closes: 427697 428022 431068 447252 479826
Changes: 
 sbackup (0.10.5) unstable; urgency=medium
 .
   * Update to use su-to-root (Closes: #479826)
   * Revert the group of all files to 'root' as there
     is no common admin group (Closes: #427697)
   * Save partition information (Closes: #431068)
   * Remove *.pyc files on purge (Closes: #428022)
   * Exclude /home/*/.gvfs/ folders by default (Launchpad: #222898)
   * Fix a typo preventing logarithmic cleanup from
     working (Closes: #447252) (Launchpad: #126278, #71698)
   * Fix a popup help type for SSH target recovery (Launchpad: #183650)
   * Check regex before adding it (Launchpad: #191127)
   * Add stop_if_no_target option to abort backups if the taget is
     on a removable drive that is not currently connected
   * Fully draw the "Restoring ..." info box before restoring a file
Files: 
 fc6d0d7863aac25ab545eea0fed93b29 499 admin optional sbackup_0.10.5.dsc
 0d754b72da3b5cadf6de203cdf7afe13 102527 admin optional sbackup_0.10.5.tar.gz
 ad20db5171bf879c1a2dfce5b34dee75 65902 admin optional sbackup_0.10.5_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIVTfEMzCiFWcgm94RAsRuAJwIc3MjeiPxIbRvKbYbc3F8A+QUpgCeJJFp
y6p5IRdHlDiIm4cuH9l4Hsg=
=qyEf
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to