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.
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.