On Fri, 5 Jan 2007, Joey Hess wrote: > What's going on is that a base sarge system looks like this: > > [ snipped datailed explanation ]
Ok, I see. Not dpkg fault. If it helps I can reintroduce /usr/doc in base-files in etch ;-) > The following in base-files's postinst would fix both issues. > > if [ -d /usr/doc ] && [ ! -L /usr/doc ]; then > find /usr/doc -maxdepth 1 -mindepth 1 -type l -print0 | xargs -0 rm -f > rmdir --ignore-fail-on-non-empty /usr/doc 2>/dev/null > fi Well, what I see is that after an upgrade from sarge to etch, the user may have an empty /usr/doc. But even in such case, it is not base-files business to remove symlinks indiscriminately in /usr/doc, as they could be there because the system admin puts them there deliberately for whatever reason. BTW: Are we talking about the base-files version in etch, for upgrades from sarge, or the one in lenny for upgrades from etch? (or both) I could add the rmdir thing for etch, if the release managers think we need it. If not, we can leave this to the user. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
