On Mon, 6 May 2024 at 17:00, Cyril Brulebois wrote:
> I'm adding Tianon to the loop explicitly since I'm definitely no Docker
> (or Go) expert, in case some time can be spared to look into this
> problem. Otherwise I'll try and come up with something.
I think the backport by Reinhard[1][2] is
Your message dated Tue, 07 May 2024 02:46:42 +
with message-id
and subject line Bug#1061358: fixed in gnumeric 1.12.57-1
has caused the Debian Bug report #1061358,
regarding gnumeric: identified for time_t transition but no ABI in shlibs
to be marked as done.
This means that you claim that
On 2024-05-07 03:57:44 +0200, Vincent Lefevre wrote:
> sshd_backend = systemd
BTW, that would fix the issue only for sshd. But what about the other
jails the user could have enabled in /etc/fail2ban/jail.local? The
user configuration may rely on systemd being the default backend, at
least the
On 2024-05-07 03:28:28 +0200, Vincent Lefevre wrote:
> May 07 03:01:28 qaa fail2ban-server[557228]: 2024-05-07 03:01:28,226 fail2ban
>[557228]: ERROR Failed during configuration: Have not found
> any log file for sshd jail
I suppose that this is because sshd no longer uses the
Package: fail2ban
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
After the upgrade to 1.1.0-1, "systemctl status" gives
× fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; preset:
enabled)
Active: failed
Processing commands for cont...@bugs.debian.org:
> found 1070652 17
Bug #1070652 [how-can-i-help] how-can-i-help: explicitly require 'ostruct'
Marked as found in versions how-can-i-help/17.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1070652:
On Sat, 10 Feb 2024 11:01:54 +0100 Petter Reinholdtsen wrote:
[Petter Reinholdtsen]
> I do not use ssr much myself, and have not had time to test.
I applied the upstream commit in git branch fix-1040375-glinject and
tested it on Bookworm, but alas, the .so file still segfaults with a
useless
Hi Santiago,
And thanks for the report.
Santiago Vila (2024-04-10):
> Package: src:docker.io
> Version: 20.10.25+dfsg1-2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> === FAIL: distribution/xfer
>
Processing commands for cont...@bugs.debian.org:
> retitle 1070652 how-can-i-help: explicitly require 'ostruct'
Bug #1070652 [how-can-i-help] ruby-json: breaks how-can-i-help
Changed Bug title to 'how-can-i-help: explicitly require 'ostruct'' from
'ruby-json: breaks how-can-i-help'.
> thanks
Processing commands for cont...@bugs.debian.org:
> reassign 1070652 how-can-i-help
Bug #1070652 [ruby-json] ruby-json: breaks how-can-i-help
Bug reassigned from package 'ruby-json' to 'how-can-i-help'.
No longer marked as found in versions ruby-json/2.7.2+dfsg-1.
Ignoring request to alter fixed
Your message dated Mon, 06 May 2024 23:40:21 +
with message-id
and subject line Bug#1070498: fixed in libvirt 10.3.0-2
has caused the Debian Bug report #1070498,
regarding libvirt attempts to write to $HOME during the build
to be marked as done.
This means that you claim that the problem has
On Thu, 18 Apr 2024 23:39:14 + IvanAbs wrote:
> On 2024-04-17 several of my servers running Debian 10 received an
> update for the tzdata package via Debian unattended-upgrade. However,
> this update resulted in corruption of files within the
> /usr/share/zoneinfo directory.
I, too,
Your message dated Mon, 06 May 2024 23:20:57 +
with message-id
and subject line Bug#1068665: fixed in cfengine3 3.21.4-1.1
has caused the Debian Bug report #1068665,
regarding cfengine3: FTBFS on arm{el,hf}: 1 of 60 tests failed
to be marked as done.
This means that you claim that the
Hi!
I am reassigning this bug to the `how-can-i-help` package. Indeed, the
script `/usr/bin/how-can-i-help` uses implicitly the OpenStruct class,
without requiring explicitly 'ostruct'. The class was loaded
transitively from the json gem it seems.
Adding below line 35 the following line:
Your message dated Mon, 06 May 2024 23:06:14 +
with message-id
and subject line Bug#997441: fixed in squirrel3 3.1-8.1
has caused the Debian Bug report #997441,
regarding squirrel3: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
to be marked as done.
This means that you claim that
Your message dated Mon, 06 May 2024 23:05:45 +
with message-id
and subject line Bug#1069793: fixed in reform-setup-wizard 1.0-1
has caused the Debian Bug report #1069793,
regarding wrong package name mnt-reform-setup-wizard -- should be
reform-setup-wizard
to be marked as done.
This means
Processing control commands:
> tag -1 pending
Bug #1070498 [src:libvirt] libvirt attempts to write to $HOME during the build
Added tag(s) pending.
--
1070498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1070498 in libvirt 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:
Well, it would certainly be simple enough: the source code should
compile fine, and the debian/* scripts would need only the very most
minor tweaks.
Your message dated Mon, 06 May 2024 22:49:46 +
with message-id
and subject line Bug#1063409: fixed in mpi4py 3.1.5-6
has caused the Debian Bug report #1063409,
regarding mpi4py accesses the net for the build
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 06 May 2024 22:49:46 +
with message-id
and subject line Bug#1066837: fixed in mpi4py 3.1.5-6
has caused the Debian Bug report #1066837,
regarding mpi4py: FTBFS: Unable to generate documentation
to be marked as done.
This means that you claim that the problem has been
On Thu, 18 Apr 2024 14:40:58 +0200 Matthias Geiger
wrote:
>
> //I have prepared a fix; however this needs the FTBFS in #997441
> adressed first.
>
> Will attach a debdiff once that has happened.
>
See attachement.
best,
--
Matthias Geiger
Debian Maintainer
diff -Nru
Control: tags -1 + patch
Description: explicitly declare returntype of main bootstrap sourcefile
dpkg version 1.22.6 makes -Werror=implicit-function-declaration
mandatory which breaks ATS2 build. this adds ats_int_type as return
type of functions that breaks the build. (keep in mind
Processing control commands:
> tags -1 + patch
Bug #1066211 [src:ats2-lang] ats2-lang: FTBFS:
prelude/ats_main_prelude_dats.c:72:1: error: implicit declaration of function
‘ATS_2d0_2e2_2e12_2prelude_2DATS_2basics_2edats__dynload’
[-Werror=implicit-function-declaration]
Added tag(s) patch.
--
Control: tag -1 pending
Hello,
Bug #1063409 in mpi4py 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 #1066837 [mpi4py] mpi4py: FTBFS: Unable to generate documentation
Added tag(s) pending.
--
1066837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1066837 in mpi4py 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 #1063409 [src:mpi4py] mpi4py accesses the net for the build
Added tag(s) pending.
--
1063409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity 1070441 important
Bug #1070441 [src:cbmc] cmbc: arm64 FTBFS with glibc 2.38
Severity set to 'important' from 'serious'
> block 1070668 by 1070441
Bug #1070668 [src:glibc] glibc: packages FTBFS caused by vector math library
header on arm64
1070668 was not
control: severity 1070441 important
control: block 1070668 by 1070441
control: severity 1070443 important
control: block 1070668 by 1070443
control: severity 1070444 important
control: block 1070668 by 1070444
control: severity 1070446 important
control: block 1070668 by 1070446
Dear
On Tue, 23 Apr 2024 17:12:54 +0300 jim_p wrote:
[...]
>
> Since there is no interest from the maintainers in fixing a 6+ month old grave
> bug, I want to ask. Has anyone moved away from lxpanel or even lxde?
[...]
Hello!
I am the original submitter of this bug report.
I have recently moved
Le lundi 29 avril 2024, 18:40:39 UTC Barak A. Pearlmutter a écrit :
> Bastien,
>
> Okay, got it. Thanks for letting me know.
>
> I can cherry-pick that fossil commit, but you know the right magic for
> a versioned apache2 breakage and how to deal with proposed-updates.
> So I think it would make
Your message dated Mon, 06 May 2024 20:15:54 +
with message-id
and subject line Bug#1070420: fixed in vagrant 2.3.7+git20230731.5fc64cde+dfsg-1
has caused the Debian Bug report #1070420,
regarding src:vagrant: unsatisfied build dependency in testing: ruby-net-ftp
(>= 0.2) | ruby-net-ftp (>=
Your message dated Mon, 06 May 2024 20:15:34 +
with message-id
and subject line Bug#1066213: fixed in slrn 1.0.3+dfsg-7
has caused the Debian Bug report #1066213,
regarding slrn: FTBFS: misc.c:376:4: error: implicit declaration of function
‘VA_COPY’ [-Werror=implicit-function-declaration]
to
Your message dated Mon, 06 May 2024 19:28:41 +
with message-id
and subject line Bug#1069009: fixed in dub 1.36.0-2
has caused the Debian Bug report #1069009,
regarding dub: hard-coded dependeny on pre-t64 libraries
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 06 May 2024 19:28:41 +
with message-id
and subject line Bug#1067825: fixed in dub 1.36.0-2
has caused the Debian Bug report #1067825,
regarding dub: FTBFS on armhf, mips64el, ppc64el
to be marked as done.
This means that you claim that the problem has been dealt with.
Control: tag -1 pending
Hello,
Bug #1070420 in vagrant 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 #1070420 [src:vagrant] src:vagrant: unsatisfied build dependency in
testing: ruby-net-ftp (>= 0.2) | ruby-net-ftp (>= 0.2)
Added tag(s) pending.
--
1070420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070420
Debian Bug Tracking System
Package: xautolock
Version: 1:2.2-8
Severity: critical
This may be related to #1022781 or not.
I have xautolock running:
% ps -fC xautolock
UID PIDPPID C STIME TTY TIME CMD
madduck 27332421 0 May05 ?00:00:53 xautolock -time 3 -locker
xsecurelock &&
Hi,
I've fixed the original error in Git but Salsa CI shows another one[1]
which is more tricky since it involves a header file for a perl module
and I have no idea how to fix this. Any help from the team is welcome.
Kind regards
Andreas.
[1]
Processing commands for cont...@bugs.debian.org:
> forwarded 1070644
> https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/260
Bug #1070644 [gnome-remote-desktop] gnome-remote-desktop: System .service file
enabled but not the user one?
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:newsboat
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package
> src:golang-github-lucas-clemente-quic-go
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:openttd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/260
It looks like upstream is proposing to split gnome-remote-desktop's
new systemd systemd service into two system services to fix this
issue. It's unclear whether they will land this in 46.x
Thank you,
Your message dated Mon, 06 May 2024 17:19:10 +
with message-id
and subject line Bug#1070444: fixed in cxref 1.6e-6
has caused the Debian Bug report #1070444,
regarding cxref: arm64 FTBFS with glibc 2.38
to be marked as done.
This means that you claim that the problem has been dealt with.
If
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 also get testsuite errors on current
Processing control commands:
> tags -1 fixed-upstream
Bug #1064486 [src:rnp] rnp: FTBFS: Errors while running CTest
Added tag(s) fixed-upstream.
--
1064486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: clickhouse
Version: 18.16.1+ds-7.4
Severity: serious
Tags: ftbfs
Justification: ftbfs
clickhouse FTBFS in unstable:
[ 87%] Building CXX object
dbms/CMakeFiles/dbms.dir/src/Storages/MergeTree/LevelMergeSelector.cpp.o
cd /<>/obj-x86_64-linux-gnu/dbms && /usr/bin/c++
Processing control commands:
> tags -1 ftbfs
Bug #1066449 [src:mpi4py] mpi4py: FTBFS: Segmentation fault in tests
Ignoring request to alter tags of bug #1066449 to the same tags previously set
--
1066449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066449
Debian Bug Tracking System
Source: mpi4py
Followup-For: Bug #1066449
Control: tags -1 ftbfs
The bug report stopped scanning at the first "error", which is not an
error (it's a check). The last error is the relevant one
testIReadIWrite (test_io.TestIOSelf.testIReadIWrite) ... ok
testIReadIWriteAll
Processing commands for cont...@bugs.debian.org:
> tags 1069799 + ftbfs
Bug #1069799 [rust-multihash-derive-impl] rust-multihash-derive-impl -
(build-)depends unsatisfiable.
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1069799:
Processing control commands:
> severity -1 serious
Bug #1070644 [gnome-remote-desktop] gnome-remote-desktop: System .service file
enabled but not the user one?
Severity set to 'serious' from 'normal'
--
1070644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070644
Debian Bug Tracking
Package: ruby-json
Version: 2.7.2+dfsg-1
Severity: grave
Justification: renders package unusable
This new ruby-json version breaks how-can-i-help:
[...]
Unpacking ruby-json:amd64 (2.7.2+dfsg-1) over (2.6.3+dfsg-1+b2) ...
Setting up ruby-json:amd64 (2.7.2+dfsg-1) ...
Your message dated Mon, 06 May 2024 14:37:58 +
with message-id
and subject line Bug#1068610: fixed in dico 2.11-4.2
has caused the Debian Bug report #1068610,
regarding dico: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On Mon, 06 May 2024 10:33:54 -0400 Scott Kitterman
wrote:
> Source: kde-spectacle
> Version: 22.12.3-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the
past)
>
> Once kcolorpicker is decrufted, this package will FTBFS. Please update
Source: kde-spectacle
Version: 22.12.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Once kcolorpicker is decrufted, this package will FTBFS. Please update
your build-depends.
Scott K
Your message dated Mon, 06 May 2024 16:12:31 +0200
with message-id
and subject line Re: Bug#1069387: distro-info: FTBFS on arm64: Can't write the
issue template for the crash in
/<>/debian/.debhelper/generated/_source/home/.cache/pylint/pylint-crash-2024-04-20-04-31-27.txt
because of: '[Errno
Source: dipy
Version: 1.8.0-2
Severity: serious
Tags: ftbfs patch
Hi Maintainer
dipy FTBFS when built with the 'nocheck' profile. I've copied what I
hope is the relevant part of the log below.
The following patch worked for me:
--- a/debian/rules
+++ b/debian/rules
@@ -111,11 +111,11 @@
;
Processing commands for cont...@bugs.debian.org:
> reassign 1069460 src:openmpi
Bug #1069460 [src:bitshuffle] bitshuffle: FTBFS on armhf: tests fail
Bug reassigned from package 'src:bitshuffle' to 'src:openmpi'.
No longer marked as found in versions bitshuffle/0.5.1-1.2.
Ignoring request to alter
Your message dated Mon, 06 May 2024 13:49:50 +
with message-id
and subject line Bug#1069404: fixed in lua-luaossl 20220711-2
has caused the Debian Bug report #1069404,
regarding lua-luaossl: FTBFS on arm64: ld: cannot find -lz: No such file or
directory
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> unarchive 1066704
Bug #1066704 {Done: Michael R. Crusoe } [src:libcgns]
libcgns: FTBFS: tkogl.c:602:8: error: implicit declaration of function
‘TkWmAddToColormapWindows’ [-Werror=implicit-function-declaration]
Unarchived Bug 1066704
> found
Your message dated Mon, 06 May 2024 13:18:58 +
with message-id
and subject line Bug#1069356: fixed in lua-cqueues 20200726-2
has caused the Debian Bug report #1069356,
regarding lua-cqueues: FTBFS on arm64: ld: cannot find -lz: No such file or
directory
to be marked as done.
This means that
Your message dated Mon, 06 May 2024 13:04:59 +
with message-id
and subject line Bug#1061519: fixed in shim 15.8-1
has caused the Debian Bug report #1061519,
regarding shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549
CVE-2023-40550 CVE-2023-40551
to be marked as done.
This
Your message dated Mon, 06 May 2024 13:04:59 +
with message-id
and subject line Bug#1057606: fixed in shim 15.8-1
has caused the Debian Bug report #1057606,
regarding shim: FTBFS: ./debian/generate_dbx_list: 23: efisiglist: not found
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 1059228 + ftbfs
Bug #1059228 [src:s2geometry] build system hard-codes -std=c++11
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1059228:
On Sat, 28 Oct 2023 12:52:30 +0200 Tobias Frost wrote:
Control: tags -1 confirmed
Here's a backtrace when clicking on Settings -> System.
Thread 1 "blastem" received signal SIGSEGV, Segmentation fault.
tern_foreach_int (head=, fun=0x555c12a0 ,
data=0x7fffd7f0, keybuf=0x7fffd8c0
Source: libvirt
Version: 10.3.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libvirt=amd64=10.3.0-1=1714824148=0
...
53) completion-command...
In '/<>/tests/virshtestdata/completion-command.out':
Offset 6
Expect
Your message dated Mon, 06 May 2024 12:09:19 +
with message-id
and subject line Bug#1056677: fixed in hpcc 1.5.0-4
has caused the Debian Bug report #1056677,
regarding build-depends on atlas, which is obsolete and scheduled for removal
to be marked as done.
This means that you claim that the
Source: webrtc-audio-processing
Version: 1.0-0.2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/webrtc-audio-processing.html
https://buildd.debian.org/status/fetch.php?pkg=webrtc-audio-processing=riscv64=1.0-0.2=1706028598=0
...
FAILED:
Processing commands for cont...@bugs.debian.org:
> notforwarded 1070335
Bug #1070335 [samba-dev] samba-dev: missing Breaks+Replaces: libwbclient-dev
(<< 2:4.20)
Unset Bug forwarded-to-address
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1070335:
Processing commands for cont...@bugs.debian.org:
> forwarded 1070335 https://bugs.launchpad.net/designate/+bug/2064916
Bug #1070335 [samba-dev] samba-dev: missing Breaks+Replaces: libwbclient-dev
(<< 2:4.20)
Set Bug forwarded-to-address to
'https://bugs.launchpad.net/designate/+bug/2064916'.
>
Processing commands for cont...@bugs.debian.org:
> notfound 1070236 2:4.19.6+dfsg-3
Bug #1070236 {Done: Michael Biebl } [python3-samba]
python3-samba: SyntaxError during configuration phase of package on upgrade
No longer marked as found in versions samba/2:4.19.6+dfsg-3.
> thanks
Stopping
Your message dated Mon, 06 May 2024 11:22:09 +
with message-id
and subject line Bug#1070188: fixed in spyder 5.5.1+ds-2
has caused the Debian Bug report #1070188,
regarding python3-spyder: uninstallable in unstable due to pylint
to be marked as done.
This means that you claim that the
Your message dated Mon, 06 May 2024 13:23:37 +0200
with message-id <22975850.EfDdHjke4D@debian>
and subject line
has caused the Debian Bug report #1070017,
regarding google-android-installers: depends on pre-64 libraries
to be marked as done.
This means that you claim that the problem has been
Package: src:mixxx
Version: 2.4.0+dfsg-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
--- LOG END ---
error:
Source: rust-pipewire
Version: 0.8.0-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=rust-pipewire=0.8.0-4
...
error[E0308]: mismatched types
--> src/thread_loop.rs:142:43
|
142 | nix::sys::time::TimeSpec::new(abstime.tv_sec, abstime.tv_nsec)
Source: rust-hypothesis
Version: 0.11.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=rust-hypothesis=0.11.1-1
https://buildd.debian.org/status/logs.php?pkg=rust-hypothesis=0.11.1-2
...
Running
Your message dated Mon, 06 May 2024 10:51:14 +
with message-id
and subject line Bug#1070460: fixed in translate-toolkit 3.13.0-1
has caused the Debian Bug report #1070460,
regarding translate-toolkit: FTBFS: failing tests
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> forwarded 1069310 https://github.com/hanwen/go-fuse/issues/514
Bug #1069310 [golang-github-hanwen-go-fuse-dev] FTBFS: tests failed
Set Bug forwarded-to-address to 'https://github.com/hanwen/go-fuse/issues/514'.
> thanks
Stopping processing here.
I spent about half an hour looking at this, and wanted to share my thoughts:
- the build / tests succeed on all architectures but mips64el
- the panic in question appears to come from here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13
--
a
please ignore the above, it was meant to be sent to #1069310 instead
On Mon, May 6, 2024 at 6:34 AM Reinhard Tartler wrote:
> I spent about half an hour looking at this, and wanted to share my
> thoughts:
>
> - the build / tests succeed on all architectures but mips64el
> - the panic in
I spent about half an hour looking at this, and wanted to share my thoughts:
- the build / tests succeed on all architectures but mips64el
- the panic in question appears to come from here:
https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13
-- a
Processing control commands:
> severity -1 important
Bug #1070463 [src:gnome-remote-desktop] gnome-remote-desktop: 46 has failing
build tests
Severity set to 'important' from 'serious'
> unblock 1050237 by -1
Bug #1050237 [release.debian.org] transition: mutter/gnome-shell 45
1050237 was blocked
Control: severity -1 important
Control: unblock 1050237 by -1
On Sun, May 5, 2024 at 1:15 PM Jeremy Bícha wrote:
> The build tests were passing with version 45. It is not clear to me
> why the tests are failing in Debian Experimental but passing in Ubuntu
> 24.04 LTS.
I have ignored
Processing commands for cont...@bugs.debian.org:
> forwarded 1061216
> https://github.com/AcademySoftwareFoundation/openvdb/issues/1804
Bug #1061216 [src:openvdb] openvdb: Please upgrade to llvm-toolchain-18
Set Bug forwarded-to-address to
* Lucas Nussbaum [Wed Mar 13, 2024 at 12:51:29PM +0100]:
[...]
> This is most likely caused by a change in dpkg 1.22.6, that enabled
> -Werror=implicit-function-declaration. For more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Processing commands for cont...@bugs.debian.org:
> tags 102 + patch
Bug #102 [src:hping3] hping3: FTBFS: script.c:1351:29: error: implicit
declaration of function ‘asprintf’; did you mean ‘vsprintf’?
[-Werror=implicit-function-declaration]
Added tag(s) patch.
> thanks
Stopping
Le 06/05/2024 à 10:27, Gregor Riepl a écrit :
Which LLVM versions are you planning to remove?
15, 16 soon. 17 later.
Would it be possible to keep at least LLVM 15 until upstream has
upgraded their code base?
Sounds very unlikely for the next Debian release.
If a fix for this can't be
Your message dated Mon, 06 May 2024 08:39:59 +
with message-id
and subject line Bug#1068058: fixed in libgtkada 24.0.0-3
has caused the Debian Bug report #1068058,
regarding libgtkada: FTBFS on armhf ( compilation of gtkada-canvas_view.adb
failed)
to be marked as done.
This means that you
Which LLVM versions are you planning to remove?
15, 16 soon. 17 later.
Would it be possible to keep at least LLVM 15 until upstream has
upgraded their code base?
Sounds very unlikely for the next Debian release.
If a fix for this can't be released on time, I'm requesting an exception
for
Processing commands for cont...@bugs.debian.org:
> reassign 1059874 src:uhd 4.6.0.0+ds1-5
Bug #1059874 [libuhd4.6.0] libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0
Warning: Unknown package 'libuhd4.6.0'
Bug reassigned from package 'libuhd4.6.0' to 'src:uhd'.
No longer marked as found in
Processing commands for cont...@bugs.debian.org:
> tags 1067724 + sid trixie
Bug #1067724 [libopenvr-dev] libopenvr-dev: Please upgrade opevr to version 2
Added tag(s) sid and trixie.
> reassign 1067724 src:openvr 1.23.7~ds1-2
Bug #1067724 [libopenvr-dev] libopenvr-dev: Please upgrade opevr to
93 matches
Mail list logo
