On 10/12/2015 11:57 AM, Piotr Ożarowski wrote:
> you're in, though. Welcome
>
> (and please note that we will use git-dpm, not any other git related
> tool so either use that or make sure it's compatible)
Thanks for adding me. I've uploaded the twistar packaging to Alioth,
it's at
git+ssh://git.de
dpmt-commit ml is already full of emails (in 4 days I have 500+ emails
there!) should we disable the git summary message? It doesnt give
additional useful information, and in cases like small fix + push it
would prevent to double the emails sent.
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
M
> Yep. Again, I've seen this, but don't know the cause and don't think it
> actually has any negative effect.
it is because a new tag is being pushed, so the post-receive hook is
trying to get a diff of it, but it fails as.. there is no "previous"
state for that. it is harmless, but annoying to s
> export PYBUILD_TEST_ARGS={dir}/tests
should I do that by default in pybuild if
* "test" or "tests" directory is detected
* PYBUILD_TEST_ARGS is not set
* nose or pytest test suite is used
?
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.grif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
I'm looking for a sponsor for my package denyhosts-server.
- From the ITP:
- -
Package name: denyhosts-server
Version : 2.0.0
Upstream Author : Jan-Pascal van Best
URL : http://github.com/janpascal/d
Hi,
On Tue, Oct 13, 2015 at 11:42:57PM +0200, Piotr Ożarowski wrote:
> > Searching for distribute
> > Reading https://pypi.python.org/simple/distribute/
> > Download error on https://pypi.python.org/simple/distribute/: [Errno 111]
> > Connection refused -- Some packages may not be found!
> > Coul
On Oct 14, 2015, at 01:26 PM, Piotr Ożarowski wrote:
>> export PYBUILD_TEST_ARGS={dir}/tests
>
>should I do that by default in pybuild if
>* "test" or "tests" directory is detected
>* PYBUILD_TEST_ARGS is not set
>* nose or pytest test suite is used
>
>?
Maybe just on the first two conditions, on
[Barry Warsaw, 2015-10-14]
> On Oct 14, 2015, at 01:26 PM, Piotr Ożarowski wrote:
>
> >> export PYBUILD_TEST_ARGS={dir}/tests
> >
> >should I do that by default in pybuild if
> >* "test" or "tests" directory is detected
> >* PYBUILD_TEST_ARGS is not set
> >* nose or pytest test suite is used
> >
>
On Oct 14, 2015, at 04:28 PM, Piotr Ożarowski wrote:
>[Barry Warsaw, 2015-10-14]
>> On Oct 14, 2015, at 01:26 PM, Piotr Ożarowski wrote:
>>
>> >> export PYBUILD_TEST_ARGS={dir}/tests
>> >
>> >should I do that by default in pybuild if
>> >* "test" or "tests" directory is detected
>> >* PYBUILD_TES
> Oh sorry, I think I misunderstood. The conditions above are ANDed not ORed.
> :)
ups, sorry. I wrote it as foo and bar and baz and later replaced "and"
with bullet point to make it... more readable, eh ;)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl
On Oct 14 2015, Piotr Ożarowski wrote:
>> export PYBUILD_TEST_ARGS={dir}/tests
>
> should I do that by default in pybuild if
> * "test" or "tests" directory is detected
> * PYBUILD_TEST_ARGS is not set
> * nose or pytest test suite is used
Yes please!
Best,
-Nikolaus
--
GPG encrypted emails p
Hi Brent,
I intend to package pyfasta for the Debian distribution. I tried to also
run the unit tests:
$ LC_ALL=C python setup.py nosetests
running nosetests
running egg_info
writing pyfasta.egg-info/PKG-INFO
writing top-level names to pyfasta.egg-info/top_level.txt
writing dependency_links to
Hello,
Can somebody please explain this email? I know it says 2015-11-05, but
looks like it was sent today.
As far as I can tell version 1.3.6-4 is in testing (not 1.3.6-3 as per
message), it got into testing 5 days ago, and this version has closed the
bug.
Is this something I have to worry abou
On Thu, 15 Oct 2015 at 15:50 Brian May
wrote:
> As far as I can tell version 1.3.6-4 is in testing (not 1.3.6-3 as per
> message), it got into testing 5 days ago, and this version has closed the
> bug.
>
Actually, I may have misread that. Probably only got into testing today,
maybe not enough ti
The date in the mail is the date on which the package will be removed from
testing if the cause for it being marked for autoremoval is not rectified;
in other words, you would still have until 2015-11-05 to resolve the
problem.
In this case, the cause is the RC bug which is fixed in 1.3.6-4. Howev
15 matches
Mail list logo
