Hi
On Thu, May 23, 2024 at 08:55:46PM +0300, Adrian Bunk wrote:
> Was this any misconfiguration on the debian.org side,
> or is/was this any issue at alioth-lists.debian.net,
> or what else might have gone wrong here?
It seems to be fixed. My mailbox contains the last bounce on March,
8th.
Control: tags -1 moreinfo
Control: severity -1 normal
On Sun, May 19, 2024 at 08:58:57PM +0200, Manny wrote:
> To install linux-image-6.6.13+bpo-amd64, this command was executed:
>
> $ apt -t bookworm-backports install linux-image-amd64
>
> I have a transcript of the session but it’s probably
Control: tags -1 moreinfo
Control: severity -1 important
On Sat, May 18, 2024 at 10:25:14PM +0200, Matteo Settenvini wrote:
> booting kernel 6.8.9-1 with dracut, systemd, and btrfs as the root device
> fails
> to mount the root partition. I just tried the kernel from sid and it seems
> indeed \
Hi
On Sun, May 12, 2024 at 11:54:42PM +0200, Helmut Grohne wrote:
> On Sun, May 12, 2024 at 07:35:09PM +0200, Bastian Blank wrote:
> > > 1. API expectation of *-$arch-cross packages
> > I asked exactly that in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10654
On Sun, May 12, 2024 at 01:53:33PM +0200, Helmut Grohne wrote:
> 2+3+6+7. linux-libc-dev could be split into linux-libc-dev-common
>arch:all m-a:foreign and the symlink farms could be kept in
>linux-libc-dev:any m-a:same retaining the size reduction.
This would not actually work.
Hi Helmut
On Sun, May 12, 2024 at 01:53:33PM +0200, Helmut Grohne wrote:
> > Care to just share what you actually found? Where is it broken and how
> > to see this?
> > Because this whole thing started with "it is broken, but I won't tell
> > you where or what or how".
> Quite clearly, this is
Control: reassign -1 src:linux
Control: severity -1 normal
Control: tags -1 moreinfo
On Mon, Apr 22, 2024 at 09:12:59AM +0200, bouv...@buxtehude.debian.org wrote:
> Something seems wrong in 6.1.0-20, but it is not immediately wrong: it waits
> until some sort of trigger. After that, rebooting
Package: python-glance-store
Version: 4.7.0-2
Severity: serious
python-glance-store build-depends on deprecated package python3-boto.
See #1058652
Also it seems to not build at all:
| dpkg-buildpackage: info: source package python-glance-store
| dpkg-buildpackage: info: source version 4.7.0-2
|
Hi
binNMU are known to not work on the signing side of the archive.
dpkg contains special handling for binNMU style versions. If it sees a
1-1+b1 as version, it will search some source files with version 1-1.
This means you can never properly have a source package with such a
version.
As the
4-01-15 10:54:55.0 +0100
+++ grub2-2.12/debian/changelog 2024-04-01 10:20:09.0 +0200
@@ -1,3 +1,10 @@
+grub2 (2.12-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * No change rebuild. (closes: #1067486)
+
+ -- Bastian Blank Mon, 01 Apr 2024 10:20:09 +0200
+
gru
Hi
On Thu, Mar 21, 2024 at 08:48:01PM +0100, Helmut Grohne wrote:
> I was recently working on gcc builds and this disagreement currently
> makes stuff unbuildable. Hence I looked into solutions and/or
> workarounds.
Care to just share what you actually found? Where is it broken and how
to see
Control: reassign -1 tech-ctte
Control: severity -1 normal
Hi
I don't see any way to solve this issue right now. Please decide this
matter according to 6.1 nr 2 Debian Constitution.
Background: linux-libc-dev provides the Linux API for consumption by
all userspace stuff.
This package was
On Wed, Mar 20, 2024 at 09:59:31PM +0100, Matthias Klose wrote:
> Independent of any technical issues, this is a hijacking of a package name.
> Please revert that change.
Okay. Please prepare to take over linux-libc-dev alltogether then,
there can be only one copy.
Bastian
--
Insufficient
Control: unmerge 1059786
Control: reassign 1059786 cross-toolchain-base
Hi
I'm going forward with the provided plan and will add Breaks with Linux
6.8.
Regards,
Bastian
--
Insults are effective only where emotion is present.
-- Spock, "Who Mourns for Adonais?" stardate 3468.1
Hi
Not a single piece of evidence of a breakage showed up within the last
weeks. I'm therefor closing this bug report.
Regards,
Bastian
--
You! What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0
Control: severity -1 important
On Sun, Mar 10, 2024 at 11:47:17AM +0100, Eric Valette wrote:
> And then it correctly builds the kernel and modules .ko file, then sign the
> ko and xz compress it to get foo.ko.xz. Here are extracts
>
> But then it tries to sign again the modules using the .ko
Control: severity -1 minor
> Because this is an x32 host.
x32 is multi-arch kernel only architecture. Debian still don't have
proper support for multi-arch for compilers.
Just use amd64.
Bastian
--
Bones: "The man's DEAD, Jim!"
Hi Helmut
On Tue, Mar 05, 2024 at 09:50:27AM +0100, Helmut Grohne wrote:
> The problem arises in the reverse sense. If a file does not exist in
> one, it is searched in the second and erroneously may be found. That may
> make tests pass that should not pass and typically causes a link failure
>
On Mon, Mar 04, 2024 at 11:04:23PM +0100, Bastian Blank wrote:
> At least to show where it breaks.
And I actually tried it and can not show the expected breakage from
missing /usr/include in the search path. gcc-13-cross builds fine with
only linux-libc-dev/6.7.7-1.
| -rw-r--r-- 1 bast
On Mon, Mar 04, 2024 at 01:49:24PM +0100, Helmut Grohne wrote:
> The packaged gcc cross toolchain uses a sysroot during its own build
> still. As it is implemented now, it searches /usr//include, but
> not /usr/include/. So quite fundamentally, the Provides that
> we two agreed do break the build
Control: tags -1 moreinfo
On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't
> do that completely
> However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.
So you claim that
On Mon, Mar 04, 2024 at 12:07:15PM +0100, Matthias Klose wrote:
> On 04.03.24 11:29, Bastian Blank wrote:
> > On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> > > However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.
> >
> >
Control: reassign -1 cross-toolchain-base
Control: forcemerge 1059786 -1
On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't
> do that completely
This is #1059786. This lacks a response from you. So I'm
Package: isospec
Severity: serious
- Forwarded message from debichem-devel-ow...@alioth-lists.debian.net -
From: debichem-devel-ow...@alioth-lists.debian.net
To: ftpmas...@ftp-master.debian.org
Subject: Processing of isospec_2.2.1-4.1~exp2_source.changes
You are not allowed to post to
Control: reassign -1 tech-ctte
Control: severity -1 normal
On Mon, Feb 26, 2024 at 02:20:41PM +0100, Julian Andres Klode wrote:
> In addition, this means that the ABI changes within the same package
> names, causing different ABIs to no longer be co-installable, which can
> have drastic effect on
Package: fai-client
Version: 6.0.5
Severity: serious
X-Debbugs-Cc: wa...@debian.org
The check-cross-arch tool copies a qemu-mumble-static binaries into the
new system, but never cleans it up. So this leaks unmanaged binaries
into the new system.
Also using qemu-user-static without the F flag is
Control: reassign -1 kmod
On Mon, Feb 12, 2024 at 10:37:46PM +0100, Marco d'Itri wrote:
> On Feb 12, Salvatore Bonaccorso wrote:
> > --with-module-directory=/usr/lib/modules
> I can revert it if it causes too much trouble, but maybe this is just
> the right time to switch the kernel packages to
On Mon, Feb 12, 2024 at 10:26:07PM +0100, Salvatore Bonaccorso wrote:
> On Mon, Feb 12, 2024 at 10:16:21PM +0100, Bastian Blank wrote:
> > On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote:
> > > kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64
> >
On Mon, Feb 12, 2024 at 10:09:41PM +0100, Salvatore Bonaccorso wrote:
> kernel-wedge copy-modules 6.6.15 amd64 6.6.15-amd64
> depmod: ERROR: could not open directory
> /<>/debian/linux-image-6.6.15-amd64/usr/lib/modules/6.6.15-amd64:
> No such file or directory
I would say depmod changed the
On Sun, Feb 04, 2024 at 08:39:41AM -0800, Noah Meyerhans wrote:
> We have images that use systemd-timesyncd and images that use chrony,
> which is why they're both on the list of dependencies. So the
> dependency list is correct and accurate, and I'm inclined to tag this
> bug "sid" and "wontfix"
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Please blacklist the signed packages, this behaviour is a requirement of
the secure boot signing.
Nothing to see here.
Bastian
--
Most legends have their basis in facts.
-- Kirk, "And The
On Sat, Jan 13, 2024 at 01:03:17AM +0100, Karsten Kruse wrote:
> Is there something else that needs to be done to get the package back into
> testing?
Yes,
https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/547
Bastian
--
If I can have honesty, it's easier to overlook mistakes.
On Wed, Jan 03, 2024 at 11:41:51AM +0100, Andreas Beckmann wrote:
> On 03/01/2024 09.49, Bastian Blank wrote:
> > The dkms autopkgtest fails with Linux 6.6. The only output is:
> > | 173s modinfo: ERROR: Module
> > /var/lib/dkms/dkms_test/1.0/6.6.9-amd64/x86_64/module/dkms_t
Package: dkms
Version: 3.0.12-1
Severity: serious
The dkms autopkgtest fails with Linux 6.6. The only output is:
| 143s autopkgtest [15:40:46]: test run_test.sh: [---
| 143s Using kernel 6.6.9-amd64/x86_64
| 143s Preparing a clean test environment
| 146s Test framework file
Control: severity -1 normal
Hi Klaus
On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote:
> -- System Information:
> Debian Release: trixie/sid
> merged-usr: no
I just realized that this system is in an unsupported state. Bookworm
and later is not longer supported without merged-/usr,
On Mon, Dec 25, 2023 at 11:38:17AM +0100, Sebastian Ramacher wrote:
> (sorry, I wasn't able to find an error, so this is the end of the build
> log.)
The error is:
| Relocations overflow available space!
| Please adjust CONFIG_RELOCATION_TABLE_SIZE to at least 0x001d3000
| make[6]: ***
On Tue, Dec 05, 2023 at 05:16:31PM +0100, Salvatore Bonaccorso wrote:
> And in fact this is the solution proposed in #1036049.
And we need to fix that in stable as well.
Not sure if we can safely use Conflicts to make sure we have a suitable
version. At least without the current apt prefering
On Fri, Oct 27, 2023 at 01:04:00PM +0300, Adrian Bunk wrote:
> > Sadly in Debian there is no way to make that happen. Think for example
> > about bin-nmu.
> Could you give a complete list of problems?
There are at least those problems:
- Bin-nmu can't change binary package names.
- There is no
On Fri, Oct 27, 2023 at 08:43:46AM +0200, Julian Andres Klode wrote:
> > > ## Image packages contains more version info
> > >
> > > Example: linux-image-6.5.3-cloud-arm64
> >
> > > It will not longer be possible to reliably derive the package name from
> > > kernel release (see above), as both
On Fri, Oct 20, 2023 at 05:54:23PM +0200, Bastian Blank wrote:
> Or would it be easier to re-use normal dependency resolving, like:
> Kernel-Provides: linux (>> 6.6.1~), linux (<< 6.6.1.)
> This would allow full flexibility and re-uses existing code to check
> such d
[ Removing some lists ]
On Sat, Oct 07, 2023 at 04:53:33PM +0200, Bastian Blank wrote:
> > ## Image packages contains more version info
> >
> > Example: linux-image-6.5.3-cloud-arm64
>
> > It will not longer be possible to reliably derive the package name from
&g
Moin
On Sun, Sep 24, 2023 at 03:01:51PM +0200, Bastian Blank wrote:
> ## Kernel modules will be signed with an ephemeral key
This is now
https://salsa.debian.org/kernel-team/linux/-/merge_requests/607.
> ## Image packages contains more version info
>
> Example: linux-image-6.5.3
Hi
On Sun, Sep 24, 2023 at 06:05:09PM +0200, Ben Hutchings wrote:
> > Multiple uploads of the same upstream version will have
> > the same package name, but those rarely happens.
> Those happen fairly often for urgent security updates.
We could encode that in the upstream version. Aka to have
Hi Ben
On Sun, Sep 24, 2023 at 06:05:09PM +0200, Ben Hutchings wrote:
> On Sun, 2023-09-24 at 15:01 +0200, Bastian Blank wrote:
> > The same upstream version in testing and backports will have the same
> > package name.
> This is not OK, because they will be incompatibl
Hi folks
Debian currently does Secure Boot signing using a shim chained to the
Microsoft key. This use requires that we follow certain rules. And one
of the recent changes to those rules state that our method of signing
kernel modules also with the same key will not be allowed anymore. Some
Control: severity -1 normal
On Fri, Sep 01, 2023 at 09:15:50AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> Helmut informed me that bugs that break bootstrap (rebootstrap fails to
> cross-build linux-libc-dev because of this bug) are usually filed with serious
> severity, so doing that now.
On Thu, Jul 06, 2023 at 09:39:43AM +0100, Luca Boccassi wrote:
> Yes I will bump the dependency in the next azcli upload, but I wanted
> to push the fix immediately.
Okay. Any reason for not just merging the two into one source? Can be
automated and you don't need to think about it again.
Hi Luca
>* New upstream version 20230705+git (Closes: #1040406)
Could you please describe how a new version of the azure module can fix
that? The dependency needs to be updated as well at least.
Also, how can it be that azure-cli is updated without the corresponding
azure?
Bastian
--
Package: python3-azure-cli
Version: 2.50.0-1
Severity: grave
azure-cli with all dependencies fullfilled does not allow "az" to run:
| % az vm -h
| The command failed with an unexpected error. Here is the traceback:
| No module named 'azure.mgmt.compute.v2022_11_01'
| Traceback (most recent call
Control: reassign -1 dkms
On Wed, Jul 05, 2023 at 10:53:19AM +0200, Vincent Lefevre wrote:
> On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote:
> > This needs to be fixed before linux 6.3.0-2-* can migrate to testing,
> > otherwise it will break dkms module building for everyone still having
>
Package: cloud.debian.org
Severity: serious
Hi Martin
Thanks for reporting this.
On Tue, Jun 20, 2023 at 08:03:48AM +0200, Martin Pitt wrote:
> This isn't done by any package postinst -- `grep -r netdev
> /var/lib/dpkg/info/*`
> shows no relevant hits. So this must be somewhere in the scripts
Control: reassign -1 src:linux
Control: severity -1 important
On Mon, Jun 12, 2023 at 05:31:53PM +0200, Andreas Beckmann wrote:
> As a consequence, if cruft *-dkms packages are still installed, but fail
> to build the module for current kernels, this may result in upgrade
> failures. Therefore
Source: youtube-dl
Version: 2021.12.17-2
Severity: serious
We have a maintained and uptodate fork of this package in the archive
and the release: yt-dlp. Do we really need to release this package in a
not so usable state?
Hint: transitional packages are supposed to be at the target of a
On Thu, May 11, 2023 at 06:25:00PM +0200, Guilhem Moulin wrote:
> On Thu, 11 May 2023 at 18:12:52 +0200, Bastian Blank wrote:
> > Nope, not really. Half VG was never a real thing. It might work in
> > some cases.
> And these use-cases are unbootable since 2.03.15…
Those
On Wed, May 10, 2023 at 03:09:04AM +0200, Guilhem Moulin wrote:
> There might be a better way to detect an initramfs-tools environment
> than checking whether ‘/run/initramfs’ exists (and ‘/run/systemd/system’
> doesn't).
The only acceptable way would be a different udev rules file for the
Hi
On Thu, Feb 09, 2023 at 03:16:15PM -0500, Theodore Ts'o wrote:
> Right, but if the conflict in e2fsprogs-udeb prevents the installer
> from pulling in an overly new version of e2fsprogs-udeb, that woul be
> sufficient, no?
No, it does not. Conflicts have undefined behaviour for udebs.
Package: ca-certificates-java
Version: 20230103
Severity: serious
ca-certificates-java fails to install with all dependencies fullfilled:
| Setting up ca-certificates-java (20230103) ...
| Exception in thread "main" java.lang.InternalError: Error loading
java.security file
| at
On Thu, Jan 19, 2023 at 10:32:04AM +0100, Andreas Beckmann wrote:
> > But it should not cause the kernel package install/upgrade to fail.
> > And that does seem in dkms' control afaict.
> We must not silently create an unbootable system.
Please stop failing the installation. I will NMU that in a
Control: reassign -1 dkms - breaks kernel installation
Control: severity -1 grave
On Tue, Jan 17, 2023 at 09:36:26AM +0100, Stefano Simonucci wrote:
> Package: src:linux
> Version: 6.0.12-1
> Severity: critical
> Justification: breaks the whole system
No, it does not. The kernel is the system
Package: cloud-initramfs-growroot
Version: 0.18.debian10
Severity: grave
Installation of new kernel now silently fails:
| Setting up linux-image-6.0.0-5-cloud-arm64 (6.0.10-2) ...
| /etc/kernel/postinst.d/initramfs-tools:
| update-initramfs: Generating /boot/initrd.img-6.0.0-5-cloud-arm64
| W:
Package: azure-cli
Version: 2.42.0-1
Severity: serious
Simple VM operations, like start, fail with ModuleNotFoundError. So some
dependencies are incorrect.
| % az vm start -h
| The command failed with an unexpected error. Here is the traceback:
| No module named
Package: mmdebstrap
Version: 1.2.1-2
Severity: serious
mmdebstrap writed "uninitialized" to /etc/machine-id. This triggers
first boot semantic[1], so makes the boot wait for input.
Please write an empty file if you are not equipped to handle first boot
questions.
Bastian
[1]:
On Wed, Sep 21, 2022 at 11:43:07AM +0100, Philip Wyett wrote:
> Upstream believes this to be an issue with GCC.
> See comment and reproducer code:
> https://trac.filezilla-project.org/ticket/12777#comment:1
> Needs to be reallocated to GCC.
Sorry, no, this is a bug in filezilla. The given
On Sat, Aug 13, 2022 at 10:41:09AM +0200, Carsten Schoenert wrote:
> > | Action: failed
> > | Final-Recipient: rfc822;c.schoen...@t-online.de
> > | Status: 5.0.0
> > | Remote-MTA: dns; mx02.t-online.de
> > | Diagnostic-Code: smtp; 554 IP=194.177.211.212 - A problem occurred. (Ask
> > your
Source: kicad-packages3d
Version: 6.0.7-1
Severity: serious
Mails sent by the archive to the maintainer are rejected with the
following message:
| Action: failed
| Final-Recipient: rfc822;c.schoen...@t-online.de
| Status: 5.0.0
| Remote-MTA: dns; mx02.t-online.de
| Diagnostic-Code: smtp; 554
On Mon, Jul 04, 2022 at 10:34:39PM +0200, Ansgar wrote:
> As a further test I tried a different PKCS#11 module:
Could you try the same with "openssl cms"? Just to make sure it's not
sign-file itself.
The complete command line I use to create signatures for kernel modules
is:
| openssl cms
Source: libpod
Version: 3.4.7+ds1-3
Severity: serious
Tags: ftbfs
libpod fails to build from source on several architectures:
|
| time="2022-05-19T21:23:53Z" level=error msg="Failed loading hooks for
/tmp/hooks-test-fallback-3506184749/a.json: parsing hook
Package: crun
Version: 0.17+dfsg-1.1+b1
Severity: serious
Moin
crun was not uploaded since before the release of Debian 11. It is now
seriously out of date and even fails hard as root, see #1012053.
Bastian
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT
Package: systemd
Version: 251.2-6
Severity: serious
systemd fails to build using the binutils from testing, aka it needs a
new build-dependency for them. Or autodetect if the option is
supported.
| FAILED: src/boot/efi/linuxx64.elf.stub
| /usr/bin/ld.bfd: unrecognized option
Control: severity -1 normal
Control: tags -1 wontfix
On Sat, Jun 18, 2022 at 09:52:41PM +0200, Thorsten Glaser wrote:
> /proc/sys/kernel/random/poolsize is now 256 instead of 4096 bits,
> which was already small before.
The pool size for an RPNG is only the size of the state, nothing else.
It
Package: selinux-policy-default
Version: 2:2.20220520-1
Severity: serious
Moin
selinux-policy-default fails to install into a basic Debian unstable
system:
Setting up selinux-policy-default (2:2.20220520-1) ...
Updating selinux default policy (this step might take a
Package: arptables
Version: 0.0.5-3
Severity: grave
arptables fails to install, using dpkg 1.21.2:
| Unpacking arptables (0.0.5-3) ...
| Setting up arptables (0.0.5-3) ...
| update-alternatives: using /usr/sbin/arptables-legacy to provide
/usr/sbin/arptables (arptables) in auto mode
|
Control: clone -1 -2
Control: retitle -2 googletest: ftbfs with GCC-11
Control: reassign -2 googletest
On Wed, Mar 03, 2021 at 04:17:56PM +, Matthias Klose wrote:
> In file included from
> /usr/src/googletest/googlemock/include/gmock/gmock-function-mocker.h:42,
> from
Control: severity -1 normal
On Fri, Dec 03, 2021 at 04:08:24PM -0500, Nicholas D Steeves wrote:
> Steps I used to try to reproduce:
>
> 1. Downloaded debian-testing-amd64-netinst.iso2021-12-03 16:21 408M
> 2. Installed to EFI-enabled qemu eg:
>kvm -bios /usr/share/ovmf/bios.bin -m 2G
Control: severity -1 important
On Thu, Sep 16, 2021 at 10:23:53AM +0200, Gert Wollny wrote:
> Package: src:linux
> Version: 5.14.3-1~exp1
> Severity: critical
> Justification: breaks the whole system
No, it does not. The kernel is the system.
Bastian
Control: notfound -1 linux/5.14.6-2
On Fri, Sep 24, 2021 at 09:29:50PM +0200, Paul Gevers wrote:
> Currently this regression is blocking the migration of linux and it's
> signed versions to testing [1]. Due to the nature of this issue, I filed
> this bug report against both packages. Can you
Package: libnginx-mod-http-lua
Version: 1.18.0-6.1
Severity: serious
The nginx source bundles the http-lua module in a version incompatible
with nginx 1.18. It segfaults immediately with a minimal config if a
"init_worker_by_lua_block" block is defined. (I haven't looked much
further.)
This
Package: sssd
Version: 2.4.1-2
Severity: serious
After upgrade from Buster, several components of sssd simply fail:
| ● sssd-nss.socket loaded failed failed
SSSD NSS Service responder socket
| sssd-pac.socket loaded active
Package: fuse3
Version: 3.10.3-1
Severity: serious
The fuse3 post installation script tries to modify permissions of
/dev/cuse. This is
- not it's job, but udev's,
- not persistent and
- fails if /dev is not writable.
Please drop that ill-adviced chmod.
Regards,
Bastian
-- System Information:
Control: severity -1 important
Control: tags -1 moreinfo
On Mon, Jun 07, 2021 at 08:43:21PM +0100, Anton Ivanov wrote:
> Version: 5.10.13-1~bpo10+1
This is not the latest version. 5.10.24 (at least) is in buster-backports.
> [801076.291139] scsi host10: uas
> [801076.291557] scsi 10:0:0:0:
Moin
On Thu, Feb 11, 2021 at 10:15:02AM +0800, YunQiang Su wrote:
> > Could the mips porters comment on this? Given that we're close to the
> > release
> > of bullseye, I'm not convinced it's a good idea to change this now.
This option is also a dependency of several types of CPU support. So
Control: sverity -1 important
On Wed, Feb 10, 2021 at 01:06:34PM +0300, Mc.Sim wrote:
> MEDIA ~ # grep kernel /var/log/syslog | grep "Code\|vgremove"
> Feb 10 11:28:37 MEDIA kernel: [ 1672.765313] vgremove[5983]: segfault at 40
> ip b7cb5b40 sp bfa75b98 error 4 in libc-2.24.so[b7c26000+1b1000]
Hi Ivo
On Mon, Feb 08, 2021 at 10:12:14AM +0100, Ivo De Decker wrote:
> I tried a rebuild of git 1:2.28.0-1, 1:2.29.2-1 and 1:2.30.0-1 in an unstable
> chroot on barriere.debian.org, and they all succeeded. It also seems the
> builds on the buildds succeeded for all the versions recently
Hi
To fix this cycle, which makes any package dependency on
default-jre-headless unstable, I propose to change the dependency in
ca-certificates-java to just specify openjdk-11-jre-headless, without
any default-jre-headless alternative.
Yes, this will cause the default java version to be
Control: tag -1 confirmed
Hi
On Sat, Jan 16, 2021 at 02:41:30PM +0100, Giacomo Mulas wrote:
> after the update of lvm2 packages to version 2.03.11-1 in sid,
> the lvmlockd.service fails to start and just hangs till
> systemctl times out and exits with an error. The previous version
> worked
Control: severity -1 important
Control: tags -1 help
I disabled the check in 5.10.1-1~exp1. There is no way to make the
kernel fit again without disabling major parts of it.
Downgrading the bug as nothing can be done.
Bastian
--
Lots of people drink from the wrong bottle sometimes.
Package: podman
Version: 2.1.1+dfsg1-3
Severity: grave
The podman version in unstable fails to run anything without root
permissions:
| $ podman run --rm --net host docker.io/library/debian:bullseye-slim echo
test; echo $?
| Error: open /proc/sys/net/ipv4/ping_group_range: Permission denied:
Package: git
Version: 1:2.29.2-1
Severity: serious
Some of the tests fail with dash, which is the default /bin/sh in
Debian.
Example:
| bbl@debian-sid:~/git-2.29.2+next.20201030/t$ bash ./t3070-wildmatch.sh | tail
-n 3
| # still have 40 known breakage(s)
| # passed all remaining 1850 test(s)
|
On Tue, Oct 27, 2020 at 04:54:13PM +0100, Thomas Goirand wrote:
> Testing to start the OpenStack image (well, the "genericcloud" image), I
> couldn't login into it, because there isn't any metadata service configured
> in it.
This is incorrect. The package uses
Package: git
Version: 1:2.28.0-1
Severity: serious
A rebuild of git 1:2.28.0-1 reports test failures and FTBFS on both unstable
and stable.
| expecting success of 0500.3 'progress display breaks long lines #1':
| sed -e "s/Z$//"
On Thu, Oct 01, 2020 at 09:54:05AM +0200, Paul Gevers wrote:
> https://ci.debian.net/data/autopkgtest/testing/amd64/v/varnish-modules/7232545/log.gz
Why is a simple ABI transition now also a autopkgtest failure?
| The following packages have unmet dependencies:
| varnish-modules : Depends:
Control: tag -1 moreinfo
Control: severity -1 important
On Tue, Sep 08, 2020 at 01:36:45PM +0200, Vincent Lefevre wrote:
> This version fails to load kernel modules (no issues with previous
> Linux kernels provided by Debian). As a consequence, X does not work.
> ** Loaded modules:
> rfcomm
>
Control: severity -1 important
On Mon, Aug 24, 2020 at 12:11:08PM +0200, Gianfranco Costamagna wrote:
> Hello, as explained on upstream ticket [1], the new kernel broke virtualbox,
> and the only fix that has been found
> so far is to export map_kernel_range and __get_vm_area_caller to modules
Package: mig
Version: 1.8-7
Severity: serious
mig mixes two incompatible licenses: GPL and a BSD derivative including
an advertisement clause (included in cpu.sym and message.h):
|and (3) all advertising
| materials mentioning features or use
Package: grub-efi-amd64-signed
Version: 1+2.04+5
Severity: grave
grub-efi-amd64-signed got a strict = dependency on grub-common, but
those packages are from different source packages. This makes this
package uninstallable.
| The following information may help to resolve the situation:
|
| The
Package: src:haproxy
Severity: serious
Mail to the maintainer address hapr...@tracker.debian.org bounces:
| host ticharich.debian.org [2607:f8f0:614:1::1274:64]
| SMTP error from remote mail server after RCPT
TO::
| 550 Unrouteable address
Do you mean
Package: shim-helpers-amd64-signed
Version: 1.33+15+1533136590.3beb971-7
Severity: grave
Binary packages in shim-signed and shim-unsigned have = dependencies,
leading to them being uninstallable:
| The following information may help to resolve the situation:
|
| The following packages have
Package: cloud-init
Version: 20.1-1
Severity: serious
cloud-init 20.1-1 fails to provision Azure:
| 2020-03-19 14:31:48,840 - util.py[DEBUG]: Running module disk_setup () failed
| Traceback (most recent call last):
| File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 848, in
Source: igraph
Version: 0.8.0-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: ftpmas...@debian.org
debian/copyright on igraph is incomplete. Examples:
- src/drl_layout_3d.cpp (BSD-3)
- src/CHOLMOD/Modify/cholmod_rowdel.c (Timothy A. Davis)
Please verify the whole copyright status.
Source: runit
Version: 2.1.2-35
Severity: critical
An installation attempt on a default system (with recommends enabled) of
runit wants to replace the installed init:
| $ sudo apt install runit
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| The
1 - 100 of 2211 matches
Mail list logo
