On Thursday, February 21, 2013 02:02:09 PM Chow Loong Jin wrote:
> On 21/02/2013 12:46, Barry Warsaw wrote:
> > #9 on Steve Bennett's list is right on target IMHO, but I've had this
> > discussion so many times before, I don't have much energy for it again.
> >
> > """
> > 9. Git history is a bunc
On Friday, February 22, 2013 03:14:30 PM Thomas Goirand wrote:
...
> The problem is that with SVN, it takes so much time and space
> (as each tag will generate some files), so you might have been
> fooled into thinking it would also with Git. But the reality simply
> not that at all.
...
I almost
Stefano Rivera wrote:
>Hi Jakub (2013.02.22_23:48:24_+0200)
>
>> * Stefano Rivera , 2013-02-22, 23:31:
>> >* you can ship extensions for more than one 3.x version in the
>> >same private directory, thanks to tags
>>
>> Does dh_python3 support such setup? (I would be very surprised if it
>> did
Stefano Rivera wrote:
>Hi Scott (2013.02.23_00:17:30_+0200)
>> >> >* you can ship extensions for more than one 3.x version in the
>> >> >same private directory, thanks to tags
>> >> Does dh_python3 support such setup? (I would be very surprised if
>it
>> >> did.)
>> >You have a point. That'd be
On Saturday, February 23, 2013 12:24:16 AM Jakub Wilk wrote:
> * Scott Kitterman , 2013-02-22, 17:56:
> >>>>>>* you can ship extensions for more than one 3.x version in the
> >>>>>>same private directory, thanks to tags
> >>>>>
> &
On Thursday, March 14, 2013 05:56:47 PM Dmitry Shachnev wrote:
> Hi,
>
> We discussed new lintian vcs-field-not-canonical check in IRC last week,
> which affects *lots* of packages in our SVN (see [¹]). Now people are
> recommended to use `svn://anonscm.debian.org/*` URIs instead of
> `svn://svn.d
Do you object to the dropping of 2.6 or just the lack of discussion before it
was done?
Scott K
On Monday, May 06, 2013 09:29:11 AM Sandro Tosi wrote:
> Hello,
> has this been discussed *and* agreed on? I can only see Luca's mail
> for python plans, but no ack from other "members of the debian p
On Friday, May 17, 2013 10:53:39 AM Daniel Kahn Gillmor wrote:
> On 05/17/2013 08:22 AM, W. Martin Borgert wrote:
> > Quoting "Scott Kitterman" :
> >> Package: trac-accountmanager
> >
> > ...
> >
> >> Since the package has been removed fr
On Friday, May 17, 2013 01:33:38 PM Daniel Kahn Gillmor wrote:
> On 05/17/2013 01:20 PM, Thomas Kluyver wrote:
> > This came up recently on debian-python. It's a very long thread, but the
> > basic outcome was that, while quite a few people wanted to move away from
> > svn, there was very little co
On Friday, May 17, 2013 01:50:09 PM Daniel Kahn Gillmor wrote:
> On 05/17/2013 01:40 PM, Scott Kitterman wrote:
> > If the team moves to full source git archives, I'll just drop the team
> > from
> > all the packages I maintain.
> >
> > Scott K
> >
On Friday, May 17, 2013 02:13:10 PM Daniel Kahn Gillmor wrote:
> On 05/17/2013 01:55 PM, Scott Kitterman wrote:
> > You misunderstand.
>
> I don't think i misunderstood at all.
>
> > I'm all for having a good common environment for the team to work on. I
>
On Tuesday, May 21, 2013 11:05:30 PM Reuben Thomas wrote:
> Near the start of Chapter 1, Section 1.1:
>
> "implmentation" → "implementation"
>
> Checked against 0.9.4.2.
Fixed in the VCS for the next python-defaults upload.
Thanks,
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@l
I've been working on this a bit ...
On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote:
> python3-defaults maintainer(s?) decided to make python3.3 a supported
> version without prior notice. Yay. Now we have dozens of packages
> failing to build:
>
> boost1.49 FTBFS TODO
> boost1.50 FTBFS TOD
Jakub Wilk wrote:
>Quite a few packages carry Conflicts or Replaces with
>
>python2.4-MODULE or
>python2.3-MODULE or sometimes even
>pythonX.Y-MODULE for X.Y < 2.3.
>
>Not only such packages are long gone, but it's very unlikely that the
>file conflict that was the reason to add these Conflict
On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote:
> I've been working on this a bit ...
>
> On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote:
> > python3-defaults maintainer(s?) decided to make python3.3 a supported
> > version without prior notice.
Vincent Bernat wrote:
>Hi!
>
>I just converted a package to add a Python3 package. I expected this to
>be as simple as:
>
> 1. Declaring the package in debian/control and add the appropriate
>dependency stuff.
> 2. Use dh --with python2,python3 $@.
>
>However, this is more tricky:
>
> - dh_
On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote:
Here's another update based on work I've done, noticed other people did, or
responses to the last one of these I sent. It does not include work which I
neither notice nor people told me about. Items marked as fixed i
On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote:
> On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote:
>
More updates and added all the "unknown" packages from the transition tracker.
Items marked as fixed in the last update have been removed.
>
>
On Wednesday, June 12, 2013 03:13:38 PM Scott Kitterman wrote:
> On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote:
> > On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote:
> More updates and added all the "unknown" packages from the transition
> track
On Wednesday, June 19, 2013 01:57:47 PM Brian May wrote:
> Hello,
>
> Can I please get somebody to review my django-tables package before I
> upload to Debian?
>
> I copied the updates from my django-filter package.
>
> Code is at
>
> http://anonscm.debian.org/viewvc/python-modules/packages/dja
Here's a further update on packages pertaining to the 3.3 transition:
boost1.49 Fixed
flufl.bounce builds now that zope.interface is updated
hivex FTBFS fixed, dependencies fixed, nothing further to do.
libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now builds
for all python3
On Wednesday, June 19, 2013 02:47:44 PM Brian May wrote:
> On 19 June 2013 14:33, Scott Kitterman wrote:
> > Patch to use the installed copy. I had to do this once before.
>
> How do I do this? I don't see any references to objects.inv in the
> upstream source code for
On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> Here's a further update on packages pertaining to the 3.3 transition:
>
> libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now
> builds for all python3 versions
> nuitka FTBFS unrepod
On Friday, June 21, 2013 02:33:02 PM Mike Neish wrote:
> * Sandro Tosi, 2013-06-21, 08:37:
> > Sandro, are you okay with me adding Mike to the team, so the
> > he can commit the patch?
> >
> > sorry for the late reply; sure go ahead,
> >
> > Welcome to the team, Mike! :)
>
On Sunday, June 23, 2013 07:21:53 PM Jakub Wilk wrote:
> * Etienne Millon , 2013-06-23, 14:57:
> >What is the preferred method: update the TODO page[2], post a RFS on
> >the list,
>
> I prefer e-mails, but I don't sponsor much, and other sponsors/reviewers
> preferences may vary.
>
> >or just set
On Friday, June 28, 2013 09:08:33 PM Jakub Wilk wrote:
> * Barry Warsaw , 2013-06-28, 11:46:
> >Could the project admins for DPMT and PAPT please add my non-guest
> >account?
>
> Done for DPMT.
Done for PAPT.
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a su
On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote:
> On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> > Here's a further update on packages pertaining to the 3.3 transition:
> >
> libguestfs - No longer FTBFS on amd64, but does on i386, #71054
On Wednesday, July 03, 2013 02:04:08 PM Barry Warsaw wrote:
> On Jul 03, 2013, at 01:55 PM, Scott Kitterman wrote:
> >Looking at where we are now, the open issues are down to #711761 and
> >#711761.
> Don't forget #711761 and #711761.
>
> :)
Meh. #710545.
Scott
On Wednesday, July 03, 2013 06:15:11 PM PICCA Frédéric-Emmanuel wrote:
> >Looking at where we are now, the open issues are down to #711761 and
> >#711761.
> To my opinion, (I am the maintainer of pytango) this is not a problem if
> pytango is not available on s390. I forwarded the bug to the upstre
On Wednesday, July 03, 2013 01:55:07 PM Scott Kitterman wrote:
> On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote:
> > On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> > > Here's a further update on packages pertaining to the 3.3 transition:
&g
On Monday, July 08, 2013 09:59:02 PM Thomas Goirand wrote:
> Hi,
>
> Over the last months, I've seen lots of inconsistency in the source
> package naming scheme in the python module maintained in the team.
> Sometimes, module X will have its source package called python-X or just X.
>
> If we hav
On Thursday, July 11, 2013 12:30:54 AM Stuart Prescott wrote:
> Thomas Goirand wrote:
> > On 07/08/2013 10:10 PM, Scott Kitterman wrote:
> >> There is no policy on this either way, so there's no "mistake".
> >
> > Well, the mistake is precisely t
On Saturday, July 06, 2013 10:22:22 PM Scott Kitterman wrote:
> On Wednesday, July 03, 2013 01:55:07 PM Scott Kitterman wrote:
> > On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote:
> > > On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> > > &
Jakub Wilk wrote:
>* Barry Warsaw , 2013-07-24, 12:38:
>>In any case, it's come up that PEP 394 recommends distros start
>>adopting shebang lines that state /usr/bin/python2 in their scripts,
>>and I don't think we do this yet. We should!
>
>We absolutely should not.
Definitely not. The ent
Barry Warsaw wrote:
>On Jul 24, 2013, at 01:32 PM, Scott Kitterman wrote:
>
>>Jakub Wilk wrote:
>>>* Barry Warsaw , 2013-07-24, 12:38:
>>>>In any case, it's come up that PEP 394 recommends distros start
>>>>adopting shebang lines that state /u
On Wednesday, July 24, 2013 07:09:26 PM Barry Warsaw wrote:
> Alright, I obviously haven't convinced anybody, so I'll drop it. We'll let
> the PEP 394 bug reports speak for themselves . But the responses I've
> read so far make me think I probably wasn't clear in what I am proposing.
> On Jul 25,
On Tuesday, July 30, 2013 09:37:21 Brian May wrote:
> > x: python-django-ajax-selects: incorrect-package-name python-ajax-select
>
> I don't know where it is getting the python-ajax-select name from.
>
> If I don't get any responses here, I will assume my package is fine.
Where is the package?
On Tuesday, July 30, 2013 11:19:58 Brian May wrote:
> On 30 July 2013 11:15, Scott Kitterman wrote:
> > Where is the package?
>
> The source is on subversion:
>
> svn+ssh://
> svn.debian.org/svn/python-modules/packages/django-ajax-selects/trunk
> http://anonscm.debia
On Tuesday, July 30, 2013 16:15:58 Brian May wrote:
> On 30 July 2013 15:52, Scott Kitterman wrote:
> > The package name is incorrect. Per the python policy, the binary name
> > should
> > be python-ajax-select. That's the module name.
>
> Really? I thought it w
python3.3 is the default python3. We're going straight to dropping python3.2
from supported python3 versions. binNMUs were already done for morse-
simulator,postgresql-9.1,yafaray,and znc after python3.3 became default.
These issues still remain:
> libguestfs - No longer FTBFS on amd64, but do
Stefano Rivera wrote:
>Hi Dmitrijs (2013.08.05_00:05:50_+0200)
>> pypy published a release with python3 support
>
>I'm not entirely sure how to handle pypy3 yet...
>pypy3 will be able to share /usr/lib/python3/dist-packages, which
>probably means single binary packages for both cpython3 and
On Friday, August 02, 2013 09:13:56 Scott Kitterman wrote:
> python3.3 is the default python3. We're going straight to dropping
> python3.2 from supported python3 versions. binNMUs were already done for
> morse- simulator,postgresql-9.1,yafaray,and znc after python3.3 became
&g
On Wednesday, August 21, 2013 21:25:41 Diane Trout wrote:
> Hi,
>
> I wanted to help maintain python-lightblue which was currently up for
> adoption. I also submitted python-htseq a little while ago through the
> debian- med team.
>
> My day job is as a python programmer/systems administrator at
Kerrick Staley wrote:
>Please install /usr/bin/python2 as part of the default Debian install.
>It
>still doesn't exist on 7.1, which prevents scripts with a shebang of
>#!/usr/bin/python2 from running.
>
>Note that the following matters (which have derailed previous threads
>on
>this topic) are
Kerrick Staley wrote:
>Thanks!
>
>The upstream recommendation (from PEP 394 [1]) is that, going forward,
>portable scripts *can't* assume python is python2, and *should* use
>python2.
>
>- Kerrick
>
>[1] http://www.python.org/dev/peps/pep-0394/
I'm very familiar with it.
Now we get to Arch is
2.7.
Scott K
>
>On Sat, Sep 14, 2013 at 9:25 AM, Scott Kitterman
>wrote:
>
>>
>>
>> Kerrick Staley wrote:
>> >Thanks!
>> >
>> >The upstream recommendation (from PEP 394 [1]) is that, going
>forward,
>> >portable scripts
Kerrick Staley wrote:
>Scott, I booted up a CentOS 6.4 VM, and the symlink is there (runs
>python2.6). I'd be interested to know if there are any other systems
>where
>it's unavailable though.
OK. I think that convinces me it's widely enough spread we ought to fix this
for Wheezy. I'll take i
On Sunday, September 15, 2013 14:34:27 Scott Kitterman wrote:
> Kerrick Staley wrote:
> >Scott, I booted up a CentOS 6.4 VM, and the symlink is there (runs
> >python2.6). I'd be interested to know if there are any other systems
> >where
> >it's unavailable th
On Wednesday, September 18, 2013 17:16:22 Ben Finney wrote:
> Howdy all,
>
> Over at the ‘python-dev’ forum, PEP 453 is being discussed. This affects
> Debian packaging of Python, and packages written for Python.
>
> See the discussion thread and take the opportunity to represent Debian
> https:/
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 03:22:19PM +0200, Piotr Ożarowski wrote:
>> [W. Martin Borgert, 2013-09-18]
>> > As a passionate pip hater I would go for a Conflicts,
>> > which finally would make pip uninstallable :~)
>> > Next steps: get rid of gem, npm, EPT, ...
>>
>> +1 (un
Paul Wise wrote:
>On Wed, Sep 18, 2013 at 4:33 PM, Scott Kitterman wrote:
>
>> P.S. I'm not nominating myself to be the diplomat that talks to
>upstream for what are probably obvious reasons.
>
>Too late, upstream folks (for eg Barry Warsaw) are on this list, are
>D
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 05:41:52PM +0200, Piotr Ożarowski wrote:
>> ok, I forgot to add ";)", but...
>
>Sure, but let's be more careful - I don't want people quoting "Debian
>Python" people telling people they're going to purge pip from the
>archive...
>
>It's all too of
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 10:57:30PM +0200, Tshepang Lekhonkhobe wrote:
>> On Wed, Sep 18, 2013 at 3:36 PM, Paul Tagliamonte
> wrote:
>> > 4) Python modules from dpkg are borderline useless for
>developers. We
>> > package modules so that apps can use them, not so t
On Monday, September 16, 2013 23:23:30 Kerrick Staley wrote:
> On Sun, Sep 15, 2013 at 11:34 AM, Scott Kitterman
wrote:
> > OK. I think that convinces me it's widely enough spread we ought to fix
> > this for Wheezy. I'll take it up with the release managers as it'
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 05:16:22PM +1000, Ben Finney wrote:
>> Howdy all,
>>
>> Over at the ‘python-dev’ forum, PEP 453 is being discussed. This
>affects
>> Debian packaging of Python, and packages written for Python.
>>
>> See the discussion thread and take the opport
On Friday, September 20, 2013 15:44:05 Thomas Kluyver wrote:
> On 20 September 2013 12:08, Paul Tagliamonte wrote:
> > Don't take this as me trashing on Python or Pythonistas. If you want to
> > talk
> > about this in person, I'm usually at PyCon. I'm also usually in the
> > packaging
> > BOF. Per
Ben Finney wrote:
>Dmitry Shachnev writes:
>
>> In your particular case, python3-coverage depends on 'python3 (<<
>> 3.4), python3 (>= 3.3)', so when it is installed /usr/bin/python3
>will
>> be always a link to python3.3, so the shebang doesn't matter here.
>But
>> in general, I recommend peop
On Saturday, October 12, 2013 11:26:28 Thomas Goirand wrote:
> On 10/12/2013 01:26 AM, Barry Warsaw wrote:
> > On Oct 11, 2013, at 07:23 PM, Julian Taylor wrote:
> >> It is better if one disables internet access of package builds
> >> completely.
> >> With pbuilder and iptables this is very easy, j
On Wednesday, October 30, 2013 09:57:36 Barry Warsaw wrote:
> On Oct 30, 2013, at 10:04 AM, Dmitry Shachnev wrote:
> >Not before python2.7 is removed from the archive. See previous
> >discussions on this ML, i.e. this thread:
> >http://lists.debian.org/debian-python/2013/07/msg00049.html.
>
> The
On Wednesday, January 08, 2014 23:22:40 Gudjon I. Gudjonsson wrote:
> Hi list
> I got a bug report regarding PyQwt (see below). Once again
> it segfaults and when I test PyQwt3d it segfaults as well.
>The problem is fixed by a new upload but my problem is that
> I cannot request a binNMU un
On Wednesday, March 05, 2014 18:28:56 Sandro Knauß wrote:
> Hello,
>
> I'm interested to join the team with my alioth account (hefee-guest). I want
> to package python-srs within this team. Scott K. has agreed to sponser me.
Sounds good. I"ve accepted your request.
Welcome,
Scott K
signature.
On Wednesday, March 19, 2014 17:40:51 Barry Warsaw wrote:
> Signed by ba...@warsaw.us.Show Details
> TL;DR: Let's re-enable the ensurepip module in Python 3.4, and possibly
>address some usability issues. We should descend en masse on Montreal
> and stage a revolt at Pycon. :)
>
> Python
On Tuesday, March 25, 2014 15:29:06 Barry Warsaw wrote:
> On Mar 25, 2014, at 03:19 PM, Donald Stufft wrote:
> >I assume once someone has installed pip with apt-get they’d still be able
> >to run pip install —upgrade pip if they wanted too?
>
> I would think they should be able to do that.
If I'v
On Sunday, March 30, 2014 17:01:05 Ben Finney wrote:
> Howdy all,
>
> I'm attempting to build a Python 3-only package, but ‘dh’ insists on
> trying to find some Python 2 versions.
>
> The ‘debian/control’ contains a “X-Python3-Versions” field, and does not
> contain any “X-Python-Versions” field.
On April 30, 2014 11:31:55 AM EDT, Luca Falavigna wrote:
>Hi,
>
>python-central is gone (\o/) and python-support usage is slowly
>decreasing in the archive:
>http://lintian.debian.org/tags/dh_pysupport-is-obsolete.html
>
>Do you think it would be the right time to prepare a mass bug filing
>asking
On April 30, 2014 1:15:42 PM EDT, Dimitri John Ledkov wrote:
>On 30 April 2014 18:01, Matthias Klose wrote:
>> Am 30.04.2014 17:31, schrieb Luca Falavigna:
>>> Hi,
>>>
>>> python-central is gone (\o/) and python-support usage is slowly
>>> decreasing in the archive:
>>> http://lintian.debian.org/
On Monday, May 05, 2014 17:20:09 Paul Tagliamonte wrote:
> On Mon, May 05, 2014 at 09:18:57PM +, Tianon Gravi wrote:
> > Hi! :)
> >
> > I'm part of the docker-maint team (which is listed in Uploaders on
> > python-docker), and I'm interested in joining DPMT to help Paul maintain
> > and update
On Wednesday, May 07, 2014 11:27:20 Barry Warsaw wrote:
> Should we also update Appendix B to promote --buildsystem=pybuild or at
> least reference it?
It's a reasonably safe bet that almost anything needs update.
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with
Based on discussions with the release team, I think we'll be able to do this
next week (assuming the sip-api transition that just started goes well).
blender will need an upload and python-astropy is broken and will remain
broken until upstream fixes it. Are there any other issues people know o
On Thursday, May 15, 2014 18:32:01 Barry Warsaw wrote:
> My thoughts...
>
> On May 16, 2014, at 12:07 AM, Matthias Klose wrote:
> > - should we add wheels everywhere? I don't think we should,
> >
> > but I'd like to state this somewhere, like in the python policy.
>
> Agreed, we should not add
-05-12 10:21:25 +
> +++ debian/python-policy.sgml 2014-05-16 15:23:30 +
> @@ -32,7 +32,11 @@
> Scott Kitterman
> sc...@kitterman.com
>
> - version 0.9.5
> +
> +Barry Warsaw
> +ba...@debian.org
> +
> +
On Friday, May 16, 2014 14:09:26 Barry Warsaw wrote:
> Second draft.
> -Barry
>
> === modified file 'debian/python-policy.sgml'
> --- debian/python-policy.sgml 2014-05-12 10:21:25 +
> +++ debian/python-policy.sgml 2014-05-16 18:08:52 +
> @@ -32,7 +32,1
On May 19, 2014 9:55:22 AM EDT, Barry Warsaw wrote:
>On May 19, 2014, at 12:19 PM, Piotr Ożarowski wrote:
...
>>* I don't think we should force maintainers to do changes in their
>> packages if it's not really needed,
>> (not to mention additional work for ftpmasters)
>
>The additional ftpmaster
On Tuesday, May 20, 2014 13:14:23 Barry Warsaw wrote:
> On May 20, 2014, at 11:38 AM, Barry Warsaw wrote:
> >+ compliant way. The set of packages providing wheels for this
> >+ purpose are (by source package name): chardet, distlib,
> >html5lib, + python-colorama, python
The release team gave the go ahead today to make 3.4 the default, so that's
done. There are a few binNMUs to do (See #746709 for details).
Is anyone aware of anything that would prevent dropping python3.3 from
supported versions as soon as this transition is done?
Scott K
signature.asc
Desc
On May 29, 2014 7:54:53 PM EDT, Barry Warsaw wrote:
>I'm looking again at updating tox to the latest upstream 1.7.1. Along
>the
>way, I'd like to make /usr/bin/tox a Python 3 script.
>
>This requires that virtualenv be importable, e.g. `$python -m
>virtualenv`. It
>is today in Python 2 since /us
On May 29, 2014 8:27:07 PM EDT, Donald Stufft wrote:
>
>On May 29, 2014, at 8:15 PM, Scott Kitterman
>wrote:
>
>> On May 29, 2014 7:54:53 PM EDT, Barry Warsaw
>wrote:
>>> I'm looking again at updating tox to the latest upstream 1.7.1.
>Along
>>&g
On June 2, 2014 3:06:15 PM MDT, Matt Grant wrote:
>Hi Torsten!
>
>I can get an NMU for PyParsing done as I am a DPMT member. Any
>Objections on the list?
>
>Regards,
>
>Matt Grant
>
>On Mon, 2014-06-02 at 21:28 +0200, Torsten Marek wrote:
>> I'm sorry but I'm not active in Debian any more. I'm no
This isn't necessarily fatal. See python-dnspython (provides the dns module)
and python-dns (provides the DNS module). Sine python-captcha is already
used, I'd recommend picking an alternate name for your package. Since python
module names are case sensitive, this thing can happen and we shou
python3.3 will be gone from Unstable as of the next dinstall.
Thanks for everyone that helped out.
Scott K
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/3135638.
On July 13, 2014 6:00:58 AM EDT, Thomas Goirand wrote:
>Hi,
>
>There's more and more packages in Sid which requires python-wheel. I
>was
>wondering if it was possible to do a backport of it. It seems very
>likely, because the setup.py is handling old stuff like Python prior
>2.7. Many backports wh
On July 14, 2014 1:35:51 AM EDT, Thomas Goirand wrote:
>On 07/13/2014 07:08 PM, Scott Kitterman wrote:
>> On July 13, 2014 6:00:58 AM EDT, Thomas Goirand
>wrote:
>>> Hi,
>>>
>>> There's more and more packages in Sid which requires python-wheel. I
>
Package: lintian
Version: 2.5.25
Severity: wishlist
For applications that use python-qt4, pyqtconfig has been the standard way to
access attributes about the PyQt4 installation. Upstream has decided to drop
this for alternate methodes. For now, we can continue to use the upstream
legacy configur
On Saturday, August 02, 2014 17:09:55 Scott Kitterman wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Both of the human maintainers/uploaders of gnupginterface are retired. See
> #698274 and #729385, leaving only the Debian Python Modules Team as an
> uploader. Th
On Tuesday, August 05, 2014 11:54:37 Ben Finney wrote:
> Vincent Cheng writes:
> > […] just don't pick a source package name that's already taken, and
> > pick one that is relevant to your package […]
>
> I further advise: Try to avoid names which are too broad (e.g.
> “coverage” for a Python-spe
On Sunday, August 03, 2014 22:01:00 Dmitry Shachnev wrote:
> On Sun, Aug 3, 2014 at 7:06 PM, Barry Warsaw wrote:
> > On Aug 02, 2014, at 06:23 PM, Scott Kitterman wrote:
> >>If someone on the team is interested in this package staying in Debian and
> >>willing to be
On Saturday, August 30, 2014 09:44:30 Barry Warsaw wrote:
> On Aug 30, 2014, at 11:19 AM, Simon McVittie wrote:
> >On 30/08/14 10:50, Cornelius Kölbel wrote:
> >> But now my originial program package is empty and does not contain the
> >> python code.
> >> It looks like only the .install scripts ar
On August 30, 2014 1:06:41 PM EDT, Barry Warsaw wrote:
>On Aug 30, 2014, at 12:57 PM, Scott Kitterman wrote:
>
>>I don't think that's the case for multiple binary packages.
>
>Hmm. An example is enum34, which has python-enum34, python3-enum34,
>and
>python-en
On Thursday, September 04, 2014 15:40:42 Barry Warsaw wrote:
> That gets you a source package, but the binary package FTBFS because one
> additional test cannot be run during the build process (there's a DEP-8 test
> for full coverage). Now though, you *must* commit or stash the d/changelog
> chan
On Thursday, September 04, 2014 16:05:53 Scott Kitterman wrote:
> On Thursday, September 04, 2014 15:40:42 Barry Warsaw wrote:
> > That gets you a source package, but the binary package FTBFS because one
> > additional test cannot be run during the build process (there's a DEP
On September 23, 2014 6:46:58 PM EDT, Charles Plessy wrote:
>Le Tue, Sep 23, 2014 at 10:29:10PM +0100, Sandro Tosi a écrit :
>> Hi all,
>> there's some people who's subscribed to the commit ml, so getting all
>> the changes done to our repos. Now, with the transition to git we are
>> getting this:
On October 9, 2014 5:36:02 AM EDT, Raphael Hertzog wrote:
>On Thu, 09 Oct 2014, W. Martin Borgert wrote:
>> On 2014-10-09 10:02, Raphael Hertzog wrote:
>> > I fixed the default configuration in setup-repository to limit to
>20
>> > commits per push as a maximum. And I also limited the size of
>ind
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote:
>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
>
>>Upstream commits are off topic.
>
>Agreed. There's no reason why we need notifications of upstream
>commits,
>though I don't know if it'
On Friday, October 10, 2014 00:22:42 Dimitri John Ledkov wrote:
> On 9 October 2014 20:57, Scott Kitterman wrote:
> > On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote:
> >>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
> >>>Upstream commits are off topic
On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote:
> On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
> > [..]
> > Presumably "one" is the one who set up the git repos. I, for another one,
> > would really appreciate it if someone would tak
On Friday, October 10, 2014 12:56:41 Charles Plessy wrote:
> Le Thu, Oct 09, 2014 at 11:41:47PM -0400, Scott Kitterman a écrit :
> > On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote:
> > > On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
> > >
On Friday, October 10, 2014 09:04:32 Barry Warsaw wrote:
> On Oct 10, 2014, at 12:16 AM, Tianon Gravi wrote:
> >At the BoF during DebConf, me and paultag discussed how we use exactly
> >this workflow for Docker stuff in Git, and we love it. We don't ever
> >worry about any kind of upstream commits
On October 12, 2014 2:49:47 AM EDT, Thomas Goirand wrote:
>On 10/10/2014 12:59 PM, Ben Finney wrote:
>> Scott Kitterman writes:
>>
>>> Changing the number of commits is solving the wrong problem. The
>>> problem that needs to be solved is including upstrea
On October 16, 2014 5:49:37 PM EDT, Per Andersson wrote:
>Hi!
>
>A while ago I uploaded python-pies to the archive, a dependency
>for frosted which is also in the archive.
>
>One of the binary packages python-pies2overrides, has an
>important bug; it overwrites configparser.py, which is also insta
the bug report, the diagnosis, and
+ the initial version of the patch
+- Note: Change is done inline to avoid adding a patch system during
+ freeze, so it does not appear in the DPMT svn
+
+ -- Scott Kitterman Sun, 23 Nov 2014 20:34:20 -0500
+
python-gnutls (2.0.1-1) unstable
201 - 300 of 781 matches
Mail list logo
