On Tue, Sep 25, 2001 at 02:20:38PM -0500, Colin Watson wrote: > If this prevents it from installing, perhaps xlibs could conflict with > those packages that have been removed rather than updated for the new > app-defaults arrangement? Otherwise it's going to be difficult to > achieve a clean upgrade path without reinstating lots of packages we've > removed (presumably for good reasons). > > I realize that an enormously long Conflicts: line for xlibs would be > bad, but there should be relatively few packages which contained > app-defaults files and were removed between potato and woody. Actually, I goofed something up in 4.1.0-6. This is fixed in my -7 prerelease packages and will be in -7 proper. Basically: 1) xlibs won't "ship" the symlink, so dpkg won't bitch 2) xlibs's preinst will move the app-defaults dir to a temporary place 3) a) xlibs's postinst will remove the temporary dir b) xlibs's postinst will create the app-defaults symlink 4) xlibs's postrm will reverse step 2) on abort-install or abort-upgrade I should *also* Conflict: with app-defaults using packages from potato that have been abandoned in woody (all surviving woody packages migrated to /etc/X11/app-defaults months ago). Colin, can you help me to come up with a such a list? -- G. Branden Robinson | It doesn't matter what you are Debian GNU/Linux | doing, emacs is always overkill. branden@debian.org | -- Stephen J. Carpenter http://people.debian.org/~branden/ |
Attachment:
pgp7sZ0dXl_ck.pgp
Description: PGP signature