> packaged bzr plugins install themselves to the "bzrlib/plugins" directory > of the bzr package, which is one of the places that bzr looks for them. The do > depend on the bzr package though, so I'm not sure why this is happening, > unless the plugins were local installs. It seems like this would be a harmless > warning in that case, and will probably go away with the migration to > --install-layout > deb.
I don't think this is a bug. The symlinks for python2.4 are not yet removed for the plugins, so you do see the warning from dpkg. The plugins are useless in the python2.4 sitedir, because bzr is missing support for 2.4 now. the python support tools don't have a dependency checker, so either we have to remove all symlinks for a runtime once it moves from the supported to the old status (and keep those explictely we need to keep), or we keep them as we do now. > I've just realised that that change will probably in fact break bzr plugins, > as > bzr loads them by using __file__, so they have to be installed to the same > "bzrlib". > I will make sure to test that and rebuild as necessary. It seems like that > will be > a problem for those that try to install bzr plugins system wide with setup.py > though. > Is this a case you considered for the "--install-layout deb" change? I'm not > sure > if we can fix it in bzr, as it does not try and load plugins from PYTHONPATH > for > a reason. Well, if you do know that anything that gets installed by a user into /usr may be overwritten by .deb's, fine. But as it looks, bzr is able to find plugins in the user's home directory as well, so how are these found? -- Unable to delete old directory in jaunty https://bugs.launchpad.net/bugs/332824 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
