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

Re: symlink vs. directory "conflicts"

On Sat, 2012-10-06 at 00:29:22 +0200, Andreas Beckmann wrote:
> On 2012-10-04 11:34, Guillem Jover wrote:
> > Nope, dpkg does not currently have enough information (missing
> > metadata) to know if a path was shipped in the package as a directory
> > or as a symlink, and to be able to distinguish between admin modified
> > directory←→symlinks. AFAIR there's already a bug report about this kind
> > of situation on dpkg.
> Does dpkg know the link target that was shipped in the package?

Nope, that's part of the missing metadata.

> I think at least debsums cannot report modified symlinks ...

Right, debsums has as much information as dpkg.

> That's probably something that should be included dpkg's metadata, too.

Well, storing that a path was a symlink w/o storing where it pointed
to would be a bit useless :), but yes the idea is that most metadata
in the tar header will be preserved.

> (Hmm, M-A: same packages shipping a shared symlink with a different
> target - does this fail properly?)

Yes, in that case the file system is used as reference to check if
they match, so unfortunately, currently if such symlink gets changed
and a new M-A:same instance gets installed it will fail to unpack.


Reply to: