Opened 6 years ago

Closed 4 years ago

#2174 closed task (fixed)

Upgrade Mailman version to recent release

Reported by: Jeff McKenna Owned by: strk
Priority: normal Milestone: Sysadmin Contract 2020-II
Component: SysAdmin Keywords: mailman
Cc: neteler

Description (last modified by Jeff McKenna)

Change History (9)

comment:1 by Jeff McKenna, 6 years ago

Description: modified (diff)

comment:2 by strk, 4 years ago

Milestone: Sysadmin Contract 2020-II
Owner: changed from sac@… to strk
Status: newassigned

comment:3 by strk, 4 years ago

Cc: neteler added

It looks like the currently installed Mailman version comes from a .deb package which is NOT in the apt repository configured on the machine. Does anyone remember who did the last upgrade ? Markus, any idea ?

comment:4 by neteler, 4 years ago

Keywords: mailman added

No idea why this was done (and I cannot imagine a reason). I scanned the old "mailman" tickets:

https://trac.osgeo.org/osgeo/query?status=assigned&status=closed&status=new&status=reopened&keywords=~mailman&order=priority

(seems Martin S was involved after Frank W, e.g. #1577)

Anyway, I'd suggest to change to a standard apt repo setup.

comment:5 by wildintellect, 4 years ago

It was probably a limitation when the machine's were stuck on an old version of Debian. I think Regina solved that upgrade path in the move to LXD containers.

+1 move to repo based install

comment:6 by strk, 4 years ago

There's no upgrade in apt repos for the current version of Debian on that machine (8), so we're left to these choicese:

  1. Find another .deb which works on that version of Debian
  2. Build another .deb which works on that version of Debian
  3. Stop using apt and move to manually built Mailman
  4. Upgrade Debian to latest (but will still not get us the .30 version of Mailman)

I tend to think 3 would be the best choice

comment:7 by strk, 4 years ago

Newest official debian package for mailman is for 2.1.29 and is targetting debian unstable (10): https://tracker.debian.org/pkg/mailman We're running old-old-stable (8)

comment:8 by strk, 4 years ago

I took approach 2 (build a deb package myself). It's ready for install, just waiting for a backup before proceeding. I packaged 2.1.34 (latest release in the 2.1 branch)

I was thinking we could start using our nexus.osgeo.org repository for storing these deb files, so to have a "proper" apt repository... https://help.sonatype.com/repomanager3/formats/apt-repositories

comment:9 by strk, 4 years ago

Resolution: fixed
Status: assignedclosed
Summary: Upgrade Mailman version to recent 2.1.27 releaseUpgrade Mailman version to recent release

The manually built 2.1.34 package of Mailman is now installed.

Note: See TracTickets for help on using tickets.