Hi
On Tue, Apr 23, 2024 at 09:20:08AM +0200, Bastian Blank wrote:
> On Tue, Apr 23, 2024 at 09:06:47AM +0200, Bastian Blank wrote:
> > On Tue, Apr 23, 2024 at 08:12:28AM +0200, bouv...@buxtehude.debian.org
> > wrote:
> > > FWIW, and following Jacob Rhoads' remark, we are
Control: tags -1 moreinfo
On Sat, May 18, 2024 at 10:49:34AM +0200, Manny wrote:
> ** Tainted: OE (12288)
> * externally-built ("out-of-tree") module was loaded
> * unsigned module was loaded
>
> ** Loaded modules:
> tp_smapi(OE)
> thinkpad_ec(OE)
You run with modules that modify low level
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
On Tue, Apr 23, 2024 at 09:06:47AM +0200, Bastian Blank wrote:
> On Tue, Apr 23, 2024 at 08:12:28AM +0200, bouv...@buxtehude.debian.org wrote:
> > FWIW, and following Jacob Rhoads' remark, we are also running CrowdStrike
> > Falcon Sensor on all our machines, virtuals servers an
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: ftp.debian.org
Severity: normal
X-Debbugs-Cc: s...@packages.debian.org, bdr...@debian.org, on...@debian.org,
wa...@debian.org
Control: affects -1 + src:salt
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove package salt. It was not released in stable. No response
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
On Tue, Apr 02, 2024 at 03:26:32PM +, Colm Buckley wrote:
> This is a real problem - however I think it is *not* one which the change
> in dependency addresses; even if -headers-Y depends on -image-Y, step 3
> above will proceed without any conflicts (because the reverse dependency is
>
On Tue, Apr 02, 2024 at 03:59:25PM +0100, Luca Boccassi wrote:
> Let's look at this the other way around: if there was no dependency, in
> what scenario would things break and how?
- linux-headers-bla and linux-image-bla are installed
- linux-image-bla is uipgraded
- no modules will be built,
On Mon, Apr 01, 2024 at 09:25:40PM +, Luca Boccassi wrote:
> Why do dkms modules need the image installed to be built? At the very
> least they didn't use to, the headers were enough last time I had to
> deal with that stuff for the nvidia drivers
dkms is used to build modules for the kernel
On Mon, Apr 01, 2024 at 08:39:06PM +, Debian Bug Tracking System wrote:
> No. We need to make sure someone installing linux-image-bla and
> linux-headers-bla have the same version, so the modules are compatible.
Revisiting this bug, I might have been not explicit enough. This
dependency is
Control: tags -1 wontfix
On Thu, Feb 29, 2024 at 01:38:12PM +0100, Bastian Blank wrote:
> On Thu, Feb 29, 2024 at 12:12:21PM +, Luca Boccassi wrote:
> > With the new vmlinux.h shipped in the headers package, the BTF case
> > should be covered.
As said, this dependency is to m
On Sat, Mar 30, 2024 at 12:44:35PM -0700, Ross Vandegrift wrote:
> Finally, apologies for not being able to do this myself - I still do not have
> my account setup for access to core machines.
Tasks related to this incident are tracked here:
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
Control: severity -1 serious
Control: reopen -1
Hi
As you might have found out, binnmu don't work with signed packages.
This needs a source rebuild.
Bastian
--
Totally illogical, there was no chance.
-- Spock, "The Galileo Seven", stardate 2822.3
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
On Tue, Mar 26, 2024 at 12:53:42PM +0100, Alessandro Vesely wrote:
> I compiled the example program given in the inet_pton(3) man page, and obtain
> the following:
> $ ./a.out i6 0:0:0::5.6.7.8
> Not in presentation format
This is no valid IPv6 address. Where did you find that?
Bastian
--
On Sun, Mar 24, 2024 at 12:04:35AM -0700, Kingsley G. Morse Jr. wrote:
> As you can see below, lines 25 and 26 of the hook
> script look in a path starting with "/lib"
>
> [...]
> 25 elif [ -e /lib/udev/rules.d/$rules ]; then
> 26 cp -p /lib/udev/rules.d/$rules
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
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 11:28:12AM +, Luca Boccassi wrote:
> > But we where talking about kernel modules.
> There are kernel modules using BPF stuff? Never seen one, do you have
> an example?
No idea, but they get linked BTF information, so you could use them.
Bastian
--
Those who hate and
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.
> >
> >
On Sat, Mar 02, 2024 at 12:40:07AM +, Luca Boccassi wrote:
> Yes precisely, the bpf program source can just include vmlinux.h and it
> should build and run as expected.
But we where talking about kernel modules.
Bastian
--
Vulcans never bluff.
-- Spock, "The Doomsday
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.
Please be a bit more precise, there are no symlinks in this directory.
| # dpkg -S /usr/alpha-linux-gnu/include/asm/a.out.h
| linux-libc-dev-alpha-cross:
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
On Thu, Feb 29, 2024 at 12:12:21PM +, Luca Boccassi wrote:
> With the new vmlinux.h shipped in the headers package, the BTF case
> should be covered.
The relevant code in Linux is:
| quiet_cmd_btf_ko = BTF [M] $@
| cmd_btf_ko = \
|
On Thu, Feb 29, 2024 at 11:03:11AM +, Colm Buckley wrote:
> Why was this never the case before? And can you be more precise about what
> "stuff" is missing? Is there a previous bug report I can reference?
It complains loudly about BTF.
> DKMS should handle its own dependencies, I'd have
Control: tags -1 wontfix
On Wed, Feb 28, 2024 at 05:19:39PM +, Colm Buckley wrote:
> The linux-headers packages for kernel version 6.6 seem to depend on the
> corresponding
> linux-image packages, but I believe that this should not be the case (and was
> not the
> case in previous
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
On Mon, Feb 26, 2024 at 02:20:41PM +0100, Julian Andres Klode wrote:
> After we had discussed the new proposal a couple months ago and were
> left with severe open questions and concerns it seems that these have
> been ignored and the packages uploaded anyway, breaking APT's algorithm
> that
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
On Fri, Feb 23, 2024 at 02:53:58PM +0100, Thomas Lange wrote:
> # set default dirs if FAI_RAMDISKS not already set
> -: ${FAI_RAMDISKS:="$target/var/lib/dpkg"}
> +: ${FAI_RAMDISKS="$target/var/lib/dpkg"}
> @wwaldi: Do you think it's still wrong?
I don't know that syntax. A proper solution would
The problem is:
| : ${FAI_RAMDISKS:="$target/var/lib/dpkg"}
:= sets the variable if it is unset _or empty_. So just defining
FAI_RAMDISKS="" does not work.
The definition of this variable needs to be moved up one tool into fai
itself, so it can provide an empty value.
Bastian
--
The sooner
The command just outputs:
| W: qemu-debootstrap is deprecated. Please use regular debootstrap directly
So the selection between debootstrap and qemu-debootstrap should just go
completely.
Bastian
--
Where there's no emotion, there's no motive for violence.
-- Spock, "Dagger of
Package: fai-client
Version: 6.0.5
Severity: important
X-Debbugs-Cc: wa...@debian.org
It is impossible to disable the use of mkramdisk. By default this tries
to setup a tmpfs for /var/lib/dpkg and does scary copy operations.
It expects an environment variable from the outside, which can never
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
Package: fai-client
Version: 6.0.5
Severity: normal
X-Debbugs-Cc: wa...@debian.org
qemu-debootstrap is deprecated since several Debian releases and should
not longer be used.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (700, 'testing'), (500,
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"
Hi Safir
On Sun, Jan 28, 2024 at 11:21:05PM +, Safir Secerovic wrote:
> I have a custom hook that omits a kernel module being built into an initrd
> image.
So it is a bug in your hook itself?
> Until kernels 6.6 and above, the hook does not seem to take effect.
> The module is not omitted
Control: tags -1 wontfix
On Wed, Jan 24, 2024 at 06:13:05PM +0100, Paul Menzel wrote:
> Trying to quickly start a VM, it’d be great to not use an initrd image, and
> also use the Virtio features, for example with the command below:
Please use virtiofs in this case.
> qemu-system-x86_64 -M
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.
Control: tags -1 moreinfo
On Mon, Jan 08, 2024 at 05:48:46PM +, Andrew Jorgensen wrote:
> The patch was released in Linux 6.7:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7=a18615b1cfc04f00548c60eb9a77e0ce56e848fd
> It's been backported to 5.15 in the LTS
Package: glibc
Version: 2.37-13
Severity: important
Currently the autopkgtest on arm64 fails sometimes.
Timeout while building:
https://ci.debian.net/packages/g/glibc/unstable/arm64/41516611/
Failed test:
https://ci.debian.net/packages/g/glibc/testing/arm64/40439311/
--
There is an order of
Package: apt
Version: 2.7.7
Severity: wishlist
As discussed around #1040901, we need an alternative way to correlate
between package and kernel. In apt this directly affects how
APT::VersionedKernelPackages works, which cares about which package
could match the current running kernel.
How it
Control: reassign -1 dkms
dkms fails the kernel installation.
On Wed, Jan 03, 2024 at 10:54:12PM +0100, T. J. Pinkert wrote:
> Error! The /var/lib/dkms/zfs/2.1.11/6.1.0-17-rt-amd64/x86_64/dkms.conf for
> module zfs includes a BUILD_EXCLUSIVE directive which does not match this
>
On Wed, Jan 03, 2024 at 11:49:12AM +0100, Andreas Beckmann wrote:
> How will it work in the future for the user that wants an out-of-tree module
> to get the right headers for his kernel?
Unclear. I don't see this as solvable with existing tools. You will
always need to get the current kernel
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: wishlist
Please stop recommending any linux-headers packages. The dependencies
inside the linux packaging have been shifted and pulling in headers will
now always pull in the image as well. This will break systems for now,
if you manage to pull in a
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
Package: autopkgtest
Severity: wishlist
Our Linux package makes heavy use of build profiles. Those can be used
to disable various parts of the build and this functionality is used in
our CI.
Now comes autopkgtest, tries to install all test dependencies and fails
if those packages have been
On Mon, Jan 01, 2024 at 10:33:10PM +0100, Bastian Blank wrote:
> Turns out this requires more work. Currently it is not possible to
> build some tests.
I'll remove the current selftest stuff.
This needs much more work, too much work for now. The runner does not
support recursive test sel
On Sun, Dec 31, 2023 at 06:33:29PM +0100, Bastian Blank wrote:
> On Sun, Dec 31, 2023 at 04:47:28PM +0100, Paul Gevers wrote:
> > Recently I added some isolation-machine support to ci.debian.net and one of
> > the first packages I tried to run the test for is src:linux.
> D
> This system is not supported. Closing the bug report. Please don't
> open new ones until your system is in a supported state.
You where already told the same in #1027697. Please don't come back.
Regards,
Bastian
--
Spock: We suffered 23 casualties in that attack, Captain.
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,
Package: cross-toolchain-base
Since Linux 6.6, the linux-libc-dev package in Debian is arch-all and
includes headers in the appropriate multiarch include paths for all
actually existing Debian architectures. Ubuntu also plans or already
did that change as well.
To finish this transition (which
On Sun, Dec 31, 2023 at 04:47:28PM +0100, Paul Gevers wrote:
> Recently I added some isolation-machine support to ci.debian.net and one of
> the first packages I tried to run the test for is src:linux.
Do you have a handy script available to try this by hand? I was just
looking at this test (to
Control: tags -1 help
Control: severity -1 normal
On Sun, Dec 31, 2023 at 12:49:54PM +0100, Jarl Gullberg wrote:
> dmsetup-udeb does not include any of the udev rules that come with the
> standard
> package, resulting in device nodes under /dev/mapper not being created for
> partitions of
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 Wed, Dec 20, 2023 at 12:13:09PM +0100, Luca Boccassi wrote:
> Please remove the i386 build of src:dpdk-kmods from Debian Testing and
> Unstable. The new src:dpdk 23.11-1 version, just uploaded to unstable,
> no longer builds for this architecture, so we don't need the ancillary
> kernel modules
Control: severity -1 serious
Control: fixed -1 6.1.0-1
This problem makes flake8 completely broken. The version in unstable
fixes that. I've fixed both the severity and the version information.
Bastian
--
A woman should have compassion.
-- Kirk, "Catspaw", stardate 3018.2
On Thu, Dec 07, 2023 at 12:30:20PM +1000, progserega wrote:
>* I create logical volume 'root_deb' on hdd and its writeback cache on ssd
> (nvme). And also I create logical volume 'home' and its cache on nvme.
>* All works. But after reboot PC - I get big value CacheDirtyBlocks for
>
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 Sat, Nov 25, 2023 at 10:30:39AM +0100, Bastian Blank wrote:
> Thank you for purposefully not mentioning that this only applies if you
> use the bothed(?) gcc spec override to build with musl instead of glibc.
> Can you show it is broken if using the standard toolchain
Hi
On Sat, Oct 28, 2023 at 07:57:54PM +1300, rhys wrote:
> char myBuf[] = { '\x01', '\x04', '\x31', '\x00', '\x00', '\x1D', '\x7E',
> '\xF7' };
> printf ("sizeof (myBuf) = %d\n", sizeof (myBuf));
This is an array, so sizeof() shows the length of that array. Making it
longer would have
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
On Thu, Oct 19, 2023 at 07:31:08PM +0200, Alexis CAMILLERI wrote:
> I suggest using grub-probe -t disk instead of grub-probe -t device.
> Disk param will return the disk name instead of the partition, so the sed
> command can be removed and raid device will work.
>
> local basedev=$(grub-probe -t
On Thu, Oct 19, 2023 at 07:31:08PM +0200, Alexis CAMILLERI wrote:
> Installing grub on an i386 server with raid partitioning does not work
> because the script does not manage a raid mount for /boot, due to
>
Package: security-tracker
Severity: important
The security tracker currently uses the JSON feeds as linked from
https://nvd.nist.gov/vuln/data-feeds. Those data feeds will be retired
on December, 15th 2023, so in a bit more then two months. After that
the information will be only available via
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
Hi Lucas
On Fri, Sep 22, 2023 at 08:42:10AM +0200, Lucas Nussbaum wrote:
> Could we use the Debian AWS account to host that service?
I would assume that a service like snapshot would be within the scope
for our AWS usage. Noah?
> It
Control: tag -1 moreinfo
Hi Klaus
On Fri, Sep 15, 2023 at 10:18:55PM +0100, Klaus Ethgen wrote:
> Booting with the new kernel makes the display (1920x1200) heavily
> flckering, diplaying two times the same one above the other and only
> displaying about 1/4 of the screen smashed together on the
On Mon, Sep 11, 2023 at 01:06:06PM +0100, Luca Boccassi wrote:
> As far as I understand dpkg's conffile machinery should recognize if
> you changed anything, and leave it in place. Upstream moved the
> default ones to /usr, so we just follow what they do.
Actually using rm_conffile is wrong.
On Thu, Sep 07, 2023 at 05:50:41PM +0200, Bastian Blank wrote:
> When the following commit is includes:
Just for background information: cloud-init depends on isc-dhcp-client
because it uses the dhclient binary. So removing that as dependency is
not feasible right now.
Bastian
--
Fascinat
On Thu, Sep 07, 2023 at 05:36:06PM +0200, Michael Prokop wrote:
> Please consider adapting the Depends for the new cloud-init version
> in Debian accordingly, so one can use e.g. cloud-init with udhcpc
> (which also allows co-installation next to dhcpcd), but without
> having to also have
.
While the stock driver in 6.1 kind of works, it is not really usable for
end user workloads.
On Tue, May 02, 2023 at 01:38:40PM +0200, Bastian Blank wrote:
> Microsoft asked to backport the jumbo frame support in the Microsoft
> Azure Network Adapter from current master. The c
Hi Laurent
On Sun, Sep 03, 2023 at 11:16:03AM +0200, Laurent BRULET wrote:
> It's still not entirely clear to me, whether this transient issue (where
> linux-
> image-amd64 can be installed while the corresponding linux-headers-amd64
> can't)
> is a "standard case" for backports, or it is an
On Sun, Sep 03, 2023 at 10:02:16AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> so rebootstrap uses the stage1 build profile which should be building headers
> only. Still it fails with the same error I've reported for a full build:
The stage1 profile is deprecated according to the
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. Thanks!
Cross-building
On Fri, Sep 01, 2023 at 08:36:53AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> diff -Nru linux-6.4.11/debian/rules.real linux-6.4.11/debian/rules.real
> --- linux-6.4.11/debian/rules.real 2023-08-17 09:05:43.0 +0200
> +++ linux-6.4.11/debian/rules.real 2023-09-01
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.
Control: tags -1 moreinfo
Hi Dmitry
On Wed, Aug 23, 2023 at 08:10:17PM +0300, Dmitry Baryshkov wrote:
> The linux-libc-dev package provides only a limited set of uAPI headers.
> For example, scsi, drm, video, etc. headers are missing from the
> package.
scsi headers are shipped by libc6-dev,
1 - 100 of 4707 matches
Mail list logo
