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]
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. 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. 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 Cheers, -- Raphaël Hertzog ◈ Offensive Security ◈ Kali Linux Developer
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]
Hi Steve, 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? Cheers, -- Raphaël Hertzog ◈ Offensive Security ◈ Kali Linux Developer
