Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'
Charlemagne Lasse wrote on 14/11/2022 at 11:08:06+0100: > Am Mo., 14. Nov. 2022 um 10:53 Uhr schrieb Pierre-Elliott Bécue > : >> I really don't need reminders about the bugs on my packages. > > This is not a reminder. I was just going through the mailman3 packages > to understand what is currently blocking the migration of packages. > And when I found out what is blocking it, I've only checked if this > problem is solved upstream or not. And if it was solved upstream, I > added information about the situation in the already existing bug. Adding tags and links via the appropriate bug commands is indeed helpful, Cc-ing me explicitely and also cc-ing the mailman team list is not the same and is indeed something I feel as putting pressure on me to do the work faster. >> Please refrain from putting pressure on people with the expectation that >> they'll do what you want at the tine you want. >> >> This is the last time I reply to such sollicitations. > > I don't understand why you are so unfriendly. Well, see upwards. The feeling I expressed there is reinforced by your previous communications: on bug #998223, you started to interact by asking the "results" of the new contributors, which I found a bit rude because it felt like they were accountable for something. Never the less, I replied politely that currently we were stuck waiting for upstream to fix the issues with sqlalchemy 1.4 and telling that except someone were to help them, there was nothing we could do. >From that you went on the upstream bug to ask them to work in it: with this: "@msapiro, any idea who to get upstream to have a look at the MR? Possibly before it is too late and everyone kicked out mailman3" I found it a bit rude again, especially since multiple people asked if they had a timeline earlier and they did not reply, I therefore asked you there to stop this behaviour. Then a fix arrived but was not released, and you pinged on november the 4th, and then again, mailman 3.3.7 got released 3 days ago, and on the 13th, you were pinging again and opening a bug to ask 3.3.7 to be packaged. This is no DEFCON1, while I could appreciate a ping two weeks after the release, you let no time to no one to start working on it that you immediately asked us to do so. I had started work on Friday, and decided to not mind and releasing without underlining once again that your enthusiasm was a bit pushy. Then today, you have me receive *6* mails because you Cc-ed me directly + the mailman team list + two bug reports because hyperkitty and django-mailman3 need fixes that were suspended because I preferred to have mailman3 fixed first. I already receive plenty mails, including those you send to the bug report, I really need to not receive multiple copies of mails I already receive, and I also need to be given *at least* a week or two before being asked to fix stuff, *especially* since you know I'm active, having released a first draft for mailman 3.3.7 (which still requires some fixing). So, please, take a breath. Feel free to mail bugs, feel free to add metadata, feel free to submit patches, but don't Cc people on a first message, wait a bit and then ask them if they saw your mails on bugs. I use mailman3, and I would be sad to not be able to make it be in bookworm, I won't ignore the suite, but I need you (and anyone else) to leave me some space, and to remember that we all have a personal life. Cc-ing me is not respecting that. Bests, -- PEB
Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'
Dear Charlemagne, Charlemagne Lasse wrote: Am Mo., 14. Nov. 2022 um 10:53 Uhr schrieb Pierre-Elliott Bécue : I really don't need reminders about the bugs on my packages. This is not a reminder. I was just going through the mailman3 packages to understand what is currently blocking the migration of packages. And when I found out what is blocking it, I've only checked if this problem is solved upstream or not. And if it was solved upstream, I added information about the situation in the already existing bug. Please refrain from putting pressure on people with the expectation that they'll do what you want at the tine you want. This is the last time I reply to such sollicitations. I don't understand why you are so unfriendly. Some small feedback from my side: I don't find your emails unfriendly at all, quite the contrary I appreciate that you do the triaging and try to contribute :) Cheers Jonas
Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'
Am Mo., 14. Nov. 2022 um 10:53 Uhr schrieb Pierre-Elliott Bécue : > I really don't need reminders about the bugs on my packages. This is not a reminder. I was just going through the mailman3 packages to understand what is currently blocking the migration of packages. And when I found out what is blocking it, I've only checked if this problem is solved upstream or not. And if it was solved upstream, I added information about the situation in the already existing bug. > Please refrain from putting pressure on people with the expectation that > they'll do what you want at the tine you want. > > This is the last time I reply to such sollicitations. I don't understand why you are so unfriendly.
Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'
De : Charlemagne Lasse À : Pierre-Elliott Bécue ; Debian Mailman Team ; Jonas Meurer ; 1013...@bugs.debian.org Date : 14 nov. 2022 10:51:44 Objet : Re: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args' > Control: tags -1 + fixed-upstream patch > > This problem currently blocks various mailman3 related packages from > migrating to Debian bookwoom. > > But it seems like this is fixed by 1.3.6: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 Hi, I really don't need reminders about the bugs on my packages. Please refrain from putting pressure on people with the expectation that they'll do what you want at the tine you want. This is the last time I reply to such sollicitations. Regards, -- Pierre-Elliott Bécue
Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'
Control: tags -1 + fixed-upstream patch This problem currently blocks various mailman3 related packages from migrating to Debian bookwoom. But it seems like this is fixed by 1.3.6: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6
Bug#1013480: hyperkitty: FTBFS: TypeError: __init__() got an unexpected keyword argument 'providing_args'
Source: hyperkitty
Version: 1.3.5.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e; \
> for python3 in python3.9 python3.10; do \
> $python3 /usr/bin/django-admin test -v 3 --pythonpath=.
> --settings=hyperkitty.tests.settings_test hyperkitty; \
> done
> /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and
> timeout are misconfigured. Set retry larger than timeout,
> failure to do so will cause the tasks to be retriggered before
> completion.
> See https://django-q.readthedocs.io/en/latest/configure.html#retry
> for details.
> warn(
> Traceback (most recent call last):
> File "/usr/bin/django-admin", line 33, in
> sys.exit(load_entry_point('Django==4.0.5', 'console_scripts',
> 'django-admin')())
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 446, in execute_from_command_line
> utility.execute()
> File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
> line 420, in execute
> django.setup()
> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
> apps.populate(settings.INSTALLED_APPS)
> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 124, in
> populate
> app_config.ready()
> File "/<>/./hyperkitty/apps.py", line 31, in ready
> import hyperkitty.signals
> File "/<>/./hyperkitty/signals.py", line 29, in
> from django_mailman3.signals import mailinglist_created,
> mailinglist_modified
> File "/usr/lib/python3/dist-packages/django_mailman3/signals.py", line 54,
> in
> domain_created = Signal(providing_args=["mail_host"])
> TypeError: __init__() got an unexpected keyword argument 'providing_args'
> make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/06/24/hyperkitty_1.3.5.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
