In the absence of an explanation for why this bug should be closed when
it is in fact still a bug in 17.10, I'm once again reopening it.
Incidentally, even if it WERE correct to close the bug because it was
fixed, the correct status to use would be "Fix Committed" or "Fix
Released", not "Invalid".
I'm sorry, but I still don't understand what you're saying or what
you're doing.
It's reported fixed in earlier releases OF LVM2, not of Ubuntu. It has
not been fixed in Ubuntu, because Ubuntu hasn't upgraded the LVM2 it
ships to the newer release.
Furthermore, the project you keep marking invali
As you says, it's declared 'fixed' some releases ago (see Artful
changelog); and zesty is now unsupported. So closing that report.
** Changed in: lvm2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I mean, did you even check if the bug still existed in 17.10 before
marking it invalid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705534
Title:
"lvs" exits with status 0 after failing
To manag
Upgrading lvm2 in Ubuntu to the current upstream release will address
this issue, according to a comment on the upstream bug I reported (link
above).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17055
Bug still exists in 17.10, not clear to me why you marked it invalid.
** Changed in: lvm2 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705534
Title:
"lvs"
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: lvm2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Reported upstream as https://bugzilla.redhat.com/show_bug.cgi?id=1473392
.
** Bug watch added: Red Hat Bugzilla #1473392
https://bugzilla.redhat.com/show_bug.cgi?id=1473392
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
