On Tue, Nov 10, 2009 at 05:47:24PM +0100, Thomas Schwinge wrote: > Hello! > > On Sun, Nov 08, 2009 at 11:45:39AM +0100, I wrote: > > I think I'll reinstall them later today (preserving /home/, of course). > > Sergiu rightfully so reminded me that I had forgotten to do that. > blubber is again up running, and grubber will be in some days -- > realistically. ;-) (I did some changes to my install scripts, and want > to test and use these improvements for re-installing grubber.) > <http://www.bddebian.com:8888/~hurd-web/public_hurd_boxen/zenhost/> now > documents the installation process, so that someday another person can do > this, too. > > > > Should be pretty easy now that crosshurd is functional again. > > Michael, FYI: This indeed the case. The only strange thing I noticed is > this: > > I: Extracting /var/cache/apt/archives/coreutils_7.5-6_hurd-i386.deb... > I: Extracting /var/cache/apt/archives/dash_0.5.5.1-3_hurd-i386.deb... > tar: ./bin/sh: Cannot create symlink to `dash': File exists > tar: ./usr/share/man/man1/sh.1.gz: Cannot create symlink to `dash.1.gz': > File exists > tar: Exiting with failure status due to previous errors > I: Extracting /var/cache/apt/archives/debianutils_3.2.1_hurd-i386.deb... > I: Extracting > /var/cache/apt/archives/diffutils_1%3a2.8.1-18_hurd-i386.deb... > > But this didn't have any negative effects (dash finally is running as > /bin/sh), so I ignored it.
Yeah, it's because both the bash and dash .debs ship the /bin/sh symlink now; not much we can do about it right now, as both packages are uptodate with respect to unstable. Michael
