Debian Bug report logs - #799281
ITP: mailman3-core -- Mailing list management system

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ITP: mailman3-core -- Mailing list management system

Date: Thu, 17 Sep 2015 16:19:09 +0200

Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue" <becue@crans.org>

* Package name    : mailman3-core
  Version         : 3.0.0
  Upstream Author : Barry Warsaw, Mark Sapiro, Aurélien Bompard, Florian Fuchs, Terri Oda, Stephen J. Turnbull, Abhilash Raj
* URL             : http://list.org/
* License         : GPLv3
  Programming Lang: Python3
  Description     : Mailing list management system

GNU Mailman3 is a package providing mailing list management system.
This would be the bare core of Mailman3, without client package,
HyperKitty or Postorius, that would be packaged in different sources
packages.

There is currenctly mailman2 in Debian archive, and I was considering
involve myself in packaging mailman3, Mailman developers seems to think
that it is a pretty good idea, but they suggested me to wait 'till 3.1.0
is out.

I'm currently looking for a sponsor as I'm not a Debian Developer, nor
used to build brand new packages. Since 3.1 is not released yet, I've
some time to learn but I'll be happy to work with people already used to
packaging.

This bug report is CC-ed to Debian mailman team, as I do intend to
collaborate with them, I hope I'll be helpful.

This bug report will come with the others for the others components of
Mailman3 suite. I hope this is the good way of doing ITP

Message #10 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: shirish <shirish@hamaralinux.org>

Cc: 799281@bugs.debian.org

Subject: Re: Any update to packaging Mailman3-core ?

Date: Wed, 28 Oct 2015 16:17:25 +0100

On mer. 28 oct. 2015 à 20:19:49, shirish wrote:
> Dear Pierre-Elliott Bécue,
> 
> Any update on the packaging of Mailman-3-core ?
> 
> Looking forward to learn more.

Good afternoon,

Heres some update:

 * I had some troubles with dependencies, that were fixed in the begining of
   October.
 * I met a lot of troubles having tests working, because they require the
   package to be installed. finally worked around using adt.
 * The packaging was working under experimental at the begining of October
 * The packaging is working under sid for some day
 * I'm currently working on a patch to move some binaries in
   /var/lib/mailman3/bin instead of /usr/bin, and I intend to see with
   upstream if they agree on merging that patch (some binaries have cool names
   but these names are too generic)
 * I'm also designing a basic configuration file and systemd unit

So, it's going on, slowly. Anyway, it is planned to wait the next (minor) release
before packaging, so that some issues reported since initial release will be
fixed.

I hope my answer satisfies your curiosity. :)

-- 
PEB

Message #15 received at 799281@bugs.debian.org (full text, mbox, reply):

From: shirish <shirish@hamaralinux.org>

To: 799281@bugs.debian.org

Cc: Pierre-Elliott Bécue <becue@crans.org>

Subject: Any update to packaging Mailman3-core ?

Date: Wed, 28 Oct 2015 20:19:49 +0530

Dear Pierre-Elliott Bécue,

Any update on the packaging of Mailman-3-core ?

Looking forward to learn more.

-- 
Regards,
Shirish Agarwal,
Community Lead,
Hamaralinux.org

Message #20 received at 799281@bugs.debian.org (full text, mbox, reply):

From: shirish <shirish@hamaralinux.org>

To: Pierre-Elliott Bécue <becue@crans.org>

Cc: 799281@bugs.debian.org, hamara-devel <hamara-devel@lists.hamaralinux.org>

Subject: Re: Any update to packaging Mailman3-core ?

Date: Wed, 28 Oct 2015 22:53:48 +0530

at bottom :-

On 10/28/2015 08:47 PM, Pierre-Elliott Bécue wrote:
> On mer. 28 oct. 2015 à 20:19:49, shirish wrote:
>> Dear Pierre-Elliott Bécue,
>>
>> Any update on the packaging of Mailman-3-core ?
>>
>> Looking forward to learn more.
>
> Good afternoon,
>
> Heres some update:
>
>   * I had some troubles with dependencies, that were fixed in the begining of
>     October.
>   * I met a lot of troubles having tests working, because they require the
>     package to be installed. finally worked around using adt.
>   * The packaging was working under experimental at the begining of October
>   * The packaging is working under sid for some day
>   * I'm currently working on a patch to move some binaries in
>     /var/lib/mailman3/bin instead of /usr/bin, and I intend to see with
>     upstream if they agree on merging that patch (some binaries have cool names
>     but these names are too generic)
>   * I'm also designing a basic configuration file and systemd unit
>
> So, it's going on, slowly. Anyway, it is planned to wait the next (minor) release
> before packaging, so that some issues reported since initial release will be
> fixed.
>
> I hope my answer satisfies your curiosity. :)
>

Thank you. So you are awaiting Mailman 3.0.1 . I am guessing you are 
pointing to this 
https://gitlab.com/groups/mailman/issues?milestone_id=&scope=all&sort=created_desc&state=opened&utf8=%E2%9C%93&assignee_id=&author_id=&milestone_title=3.0.1&label_name=

So seems only 4 bugs remaining for 3.0.1 to appear and 2 of them have 
patches ...but nothing much mentioned on them by either Barry or 
Abhilash. It seems it will take a while.

-- 
Regards,
Shirish Agarwal,
Community Lead,
Hamaralinux.org

Message #25 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: shirish <shirish@hamaralinux.org>, 799281@bugs.debian.org

Cc: hamara-devel <hamara-devel@lists.hamaralinux.org>

Subject: Re: Bug#799281: Any update to packaging Mailman3-core ?

Date: Wed, 28 Oct 2015 18:29:53 +0100

On mer. 28 oct. 2015 à 22:53:48, shirish wrote:
> at bottom :-
> 
> On 10/28/2015 08:47 PM, Pierre-Elliott Bécue wrote:
> >On mer. 28 oct. 2015 à 20:19:49, shirish wrote:
> >>Dear Pierre-Elliott Bécue,
> >>
> >>Any update on the packaging of Mailman-3-core ?
> >>
> >>Looking forward to learn more.
> >
> >Good afternoon,
> >
> >Heres some update:
> >
> >  * I had some troubles with dependencies, that were fixed in the begining of
> >    October.
> >  * I met a lot of troubles having tests working, because they require the
> >    package to be installed. finally worked around using adt.
> >  * The packaging was working under experimental at the begining of October
> >  * The packaging is working under sid for some day
> >  * I'm currently working on a patch to move some binaries in
> >    /var/lib/mailman3/bin instead of /usr/bin, and I intend to see with
> >    upstream if they agree on merging that patch (some binaries have cool names
> >    but these names are too generic)
> >  * I'm also designing a basic configuration file and systemd unit
> >
> >So, it's going on, slowly. Anyway, it is planned to wait the next (minor) release
> >before packaging, so that some issues reported since initial release will be
> >fixed.
> >
> >I hope my answer satisfies your curiosity. :)
> >
> 
> Thank you. So you are awaiting Mailman 3.0.1 . I am guessing you are
> pointing to this https://gitlab.com/groups/mailman/issues?milestone_id=&scope=all&sort=created_desc&state=opened&utf8=%E2%9C%93&assignee_id=&author_id=&milestone_title=3.0.1&label_name=
> 
> So seems only 4 bugs remaining for 3.0.1 to appear and 2 of them have
> patches ...but nothing much mentioned on them by either Barry or Abhilash.
> It seems it will take a while.

Yeah, maybe.

My goal is to make RFS by the end of december, it allows me to take some
time being sure I'm not doing wrong things. It'll also help me ensure to be
able to deliver all the package suite at once.

-- 
PEB

Message #30 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Andreas Hubel <andi@saerdnaer.de>

To: 799281@bugs.debian.org

Subject: Re: Bug#799281: Any update to packaging Mailman3-core ?

Date: Sun, 7 Feb 2016 13:23:15 +0100

[Message part 1 (text/plain, inline)]

Dear Pierre-Elliott Bécue,

On Wed, 28 Oct 2015 18:29:53 +0100 Pierre-Elliott <becue@crans.org> wrote:
> My goal is to make RFS by the end of december, it allows me to take some
> time being sure I'm not doing wrong things. It'll also help me ensure to be
> able to deliver all the package suite at once.

Any updates?

Thanks in advance,
Andi

[signature.asc (application/pgp-signature, attachment)]

Message #35 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Andreas Hubel <andi@saerdnaer.de>, 799281@bugs.debian.org

Cc: debian-devel@lists.debian.org

Subject: Re: Bug#799281: Any update to packaging Mailman3-core ?

Date: Mon, 8 Feb 2016 10:59:34 +0100

[Message part 1 (text/plain, inline)]

Le dimanche 07 février 2016 à 13:23:15+0100, Andreas Hubel a écrit :
> Dear Pierre-Elliott Bécue,
> 
> On Wed, 28 Oct 2015 18:29:53 +0100 Pierre-Elliott <becue@crans.org> wrote:
> > My goal is to make RFS by the end of december, it allows me to take some
> > time being sure I'm not doing wrong things. It'll also help me ensure to be
> > able to deliver all the package suite at once.
> 
> Any updates?

Good morning,

Yes! I successfully built something that made me happy, but so far I asked
for some reviewing, and I got only one or two answers. I took the advice
into account, I'll probably retry to ask some reviews soon, then I'll go in
packaging all the things. My main issue for now is about configuring
correctly mailman3 to have a properly running server on install, even if the
administrator will need to reconfigure some things.

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: 799281@bugs.debian.org

Cc: mailman-developers@python.org, debian-devel@lists.debian.org, andi@saerdnaer.de, shirish@hamaralinux.org

Subject: Re: [Mailman-Developers] Let's try to package mailman3 in Debian!

Date: Fri, 19 Feb 2016 11:26:15 +0100

Le lundi 14 décembre 2015 à 17:01:57+0100, Pierre-Elliott Bécue a écrit :
> Le lundi 23 novembre 2015 à 02:56:27+0100, Pierre-Elliott Bécue a écrit :
> > Le vendredi 11 septembre 2015 à 00:49:44+0200, Pierre-Elliott Bécue a écrit :
> > > [packaging mailman3]
> > 
> > Hey,
> > 
> > Here is an update.
> > 
> > For now on, I focused on mailman3-core package in order to get good
> > practices working.
> > 
> > One can find my work here : https://github.com/P-EB/mailman3-core
> > 
> > I'm working on having working systemd/sysv services and after that it'll be
> > a good idea to try installing the package and see how it goes.
> > 
> > I also have to design a good config file for debian, (see
> > debian/contrib/mailman.cfg in master branch). Any suggestion is welcome!
> > 
> > Cheers
> 
> Small bump here, I'd appreciate if somebody finds the time to tell me two
> things:
> 
>  * Is my config file enough for a start ?
>  * Is my systemd service good to have mailman started properly ?
> 
> I'd rather be sure it's okay before writing a sysv service.
> 
> You can find contrib files in debian/contrib.

Hello!

Before requesting for sponsorship, and packaging officially the other
components of mailman3, I'd like some "testers" for the core package I
built, in order to be sure that it works, and that I will not introduce some
stupid caveats on the packaging of the other components.

.deb can be found here: http://peb.pimeys.fr/mailman/mailman3-core/
git repo can be found there: https://gitlab.pimeys.fr/PEB/mailman3-core
and there: https://github.com/P-EB/mailman3-core

Any volunteer welcome! Please, I need your help, I cannot review my work
alone! :)

-- 
PEB

Message #45 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jan Luca Naumann <j.naumann@fu-berlin.de>

To: 799281@bugs.debian.org, becue@crans.org

Subject: Re: [Mailman-Developers] Let's try to package mailman3 in Debian!

Date: Mon, 7 Nov 2016 21:42:21 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear Pierre-Elliott Bécue,

what is the current status of your packaging intend. Since I did not
the WNPP-list very well I started another ITP (that I closed of course
now) and maybe we can work together and/or I can take over some of the
work.

Best regards,
Jan

On Fri, 19 Feb 2016 11:26:15 +0100 Pierre-Elliott
=?iso-8859-1?Q?B=E9cue?= <becue@crans.org> wrote:
> 
> Hello!
> 
> Before requesting for sponsorship, and packaging officially the
> other components of mailman3, I'd like some "testers" for the core
> package I built, in order to be sure that it works, and that I will
> not introduce some stupid caveats on the packaging of the other
> components.
> 
> .deb can be found here:
> http://peb.pimeys.fr/mailman/mailman3-core/ git repo can be found
> there: https://gitlab.pimeys.fr/PEB/mailman3-core and there:
> https://github.com/P-EB/mailman3-core
> 
> Any volunteer welcome! Please, I need your help, I cannot review my
> work alone! :)
> 
> -- PEB
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJYIOctAAoJEH4R1/EZ+XG7QdEQAKvSTrZeexBJLZnHXddRxCW+
W5HUxJryZvQiu73cw5w/1ra008bjWZOHzCD+oj9WdbxrKE+QFf46Zl+gFEfQO2Qf
+nNHjZIxzwK5UFrw119lhxqTrALoaJs7FgoWxnA98v0wXQ9UdXcmve7HA4fVIAOS
uL5tvybnj+SLUpw7/VPEgl1SGdhOrcRQD5m/6notmR+2JgRfYCzvptoNxv4uDGD4
ZEV/t+BxJsMuv4mS9l+mZLN6FoOBaq+Wwd9w3/Vea9npxliIFRJ54Zp0nT+uhzjG
Uyhepw4/qgRAj1hBDx+UnKwn84qd1YsTJ9LzPqMJg48LBR58bt+y5d6hX8MFpfAW
NG2aunZlwj/i7/J1uvkYJTXA/1VLtBxaWHuR2jjAQVvFjnEPHBquNSIUqinl2hv/
d+xSCnx8OGDUG231uWYiQAZWhXUGy3eyEjJjpEiyKTQyhW0msgxow9IozdVpKURY
wBcykEpa815YDfzCtHOYtdGziTEHq6Z2mGEc1kbCd9q51b7fsSMeABr7pxqyDcyA
Y5csXo9PsrdSg10a5USn29kTZiiE3V7jiiK/q6HUpcochAn2ebyE1sDea2m8HDMc
FHEJ4wlWQwRqbJ/D2PwnoZUTXyA8oe8AJTqKKqAWHLhO2qWEm9WOIf1wZ8efiyzx
K32qAoT/7AAazKn8puGY
=2jY1
-----END PGP SIGNATURE-----

Message #50 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Jan Luca Naumann <j.naumann@fu-berlin.de>, 799281@bugs.debian.org

Subject: Re: Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!

Date: Mon, 7 Nov 2016 22:26:40 +0100

[Message part 1 (text/plain, inline)]

Le lundi 07 novembre 2016 à 21:42:21+0100, Jan Luca Naumann a écrit :
> Dear Pierre-Elliott Bécue,
> 
> what is the current status of your packaging intend. Since I did not
> the WNPP-list very well I started another ITP (that I closed of course
> now) and maybe we can work together and/or I can take over some of the
> work.
> 
> Best regards,

Dear Jan,

I'd be happy to work with you.

Mostly, all parts of mailman are "pre-packaged" on my server. I met issues
with HyperKitty regarding dependencies, currently, these are not fully
solved, as the devs had to move from django-browserid (implementation of
persona protocol, by Mozilla) to another dependency offering implementation
of a still used protocol (Mozilla is dropping persona).

The second "issue" is mailman itself. It's using python3.4, but default
version of python3 in debian is 3.5 for something like 10 months. I'm
waiting mailman version 3.1, as Barry Warsaw told me it'd use python3.5.

If you wish I can give you the developper accesses on my github repositories
which contain the current packages, except hyperkitty (because of what I
mentioned before).

Cheers,

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #55 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jan Luca Naumann <j.naumann@fu-berlin.de>

To: Pierre-Elliott Bécue <becue@crans.org>, 799281@bugs.debian.org

Subject: Re: Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!

Date: Fri, 11 Nov 2016 14:39:18 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hey Pierre-Elliott,

my idea is that we package the current development versions and upload
them to Debian experimental since the development time of 3.1 will
last some more time according to the Mailman developers...

If you have no problem I could submit some changes to your repository
either as pull requests or as direct pushs?

Jan

Am 07.11.2016 um 22:26 schrieb Pierre-Elliott Bécue:
> 
> Dear Jan,
> 
> I'd be happy to work with you.
> 
> Mostly, all parts of mailman are "pre-packaged" on my server. I met
> issues with HyperKitty regarding dependencies, currently, these are
> not fully solved, as the devs had to move from django-browserid
> (implementation of persona protocol, by Mozilla) to another
> dependency offering implementation of a still used protocol
> (Mozilla is dropping persona).
> 
> The second "issue" is mailman itself. It's using python3.4, but
> default version of python3 in debian is 3.5 for something like 10
> months. I'm waiting mailman version 3.1, as Barry Warsaw told me
> it'd use python3.5.
> 
> If you wish I can give you the developper accesses on my github
> repositories which contain the current packages, except hyperkitty
> (because of what I mentioned before).
> 
> Cheers,
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJYJcoCAAoJEH4R1/EZ+XG7+loP/3McoCqbTvwbPNLcSjw9Cnbi
VNDzOoHCLMfvTOsmODH3fOJOgSUHEcpoUHF3EL3xbPYsRc+Qf2BKXcPcXJeRuHJn
qCTvXJbUNpGO+jECN4FbVjPPU3HUBLmw+m15t92ZTi5xvxBUCMwDObpErC6YtNSf
Jf7RIxk+0IpUmj4Loxq3GBJBBG7DWdDPxs5p8O7mLnT7Ep+9K3bL9ErlDMCQmP5q
tWnPoPwv+t3h5pj8kyYxhXzII5mREljytxrm2cMx4c94l/hCm7orxigeBnZfQnni
3aqKYgpAsHW2bG+S7d9kCv/rcV0C3vwM/xFu7Vi9urB0gFUu5yfmmdWP0Yl+uxOK
R5pVmZF5ckeluIjZ1qELAZvEw41HIhd0qKuIvt4pocIkplFNtME6oNdnoiJ28Z+t
T6kXrIl3j3ptYIrNQCrLq+6jJrlH/TcMrjSvSSXw27jhDw/SXE9iTXgpx1AI8FW3
QacW9WzN0c/dTnJfA4CUWMY4N6bpoCIxnIRmYBonEkBPNcB14BTs5NxpYOFzfKTU
L0PpZ5Yu+4pmWiIz3K9IMCYNNgW9jEiY4uiACq3QQ2qYt+zGXO5my1rwR0LXEOj/
5SJMquiIBGl/3inrhTJvI/QJJmY3c51ja/jhY8nhT+CPLg+riLdDYlgGj958CtDa
lmr/WRHbElhrzqXk0bKt
=N08F
-----END PGP SIGNATURE-----

Message #60 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Jan Luca Naumann <j.naumann@fu-berlin.de>, 799281@bugs.debian.org

Subject: Re: Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!

Date: Mon, 14 Nov 2016 22:42:18 +0100

Le vendredi 11 novembre 2016 à 14:39:18+0100, Jan Luca Naumann a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hey Pierre-Elliott,
> 
> my idea is that we package the current development versions and upload
> them to Debian experimental since the development time of 3.1 will
> last some more time according to the Mailman developers...
> 
> If you have no problem I could submit some changes to your repository
> either as pull requests or as direct pushs?

As said, there is two issues.

First, HyperKitty deps are missing, second, mailman relies on python3.4.

If you have some patches to offer let's go for it, what is your github login
please?

-- 
PEB

Message #65 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jan Luca Naumann <j.naumann@fu-berlin.de>

To: Pierre-Elliott Bécue <becue@crans.org>, 799281@bugs.debian.org

Subject: Re: Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!

Date: Fri, 18 Nov 2016 16:39:46 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Control: subscribe -1 j.naumann@fu-berlin.de

Hey,

my point was to start packaging the Mailman 3.1 development version
already since this version switches to python3.5 and many bug fixes
are applied there (I currently administrate a 3.0.3 installation,
there are many things not working properly). For the new
django-allauth dependency I have created a new ITP bug (you should be
in CC of the bug).

My GitHub account is JanLuca.

Best regards,
Jan

Am 14.11.2016 um 22:42 schrieb Pierre-Elliott Bécue:
> Le vendredi 11 novembre 2016 à 14:39:18+0100, Jan Luca Naumann a 
> écrit :
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
>> 
>> Hey Pierre-Elliott,
>> 
>> my idea is that we package the current development versions and 
>> upload them to Debian experimental since the development time of 
>> 3.1 will last some more time according to the Mailman 
>> developers...
>> 
>> If you have no problem I could submit some changes to your 
>> repository either as pull requests or as direct pushs?
> 
> As said, there is two issues.
> 
> First, HyperKitty deps are missing, second, mailman relies on 
> python3.4.
> 
> If you have some patches to offer let's go for it, what is your 
> github login please?
> 
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYLyC+AAoJEH4R1/EZ+XG7FoQP/3XHmbQlxo0kMO4YXLoTQuKW
HvJVW8lwiIyBTRdY7RyY/obtGXjLvNDXpnUPyGULWUX3XUC0O15F2PHXFjbxc3b4
AI/uJEDfpbr88z46fYFRCPov5/A4tUEp+Rn0qBtl6jFI3tU8kcU9dS01tTml0aw8
sexwc8W7Qu/YQ93OjrSQG4p+O95d6V9ksTgf5XihdaieQQCg9Yf+rb97oJ4c3R2A
Y9bixue+NA3fDYdkBEX52okUsVCij2iujdBuDAwOCfrhN9rhVsdtlQB480UST8j+
/a6zzOZRKcHQwbF4+QtKnAdA3KLKgmn8L/oTy+FPFit1Ew+6kb6QInx8if49VWVl
Z25f/EDUNV40xiQAvrnbwIkGqqo3mtIqZPwgak5g4IkMEtRY1kbglZT10evRkTWD
724K+604cP0/GlybDWiZIvFolH/WMyUjopLRFRccFgiJEyo1egeV8G2HBYfYKGAn
dSRpnnDCURUDNlQCEGXBd9pcLXwDK1X04o55aQxN09m8RnUuwAxDpg/bqGktwUCs
ktBoQuSDjPf7XcMjSxXIhBW9hradvQHDD/gXbD9x10kklj68kE2YtkHRuQgTbgyf
Flp8wfYwBT5ff5x8o/uyGSeDa2eedxT1XNihrmJWg4QoSebZbBkII3HNDii6Ysho
xQpjpvTGXub26IQ/WB+/
=sa/A
-----END PGP SIGNATURE-----

Message #70 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Jan Luca Naumann <j.naumann@fu-berlin.de>, 799281@bugs.debian.org

Subject: Re: Bug#799281: [Mailman-Developers] Let's try to package mailman3 in Debian!

Date: Mon, 21 Nov 2016 16:34:39 +0100

[Message part 1 (text/plain, inline)]

Le vendredi 18 novembre 2016 à 16:39:46+0100, Jan Luca Naumann a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Control: subscribe -1 j.naumann@fu-berlin.de
> 
> Hey,
> 
> my point was to start packaging the Mailman 3.1 development version
> already since this version switches to python3.5 and many bug fixes
> are applied there (I currently administrate a 3.0.3 installation,
> there are many things not working properly). For the new
> django-allauth dependency I have created a new ITP bug (you should be
> in CC of the bug).
> 
> My GitHub account is JanLuca.

Dear Jan Luca,

I pushed my HyperKitty stalled work on GitHub and gave you collaborator
accesses. I suggest we continue discussing these packaging via IRC or by
mail, removing the bug tracking of the contacts.

Cheers,

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #75 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: 799281@bugs.debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Sat, 12 Aug 2017 08:40:32 +0200

[Message part 1 (text/plain, inline)]

Le jeudi 17 septembre 2015 à 16:19:09+0200, Pierre-Elliott Bécue a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: "Pierre-Elliott Bécue" <becue@crans.org>
> 
> * Package name    : mailman3-core
>   Version         : 3.0.0
>   Upstream Author : Barry Warsaw, Mark Sapiro, Aurélien Bompard, Florian Fuchs, Terri Oda, Stephen J. Turnbull, Abhilash Raj
> * URL             : http://list.org/
> * License         : GPLv3
>   Programming Lang: Python3
>   Description     : Mailing list management system
> 
> GNU Mailman3 is a package providing mailing list management system.
> This would be the bare core of Mailman3, without client package,
> HyperKitty or Postorius, that would be packaged in different sources
> packages.
> 
> There is currenctly mailman2 in Debian archive, and I was considering
> involve myself in packaging mailman3, Mailman developers seems to think
> that it is a pretty good idea, but they suggested me to wait 'till 3.1.0
> is out.
> 
> I'm currently looking for a sponsor as I'm not a Debian Developer, nor
> used to build brand new packages. Since 3.1 is not released yet, I've
> some time to learn but I'll be happy to work with people already used to
> packaging.
> 
> This bug report is CC-ed to Debian mailman team, as I do intend to
> collaborate with them, I hope I'll be helpful.
> 
> This bug report will come with the others for the others components of
> Mailman3 suite. I hope this is the good way of doing ITP

Somme followup.

mailman3 core server v3.1 has been released in may. I've been packaging it
and it's fully compatible with python3.5 (and supposedly also with
python3.6).

I asked barry (CC-ed) to review and sponsor. Though he'll require some time
to do it.

In the meantime, I also asked to join pkg-mailman team, so that I can put
the git repo of the package on a debian's server.

Anyone interested in can have a look at the package repo on
https://github.com/P-EB/mailman3-core.git

The current .deb can be found here:
https://peb.pimeys.fr/packages/mailman/mailman3-core/ alongside with the
build logs.

I hope to have mailman 3.1 in debian soon.

Cheers.

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #80 received at 799281@bugs.debian.org (full text, mbox, reply):

From: shirish शिरीष <shirishag75@gmail.com>

To: Pierre-Elliott Bécue <becue@crans.org>, 799281@bugs.debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Thu, 17 Aug 2017 11:31:57 +0530

at bottom :-

On 12/08/2017, Pierre-Elliott Bécue <becue@crans.org> wrote:

<snipped>

> Somme followup.
>
> mailman3 core server v3.1 has been released in may. I've been packaging it
> and it's fully compatible with python3.5 (and supposedly also with
> python3.6).
>
> I asked barry (CC-ed) to review and sponsor. Though he'll require some time
> to do it.
>
> In the meantime, I also asked to join pkg-mailman team, so that I can put
> the git repo of the package on a debian's server.
>
> Anyone interested in can have a look at the package repo on
> https://github.com/P-EB/mailman3-core.git
>
> The current .deb can be found here:
> https://peb.pimeys.fr/packages/mailman/mailman3-core/ alongside with the
> build logs.
>
> I hope to have mailman 3.1 in debian soon.
>
> Cheers.
>
> --
> PEB
>

I think you forgot to CC barry in your update. His mail id is nowhere
to be seen.

Anyways, would be nice to see mailman 3.1 in Debian soonish.

Looking forward to seeing it.

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Message #85 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: shirish शिरीष <shirishag75@gmail.com>,799281@bugs.debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Thu, 17 Aug 2017 10:15:46 +0200

Le 17 août 2017 08:01:57 GMT+02:00, "shirish शिरीष" <shirishag75@gmail.com> a écrit :
>at bottom :-
>
>On 12/08/2017, Pierre-Elliott Bécue <becue@crans.org> wrote:
>
><snipped>
>
>> Somme followup.
>>
>> mailman3 core server v3.1 has been released in may. I've been
>packaging it
>> and it's fully compatible with python3.5 (and supposedly also with
>> python3.6).
>>
>> I asked barry (CC-ed) to review and sponsor. Though he'll require
>some time
>> to do it.
>>
>> In the meantime, I also asked to join pkg-mailman team, so that I can
>put
>> the git repo of the package on a debian's server.
>>
>> Anyone interested in can have a look at the package repo on
>> https://github.com/P-EB/mailman3-core.git
>>
>> The current .deb can be found here:
>> https://peb.pimeys.fr/packages/mailman/mailman3-core/ alongside with
>the
>> build logs.
>>
>> I hope to have mailman 3.1 in debian soon.
>>
>> Cheers.
>>
>> --
>> PEB
>>
>
>I think you forgot to CC barry in your update. His mail id is nowhere
>to be seen.
>
>Anyways, would be nice to see mailman 3.1 in Debian soonish.
>
>Looking forward to seeing it.

I bounced to him after sending the email and realizing that I forgot to Cc him. :)

Cheers,
-- 
PEB

Message #90 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Jonas Meurer <jonas@freesources.org>,799281@bugs.debian.org

Cc: barry@debian.org,mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Thu, 07 Sep 2017 12:37:07 +0200

Le 7 septembre 2017 12:27:27 GMT+02:00, Jonas Meurer <jonas@freesources.org> a écrit :
>Hi Pierre-Ellioth,
>
>On Thu, 17 Aug 2017 10:15:46 +0200 Pierre-Elliott Bécue wrote:
>> >I think you forgot to CC barry in your update. His mail id is
>nowhere
>> >to be seen.
>> >
>> >Anyways, would be nice to see mailman 3.1 in Debian soonish.
>> >
>> >Looking forward to seeing it.
>> 
>> I bounced to him after sending the email and realizing that I forgot
>to Cc him. :)
>
>Are there any news regarding mailman 3.1 Debian packages? I see that
>you
>have preliminary packages for most parts of mailman3 at [1], but none
>of
>them was uploaded to Debian yet, right?
>
>Did you hear anything from Barry recently regarding uploading the
>packages?
>
>I also gave the 'mailman3-core' package a quick try and realized that
>it
>still has some rough edges. First issues I spotted were:
>
>* According to 'mailman info', mailman3-core uses '/root/var/' as
>prefix
>  for its paths. That seems to be wrong. In particular config and DB
>  paths are wrong:
>
>  # mailman info
>  [...]
>  config file: /root/var/etc/mailman.cfg
>  db url: sqlite:////root/var/data/mailman.db
>
>* Also, the expected var dir at '/var/lib/mailman3' and the log file at
>  '/var/log/mailman3.log' don't exist after package installation.
>
>
>If you give me a quick heads-up, I might find time to take a deeper
>look
>into your packages and help a bit.
>
>Cheers,
> jonas

Dear Jonas,

I have some news.

Mattia (mapreri on IRC) gave me a first review of my package with plenty small fixes to apply. I didn't have time until now because of some deadlines in my PhD work.

I'll jump back in at the end of the week.

Barry was in the middle of a rush AFAIR, and for now I got little news.

Cheers,
-- 
PEB

Message #95 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jonas Meurer <jonas@freesources.org>

To: 799281@bugs.debian.org, Pierre-Elliott Bécue <becue@crans.org>

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Thu, 7 Sep 2017 12:27:27 +0200

[Message part 1 (text/plain, inline)]

Hi Pierre-Ellioth,

On Thu, 17 Aug 2017 10:15:46 +0200 Pierre-Elliott Bécue wrote:
> >I think you forgot to CC barry in your update. His mail id is nowhere
> >to be seen.
> >
> >Anyways, would be nice to see mailman 3.1 in Debian soonish.
> >
> >Looking forward to seeing it.
> 
> I bounced to him after sending the email and realizing that I forgot to Cc him. :)

Are there any news regarding mailman 3.1 Debian packages? I see that you
have preliminary packages for most parts of mailman3 at [1], but none of
them was uploaded to Debian yet, right?

Did you hear anything from Barry recently regarding uploading the packages?

I also gave the 'mailman3-core' package a quick try and realized that it
still has some rough edges. First issues I spotted were:

* According to 'mailman info', mailman3-core uses '/root/var/' as prefix
  for its paths. That seems to be wrong. In particular config and DB
  paths are wrong:

  # mailman info
  [...]
  config file: /root/var/etc/mailman.cfg
  db url: sqlite:////root/var/data/mailman.db

* Also, the expected var dir at '/var/lib/mailman3' and the log file at
  '/var/log/mailman3.log' don't exist after package installation.


If you give me a quick heads-up, I might find time to take a deeper look
into your packages and help a bit.

Cheers,
 jonas

[signature.asc (application/pgp-signature, attachment)]

Message #100 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jonas Meurer <jonas@freesources.org>

To: Pierre-Elliott Bécue <becue@crans.org>, 799281@bugs.debian.org

Cc: barry@debian.org, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Thu, 7 Sep 2017 12:55:47 +0200

[Message part 1 (text/plain, inline)]

Am 07.09.2017 um 12:37 schrieb Pierre-Elliott Bécue:
> Le 7 septembre 2017 12:27:27 GMT+02:00, Jonas Meurer <jonas@freesources.org> a écrit :
>> Hi Pierre-Ellioth,
>>
>> On Thu, 17 Aug 2017 10:15:46 +0200 Pierre-Elliott Bécue wrote:
>>>> I think you forgot to CC barry in your update. His mail id is
>> nowhere
>>>> to be seen.
>>>>
>>>> Anyways, would be nice to see mailman 3.1 in Debian soonish.
>>>>
>>>> Looking forward to seeing it.
>>>
>>> I bounced to him after sending the email and realizing that I forgot
>> to Cc him. :)
>>
>> Are there any news regarding mailman 3.1 Debian packages? I see that
>> you
>> have preliminary packages for most parts of mailman3 at [1], but none
>> of
>> them was uploaded to Debian yet, right?
>>
>> Did you hear anything from Barry recently regarding uploading the
>> packages?
>>
>> I also gave the 'mailman3-core' package a quick try and realized that
>> it
>> still has some rough edges. First issues I spotted were:
>>
>> * According to 'mailman info', mailman3-core uses '/root/var/' as
>> prefix
>>  for its paths. That seems to be wrong. In particular config and DB
>>  paths are wrong:
>>
>>  # mailman info
>>  [...]
>>  config file: /root/var/etc/mailman.cfg
>>  db url: sqlite:////root/var/data/mailman.db
>>
>> * Also, the expected var dir at '/var/lib/mailman3' and the log file at
>>  '/var/log/mailman3.log' don't exist after package installation.
>>
>>
>> If you give me a quick heads-up, I might find time to take a deeper
>> look
>> into your packages and help a bit.
>>
>> Cheers,
>> jonas
> 
> Dear Jonas,
> 
> I have some news.
> 
> Mattia (mapreri on IRC) gave me a first review of my package with plenty small fixes to apply. I didn't have time until now because of some deadlines in my PhD work.
> 
> I'll jump back in at the end of the week.
> 
> Barry was in the middle of a rush AFAIR, and for now I got little news.

Hi Pierre-Elliott,

that's great to hear. I'll wait for your fixes and give the packages
another try afterwards. Just drop me a note and I'll do further review.

Cheers,
 jonas

[signature.asc (application/pgp-signature, attachment)]

Message #105 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jonas Meurer <jonas@freesources.org>

To: Pierre-Elliott Bécue <becue@crans.org>, 799281@bugs.debian.org, barry@debian.org

Cc: mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Wed, 20 Sep 2017 18:53:50 +0200

[Message part 1 (text/plain, inline)]

Hey PEB, hey Barry,


Am 07.09.2017 um 12:55 schrieb Jonas Meurer:
> Am 07.09.2017 um 12:37 schrieb Pierre-Elliott Bécue:
>> I have some news.
>>
>> Mattia (mapreri on IRC) gave me a first review of my package>> with plenty small fixes to apply. I didn't have time until
>> now because of some deadlines in my PhD work.

Hope that your PhD work is going well.

>> I'll jump back in at the end of the week.
>>
>> Barry was in the middle of a rush AFAIR, and for now I got little news.
> 
> that's great to hear. I'll wait for your fixes and give the packages
> another try afterwards. Just drop me a note and I'll do further review.

I found some time to work on mailman3-core and mailmanclient packages
during the last days. You find the latest packaging status in the repos at

https://github.com/P-EB/mailman3-core
https://anonscm.debian.org/cgit/python-modules/packages/mailmanclient.git/

In my eyes the mailman3-core and mailmanclient packages are in shape for
getting uploaded by now (hyperkitty & postorius still need some love).

@barry: I could do the uploads but as you're PEB's sponsor so far you
might want to do that yourself. Maybe you also want to review the latest
changes to the packages? That would be awesome.

In any case, let me know what procedure you prefer. I'll wait for PEB's
and your feedback before any further steps.

Cheers,
 jonas

[signature.asc (application/pgp-signature, attachment)]

Message #110 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Jonas Meurer <jonas@freesources.org>, 799281@bugs.debian.org

Cc: barry@debian.org, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Thu, 21 Sep 2017 11:36:29 +0200

[Message part 1 (text/plain, inline)]

Le mercredi 20 septembre 2017 à 18:53:50+0200, Jonas Meurer a écrit :
> Hey PEB, hey Barry,
> 
> 
> Am 07.09.2017 um 12:55 schrieb Jonas Meurer:
> > Am 07.09.2017 um 12:37 schrieb Pierre-Elliott Bécue:
> >> I have some news.
> >>
> >> Mattia (mapreri on IRC) gave me a first review of my package>> with plenty small fixes to apply. I didn't have time until
> >> now because of some deadlines in my PhD work.
> 
> Hope that your PhD work is going well.
> 
> >> I'll jump back in at the end of the week.
> >>
> >> Barry was in the middle of a rush AFAIR, and for now I got little news.
> > 
> > that's great to hear. I'll wait for your fixes and give the packages
> > another try afterwards. Just drop me a note and I'll do further review.
> 
> I found some time to work on mailman3-core and mailmanclient packages
> during the last days. You find the latest packaging status in the repos at
> 
> https://github.com/P-EB/mailman3-core
> https://anonscm.debian.org/cgit/python-modules/packages/mailmanclient.git/
> 
> In my eyes the mailman3-core and mailmanclient packages are in shape for
> getting uploaded by now (hyperkitty & postorius still need some love).
> 
> @barry: I could do the uploads but as you're PEB's sponsor so far you
> might want to do that yourself. Maybe you also want to review the latest
> changes to the packages? That would be awesome.
> 
> In any case, let me know what procedure you prefer. I'll wait for PEB's
> and your feedback before any further steps.

Hey,

I dived in your changes.

For d/README.source, I changed the build method to put sbuild, as I never
worked out a proper solution to build with gbp, and as sbuild fits properly
for my needs. You can edit the file again if you wish, but in that case I'd
need some hints on what is going wrong on my server. ^^

Your changes induced some lintian warnings, I can take the time to fix them,
but maybe you'd be more efficient to do so.

C/P of the lintian warnings:
W: mailman3-core-doc: privacy-breach-generic
usr/share/doc/mailman3-core-doc/html/README.html
(https://gitlab.com/mailman/mailman/badges/master/build.svg)
N: 
N:    This package creates a potential privacy breach by fetching data from
an
N:    external website at runtime. Please remove these scripts or external
N:    HTML resources.
N:    
N:    Please replace any scripts, images, or other remote resources with
N:    non-remote resources. It is preferable to replace them with text and
N:    links but local copies of the remote resources are also acceptable as
N:    long as they don't also make calls to remote services. Please ensure
N:    that the remote resources are suitable for Debian main before making
N:    local copies of them.
N:    
N:    Severity: important, Certainty: wild-guess
N:    
N:    Check: files, Type: binary, udeb
N: 
W: mailman3-core-doc: privacy-breach-generic
usr/share/doc/mailman3-core-doc/html/README.html
(https://readthedocs.org/projects/mailman/badge)
W: mailman3-core-doc: privacy-breach-generic
usr/share/doc/mailman3-core-doc/html/README.html
(http://img.shields.io/pypi/v/mailman.svg)
W: mailman3-core-doc: privacy-breach-generic
usr/share/doc/mailman3-core-doc/html/README.html
(http://img.shields.io/pypi/dm/mailman.svg)

In the documentation package, your changes reintroduced the many layers of
directories before the documentation files, e.g.
./usr/share/doc/mailman3-core-doc/html/src/mailman/commands/docs/withlist.html

I had found a way to remove the src/mailman that is useless. Is there a way
to keep the .rst files as you did and mangle a bit the paths?

Otherwise, I still have to implement some suggestions of Mattia. In
particular the ones regarding the owner/group of the installed files, he
suggests we use a postinst script to set the owner appropriately.

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #115 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Jonas Meurer <jonas@freesources.org>

Cc: Pierre-Elliott Bécue <becue@crans.org>, 799281@bugs.debian.org, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Thu, 21 Sep 2017 20:08:30 -0400

[Message part 1 (text/plain, inline)]

Hi guys, apologies for not responding earlier.  I have taken a break from Debian development, so I am not reading my @debian.org email much these days:

https://lists.debian.org/debian-python/2017/08/msg00107.html

That said...

> On Sep 20, 2017, at 12:53, Jonas Meurer <jonas@freesources.org> wrote:

> @barry: I could do the uploads but as you're PEB's sponsor so far you
> might want to do that yourself. Maybe you also want to review the latest
> changes to the packages? That would be awesome.

Jonas, Mattia, thank you very much for working with PEB, and thanks to PEB for being so diligent about getting Mailman 3 into Debian!  I wholeheartedly support your sponsorship of these packages while I am on hiatus.

I did a quick review of the core package, and noticed just a few things:

d/copyright should really go back to 1998.  Even though Mailman 3 was forked from Mailman 2 only in the last few years, there’s enough code inherited from the early days to warrant the earlier copyright start year.

In d/tests/mailman3-core-tests, what do you think about using `python3 -m nose2` instead of `nose2-3`?

Another interesting integration test might be to start up MM3’s REST API and GET the /3.1/system/versions resource, then either print the JSON or compare its value to something expected.  It’s at least a minimal sniff test that some runners could be started up.

If and when you get a real manpage, please write it in reST, convertible via rst2man and contribute it back upstream!

autopkgtest fails for me with:

After this operation, 159 MB of additional disk space will be used.
Err:1 http://httpredir.debian.org/debian sid/main amd64 python3-falcon amd64 1.0.0-2+b1
  404  Not Found
E: Failed to fetch http://httpredir.debian.org/debian/pool/main/p/python-falcon/python3-falcon_1.0.0-2+b1_amd64.deb  404  Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
autopkgtest [20:07:28]: ERROR: testbed failure: apt repeatedly failed to download packages

Didn’t try to debug that.  Building the package locally works and makes lintian happy.  Didn’t try to install it.

Everything else LGTM!

[signature.asc (application/pgp-signature, attachment)]

Message #120 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Barry Warsaw <barry@debian.org>

Cc: Jonas Meurer <jonas@freesources.org>, 799281@bugs.debian.org, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Fri, 22 Sep 2017 11:30:22 +0200

[Message part 1 (text/plain, inline)]

Le jeudi 21 septembre 2017 à 20:08:30-0400, Barry Warsaw a écrit :
> Hi guys, apologies for not responding earlier.  I have taken a break from Debian development, so I am not reading my @debian.org email much these days:
> 
> https://lists.debian.org/debian-python/2017/08/msg00107.html
> 
> That said...
> 
> > On Sep 20, 2017, at 12:53, Jonas Meurer <jonas@freesources.org> wrote:
> 
> > @barry: I could do the uploads but as you're PEB's sponsor so far you
> > might want to do that yourself. Maybe you also want to review the latest
> > changes to the packages? That would be awesome.
> 
> Jonas, Mattia, thank you very much for working with PEB, and thanks to PEB for being so diligent about getting Mailman 3 into Debian!  I wholeheartedly support your sponsorship of these packages while I am on hiatus.
> 
> I did a quick review of the core package, and noticed just a few things:
> 
> d/copyright should really go back to 1998.  Even though Mailman 3 was forked from Mailman 2 only in the last few years, there’s enough code inherited from the early days to warrant the earlier copyright start year.

Done!

> In d/tests/mailman3-core-tests, what do you think about using `python3 -m nose2` instead of `nose2-3`?

As I wasn't able to have working tests for this package, they're disabled in
d/rules. Maybe I just should remove this file.

> Another interesting integration test might be to start up MM3’s REST API and GET the /3.1/system/versions resource, then either print the JSON or compare its value to something expected.  It’s at least a minimal sniff test that some runners could be started up.

I think this requires more background on mailman3 functionnalities that I
currently have. Maybe I'll set this suggestion in debian/TODO for later!

> If and when you get a real manpage, please write it in reST, convertible via rst2man and contribute it back upstream!

Sure!

> autopkgtest fails for me with:
> 
> After this operation, 159 MB of additional disk space will be used.
> Err:1 http://httpredir.debian.org/debian sid/main amd64 python3-falcon amd64 1.0.0-2+b1
>   404  Not Found
> E: Failed to fetch http://httpredir.debian.org/debian/pool/main/p/python-falcon/python3-falcon_1.0.0-2+b1_amd64.deb  404  Not Found
> E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
> autopkgtest [20:07:28]: ERROR: testbed failure: apt repeatedly failed to download packages

I guess I'm not able to do such test myself.

Thanks for your time!

Cheers,

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #125 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Barry Warsaw <barry@debian.org>

Cc: Jonas Meurer <jonas@freesources.org>, 799281@bugs.debian.org, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Fri, 22 Sep 2017 15:28:21 +0200

[Message part 1 (text/plain, inline)]

Le vendredi 22 septembre 2017 à 11:30:22+0200, Pierre-Elliott Bécue a écrit :
> Le jeudi 21 septembre 2017 à 20:08:30-0400, Barry Warsaw a écrit :
> > Hi guys, apologies for not responding earlier.  I have taken a break from Debian development, so I am not reading my @debian.org email much these days:
> > 
> > https://lists.debian.org/debian-python/2017/08/msg00107.html
> > 
> > That said...
> > 
> > > On Sep 20, 2017, at 12:53, Jonas Meurer <jonas@freesources.org> wrote:
> > 
> > > @barry: I could do the uploads but as you're PEB's sponsor so far you
> > > might want to do that yourself. Maybe you also want to review the latest
> > > changes to the packages? That would be awesome.
> > 
> > Jonas, Mattia, thank you very much for working with PEB, and thanks to PEB for being so diligent about getting Mailman 3 into Debian!  I wholeheartedly support your sponsorship of these packages while I am on hiatus.
> > 
> > I did a quick review of the core package, and noticed just a few things:
> > 
> > d/copyright should really go back to 1998.  Even though Mailman 3 was forked from Mailman 2 only in the last few years, there’s enough code inherited from the early days to warrant the earlier copyright start year.
> 
> Done!
> 
> > In d/tests/mailman3-core-tests, what do you think about using `python3 -m nose2` instead of `nose2-3`?
> 
> As I wasn't able to have working tests for this package, they're disabled in
> d/rules. Maybe I just should remove this file.
> 
> > Another interesting integration test might be to start up MM3’s REST API and GET the /3.1/system/versions resource, then either print the JSON or compare its value to something expected.  It’s at least a minimal sniff test that some runners could be started up.
> 
> I think this requires more background on mailman3 functionnalities that I
> currently have. Maybe I'll set this suggestion in debian/TODO for later!
> 
> > If and when you get a real manpage, please write it in reST, convertible via rst2man and contribute it back upstream!
> 
> Sure!
> 
> > autopkgtest fails for me with:
> > 
> > After this operation, 159 MB of additional disk space will be used.
> > Err:1 http://httpredir.debian.org/debian sid/main amd64 python3-falcon amd64 1.0.0-2+b1
> >   404  Not Found
> > E: Failed to fetch http://httpredir.debian.org/debian/pool/main/p/python-falcon/python3-falcon_1.0.0-2+b1_amd64.deb  404  Not Found
> > E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
> > autopkgtest [20:07:28]: ERROR: testbed failure: apt repeatedly failed to download packages
> 
> I guess I'm not able to do such test myself.
> 
> Thanks for your time!
> 
> Cheers,

Hi,

From now on, the mailman3-core git repository is on alioth, under
pkg-mailman repository.

As soon as the server is up to date, one will be able to find the repository
on https://anonscm.debian.org/git/pkg-mailman/mailman3-core.git

The github one stays for now, but one day or another I'll drop it.

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #130 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Pierre-Elliott Bécue <becue@crans.org>

Cc: Jonas Meurer <jonas@freesources.org>, 799281@bugs.debian.org, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Fri, 22 Sep 2017 13:51:26 -0400

[Message part 1 (text/plain, inline)]

On Sep 22, 2017, at 09:28, Pierre-Elliott Bécue <becue@crans.org> wrote:
>> 
>>> In d/tests/mailman3-core-tests, what do you think about using `python3 -m nose2` instead of `nose2-3`?
>> 
>> As I wasn't able to have working tests for this package, they're disabled in
>> d/rules. Maybe I just should remove this file.

Can you remember why the test suite doesn’t work in d/rules?

I do think that if they can’t be run in d/rules, they should be run at some point, and autopkgtests are a good alternative.  While that doesn’t block promotion in Debian (yet?) it does in Ubuntu, so there should be good feedback when the autopkgtests fail.

That said, in my own packages I always try to include a few other autopkgtests.  Things like:

* Run the command line (e.g. ``mailman —help``)
* Try to create a simple list
* Do a simple ``mailman shell`` command
* Hit the REST API and just make sure it returns some non-error.

>> Another interesting integration test might be to start up MM3’s REST API and GET the /3.1/system/versions resource, then either print the JSON or compare its value to something expected.  It’s at least a minimal sniff test that some runners could be started up.
>> 
>> I think this requires more background on mailman3 functionnalities that I
>> currently have. Maybe I'll set this suggestion in debian/TODO for later!

+1!  Tests are an investment over time, so just get the bare minimum working now, and it can always be improved.

>> autopkgtest fails for me with:
>>> 
>>> After this operation, 159 MB of additional disk space will be used.
>>> Err:1 http://httpredir.debian.org/debian sid/main amd64 python3-falcon amd64 1.0.0-2+b1
>>>  404  Not Found
>>> E: Failed to fetch http://httpredir.debian.org/debian/pool/main/p/python-falcon/python3-falcon_1.0.0-2+b1_amd64.deb  404  Not Found
>>> E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
>>> autopkgtest [20:07:28]: ERROR: testbed failure: apt repeatedly failed to download packages
>> 
>> I guess I'm not able to do such test myself.

You should be able to build the source package, and then if you have a chroot, just do:

$ autopkgtest mailman-core-blah-blah.dsc — schroot sid-amd64

Cheers,
-Barry

[signature.asc (application/pgp-signature, attachment)]

Message #135 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Barry Warsaw <barry@debian.org>, 799281@bugs.debian.org

Cc: Jonas Meurer <jonas@freesources.org>, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Sat, 23 Sep 2017 00:53:30 +0200

[Message part 1 (text/plain, inline)]

Le vendredi 22 septembre 2017 à 13:51:26-0400, Barry Warsaw a écrit :
> On Sep 22, 2017, at 09:28, Pierre-Elliott Bécue <becue@crans.org> wrote:
> >> 
> >>> In d/tests/mailman3-core-tests, what do you think about using `python3 -m nose2` instead of `nose2-3`?
> >> 
> >> As I wasn't able to have working tests for this package, they're disabled in
> >> d/rules. Maybe I just should remove this file.
> 
> Can you remember why the test suite doesn’t work in d/rules?
> 
> I do think that if they can’t be run in d/rules, they should be run at some point, and autopkgtests are a good alternative.  While that doesn’t block promotion in Debian (yet?) it does in Ubuntu, so there should be good feedback when the autopkgtests fail.

As far as I remember, at that time, it was trying to run a server but didn't
find the binary as it was not at the appropriate path.

Now, when I run the tests, there are a lot of errors, but I can't say
exactly why. If you wish I can put a copy of the last attempt.

> That said, in my own packages I always try to include a few other autopkgtests.  Things like:
>
> * Run the command line (e.g. ``mailman —help``)
> * Try to create a simple list
> * Do a simple ``mailman shell`` command
> * Hit the REST API and just make sure it returns some non-error.
> 
> >> Another interesting integration test might be to start up MM3’s REST API and GET the /3.1/system/versions resource, then either print the JSON or compare its value to something expected.  It’s at least a minimal sniff test that some runners could be started up.
> >> 
> >> I think this requires more background on mailman3 functionnalities that I
> >> currently have. Maybe I'll set this suggestion in debian/TODO for later!
> 
> +1!  Tests are an investment over time, so just get the bare minimum working now, and it can always be improved.

Yeah, especially as having the package into unstable will allow for some
feedback!

> >> autopkgtest fails for me with:
> >>> 
> >>> After this operation, 159 MB of additional disk space will be used.
> >>> Err:1 http://httpredir.debian.org/debian sid/main amd64 python3-falcon amd64 1.0.0-2+b1
> >>>  404  Not Found
> >>> E: Failed to fetch http://httpredir.debian.org/debian/pool/main/p/python-falcon/python3-falcon_1.0.0-2+b1_amd64.deb  404  Not Found
> >>> E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
> >>> autopkgtest [20:07:28]: ERROR: testbed failure: apt repeatedly failed to download packages
> >> 
> >> I guess I'm not able to do such test myself.
> 
> You should be able to build the source package, and then if you have a chroot, just do:
> 
> $ autopkgtest mailman-core-blah-blah.dsc — schroot sid-amd64

Hm, I'll have a shot at some point!

Cheers,

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #140 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: Pierre-Elliott Bécue <becue@crans.org>

Cc: 799281@bugs.debian.org, Jonas Meurer <jonas@freesources.org>, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Fri, 22 Sep 2017 18:57:00 -0400

[Message part 1 (text/plain, inline)]

On Sep 22, 2017, at 18:53, Pierre-Elliott Bécue <becue@crans.org> wrote:

> Now, when I run the tests, there are a lot of errors, but I can't say
> exactly why. If you wish I can put a copy of the last attempt.

Sure, post a link.  I’ll let you know if I see anything obvious.

-B

[signature.asc (application/pgp-signature, attachment)]

Message #145 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Pierre-Elliott Bécue <becue@crans.org>

To: Barry Warsaw <barry@debian.org>, 799281@bugs.debian.org

Cc: Jonas Meurer <jonas@freesources.org>, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Sat, 23 Sep 2017 01:13:44 +0200

[Message part 1 (text/plain, inline)]

Le vendredi 22 septembre 2017 à 18:57:00-0400, Barry Warsaw a écrit :
> On Sep 22, 2017, at 18:53, Pierre-Elliott Bécue <becue@crans.org> wrote:
> 
> > Now, when I run the tests, there are a lot of errors, but I can't say
> > exactly why. If you wish I can put a copy of the last attempt.
> 
> Sure, post a link.  I’ll let you know if I see anything obvious.

https://peb.pimeys.fr/packages/mailman/mailman3-core/mailman3-core_3.1.0-1_amd64-2017-09-22T09:25:55Z.build

There you are, I did SIGINT before the end because it was kind of frozen.

-- 
PEB

[signature.asc (application/pgp-signature, inline)]

Message #150 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jonas Meurer <jonas@freesources.org>

To: 799281@bugs.debian.org, Pierre-Elliott Bécue <becue@crans.org>, Barry Warsaw <barry@debian.org>, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Sat, 23 Sep 2017 12:19:53 +0200

[Message part 1 (text/plain, inline)]

Am 23.09.2017 um 01:13 schrieb Pierre-Elliott Bécue:
> Le vendredi 22 septembre 2017 à 18:57:00-0400, Barry Warsaw a écrit :
>> On Sep 22, 2017, at 18:53, Pierre-Elliott Bécue <becue@crans.org> wrote:
>>
>>> Now, when I run the tests, there are a lot of errors, but I can't say
>>> exactly why. If you wish I can put a copy of the last attempt.
>>
>> Sure, post a link.  I’ll let you know if I see anything obvious.
> 
> https://peb.pimeys.fr/packages/mailman/mailman3-core/mailman3-core_3.1.0-1_amd64-2017-09-22T09:25:55Z.build
> 
> There you are, I did SIGINT before the end because it was kind of frozen.

The reason for the tests failing is that some tests expect the programs
(master, runner, ...) at /usr/bin while we install them at
/usr/lib/mailman3/bin. And the tests hang forever because they wait for
the daemon to appear/disappear:

test_unregister_a_non_registered_style
(mailman.styles.tests.test_styles.TestStyle) ... /usr/bin/python3.6:
can't open file '/usr/bin/runner': [Errno 2] No such file or directory
/usr/bin/python3.6: can't open file '/usr/bin/runner': [Errno 2] No such
file or directory

I already tried setting MAILMAN_EXTRA_TESTING_CFG in debian/rules:

MAILMAN_EXTRA_TESTING_CFG=./debian/contrib/mailman.cfg

But apparently that doesn't help. Any idea how to make the tests search
the programs in the right place?

My latest try was (in debian/rules):

override_dh_auto_test:
        set -e; \
        for python in $(shell py3versions -r); do \
                MAILMAN_EXTRA_TESTING_CFG=./debian/contrib/mailman.cfg \
                PYTHONPATH="." $$python -m nose2 --verbose; \
        done


Here's the result:
https://people.debian.org/~mejo/mailman3-core_3.1.0-1_amd64-2017-09-23T10:06:41Z.build

Cheers
 jonas

[signature.asc (application/pgp-signature, attachment)]

Message #155 received at 799281@bugs.debian.org (full text, mbox, reply):

From: Jonas Meurer <jonas@freesources.org>

To: Barry Warsaw <barry@debian.org>, 799281@bugs.debian.org

Cc: Pierre-Elliott Bécue <becue@crans.org>, mattia@debian.org

Subject: Re: Bug#799281: ITP: mailman3-core -- Mailing list management system

Date: Tue, 26 Sep 2017 18:17:29 +0200

Hi Barry,

Am 22.09.2017 um 02:08 schrieb Barry Warsaw:
> Hi guys, apologies for not responding earlier.  I have taken a break from Debian development, so I am not reading my @debian.org email much these days:
> 
> https://lists.debian.org/debian-python/2017/08/msg00107.html
> 
> That said...

no worries. It's great that you clearly communicated your decision to
the teams you're involved and I very well can understand it. Hope that
you feel joy and pleasure soon again while doing Debian stuff :)

>> On Sep 20, 2017, at 12:53, Jonas Meurer <jonas@freesources.org> wrote:
> 
>> @barry: I could do the uploads but as you're PEB's sponsor so far you
>> might want to do that yourself. Maybe you also want to review the latest
>> changes to the packages? That would be awesome.
> 
> Jonas, Mattia, thank you very much for working with PEB, and thanks to PEB for being so diligent about getting Mailman 3 into Debian!  I wholeheartedly support your sponsorship of these packages while I am on hiatus.
> 
> I did a quick review of the core package, and noticed just a few things:

Thanks a lot for your review. It's much appreciated and of great help!
I'll only comment on the things PEB didn't comment on yet.

> In d/tests/mailman3-core-tests, what do you think about using `python3 -m nose2` instead of `nose2-3`?
> 
> Another interesting integration test might be to start up MM3’s REST API and GET the /3.1/system/versions resource, then either print the JSON or compare its value to something expected.  It’s at least a minimal sniff test that some runners could be started up.

As discussed in upstream issue #400[1], there seems to be no easy
solution to run the nose2 testsuite - neither during build in
debian/rules, nor with the package being installed via autopkgtests.

Thus I finally decided to go with two other simple tests, as you suggested:

* create a simple test list
* fetch http://localhost:8001/3.1/system/versions via curl

[1] https://gitlab.com/mailman/mailman/issues/400

Cheers,
 jonas

Message #160 received at 799281-close@bugs.debian.org (full text, mbox, reply):

From: Jonas Meurer <mejo@debian.org>

To: 799281-close@bugs.debian.org

Subject: Bug#799281: fixed in mailman3-core 3.1.0-1

Date: Thu, 05 Oct 2017 10:00:17 +0000

Source: mailman3-core
Source-Version: 3.1.0-1

We believe that the bug you reported is fixed in the latest version of
mailman3-core, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 799281@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Meurer <mejo@debian.org> (supplier of updated mailman3-core package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 28 Sep 2017 15:30:50 +0200
Source: mailman3-core
Binary: mailman3-core mailman3-core-doc
Architecture: source all
Version: 3.1.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Mailman Team <pkg-mailman-hackers@lists.alioth.debian.org>
Changed-By: Jonas Meurer <mejo@debian.org>
Description:
 mailman3-core - Mailing list management system
 mailman3-core-doc - Mailing list management system documentation
Closes: 799281
Changes:
 mailman3-core (3.1.0-1) unstable; urgency=low
 .
   [ Pierre-Elliott Bécue ]
   * Initial release (Closes: #799281)
Checksums-Sha1:
 ad1b13290136600b6fd64c8c7fbe232ef3364912 2780 mailman3-core_3.1.0-1.dsc
 6d297e84c0593d59b51c7aa16f3461a76bfc3b58 739076 mailman3-core_3.1.0.orig.tar.gz
 806997970bc605257898319e31c1a0f8fd50fc25 801 mailman3-core_3.1.0.orig.tar.gz.asc
 7ee535714c8907886b614c9254a8e6eb9028a0cf 40992 mailman3-core_3.1.0-1.debian.tar.xz
 07870a2fc5c2f5d5e67c4bcf6cd98377d9d7c250 356578 mailman3-core-doc_3.1.0-1_all.deb
 d93277ea1a836661c4ba9b3d54bb93c60c239265 560642 mailman3-core_3.1.0-1_all.deb
 221f2e34666934479f404a4b590595942cc8678f 8178 mailman3-core_3.1.0-1_amd64.buildinfo
Checksums-Sha256:
 e4c21a44729ff3d9877a3b505dd1dbe50278e2cb692d3f8f4b2ce18a704526df 2780 mailman3-core_3.1.0-1.dsc
 4d206d40dfa1477f1cedb6e618ef9963bd187ac99fd4e7835c943a1d75dbc374 739076 mailman3-core_3.1.0.orig.tar.gz
 7dbdd8f94472f15444fca3091f0d3a03a213aa0f3531d8727058f7066bff4f03 801 mailman3-core_3.1.0.orig.tar.gz.asc
 a847977deb78a24c3c9593a8e5e3050ff73204d574daa4bdc855fac04ed7af8a 40992 mailman3-core_3.1.0-1.debian.tar.xz
 56c4f72c2742ed44357905ed0b4cc26c81d4758b831dfc198109f0e7ce6880d5 356578 mailman3-core-doc_3.1.0-1_all.deb
 eb7ae0c485bd6c090f0d91b02d32fe4d3ccfa3e74e498389a353eedeb62ee1cc 560642 mailman3-core_3.1.0-1_all.deb
 4a99792d98b5308d90f7eac435efbc22a49c8728cc9fe851fe8031c5ca61370a 8178 mailman3-core_3.1.0-1_amd64.buildinfo
Files:
 e054e0d378a9f4b31623ee45dcb50164 2780 mail optional mailman3-core_3.1.0-1.dsc
 de6280cec617b6df40db0f6e315a241a 739076 mail optional mailman3-core_3.1.0.orig.tar.gz
 0a111a4fd432bb8fcf417c1d8ca0bf2e 801 mail optional mailman3-core_3.1.0.orig.tar.gz.asc
 1c7453654fb53e33eadc381ac3acbfc3 40992 mail optional mailman3-core_3.1.0-1.debian.tar.xz
 34e47a4b6494d82698194164282bb47b 356578 doc optional mailman3-core-doc_3.1.0-1_all.deb
 a28278b6a6a8511c53c8e31b87569e53 560642 mail optional mailman3-core_3.1.0-1_all.deb
 0e0044579dc6786879cddb431a8d9963 8178 mail optional mailman3-core_3.1.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEELIzSg9Pv30M4kOeDUmLn/0kQSf4FAlnNHPkACgkQUmLn/0kQ
Sf6law/+MwAbD445ZFJGkT1Tin1zaOcjJZjPy+n0QJe4YQ4RFRgSLKf7VyqcFIsc
hSwIxcRnv6T9pd/cArzkjWjEoxmKKbjydl3/Tn8txdzIDTZeTj2f3fkpcp2nP3m3
By71y2igdWfqueDSmLnXzj/5BxHlqL4csxqYzinaw+pN/T3guk5nFhPyu+08eNQd
LvtZV265Vi5vz4Aqj+2LfEidSLMVQbczVwaxTPF+mJBnbryipBm3TxN/Lw7p5PZS
AnKJPvBnmbxvhatnXcApYMcJ74YL+2DaXv+RkXu8l76O0wB90/Wf+3fAdyGE8Qgo
5/wp/4ybU6IafJ9/TOvi0T2uoULA1ST8cwARKSKjlfgScQT5Fj7FrdbZiW0yFKUj
KdjfkKXLc5kFZaxH3VAkb5Dxwn5Q/s5G1NSxp84kdAx6AvQ5DjH8IO7eDdY3Zc+Z
iqYJdJlCZvkpUQPQnF/Gg1QQY6z9p+rUh4+4XEPQA5y+sqclK5EidmswfO4QyN44
bYWPN2b9SMkiDNSSWte4fBs55EJC65WgzTyQmHrN73eFPJz/c0/FpoGsLHJDijtt
7y6eVnQLOgg+iV1mo1/mnu7rijhal5zop9LiqAlnEkWUteZGBDZ3e1Iz0IhL5wG6
h9Zz77FLKsXGh3NHQ6mLSUoahEhUVpeBJoSFRUnGHDAKMnkCIfg=
=dOtI
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.