[20:24] <ahasenack> hi, can a package have a build-dep that's only available in the backports pocket in a particular ubuntu release?
[20:24] <ahasenack> assuming the package itself is not in backports
[21:28] <tsimonq2> ahasenack: iirc, no, but I could be wrong.
[23:24] <rbasak> ahasenack: I agree with tsimonq2.
[23:30] <tsimonq2> rbasak: Well, I think *should* it is a different question than *can* it. I think the answer should be no on both counts, but I don't remember if backports was enabled even when apt pinned at a lower value on the builders.
[23:31] <rbasak> tsimonq2: you can build it. For example you can enable backports in a PPA. But it isn't acceptable for the archive.
[23:32] <tsimonq2> rbasak: Hm, alright. Out of curiosity, was this ever formalized anywhere or is it just an unspoken rule?
[23:33] <rbasak> I think Launchpad won't permit such a package to end up in the archive unless you're an archive admin.
[23:33] <tsimonq2> Hm, ok.
[23:34] <tsimonq2> Would you happen to know if I could test something like this on staging.launchpad.net?
[23:34] <rbasak> I don't know.
[23:34] <tsimonq2> Alright, thanks rbasak.
[23:34] <rbasak> But I'm curious to know the answer :)
[23:35] <tsimonq2> Same :)