Control: fixed -1 0.94

On Sun, 6 Aug 2017 16:31:54 +0200 Andreas Beckmann <a...@debian.org> wrote:
> Hi Julian,
>
> are you aware of the FTBFS in your NMU?

It is now fixed in the latest upload.

Thanks,
Balint

>
> Andreas
>
> On Thu, 20 Jul 2017 15:00:58 +0300 Adrian Bunk <b...@debian.org> wrote:
> > Source: unattended-upgrades
> > Version: 0.93.1+nmu2
> > Severity: serious
> >
> >
https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades&arch=all&ver=0.93.1%2Bnmu2&stamp=1500545189&raw=0
> >
> > ...
> > ======================================================================
> > FAIL: test_untrusted_check_without_conffile_check
(__main__.TestUntrusted)
> > ----------------------------------------------------------------------
> > Traceback (most recent call last):
> > File "./test_untrusted.py", line 49, in
test_untrusted_check_without_conffile_check
> > "Can not find '%s' in '%s'" % (needle, haystack))
> > AssertionError: False is not true : Can not find 'DEBUG InstCount=0
DelCount=0 BrokenCount=0' in '2017-07-20 10:06:26,539 INFO Initial
blacklisted packages:
> > 2017-07-20 10:06:26,539 INFO Initial whitelisted packages:
> > 2017-07-20 10:06:26,539 INFO Starting unattended upgrades script
> > 2017-07-20 10:06:26,540 INFO Allowed origins are:
['o=Ubuntu,a=lucid-security']
> > 2017-07-20 10:06:26,560 DEBUG pkgs that look like they should be
upgraded:
> > 2017-07-20 10:06:26,561 DEBUG fetch.run() result: 0
> > 2017-07-20 10:06:26,562 DEBUG dpkg is configured not to cause
conffile prompts
> > 2017-07-20 10:06:26,562 INFO No packages found that can be upgraded
unattended and no pending auto-removals
> > '
> >
> > ----------------------------------------------------------------------
> > Ran 1 test in 0.026s
> >
> > FAILED (failures=1)
> > Makefile:6: recipe for target 'check' failed
> > make[2]: *** [check] Error 1
> > make[2]: Leaving directory
'/<<BUILDDIR>>/unattended-upgrades-0.93.1+nmu2/test'
> > debian/rules:15: recipe for target 'override_dh_auto_test' failed
> > make[1]: *** [override_dh_auto_test] Error 2
> >
> >
>
>

Reply via email to