Clean up sync blacklist
Bug #1770792 reported by
Jeremy Bícha
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-meta (Ubuntu) |
Fix Released
|
Wishlist
|
Steve Langasek |
Bug Description
I am attaching a bzr branch here. Because the sync blacklist is a "junk" bzr repository, Launchpad isn't letting me make a merge proposal for it.
I think it makes the blacklist easier to read and use if we get rid of all the old entries.
I went through and verified that these removals were removed from Debian.
There are a few exceptions (gdm3 and openssl1.0) which didn't need to be blacklisted anymore.
I mostly ignored the Mozilla extensions. The Mozilla situation is interesting this year, but I'll save that discussion for later.
Related branches
To post a comment you must log in.
You've dropped ccsm from the blacklist, but the sole binary package built from ccsm in Debian comes from compiz source in Ubuntu; I think this needs to be retained.
You've traded icedove for thunderbird, but why should thunderbird be blacklisted? It's currently maintained in Ubuntu and not merged from Debian but I don't see any reason in principle that it couldn't be.
Why are you dropping the blacklist of fbxkb, which was identified in the blacklist file as "obsolete GNOME panel applet"?
I am satisfied that the rest of the changes here are correct, however I would want the rationales to be better documented in the commit history. I would ask you to please:
- rebase on the current sync-blacklist branch (there is a conflict)
- divide the commits up according to rationale (e.g., dropped because package removed from unstable; vs dropped because package is now in Ubuntu again; vs. reshuffling of file contents)
- resubmit
Or, you can punt this to me to do and I'll apply these changes when I have a chance.