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 )
- currently running 2.1.20 (released in 2015) on osgeo6
- upgrade will help us with a few tickets (such as #2123)
- recent changes https://launchpad.net/mailman/+milestone/2.1.27
- download http://ftp.gnu.org/gnu/mailman/
Change History (9)
comment:1 by , 6 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 4 years ago
| Milestone: | → Sysadmin Contract 2020-II |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:3 by , 4 years ago
| Cc: | added |
|---|
comment:4 by , 4 years ago
| Keywords: | mailman added |
|---|
No idea why this was done (and I cannot imagine a reason). I scanned the old "mailman" tickets:
(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 , 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 , 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:
- Find another .deb which works on that version of Debian
- Build another .deb which works on that version of Debian
- Stop using apt and move to manually built Mailman
- 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 , 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 , 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 , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
| Summary: | Upgrade Mailman version to recent 2.1.27 release → Upgrade Mailman version to recent release |
The manually built 2.1.34 package of Mailman is now installed.
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 ?