Invalid dependency in grub 0.97 (legacy)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grub (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: grub
IMO a packeage is not ready for prime time unless and until the docs are ready to go. Since I don't currently have the time to parse scripts and config files spread all over the file system, I'm sticking with grub 0.97 (legacy). Unfortunately it's packaged in *buntu as having grub-common as a dependency and the only grub-common available is for grub2.
Unfortunately, this also means that grub-docs can't be loaded, as grub-common conflicts with grub-docs.
I can't remove grub-common without having grub marked as broken.
This has been present in *buntu since 9.10
ProblemType: Bug
Architecture: i386
Date: Sun Jan 9 12:23:56 2011
DistroRelease: Ubuntu 9.10
Package: grub 0.97-29ubuntu59
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSign
SourcePackage: grub
Uname: Linux 2.6.31-22-generic i686
| Ron Widell (r-widell) wrote | #1 |
| Colin Watson (cjwatson) wrote | #2 |
We deliberately use grub-common in our GRUB Legacy packaging even though it's from GRUB 2; there's a special hack in there to allow grub-probe to emit drive names suitable for GRUB Legacy.
grub-common has:
Conflicts: grub-doc (<< 0.97-29ubuntu60), grub-legacy-doc (<< 0.97-29ubuntu60), mdadm (<< 2.6.7-2)
grub-doc is currently at version 0.97-29ubuntu60 (since Ubuntu 10.04 LTS), and depends on grub-legacy-doc. It is therefore installable.
The bug you describe was indeed present in Ubuntu 9.10 (bug 493968), but has since been fixed.