Re: Finding a tentative bullseye release date
On Mon, 2021-06-07 at 20:38 +0200, Paul Gevers wrote: > Hi all, > > On 06-06-2021 20:03, Paul Gevers wrote: > > With the availability of Adam now known (and some off-list info), > > we have: > > [...] > > So, what to pick? We still believe that shorter freezes are better > > for > > the Debian community as a whole, so Steve can you look at turning > > your > > maybe on 10 July into a "lets go for this"? If the answer is no, > > than > > lets pick 24 July as the *tentative* release date. > > Nevermind 10 July. Steve, you can stop contemplating about it. We'll > go for 24 July as the *tentative* release date. Unfortunately I've just discovered that I was given the wrong date for a family event, so I'm actually going to be AFK for most of the 24th. :-( Apologies for sticking a slight spanner in the works at this stage. Adam
Re: Installer annoyance - a bug? [SOLVED - loop mount .iso images]
On Mon, Jun 07, 2021 at 05:23:47AM -0500, Richard Owlett wrote:
> On 06/06/2021 09:51 AM, Andrew M.A. Cater wrote:
> > On Sun, Jun 06, 2021 at 07:48:06AM -0500, Richard Owlett wrote:
> > > There is *functional/quality/?* difference between an install from a
> > > physical CD/DVD and from an "equivalent" flash drive.
> >
> > There's no functional difference: the .iso image is exactly the same.
>
> YOU ARE IN ERROR!
> There IS a functional difference *BECAUSE* the the image is identical.
> There is a hard-coded ASSUMPTION that the installation medium is a physical
> DVD.
>
There is no functional difference. None whatever.
I have just installed a machine from scratch using a flash drive with the
image of DVD1 written to it using dd.
-rw-r--r-- 1 user user 3972317184 Jun 7 16:19 debian-10.9.0-amd64-DVD-1.iso
The .iso images are hybrid - so bootable from either physical media or USB.
I used the expert install method. I disconnected any ethernet cables. I did
not include any firmware. When the installer detected network hardware, I let
DHCP fail and selected to not configure the network at this time.
I selected a minimum install set - text only, no GUI so unchecked the box
for a desktop environment, unchecked the box for printing but did select an
ssh server - when this is put on a network, I might want to SSH into it.
That installed a bare minimum - 116 packages or thereabouts.
I rebooted the machine, having removed the flash drive at the appropriate
point.
/etc/apt/sources.list referenced DVD1 - all other entries were commented out
because the machine had no network.
I then replaced the flash drive with DVD1 on once the machine had safely
booted.
I ran the dmesg command as root to find out where the flash disk had been
mounted. On this machine it was /dev/sdc - the last line of the dmesg output.
I ran apt-cdrom add to see which mount point it needed the medium to be
mounted to. The default is /media/cdrom
I then loop mounted the drive to get access to the iso file system
mount -o loop -t iso9660 /dev/sdc /media/cdrom
cd /media/cdrom, type ls and you see the file structure of the iso file that
you booted from.
At that point, running apt-cdrom add and hitting enter a couple of times and
you can install packages e.g. apt install vim
umount /media/cdrom - unmounting the flash drive effectively - and you're
done.
If you have other .iso files for DVD2, DVD3, DVD4 or whatever on a USB stick
do exactly the same for those .iso files.
If you then install a large metapackage like GNOME, you may be prompted to
change disks - you now know how to do that.
If you want to get fancy, you can mount all four DVDs to different
mount points and use apt-cdrom to add them all at once.
>From what I understand from your earlier posts on debian-user you don't like
loop mounting but it is the way to do this in the canonical way.
The files - and the installer - behave identically for physical disks or
for .iso images when loop mounted.
Hope this helps - glad to be of use to someone who searches for this again
All the very best, as ever,
Andy Cater
> > [SNIP]
> > >
> > > Is there some way, during the initial installation, to drop to a terminal
> > > to
> > > specify additional packages to be installed? As preseeding can do
> > > essentially the same thing the required framework must exist.
> > >
>
> Is there some way, during the initial installation, to drop to a terminal to
> specify additional packages to be installed?
> { As preseeding can do essentially the same thing the required framework
> must exist.}
>
> The installation manual recognizes that flash drives exist but does not go
> far enough that the new user can have the same access to all the packages on
> THAT installation medium.
>
>
>
Re: Finding a tentative bullseye release date
Hi all, On 06-06-2021 20:03, Paul Gevers wrote: > With the availability of Adam now known (and some off-list info), we have: > > 26 June > [Ansgar (ftp), Sebastian (release), Adam (release)] > 3 July > [Ansgar (ftp), Paul (release), Adam (release)] > 10 July > [Steve (CD) MAYBE , Ansgar (ftp), Paul (release), Adam (release), >Graham (release)] > 17 July > [Steve (CD), press, Ansgar (ftp), Paul (release)] > 24 July > [Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release), >Graham (release)] > 31 July > [Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)] > 7 August > [Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)] > 14 August > [Steve (CD), press, Ansgar (ftp), Sebastian (release), Adam (release)] > > So, what to pick? We still believe that shorter freezes are better for > the Debian community as a whole, so Steve can you look at turning your > maybe on 10 July into a "lets go for this"? If the answer is no, than > lets pick 24 July as the *tentative* release date. Nevermind 10 July. Steve, you can stop contemplating about it. We'll go for 24 July as the *tentative* release date. > Regardless of which of the two we pick, I propose we decide two weeks > before if it's going to be final. So, we'll decide around 10 July. > And, relevant for every maintainer of non-key packages without passing > autopkgtests, the full freeze will start two weeks before the > *tentative* release. The means that, with traditionally the last week > being totally frozen, the last week that packages can migrate *all* > packages need manual unblocks by the release team. And the Full Freeze will start on 10 July too. Paul OpenPGP_signature Description: OpenPGP digital signature
debian-installer-netboot-images_20210606_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Jun 2021 17:47:04 +0200 Source: debian-installer-netboot-images Architecture: source Version: 20210606 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Changes: debian-installer-netboot-images (20210606) unstable; urgency=medium . * Update for D-I Bullseye RC 2. * Fix error reporting when no fallback suite is defined: exit immediately instead of building empty packages. * Drop unused shared-lib-without-dependency-information lintian overrides. * Add myself to Uploaders. Checksums-Sha1: bd1ae7cae1313170855c2dccf5298d37f07d6362 2585 debian-installer-netboot-images_20210606.dsc 011f0f99f9460eaa9f02c8d49e75a0f7e7be6553 7680 debian-installer-netboot-images_20210606.tar.xz 8a110eaa2265f871aac878b1118d0900fe7f15a8 6356 debian-installer-netboot-images_20210606_source.buildinfo Checksums-Sha256: 065ce99c937c14d110d32cb9df2aeb51999a3fad86288983ce8b33ae2c980626 2585 debian-installer-netboot-images_20210606.dsc b0bd5bd34f386a0694fc668cb21067e2e980df4bbeec07674d4aeb3444e6c7f2 7680 debian-installer-netboot-images_20210606.tar.xz d7c3c0a8a4325549ab10ec623cf7b2087ce5a91d27f1020f5c80726cbeb05d13 6356 debian-installer-netboot-images_20210606_source.buildinfo Files: 902297f099fb88fde7dde8897876f0b6 2585 misc optional debian-installer-netboot-images_20210606.dsc e5b926e6dad6b2cb60a2cde184ea1b11 7680 misc optional debian-installer-netboot-images_20210606.tar.xz dc3926ef356d45c54f9337e3c213c8d2 6356 misc optional debian-installer-netboot-images_20210606_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmC+QCUQHGtpYmlAZGVi aWFuLm9yZwAKCRD/kUrwwrNVILGsD/0eIiC4d1Ha7fsNSGyhfV6HFCeN33n5Qqha +yGw5KJECsscwXrE2Lg6rs5qDjC0oe8rQUjATnX/o6CjmSyJM1oj/ZFAPsoXhUSm ICJg/dyQ2jIKlHcWoB3c9s7MidBbD0+8NtgFlpT0RTNFEzMi7PrNqvEyWchpHNwZ 4svY2D6OtLdFCQ1FoGIaif/5ZYepyiIQ+sOtbrh7/apE0Rc22DVYG1q7y/Mjp71u +dA2BUU2JZRUjh0cXZrwKF7xrjZi6GqQCW8Hv5EhOaH77dzvBOk7+ot8Pxa0CBfo HbJOunSfKEWH27IKaFqz/eVasBOOuBYovJmF7B1OLVKwcdlysiL07V1PaafwSdNJ zD+V3nCL82q7bF5Ayzm6NPEHo5L753Vm+zcKlqzMxzAspbtABPJx8VYj14G9Pcw7 JQnrVWR+cOGr4hVji3Kpt2IZXSA0z6XtFRiVprt3pM6Wj2naqoRb/+ToQNmiDLRQ Bdx97sYpl4Is12mfF/UKt0AqWQkrTVBMEwXtD1T/+Lr1pmu7ozfApLu1+VlXD7ua Wq1Vd+XzhUzsCGhp7InayonFvkB8J6CBOGg5VzR+CxK1BV8zFbW/GeEBO8qCgDTu Yf9JPImU+0yymRGAIMev1BljXDiSU63eqoatT/k+vfkT4HHWhBdcUf6j68PjC7X6 YYbXwNQJNw== =YmWw -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of debian-installer-netboot-images_20210606_source.changes
debian-installer-netboot-images_20210606_source.changes uploaded successfully to localhost along with the files: debian-installer-netboot-images_20210606.dsc debian-installer-netboot-images_20210606.tar.xz debian-installer-netboot-images_20210606_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: Installer annoyance - a bug?
On Sun, Jun 06, 2021 at 07:48:06AM -0500, Richard Owlett wrote: > There is *functional/quality/?* difference between an install from a > physical CD/DVD and from an "equivalent" flash drive. > > I have a very atypical use case: > 1. internet is *not* available to support installation. > 2. my goal is what I consider a minimalist GUI > > When I first used Squeeze: > 1. an internet install was impractical as I was on dial-up. > 2. physical CD/DVDs were readily available > 3. after booting into a minimal command line system my custom > system could easily be installed using apt-get > > Although I now have high speed connectivity, my data cap is low enough to > strongly discourage ANY installation related internet usage. > > I can easily install a command line system. BUT installing desired GUI > components via apt-get is impossible because it searches for a > *non-existent* physical CD/DVD. > > An install using a preseed file is possible but I find it cumbersome. > > Is there some way, during the initial installation, to drop to a terminal to > specify additional packages to be installed. As preseeding can do > essentially the same thing the required framework must exist. Well to save bandwidth at home, you could use jigdo to download the first bluray image and write that to a 32GB USB drive. That should cover most of the packages you are likely to ever want to install. And it avoids the 'swapping disks' that may not be as simple on a usb drive. This is assuming you have somewhere you could go with lots of bandwidth to run jigdo to download a 25GB image. -- Len Sorense
Re: Please dak copy-installer 20210606
Hi, Cyril Brulebois writes: > dak copy-installer 20210606 Done: +--- | Will copy installer version 20210606 from suite unstable to testing. | Architectures to copy: i386, amd64, mipsel, ppc64el, s390x, armel, armhf, arm64, mips64el | Architectures to skip: | Installer has been copied successfully. +--- Ansgar
Bug#989552: [patch] expand description of --variant
Package: debootstrap Severity: wishlist Tags: patch Thanks Hello please consider applying this small patch to the manpage. Kind regards Vince From 1e15507bacfb2547e1c2bace7c3781dd3ab2f45c Mon Sep 17 00:00:00 2001 From: Vincent McIntyre Date: Mon, 7 Jun 2021 20:29:08 +1000 Subject: [PATCH] Improve description of --variant A discussion on debian-boot@lists.d.o elicited an explanation of how deboostrap selects packages to install, which seems to be a point of confusion for some users While here, add a colon before the first item in the list of variants. --- debootstrap.8 | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/debootstrap.8 b/debootstrap.8 index e3ed5d7..2527707 100644 --- a/debootstrap.8 +++ b/debootstrap.8 @@ -80,7 +80,10 @@ set this option to track them through debootstrap.log. .IP .IP "\fB\-\-variant=minbase|buildd|fakechroot\fP" Name of the bootstrap script variant to use. -Currently, the variants supported are minbase, which only includes +Debootstrap reads the Packages file and determines which packages +to install based on the \fIPriority:\fR field of each package and +the selected variant. +Currently, the variants supported are: minbase, which only includes \fIrequired\fR packages and apt; buildd, which installs the build-essential packages and fakechroot, which installs the packages without root privileges. The default, with no \fB\-\-variant=X\fP argument, is to create a -- 2.31.1 --
Bug#989473: choose-mirror: switch mirror list from salsa to mirror-master
On Sat, 05 Jun 2021, Philip Hands wrote: > c) filter the old masterlist to only include entries that are also in > the new list, and then use the result of that, perhaps with a tweak > to promote deb.d.o > > c) is a bit of a cludge, but seems like the only one that's got a chance > of happening before the release, and gets most of the benefit of the new > list. The Type info in the salsa Masterlist is also probably not correct in a lot of cases. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#989473: choose-mirror: switch mirror list from salsa to mirror-master
On Sat, 05 Jun 2021, Philip Hands wrote: > Philip Hands writes: > > ... > > c) filter the old masterlist to only include entries that are also in > > the new list, and then use the result of that, perhaps with a tweak > > to promote deb.d.o > > BTW Promoting deb.d.o can be done thus: > > > https://salsa.debian.org/philh/choose-mirror/-/commit/70caed09fbf4bfbcc9eca82168cf3936868d8394 > > which produces this menu ordering: > > https://openqa.debian.net/tests/6101#step/mirror_selection/2 And then add a line that maybe gives some number (6, 7?) to other things matching ~/\.debian\.org$/? -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Re: Installer annoyance - a bug?
On 06/06/2021 09:51 AM, Andrew M.A. Cater wrote:
On Sun, Jun 06, 2021 at 07:48:06AM -0500, Richard Owlett wrote:
There is *functional/quality/?* difference between an install from a
physical CD/DVD and from an "equivalent" flash drive.
There's no functional difference: the .iso image is exactly the same.
YOU ARE IN ERROR!
There IS a functional difference *BECAUSE* the the image is identical.
There is a hard-coded ASSUMPTION that the installation medium is a
physical DVD.
[SNIP]
Is there some way, during the initial installation, to drop to a terminal to
specify additional packages to be installed? As preseeding can do
essentially the same thing the required framework must exist.
Is there some way, during the initial installation, to drop to a
terminal to specify additional packages to be installed?
{ As preseeding can do essentially the same thing the required framework
must exist.}
The installation manual recognizes that flash drives exist but does not
go far enough that the new user can have the same access to all the
packages on THAT installation medium.
