| ral | Hello. Feel free to send me to somewhere better to ask this. If an upstream has a deb package in universe, and a snap package, is there any mechanism to remove the deb package from the archive and have it not be imported from Debian? | 14:47 |
|---|---|---|
| rbasak | There is a sync blacklist that could technically achieve that. I don't know if we have any established policy on whether to use the sync blacklist for that particular purpose though. | 14:53 |
| rbasak | https://bazaar.launchpad.net/~ubuntu-archive/+junk/sync-blacklist/view/head:/sync-blacklist.txt | 14:54 |
| rbasak | You could file a bug against the (deb) package in Launchpad to explain reasoning and subscribe ~ubuntu-archive to the bug in the first instance. | 14:55 |
| rbasak | ral: ^ | 14:55 |
| ral | rbasak: Thanks, I'll give that a go. | 15:01 |
| rbasak | ral: which package, OOI? I'm curious to see how that goes since it might become a general request. | 15:10 |
| ral | rbasak: mosquitto | 15:10 |
| rbasak | Thanks | 15:10 |
| rbasak | ral: ah, a library package? Removing those requires removals of rdeps. | 15:11 |
| rbasak | You'd have to remove baresip also. | 15:11 |
| rbasak | And not having a library packaged as a deb precludes packaging anything that needs that library. | 15:12 |
| ral | A fair point. | 15:12 |
| ral | There might be a compromise though. | 15:13 |
| ral | Just packaging the library would solve those problems and it's not the library that tends to need the package updates. | 15:15 |
| rbasak | That would require either convincing the Debian maintainer to do that, or to maintain a delta in Ubuntu indefinitely. | 15:16 |
| ral | I maintain the deb package (not as a dd or dm) | 15:16 |
| ral | Maybe I'll just orphan the package and let someone else deal with it :) | 15:16 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!