On Mon, Aug 15, 2016 at 05:00:52AM +1000, Ben Finney wrote:
> > https://paste.debian.net/789238/
>
> That appears to be a simple failure when the test suite is run. The
> assertions, as reported, are in the ‘test_srst2’ module:
>
> =
> […]
> File "test_srst2.py", line 213, in test_run_bowti
On Sunday, August 14, 2016 10:19:12 PM CEST Ondrej Novy wrote:
> +1 for moving VCS commits too.
+1 also from me! :)
--
Daniele Tricoli 'eriol'
https://mornie.org
signature.asc
Description: This is a digitally signed message part.
Andreas Tille writes:
> Yes, this is what I guessed from the log. However, how can I find out
> why exactly the command is not called?
That seems to be a question to take up with the upstream developer, or
just normal Python debugging.
Unless I'm misunderstanding, this doesn't appear to be a p
On 08/10/2016 10:41 PM, Barry Warsaw wrote:
> * IOW, if
> you choose to use gbp-pq, am I forced to do so when I modify the same repo?
> Or if you choose to use PoQ (plain 'ol quilt), will that affect how others
> can co-maintain the package in git?
That's the point. If we decide to use gbp-p
On Aug 15, 2016, at 11:44 PM, Thomas Goirand wrote:
>If we decide to use gbp-pq, in fact, we're deciding to not decide, and anyone
>can use PoQ (my choice, for example). Indeed, the way to store the patches is
>PoQ, and you then "gbp-pq import", modify, then "gbp-pq export" and store the
>packagin
5 matches
Mail list logo
