Hi,
在 2024-01-12星期五的 21:26 -0600，rhys写道：
> Let me try again, following up on the previous thread, but removing most of
> the irrelevant history.
Let me try to strike this message down to avoid the discussion from shifting
further to an unknown direction.
> If I have a 32-bit Intel system that is
Let me try again, following up on the previous thread, but removing most of the
irrelevant history.
If I have a 32-bit Intel system that is currently supported on bookworm
(currently running bullseye, but I can upgrade it), is that of use to anyone as
a native build platform for 32-bit binary p
rhys 于2024年1月13日周六 11:27写道：
>
> Let me try again, following up on the previous thread, but removing most of
> the irrelevant history.
>
> If I have a 32-bit Intel system that is currently supported on bookworm
> (currently running bullseye, but I can upgrade it), is that of use to anyone
> as a
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 12 Jan 2024 21:47:59 +
Source: iproute2
Architecture: source
Version: 6.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Luca
iproute2_6.7.0-1_source.changes uploaded successfully to localhost
along with the files:
iproute2_6.7.0-1.dsc
iproute2_6.7.0.orig.tar.xz
iproute2_6.7.0-1.debian.tar.xz
iproute2_6.7.0-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Fri, 12 Jan 2024 22:35:06 +
with message-id
and subject line Bug#1056582: fixed in iproute2 6.7.0-1
has caused the Debian Bug report #1056582,
regarding iproute2: [INTL:it] Italian debconf translation
to be marked as done.
This means that you claim that the problem has been
On Thu, Jan 11, 2024 at 09:48:34AM +, Dimitri John Ledkov wrote:
> Disabling debug symbols, enabling debug symbol zstd compression, using
> split debug symbols (disabled BTF usage) should help here.
Disabling debug symbols does not help.
Bastian
> Sent from Ubuntu Pro
> https://ubuntu.com/pr
On Sat, 14 Jan 2023 16:12:47 +0100 Salvatore Bonaccorso
wrote:
> Hi Jakub,
>
> On Thu, Jan 12, 2023 at 01:24:16PM +0100, Jakub Wilk wrote:
> > * Salvatore Bonaccorso , 2022-11-19 11:11:
> > > Given you were able to tackle the issue further, can you report
the
> > > issue to upstream
> >
> > Do
In a Debian Testing System one of the packages solved my problem. Secure
Boot is now displayed as active.
Start-Date: 2024-01-12 18:59:31
Commandline: apt full-upgrade
Requested-By: user (1000)
Upgrade: orca:amd64 (45.1-2, 45.2-1), dmeventd:amd64 (2:1.02.185-2,
2:1.02.185-3), libldb2:amd64 (2:
Are you forgetting that 64 bit is slower? In the arm world where it's
easily switchable 64 bit is pokey when you don't need it.
On Fri, Jan 12, 2024, 12:54 PM wrote:
>
>
> Sent from my mobile device.
>
> --
> *From:* YunQiang Su
> *Sent:* Friday, January 12, 2024 10
Sent from my mobile device.
From: YunQiang Su
Sent: Friday, January 12, 2024 10:11
To: r...@neoquasar.org
Cc: noloa...@gmail.com; debian-kernel@lists.debian.org;
debian-...@lists.debian.org; debian-de...@lists.debian.org;
debian-rele...@lists.debian.org
Subjec
Keeping in mind that I am new to this arena...
I have some Intel systems - both 64-bit and 32-bit - that I might be able to
use as build platforms.
What does the Debian team need from me to be able to use these systems?
I can't guarantee they'll be FAST, but I'll do what I can to make them
EF
于2024年1月12日周五 23:59写道：
>
> Keeping in mind that I am new to this arena...
>
> I have some Intel systems - both 64-bit and 32-bit - that I might be able to
> use as build platforms.
>
I guess all of your hardwares are 64bit. You setup different OS on them.
> What does the Debian team need from m
13 matches
Mail list logo
