On Tue, May 19, 2015 at 08:44:43PM +0200, Anto wrote:
> What is the relationship between the packages in the merged repository and
> sources on gitlab? Are you only taking the sources on gitlab under
> "pkgs-base" group? If so, is there any clear process to include the sources
> on other groups into the "pkgs-base" group, e.g. eudev package, then into
> the merged repository?

Basically almost all packages in gitlab should be compiled and pushed in
the repository, except for packages in users namespace.

Actually not all packages are ready for that, so, only a subset of them
are in the repository. You can take a look at https://ci.devuan.org to
see which packages are already done ( the blue dotted -binaries packages
).

When the release will be ready, all packages in gitlab will be pushed in
the repository.

After build, all packages are pushed in the /devuan archive, and then
amprolla merge them with ordinary debian repositories to get a full
archive ( the /merged one ).



> Back to my previous question, what do we need to do to be able to have the
> packages included into the merged repository? Please don't hesitate to ask
> me if you would need somebody to test them.

Basically, if the package is already in our gitlab, you can fork the
repo in your user, modify it and then push a merge request. Or if you
want to apply to be the maintainer, you can just open an issue for that,
and if accepted your user will have permission to work on the repository
on gitlab directly.

For a package to be pushed on devuan repositories, it has to be
buildable ( both binaries for all architectures and source package )
according to git-buildpackage utility and pbuilder, as they are used in
jenkins-debian-glue on our build hosts network.



--

Franco (nextime) Lanza
Lonate Pozzolo (VA) - Italy
SIP://casa@???
web: http://www.nexlab.net

NO TCPA: http://www.no1984.org
you can download my public key at:
http://danex.nexlab.it/nextime.asc || Key Servers
Key ID = D6132D50
Key fingerprint = 66ED 5211 9D59 DA53 1DF7 4189 DFED F580 D613 2D50
-----------------------------------
echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D212153574F444E49572045535520454D20454B414D204F54204847554F4E452059415020544F4E4E4143205345544147204C4C4942snlbxq | dc
-----------------------------------