Your message dated Fri, 18 Sep 2026 11:46:11 +0000
with message-id <[email protected]>
and subject line Bug#1137258: Removed package(s) from unstable
has caused the Debian Bug report #944981,
regarding open-infrastructure-system-tools: Components and script access
internal dpkg database
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.)
--
944981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944981
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: open-infrastructure-system-tools
Source-Version: 20190301-lts1-1
Severity: important
User: [email protected]
Usertags: dpkg-db-access-blocker
Hi!
This package contains several components (system-config) and scripts
(system-build), which directly access the dpkg internal database,
instead of using one of the public interfaces provided by dpkg.
All these components (system-config) check the presence of the .list
file to assert whether a package is installed. These components should
be switched to use something else. Either check the status for each of
these components (via dpkg-query), or these checks should be refactored
into the call site which could do the checks over the entire database
with a single call to «dpkg-query --show» instead of calling it once
per package.
The script «scripts/build/chroot_live-packages» should be changed to
do something similar to the above. The other script, even though do
mess with the internal database, seem to be installer code, and as
long as it is executed before any dpkg in that chroot, then it might
assume historical database layouts, although I'd rather we found a way
to avoid those usages too (but let's ignore these for now).
This is a problem for several reasons, because even though the layout and
format of the dpkg database is administrator friendly, and it is expected
that those might need to mess with it, in case of emergency, this
“interface” does not extend to other programs besides the dpkg suite of
tools. The admindir can also be configured differently at dpkg build or
run-time. And finally, the contents and its format, will be changing in
the near future.
Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Version: 20190301-lts1-5+rm
Dear submitter,
as the package open-infrastructure-system-tools has just been removed from the
Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1137258
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
