Your message dated Wed, 10 Jun 2026 18:08:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#1139257: autoremoval box does not explain removal
has caused the Debian Bug report #1139257,
regarding autoremoval box does not explain removal
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 [email protected]
immediately.)
--
1139257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139257
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: normal
The tracker page for fenics-dolfinx at
https://tracker.debian.org/pkg/fenics-dolfinx
currently includes an autoremoval box in "action needed" reporting that
fenics-dolfinx
is Marked for autoremoval due to getfem.
But the provided reason is not sufficient for taking any action (beyond fixing
getfem itself,
which is not always practical).
fenics-dolfinx does not depend on getfem,
and no package that fenics-dolfinx depends on depends on getfem.
The message box adds the weasel word 'transitively': "depends (transitively)
on getfem".
But what does that mean? Again, no package that fenics-dolfinx depends on
depends on getfem.
How I am supposed to interpret this adverb 'transitively'.
This instruction to autoremove "(transitively)" must come from somewhere.
It's not pixie dust sprinkled over the packages just to annoy package
developers.
How does tracker know that this package is marked for autoremoval?
Where does the knowledge about this autoremoval come from?
If the reason (the transitive dependency) can't fit in the tracker info box
itself,
then please at least provide a link to a page where this
remove-due-to-transitive-dependency
is documented, so we can review why an unrelated package is triggering
autoremoval.
--- End Message ---
--- Begin Message ---
On 2026-06-08 12:08, Andrey Rakhmatullin wrote:
On Mon, Jun 08, 2026 at 11:49:15AM +0200, Drew Parsons wrote:
Where does the knowledge about this autoremoval come from?
I assume it's https://udd.debian.org/cgi-bin/autoremovals.cgi or an
equivalent source.
This might be the link that the tracker box needs to add then.
I don't see how would this link help as it doesn't contain what you
wanted.
That link provides the list packages affected by the failing package.
https://tracker.debian.org/pkg/getfem also provides this list, and in
a more convenient way.
Fair point. The packages that are affected by getfem are listed in
getfem's own autoremoval info box.
And the link to getfem's page is provided in fenics-dolfinx's
autoremoval info box.
This is a satisfactory solution (I just have to remember to click on the
triggering package's info box),
and it's already in place, so I'll close this bug now.
--- End Message ---
