Mailinglist Archive: opensuse-buildservice (247 mails)

< Previous Next >
Re: [opensuse-buildservice] Still trying to find a solution when a package depends on universe ubuntu repository
On Wed, Jun 5, 2013 at 4:57 AM, Gianluca Emme <gmaxera@xxxxxxxxx> wrote:
This is a short summary of my adventure :-) :
- I'm building a package named yarp that depends on libace
- libace is into the universe ubuntu repository
- universe ubuntu repository is not included into the OBS service
- I'm trying to find a way to fullfill the dependency to build my package
- the solution I tryied are:
1) download the source package of libace, build it into the OBS
without publish it

This is the only sensible option, because:

2) try to fullfill the dependency taking the package from the Debian
repository (where libace is into the standard repository)
3) try to install the .deb binary package during the execution of
debian.rules before the build

Both of these violate the "no binary blobs" rule. And yes, prebuilt
debs are binary blobs, and downloading them at build time, besides
impossible, is also downloading a binary blob.

While it would be preferrably to have universe already in OBS, this is
not possible since universe's requisites allow many packages OBS rules
do not. So the only real alternative is to hand-pick packages for
inclusion, one by one.

This can be done in two ways:
1- Option 1 in your list, on a shared project for all that need
universe dependencies. Someone would create Ubuntu:X.Y:universe and
we'd populate it slowly, with legal review.
2- Same as above, except instead of making OBS build them, someone
populates the project with binaries from the official repos. This
requires OBS admins to work a lot more, but it would be optimal use of
resources. However, since manpower is harder to come by than iron
power, I expect option 1 above would be favoured by OBS admins
(especially since it's been discussed already).
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups