Bug#1038115: marked as done (transition: gdal)
Your message dated Tue, 4 Jul 2023 06:40:11 +0200 with message-id <5a7ce398-8f9c-0e8b-9266-0aa275c7d...@xs4all.nl> and subject line Re: Bug#1038115: transition: gdal has caused the Debian Bug report #1038115, regarding transition: gdal 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.) -- 1038115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: g...@packages.debian.org Control: affects -1 + src:gdal Control: forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Control: block -1 by 1030129 998833 1037920 984398 1037976 For the Debian GIS team I'd like to transition to GDAL 3.7.0. Most reverse dependencies rebuilt successfully with GDAL 3.7.0 from experimental as summarized below. mysql-workbench (8.0.32+dfsg-1) FTBFS due to ca-certificates-java (#1030129). Once that is fixed it will likely FTBFS due to #998833. ncl (6.6.2.dfsg.1-1) FTBFS due to hdf4 (4.2.16-1): /usr/include/hdf/dfi.h:128:2: error: #endif without #if 128 | #endif /* H4_DFI_H */ | ^ This is fixed in hdf4 (4.2.16-2), but NCL still FTBFS: /usr/include/hdf/dfi.h:53:33: error: two or more data types in declaration specifiers 53 | #define float32 float | ^ /usr/include/hdf/hdfi.h:121:16: note: in expansion of macro 'float32' 121 | typedef float float32; |^~~ /usr/include/hdf/hdfi.h:121:1: warning: useless type name in empty declaration 121 | typedef float float32; | ^~~ hdf4 (4.2.16-3) contains a different fix for dfi.h that resolves this issue. python-django (3:3.2.19-1) FTBFS due to an unrelated issue (#1037920). vtk6 (6.3.0+dfsg2-8.1) FTBFS due to an unrelated issue (#984398). opencv (4.6.0+dfsg-12) FTBFS due to ca-certificates-java (#1030129). Removing the Java packages lets the package build successfully with GDAL 3.7.0. osmcoastline (2.4.0-1) FTBFS due to changes in GDAL 3.7.0 (#1037976), osmcoastline (2.4.0-2) contains a patch to fix this issue. Transition: gdal libgdal32 (3.6.4+dfsg-1) -> libgdal33 (3.7.0+dfsg-1~exp1) The status of the most recent rebuilds is as follows. cloudcompare(2.11.3-7.1) OK fiona (1.9.4-1) OK gmt (6.4.0+dfsg-2)OK grass (8.2.1-1) OK libcitygml (2.5.1-1) OK libosmium (2.19.0-1)OK mapcache(1.14.0-1)OK mapnik (3.1.0+ds-3) OK mapproxy(1.16.0+dfsg-1) OK mapserver (8.0.1-1) OK merkaartor (0.19.0+ds-3) OK mysql-workbench (8.0.32+dfsg-1) FTBFS (#998833) ncl (6.6.2.dfsg.1-1) OK octave-mapping (1.4.2-3) OK openorienteering-mapper (0.9.5-3) OK openscenegraph (3.6.5+dfsg1-8) OK paraview(5.11.0+dfsg-1) OK pgsql-ogr-fdw (1.1.3-1) OK pktools (2.6.7.6+ds-4)OK postgis (3.3.3+dfsg-2)OK python-django (3:3.2.19-1) FTBFS (#1037920) qmapshack (1.16.1-2)OK r-cran-rgdal(1.6-4+dfsg-1)OK r-cran-sf (1.0-9+dfsg-1)OK r-cran-terra(1.7-3-1) OK rasterio(1.3.7-1) OK saga(9.0.2+dfsg-1)OK vtk6(6.3.0+dfsg2-8.1) FTBFS (#984398) vtk7(7.1.1+dfsg2-10.2)OK vtk9(9.1.0+really9.1.0+dfsg2-5) OK facet-analyser (0.0~git20221121142040.6be10b8+ds1-3) OK libgdal-grass (1:1.0.2-4) OK opencv (4.6.0+dfsg-12) FTBFS (#1030129) osmcoastline
Bug#1039484: transition: gpsd
Sebastian, Could you also do a binNMU for collectd? The automatic transition tracker doesn't detect that one because it is only a Recommends instead of a Depends. Thank you, Jeremy Bícha
Bug#1040001: transition: r-base
Hi Graham, Am Mon, Jul 03, 2023 at 05:24:19PM + schrieb Graham Inggs: > On Sun, 2 Jul 2023 at 19:57, Andreas Tille wrote: > > 45 > > > > serious bugs that are all caused by the non-transition while we should > > have done one. That's pretty annoying for the people who need to do the > > work (in this case basically me). > > IMHO, those autopkgtests regression bugs are useful. At least > #1039651 (in r-cran-gnm) and #1039653 (in r-cran-irkernel) appear > unrelated to the R_GE_version issue. Thank you for your uploads with fixes. > In addition, r-cran-bookdown [1] appears to break r-cran-flextable's > autopkgtests and r-cran-checkmate [2] fails its own autopkgtests on > armel, armhf and i386. These do not have bugs filed yet. I can imagine that there might be further bugs that are not filed yet. But that's not my point. I think if we would do a proper transition we can solve those issues caused by R_GE_version in one rush. All remaining things can be done manually if needed. I really wish we could make any progress in this direction. Kind regards Andreas. > [1] https://tracker.debian.org/pkg/r-cran-bookdown > [2] https://tracker.debian.org/pkg/r-cran-checkmate -- http://fam-tille.de
Bug#1040001: transition: r-base
Hi Andreas On Sun, 2 Jul 2023 at 19:57, Andreas Tille wrote: > 45 > > serious bugs that are all caused by the non-transition while we should > have done one. That's pretty annoying for the people who need to do the > work (in this case basically me). IMHO, those autopkgtests regression bugs are useful. At least #1039651 (in r-cran-gnm) and #1039653 (in r-cran-irkernel) appear unrelated to the R_GE_version issue. In addition, r-cran-bookdown [1] appears to break r-cran-flextable's autopkgtests and r-cran-checkmate [2] fails its own autopkgtests on armel, armhf and i386. These do not have bugs filed yet. Regards Graham [1] https://tracker.debian.org/pkg/r-cran-bookdown [2] https://tracker.debian.org/pkg/r-cran-checkmate
Bug#1040041: bookworm-pu: package dnf/4.14.0-3+deb12u1
Hi! On Sat, Jul 1, 2023 at 10:44 PM Frédéric Pierret wrote: > > Hello Aron, > I'm sorry for the delay, I'm just getting out of Holidays and other duties. > If anything should be done, let me know. > > Also, I rely a lot on Holger for pushing stuff, and I need to candidate for > DM/DD, just need to find time to do that. > Fully understand and that's perfectly OK. I'm just trying to speed up the process since everyone can propose a proposed-updates to stable release unless the maintainer has objections, which I don't think we are in the case, ;-) Regards, Aron
Bug#1040041: bookworm-pu: package dnf/4.14.0-3+deb12u1
On Sat, Jul 1, 2023 at 10:47 PM Adam D. Barratt wrote: > > Control: tags -1 + confirmed > > On Sat, 2023-07-01 at 22:13 +0800, Aron Xu wrote: > > Fix bug in stable release affecting dependent package (Bug #1034828, > > affecting src:dnf-plugins-core). > > > > We generally prefer codenames - i.e. "bookworm" - rather than suites > (i.e. "stable") in changelogs. > > Please go ahead. > Uploaded, with changelog entry aligned to use "bookworm" instead of "stable". Thanks! Aron
Bug#1036797: Acknowledgement (bullseye-pu: package mariadb-10.5 10.5.20-0+deb11u1)
Hi! Can you please grant permission to upload this to oldstable-proposed-updates?
Bug#1040206: bullseye-pu: package debianutils/5.7-0.5~deb12u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
There is a path canonicalization bug in update-shells that may lead to
- insertion of duplicate entries in /etc/shells
- failure to remove obsolete entries from /etc/shells
on merged-/usr systems. This is triggered if the shell itself is a
symlink, e.g. in 9base it is managed via update-alternatives.
Furthermore the handling of /bin/sh by update-shells was inconsistent
with all other shells, e.g. update-shells didn't generate the
corresponding /usr/bin/sh entry (while usrmerge did).
Miscanonicalization could also lead to invalid (i.e. nonexistent) paths
added to /etc/shells, although that does not happen with the packages
currently in the archive.
[ Impact ]
The bad entries in /etc/shells are probably harmless for normal
operation (duplicate or stale entries), but nasty for QA tooling
checking for inconsistencies. I prefer to fix these issues properly
(where possible) instead of working around them (or ignoring them) in QA
tools.
[ Tests ]
piuparts install and upgrade tests of all packages making use of
update-shells using the fixed package in merged-/usr and unmerged-/usr
contexts. No inconsistencies in /etc/shells (missing or leftover
entries) were found after the fixed package was applied.
[ Risks ]
Low. The changes are fairly minimal.
[ 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
[ Changes ]
- try to avoid creating duplicate entries in /etc/shells (using the same
mechanism that is already used multiple times in update-shells)
(duplicates should no longer happen with the canonicalization bug
fixed, unless a shell is defined multiple times in shells.d, so let's
fix these, too)
- handle /bin/sh (which is defined in /usr/share/debianutils/shells (the
template for /etc/shells) but not in /usr/share/debianutils/shells.d/)
like any other shell by treating the template file as if it were part
of shells.d/
- canonicalize only the directory of the shell (not the shell itself)
to compute the shell in an aliased location (on merged-/usr systems)
This is rebuild of the package from sid with no further changes.
[ Other info ]
With these fixes applied, my intent is to make usrmerge call
update-shells to ensure the state file of update-shells is updated after
the usrmerge conversion, too.
Andreas
diff --git a/debian/changelog b/debian/changelog
index eb37be1..b50154c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+debianutils (5.7-0.5~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Mon, 03 Jul 2023 13:56:27 +0200
+
+debianutils (5.7-0.5) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * update-shells: Do not create duplicate entries in /etc/shells.
+ * update-shells: Manage (/usr)/bin/sh in the state file.
+ * update-shells: Fix canonicalization of shells in aliased locations.
+(Closes: #1035820)
+
+ -- Andreas Beckmann Thu, 22 Jun 2023 21:59:33 +0200
+
debianutils (5.7-0.4) unstable; urgency=medium
* Non-maintainer upload
diff --git a/debian/patches/dpkg-root b/debian/patches/dpkg-root.patch
similarity index 87%
rename from debian/patches/dpkg-root
rename to debian/patches/dpkg-root.patch
index 2641b70..ead43a1 100644
--- a/debian/patches/dpkg-root
+++ b/debian/patches/dpkg-root.patch
@@ -1,3 +1,6 @@
+Author: Johannes Schauer Marin Rodrigues
+Description: set the default for ROOT to $DPKG_ROOT
+
--- a/update-shells
+++ b/update-shells
@@ -23,7 +23,7 @@ log() {
diff --git a/debian/patches/fix-aliased-location.patch
b/debian/patches/fix-aliased-location.patch
new file mode 100644
index 000..97e1efe
--- /dev/null
+++ b/debian/patches/fix-aliased-location.patch
@@ -0,0 +1,18 @@
+Author: Andreas Beckmann
+Description: fix detection of shells in aliased locations
+ only canonicalize the directory where the shell resides,
+ not the shell itself (which may be a symlink, e.g. managed by
+ update-alternatives)
+Bug-Debian: https://bugs.debian.org/1035820
+
+--- a/update-shells
b/update-shells
+@@ -80,7 +80,7 @@ for f in "$TEMPLATE_ETC_FILE" "$PKG_DIR/
+ while IFS='#' read -r line _; do
+ [ -n "$line" ] || continue
+ PKG_SHELLS="$PKG_SHELLS$line#"
+- realshell=$(dirname "$(dpkg-realpath --root "$ROOT"
"$line")")/$(basename "$line")
++ realshell=$(dpkg-realpath --root "$ROOT" "$(dirname
"$line")")/$(basename "$line")
+ if [ "$line" != "$realshell" ]; then
+ PKG_SHELLS="$PKG_SHELLS$realshell#"
+ fi
diff --git a/debian/patches/manage-usr-bin-sh.patch
b/debian/patches/manage-usr-bin-sh.patch
new file mode 100644
index 000..b9122e9
--- /dev/null
+++ b/debian/patches/manage-usr-bin-sh.patch
@@
