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
-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, 21 Apr
: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 +0200
+
deepin
(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 +0200
+
trantor
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
-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, 21 Apr
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/ldapaddressbook/configure.ac
+++ b/libs/ldapaddressboo
: #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.diff
--- lftp-4.9.2
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
@@
+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 -Nru dvdisaster
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
>
+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: https
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
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
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
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:
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
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
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
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:
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
>
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
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,
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
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
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
>
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
>
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
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():
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
-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/patches/0
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
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
Contol: tags 1039724 - pending
Contol: tags 1039724 - wontfix
On 2023-10-27 Lucas Nussbaum wrote:
> Source: gpgme1.0
> Version: 1.18.0-3
[...]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> Relevant part (hopefully):
[...]
> > dh_install: warning: Cannot
On 2023-10-20 Jeremy Stanley wrote:
> It looks to me like the default Exim config in Debian explicitly
> calls /usr/bin/spfquery.mail-spf-perl from the spf-tools-perl
> package, not the libspf2 implementation supplied by the spfquery
> package. Also spf-tools-perl is suggested by exim4-base,
On 2023-10-15 Wookey wrote:
[...]
> OK. So I read all that, and learned a whole load of stuff I was quite
> happy not knowing about.
> However despite reading it all, and especially this bit:
> "Whenever I've maintained man pages in roff I tend to be precise in
> > the usage of - and \-, but TBH
On 2023-10-01 Andreas Metzler wrote:
> On 2023-10-01 Rainer Dorsch wrote:
[...]
> > It would help if there would be a statement by the Debian exim
> > maintainer team, by when updates are expected to arrive.
> > This would at least help to judge, if I should migrate my s
On 2023-10-01 Rainer Dorsch wrote:
> Package: exim4-base
> Version: 4.94.2-7
> Severity: critical
> Justification: breaks the whole system
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where appropriate ***
> There are various CVE report with a rating of 9.8/10.
Package: libflann-dev
Version: 1.9.2+dfsg-1
Severity: serious
flann.pc looks broken:
Libs: -L${libdir} -L/usr/lib/x86_64-linux-gnu;-llz4 -lflann -lflann_cpp
^^^
cu Andreas
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 5:08 PM Andreas Metzler wrote:
[...]
> > Looking at the changelog entry
> > * Drop specify-timestamp.patch, applied upstream in binutils 2.41
> > (Closes: #1042734)
> > changing the rdeps does not m
Control: tags 1052219 moreinfo
On 2023-09-19 Shengjing Zhu wrote:
> On Tue, Sep 19, 2023 at 2:57 PM Shengjing Zhu wrote:
> > Package: binutils-mingw-w64-i686
> > Version: 2.41-4+11+nmu1
[...]
>> The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch.
>> It causes libgcrypt20,
On 2023-09-15 "László Böszörményi (GCS)" wrote:
[...]
> There's still a font issue, you will get something like:
> fontconfig: Didn't find expected font family. Perhaps URW Type 1 fonts
> need installing?
> I don't know why this is happening, as if I check the intermediate dot
> file then only
Hello,
I tried to do a test build of enblend against graphviz 8.1.0 from
experimental. I had no luck, since dot seems to be built without support
for png output:
/usr/bin/m4 --fatal-warnings --prefix-builtins --synclines
--define='dot_output_type=png' ../../doc/uml-dot.m4
Control: reassign -1 graphviz 2.42.2-7
On 2023-08-27 Aurelien Jarno wrote:
> Source: enblend-enfuse
> Version: 4.2-10
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Dear maintainer,
> enblend-enfuse fails to build from
On 2023-08-10 "Torrance, Douglas" wrote:
[...]
> I've applied the patch that you submitted upstream [1] to the package. I
> think this should fix the issue. See the latest draft in Salsa [2].
> Does this look okay?
Thank you, yes. (As you are no doubt aware) there is a functionally
identally
Package: libwraster6
Version: 0.96.0-1
Severity: grave
Tags: upstream
Justification: Policy 8.6.2
Hello,
already communicated upstream, lets add a blocker bug. The new release
bumped the symbol version of all symbols from LIBWRASTER6 to
LIBWRASTER7, i.e. we have got total ABI breakage, none of
Package: guile-gnutls
Version: 3.7.12
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
I have already forwarded this upstream
https://gitlab.com/gnutls/guile/-/issues/15
On 2023-07-04 Ted wrote:
> The only software which has ever run here is from a bookworm or vscodim
> repo so i will just wait for bookworm to stabilize and hope i can abandon
> the workarounds in the future.
Hello,
You were right all the time. python3-setuptools is the culprit,
installing it
On 2023-07-04 Blair Noctis wrote:
> On Tue, 04 Jul 2023 14:37:49 +0300 Adrian Bunk wrote:
[...]
> > result = self._execute('import importlib;
> > print(importlib.util.MAGIC_NUMBER)', version)
> >
> >
On 2023-07-03 Ted wrote:
> Just to keep updated, I checked if all build deps have updates in
> bookworm-updates and bookworm-security, but didn't find anything. I also
> checked to make sure that the package versions i'm using for all build
> dependencies are equal to the latest in bookworm.
You
On 2023-07-03 Andreas Metzler wrote:
[...]
> As I wrote before I /suspect/ because you have some outdated locally
> installed python modules and have configured the system to use them in
> preference to the system installed ones.
To provide some more detail: Your buildlogs lack t
On 2023-07-03 Ted wrote:
> On Sun, Jul 2, 2023 at 8:08 PM Ted wrote:
[...]
> > If I want to ensure that my packages build well, I can use a chroot, but
> > this is not actually something that a package should assume. Chroots are a
> > way to mitigate broad sources of brittleness, but we
On 2023-07-01 Ted wrote:
> Build still fails under debuild with no funny flags. Here's log.
[...]
Hello,
Looking at the log it looks like your are overriding CFLAGS somewhere
(-g -O2 -ffile-prefix-map=/... is missing).
This warning is missing in your log:
Control: tags -1 - patch
Control: tags -1 moreinfo
On 2023-06-28 Theodoric Stier wrote:
> Package: gpgme
> Severity: serious
> Tags: ftbfs patch
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: kerd...@gmail.com
> Dear Maintainer,
> Trying to
On 2023-06-14 Andreas Metzler wrote:
> On 2023-06-14 Andreas Beckmann wrote:
[...]
> > after building gnutls28/experimental with pbuilder, there are a lot of
> > gnutls-serv and a few openssl s_server processes running, preventing
> > pbuilder to cleanup the chroo
Control: found -1 3.8.0+git20230413-1
On 2023-06-14 Andreas Beckmann wrote:
> Source: gnutls28
> Version: 3.8.0+git20230529-1
> Severity: serious
> Hi,
> after building gnutls28/experimental with pbuilder, there are a lot of
> gnutls-serv and a few openssl s_server processes running,
Hello,
if you have not got time for an upload I can look into it.
cu Andreas
On 2023-05-24 Mathieu Malaterre wrote:
> On Wed, May 24, 2023 at 6:21 PM Andreas Metzler wrote:
[...]
> > Correct patch attached. Stuff was built but the respective dh_install
> > call was shadowed and therefore content was not shipped in the package.
> [...]
> -over
LEASED; urgency=medium
+
+ * Team upload.
+ * Fix broken symlink. Closes: #1036584
+
+ -- Andreas Metzler Wed, 24 May 2023 12:45:48 +0200
+
openjpeg2 (2.5.0-1) unstable; urgency=medium
* New upstream version 2.5.0
diff -Nru openjpeg2-2.5.0/debian/openjpeg-doc.install openjpeg2-2.5.0/deb
On 2023-05-20 Christopher Obbard wrote:
[...]
> > I've prepared an NMU for rkdeveloptool (versioned as
> > 1.32+git20210408.46bb4c0-2.1) and uploaded it to DELAYED/1.
[...]
> Thank you for your contribution, but it seems like there is some
> parallel work (this morning in fact).
> I am
Control tags -1 - patch - pending
On 2023-05-20 Rene Engelhard wrote:
> Hi,
> Am 20.05.23 um 11:38 schrieb Andreas Metzler:
> > I've prepared an NMU for python-ooolib (versioned as 0.0.22-5.1) and
> > uploaded it to DELAYED/1. Please feel free to tell me if I
> > should
.
+Closes: #998940
+
+ -- Andreas Metzler Sat, 20 May 2023 11:31:16 +0200
+
python-ooolib (0.0.22-5) unstable; urgency=medium
* remove obsolete debian/pycompat and Python-Provides:
reverted:
--- python-ooolib-0.0.22/debian/compat
+++ python-ooolib-0.0.22.orig/debian/compat
@@ -1 +0,0 @@
-5
diff
: #1035436
+
+ -- Andreas Metzler Sat, 20 May 2023 11:03:08 +0200
+
rkdeveloptool (1.32+git20210408.46bb4c0-2) unstable; urgency=medium
[ Debian Janitor ]
diff -Nru rkdeveloptool-1.32+git20210408.46bb4c0/debian/control rkdeveloptool-1.32+git20210408.46bb4c0/debian/control
--- rkdeveloptool-1.32
+
+ * Non-maintainer upload.
+ * Add libmcpl-dev: missing Depends on runtime library packages.
+Closes: #1035450
+
+ -- Andreas Metzler Sat, 20 May 2023 06:57:53 +0200
+
mcpl (1.3.2-3) unstable; urgency=medium
* Source-only upload for migration to testing.
diff -Nru mcpl-1.3.2/debian/control
Hello,
having read up on the current NMU timing guidance in developers
reference I will reschedule these to 1-day.
cu Andreas
--
`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'
signature.asc
Description:
2023-05-18 18:20:13.0 +0200
@@ -1,3 +1,11 @@
+ktexteditor (5.103.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing Breaks/Replaces of ktexteditor-data against
+libkf5texteditor-dev. Closes: #1034951
+
+ -- Andreas Metzler Thu, 18 May 2023 18:20:13 +0200
:17:42.0 +0200
@@ -1,3 +1,10 @@
+colord-gtk (0.3.0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix typo "Replacs" in debian/control. Closes: #1034921
+
+ -- Andreas Metzler Thu, 18 May 2023 14:17:42 +0200
+
colord-gtk (0.3.0-3) unstable; urgency=medium
/Replaces for correction of xineliboutput-fbfe desktop
+icon. Closes: #1034915
+
+ -- Andreas Metzler Thu, 18 May 2023 13:40:36 +0200
+
vdr-plugin-xineliboutput (2.2.0+git20211212-2.1) unstable; urgency=medium
[ Helmut Grohne ]
diff -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian
upload.
+ * Fix package-relationships with flex-old:
++ Add flex Conflicts/Replaces flex-old
++ Change versioned libfl2-dev Replaces/Breaks against flex-old (<=
+ 2.5.4a-10) to unversioned Conflicts/Replaces flex-old.
+Closes: #1034931
+
+ -- Andreas Metzler Thu, 18 May 2023 11
On 2023-04-27 Helmut Grohne wrote:
> Package: libfl-dev
> Version: 2.6.4-8.1
> Severity: serious
> Justification: dpkg unpack error
> Attempting to unpack libfl-dev/2.6.4-8.1 from Debian bookworm
> on a minimal Debian bullseye with flex-old/2.5.4a-10.1
> installed, causes an unpack error from
On 2023-05-07 Andreas Metzler wrote:
[...]
> The only proper fix would be to use versioned symbols for libpoppler
> (and libpoppler-glib while we are at it). This should not be rocket
> science, just tie it to the soname.
> But that needs to happen upstream.
Something like attach
On 2021-02-18 Simon McVittie wrote:
[...]
> So elpa-pdf-tools-server is linked to libpoppler-glib, and because the
> (parts of the) libpoppler-glib API that it uses has not changed for a
> while, it is happy with an old version; but then during a partial
> upgrade, it can get this
>
zabbix Closes: #1034973
++ pcp-doc Closes: #1034966
++ pcp-zeroconf Closes: #1034895
++ pcp-export-pcp2xlsx (unfiled)
+
+ -- Andreas Metzler Sun, 07 May 2023 11:36:37 +0200
+
pcp (6.0.3-1) unstable; urgency=low
* New release (full details in CHANGELOG).
diff -Nru pcp-6.0.3/debian/c
on libwmf0.2-7-gtk to libwmf-0.2-7-gtk.
+Closes: #1034959
+
+ -- Andreas Metzler Sat, 06 May 2023 18:19:26 +0200
+
libwmf (0.2.12-5) unstable; urgency=medium
* Upload to unstable
diff -Nru libwmf-0.2.12/debian/control libwmf-0.2.12/debian/control
--- libwmf-0.2.12/debian/control 2022-01-25 09:16
Control: tag -1 pending
Hello,
Bug #1034986 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:
On 2023-04-29 Andreas Metzler wrote:
[...]
> Trivial patch:
[...]
I will fix this.
cu Andreas
On 2023-04-27 Helmut Grohne wrote:
> Package: xmorph
> Version: 1:20150712-1
> Severity: serious
> Justification: dpkg unpack error
> Attempting to unpack xmorph/1:20150712-1 from Debian bookworm
> on a minimal Debian bullseye with libmorph/1:20140707+nmu2.1
> installed, causes an unpack error
On 2023-04-20 Paul Gevers wrote:
> Hi Andreas,
> On Fri, 31 Mar 2023 15:06:14 +0200 Andreas Metzler wrote:
> > I think 2.5.7-2 was the last sourceful < 3 upload, so (<< 2.5.7-3)
> > should work.
> And to be backports and other local packages, I think that
On 2023-04-13 Paul Gevers wrote:
> Source: gnutls28
> Version: 3.7.9-1
> Severity: serious
> Control: tags -1 bookworm-ignore
> User: debian...@lists.debian.org
> Usertags: regression
> Dear maintainer(s),
> Your package has an autopkgtest, great. However, it fails everywhere but on
> amd64. If
Control: tags -1 - ftbfs
On 2023-04-08 Andreas Beckmann wrote:
> Source: sdop
> Version: 1.00-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source twice in a row
> Hi,
> sdop/experimental fails to build twice in a row. (I haven't checked
> whether the package in sid
ilmbase-dev Breaks/Replaces binNMU-safe.
+Closes: #1033617
+
+ -- Andreas Metzler Fri, 31 Mar 2023 15:02:17 +0200
+
openexr (3.1.5-4) unstable; urgency=medium
* d/control: Add missing zlib1g-dev dependency. Closes: #1017516
diff --git a/debian/control b/debian/control
index 5fecc23..3d783c2 100644
--
On 2023-03-28 Felix Stupp wrote:
> Package: libopenexr-dev
> Version: 3.1.5-4
> Severity: serious
> Justification: Policy 7.4
> X-Debbugs-Cc: me+debian-b...@banananet.work
> Dear Maintainer,
> I cannot upgrade this package from version 2.5.7-1 to version 3.1.5-4
> due to a file conflict with
-maintainer upload.
+ * In migration CI test skip debian-archive-bookworm-stable.gpg (and
+aggregated keyring), gpg1 cannot read the ed25519 key. Closes: #1033155
+
+ -- Andreas Metzler Sun, 26 Mar 2023 15:03:05 +0200
+
gnupg2 (2.2.40-1) unstable; urgency=medium
* new upstream version
diff -Nru
On 2023-03-26 Andreas Metzler wrote:
> On 2023-03-18 Jonathan Wiltshire wrote:
[...]
> > The stable release key for bookworm is EC, and this causes gpg1 to bail
> > out when it is imported as part of the migration test. Attached patch
> > limits the keyrings used to the arc
On 2023-03-18 Jonathan Wiltshire wrote:
> Source: gnupg2
> Version: 2.2.40-1
> Severity: important
> Tags: patch
> X-Debbugs-Cc: j...@debian.org
> Hi,
> The stable release key for bookworm is EC, and this causes gpg1 to bail
> out when it is imported as part of the migration test. Attached
On 2023-01-20 tester732732 via Pkg-phototools-devel
wrote:
> Package: imv
> Version: 4.3.0-1.1+b3
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: devnull771...@proton.me
> Dear Maintainer,
>* What led up to the situation?
> After installing imv on debian
On 2022-08-24 Markus Koschany wrote:
> Package: idesk
> Version: 0.7.5-6
> Severity: important
> Tags: ftbfs sid bookwork
> User: a...@debian.org
> Usertags: imlib2-1.9.1
> X-Debbugs-Cc: a...@debian.org
> Dear maintainer,
> your package fails to build from source with imlib2 1.9.1 in
>
Control: tags -1 patch
On 2022-12-28 Sebastian Ramacher wrote:
> Source: kicad
> Version: 6.0.10+dfsg-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>
On 2022-12-20 Lucas Nussbaum wrote:
> Source: libvigraimpex
> Version: 1.11.1+dfsg-10
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
> Hi,
> During a rebuild of all packages in sid, your package failed to
On 2022-12-09 Andreas Tille wrote:
[...]
> Thanks to Alexander Sulfrian who pointed out the Git repository
> featuring old tags that were obviously taken over from SVN I was proven
> wrong with the statement that there is no configure.ac any more.
> Unfortunately this is no simple drop-in with
>=
+1.18.0-2 by using pkg_search_module(). Closes: #1024577
+
+ -- Andreas Metzler Thu, 08 Dec 2022 12:07:05 +0100
+
libzypp (17.25.7-2.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru libzypp-17.25.7/debian/patches/1010_gpgme-pkg_search_module.diff libzypp-17.25.7/deb
On 2022-11-25 Aurélien COUDERC wrote:
[...]
> I tried applying the patch on top of upstream 22.08.3 and the build still
> fails. [0]
> Ideas welcome, I won't have the time to analyse the issue any further.
Good morning,
adding pkg-config to Build-Depends works for me.
cu Andreas
--
`What a
1 - 100 of 741 matches
Mail list logo
