Your message dated Mon, 22 May 2023 02:24:32 +0100
with message-id <20230522012432.gw5...@tack.einval.com>
and subject line Re: Bug#1036371: debian-installer: Blu-ray double-level iso is 
too large to burn to DLBD disk
has caused the Debian Bug report #1036371,
regarding debian-installer: Blu-ray double-level iso is too large to burn to 
DLBD disk
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1036371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20210731+deb11u8
Severity: important
Tags: d-i
X-Debbugs-Cc: budheal...@gmail.com

Dear Maintainer,

   * What led up to the situation?
Since the DLBD .iso install neither sets up sources.list with a mirror to
download from nor requests more disks to complete the set, a test of the
DLBD install when using actual Blu-ray disks were in order.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
RC3, packaged at 61-62GB per volume, can not be burned into DLBD media.
   * What was the outcome of this action?
The test could not even be started.
   * What outcome did you expect instead?
The DLBD volumes should be configured at 48-48.5GB. At 61GB, apt still
asks for new packages in /media/cdrom, which cannot possible be
satisfied. See bug#1035476 - editing sources.list as a workaround is, as
apt reminds each time, insecure.
All the packages d-i needs fit in the 25GB set, if not the 16GB one.
Then, the following volumes allow someone with a slow connection (like
mine) to complete an installation from media - if the volumes fit on the 
media.  Otherwise, the rest of the volumes are not easy to use as a
complete download of the distribution.

-- System Information:
Debian Release: (inserted) 12 RC3 --

--- End Message ---
--- Begin Message ---
OK, no worries. Closing this bug then...

On Sun, May 21, 2023 at 05:56:03PM -0400, Bud Heal wrote:
>My apologies. I built the DLBD .iso files and then moved them by USB because I
>was curious why occasionally more files keep being downloaded when I the files
>to scan already include them.
>The files I was talking about are the 2023-05-15 build, and I must have munged
>them by putting them on USB sticks, In the always-check-again department, over
>and out.
>
>On Sun, May 21, 2023 at 2:54 AM Steve McIntyre <st...@einval.com> wrote:
>
>    Hi Bud,
>
>    On Sat, May 20, 2023 at 02:54:00AM -0400, Bud Heal wrote:
>    >Package: debian-installer
>    >Version: 20210731+deb11u8
>    >Severity: important
>    >Tags: d-i
>    >X-Debbugs-Cc: budheal...@gmail.com
>    >
>    >Dear Maintainer,
>    >
>    >   * What led up to the situation?
>    >Since the DLBD .iso install neither sets up sources.list with a mirror to
>    >download from nor requests more disks to complete the set, a test of the
>    >DLBD install when using actual Blu-ray disks were in order.
>    >   * What exactly did you do (or not do) that was effective (or
>    >     ineffective)?
>    >RC3, packaged at 61-62GB per volume, can not be burned into DLBD media.
>
>    Just looking at the files on the server, those numbers surprise me...
>
>    debian-bookworm-DI-rc3-amd64-DLBD-1.jigdo:# Image size 48415279104 bytes
>    debian-bookworm-DI-rc3-amd64-DLBD-2.jigdo:# Image size 44362018816 bytes
>
>    Could you show exactly what size your images are coming out as, please?
>
>    --
>    Steve McIntyre, Cambridge, UK.                               
>    st...@einval.com
>    "I've only once written 'SQL is my bitch' in a comment. But that code
>     is in use on a military site..." -- Simon Booth
>
>
-- 
Steve McIntyre, Cambridge, UK.                                st...@einval.com
Welcome my son, welcome to the machine.

--- End Message ---

Reply via email to