Bug 831984 - libvirt builds against libudev-devel, which is obsolete
Summary: libvirt builds against libudev-devel, which is obsolete
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 831971
TreeView+ depends on / blocked
 
Reported: 2012-06-14 08:45 UTC by Michal Schmidt
Modified: 2012-07-02 18:45 UTC (History)
11 users (show)

Fixed In Version: libvirt-0.9.13-1.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-02 18:45:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michal Schmidt 2012-06-14 08:45:51 UTC
libvirt-0.9.12-1.fc18.src.rpm

libvirt.spec has:
  BuildRequires: libudev-devel >= 145

libudev-devel is going away. Please use systemd-devel. For details see:
http://lists.fedoraproject.org/pipermail/devel/2012-June/168227.html

Comment 1 Daniel Berrangé 2012-06-14 09:45:13 UTC
Already fixed upstream, and will be in rawhide after next release of libvirt

commit dd7bc51bc45051b708c1b47b80d1e8402fcbcc5a
Author: Cole Robinson <crobinso>
Date:   Wed Jun 6 14:03:47 2012 -0400

    spec: Build against systemd for udev
    
    They have now merged. Fedora details here:
    
    https://lists.fedoraproject.org/pipermail/devel/2012-June/168227.html

Comment 2 Michal Schmidt 2012-07-02 08:24:57 UTC
When can we expect the next release to arrive?

It is strange to have fixes for packaging issues blocked on waiting for an upstream release. Why cannot this be fixed in the Fedora spec file right now?

Comment 3 Cole Robinson 2012-07-02 14:29:30 UTC
Because libvirt typically cuts a new release every month which seemed like a reasonable time frame. (and in fact a new release was made today)

Comment 4 Michal Schmidt 2012-07-02 18:45:18 UTC
Great, thanks!


Note You need to log in before you can comment on or make changes to this bug.