Bug#1037146: Booting signed kernel fails because no kernel module can be loaded due to key was rejected by service

Source: linux-signed-amd64 Version: 6.1.27+1 Tags: bookworm I would like to build the kernel from source and sign it including its corresponding modules. Booting my own built and signed kernel fails, and I end up in an emergency shell. If I Install and boot the unsigned kernel, the system

Bug#1033641: libseccomp failing to build from source on bookworm with python 3.11

Source: libseccomp Version: 2.5.4-1 Tags: bookworm ftbfs Severity: serious When I build this package from source, the build fails. Please see log output at the end. My build environment is a container image based on Debian testing bookworm, which already includes python3.11 After some

Bug#1033553: libprelude failing to build from source on bookworm with python 3.11

Source: libprelude Version: 5.2.0-5 Tags: bookworm ftbfs Severity: serious When I build this package from source, the build fails. Please see log output at the end. My build environment is a container image based on Debian testing bookworm, which already includes python3.11 After some

Bug#1033353: libpwquality failing to build on bookworm with python 3.11

Source: libpwquality Version: 1.4.5-1 Tags: bookworm ftbfs When I build this package from source, the build fails. Please see log output at the end. My build environment is a container image based on Debian testing bookworm, which already includes python3.11 After some research I guess it may

Bug#916682: python-cryptography: build from source fails with libssl-dev_1.1.0j-1~deb9u1 amd64

was successfully. Therefor this bug can be closed in my opinion. Thanks and best regards, Dirk Mayer -Original Message- From: Sebastian Andrzej Siewior Sent: Dienstag, 24. September 2019 22:18 To: Mayer, Dirk (DI PA DE-L SWA OP) Cc: Tristan Seligmann ; 916...@bugs.debian.org; debian

Bug#916682: python-cryptography: build from source fails with libssl-dev_1.1.0j-1~deb9u1 amd64

Sent: Montag, 17. Dezember 2018 12:24 To: Mayer, Dirk (PD PA DE-L SWA OP) ; 916...@bugs.debian.org; debian-python Subject: Re: Bug#916682: python-cryptography: build from source fails with libssl-dev_1.1.0j-1~deb9u1 amd64 I suspect this is fixed upstream but I am unable to take care of uploading

Bug#922375: closed by Bastian Blank (Re: Bug#922375: cloud-init: build from src failes some unit tests)

-Original Message- From: Debian Bug Tracking System Sent: Freitag, 15. Februar 2019 09:27 To: Mayer, Dirk (PD PA DE-L SWA OP) Subject: Bug#922375 closed by Bastian Blank (Re: Bug#922375: cloud-init: build from src failes some unit tests) This is an automatic notification regarding

Bug#922375: cloud-init: build from src failes some unit tests

Package: cloud-init Version: 18.3-3 Tags: ftbs Hello Debian community, while building the cloud-init source package on a buster based build system, the resulting build fails during the test phase with the following errors: ==

Bug#921715: libgtk2.0-0-udeb: wrong dependency while building on buster based system

Package: gtk+2.0 Version: 2.24.32-3 Tags: d-i, buster Hello Debian community, while building the gtk+2.0 source package on a buster based build system, the resulting package libgtk2.0-0-udeb yields a wrong dependency. Instead of the correct dependency to the package libxinerama1-udeb it depends

Bug#921712: libgtk2.0-0-udeb: wrong dependency while building on buster based system

Source: libgtk2.0-0-udeb Version: 2.24.32-3 Tags: d-i, buster Hello Debian community, while building the gtk+2.0 source package on a buster based build system, the resulting package libgtk2.0-0-udeb yields a wrong dependency. Instead of the correct dependency to the package libxinerama1-udeb it

Bug#920334: Referes to Bug #918102

Hello, I think it has the same root cause like the issue reported by me and tracked under #918102 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918102 I also included a possible fix to this problem in there. Changes suggested: Add the '--batch' parameter to gpg execution calls. This also

Bug#918102: Issue also refers to #920334

This issue also refers to #920334, which describes a missing --no-tty parameter https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920334 Regards, Dirk

Bug#918218: additional information

Severity: important Hi, sorry forgot to mention some additional information. Inside docker container: $ uname -a Linux 27046b6215ae 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux $ cat /etc/debian_version 9.5

Bug#918218: Bug: symlinks does not work in a container with overlayFS

Package: symlinks Version: 1.4-3+b1 Hello Debian community, the symlinks command does not work as expected, if executed from a docker container containing overlay2 filesystem. No absolute symlinks are converted to relative ones, when executing symlinks -o -r -c -v dir1 How to reproduce: 1)

Bug#918102: simple-cdd: build of custom iso failes in docker container with not tty and openssl 1.1.0j-1~deb9u1 installed

Package: simple-cdd Version: 0.6.6 Hello Debian community, when I try to build a custom Debian installer ISO with simple-cdd and the latest openssl libs installed, the following (truncated) error occurs: $ build-simple-cdd --conf detox.conf --logfile detox_mirror.log --verbose --debug

Bug#916682: python-cryptography: build from source fails with libssl-dev_1.1.0j-1~deb9u1 amd64

Package: python3-cryptography Version: 1.7.1-3 Source: python-cryptography Hello Debian community, when I try to compile and package the python3-cryptography 1.7.1-3 the build fails with the following (truncated) error: running build_ext generating cffi module