upload rights for my Debian packages

Daniel Pocock daniel at pocock.com.au
Fri Jan 10 14:09:34 UTC 2014


On 10/01/14 10:41, Iain Lane wrote:
>
>>> One of the 'areas of improvement' on your application talks about test
>>> building packages. When you request or perform uploads explicitly (e.g.
>>> when asking for a sync after Debian Import Freeze), how do you check the
>>> package is suitable for Ubuntu?
>> I look at a lot of things
>> […]
> Thanks for the info which gives me confidence about your QA processes.
> I'm also wondering if you perform any explicit Ubuntu testing. For
> example, do you have a pbuilder or sbuild chroot for the Ubuntu
> development release in which you can test build/run packages, or a full
> installation (including inside a VM)?

For those packages where I use travis-ci, travis is building the
packages in Ubuntu on every commit, e.g.

https://github.com/resiprocate/resiprocate/blob/master/.travis.yml

I have a few virtualization environments, Xen Cloud Platform (XCP)
(headless machines in a data center) and VirtualBox (on dev
workstations/laptop)

My Ubuntu environment is currently saucy running as a guest in XCP

As an upstream developer, users who I deal with directly are using
packages on stable releases of Ubuntu, Debian and Fedora so I tend to do
builds in VMs running the current stable release but I also
intermittently test with pbuilder

Most of the code I work with does not have linking dependencies on other
complicated frameworks like Gnome so it builds just as easily on CentOS5
as on saucy or sid






More information about the Devel-permissions mailing list