Bug#782173: RFS: chrony/1.30-2 [RC] -- Set the computer clock from time servers on the Net

2015-04-09 Thread gregor herrmann
Control: owner -1 ! Control: tag -1 + moreinfo On Thu, 09 Apr 2015 01:00:12 +0200, Joachim Wiedorn wrote: > I am looking for a sponsor for my package "chrony" [..] > dget -x > http://mentors.debian.net/debian/pool/main/c/chrony/chrony_1.30-2.dsc I'd be willing to sponsor this upload, I just s

Re: CI tests

2015-04-09 Thread gregor herrmann
On Thu, 09 Apr 2015 09:33:51 +0200, Ole Streicher wrote: > for one of my packages (python-astropy), I want to create a Continuous > Integration test. However, I seem to not understand some basics: > > * Are the tests done with the installed package, or with the installed > sources, or both? [..

Bug#779377: RFS: classified-ads/0.03-1 / ITP

2015-04-09 Thread Antti Järvinen
Tobias Frost writes: > Almost... you must regenerate the bitmap during the build. > Manually is not enough. > (Its ok do do it via d/rules, no need to patch your "upstream" > buildsystem. Remember to clean the generated images, e.g using > debian/clean. Ok, question: Initiating bitmap conve

Re: GBP and moving to a new upstream release...

2015-04-09 Thread Darryl L. Pierce
On Thu, Apr 09, 2015 at 05:47:51PM +0200, Dominique Dumont wrote: > On Thursday 09 April 2015 09:21:24 Darryl L. Pierce wrote: > > I've been following the steps as best I can here [1] to upgrade my > > package (qpid-proton) to the latest upstream release (0.9). However, > > these steps result in a

Re: GBP and moving to a new upstream release...

2015-04-09 Thread gregor herrmann
On Thu, 09 Apr 2015 17:47:51 +0200, Dominique Dumont wrote: > > What is the right way to go about this? > First, fix your git repo before attempting an import: > - watch file is broken > - several files have git merge artifacts (try a «ack '<<<'» in your repo) > - upstream and pristine-tar branche

Re: GBP and moving to a new upstream release...

2015-04-09 Thread Dominique Dumont
On Thursday 09 April 2015 09:21:24 Darryl L. Pierce wrote: > I've been following the steps as best I can here [1] to upgrade my > package (qpid-proton) to the latest upstream release (0.9). However, > these steps result in a merge commit (actually, they result in a huge > set of conflicts) and that

GBP and moving to a new upstream release...

2015-04-09 Thread Darryl L. Pierce
I've been following the steps as best I can here [1] to upgrade my package (qpid-proton) to the latest upstream release (0.9). However, these steps result in a merge commit (actually, they result in a huge set of conflicts) and that strikes me as a Bad Thing (tm). Why does GBP try to merge, rather

CI tests

2015-04-09 Thread Ole Streicher
Hi, for one of my packages (python-astropy), I want to create a Continuous Integration test. However, I seem to not understand some basics: * Are the tests done with the installed package, or with the installed sources, or both? * I would need just one one-liner per test, so my debian/tests/co