Re: Continuous integration for Debian packages

On Wed, Dec 21, 2016 at 04:36:54PM +0300, Andrey ``Bass'' Shcheglov wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > I want to use a continuous integration server (Jenkins or TeamCity) to > build binary packages from the official Debian distribution. If using Jenkins have

Re: Continuous integration for Debian packages

Ian Jackson writes ("Re: Continuous integration for Debian packages"): > dgit is not formally available in backports (yet), but the dgit.deb > from unstable is directly installable and useable back to at least > stretch. I mean squeeze. Ian. -- Ian JacksonThese opinion

Re: Continuous integration for Debian packages

Andrey ``Bass'' Shcheglov writes ("Re: Continuous integration for Debian packages"): > On 21.12.2016 16:40, Andrey Rahmatullin wrote: > > It's not clear what does "build binary packages from the official Debian > > distribution" mean. Do you want

Re: Continuous integration for Debian packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21.12.2016 16:40, Andrey Rahmatullin wrote: >> I want to use a continuous integration server (Jenkins or TeamCity) t o >> build binary packages from the official Debian distribution. > It's not clear what does "build binary packages from the officia

Re: Continuous integration for Debian packages

On Wed, Dec 21, 2016 at 04:36:54PM +0300, Andrey ``Bass'' Shcheglov wrote: > I want to use a continuous integration server (Jenkins or TeamCity) to > build binary packages from the official Debian distribution. It's not clear what does "build binary packages from the official Debian distribution" m

Continuous integration for Debian packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I want to use a continuous integration server (Jenkins or TeamCity) to build binary packages from the official Debian distribution. Do I have to somehow account for Debian-specific use cases like NMU, Team Upload (dch --team) and/or QA Upload (