FWIW, this is fixed upstream (in GPT fdisk 1.0.1), and bug 1514400 now
requests an update to that version.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1285197
Title:
growpart
I'm the upstream author of GPT fdisk. This bug will be fixed in version
1.0.1, which I hope to release later today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/924028
Title:
I've released GPT fdisk 1.0.1. I know it's way too late to get it into
Wily, so either 1.0.1 can be SRU'd or I can provide a patch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/924028
I've released gdisk 1.0.1 this weekend, which addresses this
documentation issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1445456
Title:
Manpage documentation for exit status
What does this have to do with gdisk? It sounds like it's describing a
GRUB issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/941089
Title:
Force /etc/crypttab entry for
The upstream GPT fdisk project provides separate "gdisk" (containing
gdisk, cgdisk, and sgdisk binaries) and "fixparts" (containing the
fixparts binary) packages, since FixParts is intended to manipulate MBR
partition tables and the other binaries work on GPT disks. The Ubuntu
"gdisk" package,
This is a conflict between the Ubuntu-provided gdisk 0.8.8 package and
the upstream-provided fixparts-1.0.1 package. Upstream (that's me)
provides separate gdisk and fixparts packages, whereas Ubuntu provides a
single gdisk package that includes both gdisk and fixparts binaries.
To overcome the
The bug may or may not still exist, but I've been unable to reproduce it
since deleting and re-creating the "maas" user on the affected system,
as noted in comment #3, above.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
