Bug#1066959: sysdig: wrong runtime dependency on old falcosecurity binary
Package: sysdig
Version: 0.35.0+repack-1
Severity: Serious
Hello, for some reasons sysdig has an hardcoded runtime dependency on
libfalcosecurity0, now renamed in libfalcosecurity0t64.
You can remove it and let debhelper create it via shlibs:Depends automatically
*** /tmp/tmpmxvw_b1d/sysdig_0.35.0+repack-1ubuntu1.debdiff
diff -Nru sysdig-0.35.0+repack/debian/control
sysdig-0.35.0+repack/debian/control
--- sysdig-0.35.0+repack/debian/control 2024-01-26 07:25:50.0 +0100
+++ sysdig-0.35.0+repack/debian/control 2024-03-16 06:50:27.0 +0100
@@ -27,8 +27,7 @@
Package: sysdig
Architecture: any
-Depends: libfalcosecurity0 (>= 0.11.3),
- ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
Recommends: falcosecurity-scap-dkms
Description: system-level exploration and troubleshooting tool
Sysdig instruments your physical and virtual machines at the OS level
G.
Bug#1066908: lowdown FTCBFS: performs a native build
Hi, On Fri, Mar 15, 2024 at 01:32:00PM +0200, Faidon Liambotis wrote: > > lowdown fails to cross build from source, because it performs a native > > build. Since there is a configure script, debhelper concludes that the > > autoconf build system should be used and that it thus should not pass > > cross tools to make, but it really should. Also since dh_auto_configure > > is overridden, passing cross flags there (CC in particular) is required. > > Last but not least, the pkg-config invocations also need to use the host > > tools. I'm attaching a patch for your convenience. > > Thanks for this, Helmut! > > > include /usr/share/dpkg/architecture.mk > > +-include /usr/share/dpkg/buildtools.mk > > Why -include? Are there conditions under which buildtools.mk wouldn't > exist? When you use a very old dpkg (like stretch), buildtools.mk does not exist. I guess these days, we can include without -. I suspect I have to adjust my finger memory. > > +PKG_CONFIG ?= pkg-config > > ...and if we assume buildtools.mk always exist, can we drop this and > assume PKG_CONFIG is always going to be defined? Yes. >From your other mail: | One more thing: should we also pass AR=$(AR)? It did matter for | WebAssembly (which required the use of llvm-ar) and why I added support | for it to oconfigure¹, but I'm not sure if it makes a difference between | different binutils architectures when cross-building. Generally speaking, adding AR does not hurt and makes things better for the reasons you cite. Other than that, it does not seem to be strictly necessary in this case. So yeah, add it. Helmut
Bug#1066958: lintian: source-is-missing: consider package.texi as source for package.html
Package: lintian Version: 2.117.0 Severity: normal I just noticed source-is-missing [doc/netperf.html] in src:netperf (non-free), but that file is generated from doc/netperf.texi Andreas
Bug#1061901: compiz: NMU diff for 64-bit time_t transition
Unfortunately, compiz FTBFS on armel and armhf because
libstartup-notification is not 64-bit time_t-safe. I have uploaded a
follow-up NMU to fix this. Please find attached the comprehensive NMU
patch.
On Wed, Feb 28, 2024 at 05:32:03PM +, Steve Langasek wrote:
> Dear maintainer,
>
> Please find attached a final version of this patch for the time_t
> transition. This patch is being uploaded to unstable.
>
> Note that this adds a versioned build-dependency on dpkg-dev, to guard
> against accidental backports with a wrong ABI.
>
> Thanks!
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru compiz-0.8.18/debian/changelog compiz-0.8.18/debian/changelog
--- compiz-0.8.18/debian/changelog 2023-01-01 21:58:27.0 +
+++ compiz-0.8.18/debian/changelog 2024-03-16 01:19:57.0 +
@@ -1,3 +1,18 @@
+compiz (2:0.8.18-5.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/64-bit-time-t-compat.patch: fix build with
+_TIME_BITS=64.
+
+ -- Steve Langasek Sat, 16 Mar 2024 01:19:57 +
+
+compiz (2:0.8.18-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition. Closes: #1061901
+
+ -- Steve Langasek Wed, 28 Feb 2024 17:31:21 +
+
compiz (2:0.8.18-5) unstable; urgency=medium
[ Samuel Thibault ]
diff -Nru compiz-0.8.18/debian/control compiz-0.8.18/debian/control
--- compiz-0.8.18/debian/control2023-01-01 21:58:27.0 +
+++ compiz-0.8.18/debian/control2024-02-28 17:31:21.0 +
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Hypra Team
Uploaders: Samuel Thibault
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13),
intltool,
libcairo2-dev,
libglib2.0-dev,
@@ -159,7 +159,10 @@
This package contains the standard plugins that come with compiz. Compiz
without these plugins is not very useful.
-Package: libdecoration0
+Package: libdecoration0t64
+Provides: ${t64:Provides}
+Replaces: libdecoration0
+Breaks: libdecoration0 (<< ${source:Version})
Section: libs
Architecture: any
Multi-Arch: same
@@ -174,7 +177,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libdecoration0 (= ${binary:Version}),
+Depends: libdecoration0t64 (= ${binary:Version}),
${misc:Depends},
libx11-dev,
libxrender-dev
diff -Nru compiz-0.8.18/debian/libdecoration0.install
compiz-0.8.18/debian/libdecoration0.install
--- compiz-0.8.18/debian/libdecoration0.install 2018-10-27 12:09:18.0
+
+++ compiz-0.8.18/debian/libdecoration0.install 1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-usr/lib/libdecoration*.so.*
diff -Nru compiz-0.8.18/debian/libdecoration0t64.install
compiz-0.8.18/debian/libdecoration0t64.install
--- compiz-0.8.18/debian/libdecoration0t64.install 1970-01-01
00:00:00.0 +
+++ compiz-0.8.18/debian/libdecoration0t64.install 2018-10-27
12:09:18.0 +
@@ -0,0 +1 @@
+usr/lib/libdecoration*.so.*
diff -Nru compiz-0.8.18/debian/libdecoration0t64.lintian-overrides
compiz-0.8.18/debian/libdecoration0t64.lintian-overrides
--- compiz-0.8.18/debian/libdecoration0t64.lintian-overrides1970-01-01
00:00:00.0 +
+++ compiz-0.8.18/debian/libdecoration0t64.lintian-overrides2024-02-28
17:29:20.0 +
@@ -0,0 +1 @@
+libdecoration0t64: package-name-doesnt-match-sonames libdecoration0
diff -Nru compiz-0.8.18/debian/patches/64-bit-time-t-compat.patch
compiz-0.8.18/debian/patches/64-bit-time-t-compat.patch
--- compiz-0.8.18/debian/patches/64-bit-time-t-compat.patch 1970-01-01
00:00:00.0 +
+++ compiz-0.8.18/debian/patches/64-bit-time-t-compat.patch 2024-03-16
01:19:57.0 +
@@ -0,0 +1,30 @@
+Description: fix build with _TIME_BITS=64
+ The startup-notification API takes a long * where it ought to have always
+ taken a time_t *. As a consequence, changing the size of time_t makes
+ callers fail to build. Work around this by safely casting to a long.
+ This will continue to work on 32-bit systems until 2038, by which time
+ all the 32-bit systems will be dead or no longer running GUIs or at least
+ not using libstartup-notification0.
Bug#990451: [EXT]Re: Bug#990451: (no subject)
David Kalnischkies wrote on 3/13/24 2:28 AM: > What would this achieve; what is the use case? The use case is when a repo has too many versions of a software on it. I'd only be interested in seeing the details for the Installed and Candidate versions, so even my initial --versions suggestion is not good enough for that. > I literally see no point in having 'policy' limited to a single > version (and which one?) given its usually used to show which versions > are available from where, how the pin values are for those and which > one is considered the candidate as a result of that. Maybe just the candidate version? Who knows? Chances are someone would find it useful. > Uhm… beside that the --no-all-versions flag switches the display from > "display all versions" to "display the candidate version only" in e.g. > 'show' (and one or the other is the default in apt-cache vs. apt), so > the equivalent would be more like '1' … and '0' would display nothing? Precisely, for those of us looking for a little more zen in our lives. > How would --versions=3 behave through: Assuming I have 5 different > versions available in the sources, which of these are displayed and > which are not… regardless of the choice, this seems rather unintuitive > to discover without many paragraphs of documentation that basically > duplicates the code in prose text. Now is this 5 repos with 1 version each, or 2 repos with 2 versions plus 1 repo with 1 version, or 1 repo with 5 versions, or 3 repos with 1 version plus 1 repo with 2 versions, or 1 repo with 1 version plus 1 repo with 4 versions? Will --versions apply on a per-repo basis or globally? We could go down a list of priorities until the number of desired versions has been reached, that could include: Installed, Candidate, Candidate-1, Installed+1, Installed-1, Candidate-2, Installed+2, Installed-2, et cetera, et cetera > Again, what would this achieve and what is the use case for this? Likely the same or similar reasons --no-all-versions already exists, for one to limit the clutter and undesirable information on our screens, et cetera, et cetera. > Sidenote: If a specific task has no people interested in working on it, There're categories for such tasks such as "closed" or "wontfix" et cetera, et cetera, none of which apply to this request as of yet. > Either create a compelling new task referencing related ones Such was of course considered but this path was chosen in our infinite wisdom. We're sure you'd've complained either way, saying it's a duplicate and how kilobytes of bandwidth and storage were wasted, right? Et cetera, et cetera. > or much better yet do work on it yourself. Our time is quite limited and you're blessed to have received this much of it already. > Its open source after all and nothing will ever get done if everyone > hopes someone else will do it. It is? -squints- Our Gods! You're right, all this time wasted sharing our ideas for improvements when we could've just done it ourselves, silly us! Why are there even mailing lists? Decades of work, lost! The travesty! Just think where we could be by now, et cetera, et cetera... Fax mentis incendium gloriæ culpum et cetera, et cetera... Memor bis punitor delicatum! > Best regards You sure?
Bug#1066952: Defaulting to -Werror=implicit-function-declaration might not be a good idea
Hi! On Sat, 2024-03-16 at 02:18:22 +0200, Adrian Bunk wrote: > Package: dpkg-dev > Version: 1.22.6 > Severity: serious > X-Debbugs-Cc: Steve Langasek > 3. Code that does still compile with -Werror=implicit-function-declaration >but behaves differently, e.g. due to failing autoconf tests silently >disabling features > Debian has automation listing implicit-function-declaration warnings > in all packages already running for several years: > https://qa.debian.org/bls/bytag/W-implicit-declaration.html > My main worry is point 3, issues like #1066394. > > #1066394 was found due to causing a FTBFS in a different package, > but the more common case is likely that a program has some > feature/plugin disabled and this won't be spotted until much later. > > "Much later" might be after the release of trixie a user upgrading > to bookworm who uses this feature. > > Or it might result in a program silently using an insecure legacy codepath, > e.g. after a test for getentropy() failed. Not enabling this -Werror might imply ABI breakage for the time64 transition, which seems pretty terrible too. The way I see it, and given the timing, effort and preparation necessary for this transition, both options (enabling or not enabling the fatal warning) are potentially bad in their own way. But given that these are clearly bugs, that not enabling them can imply ABI breakage, that if things go according to plan (AFAIK) this will be made the default anyway with gcc-14, that we can track those down, and people have already been doing that for the Modern-C effort, see: https://fedoraproject.org/wiki/Changes/PortingToModernC https://wiki.gentoo.org/wiki/Modern_C_porting I think we might as well just cope with this anyway right away. > A large part of the packages in unstable might not get recompiled > between now and the release of trixie, creating the additional > issue that any such problem might occur only after a security update > or point release update if this is the next rebuild of the package > in trixie. AFAIUI (and I'd expect) the whole distribution needs to be rebuilt anyway as part of the time64 transition, otherwise the 32-bit ports that are affected by it, will not benefit from it. So I don't think this should be a concern. So I'm inclined to close this, and consider the current state, the less bad one. :/ Thanks, Guillem
Bug#1066957: dependency not satisfiable in bookworm-backports
Package: grub-efi-amd64-bin
Version: 2.12-1~bpo12+1
Hello,
This package seems to require[1] grub-efi-amd64-signed >= 1+2.12, which is
available in testing[2].
Please excuse the report if this is expected behavior. Apt output follows.
Thank you for your time.
$ sudo apt install grub2-common
The following packages will be upgraded:
grub-common grub-efi-amd64 grub-efi-amd64-bin{b} grub2-common
4 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 5,578 kB of archives. After unpacking 5,963 kB will be freed.
The following packages have unmet dependencies:
grub-efi-amd64-bin : Breaks: grub-efi-amd64-signed (< 1+2.12~rc1) but
1+2.06+13+deb12u1 is installed
The following actions will resolve these dependencies:
Remove the following packages:
1) grub-efi-amd64 [2.06-13+deb12u1 (now, stable, stable-security)]
2) grub-efi-amd64-bin [2.06-13+deb12u1 (now, stable, stable-security)]
3) shim-signed [1.39+15.7-1 (now, stable)]
Leave the following dependencies unresolved:
4) grub-efi-amd64-signed recommends shim-signed
[1] Per changelog entry dated Tue, 05 Sep 2023 19:06:05 +0200
https://metadata.ftp-master.debian.org/changelogs//main/g/grub2/grub2_2.12-1~bpo12+1_changelog
[2] https://tracker.debian.org/pkg/grub-efi-amd64-signed
Bug#1066956: blimps: FTBFS with -Werror=implicit-function-declaration
Source: blimps Version: 3.9+ds-1 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source Hi, blimps FTBFS with -Werror=implicit-function-declaration which was recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t transition. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration /usr/bin/gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/blimps-3.9+ds=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wuninitialized -O2 -I../include -fpic -Wdate-time -D_FORTI FY_SOURCE=2 -c -o biassed_blocks_finder.o biassed_blocks_finder.c biassed_blocks_finder.c: In function 'parse': biassed_blocks_finder.c:101:6: error: implicit declaration of function 'plustospace' [-Werror=implicit-function-declaration] 101 | plustospace(entries[i].val); | ^~~ biassed_blocks_finder.c:102:6: error: implicit declaration of function 'unescape_url' [-Werror=implicit-function-declaration] 102 | unescape_url(entries[i].val); | ^~~~ biassed_blocks_finder.c: In function 'clean_temp_files': biassed_blocks_finder.c:120:3: warning: ignoring return value of 'system' declared with attribute 'warn_unused_result' [-Wunused-result] 120 | system(buf); | ^~~ ... Andreas
Bug#1066955: metis-edf: FTBFS with -Werror=implicit-function-declaration
Source: metis-edf Version: 4.1-2-4 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source Hi, metis-edf FTBFS with -Werror=implicit-function-declaration which was recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t transition. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/metis-edf-4.1-2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIC -DPIC -I. -c initpart.c In file included from ./metis.h:35, from initpart.c:16: initpart.c: In function '__GrowBisection': ./rename.h:380:42: error: implicit declaration of function '__GKfree'; did you mean 'GKfree'? [-Werror=implicit-function-declaration] 380 | #define GKfree __GKfree | ^~~~ initpart.c:199:4: note: in expansion of macro 'GKfree' 199 |GKfree(, , , LTERM); |^~ cc1: some warnings being treated as errors make[3]: *** [Makefile:23: initpart.o] Error 1 Andreas
Bug#1066954: xtrs: FTBFS with html2test 2.x: Unrecognized command line option "-style"
Source: xtrs Version: 4.9d-2 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) Hi, xtrs FTBFS with the new html2test version in sid: html2text -nobs -style pretty cpmutil.html >cpmutil.txt Unrecognized command line option "-style", try "-help". make[1]: *** [Makefile:184: cpmutil.txt] Error 1 Andreas
Bug#1066953: pvpgn: FTBFS with -Werror=implicit-function-declaration
Source: pvpgn Version: 1.8.5-3 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) Hi, pvpgn FTBFS with -Werror=implicit-function-declaration which was recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t transition. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/pvpgn-1.8.5=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DHAVE_CONFIG_H -DWITH_SQL_MYSQL -DWITH_SQL_PGSQL -DWITH_SQL_SQLITE 3 -DBNETD_DEFAULT_CONF_FILE=\"/etc/pvpgn/bnetd.conf\" -DD2CS_DEFAULT_CONF_FILE=\"/etc/pvpgn/d2cs.conf\" -DD2DBS_DEFAULT_CONF_FILE=\"/etc/pvpgn/d2dbs.conf\" -I"." -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include - fno-strict-aliasing -c bnetd/handle_irc.c -o bnetd/handle_irc.o bnetd/handle_irc.c: In function '_handle_whereto_command': bnetd/handle_irc.c:1391:8: error: implicit declaration of function 'trans_net' [-Werror=implicit-function-declaration] 1391 |trans_net(conn_get_addr(conn), , ); |^ bnetd/handle_irc.c: In function '_handle_join_command.part.0.isra': bnetd/handle_irc.c:1026:75: warning: '%s' directive writing up to 508 bytes into a region of size between 2 and 510 [-Wformat-overflow=] 1026 | sprintf(temp,"%s :%s",ircname,topic); | ^~ In file included from /usr/include/stdio.h:906, from ./common/util.h:26, from bnetd/handle_irc.c:23: In function 'sprintf', inlined from '_handle_join_command.part.0.isra' at bnetd/handle_irc.c:1026:8: /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: '__builtin___sprintf_chk' output between 3 and 1019 bytes into a destination of size 512 30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 31 | __glibc_objsize (__s), __fmt, | ~ 32 | __va_arg_pack ()); | ~ Dependency check: bniutils bnetd/handle_irc.c: In function '_handle_joingame_command': bnetd/handle_irc.c:1683:75: warning: '%s' directive writing up to 508 bytes into a region of size between 2 and 510 [-Wformat-overflow=] 1683 | sprintf(temp,"%s :%s",ircname,topic); | ^~ In function 'sprintf', inlined from '_handle_joingame_command' at bnetd/handle_irc.c:1683:8: /usr/include/x86_64-linux-gnu/bits/stdio2.h:30:10: note: '__builtin___sprintf_chk' output between 3 and 1019 bytes into a destination of size 512 30 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 31 | __glibc_objsize (__s), __fmt, | ~ 32 | __va_arg_pack ()); | ~ cc1: some warnings being treated as errors make[1]: *** [Makefile:740: bnetd/handle_irc.o] Error 1 Andreas
Bug#1062199: gvm-libs: NMU diff for 64-bit time_t transition
Hi Sophie,
gvm-libs needs a further change to actually be buildable on 32-bit archs
with 64-bit time_t. I've done a follow-up NMU for this; please find a
comprehensive debdiff attached.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gvm-libs-22.7.3/debian/changelog gvm-libs-22.7.3/debian/changelog
--- gvm-libs-22.7.3/debian/changelog2023-11-20 15:13:25.0 +
+++ gvm-libs-22.7.3/debian/changelog2024-03-16 00:32:34.0 +
@@ -1,3 +1,18 @@
+gvm-libs (22.7.3-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/64-bit-time-t-compat.patch: wrap the write symbols
+when _FILE_OFFSET_BITS=64 is set.
+
+ -- Steve Langasek Sat, 16 Mar 2024 00:32:34 +
+
+gvm-libs (22.7.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition. Closes: #1062199
+
+ -- Lukas Märdian Wed, 28 Feb 2024 09:24:41 +
+
gvm-libs (22.7.3-1) unstable; urgency=medium
* New upstream version 22.7.3
diff -Nru gvm-libs-22.7.3/debian/control gvm-libs-22.7.3/debian/control
--- gvm-libs-22.7.3/debian/control 2023-11-20 15:13:25.0 +
+++ gvm-libs-22.7.3/debian/control 2024-02-28 09:24:41.0 +
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Debian Security Tools
Uploaders: Sophie Brun
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13),
cmake,
libcgreen1-dev [!ppc64el !s390x],
libglib2.0-dev,
@@ -37,7 +37,7 @@
libgpgme-dev,
libhiredis-dev,
libksba-dev,
- libgvm22 (= ${binary:Version}),
+ libgvm22t64 (= ${binary:Version}),
libpcap-dev,
libssh-dev,
uuid-dev,
@@ -71,12 +71,14 @@
libraries.
-Package: libgvm22
+Package: libgvm22t64
+Provides: ${t64:Provides}
+Breaks: libgvm22 (<< ${source:Version})
Architecture: any
Depends: ${misc:Depends},
${shlibs:Depends},
Multi-Arch: same
-Replaces: libopenvas9
+Replaces: libgvm22, libopenvas9
Conflicts: libopenvas9
Description: remote network security auditor - shared libraries
The Open Vulnerability Assessment System is a modular security auditing
diff -Nru gvm-libs-22.7.3/debian/libgvm22.install
gvm-libs-22.7.3/debian/libgvm22.install
--- gvm-libs-22.7.3/debian/libgvm22.install 2023-11-20 15:13:25.0
+
+++ gvm-libs-22.7.3/debian/libgvm22.install 1970-01-01 00:00:00.0
+
@@ -1 +0,0 @@
-usr/lib/*/libgvm*.so.*
diff -Nru gvm-libs-22.7.3/debian/libgvm22.lintian-overrides
gvm-libs-22.7.3/debian/libgvm22.lintian-overrides
--- gvm-libs-22.7.3/debian/libgvm22.lintian-overrides 2023-11-20
15:13:25.0 +
+++ gvm-libs-22.7.3/debian/libgvm22.lintian-overrides 1970-01-01
00:00:00.0 +
@@ -1,4 +0,0 @@
-# this package provides several shared libraries built from the same source
-# tree; since they change their SONAMES together they are provided in a single
-# library package
-package-name-doesnt-match-sonames
diff -Nru gvm-libs-22.7.3/debian/libgvm22.symbols
gvm-libs-22.7.3/debian/libgvm22.symbols
--- gvm-libs-22.7.3/debian/libgvm22.symbols 2023-11-20 15:13:25.0
+
+++ gvm-libs-22.7.3/debian/libgvm22.symbols 1970-01-01 00:00:00.0
+
@@ -1,486 +0,0 @@
-libgvm_base.so.22 libgvm22 #MINVER#
-* Build-Depends-Package: libgvm-dev
- addr6_as_str@Base 22.4.0
- addr6_to_str@Base 22.4.0
- append_to_credentials_password@Base 22.4.0
- append_to_credentials_username@Base 22.4.0
- array_add@Base 22.4.0
- array_free@Base 22.4.0
- array_reset@Base 22.4.0
- array_terminate@Base 22.4.0
- cleanup_settings_iterator@Base 22.4.0
- current_environ@Base 22.4.0
- drop_privileges@Base 22.4.0
- facilitynames@Base 22.4.0
- free_credentials@Base 22.4.0
- free_log_configuration@Base 22.4.0
- free_log_reference@Base 22.4.4
- get_cvss_score_from_base_metrics@Base 22.4.0
- get_log_reference@Base 22.4.4
- get_time@Base 22.4.0
- global_source_addr6@Base 22.4.0
- global_source_addr@Base 22.4.0
- global_source_iface@Base 22.4.0
- gvm_append_string@Base 22.4.0
- gvm_append_text@Base 22.4.0
- gvm_close_sentry@Base 22.4.0
- gvm_disable_password_policy@Base 22.4.0
- gvm_duplicate_host@Base 22.4.0
- gvm_duplicate_vhost@Base 22.4.0
- gvm_free_string_var@Base 22.4.0
- gvm_get_host_type@Base 22.4.0
- gvm_get_outgoing_iface@Base 22.4.0
- gvm_has_sentry_support@Base 22.4.0
- gvm_host_add_reverse_lookup@Base 22.4.0
- gvm_host_find_in_hosts@Base 22.4.0
- gvm_host_free@Base 22.4.0
- gvm_host_from_str@Base 22.4.0
- gvm_host_get_addr6@Base 22.4.0
- gvm_host_in_hosts@Base 22.4.0
- gvm_host_resolve@Base 22.4.0
- gvm_host_reverse_lookup@Base 22.4.0
- gvm_host_type@Base
Bug#1066931: Acknowledgement (replace debian/1.39 with 1.39 tag)
moreover that added tag was not even annotated as the release tags: hence ❯ git describe 1.38-11-gb182a2e ❯ git describe --tags debian/1.39-8-gb182a2e -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik
Bug#1066952: Defaulting to -Werror=implicit-function-declaration might not be a good idea
Package: dpkg-dev Version: 1.22.6 Severity: serious X-Debbugs-Cc: Steve Langasek There are at least 3 different ways how -Werror=implicit-function-declaration breaks packages: 1. Code that did emit implicit-function-declaration warnings during compilation before and does FTBFS now 2. Code that does FTBFS now due to other breakage caused by -Werror=implicit-function-declaration, e.g. in autoconf tests 3. Code that does still compile with -Werror=implicit-function-declaration but behaves differently, e.g. due to failing autoconf tests silently disabling features Cases from point 1 were always(?) bugs and it is good that they get fixed. The real-world effect of these bugs can be everywhere from "completely harmless" to "that was always broken". Debian has automation listing implicit-function-declaration warnings in all packages already running for several years: https://qa.debian.org/bls/bytag/W-implicit-declaration.html My main worry is point 3, issues like #1066394. #1066394 was found due to causing a FTBFS in a different package, but the more common case is likely that a program has some feature/plugin disabled and this won't be spotted until much later. "Much later" might be after the release of trixie a user upgrading to bookworm who uses this feature. Or it might result in a program silently using an insecure legacy codepath, e.g. after a test for getentropy() failed. A large part of the packages in unstable might not get recompiled between now and the release of trixie, creating the additional issue that any such problem might occur only after a security update or point release update if this is the next rebuild of the package in trixie.
Bug#1066003: libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.
On Wed, Mar 13, 2024 at 10:48:45AM -0100, Graham Inggs wrote: >... > Ubuntu is further along in the time_t transition, so further > investigation is needed as to which package causes the change in buld > behaviour of db5.3. >... It's dpkg, Ubuntu disabled -Werror=implicit-function-declaration cu Adrian
Bug#1063333: cardpeek: Built version of cardpeek in Sid use lua5.3 and breaks lua's scripts. Need lua5.2 only.
I am NMUing once again because I have caused this issue. The debdiff is attached.diff -Nru cardpeek-0.8.4/debian/changelog cardpeek-0.8.4/debian/changelog --- cardpeek-0.8.4/debian/changelog 2023-08-25 21:55:49.0 + +++ cardpeek-0.8.4/debian/changelog 2024-03-15 23:31:12.0 + @@ -1,3 +1,10 @@ +cardpeek (0.8.4-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Revert back to lua 5.2. (Closes: #106) + + -- Bastian Germann Fri, 15 Mar 2024 23:31:12 + + cardpeek (0.8.4-1.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru cardpeek-0.8.4/debian/control cardpeek-0.8.4/debian/control --- cardpeek-0.8.4/debian/control 2023-08-25 21:55:49.0 + +++ cardpeek-0.8.4/debian/control 2024-03-15 23:31:12.0 + @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Richard Ulrich -Build-Depends: debhelper-compat (= 10), libluabind-dev, libpcsclite-dev, libgtk-3-dev, libglib2.0-dev, doc-base, libssl-dev, liblua5.3-dev, libcurl4-openssl-dev +Build-Depends: debhelper-compat (= 10), libluabind-dev, libpcsclite-dev, libgtk-3-dev, libglib2.0-dev, doc-base, libssl-dev, liblua5.2-dev, libcurl4-openssl-dev Standards-Version: 3.9.6 Homepage: http://pannetrat.com/Cardpeek/ diff -Nru cardpeek-0.8.4/debian/patches/series cardpeek-0.8.4/debian/patches/series --- cardpeek-0.8.4/debian/patches/series2023-08-25 21:55:49.0 + +++ cardpeek-0.8.4/debian/patches/series2024-03-15 23:31:12.0 + @@ -1,4 +1,2 @@ lintian_warnings lintian2 -lua5.3.patch -lua5.3-pkgconf.patch
Bug#1060035: prison-kf5: update debian/libkf5prison5.symbols for loong64
Hi Zhang, On Fri, 05 Jan 2024 03:23:21 + Zhang Na wrote: > Source: prison-kf5 > Version: 5.107.0-2 > Severity: normal > X-Debbugs-Cc: zhan...@loongson.cn > > Dear Maintainer, > > Please update debian/libkf5prison5.symbols for loong64, thanks! I don't quite understand that patch. prison-kf5 builds fine on loong64, there are no symbol errors and hence there is nothing to fix. -- Med vänliga hälsningar Patrick Franz
Bug#1066891: gcc-13: ICE compiling OpenSSH: in change_address_1
Control: forwarded -1 https://gcc.gnu.org/PR114358
Bug#1066891: gcc-13: ICE compiling OpenSSH: in change_address_1
On 15.03.24 23:33, Thorsten Glaser wrote: tags 1066891 - moreinfo found 1066891 13.2.0-18 thanks On Fri, 15 Mar 2024, Matthias Klose wrote: please provide the /tmp/cc* files that GCC left. Just literally dumping a file into a bug report cries for garbage. OK, /tmp/cc* file and latest build log with latest gcc-13 version attached, compressed. Sorry, I thought that the stuff output to the build log was supposed to be sufficient. bye, //mirabilos you can work-around that by omitting -fzero-call-used-regs=used
Bug#1066891: gcc-13: ICE compiling OpenSSH: in change_address_1
On Sat, 16 Mar 2024, Matthias Klose wrote: > you can work-around that by omitting -fzero-call-used-regs=used Thanks! That will help with the transition. Will you hand this over to upstream for an eventual fix? bye, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
Bug#1066951: RM: a56 -- ROM; rc buggy and dead upstream
Package: ftp.debian.org Severity: normal When trying to fix #1066195, the corresponding patch grew more and more. I no longer wonder why C got such a bad reputation when this was valid code 30 years ago. From my point of view this code needs an entire rework. As I long time ago stopped working with DSPs, I don't want to do this rework by myself. If nobody takes up the baton, I think it is better to remove this package from Debian. As the software fails to compile now, orphaning the package does not seem to be appropriate. Thorsten
Bug#1066872: mozjs102: Fails to build with Python 3.12
Control: forwarded -1 https://src.fedoraproject.org/rpms/mozjs102/c/72d6ad552c3087fafb475370b1a8a7?branch=rawhide Fedora has included two patches to fix this.
Bug#1066950: elpa-org: elpa-org is outdated – emacs version is newer
Package: elpa-org Version: 9.6.10+dfsg-1-c42-bpo-1 Severity: important X-Debbugs-Cc: none, H.-Dirk Schmitt The in bug #1033400 reported version problem is repeated again with the emacs version 1.29 in bookworm-backports and trixie. This emacs package includes org-mode 9.6.15, but the elpa-org package is still the outdated 9.6.10 or 9.5.2 package. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (600, 'stable-updates'), (600, 'stable-security'), (600, 'stable'), (500, 'oldstable-security'), (99, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de:en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages elpa-org depends on: ii dh-elpa-helper 2.0.16 ii elpa-htmlize1.56-1 ii emacsen-common 3.0.5 Versions of packages elpa-org recommends: ii elpa-org-drill 2.7.0+20200412+dfsg1-2 ii emacs 1:29.2+1-2~bpo12+1 ii emacs-gtk [emacs] 1:29.2+1-2~bpo12+1 Versions of packages elpa-org suggests: ii ditaa 0.10+ds1-1.2 ii elpa-org-contrib 0.4+git20220927.1.6422b26-1 ii org-mode-doc 9.5.2-1 ii texinfo6.8-6+b1 ii texlive-fonts-recommended 2022.20230122-3 ii texlive-latex-extra2022.20230122-4 pn xprintidle -- no debconf information -- --- H.-Dirk_Schmitt Dipl.Math. eMail:dirk.schm...@computer42.org pgp: http://www.computer42.org/~dirk/OpenPGP-fingerprint.html
Bug#1066850: Depends extraction not robust
now you're relying on the fact that the first dependency is the libmagic1XX one. That's not robust.
Bug#1060407: Multiple security issues
On Wed, Jan 10, 2024 at 08:36:38PM +0100, Moritz Muehlenhoff wrote: > Source: gtkwave > Version: 3.3.116-1 > Severity: grave > Tags: security > X-Debbugs-Cc: Debian Security Team > > A very thorough security audit of gtkwave unveiled a total of 82 security > issues in gtkwave, all fixed in 3.3.118: > > CVE-2023-32650 CVE-2023-34087 CVE-2023-34436 CVE-2023-35004 > CVE-2023-35057 CVE-2023-35128 CVE-2023-35702 CVE-2023-35703 > CVE-2023-35704 CVE-2023-35955 CVE-2023-35956 CVE-2023-35957 > CVE-2023-35958 CVE-2023-35959 CVE-2023-35960 CVE-2023-35961 > CVE-2023-35962 CVE-2023-35963 CVE-2023-35964 CVE-2023-35969 > CVE-2023-35970 CVE-2023-35989 CVE-2023-35992 CVE-2023-35994 > CVE-2023-35995 CVE-2023-35996 CVE-2023-35997 CVE-2023-36746 > CVE-2023-36747 CVE-2023-36861 CVE-2023-36864 CVE-2023-36915 > CVE-2023-36916 CVE-2023-37282 CVE-2023-37416 CVE-2023-37417 > CVE-2023-37418 CVE-2023-37419 CVE-2023-37420 CVE-2023-37442 > CVE-2023-37443 CVE-2023-37444 CVE-2023-37445 CVE-2023-37446 > CVE-2023-37447 CVE-2023-37573 CVE-2023-37574 CVE-2023-37575 > CVE-2023-37576 CVE-2023-37577 CVE-2023-37578 CVE-2023-37921 > CVE-2023-37922 CVE-2023-37923 CVE-2023-38583 CVE-2023-38618 > CVE-2023-38619 CVE-2023-38620 CVE-2023-38621 CVE-2023-38622 > CVE-2023-38623 CVE-2023-38648 CVE-2023-38649 CVE-2023-38650 > CVE-2023-38651 CVE-2023-38652 CVE-2023-38653 CVE-2023-38657 > CVE-2023-39234 CVE-2023-39235 CVE-2023-39270 CVE-2023-39271 > CVE-2023-39272 CVE-2023-39273 CVE-2023-39274 CVE-2023-39275 > CVE-2023-39316 CVE-2023-39317 CVE-2023-39413 CVE-2023-39414 > CVE-2023-39443 CVE-2023-39444 > > Let's first fix unstable and then we can simple build 3.3.118 > for stable-security and oldstable-security as well. >... I looked at it for LTS, and there are at least two issues to consider: 1. GTK 2 versus GTK 3 Between bullseye and bookworm the UI switched from GTK 2 to GTK 3. The good news is that in buster both versions of 3.3.118 work with a small testcase. The bad news is that upstream has different tarballs for GTK 2 and GTK 3. 2. ghwdump moved to ghdl-tools The ghwdump tool (and manpage) was dropped in 3.3.110 from the upstream sources, and is now in ghdl-tools. My suggestion would be that I do: sid: 3.3.118-0.1 (or 3.3.118-1 if done by a maintainer) bookworm: 3.3.118-0.1~deb12u1 bullseye: 3.3.104+really3.3.118-0.1 (GTK 2 and with ghwdump re-added) buster: 3.3.104+really3.3.118-0.1~deb10u1 (or 3.3.98+really3.3.118-0.1) Any comments? Especially maintainer feedback would be appreciated. > Cheers, > Moritz cu Adrian
Bug#1066949: slic3r-prusa: Unneeded build dependencies on xvfb, xauth
Source: slic3r-prusa Version: 1.37.1+dfsg2-1 Severity: minor Dear Maintainer, Please drop xvfb and xauth from the build dependencies for slic3r-prusa. Prior to version 1.37.1+dfsg2-1 of slic3r-prusa, the debian/rules file made use of xvfb (and, by extension, xauth), but this is no longer the case. Thanks, -- Plasma
Bug#1065701: rocm_agent_enumerator: crash on systems without AMD GPU
Control: notfound -1 5.7.1-1 [Cordell Bloor] > reportbug noted that I had 5.7.1-1 installed, but my report was based on > the rocm-hipamd autopkgtests run on the DebCI. I didn't notice that the > DebCI was using a different version of rocminfo than me, as I'd assumed > it used packages from Unstable. OK. Updated issue metadata. -- Happy hacking Petter Reinholdtsen
Bug#1064967: fontforge DSA (was: Re: Bug#1064967: fontforge: diff for NMU version 1:20230101~dfsg-1.1)
On Wed, Mar 13, 2024 at 08:39:47PM +0100, Salvatore Bonaccorso wrote:
> Hi Adrian,
Hi Salvatore,
> On Fri, Mar 08, 2024 at 02:03:55AM +0200, Adrian Bunk wrote:
> > Control: tags 1064967 + patch
> > Control: tags 1064967 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for fontforge (versioned as 1:20230101~dfsg-1.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.
> >
> > @Security team:
> > If wanted, I could afterwards also prepare (pu or DSA) updates for
> > bookworm and bullseye.
>
> We came to the conclusion that it warrants a DSA. Could you prepare
> debdiffs for bookworm-security and bulseye-security?
the debdiffs are attached.
Tested on both releases with the PoCs from [1] and that opening a normal
compressed font still works.
> Regards,
> Salvatore
cu
Adrian
[1]
https://www.canva.dev/blog/engineering/fonts-are-still-a-helvetica-of-a-problem/
diffstat for fontforge-20201107~dfsg fontforge-20201107~dfsg
changelog | 10
patches/0001-fix-splinefont-shell-command-injection-5367.patch | 181
++
patches/series |1
3 files changed, 192 insertions(+)
diff -Nru fontforge-20201107~dfsg/debian/changelog
fontforge-20201107~dfsg/debian/changelog
--- fontforge-20201107~dfsg/debian/changelog2021-01-15 17:55:46.0
+0200
+++ fontforge-20201107~dfsg/debian/changelog2024-03-15 22:56:38.0
+0200
@@ -1,3 +1,13 @@
+fontforge (1:20201107~dfsg-4+deb11u1) bullseye-security; urgency=medium
+
+ * Non-maintainer upload.
+ * CVE-2024-25081: Spline Font command injection via crafted filenames
+ * CVE-2024-25082: Spline Font command injection via crafted archives
+or compressed files
+ * Closes: #1064967
+
+ -- Adrian Bunk Fri, 15 Mar 2024 22:56:38 +0200
+
fontforge (1:20201107~dfsg-4) unstable; urgency=medium
* Rename extended to extendeddbl to avoid FTBFS on Hurd.
diff -Nru
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
---
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
1970-01-01 02:00:00.0 +0200
+++
fontforge-20201107~dfsg/debian/patches/0001-fix-splinefont-shell-command-injection-5367.patch
2024-03-15 22:48:11.0 +0200
@@ -0,0 +1,181 @@
+From 216eb14b558df344b206bf82e2bdaf03a1f2f429 Mon Sep 17 00:00:00 2001
+From: Peter Kydas
+Date: Tue, 6 Feb 2024 20:03:04 +1100
+Subject: fix splinefont shell command injection (#5367)
+
+---
+ fontforge/splinefont.c | 125 +
+ 1 file changed, 90 insertions(+), 35 deletions(-)
+
+diff --git a/fontforge/splinefont.c b/fontforge/splinefont.c
+index 239fdc035..647daee10 100644
+--- a/fontforge/splinefont.c
b/fontforge/splinefont.c
+@@ -788,11 +788,14 @@ return( name );
+
+ char *Unarchive(char *name, char **_archivedir) {
+ char *dir = getenv("TMPDIR");
+-char *pt, *archivedir, *listfile, *listcommand, *unarchivecmd,
*desiredfile;
++char *pt, *archivedir, *listfile, *desiredfile;
+ char *finalfile;
+ int i;
+ int doall=false;
+ static int cnt=0;
++gchar *command[5];
++gchar *stdoutresponse = NULL;
++gchar *stderrresponse = NULL;
+
+ *_archivedir = NULL;
+
+@@ -827,18 +830,30 @@ return( NULL );
+ listfile = malloc(strlen(archivedir)+strlen("/" TOC_NAME)+1);
+ sprintf( listfile, "%s/" TOC_NAME, archivedir );
+
+-listcommand = malloc( strlen(archivers[i].unarchive) + 1 +
+- strlen( archivers[i].listargs) + 1 +
+- strlen( name ) + 3 +
+- strlen( listfile ) +4 );
+-sprintf( listcommand, "%s %s %s > %s", archivers[i].unarchive,
+- archivers[i].listargs, name, listfile );
+-if ( system(listcommand)!=0 ) {
+- free(listcommand); free(listfile);
+- ArchiveCleanup(archivedir);
+-return( NULL );
+-}
+-free(listcommand);
++command[0] = archivers[i].unarchive;
++command[1] = archivers[i].listargs;
++command[2] = name;
++command[3] = NULL; // command args need to be NULL-terminated
++
++if ( g_spawn_sync(
++ NULL,
++ command,
++ NULL,
++ G_SPAWN_SEARCH_PATH,
++ NULL,
++ NULL,
++ ,
++ ,
++ NULL,
++ NULL
++ ) == FALSE) { // did not successfully execute
++ ArchiveCleanup(archivedir);
++ return( NULL );
++}
++// Write out the listfile to be read in later
++FILE *fp = fopen(listfile, "wb");
++fwrite(stdoutresponse, strlen(stdoutresponse), 1, fp);
++fclose(fp);
+
+ desiredfile =
Bug#1065701: rocm_agent_enumerator: crash on systems without AMD GPU
Hi Petter, On 2024-03-15 02:39, Petter Reinholdtsen wrote: [Cordell Bloor] Thanks Petter. After inspecting the code and reviewing both your report and the buildd logs, my conclusion is that this issue was fixed by upstream and included in 5.7.1-1. But your original report claimed it was present in version 5.7.1-1? Which version was used to trigger the error? reportbug noted that I had 5.7.1-1 installed, but my report was based on the rocm-hipamd autopkgtests run on the DebCI. I didn't notice that the DebCI was using a different version of rocminfo than me, as I'd assumed it used packages from Unstable. In retrospect, I suppose it makes sense that Testing is used as the base for the autopkgtests, since they're used to gate migration to Testing. Sincerely, Cory Bloor
Bug#1066948: prusa-slicer: No installable version on trixie
Package: prusa-slicer Version: 2.7.1+dfsg-1 Severity: normal X-Debbugs-Cc: x...@iki.fi Dear Maintainer, Looks like my system offers an upgrade for prusa-slicer, which is being kept back. The current/old version doesn't seem to appear available at all and the only one offered is from sid. That isn't reasonably installable either as it seems to replace or remove half the system. So, it looks like prusa-slicer is not availble and that effectively means trixie can not do 3d printing. Which has worked so far and works as long as I keep the old package that I luckily have on one machine. This seems like a situation that should never happen IMO. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prusa-slicer depends on: ii fonts-noto-cjk 1:20230817+repack1-3 ii fonts-noto-core 20201225-2 ii libboost-chrono1.83.01.83.0-2+b2 ii libboost-filesystem1.83.01.83.0-2+b2 ii libboost-log1.83.0 1.83.0-2+b2 ii libboost-thread1.83.01.83.0-2+b2 ii libc62.37-15 ii libcurl3-gnutls 8.5.0-2 ii libdbus-1-3 1.14.10-4 ii libexpat12.5.0-2+b2 ii libfontconfig1 2.15.0-1.1 ii libgcc-s114-20240201-3 ii libgl1 1.7.0-1 ii libglew2.2 2.2.0-4+b1 ii libglib2.0-0 2.78.4-1 ii libgmp10 2:6.3.0+dfsg-2+b1 ii libgtk-3-0 3.24.41-1 ii libimath-3-1-29 3.1.9-3+b2 ii libjpeg62-turbo 1:2.1.5-2+b2 ii libmpfr6 4.2.1-1+b1 ii libnlopt02.7.1-5+b2 ii libocct-data-exchange-7.67.6.3+dfsg1-7+b1 ii libocct-foundation-7.6 7.6.3+dfsg1-7+b1 ii libocct-modeling-algorithms-7.6 7.6.3+dfsg1-7+b1 ii libocct-modeling-data-7.67.6.3+dfsg1-7+b1 ii libocct-ocaf-7.6 7.6.3+dfsg1-7+b1 ii libopenvdb10.0 10.0.1-2+b2 ii libpng16-16 1.6.43-1 ii libqhull-r8.02020.2-6+b1 ii libqhullcpp8.0 2020.2-6+b1 ii libstdc++6 14-20240201-3 ii libtbb12 2021.11.0-2 ii libtbbmalloc22021.11.0-2 ii libwxbase3.2-1 3.2.4+dfsg-3 ii libwxgtk-gl3.2-1 3.2.4+dfsg-3 ii libwxgtk3.2-13.2.4+dfsg-3 ii zlib1g 1:1.3.dfsg-3+b1 prusa-slicer recommends no packages. prusa-slicer suggests no packages. -- no debconf information
Bug#1066848: freediameter: replace libidn11-dev with libidn-dev
Hi again,
I have uploaded a NMU with the patch below into DELAYED/10. Let me know
if you want to cancel it.
/Simon
Simon Josefsson writes:
> Hi Ruben, all,
>
> I have opened a merge request to resolve the bug below:
>
> https://salsa.debian.org/debian-mobcom-team/freediameter/-/merge_requests/4
>
> Are you able to merge and upload a new version?
>
> If you agree, and add me to the Salsa group, I can merge it and prepare
> the upload too.
>
> /Simon
>
> Simon Josefsson writes:
>
>> Package: freediameter
>> Version: 1.2.1-8
>> Tags: patch
>>
>> Hi! I'd like to drop the transitional package 'libidn11-dev' as most
>> packages have already moved to use 'libidn-dev' which is in stable.
>>
>> How about this patch?
>>
>> /Simon
>>
>> diff --git a/debian/control b/debian/control
>> index 335362a..2856eae 100644
>> --- a/debian/control
>> +++ b/debian/control
>> @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11),
>> libsctp-dev,
>> bison,
>> flex,
>> - libidn11-dev,
>> + libidn-dev,
>> libgcrypt20-dev,
>> libgnutls28-dev,
>> pkg-config,
>> @@ -63,7 +63,7 @@ Depends: libfdcore6 (= ${binary:Version}),
>> libfdproto6 (= ${binary:Version}),
>> libgnutls28-dev,
>> libgcrypt20-dev,
>> - libidn11-dev,
>> + libidn-dev,
>> libsctp-dev,
>> ${misc:Depends}
>> Description: Library for the Diameter protocol (development files)
>>
>
signature.asc
Description: PGP signature
Bug#1066947: zookeeper: CVE-2024-23944
Source: zookeeper Version: 3.9.1-1 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for zookeeper. CVE-2024-23944[0]: | Information disclosure in persistent watchers handling in Apache | ZooKeeper due to missing ACL check. It allows an attacker to monitor | child znodes by attaching a persistent watcher (addWatch command) to | a parent which the attacker has already access to. ZooKeeper server | doesn't do ACL check when the persistent watcher is triggered and as | a consequence, the full path of znodes that a watch event gets | triggered upon is exposed to the owner of the watcher. It's | important to note that only the path is exposed by this | vulnerability, not the data of znode, but since znode path can | contain sensitive information like user name or login ID, this issue | is potentially critical. Users are recommended to upgrade to | version 3.9.2, 3.8.4 which fixes the issue. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-23944 https://www.cve.org/CVERecord?id=CVE-2024-23944 [1] https://www.openwall.com/lists/oss-security/2024/03/14/2 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1066946: fix ftbfs with Python 3.12
Package: src:ros-ros-comm Version: 1.16.0+ds-3.1 Severity: important Tags: sid trixie patch User: debian-pyt...@lists.debian.org Usertags: python3.12 tests fail with Python 3.12, patch at http://launchpadlibrarian.net/719571248/ros-ros-comm_1.16.0+ds-3.1build2_1.16.0+ds-3.1ubuntu1.diff.gz
Bug#1066945: libglibmm-2.4-dev: Printing Glib::ustring containing non-ascii character throws exception
Package: libglibmm-2.4-dev
Version: 2.66.5-2
Severity: normal
X-Debbugs-Cc: gerardo.balla...@gmail.com
Dear Maintainer,
a C++ program of mine, when I tried printing a Glib::ustring that
contained a non-ascii UTF-8 character, threw an exception and aborted.
The following program reproduces the failure:
#include
#include
#include
int main()
{
std::cout << std::string("però") << std::endl; // works
std::cout << Glib::ustring("pero") << std::endl; // works
std::cout << Glib::ustring("però") << std::endl; // throws
return 0;
}
The third statement generates this error:
terminate called after throwing an instance of 'Glib::ConvertError'
Aborted
I thought that the reason why Glib::ustring was created was exactly to
handle UTF-8 characters correctly...
Thanks
Gerardo Ballabio
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libglibmm-2.4-dev depends on:
ii libglib2.0-dev2.74.6-2
ii libglibmm-2.4-1v5 2.66.5-2
ii libsigc++-2.0-dev 2.12.0-1
ii pkg-config1.8.1-1
ii pkgconf [pkg-config] 1.8.1-1
libglibmm-2.4-dev recommends no packages.
Versions of packages libglibmm-2.4-dev suggests:
pn libglibmm-2.4-doc
ii libgtkmm-3.0-dev 3.24.7-1
-- no debconf information
Bug#1066944: FTBFS on 32-bit arches with 64-bit time_t
Source: ulfius
Version: 2.7.15-2.1
Severity: serious
Tags: ftbfs patch upstream fixed-upstream
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=ulfius=armel=2.7.15-2.1=1709168616=0
/<>/src/u_websocket.c: In function ‘ulfius_websocket_wait_close’:
/<>/src/u_websocket.c:2316:28: error: conversion from ‘long long
int’ to ‘long int’ may change value [-Werror=conversion]
2316 | abstime.tv_nsec += (((time_t)timeout%1000) * 100);
|^
>From 9457809a5321ca4a87f19fdc3f7f4af68e72afa8 Mon Sep 17 00:00:00 2001
From: Nicolas Mora
Date: Wed, 28 Feb 2024 20:36:03 -0500
Subject: [PATCH] Fix timespec.tv_nsec value conversion
---
src/u_websocket.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/u_websocket.c b/src/u_websocket.c
index efca309..771f872 100644
--- a/src/u_websocket.c
+++ b/src/u_websocket.c
@@ -2322,7 +2322,7 @@ int ulfius_websocket_wait_close(struct _websocket_manager * websocket_manager, u
if (timeout) {
clock_gettime(CLOCK_REALTIME, );
abstime.tv_sec += ((time_t)timeout / 1000);
-abstime.tv_nsec += (((time_t)timeout%1000) * 100);
+abstime.tv_nsec += long int)timeout)%1000) * 100);
if (abstime.tv_nsec > 9) {
abstime.tv_nsec %= 10;
abstime.tv_sec ++;
--
2.43.0
Bug#1066113: guix: CVE-2024-27297
Hi, On Fri, Mar 15, 2024 at 11:22:52AM -0700, Vagrant Cascadian wrote: > On 2024-03-13, Vagrant Cascadian wrote: > > On 2024-03-12, Vagrant Cascadian wrote: > >> On 2024-03-12, Salvatore Bonaccorso wrote: > > I have now tested an updated 1.4.x package on bookworm and a 1.2.x > > package on bullseye, and the reproducer (with a small change for 1.2.x) > > was able to reproduce the problem before upgrading to the patched > > versions, but not after upgrading to a patched version. > > > > I've pushed fixes to various branches; debian/latest (for unstable), > > debian/bookworm and debian/bullseye: > > > > https://salsa.debian.org/debian/guix/ > > Attached should be debdiffs for updates for bookworm and bullseye. Let > me know if I should upload them or if someone from the security team > will! > > Guix did make a good blog post, and I am wondering if just referencing > it is sufficient, or if we should provide some of the instructions > directly in the secucity announcement? > > > https://guix.gnu.org/en/blog/2024/fixed-output-derivation-sandbox-bypass-cve-2024-27297/ > > The main things we might want to highlight are checking for corrupt > items in the store (which may be expensive, depending on how big of an > installation) and maybe also running the reproducer script (which needs > changes mentioned previously in order to work with 1.2.x from bullseye). > > Hrm. The upgrading instructions from the blog post are not really > relevent, as they are simply handled with "apt upgrade", so that might > be a little confusing. We had a look, and as per https://salsa.debian.org/security-tracker-team/security-tracker/-/commit/b11b98d89550ce201b0de31401e822c55f4fa2a1 we think that it does not require a DSA, but a fix in the upcoming point releases would be good. So can you submit it for the point releases? (make sure to adjust the target distribution to bullseye respetively bookworm instead of *-security). Thanks a lot for your work! Regards, Salvatore
Bug#1063308: transition: libvterm
On Mon, Mar 04, 2024 at 06:40:46AM -0500, James McCoy wrote: > On Mon, Feb 05, 2024 at 10:54:12PM -0500, James McCoy wrote: > > libvterm doesn't have a stable API/ABI yet, so although the SONAME > > didn't change, this is a breaking update. > > > > There are 3 packages which use libvterm: > > * pangoterm: I've filed #1063196 to RM the package, so it shouldn't > > block > > * emacs-libvterm: It supports building against either 0.1 or 0.3, so it > > just needs a binNMU > > * neovim: 0.7.2 (in unstable) only supports 0.1, but 0.9.5 (in > > experimental) supports 0.3. > > > > Ben file: > > > > title = "libvterm 0.1 -> 0.3"; > > is_affected = .build-depends ~ "libvterm-dev"; > > is_good = .depends ~ /libvterm0 \(>= 0\.[23]/; > > is_bad = .depends ~ /libvterm0 \(>= 0\.1/; > > This was ACKed on IRC, so I've uploaded libvterm and neovim. Now that cmake is available on arm* again, emacs-libvterm just needs a binNMU to finish this transition. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1066903: libgnt: please drop runtime dependencies
This sounds reasonable to. It looks like you beat me to this with an
NMU. Thanks!
On 2024-03-15 04:08, Gianfranco Costamagna wrote:
Package: libgnt
Version: 2.14.4-1.1
Severity: serious
Tags: patch
Hello, I found some runtime dependencies, such as removed libglib2.0-0
breaking every 32bit build except i386 due to
time64_t transition.
Please update, remove them, let debhelper evaluate them via shlibs:Depends.
Also I added libxml2-dev build-dependency, looks like the support was
not enabled.
before:
Run-time dependency glib-2.0 found: YES 2.79.3
Run-time dependency gobject-2.0 found: YES 2.79.3
Run-time dependency gmodule-2.0 found: YES 2.79.3
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency libxml-2.0 found: NO (tried pkgconfig and cmake)
Now:
Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
Run-time dependency glib-2.0 found: YES 2.79.3
Run-time dependency gobject-2.0 found: YES 2.79.3
Run-time dependency gmodule-2.0 found: YES 2.79.3
Run-time dependency libxml-2.0 found: YES 2.9.14
Also dpkg shows correct dependencies now:
Package: libgnt0t64
[...]
Depends: libc6 (>= 2.38), libglib2.0-0t64 (>= 2.75.3), libncursesw6 (>=
6), libtinfo6 (>= 6), libxml2 (>= 2.7.4)
Breaks: finch (<< 2.14.1), libgnt0 (<< 2.14.4-1.2)
Replaces: finch (<< 2.14.1), libgnt0
Provides: libgnt0 (= 2.14.4-1.2)
[...]
Thanks for considering the patch.
*** /tmp/tmpkfjro47y/libgnt_2.14.4-1.1ubuntu1.debdiff
diff -Nru libgnt-2.14.4/debian/control libgnt-2.14.4/debian/control
--- libgnt-2.14.4/debian/control 2024-03-08 06:22:50.0 +0100
+++ libgnt-2.14.4/debian/control 2024-03-15 09:59:05.0 +0100
@@ -1,6 +1,7 @@
libglib2.0-dev,
libglib2.0-doc,
libncurses-dev,
+ libxml2-dev,
meson,
Build-Depends-Indep: gtk-doc-tools,
Homepage: https://keep.imfreedom.org/libgnt/libgnt
@@ -18,10 +18,7 @@
Package: libgnt0t64
Provides: ${t64:Provides}
Architecture: any
-Depends: libglib2.0-0,
- libncursesw6,
- libxml2,
- ${misc:Depends},
+Depends: ${misc:Depends},
${shlibs:Depends},
Breaks: libgnt0 (<< ${source:Version}), finch (<< 2.14.1),
Replaces: libgnt0, finch (<< 2.14.1),
--
Richard
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1066444: nacl: FTBFS: ld: cannot find -lnsl: No such file or directory
control: retitle -1 nacl: FTBFS due to -Werror=implicit-function-declaration Hi, On 2024-03-13 13:03, Lucas Nussbaum wrote: > Source: nacl > Version: 20110221-13 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240313 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): [ snip] > > === Tue Mar 12 20:30:43 UTC 2024 === checking -lnsl > > /usr/bin/ld: cannot find -lnsl: No such file or directory > > collect2: error: ld returned 1 exit status The build system of nacl is totally nonstandard and difficult to understand, but it appears that this error is harmless. The real issue behind this FTBFS is the -Werror=implicit-function-declaration introduced by dpkg 1.22.6. Retitling the bug accordingly. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1066367: libsearpc: diff for NMU version 3.3.0+really3.3+git20230527.783141f-3.2
Control: tags 1066367 + patch Control: tags 1066367 + pending Dear maintainer, I've prepared an NMU for libsearpc (versioned as 3.3.0+really3.3+git20230527.783141f-3.2) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog --- libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog 2024-02-28 23:11:14.0 +0500 +++ libsearpc-3.3.0+really3.3+git20230527.783141f/debian/changelog 2024-03-16 00:36:38.0 +0500 @@ -1,3 +1,10 @@ +libsearpc (3.3.0+really3.3+git20230527.783141f-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066367). + + -- Andrey Rakhmatullin Sat, 16 Mar 2024 00:36:38 +0500 + libsearpc (3.3.0+really3.3+git20230527.783141f-3.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch --- libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/fix-implicit-function-declaration.patch 2024-03-16 00:35:16.0 +0500 @@ -0,0 +1,36 @@ +From d78aede0e4c559fa3dbce0e64ffc943da47fe76c Mon Sep 17 00:00:00 2001 +From: orbea +Date: Sat, 8 Apr 2023 17:13:55 -0700 +Subject: [PATCH] Fix -Werror=implicit-function-declaration + +unistd.h is needed for write, close and read +--- + demo/searpc-demo-packet.h | 1 + + demo/test-object.h| 2 ++ + 2 files changed, 3 insertions(+) + +diff --git a/demo/searpc-demo-packet.h b/demo/searpc-demo-packet.h +index 926f36b..6552396 100644 +--- a/demo/searpc-demo-packet.h b/demo/searpc-demo-packet.h +@@ -4,6 +4,7 @@ + + #include + #include ++#include + #include + + #ifdef WIN32 +diff --git a/demo/test-object.h b/demo/test-object.h +index f3f7589..a6d8b5d 100644 +--- a/demo/test-object.h b/demo/test-object.h +@@ -4,6 +4,8 @@ + #include + #include + ++GType test_object_get_type (void); ++ + #define TEST_OBJECT_TYPE(test_object_get_type()) + #define TEST_OBJECT(obj)(G_TYPE_CHECK_INSTANCE_CAST ((obj), TEST_OBJECT_TYPE, TestObject)) + #define IS_TEST_OBJCET(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), TEST_OBJCET_TYPE)) diff -Nru libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series --- libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series 2023-06-30 15:18:13.0 +0500 +++ libsearpc-3.3.0+really3.3+git20230527.783141f/debian/patches/series 2024-03-16 00:35:49.0 +0500 @@ -3,3 +3,4 @@ 0003-Use-argparse-in-searpc-codegen-for-basic-help.patch 0004-Use-g_realloc-in-named_pipe_client_handler.patch #0005-Fix-memory-leak.patch +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1066327: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 12:48:27PM +0100, Lucas Nussbaum wrote: > > chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ > > [-Werror=implicit-function-declaration] > > chm_http.c:179:9: error: implicit declaration of function ‘close’; did you > > mean ‘pclose’? [-Werror=implicit-function-declaration] These are fixed by including and but then there is an undefined pread64() in chm_lib.c, not sure what is the correct way to fix that. Gentoo fixed that by adding #define _LARGEFILE64_SOURCE to the file, but I hesitate to do that as I don't understand the implications of doing that on different architectures. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1051418: bad patch: debian/patches/0013-Fix-comparision-if-char-is-unsigned.patch
Control: found -1 30.0.2+dfsg-2.1+b1 Can trivially repro the issue and the fix: after reopening a session with an Xcomposite capture, clicking on it segfaults (strlen over NULL); rebuilding 30.0.2+dfsg-2 with 0013-Fix-comparision-* stripped from d/p/series fixes the segfault and works as-expected. Best, наб signature.asc Description: PGP signature
Bug#1066943: ntirpc: FTBFS: missing dependency on libnsl-dev
Source: ntirpc Version: 4.3-3.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=ntirpc=armel=4.3-3.1=1710521344=0 -- Looking for epoll_create -- Looking for epoll_create - found -- Found EPOLL: 1 -- Could NOT find NSL (missing: NSL_LIBRARY) -- -- --- -- TIRPC_EPOLL = TRUE -- USE_RPC_RDMA = OFF -- USE_GSS = ON -- USE_PROFILE = OFF -- USE_LTTNG_NTIRPC = OFF -- Configuring done (5.2s) CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: NSL_LIBRARY (ADVANCED) linked by target "ntirpc" in directory /<>/src -- Generating done (0.1s) CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY CMAKE_INSTALL_LIBDIR CMAKE_INSTALL_LOCALSTATEDIR CMAKE_INSTALL_RUNSTATEDIR CMAKE_INSTALL_SYSCONFDIR FETCHCONTENT_FULLY_DISCONNECTED CMake Generate step failed. Build files cannot be regenerated correctly. Cheers> -- Sebastian Ramacher
Bug#1066942: xmrig: FTBFS on armhf: cc: error: unrecognized command-line option ‘-maes’
Source: xmrig Version: 6.21.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=xmrig=armhf=6.21.1%2Bdfsg-1%2Bb1=1710494247=0 cd /<>/obj-arm-linux-gnueabihf/src/3rdparty/argon2 && /usr/bin/cc -DCL_TARGET_OPENCL_VERSION=200 -DCL_USE_DEPRECATED_OPENCL_1_2_APIS -DHAVE_BUILTIN_CLEAR_CACHE -DHAVE_ROTR -DHAVE_SYSLOG_H -DUNICODE -DXMRIG_ALGO_ARGON2 -DXMRIG_ALGO_RANDOMX -DXMRIG_FEATURE_ADL -DXMRIG_FEATURE_API -DXMRIG_FEATURE_BENCHMARK -DXMRIG_FEATURE_CUDA -DXMRIG_FEATURE_ENV -DXMRIG_FEATURE_HTTP -DXMRIG_FEATURE_HWLOC -DXMRIG_FEATURE_NVML -DXMRIG_FEATURE_OPENCL -DXMRIG_JSON_SINGLE_LINE_ARRAY -DXMRIG_MINER_PROJECT -DXMRIG_OS_LINUX -DXMRIG_OS_UNIX -DXMRIG_STRICT_OPENCL_CACHE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D__STDC_FORMAT_MACROS -I/<>/src/3rdparty/argon2/../.. -I/<>/src/3rdparty/argon2/lib -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-strict-aliasing -maes -std=gnu99 -MD -MT src/3rdparty/argon2/CMakeFiles/argon2.dir/lib/impl-select.c.o -MF CMakeFiles/argon2.dir/lib/impl-select.c.o.d -o CMakeFiles/argon2.dir/lib/impl-select.c.o -c /<>/src/3rdparty/argon2/lib/impl-select.c cc: error: unrecognized command-line option ‘-maes’ Cheers -- Sebastian Ramacher
Bug#1066531: policykit-1: FTBFS: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration]
Control: tags -1 - patch On Wed, 13 Mar 2024 13:01:49 + Mark Hindley wrote: Control: tags -1 patch I also bumped into this whilst rebuilding src:policykit-1 yesterday. There is an upstream patch[1], but it doesn't fix the build for me; I think it is patching the wrong files.The problem appears to be multiple copies of mocklibc. AFAICS ./test/mocklibc is not used in favour of a meson subproject. The pkla-compat tarball also has mocklibc, but that is also patched already. Getting the multiple layers of quilt and meson patches to work was unpleasant. So the attached patch may save you some time. HTH Mark [1] https://github.com/polkit-org/polkit/commit/0d78d1e4bf5ab3ce11678005b220aac0cfc5bee5 Thanks for the patch Unfortunately it fails to apply to the src:policykit-1 package as shipped in Debian sid. Thus marking the bug report accordingly. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1066941: coz-profiler: FTBFS: what(): unknown compilation unit version 5
Source: coz-profiler
Version: 0.2.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=coz-profiler=amd64=0.2.2-2%2Bb1=1710517462=0
printf "int main(int argc, char *argv[])\n{\nreturn (0);\n}\n" > x.c
gcc -g -o x x.c || ( rm -f x x.c ; exit 1)
../coz run --- ./x
␛[34m[libcoz.cpp:100] ␛[01;34mbootstrapping coz␛[0m
␛[34m[libcoz.cpp:128] ␛[01;34mIncluding MAIN, which is
/<>/libcoz/x␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/<>/libcoz/libcoz.so is not in
scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libdwarf++.so.0 is not
in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
is not in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.33 is
not in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libelf++.so.0 is not
in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libgcc_s.so.1 is not
in scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libc.so.6 is not in
scope␛[0m
␛[34m[inspect.cpp:325] ␛[01;34m/usr/lib/x86_64-linux-gnu/libm.so.6 is not in
scope␛[0m
terminate called after throwing an instance of 'dwarf::format_error'
what(): unknown compilation unit version 5
make[3]: *** [Makefile:12: check] Error 250
Cheers
--
Sebastian Ramacher
Bug#1066940: RFP: aiotdlib -- Python asyncio Telegram client
Package: wnpp Severity: wishlist * Package name: aiotdlib Version : 0.22.0 Upstream Author : pylakey * URL or Web page : https://github.com/pylakey/aiotdlib * License : MIT Programming Lang: Python Description : Python asyncio Telegram client Dependency for slidge-slidgram (#1066937). Needs tdlib.
Bug#1066939: xboxdrv: FTBFS on arm{el,hf}: src/linux_uinput.cpp:294:20: error: ‘struct input_event’ has no member named ‘time’
Source: xboxdrv
Version: 0.8.8-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=xboxdrv=armhf=0.8.8-3%2Bb1=1710520170=0
g++ -o src/linux_uinput.o -c -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-isystem/usr/include/dbus-1.0
-isystem/usr/lib/arm-linux-gnueabihf/dbus-1.0/include
-isystem/usr/include/glib-2.0
-isystem/usr/lib/arm-linux-gnueabihf/glib-2.0/include -pthread
-isystem/usr/include/libusb-1.0 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3 -Wall -ansi -pedantic
-DPACKAGE_VERSION='"0.8.8"' -Isrc src/linux_uinput.cpp
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’
is not valid for C++
In file included from /usr/include/boost/function/detail/requires_cxx11.hpp:9,
from /usr/include/boost/function/detail/prologue.hpp:12,
from /usr/include/boost/function.hpp:30,
from src/linux_uinput.hpp:22,
from src/linux_uinput.cpp:19:
/usr/include/boost/function/detail/requires_cxx11.hpp:18:1: note: ‘#pragma
message: C++03 support was deprecated in Boost.Function 1.82 and will be
removed in Boost.Function 1.84. Please open an issue in
https://github.com/boostorg/function if you want it retained.’
18 | BOOST_PRAGMA_MESSAGE("C++03 support was deprecated in Boost.Function
1.82 and will be removed in Boost.Function 1.84. Please open an issue in
https://github.com/boostorg/function if you want it retained.")
| ^~~~
/usr/include/boost/bind/detail/requires_cxx11.hpp:18:1: note: ‘#pragma message:
C++03 support was deprecated in Boost.Bind 1.82 and will be removed in
Boost.Bind 1.84. Please open an issue in https://github.com/boostorg/bind if
you want it retained.’
18 | BOOST_PRAGMA_MESSAGE("C++03 support was deprecated in Boost.Bind 1.82
and will be removed in Boost.Bind 1.84. Please open an issue in
https://github.com/boostorg/bind if you want it retained.")
| ^~~~
/usr/include/boost/smart_ptr/detail/requires_cxx11.hpp:19:1: note: ‘#pragma
message: C++03 support was deprecated in Boost.SmartPtr 1.82 and will be
removed in Boost.SmartPtr 1.84. Please open an issue in
https://github.com/boostorg/smart_ptr if you want it retained.’
19 | BOOST_PRAGMA_MESSAGE("C++03 support was deprecated in Boost.SmartPtr
1.82 and will be removed in Boost.SmartPtr 1.84. Please open an issue in
https://github.com/boostorg/smart_ptr if you want it retained.")
| ^~~~
/usr/include/boost/lexical_cast.hpp:40:1: note: ‘#pragma message: C++03 support
is deprecated in Boost.LexicalCast 1.82 and will be removed in
Boost.LexicalCast 1.84.’
40 | BOOST_PRAGMA_MESSAGE("C++03 support is deprecated in Boost.LexicalCast
1.82 and will be removed in Boost.LexicalCast 1.84.")
| ^~~~
src/linux_uinput.cpp: In member function ‘void LinuxUinput::send(uint16_t,
uint16_t, int32_t)’:
src/linux_uinput.cpp:294:20: error: ‘struct input_event’ has no member named
‘time’
294 | gettimeofday(, NULL);
|^~~~
scons: *** [src/linux_uinput.o] Error 1
scons: building terminated because of errors.
Cheers
--
Sebastian Ramacher
Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined
Source: libfiu Version: 1.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=libfiu=armhf=1.2-2=1710292712=0 cc -D_XOPEN_SOURCE=600 -fPIC -DFIU_ENABLE=1 -D_LARGEFILE64_SOURCE=1 -I. -I../../libfiu/ -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -D_GNU_SOURCE -c codegen.c -o codegen.o /tmp/cc54dEva.s: Assembler messages: /tmp/cc54dEva.s:726: Error: symbol `open64' is already defined /tmp/cchEoHpC.s: Assembler messages: /tmp/cchEoHpC.s:474: Error: symbol `mmap64' is already defined make[4]: *** [Makefile:67: modules/posix.mm.mod.o] Error 1 make[4]: *** Waiting for unfinished jobs make[4]: *** [Makefile:67: modules/posix.custom.o] Error 1 /tmp/cct4HXD3.s: Assembler messages: /tmp/cct4HXD3.s:1810: Error: symbol `pread64' is already defined /tmp/cct4HXD3.s:3995: Error: symbol `pwrite64' is already defined /tmp/cct4HXD3.s:5803: Error: symbol `truncate64' is already defined /tmp/cct4HXD3.s:6480: Error: symbol `ftruncate64' is already defined /tmp/ccInAMjZ.s: Assembler messages: /tmp/ccInAMjZ.s:437: Error: symbol `fopen64' is already defined make[4]: *** [Makefile:67: modules/posix.io.mod.o] Error 1 /tmp/ccInAMjZ.s:1099: Error: symbol `freopen64' is already defined /tmp/ccInAMjZ.s:3393: Error: symbol `tmpfile64' is already defined /tmp/ccInAMjZ.s:5973: Error: symbol `ftello64' is already defined /tmp/ccInAMjZ.s:7007: Error: symbol `fseeko64' is already defined /tmp/ccInAMjZ.s:7699: Error: symbol `fsetpos64' is already defined make[4]: *** [Makefile:67: modules/posix.stdio.mod.o] Error 1 Cheers -- Sebastian Ramacher
Bug#1066515: pmount: diff for NMU version 0.9.23-7.1
Control: tags 1066515 + patch Control: tags 1066515 + pending Dear maintainer, I've prepared an NMU for pmount (versioned as 0.9.23-7.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru pmount-0.9.23/debian/changelog pmount-0.9.23/debian/changelog --- pmount-0.9.23/debian/changelog 2023-09-14 12:58:36.0 +0500 +++ pmount-0.9.23/debian/changelog 2024-03-15 23:43:49.0 +0500 @@ -1,3 +1,10 @@ +pmount (0.9.23-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066515). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 23:43:49 +0500 + pmount (0.9.23-7) unstable; urgency=medium * New maintainer. Closes: #689854 diff -Nru pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch --- pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ pmount-0.9.23/debian/patches/fix-implicit-function-declaration.patch 2024-03-15 23:43:49.0 +0500 @@ -0,0 +1,18 @@ +Description: Add missing header includes. +Author: Andrey Rakhmatullin +Bug-Debian: https://bugs.debian.org/1066515 +Last-Update: 2024-03-15 + +Index: pmount-0.9.23/src/luks.c +=== +--- pmount-0.9.23.orig/src/luks.c pmount-0.9.23/src/luks.c +@@ -16,6 +16,8 @@ + #include + #include + #include ++#include ++#include + + + /* If CRYPTSETUP_RUID is set, we run cryptsetup with ruid = euid = 0. diff -Nru pmount-0.9.23/debian/patches/series pmount-0.9.23/debian/patches/series --- pmount-0.9.23/debian/patches/series 2023-09-14 12:58:36.0 +0500 +++ pmount-0.9.23/debian/patches/series 2024-03-15 23:43:32.0 +0500 @@ -1,3 +1,4 @@ 01-man-plugdev.diff 10_fix-spelling-binary-errors.patch 20_fix-spelling-manpage-error.patch +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1066465: dcraw: diff for NMU version 9.28-3.1
Control: tags 1066465 + patch Control: tags 1066465 + pending Dear maintainer, I've prepared an NMU for dcraw (versioned as 9.28-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru dcraw-9.28/debian/changelog dcraw-9.28/debian/changelog --- dcraw-9.28/debian/changelog 2021-11-22 03:15:39.0 +0500 +++ dcraw-9.28/debian/changelog 2024-03-15 23:31:51.0 +0500 @@ -1,3 +1,10 @@ +dcraw (9.28-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066465). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 23:31:51 +0500 + dcraw (9.28-3) unstable; urgency=medium * Written wrappers of fread(),fwrite(),fseek() library functions which diff -Nru dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch --- dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ dcraw-9.28/debian/patches/fix-implicit-function-declaration.patch 2024-03-15 23:31:51.0 +0500 @@ -0,0 +1,41 @@ +Description: Add missing header includes. +Author: Andrey Rakhmatullin +Bug-Debian: https://bugs.debian.org/1066465 +Last-Update: 2024-03-15 + +Index: dcraw-9.28/fujiturn.c +=== +--- dcraw-9.28.orig/fujiturn.c dcraw-9.28/fujiturn.c +@@ -15,6 +15,7 @@ + #include + #include + #include ++#include + + #ifdef _16BIT + typedef unsigned short value; +Index: dcraw-9.28/fuji_green.c +=== +--- dcraw-9.28.orig/fuji_green.c dcraw-9.28/fuji_green.c +@@ -11,6 +11,8 @@ + #include + #include + #include ++#include ++#include + + #define ushort UshORt + typedef unsigned char uchar; +Index: dcraw-9.28/Makefile.am +=== +--- dcraw-9.28.orig/Makefile.am dcraw-9.28/Makefile.am +@@ -14,5 +14,6 @@ dcfujiturn16_SOURCES = fujiturn.c + dcfujiturn16_CFLAGS = -D_16BIT + + dcfujigreen_SOURCES = fuji_green.c ++dcfujigreen_CFLAGS = -D_XOPEN_SOURCE + + dccleancrw_SOURCES = clean_crw.c diff -Nru dcraw-9.28/debian/patches/series dcraw-9.28/debian/patches/series --- dcraw-9.28/debian/patches/series 2021-11-22 03:15:39.0 +0500 +++ dcraw-9.28/debian/patches/series 2024-03-15 23:31:51.0 +0500 @@ -6,3 +6,4 @@ 906529.patch 906530.patch iowrap.diff +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1066937: RFP: slidge-slidgram -- feature-rich Telegram to XMPP puppeteering gateway
Package: wnpp Severity: wishlist * Package name: slidge-slidgram Version : git master 75f8aafc Upstream Author : Nicolas Cedilnik * URL or Web page : https://git.sr.ht/~nicoco/slidgram * License : AGPL-3 Programming Lang: Python Description : feature-rich Telegram to XMPP puppeteering gateway Depends on slidge (already in Debian) and aiotdlib.
Bug#1066234: php8.2: diff for NMU version 8.2.16-2.1
Control: tags 1066234 + patch Control: tags 1066234 + pending Dear maintainer, I've prepared an NMU for php8.2 (versioned as 8.2.16-2.1) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru php8.2-8.2.16/debian/changelog php8.2-8.2.16/debian/changelog --- php8.2-8.2.16/debian/changelog 2024-02-18 12:09:07.0 +0500 +++ php8.2-8.2.16/debian/changelog 2024-03-15 23:36:01.0 +0500 @@ -1,3 +1,10 @@ +php8.2 (8.2.16-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066234). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 23:36:01 +0500 + php8.2 (8.2.16-2) unstable; urgency=medium * Regenerate d/tests for correct PHP version (Closes: #1064174) diff -Nru php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch --- php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch 1970-01-01 05:00:00.0 +0500 +++ php8.2-8.2.16/debian/patches/fix-implicit-function-declaration.patch 2024-03-15 22:28:43.0 +0500 @@ -0,0 +1,15 @@ +Description: Add missing header includes. +Author: Andrey Rakhmatullin +Bug-Debian: https://bugs.debian.org/1066234 +Last-Update: 2024-03-15 + +--- php8.2-8.2.16.orig/ext/standard/credits.c php8.2-8.2.16/ext/standard/credits.c +@@ -24,6 +24,7 @@ + #include "php.h" + #include "info.h" + #include "SAPI.h" ++#include "credits.h" + + #define CREDIT_LINE(module, authors) php_info_print_table_row(2, module, authors) + diff -Nru php8.2-8.2.16/debian/patches/series php8.2-8.2.16/debian/patches/series --- php8.2-8.2.16/debian/patches/series 2024-02-18 12:09:07.0 +0500 +++ php8.2-8.2.16/debian/patches/series 2024-03-15 22:28:28.0 +0500 @@ -45,3 +45,4 @@ 0045-scripts-php-.in-Explicitly-define-the-path-to-sed.patch 0046-Remove-timestamps-from-phar.patch 0047-Disable-garbage-collection-routine.patch +fix-implicit-function-declaration.patch signature.asc Description: PGP signature
Bug#1066936: Qt5 Wayland applications with touch support crash
Package: libqt5waylandclient5
Version: 5.15.8-2
Native Wayland Qt5 applications with touchscreen support have a nasty tendency
to segfault while receiving touch input, especially when one is trying to write
using a stylus as the palm also makes contact with the touchscreen. This issue
has only been recently fixed in Qt 6.7 and as far as I know there is no
upstream fix at the moment for Qt 5.15. An if statement (highlighted with
pointer arrow) is added to function QWaylandInputDevice::Touch::touch_frame()
in qwaylandinputdevice.cpp in Qt 6.7 to fix the bug:
if (mFocus) {
// Returns a reference to the last item in the list. The list must not
be empty.
// If the list can be empty, call isEmpty() before calling this
function.
// See: https://doc.qt.io/qt-5.15/qlist.html#last
-> if (mPendingTouchPoints.empty())
return;
const QWindowSystemInterface::TouchPoint =
mPendingTouchPoints.constLast();
I encountered the issue using MrWriter, compiled from source, on Ubuntu 22.04
(linked against Qt 5.15.3). Said issue was severe enough in my experience to
interfere with day-to-day activities. As Ubuntu is downstream to Debian, I
thought it would be better if I report the bug here.
Bug#1066113: guix: CVE-2024-27297
On 2024-03-13, Vagrant Cascadian wrote: > On 2024-03-12, Vagrant Cascadian wrote: >> On 2024-03-12, Salvatore Bonaccorso wrote: > I have now tested an updated 1.4.x package on bookworm and a 1.2.x > package on bullseye, and the reproducer (with a small change for 1.2.x) > was able to reproduce the problem before upgrading to the patched > versions, but not after upgrading to a patched version. > > I've pushed fixes to various branches; debian/latest (for unstable), > debian/bookworm and debian/bullseye: > > https://salsa.debian.org/debian/guix/ Attached should be debdiffs for updates for bookworm and bullseye. Let me know if I should upload them or if someone from the security team will! Guix did make a good blog post, and I am wondering if just referencing it is sufficient, or if we should provide some of the instructions directly in the secucity announcement? https://guix.gnu.org/en/blog/2024/fixed-output-derivation-sandbox-bypass-cve-2024-27297/ The main things we might want to highlight are checking for corrupt items in the store (which may be expensive, depending on how big of an installation) and maybe also running the reproducer script (which needs changes mentioned previously in order to work with 1.2.x from bullseye). Hrm. The upgrading instructions from the blog post are not really relevent, as they are simply handled with "apt upgrade", so that might be a little confusing. live well, vagrant guix_1.2.0-4+deb11u2.debdiff Description: Binary data guix-1.4.0-3+deb12u1.debdiff Description: Binary data signature.asc Description: PGP signature
Bug#1066220: mono: diff for NMU version 6.8.0.105+dfsg-3.6
Control: tags 1066220 + patch Control: tags 1066220 + pending Dear maintainer, I've prepared an NMU for mono (versioned as 6.8.0.105+dfsg-3.6) and uploaded it to unstable. Regards. -- WBR, wRAR diff -Nru mono-6.8.0.105+dfsg/debian/changelog mono-6.8.0.105+dfsg/debian/changelog --- mono-6.8.0.105+dfsg/debian/changelog 2023-09-06 17:03:58.0 +0500 +++ mono-6.8.0.105+dfsg/debian/changelog 2024-03-15 22:02:36.0 +0500 @@ -1,3 +1,10 @@ +mono (6.8.0.105+dfsg-3.6) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with -Werror=implicit-function-declaration (Closes: #1066220). + + -- Andrey Rakhmatullin Fri, 15 Mar 2024 22:02:36 +0500 + mono (6.8.0.105+dfsg-3.5) unstable; urgency=medium * Non-maintainer upload. diff -Nru mono-6.8.0.105+dfsg/debian/patches/debian-changes mono-6.8.0.105+dfsg/debian/patches/debian-changes --- mono-6.8.0.105+dfsg/debian/patches/debian-changes 2023-09-06 17:03:58.0 +0500 +++ mono-6.8.0.105+dfsg/debian/patches/debian-changes 2024-03-15 22:02:36.0 +0500 @@ -24,6 +24,108 @@ Reviewed-By: Last-Update: 2021-06-29 +Index: mono-6.8.0.105+dfsg/Makefile.am +=== +Index: mono-6.8.0.105+dfsg/configure.ac +=== +Index: mono-6.8.0.105+dfsg/data/mono-cairo.pc.in +=== +Index: mono-6.8.0.105+dfsg/data/mono.pc.in +=== +Index: mono-6.8.0.105+dfsg/docs/docs.make +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/DocUtils.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/DocumentationEnumerator.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/CppFormatters/CppFullMemberFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/FSharpFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/JsFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/api-doc-tools/mdoc/Mono.Documentation/Updater/Formatters/JsMemberFormatter.cs +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/build/monodroid/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/build/monotouch/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/mono/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v2.0/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v3.5/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.0/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.5.1/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.5.2/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.5/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.6.1/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.6.2/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.6/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.7.1/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.7.2/Makefile +=== +Index: mono-6.8.0.105+dfsg/external/binary-reference-assemblies/v4.7/Makefile
Bug#1066935: imagemagick: NMU diff for 64-bit time_t transition (second fix)
Package: imagemagick
Version: 6.9.12.98+dfsg1-5.1
Severity: normal
Tags: patch
Hello, some dependencies were incorrectly generated, leading to impossibility
to install the package on armhf.
Thanks for considering the patch.
*** /tmp/tmpx4ebe5bv/imagemagick_8:6.9.12.98+dfsg1-5.1ubuntu1.debdiff
diff -Nru imagemagick-6.9.12.98+dfsg1/debian/control.d/quantum.in
imagemagick-6.9.12.98+dfsg1/debian/control.d/quantum.in
--- imagemagick-6.9.12.98+dfsg1/debian/control.d/quantum.in 2023-12-27
11:29:58.0 +0100
+++ imagemagick-6.9.12.98+dfsg1/debian/control.d/quantum.in 2024-03-15
16:00:07.0 +0100
@@ -31,7 +31,7 @@
# predepend on dpkg (>= 1.17.6) for libgomp symbols remove after jeesie +2
# normally depends on imagemagick-${IMVERSION}-common >= ${source:version}
except
# here when some files were moved between two packages
-Package: libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION}
+Package: libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION}t64
Architecture: any
Multi-Arch: same
Section: libs
@@ -59,7 +59,7 @@
Section: libs
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
-Enhances: libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION}
+Enhances: libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION}t64
Provides: libmagickcore-extra,
libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-1-extra,
libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-2-extra,
libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-3-extra,
@@ -82,7 +82,7 @@
Pre-Depends: dpkg (>= 1.17.11)
Depends:
libmagickcore-${IMVERSION}-arch-config (= ${binary:Version}),
- libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION} (=
${binary:Version}),
+ libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION}t64 (=
${binary:Version}),
libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION}-extra (=
${binary:Version}),
libbz2-dev, libdjvulibre-dev,
libexif-dev, libfreetype-dev, libjpeg-dev, libopenjp2-7-dev,
diff -Nru
imagemagick-6.9.12.98+dfsg1/debian/libmagickcore-IMVERSION.QUANTUMDEPTH-CORESOVERSION.symbols.in
imagemagick-6.9.12.98+dfsg1/debian/libmagickcore-IMVERSION.QUANTUMDEPTH-CORESOVERSION.symbols.in
---
imagemagick-6.9.12.98+dfsg1/debian/libmagickcore-IMVERSION.QUANTUMDEPTH-CORESOVERSION.symbols.in
2023-12-27 11:29:58.0 +0100
+++
imagemagick-6.9.12.98+dfsg1/debian/libmagickcore-IMVERSION.QUANTUMDEPTH-CORESOVERSION.symbols.in
2024-03-15 16:00:40.0 +0100
@@ -1,5 +1,5 @@
# SymbolsHelper-Confirmed: 1.0.0 amd64
-libMagickCore-${IMVERSION}.${UCQUANTUMDEPTH}.so.${CORESOVERSION}
libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION} #MINVER#
+libMagickCore-${IMVERSION}.${UCQUANTUMDEPTH}.so.${CORESOVERSION}
libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-${CORESOVERSION}t64 #MINVER#
* Build-Depends-Package: libmagickcore-${IMVERSION}.${QUANTUMDEPTH}-dev
(regex|optional)"^.gomp_critical_user_.*@Base" 8:6.9.10.2
AcquireAlignedMemory@Base 8:6.9.10.2
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'),
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x86
Kernel: Linux 6.2.0-35-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1066934: ruby3.1: diff for NMU version 3.1.2-8.2
Package: ruby3.1 Version: 3.1.2-8.1~exp1 Severity: normal Tags: patch pending Dear maintainer, I've uploaded an NMU for ruby3.1 (versioned as 3.1.2-8.2). The diff is attached to this message. I skipped waiting to help along with the currently ongoing t64 transition, and I figured you'll want to transition to ruby3.2 after that anyway. HTH, Chris diff -Nru ruby3.1-3.1.2/debian/changelog ruby3.1-3.1.2/debian/changelog --- ruby3.1-3.1.2/debian/changelog 2024-02-03 22:03:22.0 +0100 +++ ruby3.1-3.1.2/debian/changelog 2024-03-15 17:44:11.0 +0100 @@ -1,3 +1,14 @@ +ruby3.1 (3.1.2-8.2) unstable; urgency=medium + + * Non-maintainer upload. + * Release to unstable. + * Update test certificates from ruby 3.2.3. (Closes: #1064034) + * Disable test needing a working DNS resolver. + * Build-Depend on new dpkg-dev to ensure getting time_t 64bit flags. +(Closes: #1062873) + + -- Chris Hofstaedtler Fri, 15 Mar 2024 17:44:11 +0100 + ruby3.1 (3.1.2-8.1~exp1) experimental; urgency=medium * Non-maintainer upload. diff -Nru ruby3.1-3.1.2/debian/control ruby3.1-3.1.2/debian/control --- ruby3.1-3.1.2/debian/control 2024-02-03 22:03:22.0 +0100 +++ ruby3.1-3.1.2/debian/control 2024-03-15 17:44:11.0 +0100 @@ -8,6 +8,7 @@ Build-Depends: bison, coreutils (>= 7.5), debhelper-compat (= 13), + dpkg-dev (>= 1.22.6), file, libffi-dev, libgdbm-compat-dev, diff -Nru ruby3.1-3.1.2/debian/patches/0004-Disable-tests-failing-on-Ubuntu-builders.patch ruby3.1-3.1.2/debian/patches/0004-Disable-tests-failing-on-Ubuntu-builders.patch --- ruby3.1-3.1.2/debian/patches/0004-Disable-tests-failing-on-Ubuntu-builders.patch 2023-12-08 20:40:32.0 +0100 +++ ruby3.1-3.1.2/debian/patches/0004-Disable-tests-failing-on-Ubuntu-builders.patch 2024-03-15 17:44:11.0 +0100 @@ -1,25 +1,16 @@ From: Chris Hofstaedtler -Date: Sat, 6 Oct 2018 11:43:33 -0300 -Subject: Disable tests failing on Ubuntu builders +Date: Fri, 15 Mar 2024 18:13:07 +0100 +Subject: Disable some problematic tests - test/excludes/TestFileUtils.rb | 1 + - test/excludes/TestProcess.rb | 1 + - 2 files changed, 2 insertions(+) - create mode 100644 test/excludes/TestFileUtils.rb - create mode 100644 test/excludes/TestProcess.rb - -diff --git a/test/excludes/TestFileUtils.rb b/test/excludes/TestFileUtils.rb -new file mode 100644 -index 000..ee8b15c --- /dev/null -+++ b/test/excludes/TestFileUtils.rb ruby3.1-3.1.2/test/excludes/TestFileUtils.rb @@ -0,0 +1 @@ +exclude :test_chown, "fails on Launchpad builders" -diff --git a/test/excludes/TestProcess.rb b/test/excludes/TestProcess.rb -new file mode 100644 -index 000..37b406e --- /dev/null -+++ b/test/excludes/TestProcess.rb ruby3.1-3.1.2/test/excludes/TestProcess.rb @@ -0,0 +1 @@ +exclude :test_execopts_gid, "fails on Launchpad builders" +--- /dev/null 2024-03-15 17:16:31.66800 +0100 ruby3.1-3.1.2/test/excludes/TestAddressResolve.rb 2024-03-15 18:12:06.0 +0100 +@@ -0,0 +1 @@ ++exclude :test_socket_getnameinfo_domain_blocking, "No internet in buildd" diff -Nru ruby3.1-3.1.2/debian/patches/series ruby3.1-3.1.2/debian/patches/series --- ruby3.1-3.1.2/debian/patches/series 2023-12-08 20:40:32.0 +0100 +++ ruby3.1-3.1.2/debian/patches/series 2024-03-15 17:41:16.0 +0100 @@ -16,3 +16,4 @@ Merge-CGI-0.3.5.patch openssl-3.0.1.patch Fix-splitting-relative-URI.patch +Update-test-certificates.patch diff -Nru ruby3.1-3.1.2/debian/patches/Update-test-certificates.patch ruby3.1-3.1.2/debian/patches/Update-test-certificates.patch --- ruby3.1-3.1.2/debian/patches/Update-test-certificates.patch 1970-01-01 01:00:00.0 +0100 +++ ruby3.1-3.1.2/debian/patches/Update-test-certificates.patch 2024-03-15 17:42:40.0 +0100 @@ -0,0 +1,217 @@ +Index: ruby3.1-3.1.2/test/net/fixtures/cacert.pem +=== +--- ruby3.1-3.1.2.orig/test/net/fixtures/cacert.pem ruby3.1-3.1.2/test/net/fixtures/cacert.pem +@@ -1,24 +1,24 @@ + -BEGIN CERTIFICATE- +-MIID7TCCAtWgAwIBAgIJAIltvxrFAuSnMA0GCSqGSIb3DQEBCwUAMIGMMQswCQYD +-VQQGEwJKUDEQMA4GA1UECAwHU2hpbWFuZTEUMBIGA1UEBwwLTWF0ei1lIGNpdHkx +-FzAVBgNVBAoMDlJ1YnkgQ29yZSBUZWFtMRUwEwYDVQQDDAxSdWJ5IFRlc3QgQ0Ex +-JTAjBgkqhkiG9w0BCQEWFnNlY3VyaXR5QHJ1YnktbGFuZy5vcmcwHhcNMTkwMTAy +-MDI1ODI4WhcNMjQwMTAxMDI1ODI4WjCBjDELMAkGA1UEBhMCSlAxEDAOBgNVBAgM +-B1NoaW1hbmUxFDASBgNVBAcMC01hdHotZSBjaXR5MRcwFQYDVQQKDA5SdWJ5IENv +-cmUgVGVhbTEVMBMGA1UEAwwMUnVieSBUZXN0IENBMSUwIwYJKoZIhvcNAQkBFhZz +-ZWN1cml0eUBydWJ5LWxhbmcub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB +-CgKCAQEAznlbjRVhz1NlutHVrhcGnK8W0qug2ujKXv1njSC4U6nJF6py7I9EeehV +-SaKePyv+I9z3K1LnfUHOtUbdwdKC77yN66A6q2aqzu5q09/NSykcZGOIF0GuItYI +-3nvW3IqBddff2ffsyR+9pBjfb5AIPP08WowF9q4s1eGULwZc4w2B8PFhtxYANd7d +-BvGLXFlcufv9tDtzyRi4t7eqxCRJkZQIZNZ6DHHIJrNxejOILfHLarI12yk8VK6L
Bug#1066314: regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> This is most likely caused by a change in dpkg 1.22.6, that enabled
> -Werror=implicit-function-declaration. For more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
>
> Relevant part (hopefully):
> > cc -DNDEBUG -g -O2 -Werror=implicit-function-declaration
> > -ffile-prefix-map=/<>=. -fstack-protector-strong
> > -fstack-clash-protection -Wformat -Werror=format-security
+-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2
-DREGINA_SHARE_DIRECTORY=\"//usr/share/regina-rexx\" -funsigned-char
-DREGINA_VERSION_DATE=\""31 Dec 2011"\" -DREGINA_VERSION_MAJOR=\"3\"
+-DREGINA_VERSION_MINOR=\"6\" -DREGINA_VERSION_SUPP=\"\"
-DHAVE_CONFIG_H-I. -I. -I./contrib-o rexxext.o -c ./rexxext.c
> > ./rexxext.c: In function ‘__regina_rex_getcallstack’:
> > ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’;
> > did you mean ‘popcallstack’? [-Werror=implicit-function-declaration]
> >95 | getcallstack( TSD, parms->value );
> > | ^~~~
> > | popcallstack
> > cc1: some warnings being treated as errors
> > make[1]: *** [Makefile:427: rexxext.o] Error 1
Hi, Lucas and Alen.
While it is easy to fix this particular error (see attached patch,
from upstream repo), other similar error happens afterwards in my
tests. The problem is that this package is way behind upstream and I
think priority is to upgrade to a recent upstream version and then fix
whatever is left.
Not tagging 'patch' since this change alone does not fix build.
Regards,
--- regina-rexx.orig/rexxext.c
+++ regina-rexx/rexxext.c
@@ -55,6 +55,8 @@
# endif
#endif
+extern void getcallstack( tsd_t *TSD, streng *stem );
+
streng *rex_userid( tsd_t *TSD, cparamboxptr parms )
{
#if defined(WIN32)
Bug#1066887: Patch not sufficient
Unfortunately enhancing `locale-gen` doesn't work during an package update via apt: ... Setting up locales (2.36-9+deb12u4) ... Generating locales (this might take a while)... en_US.UTF-8... done en_DE.UTF-8@INTL...[error] cannot open locale definition file `en_US@INTL': No such file or directory done en_US.UTF-8@INTL... done Generation complete. ...
Bug#1066933: /usr/bin/plasma-emojier: Emoji selector `plasma-emojier` displays emojis in black and white.
Package: plasma-desktop Version: 4:5.27.10-1 Severity: normal File: /usr/bin/plasma-emojier X-Debbugs-Cc: foor...@gmail.com Dear Maintainer, Emojis show up in black and white in the KDE Plasma emoji selector `plasma-emojier`, but they display just fine in other programs. This is happening on 2 different computers on Debian testing (trixie). Folks at KDE suggest that this is a font config issue (https://bugs.kde.org/show_bug.cgi?id=483489). I have tried making a /etc/fonts/local.conf file as suggested in the above bug report, but that did not help. The issue appeared at some point between late Feb and mid March. Many thanks. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-desktop depends on: ii accountsservice 23.13.9-6 ii breeze 4:5.27.10-2 ii kactivitymanagerd5.27.10-1 ii kde-cli-tools4:5.27.10-1 ii kded55.107.0-1 ii kio 5.107.0-1+b1 ii kpackagetool55.107.0-1+b1 ii layer-shell-qt 5.27.10-1 ii libaccounts-qt5-11.16-2 ii libc62.37-15 ii libglib2.0-0 2.78.4-1 ii libibus-1.0-51.5.29-1 ii libkaccounts24:22.12.3-1+b1 ii libkf5activities55.107.0-1+b1 ii libkf5activitiesstats1 5.107.0-1+b1 ii libkf5authcore5 5.107.0-1+b1 ii libkf5baloo5 5.107.0-1 ii libkf5bookmarks5 5.107.0-1+b1 ii libkf5codecs55.107.0-1+b1 ii libkf5completion55.107.0-1+b1 ii libkf5configcore55.107.0-1+b1 ii libkf5configgui5 5.107.0-1+b1 ii libkf5configwidgets5 5.107.0-2+b1 ii libkf5coreaddons55.107.0-1+b1 ii libkf5crash5 5.107.0-1+b1 ii libkf5dbusaddons55.107.0-1+b1 ii libkf5globalaccel-bin5.107.0-2+b1 ii libkf5globalaccel5 5.107.0-2+b1 ii libkf5guiaddons5 5.107.0-1+b1 ii libkf5i18n5 5.107.0-1+b1 ii libkf5iconthemes55.107.0-1+b1 ii libkf5itemviews5 5.107.0-1+b1 ii libkf5jobwidgets55.107.0-1+b1 ii libkf5kcmutils5 5.107.0-2+b1 ii libkf5kcmutilscore5 5.107.0-2+b1 ii libkf5kdelibs4support5 5.107.0-1+b1 ii libkf5kiocore5 5.107.0-1+b1 ii libkf5kiofilewidgets55.107.0-1+b1 ii libkf5kiogui55.107.0-1+b1 ii libkf5kiowidgets55.107.0-1+b1 ii libkf5newstuffcore5 5.107.0-2+b1 ii libkf5notifications5 5.107.0-1+b1 ii libkf5notifyconfig5 5.107.0-1+b1 ii libkf5package5 5.107.0-1+b1 ii libkf5plasma55.107.0-1+b1 ii libkf5plasmaquick5 5.107.0-1+b1 ii libkf5quickaddons5 5.107.0-1+b1 ii libkf5runner55.107.0-1+b1 ii libkf5service-bin5.107.0-1+b1 ii libkf5service5 5.107.0-1+b1 ii libkf5solid5 5.107.0-1+b1 ii libkf5sonnetcore55.107.0-1+b1 ii libkf5sonnetui5 5.107.0-1+b1 ii libkf5widgetsaddons5 5.107.0-1+b1 ii libkf5windowsystem5 5.107.0-1+b1 ii libkf5xmlgui55.107.0-1+b1 ii libkworkspace5-5 4:5.27.10-3 ii libnotificationmanager1 4:5.27.10-3 ii libpackagekitqt5-1 1.1.1-1+b1 ii libphonon4qt5-4 4:4.12.0-3+b1 ii libprocesscore9 4:5.27.10-1 ii libqt5concurrent55.15.10+dfsg-7 ii libqt5core5a 5.15.10+dfsg-7 ii libqt5dbus5 5.15.10+dfsg-7 ii libqt5gui5 5.15.10+dfsg-7 ii libqt5network5 5.15.10+dfsg-7 ii libqt5qml5
Bug#1066910: chromium: downloads non-free component libchromescreenai.so without asking
Control: tags -1 bookworm trixie sid On 3/15/24 06:57, Helmut Grohne wrote: Package: chromium Version: 122.0.6261.128-1 Severity: serious In recent versions, chromium started downloading a file ~/.config/chromium/screen_ai/*/libchromescreenai.so. Evidently, the source of this shared object is not in the chromium source package. I think the chromium package - being in main - should not download a shared object and run it without user confirmation. Helmut Thanks for reporting this! It looks like this is controlled with the enable_screen_ai_service, I'll test that & fix it in the next series of upload. OpenPGP_0x645D0247C36E7637.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1066932: gcc-14: Please enable m2 on hurd-any
Source: gcc-14 Version: 14-20240303-1 Severity: normal Tags: patch User: debian-h...@lists.debian.org Usertags: hurd Hello, Now that upstream has fixed the m2 portability (available in the 20240303 snapshot), could you enable m2 on hurd-any, as the attached patch does? Thanks, Samuel -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.7.0 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Samuel --- Pour une évaluation indépendante, transparente et rigoureuse ! Je soutiens la Commission d'Évaluation de l'Inria. diff --git a/debian/rules.defs b/debian/rules.defs index 928d4e56..44f3f3a0 100644 --- a/debian/rules.defs +++ b/debian/rules.defs @@ -1195,7 +1195,7 @@ ifneq ($(with_base_only),yes) endif endif m2_no_cpus = loong64 powerpc ppc64 sh4 -m2_no_systems = gnu +m2_no_systems = ifneq (,$(filter $(DEB_TARGET_ARCH_CPU),$(m2_no_cpus))) with_m2 := disabled for cpu $(DEB_TARGET_ARCH_CPU) endif
Bug#1066543: ucx: FTBFS: cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]
On Wed, Mar 13, 2024 at 12:57:48PM +0100, Lucas Nussbaum wrote: > > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= > > -I/<>/src -I/<> -I/<>/src > > -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables > > -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label > > -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar > > -Wno-deprecated-declarations -Winvalid-pch -fopenmp -g -O2 > > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > > -fstack-protector-strong -fstack-clash-protection -Wformat > > -Werror=format-security -fcf-protection -nostdlib -std=c++11 -c > > ucp_tests.cc -fPIC -DPIC -o .libs/libucxperf_la-ucp_tests.o > > cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > > is not valid for C++ [-Werror] > > cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ > > is not valid for C++ [-Werror] Two notes here after a local sbuild build. First, these are warnings, not errors. Not sure what's the difference, it also has -Werror passed and gcc is also 13.2.0-18, but I don't see the "all warnings being treated as errors" text. The command: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. -DCPU_FLAGS= -I/<>/src -I/<> -I/<>/src -I/usr/include/hsa -I/usr/include/hip -O3 -g -Wall -Werror -funwind-tables -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar -Wno-deprecated-declarations -Winvalid-pch -fopenmp -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -nostdlib -std=c++11 -c ucp_tests.cc -fPIC -DPIC -o .libs/libucxperf_la-ucp_tests.o Second, the build also failed, and also in the same directory, but for a totally different cause: libtool: link: gcc -O3 -g -Wall -Werror -funwind-tables -Wno-missing-field-initializers -Wno-unused-parameter -Wno-unused-label -Wno-long-long -Wno-endif-labels -Wno-sign-compare -Wno-multichar -Wno-deprecated-declarations -Winvalid-pch -Wno-pointer-sign -Werror-implicit-function-declaration -Wno-format-zero-length -Wnested-externs -Wshadow -Werror=declaration-after-statement -fopenmp -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-dynamic-list-data -Wl,-z -Wl,relro -o .libs/ucx_perftest ucx_perftest-perftest.o ucx_perftest-perftest_run.o ucx_perftest-perftest_params.o ucx_perftest-perftest_mad.o -libmad -libumad lib/.libs/libucxperf.a /<>/src/ucp/.libs/libucp.so /<>/src/uct/.libs/libuct.so /<>/src/ucs/.libs/libucs.so -lm /<>/src/ucm/.libs/libucm.so -ldl -lrt -fopenmp /usr/bin/ld: lib/.libs/libucxperf.a(libucxperf_la-uct_tests.o):(.data.rel.local.DW.ref.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x0): undefined reference to `__gxx_personality_v0' -- WBR, wRAR signature.asc Description: PGP signature
Bug#1065787: 64-bit time_t transition: cargo needs manual intervention
On 2024-03-14 22:03 -0700, Otto Kekäläinen wrote: > Hi! > > Is anyone perhaps planning to fix cargo? Yes. We have been working on it this week (e.g. ema built cargo for armhf), but that is not sufficient to unbung the curl->stunnel4->python->crypography->cargo loop. I tried building the patched stunnel4 last night but got stuck on other missing dependencies, and just about everything being uninstallable (and then my wife made me do something else for the rest of the evening). > For example curl isn't building on armel/armhf now and numerous packages > that depend of curl are not building on armel/armhf. We are well aware that this is broken and blocking lots of things. Co-ordinate efforts on the #debian-arm channel. There are plenty of other loops to unbung too. Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#1066931: replace debian/1.39 with 1.39 tag
Package: python3-dput Version: 1.39 Severity: minor Tags: upstream X-Debbugs-Cc: Andreas Tille Hi Andreas, Thanks for taking care about recent release. But I got confused when I didn't see 1.39 tag, and only later detected that you tagged it as debian/1.39 . Unless there is team decision on changing tagging scheme, should we replace debian/1.39 with a more regular for this repo 1.39 tag? ❯ git tag | grep -e '1\.3' 1.3 1.30 1.31 1.32 1.33 1.34 1.35 1.35+deb12u1 1.36 1.37 1.38 debian/1.39 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable-updates'), (100, 'stable-security'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-dput depends on: ii gnupg 2.2.40-1.1 ii python3 3.11.6-1 ii python3-debian 0.1.49 ii python3-xdg 0.28-2 Versions of packages python3-dput recommends: ii debian-keyring 2023.12.24 ii lintian 2.117.0 ii openssh-client 1:9.6p1-4 ii python3-distro-info 1.7 ii python3-jsonschema 4.10.3-2 ii python3-paramiko 2.12.0-2 python3-dput suggests no packages. -- debconf-show failed
Bug#626251: apt-get source gets confused by multiple versions in a list
Hi all, I'm looking at bug reports to try and clean some up and I noticed this one. I think we can close it, see my reasoning below your message and if you don't agree feel free to reopen the bug. On Tue, May 10, 2011 at 08:14:24AM +, Simon Cozens wrote: > After upgrading from lenny to squeeze, trying to build packages from unstable, > apt-get source sometimes works: > > simon@dealer ~ % apt-get source apt > ... > Get:1 http://ftp.de.debian.org/debian/ unstable/main apt 0.8.14.1 (dsc) > [1,363 B] > ... > > (That is, correctly, fetching the unstable version.) And sometimes fails > spectacularly: > > simon@dealer ~ % apt-get source duplicity > ... > E: Ignore unavailable version '0.6.08b-1' of package 'duplicity' > E: Unable to find a source package for duplicity > > Wait, 0.6.08b-1 is the *stable* version. I don't want the stable version, > that's the whole point. Oh, maybe I need to say "-t unstable": > > simon@dealer ~ % apt-get -t unstable source duplicity > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Ignore unavailable target release 'unstable' of package 'duplicity' > E: Unable to find a source package for > > But clearly there is an entry for duplicity in the sources list: > > simon@dealer ~ % grep duplicity_ /var/lib/apt/lists/*Sources > a35f37d3a519b51be903c3f71588f487 1032 duplicity_0.6.12-1.dsc > 9b84c984054550bbb2ba29b553567b7b 296045 duplicity_0.6.12.orig.tar.gz > 17ecd266d7b7307512ab969c8fbd2669 13272 duplicity_0.6.12-1.diff.gz > ... > > In fact, there are *two different versions*: > > ... > b73a68286bc79140aab950ed13747a49 1033 duplicity_0.6.13-1.dsc > b3d627f35fc527b00121925840d5cca7 296955 duplicity_0.6.13.orig.tar.gz > ee420e83778e7a8dda731ed848cf84ab 13635 duplicity_0.6.13-1.diff.gz > > Obviously that's not an ideal scenario but apt-get source should *not* > throw its hands up and say "obviously you wanted the stable version which > I can't find". We have multiple source files for dovecot: $ grep dovecot_ /var/lib/apt/lists/*Sources | grep dsc /var/lib/apt/lists/deb.debian.org_debian_dists_stable_main_source_Sources: c305facad2b3785986e470397df410f3 4166 dovecot_2.3.19.1+dfsg1-2.1.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_stable_main_source_Sources: 6e55d7ce048a613f00562e32a51e19d6503c9da9ae5d34d5692cca636c518d2b 4166 dovecot_2.3.19.1+dfsg1-2.1.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources: 3d1fa5b58612668cb578df2e04f36002 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources: 33a22aa897249f9600e7fdf95a4e96c11611ba3385cb8a5f8c87561d33c67f06 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 3d1fa5b58612668cb578df2e04f36002 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 33a22aa897249f9600e7fdf95a4e96c11611ba3385cb8a5f8c87561d33c67f06 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: ca294cabc50b51d197c2b33777073078 4090 dovecot_2.3.21+dfsg1-3.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 13dd3e6c39b752f0925ec880ff4c1d807b6346a22bea1c4677dd6fd978f6ae74 4090 dovecot_2.3.21+dfsg1-3.dsc $ grep dovecot_ /var/lib/apt/lists/*Sources | grep unstable | grep dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 3d1fa5b58612668cb578df2e04f36002 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 33a22aa897249f9600e7fdf95a4e96c11611ba3385cb8a5f8c87561d33c67f06 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: ca294cabc50b51d197c2b33777073078 4090 dovecot_2.3.21+dfsg1-3.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 13dd3e6c39b752f0925ec880ff4c1d807b6346a22bea1c4677dd6fd978f6ae74 4090 dovecot_2.3.21+dfsg1-3.dsc We try to get the source package: $ apt-get source dovecot Reading package lists... Done NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 9598 kB of source archives. Get:1 https://deb.debian.org/debian unstable/main dovecot 1:2.3.21+dfsg1-3 (dsc) [4090 B] $ apt-get source dovecot/unstable Reading package lists... Done Selected version '1:2.3.21+dfsg1-3' (unstable) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest
Bug#1064028: libpython3.12-dev: non-C90 headerfile code breaks -Werror=declaration-after-statement
Followup-For: Bug #1064028 X-Debbugs-Cc: d...@debian.org Control: forwarded -1 https://github.com/python/cpython/issues/116869 It seemed worth forwarding this bugreport upstream, since it may be a quick fix there (initially I felt that it may be worth handling in Debian initially and then forwarding; perhaps not, though). Alternatively we may learn that C90 is no-longer a code style baseline for cpython, and in that case we can adjust accordingly.
Bug#1066930: nmu: vlc-plugin-pipewire_3-3
Package: release.debian.org Severity: normal X-Debbugs-Cc: vlc-plugin-pipew...@packages.debian.org Control: affects -1 + src:vlc-plugin-pipewire User: release.debian@packages.debian.org Usertags: binnmu nmu vlc-plugin-pipewire_3-3 . ANY . unstable . -m "Rebuild for time_t"
Bug#1065667: RFS ping mini-httpd/1.30-9 -- Small HTTP server
Gently pinging about the RFS - mini-httpd/1.30-9 Mentors page: https://mentors.debian.net/package/mini-httpd/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mini-httpd/mini-httpd_1.30-9.dsc Thanks a lot ! signature.asc Description: This is a digitally signed message part
Bug#1066829: ITP: assetfinder -- Find domains and subdomains related to a given domain
Hi, On 2024-03-14 01:47, aquilamac...@riseup.net wrote: * Package name: assetfinder Version : 0.1.1 Upstream Contact: Tom Hudson * URL : https://github.com/tomnomnom/assetfinder * License : MIT Programming Lang: Golang Description : Find domains and subdomains related to a given domain assetfinder is a command-line tool to find domains and subdomains potentially related to a specified domain. Enhances domain discovery for comprehensive analysis. I'm writing to submit an Intention to Package (ITP) for assetfinder under the pkg-security team's umbrella. Is this tool still maintained? The last changes have been 5 years ago and it references quite a few sources that no longer exist. I'd also expect that such a tool needs maintenance to keep up with API changes. And lastly the name is a tad too generic, given that it's solely focussed on DNS "assets", and not any other assets you might want to track. Kind regards Philipp Kern
Bug#607999: 'apt-get source $src' fails
Hi all, On Wed, Feb 28, 2024 at 11:01:53AM +0800, Tianyu Chen wrote: > In apt-get(8): > The arguments are interpreted as binary and source package names. See the > --only-source option if you want to change that. > I think this bug should be closed now? > Best regards, > Tianyu Chen @ deepin I think this bug can be closed indeed. In apt 2.6.1 (bookworm) 2.7.13+b1 (sid) this seems to be fixed. On bookworm: $ apt-get source --only-source dovecot -t oldstable Reading package lists... Done Selected version '1:2.3.13+dfsg1-2+deb11u1' (oldstable) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: $ apt-get source --only-source dovecot Reading package lists... Done NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 9499 kB of source archives. Get:1 https://deb.debian.org/debian bookworm/main dovecot 1:2.3.19.1+dfsg1-2.1 (dsc) [4166 B] $ apt-get source dovecot Reading package lists... Done NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Skipping already downloaded file 'dovecot_2.3.19.1+dfsg1-2.1.dsc' Need to get 9495 kB of source archives. Get:1 https://deb.debian.org/debian bookworm/main dovecot 1:2.3.19.1+dfsg1-2.1 (tar) [1637 kB] On sid: $ apt-get source dovecot -t testing Reading package lists... Done Selected version '1:2.3.21+dfsg1-2' (testing) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git apt-get source dovecot-core Reading package lists... Done Picking 'dovecot' as source package instead of 'dovecot-core' NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Skipping already downloaded file 'dovecot_2.3.21+dfsg1.orig-pigeonhole.tar.gz' Need to get 7910 kB of source archives. Get:1 https://deb.debian.org/debian unstable/main dovecot 1:2.3.21+dfsg1-3 (dsc) [4090 B] $ apt-get source --only-source dovecot -t stable Reading package lists... Done Selected version '1:2.3.19.1+dfsg1-2.1' (stable) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git $ apt-get source dovecot-core -t stable Reading package lists... Done Picking 'dovecot' as source package instead of 'dovecot-core' Selected version '1:2.3.19.1+dfsg1-2.1' (stable) for dovecot I think this all works as intended. If you feel this is incorrect, feel free to reopen the bug. Cheers, Wesley
Bug#1017720: nfs-common: No such file or directory
I've been looking for an explanation for a similar kind of failure. I
wonder if the core problem is the same as reported here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1209457
Supposedly fixed by the patch posted to linux-nfs here (also attached
after extraction from the SuSE kernel build source RPM):
https://www.spinics.net/lists/linux-nfs/msg86343.html
And merged into the main-line kernel in 5.15.3, see the Changelog here
(specifically under commit "69e0be0efe53fb012f5db32bc328590745cf8f71"):
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.3
I would be interested to hear whether it makes any difference for the
issue reported in this Debian bug.
--KenFrom 255fc6efacf25d954a986ff058fd9899f322e7d1 Mon Sep 17 00:00:00 2001
From: Trond Myklebust
Date: Tue, 28 Sep 2021 11:15:53 -0400
Subject: [PATCH] NFS: Don't set NFS_INO_DATA_INVAL_DEFER and NFS_INO_INVALID_DATA
Git-commit: 488796ec1e39fb9194cc8175f770823d40fbf0ed
Patch-mainline: v5.16-rc1
References: stable-5.14.19
[ Upstream commit 488796ec1e39fb9194cc8175f770823d40fbf0ed ]
NFS_INO_DATA_INVAL_DEFER and NFS_INO_INVALID_DATA should be considered
mutually exclusive.
Fixes: 1c341b777501 ("NFS: Add deferred cache invalidation for close-to-open consistency violations")
Signed-off-by: Trond Myklebust
Tested-by: Benjamin Coddington
Reviewed-by: Benjamin Coddington
Signed-off-by: Sasha Levin
Acked-by: Takashi Iwai
---
fs/nfs/inode.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index 6ea1bde33cb6..f9d3ad3acf11 100644
--- a/fs/nfs/inode.c
+++ b/fs/nfs/inode.c
@@ -210,10 +210,15 @@ void nfs_set_cache_invalid(struct inode *inode, unsigned long flags)
flags &= ~NFS_INO_INVALID_XATTR;
if (flags & NFS_INO_INVALID_DATA)
nfs_fscache_invalidate(inode);
- if (inode->i_mapping->nrpages == 0)
- flags &= ~(NFS_INO_INVALID_DATA|NFS_INO_DATA_INVAL_DEFER);
flags &= ~(NFS_INO_REVAL_PAGECACHE | NFS_INO_REVAL_FORCED);
+
nfsi->cache_validity |= flags;
+
+ if (inode->i_mapping->nrpages == 0)
+ nfsi->cache_validity &= ~(NFS_INO_INVALID_DATA |
+ NFS_INO_DATA_INVAL_DEFER);
+ else if (nfsi->cache_validity & NFS_INO_INVALID_DATA)
+ nfsi->cache_validity &= ~NFS_INO_DATA_INVAL_DEFER;
}
EXPORT_SYMBOL_GPL(nfs_set_cache_invalid);
--
2.26.2
Bug#1066887: ENhance Patch for local-gen
Adding / back to end of the path, so that a locale file is immediately
found.
diff --git a/debian/local/usr_sbin/locale-gen b/debian/local/usr_sbin/locale-gen
index 7fa3d772..1711a4f0 100755
--- a/debian/local/usr_sbin/locale-gen
+++ b/debian/local/usr_sbin/locale-gen
@@ -23,6 +23,12 @@ is_entry_ok() {
fi
}
+if [ -z "${I18NPATH:-}" ]; then
+ if [ -d "${USER_LOCALES}" ]; then
+I18NPATH="${USER_LOCALES%%/locales*}/"
+ fi
+fi
+
echo "Generating locales (this might take a while)..."
while read -r locale charset; do
if [ -z "$locale" ] || [ "${locale#\#}" != "$locale" ]; then continue;
fi
@@ -46,7 +52,7 @@ while read -r locale charset; do
input="$USER_LOCALES/$input"
fi
fi
- localedef -i "$input" -c -f "$charset" -A
/usr/share/locale/locale.alias "$locale" || :
+ I18NPATH="${I18NPATH}" localedef -i "$input" -c -f "$charset" -A
/usr/share/locale/locale.alias "$locale" || :
echo " done"
done < "$LOCALEGEN"
echo "Generation complete."
Bug#1064028: libpython3.12-dev: non-C90 headerfile code breaks -Werror=declaration-after-statement
Package: libpython3.12-dev Followup-For: Bug #1064028 X-Debbugs-Cc: d...@debian.org Control: reopen -1 Control: found -1 3.12.1-2 Hello, On Sun, 3 Mar 2024 10:35:42 +0100, Matthias wrote: > That was fixed in the upstream 3.12.2 release. The problem does not appear to be resolved; building onboard/1.4.1-5 using the headerfiles from libpython3.12-dev/3.12.2-1 continues to fail. x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/root/onboard-1.4.1=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DMAJOR_VERSION=0 -DMINOR_VERSION=4 -DMICRO_VERSION=0 -I/usr/include/blkid -I/usr/include/cairo -I/usr/include/cloudproviders -I/usr/include/dconf -I/usr/include/freetype2 -I/usr/include/fribidi -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/glib-2.0 -I/usr/include/gtk-3.0 -I/usr/include/harfbuzz -I/usr/include/hunspell -I/usr/include/libmount -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/webp -I/usr/include/x86_64-linux-gnu -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.12 -c Onboard/osk/osk_audio.c -o build/temp.linux-x86_64-cpython-312/Onboard/osk/osk_audio.o -Wsign-compare -Wdeclaration-after-statement -Werror=declaration-after-statement In file included from /usr/include/python3.12/Python.h:44, from Onboard/osk/osk_module.h:25, from Onboard/osk/osk_audio.c:21: /usr/include/python3.12/object.h: In function ‘Py_SIZE’: /usr/include/python3.12/object.h:233:5: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement] 233 | PyVarObject *var_ob = _PyVarObject_CAST(ob); | ^~~ Thanks, James
Bug#1066887: Patch for locale-gen
diff --git a/debian/local/usr_sbin/locale-gen b/debian/local/usr_sbin/locale-gen
index 7fa3d772..1711a4f0 100755
--- a/debian/local/usr_sbin/locale-gen
+++ b/debian/local/usr_sbin/locale-gen
@@ -23,6 +23,12 @@ is_entry_ok() {
fi
}
+if [ -z "${I18NPATH:-}" ]; then
+ if [ -d "${USER_LOCALES}" ]; then
+I18NPATH="${USER_LOCALES%/locales}"
+ fi
+fi
+
echo "Generating locales (this might take a while)..."
while read -r locale charset; do
if [ -z "$locale" ] || [ "${locale#\#}" != "$locale" ]; then continue;
fi
@@ -46,7 +52,7 @@ while read -r locale charset; do
input="$USER_LOCALES/$input"
fi
fi
- localedef -i "$input" -c -f "$charset" -A
/usr/share/locale/locale.alias "$locale" || :
+ I18NPATH="${I18NPATH}" localedef -i "$input" -c -f "$charset" -A
/usr/share/locale/locale.alias "$locale" || :
echo " done"
done < "$LOCALEGEN"
echo "Generation complete."
Bug#1066929: Package outdated, crippled, unfit for release
Source: bcachefs-tools Version: 24+really1.3.4-2 Severity: serious I don't think bcachefs-tools in its current state is fit for release. * The package is severely behind: Debian is currently at 1.3.4. Upstream is at 1.6.4. * Chronologically speaking, 1.3.4 was released in November 2023, so in theory, it's not that old. In practice, however, bcachefs is a fast-moving project, and in particular the past few months have been critical both in terms of pace, and in terms of stabilization: bcachefs was merged in the upstream Linux kernel, starting with v6.7, released in January 2024. Linux 6.8 was released this week as well, with even more fixes, including the ability to use the in-kernel fsck. * Linux v6.7 entered unstable this week, which opens up the user base for this package quite a bit. Especially with the recent hype, others may be inclined to try it, and be surprised by back-and-forth metadata migrations between kernel and userspace, as a concrete example of a problem. * Moreover, even the outdated version that we have in Debian is crippled, because large parts of its functionality are missing: all the Rust functionality included in this software, which is ever increasing (up to being required, in newer upstream releases). This has been reported previously as #1060256. * I'd also argue that the package lacks attentive maintainership, and would recommend to orphan and/or find one or more comaintainers: - There are various packaging issues: wrong version number, branches not pushed into git etc. etc. (most reported as #1054620) - There hasn't been any coordination/two-way street with upstream; I contributed a bunch of PRs to help with the Rust integration bits in Debian, and I know Steinar was in touch with them as well, but none of this was done by the package maintainer or in coordination with them. - No serious effort was made to package the Rust bits before. I worked on it and made it happen with only a few hours of work, as documented in that bug report above. - There hasn't been any coordinated system integration effort with other Debian packages like grub/initramfs-tools/etc. #1061525 describes issues that are across projects and up for us, the distributor, to really triage and coordinate fixes for. - Finally, while a bunch of work happened by others, like myself paving the road for the Rust bits to be enabled, and by Steinar to prepare fixed packages (and even an NMU), there hasn't been an appropriate level of response to our contributions IMHO, that would have included in an upload that includes all of these fixes. We are basically blocked. Now, I realize that the maintainer may be quite busy with other tasks, including what I can only image is a busy Debian workload due to some other, erm, duties (for which I'm thankful!). In an effort to be more collegial, I've even reached out in private, twice. But, I think we are at the point where weeks pass while the state of this package is simply not OK, a disservice to our users, and unfit for release, hence this RC bug. This is a filesystem we're talking about, so outdated/buggy software can even mean broader system-wide issues including data corruption. In terms of a path forward: I would recommend to upload the package as prepared by Steinar ASAP, and/or submit an RFH/O for the long-term maintainership of the package. Best, Faidon
Bug#1066095: llvm-18 is available in unstable, please also build spirv-llvm-translator-18 in unstable
On 15/03/2024 15.19, Matthias Klose wrote: spirv-headers are now updated in unstable. Please could you check if you're able to build with the LLVM-18 in unstable? asking because I already updated the b-d in LLVM-18 to spirv-llvm-18, which I need to revert, if you cannot build it. A quick build of the spirv-llvm-translator 18.1.0 release in sid (using llvm packages versioned 1:18.1.1-1) mostly succeeded, seems like I only need to update the symbols file ... I'm currently preparing an update for -16, thereafter for -17. Once these are done, I'll update to the -18 release and upload to sid. Andreas
Bug#1065327: ITA: python-levenshtein
On Fri, Mar 15, 2024 at 10:03:44AM -0400, Louis-Philippe Véronneau wrote: > Ah, great news then, happy to let you have it :) > > I'll be happy to contribute punctually if needed if you do indeed keep it in > the DPT. Thanks! Quick update, having taken a peek at the package: the version currently in unstable is quite old - it is a version that did not require rapidfuzz. So I will leave it as-is until rapidfuzz makes it into testing (which may be some time), and then it can be updated. Best wishes, Julian > On 2024-03-15 07:01, Julian Gilbey wrote: > > On Thu, Mar 14, 2024 at 10:40:38AM -0400, Louis-Philippe Véronneau wrote: > > > retitle 1065327 ITA: python-levenshtein -- extension for computing string > > > similarities and edit distances (Python 3) > > > owner 1065327 Louis-Philippe Véronneau > > > thanks > > > > > > I need this package for sublime-music and since it's being orphaned, I'm > > > planning to adopt it. > > > > > > If someone else wants to maintain this package though, I won't fight you > > > for it :) > > > > > > Cheers (and thanks to morph for the work so far), > > > > Hi Louis-Philippe, > > > > Both Jelmer and I are also willing to take it on. I wrote to the > > Python list in response to Jelmer (before I saw your ITA): > > > >I've just taken a look at python-levenshtein, as I remember the name > >now: it might make more sense for me to take it as it depends on > >rapidfuzz and rapidfuzz-cpp, which I've just packaged and are sitting > >in NEW. But if you want to take it, please feel free to do so! (Once > >rapidfuzz makes it into unstable, a lot of debian/rules could probably > >also be simplified.) > > > > So happy whoever wants to take it; we just won't be able to do much > > until rapidfuzz, rapidfuzz-cpp and taskflow make it to unstable. > > > > I do suggest that we keep it within the DPT, though. > > > > Best wishes, > > > > Julian
Bug#1066922: ITP: python-mercantile -- Web mercator XYZ tile utilities
Note that this packages was in the archive in the past: https://tracker.debian.org/pkg/mercantile Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1066095: llvm-18 is available in unstable, please also build spirv-llvm-translator-18 in unstable
spirv-headers are now updated in unstable. Please could you check if you're able to build with the LLVM-18 in unstable? asking because I already updated the b-d in LLVM-18 to spirv-llvm-18, which I need to revert, if you cannot build it.
Bug#1066928: bookworm-pu: package ovn/23.03.1-1~deb12u2
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu Dear Release Team, We would like to upload an update to the bookwork ovn package. The package contains a patch to CVE-2024-2182. Debdiff attached. The appropriate salsa git branches have also been updated. -- Frode Nordahl ovn_23.03.1-1~deb12u2.debdiff Description: Binary data
Bug#1066927: ITP: python-momepy -- Urban Morphology Measuring Toolkit
Package: wnpp Severity: wishlist Owner: Thomas Goirand X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: python-momepy Version : 0.7.0 Upstream Contact: Martin Fleischmann * URL : https://github.com/pysal/momepy * License : BSD-3-clause Programming Lang: Python Description : Urban Morphology Measuring Toolkit Momepy is a library for quantitative analysis of urban form - urban morphometrics. It is part of PySAL (Python Spatial Analysis Library) and is built on top of GeoPandas, other PySAL modules, and networkX. Note: this is a new dependency of networkx, so we can continue to build its documentation.
Bug#1065787: 64-bit time_t transition: cargo needs manual intervention
On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote: > Hi! > > Is anyone perhaps planning to fix cargo? > > For example curl isn't building on armel/armhf now and numerous packages > that depend of curl are not building on armel/armhf. > > Thanks in advance to the person who steps up. see the (linked) t64 transition bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884#197
Bug#1066926: icingaweb2-module-x509_1: [INTL:de] updated German po file translation
Package: icingaweb2-module-x509_1 Version: 1.2.1+dfsg-3 Severity: wishlist Tags: patch l10n Please find the updated German po file translation for icingaweb2-module-x509_1 attached. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Yours Hermann-Josef Beckers icingaweb2-module-x509_1_1.2.1+dfsg-3_templates.pot.bz2 Description: application/bzip
Bug#1066925: ITP: python-contextily -- Context geo-tiles in Python
Package: wnpp Severity: wishlist Owner: Thomas Goirand X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: python-contextily Version : 1.5.2 Upstream Contact: Dani Arribas-Bel * URL : https://github.com/geopandas/contextily * License : BSD-3-clause Programming Lang: Python Description : Context geo-tiles in Python Contextily is a package to retrieve tile maps from the internet. It can add those tiles as basemap to matplotlib figures or write tile maps to disk into geospatial raster files. Bounding boxes can be passed in both WGS84 (EPSG:4326) and Spheric Mercator (EPSG:3857). Note: this is a new build-depends for networkx, so we can continue to build its documentation.
Bug#1065327: ITA: python-levenshtein
Ah, great news then, happy to let you have it :) I'll be happy to contribute punctually if needed if you do indeed keep it in the DPT. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ On 2024-03-15 07:01, Julian Gilbey wrote: On Thu, Mar 14, 2024 at 10:40:38AM -0400, Louis-Philippe Véronneau wrote: retitle 1065327 ITA: python-levenshtein -- extension for computing string similarities and edit distances (Python 3) owner 1065327 Louis-Philippe Véronneau thanks I need this package for sublime-music and since it's being orphaned, I'm planning to adopt it. If someone else wants to maintain this package though, I won't fight you for it :) Cheers (and thanks to morph for the work so far), Hi Louis-Philippe, Both Jelmer and I are also willing to take it on. I wrote to the Python list in response to Jelmer (before I saw your ITA): I've just taken a look at python-levenshtein, as I remember the name now: it might make more sense for me to take it as it depends on rapidfuzz and rapidfuzz-cpp, which I've just packaged and are sitting in NEW. But if you want to take it, please feel free to do so! (Once rapidfuzz makes it into unstable, a lot of debian/rules could probably also be simplified.) So happy whoever wants to take it; we just won't be able to do much until rapidfuzz, rapidfuzz-cpp and taskflow make it to unstable. I do suggest that we keep it within the DPT, though. Best wishes, Julian
Bug#1066924: icingaweb2-module-toplevelview: [INTL:de] updated German po file translation
Package: icingaweb2-module-toplevelview Version: 0.3.3-3 Severity: wishlist Tags: patch l10n Please find the updated German po file translation for icingaweb2-module-toplevelview attached. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Yours Hermann-Josef Beckers icingaweb2-module-toplevelview_0.3.3-3_templates.pot.bz2 Description: application/bzip
Bug#1062896: shishi: NMU diff for 64-bit time_t transition
reopen 1062896
thanks
Benjamin Drung writes:
> Source: shishi
> Dear maintainer,
>
> Please find attached a final version of this patch for the time_t
> transition. This patch is being uploaded to unstable.
>
> Note that this adds a versioned build-dependency on dpkg-dev, to guard
> against accidental backports with a wrong ABI.
Thanks for working on this.
I noticed that autopkgtest for 1.0.3-2.1 fails on i386:
https://ci.debian.net/packages/s/shishi/testing/i386/43439759/
It is time related:
100s PASS: gcc tests/gztime.c
100s Segmentation fault
Debugging this (with help from #debian-devel) led me down several chains
of discoveries. I believe that this package has enabled and assumes
64-bit time_t on all 32-bit platforms for a long time, including i386.
Look at how the old version before your changes behave:
jas@kaka:~$ podman run --arch=386 -it --rm debian:testing
root@78d65bc11b9f:/# cat /etc/apt/sources.list.d/debian.sources | sed 's,:
deb,: deb-src,' > /etc/apt/sources.list.d/src.sources
root@78d65bc11b9f:/# apt update
root@78d65bc11b9f:~# apt install libshishi-dev build-essential
Get:76 http://deb.debian.org/debian testing/main i386 libshishi-dev i386
1.0.3-2 [217 kB]
root@78d65bc11b9f:~# apt source shishi
root@78d65bc11b9f:~# cd shishi-1.0.3/
root@78d65bc11b9f:~/shishi-1.0.3# touch config.h
root@78d65bc11b9f:~/shishi-1.0.3# WORKDIR=.
root@78d65bc11b9f:~/shishi-1.0.3# gcc -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
-I$WORKDIR -Ilib/gl -D_GL_ATTRIBUTE_CONST= -DPACKAGE='"shishi"' -o $WORKDIR/foo
tests/gztime.c `pkg-config --cflags --libs shishi`
root@78d65bc11b9f:~/shishi-1.0.3# ./foo
root@78d65bc11b9f:~/shishi-1.0.3# gcc -I$WORKDIR -Ilib/gl
-D_GL_ATTRIBUTE_CONST= -DPACKAGE='"shishi"' -o $WORKDIR/foo tests/gztime.c
`pkg-config --cflags --libs shishi`
root@78d65bc11b9f:~/shishi-1.0.3# ./foo
Segmentation fault (core dumped)
root@78d65bc11b9f:~/shishi-1.0.3#
This suggests passing 32-bit time_t to this library break before your
change, and it breaks after your changes too. See earlier debci failure
for 1.0.3-2 without your t64 changes here that confirms this hypothesis:
https://ci.debian.net/packages/s/shishi/testing/i386/43917754/
So the library is 64-bit only even on 32-bit architectures, or at least
i386, I briefly compared build logs on armhf too.
You can re-run the snippet above on unstable instead, and you will see
it behaves the same for 1.0.3-2.1. So the t64 patches did not modify
any ABI at all.
As far as I understand, this means this package does not need any
t64-migration at all, and your NMU should be reverted. Do you agree?
Arguable the package header .h file should not use the time_t type since
the shared library ABI will only work if the application uses 64-bit
time_t, but on i386 the normal approach is to have 32-bit time_t. This
would be an upstream wishlist, it was suggested to replace time_t with
int64_t so that callers that pass 32-bit time_t would get automatically
extended, which is one solution.
/Simon
> Thanks!
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: unable to detect
>
> diff -Nru shishi-1.0.3/debian/changelog shishi-1.0.3/debian/changelog
> --- shishi-1.0.3/debian/changelog 2024-01-30 16:09:13.0 +
> +++ shishi-1.0.3/debian/changelog 2024-02-29 15:52:14.0 +
> @@ -1,3 +1,10 @@
> +shishi (1.0.3-2.1) unstable; urgency=medium
> +
> + * Non-maintainer upload.
> + * Rename libraries for 64-bit time_t transition. Closes: #1062896
> +
> + -- Benjamin Drung Thu, 29 Feb 2024 15:52:14 +
> +
> shishi (1.0.3-2) unstable; urgency=medium
>
>[ Simon Josefsson ]
> diff -Nru shishi-1.0.3/debian/control shishi-1.0.3/debian/control
> --- shishi-1.0.3/debian/control 2024-01-30 15:57:25.0 +
> +++ shishi-1.0.3/debian/control 2024-02-29 15:52:14.0 +
> @@ -5,7 +5,7 @@
> Uploaders:
> Simon Josefsson ,
> Russ Allbery ,
> -Build-Depends:
> +Build-Depends: dpkg-dev (>= 1.22.5),
> debhelper-compat (= 13),
> libgcrypt-dev,
> libgnutls28-dev,
> @@ -25,7 +25,10 @@
> Homepage: https://www.gnu.org/software/shishi/
> Rules-Requires-Root: no
>
> -Package: libshishi0
> +Package: libshishi0t64
> +Provides: ${t64:Provides}
> +Replaces: libshishi0
> +Breaks: libshishi0 (<< ${source:Version})
> Section: libs
> Architecture: any
> Multi-Arch: same
> @@ -63,7 +66,7 @@
> Architecture: any
> Multi-Arch: same
> Depends:
> - libshisa0 (= ${binary:Version}),
> + libshisa0t64 (= ${binary:Version}),
> libshishi-dev (= ${binary:Version}),
> ${misc:Depends},
> Description: Development files for the
Bug#1066923: icingaweb2-module-generictts: [INTL:de] updated German po file translation
Package: icingaweb2-module-generictts Version: 2.1.0-2 Severity: wishlist Tags: patch l10n Please find the updated German po file translation for icingaweb2-module-generictts attached. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Yours Hermann-Josef Beckers icingaweb2-module-generictts_2.1.0-2_templates.pot.bz2 Description: application/bzip
Bug#1066922: ITP: python-mercantile -- Web mercator XYZ tile utilities
Package: wnpp Severity: wishlist Owner: Thomas Goirand X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: python-mercantile Version : 1.2.1 Upstream Contact: Sean Gillies * URL : https://github.com/mapbox/mercantile * License : BSD-3-clause Programming Lang: Python Description : Web mercator XYZ tile utilities The mercantile module provides ul(xtile, ytile, zoom) and bounds(xtile, ytile, zoom) functions that respectively return the upper left corner and bounding longitudes and latitudes for XYZ tiles, a xy(lng, lat) function that returns spherical mercator x and y coordinates, a tile(lng, lat, zoom) function that returns the tile containing a given point, and quadkey conversion functions quadkey(xtile, ytile, zoom) and quadkey_to_tile(quadkey) for translating between quadkey and tile coordinates. Note: This is a new build-dependency for networkx so we can continue to build its documentation.
Bug#1066921: icingaweb2_module_eventdb: [INTL:de] updated German po file translation
Package: icingaweb2_module_eventdb Version: 1.3.0-4 Severity: wishlist Tags: patch l10n Please find the updated German po file translation for icingaweb2_module_eventdb attached. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Yours Hermann-Josef Beckers icingaweb2-module-eventdb_1.3.0-4_templates.pot.bz2 Description: application/bzip
Bug#1066920: icingaweb2-module-audit: [INTL:de] updated German po file translation
Package: icingaweb2-module-audit Version: 1.0.2-3 Severity: wishlist Tags: patch l10n Please find the updated German po file translation for icingaweb2-module-audit attached. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Yours Hermann-Josef Beckers icingaweb2-module-audit_1.0.2-3_templates.pot.bz2 Description: application/bzip
Bug#1066919: icingaweb2-module-fileshipper: [INTL:de] updated German po file translation
Package: icingaweb2-module-fileshipper Version: 1.2.0-3 Severity: wishlist Tags: patch l10n Please find the updated German po file translation for icingaweb2-module-fileshipper attached. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Yours Hermann-Josef Beckers icingaweb2-module-fileshipper_1.2.0-3_templates.pot.bz2 Description: application/bzip
Bug#1066891: Processed: gcc-13: ICE compiling OpenSSH: in change_address_1
Control: tags -1 + moreinfo On 15.03.24 01:39, Debian Bug Tracking System wrote: Processing control commands: affects -1 src:openssh Bug #1066891 [src:gcc-13] gcc-13: ICE compiling OpenSSH: in change_address_1 Added indication that 1066891 affects src:openssh please provide the /tmp/cc* files that GCC left. Just literally dumping a file into a bug report cries for garbage.
Bug#1059228: This is fixed in the next release 0.11.1
This is fixed in the next release 0.11.1. However, I fail to build a package (due to my unexperience I guess). When I try to build a package from https://salsa.debian.org/DebianOnMobile-team/s2geometry I get the error: CMake Error at CMakeLists.txt:204 (target_link_libraries): Target "s2" links to: absl::check but the target was not found. Possible reasons include: * There is a typo in the target name. * A find_package call is missing for an IMPORTED target. * An ALIAS target is missing. So something seems to be missing in the abseil library that it depends on. I am a bit at a loss about how to fix this. With a working package I could upload a new version...
Bug#1066918: nmu: packages that build-depend on the libsimde-dev header-only library
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: cru...@debian.org
Hello!
There is a new release of the libsimde-dev header only library which
include fixes for many architectures and numerous optimizations. More
information is available at https://wiki.debian.org/SIMDEverywhere
Please rebuild all packages that build-dep on libsimde-dev so they may
gain the benefits of the new release.
Of course, given all of the excitement in the archive with the t64
transition, I am happy for this to wait for a bit :-)
The following command is from the output of:
# apt install wget devscripts dose-extra dctrl-tools
echo "nmu " ; for source in $(build-rdeps --quiet --distribution
unstable libsimde-dev); \
do for version in $(rmadison ${source} --suite unstable
--architecture source | awk '{ print $3}') ; \
do echo -n "${source}_${version} " ; done ; done ; echo " . ANY .
-m 'Rebuild using libsimde-dev 0.8.0-1.'"
nmu abpoa_1.5.1-1 bowtie2_2.5.2-1 bwa_0.7.17-7 emscripten_3.1.6~dfsg-6
examl_3.0.22-4 fasta3_36.3.8i.14-Nov-2020-1
fermi-lite_0.1+git20190320.b499514-1 gatk-bwamem_1.0.4+dfsg2-2
gmap_2024-02-22+ds-1 hhsuite_3.3.0+ds-8 hisat2_2.2.1-4 kalign_1:3.3.5-1
kmc_3.2.4+dfsg-1 last-align_1542-1 libssw_1.1-14 looking-glass_0+b6-1
macs_3.0.1-2 metaeuk_6-a5d39d9+ds-4 minimap2_2.24+dfsg-3
minimap2_2.26+dfsg-1 mmseqs2_15-6f452+ds-2
ngmlr_0.2.7+git20210816.a2a31fb+dfsg-2 obs-3d-effect_0.0.2-2
obs-advanced-scene-switcher_1.23.1-2 obs-ashmanix-blur-filter_1.0.1-2
obs-ashmanix-countdown_1.3.3-1 obs-color-monitor_0.6.1-1
obs-command-source_0.4.0-4 obs-downstream-keyer_0.2.7-2
obs-gradient-source_0.3.2-1 obs-move-transition_2.9.6-1 obs-ptz_0.10.4-1
obs-scene-as-transition_1.1.0+20230419.ce423a3-2
obs-scene-collection-manager_0.0.8-4 obs-scene-notes-dock_0.2.0-2
obs-scene-tree-view_0.1.7-1 obs-source-clone_0.1.4-1
obs-source-copy_0.2.2-7 obs-studio_29.1.3+dfsg-2
obs-studio_30.0.2+dfsg-2 obs-studio_30.0.2+dfsg-2.1
obs-time-source_0.2-3 obs-transition-table_0.2.7-1
obs-vintage-filter_1.0.0-2 obs-websocket_4.9.0-2 onednn_2.7.4-2
onednn_3.1.1-2 openmm_8.0.0+dfsg-6 openmm_8.0.0+dfsg-6.1
parasail_2.6.2+dfsg-1 pbcopper_2.3.0+dfsg-2 plast_2.3.2+dfsg-10
plink2_2.00~a5.8-231123+dfsg-1 python-skbio_0.5.9-4 rapmap_0.15.0+dfsg-3
raxml_8.2.13+dfsg-1 rna-star_2.7.11b+dfsg-1 salmon_1.10.2+ds1-1
scrappie_1.4.2-8 seqan-raptor_3.0.1+ds-5 snap-aligner_2.0.3+dfsg-2
spoa_4.0.8-1 supertuxkart_1.4+dfsg-3 vg_1.30.0+ds-1 wtdbg2_2.5-9
z3_4.8.12-3.1 . ANY . -m 'Rebuild using libsimde-dev 0.8.0-1.'
Thanks!
--
Michael R. Crusoe
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1066917: remmina: Please upgrade to 1.4.35
Source: remmina Version: 1.4.34+dfsg-1 Severity: wishlist Please update remmina to 1.4.35. I tested Remmina 1.4.34 with freerdp3 (currently in the Debian NEW queue) and it crashed attempting to connect. Remmina 1.4.35 worked though. https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md Thank you, Jeremy Bícha
Bug#1066916: wiki.debian.org: Remove ""PackagingWithGit/GitDpm/ImportDsc" because it is merged into ""PackagingWithGit/GitDpm"
Package: wiki.debian.org Severity: normal Dear Maintainer, I don't see how to remove wiki pages. Please remove "PackagingWithGit/GitDpm/ImportDsc" because it's content now is integrated into "PackagingWithGit/GitDpm". There was to less content on that page to reason it existence. Kind Christian Buhtz
Bug#1066908: lowdown FTCBFS: performs a native build
On Fri, Mar 15, 2024 at 07:23:04AM +0100, Helmut Grohne wrote:
> override_dh_auto_configure:
> + CC='$(CC)' \
> CFLAGS="${CFLAGS}" \
> ./configure \
> PREFIX=/usr \
One more thing: should we also pass AR=$(AR)? It did matter for
WebAssembly (which required the use of llvm-ar) and why I added support
for it to oconfigure¹, but I'm not sure if it makes a difference between
different binutils architectures when cross-building.
Thanks again,
Faidon
1: https://github.com/kristapsdz/oconfigure/pull/23
