Make -displaylink conform to debian-x packaging standards

Bug #552997 reported by Bryce Harrington
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xf86-video-displaylink (Ubuntu)
Fix Released
Wishlist
Bryce Harrington
Lucid
Fix Released
Wishlist
Bryce Harrington

Bug Description

Binary package hint: xf86-video-displaylink

Ultimately we want -displaylink in main, but first the -displaylink driver should be renamed to confirm to the debian X team's standard naming convention (xserver-xorg-*) and to use xsfbs for packaging.

This is needed for the following blueprint:
  https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-xorg-enable-century-usb-screen

I'd hoped to get this in by beta2 freeze, but it was a target of opportunity and thus low on my priority list, and it >just< missed the freeze cutoff. :-)

Bryce Harrington (bryce)
Changed in xf86-video-displaylink (Ubuntu Lucid):
milestone: none → ubuntu-10.04-beta-2
assignee: nobody → Bryce Harrington (bryceharrington)
importance: Undecided → Wishlist
status: New → In Progress
status: In Progress → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote :

Didn't make it for beta2, pushing milestone.

Bryce, the source package uploaded to the NEW queue seems to have two complete copies of the upstream source: one from the upstream tarball in the xf86-video-displaylink subdirectory, and one in the src subdirectory that's only in the diff.gz. Could you please clean up the package to use the upstream sources?

Changed in xf86-video-displaylink (Ubuntu Lucid):
milestone: ubuntu-10.04-beta-2 → ubuntu-10.04
Revision history for this message
Emmet Hikory (persia) wrote :

I've reuploaded a cleaner version that doesn't have all the duplicated source, yet still uses xsfbs.

Revision history for this message
Steve Langasek (vorlon) wrote :

has been accepted into the archive; bug didn't autoclose because of the changed package name.

Changed in xf86-video-displaylink (Ubuntu Lucid):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.