After dozens of reviews by the security team, we are ending the MIR for
mailman3 and the enormous list of dependencies due to the complexity of
the package, difficulties maintaining, and security concerns. mailman3
will live in universe.
** Changed in: mailman3 (Ubuntu)
Assignee: Ubuntu
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
** Tags added: py2-demotion py2-removal
** Changed in: mailman3 (Ubuntu)
Importance: Undecided => Critical
** Changed in: mailman3 (Ubuntu)
Milestone: None => ubuntu-19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
Setting mailman to Triaged; let's get this off the "New MIRs" list --
it's not new, just not completed yet. mailman3's status nicely captures
this.
** Changed in: mailman (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Completed the review on the remaining pytohn libs, overall the remaining TODOs
are some tasks for the server Team (breakign dependencies), a lot of security
reviews, but also 5 tasks for the MIR team.
Those split into 3 discussion and 2 package reviews.
As discussed I'll bring those up on next
Updates for completing python-arrow python-blessed python-public and
python-uritemplate
Some new non blocking but recommended tasks added, as usual marked in the
overview and details can be found in the respective bugs.
** Description changed:
[Availability]
The package is already universe
[Duplication]
This is part of the six core packages of mailman3 that pull in further
components as needed.
Since this represents mailman doing mailing list processing there is a
duplication to mailman2.
But the intention is to stop seeding mailman2 as soon as mailman3 got promoted.
[Embedded
Updated for the complete of the MIR review on main mailman3 components:
hyperkitty, mailman* and postorious
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775427
Title:
[MIR] mailman3 to replace
Updated for MIR review of coreapi coreschema robot-detection and wcwidth
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This
zeromq ftbfs is fixed and there was no explicit reason to demote it, so
we can use the old MIR and consider that one done. Updated the
description.
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example
Updated description after the review of django.* and marking some
packages for Team review already
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
Updated after completion of flufl.* and lazr.* MIR review.
FYI: after discussion with Doko we will discuss in todays MIR team
meeting if/how to distribute further reviews (especially the less
trivial cases) among the team to spread the load as usual, but also not
carry too much of the "self-ack"
MIR review on zope.* done (I start with the easier bits first, to have the
feeling of hope :-) )
Due to their integration into a web stack I marked them in the description and
the respective bugs as waiting for security review.
** Description changed:
[Availability]
The package is already
** Description changed:
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides
Work to cut out more of the dependencies we really don't think to be
approproate (ruby/nodejs) was discussed upstream and started with Debian:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/gbugreport.cgi?bug=924961
The conclusion of this might have
** Description changed:
- TODO - references to all the MIR bug - one per affected package.
+ [Availability]
+ The package is already universe for quite a while and build/works fine so far.
+ It is for example already used for
https://lists.canonical.com/mailman3/postorius/lists/
+
+ This source
** Description changed:
+ TODO - references to all the MIR bug - one per affected package.
+
+ ---
+
mailman is python2, mailman3 is python3, but also it has new dependency
- stack.
+ stack due to adopting django but also splitting or rewriting a lot of
+ its components.
- Do we want
While preparing the MIR bugs for the involved soruces I found that some we
initially detected are already in main pulled in by
python3-django-openstack-auth:
- python3-csscompressor
- python3-django-compressor
- python3-rcssmin
- python3-rjssmin
Dropping those from our list we have to work on
On Mon, Feb 18, 2019 at 11:41 PM Dimitri John Ledkov
wrote:
> Well #is has now deployed mailman3, i think it all should go into main.
Oh yeah Dimitri - decisions are actually made already, there will be a
mass MIR filing (and then processing) hopefully starting this week to
spread the load.
Tthe
Well #is has now deployed mailman3, i think it all should go into main.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775427
Title:
[MIR] mailman3 to replace mailman, or drop mailman to universe
** No longer affects: django-allauth (Ubuntu Disco)
** Also affects: django-allauth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775427
Title:
Existing option left, let mailman[23] go - not my decision thou - might
bring it up on the sprint thou.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775427
Title:
[MIR] mailman3 to replace
Discussed in the Team, and the conclusion is that we have to go the big route
of mailman3-full
Maybe breaking out hyperkitty to a suggests, but that is not helping too much.
I'll update the bug tasks tomorrow and prep a summarized Dependency list
of the planned approach. I will then send a few
** Attachment added: "hyperkitty deps on top of mailman3 and mailman3-web"
https://bugs.launchpad.net/ubuntu/+source/zope.schema/+bug/1775427/+attachment/5219450/+files/mailman3-main-promotion-dependencies-hyperkitty.txt
--
You received this bug notification because you are a member of
To help the discussions to come I isolated the dependencies of mailman3-web
mailman-hyperkitty is very similar.
** Attachment added: "dependencies for mailman3-web which is most of the
superset of extra packages"
Summary (mostly as a working theory for now):
Seeding/Unseeding:
- we would only select and fully support the core mailman3 (to keep things
reviewable and supportable)
- all the web bits pulled in by mailman3-full via mailman3-web and hyperkitty
would not get into main
- once migrated mailman2
Time to get it started, I assume this will accompany us for a while at
least, but we have to start at some point.
Thanks xnox for the initial list of affected packages, but I assume it is much
worse.
I agree that mass-MIR handling is probably the biggest step to take here.
--
You received this
I wanted to eventually file MIRs for all of these and reference the bugs here.
I wondered to drive all in this MIR, but that will break discussions as e.g.
python-flufl and zope are so damn different that doing that in just this bug
will make us loose track too much.
OTOH now that I did the deep
** Attachment added: "dependencies if we "only" select the core mailman3"
https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1775427/+attachment/5219445/+files/mailman3-main-promotion-dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "dependencies if we select the core mailman3-full as one
might expect"
https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1775427/+attachment/5219446/+files/mailman3-main-promotion-dependencies-all.txt
** Also affects: zope.i18nmessageid (Ubuntu)
Importance:
Assigning to Christian for investigation
** Changed in: mailman3 (Ubuntu)
Assignee: David Britton (davidpbritton) => Christian Ehrhardt (paelzer)
** Changed in: mailman (Ubuntu)
Assignee: Joshua Powers (powersj) => (unassigned)
--
You received this bug notification because you are
@powersj I think the biggest blocker would be security reviews of all of
these things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775427
Title:
[MIR] mailman3 to replace mailman, or drop
There is consensus to do this, we need the work broken down to determine
if we can get it all done next cycle or over 2 cycles.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775427
Title:
[MIR]
mailman-suite / mailman3-web should change packaging to launch as
python3, not python2 webapp.
** Also affects: mailman-suite (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@powersj @dpb1 - ping? i thought there was consensus the other day...
** Changed in: mailman (Ubuntu)
Assignee: (unassigned) => Joshua Powers (powersj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mailman3 (Ubuntu)
Assignee: (unassigned) => Don Bennett (dpb)
** Changed in: mailman3 (Ubuntu)
Assignee: Don Bennett (dpb) => David Britton (davidpbritton)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- mailman is python2, but mailman3 is python3, but also it has new
- dependency stack.
+ mailman is python2, mailman3 is python3, but also it has new dependency
+ stack.
Do we want src:mailman3 in main? bin:mailman3 pulls in above listed
dependencies (*)
(*) and
43 matches
Mail list logo
