Please sync adept (2.1.3) from Debian (unstable)

Bug #123635 reported by Marco Rodrigues
2
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: adept

 adept (2.1.3) unstable; urgency=low
 .
   * Ported to new apt-front. Closes: bug#423736.
   * Built with new apt. Closes: bug#429806.

- http://packages.qa.debian.org/a/adept/news/20070627T073202Z.html

Revision history for this message
Colin Watson (cjwatson) wrote :

adept has very extensive modifications. It seems highly unlikely that it can be synced, and you've provided no justification.

Revision history for this message
Marco Rodrigues (gothicx) wrote :

Extensive modifications? The changelog don't show that.. The justification is now that has built to new apt 7 and ported to new apt-front that need to be upgraded on gutsy.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

This has 27 ubuntu revisions. This is definetly not a sync.

Please do not file syncs for things that you do not understand. If you dont understand it, err on the side of caution, and leave it alone. Particularly packages in main.

Changed in adept:
status: New → Invalid
Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.