[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1037182: marked as done (bullseye-pu: package bmake/20200710-14+deb11u1)

Your message dated Sat, 07 Oct 2023 12:41:28 +0100
with message-id <84bb5ff8312f749ebe536897993782bf35aa1977.camel@adam-barratt.org.uk>
and subject line Closing opu requests for updates included in 11.8
has caused the Debian Bug report #1037182,
regarding bullseye-pu: package bmake/20200710-14+deb11u1
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 owner@bugs.debian.org
immediately.)


-- 
1037182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037182
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian.org@packages.debian.org
Usertags: pu

[ Reason ]
There is a directory vs. symlink conflict between bsdowl (buster, not in
bullseye) and bmake (buster), causing bsdowl files to and up in a
location behind a symlink from bmake.
bsdowl has been fixed in bookworm and sid, but that happened to late for
bullseye (was already autorm'ed, not reintroducible).
With the Conflicts against the unfixed bsdowl version added to bmake,
the old bsdowl package from buster gets removed on systems upgraded to
bullseye. If someone really need it, I can provide a backport of the
fixed bsdowl from bookworm in bullseye-backports.

[ Impact ]
QA tools warn about files installed over a directory symlink, maybe
silently overwriting other packages files.

[ Tests ]
manual piuparts tests
  buster -> bullseye + fix
  buster -> bullseye -> bullseye + fix
no longer fail with
  ERROR: installs objects over existing directory symlinks:
  /usr/share/mk/bps.autoconf.mk (bsdowl) != /usr/share/bmake/mk-bmake/bps.autoconf.mk (?)
    /usr/share/mk -> bmake/mk-bmake
  ...

[ Risks ]
Low, only affects packages not part of bullseye.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable
      - bsdowl ships the files in the new canonical location
      - bmake verifies that no other package messes up its symlinks

[ Changes ]
add Conflict against unfixed bsdowl versions, i.e. the version from
buster that may have survived the upgrade to bullseye since bsdowl is
not part of bullseye.

[ Other info ]
n/a

Andreas

diff -Nru bmake-20200710/debian/changelog bmake-20200710/debian/changelog
--- bmake-20200710/debian/changelog	2021-04-02 12:53:47.000000000 +0200
+++ bmake-20200710/debian/changelog	2023-06-07 09:48:17.000000000 +0200
@@ -1,3 +1,11 @@
+bmake (20200710-14+deb11u1) bullseye; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Conflicts: bsdowl (<< 2.2.2-1.2~) for directory vs. symlink conflict.
+    (Closes: #985347)
+
+ -- Andreas Beckmann <anbe@debian.org>  Wed, 07 Jun 2023 09:48:17 +0200
+
 bmake (20200710-14) unstable; urgency=medium
 
   * Remove the bsd.*.mk autodetection now that we actually ship symlinks.
diff -Nru bmake-20200710/debian/control bmake-20200710/debian/control
--- bmake-20200710/debian/control	2021-04-02 12:53:47.000000000 +0200
+++ bmake-20200710/debian/control	2023-06-07 09:48:17.000000000 +0200
@@ -13,6 +13,7 @@
 Multi-Arch: foreign
 Replaces: pmake
 Provides: pmake
+Conflicts: bsdowl (<< 2.2.2-1.2~)
 Breaks: pmake (<< 20200710-2)
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: NetBSD make

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 11.8

Hi,

The updates referred to by each of these requests were included in
today's 11.8 bullseye point release.

Regards,

Adam

--- End Message ---
Reply to: