Bug#1069682: debian-cd DVD source run failing
Package: cdimage.debian.org As a reminder for me: the latest weekly build failed, looks like source packages no longer fit??? -- Steve McIntyre, Cambridge, UK.st...@einval.com "C++ ate my sanity" -- Jon Rabone
Re: Re-planning for 12.6
On Sat, Apr 20, 2024 at 05:41:13PM +0100, Jonathan Wiltshire wrote: >On Thu, Apr 18, 2024 at 10:58:41PM +0100, Steve McIntyre wrote: >> Hiya! >> >> Not wanting to pester *too* much, but where are we up to? >> > >Right now I can still have 27th April on the cards but we're missing FTP and >press. It's next week, we'd have to know this weekend and get frozen. >Mark indicated "maybe" and no answer from press. > >If that date works please reply urgently otherwise we're looking into May >and possibly just skipping to line up with the final bullseye anyway. It works for me, I guess. Dunno about other folks. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Changing random stuff until your program works is bad coding practice, but if you do it fast enough it’s Machine Learning.” -- https://twitter.com/manisha72617183
Re: Re-planning for 12.6
Hiya! Not wanting to pester *too* much, but where are we up to? On Tue, Apr 02, 2024 at 10:53:49PM +0100, Steve McIntyre wrote: >On Mon, Apr 01, 2024 at 01:07:27PM +0100, Adam Barratt wrote: >>Hi, >> >>As we had to postpone 12.6, let's look at alternative dates. >> >>April 13th >>- Not great for me for personal reasons, mhy previously said no. I >>could probably do if need be > >Works for me. > >>April 20th >>- Doesn't work for me; I'm away from the Tuesday before until late on >>the Friday > >Works for me. > >>April 27th >>- Doesn't work for me; I have a pre-existing appointment which means >>I'll be AFK much of the day > >Works for me. > >>May 4th >>- Apparently doesn't work for me; long weekend in the UK >> > >Works for me. > >>May 11th >>- Should work for me > >Nope, already booked for that Saturday. > >-- >Steve McIntyre, Cambridge, UK.st...@einval.com >"...In the UNIX world, people tend to interpret `non-technical user' > as meaning someone who's only ever written one device driver." -- Daniel Pead -- Steve McIntyre, Cambridge, UK.st...@einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen
Re: Re-planning for 12.6
On Mon, Apr 01, 2024 at 01:07:27PM +0100, Adam Barratt wrote: >Hi, > >As we had to postpone 12.6, let's look at alternative dates. > >April 13th >- Not great for me for personal reasons, mhy previously said no. I >could probably do if need be Works for me. >April 20th >- Doesn't work for me; I'm away from the Tuesday before until late on >the Friday Works for me. >April 27th >- Doesn't work for me; I have a pre-existing appointment which means >I'll be AFK much of the day Works for me. >May 4th >- Apparently doesn't work for me; long weekend in the UK > Works for me. >May 11th >- Should work for me Nope, already booked for that Saturday. -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead
Re: Upcoming stable point release (12.6)
On Fri, Mar 29, 2024 at 10:24:09PM +, Adam Barratt wrote: >On Fri, 2024-02-16 at 17:35 +, Jonathan Wiltshire wrote: >> The next point release for "bookworm" (12.6) is scheduled for >> Saturday, April 6th. Processing of new uploads into bookworm- >> proposed-updates will be frozen during the preceeding weekend. > >Due to recent events, the point release has been postponed. A new date >will be announced when possible. ACK, thanks for the update -- Steve McIntyre, Cambridge, UK.st...@einval.com Google-bait: https://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you.
Re: Where to download cd iso?
On Wed, Mar 27, 2024 at 02:24:10PM +0100, Thomas Schmitt wrote: >Hi, > >Tatsu Takamaro wrote: >> I've received my own message to you. But I don't see your answer... > >Well, i have't seen that message and the mailing list archive doesn't >show it either: > https://lists.debian.org/debian-cd/2024/03/threads.html >(The one i reply to is your follow-up: > https://lists.debian.org/debian-cd/2024/03/msg00022.html I didn't see it either. >> > I don't see the cd iso on the iso-cd page. >> > I mean a usual one, not a netinst. > >I guess they have been discontinued because of the insane number of ISO >images with 650 MB which would emerge. (I estimate ~ 130 pieces.) Exactly. Single CDs are just too small to be useful for most things now. We only just manage to fit the "netinst" into a single CD these days. >The smallest granularity seems to be the ~4.5 GB sized DVD images which >are available via Jigdo download: > https://cdimage.debian.org/debian-cd/current/amd64/jigdo-dvd/ >21 pieces. Yup. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
Re: Jigdo files wrong?
Hi Marcelo, On Mon, Mar 04, 2024 at 12:25:49PM -0300, Marcelo B. wrote: >Hi guys, there seem to be a problem with AMD64's jigdo files of the weekly >builds: they're all the same at 120 bytes in size. ACK, thanks for reporting. I'll take a look. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Why do people find DNS so difficult? It’s just cache invalidation and naming things.” -– Jeff Waugh (https://twitter.com/jdub)
Re: Planning for 12.6
On Mon, Feb 12, 2024 at 06:04:17PM +, Jonathan Wiltshire wrote: >Hi, > >12.6 should be around 10th April, so please indicate availability for: > >7 April >13 April >20 April Any of those should work for me, assuming (re Adam) that you mean 6 April and not 7 April. -- Steve McIntyre, Cambridge, UK.st...@einval.com Dance like no one's watching. Encrypt like everyone is. - @torproject
Bug#1059858: debian-cd: Missing firmware packages due to usr-move
control: tag -1 pending Tue, Jan 02, 2024 at 06:22:21PM +0100, Helmut Grohne wrote: >Hi Emanuele, > >On Tue, Jan 02, 2024 at 03:03:49PM +0100, Emanuele Rocca wrote: >> quite a few firmware packages are missing from today's debian-installer >> ISOs. Among the missing ones: firmware-atheros, firmware-realtek, and >> many others. Some firmware packages such as firmware-ath9k-htc and >> firmware-linux-free are instead present. >> >> Packages correctly included in the ISOs ship firmware files under /lib, >> while those not included use /usr/lib. For example the following is >> included: >> >> firmware-linux-free: /lib/firmware/av7110/bootcode.bin >> >> While missing packages install firmware files under /usr/lib: >> >> firmware-atheros: /usr/lib/firmware/wil6210.brd >> >> It seems likely that tools/generate_firmware_task needs to be patched to >> take usr-move into account. > >Yes, this very much looks like /usr-merge breakage and I fully agree >with the pointers you give. Just reading generate_firmware_task, the >contains_firmware sub immediately jumps into my eyes as the grep will >miss moved firmware packages. It should probably become > >grep ' \\./\\(usr/\\)\\?lib/firmware/' > >(with the double escaping for the target context already applied). > >I happen to not know how to test this though. Quite possibly, this is >not the only issue. Are you able to drive this forward from here? Already fixed in git, along with another usr-merge issue I found. The next regular build should be fine. Hmm, why didn't this get tagged as "pending" already when I pushed?? -- Steve McIntyre, Cambridge, UK.st...@einval.com Google-bait: https://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you.
Re: Planning for 12.5/11.9
On Tue, Dec 19, 2023 at 09:25:06PM +, Jonathan Wiltshire wrote: >Hi, > >It's time to set a date for 12.5 (taking account of the emergency .4) and >11.9. I expect this to be the penultimate update for bullseye before LTS. > >Please indicate availability for: > > Saturday 3rd February (preferred for cadence) > Saturday 10th February > Saturday 17th February Any of those *should* be OK for me. -- Steve McIntyre, Cambridge, UK.st...@einval.com Welcome my son, welcome to the machine.
Re: Problem with jigdo files
On Wed, Dec 20, 2023 at 05:48:52PM +0100, Thomas Lange wrote: > >I would guess he means the >debian-12.4.0-amd64-DVD-17.jigdo in the directory > >https://cdimage.debian.org/debian-cd/current/amd64/jigdo-dvd/ Right. I've tested DVD17 here and it rebuilds just fine. Can you ask this user to share more details of exactly what they're seeing please? -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross
Re: Problem with jigdo files
On Wed, Dec 20, 2023 at 09:03:47AM +0100, Thomas Lange wrote: >Hi, > >I've contacted some CD vendors that were providing old Debian releases >to update to the newest release. One of them replied, that >he was unable to create DVD17 with the jigdo file both i386 and >amd64. He asked for an alternative download of the ISO but IIRC we do >not provide torrents for these.Maybe you can check if there's a >problem with DVD17. >Attached is the german email of the person who reported this problem: *which* DVD 17, please? -- Steve McIntyre, Cambridge, UK.st...@einval.com "Managing a volunteer open source project is a lot like herding kittens, except the kittens randomly appear and disappear because they have day jobs." -- Matt Mackall
Bug#1057844: bookworm live images: d-i speech installation not loading sof firmware
On Sat, Dec 09, 2023 at 05:06:47PM +0100, Roland Clobus wrote: >On 09/12/2023 15:48, Steve McIntyre wrote: >> Package: cdimage.debian.org >> Severity: important >> Tags: a11y >> >> Testing the gnome live image for the 12.3 release... >> >> Running d-i from that image complained early on about missing Intel SOF >> firmware. Later on, the same image finds and loads intel wifi firmware >> just fine. Checking on the image, all the firmware debs are sym-linked >> in /firmware just fine but we don't have the extra metadata file >> (Contents file and dep11 stuff). Early on, AFAICS this means that the >> sof firmware isn't detected and loaded. >> >> Indeed, checking a d-i speech installation from this image, I don't >> get audio. Argh. >> >> Checking the same machine (Thinkpad T14s) with the amd64 netinst, it >> successfully loads firmware and starts the speech installer. > >This isn't new for Bookworm 12.3, is it? There has been no change in the >images generated by live-build regarding the /firmware folder, they have >always contained just the symlinked .deb files. Nod; this is just the first time I've realised this behaviour. >I only recently started to look deeper into the special folders for the >installer and noticed that the content of /firmware differs between the >netinst and the live images. > >Let's discuss this under less time pressure (today is the 12.3 release day). >I think that this ticket could be re-assigned (or cloned) to live-build for >the implementation of the fix. > >If needed, could a 12.3.1 live image be released, with just this fix, instead >of waiting for 12.4? For other reasons, we're about to do a quick-turnaround 12.4. But otherwise the sentiment is fine, yes! :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com Into the distance, a ribbon of black Stretched to the point of no turning back
Bug#1057844: bookworm live images: d-i speech installation not loading sof firmware
Package: cdimage.debian.org Severity: important Tags: a11y Testing the gnome live image for the 12.3 release... Running d-i from that image complained early on about missing Intel SOF firmware. Later on, the same image finds and loads intel wifi firmware just fine. Checking on the image, all the firmware debs are sym-linked in /firmware just fine but we don't have the extra metadata file (Contents file and dep11 stuff). Early on, AFAICS this means that the sof firmware isn't detected and loaded. Indeed, checking a d-i speech installation from this image, I don't get audio. Argh. Checking the same machine (Thinkpad T14s) with the amd64 netinst, it successfully loads firmware and starts the speech installer.
Bug#1056998: cdrom: Installation media changes after booting it
Hey Thomas!
On Tue, Dec 05, 2023 at 10:15:53AM +0100, Thomas Schmitt wrote:
>
>As for a better message from Integrity Check:
>
>I find in the ISO in file /install.amd/initrd.gz the lines:
> "The file ${FILE} failed the MD5 checksum verification. Your installation"
> "media or this file may have been corrupted."
>
>But i failed to find these texts in debian-cd or debian-installer
>Even searching for just "corrupted" yields only a remark in debian-cd.
>
>Does any of the bystanders know from what package this message text stems ?
That's cdrom-checker: https://salsa.debian.org/installer-team/cdrom-checker
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?
Re: Debian qcow2 image username and password
Hi Guillermo, On Mon, Nov 27, 2023 at 10:48:05PM +, Guillermo Zuniga wrote: > >We have downloaded the debian image: >debian-10-genericcloud-amd64-20230917-1506.qcow2, and we have deployed it on a >virtual machine in the cloud, however we cannot access the operating system >since it asks us for the username and password of authentication. Could you >tell us what the authentication username and password are or the procedure to >generate a username and password on the qcow2 image. The cloud team are responsible for that image (in CC). AFAIK you need to use cloud-init to set up authentication via SSH key - see https://wiki.debian.org/Cloud/#What_is_the_default_user_name_on_the_Debian_cloud_images.3F -- Steve McIntyre, Cambridge, UK.st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
Re: Planning for 12.3
On Fri, Oct 27, 2023 at 11:28:21AM +0100, Steve McIntyre wrote: >Argh, forgot to respond to this. :-( > >On Sat, Oct 07, 2023 at 06:59:03PM +0100, Jonathan Wiltshire wrote: >>Hi, >> >>The next point release for bookworm should be around the end of November >>2023. We're about a week behind cadence anyway, but I already know the 28th >>November will be unsuitable (Cambridge mini-debconf) and the weekend >>following is probably recovery time for a lot of people. >> >>Much after that we get into holidays and well off cadence. >> >>How about: >> 4th December (better for cadence) >> 11th December (more likely suitable in practice) > >Both of those currently look feasible for me. Do we have a decision being made yet please? -- Steve McIntyre, Cambridge, UK.st...@einval.com "War does not determine who is right - only who is left." -- Bertrand Russell
Re: Planning for 12.3
Argh, forgot to respond to this. :-( On Sat, Oct 07, 2023 at 06:59:03PM +0100, Jonathan Wiltshire wrote: >Hi, > >The next point release for bookworm should be around the end of November >2023. We're about a week behind cadence anyway, but I already know the 28th >November will be unsuitable (Cambridge mini-debconf) and the weekend >following is probably recovery time for a lot of people. > >Much after that we get into holidays and well off cadence. > >How about: > 4th December (better for cadence) > 11th December (more likely suitable in practice) Both of those currently look feasible for me. -- Steve McIntyre, Cambridge, UK.st...@einval.com "The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll
Re: Typo on https://www.debian.org/CD/faq/
Hi Roger! On Mon, Oct 23, 2023 at 03:44:18PM +0100, Roger Davies wrote: >Hello CD Team > >In the section titled: How do I write a CD/DVD/BD image to a USB flash drive? >4th bullet list item "...when the command suceeds, the USB flash..." > >suceeds should be spelled succeeds . Fixed, thanks! The change will appear in the next few hours on the next scheduled rebuild of the website. >Please send my prize t-shirt or other suitable reward to >Roger Davies >6 Ashley Road >Keyworth >Nottingham >NG12 5FJ Come along to the miniconf in Cambridge in November [1] and we may have some free stuff... [1] https://wiki.debian.org/DebianEvents/gb/2023/MiniDebConfCambridge -- Steve McIntyre, Cambridge, UK.st...@einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen
Re: question about weekly builds
On Fri, Oct 06, 2023 at 11:31:44AM +0200, UM Jérôme PEREZ wrote: >Hi. >To test weekly build, can i use apt-get or apt to upgrade weekly or is it >necessary to install weekly iso every week? You can absolutely just run apt to upgrade whenever you like. The reasons for the weekly builds are: * for testing of the installer * to allow people to install a clean new version of testing -- Steve McIntyre, Cambridge, UK.st...@einval.com You lock the door And throw away the key There's someone in my head but it's not me
Re: Enabling arm64 live image builds
Hey Emanuele! On Mon, Sep 25, 2023 at 12:59:46PM +0200, Emanuele Rocca wrote: > >Live images are currently only being built for x86 machines as far as I >can see on [1] and [2]. Yup. >I've tried building them on arm64 too, and everything worked perfectly >fine. I'm thus wondering whether it would be possible to build official >images for arm64 as well? It should be, but may need some extra build setup work. All the official installer and live images are built on casulana, our big amd64 build machine. We have some infra for doing builds in qemu VMs if needed, but I suspect that's going to be very slow. Meh, we can work our a solution for that at some point >Here's the commands I've used: > >$ lb config --distribution sid --updates false --bootloaders grub-efi >--archive-areas 'main non-free-firmware' >$ echo task-gnome-desktop > config/package-lists/desktop.list.chroot >$ sudo lb build > >The resulting image can be tested with qemu on a x86 host. > >For example: > >$ ISO=/var/tmp/live-image-arm64.hybrid.iso >$ cp /usr/share/AAVMF/AAVMF_VARS.fd /tmp >$ qemu-system-aarch64 -machine virt -cpu max,pauth-impdef=on -smp `nproc` -m >4G \ > -device qemu-xhci -device usb-kbd -device ramfb -device usb-tablet \ > -drive file=$ISO,format=raw,if=none,id=thumb -device > usb-storage,drive=thumb,bootindex=1 \ >-drive file=/usr/share/AAVMF/AAVMF_CODE.fd,if=pflash,readonly=true \ > -drive file=/tmp/AAVMF_VARS.fd,format=raw,if=pflash \ > -netdev user,id=net0 -device virtio-net-pci,netdev=net0 > >Click on View -> serial0 to follow the boot process, and switch back to >ramfb after gdm has started. OK. However, do we expect the image to be usable on any real machines as-is? -- Steve McIntyre, Cambridge, UK.st...@einval.com Welcome my son, welcome to the machine.
Re: Debian 9 live-cd standards iso missing
Hi Florian, On Thu, Aug 24, 2023 at 04:00:07PM +, Florian Holzbauer wrote: >Dear Debian Image Team, > >I relied on the standards iso live-cd iso files for some automated kernel >testing. >Why is there no standard isos available for stretch? > >Archive Path (e.g. 9.0.0, but affects all 9.x): >https://cdimage.debian.org/mirror/cdimage/archive/9.0.0-live/amd64/iso-hybrid/ >Full path for 8.11: >https://cdimage.debian.org/mirror/cdimage/archive/8.11.0-live/amd64/iso-hybrid/ >debian-live-8.11.0-amd64-standard.iso We never built any "standard" live images for stretch. We switched to a different build setup and it was left out. It was re-added for buster. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
Re: 11.8/12.2 planning
Apologies, I don't think I've responded to this yet :-( On Mon, Jul 24, 2023 at 07:25:13PM +0100, Jonathan Wiltshire wrote: >I think I confused matters with my messy thread; let's start again. > >I originally suggested: > >Jonathan Wiltshire (2023-06-28): >> The proper cadence for 11.8 and 12.2 is the weekend of 30th September >> 2023. Please indicate your availability for: >> >> 23 Sep >> 30 Sep (preferred) >> 7 Oct > >Let's say 30 Sep is still preferred, 7th Oct or at a stretch 14th Oct are >options. Please indicate your availability for those three. 23rd and 7th are fine, 30th may be more awkward for me. -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead
Re: Debian ISO Testing
Hi Martin! On Thu, Jul 27, 2023 at 04:52:29PM +0100, Martin McCarthy wrote: > >I'm very pleased to be involved in the Debian project. Thank you for having >me. Let me introduce myself. I'm Martin, I am a developer based in Manchester >in the UK and I've recently decided to dive head first into the wonderful >world of FOSS. I have been in the Microsoft ecosystem for the best part of >two decades and only ever dabbled in Linux and Debian a little bit during >that time. I recently took part in the Debian 12.1 ISO release event and I >had fun, learned a lot of things and met some interesting people (including >the former DPL Sledge). I had some suggestions based on my experience that I >would like to share with you. > >1) When I was conducting testing of Debian 12.1, I had an idea of writing a >"Testing Wizard" Bash/Perl/Python script to help with the testing process. A >simple shell script that will test the ISO against a predefined set of tests >and gather pertinent information (such as hardware information for the team). >The tester would run the script, all the automatic code would execute (such >as gathering hardware information, ISO name, boot time, etc) then the wizard >would guide the tester through a series of required tests and then possibly >some random ones thrown in (in order to increase chances of catching bugs >before publishing). I'd be interested to hear other people's opinions on it >and possibly we could have a session to discuss it in a bit more detail if >you're interested. If I'm overthinking it or over egging the pudding here, I >am also interested to hear your feedback there too. :-) You're describing something that overlaps quite a bit with what we've discussed already (your point 3 below). We'd like to have a system set up to guide testing and help us test most effectively: * minimise the number of tests we need to cover all the features * track what hardware people are using * lead people through the tests if needed, to make things easier >2) Recognition of testers. Although the small group over on #debian-cd on >OFTC were thankful for everyone's contributions including my own, it would be >really great for new testers like myself to have some kind of formal project >recognition. It may seem like a small thing but it makes a huge difference to >me personally. There are several ways of recognising the testers...some easy >some not so easy. Firstly, when publishing the release notes, naming the >testers (by their chosen names) that helped test the images before >publication would be a nice way to recognise us. Also, as cheesy as this may >seem or sound, awarding a certificate to recognise that that person has >participated in the Debian release testing process. Doesn't have to be >printed of course, it could be designed in Gimp or whathaveyou. I have mocked >a design which you can view here - > https://justpaste.it/de4hd (NB: this is >a heads up. This link is SFW...if you happen to be in the office right now). As Andy C already mentioned, we're already keen to track and recognise the efforts of volunteers in Debian. If you look at https://contributors.debian.org/ you'll see that we track what people are doing in a number of ways. If you follow the link to https://contributors.debian.org/source/Release%20image%20testers/ that's the set of data for people who've helped test our images. For you to appear there too, you just need to set up an account and log in to claim your data. The data is in the system, we just deliberately do *not* publically list people who haven't signed up. Privacy, etc... :-) >3) Overhaul of the wiki testing process. Rattus proposed some overhauling of >the ISO testing situation with the wiki. I am happy to work on that with you >Rattus if you get time and we have something where we don't need to wait for >the wiki to be released from another user. Although, I'm also happy to keep >it as is if that's what the community wants. If it's a nod to times of old, >I'm all for that too. I found the process quaint and reminded me of the old >days of locking Excel workbooks. :D *grin* >4) Automation. I read a thread on this mailing list recently talking about >openQA and whilst I am not opposed to automatic testing by machines, I would >insist that the manual testers are still retained as relying solely on >machines for QA can be problematic (machines are not perfect just like >humans). Not only that, the testers over on #debian-cd is a community and >having full automation would mean that community no longer meets regularly to >test stuff...and thus the community disperses and fades away over time. FOSS >to me is all about community so I would hope that openQA works alongside the >ISO testers rather than replace us. This is slightly off-topic but AI is >doing a lot of damage to co
Re: Push in git repo missing?
On Wed, Jul 26, 2023 at 10:53:15AM +0200, Roland Clobus wrote: >Hello Debian-cd Team, > >now that 12.1 has been released, is a push to the git repository at Salsa >missing? >The file `available/CONF.sh.bookworm_release` still mentions 12.0.0 Pushed now, thanks for the prod... -- Steve McIntyre, Cambridge, UK.st...@einval.com 'There is some grim amusement in watching Pence try to run the typical "politician in the middle of a natural disaster" playbook, however incompetently, while Trump scribbles all over it in crayon and eats some of the pages.' -- Russ Allbery
Bug#1032071: ARM firmware packages included in amd64 installation images
Control: severity 1035382 grave On Thu, Jul 06, 2023 at 06:29:49PM +0200, Magnus Wallin wrote: > >Hi Magnus, and thanks for the heads-up > >[ . . . ] > >Just because the raspi-firmware package is included on the d-i >installation media, it shouldn't necessarily be installed on an amd64 >host. Or is this coming from live images? > >Hi Steve! > >Speaking for myself: I installed from a live image on the release day of Debian >12. OK, that explains it. Let's try to get this fixed before 12.1... I can see that there is already #1035382 open on the live side, let's bump the severity on that. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Why do people find DNS so difficult? It’s just cache invalidation and naming things.” -– Jeff Waugh (https://twitter.com/jdub)
Bug#1032071: ARM firmware packages included in amd64 installation images
Hi Magnus, and thanks for the heads-up On Thu, Jul 06, 2023 at 06:13:28PM +0200, Magnus Wallin wrote: >> Just a head's up that this is starting to affect numerous people. >> If at all possible to prioritize it would be great. >> > >Sorry: I somehow managed to not include links in my previous message. > >Here below are examples of affected individuals and workarounds: >https://forums.debian.net/viewtopic.php?t=155195 >https://forums.debian.net/viewtopic.php?t=154857 Just because the raspi-firmware package is included on the d-i installation media, it shouldn't necessarily be installed on an amd64 host. Or is this coming from live images? -- Steve McIntyre, Cambridge, UK.st...@einval.com “Changing random stuff until your program works is bad coding practice, but if you do it fast enough it’s Machine Learning.” -- https://twitter.com/manisha72617183
Bug#1032071: ARM firmware packages included in amd64 installation images
On Mon, Feb 27, 2023 at 12:36:22PM +0100, Pascal Hambourg wrote: >Package: debian-cd >Version: 3.2.0 >Severity: minor > >debian-bookworm-DI-alpha2-amd64-netinst.iso includes firmware packages for >ARM platforms: > > firmware-qcom-soc > firmware-samsung > firmware-ti-connectivity > raspi-firmware Now all filtered in debian-cd unless we have an arm* architecture for the build. >These packages add 34 MB to the ISO image, which is not negligible. > >Additionally, IIUC the installer only needs firmware for storage, >network/wireless and sound devices. It uses generic graphic drivers for >display so it does not need GPU firmware. The netinst image includes firmware >packages which do not seem to be needed by the installer: > > bluez-firmware (Bluetooth) > dahdi-firmware-nonfree (VoIP) > firmware-amd-graphics (GPU) > firmware-ast (GPU) > firmware-ivtv (MPEG codec) > firmware-realtek-rtl8723cs-bt (Bluetooth) > firmware-siano (TV receiver) > hdmi2usb-fx2-firmware (?) > >Among them, firmware-amd-graphics takes 12 MB. >Is it useful to include these packages in the netinst image ? >Couldn't they be downloaded from a mirror like other ordinary packages when >needed ? I'm not currently filtering by build type, so I'm leaving these in. >Note: it also includes firmware-linux-nonfree which is a meta-package not >containing any firmware file. That's been fixed separately by other changes - we now check the contents of the firmware .debs too. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Managing a volunteer open source project is a lot like herding kittens, except the kittens randomly appear and disappear because they have day jobs." -- Matt Mackall
Re: 11.8/12.2 planning
On Wed, Jun 28, 2023 at 10:09:42AM +0200, Cyril Brulebois wrote: >Jonathan Wiltshire (2023-06-28): >> The proper cadence for 11.8 and 12.2 is the weekend of 30th September >> 2023. Please indicate your availability for: >> >> 23 Sep >> 30 Sep (preferred) >> 7 Oct > >I should be able to make any of those work for the installer team, and >optionally for the images team. 23rd and 7th are fine, 30th may be more awkward for me. -- Steve McIntyre, Cambridge, UK.st...@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Re: 11.8 planning
On Sat, Jun 24, 2023 at 03:17:22PM +0100, Jonathan Wiltshire wrote: >On Tue, Jun 20, 2023 at 06:15:30PM +0100, Adam D. Barratt wrote: >> The traditional cadence for oldstable point releases is four months, >> rather than two. That technically means that 11.8 would be due >> somewhere in late August to mid-September. So we could either punt 11.8 >> so it aligns with 12.2 rather than 12.1, or do 11.8 together with 12.1 >> and then align 11.9 with 12.3. >> >> I think I'd prefer the latter option, i.e. we do 11.8+12.1 in July, >> 12.2 probably September, then 11.9+12.3 Novemberish. >> > >Yes, I had forgotten about the transition to oldstable candece. I was going >to suggest, though, that 11.8 gets pushed back to cadence with 12.2 and we >just do 12.1 on its own first. How does that sound? WFM. -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead
Re: 11.8 planning
On Mon, Jun 19, 2023 at 10:02:27PM +0100, Jonathan Wiltshire wrote: >Hi, > >I'm sending this separately to a similar mail for 12.1. That's because the >timings are far enough out that they would make sense on separate weekends, >but they could also be stretched[1] and combined. > >Two months from 29th April is around the 1st July, so I propose: > >1st July >8th July >15th July at a push > > >1: a shame that joke hasn't worked for some years now 1st July is out for me, but I can do the others fine. -- Steve McIntyre, Cambridge, UK.st...@einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen
Re: 12.1 planning
On Mon, Jun 19, 2023 at 10:04:06PM +0100, Jonathan Wiltshire wrote: >Hi, > >The promised 4-6 weeks following release for 12.1 looks like: > > 8th July (4) >15th July (5) >22nd July (6) > >The first of them would combine with a very stretched 11.8; SRM might >prefer to get 11.8 done earlier and leave more time for 12.1 to mature. All of those work for me. -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross
Re: Bug#1036371: debian-installer: Blu-ray double-level iso is too large to burn to DLBD disk
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 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.
Re: Bug#1036371: debian-installer: Blu-ray double-level iso is too large to burn to DLBD disk
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
Re: i386 in the future (was Re: 64-bit time_t transition for 32-bit archs: a proposal)
Andrew Cater wrote: >On Fri, May 19, 2023 at 03:03:40PM +0100, Steve McIntyre wrote: >> >> I had been thinking about doing similar for installer images too, but >> with other work going on too I think it got too late in the cycle to >> make that change. My plan is therefore to ship i386 installer images >> for bookworm as normal (including bookworm point releases going >> forwards), but to disable those builds for testing/trixie ~immediately >> after the release. > >I'd honestly suggest *just* publishing DVD1 for i386. > >Netinst requires internet access: DVD1 can be used to install a basic >system without this. Scrap *everything else* for i386 installation media. We've had this discussion before. I don't see the point in removing choice here at *really* short notice before bookworm, but still keeping a non-zero number of installer images for the architecture. It saves us very little effort and doesn't really gain us anything. This is why I'm talking *now* about dropping things for trixie. -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Re: 11.7 planning + bookworm planning
On Sun, Apr 23, 2023 at 09:13:40PM +0200, Paul Gevers wrote: >Hi all, > >Let's book June 10 as the bookworm release date. A more formal announcement >will follow. \o/ -- Steve McIntyre, Cambridge, UK.st...@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Re: 11.7 planning + bookworm planning
On Thu, Apr 20, 2023 at 08:20:51PM +0200, Paul Gevers wrote: >Hi all, > >TL;DR: ftp & press input for June needed. > >On 20-04-2023 18:29, Adam D. Barratt wrote: >> The 13th does seem a bit close now, without having announced. > >After some consideration today, and the vibe felt in this discussion, let's >not rush this, so let's skip May 13 (also giving Press some time, see below). > >> One other thing of note is that, unless I've missed some mail, there's >> no press / publicity team member confirmed as available, which is >> really a requirement. > >Jonathan (DPL) mentioned earlier: >""" >Press team is in some slight limbo at the moment, I hope to help fix that >after the DPL election is over, in the mean time, it might be a good idea not >to block on them. >""" >If press is "really a requirement", we'll have to wait until this is settled. > >From the CD side we know that with May 13 out, the rest of May is also out. >So we're looking for a date in June. For June, starting with 10, we have: >kibi - 10, 17, 24d-i >Luna - 10, 17, 24CD testing >elbrus- 10, 24release team >adsb - 10, 17, 24release team Sledge - 10, 17, 24images team -- Steve McIntyre, Cambridge, UK.st...@einval.com Is there anybody out there?
Re: 11.7 planning + bookworm planning
On Thu, Apr 20, 2023 at 11:32:49AM +0200, Paul Gevers wrote: >Dear all, > >Progress \o/. > >On 13-04-2023 11:29, Paul Gevers wrote: >> For me to do the release, I'd need to get my hands on the key. > >I'm in contact with Jonathan and we're convinced we'll be able to get the key >to me in time. > >Which leaves finding a date (and me learning what to do :) ). OK... >We have (if earlier mentioned dates still work for those involved): >May | June >> kibi - 13, 20, 27 d-i >> mhy - 13, 20, 27 ftp >> Sledge- 13 CD >> Luna - 20 CD testing >> elbrus- 13 27, (3), 10, 24 release team > >It seems a tiny bit late for 13 already, but still, would be awesome. What do >we think? I'm still OK for the 13th. >If we have somebody from CD to do 27 (yes, I remember Sledge can't >do that one), that would be great as it would be my preference; I'll have >lots of Debian people physically around me. As the DPL mentioned, we might >not want to block on press availability, although it would be real great if >we had them. Unfortunately, the other person on the images team who has the knowledge to do a release (Andy) is also away - we're on the same vacation! May 27 and June 3 are both out for that reason. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Changing random stuff until your program works is bad coding practice, but if you do it fast enough it’s Machine Learning.” -- https://twitter.com/manisha72617183
Re: .zsync files for the weekly live images
On Sun, Apr 16, 2023 at 09:36:37PM +0200, Roland Clobus wrote: >Hello Debian-Images team, > >(and reply to self for the second time) :-) > >On 12/04/2023 17:03, Roland Clobus wrote: >> On 08/04/2023 10:48, Roland Clobus wrote: >> > I've tested the .zsync files on [1]. >> > They currently don't work, because the original filename >> > (live-image-amd64.hybrid.iso) is embedded in those files. > >I've chosen to turn off zsync: >https://salsa.debian.org/images-team/live-setup/-/merge_requests/3 Nod, fair enough. Merged. >Reasons: >* The package zsync was orphaned for 1.5 years ago >* The package zsync does not support https for the URL with the .zsync file >* Minor reason: The live-build-binary script could generate the images with >the correct filename part, but the extension (.hybrid.iso) is fixed by the >live-build package. ACK. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
Re: 11.7 planning + bookworm planning
Hey Paul, Nobody else seems to have replied yet, so... :-) On Thu, Mar 23, 2023 at 01:31:22PM +0100, Paul Gevers wrote: >Hi, > >With the point release scheduled for April 29th, it's probably good to have >at least one weekend in between, or do people not mind doing two weekends in >a row? Definitely *not* two weekends on the run, please! >On 17-03-2023 15:59, Steve McIntyre wrote: >> On Thu, Mar 16, 2023 at 11:26:00AM +0100, Paul Gevers wrote: >> > So, shall we add availability for May too? 6th, 13th, 20th (Ascension >> > weekend), and 27th (coincides with DebianReunionHamburg)? >> >> I could do the 6th and 13th, but I'm away on vacation 20th and 27th >> (and 3rd June). > >If I did the bookkeeping correctly, the missing necessary teams are press and >release team, as I now have: >kibi - 6, 13, 20, 27 d-i >mhy - 6, 13, 20, 27 ftp >Sledge- 6, 13 CD >Luna - 6, 20 CD testing > >I can help 6 (probably), 13 and 27, but I don't have the signing key and I >haven't witnessed all details from our side so I'm not comfortable doing it >alone even if I could get my hands on the key. > >elbrus-13, 27 release team 13th could work. I'll admit I'm a little anxious about the amount of work needed before release, but tbh that's not a new thing here... :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com "This dress doesn't reverse." -- Alden Spiess
Re: Starting the weekly live images for Bookworm building again
Hey again, On Tue, Jan 31, 2023 at 03:36:53PM +, Steve McIntyre wrote: >> >>As you can see, this affects many teams: >>* live-setup: a MR to generate all live images for Bookworm [A2] So, after some delay from me and some further delays from various Debian machines committing suicide [1], I've got bookworm live builds running again. \o/ I've taken Roland's updated patches and tweaked a little more in the setup.git and live-setup.git repos, and we now have live builds integrated. Changes I've added: * turned on source tarball generation using LB_SOURCE=true, and disable the external source build that we dod for the older live-wrapper builds * when building on casulana, warn about archive updates rather than restarting builds * don't attempt to build i386 live images any more, they're not useful * tweaked logging So, *builds* work fine but I've not *yet* tested actually booting/using one of these images in any way. I've just triggered a full build of "testing" live images now, please help test if you can once they're in place at [2] in a couple of hours from now. I don't yet know how close we are to having full non-free-firmware integration with the live images; I expect there might be some more work needed there yet, but I'd love to be proven wrong. :-) [1] "yay" for the long-standing tradition of services failing as we get close to a release: this time it was casulana and salsa... [2] https://get.debian.org/images/weekly-live-builds/ -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead
Re: 11.7 planning + bookworm planning
On Thu, Mar 16, 2023 at 11:26:00AM +0100, Paul Gevers wrote: > >From where I'm looking, bookworm is looking pretty good. Obviously we'll have >to follow through on the flurry of unblock requests that came in after the >hard freeze, but that should be manageable in a couple of weeks. kibi just >told me on IRC that asking this question now is not crazy from a d-i point of >view. That hopefully means that around the end of April, also the bookworm >d-i should™ be ready for release (kibi, I'm sure you'll comment on this if I >got you wrong or if you want to provide more details). > >So, shall we add availability for May too? 6th, 13th, 20th (Ascension >weekend), and 27th (coincides with DebianReunionHamburg)? I could do the 6th and 13th, but I'm away on vacation 20th and 27th (and 3rd June). -- Steve McIntyre, Cambridge, UK.st...@einval.com 'There is some grim amusement in watching Pence try to run the typical "politician in the middle of a natural disaster" playbook, however incompetently, while Trump scribbles all over it in crayon and eats some of the pages.' -- Russ Allbery
Re: 11.7 planning
On Wed, Mar 15, 2023 at 08:33:47PM +, Jonathan Wiltshire wrote: >Hi, > >We're overdue for 11.7 and need it done with a keyring update included >before bookworm can be released. The wheels are turning on the keyring so >how do dates in April look for everybody? Saturdays are 1st (probably too >soon), 8th, 15th, 22nd and 29th. I think I'm clear for any of: 8th 22nd 29th -- Steve McIntyre, Cambridge, UK.st...@einval.com Google-bait: https://www.debian.org/CD/free-linux-cd Debian does NOT ship free CDs. Please do NOT contact the mailing lists asking us to send them to you.
Bug#1031696: Use of symbolic links in non-free ISO images breaks file system transposition support
On Sun, Mar 12, 2023 at 05:43:24PM +, James Addison wrote: >Followup-For: Bug #1031696 > >Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS >achieve the desired result for both documentation and firmware files, without >requiring any other changes? No, then I expect we'll simply end up with duplicate copies of the files. >(I'll mention as context that there are symlinks in the debian-faq tarball >that is used as input for the on-disc documentation) Then a better answer for this edge case is to manually flatten the symlinks to hard links. But of course that will only work for files and won't work for directories. Probably best not to worry about the FAQ tarball here, to be honest. -- Steve McIntyre, Cambridge, UK.st...@einval.com "This dress doesn't reverse." -- Alden Spiess
Bug#1031696: Also affects bookworm
Hi Pete, On Thu, Mar 09, 2023 at 08:24:08PM +, Pete Batard wrote: >Please note that, since bookworm has started to include firmware files, this >issue is also starting to affect bookworm users [1] and I can only advise >Debian maintainers to raise its priority, rather than dismiss it as something >that will only affect folks who don't use DD mode to write the ISOHybrid, as >this is going to affect people who are used to simply extracting the ISO >content onto FAT32 media to install Debian on a UEFI system. > >In short, if this issue is left unaddressed, bookworm will be introducing a >*regression* compared to bullseye, in that it will no longer be possible to >perform a Debian installation on a UEFI system through file system >transposition, and everyone will be forced to either use DD or use a utility >(like Rufus 3.22) that includes a *custom workaround* for Debian, in order to >duplicate the symbolically linked firmware files. It looks like James (with some help from Thomas) has worked out a quick way to change things to make things better for you, which is good! (Thanks, guys! I'm about to test the change locally.) *However* you're the *only* person I've seen complaining about this problem with "file system transposition". I genuinely have not seen issues raised by people doing this, except where (it seems) Rufus is working this way. Let's be clear: "transposition" == "copying things onto a less capable filesystem". I'm normally really impressed by your skills and knowledge, but I don't understand why you seem to be so obsessed by this. With some tweaks like this MR, simply copying files onto FAT32 can clearly be made to work for UEFI-only media. That's fine. But it still breaks other useful features, at least: * BIOS boot * image checksums and those are important for me and a lot our users. Seriously, just using DD or similar gives people a verifiable, known-good copy of our installer image that will boot on as many machines as possible and work well in the debian-installer environment. That's my primary goal here. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
Re: "up to 300 mb in size"
On Wed, Mar 08, 2023 at 05:23:29AM -0500, nick black wrote: >Steve McIntyre left as an exercise for the reader: >> Yup, we know. Things are growing over time. >> In fact, the bookworm release will be bigger again due to including >> firmware too. > >my sincere apologies if this came off as a complaint about the >size or anything else; i just wanted to bring it to the team's >attention =]. perhaps a salsa MR might have been a better >approach. Not at all. No worries, thanks for mentioning it! :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
Re: "up to 300 mb in size"
On Wed, Mar 08, 2023 at 02:53:43AM -0500, nick black wrote: >the netinst page claims: > > Up to 300 MB in size, this image contains the installer and a > small set of packages which allows the installation of a (very) > basic system. > > netinst CD image (generally 150-300 MB, varies by architecture) > >but we're now at 400MB on amd64: > > [schwarzgerat](0) $ ls -l downloads/debian-11.6.0-amd64-netinst.iso > -rw-r--r-- 1 dank dank 406847488 2023-03-08 02:47 > downloads/debian-11.6.0-amd64-netinst.iso > [schwarzgerat](0) $ > >just thought i'd let y'all know! Yup, we know. Things are growing over time. In fact, the bookworm release will be bigger again due to including firmware too. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say." -- Edward Snowden
Bug#1031424: add config option to control mixed-mode EFI on x86
Package: debian-cd Version: 3.1.36 Severity: normal [ Reminder for me ] I've added support for mixed-mode EFI stuff on amd64 builds. Add an option to enable/disable it, so that local hack builds don't need both amd64 and i386 d-i builds to function. -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-21-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debian-cd depends on: ii apt2.2.4 ii bc 1.07.1-2+b2 ii bzip2 1.0.8-4 ii cpp4:10.2.1-1 ii curl 7.74.0-1.3+deb11u5 ii dctrl-tools [grep-dctrl] 2.24-3+b1 ii dpkg-dev 1.20.12 ii genisoimage9:1.1.11-3.2 pn libcompress-zlib-perl pn libdigest-md5-perl ii libdigest-sha-perl 6.02-1+b3 ii libdpkg-perl 1.20.12 ii libfile-slurp-perl .32-1 ii libyaml-libyaml-perl 0.82+repack-1+b1 ii lynx 2.9.0dev.6-3~deb11u1 ii make 4.3-4.1 ii perl [libdigest-sha-perl] 5.32.1-4+deb11u2 ii tofrodos 1.7.13+ds-5 ii wget 1.21-1+deb11u1 ii xorriso1.5.2-1 Versions of packages debian-cd recommends: ii dosfstools 4.2-1 ii hfsutils 3.2.6-15 ii isolinux 3:6.04~git20190206.bf6db5b4+dfsg1-3 ii mtools 4.0.26-1 ii syslinux-common 3:6.04~git20190206.bf6db5b4+dfsg1-3 debian-cd suggests no packages. -- no debconf information
Re: Weekly testing is same as a week ago, it seems
On Tue, Feb 07, 2023 at 11:53:10AM +0100, Cyril Brulebois wrote: > >Sorry for the breakage, and thanks for prodding. > >I've indeed worked a lot on the netinst, and it looks like I might have >broken other kinds of images in the process, my apologies. It's probably >as easy as making that “else” part conditional (only tweaking that file >if it exists), but since I'm not familiar with other kinds of images, >I'll let Steve comment on whether that's (1) expected and (2) the best >way to fix this issue. I wouldn't want to paper over a possible bug… That's exactly the fix I just came up with independently, so I've just pushed it now. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Yes, of course duct tape works in a near-vacuum. Duct tape works anywhere. Duct tape is magic and should be worshipped." -― Andy Weir, "The Martian"
Re: Starting the weekly live images for Bookworm building again
Hey Roland, Apologies for leaving you waiting a while :-/ On Mon, Jan 16, 2023 at 05:35:50PM +0100, Roland Clobus wrote: > >This is a follow-up of my mail from 2022-11-21 [A1]. > >I've made progress in the last two months, but would like to have some merge >requests approved, to get more traction and to allow others to jump aboard >and make the live images for Bookworm possible. > >As you can see, this affects many teams: >* live-setup: a MR to generate all live images for Bookworm [A2] ACK, I'll take a look at this again shortly. >* localechooser: A minor fix [A3] No idea about that, leaving for somebody else. >* live-installer: A better user experience after the installer is finished >[A4] Merred just now. >* live-build: Various installer improvements, including off-line installation >[A5] Not sure who might review that, let's see -- Steve McIntyre, Cambridge, UK.st...@einval.com < Aardvark> I dislike C++ to start with. C++11 just seems to be handing rope-creating factories for users to hang multiple instances of themselves.
Bug#1024346: cdrom: debian-11.5.0-amd64-netinst.iso boots to Grub CLI on Dell Optiplex 5090
On Fri, Nov 25, 2022 at 03:28:28AM +, r...@tekhax.io wrote: > >That seems to have been the problem. Thanks! Awesome, thanks for confirming. I've just pushed a fix to the debian-cd build scripts which should fix this for future builds. -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
Bug#1024346: cdrom: debian-11.5.0-amd64-netinst.iso boots to Grub CLI on Dell Optiplex 5090
Hi Rob, I see Andy has been helping you! On Sat, Nov 19, 2022 at 03:38:33PM +, r...@tekhax.io wrote: >Thanks, after messing with it for quite awhile, I finally got it to work with >the standard ISO. > >I booted with the Arch live image and did: > >wipefs -a /dev/nvme0n1 >dd if=/dev/zero of=/dev/nvme0n1 bs=512 count=10 > >then I used efibootmgr to delete all existing entries. > >Once I did that, the netinst booted into the installer >immediately. Not sure if it was the actual existence of valid >partitions on the drive, or just the existence of EFI entries in the >table. If your system has (had) existing EFI boot entries, then the firmware would normally attempt to boot those. AIUI you selected the USB stick and that failed to boot? The partitioning on Debian images is slightly complex, to make them work as a so-called "isohybrid". (This means that you can use the same image both when written to optical media and when written to a USB stick.) But the partitions should still show up. For example, looking at the netinst image file here: $ fdisk -l debian-11.5.0-amd64-netinst.iso Disk debian-11.5.0-amd64-netinst.iso: 382 MiB, 400556032 bytes, 782336 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x5004a58b Device Boot StartEnd Sectors Size Id Type debian-11.5.0-amd64-netinst.iso1 *0 782335 782336 382M 0 Empty debian-11.5.0-amd64-netinst.iso2 4064 92475184 2.5M ef EFI (FAT-12/16/32) The first partition covers the whole of the image; the second one is *just* the EFI boot setup that you've seen already. If you're only seeing the second partition then it appears there is some other problem here. Checking your original report here, you said you wrote to the USB stick using dd if= of=/dev/sdb. Did you run "sync" or similar to make 100% sure that the image was all flushed to the USB stick before removing it / booting it? Unless you tell it otherwise, Linux will cache writes to USB drives and it can appear that writes have completed well before the data is actually written to the drive. This is a common cause of confusion for people in this situation, I'm afraid. Andy already mentioned a different way to force writing data, using the "oflag=sync" option to dd. Using that with "bs=4M" should also give good performance when writing out an image to a USB stick. Could you possibly retry this and check if it works for you please? -- Steve McIntyre, Cambridge, UK.st...@einval.com < liw> everything I know about UK hotels I learned from "Fawlty Towers"
Re: 11.6 planning
On Thu, Nov 17, 2022 at 09:33:33PM +, Adam Barratt wrote: >Hi, > >We've managed to slip behind on getting a bullseye point release >sorted, again. :-( I realise we're heading towards the holidays at a >surprising rate of knots, but hopefully we can find a generally >agreeable date. > >Please could you indicate your availability and preferences between: > >- December 3rd >- December 10th >- December 17th > >At this point, the 10th is probably my preference, as I'm likely to be >busy with work stuff at the tail end of November. I'm away on a work trip on the 1st and 2nd, due back home sometime on the 3rd. I could do a release, but I'd be starting later than normal. Maybe Andy could start it and I'd catch up with him when I'm back. I'm busy on the evening of the 10th, but we can work around that if needed. The 17th looks clear and hence would be easiest for me. -- Steve McIntyre, Cambridge, UK.st...@einval.com 'There is some grim amusement in watching Pence try to run the typical "politician in the middle of a natural disaster" playbook, however incompetently, while Trump scribbles all over it in crayon and eats some of the pages.' -- Russ Allbery
Re: échec installation debian
[ Re-adding a CC to the debian-cd list ] Maybe you'd get better help on the debian-user-french mailing list. On Wed, Nov 09, 2022 at 01:45:00PM +0100, Rima AOUADENE wrote: >Hi! >I have a Mac Os, I don't arrive to install debian! > >Le mar. 8 nov. 2022 à 15:02, Steve McIntyre a écrit : > >Hi Rima! > >On Tue, Nov 08, 2022 at 01:37:36PM +0100, Rima AOUADENE wrote: >>Good morning, >>I send you this mail because I can't install the version debian for mac! >>can you explain me why? > >Could you give us some more information please: > > * what machine are you using? > * which exact image are you using? (URL will help) > * how are you trying to boot the system? > >-- >Steve McIntyre, Cambridge, UK. >st...@einval.com >"War does not determine who is right - only who is left." > -- Bertrand Russell > > -- Steve McIntyre, Cambridge, UK.st...@einval.com “Changing random stuff until your program works is bad coding practice, but if you do it fast enough it’s Machine Learning.” -- https://twitter.com/manisha72617183
Re: échec installation debian
Hi Rima! On Tue, Nov 08, 2022 at 01:37:36PM +0100, Rima AOUADENE wrote: >Good morning, >I send you this mail because I can't install the version debian for mac! >can you explain me why? Could you give us some more information please: * what machine are you using? * which exact image are you using? (URL will help) * how are you trying to boot the system? -- Steve McIntyre, Cambridge, UK.st...@einval.com "War does not determine who is right - only who is left." -- Bertrand Russell
Re: CDimages go 2 NET INSTALLERS
On Tue, Nov 01, 2022 at 10:07:23AM +0100, J.A. Bezemer wrote: > >On Tue, 1 Nov 2022, Steve McIntyre wrote: > >[..] >> The netinstall image *is* a CD image. For example, from >> >> https://cdimage.debian.org/cdimage/release/current/amd64/iso-cd/ : >> >> What is a netinst image? >> >> The netinst CD here is a small CD image that contains just the core >> Debian installer code and a small core set of text-mode programs >> (known as "standard" in Debian). To install a desktop or other >> common software, you'll also need either an Internet connection or >> some other Debian CD/DVD images. > >The "other *CD* images" is incorrect since we do not produce other CD images >any more. The /CD/http-ftp/ states: "it's possible to use CD images (700 MB >each)" which is equally incorrect. This may have caused OP's >misunderstanding. *Possibly*, yeah. Let's fix that now... -- Steve McIntyre, Cambridge, UK.st...@einval.com "Since phone messaging became popular, the young generation has lost the ability to read or write anything that is longer than one hundred and sixty characters." -- Ignatios Souvatzis
Re: CDimages go 2 NET INSTALLERS
You don't mention exactly which page(s) you're looking at, which makes it difficult to identify if you've actually found a problem here. :-( On Mon, Oct 31, 2022 at 01:39:09PM -0500, Fresh Air wrote: > >It's clear to me that you all do NOT check your own links on your website. >I'm trying to download a CD image, but wouldn't you know it, ALL TEN LINKS to >the different archs go to the "Net instal" which only has three image files. The netinstall image *is* a CD image. For example, from https://cdimage.debian.org/cdimage/release/current/amd64/iso-cd/ : What is a netinst image? The netinst CD here is a small CD image that contains just the core Debian installer code and a small core set of text-mode programs (known as "standard" in Debian). To install a desktop or other common software, you'll also need either an Internet connection or some other Debian CD/DVD images. >Do you even link bro? Can you translate that to English please? -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
Re: Issue with preseeded install - cannot skip apt media scanning
Hi Jerzy, You might be better off asking on the debian-boot mailing list (in CC). On Sat, Oct 22, 2022 at 04:50:20PM +0200, Jerzy Patraszewski wrote: >Hi debian-wizards, >I'm seeking your wisdom, since I'm almost banging my head against the wall... >Any ideas how to get rid of the described error and achieve fully unattended >Debian install? >Thanks in advance, any suggestion will be much appreciated! >Jerzy > >The issue: >While using preseed file, regardless of any setting, debian installer (dialog) >jumps off to interactive mode on error: "Apt configuration problem. An attempt >to configure apt to install additional packages from the media failed". This >happens just after installing the base system. After pressing continue - apt >scans mirror correctly and the rest of the process goes unattended till the >end. > > >Preseed file includes (whole file can be here: http://paste.debian.net/1257950/ >): ><...> >d-i apt-setup/cdrom/set-first boolean false >d-i apt-setup/cdrom/set-next boolean false >d-i apt-setup/cdrom/set-failed boolean false > >apt-cdrom-setup apt-setup/cdrom/set-first boolean false >apt-cdrom-setup apt-setup/cdrom/set-next boolean false >apt-cdrom-setup apt-setup/cdrom/set-double boolean false >apt-cdrom-setup apt-setup/cdrom/set-failed boolean false ><...> > >The boot command: >auto=true priority=critical preseed/url=http://[IP:port]/debian-preseed.txt > >ISO file used for installation: >debian-cd/current/amd64/iso-cd/debian-11.5.0-amd64-netinst.iso > >Additional info: >From https://preseed.einval.com/debian-preseed/bullseye/amd64-main-full.txt >it seems that only apt-setup/cdrom/set-failed should be sufficient: > >### Description: Scan extra installation media? ># An attempt to configure apt to install additional packages from the ># media failed. ># . ># Please check that the media has been inserted correctly. ># d-i apt-setup/cdrom/set-failed boolean true > >Unfortunately this does not work :/ -- Steve McIntyre, Cambridge, UK.st...@einval.com "I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop" -- Vivek Das Mohapatra
Bug#1021702: debian-cd: Take constraints into account while building the cd packages pool
Hi Arnaud, On Thu, Oct 13, 2022 at 05:13:03PM +0700, Arnaud Rebillout wrote: ... >By entering a chroot, and trying to install the king-phisher package, >using the pool of packages provided in the Kali installer, I get: > > # apt install king-phisher > [...] > The following packages have unmet dependencies: > python3-fonttools : Depends: python3-unicodedata2 (>= 14.0.0) but it is not > installable or >python3-all (>= 3.11.0) but 3.10.6-1 is to be > installed > E: Unable to correct problems, you have held broken packages. > >Looking at the dependency tree now: > > king-phisher > +-- python3-matplotlib >+-- python3-fonttools > +-- python3-unicodedata2 (>= 14.0.0) | python3-all (>= 3.11.0) > >In the pool of packages that are available in the Kali iso, we don't >have python3-unicodedata2 , however we have python3-all , BUT it's at >version 3.10.6-1 ... So nothing can satisfy the dependency. > >So it looks to me that it's a bug in debian-cd. I guess that the >resolver that decides which packages are included in the pool didn't >include python3-unicodedata2 because there was python3-all already, but >it didn't take into account the constraints >= 3.11.0. If you check in sort_deps.$ARCH.log, that'll tell you what dependency resolution happened. >As a sidenote, it looks like the maintainer of python3-fonttools is a >bit ahead of time, his package depends on python3-unicodedata2 (>= >14.0.0) | python3-all (>= 3.11.0) but 3.11 is not yet released, it's >planned for end of October. > >Note that this is an issue only for installers that don't have access to >the network. If network is available, I guess that python3-unicodedata2 >will be fetched from a remote package repository, so no problem for most >users. ACK. -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Re: sha512sum-error at debian-live-11.5.0-amd64-gnome.iso
Thanks Thomas! On Wed, Oct 12, 2022 at 09:04:06AM +0200, Thomas Schmitt wrote: >Hi, > >just for the records i report what Gerd Mühlenbruch and i found out >off list: > >The reason for the bad dowload was that two wget processes were writing >to the same file. > >Gerd had started the first wget by letting nautilus executing it. For >this it created a terminal window with a running wget, which Gerd soon >after closed by means of the desktop. >Then he wanted to continue downloading by starting wget in terminal >window. > >Closing the nautilus-made terminal would normally shut down the program >that is running in it. Not so with wget, where the man page says: > > Wget is non-interactive, meaning that it can work in the background, > while the user is not logged on. This allows you to start a retrieval > and disconnect from the system, letting Wget finish the work. > >We did not explore what exactly causes the oversize of the download result. >The situation of two simultanously working wgets on the same file is ill >enough to serve as explanation. > > >Have a nice day :) > >Thomas > > -- Steve McIntyre, Cambridge, UK.st...@einval.com "C++ ate my sanity" -- Jon Rabone
Bug#1017540: cdimage.debian.org: i386 DVD 1 iso fails to install - md5 file integrity
Hi Dominik! On Wed, Aug 17, 2022 at 01:09:45PM -0400, dominik wrote: >Package: cdimage.debian.org >Severity: normal >Tags: ftbfs a11y >X-Debbugs-Cc: domin...@organworks.com > >Dear Maintainer, > >Attempting an install of .i386 DVD 1 through USB stick, the Install process >stops shortly after >searching for installation files, bringing up a read error. Running the md5 >integrity check will eventually >find an error with some file on the system, though the specific file varies on >installation attempts. Thus it is not >possible to install the .iso. This is despite correct sha256sum checks. A >netinst iso is available and works fine, >as a temporary workaround. This suggests that *maybe* your USB stick is faulty - this can be all-too-common problem. How are you writing the image to it please? Could you also please double-check that the image is written correctly by doing a checksum readback from the USB stick afterwards? -- 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
Bug#1016954: cdimage.debian.org: Installing from live system sets up LUKS1 partitions instead of LUKS2
Hi Markus! On Wed, Aug 10, 2022 at 02:20:08PM +, Legner, Markus wrote: >Package: cdimage.debian.org >Severity: normal >X-Debbugs-Cc: markus.leg...@siemens.com > >I've found some inconsistent installation behavior between the "normal" >installer and the installer from the live system on the live image [1]: > >When choosing to encrypt the system, the installer from the live system >sets up >LUKS1, while the normal installer (from the same image) sets up a LUKS2 >partition. I'm not sure if this is intentional but it's definitely >unexpected >considering the announcement of using LUKS2 by default already in >Buster [2]. >(There are some other inconsistencies as well; for example the LVM >option.) ACK. The live installer (Calamares) does things quite differently to d-i, and we cna't always guarantee that they'll be in sync for things like this. :-( -- Steve McIntyre, Cambridge, UK.st...@einval.com < Aardvark> I dislike C++ to start with. C++11 just seems to be handing rope-creating factories for users to hang multiple instances of themselves.
Re: Time to drop win32-loader ?
On Tue, Jul 19, 2022 at 03:46:09PM +0200, Didier 'OdyX' Raboud wrote: >Hello there, >(please CC me on replies, I'm not on these lists) > >(live from the d-i/debian-cd BoF) > >as some of you likely remember, win32-loader is shipped on d-i and debian-cd >images, and is added in autorun.inf for automated launch on Windows machines, >when USB/CDs are plugged in. What it does is allow a machine booted in Windows >to download a d-i image, put a grub image and d-i in C:/debian-installer, and >fiddle with the (old?) Windows bootloader to allow selection of d-i upon >reboot. It either works from the image, or downloading stuff from internet. > >I haven't checked (as I don't have access to Windows machines...), but I'm >quite confident that the Windows Bootloader fiddling is quite unlikely to work >on modern (Secure Boot ?) machines. > >That brings two sides of the question: >* should it still be shipped on amd64 netinsts, CD's, other images? >* should it still be offered on the mirrors ? > on https://deb.debian.org/debian/tools/win32-loader/stable/ > (where it lands via dak's byhand handling upon uploads; but is manually > moved by ftp-master on migrations and release days) > >(I orphaned win32-loader back in September, and it still doesn't have an >official maintainer; but I'd be happy to work towards ditching it away :-P) Let's kill it, agreed. Please file a bug against debian-cd and I'll remove it from our setup there. -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead
Re: [debian...@casulana.debian.org: testingcds 3sidamd64 (amd64 dvd) has failed; log included]
Hey Raphael! On Tue, Aug 09, 2022 at 07:55:21PM +0200, Raphael Hertzog wrote: >Hello, > >On mar., 09 août 2022, Raphael Hertzog wrote: >> Ah, sure, that seems quite likely. I did not have the issue in my >> tests, but I tested with a partial mirror as created by simple-cdd so I >> quite likely did not hit the problematic recursive dependency. >> >> Can you point me to the debian-cd configuration that I shall use to reproduce >> the issue? > >So the issue was not trivial to reproduce. FWIW, it's only reproducible in >bullseye, for some reason buster was coping fine with it. Hmmm, OK. >But I got it reproduced and the problem was due to packages which have >strong "Recommends" like libapreq2-dev which has "Recommends: >libapreq2-doc (= 2.13-7+b3)" which is not satisfiable. It would never stop >its recursion because the version found was not good for it. Argh. >So in the end I have a new patch in the hertzog/bug601203 branch. I'm >doing some further tests but it seems to solve the issue: >https://salsa.debian.org/images-team/debian-cd/-/commit/ca9ac8deac5c1436f4b311a22a34a56f236dfe05 > >But as I investigated I found more things to fix, like quite >some dead code: >https://salsa.debian.org/images-team/debian-cd/-/commit/e77ade6033445571092e8663ad94a24c7e882b03 > >I'm going to push this soon but I would love if someone else could >do a test run and ensure it doesn't break anything else. > >I have created a merge request to make it easier to review the code if >anyone wants to do it: >https://salsa.debian.org/images-team/debian-cd/-/merge_requests/26 I can have a look, but not *right* now I'm afraid - swamped with other stuff. Hopefully by the end of the week... -- Steve McIntyre, Cambridge, UK.st...@einval.com “Changing random stuff until your program works is bad coding practice, but if you do it fast enough it’s Machine Learning.” -- https://twitter.com/manisha72617183
Re: [debian...@casulana.debian.org: testingcds 3sidamd64 (amd64 dvd) has failed; log included]
Hey Raphael On Tue, Aug 09, 2022 at 09:00:59AM +0200, Raphael Hertzog wrote: > >On lun., 08 août 2022, Steve McIntyre wrote: >> This weekly DVD run just tooke ~15h to run compared to the normal ~30m >> or so. Checking the stuff in the log here, I'm thinking that this >> "Deep recursion on subroutine" message is very likely due to your >> changes in commit cc4e1fa450a074ef1428bf678a57cdf8b0d0f0e5. Could you >> take a look please? > >Ah, sure, that seems quite likely. I did not have the issue in my >tests, but I tested with a partial mirror as created by simple-cdd so I >quite likely did not hit the problematic recursive dependency. > >Can you point me to the debian-cd configuration that I shall use to reproduce >the issue? It's the weekly config that builds all the full media sets. The DVD build on its own will show it: B_amd64_dvd config start: amd64.cfg start export ARCH=amd64 export VARIANTS=xen export MAXISOS=1 export MAXJIGDOS=ALL export MAX_PKG_SIZE= export DESKTOP=all export INSTALLER_CD=3 export KERNEL_PARAMS="desktop=all" export TASK=Debian-all export DRYRUN_WAIT=0.5 export FORCE_CD_SIZE1=STICK4GB;; dvd.cfg end B_amd64_dvd config end: -- Steve McIntyre, Cambridge, UK.st...@einval.com "... the premise [is] that privacy is about hiding a wrong. It's not. Privacy is an inherent human right, and a requirement for maintaining the human condition with dignity and respect." -- Bruce Schneier
Re: [debian...@casulana.debian.org: testingcds 3sidamd64 (amd64 dvd) has failed; log included]
On Mon, Aug 08, 2022 at 07:56:49PM +0100, Steve McIntyre wrote: >Hey Raphaël! > >This weekly DVD run just tooke ~15h to run compared to the normal ~30m >or so. Checking the stuff in the log here, I'm thinking that this >"Deep recursion on subroutine" message is very likely due to your >changes in commit cc4e1fa450a074ef1428bf678a57cdf8b0d0f0e5. Could you >take a look please? Sorry, I meant 8513b237afbdb59a4a59d1bc707d37f0aa9138f7 of course. -- Steve McIntyre, Cambridge, UK.st...@einval.com "I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop" -- Vivek Das Mohapatra
Re: [debian...@casulana.debian.org: testingcds 3sidamd64 (amd64 dvd) has failed; log included]
On Mon, Aug 08, 2022 at 07:56:49PM +0100, Steve McIntyre wrote: >Hey Raphaël! > >This weekly DVD run just tooke ~15h to run compared to the normal ~30m >or so. Checking the stuff in the log here, I'm thinking that this >"Deep recursion on subroutine" message is very likely due to your >changes in commit cc4e1fa450a074ef1428bf678a57cdf8b0d0f0e5. Could you >take a look please? Checking on the build machine just now, I could see that a number of sort_deps processes were chewing up ~40G of memory each. I'm going to revert your commit for now and re-trigger the weekly build. -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross
[debian...@casulana.debian.org: testingcds 3sidamd64 (amd64 dvd) has failed; log included]
Hey Raphaël!
This weekly DVD run just tooke ~15h to run compared to the normal ~30m
or so. Checking the stuff in the log here, I'm thinking that this
"Deep recursion on subroutine" message is very likely due to your
changes in commit cc4e1fa450a074ef1428bf678a57cdf8b0d0f0e5. Could you
take a look please?
- Forwarded message from cdimage creator role
-
From: cdimage creator role
To: st...@einval.com
Date: Mon, 08 Aug 2022 18:29:33 +
Subject: testingcds 3sidamd64 (amd64 dvd) has failed; log included
Message-Id:
Error when trying to create cds for 3sidamd64
Mon Aug 8 03:20:26 UTC 2022: Using CONF from
/home/debian-cd/build.bookworm/CONF.sh.
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make
rule.
make[1]: Entering directory
'/srv/cdbuilder.debian.org/git/setup/bookworm/debian-cd'
rm -rf
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/CD[1234567890]*
rm -rf /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/tasks
rm -f /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/*.filelist*
rm -f
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/packages-stamp
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/upgrade-stamp
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/checksum-check
echo "Cleaning the build directory"
Cleaning the build directory
rm -rf /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/apt
rm -rf /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64
make[1]: Leaving directory
'/srv/cdbuilder.debian.org/git/setup/bookworm/debian-cd'
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make
rule.
make[1]: Entering directory
'/srv/cdbuilder.debian.org/git/setup/bookworm/debian-cd'
mkdir -p /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64
mkdir -p /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm
mkdir -p /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/apt
...
Generating the complete list of packages to be included in
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list...
perl -ne 'chomp; next if /^\s*$/; \
print "$_\n" if not $seen{$_}; $seen{$_}++;' \
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/rawlist \
> /srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list
/home/debian-cd/build.bookworm/debian-cd/tools/check_backports_packages
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list.backports
if [ -f
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list.backports ];
then mv
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list.backports
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list; fi
for ARCH in amd64; do \
ARCH=$ARCH /home/debian-cd/build.bookworm/debian-cd/tools/sort_deps
/srv/cdbuilder.debian.org/src/deb-cd/tmp/3sidamd64/bookworm/list; \
done
Running sort_deps to sort packages for amd64:
Generating dependency tree with apt-cache depends...
Adding standard, required, important and base packages first
S/R/I/B packages take 124138086 bytes
Adding the rest of the requested packages
Deep recursion on subroutine "main::add_missing" at
/home/debian-cd/build.bookworm/debian-cd/tools/sort_deps line 1139, line
52916.
Deep recursion on subroutine "main::add_missing" at
/home/debian-cd/build.bookworm/debian-cd/tools/sort_deps line 1142, line
52916.
Killed
make[1]: *** [Makefile:484: image-trees] Error 137
make[1]: Leaving directory
'/srv/cdbuilder.debian.org/git/setup/bookworm/debian-cd'
- End forwarded message -
--
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.
Re: buster EOL (10.13) and 11.5 planning
Hey Adam! On Thu, Jul 28, 2022 at 05:09:52PM +0100, Adam Barratt wrote: > >Use of buster-security will pass from the Security Team to LTS in a few >days time, so we should get the EOL point release organised. We need at >least a couple of weeks to get things sorted, so as some suggestions: > >- August 20 >- [August 27 doesn't work for at least me and the Images Team, so nope] >- September 3rd >- September 10th August 20th or September 10th work best for me, with a slight preference for the latter so we have as much time as possible for shim signing in the two releases. I can do September 3rd at a push, but it will be difficult for me to commit to a double release that weekend as I have plans on Sunday 4th. >We're currently only 3 weeks past the 11.4 bullseye point release, but >that was also about 6 weeks late. It's therefore worth considering >whether we want to try and get 11.5 out sooner and get back onto the >previous track, or delay it a little more and aim for every two months >from 11.4's release date. > >tl;dr - please indicate your availability / preferences for the above >dates (for both 10.13 and 11.5) and any opinions on whether we should >do them at the same time or separately. Happy to do a double release on 20/08 or 10/09, or a single release or 03/09. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Why do people find DNS so difficult? It’s just cache invalidation and naming things.” -– Jeff Waugh (https://twitter.com/jdub) signature.asc Description: PGP signature
Re: New unofficial Debian 11.4 release torrent files not registered in the bittorent tracker
Hi Blaž! On Mon, Jul 11, 2022 at 01:24:30PM +0200, Blaž Zakrajšek wrote: > >I am not sure if this is the correct address to report, but I would >just like to report that (at least some) new unofficial Debian 11.4 >torrent files are not registered with the bittorent tracker[1][2], >however the official ones are[3]. Hmmm, looks like the tracker didn't pick up on those on when I released them. Oh, hmmm. I've just fixed a typo and re-prodded the seeders now. Looks like that's fixed it. Thanks for reporting! -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Bug#1013432: debian-cd: UEFI boot uses black text on dark blue background
Hi Roland! On Thu, Jun 23, 2022 at 04:11:07PM +0200, Roland Clobus wrote: >Package: debian-cd >Version: 3.1.35 >Severity: normal > >Hello, > >since grub version 2.06-3 entered sid, the UEFI menu of the daily netinst image >shows a black text on the dark blue background for the selected boot item. > >https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/amd64/iso- >cd/ >debian-testing-amd64-netinst.iso > >This can be seen e.g. at >https://openqa.debian.net/tests/61507#step/bootwalk_0/2 > >It appears that the grub theme is active now (which was not the case for e.g. >the netinst-11 images). > >As a local hack, I've replaced: >selected_item_color = "black" >with >selected_item_color = "white" > >in boot/grub/theme/1 inside my netinst image. Aha! Thanks for reporting this, I'll take a look. -- Steve McIntyre, Cambridge, UK.st...@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Re: 11.4 planning
Hey Adam!
On Fri, Jun 17, 2022 at 08:31:23PM +0100, Adam Barratt wrote:
>
>We're (again) running behind in getting the next point release for
>bullseye sorted, and I know we're about to run into the Deb{Camp,Conf}
>period. I think the possible dates that make sense are:
>
>- July 2nd (means freezing next weekend, but so be it)
>- July 9th
>
>I think there's already a couple of things pending on KiBi's review
>list; I'll try and flag up any others as soon as I can.
Argh. I've got a few pertinent issues here:
* I'm *really* busy over the next few weeks (work and debconf) which
make things awkward for me to fit stuff in. :-/
* IIRC this should also be another buster point release, possibly the
last before it's dropped / passed over to LTS? Or are we thinking
another one in August for Buster? Checking last year's dates, we
released on Aug 14 so I'm thinking maybe we could/should push back
that last point release into August. In that case, I'd be happier
to do a bullseye-only point release in July. Neither of the dates
you suggest are ideal for me (see above!), but under time pressure
it's easier to cope with a single release rather than two.
* We have some secure-boot related updates that have not yet filtered
through for buster and bullseye. We're working on stuff for bullseye
now, but buster may take a little bit longer yet. I'd prefer the
9th if possible.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"The whole problem with the world is that fools and fanatics are
always so certain of themselves, and wiser people so full of doubts."
-- Bertrand Russell
Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?
Hey Thomas! On Wed, Jun 15, 2022 at 01:17:31PM +0200, Thomas Schmitt wrote: >Hi, > >although it was not the final solution of this bug report, i beefed up >my merger script for Debian ISOs so that it can combine an arbitrary >number of ISOs (within the limits of /dev/loop* and mount(8)). >Maybe it can serve as answer for the next time this wish comes up. > >The script is uploaded as > > > https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos > >with GPG detached signature > > https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos.sig >for checking by gpg --verify. Cool. :-) That might be a useful thing to include in a package. What do you think? -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?
Hey Thomas! On Sun, May 22, 2022 at 12:03:23PM +0200, Thomas Schmitt wrote: >Steve McIntyre wrote: >> youre initial guess is correct. We don't generate the .iso files >> at all for the larger images [1]. This means we also don't have >> torrent files for them [2]. > >I began to ponder about a shortcut in libisofs which would trust the >checksum file (-checksum-list , -md5-list) enough to omit the reading of >all the package files' content. >Size, ownership, permissions, et.al would still be taken from the package >files on disk. No ISO image would emerge (because of no valid file content) >but .jigdo and .template would be created. >Probably libjte would need an API extension so that it knows that only >the count parameter of a libjte_show_data_chunk() call is valid. >Vice versa libisofs would have to ask libjte whether a particular file >is covered by the checksum list. > >All tricky and probably not worth the risk of embarassing failure. Cute idea (grin!), but it's a non-started - we wouldn't be able to generate the various checksums for the whole image. >So back to my idea of merging ISOs: > >> The debian-cd code in tools/make_disc_trees.pl is not documentation >> **as such**, but it's exactly how we create disc trees: > >I am using it now for checking detail questions. > > >> It's baiscally just making a self-contained apt repository on each medium. > >So > https://wiki.debian.org/DebianRepository/Format >looks like the specs to follow. > >Question (to everybody): > >The description of Packages[.gz] files talks of "paragraphs" but does not >exactly define a paragraph's end delimiter. From Packages.gz in the ISO >i'd guess it is an empty line or the "Package" field of the next paragraph. > >Is an empty line needed between paragraphs ? Yup, it's an empty line. >Would more than one empty line between paragraphs damage the readability ? Not sure, to be honest. >Reason: I want to merge the Packages.gz files like > > (gunzip | gzip >temp_file > >but am not sure that the found Packages.gz will always end by an empty >line. So i could simply insert an echo between the gunzips, or simply >trust that the empty line is not needed as separator, or begin to think ... Might just work, yeah! -- Steve McIntyre, Cambridge, UK.st...@einval.com < liw> everything I know about UK hotels I learned from "Fawlty Towers"
Bug#1011261: The digest algorithm in SHA512SUMS.sign is SHA256
Control: severity -1 minor On Thu, May 19, 2022 at 12:31:28PM +0800, Zhang Boyang wrote: >Package: debian-cd > >Hello, > >I downloaded debian iso and its SHA512SUMS file. However, when I use gpg to >verify authenticity of SHA512SUMS, I found the signature file use SHA256 as >its digest algorithm. Although SHA256 is pretty safe, it's seem strange that >sign a SHA512SUMS with SHA256. I think it's better to sign SHA512SUMS with >SHA512. Maybe. It's not really a priority to change anything here right now, I'll be honest... -- Steve McIntyre, Cambridge, UK.st...@einval.com There's no sensation to compare with this Suspended animation, A state of bliss
Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?
Hey folks, On Sat, May 21, 2022 at 04:59:27PM +0200, Thomas Schmitt wrote: >Andrew M.A. Cater wrote to debian-cd@lists.debian.org: > >> I don't actually know how long it take to create the .jigdo and .template >> files - I don't think it's as long as generating the full .iso files Whether you make the .iso or not, we have to run the full process. The *only* part of the process we can win on (a little) is by not actually writing the .iso file to disk. If we don't want the .iso, we output to /dev/null and save a little bit of output I/O [1]. All the same I/O us used for input, of course - we have to scan all the data to generate checksums, etc. >They are created by libjte under control of libisofs under control of >xorriso as side effect of actual ISO production under control of debian-cd. >(I'm developer of libisofs and xorriso, and co-funder of libjte, which is >now back in the hands of Steve McIntyre from whose genisoimage code it >got large parts of its entrails.) > >I was possibly wrong with guessing that the ISO is dumped into /dev/null, >although debian-cd seems to be smart enough to read the various checksums >from the .jigdo files, rather than calculating them from the .iso files. >The checksum code > https://sources.debian.org/src/debian-cd/3.1.35/tools/imagesums/#L57 >reminded me that there are .torrent files made, which obviously need >the .iso files at least at build time. No, youre initial guess is correct. We don't generate the .iso files at all for the larger images [1]. This means we also don't have torrent files for them [2]. There's no point generating the .torrent if we don't have the full .iso available as well, after all. [1] https://salsa.debian.org/images-team/debian-cd/-/blob/master/tools/make_image#L124 [2] https://cdimage.debian.org/cdimage/release/11.3.0/amd64/ >- > >> it's always good to have otehr people to think round a problem with. > >Is there documentation from which i could learn how the stuff in (i guess) >/dists of DLBD-1 and DLBD-2 could be merged so that it properly describes >a merged pool tree ? > >My rough idea would be: >- mount both ISOs >- derive merged /dists files >- run xorriso to let it > - load DLBD-1 with its boot equipment > - merge-in the pool tree of mounted DLBD-2 > - overwrite the old /dists files by the newly derived ones > - automatically replay the commands for the loaded boot equipment > - store the result as new .iso file > >The second step is where i would need info or advise. The debian-cd code in tools/make_disc_trees.pl is not documentation **as such**, but it's exactly how we create disc trees: all the packages/sources and metadata of various flavours. It's baiscally just making a self-contained apt repository on each medium. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Why do people find DNS so difficult? It’s just cache invalidation and naming things.” -– Jeff Waugh (https://twitter.com/jdub)
Re: iso image for PPC G4 700MHz
Hi Stefano, On Thu, May 05, 2022 at 10:38:09AM +0200, RiseUp wrote: >Hello, > >I'm trying an installation on an old iMac PowerPC G4 700MHz. > >If you know an iso image doing this witrh a size less ro equal 700MB (to >record it on a CD), I'll be gratefull. You'd be better asking the porters on the powerpc list, we've not maintained official CD releases for old powerpc images for some time. -- Steve McIntyre, Cambridge, UK.st...@einval.com "You can't barbecue lettuce!" -- Ellie Crane
Re: Live CD for Debian Jr.
Hi Stefan! Sorry for not responding sooner... On Wed, Mar 23, 2022 at 01:57:44PM +, Stefan Kropp wrote: >Hello, > >I have started to work on a Live CD for Debian Jr. The live CD is >still in status "experimental". Is it possible to build this CD >on a Debian server and put it in a "experimental" / "unstable" >folder or maybe somewhere here [1]. > >To build the live CD, I used the "live-build" package. The files >are one salsa [2]. > >Would be nice if somebody can help me to get a build for >development / testing. We don't currently have anybody looking after live image releases for unstable/testing, but you might get some help on the debian-live list (in CC). -- Steve McIntyre, Cambridge, UK.st...@einval.com We don't need no education. We don't need no thought control.
Re: Wrong directory name for 10.12 images with firmware
On Sun, Mar 27, 2022 at 12:32:13PM +0200, Raphaël Halimi wrote: >Hi, > >In >"http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/;, >the directory holding non-free live CD images for Debian 10.12 is named >"10.12-live+nonfree" instead of "10.12.0-live+nonfree" (missing ".0" present >in all other names). > >It messed up one of my daily scripts which downloads ISO images to feed a PXE >server :) Apologies, that was my mistake after a long day yesterday. Now fixed. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
Re: weekly cdimage text still refers to bullseye
Hi Thomas, On Thu, Mar 17, 2022 at 08:35:33AM +0100, Thomas Lamprecht wrote: > >I just wanted to report that while the cdimage overview[0] already refers >to testing as "what will be Bookworm", the linked weekly builds page[1] >still reads "what will be eventually released as "Bullseye", Debian 11." A >minor, but potentially confusing detail, as I guess with Bullseye already >released since mid of 2021, the latter should now refer to Bookworm? >Especially as the ISO gets one a installation referring to Bookworm in the >/etc/os-release and debian_version info. Oops, looks like another place I missed when switching things around last year. Now fixed. Thanks for telling us! -- Steve McIntyre, Cambridge, UK.st...@einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen
Re: 11.3 and 10.12 planning
On Sun, Mar 06, 2022 at 09:51:57PM +, Adam Barratt wrote: >Hi, > >As you may have noticed, we're a bit overdue now for both 11.3 and the >penultimate buster point release, 10.12. > >Some potential dates: > >- March 19th (means freezing next weekend, so not ideal) >- March 26th >- April 2nd >- April 9th The 19th is awkward for me (and Andy S!) - prior commitments. The others look OK for me. -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
Bug#1003014: make_disc_trees.pl misdetects files missing for debootstrap when a proxy is used to retrieve packages - essentially making the installer ignore packages on the CDROM
Hi Daniel, and Happy New Year! On Sun, Jan 02, 2022 at 08:30:45PM +0100, Daniel Leidert wrote: >Package: debian-cd >Version: 3.1.35 >Severity: normal > >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >I was recently building custom images using simple-cdd, and for some reason the >installer was completely ignoring the packages shipped with the media. With >some digging I found the installer reporting: > >cdrom-detect: Base system not installable from CD, requesting choose-mirror > >With some more digging I found that make_disc_trees.pl was reporting: > >5 files missing for debootstrap, not creating base_installable > >But the relevant make_disc_tree.log file only contained this at the end: > >Missing debootstrap-required I: >Missing debootstrap-required Using >Missing debootstrap-required auto-detected >Missing debootstrap-required proxy: >Missing debootstrap-required http://127.0.0.1:8000/ > >So actually there were no packages missing. Disabling the proxy then "fixed" >the issue. There were no more complaints by make_disc_trees.pl, and the >installer was using all the package put on the CD. > >So we somehow need to ignore messages like the above, which do not indicate >packages missing. Argh, OK. That's clearly the apt wrapper getting confused by the extra output from apt. I'm guessing you have extra environment config to set up the proxy here? -- Steve McIntyre, Cambridge, UK.st...@einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen
Re: non-free firmware unofficial BD jigdo files missing
[ Re-adding the cc to debian-cd. Please always send to the list, not just me. ] On Tue, Dec 21, 2021 at 04:43:56AM +0100, sp...@caiway.net wrote: >On Tue, 21 Dec 2021 00:44:05 +0000 >Steve McIntyre wrote: >> >> Ummm. What files are you expecting? I can see >> firmware-edu-11.2.0-amd64-BD-1* in place, similarly to the >> firmware-edu-11.1.0-amd64-BD-1.* that we did for 11.1 (etc.) > >Hi!, > >firmware-11.2.0-amd64-DVD-1.jigdo >firmware-11.2.0-amd64-DVD-1.template > >do excist > >firmware-edu-11.2.0-amd64-BD-1.jigdo also, but I do not want the >edu-debian. > >I do hopefully expect: > >firmware-11.2.0-amd64-BD-1.jigdo >firmware-11.2.0-amd64-BD-1.template >firmware-11.2.0-amd64-BD-2.jigdo >firmware-11.2.0-amd64-BD-2.template >firmware-11.2.0-amd64-BD-3.jigdo >firmware-11.2.0-amd64-BD-3.template >firmware-11.2.0-amd64-BD-4.jigdo >firmware-11.2.0-amd64-BD-4.template > >The free ones (without firmware) do excist. > >PS. >firmware-11.2.0-amd64-DLBD-1.jigdo >firmware-11.2.0-amd64-DLBD-1.template >firmware-11.2.0-amd64-DLBD-2.jigdo >firmware-11.2.0-amd64-DLBD-2.template >(double blu ray) >would also be more than welcome. I'm afraid you're out of luck. We don't provide firmware-included versions of every media type, just netinst and DVD. >PS2. >Don't be afraid for traffic on debian servers. I use a local mirror. >It is to be used in areas without internet access. > >PS3. >Perhaps you can give me the link with info how to make my own files > >*.jigdo & *.template > >for debian install media with included media. For that, you'll need a full local mirror and use debian-cd. The best place to look for guidance would be our build scripts, if you can follow them: https://salsa.debian.org/images-team/setup -- Steve McIntyre, Cambridge, UK.st...@einval.com "War does not determine who is right - only who is left." -- Bertrand Russell
Re: non-free firmware unofficial BD jigdo files missing
Hi! On Tue, Dec 21, 2021 at 12:52:31AM +0100, sp...@caiway.net wrote: > >The non-free firmware unofficial BD jigdo files for release 11.2 are >still missing. I only checked for the amd64 systems. > >Will they be published? Ummm. What files are you expecting? I can see firmware-edu-11.2.0-amd64-BD-1* in place, similarly to the firmware-edu-11.1.0-amd64-BD-1.* that we did for 11.1 (etc.) -- Steve McIntyre, Cambridge, UK.st...@einval.com "The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." -- Bertrand Russell
Re: 11.2 planning
Hey Adam! On Tue, Nov 23, 2021 at 08:12:11PM +, Adam Barratt wrote: > >It's (a little past) time that we organised the next point release. As >an "every other" release, this time will only be for stable. > >Any of the first three weekends of December would work for me, although >the 4th is my least preferred as it means freezing over the coming >weekend and I'm not sure if I'll have time to do a fair job of dealing >with things before that. > >tl;dr, suggested dates: > >December 4th [least preferable for me] >December 11th >December 18th 4th December is a no-go for me, but the 11th and 18th look OK. -- Steve McIntyre, Cambridge, UK.st...@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
Re: debian testing bd-s not getting updates
On Wed, Oct 06, 2021 at 04:10:21PM +, M G wrote: >What about the "weekly-live-builds"? We don't have any live builds configured at the moment for testing. I'm hoping somebody is going to work on that soon. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Rarely is anyone thanked for the work they did to prevent the disaster that didn’t happen.” -- Mikko Hypponen (https://twitter.com/mikko/)
Re: debian testing bd-s not getting updates
Hi Mike,
On Mon, Oct 04, 2021 at 07:26:17PM +, M G wrote:
>Hi,
>Looking at the latest debian-testing-source-BD-{1,2,3,4}.iso, it seems that no
>files were added since the release of "bullseye". This must be an error,
>right?
>
>Based on a script, checking mod times, there was only 1 file, named
>"bug-reporting.txt".
>Output:
>between this date:
> 162810.0: Wed Aug 4 14:00:00 2021
>and this date:
> 163330.0: Sun Oct 3 18:26:40 2021
>1/doc/bug-reporting.txt
> 1629683651.0: Sun Aug 22 21:54:11 2021
>
>In "/debian/pool" on the mirrors, for example, there's a "gcc-11". But it
>doesnt show up on the source BD-s.
Argh, sorry - there was a config breakage that meant we were still
building targeting bullseye. Now fixed, and I've just triggered a new
full build. There should be new images in a few hours.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"The whole problem with the world is that fools and fanatics are
always so certain of themselves, and wiser people so full of doubts."
-- Bertrand Russell
Re: full CD installer, non netinst
Hi Joseph! On Thu, Sep 30, 2021 at 08:39:14AM +, Joseph wrote: > >I'm looking for the smallest full installer possible with just xfce (CD >installer for example < 700MB), that works without internet, non netinst. >I know this existed for 10.4, I still have: > > "debian-10.4.0-amd64-xfce-CD-1.iso" which is 640 MB > >I'm looking for the same thing for 11.0, but when searching on: > >https://get.debian.org/images/ >https://get.debian.org/images/release/current/amd64/iso-cd/ > >there are only "netinst" vesions, such as debian-11.0.0-amd64-netinst.iso. > >Question: does > > "debian-11.0.0-amd64-xfce-CD-1.iso" < 700 MB > >exist? I'm afraid not, no. We found that it's been getting harder and harder to make a sensible desktop fit onto small media, even with something simpler like xfce. So I took the decision to stop producing the xfce CD image during the 11.x (Bullseye) development cycle. -- Steve McIntyre, Cambridge, UK.st...@einval.com You lock the door And throw away the key There's someone in my head but it's not me
Re: Could not finish download on Windows of DVD6 and BD2 images by means of jigdo because of too long path name for one of the packages
Hi Ivan, On Thu, Sep 23, 2021 at 07:08:14PM +0300, Ivan Petroff wrote: >When downloading debian-11.0.0-amd64-DVD-6.iso and debian-11.0.0-amd64-BD-2.iso >images I got next error (and yes, I tried different mirrors): > >Could not open `.\tmp/debian-11.0.0-amd64-DVD-6.iso.tmpdir\snapshot.debian.org\ >archive\debian\20210815T100244Z\pool\main\e\ettercap\ >ettercap-common_0.8.3.1-3_amd64.deb' for input - excluded (Permission denied) > >As I understand the path for this package is too long for windows to handle. In my experience, the limiting factor is often total length of the path here. How long is the path to the current working directory when you're seeing this problem? -- Steve McIntyre, Cambridge, UK.st...@einval.com < liw> everything I know about UK hotels I learned from "Fawlty Towers"
Bug#994121: debian-cd: Default CODENAME should be changed to bookworm (testing)
Hi Daniel! On Sun, Sep 12, 2021 at 04:40:00AM -0500, Daniel Lewart wrote: >Source: debian-cd >Version: 3.1.35 >Severity: normal >Tags: patch >X-Debbugs-Cc: szilard.an...@gmail.com > >Debian CD Group, > >The default CODENAME should be changed to bookworm (testing). > >Below is a patch, which I successfully tested with: >$ ./easy-build.sh NETINST > >Thank you! >Daniel Lewart >Urbana, Illinois Thanks for the patches. (Mostly) applied, but please don't make unrelated changes when you send patches. In this case, I've *not* changed the CONTRIB setting. >--- >diff -ru a/CONF.sh b/CONF.sh >--- a/CONF.sh 2021-09-06 05:22:44.0 -0500 >+++ b/CONF.sh 2021-09-12 00:00:00.0 -0500 >@@ -70,7 +70,7 @@ > export DI_CODENAME=$CODENAME > fi > # If you want backported d-i (e.g. by setting >-# DI_CODENAME=jessie-backports, then you'll almost definitely also >+# DI_CODENAME=bookworm-backports, then you'll almost definitely also > # want to enable BACKPORTS below as well > > # Should we include some packages from backports? If so, point at a >@@ -86,8 +86,8 @@ > # the Debian mirror. > #export DI_WWW_HOME=default > >-# Version number, "2.2 r0", "2.2 r1" etc. >-export DEBVERSION="11.0.0" >+# Version number, "10.11.0", "11.1.0", "testing", etc >+export DEBVERSION="testing" > > # Official or non-official set. > # NOTE: THE "OFFICIAL" DESIGNATION IS ONLY ALLOWED FOR IMAGES AVAILABLE >@@ -136,7 +136,7 @@ > # export NONFREE=1 > > # Do I want to have CONTRIB merged in the CD set >-export CONTRIB=1 >+# export CONTRIB=1 > > # Do I want to have NONFREE on a separate CD (the last CD of the CD set) > # WARNING: Don't use NONFREE and EXTRANONFREE at the same time ! >@@ -208,8 +208,8 @@ > > # Extra keys that you might want apt to trust. List their fingerprints > # here and debian-cd will grab them from the user's keyring as needed >-# (The example here is the buster release key) >-#export ARCHIVE_EXTRA_KEYS="80D15823B7FD1561F9F7BCDDDC30D7C23CBBABEE" >+# (The example here is the bullseye release key) >+#export ARCHIVE_EXTRA_KEYS="1F89983E0081FDE018F3CC9673A4F27B8DD47936" > > # By default we use debootstrap --no-check-gpg to find out the minimal set > # of packages because there's no reason to not trust the local mirror. But >diff -ru a/easy-build.sh b/easy-build.sh >--- a/easy-build.sh2021-09-06 05:22:44.0 -0500 >+++ b/easy-build.sh2021-09-12 00:00:00.0 -0500 >@@ -72,10 +72,10 @@ > ## For what release to build images > > # The suite the installed system will be based on >-export CODENAME=buster >+export CODENAME=bookworm > # The suite from which the udebs for the installer will be taken (normally > # the same as CODENAME) >-export DI_CODENAME=buster >+export DI_CODENAME=bookworm > > > ## The debian-installer images to use. This must match the suite (DI_CODENAME) >### > > On Sun, Sep 12, 2021 at 04:51:05AM -0500, Daniel Lewart wrote: >Makefile patch is attached. Dan >--- a/Makefile 2021-09-06 05:22:44.0 -0500 >+++ b/Makefile 2021-09-12 00:00:00.0 -0500 >@@ -191,14 +191,14 @@ > fi > endif > >-# Make sure unstable/sid points to testing/buster, as there is no build >+# Make sure unstable/sid points to testing/bookworm, as there is no build > # rule for unstable/sid. > unstable-map: > $(Q)if [ ! -d $(BASEDIR)/data/sid ] ; then \ >- ln -s buster $(BASEDIR)/data/sid ; \ >+ ln -s bookworm $(BASEDIR)/data/sid ; \ > fi > $(Q)if [ ! -d $(BASEDIR)/tools/boot/sid ] ; then \ >- ln -s buster $(BASEDIR)/tools/boot/sid ; \ >+ ln -s bookworm $(BASEDIR)/tools/boot/sid ; \ > fi > > # -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
Re: 11.1 and 10.11 planning]
Forwarding to the lists Andy forgot... - Forwarded message from Andy Simpkins - From: Andy Simpkins To: debian-cd@lists.debian.org Date: Wed, 15 Sep 2021 20:53:41 +0100 Subject: Re: 11.1 and 10.11 planning Message-ID: <717ba215-4bcc-08ab-b087-8f781f15c...@koipond.org.uk> On 14/09/2021 20:14, Steve McIntyre wrote: > On Tue, Sep 14, 2021 at 07:04:11PM +0100, Adam Barratt wrote: > > Hi, > > > > Thanks for the responses everyone. Mark indicated on IRC that he'd be > > happy to be ftpmaster-du-jour on any of the dates. > > > > On Mon, 2021-09-06 at 12:51 +0100, Adam D. Barratt wrote: > > > We've ended up being late with planning 10.11 due to the timing of > > > the bullseye release, and also need to look at getting 11.1 sorted. > > [...] > > > September 18th - not great; means freezing this coming weekend > > > September 25th - not great; I'm away during most of the week > > > beforehand, so will be unlikely to be able to deal with any issues, > > > make sure everything's ready, etc. > > > October 2nd - OK for me > > > > The conclusion seems to be that if we want to have all of the Images > > Team available then we're looking at: > > > > > October 9th - OK for me > > > October 16th - OK for me > > > > Images Team, what was the conclusion in terms of timing for the two > > point releases? Are you happy for the archive side for both to happen > > on the same day, with image testing for buster possibly being delayed, > > or would you prefer to try and separate the whole process? (In which > > case we would need all teams available for multiple dates.) > > I'm happy either way, I think Andy was less sure in the case that we > got him to do both? :-) > given that Steve will be around I am happy for both in one day :-) /Andy - End forwarded message - -- Steve McIntyre, Cambridge, UK.st...@einval.com < Aardvark> I dislike C++ to start with. C++11 just seems to be handing rope-creating factories for users to hang multiple instances of themselves.
Re: 11.1 and 10.11 planning
On Tue, Sep 14, 2021 at 07:04:11PM +0100, Adam Barratt wrote: >Hi, > >Thanks for the responses everyone. Mark indicated on IRC that he'd be >happy to be ftpmaster-du-jour on any of the dates. > >On Mon, 2021-09-06 at 12:51 +0100, Adam D. Barratt wrote: >> We've ended up being late with planning 10.11 due to the timing of >> the bullseye release, and also need to look at getting 11.1 sorted. >[...] >> September 18th - not great; means freezing this coming weekend >> September 25th - not great; I'm away during most of the week >> beforehand, so will be unlikely to be able to deal with any issues, >> make sure everything's ready, etc. >> October 2nd - OK for me > >The conclusion seems to be that if we want to have all of the Images >Team available then we're looking at: > >> October 9th - OK for me >> October 16th - OK for me > >Images Team, what was the conclusion in terms of timing for the two >point releases? Are you happy for the archive side for both to happen >on the same day, with image testing for buster possibly being delayed, >or would you prefer to try and separate the whole process? (In which >case we would need all teams available for multiple dates.) I'm happy either way, I think Andy was less sure in the case that we got him to do both? :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com "Further comment on how I feel about IBM will appear once I've worked out whether they're being malicious or incompetent. Capital letters are forecast." Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html
Re: 11.1 and 10.11 planning
On Mon, Sep 06, 2021 at 12:51:07PM +0100, Adam Barratt wrote: >Hi, > >We've ended up being late with planning 10.11 due to the timing of the >bullseye release, and also need to look at getting 11.1 sorted. > >Traditionally, we've combined stable and oldstable point releases (at >2- and 4-month cadences) while both are supported. That would still be >my preference, but I understand that not everyone on the Images side is >so keen on the idea. Open questions in addition to dates are therefore >whether we should do 10.11 and 11.1 on the same day and, if not, how >close together they should be. > >A few suggested dates to get things going: > >September 18th - not great; means freezing this coming weekend >September 25th - not great; I'm away during most of the week >beforehand, so will be unlikely to be able to deal with any issues, >make sure everything's ready, etc. >October 2nd - OK for me >October 9th - OK for me >October 16th - OK for me At this point I'm free for all of those weekends. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Why do people find DNS so difficult? It’s just cache invalidation and naming things.” -– Jeff Waugh (https://twitter.com/jdub)
Re: DVD-2 and DVD-3
On Thu, Aug 19, 2021 at 12:15:00PM +0100, Brian Potkin wrote: >I was hoping to get DVD-2 and DVD-3 from > > https://cdimage.debian.org/debian-cd/current/i386/iso-dvd/ > >but they are not there. > >(I know I can use jigdo). ACK. Very few people seem to be grabbing anything beyond DVD-1 these days, so I slimmed down the set of ISOs we ship. -- Steve McIntyre, Cambridge, UK.st...@einval.com "You can't barbecue lettuce!" -- Ellie Crane
Bug#992449: cdimage.debian.org: sr kernel module is missing on install media for arm64 which prevents installation in KVM guest
Hi Lance, Sorry to hear that you're having problems here :-( On Wed, Aug 18, 2021 at 12:49:05PM -0700, Lance Albertson wrote: >I forgot to mention that the mini.iso image located here [1] does appear to >work as expected FWIW. But the image found here [2] does not. > >[1] https://debian.osuosl.org/debian/dists/bullseye/main/installer-arm64/ >20210731/images/netboot/ >[2] https://debian.osuosl.org/debian-cdimage/11.0.0/arm64/iso-cd/ So, I'm surprised to read this. On release day I tested our arm64 media locally using qemu/KVM VMs on an arm64 host here. I've just booted the netinst media again now (debian-11.0.0-arm64-netinst.iso) and I can see the following modules loaded, clearly including sr_mod: # lsmod Module Size Used by virtio_net 53248 0 net_failover 24576 1 virtio_net failover 20480 1 net_failover nls_utf8 16384 1 isofs 49152 1 sr_mod 32768 1 cdrom 61440 2 isofs,sr_mod virtio_scsi24576 1 scsi_mod 221184 2 virtio_scsi,sr_mod virtio_blk 28672 0 virtio_pci 28672 0 virtio_mmio24576 0 virtio_ring28672 5 virtio_mmio,virtio_scsi,virtio_pci,virtio_blk,virtio_net virtio 20480 5 virtio_mmio,virtio_scsi,virtio_pci,virtio_blk,virtio_net I'm curious why you might be seeing different. Could you share more details of your setup please? -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Re: Spyder package missing from jigdo amd64 weekly 16 GB stick ISO, but its dependencies are there
On Thu, Jul 29, 2021 at 03:01:54PM +0200, epsommum...@virgilio.it wrote: >I am now using the BluRay image which contains Spyder and its dependencies, so >I am fine. > >But obviously there is a problem with the current algo being used if >the dependencies of a software end up in an ISO but not the software >actually depending on them. No, there is *not* obviously a problem there. There would be a problem the *other* way round, as then you'd have the top-level software package but not be able to install it. As I said, we sort packages in dependency order and then go through the list as far as we can before the media is full. >I remember being surprised by the size of the ISO being significantly >less than 16 GB. I believe it was 14.8 GB. I just downloaded it again >to verify and voila : 14,8 Gio (15 909 054 464) Well...also known as >: 15,9 GB Right, so you can see the difference between GiB (powers of 2) and GB (powers of 10). Storage media is normally describe in terms of GB, as that way the numbers look bigger. -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
Re: Spyder package missing from jigdo amd64 weekly 16 GB stick ISO, but its dependencies are there
On Thu, Jul 29, 2021 at 03:40:54AM +0200, epsommum...@virgilio.it wrote: >Hi Steve! > >The 16GB image is actually less than 15GB. Incorrect. Checking the size in the jigdo file: Image size 15909054464 bytes >The Spyder package is 200kb. >There is ample room. >Someone who does not use Spyder put python3-spyder in this ISO thinking it was >the real Spyder software, except that it was just one if its dependencies. >You could either remove the dependencies or add the small Spyder package, but >leaving things as they are makes no sense. Packages are ordered and placed automatically when we build the image sets. Earlier packages are the key ones that we must have (installer, base system, etc.). Beyond that, we don't have much information to go on to work out ordering automatically. So we sort by popularity contest and dependency order, and fill media as much as possible. (In fact, the algorithm actually runs until it has *over* filled the media then backs out the last package added.) In the case of this weekly 16G image build, the last few packages added look like: ... CD 1: GUESS_TOTAL is 7776204 after adding amd64:main:wesnoth-1.14-dm:5415204 CD 1: GUESS_TOTAL is 7778734 after adding amd64:main:wesnoth-1.14-dw:5178524 CD 1: GUESS_TOTAL is 7781926 after adding amd64:main:wesnoth-1.14-sota:6531368 CD 1: GUESS_TOTAL is 7781930 after adding amd64:main:wesnoth-1.14:1488 CD 1: GUESS_TOTAL is 7781937 after adding amd64:main:wesnoth:1224 CD 1: GUESS_TOTAL is 7856754 after adding amd64:main:wesnoth-1.14-music:153218372 Running xorriso -as mkisofs -r -checksum_algorithm_iso sha256,sha512 -jigdo-min-file-size 1024 -jigdo-exclude 'README*' -jigdo-exclude /doc/ -jigdo-exclude /md5sum.txt -jigdo-exclude /.disk/ -jigdo-exclude /pics/ -jigdo-exclude 'Release*' -jigdo-exclude 'Packages*' -jigdo-exclude 'Sources*' -r -print-size -quiet -J -joliet-long -cache-inodes -isohybrid-mbr syslinux/usr/lib/ISOLINUX/isohdpfx.bin -b isolinux/isolinux.bin -c isolinux/boot.cat -boot-load-size 4 -boot-info-table -no-emul-boot -eltorito-alt-boot -e boot/grub/efi.img -no-emul-boot -isohybrid-gpt-basdat -isohybrid-apm-hfsplus -o /dev/null boot1 /srv/cdbuilder.debian.org/src/deb-cd/tmp/Msidamd64/bullseye/CD1 CD 1: Real current size is 7847282 blocks after adding amd64:main:wesnoth-1.14-music:153218372 CD 1 over-full (7847282 > 7812500). Rollback! CD 1: Real current size is 7772466 blocks after rolling back amd64:main:wesnoth-1.14-music:153218372 CD 1 filled with 10904 packages, 7768092 blocks, 15909052416 bytes ... If you care about spyder fitting on the 16G media so much, try getting more popcon votes for it. -- Steve McIntyre, Cambridge, UK.st...@einval.com We don't need no education. We don't need no thought control.
Re: Spyder package missing from jigdo amd64 weekly 16 GB stick ISO, but its dependencies are there
Hi! On Wed, Jul 28, 2021 at 08:26:53PM +0200, epsommum...@virgilio.it wrote: > >The Spyder package is missing from jigdo amd64 weekly 16 GB stick ISO. > >All its dependencies are there like python3-spyder, but since spyder >itself is missing, spyder can not be used. > >https://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-16G/ > >https://packages.debian.org/fr/sid/spyder > >I quote from this page : "This package provides the application for Python 3." The 16GB image isn't big enough to hold every package in Debian, I'm afraid. A full set of all packages for amd64 bullseye is currently around 70GB... -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead
Re: Finding a tentative bullseye release date
On Sat, Jul 17, 2021 at 10:25:17PM +0200, Paul Gevers wrote: >Hi all, > >On 11-07-2021 21:11, Paul Gevers wrote: >> With less than three weeks to go until the tentative release date, I >> would love to confirm the date by now, but there is a serious issue with >> crucial infrastructure (cdbuilder.d.o). Apart from this issue (and what >> it means for solving the debian-installer blocking issues in time), I'm >> not aware of other blocking issues, so let's hope the teams involved can >> recover in time. > >Albeit there is some progress, we think it better for the people >involved to now say that we will *not* release on July 31. > >Unfortunately, that means that we have to start looking for a new date >again. Assuming what we'll learn in the upcoming week or two is good, I >propose to already start the list below with two weeks after the >previous date. Upcoming time is around DebConf, I can imagine it could >even be an advantage, especially as that's on-line, let's see. > >14 August (day before DebCamp) Works for me for images team >21 August (last day of DebCamp) > RT: elbrus Awkward - wife has plans for us that evening. >28 August (DebConf) > RT: elbrus Debian UK BBQ, argh >4 September > RT: elbrus Works fine for me >11 September: > RT: elbrus That's the week of my wedding anniversary, I'll be on VAC. -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Re: Debian Live sudo password
On Mon, Jun 28, 2021 at 08:48:30PM +, Odunola Ibrahim wrote: >Hello, > >I downloaded the debian live 10.10.0-amd64-gnome image file. I needed to make >user authorisation but I couldn't find the root password anywhere on the >website. the username/password is user/live -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud.
