what about something like
ifeq (,$(findstring get-orig-source, $(MAKECMDGOALS)))
export http_proxy=http://127.0.0.1:9/
endif
so unless called with get-orig-source -- it would get defined... ?
On Wed, 06 Feb 2013, Piotr Ożarowski wrote:
> [Dmitrijs Ledkovs, 2013-02-06]
> > On 5 February 2013 17
On Wed, Feb 6, 2013 at 10:24 PM, Thomas Kluyver wrote:
> On 6 February 2013 19:30, Sandro Tosi wrote:
>>
>> please read our "unwritten policy" about Maintainer field at
>> http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
>
>
> "As a general rule of thumb, just set Maintainer to the team;
On 6 February 2013 19:30, Sandro Tosi wrote:
> please read our "unwritten policy" about Maintainer field at
> http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
"As a general rule of thumb, just set Maintainer to the team; there might
be some exceptions, like in situations where the packa
On Feb 06, 2013, at 11:18 AM, Dmitrijs Ledkovs wrote:
>I should add a hook to export that for the build & binary stages of the
>package build in my sbuild config (but not the fetching build-deps) Also one
>should be able to set that in debuild hooks.
That would help make local sbuilds act more li
On Feb 06, 2013, at 01:13 PM, Piotr Ożarowski wrote:
>FTR: pybuild does that by default (http_proxy=http://127.0.0.1:9/)
Nice.
>it probably should be changed to not overwrite existing http_proxy (if set)
>or to make it possible to disable it.
The only case where I found I had to unset http_prox
On Wed, Feb 6, 2013 at 5:12 PM, Thomas Kluyver wrote:
> I suggest that we encourage packagers to make team maintainership the norm,
> and individual maintainership the exception, to avoid this kind of problem.
> This is in line with plenty of other open source projects, where people talk
> about n
On 06/02/13 16:12, Thomas Kluyver wrote:
> Of course, it's good to exercise due diligence, but the flip
> side is that technical changes which I hope would be uncontroversial
> have now taken a back seat to bureaucracy, because one man a few years
> ago declared himself 'the maintainer'.
If the re
On 2013-02-06 at 16:12:21 +, Thomas Kluyver wrote:
> No doubt he should have declared his packages orphaned before he left. But
> whether he got hit by a bus, or just lost interest in them, I'm not
> interested in blaming him. I have e-mailed the MIA team to start the
> 2-month process [3] that
On Feb 06, 2013, at 04:12 PM, Thomas Kluyver wrote:
>I suggest that we encourage packagers to make team maintainership the norm,
>and individual maintainership the exception, to avoid this kind of problem.
>This is in line with plenty of other open source projects, where people
>talk about not bec
On 6 February 2013 12:52, Sandro Tosi wrote:
> Yes I do: Thomas is set as the Maintainer (as opposed to the team
> being the Maintainer), so your are more forced to ask Thomas first
> given the huge changes you're planning to do: did you contact him (it
> doesn't seem so from your email)? have yo
On Wed, Feb 6, 2013 at 12:48 PM, Thomas Kluyver wrote:
> Does
> anyone object to me committing this to the DPMT SVN repository, and seeking
> sponsorship for the new version?
Yes I do: Thomas is set as the Maintainer (as opposed to the team
being the Maintainer), so your are more forced to ask Th
[Dmitrijs Ledkovs, 2013-02-06]
> On 5 February 2013 17:48, Barry Warsaw wrote:
> > http://mail.python.org/pipermail/catalog-sig/2013-February/004831.html
>
> I should add a hook to export that for the build & binary stages of
FTR: pybuild does that by default (http_proxy=http://127.0.0.1:9/)
it
The python-xlrd package is maintained by Thomas Bläsing and the DPMT, but
the packaged version is quite old. A PAPT thread from last year suggests
that Thomas Bläsing is missing in action [1].
I've prepared a new version of the package, using a patch from the bug
tracker, the latest upstream versi
On 5 February 2013 17:48, Barry Warsaw wrote:
> There's been a lot of discussion lately on various forums (e.g. catalog-sig)
> about PyPI security. I realized that our recommendation for setting
> http_proxy in debian/rules can have beneficial local security implications.
>
> More details here:
>
14 matches
Mail list logo
