Migration prevented due to "missing dep libssl-dev (>= 3.1.4)"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fetchmail (Ubuntu) |
Fix Released
|
Low
|
Danilo Egea Gondolfo |
Bug Description
fetchmail (6.4.37-1 to 6.4.38-1)
Migration status for fetchmail (6.4.37-1 to 6.4.38-1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
missing build on amd64: fetchmail (from 6.4.37-1)
missing build on arm64: fetchmail (from 6.4.37-1)
missing build on armhf: fetchmail (from 6.4.37-1)
missing build on ppc64el: fetchmail (from 6.4.37-1)
missing build on riscv64: fetchmail (from 6.4.37-1)
missing build on s390x: fetchmail (from 6.4.37-1)
arch:all not built yet, autopkgtest delayed
Additional info:
8 days old
The problem here is that openssl 3.1 is in Debian, however openssl 3.0 is preferred in Ubuntu since 3.0 is upstream's long term support release.
This new fetchmail 6.4.38 upstream release includes no substantive code changes or bug fixes, and in addition to the dependency version updates is mainly comprised of just documentation, translation, copyright date, and project metadata changes, which looks to me not crucial for us to include at this time.
So, given the openssl incompatibility I think we can skip this "6.4.38-1" release, and remove it from -proposed. If a new Debian or upstream release comes out prior to 24.04 release we can re-evaluate if it's worth pulling in (and patching the dependency issue if necessary) at that time.
Related branches
- Bryce Harrington (community): Approve
- git-ubuntu import: Pending requested
-
Diff: 32 lines (+11/-2)2 files modifieddebian/changelog (+8/-0)
debian/control (+3/-2)
tags: | added: update-excuse |
Changed in fetchmail (Ubuntu): | |
status: | New → Incomplete |
Changed in fetchmail (Ubuntu): | |
status: | Incomplete → Fix Committed |
assignee: | nobody → Danilo Egea Gondolfo (danilogondolfo) |
importance: | Undecided → Low |
Well, update SSL before release. It doesn't make sense to ship old
garbage for a release if upstream support with patchlevel updates, as
OpenSSL do.
However you should ship the translation updates -- if and only if Ubuntu
maintain libssl properly, it is feasible to (a) change the support
addresses in fetchmail's documentation, (b) add the GPL-mandated notes
that the code was modified, and (c) take responsibility for support, and
then finally (d) relax the version checks in the source code.
This is normal integration work for a distro, nothing special. Just if
you break it, or the underlying SSL library, I will not support it if
you modified it to work on outdated OpenSSL, which is what 6.4.38
strives to prevent.
(Of course you can also keep older versions in and I will send people
with outdated versions away, if Ubuntu prefer that disservice to
maintainers and community.)