Re: Recent Dockyard-devel safe?
Bernhard Rosenkraenzer <[email protected]> Sun, 16 Oct 2005 23:27:41 +0200
| Newsgroups | gmane.linux.arklinux.general |
|---|---|
| Message-ID | <[email protected]> |
On Sunday, 16. October 2005 23:07, N. Thompson wrote: > I tried installing dockyard-devel recently and wound up having the > installer fail because it couldn't install ark-version-info and some > other package. Yes, that was happening a couple of weeks back due to a bug in the iso build script, caused by the huge number of packages we have these days (the script uses "*" in a couple of places, and the expansion causes weird things like "rpm: argument list too long". This is fixed now and the current dockyard-devel image is supposed to work -- however, keep in mind that dockyard-devel may break at any time (it's just a development snapshot after all) --- if dockyard-devel doesn't work, get a dockyard (or 2005.2-rc3) image and upgrade packages manually. > As an > interesting side effect of the failed installation I couldn't boot > Windows or Linux, my computer would boot up with a message that there > was no operating system installed. Hmm... The MBR definitely isn't being overwritten before you get an error about dependencies -- prior to checking dependencies, the only thing that happens is adjustments to the partition tables. It's possible that the problem was simply caused by a missing active flag - AFAIK Windoze still needs that to be set to its partition. LLaP bero