Your message dated Fri, 05 Oct 2018 23:45:41 +0200
with message-id <783df066-06cc-48d2-a6a1-86823e5ec...@crans.org>
and subject line Re: [Pkg-mailman-hackers] Bug#909602: Bug#909602: Bug#909602: 
Bug#909602: mailmanclient causes python3-mailman-hyperkitty and mailman3-web to 
fail to install in buster
has caused the Debian Bug report #909602,
regarding mailmanclient causes python3-mailman-hyperkitty and mailman3-web to 
fail to install in buster
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 ow...@bugs.debian.org
immediately.)


-- 
909602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailman-hyperkitty, mailmanclient, mailman-suite
Control: found -1 python3-mailman-hyperkitty/1.1.0-7
Control: found -1 src:mailmanclient/3.2.0-1
Control: found -1 mailman3-web/0+20170523-16
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Severity: serious

Dear maintainers,

With the recent migration of mailmanclient to testing, the autopkgtest
of mailman3 fails in testing because python3-mailman-hyperkitty and
mailman3-web fail to install. It passes when run with only packages from
unstable. I copied some of the output at the bottom of this report.

If the right binary package(s) from mailmanclient would have had a
versioned Breaks on the broken versions of mailman3-web and
python3-mailman-hyperkitty this could have been prevented. Also this
regression wasn't caught by the migration software framework because
mailmanclient isn't in the Testsuite-Trigger list of mailman3 (which can
be fixed for the future if desired, via a test case with the
hint-testsuite-triggers restriction).  Unfortunately, due to failing
testsuites of mailman-hyperkitty (bug 909238) with the fixed mailman
stack will not migrate soon.

If the regression in the mailman-hyperkitty is deemed relatively
innocent, we can speed up the migration by ignoring the test failures.
If you want this to happen please CC me in responses or play this via
the release team.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/m/mailman3/1054247/log.gz

Setting up python3-mailman-hyperkitty (1.1.0-7) ...
Traceback (most recent call last):
  File "/usr/bin/django-admin", line 21, in <module>
    management.execute_from_command_line()
  File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 364, in execute_from_command_line
    utility.execute()
  File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 338, in execute
    django.setup()
  File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 27,
in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line
108, in populate
    app_config.import_models()
  File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line
202, in import_models
    self.models_module = import_module(models_module_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/lib/python2.7/dist-packages/hyperkitty/models/__init__.py",
line 28, in <module>
    from .email import Email, Attachment
  File "/usr/lib/python2.7/dist-packages/hyperkitty/models/email.py",
line 39, in <module>
    from .mailinglist import MailingList
  File
"/usr/lib/python2.7/dist-packages/hyperkitty/models/mailinglist.py",
line 34, in <module>
    from django_mailman3.lib.mailman import get_mailman_client
  File
"/usr/lib/python2.7/dist-packages/django_mailman3/lib/mailman.py", line
31, in <module>
    from mailmanclient import Client as MailmanClient,
MailmanConnectionError
  File "/usr/lib/python2.7/dist-packages/mailmanclient/__init__.py",
line 25, in <module>
    from mailmanclient.client import Client
  File "/usr/lib/python2.7/dist-packages/mailmanclient/client.py", line
36, in <module>
    from mailmanclient.restbase.connection import Connection
  File
"/usr/lib/python2.7/dist-packages/mailmanclient/restbase/connection.py",
line 18, in <module>
    from urllib.error import HTTPError
ImportError: No module named error



Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Le 5 octobre 2018 21:58:46 GMT+02:00, "Pierre-Elliott Bécue" <p...@debian.org> 
a écrit :
>Le vendredi 05 octobre 2018 à 11:30:03+0200, Pierre-Elliott Bécue a
>écrit :
>> Le jeudi 04 octobre 2018 à 08:57:52+0200, Paul Gevers a écrit :
>> > Hi Pierre,
>> > 
>> > On 04-10-18 00:47, Pierre-Elliott Bécue wrote:
>> > > Would you prefer if we push a fix or if we wait for
>mailman-hyperkitty
>> > > migration?
>> > 
>> > I don't think my preference matters here. Do what you think is best
>for
>> > the mailman suite. I'll just quote [1] a statement from the release
>team
>> > on this matter: "Therefore, we highly recommend that people work on
>> > solving the underlying issue rather than wait it out."
>> > 
>> > Paul
>> > 
>> > [1]
>https://lists.debian.org/debian-devel-announce/2018/09/msg00004.html
>> 
>> I think I'll do something this evening. :)
>
>Good evening.
>
>I had a look ad it this evening.
>
>The only really missing element was the explicit dependency for the
>latest
>release of mailman3 (more specifically, bin:mailman3-full) on the
>latest
>release of mailman3-web (ie 20180916).
>
>Since this dep was missing, it was possible to install mailman3-full
>alongside with mailman3-web 20170523 which draws py2 deps instead of
>py3
>ones.
>
>I'll do a batch of uploads that should set the dependency tree right.
>
>That said, the problem is gone.
>
>I'll close this bug by hand when the uploads are done.
>
>Cheers!

Done. :) 
-- 
PEB

--- End Message ---

Reply via email to