Sergey Bugaev, le mer. 10 mai 2023 13:25:25 +0300, a ecrit: > On Wed, May 10, 2023 at 3:55 AM Samuel Thibault <samuel.thiba...@gnu.org> > wrote: > > With the available .debs you should now be able to enable these. > > I'm afraid I'm going to need more guidance here. Your little tutorial > in readme [0] is helpful (thank you!),
Note that it is just the boilerplate that I have in all my tmp/ repos. > but I still have questions. > > [0]: https://people.debian.org/~sthibault/tmp/hurd-amd64/README.txt > > I can't just install packages by reconfiguring apt and installing them > directly as you suggest, because that assumes a working Debian > installation Yes, that's why I added there that you can just use dpkg-deb to unpack them to your test fs. > Maybe I'm supposed to use the apt flags which tell it to operate on a > chroot? That's quite complex, there are a lot of configuration details to get right. I'd say just unpack by hand for now. > I've tried debootstrap, but that errors out at "Can't verify that > target arch works" -- apparently usr/bin/arch-test does not recognize > hurd-amd64. There is no real hurd-amd64 archive yet anyway. Possibly debootstrap could be pointed to my repo, I haven't tested. > The way to disable that check appears to be --foreign; but > I wasn't (yet) able to get that working either. If you are using > debootstrap and it works for you, I'm not, I haven't had the time to investigate that part yet. > I could try to just extract some packages using your 'dpkg-deb -x' > tip, but I would still like for apt/dpkg to figure out the > dependencies for me, For now you'll just be faced with library dependencies, so I'd say just unpack all lib*.deb (+zlib1g*.deb) and you'll be done. Samuel
