On 2025-05-09 Andreas Metzler wrote:
> On 2025-05-09 Helmut Grohne wrote:
[...]
> > The file /usr/share/aclocal/autoopts.m4 is contained in the packages
> > * autogen
> >* 1:5.19.96-3 as present in experimental
> >* 1:5.19.96-3+b1 as present in experime
On 2025-05-10 Bastian Germann wrote:
> Hi Andreas,
> Am 10.05.25 um 11:31 schrieb Andreas Metzler:
>> It is a no-op, SOURCE_DATE_EPOCH is exactly
>> the date from debian/changelog
> If that is true, why does SOURCE_DATE_EPOCH change on a binNMU, which
> was the rea
Control: reopen -1 1:5.18.16-5
Control: tags -1 - patch
On 2025-05-07 Helmut Grohne wrote:
> Package: libopts25-dev
> Version: 1:5.18.16-5+b2
> Severity: serious
> Justification: unpack error
> User: debian...@lists.debian.org
> Usertags: fileconflict
> User: debian-cr...@lists.debian.org
> Usert
r
> + * Record changelog date in manpages (Closes: #1104867)
> +
> + [ Andreas Metzler ]
> + * Drop ancient (2014 and pre-2008) Breaks/Conflicts/Replaces.
> +
> + -- Bastian Germann Thu, 08 May 2025 20:03:08 +0200
> +
> autogen (1:5.18.16-5) unstable; urgency=low
>* P
On 2025-05-09 Helmut Grohne wrote:
> Package: autogen
> Version: 1:5.19.96-3
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fileconflict
> Control: affects -1 + libopts25-dev
> autogen has an undeclared file conflict. This may result in an unpack
> error from dpkg.
> The file
On 2025-04-21 Andreas Metzler wrote:
> Source: gpgme1.0
[...]
> FAIL! : AddExistingSubkeyJobTest::testAddExistingSubkeyWithExpiration()
> Compared values are not the same
>Actual (result.code()) : 0
>Expected (static_cast(GPG_ERR_INV_TIME)
Source: gpgme1.0
Version: 1.24.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org, ametz...@bebt.de
User: debian-...@lists.debian.org
Usertags: armel armhf
Hello,
upgrading gpg from 2.2 to 2.4
On 2025-04-15 Santiago Vila wrote:
> Package: src:gpgme1.0
> Version: 1.24.2-1
> Severity: serious
> Tags: ftbfs trixie sid
> Dear maintainer:
> During a rebuild of all packages in unstable, your package failed to build:
>
On 2025-04-13 Chris Hofstaedtler wrote:
> brian m. carlson (one of the git upstream copyright holders) claims
> in Bug #1094969 that git cannot be distributed when linked with
> OpenSSL. IIRC the Debian position is to use the system library
> exception.
> Indeed our /usr/lib/git-core/git-remot
On 2025-04-11 Cyril Brulebois wrote:
> Package: gpgv-udeb
> Version: 2.4.7-13
> Severity: serious
> Tags: d-i
> Justification: broken package
> Hi,
> The upload of the 2.4.7 series to unstable just broke gpgv-udeb, which
> bootstrap-base and net-retriever rely on:
> Depends: libassuan9 (>=
On 2025-03-22 Daniel Lange wrote:
[...]
> @dkg: any idea which of the last patches breaks this code path?
[...]
freepg/0027-gpg-Fix-newlines-in-Cleartext-Signature-Framework-CS.patch
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew
Control: tags -1 help
On 2025-01-29 Andreas Metzler wrote:
> On 2025-01-27 Andreas Metzler wrote:
[...]
> > Is Cmake's
> > FIND_PACKAGE(Python COMPONENTS Interpreter Development NumPy)
> > supposed to break with Numpy2?
> well I can work around this with
> -D
On 2025-01-27 Andreas Metzler wrote:
> On 2025-01-27 Bas Couwenberg wrote:
> > Source: libvigraimpex
> > Version: 1.12.1+dfsg-1
> > Severity: serious
> > Tags: upstream ftbfs
> > Justification: makes the package in question unusable or mostly so
> > Control
On 2025-01-27 Bas Couwenberg wrote:
> Source: libvigraimpex
> Version: 1.12.1+dfsg-1
> Severity: serious
> Tags: upstream ftbfs
> Justification: makes the package in question unusable or mostly so
> Control: block 1082237 by -1
> Dear Maintainer,
> Your package FTBFS during the numpy2 transition
On 2025-01-06 Andreas Metzler wrote:
> On 2025-01-03 SHITAMORI Akira wrote:
> > https://github.com/arakiken/mlterm/commit/4eb3aa4bba9d918b1923b5a46a67c92142ecaade
> > Will this change fix it?
> Hello,
> I have packaged GIT HEAD and pushed to
> https://salsa.debian.org/
On 2025-01-03 SHITAMORI Akira wrote:
> https://github.com/arakiken/mlterm/commit/4eb3aa4bba9d918b1923b5a46a67c92142ecaade
> Will this change fix it?
Hello,
I have packaged GIT HEAD and pushed to
https://salsa.debian.org/debian/mlterm/-/tree/tmp-ametzler-2025-snapshot?ref_type=heads
[I have not
pload.
+ * Build-depend on libidn-dev instead of transitional libidn11-dev package.
+Closes: #1086104
+
+ -- Andreas Metzler Sun, 29 Dec 2024 11:47:04 +0100
+
libpodofo (0.9.8+dfsg-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru libpodofo-0.9.8+dfsg/debian/control libpodofo-
Control: tags -1 patch
On 2024-12-22 Lucas Nussbaum wrote:
[...]
> > dpkg-source -b .
> > dpkg-source: info: using source format '3.0 (quilt)'
> > dpkg-source: info: building libjpeg using existing
> > ./libjpeg_0.0~git20220805.54ec643.orig.tar.xz
> > dpkg-source: info: using patch list from de
On 2024-12-22 Lucas Nussbaum wrote:
> Source: libjpeg
> Version: 0.0~git20220805.54ec643-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20241222 ftbfs-trixie
> Hi,
> During a rebuild of all packages in sid, your package failed to
On 2024-12-17 Vincent Lefevre wrote:
> On 2024-12-12 10:09:15 +0100, Yuri D'Elia wrote:
> > I'm getting a ~50% random crash chance during startup:
> [...]
> I do not notice any crash when just running mlterm from 3.9.3-2,
> but I confirm an issue I can see with valgrind:
[...]
How about packagin
Source: rst2pdf
Version: 0.102-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hello,
rst2pdf FTBFS on current sid with
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd
/tmp/JJJ/rst2pdf-0.102/.pybuild/cpython3_3.13_rst2pdf/build; python3.13 -m
pytes
21:45:16.0 +0200
+++ icewm-3.6.0/debian/changelog 2024-11-15 12:41:15.0 +0100
@@ -1,3 +1,10 @@
+icewm (3.6.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with nocheck build profile. Closes: #1086946
+
+ -- Andreas Metzler Fri, 15 Nov 2024 12:41:15 +0100
+
Control: tags -1 patch
On 2024-11-06 Helmut Grohne wrote:
> Source: icewm
> Version: 3.6.0-1
> Severity: serious
> Justification: nocheck ftbfs is rc since trixie
> Tags: ftbfs trixie sid
> Hi,
> icewm fails to build from source when enabling the nocheck build
> profile. A build ends as follows
On 2024-10-27 Vagrant Cascadian wrote:
> On 2024-09-11, Debian Bug Tracking System wrote:
> > guile-gnutls (4.0.0-2) experimental; urgency=low
> > .
> >* Re-run cme update dpkg-copyright, now that #1052168 is fixed.
> >* Test suggested fix for FTBFS by Natanael Copa. Closes: #1069390
>
On 2024-11-11 Emilio Pozuelo Monfort wrote:
[...]
> A simple pkg-config call gives the correct includes, e.g.:
> pkg-config --cflags Magick++
> -I/usr/include/x86_64-linux-gnu/ImageMagick-7 -I/usr/include/ImageMagick-7
> -fopenmp -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16
> -DMAGICK
On 2024-11-09 Andreas Metzler wrote:
[...]
> And afaict this looks like a either a bug in cmake-data 3.30.5-1 or the
> imagemagick 7 debian package uses different paths than cmake's
> /usr/share/cmake-3.30/Modules/FindImageMagick.cmake expects.
[...]
Hello,
Apart from that th
On 2024-11-10 Andreas Metzler wrote:
[...]
> pfstools uses cmakes FindImageMagick.cmake as
> find_package(ImageMagick COMPONENTS Magick++ MagickCore)
> With imagemagick 7 magick-baseconfig.h was moved from
> /usr/include/x86_64-linux-gnu/ImageMagick-6/magick/magick-baseconfig.h
Package: cmake-data
Version: 3.30.5-1
Severity: serious
Justification: 5
X-Debbugs-Cc: imagemag...@packages.debian.org, pfsto...@packages.debian.org
Affects: pfstools
Control: block 1086937 by -1
Good morning,
pfstools FTBFS against imagemagick 7 (apt-get build-dep pfstools; apt-get
install libma
On 2024-11-07 po...@debian.org wrote:
> Source: pfstools
> Severity: serious
> Hi,
> pfstools is still built against imagemagick 6, but we're transitioning
> to imagemagick 7, see [1].
> Your package may be build-depending on imagemagick 6 binaries (e.g.
> libmagickwand-6.q16-dev), in which case
On 2024-11-06 Andreas Tille wrote:
> Am Wed, Nov 06, 2024 at 06:40:41PM +0100 schrieb Andreas Metzler:
>> Are you really convinced we would not be better off dropping this
>> from Debian instead? mpg321 is stone-dead upstream (last commit about 12
>> years ago), alternatives
On 2024-11-06 Andreas Tille wrote:
> Control: tags -1 patch
> Control: tags -1 pending
> Thanks
> Hi,
> this package came up as a candidate for the Bug of the Week[1].
> I've commited a patch[2] for this bug and will file an ITS bug
> soon to get permission to maintain this package in Debian
> M
On 2023-06-28 Andrius Merkys wrote:
> On Wed, 28 Jun 2023, 10:09 Mikael Frykholm, wrote:
>>> The upstream wishes to keep the package out of stable distributions for
>>> now, until the NIST Post-Quantum Cryptography standardization project
>>> reaches its conclusion
>> Is this still true? Can th
On 2024-10-27 Simon McVittie wrote:
[...]
> I can reproduce this. The actual error appears to be:
> > + gpg --homedir=/var/tmp/tap-test.4h3gy2/gpghome --import
> > /var/tmp/tap-test.4h3gy2/gpghome/revocations/key1.rev
> > Imported 0 GPG keys to remote "R1"
> > gpg: key 7FCA23D8472CDAFA: "Ostree
Source: ostree
Version: 2024.8-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: gnu...@packages.debian.org
Hello,
ostree throws a CI error and FTBFS against current sid with gpg
2.2.45:
ERROR: tests/test-remote-gpg-list-
Package: gnupg2
Version: 2.4.5-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
No idea what broke here:
i686-w64-mingw32-gcc -I/usr/i686-w64-mingw32/include -I/usr/i686-w64-mingw32/in
clude -I/usr/i686-w64-mingw32/include -I/usr/i686
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Double quote AC_MSG_ERROR arg to avoid split on comma.
Author: Andreas Metzler
Bug-Debian: https://bugs.debian.org/1080143
Origin: vendor
La
Control: reassign -1 efl-all-dev 1.27.0-3
Control: reassign 1080105 efl-all-dev 1.27.0-3
Control: reassign 1080141 efl-all-dev 1.27.0-3
Control: forcemerge 1080103 1080105 1080103
On 2024-08-30 Santiago Vila wrote:
> Package: src:e17
> Version: 0.26.0-4
[...]
> Called: `/usr/bin/pkg-config --modv
Source: gpgme1.0
Version: 1.18.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: python3-setupto...@packages.debian.org, ametz...@debian.org
Hello,
gpgme1.0 has recently started to FTBFS on current sid while it build
suc
Control: close -1
On 2024-08-23 Santiago Vila wrote:
> reassign 1076905 libgpg-error-dev
> affects 1076905 + src:poldi
> found 1076905 1.49-2
> fixed 1076905 1.50-3
> thanks
> Hello.
> The configure error which I reported here does not
> happen anymore, but the poldi version has not changed at
024-08-23 13:54:40.0 +0200
@@ -1,3 +1,12 @@
+kleopatra (4:22.12.3-2.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Use pkgconf to locate libassuan. Closes: #1072277
+ * B-d on libqgpgme-dev (split-off QT5 gpgme bindings) instead of
+libgpgmepp-dev. Closes: #1078485
+
+ --
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gimp/-/issues/11929
On 2024-08-10 Lucas Nussbaum wrote:
> Source: gimp
> Version: 2.10.38-2
> Severity: serious
[...]
> > dh_install: warning: Cannot find (any matches for)
> > "usr/lib/gimp/2.0/plug-ins/file-heif" (tried in ., debian/tmp)
[..
+0100
+++ scute-1.5.0/debian/changelog 2024-08-15 09:51:15.0 +0200
@@ -1,3 +1,10 @@
+scute (1:1.5.0-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Also remove old copy of m4/libassuan.m4. Closes: #1072278
+
+ -- Andreas Metzler Thu, 15 Aug 2024 09:51:15 +0200
+
scute (1:1.5.
FTBFS against libgcrypt without libgcrypt-config.
+Closes: #1071933
+
+ -- Andreas Metzler Tue, 09 Jul 2024 13:14:07 +0200
+
libccrtp (2.0.9-4) unstable; urgency=medium
* Team upload.
diff -Nru libccrtp-2.0.9/debian/patches/15_delete_outdated_libgcrypt_m4_macro.diff libccrtp-2.0.9/debian/pa
estep ./configure's reliance on libgcrypt-config to locate
+libgcrypt. Closes: #1070905
+
+ -- Andreas Metzler Sun, 07 Jul 2024 18:42:43 +0200
+
collectd (5.12.0-18) unstable; urgency=medium
* [e3c9674] add .gitignore to ignore swp files
diff -Nru collectd-5.12.0/debian/.gitignore colle
.553060d/debian/changelog 2024-07-07 16:03:11.0 +0200
@@ -1,3 +1,11 @@
+poldi (0.4.2+git20161115.553060d-1.4) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Delete outdated local copy of libgcrypt.m4 which relies on
+libgcrypt-config. (Closes: #1071951)
+
+ -- Andreas Metzle
+0100
+++ gfsecret-0.5.0/debian/changelog 2024-07-07 15:51:49.0 +0200
@@ -1,3 +1,11 @@
+gfsecret (0.5.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Delete outdated copy of libgcrypt.m4 which requires libgcrypt-config.
+Closes: #1071862
+
+ -- Andreas Metzler Sun, 07 Jul 20
Control: tags -1 pending
See
https://github.com/bitlbee/bitlbee/commit/684aca266fad3fe7793fe637a71b095500c35998
cu Andreas
signature.asc
Description: PGP signature
ebian/changelog 2024-07-07 15:34:28.0 +0200
@@ -1,3 +1,10 @@
+axc (0.3.7-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use pkg-config to locate libgcrypt. Closes: #1070903
+
+ -- Andreas Metzler Sun, 07 Jul 2024 15:34:28 +0200
+
axc (0.3.7-1) unstable; urgency=medium
hntpw-140201/debian/changelog 2024-07-07 14:07:39.0 +0200
@@ -1,3 +1,11 @@
+chntpw (140201-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use pkg-config instead of libgcrypt-config to locate libgcrypt.
+Closes: #1071837
+
+ -- Andreas Metzler Sun, 07 Jul 2024 14:07:39
Control: tags -1 patch
On 2024-06-16 Lucas Nussbaum wrote:
> Source: abiword
> Version: 3.0.5~dfsg-3.2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240615 ftbfs-trixie
> Hi,
> During a rebuild of all packages in sid, your packag
Control: tags -1 pending
On 2024-06-23 Andreas Metzler wrote:
[...]
> I will give it a litte bit of time to check whether somebody else from
> -med picks this up and will NMU otherwise.
Hello,
I have now uploaded a NMU to delayed/7-days using the attached patch. I
have gone for the m
Control: tags -1 patch
On 2024-06-19 "Gustavo R. Montesino" wrote:
> Package: libuim-data
> Version: 1:1.8.8-9.4
> Severity: serious
> Justification: Policy 8.6
> Hello,
> Can't upate libuim-data due to undefined symbol in uim-module-manager:
> Configurando libuim-data (1:1.8.8-9.4) ...
> uim-
Control: tags -1 patch
On 2024-06-23 Andreas Tille wrote:
> Control: tags -1 help
> Hi Andreas,
> strange, it has build for me.
Very strange, perhaps you did not build against the libgcrypt package in
experimental.
> Am Sun, Jun 23, 2024 at 08:03:30AM +0200 schrieb And
FTP Masters
> (reply to Andreas Tille ).
[...]
> fis-gtm (7.0-005-2) unstable; urgency=medium
> .
>* Build-Depends: s/libgcrypt20-dev | //, pkgconf
> Closes: #1071860
[...]
> From: Andreas Metzler
> To: Debian Bug Tracking System
> Subject: fis-gtm: Searches
On 2024-06-07 Carlos Henrique Lima Melara wrote:
> On Wed, 5 Jun 2024 18:39:40 +0200 Andreas Metzler wrote:
[...]
>> TESTFAIL: These test cases failed: 241 507
> Were you able to consistently get those exact failures? We are getting
> some random and unreproducible failure
Package: curl
Version: 8.8.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hello,
I did a local rebuild on sid which failed:
srcdir=. /usr/bin/perl -I. ./runtests.pl -a -p ~flaky ~timing-dependent -n -j35
~300 ~301 ~303 ~304 ~306 ~
On 2024-05-27 Daniel Kahn Gillmor wrote:
[...]
> Would anyone be willing to try to backport the patches from upstream's
> fixes for T6481 to the 2.2.x series?
Hello Daniel,
the issue report refers to two patches, one of these is already part of
2.2.43. The other one[1] seemed pretty straightforw
Control: tags -1 fixed-upstream
On 2024-05-05 Andreas Metzler wrote:
> On 2024-05-04 Santiago Vila wrote:
> > found 1064486 0.16.3-1
> > tags 1064486 + ftbfs bookworm trixie sid
> > thanks
> > El 20/4/24 a las 14:12, Andreas Metzler escribió:
> > > FWIW I
On 2024-05-04 Santiago Vila wrote:
> found 1064486 0.16.3-1
> tags 1064486 + ftbfs bookworm trixie sid
> thanks
> El 20/4/24 a las 14:12, Andreas Metzler escribió:
> > FWIW I also get testsuite errors on current sid on amd64
> > The following tests
On 2024-04-20 Lucas Nussbaum wrote:
> Source: libsoup2.4
> Version: 2.74.3-7
> Severity: serious
> Justification: FTBFS
[...]
> > (hsts-test:547071): GLib-Net-WARNING **: 04:03:06.247: Failed to load TLS
> > database: System trust contains zero trusted certificates; please
> > investigate your G
23-03-20 07:10:18.0 +0100
+++ veusz-3.6.2/debian/changelog 2024-04-21 14:19:21.0 +0200
@@ -1,3 +1,10 @@
+veusz (3.6.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop runtime library packages (not -dev) from b-d. Closes: #1067915
+
+ -- Andreas Metzler Sun, 2
024-04-21 13:23:59.0 +0200
@@ -1,3 +1,11 @@
+deepin-movie-reborn (5.10.8-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Change hardcoded dependency to libqt5concurrent5t64 instead of
+libqt5concurrent5. Closes: #1068224
+
+ -- Andreas Metzler Sun, 21 Apr 2024 13:23:59
,12 @@
+trantor (1.5.12+ds-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Pull fix from Ubuntu by Michael Hudson-Doyle:
++ Drop spurious Depends on libssl3 as package is currently built with no
+ TLS provider. Closes: #1068226
+
+ -- Andreas Metzler Sun, 21 Apr 2024 12:04:17 +
On 2024-04-08 Andre Noll wrote:
> On Sun, Apr 07, 22:02, Peter Michael Green wrote:
> > After being rebuilt for the time64 transition, tfortune
> > depends on both liblopsub1 and liblopsub1t64. As a
> > result it is uninstallable on architectures that are undergoing
> > the time64 transition (arm
2023-09-06 15:48:31.0 +0200
+++ urfkill-0.5.0/debian/changelog 2024-04-21 11:43:27.0 +0200
@@ -1,3 +1,10 @@
+urfkill (0.5.0-7.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop hardcoded dependency on libglib2.0-0. Closes: #1068689
+
+ -- Andreas Metzler Sun, 2
His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Fixx FTBFS due to implicit declarations in autoconf tests.
Author: Andreas Metzler
Bug-Debian: https://bugs.debian.org/1069307
Origin: vendor
Last-Update: 2024-04-20
--- a/libs/ldapa
nf.
+Closes: #1066396
+
+ -- Andreas Metzler Sat, 20 Apr 2024 14:28:35 +0200
+
lftp (4.9.2-2) unstable; urgency=medium
* lftp.tech domain doesn't work anymore; switch back to lftp.yar.ru
diff -Nru lftp-4.9.2/debian/patches/ftbfs_implicit.diff lftp-4.9.2/debian/patches/ftbfs_implicit
On 2024-02-23 Bo YU wrote:
> Source: rnp
> Version: 0.17.0-3
> Severity: serious
> Dear Maintainer,
> The package has a ftbfs issue on my local amd64 build:
> ```
> 260/260 Test #255: cli_tests-Encryption
> .. Passed 60.86
> sec
>
On 2024-03-06 Ondřej Surý wrote:
>> On 6. 3. 2024, at 12:45, Matthias Klose wrote:
>> Package: bind9-libs
>> Version: 1:9.19.21-1
>> Severity: serious
>> Tags: sid trixie
>> bind9-libs hard-codes a dependency on libuv1, that should be
>> libuv1t64 now. But better derive it form the libuv1-dev
On 2024-03-23 Diederik de Haas wrote:
[...]
> 2) near the end of your build log is the following message:
> "../os/meson.build:63:8: ERROR: Problem encountered: secure-rpc requested,
> but
> neither libtirpc or libc RPC support were found"
> And that matches the build issue mentioned in #1065184
0
@@ -1,3 +1,10 @@
+dvdisaster (0.79.10-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with -Werror=implicit-function-declaration Closes: #1066010
+
+ -- Andreas Metzler Sun, 07 Apr 2024 18:38:18 +0200
+
dvdisaster (0.79.10-3) unstable; urgency=medium
* Team upload
diff
Control: tags -1 patch
On 2024-04-02 Peter Michael Green wrote:
> Package: chatty
> Version: 0.8.2-1
> Severity: serious
> User: debian-...@lists.debian.org
> Usertag: time-t
> After being rebuilt for the time64 transition, chatty depends
> on both libpurple0 and libpurple0t64. As a
> result it
Control: tags -1 fixed-upstream
On 2024-03-10 Sebastian Ramacher wrote:
> Source: epic4
> Version: 1:2.10.10-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/statu
0 +0100
+++ mpg321-0.3.2/debian/patches/ftbfs_implicit.diff 2024-03-27 15:39:14.0 +0100
@@ -0,0 +1,34 @@
+Description: Fix build error with -Wno-error=implicit-function-declaration
+Author: Andreas Metzler
+Origin: vendor
+Forwarded: no
+Last-Update: 2024-03-27
+Bug-Debian:
On 2024-03-26 Joachim Reichel wrote:
> Hi Andreas,
> usually I would have implemented your suggestion (and I don't mind anyone
> implementing it), but I'm not really keen on investing in a dependency that
> hasn't seen a single upstream release in 12 years and where the last upload
> was an NMU f
On 2024-03-22 Joachim Reichel wrote:
> tag 1066115 + patch
> thanks
> Hi,
> attached is the debdiff for the NMU, uploaded to delayed/10. Similar to the
> previous NMU it adds -Wno-error=implicit-function-declaration to downgrade
> these errors back into warnings again.
[...]
That seems to be su
Source: libspf2
Version: 1.2.10-8.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Even with fixing the -Werror=implicit-function-declaration build error
libspf2 also fails to build (dpkg-buildpackage -b) at dh_installdocs
with:
Control: tags -1 patch
On 2024-03-24 Andrey Rakhmatullin wrote:
> On Wed, Mar 13, 2024 at 01:03:20PM +0100, Lucas Nussbaum wrote:
> > > ./config.h:2540:11: fatal error: trio.h: No such file or directory
> > > 2540 | # include "trio.h"
> > > | ^~~~
> (this suggests that using
On 2024-03-13 Lucas Nussbaum wrote:
> Source: canna
> Version: 3.7p3-20
> Severity: serious
[...]
> 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
Control: tags -1 patch
On 2024-03-13 Lucas Nussbaum wrote:
> Source: uim
> Version: 1:1.8.8-9.2
> 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 fail
Source: xmorph
Version: 1:20150712-5
Severity: serious
Tags: ftbfs
Hello,
there are multiple implicit function errors when trying to build
xmorph, some trivial, but also an API issue:
8X--
In file included from RgbaImage.c:935:
RgbaImage.c: In function 'rgbaImageWarp':
warp.h:19:20: e
On 2024-03-13 Thorsten Glaser wrote:
[...]
> >It is fixed in 2.4 and I am very reluctant to backport major packaging
> >updates to 2.2
> For some values of major; Helmut already verified that the resulting
> binary packages are identical, and…
> >since I think we will need to ship some kind of 2
Control: notfound 1066137 2.4.3-2
Control: close 1066137 2.4.3-2
On 2024-03-14 Sune Stolborg Vuorela wrote:
> On Wednesday, March 13, 2024 7:10:13 PM CET Andreas Metzler wrote:
>> I have upload a fix for 2.2, probably will not be able to spend any time
>> on 1.x or 2.4 bef
On 2024-03-13 Thorsten Glaser wrote:
> clone 1066137 -1
> reassign -1 gnupg1 1.4.23-1.1
> retitle -1 gnupg1: fails to build gpgkeys_ldap, probably due to
> -Werror=implicit-function-declaration
> thanks
> Dixi quod…
> >This matches the following failure mode at the end of the build:
> Same for
Control: forcemerge 1066137 1066744
Control: found 1066137 2.4.3-2
On 2024-03-12 Thorsten Glaser wrote:
> Source: gnupg2
> Version: 2.2.40-1.1
> Severity: serious
> Justification: ftbfs
> X-Debbugs-Cc: t...@mirbsd.de
> Trying to binNMU gnupg2 to make it installable during t64 transition,
> I not
Control: tag -1 pending
Hello,
Bug #1063316 in xmorph reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian-phototools-team/xmorph/-/commit/f7dfca3f49f85a97890
On 2024-03-09 Sebastian Ramacher wrote:
> Source: freewnn
> Version: 1.1.1~a021+cvs20130302-7.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=
On 2024-03-01 Daniel Serpell wrote:
> Source: poppler
> Followup-For: Bug #1064282
> Control: reopen 1064282
> As reported in bug 1065155, the provided patch was incorrect, the
> X-Time64-Compat header is set incorrectly to libpoppler-cpp0v5 for all
> the library packages.
Good Morning,
Also af
On 2024-02-29 Aurelien Jarno wrote:
> Source: exim4
> Version: 4.97-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> User: debian-gl...@lists.debian.org
> Usertags: libnsl-dev
> Dear maintainer,
> Starting with glibc 2.31, sup
Source: libgdiplus
Version: 6.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
libgdiplus FTBFS on current sid:
make[7]: Entering directory '/dev/shm/x/libgdiplus-6.1+dfsg/gtest_build'
[ 12%] Building CXX object googletest/CMake
Comtrol: tags -1 patch
On 2024-02-07 Andreas Beckmann wrote:
> Package: libeegdev-dev,libeegdev0t64
[...]
> Something weird happened after the package rename:
> /usr/share/doc/libeegdev0/changelog.Debian.gz
> /usr/share/doc/libeegdev0/changelog.gz
> Are now shipped by libeegdev-dev and libe
Control: tags -1 patch
On 2024-02-07 Andreas Beckmann wrote:
> Package: atm-tools
> Version: 1:2.5.1-5.1~exp1
[...]
> atm-tools/experimental has gained two unexpected files, causing file
> conflicts on upgrades:
[...]
> There is still an libatm1 dependency, and the new libatm1t64 dependency
> see
On 2024-02-06 Helmut Grohne wrote:
> Package: libselinux1t64
[...]> This looks fairly innocuous. We create a minimal sid chroot and install
> libselinux1t64 using apt. What could possibly go wrong? Well, apt thinks
> that it would be a good idea to avoid coinstalling breaking packages and
> first
On 2024-02-05 Niels Möller wrote:
> Graham Inggs writes:
>> we have identified nettle as a source package shipping runtime
>> libraries whose ABI either is affected by the change in size of
>> time_t, or could not be analyzed via abi-compliance-checker (and
>> therefore to be on the safe side we
On 2024-01-28 Adrian Bunk wrote:
> ppmtowinicon -andpgms \
> kcemu-winicon_16x16.ppm kcemu-winicon_16x16.alpha.pgm \
> kcemu-winicon_32x32.ppm kcemu-winicon_32x32.alpha.pgm \
> kcemu-winicon_48x48.ppm kcemu-winicon_48x48.alpha.pgm \
> > kcemu-winicon.ico
> malloc(): invalid
On 2023-11-01 Debian Bug Tracking System wrote:
[...]
> #1042659: restic: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all
> arguments converted during string formatting
> It has been closed by Debian FTP Masters
> (reply to Félix Sipma ).
[...]
>* New upstream version 0.16.0 (Clos
c-fix-building-with-Sphinx-6.patch from upstream to fix
+FTBFS against sphinx >= 6. Closes: #1042659
+
+ -- Andreas Metzler Wed, 01 Nov 2023 13:49:52 +0100
+
restic (0.14.0-1) unstable; urgency=medium
* New upstream version 0.14.0 (Closes: #1018154)
diff -Nru restic-0.14.0/debian/patc
On 2023-10-31 Tomas Pospisek wrote:
[...]
> PS: I'd prefer this bugreport to be open as long as the stable and
> oldstable packages are still vulnerable...
Hello Thomas,
The Debian BTS does not use a simple open/close logic, it tracks which
specific versions a bug applies to. If you look at
h
On 2023-10-31 Tomas Pospisek wrote:
> On Tue, 31 Oct 2023, Salvatore Bonaccorso wrote:
[...]
>> Fixes for CVE-2023-42117 and CVE-2023-42119 are right now considered
>> no-dsa (see comment on the security-tracker about it), and are going
>> to be fixed in the next point releases.
> The notes say:
Colntrol: tags -1 patch
On 2023-07-30 Lucas Nussbaum wrote:
> Source: restic
[...]
> restic fails to build with Sphinx 7.1 and docutils 0.20, both of which
> are currently available in experimental.
> Relevant part (hopefully):
[...]
> >
> > Exception occurred:
> > File "/usr/lib/python3/dist
1 - 100 of 807 matches
Mail list logo
