Your message dated Mon, 12 Feb 2024 07:49:12 +
with message-id
and subject line Bug#1053865: fixed in prody 2.4.1+dfsg-1
has caused the Debian Bug report #1053865,
regarding prody: incompatible with python3-biopython > 1.79
to be marked as done.
This means that you claim that the problem has
Package: mutter
Version: 44.8-3
Followup-For: Bug #1063640
X-Debbugs-Cc: guyrutenb...@gmail.com
Dear Maintainer,
I just experienced the same bug using mutter 44.8-3 and adwaita-icon-them
46~beta-1. Reverting back to adwaita-icon-theme 45.0-2 resolved the issue.
Guy
*** Reporter, please
flask 3.0 is there now.
https://tracker.debian.org/news/1502520/accepted-flask-302-1-source-into-unstable/
Le lun. 12 févr. 2024 à 04:47, Emmanuel Arias a écrit :
>
> Hi,
>
> flask 3.0 will fix this two tests?
I don't know, I was just busy with other things
and it felt like wastign time to test
Source: custodian
Version: 2024.1.9-2
Severity: serious
Justification: Policy 3.3
Policy 3.3 says that maintainer addresses must accept mail from Debian
role accounts. This one, apparently, does not:
From: debichem-devel-ow...@alioth-lists.debian.net
To: ftpmas...@ftp-master.debian.org
Processing control commands:
> reassign -1 src:curl 8.6.0-1
Bug #1063462 [src:pycurl] pycurl: FTBFS during tests: GnuTLS recv error (-110):
The TLS connection was non-properly terminated
Bug reassigned from package 'src:pycurl' to 'src:curl'.
No longer marked as found in versions
Control: reassign -1 src:curl 8.6.0-1
Control: affects -1 src:pycurl
On Thu, 8 Feb 2024, Emanuele Rocca wrote:
Source: pycurl
Version: 7.45.2-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid trixie ftbfs
Dear Maintainer,
pycurl
Hi,
flask 3.0 will fix this two tests? New upstream release of flask-restful
+ this two tests turned off can not be uploaded yet?
--
cheers,
Emmanuel Arias
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
⠈⠳⣄
Your message dated Mon, 12 Feb 2024 01:00:39 +
with message-id
and subject line Bug#1058720: fixed in slurm-wlm 23.11.3-1
has caused the Debian Bug report #1058720,
regarding slurm-wlm: CVE-2023-49933 CVE-2023-49935 CVE-2023-49936
CVE-2023-49937 CVE-2023-49938
to be marked as done.
This
Your message dated Mon, 12 Feb 2024 01:00:26 +
with message-id
and subject line Bug#1016379: fixed in nfft 3.5.3-2
has caused the Debian Bug report #1016379,
regarding nfft: soname changes without package renaming and library transition
to be marked as done.
This means that you claim that
Your message dated Mon, 12 Feb 2024 01:00:26 +
with message-id
and subject line Bug#1016378: fixed in nfft 3.5.3-2
has caused the Debian Bug report #1016378,
regarding nfft: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Mon, 12 Feb 2024 01:00:26 +
with message-id
and subject line Bug#1016377: fixed in nfft 3.5.3-2
has caused the Debian Bug report #1016377,
regarding nfft builds with -march=native
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> tags 1058130 + fixed-upstream
Bug #1058130 [src:python-nmea2] python-nmea2: FTBFS: ModuleNotFoundError: No
module named 'imp'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1058130:
On Sun, 11 Feb 2024 at 13:53:56 -0800, Benjamin Kaduk wrote:
> On Sat, Feb 10, 2024 at 01:33:15PM +0100, Johannes Schauer Marin Rodrigues
> wrote:
> > there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that
> > failed for arm64, armel and ppc64el:
> >
> >
Source: golang-github-katalix-go-l2tp
Version: 0.1.6-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
In a clean sid schroot, one of the tests is timing out:
> transport_test.go:388: test sender function reported an error: failed to
> send Hello message: transmit of
Source: gloo-cuda
Version: 0.0~git20230117.1090929-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org
gloo-cuda is involved in the libhiredis transition. But since the
package cannot be built on the buildds, uploads of builds against the
Processing commands for cont...@bugs.debian.org:
> affects 1063737 + src:nvidia-graphics-drivers-tesla-470
Bug #1063737 [release.debian.org] bookworm-pu: package
nvidia-graphics-drivers-tesla-470/470.223.02-4~deb12u1
Added indication that 1063737 affects src:nvidia-graphics-drivers-tesla-470
>
Your message dated Sun, 11 Feb 2024 22:06:50 +
with message-id
and subject line Bug#1061034: fixed in lazarus 3.0+dfsg1-8
has caused the Debian Bug report #1061034,
regarding lcl-utils-3.0 Missing dependencies for lazbuild
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 11 Feb 2024 21:52:40 +
with message-id
and subject line Bug#1061007: fixed in xeus-python 0.15.10+~0.6.1-2
has caused the Debian Bug report #1061007,
regarding libxeus9 incompatible with nlohmann::json_abi_v3_11_3
to be marked as done.
This means that you claim that
Your message dated Sun, 11 Feb 2024 21:52:40 +
with message-id
and subject line Bug#1061007: fixed in xeus-python 0.15.10+~0.6.1-2
has caused the Debian Bug report #1061007,
regarding xeus-python: FTBFS:
./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5bd): undefined
reference to
Your message dated Sun, 11 Feb 2024 21:52:32 +
with message-id
and subject line Bug#1061007: fixed in xeus 3.1.3-2
has caused the Debian Bug report #1061007,
regarding libxeus9 incompatible with nlohmann::json_abi_v3_11_3
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 11 Feb 2024 21:52:32 +
with message-id
and subject line Bug#1061007: fixed in xeus 3.1.3-2
has caused the Debian Bug report #1061007,
regarding xeus-python: FTBFS:
./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5bd): undefined
reference to
Your message dated Sun, 11 Feb 2024 21:52:31 +
with message-id
and subject line Bug#1060164: fixed in xeus 3.1.3-2
has caused the Debian Bug report #1060164,
regarding libxeus9 incompatible with nlohmann::json_abi_v3_11_3
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 11 Feb 2024 21:52:31 +
with message-id
and subject line Bug#1060164: fixed in xeus 3.1.3-2
has caused the Debian Bug report #1060164,
regarding xeus-python: FTBFS:
./obj-x86_64-linux-gnu/./src/main.cpp:147:(.text.startup+0x5bd): undefined
reference to
On Sat, Feb 10, 2024 at 01:33:15PM +0100, Johannes Schauer Marin Rodrigues
wrote:
>
> there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that
> failed for arm64, armel and ppc64el:
>
> https://buildd.debian.org/status/package.php?p=krb5
>
> The error logs look very similar:
> ***
Processing control commands:
> reopen -1
Bug #1063029 {Done: Jelmer Vernooij } [src:rust-breezyshim]
rust-breezyshim fails autopkg tests with breezy from unstable, blocking
migration
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and
Control: reopen -1
python3-tzlocal was added as a suggestion, not a dependency.
Processing commands for cont...@bugs.debian.org:
> reassign 1063731 nvidia-kernel-dkms
Bug #1063731 [linux-image-6.1.0-18-amd64] Kernel panic after update from Debian
12.4 to 12.5 in command line
Bug reassigned from package 'linux-image-6.1.0-18-amd64' to
'nvidia-kernel-dkms'.
Ignoring request
Processing commands for cont...@bugs.debian.org:
> reassign 1063717 nvidia-kernel-dkms
Bug #1063717 [nvidia-graphics-drivers] cuda-drivers: Build of module nvidia.ko
fails
Bug reassigned from package 'nvidia-graphics-drivers' to 'nvidia-kernel-dkms'.
Ignoring request to alter found versions of
Processing commands for cont...@bugs.debian.org:
> reassign 1063717 nvidia-graphics-drivers
Bug #1063717 [cuda-drivers] cuda-drivers: Build of module nvidia.ko fails
Warning: Unknown package 'cuda-drivers'
Bug reassigned from package 'cuda-drivers' to 'nvidia-graphics-drivers'.
No longer marked
Processing commands for cont...@bugs.debian.org:
> reassign 1063729 nvidia-kernel-dkms
Bug #1063729 [linux-image-6.1.0-18-amd64] Kernel panic after update from Debian
12.4 to 12.5 in command line and reboot
Bug reassigned from package 'linux-image-6.1.0-18-amd64' to
'nvidia-kernel-dkms'.
Package: linux-image-6.1.0-18-amd64
Version: 6.1.76-1: amd64
Severity: critical
Bug Description:
Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot.
Look "Kernel panic after update.txt" in attachment for details.
Look message booting display in attachment for
Your message dated Sun, 11 Feb 2024 18:34:59 +
with message-id
and subject line Bug#1063056: fixed in lfortran 0.30.0-5
has caused the Debian Bug report #1063056,
regarding dh-fortran-mod: autopkgtest failure: No CMAKE_C_COMPILER could be
found.
to be marked as done.
This means that you
Your message dated Sun, 11 Feb 2024 18:34:59 +
with message-id
and subject line Bug#1062813: fixed in lfortran 0.30.0-5
has caused the Debian Bug report #1062813,
regarding lfortran fails both autopkg tests
to be marked as done.
This means that you claim that the problem has been dealt with.
The same bug is cited here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
You can close this bug.
Package: cuda-drivers
Version: 545.23.08-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: matte.mb2006.9...@gmail.com
Dear Maintainer,
Compiling the cuda driver for kernel 6.1.0-18 fails with this error:
"
ERROR: modpost: GPL-incompatible module nvidia.ko
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
Adding "init_on_alloc=0" to kernel boot does NOT change anything.
Your message dated Sun, 11 Feb 2024 16:20:37 +
with message-id
and subject line Bug#1058438: fixed in transmissionrpc 7.0.3-1
has caused the Debian Bug report #1058438,
regarding transmissionrpc: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11"
Processing commands for cont...@bugs.debian.org:
> reassign 1063713 nvidia-kernel-dkms
Bug #1063713 [src:linux] linux-image-6.1.0-18-amd64: apt fails to install the
kernel version, reports problem with building modules
Bug reassigned from package 'src:linux' to 'nvidia-kernel-dkms'.
No longer
Package: src:linux
Version: 6.1.76-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: gnomedeu...@gmail.com
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model information
sys_vendor:
Processing commands for cont...@bugs.debian.org:
> retitle 1063707 liblua5.4-0: C++ library missing all "lua*" function symbols
Bug #1063707 [liblua5.4-0] liblua5.4-0: C++ library missing all "lua_*"
function symbols
Changed Bug title to 'liblua5.4-0: C++ library missing all "lua*" function
Processing commands for cont...@bugs.debian.org:
> reassign 1063706 src:nvidia-graphics-drivers-tesla-470
Bug #1063706 [nvidia-graphics-drivers-tesla-470] linux-image-6.1.0-18-amd64:
nvidia-tesla-470 doesn't build in 6.1.0-18 kernel
Bug reassigned from package 'nvidia-graphics-drivers-tesla-470'
Processing commands for cont...@bugs.debian.org:
> tags 1063707 + patch
Bug #1063707 [liblua5.4-0] liblua5.4-0: C++ library missing all "lua_*"
function symbols
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1063707:
tags -1 + patch
thanks
https://salsa.debian.org/lua-team/lua5.4/-/merge_requests/5
--
Patrick "P. J." McDermott: http://www.pehjota.net/
Lead Developer, ProteanOS: http://www.proteanos.com/
Founder and CEO, Libiquity: http://www.libiquity.com/
Package: torbrowser-launcher
Version: 0.3.6-2
Severity: serious
The torbrowser-launcher package in Debian is still on the outdated 0.3.6
version that has multiple problems and does not work properly because of the
download URL change, AppArmor rules change and other things that were fixed in
Processing commands for cont...@bugs.debian.org:
> tags 1063666 -trixie
Bug #1063666 [src:adwaita-icon-theme] adwaita-icon-theme: 46 breaks gnome-shell
cursor, fixed with mutter 44.8-3
Removed tag(s) trixie.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
> tags 1063666 sid
Bug #1063666 [src:adwaita-icon-theme] adwaita-icon-theme: 46 breaks gnome-shell
cursor, fixed with mutter 44.8-3
Added tag(s) sid.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
Package: liblua5.4-0
Version: 5.4.6-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: p...@pehjota.net
Hi,
Since version 5.4.6-1, liblua5.4-c++.so.0.0.0 defines no "lua_*"
function symbols (only "lua_ident@@LUA_5.4"):
$ readelf -s
Processing commands for cont...@bugs.debian.org:
> reassign 1063689 nvidia-kernel-dkms
Bug #1063689 [src:linux] linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU
Bug reassigned from package 'src:linux' to 'nvidia-kernel-dkms'.
No longer marked as found in versions linux/6.1.76-1.
Ignoring
Processing commands for cont...@bugs.debian.org:
> reassign 1063706 nvidia-graphics-drivers-tesla-470
Bug #1063706 [src:linux] linux-image-6.1.0-18-amd64: nvidia-tesla-470 doesn't
build in 6.1.0-18 kernel
Bug reassigned from package 'src:linux' to 'nvidia-graphics-drivers-tesla-470'.
No longer
Your message dated Sun, 11 Feb 2024 13:32:13 +0100
with message-id <20240211133213.1096c5547204d11da4759...@mailbox.org>
and subject line Re: Bug#1063413: FTBFS: cannot open
/<>/Keyboard/pc105.ekbd: No such file
has caused the Debian Bug report #1063413,
regarding FTBFS: cannot open
Your message dated Sun, 11 Feb 2024 11:34:19 +
with message-id
and subject line Bug#1063494: fixed in engrampa 1.26.2-1
has caused the Debian Bug report #1063494,
regarding engrampa: CVE-2023-52138: Path traversal via crafted cpio archives in
Engrampa archivers
to be marked as done.
This
The bug still persists with the linux-image-6.1.0-18-amd64.
Processing commands for cont...@bugs.debian.org:
> unblock 1061605 by 1063636
Bug #1061605 [src:scipy] scipy: tests skipped during build and autopkgtest not
in sync
1061605 was blocked by: 1063527 1063636 1063584 1063526
1061605 was not blocking any bugs.
Removed blocking bug(s) of 1061605:
Package: kxc
Version: 0.15-4.1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The package fails to install because building the initramfs fails with
the following error:
update-initramfs: Generating /boot/initrd.img-6.4.0-1-amd64
cp: cannot stat '/etc/kxc/': No such
Your message dated Sun, 11 Feb 2024 09:04:08 +
with message-id
and subject line Bug#1063491: fixed in python-jedi 0.19.1+ds1-1
has caused the Debian Bug report #1063491,
regarding python3-jedi: unvendoring python3-typeshed breaks other packages
to be marked as done.
This means that you claim
56 matches
Mail list logo
