Package: python3-bsddb3 Version: 5.2.0-1 Severity: serious Hi,
while looking into #700782, we discovered that there is a symlink vs. directory conflict between python3-bsddb3 and python3.2-dev: python3.2-dev has /usr/include/python3.2 -> python3.2mu python3-bsddb3 ships /usr/include/python3.2/bsddb3 Please move the files shipped under python3.2/bsddb3 to python3.2mu. # apt-get install python3-bsddb3 # apt-get install python3-dev [...] Setting up python3.2-dev (3.2.3-6) ... WARNING: non-empty directory on upgrade: /usr/include/python3.2 total 0 drwxr-xr-x 2 root root 60 Feb 20 09:08 bsddb3 Setting up python3-dev (3.2.3-5) ... [...] # ls -lad /usr/include/python* drwxr-xr-x 3 root root 60 Feb 20 09:08 /usr/include/python3.2 drwxr-xr-x 2 root root 1900 Feb 20 09:08 /usr/include/python3.2mu After fixing this in python3-bsddb3, please clone this a bug and reassign to python3.2-dev to add an appropriate versioned Conflicts against the buggy python3-bsddb3 versions. Breaks is probably not sufficient to solve this "file conflict", as apt could decide to deconfigure (and not upgrade) python3-bsddb3 before installing/upgrading python3-dev. Andreas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
