Control: tags -1 upstream
Controm: forwarded -1
https://gitlab.com/apparmor/apparmor/-/blob/692e6850ba90582105713a683bed753bad696aab/kernel-patches/v4.17/0002-apparmor-af_unix-mediation.patch
On Thu, Jan 16, 2025 at 02:16:18PM +0100, Guido Berhoerster wrote:
> From my superficial reading of the c
Control: tags -1 upstream
Controm: forwarded -1
https://gitlab.com/apparmor/apparmor/-/blob/692e6850ba90582105713a683bed753bad696aab/kernel-patches/v4.17/0002-apparmor-af_unix-mediation.patch
On Thu, Jan 16, 2025 at 02:16:18PM +0100, Guido Berhoerster wrote:
> From my superficial reading of the c
Package: pahole
Version: 1.28-1
Severity: normal
X-Debbugs-Cc: wa...@debian.org
pahole is used by the Linux kernel. To allow use for cross compilation
and such, please mark it as multi-arch foreign, as the tool is actually
not restricted to one architecture.
Bastian
-- System Information:
Debia
On Thu, Jan 09, 2025 at 08:58:38AM +, Ilya Leoshkevich wrote:
> I'm trying to bootstrap gcc from git master with multilib on debian 12.
> As far as I can see all the necessary cross packages are installed.
How do you configure GCC to support the Debian multi-arch include
layout? Also direct s
On Thu, Jan 09, 2025 at 08:58:38AM +, Ilya Leoshkevich wrote:
> I'm trying to bootstrap gcc from git master with multilib on debian 12.
> As far as I can see all the necessary cross packages are installed.
How do you configure GCC to support the Debian multi-arch include
layout? Also direct s
On Tue, Jan 07, 2025 at 09:25:13AM +, Mark Hindley wrote:
> Proposed patch attached. Do you have any comments on it?
I would say: the loop can now also go. Otherwise looks fine.
Bastian
--
Bones: "The man's DEAD, Jim!"
On Tue, Jan 07, 2025 at 09:25:13AM +, Mark Hindley wrote:
> Proposed patch attached. Do you have any comments on it?
I would say: the loop can now also go. Otherwise looks fine.
Bastian
--
Bones: "The man's DEAD, Jim!"
On Mon, Jan 06, 2025 at 12:56:08PM +0100, Chris Hofstaedtler wrote:
> * Bastian Blank [250106 11:22]:
> > On Sat, Jan 04, 2025 at 03:56:16PM +0100, Chris Hofstaedtler wrote:
> > > Hi s390x porters,
> > >
> > > DSA (Debian System Administrators) relies
On Mon, Jan 06, 2025 at 12:56:08PM +0100, Chris Hofstaedtler wrote:
> * Bastian Blank [250106 11:22]:
> > On Sat, Jan 04, 2025 at 03:56:16PM +0100, Chris Hofstaedtler wrote:
> > > Hi s390x porters,
> > >
> > > DSA (Debian System Administrators) relies
On Mon, Jan 06, 2025 at 12:56:08PM +0100, Chris Hofstaedtler wrote:
> * Bastian Blank [250106 11:22]:
> > On Sat, Jan 04, 2025 at 03:56:16PM +0100, Chris Hofstaedtler wrote:
> > > Hi s390x porters,
> > >
> > > DSA (Debian System Administrators) relies
On Sat, Jan 04, 2025 at 03:56:16PM +0100, Chris Hofstaedtler wrote:
> Hi s390x porters,
>
> DSA (Debian System Administrators) relies on samhain for the
> debian.org infrastructure.
>
> On Wed, Dec 25, 2024 at 01:33:11AM +0100, Chris Hofstaedtler wrote:
> > samhain previously built on s390x but n
On Sat, Jan 04, 2025 at 03:56:16PM +0100, Chris Hofstaedtler wrote:
> Hi s390x porters,
>
> DSA (Debian System Administrators) relies on samhain for the
> debian.org infrastructure.
>
> On Wed, Dec 25, 2024 at 01:33:11AM +0100, Chris Hofstaedtler wrote:
> > samhain previously built on s390x but n
On Sat, Jan 04, 2025 at 03:56:16PM +0100, Chris Hofstaedtler wrote:
> Hi s390x porters,
>
> DSA (Debian System Administrators) relies on samhain for the
> debian.org infrastructure.
>
> On Wed, Dec 25, 2024 at 01:33:11AM +0100, Chris Hofstaedtler wrote:
> > samhain previously built on s390x but n
elog
index 6deaa306729c42c98d9c281530c45cc8918da535..f3da58877e3391f4692cb6fcf53d3b517fcb0791 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+systemd (252.33-1~deb12u1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport PR#32194. (closes: #1081633)
+
+
elog
index 6deaa306729c42c98d9c281530c45cc8918da535..f3da58877e3391f4692cb6fcf53d3b517fcb0791 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+systemd (252.33-1~deb12u1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport PR#32194. (closes: #1081633)
+
+
elog
index 6deaa306729c42c98d9c281530c45cc8918da535..f3da58877e3391f4692cb6fcf53d3b517fcb0791 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+systemd (252.33-1~deb12u1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport PR#32194. (closes: #1081633)
+
+
Package: sysvinit-core
Version: 3.11-1
Severity: serious
X-Debbugs-Cc: wa...@debian.org
Running the trigger of sysvinit-core unconditionally kills a pid 1 that
is not sysvinit. This process will not respond to the same signal
protocol and just die.
| root@c9570f76c33b:/# ps aux
| USER PI
Package: sysvinit-core
Version: 3.11-1
Severity: serious
X-Debbugs-Cc: wa...@debian.org
Running the trigger of sysvinit-core unconditionally kills a pid 1 that
is not sysvinit. This process will not respond to the same signal
protocol and just die.
| root@c9570f76c33b:/# ps aux
| USER PI
Hi
On Fri, Sep 13, 2024 at 12:34:11PM +0200, Bastian Blank wrote:
> Could you please backport the support for changing this default from
> #32194?
I did not get any response to this bug report. If I don't get
anything, I'll handle that with the release team on my own, but it mig
Hi Luca
On Sat, Dec 21, 2024 at 03:36:03PM +0100, Bastian Blank wrote:
> So please either
> - restore the upstream default of color disabled by default, or
> - use a better usable color scheme (yes, I know this is hard with how
> colors work on usual termionals).
Please ack
Hi Luca
On Sat, Dec 21, 2024 at 03:36:03PM +0100, Bastian Blank wrote:
> So please either
> - restore the upstream default of color disabled by default, or
> - use a better usable color scheme (yes, I know this is hard with how
> colors work on usual termionals).
Please ack
Hi
On Fri, Sep 13, 2024 at 12:34:11PM +0200, Bastian Blank wrote:
> Could you please backport the support for changing this default from
> #32194?
I did not get any response to this bug report. If I don't get
anything, I'll handle that with the release team on my own, but it mig
On Fri, Dec 06, 2024 at 08:56:38PM +0100, Sven Geuer wrote:
> If you agree to this ITS please state your consent right away so that I
> can upload an updated package near-term.
Sorry for the silence. You are right, I'm able to properly care for
this package. So please go ahead.
I can just move
Control: tags -1 - wontfix
Control: reopen -1
Hi Luca
On Sat, Nov 30, 2024 at 11:39:31AM +, Luca Boccassi wrote:
> See the manpage, you can set COLORFGBG in your shell profile according
> to your configuration.
> There are no patches or color choices downstream, it's just what
> upstream prov
Control: tags -1 - wontfix
Control: reopen -1
Hi Luca
On Sat, Nov 30, 2024 at 11:39:31AM +, Luca Boccassi wrote:
> See the manpage, you can set COLORFGBG in your shell profile according
> to your configuration.
> There are no patches or color choices downstream, it's just what
> upstream prov
On Mon, Dec 16, 2024 at 09:02:36PM -0500, InterLinked wrote:
> The Debian 12 installer (any minor version) fails to install on HyperV
> on Windows Server 2008 R2. For demonstration purposes, I am using the
> debian-12.6.0-amd64-netinst ISO installer.
Windows Server 2008 R2 is EOL since a few years
On Mon, Dec 16, 2024 at 09:02:36PM -0500, InterLinked wrote:
> The Debian 12 installer (any minor version) fails to install on HyperV
> on Windows Server 2008 R2. For demonstration purposes, I am using the
> debian-12.6.0-amd64-netinst ISO installer.
Windows Server 2008 R2 is EOL since a few years
On Sun, Dec 08, 2024 at 03:55:38AM +0100, Cyril Brulebois wrote:
> I see upstream seems to have renamed something:
>
> -## choice: Module compression mode
> +## choice: Module compression type
> CONFIG_MODULE_COMPRESS_XZ=y
> ## end choice
>
> but that seems to be about setting a
On Sun, Dec 08, 2024 at 03:55:38AM +0100, Cyril Brulebois wrote:
> I see upstream seems to have renamed something:
>
> -## choice: Module compression mode
> +## choice: Module compression type
> CONFIG_MODULE_COMPRESS_XZ=y
> ## end choice
>
> but that seems to be about setting a
Control: notfound -1 6.1.0-28-amd64
Control: forcemerge 1086175 -1
On Fri, Dec 06, 2024 at 01:09:46PM +0100, Vincent Roch wrote:
> After installing Debian 12.7 (Bookworm) using the official netinst ISO, the
> system encountered a Kernel Panic during a shutdown or reboot when the
> `mdadm` utility
Control: notfound -1 6.1.0-28-amd64
Control: forcemerge 1086175 -1
On Fri, Dec 06, 2024 at 01:09:46PM +0100, Vincent Roch wrote:
> After installing Debian 12.7 (Bookworm) using the official netinst ISO, the
> system encountered a Kernel Panic during a shutdown or reboot when the
> `mdadm` utility
Control: notfound -1 6.1.0-28-amd64
Control: forcemerge 1086175 -1
On Fri, Dec 06, 2024 at 01:09:46PM +0100, Vincent Roch wrote:
> After installing Debian 12.7 (Bookworm) using the official netinst ISO, the
> system encountered a Kernel Panic during a shutdown or reboot when the
> `mdadm` utility
On Thu, Dec 05, 2024 at 08:38:35AM +0100, Helmut Grohne wrote:
> This is the stage I am concerned about. You claim that it would not
> matter whether the package is all or any, but my experience is
> otherwise. With the exception of linux, the cross bootstrap tooling does
> not build any Arch:all p
On Thu, Dec 05, 2024 at 08:38:35AM +0100, Helmut Grohne wrote:
> This is the stage I am concerned about. You claim that it would not
> matter whether the package is all or any, but my experience is
> otherwise. With the exception of linux, the cross bootstrap tooling does
> not build any Arch:all p
On Thu, Oct 24, 2024 at 01:29:31AM +0200, Ben Hutchings wrote:
> On Sat, 2024-10-19 at 15:35 +0200, Bastian Blank wrote:
> > I have to disagree. With this setup, we can support architectures that
> > are neither known by dpkg nor dak. This was not possible before and
> > r
On Thu, Oct 24, 2024 at 01:29:31AM +0200, Ben Hutchings wrote:
> On Sat, 2024-10-19 at 15:35 +0200, Bastian Blank wrote:
> > I have to disagree. With this setup, we can support architectures that
> > are neither known by dpkg nor dak. This was not possible before and
> > r
On Sat, Oct 19, 2024 at 06:15:57PM +0200, Helmut Grohne wrote:
> On Sat, Oct 19, 2024 at 03:35:21PM +0200, Bastian Blank wrote:
> > On Thu, Oct 10, 2024 at 06:03:24PM +0200, Helmut Grohne wrote:
> > > A. Multi-Arch: foreign is a lie
> > All the examples of yours will im
On Sat, Oct 19, 2024 at 06:15:57PM +0200, Helmut Grohne wrote:
> On Sat, Oct 19, 2024 at 03:35:21PM +0200, Bastian Blank wrote:
> > On Thu, Oct 10, 2024 at 06:03:24PM +0200, Helmut Grohne wrote:
> > > A. Multi-Arch: foreign is a lie
> > All the examples of yours will im
This bug actually shows up on the buildds. It is just hidden by
ignoring errors:
| Transcript written on cookbook.log.
| pdflatex returned an error, check the log file
| scons: *** [debian/tmp3/posix/doc/cookbook/cookbook.pdf] Error 1
https://buildd.debian.org/status/fetch.php?pkg=python-escript
This bug actually shows up on the buildds. It is just hidden by
ignoring errors:
| Transcript written on cookbook.log.
| pdflatex returned an error, check the log file
| scons: *** [debian/tmp3/posix/doc/cookbook/cookbook.pdf] Error 1
https://buildd.debian.org/status/fetch.php?pkg=python-escript
Hi
This weeks meeting will happen today at 20:00 UTC in #debian-kernel.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meetings/-/wikis/20241127
Please reply here if you would like to add more points.
Bastian
--
Another Armenia, Belgium ... the weak innocents who a
On Fri, Nov 22, 2024 at 06:14:13PM -0600, Ava wrote:
> debootstrap --exclude=systemd-sysv doesn't work. The option is completely
> ignored.
Could you please describe your goal? If you want to exclude the init
system, using "--variant=minbase" should help.
Bastian
--
There's a way out of any c
Hi Jaak
On Sat, Nov 23, 2024 at 12:04:46AM +0200, Jaak Ristioja wrote:
> I'm thinking of bisecting this. Any ideas where I could find a set of
> suitable pre-built kernels to speed things up?
There is snapshot.debian.org, which stores old versions of packages. It
might miss some, but it is still
Hi Jaak
On Sat, Nov 23, 2024 at 12:04:46AM +0200, Jaak Ristioja wrote:
> I'm thinking of bisecting this. Any ideas where I could find a set of
> suitable pre-built kernels to speed things up?
There is snapshot.debian.org, which stores old versions of packages. It
might miss some, but it is still
On Fri, Nov 22, 2024 at 06:14:13PM -0600, Ava wrote:
> debootstrap --exclude=systemd-sysv doesn't work. The option is completely
> ignored.
Could you please describe your goal? If you want to exclude the init
system, using "--variant=minbase" should help.
Bastian
--
There's a way out of any c
Hi Jeak
On Sun, Nov 10, 2024 at 01:10:11AM +0200, Jaak Ristioja wrote:
> I'm experiencing a black screen and system freeze when Xorg starts on Debian
> Trixie on a HP Compaq DC7800 Small Form Factor computer. No SSH, no ping, no
> VT switching, no sysrq.
> [0.00] DMI: Hewlett-Packard HP C
Hi Jeak
On Sun, Nov 10, 2024 at 01:10:11AM +0200, Jaak Ristioja wrote:
> I'm experiencing a black screen and system freeze when Xorg starts on Debian
> Trixie on a HP Compaq DC7800 Small Form Factor computer. No SSH, no ping, no
> VT switching, no sysrq.
> [0.00] DMI: Hewlett-Packard HP C
Hi
Our next team meeting is scheduled for 2024-11-13 21:00 UTC, please note
the changed time. We'll be on jitsi:
https://jitsi.debian.social/DebianCloudMeeting20241113.
Regards,
Bastian
--
"Evil does seek to maintain power by suppressing the truth."
"Or by misleading the innoce
Hi
Our regular meeting is scheduled for this Wednesday. We did not manage
to do a meeting since August, but I have some stuff to talk about, so it
would be nice if we would manage that.
Due to the time change, I now have a conflicting meeting. Could we
move this one here to 2100 UTC (so matchin
On Fri, Nov 08, 2024 at 06:54:26AM +0100, Ansgar 🙀 wrote:
> On Thu, 2024-11-07 at 15:46 +, Matthew Vernon wrote:
> > On 07/11/2024 10:03, Helmut Grohne wrote:
> > > Indeed, we can lift Bastian's mail into a proper proposal. Logging
> > > services are generally assumed to be available. It become
On Fri, Nov 08, 2024 at 06:54:26AM +0100, Ansgar 🙀 wrote:
> On Thu, 2024-11-07 at 15:46 +, Matthew Vernon wrote:
> > On 07/11/2024 10:03, Helmut Grohne wrote:
> > > Indeed, we can lift Bastian's mail into a proper proposal. Logging
> > > services are generally assumed to be available. It become
On Thu, Nov 07, 2024 at 03:27:31PM +, Jeremy Stanley wrote:
> On 2024-11-07 10:22:09 -0500 (-0500), Nick Lockheart wrote:
> [...]
> > Is the virtual CD-ROM drive one of the missing drivers? I think that's
> > how virt-install passes the cloud-init data- as a mounted CDROM disk.
>
> Yes, this h
On Mon, Oct 28, 2024 at 11:04:02AM +0100, Helmut Grohne wrote:
> On Mon, Oct 28, 2024 at 04:37:06PM +0800, Sean Whitton wrote:
> > I think I see a way to distinguish these four cases in a way that gets
> > everyone what they want.
> >
> > systemd adds an *empty* binary package
> > Package: sys
On Mon, Oct 28, 2024 at 11:04:02AM +0100, Helmut Grohne wrote:
> On Mon, Oct 28, 2024 at 04:37:06PM +0800, Sean Whitton wrote:
> > I think I see a way to distinguish these four cases in a way that gets
> > everyone what they want.
> >
> > systemd adds an *empty* binary package
> > Package: sys
On Wed, Nov 06, 2024 at 07:57:41PM +0100, Bastian Blank wrote:
> We will rename the branches in the linux git repository in a short
> while.
This will happen tomorrow, 2024-11-07 from 1800 UTC.
Bastian
--
Warp 7 -- It's a law we can live with.
Hi folks
We will rename the branches in the linux git repository in a short
while. This will incorporate the spirit of DEP 14 with a bit of special
sauce.
The HEAD branch, currently called master, will become debian/latest.
All the other suite specific branches will be updated to
"debian//", ak
On Fri, Oct 04, 2024 at 12:50:36PM +0200, Daniel Baumann wrote:
> On 10/4/24 09:16, Bastian Blank wrote:
> > What is the plan to get this fixed?
> I'm working on getting all required build-depends in debian, but I can
> also just remove the non-free bits until thats done.
On Fri, Oct 04, 2024 at 12:50:36PM +0200, Daniel Baumann wrote:
> On 10/4/24 09:16, Bastian Blank wrote:
> > What is the plan to get this fixed?
> I'm working on getting all required build-depends in debian, but I can
> also just remove the non-free bits until thats done.
Hi
This weeks meeting will happen today at 20:00(!) UTC in #debian-kernel.
Due to return to standard time in Europe, future meetings will happen
one hour later (at 21:00 MET/MEST). Please note the change in place.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meeting
Hi
On Sun, Oct 27, 2024 at 07:13:00AM +0100, Salvatore Bonaccorso wrote:
> The tracking here is already correct. The shipped source is affected
> but the security impact is not present, as binaries are not built.
> this is already sufficiently reflected with the ignored note.
It is correct, as i
Control: tag -1 moreinfo
Hi
On Tue, Oct 15, 2024 at 12:13:09PM -0700, Nye Liu wrote:
> ** Model information
> sys_vendor: QEMU
> product_name: Standard PC (Q35 + ICH9, 2009)
> product_version: pc-q35-5.2
> chassis_vendor: QEMU
> chassis_version: pc-q35-5.2
> bios_vendor: SeaBIOS
> bios_version: 1
Control: tag -1 moreinfo
Hi
On Tue, Oct 15, 2024 at 12:13:09PM -0700, Nye Liu wrote:
> ** Model information
> sys_vendor: QEMU
> product_name: Standard PC (Q35 + ICH9, 2009)
> product_version: pc-q35-5.2
> chassis_vendor: QEMU
> chassis_version: pc-q35-5.2
> bios_vendor: SeaBIOS
> bios_version: 1
Hi
On Thu, Oct 10, 2024 at 06:03:24PM +0200, Helmut Grohne wrote:
> A. Multi-Arch: foreign is a lie
>
> linux-libc-dev declares being Multi-Arch: foreign, but it does not live
> up to the involved promise and cannot. Earlier, a dependency on
> linux-libc-dev:hurd-i386 would be considered unsatisf
Hi
On Thu, Oct 10, 2024 at 06:03:24PM +0200, Helmut Grohne wrote:
> A. Multi-Arch: foreign is a lie
>
> linux-libc-dev declares being Multi-Arch: foreign, but it does not live
> up to the involved promise and cannot. Earlier, a dependency on
> linux-libc-dev:hurd-i386 would be considered unsatisf
Package: nvidia-graphics-drivers
Version: 535.183.06-1
Severity: serious
This package fails it's autopkgtests against linux.
https://ci.debian.net/packages/n/nvidia-graphics-drivers/testing/arm64/52858087/#S6
And while we are at, please remove the linux trigger from this package,
as it can't kee
Package: nvidia-graphics-drivers
Version: 535.183.06-1
Severity: serious
This package fails it's autopkgtests against linux.
https://ci.debian.net/packages/n/nvidia-graphics-drivers/testing/arm64/52858087/#S6
And while we are at, please remove the linux trigger from this package,
as it can't kee
Control: severity -1 important
On Wed, Oct 09, 2024 at 08:18:46AM +, Jing Luo wrote:
> rtla causes linux FTBFS when using "--host=i386" with amd64 schroots.
> And this was the sbuild command I used: `sbuild --host=i386 -c
> sid-amd64-sbuild -d unstable --no-arch-all --no-run-lintian`.
> Maybe
Control: severity -1 important
On Wed, Oct 09, 2024 at 08:18:46AM +, Jing Luo wrote:
> rtla causes linux FTBFS when using "--host=i386" with amd64 schroots.
> And this was the sbuild command I used: `sbuild --host=i386 -c
> sid-amd64-sbuild -d unstable --no-arch-all --no-run-lintian`.
> Maybe
Control: severity -1 important
On Wed, Oct 09, 2024 at 08:18:46AM +, Jing Luo wrote:
> rtla causes linux FTBFS when using "--host=i386" with amd64 schroots.
> And this was the sbuild command I used: `sbuild --host=i386 -c
> sid-amd64-sbuild -d unstable --no-arch-all --no-run-lintian`.
> Maybe
Hi
This weeks meeting will happen today at 19:00 UTC in #debian-kernel.
Sorry for the late announcement.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meetings/-/wikis/20241009
Please reply here if you would like to add more points.
Bastian
--
The sight of death f
Hi
I see that this bug is now open for over a year. It is also marked as
pending for almost a year. And there have been numerous uploads done by
the maintainer since then without a fix.
What is the plan to get this fixed?
Bastian
--
He's dead, Jim.
-- McCoy, "The Devil in the
Hi
I see that this bug is now open for over a year. It is also marked as
pending for almost a year. And there have been numerous uploads done by
the maintainer since then without a fix.
What is the plan to get this fixed?
Bastian
--
He's dead, Jim.
-- McCoy, "The Devil in the
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: thin-provisioning-to...@packages.debian.org, wa...@debian.org
Control: affects -1 + src:thin-provisioning-tools
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove thin-provisioning-tools from armel. This is now
implemente
Package: dhcpcd
Version: 1:10.0.10-2
Severity: serious
X-Debbugs-Cc: wa...@debian.org
dhcpcd runs itself as service, not controlled by the network management.
This makes it not a suitable replacement for isc-dhcp.
It breaks network in cloud images.
Bastian
-- System Information:
Debian Release:
Package: cloud-init
Version: 24.3.1-1
Severity: serious
X-Debbugs-Cc: wa...@debian.org
After the cloud-init run, a dhcpcd keeps running and regularly redoing
the network config:
| Sep 27 20:40:01 boot1 dhcpcd[686]: eth0: pid 1 deleted default route via
fe80::1234:5678:9abc
| Sep 27 20:40:01 boot
Package: cloud-init
Version: 24.3.1-1
Severity: serious
X-Debbugs-Cc: wa...@debian.org
After the cloud-init run, a dhcpcd keeps running and regularly redoing
the network config:
| Sep 27 20:40:01 boot1 dhcpcd[686]: eth0: pid 1 deleted default route via
fe80::1234:5678:9abc
| Sep 27 20:40:01 boot
Package: dhcpcd
Version: 1:10.0.10-2
Severity: serious
X-Debbugs-Cc: wa...@debian.org
dhcpcd runs itself as service, not controlled by the network management.
This makes it not a suitable replacement for isc-dhcp.
It breaks network in cloud images.
Bastian
-- System Information:
Debian Release:
Package: cloud-init
Version: 24.3.1-1
Severity: serious
X-Debbugs-Cc: wa...@debian.org
After the cloud-init run, a dhcpcd keeps running and regularly redoing
the network config:
| Sep 27 20:40:01 boot1 dhcpcd[686]: eth0: pid 1 deleted default route via
fe80::1234:5678:9abc
| Sep 27 20:40:01 boot
On Mon, Sep 23, 2024 at 05:39:07PM -0400, Noah Meyerhans wrote:
> On Mon, Sep 23, 2024 at 07:32:05PM +0200, Alexandre Detiste wrote:
> > I seen 1 remaining refererence
> > tests/common/test_cgroupconfigurator.py:from nose.plugins.attrib import attr
> Yeah, but we don't actually fail on test failure
On Mon, Sep 23, 2024 at 05:39:07PM -0400, Noah Meyerhans wrote:
> On Mon, Sep 23, 2024 at 07:32:05PM +0200, Alexandre Detiste wrote:
> > I seen 1 remaining refererence
> > tests/common/test_cgroupconfigurator.py:from nose.plugins.attrib import attr
> Yeah, but we don't actually fail on test failure
On Mon, Sep 23, 2024 at 05:39:07PM -0400, Noah Meyerhans wrote:
> On Mon, Sep 23, 2024 at 07:32:05PM +0200, Alexandre Detiste wrote:
> > I seen 1 remaining refererence
> > tests/common/test_cgroupconfigurator.py:from nose.plugins.attrib import attr
> Yeah, but we don't actually fail on test failure
On Sun, Sep 15, 2024 at 05:23:10PM +0200, Francesco Poli wrote:
> Or otherwise, if you think there's something wrong with them, could you
> please explain what is wrong? Maybe there's a way to fix them...
The linux-cpupower package includes low level tools to interrogate and
set certain low level
On Sun, Sep 15, 2024 at 05:23:10PM +0200, Francesco Poli wrote:
> Or otherwise, if you think there's something wrong with them, could you
> please explain what is wrong? Maybe there's a way to fix them...
The linux-cpupower package includes low level tools to interrogate and
set certain low level
On Sun, Sep 22, 2024 at 04:37:54PM +1000, Viktor Dukhovni via mailop wrote:
> On Sun, Sep 22, 2024 at 09:25:36AM +0300, Atro Tossavainen via mailop wrote:
> > > Get a Linux machine in an AS that doesn't host abusers (check the AS
> > > using http://www.uceprotect.net/de/rblcheck.php) and install yo
Hi
On Wed, Sep 18, 2024 at 04:53:09PM +0200, Ben Hutchings wrote:
> On Thu, 2024-06-13 at 20:48 +0200, Bastian Blank wrote:
> > What is not longer possible in non-confusing ways is to use branches
> > named after Debian distributions. We would either need to do non fast
> >
Hi
This weeks meeting will happen tomorrow at 19:00 UTC in #debian-kernel.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meetings/-/wikis/20240911
Please reply here if you would like to add more points.
Bastian
--
The sight of death frightens them [Earthers].
On Mon, Sep 09, 2024 at 05:56:50PM +0300, Martin-Éric Racine wrote:
> Fair enough. In that case, I suggest editing the following (4.5.1.
> Preparation) to remove the step about installing build-essential,
> since it installs a compiler suite that won't be used by src:linux.
build-essential is requ
On Mon, Sep 09, 2024 at 05:56:50PM +0300, Martin-Éric Racine wrote:
> Fair enough. In that case, I suggest editing the following (4.5.1.
> Preparation) to remove the step about installing build-essential,
> since it installs a compiler suite that won't be used by src:linux.
build-essential is requ
On Mon, Sep 09, 2024 at 11:51:17AM +0300, Martin-Éric Racine wrote:
> src:linux currently has an explicit Build-Depends on gcc-13. This defeats the
> whole point of building against whatever 'build-essential' pulls in for the
> target Debian release, and it results in several GCC suites getting
On Mon, Sep 09, 2024 at 11:51:17AM +0300, Martin-Éric Racine wrote:
> src:linux currently has an explicit Build-Depends on gcc-13. This defeats the
> whole point of building against whatever 'build-essential' pulls in for the
> target Debian release, and it results in several GCC suites getting
Hi
> My sender_access file looks like this:
> /@*.onmicrosoft\.com/ REJECT
> /\.pro$/ REJECT We reject all .pro domains. Contact thomas dot cameron at
> camerontech dot com from a trusted email service if you need assistance.
You could do that without regular expressions. Depending on y
Control: tags -1 wontfix
Hi
Yes, this change is expected. It is documented in the NEWS file of the
package and should be showed to the user via apt-listchanges.
We decided to make this change, even if some systems will fail, to align
Debian better to a general purpose use case.
Bastian
--
Be
Control: tags -1 wontfix
Hi
Yes, this change is expected. It is documented in the NEWS file of the
package and should be showed to the user via apt-listchanges.
We decided to make this change, even if some systems will fail, to align
Debian better to a general purpose use case.
Bastian
--
Be
Package: release-notes
The kernel team decided to switch the default kernel for ppc64el (and
with this also ppc64) to 4k page size. This is known to break systems
in some circumstances. We need to document this in the release notes as
well as in the package.
For reference, the NEWS entry in the
Package: release-notes
The kernel team decided to switch the default kernel for ppc64el (and
with this also ppc64) to 4k page size. This is known to break systems
in some circumstances. We need to document this in the release notes as
well as in the package.
For reference, the NEWS entry in the
On Fri, Aug 23, 2024 at 11:10:03AM +0100, Steve McIntyre wrote:
> There's potentially quite a lot of modules that aren't going to be
> triggered by udev, e.g. extra filesystems or hardware that's not
> discoverable.
hw-detect only does this for network drivers.
Bastian
--
Every living thing wan
On Fri, Aug 23, 2024 at 12:39:14AM +0200, Pascal Hambourg wrote:
> On 22/08/2024 at 18:50, Bastian Blank wrote:
> > On Thu, Aug 22, 2024 at 04:38:30PM +0200, Marco d'Itri wrote:
> > >
> > > So, does d-i actually use depmod or modinfo?
> >
> > Ye
On Thu, Aug 22, 2024 at 04:38:30PM +0200, Marco d'Itri wrote:
> It has been suggested to me that, since our kernels nowadays are built
> with CONFIG_MODULE_COMPRESS_XZ=Y, there is no need to link kmod.udeb
> with libxz *as long as* we also do not use depmod or modinfo in d-i.
>
> So, does d-i ac
Hi
This weeks meeting will happen tomorrow at
https://jitsi.debian.social/dkt.
Here you can find the current agenda:
https://salsa.debian.org/kernel-team/meetings/-/wikis/20240821
Please reply here if you would like to add more points.
Bastian
--
The sight of death frightens them [Earthers].
Hi
On Wed, Aug 07, 2024 at 08:31:28AM +, daniel.u...@telekom.de wrote:
> We are kind of lucky. My colleagues updated the kernel on one the hosts,
> rebooted it and the problem occurred right away. Currently the system is
> running, but it looks like all san paths are gone ("multipath -ll" sh
1 - 100 of 2458 matches
Mail list logo
