Re: Which version/change in dpkg made it fully honour file modes?
Hi!
On Sat, 2014-06-14 at 12:46:12 +0100, Michael Tautschnig wrote:
> In my build setup I'm unpacking packages in a wheezy environment, and only then
> go to a sid chroot to build those packages. This has started to cause a bit of a
> headache with a handful of packages that introduce symlinks through quilt
> patches, resulting in errors like this:
>
> dpkg-source: error: cannot represent change to sfst-1.4.6h/NEWS:
> dpkg-source: error: new version is plain file
> dpkg-source: error: old version is symlink to ChangeLog
> dpkg-source: error: unrepresentable changes to source
> So it seems that wheezy's dpkg ignores this:
>
> diff --git a/NEWS b/NEWS
> new file mode 120000
>
> while sid's dpkg fully interprets the this-is-a-symlink bit.
Actually dpkg-source does not even know about git-style patches, it's
just that the patch program has started recognizing them since version
2.7. There's already 749070, and I had pending sending a mail to d-d,
precisely looking for possible build breakages. Anyway I'll try to whip
up that mail today.
> So mainly out of curiosity I was wondering when support for this had been added?
> Obviously I would be really nice to see that backported, but I guess there is no
> urgency here.
Depends on what you mean by backported, if you mean porting back that
functionality to stable, I don't really see it happening as it requires
a new upstream patch version. If you mean to backports.d.o, then I guess
you'll need to talk with the patch maintainer and the backports admins.
I'm not sure that would be a good idea though, as I might, perhaps, end
up disabling git-style patches depending on the discussion on d-d.
Thanks,
Guillem
Reply to: