On 06/11/2013 07:46 PM, Richard Vickery wrote:
On Tue, Jun 11, 2013 at 10:31 AM, Chuck Forsberg WA7KGX N2469R
wrote:
It seems the name of the Fedora 19 release is getting corrupted in various
places.
It might be breaking some scripts as well.
It might be wise to eliminate the special character
On Tue, 2013-06-11 at 10:31 -0700, Chuck Forsberg WA7KGX N2469R wrote:
> It seems the name of the Fedora 19 release is getting corrupted in
> various places.
> It might be breaking some scripts as well.
>
> It might be wise to eliminate the special characters (including the ' )
> before final re
On Ter, 2013-06-11 at 10:31 -0700, Chuck Forsberg WA7KGX N2469R wrote:
> It seems the name of the Fedora 19 release is getting corrupted in
> various places.
Could you specify where ? to fix it
> It might be breaking some scripts as well.
>
> It might be wise to eliminate the special charac
On Tue, Jun 11, 2013 at 10:31 AM, Chuck Forsberg WA7KGX N2469R
wrote:
> It seems the name of the Fedora 19 release is getting corrupted in various
> places.
> It might be breaking some scripts as well.
>
> It might be wise to eliminate the special characters (including the ' )
> before final relea
It seems the name of the Fedora 19 release is getting corrupted in
various places.
It might be breaking some scripts as well.
It might be wise to eliminate the special characters (including the ' )
before final release.
--
Chuck Forsberg WA7KGX c...@omen.com www.omen.com
Developer of
https://bugzilla.redhat.com/show_bug.cgi?id=961533
This bug is still a problem even after updating grub and reinstalling the
bootloader code, recreating the grub.cfg, and then updating the kernel. The
grub.cfg doesn't appear to be malformed.
Is this bug properly assigned? It's not getting any a
