Bug#503419: etch-lenny: libvte-common not upgraded because of unmet dep for libvte4
On Sat, Oct 25, 2008, Giovanni Rapagnani wrote: During the upgrade form etch to lenny (aptitude full-upgrade), the following situation occurs: - libvte-common is not upgraded for not breaking the dependency needed by libvte4 - libvte4 remains installed - libvte9 is installed After doing a second 'aptitude full-upgrade', the following situation occurs: - libvte4 is deinstalled - libvte-common is then upgraded. Err ok; and is that a problem? I don't know if libvte9 is a full replacement for libvte4. In this case, maybe adding the info 'Replaces: libvte4 (=1:0.12.2-5)' in the package libvte9 will in the first 'aptitude full-upgrade' run : - remove libvte4 - install libvte9 - upgrade libvte-common Lenny packages should be depending on libvte9 and etch packges on libvte4; both can be installed at the same time, but at the end of the upgrade, libvte4 should be removed automatically (or should be removable manually). -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503419: etch-lenny: libvte-common not upgraded because of unmet dep for libvte4
On 26/10/08 09:56, Loïc Minier wrote: On Sat, Oct 25, 2008, Giovanni Rapagnani wrote: During the upgrade form etch to lenny (aptitude full-upgrade), the following situation occurs: - libvte-common is not upgraded for not breaking the dependency needed by libvte4 - libvte4 remains installed - libvte9 is installed After doing a second 'aptitude full-upgrade', the following situation occurs: - libvte4 is deinstalled - libvte-common is then upgraded. Err ok; and is that a problem? For me, there is no problem. It is just that I find a little confusing to receive a message such The following packages are BROKEN: libvte4 during an upgrade. Even if 30 lines below aptitude says that it will fix this by keeping libvte-common to its current version. Also I don't understand why we would have to run twice 'aptitude full-upgrade', one just after the other, instead of having the whole upgrade done in one run. Said that, there are surely more important thing to do at the moment for releasing lenny. Is it worth giving a word about this in the release-note ? Something like: During the full-upgrade, aptitude could complain about unmet dependencies for the libvte4 package. Just accept that aptitude keeps libvte-common to its current version for satisfying the libvte4 dependencies. At the end of the upgrade, issuing a second aptitude full-upgrade should remove the libvte4 package and then upgrade libvte-common to its lenny version. Giovanni -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503419: etch-lenny: libvte-common not upgraded because of unmet dep for libvte4
This behavior is not encountered when dist-upgrading with apt-get. apt-get directly deinstalls libvte4, upgrade livte-common and installs libvte9. I think then this is more a strange behavior introduced by aptitude. I will then give a word about this in the release-note. Feel free to close the bug. Giovanni -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503419: etch-lenny: libvte-common not upgraded because of unmet dep for libvte4
reassign 503419 aptitude thanks Giovanni Rapagnani wrote: This behavior is not encountered when dist-upgrading with apt-get. apt-get directly deinstalls libvte4, upgrade livte-common and installs libvte9. I think then this is more a strange behavior introduced by aptitude. Thanks, reassigning to aptitude. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#503419: etch-lenny: libvte-common not upgraded because of unmet dep for libvte4
Package: libvte4 Version: 1:0.12.2-5 System: Xen image - i386 - Kernel 2.6.18-6-xen-686 Hi, During the upgrade form etch to lenny (aptitude full-upgrade), the following situation occurs: - libvte-common is not upgraded for not breaking the dependency needed by libvte4 - libvte4 remains installed - libvte9 is installed After doing a second 'aptitude full-upgrade', the following situation occurs: - libvte4 is deinstalled - libvte-common is then upgraded. I don't know if libvte9 is a full replacement for libvte4. In this case, maybe adding the info 'Replaces: libvte4 (=1:0.12.2-5)' in the package libvte9 will in the first 'aptitude full-upgrade' run : - remove libvte4 - install libvte9 - upgrade libvte-common Giovanni. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
