On 4 April 2024 02:52:29 CEST, David Landry wrote:
>Good evening,
>
>The bug involving compiling/installing nvidia-kernel-dkms is still present.
>The result of the bug is that following a reboot after the erroneous
>installation noted below, my display drivers get completely disabled,
Processing control commands:
> severity -1 important
Bug #1067755 [src:ifuse] ifuse ftbfs from source, not finding the libplist
configuration
Severity set to 'important' from 'serious'
--
1067755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067755
Debian Bug Tracking System
Contact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
On Tue, 2024-03-26 at 12:25 +0100, Matthias Klose wrote:
> Package: src:ifuse
> Version: 1.1.4~git20181007.3b00243-1
> Severity: serious
> Tags: sid trixie ftbfs patch
>
> ifuse ftbfs from source, not finding the
Your message dated Thu, 04 Apr 2024 20:49:22 +
with message-id
and subject line Bug#1066352: fixed in tla 1.3.5+dfsg1-3
has caused the Debian Bug report #1066352,
regarding tla: FTBFS: cmd-apply-delta.c:307:3: error: implicit declaration of
function ‘arch_merge3’; did you mean
Processing commands for cont...@bugs.debian.org:
> block 1052746 with 1050390
Bug #1052746 [src:loadlin] loadlin: FTBFS: cc1: error: ‘-fcf-protection’ is not
compatible with this target
1052746 was not blocked by any bugs.
1052746 was not blocking any bugs.
Added blocking bug(s) of 1052746:
On 04/04/24 21:36, Salvatore Bonaccorso wrote:
> Source: nghttp2
> Version: 1.60.0-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team
>
>
> Hi,
>
> The following vulnerability was published for nghttp2.
>
>
Your message dated Fri, 05 Apr 2024 02:36:37 +
with message-id
and subject line Bug#1066511: fixed in photopc 3.07-3
has caused the Debian Bug report #1066511,
regarding photopc: FTBFS: fnames.c:118:21: error: implicit declaration of
function ‘strlen’ [-Werror=implicit-function-declaration]
Your message dated Fri, 05 Apr 2024 02:34:31 +
with message-id
and subject line Bug#1066387: fixed in gkermit 2.01-4
has caused the Debian Bug report #1066387,
regarding gkermit: FTBFS: gkermit.c:350:7: error: implicit declaration of
function ‘sleep’ [-Werror=implicit-function-declaration]
Package: reapr
Version: 1.0.18+dfsg-5
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, reapr
depends on both libtabixpp0 and libtabixpp0t64. As a
result it is uninstallable on architectures that are undergoing
the
Package: riseup-vpn
Version: 0.21.11+ds1-5
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, riseup-vpn
depends on both libqt5widgets5 and libqt5widgets5t64. As a
result it is uninstallable on architectures that are
Processing commands for cont...@bugs.debian.org:
> # OpenSSL 3.2 has been uploaded to unstable, raise the severity
> severity 1061458 serious
Bug #1061458 [src:gdm3] gdm3: Testsuite breaks with openssl 3.2
Severity set to 'serious' from 'important'
> severity 1061869 serious
Bug #1061869
On Do 04 Apr 2024 17:53:07 CEST, Peter Green wrote:
Package: lomiri-system-settings
Version: 1.1.0-2
Severity: grave
lomiri-system-settings depends on
lomiri-system-settings-security-privacy, which
is not availble on armel, armhf or mips64el.
The reason, or at least one reason, it is not
Your message dated Fri, 05 Apr 2024 00:49:31 +
with message-id
and subject line Bug#1066241: fixed in epm 4.2-12
has caused the Debian Bug report #1066241,
regarding epm: FTBFS: mantohtml.c:230:27: error: implicit declaration of
function ‘tolower’ [-Werror=implicit-function-declaration]
to
Your message dated Thu, 04 Apr 2024 22:47:12 +
with message-id
and subject line Bug#1066108: fixed in intel-microcode 3.20240312.1~deb12u1
has caused the Debian Bug report #1066108,
regarding intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575
CVE-2023-22655 CVE-2023-28746
to be
Your message dated Thu, 04 Apr 2024 22:47:08 +
with message-id
and subject line Bug#1060407: fixed in gtkwave 3.3.118-0.1~deb12u1
has caused the Debian Bug report #1060407,
regarding Multiple security issues
to be marked as done.
This means that you claim that the problem has been dealt
Package: pyode
Version: 1.2.0.dev15-4
Severity: grave
Tags: patch
Justification: renders package unusable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org
Dear Maintainer,
the python3-pyode package is empty, because it silently fails
Your message dated Fri, 05 Apr 2024 01:05:59 +
with message-id
and subject line Bug#1068420: fixed in pidgin-gnome-keyring 2.0-3
has caused the Debian Bug report #1068420,
regarding pidgin-gnome-keyring - still depends on old libpurple after binnmu
to be marked as done.
This means that you
Galera patch releases have been accepted as stable updates before. That is
also what users expect.
Thanks for reminding about this though, I yad forgotten about it. Will do
it next weekend.
Package: libqt5-ukui-style1
Version: 1.0.8-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, libqt5-ukui-style1
depends on both libqt5widgets5 and libqt5widgets5. As a
result it is uninstallable on architectures
Your message dated Fri, 05 Apr 2024 01:35:07 +
with message-id
and subject line Bug#1066614: fixed in splitvt 1.6.6-16
has caused the Debian Bug report #1066614,
regarding splitvt: FTBFS: vt100.c:146:16: error: implicit declaration of
function ‘check_attr’; did you mean ‘set_attr’?
Processing commands for cont...@bugs.debian.org:
> fixed 1068415 1.61.0-1
Bug #1068415 [src:nghttp2] nghttp2: CVE-2024-28182: Reading unbounded number of
HTTP/2 CONTINUATION frames to cause excessive CPU usage
Marked as fixed in versions nghttp2/1.61.0-1.
> thanks
Stopping processing here.
Control: retitle -1 src:r-cran-rstanarm: FTBFS on mips64el and risc64
Control: reopen -1
Control: tags -1 upstream
Control: forwarded -1 https://github.com/stan-dev/rstanarm/issues/619
thanks
As per autobuilders log[1] the package fails to build on mips64el and risc64
with
...
g++ -std=gnu++17
Processing control commands:
> retitle -1 src:r-cran-rstanarm: FTBFS on mips64el and risc64
Bug #1065339 {Done: Paul Gevers } [src:r-cran-rstanarm]
src:r-cran-rstanarm: fails to migrate to testing for too long: FTBFS on mips64el
Changed Bug title to 'src:r-cran-rstanarm: FTBFS on mips64el and
El 23/12/23 a las 3:07, Otto Kekäläinen escribió:
Sure, this will be fixed (automatically) with uploading latest upstream minor
release as stable update, and I intend to do it in coming 1-2 weeks.
Hi. Can you elaborate on that? Release managers do not usually allow
new upstream releases in
Hi Cris,
Would be possible reintroduce libnss-db to testing?
I'm asking because I'm maintainer of the pglistener package and I know
there aren't plans to update the sofwtare with another database solution.
And now I can't have pglistener on testing.
Best regards,
On Sat, 09 Dec 2023
Your message dated Thu, 04 Apr 2024 23:05:52 +
with message-id
and subject line Bug#1066866: fixed in railway-gtk 2.4.0-2
has caused the Debian Bug report #1066866,
regarding railway-gtk: FTBFS on i386 "type annotations needed"
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 04 Apr 2024 23:04:55 +
with message-id
and subject line Bug#1067561: fixed in lightdm 1.32.0-5~exp1
has caused the Debian Bug report #1067561,
regarding FTBFS: Error: symbol `open64' is already defined
to be marked as done.
This means that you claim that the problem
On Wed 2024-04-03 13:03:19 +0800, Sean Whitton wrote:
> Thanks, but can you sign this off? Ty!
Sure, attached. Let me know if you need anything different.
--dkg
From b522c1cc6201f75ab6103954016bbb719d4dd2fa Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor
Date: Tue, 30 Jan 2024
Your message dated Thu, 04 Apr 2024 20:35:09 +
with message-id
and subject line Bug#1042967: fixed in nheko 0.11.3+~0.9.2+~1.0.0+~0.3.0-2
has caused the Debian Bug report #1042967,
regarding nheko crashes on first launch in arm64 (librem 5)
to be marked as done.
This means that you claim
Hi Andreas,
after routine-update dh_missing failed due to compat level 13 which
defaults to fail if some files are not installed.
Yep, encountered that in other places as well when updating a few (old!)
things.
This made me aware that upstream in principle installs a test suite
we could use
Processing commands for cont...@bugs.debian.org:
> tags 1052746 - pending
Bug #1052746 [src:loadlin] loadlin: FTBFS: cc1: error: ‘-fcf-protection’ is not
compatible with this target
Removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052746:
Your message dated Thu, 04 Apr 2024 21:34:51 +
with message-id
and subject line Bug#1068399: fixed in lomiri-system-settings-security-privacy
1.0.2-3
has caused the Debian Bug report #1068399,
regarding lomiri-system-settings - uninstallable on armel, armhf and mips64el
due to
Your message dated Thu, 04 Apr 2024 21:34:42 +
with message-id
and subject line Bug#1068400: fixed in lomiri-filemanager-app 1.0.4+dfsg-2
has caused the Debian Bug report #1068400,
regarding lomiri-filemanager-app dependencies unsatisfiable on 32-bit non-i386
architectures.
to be marked as
Unfortunately, this applies to unstable now too, and did apply to
trixie until it resulted in autoremoval of the package. Would it
help if I were to backport the fix from upstream? Or is the plan to
just wait? (I can always build my own local package from upstream
source, but this doesn't really
Your message dated Thu, 04 Apr 2024 22:06:11 +
with message-id
and subject line Bug#1066521: fixed in weplab 0.1.5-7
has caused the Debian Bug report #1066521,
regarding weplab: FTBFS: analpfile.c:105:21: error: implicit declaration of
function ‘GetPacketBssid’
Control: tags -1 + patch
On 04.04.2024 21:57, Peter Green wrote:
Hi,
After being rebuilt for the time64 transition, perdition
depends on both libvanessa-socket2 and libvanessa-socket2.
As a result it is uninstallable.
Interesting in this case, the uninstallability seems to apply to all
Processing control commands:
> tags -1 + patch
Bug #1068419 [perdition] perdition: dependencies unsatisfiable after binnmu for
time64 transition.
Added tag(s) patch.
--
1068419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068419
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Your message dated Fri, 05 Apr 2024 04:34:40 +
with message-id
and subject line Bug#1067352: fixed in mtail 3.0.0~rc54+git0ff5-1
has caused the Debian Bug report #1067352,
regarding mtail: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_build]
Error 25
to be marked as done.
This
Processing control commands:
> tag -1 pending
Bug #1068400 [lomiri-filemanager-app] lomiri-filemanager-app dependencies
unsatisfiable on 32-bit non-i386 architectures.
Added tag(s) pending.
--
1068400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068400
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1068400 in lomiri-filemanager-app 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:
> reassign -1 lomiri-system-settings-security-privacy
Bug #1068399 [lomiri-system-settings] lomiri-system-settings - uninstallable on
armel, armhf and mips64el due to depends/build-depends cycles.
Bug reassigned from package 'lomiri-system-settings' to
Package: python3-dask
Version: 2023.12.1+dfsg-2
Severity: serious
Control: affects -1 src:pandas
Control: block 1068104 by -1
Importing dask.dataframe currently fails with the error
TypeError: descriptor '__call__' for 'type' objects doesn't apply to a
'property' object
amd64
Processing control commands:
> affects -1 src:pandas
Bug #1068422 [python3-dask] can't import dask.dataframe - TypeError: descriptor
'__call__' for 'type' objects doesn't apply to a 'property' object
Added indication that 1068422 affects src:pandas
> block 1068104 by -1
Bug #1068104 [src:pandas]
Control: reassign -1 lomiri-system-settings-security-privacy
Control: found -1 1.0.2-2
On Do 04 Apr 2024 17:53:07 CEST, Peter Green wrote:
Package: lomiri-system-settings
Version: 1.1.0-2
Severity: grave
lomiri-system-settings depends on
lomiri-system-settings-security-privacy, which
is
Package: populations
Version: 1.2.33+svn0120106+dfsg-6
Severity: grave
Tags: trixie, sid
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition,
populations still depends on libqt5xml5,
rather than libqt5xml5t64. As a result it is uninstallable on
Your message dated Thu, 04 Apr 2024 23:51:05 +
with message-id
and subject line Bug#1066343: fixed in wily 0.13.42-2
has caused the Debian Bug report #1066343,
regarding wily: FTBFS: getrect.c:27:17: error: implicit declaration of function
‘sleep’ [-Werror=implicit-function-declaration]
to
Package: rakarrack
Version: 0.6.1-8
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, rakarrack
depends on both libasound2 and libasound2t64. As a
result it is uninstallable on architectures that are undergoing
the
Your message dated Fri, 05 Apr 2024 05:19:03 +
with message-id
and subject line Bug#1067572: fixed in rust-parsec-tool 0.7.0-4
has caused the Debian Bug report #1067572,
regarding rust-parsec-tool: Testsuite fails with openssl 3.2
to be marked as done.
This means that you claim that the
Hi Sascha,
Am Thu, Apr 04, 2024 at 10:33:16PM +0200 schrieb Sascha Steinbiss:
> Interesting to see that there is no ltrsift-examples package indeed. But
> I must have had my reasons back then...
>
> Anyway, to be honest I don't see much long-term future for LTRsift. I am
> actually surprised to
Package: gir1.2-keybinder-0.0
Version: 0.3.1-2.3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
libkeybinder0 has been renamed to libkeybinder0t64, however gir1.2keybinder0.0
still depends on the former on most architectures. As a result it is
uninstallable on architectures
user release.debian.org
usertag 1064533 time-t-downgrade
severity 1064533 important
Hi
On 04-04-2024 4:25 a.m., handsome_feng wrote:
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
The excuses shows
Package: gpa
Version: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, gpa depends
on both libgpgme11 and libgpg11t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf
Your message dated Thu, 04 Apr 2024 08:35:35 +
with message-id
and subject line Bug#1066910: fixed in chromium 123.0.6312.105-1~deb13u1
has caused the Debian Bug report #1066910,
regarding chromium: downloads non-free component libchromescreenai.so without
asking
to be marked as done.
This
Your message dated Thu, 04 Apr 2024 08:38:11 +
with message-id
and subject line Bug#1068211: fixed in pmix 5.0.2-2
has caused the Debian Bug report #1068211,
regarding pmix: FTBFS on 32 bit architectures: configure: WARNING: PMIx does
not support 32 bit builds.
to be marked as done.
This
On Sat, Feb 24, 2024 at 09:59:48AM +0100, Sebastian Ramacher wrote:
> Source: faketime
> Version: 0.9.10-2.1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>
>
Source: autopkgtest
Version: 5.33
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it recently started to fail a lot on ppc64el. The failures seem
related to the host that runs the
Package: indi-apogee
Version: 0.10.0-5
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t
After being rebuilt for the time64 transition, indi-apogee depends
on both libapogee3 and libapogee3t64. As a
result it is uninstallable on architectures that are undergoing
the time64
Processing control commands:
> tags -1 patch
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml
5.2: lxml.html.clean
Added tag(s) patch.
> severity -1 serious
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml
5.2: lxml.html.clean
Processing commands for cont...@bugs.debian.org:
> user release.debian.org
Selected user id (release.debian.org) invalid, sorry
> usertag 1064533 time-t-downgrade
No valid user selected
> severity 1064533 important
Bug #1064533 {Done: Paul Gevers } [src:peony] src:peony:
fails to migrate to
Control: tag -1 pending
Hello,
Bug #1068075 in tanglet 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 #1068075 [src:tanglet] Update Build-Depends for the time64 library renames
Added tag(s) pending.
--
1068075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1068075 in tanglet 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 #1068075 [src:tanglet] Update Build-Depends for the time64 library renames
Ignoring request to alter tags of bug #1068075 to the same tags previously set
--
1068075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068075
Debian Bug Tracking
On Wed, Mar 01, 2023 at 08:30:12AM +0100, Jakub Wilk wrote:
> Package: faketime
> Version: 0.9.10-2.1
> Severity: grave
>
> faketime no longer works on i386:
>
>$ faketime -f '2008-12-24 08:15:42' date -R
>Wed, 01 Mar 2023 08:25:58 +0100
The reason here is that date uses
Processing commands for cont...@bugs.debian.org:
> found 1068349 5.2.1-1
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml
5.2: lxml.html.clean
There is no source info for the package 'python3-nbconvert' at version
'5.2.1-1' with architecture ''
Marked as found in
Source: coda
Version: 2.25.2-1
Severity: serious
Tags: upstream ftbfs patch
Justification: makes the package in question unusable or mostly so
User: debian-...@lists.debian.org
Usertags: hdf-4.3
Dear Maintainer,
Your package FTBFS while performing test rebuilds with HDF 4.3.20.
The attached
Your message dated Thu, 04 Apr 2024 09:06:27 +
with message-id
and subject line Bug#1067292: fixed in prometheus-sql-exporter 0.4.5-2
has caused the Debian Bug report #1067292,
regarding prometheus-sql-exporter: FTBFS: make: *** [debian/rules:4: build]
Error 25
to be marked as done.
This
On 29/03/2024 00:06, Adrian Bunk wrote:
Hi,
attached are proposed debdiffs for updating gtkwave to 3.3.118 in
{bookworm,bullseye,buster}-security for review for a DSA
(and as preview for buster).
General notes:
As suggested by the security team in #1060407, this is a backport of a
new
Your message dated Thu, 04 Apr 2024 09:21:55 +
with message-id
and subject line Bug#1068075: fixed in tanglet 1.6.5-2
has caused the Debian Bug report #1068075,
regarding Update Build-Depends for the time64 library renames
to be marked as done.
This means that you claim that the problem has
Source: python-hdf4
Version: 0.11.4-1
Severity: serious
Tags: upstream ftbfs
Justification: makes the package in question unusable or mostly so
User: debian-...@lists.debian.org
Usertags: hdf-4.3
Dear Maintainer,
Your package FTBFS while performing test rebuilds with HDF 4.3.20.
Your message dated Thu, 04 Apr 2024 11:49:47 +
with message-id
and subject line Bug#1068090: fixed in tetzle 2.2.3-1.1
has caused the Debian Bug report #1068090,
regarding Update Build-Depends for the time64 library renames
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> forwarded 1068384 https://github.com/fhs/pyhdf/issues/70
Bug #1068384 [src:python-hdf4] python-hdf4: FTBFS with HDF 4.3.0.
Set Bug forwarded-to-address to 'https://github.com/fhs/pyhdf/issues/70'.
> thanks
Stopping processing here.
Please
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Control: severity -1 important
Hi,
On Sat, 30 Mar 2024 14:48:24 +0900 Kentaro HAYASHI wrote:
tilix fails to build on armhf, s390x.
But on armhf, there currently are no binaries in any suite and on s390x
it never build. So, this is no regression and hence not serious (this
bug is blocking
Processing control commands:
> severity -1 important
Bug #1068051 [src:tilix] tilix: FTBFS on armhf, s390x (undefined reference to
`_D4core8internal5array8equality...)
Severity set to 'important' from 'serious'
--
1068051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068051
Debian Bug
Source: pcp
Version: 6.2.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from
Source: translate-toolkit
Version: 3.12.2-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Source: ruby-graphlient
Version: 0.7.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Source: pytest-testinfra
Version: 10.1.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Your message dated Thu, 04 Apr 2024 12:34:41 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.19.0-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that
Source: ruby-asana
Version: 0.10.13-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
On Thu, Apr 04, 2024 at 11:21:21AM +0200, Emilio Pozuelo Monfort wrote:
> On 29/03/2024 00:06, Adrian Bunk wrote:
>...
> > As already mentioned in #1060407, the ghwdump tool (and manpage) was
> > dropped in 3.3.110 from the upstream sources, and is now in ghdl-tools.
> > For bullseye and buster it
Source: harp
Version: 1.21-1
Severity: serious
Tags: upstream ftbfs patch
Justification: makes the package in question unusable or mostly so
User: debian-...@lists.debian.org
Usertags: hdf-4.3
Dear Maintainer,
Your package FTBFS while performing test rebuilds with HDF 4.3.20.
The attached patch
Your message dated Thu, 04 Apr 2024 11:57:43 +
with message-id
and subject line Bug#1067633: Removed package(s) from unstable
has caused the Debian Bug report #1067331,
regarding hdmi2usb-fx2-firmware: FTBFS: sdcpp: fatal error: cannot execute
'cc1': execvp: No such file or directory
to be
On Mon, 25 Mar 2024 00:34:21 +0500 Andrey Rakhmatullin
wrote:
> Source: xpra
> Version: 3.1.5+dfsg1-0.2
> Severity: serious
> Tags: ftbfs
>
>
https://buildd.debian.org/status/fetch.php?pkg=xpra=i386=3.1.5%2Bdfsg1-0.2%2Bb3=1710056306=0
>
> xpra/x11/bindings/keyboard_bindings.c: In function
Your message dated Thu, 04 Apr 2024 16:19:02 +
with message-id
and subject line Bug#1066330: fixed in bluemon 1.4-9
has caused the Debian Bug report #1066330,
regarding bluemon: FTBFS: bluemon-query.c:46:15: error: implicit declaration of
function ‘strncmp’
1 - 100 of 151 matches
Mail list logo
