Your message dated Sat, 1 Mar 2025 11:08:10 +0100
with message-id <ba0967f4-9917-4441-9d90-689a76aa1...@debian.org>
and subject line Re: Bug#1094017: transition: poppler
has caused the Debian Bug report #1094017,
regarding transition: poppler
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1094017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: popp...@packages.debian.org
Control: affects -1 + src:poppler
User: release.debian....@packages.debian.org
Usertags: transition
I'd like to update poppler to version 25.01 for Debian 13.
This requires a transition for libraries libpoppler and libpoppler-cpp:
the former gets a SONAME bump with every monthly release, and this time
the -cpp library got bumped too.
I've already checked all rdepends in sid and submitted patches or asked
for packaging new versions of the affected packages which needed source
changes for API differences. This is always handled by #ifdef'ing so
that the same source can compile against either version of the API.
As of today all rdepends from sid can already be binNMU'd except:
* libreoffice: fix is committed in salsa but unreleased
* scribus: there is a new minor version upstream to be packaged: we
would upload this as NMU if the maintainer doesn't in time
* calligra: could not verify the build because it already FTBFS for
different reasons - but it is sid-only so not a blocker
The auto tracker here is correct:
https://release.debian.org/transitions/html/auto-poppler.html
I'm not a maintainer of the poppler package; my point of contact for
help and sponsoring the upload is Jeremy Bícha.
I'm confident we can finish the transition by the transition freeze,
just announced to be 2025-03-15.
Thanks.
Ben file:
title = "poppler";
is_affected = .depends ~ "libpoppler140" | .depends ~ "libpoppler-cpp1"
| .depends ~ "libpoppler145" | .depends ~ "libpoppler-cpp2";
is_good = .depends ~ "libpoppler145" | .depends ~ "libpoppler-cpp2";
is_bad = .depends ~ "libpoppler140" | .depends ~ "libpoppler-cpp1";
--- End Message ---
--- Begin Message ---
On 28/02/2025 23:28, Jeremy Bícha wrote:
libpoppler140 is only still in Unstable because libgdal35 is in
Unstable because of mysql-workbench which is unbuildable and also
already has unsatisfiable dependencies (pcre3). Could we manually
remove those libraries to complete this transition?
The transition is complete (closing it as I forgot), as poppler migrated to
testing, and the old library was removed from testing.
As for libpoppler140 still being in unstable, that's, as you say, because there
are packages (only in sid) that still depend on it. You have identified the
chain, but it'd mean removing mysql-workbench from sid, which then would have to
go through NEW, and the maintainers may object, etc. So usually you can just
ignore that cruft. It's listed in [1], fwiw, along with the rest of the "cruft"
in the archive.
I should file a removal bug, right?
Probably not.
Cheers,
Emilio
[1] https://ftp-master.debian.org/cruft-report-daily.txt
--- End Message ---
