Installing, booting, logical problem shown by D-I
I have a working machine with bookworm. Really nice one. It happen to be booted from an USB stick with DB12 SCSI10 for the moment And I want it to bring Debian 12 from this stick SCSI10 to another stick, SCSI9! which is prepared with db12-live now, but should be useable as quite normal bookworm on other machines. Here is the table shown by debian-install and its partitionering working machine with /dev/nvmw0n1, part of RAID! 1 MB Freier Speicher Nr.:1 536,9 MB B K ESP Nr.:2 998,6 GB ext4 Nr.:3 1 GB F SWAP 728 KB Freier Speicher SCSI9 (0.0.0)(sda) 126,6 GB Disk 3,0 to be installed, with DB12 "live".iso now. To be replaced by regular DB12. SCSI10 (0.0.0)(sdd) 7,9 GB Source disk with DB12.iso as the source and with D-I Problem: The working machine cannot be changed, therefore SCSI10 is booted. And SCSI9 has to be partioned. But! Partioning tries to influence the working machine, especially N r.:1, of course NR..3 too! And! What does B K ESP mean? Thanks for reading up to here:-) Ciao Matthias
[rt.debian.org #9382] Upgrade dillon to bullseye
On Sun Nov 19 07:53:22 2023, hwans...@mailbox.org wrote: > Hi, > > Am 19. November 2023 02:05:46 MEZ schrieb Cyril Brulebois > : > > Hi Adam, > > > > Adam D. Barratt via RT (2023-11-18): [...] > >> The d-i.debian.org metapackage fails to install on bullseye, because > >> it depends on ko.tex-base, which no longer exists in bullseye. The > >> removal notice suggests that its replacement is texlive-lang-korean, > >> which the metapackage already depends on for a few years now, so > >> hopefully dropping ko.tex-base shouldn't be an issue. > > > > That was an installation-guide dependency, removed in 2017, first > > released in 20180603: > > https://salsa.debian.org/installer-team/installation-guide/- > > /commit/3aa082a832ed636874995bf9e7bd25d0910c3365 > > > > Some more cleanup might be possible in there, but if you can build a > > package that's installable again right away, let's do that. Thanks, I've updated the metapackage to remove that dependency. > >> Do you see any issues with the upgrade from a d-i perspective? Are > >> there any particularly good times to do the upgrade, or that you'd > >> prefer to avoid? > > > > I'm less used to keeping an eye on the l10n machinery than Holger > > does, > > so you might want to wait for an explicit ACK there, but the rest I > > can > > probably check and fix/adjust as needed once the upgrade happens. > > > > No particular constraints on my side, thanks for asking. > > Yes, please go ahead at your own schedule Great, thanks both. Regards, Adam
Re: Installing, booting, logical problem shown by D-I
Hi Matthias ! Your mail appears to be a bit confused. On 19/11/2023 at 12:03, y...@vienna.at wrote: I have a working machine with bookworm. Really nice one. It happen to be booted from an USB stick with DB12 SCSI10 for the moment What does "DB12 SCSI10" mean ? And I want it to bring Debian 12 from this stick SCSI10 to another stick, SCSI9! What do you mean by "bring" ? Install ? which is prepared with db12-live now, but should be useable as quite normal bookworm on other machines. What do you mean by "prepared with db12-live" ? Did you write some live system image on it ? working machine with /dev/nvme0n1, part of RAID! 1 MB Freier Speicher Nr.:1 536,9 MB B K ESP Nr.:2 998,6 GB ext4 Nr.:3 1 GB F SWAP 728 KB Freier Speicher SCSI9 (0.0.0)(sda) 126,6 GB Disk 3,0 to be installed, with DB12 "live".iso now. To be replaced by regular DB12. SCSI10 (0.0.0)(sdd) 7,9 GB Source disk with DB12.iso as the source and with D-I What is DB12.iso ? Problem: The working machine cannot be changed, therefore SCSI10 is booted. What do you mean ? And SCSI9 has to be partioned. But! Partioning tries to influence the working machine, especially N r.:1, of course NR..3 too! What do you mean by "influence" ? And! What does B K ESP mean? "B" means "boot" because partman stupidly confuses the ESP type and the boot flag on GPT. "K" means "keep", do not reformat the partition.
Re: Bug#1055907: nmu: libalien-wxwidgets-perl_0.69+dfsg-6+b3
On Sat, 18 Nov 2023, Cyril Brulebois wrote: Scott Talbert (2023-11-16): Scott Talbert (2023-11-13): Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: libalien-wxwidgets-p...@packages.debian.org Control: affects -1 + src:libalien-wxwidgets-perl nmu libalien-wxwidgets-perl_0.69+dfsg-6+b3 . ANY . unstable . -m "Rebuild for wxwidgets3.2 (3.2.4+dfsg-1)" This looks like a redux of #1054146, with libwx-perl also needing a binNMU (after the libalien-wxwidgets-perl one)? Yeah, I did at least file both at the same time this round though :) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055908 I was trying to suggest filing both in the same request, to have them scheduled in one go. I tried to figure out how to do that with reportbug, but I did not see an obvious way to do it. For the future, how do I do that? Hand-written bug report? Scott
Re: Installing, booting, logical problem shown by D-I
Sun, 19 Nov 2023 20:55:16 +0100 Pascal Hambourg wrote: Hi Matthias ! And! What does B K ESP mean? "B" means "boot" because partman stupidly confuses the ESP type and the boot flag on GPT. "K" means "keep", do not reformat the partition. Oh! Thank you.
changed salsa-ci configuration for flash-kernel
The default salsa-ci pipeline for installer-team projects has always failed for flash-kernel, probably because flash-kernel builds no arch:amd64 packages. I recently merged a salsa-ci configuration from josch and switched flash-kernel to use a a salsa-ci pipeline that used arm64 runners instead, so that the pipelines could actually succeed. Now I have a bunch of green checkmarks for flash-kernel, yay! I do not know what, if anything, might be missing from this compared to the usual salsa-ci jobs for installer projects, so I figured it was worth mentioning here. Holler if this change broke anything! live well, vagrant signature.asc Description: PGP signature
