Hi, Cyril Brulebois <[email protected]> wrote (Sun, 19 Oct 2025 21:30:57 +0200): > Holger Wansing <[email protected]> (2025-10-19): > > I managed to successfully do these changins in 31 d-i packages, I fail > > for the last 3 ones: > > hw-detect > > s390-dasd > > s390-zfcp > > > > > > While the s390 packages are not on the top of my to-worry-about list > > (are they used at all ???), I would like to have hw-detect migrated, but > > I fail. It seems to follow a different concept, which I don't understand. > > Do you have a branch somewhere? Or some error messages?
Yes, you got me. My ask-for-help was not very constructive. Not much information, no error messages. I made several attempts, and at the end I was just missing motivation, but pushed that help message nevertheless. Sorry for this. So I will add a summary here: First attempt was to simply change all hardcoded paths I could find in ./debian from bin|lib to usr/bin|usr/lib. This approach has worked fine for 98% of the d-i packages I touched before in this migration. It is at https://salsa.debian.org/holgerw/hw-detect-usrmerge-ready However, this doesn't look promissing, to be honest, since not all included binary packages are involved here (only ethdetect and and hw-detect get changings in this attempt). And the result is, that /usr/bin does not contain any files in the generated udebs, only empty directory. So I made a more global attempt, adding *.install files for all binary packages, to have the possibility, to control install paths for all files for all binary packages. This is at https://salsa.debian.org/holgerw/hw-detect-usrmerge-2 But this build fails with -----------snip--------------------- dh_install: warning: Cannot find (any matches for) "check-missing-firmware" (tried in ., debian/tmp) dh_install: warning: hw-detect missing files: check-missing-firmware dh_install: warning: Cannot find (any matches for) "hotplug-pcmcia" (tried in ., debian/tmp) dh_install: warning: hw-detect missing files: hotplug-pcmcia dh_install: warning: Cannot find (any matches for) "hw-detect" (tried in ., debian/tmp) dh_install: warning: hw-detect missing files: hw-detect dh_install: warning: Cannot find (any matches for) "sysfs-update-devnames" (tried in ., debian/tmp) dh_install: warning: hw-detect missing files: sysfs-update-devnames dh_install: warning: Cannot find (any matches for) "udev" (tried in ., debian/tmp) dh_install: warning: hw-detect missing files: udev dh_install: warning: Cannot find (any matches for) "ethdetect" (tried in ., debian/tmp) dh_install: warning: ethdetect missing files: ethdetect dh_install: warning: Cannot find (any matches for) "disk-detect" (tried in ., debian/tmp) dh_install: warning: disk-detect missing files: disk-detect dh_install: warning: Cannot find (any matches for) "driver-injection-disk" (tried in ., debian/tmp) dh_install: warning: driver-injection-disk-detect missing files: driver-injection-disk dh_install: error: missing files, aborting make: *** [debian/rules:3: binary] Fehler 25 --------------snap---------------- I had some more sub-steps between these two, but they were even less senseful. So I leave them out here. At the end, it seems that hw-detect follows a completely different concept than all the other d-i packages I touched in this migration, and I doubt, if this can be correct (or good) ? Holger -- Holger Wansing <[email protected]> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
