[Debian-med-packaging] mriconvert_2.0.217-1_amd64.changes ACCEPTED into unstable

[Michael Hanke]

Hi Steve,

On Wed, Oct 5, 2011 at 5:47 AM, Debian FTP Masters <
ftpmaster at ftp-master.debian.org> wrote:

> Accepted:
> mriconvert_2.0.217-1.diff.gz
>  to main/m/mriconvert/mriconvert_2.0.217-1.diff.gz
> mriconvert_2.0.217-1.dsc
>  to main/m/mriconvert/mriconvert_2.0.217-1.dsc
> mriconvert_2.0.217-1_amd64.deb
>  to main/m/mriconvert/mriconvert_2.0.217-1_amd64.deb
> mriconvert_2.0.217.orig.tar.gz
>  to main/m/mriconvert/mriconvert_2.0.217.orig.tar.gz
>

Thanks for this update. I see that you are now using a feature in
debian/rules that was recently
introduced in dpkg 1.16.1.

| DPKG_EXPORT_BUILDFLAGS = 1



| include /usr/share/dpkg/buildflags.mk







(see http://lists.debian.org/debian-devel-announce/2011/09/msg00001.html)

Unfortunately, this makes it harder to backport mriconvert. Since this
feature is only necessary to
emulate the previous behavior of dpkg in exporting CFLAGS etc. would you
mind making it conditional
on the actual presence of a recent dpkg version?

Thanks in advance!

Michael

-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://mih.voxindeserto.de
Jabber: michael.hanke at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20111006/9d941f49/attachment.html>