Your message dated Sun, 24 Feb 2019 22:41:37 +0100
with message-id <[email protected]>
and subject line Re: Bug#923179: systemd breaks python-dbusmock autopkgtest
has caused the Debian Bug report #923179,
regarding systemd breaks python-dbusmock autopkgtest
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.)
--
923179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923179
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: systemd, python-dbusmock
Control: found -1 systemd/241-1
Control: found -1 python-dbusmock/0.18.1-2
Severity: important
X-Debbugs-CC: [email protected]
User: [email protected]
Usertags: breaks needs-update
Dear maintainers,
With a recent upload of systemd the autopkgtest of python-dbusmock fails
in testing when that autopkgtest is run with the binary packages of
systemd from unstable. It passes when run with only packages from
testing. In tabular form:
pass fail
systemd from testing 241-1
python-dbusmock from testing 0.18.1-2
versioned deps [0] from testing from unstable
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of systemd to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? If needed, please change the
bug's severity.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
systemd/241-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=systemd
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/1994233/log.gz
======================================================================
FAIL: test_empty (__main__.TestLogind)
----------------------------------------------------------------------
Traceback (most recent call last):
File "test_logind.py", line 57, in test_empty
self.assertEqual(out, '')
AssertionError: 'No sessions.\n' != ''
- No sessions.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: reassign -1 python-dbusmock
Version: 0.18.2-1
Hello Paul,
Paul Gevers [2019-02-24 20:36 +0100]:
> With a recent upload of systemd the autopkgtest of python-dbusmock fails
> in testing when that autopkgtest is run with the binary packages of
> systemd from unstable.
Right, I already noticed that, fixed it upstream, and did a new release:
https://tracker.debian.org/news/1031875/accepted-python-dbusmock-0182-1-source-into-unstable/
They succeed again in unstable:
https://ci.debian.net/packages/p/python-dbusmock/unstable/amd64/
So what's left to do is to re-run systemd 241's tests against the unstable
version of python-dbusmock.
Thanks,
Martin
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
