ollieparanoid / binary-package-repo Goto Github PK

Could you try build binary package of AzPainter for postmarketOS?

• http://github.com/symbian9/azpainter

REFERENCE:

• http://azsky2.html.xdomain.jp/linux/azpainter.html
• http://azsky2.html.xdomain.jp/memo/index.html

Right now, the description simply says "user" (because we build the package in /home/user/build).
I have upstreamed a parameter to set any description in abuild. But it will take some time, until it lands in the released version of abuild, that gets actually used in Alpine Linux.

I suggest we wait until they released it, and then simply use the parameter in pmbootstrap to set the description to postmarketOS (maybe with a date appended?). It will probably make sense to add a parameter to pmbootstrap, so we can use another value when building for the binary package repo, than when creating packages locally.

This should not happen.

Use git-lfs, so the repository performs better: https://git-lfs.github.com

It looks like we will need our own git-lfs storage backend though, as it is not possible to remove old files from GitHub's integrated LFS storage: git-lfs/git-lfs#1043

So more research is needed for this topic.

Right now, we clone the binary packages repo from GitHub.
It would be better to clone the packages from a mirror, so we have less traffic on the GitHub mirror.
In order to do that, we need a mirror that actually gets updated directly on changes.

Binary mirrors get discussed here:
https://github.com/postmarketOS/pmbootstrap/issues/365

It fails with:

(004383) [10:27:27] Compare: usr/bin/aarch64-alpine-linux-musl-c++
(004383) [10:27:27] CHALLENGE FAILED for usr/bin/aarch64-alpine-linux-musl-c++:Entry 'usr/bin/aarch64-alpine-linux-musl-c++' has a different type!
(004383) [10:27:27] Compare: usr/bin/aarch64-alpine-linux-musl-g++
(004383) [10:27:27] CHALLENGE FAILED for usr/bin/aarch64-alpine-linux-musl-g++:Entry 'usr/bin/aarch64-alpine-linux-musl-g++' has a different type!

Log:
https://api.travis-ci.org/jobs/261273294/log.txt?deansi=true

Right now we use travis foldings with shell color output - but that does not get displayed in the raw log.
Displaying the raw log is necessary for very long builds.
It would be better to have the sections printed without color, but somehow easily recognizable. Example:

#
# SECTION START
#

Right now it fails, because we get a so:libc.musl-armhf.so.1 entry in the weston-99999-r2.apk.buildinfo.json file. I guess the easiest fix would be to not listso: entries in the buildinfo.json file, because they are redundant anyway. We already list all installed packages!

Actually we only list the packages, that the package we're building depends on. So the fix would be to replace all so: packages with the packages, by whom they are provided.

And there I thought weston would work, because it works for armhf already...

https://travis-ci.org/postmarketOS/binary-package-repo/builds/264509723

Interestingly, the weston-dev generated with Travis CI is missing the header files. So it might be a bug in weston's buildsystem?

It will just be a great source of confusion once this gets the much appreciated uptake.