[10:28] cjwatson, hmm, so it seems esm packages are actually not visible on LP ... fonto-de-kerno gets "libgssapi-krb5-2 1.13.2+dfsg-5ubuntu2.2+esm1" from the core snap dpkg.list file ... looking at https://launchpad.net/ubuntu/xenial/+source/krb5 it does not seem to know this version ... [10:29] does my snap need to subscribe to UA ? 🙂 [10:48] ogra: I would indeed not expect them to be visible there. ESM packages are uploaded to separate PPAs (~ubuntu-esm/+archive/ubuntu/esm-{infra,apps}-{security,updates}). As discussed previously, the format of dpkg.list is going to have to be extended somehow to keep track of what PPAs things came from. [10:48] ogra: And yes, these PPAs are private. You either need a UA subscription or an archive subscription to those PPAs in Launchpad in order to fetch from them. [10:49] ogra: (A UA subscription would allow you to fetch from esm.ubuntu.com, not from LP.) [10:50] ogra: That particular upload is in esm-apps-security. [10:51] well, i guess i'll just disable xenial for now then ... [10:52] There really isn't an alternative to anything that's fetching ESM packages having some kind of suitable access. [10:52] right ... something to take into account for your implementation then ... (i guess it will have more powers than an external snap 🙂 ) [10:54] Right - either users of it will need to be given a suitable subscription, or we'll need a way to run it centrally. [10:54] The former would be quite a bit simpler. [10:56] yeah ... perhaps it could be hooked into the brand store though ... (UI wise at least) [10:57] It would probably not be impossible to fetch from esm.u.c given a UA subscription, with a few heuristics to map URLs around. [10:57] Brand stores and Launchpad are entirely disconnected, so that would be significant complexity you're adding to this project right there - are you sure? [10:57] They also seem quite conceptually unrelated. [10:58] well, you get a "virtual subscription" along when using a brand store with a contract for UC16 i guess ... [10:58] As I mentioned in previous calls, if we can possibly get away with it we don't intend to do this as a web service in the first iteration. [10:58] ah, k [10:58] I explicitly asked if a script would do and was told yes. [10:59] Anyway, if a brand store grants a UA subscription, then the UA subscription is the relevant thing. [11:00] yeah, i dont think it matters what the UI is ... i was just thinking it might make things easier over separately handing out UA [11:00] I think we could cope with a bit of URL-hacking on esm.u.c; the URLs should be predictable. [11:00] ... especially since a core UA is likely only relevant for a minimal set of packages