This bug was fixed in the package storebackup - 3.1-1
---------------
storebackup (3.1-1) unstable; urgency=low
* New Upstream Version
* update copyright
* simplify debian/rules a bit
* upload to unstable
storebackup (3.1~rc1-1) experimental; urgency=low
* New Maintainer (Closes: #508535)
- add Vcs-* fields
* New upstream release (LP: #307885)
- fixed logging (LP: #212258)
- fixes mtime of restored files (Closes: #375401)
- remove exceptDirsSep option (Closes: #490398)
* name the example config file storeBackup_example instead of
storeBackup.conf (Closes: #474369)
* debian policy 3.8.1
* redo debian/rules with debhelper 7
* add Homepage field
* use dh_clean to remove files
* add watch file and get-orig-source target
* remove debian/storebackup.cron.daily, it's included upstream
* update debian/copyright:
- update copyright years
- update license to GPLv3
* remove debian/links, and create the links in debian/rules
* add copyright for Debian packaging
* remove multitail from /usr/bin/ as another package already provides
that
* install man pages from upstream
* add DM-Upload-Allowed field
-- Ubuntu Archive Auto-Sync <arch...@ubuntu.com> Mon, 01 Jun 2009
10:46:30 +0100
** Changed in: storebackup (Ubuntu)
Status: In Progress => Fix Released
--
storebackup logging error
https://bugs.launchpad.net/bugs/212258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
