Your message dated Mon, 21 Sep 2026 07:04:07 +0200
with message-id
<caaajcmydg-ygab1a-jxy5h9fmk6zsyxvydga0munpdqzrjn...@mail.gmail.com>
and subject line Re: Bug#1067675: library package (arch any) depending on a
"common" package with too strict version constraint
has caused the Debian Bug report #1067675,
regarding library package (arch any) depending on a "common" package with too
strict version constraint
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.)
--
1067675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067675
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:folks
Version: 0.15.9-1
Severity: important
Tags: patch
This is a bad packaging practice which happens way to often within all
the GTK/Gnome packaging (cloning for mutter as well). The scenario goes
as follows:
- upload a new package
- build fails on "all", not building the "common" package.
- build succeeds on other architectures, in most cases
because the packagers don't run the tests, or ignore test
results.
- the packages then are not installable anymore until the
uploads are in sync, blocking any other builds depending
on these packages. This can take a long, if the uploader
goes to vacation, or a new package build takes ages (yes,
LLVM had that issue as well, and LLVM builds take days).
proposed patch attached. Note that (>= ${source:Version}) has the same
problem, and doesn't help either. Feel free to use some other version
constraint than the upstream version.
diff -Nru folks-0.15.9/debian/control folks-0.15.9/debian/control
--- folks-0.15.9/debian/control 2024-03-23 12:41:20.000000000 +0100
+++ folks-0.15.9/debian/control 2024-03-24 22:06:08.000000000 +0100
@@ -31,7 +31,7 @@
Package: libfolks26
Architecture: any
-Depends: folks-common (= ${source:Version}),
+Depends: folks-common (>= ${upstream:Version}),
${misc:Depends},
${shlibs:Depends}
Recommends: libfolks-eds26
diff -Nru folks-0.15.9/debian/rules folks-0.15.9/debian/rules
--- folks-0.15.9/debian/rules 2024-03-23 12:41:20.000000000 +0100
+++ folks-0.15.9/debian/rules 2024-03-24 22:06:08.000000000 +0100
@@ -35,3 +35,8 @@
dh_auto_test --no-parallel -- --timeout-multiplier 3
override_dh_gnome_clean:
+
+
+override_dh_gencontrol:
+ dh_gencontrol -- \
+ -Vupstream:Version=$(shell dpkg-parsechangelog -S Version | sed
's/-[^-]*$$//')
--- End Message ---
--- Begin Message ---
Version: 51.0-2
libmutter now has
Depends: mutter-common (>= ${source:Upstream-Version})
which becomes
Depends: mutter-common (>= 51.0)
That satisfies your request for looser dependencies for NMUs etc., in
Debian and Ubuntu, while still ensuring that the mutter library is
installed with the minimum version of its gsettings schemas, etc.
I think this dependency syntax is useful, so I'll use it more often in
other packages. It is far less commonly used in Debian than the
previous syntax.
Thank you,
Jeremy Bícha
--- End Message ---
