On Thu, Jan 16, 2025 at 11:22:11PM +0100, Aurelien Jarno wrote:
> On 2025-01-16 18:27, Aurelien Jarno wrote:
> > Hi,
> >
> > On 2025-01-16 11:02, Simon McVittie wrote:
> > > Control: found -1 2.58.93+dfsg-2
> > >
> > > On Thu, 16 Jan 2025 at 10:45:28 +, Simon McVittie wrote:
> > > > librsvg/2
On Mon, Mar 04, 2024 at 09:52:14AM +0100, Gerardo Ballabio wrote:
> Gianluca Renzi wrote:
> > The same here. We never used the d-i but we are using Debian systems
> > (kernel and root file system) as daily bases of our line of products
> > embedded systems. Hundred of thousands of boards are usin
On Thu, Jan 11, 2024 at 11:28:19AM +0100, Bastian Blank wrote:
>...
> 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.
>
> Okay, maybe more
On Wed, Jul 12, 2023 at 11:07:12AM +0200, Bastian Blank wrote:
> Control: tags -1 confirmed
>
> Hi
>
> On Sat, Jul 08, 2023 at 08:41:03PM +0200, John Paul Adrian Glaubitz wrote:
> > Please enable building the linux-libc-dev package for the new Debian
> > architecture loong64.
> > The correspondi
On Fri, Oct 27, 2023 at 10:55:48AM +0200, Bastian Blank wrote:
> 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 reliabl
On Tue, Oct 03, 2023 at 07:30:49PM +0200, Bastian Blank wrote:
>...
> The core problem is that people assume they can get headers matching the
> currently running kernel, without upgrading first, see also the parallel
> thread.
>...
If the new kernel has a regression that affects the user, the use
On Sat, Sep 09, 2023 at 10:15:59AM +0200, Salvatore Bonaccorso wrote:
>...
> Note that the last time the problem arised already earlier in
> experimental and Ben workarounded it there with
> https://salsa.debian.org/kernel-team/linux/-/commit/9dfe6d33a4fd220394228b30cbbfdb3b444d36ec
> We probably c
On Sat, Sep 09, 2023 at 10:15:59AM +0200, Salvatore Bonaccorso wrote:
>...
> - Relese the DSA without armel builds. This is not optimal and for the point
> release
> we need to have to have all builds, but this gives people who still are
> interested
> in this architecture to step up and prop
On Sun, Jul 23, 2023 at 09:44:40AM +0200, Bastian Blank wrote:
>...
> We uncouple the package names and ABI. The ABI will include the
> complete version, so every rebuild will change it.
That's also what I meant with "It should only be impossible to make them
co-installable".
> The package name
On Thu, Jul 13, 2023 at 09:16:15PM +0200, Bastian Blank wrote:
>...
> ### NMU
>
> Can be easily added back by adding "bX" or so to the ABI.
That would be confusing, bX is naming convention for binNMUs in Debian
revisions.
> ### BinNMU
>
> Is impossible to support. The version change requires
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#marking-non-free-packages-as-auto-buildable
https://buildd.debian.org/status/logs.php?pkg=firmware-nonfree&arch=all
https://buildd.debian.org/status/package.php?p=firmware-nonfree
"Section: contrib/misc" at the latter URL looks very
On Sun, Jul 17, 2022 at 09:02:23PM +0200, Moritz Mühlenhoff wrote:
>...
> but the quickly vaninishing
> upstream support for i386 and the lack of active porters make i386
> problematic from the Security Team's point of view.
>
> For packages where new upstream releases are being introduced
> this m
On Sun, Jul 17, 2022 at 02:02:34PM +0200, Ben Hutchings wrote:
> On Sat, 2022-07-16 at 18:03 +0300, Adrian Bunk wrote:
>...
> > What problem is building i386 bookworm kernel binaries causing for you
> > that are not present on other architectures like armhf or s390x?
>
>
On Sat, Jul 16, 2022 at 03:54:21PM +0200, Ben Hutchings wrote:
> On Sat, 2022-07-16 at 06:23 +0300, Adrian Bunk wrote:
> > On Fri, Jul 15, 2022 at 01:51:21PM +0200, Ben Hutchings wrote:
>...
> > This is not limited to i386, it is also quite relevant for embedded arm
> > whe
On Wed, Jun 22, 2022 at 10:05:37AM +0200, Graham Inggs wrote:
>...
> List of concerns for architectures
> ==
>...
> * Concern for mips64el and mipsel: builders are extremely slow.
>(Raised by kernel team; carried over from bullseye)
>...
This was mitigated with
On Fri, Jul 15, 2022 at 01:51:21PM +0200, Ben Hutchings wrote:
>
> For i386, I have some concerns about upstream support of the Linux
> kernel. CPU security mitigations for x86 are concentrated on amd64,
> with i386 being left behind. Mitigation of Meltdown required a
> different implementation
On Fri, Jul 10, 2020 at 06:13:58PM +0100, Ben Hutchings wrote:
> I don't know if this should be a blocker, but the MIPS builders are
> still extremely slow for kernel builds. In the worst case (mipsel:
> mipsel-aql-{01,02}) it takes about 41 hours, which is 3 times longer
> than the next slowest g
09:04, YunQiang Su wrote:
> > Adrian Bunk 于2020年5月21日周四 下午3:40写道：
> > > On Thu, May 21, 2020 at 06:41:34AM +0800, YunQiang Su wrote:
> > > > Adrian Bunk 于2020年5月21日周四 上午4:44写道：
> > > > > On Tue, May 19, 2020 at 11:43:30AM +0800, Shengjing Zhu wrote:
&
Source: ethtool
Version: 1:5.4-1
Severity: important
ethtool is linux specific.
Currently this is implemented in Packages-arch-specific,
but Packages-arch-specific is obsolete and will go away.
Please change the architecture in debian/control to
Architecture: linux-any
On Sun, Feb 17, 2019 at 09:52:48AM -0800, Vagrant Cascadian wrote:
> After upgrading to the latest 4.9.x kernel in sid, all of the armhf
> boards running this kernel failed to boot.
>
> Adding to the list:
>
> imx6: Cubox-i4pro, Cubox-i4x4, Wandboard Quad
> exynos5: Odroid-XU4
> exynos4: Odroid-U
Source: nfs-utils
Version: 1:1.3.4-2.3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nfs-utils.html
...
device-discovery.c: In function 'bl_add_disk':
device-discovery.c:156:28: warning: implicit declaration of function 'major'
[-Wimplicit-funct
reassign 912411 src:linux 4.9.110-3+deb9u2~deb8u1
thanks
On Wed, Oct 31, 2018 at 05:21:39PM +0800, 段熊春 wrote:
> Package: linux-image-4.9.0-0.bpo.7-amd64
> Version: 4.9.110-3+deb9u2~deb8u1
>
> Package: systemd
> Version: 230-7~bpo8+2
>
> hi guys：
> We suspect that we may have found a memory leak
reassign 909852 src:linux
thanks
On Sat, Sep 29, 2018 at 05:36:15PM +0200, m.alfa...@gmail.com wrote:
> Package: linux-image-4.18-0-0.bpo.1-amd64
> Version: linux-image-4.18.0-0.bpo.1-amd64
> Severity: minor
>
> Dear Maintainer,
>
> Today i tried a suspend on my system and it resulted in backtra
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.9.y&id=6bb53ee170c45f44ac80ad8318f72feff9cdee1b
We don't have that commit, and this explains why
cpu-hotplug-boot-ht-siblings-at-least-once.patch broke ARM.
cu
Adrian
--
"Is there not promise of rain?" L
On Mon, May 14, 2018 at 03:11:30AM +0100, Ben Hutchings wrote:
> On Sun, 2018-05-13 at 23:48 +0300, Adrian Bunk wrote:
>...
> > Due to the gdm bugs mentioned above we know that there are real-life
> > situations where gdm currently uses "random" data that might be
&g
On Wed, May 09, 2018 at 11:46:00PM +0100, Ben Hutchings wrote:
>...
> # Security flaw and initial fix
>
> Recently it was discovered that getrandom() could return successfully
> before the RNG was really ready to produce unpredictable data. This
> issue was designated as CVE-2018-1108, and was fi
reassign 893161 src:linux 4.9.82-1+deb9u3
thanks
On Sat, Mar 17, 2018 at 12:07:54AM +0100, compo...@trash-mail.com wrote:
> Package: src:linuxVersion: 4.9.82-1+deb9u3Severity: importantDear
> Maintainer,I tracked down an issue I've been having on my Debian Stable
> machine with suspending. Other
reassign 891418 src:linux 4.9.0-6
thanks
On Sun, Feb 25, 2018 at 01:54:35PM +0100, Petr wrote:
> Package: linux-image-4.9.0-6-amd64
> Version: 4.9.0-6
> Severity: normal
>
> Dear Maintainer,
>
>
> after upgrade from linux-image-4.9.0-3-amd64 to linux-image-4.9.0-6-amd64
> smartctl stop showing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 06 Feb 2018 21:20:36 +0200
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source
Version: 1:1.3.4-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team
Changed-By: Adrian Bunk
95)
+ * Update the build dependency from the obsolete dh-systemd.
+ * Stop using bzip2 for source compression,
+the default xz compresses better.
+
+ -- Adrian Bunk Tue, 06 Feb 2018 21:20:36 +0200
+
nfs-utils (1:1.3.4-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru nfs-u
Source: nfs-utils
Version: 1:1.3.4-2.1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nfs-utils.html
...
rpc.c: In function 'nsm_recv_getport':
rpc.c:469:13: error: 'UINT16_MAX' undeclared (first use in this function); did
you mean 'UINT_MAX
Control: reassign -1 src:linux 3.16.48-1
Control: severity -1 grave
On Wed, Oct 11, 2017 at 08:45:14AM +, Cristiano Casella wrote:
> Package: linux-image
>
> Version: 3.16.0-4-amd64_3.16.48-1_amd64.deb
>
>
> Hi,
>
> we are an hosting provider and we are offering to our customers virtual
>
reassign 872921 src:linux
thanks
On Tue, Aug 22, 2017 at 01:32:05PM +, Nicolas wrote:
> Package: linux-image
> Version: 4.9.0-3-amd64
> Hi,
>
> Using an APU2 from pcengines, and debian stretch (uptodate, x64), when I
> blacklist the i2c_piix4 modules and load sp5100_tco for watchdog, I got
reassign 872435 src:linux
thanks
On Thu, Aug 17, 2017 at 02:12:46PM +0200, Lars Mucha wrote:
> Package: linux-image-3.16.0.4-amd64
> Version: linux-image-3.16.0-4-amd64
> Severity: important
>
> Dear Maintainer,
>
>* What led up to the situation?
> The computer contains an intel processor wi
On Sun, Jul 16, 2017 at 11:21:27PM +0100, Ben Hutchings wrote:
> On Thu, 2017-07-06 at 13:10 +0300, Adrian Bunk wrote:
> > Control: reassign -1 src:linux 4.9.30-2
> > Control: retitle -1 mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
> > Control: affects -1 src:golan
Control: reassign -1 src:linux 4.9.30-2
Control: retitle -1 mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address
Control: affects -1 src:golang-github-pelletier-go-toml
src:golang-github-nicksnyder-go-i18n gccgo-7
On Thu, Jul 06, 2017 at 02:11:00AM +0300, Adrian Bunk wrote:
> Source: gol
reassign 867011 src:linux 4.9.30-2
thanks
On Mon, Jul 03, 2017 at 03:18:18PM +0300, Vadim Kolchev wrote:
> Package: linux 4.9.30-2+deb9u1
>
> Hello,
> Since update to Debian 9 cannot connect to WiFi using rt28xxusb
> (particularly rt2870usb is loaded) driver.
> Network Manager cannot connect.
> I
Control: tags -1 sid
linux-libc-dev 4.9.30-2 reverted the headers change that caused the
radvd FTBFS, so there does not seem to be a real need to get that fixed
in a stretch point release (but it should still be fixed in unstable).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan
Source: linux-signed
Version: 4.4
Severity: serious
linux-signed has build dependencies on the exact version 4.9.18-1
of packages from src:linux, but version 4.9.25-1 is now in stretch.
Control: reopen -1
Control: reassign -1 src:linux 4.7.2-1
Control: retitle -1 Kernel packages need Breaks on older virtualbox-dkms
versions
> From: Gianfranco Costamagna
> To: Karl Voit , 849633-d...@bugs.debian.org
> Subject: Re: Bug#849633: virtualbox-dkms: Compiling error when updating
> ker
On Tue, Dec 20, 2016 at 08:57:55AM +0100, Salvatore Bonaccorso wrote:
> Source: linux
> Version: 4.8.15-1
> Severity: serious
> Justification: FTBFS
>
> Hi
>
> src:linux 4.8.15-1 FTBFS on ppc64el.
>
> Log:
> https://buildd.debian.org/status/fetch.php?pkg=linux&arch=ppc64el&ver=4.8.15-1&stamp=14
control: reassign 847779 linux-image-4.9.0-rc8-armmp-unsigned 4.9~rc8-1~exp1
There were some linebreaks the bug tracking system was not happy with,
reassign it to the intended package.
On Sun, Dec 11, 2016 at 05:34:06PM +0100, Josua Mayer wrote:
> Package: linux-image-4.9.0-rc8-armmp-unsigned: sr
On Thu, Dec 08, 2016 at 02:21:21AM +, Ben Hutchings wrote:
>...
> > (2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
> > 0.125)" which it will need even after #847340 is fixed.
>
> I won't add that Breaks line because:
> - Only the combination of the new firmware-misc-nonfree *and*
Package: user-mode-linux
Version: 4.7-1um-1
Severity: normal
A separate source package for user-mode-linux made sense 15 years ago,
when a huge patch of non-upstreamed kernel code existed for user-mode-linux.
What is left today in the user-mode-linux source package are 6 small
patches to UML-spec
reassign 807010 src:linux
affects 807010 xl2tpd
reassign 822801 src:linux
affects 822801 xl2tpd
thanks
Hi,
the bugs #807010 (xl2tpd freezes all system) and #822801
(xl2tpd makes kernel soft lockup) look like bugs in the
kernel to me.
xl2tpd might also be buggy, but the worst part of these bugs i
On Thu, Jul 21, 2011 at 12:50:01PM +0200, Ben Hutchings wrote:
> On Thu, 2011-07-21 at 07:05 +0300, Adrian Bunk wrote:
> > On Thu, Jul 21, 2011 at 01:09:34AM +0200, Ben Hutchings wrote:
> > > On Mon, 2011-07-18 at 14:29 +0300, Adrian Bunk wrote:
> > > > On Fri, Ju
On Thu, Jul 21, 2011 at 01:09:34AM +0200, Ben Hutchings wrote:
> On Mon, 2011-07-18 at 14:29 +0300, Adrian Bunk wrote:
> > On Fri, Jul 15, 2011 at 06:30:41PM +0100, Ben Hutchings wrote:
> > >...
> > > This is wrong on so many levels.
> > > 1. There is no way
On Mon, Jul 18, 2011 at 02:30:41PM -0500, Jonathan Nieder wrote:
> Adrian Bunk wrote:
>
> > What would be the correct handling for a package whose upstream sources
> > use a userspace<->kernel interface introduced in 2.6.39?
>
> Check for -ENOSYS, print a helpful
On Mon, Jul 18, 2011 at 08:35:21PM +0200, Julien Cristau wrote:
> On Mon, Jul 18, 2011 at 14:29:47 +0300, Adrian Bunk wrote:
>
> > How could a package declare "I need at least kernel 2.6.39"?
>
> You can't, and shouldn't, do that (at least until after
On Mon, Jul 18, 2011 at 02:45:20PM +0200, Uwe Kleine-König wrote:
> On Mon, Jul 18, 2011 at 02:29:47PM +0300, Adrian Bunk wrote:
> > tags 609300 +patch
> > thanks
> >
> > On Fri, Jul 15, 2011 at 06:30:41PM +0100, Ben Hutchings wrote:
> > >...
> > > Th
tags 609300 +patch
thanks
On Fri, Jul 15, 2011 at 06:30:41PM +0100, Ben Hutchings wrote:
>...
> This is wrong on so many levels.
> 1. There is no way to declare relations to 'all kernel packages'.
Why not?
How could a package declare "I need at least kernel 2.6.39"?
(I know that self-compiled ke
On Fri, Jul 15, 2011 at 03:45:58PM +0100, Ben Hutchings wrote:
> On Fri, 2011-07-15 at 16:04 +0300, Adrian Bunk wrote:
> > Package: linux-image-2.6.39-2-amd64
> > Version: 2.6.39-3
> > Severity: serious
>
> This is not RC for the kernel.
"Upgrade makes another
Package: linux-image-2.6.39-2-amd64
Version: 2.6.39-3
Severity: serious
Upgrading the kernel without also upgrading input-utils (e.g. when
using the version in squeeze or the version currently in testing)
makes input-utils unusable (see #609300).
After #609300 got fixed, the linux images should t
Package: linux-libc-dev
Version: 2.6.32-15
Severity: normal
I run a self-compiled kernel and have therefore no Debian kernel images
installed.
While upgrading linux-libc-dev the contents of
/usr/share/doc/linux-libc-dev/NEWS.Debian.gz
was shown, which is kinda pointless.
--
To UNSUBSCRIBE, em
forwarded 439072 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3335
thanks
On Thu, Aug 23, 2007 at 11:17:28PM +0200, Josip Rodin wrote:
> On Thu, Aug 23, 2007 at 07:04:13PM +0200, Adrian Bunk wrote:
> > > While browsing kernel options, I noticed:
> > >
> >
ht be that this
> > is an OSS->ALSA regression that slipped through the cracks?
>
> While browsing kernel options, I noticed:
>
> Please contact Adrian Bunk <[EMAIL PROTECTED]> if you had to
> say Y here because your hardware is not properly supported
> by ALSA.
forcemerge 398470 415112
tags 398470 +patch
tags 398470 +security
tags 398470 serious
retitle 398470 key serial number collision (CVE-2007-0006)
thanks
Severity "serious" since bugs causing kernel Oopses with CVE number and
patches available are IMHO nothing a stable release should ship with.
cu
Package: firmware-nonfree
Version: 0.3
Severity: serious
The build dependency on linux-support-2.6.17-2 can't be fulfilled
in unstable or testing.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:
should select CRYPTO.
Additionally, this patch removes the #ifdef's for the non-compiling
CRYPTO=n case from drivers/net/wireless/airo.c.
Bug report by Roland Mas <[EMAIL PROTECTED]>,
initial patch by dann frazier <[EMAIL PROTECTED]>.
Signed-off-by: Adrian Bunk <[EMAI
Hi John,
regarding your bug report "cramfsprogs: Extremely inefficient
performance on large trees":
mkfs.cramfs (shipped with the util-linux package) already uses md5sums
the way you suggest them. Can you confirm that mkfs.cramfs fixes your
problem?
cu
Adrian
--
"Is there not promis
Package: linux-image-2.6.12-1-386
Version: 2.6.12-5
Severity: normal
There is not much value in shipping kernel images supporting
a CPU no longer supported by Debian since Debian 3.1 .
Renaming the kernel image and letting the compiler optimize it
for the 486 would also give your 486 and 586 use
On Wed, Aug 03, 2005 at 08:54:37PM +0900, Horms wrote:
>...
> Hi Frans,
>
> The null devfs_name check seems fine to me,
> I've CCed Richard Gooch for comment, hopefully
> he can offer one despite devfs being debricated
> upstream.
>...
The DEVFS_FS config option is no longer available in 2.6.13 m
On Thu, May 19, 2005 at 10:12:43AM +0200, Goswin von Brederlow wrote:
>...
> And all have problems:
>
> package | danger
> -+--
> kernel-image*| kernel-source* update replaces source
> | rebuild differs
> |
Package: kernel-image-2.4.27-sparc
Version: 2.4.27-2
Severity: critical
Tags: security, sarge
The package in sarge lacks the security fixes from
kernel-source-2.4.27 2.4.27-9 .
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Apr 08, 2005 at 08:31:22PM -0400, Raul Miller wrote:
> On Fri, Apr 08, 2005 at 07:34:00PM +0200, Adrian Bunk wrote:
> > If Debian was at least consistent.
> >
> > Why has Debian a much more liberal interpretation of MP3 patent issues
> > than RedHat?
>
>
On Fri, Apr 08, 2005 at 07:42:51PM +0200, Josselin Mouette wrote:
> Le vendredi 08 avril 2005 à 19:34 +0200, Adrian Bunk a écrit :
> > > When there are several possible interpretations, you have to pick up the
> > > more conservative one, as it's not up to us to make the
On Fri, Apr 08, 2005 at 09:22:00AM +0200, Josselin Mouette wrote:
> Le jeudi 07 avril 2005 à 23:07 +0200, Adrian Bunk a écrit :
> > > You are mixing apples and oranges. The fact that the GFDL sucks has
> > > nothing to do with the firmware issue. With the current situation
On Fri, Apr 08, 2005 at 08:54:40AM +0200, Sven Luther wrote:
> On Fri, Apr 08, 2005 at 02:31:36AM +0200, Adrian Bunk wrote:
> > On Thu, Apr 07, 2005 at 11:05:05PM +0200, Sven Luther wrote:
> > > On Thu, Apr 07, 2005 at 10:56:47PM +0200, Adrian Bunk wrote:
> > >...
&g
On Thu, Apr 07, 2005 at 11:05:05PM +0200, Sven Luther wrote:
> On Thu, Apr 07, 2005 at 10:56:47PM +0200, Adrian Bunk wrote:
>...
> > If your statement was true that Debian must take more care regarding
> > legal risks than commercial distributions, can you explain why Debia
On Tue, Apr 05, 2005 at 04:05:07PM +0200, Josselin Mouette wrote:
> Le lundi 04 avril 2005 à 21:32 +0200, Adrian Bunk a écrit :
> > On Mon, Apr 04, 2005 at 09:05:18PM +0200, Marco d'Itri wrote:
> > > On Apr 04, Greg KH <[EMAIL PROTECTED]> wrote:
> > >
>
On Tue, Apr 05, 2005 at 03:57:01PM +0200, Sven Luther wrote:
>...
> The other point is that other entities, like redhat, or suse (which is now
> novel and thus ibm) and so have stronger backbones, and can more easily muster
> the ressources to fight of a legal case, even one which is a dubious one,
On Mon, Apr 04, 2005 at 10:23:08PM +0200, Sven Luther wrote:
> On Mon, Apr 04, 2005 at 09:58:30PM +0200, Adrian Bunk wrote:
> > On Mon, Apr 04, 2005 at 09:29:45PM +0200, Sven Luther wrote:
> > > On Mon, Apr 04, 2005 at 12:17:46PM -0700, Greg KH wrote:
> > > > On M
On Mon, Apr 04, 2005 at 09:29:45PM +0200, Sven Luther wrote:
> On Mon, Apr 04, 2005 at 12:17:46PM -0700, Greg KH wrote:
> > On Mon, Apr 04, 2005 at 08:27:53PM +0200, Sven Luther wrote:
> > > Mmm, probably that 2001 discussion about the keyspan firmware, right ?
> > >
> > > http://lists.debian.or
On Mon, Apr 04, 2005 at 09:05:18PM +0200, Marco d'Itri wrote:
> On Apr 04, Greg KH <[EMAIL PROTECTED]> wrote:
>
> > What if we don't want to do so? I know I personally posted a solution
> Then probably the extremists in Debian will manage to kill your driver,
> like they did with tg3 and others.
On Sat, Aug 28, 2004 at 06:27:04PM +0200, Christoph Hellwig wrote:
> Adrian, which m-i-t release should have fixed this?
>...
I thought it was #225372, but it seems it is/was a different problem.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the da
[ this mail is not in a thread with the original mail since I saw it
when looking through the list archives ]
Hi Thomas,
this is bug #255849 [1] in the initscripts package. The patch from this
bug applied against /etc/init.d/checkroot.sh plus a reboot should fix
this issue.
For most people
76 matches
Mail list logo
