Hi Kyle,
On 7 February 2017 at 16:28, Kyle Fazzari wrote:
> It doesn't, I'm afraid. That fix (and another coming soon[1]) are
> specific to stage-packages, whereas it sounds like popey is using
> `source` directly. I don't think there's a way to do this today, but we
> were discussing implementin
On Tue, Feb 7, 2017 at 1:20 PM, Oliver Grawert wrote:
> hi,
> On Di, 2017-02-07 at 16:07 +, Alan Pope wrote:
> > Hi,
> >
> > Suppose I have a snap which requires a couple of non-archive debs as
> > stage packages. Typically I'd have a part for each which uses the
> > source: of a url directly
On Tue, Feb 7, 2017 at 1:07 PM, Alan Pope wrote:
> Hi,
>
> Suppose I have a snap which requires a couple of non-archive debs as
> stage packages. Typically I'd have a part for each which uses the
> source: of a url directly to the deb using the dump plugin. This works
> fine building on my amd64
On 02/07/2017 08:20 AM, Oliver Grawert wrote:
> hi,
> On Di, 2017-02-07 at 16:07 +, Alan Pope wrote:
>> Hi,
>>
>> Suppose I have a snap which requires a couple of non-archive debs as
>> stage packages. Typically I'd have a part for each which uses the
>> source: of a url directly to the deb u
hi,
On Di, 2017-02-07 at 16:07 +, Alan Pope wrote:
> Hi,
>
> Suppose I have a snap which requires a couple of non-archive debs as
> stage packages. Typically I'd have a part for each which uses the
> source: of a url directly to the deb using the dump plugin. This
> works
> fine building on my
Hi,
Suppose I have a snap which requires a couple of non-archive debs as
stage packages. Typically I'd have a part for each which uses the
source: of a url directly to the deb using the dump plugin. This works
fine building on my amd64 laptop (or wherever) and I end up with an
amd64 snap.
However