Procedure for adding dependency

Pierre Equoy pierre.equoy at canonical.com
Thu Feb 4 03:47:50 UTC 2016


Hi Rod,

On Thu, Feb 4, 2016 at 4:57 AM, Roderick W. Smith <rod.smith at canonical.com>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> A while ago I had a problem with a dependency for a new test not
> showing up in Checkbox. I've just submitted merge requests for a new
> test that again depends on a new package:
>
> https://code.launchpad.net/~rodsmith/checkbox/new-cpu-test/+merge/284966
>
> https://code.launchpad.net/~rodsmith/plainbox-provider-canonical-certification/+git/plainbox-provider-canonical-certification/+merge/284971
>
> This one depends on a fairly recent version of stress-ng, which I've
> uploaded to the certification PPA. (The version in all Ubuntu releases
> through Wily are too old for this test.) I've put in the "package.name
> = 'stress-ng'" line in stress.txt.in, but if I need to modify another
> file to ensure that stress-ng will be installed, could somebody please
> tell me what to modify? Thanks.
>

I might be wrong, but I think you may want to edit the Debian control file
in the packaging repository to include stress-ng in the "Depends" section:

https://git.launchpad.net/~checkbox-dev/plainbox-provider-canonical-certification/+git/packaging-server/tree/debian/control

You may also use the "Recommends" section instead; you can check the Debian
doc about this here:
https://www.debian.org/doc/debian-policy/ch-relationships.html

And maybe someone else will have an opinion about this :)

P.S.: It looks like the merge that was done after your modification is
breaking things [1], but I'm not sure why exactly (I mean it's a merge
conflict but I'm not sure of the root cause).

[1] for example on Xenial build:
https://launchpadlibrarian.net/236184287/buildlog.txt.gz

-- 
Pierre Equoy
QA & Certification Engineer | Canonical
www.canonical.com | www.ubuntu.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/checkbox-devel/attachments/20160204/3e71e06c/attachment.html>


More information about the Checkbox-devel mailing list