[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#538536: xserver-xorg-video-neomagic: FTBFS with new source format 3.0 (quilt): broken patches



hertzog@debian.org wrote:
> Package: xserver-xorg-video-neomagic
> Version: 1:1.2.2-2
> Severity: wishlist
> Usertags: 3.0-quilt-by-default
>
> To prepare a possible switch to the new source package format "3.0
> (quilt)" [1], I converted all source packages and rebuilt the packages
> afterwards to see what breaks, and xserver-xorg-video-neomagic does break. To reproduce the
> problem you can do this:
> $ apt-get source xserver-xorg-video-neomagic
> $ mkdir -p xserver-xorg-video-neomagic-1.2.2/debian/source
> $ echo "3.0 (quilt)" >xserver-xorg-video-neomagic-1.2.2/debian/source/format
> $ dpkg-source -b xserver-xorg-video-neomagic-1.2.2
> $ dpkg-source -x xserver-xorg-video-neomagic_1.2.2-2.dsc
> $ cd xserver-xorg-video-neomagic-1.2.2 && debuild -us -uc
>
> In this process, if the .diff.gz contains changes to upstream files,
> dpkg-source will have created a corresponding patch in
> debian/patches/debian-changes-1:1.2.2-2 and will have registered that
> patch in a quilt series (debian/patches/series, it is created if needed).
> All the patches listed in the "series" file are applied directly during
> the extraction (dpkg-source -x). quilt itself is used if available (and
> will thus lead to the creation of the .pc directory), otherwise
> dpkg-source applies the patches by itself. For more information about the
> new source package format see the manual page dpkg-source(1).
>
> In the case of xserver-xorg-video-neomagic, one of the patches is broken. It has probably
> been hand edited without updating the numbers at the start of the hunk.
> Please refresh all patches (quilt refresh) to make sure that they are
> correct (and verify that the above procedure now works).
>   

Most X drivers don't have any patch anymore since we let the upstream
server do the driver autodetection now. neomagic has not been uploaded
since the patch was removed in git since no new release occured. But
there shouldn't be any problem anymore.

Brice




Reply to: