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

2017-09-26 Thread Jonas Meurer
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  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



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

2017-09-23 Thread Jonas Meurer
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  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
Description: OpenPGP digital signature


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

2017-09-22 Thread 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  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
Description: PGP signature


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

2017-09-22 Thread Barry Warsaw
On Sep 22, 2017, at 18:53, Pierre-Elliott Bécue  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
Description: Message signed with OpenPGP


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

2017-09-22 Thread Pierre-Elliott Bécue
Le vendredi 22 septembre 2017 à 13:51:26-0400, Barry Warsaw a écrit :
> On Sep 22, 2017, at 09:28, Pierre-Elliott Bécue  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
Description: PGP signature


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

2017-09-22 Thread Barry Warsaw
On Sep 22, 2017, at 09:28, Pierre-Elliott Bécue  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
Description: Message signed with OpenPGP


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

2017-09-22 Thread Pierre-Elliott Bécue
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  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
Description: PGP signature


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

2017-09-22 Thread Pierre-Elliott Bécue
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  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
Description: PGP signature


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

2017-09-21 Thread 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...

> On Sep 20, 2017, at 12:53, Jonas Meurer  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
Description: Message signed with OpenPGP


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

2017-09-21 Thread Pierre-Elliott Bécue
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
Description: PGP signature


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

2017-09-20 Thread Jonas Meurer
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
Description: OpenPGP digital signature


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

2017-09-07 Thread Jonas Meurer
Am 07.09.2017 um 12:37 schrieb Pierre-Elliott Bécue:
> Le 7 septembre 2017 12:27:27 GMT+02:00, Jonas Meurer  
> 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
Description: OpenPGP digital signature


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

2017-09-07 Thread Jonas Meurer
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
Description: OpenPGP digital signature


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

2017-09-07 Thread Pierre-Elliott Bécue
Le 7 septembre 2017 12:27:27 GMT+02:00, Jonas Meurer  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



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

2017-08-17 Thread Pierre-Elliott Bécue
Le 17 août 2017 08:01:57 GMT+02:00, "shirish शिरीष"  a 
écrit :
>at bottom :-
>
>On 12/08/2017, Pierre-Elliott Bécue  wrote:
>
>
>
>> 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



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

2017-08-17 Thread shirish शिरीष
at bottom :-

On 12/08/2017, Pierre-Elliott Bécue  wrote:



> 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



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

2017-08-12 Thread Pierre-Elliott Bécue
Le jeudi 17 septembre 2015 à 16:19:09+0200, Pierre-Elliott Bécue a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: "Pierre-Elliott Bécue" 
> 
> * 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
Description: PGP signature


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

2015-09-17 Thread Pierre-Elliott Bécue
Package: wnpp
Severity: wishlist
Owner: "Pierre-Elliott Bécue" 

* 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