> On 16 Aug 2020, at 9:41 am, andy pugh <[email protected]> wrote:
>
> I am starting to feel that I might have bitten off more than I can chew here.
>
> Does anyone have any idea why _some_ packages fail and others seem OK?
>
> http://buildbot.linuxcnc.org/buildbot/grid
>
> I would like to see green all the way before releasing, but I suspect
> that is only achievable with a lot more work and knowledge than one
> person can manage.
>
> But even orange all-over is looking hard to achieve.
>
I wish I could help.
I did notice this in the lintian stdio for the 4040, 4041 & 4042 buster builds.
W: linuxcnc-doc-cn: empty-binary-package
N:
N: This binary package appears to be empty, and its description does not
N: say that it's a metapackage or a transitional package. This is often due
N: to problems with updating debhelper *.install files during package
N: renames or similar problems where installation rules don't put files in
N: the correct place.
N:
N: If the package is deliberately empty, please mention in the package long
N: description one of the phrases "metapackage", "dummy", "dependency
N: package", or "empty package".
N:
N: Previously, Lintian also accepted the use of "virtual package". This was
N: removed to avoid overloading the term. If you have been relying on the
N: phrase "virtual package" to avoid this warning, please replace it with
N: one of the others.
N:
N: Severity: important, Certainty: wild-guess
N:
N: Check: files, Type: binary, udeb
N:
In 4042 this is the last entry and in 4040 & 4041 the logging continues. I
don't know if that means anything.
I have noticed recently that there will be a test fail on a build then the next
build it may pass and there seems to be no changes made.
Cheers, Phill
P.S. I did notice a few spelling error notifications in the lintian stdio as
well. I don't mind going through and trying to fix them if that is any help.
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
