Hi folks
I'd like to schedule the upload of linux-2.6 2.6.21-3 for tomorrow or
so. I'd like to have a snapshot build.
Fixes:
- 2.6.21.[12]
- linux-libc-dev
- hppa debuging
- hppa64 compiler workaround
- s390/hercules
Bastian
--
Either one of us, by himself, is expendable. Both of us are not.
Package: linux-image-2.6.21-1-686
Version: 2.6.21-2
Severity: important
Hi,
I've installed 2.6.21 on two different VMware Workstation guests running on two
different hosts and both fail to boot.
They wait for a long time at Begin: Waiting for root file system... ...
Then it says:
ALERT!
Package: linux-source-2.6.21
Version: 2.6.21-2
Followup-For: Bug #425072
Hi,
FYI, this is the same issue I reported as #419217 for
linux-source-2.6.20.
elmar
--
.'`./\
| :' : Elmar Hoffmann [EMAIL PROTECTED]ASCII Ribbon
Processing commands for [EMAIL PROTECTED]:
reassign 423474 swat
Bug#423474: Swat / Samba share error
Bug reassigned from package `swat' to `swat'.
reassign 424868 linux-2.6
Bug#424868: Noise from backlight electronics with new kernel 2.6.18 for PowerPC
Warning: Unknown package 'linux'
Bug
On Sun, May 20, 2007 at 07:04:47PM -0700, Steve Langasek wrote:
On Sat, May 19, 2007 at 01:31:46PM +0200, Bastian Blank wrote:
- Replace the term subarch with something else, it is missleading. I
only have one new term yes: featureset.
If anything, I would have thought that the current
Accepted:
linux-headers-2.6.18-4-all-arm_2.6.18.dfsg.1-12etch1_arm.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-4-all-arm_2.6.18.dfsg.1-12etch1_arm.deb
linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12etch1_arm.deb
to
Accepted:
linux-headers-2.6.18-4-all-sparc_2.6.18.dfsg.1-12etch1_sparc.deb
to
pool/main/l/linux-2.6/linux-headers-2.6.18-4-all-sparc_2.6.18.dfsg.1-12etch1_sparc.deb
linux-headers-2.6.18-4-all_2.6.18.dfsg.1-12etch1_sparc.deb
to
Accepted:
linux-2.6_2.6.18.dfsg.1-12etch2.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12etch2.diff.gz
linux-2.6_2.6.18.dfsg.1-12etch2.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-12etch2.dsc
linux-doc-2.6.18_2.6.18.dfsg.1-12etch2_all.deb
to
Accepted:
linux-2.6_2.6.18.dfsg.1-13.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-13.diff.gz
linux-2.6_2.6.18.dfsg.1-13.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-13.dsc
linux-doc-2.6.18_2.6.18.dfsg.1-13_all.deb
to
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#417629: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418344: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#417631: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:50 +
with message-id [EMAIL PROTECTED]
and subject line Bug#406111: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#421283: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418076: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#421281: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418344: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412132: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412957: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:50 +
with message-id [EMAIL PROTECTED]
and subject line Bug#404148: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Accepted:
linux-2.6_2.6.18.dfsg.1-13lenny1.diff.gz
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-13lenny1.diff.gz
linux-2.6_2.6.18.dfsg.1-13lenny1.dsc
to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-13lenny1.dsc
linux-doc-2.6.18_2.6.18.dfsg.1-13lenny1_all.deb
to
Your message dated Thu, 24 May 2007 21:16:50 +
with message-id [EMAIL PROTECTED]
and subject line Bug#406111: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:16:51 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412092: fixed in linux-2.6 2.6.18.dfsg.1-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412132: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#404148: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#417629: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#421283: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418344: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#417631: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#406111: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412092: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418344: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#421281: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418076: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#412957: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Thu, 24 May 2007 21:27:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#406111: fixed in linux-2.6 2.6.18.dfsg.1-13lenny1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
2.6.18.dfsg.1-13 has been accepted into stable for the upcoming 4.0r1
release. However, I also need to upload various other packages
including linux-latest-2.6. stable is not permitted to have a version
greater than testing or unstable (and propagation does not
automatically occur) so we will also
Processing commands for [EMAIL PROTECTED]:
severity 425630 normal
Bug#425630: initramfs-tools: typo in init-premount/ps3
Severity set to `normal' from `minor'
merge 423469 425630
Bug#423469: initramfs-tools: Type in ps3 pre-mount script
Bug#425630: initramfs-tools: typo in init-premount/ps3
38 matches
Mail list logo
