On Sat, Sep 24, 2016 at 9:58 AM, Eric Smith wrote:
> On Sat, Sep 24, 2016 at 2:50 AM, Dan Horák wrote:
>> As I wrote earlier package maintainers shouldn't (must not) initiate
>> any non-scratch builds in the secondary build systems, the koji-shadow
>>
On Sat, 24 Sep 2016 02:58:45 -0600
Eric Smith wrote:
> On Sat, Sep 24, 2016 at 2:50 AM, Dan Horák wrote:
> > As I wrote earlier package maintainers shouldn't (must not) initiate
> > any non-scratch builds in the secondary build systems, the
> > koji-shadow
On Sat, Sep 24, 2016 at 2:50 AM, Dan Horák wrote:
> As I wrote earlier package maintainers shouldn't (must not) initiate
> any non-scratch builds in the secondary build systems, the koji-shadow
> semi-automated system (and other tools) managed by release engineering
> take care of
On Sat, 24 Sep 2016 02:35:56 -0600
Eric Smith wrote:
> On Sat, Sep 24, 2016 at 2:14 AM, Dan Horák wrote:
> > that's correct, only F-26/rawhide has aarch64 as part of primary
> > koji instance, F<=25 are still built in
> > http://arm.koji.fedoraproject.org
>
>
On Sat, 24 Sep 2016 02:01:11 -0600
Eric Smith wrote:
> I wrote:
> > Normally I build release packages and push updates using "fedpkg
> > build" and "fedpkg update". I've already done that for a few
> > packages for f24, but those didn't get aarch64. Is there a simple
> > way
I wrote:
> Normally I build release packages and push updates using "fedpkg
> build" and "fedpkg update". I've already done that for a few packages
> for f24, but those didn't get aarch64. Is there a simple way to build
> them and push updates for aarch64 as well?
On Sat, Sep 24, 2016 at 12:54
On Fri, 23 Sep 2016 20:49:25 -0600
Eric Smith wrote:
> Normally I build release packages and push updates using "fedpkg
> build" and "fedpkg update". I've already done that for a few packages
> for f24, but those didn't get aarch64. Is there a simple way to build
> them and