On 2024-04-08 18:30, Andreas Metzler wrote:
>> It fails with "*** Fatal error: The encryption algorithm is not supported."
>
> Thank you and sorry. I have done a bisect and will try reverting the
> offending upstream commit as a hotfix.
Thank you for the quick fix. I've just updated the
Package: urfkill
Version: 0.5.0-7.1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, urfkill
depends on both libglib2.0-0 and libglib2.0-0t64. As a
result it is uninstallable on architectures that are undergoing
Package: tpm2-initramfs-tool
Version: 1.0.1-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, tpm2-initramfs-tool
depends on both libtss2-esys-3.0.2-0 and libtss2-esys-3.0.2-0t64. As a
result it is uninstallable
Source: bornagain
Version: 21.1+ds3-4
Severity: serious
Tags: ftbfs
Dear Maintainer,
Recently upload did not fixed ftbfs on many architectures, see:
https://buildd.debian.org/status/package.php?p=bornagain
Tests failed on arm64, ppc64el, riscv64 and s390x. Build issue on
arm{el,hf} and i386.
Source: zmat
Version: 0.9.9+ds.1-2
Severity: serious
Tags: ftbfs
Dear Maintainer,
The package has ftbfs issue but on amd64 and i386, the common issue is
follows:
```
CC obj/conf_91c451f6ae5e059804729dd256611361/static/cover.o
CC obj/conf_91c451f6ae5e059804729dd256611361/static/divsufsort.o
CC
Control: forwarded -1 https://github.com/newsboat/newsboat/issues/2716
On Fri, 27 Oct 2023 21:15:28 +0200 Lucas Nussbaum
wrote:
> Source: newsboat
> Version: 2.32-3
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231027
Processing control commands:
> forwarded -1 https://github.com/newsboat/newsboat/issues/2716
Bug #1054680 [src:newsboat] newsboat: FTBFS: test/cliargsparser.cpp:1:10: fatal
error: 3rd-party/catch.hpp: No such file or directory
Set Bug forwarded-to-address to
Hi Nilish,
I don't have a 32-bit machine to test on, but my understanding is that
Linux has moved to a 64-bit signed integer for time_t and this is a long
long on 32-bit machines which is explicitly not supported by GMP's C++ API.
https://en.wikipedia.org/wiki/Year_2038_problem
Your message dated Mon, 08 Apr 2024 23:05:55 +
with message-id
and subject line Bug#1065088: fixed in pam 1.5.3-7
has caused the Debian Bug report #1065088,
regarding pam 1.5.3-5 not suitable because pam_userdb is missing
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> reopen 1064128
Bug #1064128 {Done: Kyle Robbertze } [src:liquidsoap]
liquidsoap: FTBFS: Error: Unbound module Pcre
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to
Your message dated Mon, 08 Apr 2024 22:07:01 +
with message-id
and subject line Bug#1066681: fixed in scilab 2024.0.0+dfsg-6
has caused the Debian Bug report #1066681,
regarding scilab: FTBFS: sci_gateway/c/sci_getURL.c:43:5: error: implicit
declaration of function ‘Sciwarning’
Hi Helmut,
On 2024-04-08 22:19, Helmut Grohne wrote:
> Control: tags -1 + patch
>
> Hi Aurelien and Canonical folks,
>
> On Tue, Apr 02, 2024 at 08:53:31PM +0200, Aurelien Jarno wrote:
> > Starting with gcc-12 version 12.3.0-15, -D_TIME_BITS=64 together with
> > -D_FILE_OFFSET_BITS=64 are
Your message dated Mon, 08 Apr 2024 21:19:08 +
with message-id
and subject line Bug#1068513: fixed in dablin 1.16.0-1
has caused the Debian Bug report #1068513,
regarding dablin: FTBFS on arm{el,hf}: manually disables mpg123's large file API
to be marked as done.
This means that you claim
Source: haskell-fold-debounce
Version: 0.2.0.11-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=haskell-fold-debounce=armel=0.2.0.11-1%2Bb2=1712466208=0
Source: cfengine3
Version: 3.21.4-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=cfengine3=armel=3.21.4-1=1712477798=0
Source: haskell-filestore
Version: 0.6.5-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
Running 1 test suites...
Test suite test-filestore: RUNNING...
Cases: 21 Tried: 0 Errors: 0 Failures: 0
Source: zzuf
Version: 0.15-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=zzuf=armhf=0.15-3=1712473020=0
In file included from
Your message dated Mon, 08 Apr 2024 20:34:58 +
with message-id
and subject line Bug#1064724: fixed in yapet 2.6-2
has caused the Debian Bug report #1064724,
regarding yapet: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8
--verbose" VERBOSE=1 returned exit code 2
to be marked
Your message dated Mon, 08 Apr 2024 20:34:58 +
with message-id
and subject line Bug#1064724: fixed in yapet 2.6-2
has caused the Debian Bug report #1064724,
regarding libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB
to be marked as done.
This means that you claim that the problem has
Control: tags -1 + patch
Hi Aurelien and Canonical folks,
On Tue, Apr 02, 2024 at 08:53:31PM +0200, Aurelien Jarno wrote:
> Starting with gcc-12 version 12.3.0-15, -D_TIME_BITS=64 together with
> -D_FILE_OFFSET_BITS=64 are passed by default on 32-bit architectures
> except i386.
>
> This has
Processing control commands:
> tags -1 + patch
Bug #1068251 [src:glibc] glibc: FTBFS on 32-bit architectures due to GCC
defaulting to 64-bit time_t
Added tag(s) patch.
--
1068251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068251
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> tag -1 pending
Bug #1064724 [src:yapet] yapet: FTBFS: dh_auto_test: error: make -j8 check
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Bug #1068045 [src:yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB
Added tag(s) pending.
Added
Control: tag -1 pending
Hello,
Bug #1064724 in yapet 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:
Processing commands for cont...@bugs.debian.org:
> forwarded 1067560 https://github.com/linuxdeepin/developer-center/issues/7771
Bug #1067560 [src:deepin-log-viewer] FTBFS on 32-bit time64 architectures:
cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}
Set Bug
Source: pkcs11-provider
Version: 0.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=pkcs11-provider=ppc64el=0.3-1%2Bb2=1712517987=0
...
FAIL: basic-softhsm
===
Executing ./tbasic
## Raw Sign check error
openssl
pkeyutl -sign -inkey "${BASEURI}"
Source: pgsql-http
Version: 1.6.0-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian PostgreSQL Maintainers
https://buildd.debian.org/status/fetch.php?pkg=pgsql-http=arm64=1.6.0-1=1712600451=0
...
regression.diffs
diff -U3 /<>/expected/http.out /<>/results/http.out
---
Source: lomiri-telephony-service
Version: 0.5.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=lomiri-telephony-service=amd64=0.5.3-1%2Bb3=1712518065=0
...
/<>/libtelephonyservice/contactwatcher.cpp: In member function
‘void ContactWatcher::updateAlias()’:
Your message dated Mon, 08 Apr 2024 18:04:42 +
with message-id
and subject line Bug#1068589: fixed in gem2deb 2.2.3
has caused the Debian Bug report #1068589,
regarding gem2deb: autopkgtest needs update for new version of ruby3.1: "libc6
(>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)",
Processing control commands:
> tag -1 pending
Bug #1068589 [src:gem2deb] gem2deb: autopkgtest needs update for new version of
ruby3.1: "libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby |
ruby-interpreter\n"] expected to include 'ruby (>= something)'
Added tag(s) pending.
--
Control: tag -1 pending
Hello,
Bug #1068589 in gem2deb 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:
Processing control commands:
> tags -1 + patch
Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest
regression with NumPy 1.26
Bug #1067294 [src:python-pomegranate] python-pomegranate: FTBFS: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11"
Control: tags -1 + patch
Hi Maintainer
The attached patch fixes the test failures for me.
I noticed in this package's changelog that its only purpose is to work
with cnvkit. I have not tested whether cnvkit still functions with
this patch in place.
Regards
Graham
Description: Only compare
Your message dated Mon, 08 Apr 2024 17:19:41 +
with message-id
and subject line Bug#1068644: fixed in gnutls28 3.8.5-2
has caused the Debian Bug report #1068644,
regarding gnutls-bin: "Fatal error: The encryption algorithm is not supported"
appeared with 3.8.5 upgrade
to be marked as done.
Your message dated Mon, 8 Apr 2024 19:18:28 +0200
with message-id <0b7fe4e3-592c-abb3-6a02-0c6dd4100...@debian.org>
and subject line python3.10 has been removed from Debian
has caused the Debian Bug report #1031969,
regarding python3.10-venv: python3-venv no longer installable since
Hi Sebastian,
On Mon, Apr 08, 2024 at 06:43:01PM +0200, Sebastian Andrzej Siewior wrote:
> control: tags -1 patch
> control: reassign -1 yapet 2.6-1
>
> On 2024-04-08 08:32:58 [+0200], Kurt Roeckx wrote:
> > There might be a related change that doesn't allow restarting the
> > operation with the
Processing commands for cont...@bugs.debian.org:
> reassign 1068045 src:yapet
Bug #1068045 [yapet] libssl3,yapet: YAPET cannot decrypt YAPET1.0-format DB
Bug reassigned from package 'yapet' to 'src:yapet'.
No longer marked as found in versions yapet/2.6-1.
Ignoring request to alter fixed versions
Processing control commands:
> tags -1 + patch
Bug #1067234 [src:symfit] symfit: autopkgtest regression with NumPy 1.26
Bug #1067282 [src:symfit] symfit: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) patch.
Added
Control: tags -1 + patch
Hi Maintainer
While asserting that no warnings are raised is a useful test for the
upstream developers, I don't think it makes sense for downstreams.
I propose to disable the assertion as follows:
--- a/tests/test_minimizers.py
+++ b/tests/test_minimizers.py
@@ -117,7
Processing commands for cont...@bugs.debian.org:
> merge 1067234 1067282
Bug #1067234 [src:symfit] symfit: autopkgtest regression with NumPy 1.26
Bug #1067234 [src:symfit] symfit: autopkgtest regression with NumPy 1.26
Added tag(s) trixie, ftbfs, and sid.
Bug #1067282 [src:symfit] symfit: FTBFS:
control: tags -1 patch
control: reassign -1 yapet 2.6-1
On 2024-04-08 08:32:58 [+0200], Kurt Roeckx wrote:
> There might be a related change that doesn't allow restarting the
> operation with the same context without setting things up again.
Yapet is broken and the openssl update revealed the
Processing control commands:
> tags -1 patch
Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt
YAPET1.0-format DB
Added tag(s) patch.
> reassign -1 yapet 2.6-1
Bug #1068045 [libssl3,yapet] libssl3,yapet: YAPET cannot decrypt
YAPET1.0-format DB
Bug reassigned from package
Processing control commands:
> severity -1 serious
Bug #1068644 [gnutls-bin] gnutls-bin: "Fatal error: The encryption algorithm is
not supported" appeared with 3.8.5 upgrade
Severity set to 'serious' from 'normal'
> forwarded -1 https://gitlab.com/gnutls/gnutls/-/issues/1540
Bug #1068644
Package: evolution
Version: 3.50.3-1+b1
Severity: grave
I have two accounts (personal and work) and both of them are returning
“Timeout was reached”. I have tried removing the accounts and re-adding
them without success.
personal account is @gmail.com
work account is @EMPLOYER'S-DOMAIN
--
Your message dated Mon, 08 Apr 2024 16:21:32 +
with message-id
and subject line Bug#1065791: fixed in sleuthkit 4.12.1+dfsg-2
has caused the Debian Bug report #1065791,
regarding sleuthkit: FTBFS on arm{el,hf}: /usr/include/zlib.h:1840:5: error:
unknown type name ‘off64_t’
to be marked as
Processing control commands:
> tag -1 pending
Bug #1065791 [src:sleuthkit] sleuthkit: FTBFS on arm{el,hf}:
/usr/include/zlib.h:1840:5: error: unknown type name ‘off64_t’
Added tag(s) pending.
--
1065791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065791
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1065791 in sleuthkit 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:
[Cc Steve]
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 (armel, armhf and some
On Sun, Mar 24, 2024 at 03:42:18PM +0500, 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
Processing commands for cont...@bugs.debian.org:
> severity 1064996 important
Bug #1064996 {Done: Michael R. Crusoe }
[src:azure-uamqp-python] azure-uamqp-python: CVE-2024-27099
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need
Source: python-pot
Version: 0.9.3+dfsg-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
your package has a autopkgtest regression on i386 with NumPy 1.26.4.
Hopefully relevant excerpt from test log at
Source: pyorbital
Version: 1.8.2-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
the pyorbital package has an autopkgtest regression on i386 only with
NumPy 1.26.4. Hopefully relevant excerpt from test log at
Ok. I re-checked the patch and realized that I checked the only wrong
module (the only one which is arch all and not any).
So my apologies for the fuzz and will apply the patch with the
appropriate changes.
But here my original reply too:
I admit that I joined late to this conversation. But my
Your message dated Mon, 08 Apr 2024 11:05:00 +
with message-id
and subject line Bug#1068634: fixed in dialog 1.3-20240307-2
has caused the Debian Bug report #1068634,
regarding libdialog-dev has an undeclared file conflict on
/usr/lib/x86_64-linux-gnu/libdialog.a
to be marked as done.
This
Just for the record: I finally used this, in line with the original proposal:
Replaces: dialog (<< 1.3-20240307-1~)
Breaks: dialog (<< 1.3-20240307-1~)
Thanks.
Your message dated Mon, 08 Apr 2024 10:49:37 +
with message-id
and subject line Bug#1066657: fixed in daemonize 1.7.8-4
has caused the Debian Bug report #1066657,
regarding daemonize: FTBFS: daemonize.c:118:12: error: implicit declaration of
function ‘basename’; did you mean ‘rename’?
Your message dated Mon, 08 Apr 2024 10:35:31 +
with message-id
and subject line Bug#1068089: fixed in ukui-control-center 3.22.1.26-1
has caused the Debian Bug report #1068089,
regarding FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka
‘const long long int*’}
to be marked as
Your message dated Mon, 08 Apr 2024 10:35:04 +
with message-id
and subject line Bug#1067067: fixed in ruby-rdiscount 2.1.8-3
has caused the Debian Bug report #1067067,
regarding ruby-rdiscount: FTBFS: rdiscount.c:50:17: error: implicit declaration
of function ‘rb_rdiscount__get_flags’
Control: severity -1 wishlist
On Mon, Apr 08, 2024 at 11:50:04AM +0200, Vincent Lefevre wrote:
> Package: apt
> Version: 2.7.14
> Severity: serious
>
> The lvm2 package is installed, but not thin-provisioning-tools,
> though lvm2 recommends it. This can yield a broken system:
>
>
Processing control commands:
> severity -1 wishlist
Bug #1068637 [apt] apt does not always install Recommends
Severity set to 'wishlist' from 'serious'
--
1068637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Ok. This is a little bit subtle.
I naively tried to simplify the fields by using this:
Replaces: dialog (<< 1.3-20240307)
Breaks: dialog (<< 1.3-20240307)
But this actually means upstream version 1.3, debian revision 20240307,
not upstream 1.3-20240307.
I guess I should use 1.3-20240307-0 at
Control: tag -1 pending
Hello,
Bug #1067067 in ruby-rdiscount 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:
Processing control commands:
> tag -1 pending
Bug #1067067 [src:ruby-rdiscount] ruby-rdiscount: FTBFS: rdiscount.c:50:17:
error: implicit declaration of function ‘rb_rdiscount__get_flags’
[-Werror=implicit-function-declaration]
Added tag(s) pending.
--
1067067:
Your message dated Mon, 08 Apr 2024 09:50:14 +
with message-id
and subject line Bug#1059839: fixed in cython-legacy 0.29.37-2
has caused the Debian Bug report #1059839,
regarding cython-legacy: autopkgtest regression with Python 3.12 on 32-bit
to be marked as done.
This means that you claim
El 8/4/24 a las 9:18, Helmut Grohne escribió:
Package: libdialog-dev
Version: 1.3-20240307-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + dialog
libdialog-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.
The
Package: apt
Version: 2.7.14
Severity: serious
The lvm2 package is installed, but not thin-provisioning-tools,
though lvm2 recommends it. This can yield a broken system:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857142
the fix of this bug being
* Make lvm2 recommend
Processing control commands:
> tags -1 + patch
Bug #1068610 [src:dico] dico: binary-all FTBFS
Added tag(s) patch.
--
1068610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
Hi Adrian,
On Mon, Apr 08, 2024 at 02:03:01AM +0300, Adrian Bunk wrote:
> Source: dico
> Version: 2.11-4
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: Helmut Grohne
Thank you for notifying me. Mea culpa. Patch attached.
>
Package: libdialog-dev
Version: 1.3-20240307-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + dialog
libdialog-dev has an undeclared file conflict. This may result in an
unpack error from dpkg.
The file /usr/lib/x86_64-linux-gnu/libdialog.a is
Processing control commands:
> affects -1 + dialog
Bug #1068634 [libdialog-dev] libdialog-dev has an undeclared file conflict on
/usr/lib/x86_64-linux-gnu/libdialog.a
Added indication that 1068634 affects dialog
--
1068634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068634
Debian Bug
There might be a related change that doesn't allow restarting the operation
with the same context without setting things up again.
Your message dated Mon, 08 Apr 2024 11:05:36 +0200
with message-id
and subject line bitsnpicas: Contains potentially non-free binary unicode data
has caused the Debian Bug report #1041435,
regarding bitsnpicas: Contains potentially non-free binary unicode data
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> tags 1066628 - trixie
Bug #1066628 {Done: tony mancill } [src:tlf] tlf: FTBFS:
test_wwv.c:26:5: error: implicit declaration of function ‘g_strchomp’; did you
mean ‘strcmp’? [-Werror=implicit-function-declaration]
Removed tag(s) trixie.
> thanks
Pyparsing upstream finally made the v3.1.2 release the other day with the
fix. So I guess once that lands in unstable it should be ok.
On Sat, Apr 6, 2024 at 12:30 AM Antoine Beaupré wrote:
> On 2023-07-27 13:04:22, Riccardo Coccioli wrote:
> > I've checked the issue and opened a bug upstream
Processing commands for cont...@bugs.debian.org:
> severity 1066501 important
Bug #1066501 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:pd-wiimote] pd-wiimote: FTBFS: wiimote.c:736:7: error: implicit
declaration of function ‘error’; did you mean ‘perror’?
On Mon, Apr 08, 2024 at 12:58:13AM +, tony mancill wrote:
> This may be a naive question, but since we're dealing with a syscall
> that passes a timespec, is there a minimum kernel version required for
> the time_t 64 userspace?
I've never heard anything about this.
> In any event, I'm not
Processing commands for cont...@bugs.debian.org:
> close 1063982
Bug #1063982 [setuptools-scm] setuptools-scm: autopkgtest regression with
pytest 8
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1063982:
Your message dated Mon, 08 Apr 2024 07:06:40 +
with message-id
and subject line Bug#1068449: fixed in opentracker 0.0~git20210823.110868e-9
has caused the Debian Bug report #1068449,
regarding opentracker: libowfat headers have moved
to be marked as done.
This means that you claim that the
Your message dated Mon, 08 Apr 2024 07:05:55 +
with message-id
and subject line Bug#1068613: fixed in lomiri-history-service 0.5-2
has caused the Debian Bug report #1068613,
regarding lomiri-history-service FTBFS with abseil 20230802.1
to be marked as done.
This means that you claim that the
Your message dated Mon, 08 Apr 2024 06:53:02 +
with message-id
and subject line Bug#1068430: fixed in qt5-ukui-platformtheme 1.0.8-2
has caused the Debian Bug report #1068430,
regarding libqt5-ukui-style1 dependencies unsatisfiable on 32-bit non-i386
architectures.
to be marked as done.
Control: tag -1 pending
Hello,
Bug #1068613 in lomiri-history-service 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:
Processing control commands:
> tag -1 pending
Bug #1068613 [src:lomiri-history-service] lomiri-history-service FTBFS with
abseil 20230802.1
Added tag(s) pending.
--
1068613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Your message dated Mon, 08 Apr 2024 06:23:28 +
with message-id
and subject line Bug#1068599: fixed in xapian-bindings 1.4.22-2
has caused the Debian Bug report #1068599,
regarding ruby-xapian - still depends on old libruby3.1 after binnmu
to be marked as done.
This means that you claim that
* Andrey Rakhmatullin [2024-04-07 17:13]:
This works in a current sid chroot, both build-time tests and autopkgests.
Timo, do you think we can close this or does something else need to be
checked?
pytest 8.1 fixed a few regressions, so it is likely that either that
or another fix in a
83 matches
Mail list logo
