Your message dated Fri, 26 Jul 2024 10:40:06 +0200 with message-id <[email protected]> and subject line backuppc bug triaging -- closing ancient bugs has caused the Debian Bug report #601843, regarding backuppc: backuppc_nightly gets wrong parameter 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.) -- 601843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601843 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: backuppc Version: 3.2.0-1 Severity: normal Backuppc_nighthly is supposed to clean up the pool daily. To keep the load down, it is possible to configure which portion is to be cleaned up. Backuppc tracks what has been cleaned already, but it seems there is something wrong: - According comments in /usr/share/backuppc/bin/BackupPC_nightly, its syntax is: Usage: BackupPC_nightly [-m] poolRangeStart poolRangeEnd later in the same file) The poolRangeStart and poolRangeEnd arguments are integers from 0 to 255. - On the web interface I saw the following: admin 10/30 10:12 BackupPC_nightly -m 1280 1535 32546 I did not find a way to reproduce this, but I saw this already some (few) times. (also with 3.1.0) A cause could be that I switched "BackupPCNightlyPeriod" some times latly (from 8 to x and back). Note: The Web UI will still showing, as if it did its job, but as the numbers given are always the same over the past week, I assume it is not doing anything. (cleaned up xxx files with a size of zzz GB (at 10/28 10:27). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-bpo.5-iop32x Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages backuppc depends on: ii adduser 3.112 add and remove users and groups ii bzip2 1.0.5-6 high-quality block-sorting file co ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii dpkg 1.15.8.5 Debian package management system ii exim4 4.72-1 metapackage to ease Exim MTA (v4) ii exim4-daemon-heavy [mail- 4.72-1 Exim MTA (v4) daemon with extended ii iputils-ping 3:20100418-2 Tools to test the reachability of ii libarchive-zip-perl 1.30-3 Perl module for manipulation of ZI ii libcompress-zlib-perl 2.024-1 Transitional dummy package for Com ii libio-compress-perl [libc 2.024-1 bundle of IO::Compress modules ii libtime-modules-perl 2006.0814-2 Various Perl modules for time/date ii lighttpd [httpd] 1.4.28-1 A fast webserver with minimal memo ii perl [libdigest-md5-perl] 5.10.1-15 Larry Wall's Practical Extraction ii perl-suid 5.10.1-15 runs setuid Perl scripts ii samba-common-bin 2:3.5.5~dfsg-1 common files used by both the Samb ii smbclient 2:3.5.6~dfsg-1 command-line SMB/CIFS clients for ii tar 1.23-2.1 GNU version of the tar archiving u ii ucf 3.0025+nmu1 Update Configuration File: preserv Versions of packages backuppc recommends: ii libfile-rsyncp-perl 0.68-1.1+b1 A perl based implementation of an ii libio-dirent-perl 0.04-2+b1 Perl module for accessing dirent s ii openssh-client [ssh-client] 1:5.5p1-4 secure shell (SSH) client, for sec ii rrdtool 1.4.3-1 time-series data storage and displ ii rsync 3.0.7-2 fast remote file copy program (lik Versions of packages backuppc suggests: ii lynx-cur [www-browser] 2.8.8dev.5-1 Text-mode WWW Browser with NLS sup pn par2 <none> (no description available) -- Configuration Files: /etc/backuppc/config.pl changed [not included] /etc/backuppc/hosts changed [not included] /etc/backuppc/localhost.pl changed [not included] /etc/init.d/backuppc changed [not included] -- debconf information excluded
--- End Message ---
--- Begin Message ---Hi, I was going through those very old bugs and decided to close them, as BackupPC V4 has evolved a lot and a lot of those bugs seems to be feature requests, unsure if the problems still exist or otherwise not actionable. Please feel free to reopen the bugs, if think that is sensible, or maybe if it as feature request check directly with upstream. -- tobi
--- End Message ---
