Is there a reason why there is no new lvm2 package for amd64?
On Mon, Feb 23, 2009 at 11:30 PM, Launchpad Bug Tracker
<email address hidden> wrote:
> This bug was fixed in the package lvm2 - 2.02.39-0ubuntu7
>
> ---------------
> lvm2 (2.02.39-0ubuntu7) jaunty; urgency=low
>
> * debian/patches/open-readonly.patch:
> - Generally we don't need to write to every single block device we open,
> in fact if we do that when scanning we'll make udev think they all
> changed, and it could run "lvm vgscan" again! When the file descriptor
> is needed for writing, it will be closed and opened again. LP: #332270.
>
> -- Scott James Remnant <email address hidden> Mon, 23 Feb 2009 21:44:51
> +0000
>
> ** Changed in: lvm2 (Ubuntu Jaunty)
> Status: Triaged => Fix Released
>
> --
> udev repeatedly generates "change" events for the same block device(s)
> https://bugs.launchpad.net/bugs/332270
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Is there a reason why there is no new lvm2 package for amd64?
On Mon, Feb 23, 2009 at 11:30 PM, Launchpad Bug Tracker patches/ open-readonly. patch: /bugs.launchpad .net/bugs/ 332270
<email address hidden> wrote:
> This bug was fixed in the package lvm2 - 2.02.39-0ubuntu7
>
> ---------------
> lvm2 (2.02.39-0ubuntu7) jaunty; urgency=low
>
> * debian/
> - Generally we don't need to write to every single block device we open,
> in fact if we do that when scanning we'll make udev think they all
> changed, and it could run "lvm vgscan" again! When the file descriptor
> is needed for writing, it will be closed and opened again. LP: #332270.
>
> -- Scott James Remnant <email address hidden> Mon, 23 Feb 2009 21:44:51
> +0000
>
> ** Changed in: lvm2 (Ubuntu Jaunty)
> Status: Triaged => Fix Released
>
> --
> udev repeatedly generates "change" events for the same block device(s)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Francisco