On Tue, 2019-10-29 at 20:30 +0100, Martin Jansa wrote:
> PR server never knows which one is really newer (in git).
>
> It just returns max(LOCALCOUNT)+1 when it gets query for hash which
> isn't stored in the database yet.
>
> Either the build in question didn't use PRserv at all or PRserv's cach
On Mon, 2019-10-28 at 19:06 +, Ross Burton wrote:
> On 28/10/2019 16:25, robert.jos...@redrectangle.org wrote:
> > I'm using buildhistory in one of my builds that creates a package
> > feed, and a recent update to systemd on warrior triggered version-
> > going-backwards errors:
> >
> > ERROR:
I'm using buildhistory in one of my builds that creates a package feed, and a
recent update to systemd on warrior triggered version-going-backwards errors:
ERROR: systemd-conf-241+AUTOINC+511646b8ac-r0 do_packagedata: QA Issue: Package
version for package systemd-conf-src went backwards which wo
On Sun, 2019-06-23 at 16:15 +0300, Adi Malca wrote:
> Hello,
>
> I'm looking for the current official OPKG spec with spelling and case
> sensitive.
> For example:
> Package:
> Version:
> Description:
> Section:
> Priority:
> Maintainer:
> License:
> Architecture:
> OE:
> Homepage:
> Depen
On Sat, 2017-07-15 at 15:47 +0300, Robert Berger wrote:
> Hi,
>
> On 2017-07-14 23:32, Robert Joslyn wrote:
> >
> > Just to clarify, the typical way this is done is to put the major
> > version number as part of the package name. For example, the
> > recipes
>
On Fri, 2017-07-14 at 19:49 +0100, Burton, Ross wrote:
>
> On 14 July 2017 at 18:17, Jimi Damon wrote:
> > Do to a fun "feature" of zeromq, the newest libraries are not
> > backward compatible and hence I need to install a zeromq-4.1.5 and
> > zeromq-3.2.2 libraries onto my target to assist with
