Your message dated Sun, 24 Jul 2011 08:47:12 +
with message-id
and subject line Bug#633158: fixed in debootstrap 1.0.33
has caused the Debian Bug report #633158,
regarding debootstrap: does not generate a sarge/amd64 chroot
to be marked as done.
This means that you claim that the problem has
Package: debootstrap
Version: 1.0.32
The unofficial sarge/amd64 release can't be installed:
sudo debootstrap --variant=buildd sarge ./base-sarge
http://archive.debian.org/debian-amd64/
I: Retrieving Release
E: Invalid Release file, no entry for main/binary-amd64/Packages
I see this i
Your message dated Fri, 22 Apr 2011 11:54:07 +0100
with message-id <201104221154.07174.el...@debianpt.org>
and subject line
has caused the Debian Bug report #314163,
regarding Sarge installer bug report
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Tue, 11 Jan 2011 22:49:16 +
with message-id <1294786156.3497.17.ca...@eeepc.belkin>
and subject line
has caused the Debian Bug report #299059,
regarding sarge network-preseed not getting executed
to be marked as done.
This means that you claim that the problem ha
Your message dated Sat, 08 Jan 2011 15:12:03 +
with message-id <1294499523.2463.159.ca...@eeepc.belkin>
and subject line
has caused the Debian Bug report #317941,
regarding Installing Sarge with separate /tmp mount causes wrong permissions
to be marked as done.
This means that you clai
Your message dated Sat, 08 Jan 2011 15:02:44 +
with message-id <1294498964.2463.157.ca...@eeepc.belkin>
and subject line
has caused the Debian Bug report #286614,
regarding Problem with existing LVM installation during Sarge install
to be marked as done.
This means that you claim th
Your message dated Sat, 08 Jan 2011 15:02:21 +
with message-id <1294498941.2463.156.ca...@eeepc.belkin>
and subject line
has caused the Debian Bug report #267441,
regarding install: Problems with sarge installer/grup/build-in sata controller
to be marked as done.
This means that you
PM, Steve Langasek wrote:
> On Mon, Nov 15, 2010 at 09:01:25AM -0500, Julien Savard wrote:
> > Debian Sarge was the last to officially support all sparc32 systems (wich
> > include sun4, sun4c, sun4d and sun4m). Etch support only sun4m and lenny
> > only support sparc64. I have a
On Mon, Nov 15, 2010 at 09:01:25AM -0500, Julien Savard wrote:
> Debian Sarge was the last to officially support all sparc32 systems (wich
> include sun4, sun4c, sun4d and sun4m). Etch support only sun4m and lenny
> only support sparc64. I have an old SparcStation5 ans a Sparc Classic w
The SparcStation 5 have CD-Rom drvie but it's broken (don't mount any CD).
The SparcClassic simply don't have Cd-Rom drive. I tried via floppies but it
was pain in the neck. I'm just installing it via tftp image.
On Mon, Nov 15, 2010 at 11:52 AM, Holger Wansing wrote:
> Hello,
>
> Julien Savard w
Hello,
Julien Savard wrote:
> If you have any suggestion exept tweaking old debian installer I'm open to
> any idea.
Which installation media do you use?
Do you have the possibility to boot from cdrom?
In that case, it should be possible to use a full binary installation cd
and install complete
Hi,
Debian Sarge was the last to officially support all sparc32 systems (wich
include sun4, sun4c, sun4d and sun4m). Etch support only sun4m and lenny
only support sparc64. I have an old SparcStation5 ans a Sparc Classic wich
are both sun4m. I already tried NetBsd but it's way too
Hi Julien,
On Wed, Nov 10, 2010 at 01:24:11PM -0500, Julien Savard wrote:
> I'm looking for something really particular. I'm trying to correct the
> debian sarge installation script and maybe adapt it to archive.debian.org as
> it's main mirror. It seems when the install
Hi,
I'm looking for something really particular. I'm trying to correct the
debian sarge installation script and maybe adapt it to archive.debian.org as
it's main mirror. It seems when the installation script was created the
developper didn't have in mind that the "mirro
Your message dated Mon, 13 Sep 2010 19:31:27 +0200
with message-id <20100913173127.gf3...@mykerinos.kheops.frmug.org>
and subject line No more floppies...no more bug
has caused the Debian Bug report #252426,
regarding Problems installing Sarge on OldWorld 7300/200 Mac
to be marked as done.
Your message dated Wed, 08 Sep 2010 03:58:26 +
with message-id
and subject line Closing old installation report #420425
has caused the Debian Bug report #420425,
regarding Installation problems in latest sarge and etch
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:15 +
with message-id
and subject line Closing old installation report #379193
has caused the Debian Bug report #379193,
regarding installation report sarge/etch
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2010 03:58:15 +
with message-id
and subject line Closing old installation report #378078
has caused the Debian Bug report #378078,
regarding failed sarge install on laptop
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2010 03:58:43 +
with message-id
and subject line Closing old installation report #364727
has caused the Debian Bug report #364727,
regarding install: Debian Sarge Install image kernel panics on a Sun Fire V100
(UltraSPARC-IIe 548MHz), No Keyboard
to be marked
Your message dated Wed, 08 Sep 2010 03:58:12 +
with message-id
and subject line Closing old installation report #364409
has caused the Debian Bug report #364409,
regarding Partitioning failure during install of Sarge 3.1r2
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:58:10 +
with message-id
and subject line Closing old installation report #354424
has caused the Debian Bug report #354424,
regarding Install report: sarge 3.1r1a
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2010 03:58:08 +
with message-id
and subject line Closing old installation report #344944
has caused the Debian Bug report #344944,
regarding z/VM install problems with "sarge"
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:08 +
with message-id
and subject line Closing old installation report #344328
has caused the Debian Bug report #344328,
regarding installation-reports: Debian "Sarge" installation on Alpha (PWS 433au)
to be marked as done.
This means that
Your message dated Wed, 08 Sep 2010 03:58:07 +
with message-id
and subject line Closing old installation report #342164
has caused the Debian Bug report #342164,
regarding Sarge Installer Bug Report: Kernel Module Fails To Load
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 08 Sep 2010 03:58:04 +
with message-id
and subject line Closing old installation report #330560
has caused the Debian Bug report #330560,
regarding Partitioning fails when setting up software RAID during Sarge install
to be marked as done.
This means that you claim
Your message dated Wed, 08 Sep 2010 03:58:04 +
with message-id
and subject line Closing old installation report #327287
has caused the Debian Bug report #327287,
regarding Cannot boot Sarge boot disk on Proliant 1500
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:04 +
with message-id
and subject line Closing old installation report #327047
has caused the Debian Bug report #327047,
regarding Successful installation of Sarge on a SparcStation5
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:58:02 +
with message-id
and subject line Closing old installation report #322114
has caused the Debian Bug report #322114,
regarding Sarge install report
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 08 Sep 2010 03:58:02 +
with message-id
and subject line Closing old installation report #321919
has caused the Debian Bug report #321919,
regarding Sarge 3.1_r0a installation problem with dvd-iso on computer with
DVD-player and CD-writer
to be marked as done.
This
Your message dated Wed, 08 Sep 2010 03:58:01 +
with message-id
and subject line Closing old installation report #319428
has caused the Debian Bug report #319428,
regarding HPPA 'Sarge'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 08 Sep 2010 03:58:01 +
with message-id
and subject line Closing old installation report #319231
has caused the Debian Bug report #319231,
regarding Package: installation-reports sarge
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:58:01 +
with message-id
and subject line Closing old installation report #317248
has caused the Debian Bug report #317248,
regarding install: Sarge install hangs when scanning disks (at 38%)
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:58:00 +
with message-id
and subject line Closing old installation report #316783
has caused the Debian Bug report #316783,
regarding Problems attempting to install Sarge (Hard drive is at /dev/hdg)
to be marked as done.
This means that you claim that
Your message dated Wed, 08 Sep 2010 03:58:00 +
with message-id
and subject line Closing old installation report #314357
has caused the Debian Bug report #314357,
regarding trouble with VIA RAID array when installing sarge
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:57:59 +
with message-id
and subject line Closing old installation report #311342
has caused the Debian Bug report #311342,
regarding sarge RC3 finds "no partionable media" with 82801FBM SATA disk
to be marked as done.
This means that you clai
Your message dated Wed, 08 Sep 2010 03:58:44 +
with message-id
and subject line Closing old installation report #309277
has caused the Debian Bug report #309277,
regarding debian-install netinstall sarge amd64
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 08 Sep 2010 03:58:42 +
with message-id
and subject line Closing old installation report #263077
has caused the Debian Bug report #263077,
regarding Debian Sarge beta 4: installation-reports
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:42 +
with message-id
and subject line Closing old installation report #261376
has caused the Debian Bug report #261376,
regarding hppa testing (sarge) very slow installer
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 08 Sep 2010 03:58:41 +
with message-id
and subject line Closing old installation report #260708
has caused the Debian Bug report #260708,
regarding PowerMac G3 (beige) sarge d-i (20 July 2004) Installation Report
installing quik
to be marked as done.
This means that
Your message dated Wed, 08 Sep 2010 03:58:41 +
with message-id
and subject line Closing old installation report #260403
has caused the Debian Bug report #260403,
regarding sarge install on powerpc RS/6000 7043-140 failed
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:58:41 +
with message-id
and subject line Closing old installation report #260225
has caused the Debian Bug report #260225,
regarding Sarge installer not recognising partition table for disk larger than
137GB
to be marked as done.
This means that you
Your message dated Wed, 08 Sep 2010 03:58:41 +
with message-id
and subject line Closing old installation report #260154
has caused the Debian Bug report #260154,
regarding PowerMac G3 (beige) sarge d-i Installation Report
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:58:39 +
with message-id
and subject line Closing old installation report #253312
has caused the Debian Bug report #253312,
regarding Installation failure for XFS over LVM on Test1 Sarge Netinstall CD
to be marked as done.
This means that you claim that
Your message dated Wed, 08 Sep 2010 03:58:39 +
with message-id
and subject line Closing old installation report #253161
has caused the Debian Bug report #253161,
regarding installation-reports, sarge-i386-netinst (beta4)
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:58:38 +
with message-id
and subject line Closing old installation report #251821
has caused the Debian Bug report #251821,
regarding d-i gives black screen Installing sarge beta4 and 20040530 on
OldWorld Power Macs
to be marked as done.
This means that
Your message dated Wed, 08 Sep 2010 03:58:38 +
with message-id
and subject line Closing old installation report #250934
has caused the Debian Bug report #250934,
regarding installation-reports, sarge beta 4
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:58:38 +
with message-id
and subject line Closing old installation report #250861
has caused the Debian Bug report #250861,
regarding installing base system fails with sarge-i386-businesscard.iso beta4
to be marked as done.
This means that you claim that
Your message dated Wed, 08 Sep 2010 03:58:38 +
with message-id
and subject line Closing old installation report #250768
has caused the Debian Bug report #250768,
regarding Error in sparc Beta 4 installer for Sarge
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:38 +
with message-id
and subject line Closing old installation report #250396
has caused the Debian Bug report #250396,
regarding sarge beta 4 powerpc installer issues
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 08 Sep 2010 03:58:38 +
with message-id
and subject line Closing old installation report #249955
has caused the Debian Bug report #249955,
regarding sarge beta 4 powerpc installer issues
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 08 Sep 2010 03:58:37 +
with message-id
and subject line Closing old installation report #249287
has caused the Debian Bug report #249287,
regarding failed sarge install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 08 Sep 2010 03:58:37 +
with message-id
and subject line Closing old installation report #248973
has caused the Debian Bug report #248973,
regarding sarge netinst hangs on scanning for ISO image
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:58:37 +
with message-id
and subject line Closing old installation report #248963
has caused the Debian Bug report #248963,
regarding Sarge Debian-installer installation error on SPARC IPX
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 08 Sep 2010 03:58:37 +
with message-id
and subject line Closing old installation report #248350
has caused the Debian Bug report #248350,
regarding d-i sarge sparc 20040315
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 08 Sep 2010 03:58:36 +
with message-id
and subject line Closing old installation report #248349
has caused the Debian Bug report #248349,
regarding d-i sarge sparc beta4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 08 Sep 2010 03:58:01 +
with message-id
and subject line Closing old installation report #318225
has caused the Debian Bug report #318225,
regarding sarge r0a i386 netinst partial success, IBM ThinkCentre 8189LDG
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:58:01 +
with message-id
and subject line Closing old installation report #318068
has caused the Debian Bug report #318068,
regarding Sarge/Sparc Installer refuses creation of Raid-Devices
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 08 Sep 2010 03:57:58 +
with message-id
and subject line Closing old installation report #309123
has caused the Debian Bug report #309123,
regarding Sarge install on Dell PE 1420 SCSI failed
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:57:58 +
with message-id
and subject line Closing old installation report #309028
has caused the Debian Bug report #309028,
regarding installation report Sun Ultra 10 sarge rc3
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:57:57 +
with message-id
and subject line Closing old installation report #306423
has caused the Debian Bug report #306423,
regarding Inst Problem SARGE Netinstall
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2010 03:57:57 +
with message-id
and subject line Closing old installation report #306148
has caused the Debian Bug report #306148,
regarding Error on sparc sarge rc2 install
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:57:57 +
with message-id
and subject line Closing old installation report #305127
has caused the Debian Bug report #305127,
regarding installation-reports: sarge on Dell Dimension 8400
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:57:57 +
with message-id
and subject line Closing old installation report #303812
has caused the Debian Bug report #303812,
regarding sarge floppy install report
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2010 03:57:56 +
with message-id
and subject line Closing old installation report #302238
has caused the Debian Bug report #302238,
regarding debian installer (sarge) fails on startup for b132l PA RISC (woody
worked)
to be marked as done.
This means that you
Your message dated Wed, 08 Sep 2010 03:57:55 +
with message-id
and subject line Closing old installation report #300719
has caused the Debian Bug report #300719,
regarding sarge installer is unable to mount any drive (ide-cd, ide-disk, etc.)
to be marked as done.
This means that you claim
Your message dated Wed, 08 Sep 2010 03:57:55 +
with message-id
and subject line Closing old installation report #300706
has caused the Debian Bug report #300706,
regarding debian sarge (debian-installer system) dvdrom and floppy issues
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:55 +
with message-id
and subject line Closing old installation report #299690
has caused the Debian Bug report #299690,
regarding installation-reports: sarge-i386-netinst.iso : daily and rc2 : don't
work for 15 days.
to be marked as done.
Your message dated Wed, 08 Sep 2010 03:57:55 +
with message-id
and subject line Closing old installation report #299169
has caused the Debian Bug report #299169,
regarding Sarge i386 netinst CD fails to boot
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:57:54 +
with message-id
and subject line Closing old installation report #298914
has caused the Debian Bug report #298914,
regarding Sarge mirror should include mdadm_1.9.0-2 for netinstall
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:54 +
with message-id
and subject line Closing old installation report #297754
has caused the Debian Bug report #297754,
regarding Keyboard not go at Sarge CD-NETINST
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:57:54 +
with message-id
and subject line Closing old installation report #296009
has caused the Debian Bug report #296009,
regarding Sarge installer
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 Wed, 08 Sep 2010 03:57:53 +
with message-id
and subject line Closing old installation report #294654
has caused the Debian Bug report #294654,
regarding sarge-386-netinst stops during base system installation
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 08 Sep 2010 03:57:53 +
with message-id
and subject line Closing old installation report #293644
has caused the Debian Bug report #293644,
regarding [powerpc] [rc2] Sarge installation report on Powerbook Lombard
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:53 +
with message-id
and subject line Closing old installation report #293506
has caused the Debian Bug report #293506,
regarding Debian sarge RC2 NewWorld PowerMac installation report
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 08 Sep 2010 03:57:52 +
with message-id
and subject line Closing old installation report #292586
has caused the Debian Bug report #292586,
regarding Fwd: Package: installation-reports for sarge in a Sun IPX
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:52 +
with message-id
and subject line Closing old installation report #292277
has caused the Debian Bug report #292277,
regarding Debian Installation Report (netinst cd image for sarge rc2)
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:51 +
with message-id
and subject line Closing old installation report #289820
has caused the Debian Bug report #289820,
regarding Sarge installer
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 Wed, 08 Sep 2010 03:57:51 +
with message-id
and subject line Closing old installation report #289536
has caused the Debian Bug report #289536,
regarding Installation Debian Sarge (Dezember 2004)
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:57:51 +
with message-id
and subject line Closing old installation report #288280
has caused the Debian Bug report #288280,
regarding sarge cd install hangs in reboot
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:57:51 +
with message-id
and subject line Closing old installation report #287830
has caused the Debian Bug report #287830,
regarding Hi there, install sarge on IBM xseries 305
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:57:51 +
with message-id
and subject line Closing old installation report #287576
has caused the Debian Bug report #287576,
regarding installation-reports: sarge install under VMware
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Sep 2010 03:57:50 +
with message-id
and subject line Closing old installation report #287177
has caused the Debian Bug report #287177,
regarding Sarge
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 Wed, 08 Sep 2010 03:57:49 +
with message-id
and subject line Closing old installation report #284933
has caused the Debian Bug report #284933,
regarding sarge installer freezes BIOS
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2010 03:57:49 +
with message-id
and subject line Closing old installation report #284696
has caused the Debian Bug report #284696,
regarding Sarge netinst-cd report
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 08 Sep 2010 03:57:49 +
with message-id
and subject line Closing old installation report #284128
has caused the Debian Bug report #284128,
regarding GRUB fails with Sarge RC2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 08 Sep 2010 03:57:48 +
with message-id
and subject line Closing old installation report #283011
has caused the Debian Bug report #283011,
regarding Sarge Installer does not install GRUB into MBR on Software RAID
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:48 +
with message-id
and subject line Closing old installation report #282997
has caused the Debian Bug report #282997,
regarding bug in sarge net-inst
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 08 Sep 2010 03:57:47 +
with message-id
and subject line Closing old installation report #281843
has caused the Debian Bug report #281843,
regarding sarge-i386 2.4 kernel on AMD64 install report
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 08 Sep 2010 03:57:45 +
with message-id
and subject line Closing old installation report #279330
has caused the Debian Bug report #279330,
regarding debian sarge installation report
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:57:45 +
with message-id
and subject line Closing old installation report #279161
has caused the Debian Bug report #279161,
regarding sarge sparc netinst
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 08 Sep 2010 03:57:45 +
with message-id
and subject line Closing old installation report #278893
has caused the Debian Bug report #278893,
regarding Debian-Installer and logical volume manager on dvd sarge-i386-1.iso
to be marked as done.
This means that you claim
Your message dated Wed, 08 Sep 2010 03:57:44 +
with message-id
and subject line Closing old installation report #277804
has caused the Debian Bug report #277804,
regarding installation report Sarge sparc64
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:57:43 +
with message-id
and subject line Closing old installation report #276517
has caused the Debian Bug report #276517,
regarding Installer Problem with Sarge
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 08 Sep 2010 03:57:42 +
with message-id
and subject line Closing old installation report #275758
has caused the Debian Bug report #275758,
regarding installation-reports: Debian Sarge install, netinst CD fails to boot
to be marked as done.
This means that you claim
Your message dated Wed, 08 Sep 2010 03:57:42 +
with message-id
and subject line Closing old installation report #275508
has caused the Debian Bug report #275508,
regarding sarge installer hang-ups
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 08 Sep 2010 03:57:42 +
with message-id
and subject line Closing old installation report #275049
has caused the Debian Bug report #275049,
regarding installer of sarge
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 08 Sep 2010 03:57:41 +
with message-id
and subject line Closing old installation report #274807
has caused the Debian Bug report #274807,
regarding Sarge RC2 Installation Report on IA64 Compaq DL590/64
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 08 Sep 2010 03:57:41 +
with message-id
and subject line Closing old installation report #274579
has caused the Debian Bug report #274579,
regarding sarge d-i rc2 install on Beige G3
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Wed, 08 Sep 2010 03:57:41 +
with message-id
and subject line Closing old installation report #274397
has caused the Debian Bug report #274397,
regarding installation-reports - Sarge - Alpha
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 08 Sep 2010 03:57:41 +
with message-id
and subject line Closing old installation report #274260
has caused the Debian Bug report #274260,
regarding Successful Sarge Debian-Installation rc1 on PowerPC Beige G3 from 2.6
ofonlyboot.img boot floppy
to be marked as done
1 - 100 of 1711 matches
Mail list logo
