Your message dated Thu, 27 Aug 2015 00:52:27 +0200
with message-id <1440629547.3522.10.camel@ger-i5u>
and subject line Fixed upstream
has caused the Debian Bug report #754168,
regarding backintime-common: Backintime can not find anacron
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.)
--
754168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754168
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: backintime-common
Version: 1.0.34-0.1
Severity: important
Dear Maintainer,
* What led up to the situation?
The setup of a periodic backup on a fresh installation.
* What was the outcome of this action?
Backintime doesn't recognize that anacron is installed on the system.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages backintime-common depends on:
ii cron 3.0pl1-124.1
pn python:any <none>
ii rsync 3.1.0-3
backintime-common recommends no packages.
backintime-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
fixed 754168 backintime/1.1.6-1
This was fixed upstream in 1.1.0. BiT doesn't use anacron anymore but
has those features implemented.
thanks
signature.asc
Description: This is a digitally signed message part
--- End Message ---
