As a contributor to adept, I would second a serious use of caution in any sort of syncing. If we have a new version of apt-front to work with, I would urge an approach of a very supervised and tested merge more than a sync.
We do have extensive changes to adept including crash bug fixes with the upgrader, the inclusion of the kubuntu logo for supported packages, changelog viewing support, and quite a few more grab-bag bug fixes. Some of these bug fixes have greatly changed how some things happen in adept. The feature I'm working on now for fixing the dpkg locks is one of the most complained about bugs and it requires some serious tinkering in how adept opens the dpkg database for use with the adept UI. Let's please make sure we've got a good reason for why we need to do this. As I stated previously, if an apt or apt-front change requires some updating of adept, I'll see if I can put some time into helping after I'm done with the bug I'm currently on. I just don't want to see us throw away a lot of the stuff we've got in there. -- Please sync adept (2.1.3) from Debian (unstable) https://bugs.launchpad.net/bugs/123635 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
