On Fri, Jun 11, 2004 at 03:46:29PM -0400, Joey Hess wrote:
> severity 251861 grave
> thanks
> This bug is release crticial: it makes it impossible to install debian
> with the 2.6 kernel.
> We have a patch for the bug, but I don't know if Herbert will be
> avilable to release it. Didn't he quit?
On 11 Jun 2004 at 17:25, Patrick Caulfield wrote:
> On Fri, Jun 11, 2004 at 03:10:18PM +0100, Martin Michlmayr wrote:
> > > > In any case, can you type:
> > > > vgchange -a y
> > > > and restart the partitioner; then they should show up.
> > > >
> > > Done. For each lv, I get:
> > > Incorrect
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> severity 253731 normal
Bug#253731: test-candidate-1: linux26: some cosmetic and usability problems
Severity set to `normal'.
>
End of message, stopping processing here.
Please con
Colin Turner wrote:
> 1. The problem wasn't in the BTS, that's the whole point of my report.
You're mistaken; the bug was in the BTS.
--
see shy jo
signature.asc
Description: Digital signature
Your message dated Fri, 11 Jun 2004 20:26:18 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#253814: please add ppp-udeb and ppp-modules to the netboot image
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Fri, 11 Jun 2004 20:02:59 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 20:01:48 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:59:58 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:57:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:55:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:53:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:53:26 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:59:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:56:54 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 20:00:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 20:03:58 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Kurt Roeckx wrote:
> Why are those two in state building? They're available on the
> site. Is it a problem that they're in the 2.6 dir?
I marked them as such because I've not seem reports that specifically
say that installs from those images work.
--
see shy jo
signature.asc
Description: Dig
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:51:58 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:49:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:47:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 19:48:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:51:01 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 19:40:09 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 252588 debian-installer
Bug#252588: install: Installation fails on Sparc Ultra 10
Bug reassigned from package `install' to `debian-installer'.
> reassign 246007 debootstra
On Fri, Jun 11, 2004 at 06:53:35PM -0400, Joey Hess wrote:
> W. Borgert wrote:
> > What is the solution? Use LILO?
>
> A small /boot partition and grub works for me.
Hm, the harddisk is already very small, so I don't want to
waste space with multiple partitions. Also, my other
problem remains:
On Fri, 11 Jun 2004, Debian Bug Tracking System wrote:
> I don't think this is worth implementing; the installer now detects
> windows and other OSes and adds them to the grub boot menu automatically
> which will be much nicer for most users than some manual windows boot
> loader setup.
With sarg
Scott M. Dier wrote:
> The installer didn't load ehci-hcd for this machine under a CD boot
> where it did under a USB boot (!?). I've got no idea (yet) how modules
> are called before the ISO is mounted, so I'm assigning this to install.
>
> The usb controller is a 82801DB USB2 chip. The usb1 dr
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 253910 hw-detect
Bug#253910: cd install not working on dell latitude x300
Bug reassigned from package `install' to `hw-detect'.
>
End of message, stopping processing here.
* Joey Hess [2004-06-11 14:44:16-0400]
> (Please use the bts, I'm not the only one working on this stuff, and can
> easily miss mails. I'm also the worst possible person of base-config's
> several maintainers to talk about this stuff to, since I don't
> understand encodings, fonts, or localisation
W. Borgert wrote:
> What is the solution? Use LILO?
A small /boot partition and grub works for me.
--
see shy jo
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Debian Bug Tracking System wrote:
| This is an automatic notification regarding your Bug report
| #243606: debian-installer: Known bugs on website don't appear in this
list,
| which was filed against the debian-installer package.
|
| d-i bugs are sc
[ Please keep [EMAIL PROTECTED] CC'ed ]
Thanks for the information.
Discover1's hardware database lists the cciss kernel module for your
device. This module is in the scsi-extra-modules udeb in
debian-installer.
Did you already download debian-installer[1] and try if it works for
you? You can al
On Thu, Jun 10, 2004 at 09:34:59PM +0200, Kurt Roeckx wrote:
> On Thu, Jun 10, 2004 at 02:15:33PM -0400, Joey Hess wrote:
> >
> > If you would build those using the installer/build/daily-build script,
> > then I could add them to the build tracking page
> > (http://people.debian.org/~joeyh/d-i/bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This bug is defintely fixed, but I just gave an update on 239284 a
related PCMCIA matter.
Mail was sent to [EMAIL PROTECTED]
THe installer is looking pretty good. The DMA issue on the 2.6 kernel
installs is still a minor problem, but it looks like the
Your message dated Fri, 11 Jun 2004 16:50:31 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:45:20 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
On Jun 11, Joey Hess <[EMAIL PROTECTED]> wrote:
> > PPPoE support needs everything available in the netboot image (i.e. the
> > drivers for ethernet cards) and nothing else than ppp-udeb and the ppp
> > kernel modules package[1], so it looks quite appropriate to me.
> If you've netbooted a machine
Joey Hess wrote:
Marco d'Itri wrote:
On Jun 11, Joey Hess <[EMAIL PROTECTED]> wrote:
Is there an agreement that the netboot image is a correct image for
pppoe installs? That seems rather out of its scope to me.
I tought we had one the last time we discussed this...
PPPoE support need
Finn-Arne Johansen wrote:
> On Fri, Jun 11, 2004 at 03:03:10PM -0400, Joey Hess wrote:
> > Apparently one of the ide chipset modules makes your CD not work. The
> > thing to do, then, would be to boot the installer in expert mode, and
> > tell it not to load some of the ide chipset modules. Repeat
Your message dated Fri, 11 Jun 2004 16:44:27 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:47:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Processing commands for [EMAIL PROTECTED]:
> clone 228327 -1
Bug#228327: installation-reports: PCMCIA of the yenta_socket variety not detected
properly
Bug 228327 cloned as bug 253915.
> retitle -1 does not load yenta_socket module
Bug#253915: installation-reports: PCMCIA of the yenta_socket var
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 228158 discover1-data
Bug#228158: DI installation report for Dell Latitude CPi 366A
Bug reassigned from package `installation-reports' to `discover1-data'.
> tags 228158 m
Your message dated Fri, 11 Jun 2004 16:40:15 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:35:55 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:35:55 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:32:40 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:31:21 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
On Fri, Jun 11, 2004 at 02:05:34PM -0400, Joey Hess wrote:
> Right, but it still seems to be a bios issue, it's unable to access all
> of the drive. They never really fix this, just push the problem back
What is the solution? Use LILO? I had LILO on that machine
before, so it still should work.
Your message dated Fri, 11 Jun 2004 16:33:26 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:33:59 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:42:31 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing installation report
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 is now your res
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 227904 moreinfo
Bug#227904: Boot fails on Alpha DS 10 with illegal instruction
There were no tags set.
Tags added: moreinfo
> reassign 227904 kernel
Bug#227904: Boot fails on
Processing commands for [EMAIL PROTECTED]:
> clone 227498 -1
Bug#227498: failed install with 20040111 sarge netinst ISO on Tosh SatPro 4300 Laptop
Bug 227498 cloned as bug 253912.
> reassign -1 syslinux
Bug#253912: failed install with 20040111 sarge netinst ISO on Tosh SatPro 4300 Laptop
Bug reas
Your message dated Fri, 11 Jun 2004 16:23:24 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:29:06 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:20:19 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:18:06 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing installation report
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 is now your respon
Your message dated Fri, 11 Jun 2004 16:22:26 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:25:00 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:16:49 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
On Wed, Jun 09, 2004 at 05:14:58PM -0400, Joey Hess wrote:
> 1. My (probably misconfigured) vmware virtual machine. I never seem to
>get a default route set up on this machine via dhcp. If I add one by
>hand, it's ok.
> 2. My test laptop, connected directly to my cable company's interface
>
Quoting Joey Hess ([EMAIL PROTECTED]):
> I'm currently trying to get a usable base-config into testing to use for
> the tc1 release, and since recent, insufficiently tested, font changes
> have led to the current mess, the last thing I want to do is make any
Well, I think we can't call this a mes
Package: install
Version: test candidate 1
The installer didn't load ehci-hcd for this machine under a CD boot
where it did under a USB boot (!?). I've got no idea (yet) how modules
are called before the ISO is mounted, so I'm assigning this to install.
The usb controller is a 82801DB USB2 chip.
Your message dated Fri, 11 Jun 2004 16:26:20 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
On Fri, Jun 11, 2004 at 03:03:10PM -0400, Joey Hess wrote:
> Apparently one of the ide chipset modules makes your CD not work. The
> thing to do, then, would be to boot the installer in expert mode, and
> tell it not to load some of the ide chipset modules. Repeat until you've
> narrowed it down to
The keyboard problem is a fairly well-known problem. For example, see
http://wiki.debian.net/index.cgi?DebianInstallerWorkarounds
Most people report that it occurs up until X starts; they don't have
gpm, or gpm does not seem to be the cause.
I'm reassigning this bug to the kernel.
--
see shy j
Your message dated Fri, 11 Jun 2004 16:09:35 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 is now your responsibility to reopen t
Your message dated Fri, 11 Jun 2004 16:03:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:04:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line processing report
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 is now your responsibility t
Your message dated Fri, 11 Jun 2004 16:11:15 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing report
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 is now your responsibility to r
Your message dated Fri, 11 Jun 2004 16:12:49 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing report
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 is now your responsibility to r
Your message dated Fri, 11 Jun 2004 16:14:31 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing report
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 is now your responsibility to r
Processing commands for [EMAIL PROTECTED]:
> tag 247734 + pending
Bug#247734: debian-installer: incorrect /etc/hosts localhost line
There were no tags set.
Tags added: pending
> tag 248147 + pending
Bug#248147: debian-installer: netcfg/use_dhcp parameter can't be allowed on cdrom image
There were
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 221505 kernel
Bug#221505: Cannot configure network on sarge install
Bug reassigned from package `installation-reports' to `kernel'.
>
End of message, stopping processing h
Processing commands for [EMAIL PROTECTED]:
> tag 220496 d-i
Bug#220496: Beta 1 Installation Report
Tags were: moreinfo
Tags added: d-i
> clone 220496 -1
Bug#220496: Beta 1 Installation Report
Bug 220496 cloned as bug 253908.
> reassign -1 lilo-installer
Bug#253908: Beta 1 Installation Report
Bug
Quoting Joey Hess ([EMAIL PROTECTED]):
> So, did you also not commit the fix to the bug to svn? There's at least
> nothing in the changelog. If so a .10 release should be made with your fixes.
The fix mas commited. However, I forgot to add the changelog
entry. Funnily, when looking at the changel
Your message dated Fri, 11 Jun 2004 15:50:29 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing old installation report
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 is now your re
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 242343 debian-installer,
Bug#242343: debian-installer beta 3 sparc netinst image failed to boot up on Ultra10
Bug#247088: Unable to boot beta4 on sparc (SunBlade 150)
Bug r
On Thu, Jun 10, 2004 at 05:04:24PM +0100, Alastair McKinstry wrote:
> Hi,
>
> Can you please confirm whether or not you still see this problem?
>
> I do not have access to a sparc machine and cannot debug
> this without help
Hi,
I just tried it with last netboot image in sid (url attached).
W
On Thu, Jun 10, 2004 at 11:44:26AM +0200, Mikael Ljungberg, technordic wrote:
> Hi!
>
> I've bought an HP Proliant ML350 G3. On this computer there is a harddisk
> controller (HP Smart Array 641 Controller) that doesn't work with any
> linuxdistribution out of the box (the installation programs ca
|| On Fri, 11 Jun 2004 21:06:34 +0200
|| Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
pr> [Otavio Salvador]
>> Since sometimes is need change somefile before the base-installer is
>> run, I built the prebaseinstaller package. This is almost based in
>> prebasec
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 251902 kernel-source-2.6.6
Bug#251902: installation-reports: 2nd stage problem with Linux 2.6.6
Bug reassigned from package `installation-reports' to `kernel-source-2.6.6'.
severity 251861 grave
thanks
This bug is release crticial: it makes it impossible to install debian
with the 2.6 kernel.
We have a patch for the bug, but I don't know if Herbert will be
avilable to release it. Didn't he quit? So can someone step up and get a
fixed package into the archive?
An al
Martin Michlmayr wrote:
* W. Borgert <[EMAIL PROTECTED]> [2004-06-11 15:00]:
- Is RAID1 on / planned to be supported? IMHO, it doesn't
make much sense to have RAID1 support, but not on /. OK,
you may save the / or /boot from time to time manually
on the second disk, but that's not convenien
Your message dated Fri, 11 Jun 2004 15:18:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 is now your responsibility to reopen t
Your message dated Fri, 11 Jun 2004 15:17:39 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 is now your responsibility to reopen t
Your message dated Fri, 11 Jun 2004 15:16:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 is now your responsibility to reopen t
1 - 100 of 200 matches
Mail list logo
