Angel Ramírez Isea you did assigning yourself to this bug which means
you are working on it, is this correct?
** Changed in: grub (Ubuntu)
Sourcepackagename: None = grub
** Changed in: grub (Ubuntu)
Status: New = Incomplete
--
[Hardy] Fixing update-grub in Hardy Beta
Yup. I would even consider it fixed. I just thought it would be good
to have it reported there in order to make it easier to find for
people with a similar problem.
2008/3/30, Pascal De Vuyst [EMAIL PROTECTED]:
Angel Ramírez Isea you did assigning yourself to this bug which means
you are
I would even consider it fixed.
You mean you have worked around the problem, that doesn't mean the problem is
fixed in Ubuntu.
I think you don't understand, if you expect this to be fixed in Ubuntu you
should not assign yourself as working on this bug. SOo please unassign yourself
from this
Ok. I'll do that. Now, how do I include the fix in Ubuntu?
2008/3/30, Pascal De Vuyst [EMAIL PROTECTED]:
I would even consider it fixed.
You mean you have worked around the problem, that doesn't mean the problem is
fixed in Ubuntu.
I think you don't understand, if you expect this to be
** Changed in: grub (Ubuntu)
Assignee: Angel Ramírez Isea (angel-ramirez-isea) = (unassigned)
--
[Hardy] Fixing update-grub in Hardy Beta
https://bugs.launchpad.net/bugs/208638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: grub (Ubuntu)
Status: Incomplete = New
--
[Hardy] Fixing update-grub in Hardy Beta
https://bugs.launchpad.net/bugs/208638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm sorry, but the errors you're describing did not come from an Ubuntu-
provided /sbin/update-grub script. The bashisms in update-grub were
fixed in an upload in 2006 - neither the gutsy nor feisty versions of
update-grub contain either of the errors you've cited. Marking this bug
as invalid,
That's weird. It's such a simple error that it's easy to understand
that it was fixed a long time ago. I got my Beta Hardy upgrade via the
Venezuelan server. Maybe that repository got the file wrong. I'll
check with the guys in Venezuela.
Thank you all for your time.
2008/3/30, Steve Langasek
On Sat, Mar 29, 2008 at 09:53:33PM -, Angel Ramírez Isea wrote:
That's weird. It's such a simple error that it's easy to understand
that it was fixed a long time ago. I got my Beta Hardy upgrade via the
Venezuelan server. Maybe that repository got the file wrong. I'll
check with the guys
Oops! Now I get it.
The output to all 3:
apt-cache policy grub
dpkg -l grub
debsums -s grub
tells me that grub is not installed. And it's true. I'm using grub-
gfxboot.
[EMAIL PROTECTED]:~$ apt-cache policy grub-gfxboot
grub-gfxboot:
Instalados: 0.97-11
Candidato: 0.97-11
Tabla
On Sun, Mar 30, 2008 at 03:49:24AM -, Angel Ramírez Isea wrote:
I guess that pretty much explains it all. This bug report shouldn't go
under grub, right? I'm a little embarrased for not sharing that
information on the first post. I thought that the upgrade would
reinstall grub. Well, live
11 matches
Mail list logo
