Re: PyGPU
Hi Dirk, > GPU programming from Python: > http://www.cs.lth.se/home/Calle_Lejdfors/pygpu/ > > Looks promising, but I still don't really speak Python. Anybody with more > skills and some free time interested in packaging this? I've filled an ITP last night, 446687 :) Just a question for d-python: I can't quite get the convention (if it exists) for names.. should I call the package pygpu, python-gpu, python-pygpu? Or call the package pygpu and Provides: ? Thanks in advance, Sandro -- Sandro Tosi (aka Morpheus, matrixhasu) My (little) site: http://matrixhasu.altervista.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PyGPU
> binary package should follow python-modulename schema. In your case: > python-pygpu (I saw `import pygpu` in example scripts) ok, got it > BTW: join DPMT[1] - we will try to help you maintain this package > > [1] http://python-modules.alioth.debian.org/python-modules-policy.html that would be interesting... so I can provide some "horsepower" to the team (even if I'm not a DD). Just let me play around with pygpu, I can even import it later, right? Cheers, -- Sandro Tosi (aka Morpheus, matrixhasu) My (little) site: http://matrixhasu.altervista.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: python-pyglew + join team
Hi All, after some time, I can at present the first piece of pygpu: python-pyglew. The package is available at: http://matrixhasu.altervista.org/debian/python-pyglew_0.1.2-1.dsc It's lintian/linda clean, and has been already checked by Bernd on #d-python, it just misses a sponsor to upload in in debian :) As soon as I'll find time, I'll inject (this and other python pkgs) into group's svn repository; in the meantime, I'd like to request to join the team; my alioth account is: morph-guest. -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: python-pyglew + join team
On 10/23/07, Sandro Tosi <[EMAIL PROTECTED]> wrote: > Hi All, [8<] > join the team; my alioth account is: morph-guest. Damn, I've forgot to "Thank you" at the end of previous email :) -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457473: ITP: extended_threading -- Extension of the python threading api
let's continue this on d-{devel,python}
On Dec 22, 2007 8:50 PM, Adeodato Simó <[EMAIL PROTECTED]> wrote:
> * Julien Cristau [Sat, 22 Dec 2007 18:41:37 +0100]:
>
> > Why not use the same name for both? I think it'd be clearer, and
> > has no drawbacks afaics.
>
> +1. I personally dislike so many python modules "suffering" from this.
and
> > Why not use the same name for both? I think it'd be clearer, and
> > has no drawbacks afaics.
>
> On Debian Python Modules Team requested me not to change source
> package name from upstream name if not strictly necessary. I'd call
> them both the same (it's clearer for me too) if was not for that
> advice.
I'd like to have source and binary package name the same (thuogh I
understand it's not needed to have source package renamed from
upstream one), but that would be linear (for me).
Thanks,
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Re: Request to join Python Modules Packaging Team
Hi Andrew, > I would like to request membership in the python modules packaging team. Nice to see you accepted my invitation ;) Another place where you can find help is IRC channel #debian-python on OFTC network. Hope to see your package soon ;) Kindly, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On team maintainership of DPMT (PAPT) packages
Hi all,
I'd like to report here my feelings about the current way to maintain
package in our repositories (DPMT and PAPT).
As of now, policy[1] states that:
Thus if you bring some packages into the team, you can keep your
name in the Maintainer field. You will receive bug reports and
handle your package as usual except that other team members may help
from time to time and/or take over when you're too busy.
If you put the team in the Maintainer field, the package will be
handled completely by the team and every member is invited to work
on any outstanding issue.
I personally feel this is not the way a team should work. If I inject
a package in the team, I think the team should be the maintainer, and
every people that do "important" work on the package can add
{him,her}self to Uploaders.
If you're in the Uploaders fields, the package will appear in personal
DDPO page too, so bugs can be noticed there (I hope this should reduce
oppositions about bugs notification).
The things I'd like to change, inspired from perl group policy [2]
(don't kill me for this ;), are the following:
* everyone that inject a package in the team repository have to set
Maintaner to the team (adding {him,her}self to Uploaders)
* everyone interested in actively taking part to team packages
mainteinership, must subscribe to alioth mailing list[3], where bug
reports and other messages about packages arrive
Maybe this way, would allow more people with "spot spare time" (I
mean, some hours in random situation, not every day) to collaborate,
attracting eventually new guys to the team.
I know I'm in the team since few months, and not being a DD hides me
from different kind of problems and point-of-views, but those are my
feelings, so please come join and discuss about this and every other
problems currently affecting the team.
Thanks a lot for your attention,
Sandro
[1] http://python-modules.alioth.debian.org/python-modules-policy.html
[2] http://pkg-perl.alioth.debian.org/policy.html
[3] http://python-modules.alioth.debian.org/
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Proposed new package, bugs-everywhere_0.0.193-1.1
Hi Ben, > feedback on my packaging efforts before seeking a sponsor, as I'm > still rather green at packaging Python applications. > > (I'm also seeking Alioth hosting for the project, but encountering > technical difficulties unrelated to the package.) If this is as python app (and you'd like to follow this path) the repository it's already on Alioth, and it's called PAPT[1] ;) Regards, Sandro [1] Python Applications Packaging Team, http://wiki.debian.org/Teams/PythonAppsPackagingTeam -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Python 2.5 specific bug
On Wed, May 14, 2008 at 12:35 AM, Josselin Mouette <[EMAIL PROTECTED]> wrote: > Le mercredi 14 mai 2008 à 00:32 +0200, Josselin Mouette a écrit : > > > Le mardi 13 mai 2008 à 16:35 +0100, Sam Morris a écrit : > > > > The bug can be reproduced with python 2.5 but only on Debian systems--on > > > an Ubuntu 8.04 system the code does not throw an error. Please try the > > > test case attached to the bug and let me know if you see it too. > > > > The pygame code looks buggy to me. len should be a size_t, not an int. > > Which is why it is failing on your amd64 system. > > It will be no surprise to anyone that the patch in Ubuntu [0] that > prevents this from happening was not forwarded to Debian. > > [0] http://patches.ubuntu.com/p/pygame/extracted/01_stack_overwrite.dpatch well, the package is hardly maintained now days; I've talked on IRC with Sam and it seems interested in pygame. I've suggested to contact both actual maintainer and co-maint to please orphan it if they are no more interested / have no more time, if 7/10 days will pass with no reply, go ask the QA team for what to do. If we can get an O: for it, we can inject in the DPMT repository, and start maintaining it in the team (I volunteer to comaint, and do the previous steps if Sam prefers me to do). Cheers, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Co-maintenance of pygpu
Hi all, I'm searching for a co-maintainer for pygpu: it's a rather interesting software to use GPU to do elaborations. Sadly, my graphic card + drivers does not allow me to test directly the code, so I'm looking for someone interested in the tool and willing to help me in such a way. The package is already in DPMT repo. I hope to find someone in the team, if after sometime no-one steps out, I'll expand the search to d-devel (there was some interest in the tool once the ITP was filed). Thanks in advance, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Co-maintenance of pygpu
On Tue, Jul 1, 2008 at 13:57, Sandro Tosi <[EMAIL PROTECTED]> wrote: > Hi all, > I'm searching for a co-maintainer for pygpu: it's a rather interesting > software to use GPU to do elaborations. Sadly, my graphic card + > drivers does not allow me to test directly the code, so I'm looking > for someone interested in the tool and willing to help me in such a > way. The package is already in DPMT repo. Sorry for the late reply: Jan kindly accepted to co-maintain this package and it's already been uploaded (thanks Piotr!) and lies in NEW. Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Best practice for test(s) directories?
Hi Kibi! On Mon, Jul 14, 2008 at 20:13, Cyril Brulebois <[EMAIL PROTECTED]> wrote: > Hi folks, > > I'm wondering whether there's a preferred place where to drop the > test(s) directory. I don't really know whether to choose >/usr/share/python-support/$package/test(s) > or >/usr/share/$package/test(s). > > Since it isn't really needed for the module to correctly work, I'd be > tempted to keep it out of python-support's paths, and to keep it under > /usr/share/$package instead, but what do you think? Well, since tests are something not needed for the module to work and they provide a sort of documentation of the module itself, I usually install them as examples under /usr/share/doc/$pkg/examples (as suggested by Piotr and/or Bernd, IIRC). Just my 2 cc :) Cheers, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: reportbug-ng (closes RC #496544)
On Tue, Aug 26, 2008 at 23:04, Nelson A. de Oliveira <[EMAIL PROTECTED]> wrote: > On Tue, 26 Aug 2008 21:41:09 +0100 > Serafeim Zanikolas <[EMAIL PROTECTED]> wrote: > >> I need sponsorship for a NMU that closes RC bug #496544 of the native >> package reportbug-ng. Do I have to ask for a release freeze, or would >> that be the sponsor? > > Shouldn't you give more time for the maintainer? (since there is only 1 > day that the bug is open) >From [1][2]: "we still have a 0-day NMU policy in effect" so it's a valid NMU (as long as he find a sponsor in time :) ), even if I agree that more time would be nice (but upload to deferred queues could be a solution). Cheers, Sandro [1] http://lists.debian.org/debian-devel-announce/2008/07/msg5.html [2] http://lists.debian.org/debian-devel-announce/2008/07/msg7.html -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Django 1.0 - Possibility of a freeze exception?
Hi David, I'm sorry, but I don't use django, but... On Wed, Aug 27, 2008 at 15:34, David Spreen <[EMAIL PROTECTED]> wrote: > Let me know what you think and how to best approach the release managers > with this. ...I think that you have to simply explain to release team the situation, in the more polite way possible (they are really stressed these days) strongly motivating your request for 1.0 for Lenny. Try to do it asap, just to avoid rushing to have a package ready, ask RT and have a "no" as reply. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Typo in python-matplotlib
Hello Tiziano,
On Mon, Sep 8, 2008 at 12:07, Tiziano Zito <[EMAIL PROTECTED]> wrote:
> Hi, in the package python-matplotlib I've just hit a typo in
> /usr/share/pyshared/matplotlib/axes3d.py:
>
> raise NotImplmentedError('axes3d is not supported in matplotlib-0.98.
> You may want to try the 0.91.x maintenance branch')
>
> should read "NotImplementedError" instead of "NotImplmentedError".
> To reproduce just try:
>
>>>> from matplotlib import axes3d
> Traceback (most recent call last):
> File "", line 1, in
> File "/usr/lib/python2.5/site-packages/matplotlib/axes3d.py", line
> 1, in
>raise NotImplmentedError('axes3d is not supported in
> matplotlib-0.98. You may want to try the 0.91.x maintenance branch')
> NameError: name 'NotImplmentedError' is not defined
>>>>
Thanks for the notice.
> not such a big deal, the import should fail with NotImplementedError
> instead of NameError. How is the policy for reporting such bugs
> upstream? Should I simply go and report, or is there an official
> "spokesman" of the DPMT?
Well, at your choice: you can report the bug on Debian BTS and let me
forward it or directly open the bug upstream (there are chances that
someone already reported it, either on their mailing list or BTS).
Kindly,
Sandro
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: drobo-utils
Hi Chris, On Sat, Oct 25, 2008 at 19:42, Chris AtLee <[EMAIL PROTECTED]> wrote: > Hi all, > > I am looking for a sponsor for my package "drobo-utils". I'll give it a look at the package, taking the code from PAPT svn repo. Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: drobo-utils
On Sat, Oct 25, 2008 at 20:44, Sandro Tosi <[EMAIL PROTECTED]> wrote:
> Hi Chris,
>
> On Sat, Oct 25, 2008 at 19:42, Chris AtLee <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I am looking for a sponsor for my package "drobo-utils".
>
> I'll give it a look at the package, taking the code from PAPT svn repo.
[EMAIL PROTECTED]:~/deb/python-apps/drobo-utils$ uscan --report
Processing watchfile line for package drobo-utils...
Newest version on remote site is 0.3.0-1, local version is 0.3.2-1
drobo-utils: remote site does not even have current version
mh, not a good start ;) Works with this line:
http://sf.net/drobo-utils/drobo-utils_(.+)\.tar\.gz
Please, prod the upstream author to remove the debian/ dir from the
upstream tarball (if he wants, can join PAPT and maintain that part in
our repo) and to name the dir in the tarball with the classic
- instead of "trunk".
What about merge the 2 entries in debian/changelog? At the end, this
will be the first revision uploaded ;)
Is Peter really the maintainer of this package? I just don't want you
to confuse this field with upstream author: the Maintainer field
contains the person primarly responsable for the *Debian* package, not
the upstream part of the code. Given that all the commits was done by
your user and that "This package was debianized by Chris AtLee", I
think that this field has to contain either your name or the team (at
your choice). Oh, please note that I'm fine with Peter being there,
but I just want to be sure you have clear its meaning. :)
What about adding Vcs-{Browser,Svn} and Homepage fields?
Could you please insert the GPLv3 boilerplate in debian/copyright
file? It's enought the "usual" stuff "This program is free software:
...".
What is this "The Debian packaging is (C) 2008, informavore
<[EMAIL PROTECTED]>"? Who is the copyright holder for the
packaging (so debian/ dir in PAPT repo I'll upload) (connected to
above)? "informavore" is for sure wrong ;) Moreover, it's better to
state the same license for both upstream and packaging code, so both
GPLv3 (not clear for the packaging part).
It might be better to refer to GPL-3 file, not to the generic GPL link.
You can merge the "rm -f" and dh_clean commands in clean target (they
do the same job).
./DroboDMP.c needs better copyright info
what about writing the two manpages (even if minimal) missing (and
submit them upstream)?
Given that python-qt4 is defined as "essential" in upstream
README.txt, maybe it would be better to have in Depends not
Recommends?
Just wondering, is the Depends on libsgutils1 really needed? I would
expected misc:Depends to introduce it if NEEDED by libs, but that's
not the case, and even a fast inspectoin of .so seems to confirm it:
$ objdump -x lib.linux-i686-2.5/DroboDMP.so | grep NEEDED
NEEDED libpthread.so.0
NEEDED libc.so.6
Both descriptions need a little more attention: reading the
description, I really can't understand what the package does :S For
example you need to clarify what drobos are, what kind of dashboard
is, etc etc (something to give an idea of what the package contains to
guys who know nothing about it (like me)).
I think it's enough for a first check ;) Feel free to contact me in
case of clarification ([EMAIL PROTECTED] for a fast reply) and commit your
changes into PAPT repo (I'd prefer using the same revision, -1), then
get back to me again for another check.
Thanks for your contribution (so far and futurable),
Sandro
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Let's switch to viewsvn for Vcs-Browser?
Hi all, following up what once POX suggested on irc, I'd like to switch from wsvn to viewsvn (compare the difference yourself at [1] and [2]) for Vcs-Browser field. I already checked-out the whole packages/ dir from both svn repos (so that the changes thru all the repo can be done in a single commit instead of polluting with commit for each package) and I got the script I used to uniform Vcs-* fields I can modify to do this conversion (so basically I'm volunteering :) ). If no-one will complain, let's say, in a couple of days, I'll run the script. Cheers, Sandro [1] http://svn.debian.org/wsvn/python-modules/packages/matplotlib/trunk/?op=log [2] http://svn.debian.org/viewsvn/python-modules/packages/matplotlib/trunk/ -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Let's switch to viewsvn for Vcs-Browser?
Hi dato :) On Sat, Nov 1, 2008 at 18:17, Adeodato Simó <[EMAIL PROTECTED]> wrote: > * Sandro Tosi [Sat, 01 Nov 2008 18:07:11 +0100]: > >> Hi all, >> following up what once POX suggested on irc, I'd like to switch from >> wsvn to viewsvn (compare the difference yourself at [1] and [2]) for >> Vcs-Browser field. > >> I already checked-out the whole packages/ dir from both svn repos (so >> that the changes thru all the repo can be done in a single commit >> instead of polluting with commit for each package) and I got the >> script I used to uniform Vcs-* fields I can modify to do this >> conversion (so basically I'm volunteering :) ). > >> If no-one will complain, let's say, in a couple of days, I'll run the script. > > I'm not a member of the team, but I'd like to say one thing: please note > that both interfaces suck in their own ways: ViewSvn makes easier to > navigate through the tree, and feels generally prettier [to me], but it > doesn't seem to have a view where history of the repository is shown: > how do you find out the latest changes to the package? wsvn gets that > right, presenting that as the first thing (which is usually what you're > interested in, anyway). Relatedly to this, ViewSvn does not support > (AFAIK/CS) "give me the diff for revision 123". Well, maybe you won't have the complete diff between 2 revisions, but you can have a pretty nice one for one file, for example[3] [3] http://svn.debian.org/viewsvn/python-modules/packages/matplotlib/trunk/debian/changelog?rev=6818&view=log where you can select a particular revision, and diff any other revision from that selected (or from the previous). What I want from a browser interface is to let me navigate on the files tree easily (and wsvn is not strong in this :) while viewsvn is) and let me do some basic operations: to exploit the full power of svn I'd use the cli. Thanks for the critics :) -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Let's switch to viewsvn for Vcs-Browser?
On Sat, Nov 1, 2008 at 18:23, Emilio Pozuelo Monfort <[EMAIL PROTECTED]> wrote: > Sandro Tosi wrote: >> Hi all, >> following up what once POX suggested on irc, I'd like to switch from >> wsvn to viewsvn (compare the difference yourself at [1] and [2]) for >> Vcs-Browser field. > > Please! Also, would it be OK to do that in PAPT too? I'm not sure if it would > be > in those packages PAPT is not the maintainer... I'm talking about both DPMT and PAPT. Regarding the team not maint, we seem to agree to the rule where: - if team is maint, do the changes and upload (if needed) - if not, do the changes and ask the current maint for a check and to upload (if needed). Since what I want to do is a repository wide change with no need for an upload (is really too small change), I feel I'm not violating that rule. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Request for a package: Pivy
Hi Teemu, what about filing a proper RFP (X-Debbugs-CCing us), so that maybe even other can take your request up :) Kindly, Sandro On Wed, Oct 29, 2008 at 18:44, Teemu Ikonen <[EMAIL PROTECTED]> wrote: > Dear all, > > I'm slowly working on getting FreeCAD > (http://juergen-riegel.net/FreeCAD/Docu/index.php?title=Main_Page ) to > a releasable state (see > http://git.debian.org/?p=debian-science/packages/freecad.git;a=summary > ). FreeCAD depends on a whole bunch of libraries and modules, most of > which are fortunately in Debian already. One missing module is Pivy > (http://pivy.coin3d.org/ ), a python binding to the Coin 3D graphics > library. Currently FreeCAD upstream ships it on their tarball, but > this of course is ugly. > > Pivy uses distutils and builds on my lenny / sid system out of the > box. Could someone please package it? I have no experience in > packaging python stuff and this package looks like it could be added > to the Debian Python Modules SVN without too much manual packaging. > > Teemu > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Let's switch to viewsvn for Vcs-Browser?
Hi all,
On Sat, Nov 1, 2008 at 18:07, Sandro Tosi <[EMAIL PROTECTED]> wrote:
> Hi all,
> following up what once POX suggested on irc, I'd like to switch from
> wsvn to viewsvn (compare the difference yourself at [1] and [2]) for
> Vcs-Browser field.
>
> I already checked-out the whole packages/ dir from both svn repos (so
> that the changes thru all the repo can be done in a single commit
> instead of polluting with commit for each package) and I got the
> script I used to uniform Vcs-* fields I can modify to do this
> conversion (so basically I'm volunteering :) ).
>
> If no-one will complain, let's say, in a couple of days, I'll run the script.
Done! Now DPMT and PAPT packages that already have Vcs-Browser field,
now have it using viewsvn. I did the changes with a script, so I hope
I didn't create too much artifacts in the changelog (but they are so
trivial, easily removable when the maint will approach to upload the
package).
I've not done yet: I'd like to add Vcs-{Svn,Browser} fields to those
packages currently lacking 'em, but that's a job for another day ;)
Cheers,
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Python-modules-team] ITP: python-pivy -- Coin binding for Python
Hi Teemu, On Mon, Nov 10, 2008 at 23:21, Teemu Ikonen <[EMAIL PROTECTED]> wrote: > retitle 504617 ITP: python-pivy -- Coin binding for Python > thanks > > I've made preliminary packaging of Pivy, it's now at right on time: I was considering start working on it, since it's needed for another package of yours :) > http://git.debian.org/?p=collab-maint/pivy.git but I really hope it > could be integrated with the Python modules team packages to the SVN > repository. Request to join the team at [1]. then follow this doc[2] to inject the code into out repo (basically it's a "svn-inject -o .dsc"). Then you can ask back here, or on IRC at [EMAIL PROTECTED] In the meantime, I'm going to give a look to the package you prepared. [1] http://alioth.debian.org/projects/python-modules/ [2] http://python-modules.alioth.debian.org/python-modules-policy.html Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Python-modules-team] ITP: python-pivy -- Coin binding for Python
Hi Teemu, On Wed, Nov 12, 2008 at 16:59, Teemu Ikonen <[EMAIL PROTECTED]> wrote: > Thanks for checking the package. I would be happy to work on the > package until it is of release quality, but committing to long term > maintenance is something I'm a bit hesitant to do, due to lack of time > and experience in Python and SVN-based packaging. > > Pivy seems to be a stable package in a sense that it hasn't had a > release in a while. This on one hand means that there is probably not > going to be much work in packaging new upstream versions. On the other > hand this might mean that upstream is dead and someone in Debian has > to deal with the bitrot and possible security issues. Still I would > really appreciate if someone more involved with Python modules than me > could inject this package to the SVN and take care of the (extremely > simple) packaging if it needs to be changed due to new policies etc. Personally, I don't even know what this module does :) so I can't maintain it, and in debian we usually refuse to have only "non-human" maintainers (without any "real" ones). What I can offer you is "mentoring" in svn management and python modules packaging, both now and for futures requests, but I won't step in as maintainer :) Kindly, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: python-uniconvertor breaks help("modules") in python
Hello Andreas,
On Tue, Nov 25, 2008 at 01:03, Andreas Wenning <[EMAIL PROTECTED]> wrote:
> I have a bug[1] against my package[2] that it breaks running help("modules")
> in python when the package is installed (more precisely, it kills the python
> interpreter when trying to import the package).
>
> It looks to qualify for having a severity grave[3] as it "makes unrelated
> software on the system break". Can anyone with more insight into the policies
> advice me if I should consider doing something special for lenny?
One first try could be to ask release team (mailing
[EMAIL PROTECTED]) to accept the latest version in sid into lenny,
but the chances are high the won't approve it.
So, the best approach could be to create a patch from the latest
package against the version in lenny, and then prepare an upload
targetted to testing-proposed-updates.
Regards,
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Would like to add a new package and looking for support.
Hello Nima, On Wed, Dec 17, 2008 at 13:40, Nima Talebi wrote: > Hi Everybody. > I've taken the latest dmidecode (http://www.nongnu.org/dmidecode/) and > recompiled it as a python module, which I'd now like to introduce into the > unstable debian release. > The web page for this project is > at http://projects.autonomy.net.au/dmidecode, and I'm almost done with the > debian package itself, I wanted to know if there is anyone here who is > interested enough to look at my package and tell me if I've done the right > thing. It should be in the code repository detailed on the site soon. Look at some hints on http://wiki.debian.org/Teams/PythonModulesTeam (basically, you need to "request to join" in the alioth project page, then "svn-inject -o .dsc" into our repository, then you can follow up this email requesting for sponsorship. Another fast way to interact with us is using IRC: #debian-python @ irc.debian.org Regards, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: numpy 1.2.1, switching to git?
> P.S. bzed, POX, isn't it time to move our packaging to git? I'm none of them, but I'll speak anyway :) Buxy almost did my point, I'd like to express me a bit. To do a change into something different we need a reason: what's the reason for moving from svn to git? is it because it's cool? (I hope not ;) ) is it because it has some features missing in svn? maybe, but which ones? something else? It's DVCS, ok, but how many time did you have to diff or log a package offline? How many time did you have to leave uncommitted changes locally while waiting to connect to network for "svn up && svn co"? it would be the same for git or svn: you need network to upload a package, and you need network to update/commit/whatever action on the repo. Having a centralized place, to concentrate our work it's a plus, not a minus for us (IMO): why would you distribute it? Moreover, I do not want upstream code in the VCS we use for debianization (I did this error for personal managed pacakges and I do not want to do it again). Let upsteam tracks his own source code like he prefers, we do not need re-tracking it in git/svn/XXX, what we want to do is to keep track of our work, what's in debian/ dir *only*. If, for packaging reason, you need to "touch" the upstream code, then checkout the upstream code in whatever place you prefer, using the same VCS upstream uses, and submit them patches, check differences or what-so-ever, but that has nothing to do with packaging that tool. > So that I > can just commit such patches in a branch and also so that we don't > have to mess with the orig.tar.gz, svn-uscan and other things apt-get source --tar-only uscan --verbose --repack --rename --destdir=/where/you/keep/tarballs I don't see too difficult: 1 command (whatever you prefer) comparing with the many of "vi + dch + build + lintian" loops you do to prepare a package. > everything will be in one git repo, Given my slow line, I cannot afford the pain to download every packages source code + debianization; now, to have a full checkout of dpmt/papt repositories, I need to launch the commands during the night. Additionally, doing repositories wide updates will become more painful, so I have to refrain from "work on every package" but just on mine. Moreover, I don't see any reason to have the fullsource code in the same VCS of debian/ for the myriad of damn-simple packages we have. Another question: do you know of any other big team (we have ~300 pkgs in both papt/dpmt so I see us as a big team) that is on git? I know none :) I'd take the example of pkg-perl: they maintain ~1000 pkgs, and they are still on svn (but I don't know if the plan to move to git anytime soon, but they use for some "corner cases" like perl apps). So, any team experience we can learn from? are the tools ready to allow a team (not just single/small group of maintainers) to work on a plethora of packages in a feasible way? > so users can just download, hit > one command and they have a working package (as opposed to the current > scheme, were they need to download svn, then setup some tarball > directories, then setup svn-uscan, then execute it and only then they > can actually build the package, so it's very annoying for casual users > to setup the environment to contribute to the packaging) What users are you talking about? those that wants to rebuild a package are experienced used, so they can apt-get source and then debcheckout it or whatever order/way they prefer. A normal used is "client" of the .deb package installed via apt-get/aptitude/synaptic/dpkg/ I recognize that some particularly complex packages may need an ad-hoc management, but the vast majority of the packages in the team do not need it; so let's "split" those packages in a separate DVCS repository (maybe still called papt/dpmt) and keep the other where they are. Concluding, if you ever switch to a DVCS, I'd vote for git, but given the situation, I don't see a strong need to move away from svn. Cheers, Sandro PS: I may have written it tough (and the "you" is a generic one), but read it as an open discussion email with ":)" in whatever place you like :) -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: numpy 1.2.1, switching to git?
On Wed, Dec 24, 2008 at 00:48, Ondrej Certik wrote: > thanks for the points, I reacted to some. so please accept my reply :) > On Tue, Dec 23, 2008 at 5:02 PM, Sandro Tosi wrote: >>> P.S. bzed, POX, isn't it time to move our packaging to git? >> >> I'm none of them, but I'll speak anyway :) Buxy almost did my point, >> I'd like to express me a bit. >> >> To do a change into something different we need a reason: what's the >> reason for moving from svn to git? is it because it's cool? (I hope >> not ;) ) is it because it has some features missing in svn? maybe, but >> which ones? something else? > > Yes, distributed version control system has many features that are > missing in svn (=that I am missing in svn), mainly that I can easily > fiddle with different approaches and branches locally, that I can > easily upload my own branch somewhere for someone else to try. With > svn, I need to append a patch to our BTS/mailinglist. have you ever tried git-svn to work over your packages actually in the team? >> It's DVCS, ok, but how many time did you have to diff or log a package >> offline? How many time did you have to leave uncommitted changes > > Actually, all the time. Maybe it's only how I work, but I often look > at the history to learn what are the latest changes to see where the > package is heading to, what is the style of maintaining, etc. Or > simply to remind myself what I did on this package in the past. Really? for a bunch of file under debian/ you need all of this? or are you talking about upstream code? I think we need to separate the 2 arguments, because the *are* separated: we are packagers, we have to keep track of our team's things; your involvement in upstream development is commendable, but this is something "other" that debian packaging, so it has to be. >> Moreover, I do not want upstream code in the VCS we use for >> debianization (I did this error for personal managed pacakges and I do >> not want to do it again). Let upsteam tracks his own source code like >> he prefers, we do not need re-tracking it in git/svn/XXX, what we want >> to do is to keep track of our work, what's in debian/ dir *only*. > > As I understand, the upstream code in the repo is useful only so that > one doesn't have to fiddle with orig.tar.gz. the problem is that I don't see what is the "problem of orig.tar.gz": you have to have one to upload the package, it's compressed (so you reduce space occupation), if you're good/lucky (no repackage or so) it's the same "bit-by-bit" the upstream released (And that assure that nothing weird is happening). > However, sometimes the orig.tar.gz cannot be obtained with svn-uscan > --- let's say if you are repackaging upstream, or simply if you are > packaging a different version than svn-uscan downloads. well, either you're creating a new revision of an already existing package (so apt-get source --tar-only would do) or you should stick to the lastest released tarball, ain't you? There should be strong reason to not package the latest version but one between the latest and the one in the archive, that could he handled as expection: they are not the regular way to do, so we cannot take them as examples. > One example > being the abinit package, where svn-uscan is offering me the highest > released version number, however the production version (that should > be packaged) is not the highest version available. this seems to be a very corner case >> I don't see too difficult: 1 command (whatever you prefer) comparing >> with the many of "vi + dch + build + lintian" loops you do to >> prepare a package. >> >>> everything will be in one git repo, >> >> Given my slow line, I cannot afford the pain to download every >> packages source code + debianization; now, to have a full checkout of >> dpmt/papt repositories, I need to launch the commands during the >> night. Additionally, doing repositories wide updates will become more >> painful, so I have to refrain from "work on every package" but just on >> mine. > > That's a good argument and I don't know the answer to it. But are you > sure it would be that much bigger? Ondrej, you're a science man :) are you just kidding here? :D Of course it's bigger. A lot bigger. Given you have the whole repository locally, you have the HEAD + all other modifications done in the past, for both the upstream code and the debianization. It's like downloading all the uploaded version of the package in the archive compared with only the latest one. Let's take the example of DPMT: the dimension on the svn repo on al
Re: numpy 1.2.1, switching to git?
On Thu, Dec 25, 2008 at 15:54, Ondrej Certik wrote:
...
Last reply on this thread, just to recap what Ondrej and me discussed
on irc this evening.
I didn't realize I ain't made clear what's my network situation: I'm
still at 56k, so many of the think you broadband users consider
normal, trivial, or chip, for me they're not. I have to minimize the
stuff I download at home and maximize the effort, and svn
(+downloading the tarball at work, if they are big) allows me to
achieve this balance.
But even if I had an adsl or so, I would say that that git is not the
right choice for our team (but I would have made a lot less problems
migrating to it). I think that, being things are they are now, svn is
the right choice and keep being. What we really need is to migrate a
svn layout-2 repository (one composed by
{trunk,tags,branches,...}/package).
Anyhow, to be short: I count as 1, and we are in democracy; whatever
the team will come up, I'll stick to it eventually changing/reducing
the way I contribute to it.
Cheers and Happy Holidays,
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-pytc
On Fri, Dec 26, 2008 at 22:12, Piotr Ożarowski wrote: > I cannot build it as I have currently access to i386 arch. only > (and libtokyocabinet-dev is available for amd64 only), > > Please ping me (in private) when libtokyocabinet will be available for > i386 or next week (I will be back home then)... unless someone else will > pick it up in the meantime :-) Built on amd64 and it builds fine, even package contents it's ok; my only concern is about depending on python-all-dbg for -dbg package. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
Re: RFS: python-pytc
On Fri, Dec 26, 2008 at 22:12, Piotr Ożarowski wrote: > I cannot build it as I have currently access to i386 arch. only > (and libtokyocabinet-dev is available for amd64 only), > > Please ping me (in private) when libtokyocabinet will be available for > i386 or next week (I will be back home then)... unless someone else will > pick it up in the meantime :-) Uploaded, fixing the copyright year (it's 2007 in the source code, not 2008) and adding README.source, a "should" in policy 3.8.0 for packages with patch system. Thanks for your contribution to Debian, Vernon, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
Re: Bug#509697: Python 2.5, ctypes, and binutils
Hi all, reporting here what discussed with Adeodato on irc: On Fri, Dec 26, 2008 at 17:04, Adeodato Simó wrote: > Regarding #509697 (python 2.5 providing ctypes, and ctypes using > objdump), I don't think it's reasonable to make python2.5 depend on > binutils, just for the purpose of one of the modules in the standard > library. One option would be to add binutils to Recommends or Suggest, > but that does not ensure packages that Depend: python-ctypes will work. > > Maybe "python" should stop Providing: python-ctypes, and python-ctypes > should depend on "python (>= 2.5) | python2.4" instead of just > "python2.4" (plus the recently added a dependency on binutils). This way > binutils will get pulled only when a package that depends on > python-ctypes is installed. (This does not solve, however, packages that > are being smart and are depending on "python (>= 2.5) | python-ctypes". > But maybe those packages should stop doing that.) > > If this is the way to go, then for squeeze it means that, if the ctypes > source package is to disappear, it should be created as a dummy package > (from python-defaults instead?), if only to contain the binutils > depends/recommends. Of course, upload again ctypes to update the depends it's pretty easy; what it's a little bit more "critical" are the "smarts" rdepends that currently Deps on "python (>= 2.5) | python-ctypes"; those are: $ grep-available -FDepends,Recommends,Suggests "python-ctypes | python (>= 2.5)" -o -FDepends,Recommends,Suggests "python (>= 2.5) | python-ctypes" -sPackage Package: python-musicbrainz2 Package: telepathy-butterfly Package: python-elisa Package: python-utidylib Package: python-msn Package: python-opengl Package: python-pyglet Now, even since they're not that many, and nmus (if the maints won't react in a timely fashion) could be done, my fear (partially shared with dato) if this is the right time for this "mini"-migration, due to the hard freeze is coming ReallySoonNow. I'd like to hear from you what's you're thinking. With the occasion, I'd like to wish a Happy New Year to all of you, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#509697: Python 2.5, ctypes, and binutils
On Wed, Dec 31, 2008 at 14:58, Sandro Tosi wrote: > $ grep-available -FDepends,Recommends,Suggests "python-ctypes | python > (>= 2.5)" -o -FDepends,Recommends,Suggests "python (>= 2.5) | > python-ctypes" -sPackage > Package: python-musicbrainz2 > Package: telepathy-butterfly > Package: python-elisa > Package: python-utidylib > Package: python-msn > Package: python-opengl > Package: python-pyglet better command, to catch even uber-smart depends: $ grep-available -FDepends,Recommends,Suggests "python-ctypes | python (>= 2.5)" -o -FDepends,Recommends,Suggests "python (>= 2.5) | python-ctypes" -o -FDepends,Recommends,Suggests "python2.5 | python-ctypes" -o -FDepends,Recommends,Suggests "python-ctypes | python2.5" -sPackage Package: python-coherence Package: python-musicbrainz2 Package: telepathy-butterfly Package: python-elisa Package: python-utidylib Package: python-msn Package: python-opengl Package: python-pyglet Now, since unstable ctypes upload was caught by libffi soname bump, and probably needs a tpu upload (please RT confirm this or if libffi5 will be migrated in lenny) it's an additional reason to decide about the situation explained above. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: please test the numpy package
On Thu, Feb 5, 2009 at 17:21, Ondrej Certik wrote: > 3) upload to experimental > 3a) keep the sphinx docs (sphinx is in experimental) I'd recommends this. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: please test the numpy package
On Fri, Feb 6, 2009 at 05:57, Ondrej Certik wrote: > On Thu, Feb 5, 2009 at 8:41 PM, Cyril Brulebois wrote: >> Ondrej Certik (05/02/2009): >>> Ok. But we are wasting people's time. I just got another email from a >>> Ubuntu user that he will rather consider compiling it for Ubuntu's PPA >>> himself, because he cannot use debian experimental. Of course. >>> >>> So he needs to invest his time in the package, I need to invest my >>> time in the package and the result is that it will not even be in >>> unstable anyway. :( >> >> (Following at home, so I might be missing something obvious.) >> >> What's the difference between unstable and experimental from that Ubuntu >> user point of view? If the use of a PPA is what I think it is, he has to >> fetch the source, be it from unstable or from experimental, throw it >> into the *builder of his choice, and upload that to the so-called PPA. >> >> How much time does he need to dget && *builder && dput? That's not what >> I call "invest time in the package". > > Ok, you are probably right. So I'll prepare an upload to experimental > and other people can just dget and pbuilder it. Is it easier then add an experimental source to /etc/apt/sources.list and apt-get -t experimental install python-numpy? What is the problem of using experimental? moreover, even because this is an experimental package itself, where by-hand operation are done downloading the tarball, and you request tests before uploading. Experimental is there to be used, and if users have a bad feeling using it, the same is to be there when using unstable too (like the names say). So, my suggestions is: upload to experimental and let your peers (blog posts, ml msgs, morse code ;) ) know where to find it and how to install it. >> And not breaking unstable at this point of the release cycle is >> something that matters, especially for late hotfixes that might be >> needed (and there still are such needs). > > Yes. I am unhappy that unstable gets frozen for such a long time, but > I understand that with the current setup (e.g. unstable, testing, ..), > there is probably no other way. As smarter people than me already explained, unstalbe is not frozen, but if you upload there "lower level" packages not targetted to Lenny, the "higher level" pkgs, that depend on those lowers, will start depends on them (via shlibdeps and so) and neither the highers will be able to transit to testing from unstable but needs t-p-u (that results in a lt less users testing the package for errors). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [Python-apps-team] RFS: cgmail (adopted)
On Mon, Feb 16, 2009 at 04:20, wrote: > My alioth id is xnox-guest and I would like to join and maintain this > package under Python > Apps Team in their SVN. (Although I don't know how to use SVN, git was first > and later I > learned bzr). you'd be welcome to so do :) You can find some documentation at [1] [2] [3], and feel free to ask d-pyt...@l.d.o for clarification or, if you hang around irc, we're on #debian-python at irc.debian.org. [1] http://wiki.debian.org/Teams/PythonAppsPackagingTeam [2] http://python-apps.alioth.debian.org/policy.html [3] http://wiki.debian.org/PAPT_Howto Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [Python-apps-team] RFS: cgmail (adopted)
Hi Dmitrijs,
I finally had some time to check at your package:
On Tue, Feb 17, 2009 at 00:04, Dmitrijs Ledkovs
wrote:
> 2009/2/16 Sandro Tosi :
>>
>> you'd be welcome to so do :) You can find some documentation at [1]
>> [2] [3], and feel free to ask d-pyt...@l.d.o for clarification or, if
>> you hang around irc, we're on #debian-python at irc.debian.org.
>>
>> [1] http://wiki.debian.org/Teams/PythonAppsPackagingTeam
>> [2] http://python-apps.alioth.debian.org/policy.html
>> [3] http://wiki.debian.org/PAPT_Howto
>>
>
> Thanks for the links. Inject didn't work so I did the manual injection. Looks
> good to me =D
>
> * Updated Maintainers field to PAPT
> * Set myself in Uploaders
> * Update VCS-* fields to point to svn
none of this changes has been documented in debian/changelog. Please
use this file to report every change you made from the previous
package to the current one.
debian/changelog:
- explain why you're removing lib/feedparser.py even here.
debian/control:
- the short description needs better improvement ("new shiny" is not
to be here, and 'A ' is wrong for short descr (cfr devref on it))
- why b-d-i on 'perl'? "grep -riw perl *" returns nothing on the top
level dir of upstream tarball
- it's an arch:all packages, can't some other packages be moved to b-d-i?
debian/NEWS:
- please use the same format of debian/changelog, dch --news is your
friend (too much indentation, to name one).
debian/rules:
- why "rm $(CURDIR)/debian/pycompat" ?
debian/watch:
- you can remove the empty bottom lines in this file
$ lintian -iIv --pedantic cgmail_0.5-1_amd64.changes
gives something to work on (v2.2.5).
Get back to me/us (on irc at #debian-python on irc.debian.org even
better) once a new package is ready (no need to upload to mentors, we
build from svn).
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516501: RFH: libapache2-mod-python -- Python-embedding module for Apache 2
Package: wnpp Severity: normal Hello, I'm hereby looking for a person to support DPMT[1] in maintaining libapache2-mod-python. I did the latest team uploads, but I don't use it, so I'm not the right person to maintain it. [1] http://wiki.debian.org/Teams/PythonModulesTeam The package has some bugs to triage, fix or else report upstream, other than that it's not in a bad shape, but having someone that can cope with the package in a good way is really needed. A strict requirement is that the package needs to remain in the DPMT repository, in reply we can offer sponsorship (I know the package so you can contact me for any support/question) and mentoring. Robert (the current co-maintainer) agreed to this RFH. The package description is: The mod_python module supports web applications written in Python. Because the parser is embedded in the server as an Apache module, it will run much faster than traditional CGI. . This package is built for the current Python version. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
On Thu, Feb 26, 2009 at 22:11, Ondrej Certik wrote: > Currently I think Sandro is the last major contributor for DPMT who > wants to stay in svn. No, what I said was: - I see no need to move to git as a team - I can't afford to download all the git repos for packages I want to modify once - My position must not stop the team to migrate to something else, if decided, but my contributions will be re-evaluated if it will happen Now, don't restart that discussion if nothing has changed. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Leaving DPMT?
On Sat, Feb 28, 2009 at 01:11, Ben Finney wrote: > I see this discussion focussing exclusively on Subversion versus Git; > I wish with this message to point out that not all DVCSen are > necessarily like Git. WTF?! As Ondrej said just some hours ago: On Fri, Feb 27, 2009 at 16:41, Ondrej Certik wrote: > We discussed that in the pust, just find the discussion on this list > before. I apologize for opening it again. Use the right thread to discuss this. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Developer workflow and DVCS (was: Leaving DPMT?)
On Sat, Feb 28, 2009 at 02:21, Ben Finney wrote: > [re-sending as a followup to an older thread] > > I see this discussion focussing on Subversion versus Git; I wish with > this message to point out that's a false dichotomy, as not all DVCSen > are necessarily like Git. Wanna revamp it? then here's GvR opinion[1] on DVCSes. [1] http://mail.python.org/pipermail/python-committers/2009-February/000433.html -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Developer workflow and DVCS
On Sat, Feb 28, 2009 at 23:00, Ben Finney wrote: > Sandro Tosi writes: > >> On Sat, Feb 28, 2009 at 02:21, Ben Finney wrote: >> > I see this discussion focussing on Subversion versus Git; I wish >> > with this message to point out that's a false dichotomy, as not >> > all DVCSen are necessarily like Git. >> >> Wanna revamp it? > > Revamp what? I don't know the referent of “it” in your sentence. > >> then here's GvR opinion[1] on DVCSes. > > That's GvR's opinion specifically in the context of choosing a DVCS > for development of Python itself. > > Since GvR won't (I presume) be using the PMPT or PAPT repositories, DPMT... > his opinion surely counts less than the opinion of those who intend to > use these repositories. I don't see why you bring that up. You too are not using our repository (because we are so bad that won't adopt bzr and svn is an ugly ugly VCS), so GvR opinion counts as anyone else. > Can you explain the relevance? How does it address the points I've > made? Because you only see bzr, while there's much more DVCSes around. For me, the discussion (being this particular new "branch" or the original one, since no advances are made) is closed. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ldaptor in DPMT: anyone interested?
Hello, anytime soon (== when I'll find some time to work on it) I'll have to do a QA upload for ldpator[1] (a couple of bugs need to be fixed: pysupport and pyopenssl transition). [1] http://packages.qa.debian.org/l/ldaptor.html So I'm wondering if anyone is interested to maintain it in the DPMT (it seems mainly a module, only inferred from its PTS page and popcon ;) ); in that case, we can work together and sponsorship is free :) Let me know asap. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: ldaptor in DPMT: anyone interested?
On Mon, Mar 9, 2009 at 13:00, Jan Dittberner wrote: > On Mon, Mar 09, 2009 at 12:41:58PM +0100, Sandro Tosi wrote: >> So I'm wondering if anyone is interested to maintain it in the DPMT >> (it seems mainly a module, only inferred from its PTS page and popcon >> ;) ); in that case, we can work together and sponsorship is free :) >> >> Let me know asap. > > Hi Sandro, > > I'm interested and use this module for a current development. That's great!! If you have time before I do, please start the "injection & adaptation" part :) > PS: I got my AM approval on Saturday and wait for FD/DAM now yeah, seen (& congrats) but that wait time can last a lot! (/me waited 3 months but now the situation is better) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#493888: dh-make: debian/rule template lists deprecated dh_python call
Hi Craig, thanks for contacting us (python modules/apps team). On Thu, Mar 12, 2009 at 08:02, Craig Small wrote: > On Tue, Aug 05, 2008 at 09:20:47PM +0300, Jari Aalto wrote: >> Packaging with dh-make using "single" choice, the generated >> debian/control includes deprecated dh_python line. During the deb >> making this is shown in message: >> >> dh_python: This program is deprecated, you should use dh_pysupport or >> dh_pycentral instead. > > The examples in debhelper still use dh_python too :( > Anyone know what I should replace dh_python with? Is it both? > > I've CC'ed the debhelper maintainer, because he needs to fix the > examples, and the python list, because you guys will be copping the > wrong packages if I don't fix it (and they should know python thingies). We (as in packagers) are standardizing to python-support, so I think all helpers and examples should do the same. Thanks for the cooperation, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Preparing for the new python-support
Hi Gustavo, On Fri, Mar 27, 2009 at 22:30, Gustavo Franco wrote: > [+pi...@d.o] > > Hi Joss, > > Is it done? > > What do you think POX? Let me know if you need any help with the > packages in the list that are being under team's maintenance. I could > prepare some in dpmt's svn during the weekend. If I didn't miss someone, the bugs affecting DPMT/PAPT package are already tagged as pending (hopefully near an upload), so the left package with outstanding bugs are all outside the teams. Once new python-support will be in sid, and then bugs will become RC, I'll dedicate part of my Debian time (always too few) to NMU those packages. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Sorry for the mess on elementtree
Hello, I want to apologize for the errors I did on the upload of elementtree; I was pretty sure it depended on python-support (>= 0.90.0), of course it was not. Thanks to bzed and joss for working on it this morning. I hope I won't commit such errors again in the future. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
2 new RFA pkgs: pycallgraph python-glpk (+ pmok orphaned)
Hi, I just filed 2 RFA for the packages in object. Anyone interested in them to remain in the team, please adopt now. I may take pycallgraph, but still not sure. I also orphaned pmock, that's only something that fits our team and you might be interested into adoption. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Butchered python configuration ...
2009/4/29 itsovermyhead : > 2009/4/29 Piotr Ożarowski : >> [itsovermyhead, 2009-04-29] >>> 2009/4/29 Piotr Ożarowski : >>> > Anyway, don't come back, nobody will help you on this list again >>> > (you broke what we prepared for you (Python installation), blamed us for >>> > it and then called us names) >>> >>> You're a fruit cake aren't you mate? Why didn't you post this to the >>> list? - just into to sending creepy little emails >> >> because when I'm feeding a troll, I at least try to do it in private >> (I admit, I should just ignore you, my fault) > > More creeepy little emails... Polite reply: you're not welcome here, please go away Upset reply: what do you want? you don't know nothing about python installations but to mess with them, we provide support and you insult us? go and play with the babies like you. Angry reply: go the fuck away from here!! Are you happy with this public reply? I'm not, like I'm not happy you're still here bothering up. PLEASE, go away and don't come back never again. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: intent to hijack turbogears 2 (and some of its friends)
On Mon, Jun 15, 2009 at 19:13, Stefano Zacchiroli wrote: ... > Given that the maintainer (Cc-ed) has not replied to any of the above > bug reports---the latter is 7-month old---I'm hereby notifying my > intention to hijack both turbogears 2 and turbojson. > > Comments, about either approval or disapproval of this intended > action, are more than welcome. Yay, go for it!! Thanks a lot for the work you did/do/will do :) . Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: what's keeping python2.6? why is Josselin acting like a deaf man when his packages contain critical bugs?
Hello Jan, I would like to reply politely: sorry if I will not be able to (or the resulting words don't look like), the intention is this :) On Sun, Jul 5, 2009 at 11:00, Jan Geboers wrote: > Hi team python, > > I am quite curious to hear what is keeping python2.6 from entering debian > sid? I think several people wonder this. >From a technical point of view, there is some work to do on the modules to make them compatible with 2.6 new features (for example: dist-package instead of site-package, /usr/local instead of /usr etc). This transition is currently running, but it's not yet completed; but I also think that an upload without adding to support version would work. > It's a rock solid release, which has seen many bugfixes, and is the fastest > python version ever. > The package in experimental has had only 2 bugreports, both are fixed. I'm not sure if this ml is the right place to ask: the description on [1] reports "Discussion of issues related to Python on Debian systems with a stress on packaging standards. Therefore relevant for maintainers of Python related packages." so it may or may not be on topic :) [1] http://lists.debian.org/debian-python/ But in any case, you should ask the package maintainer that, as you can see on [2], is maintained outside a team (that we can ideally suppose be represented by people actively working on python "stuff") so its his decision you're looking for and we (honestly) don't know. [2] http://packages.qa.debian.org/p/python2.6.html > Please, instead of putting so much effort in turbogears2 and zope and > whatever, wouldn't it be better to finally upgrade to the latest python > which > was released in OCTOBER 2008? Never write something like this: we are all volunteers, and we are free to work on whatever we like in our spare time. If you want something done, then work on it: did you contributed to py2.6 packaging, for example? Please also note that debian is also used in companies, and they might need zope package working for money to come to their bank accounts, so don't speculate. > Also, a more personal note to that notorious person called Josselin: why > don't you answer any emails regarding your debian packages? > Why don't you even respond when I ask for a simple upgrade of the > python-pymssql package, even after filing a critical bug report about the > grave bugs that > make the package unusable? Pymssql 1.0.2 was released over 2 months ago. > Upgrading the debian package takes about 5 minutes of your time. > Even if you don't have time to do that, a small reply to an email or to a > bug report would be more than welcome. This is a personal attack (against a guy I believe to be very active, technically skilled, even if something a little bit "rough" ;) ) and I don't like it at all. If you have complains against him not fixing a RC bug on that package, reply to the bug itself, so that a public statement of your "pressure" on the bug is made. Additionally, you can also help the maintainer, preparing a NMU or a series of patches to fix what you believe to be wrong, so that you can alleviate him from some work. That said, I really hope you now provide an updated package to Joss for him to check and possibly upload. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: what's keeping python2.6? why is Josselin acting like a deaf man when his packages contain critical bugs?
Hi Jan,
On Sun, Jul 5, 2009 at 19:34, Jan Geboers wrote:
> thanks for replying.
you're welcome.
> I dont have much time right now to prepare a large piece on this,
> but I wanted to say that I have tried to contact Josselin, both by email and
> debian bug report, but no success so far.
Probably because he has other (more important?) stuff to look at, at
this stage of the release cycle.
But you lacking time can show you that also other people may be in a
period of low free time, so they dedicate their time to what they feel
more important for the release and/or for our users. (and as personal
note, a module to connect to M$ sql server doesn't look like too much
"interesting").
Also note that an RC bug can be fixed with a NMU: if you complain
against something, you should be prepared to pay the price of it :)
Now the package has been injected in the Debian Python Modules Team:
you are encouraged to join us and fix this bug, and prepare and
accordingly upload.
> I also tried to get in touch with Matthias Klose with regard to the state of
> the python 2.6 package, but no reply came to that either.
That's another story, sorry.
> Even a short statement about the progress would be more than welcome,
> or maybe a call for assistance on the specific parts of work that can be
> done?
We are also waiting for this statement to come.
> But if both the python maintainer and the maintainer of the individual
> package can't be bothered to reply to e-mails or read their bug report that
> is marked critical,
> what more can be done? It's hard to help if you have no clue about where the
> problem or high workload is situated.
I said above: for RC bugs (severity in ('grave', 'serious',
'critical')) provide a well-done NMU and you'll (almost :) ) find a
sponsor to upload it.
> Taking into account Josselin's charming personality I'm quite sure that he
> wouldn't even accept an updated version of said package that I would provide
> to him.
You're again speculating (with another personal attach coming from the
backdoor): you didn't even try to propose a package to him, so how
could you know? Please do something "real" and then complain about
that not being taken into account.
> Personal attacks are not my intention, I hope my point of view isn't
> interpreted as such, I just care about Debian as a whole, and the state of
> python in Debian in particular.
And the best way to achieve this is to actually *help* debian packages
doing packaging work, bug triaging, etc etc.
At this point, I really want to see you involved in what you are
highlight as 2 problems. Else, you are forced to wait for some spare
time to come to the relevant maintainers.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [Python-modules-team] Bug#535855: ImportError: No module named _path
On Tue, Jul 7, 2009 at 08:20, Fabrice Silva wrote: > Le mardi 07 juillet 2009 à 08:02 +0200, Sandro Tosi a écrit : >> locate matplotlib > 535855.txt > > Listed : > - the system wide rc file > - an old subscription to matplotlib ML :) > - I renamed ~/.matplotlib to determine whether my configuration files > were corrupted. > - package information I'm out of ideas: could someone on the team give a look to this bug and see what's going wrong? Thanks a lot in advance :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Please take care of numpy
Hi Kumar, On Tue, Jul 28, 2009 at 19:30, Kumar Appaiah wrote: > Dear Debian Python, > > Since I have not been very attentive to the changes required for > python-numpy, I have removed my name from the uploaders. That, > however, will not prevent me from helping out with it whenever > possible, since it is team maintained. That's sad :( Since matplotlib and numpy are quite twisted together I might step in as one of the new co-maintainers. > I have updated the SVN version to use the latest numpy (1.3.0) and > have observed that it fixes several bugs. In fact, other than deciding > if pycentral is to be retained/pysupport is to be used (Piotr's advice > from earlier), it should be more or less ready for upload. I'd > appreciate it if someone could please handle these issues and upload > it when possible. Of course, due to previous commitments, I can't do anything important since September. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting stuck into apps-team and modules-team
Hi Jonathan, first of all, thanks for your interest in helping the teams! On Thu, Aug 13, 2009 at 16:00, Jonathan Wiltshire wrote: > Hi, > > I've looked at a few packages in the repositories for these teams, but I'm > reluctant to start making changes without making sure it's not going to > upset anybody :) > > Where the team is just an uploader, I'm inclined to leave the maintainer to > ask for help when s/he needs it. But where packages are fully under the team's > scope, is there any protocol for starting work on an oustanding package? Unwritten policy (or maybe it's written and I don't remember where ;) ) says: if the team is in Maintainer field, any member can do changes and upload the package; if the team is in the Uploaders field, any member can do changes but an upload is to be ack'ed by the maintainer. > Particularly where there are bugs or new upstreams available, is it acceptable > to just get stuck in, or is wise to contact the last changer (I found little > evidence of this on lists, but I may have been looking in the wrong > places)? Well, our course it would be nice to contact the current "real" person behind a package, but it's not strictly needed, see above :) Some things you might work on: - bug fixing - bug forwarding upstream - general cleanup of packages - review of packages in need for a sponsor (you can't sponsor, but you can screen the package to spot something wrong) - (cautious) upgrade to now upstream releases. have fun BTW: please do something for your signature: is as long as this email, and this a long mail of yours - it only adds confusion in the text. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Getting stuck into apps-team and modules-team
On Thu, Aug 13, 2009 at 16:09, Jonathan Wiltshire wrote: > On Thu, Aug 13, 2009 at 03:00:15PM +0100, Jonathan Wiltshire wrote: >> I've looked at a few packages in the repositories for these teams, but I'm >> reluctant to start making changes without making sure it's not going to >> upset anybody :) > > And of course, I was bound to forget something. Last question: what is the > consensus on deep packaging changes, check with the current "real" guy behind the package, it's the safest way. > like (examples) dpatch/quilt, I'd say dpatch - it's easier to use it in SVN > cdbs/debhelper/dh, I strongly encourage to use debhelper, and others do the same > python-central/python-support and so on? python-support is what we're standardizing on, so feel free to migrate to pysupport is you stumble upon a pycentral package. > -BEGIN PGP SIGNATURE- (+ 18 others line of signature) ditto. Ah, a nice communication medium is IRC: if you like, you can find us at #debian-python on irc.debian.org OFTC network. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Need for help ?
n Tue, Aug 25, 2009 at 21:56, Carl Chenet wrote: > If you need help for one of your packages, feel free to contact me :) please use $ ./chaica --verbose next time :) I'll be here for you. I suggested Carl to send this email because: - he is a very good python programmer (he's helping *a lot* with reportbug bug fixing providing tons of patches); - he wants to gain more skills in Debian packaging; so help here is a straightforward consequence. Other then bag triaging, classic help on the team packages, I think an explicit declaration of "willing to help" would allow maintainers with few spare time to dedicate to theirs packages, to encourage Carl to co-maintain those packages. Or any other activities we believe need a helping hand. Let's hope it works ;) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: python-support source repository
On Tue, Sep 1, 2009 at 12:53, anatoly techtonik wrote: > Hello, > > Can anybody point me to the repository location of python-support package? You should ask the maintainer of the package, since we are "users" of it. I've added Joss in CC, python-support developer and maintainer. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [Python-modules-team] Bug#543351: logilab.astng cannot be imported after upgrade from stable
Hi Chris, thanks for your report. On Mon, Aug 24, 2009 at 14:43, Chris Lamb wrote: > Package: python-logilab-astng > Severity: serious > Version: 0.19.0-2 > ... > I can make it work by manually removing > > /usr/lib/python2.5/site-packages/logilab Since all the packages sharing logilab namespace have a new upstream version to package, it's a good time to try to fix this on all of them. The preinst file of logilab-astng is [1]: we already try to fix the migration (central->support) problem but we don't remove to common logilab/ directory. [1] http://svn.debian.org/viewsvn/python-modules/packages/logilab-astng/trunk/debian/python-logilab-astng.preinst?view=markup I'd like to know what would be the best solution for this (hence -python in the loop): - logilab-common is the lower level of logilab* packages, so we can add conflict there with all the other logilab-* packages and then remove logilab/ completely from its preinst - add extra logic to all logilab* packages to check if /usr/lib/python*/site-packages/logilab is empty and then remove it (could there be cases where it left hanging dirs?) I'm considering teh second solution a bit better, but I'd like to hear from your what youi think. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Menu entries not appearing
Please use debian-mentors for general questions. follow up there On Thu, Sep 3, 2009 at 13:42, Alessandro Dentella wrote: > Hi, > > I tried to add a menu entry for application 'sqledit', but the entry does not > appear if I use standard menu entry in debian as: > > ?package(python-sqlkit):needs="X11" section="Applications/Office"\ > title="sqledit" command="/usr/bin/sqledit" > > it gets placed in /usr/share/menu/python-sqlkit but it does not show in the > menu. In postinst scipt I correctly see: > > if [ "$1" = "configure" ] && [ -x "`which update-menus 2>/dev/null`" ]; > then > update-menus > fi > > It *does* appear correctly if I place a sqlkit.desktop in > /usr/share/applications. > > I'm doing something wrong with the menu entry? > Is it ok to use only sqlkit.desktop? > > thanks again > > sandro > *:-) > > > > -- > Sandro Dentella *:-) > http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy > > > -- > To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > > -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: XS-Python-Version vs pyversions
Hi Steve, I don't think that keep accusing the only (and really) active python helper developer would help anyone, you made your statement pretty clear already :) Additionally, please consider that: - if python-central was good, I don't think there would have been any need for an additional helper - if python-support is that bad, I don't think that developers would have used, and chosen to be the default|suggested|preferred|etc one. On Tue, Sep 8, 2009 at 05:21, Steve Langasek wrote: > On Tue, Sep 08, 2009 at 01:49:06AM +0700, Mikhail Gusarov wrote: > >> Twas brillig at 11:37:50 07.09.2009 UTC-07 when vor...@debian.org did gyre >> and gimble: > >> SL> They were part of the design that came out of the python packaging >> SL> BoF in DebConf 6 that you then proceeded to ignore entirely. > >> Is this design and rationale written down somewhere? It's hard to follow >> policy which contains completely opaque requirements. > > No, ehm... so how are you expecting external people to evaluate your statement? a "either you're at that BoF or stick to what I'm telling now" it's unacceptable. Keep things secrets does not help anyone. Moreover, could you please tell us how the release team exactly used the XS-P-* fields so far? Real examples, not "we used them, don't worry", are appreciated. > it's pretty much bitrotted away by now thanks to people deciding to > discard all the efforts of the session in question and unilaterally > implement helpers that don't do what was asked for. Now, if you really think that the only culprit here is pysupport developer, then maybe your opinion are a bit biased. Yes, I would really like to have the ultimate python helper, just one, but now the only one elegible to this status is python-support. And you want to know why? because python toolchain maintainer is neglecting his activities in Debian (and we all sadly know that). So, if you /really/ want to accuse someone, you should better reconsider your target. Oh, good morning everyone (@7.30AM) :) Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [Python-modules-team] Bug#543351: logilab.astng cannot be imported after upgrade from stable
Hi Alexandre & others, On Mon, Sep 7, 2009 at 10:21, Alexandre Fayolle wrote: > The problem I can see with removing blindly from the postinst is that > potentially you're going to delete files belonging to other packages (e.g. > older packages installed from Logilab's Debian repositories). They won't work anyway: they have to be ported to python-support too. This because if /usr/lib/python*/site-packages/logilab/ is left there, new packages won't work, but neither the old, since they would use the new one (migrated to pysupport), but they're not functional, so we closed the cycle :( > Could the following work: > > logilab-common postinst removes /usr/lib/python*/site- > packages/logilab/__init__.py*, and issues a warning if there are other stuff > in > the directory : this will stop packages installed under that tree from working > without deleting the files themselves (enabling the administrator to find out > what's broken with that installation). For what said above, I have implemented the solution of "brutally" removing /usr/lib/python*/site-packages/logilab/ in loglab-common (since it's the commno (base) ground for all the other logilab packages), adding conflicts with the older versions of logilab-* pkgs and bumping the dependencies on logilab-* to the most recent version of logilab-common. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#550458: RFA: petsc4py -- Python bindings for PETSc libraries
Package: wnpp Severity: normal Ondrej asked to be remove from this package, so it is now without a real maintainer. Hence, a new maintainer is needed for this package. NOTE: the package must be left into the DPMT repository. Regards, Sandro -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Request to join Python Modules Team
Hi Martin, I'm happy to see this email coming :) On Sun, Oct 11, 2009 at 20:50, Martin Kelly wrote: > Hi, I have been the maintainer of pyecm and python-gmpy for several years > now and have thought it would be a good idea to maintain these packages > within the Python Modules Team. Therefore, I request to join it. Note that I > am not a Debian developer and therefore do not have an Alioth login. You can register on alioth even if you're not a DD: your login name will have '-guest' suffix, but that's all. Having an alioth user is a precondition to join any team (so this included). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Request to join Python Modules Team
Hi Martin, On Fri, Oct 16, 2009 at 05:03, Martin Kelly wrote: >> if you've read our policy, then yes, you're DPMT member now :-) >> >> [1] http://python-modules.alioth.debian.org/python-modules-policy.html > > Yes, I've read it. Do I need to submit my packages to the subversion > repository or do I just keep maintaining them like I have in the past? A key point of a team is having a shared repository where all the members inject their packages and anyone other can check them out, change them, collaborate in their maintainership. So, yes, you have to inject in the SVN repo. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: twisted-doc for python-twisted
Hello, On Sat, Nov 7, 2009 at 03:42, anatoly techtonik wrote: > Hello, > > Shouldn't twisted-doc be renamed to python-twisted-doc for consistency? IMO, yes, it should be 'python-twisted-doc', but given who's the maintainer... Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Python 2.6 in unstable
On Sun, Nov 8, 2009 at 22:22, Kumar Appaiah wrote: > Dear Debian Python, IIUIC s/Debian Python/Python Maintainer/ :) > Most of the Python 2.6 transition bugs have been fixed, and the > remaining ones are only some leaf packages, as can be seen here: > > http://tiny.pl/hqwjz > > With the last upload of python-central, only a few issues with > python-central remain, before python 2.6 can be uploaded to unstable, > as has been outlined by Piotr here: > > http://lists.debian.org/debian-python/2009/11/msg00014.html > > Given this, could you please let me know when Python 2.6 can be > uploaded to unstable? I'd really like to see it in unstable quickly, > so that we have enough time for testing all Python applications and > modules, and handle bug reports and troubles with a lot of time to > spare. I fear that delaying the upload to close to the freeze might > not provide sufficient time for testing. I'd really like to know that too. I completely agree with Kumar request, reasoning and fears. Please Matthias, share your thoughts with us. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#556148: installs files into /usr/local for Python >= 2.6
Hi Dirk,
On Fri, Nov 13, 2009 at 23:45, Dirk Eddelbuettel wrote:
>
> On 13 November 2009 at 22:54, Piotr Ożarowski wrote:
> | Package: nwsclient
> | Version: 1.6.4-1
> | Severity: important
> | User: debian-python@lists.debian.org
> | Usertags: python2.6 usr-local
> |
> | Hi,
> |
> | Starting from Python 2.6, the installation paths for distutils have
> | changed. /usr/local is now used by default.
> |
> | When rebuilt against python-all{,-dev,-dbg} (and thus python2.6) from Debian
> | experimental, your package contained these files:
>
> I don't have access to experimental in my pbuilder. So how should I test this?
After Piotr suggestions, I'm creating right now a pbuilder chroot to
test these bugs, here are the steps I'm doing:
- cd where 'base.tgz' is
- cp base.tgz base_python2.6.tgz
- sudo pbuilder --login --basetgz base_python2.6.tgz --save-after-login
- echo "deb http://ftp.debian.org/debian/ experimental main" >>
/etc/apt/sources.list
- apt-get update
- apt-get install -t experimental python-all-dev python-all-dbg (I
need these 2, they should pull in all the needed packages)
- exit
- sudo pbuilder --build --basetgz base_python2.6.tgz .dsc
I'm at 'apt-get install...' but the rest should Just Work.
> | nwsclient:drwxr-xr-x root/root 0 2009-11-13 04:20 ./usr/local/
> | nwsclient:drwxr-xr-x root/root 0 2009-11-13 04:20 ./usr/local/bin/
> | nwsclient:-rwxr-xr-x root/root 7313 2009-11-13 04:20
> ./usr/local/bin/PythonNWSSleighWorker.py
> | nwsclient:-rwxr-xr-x root/root 2882 2009-04-27 23:18
> ./usr/local/bin/PythonNWSSleighWorker
> | nwsclient:-rwxr-xr-x root/root 2394 2009-11-13 04:20
> ./usr/local/bin/pybabelfishd
> | nwsclient:-rwxr-xr-x root/root 845 2009-11-13 04:20
> ./usr/local/bin/pybabelfish
> |
> | How can it be fixed?
> |
> | * try to pass "--prefix=/usr" to setup.py call, check if it's enough,
> | * if your package is using python-central:
> | - add "XB-Python-Version: ${python:Versions}" to all binary packages that
> ship
> | Python modules (.py files) or extensions (.so, including _d.so) in
> | debian/control, check if it's enough,
>
> I already did that, so I guess it is not enough.
>
> | - try to convert to python-support[1], check if it's enough,
> | * add --install-layout=deb to setup.py call and bump minimum required
> | python{,-all,all-dev} build dependency to 2.5.4-1~, check if it's enough
Did you add this too?
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#556148: installs files into /usr/local for Python >= 2.6
Err, sent too fast
On Fri, Nov 13, 2009 at 23:45, Dirk Eddelbuettel wrote:
> | How can it be fixed?
> |
> | * try to pass "--prefix=/usr" to setup.py call, check if it's enough,
> | * if your package is using python-central:
> | - add "XB-Python-Version: ${python:Versions}" to all binary packages that
> ship
> | Python modules (.py files) or extensions (.so, including _d.so) in
> | debian/control, check if it's enough,
>
> I already did that, so I guess it is not enough.
you you mean you use the correct XB-P-V or that you *also* add the
--prefix=/usr? The file installed into /usr/local seems executables,
so it's possible that when insalling them, an explicit prefix is
needed.
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Python Policy Update
On Mon, Dec 14, 2009 at 06:19, Scott Kitterman wrote: > I know a lot of effort has been made to get the archive ready for Python 2.6. > Either before or with the Python 2.6 upload, we are going to have to drop > Python 2.4 as a supported Python version. Any work that could be done now to > ease that transition would be beneficial. So let the python maintainer present us his uploads plan, his impact study of the python2.6 upload and python2.4 removal breakage, and also the usertag for the bug he filed to archive this transition. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Request to join the Python Modules Packaging Team
Hi Christopher, On Sun, Dec 20, 2009 at 23:51, Christopher Albert wrote: > I'd like to offer my support related to the broken package petsc4py > (Bug#550458 - RFA: petsc4py -- Python bindings for PETSc), possibly becoming > its new maintainer. if you plan to adopt the package, please retitle the RFA bug to an ITA (Intent To Adopt), so that it's clear someone is working on taking over the package (and avoid potential duplicate work). > I have already updated and fixed the package (for details, see the bug > thread at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550458) and would > love to become a member of your team in order to commit my changes. > > My alioth username is ert_guest. As I am no DD right now I would need a > sponsor (maybe Sandro?) to upload the package. I'd be happy to review the changes once you'll be able to commit your changes: just give me a ping (off-list, or on irc as morph on #debian-python channel of OFTC network). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Unit tests
On Sat, Dec 26, 2009 at 19:11, Guy Hulbert wrote: > On Sat, 2009-26-12 at 17:13 +0100, W. Martin Borgert wrote: >> Quoting "anatoly techtonik" : >> If unit tests were in the package, reportbug could automatically >> run them on a bug report. Does someone do this already, maybe? > > Can reportbug be modified to download a source package and run tests ? Short answer: no. Detailed answer: no, because: - it bloats reportbug to do something that's not meant to (it _reports bugs_) - how to recognize packages that have unit tests and those that haven't? - where are those unit tests and how to execute them? more generally: there is no standard way to run unit tests. - what if unit tests need additional dependencies (not present on the user system) to be executed? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: please upload python2.6 to unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, On Tue, Jan 12, 2010 at 03:08, Mr. Foobarra wrote: > I have grown woefully tired of watching respected developers ask nicely, > tiptoe around, get angry, ask again after waiting a few weeks, and continue > to make every attempt to give you every benefit of the doubt. This upload is > way overdue and was requested formally in the BTS August 26, 2009 - with no > response from you. because he's not talking to us. either because he doesn't have time, or doesn't care about other developers, the fact remains: he's not talking to Debian (except for 2IC or relteam). > 1) Upload python2.6 to unstable within the next 7 days, or > 2) RFA python2.6 and all relevant python packages within the next 7 days. IMO step 2. must be done anyhow: Matthias, you're doing a very bad job at maintaining Python in Debian, really. and the request to drop Python 2.4 before even considering uploading Python 2.6 in unstable (they are completely unrelated!) is another example of what I'm talking about, and of the very low interest you have in the Debian Python community. You have people doing analysis, filing bugs, doing NMUs but none of them are identified as Python maintainer (being in Maintainer/Uploaders field) but those activities are part of py maintainer ones. Easy as it can be, just leave Python to Debian, and step over. I have no doubt there will be a group of people interested in Debian and Python that will take over the package (I'm one of them, I've already asked some other guy and I'm intended to ask some other to join). Consider this a "nice" request of orphaning Python and let new fresh blood comes in, else, you'll see it pushed further. > I'm sure there are possible issues with other packages, yada, yada, but they > will get worked out just fine - no need to keep waiting on...what are you > waiting on? On nothing, but he doesn't have time to maintain properly this package, and so we must wait for a small free slot of time (because Debian doesn't have any priority) to do "dch -m "uploading to unstable" ; dch -r ; " (because that's what needs to be done...) Matthias, it's clear to everyone you're most interested in other part of the toolchain (gcc, binutils & co) so leave Python to people caring for it. Regards, - -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.10) iEYEARECAAYFAktMFBAACgkQAukwV0RN2VAlbgCgmJVghzSHO1d2OjJiMBtMSNxU fjUAnRE+PKCcSZdIc9XcYJovssqINLqf =4JBG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: please upload python2.6 to unstable
Hi Andreas, On Tue, Jan 12, 2010 at 08:39, Andreas Tille wrote: > I have no idea what makes you think that even more angry mails on public > mailing list will solve the problem. Be quiet won't solve it either, sadly. That's proved by the long silent period that provides not advance on the python maintainership-side. At least i'm proposing to form a group (and be part of that) to take over maintainership. > Matthias has obviousely recovered > from his illness >From the few information I got, I think the illness was some sort of flu, and nothing more scaring (I hope so!). Anyhow, it's not the problem of illness of mid-December: the situation is lasting a long time. > if he has time for gcc-4.5 testing That's my point: I'm not saying it's something that should not be done, but since the freeze is coming, and py2.6 is targetted for squeeze, maybe work on this is more Debian-oriented that working on gcc-4.5 that won't be the default gcc for squeeze. > and is perfectly > able to give a statement to your suggestion. I don't argue he's not able to reply, but that he's not inclined to. I really hope to be proved wrong. > And no, I will not become a member of Python packaging team - I just > wanted to share my experiences which worked quite good and in all cases > resulted in either a positive or no reaction of the maintainer in > question and thus solved the problem. Probably you don't know (because I, in the first place, didn't make them always public/well-spread) how many times I've asked to collaboratively maintains all the python modules he maintain, and they went all with no reply. Also the packages that are/were already in the DPMT are uploaded without committing the changes to SVN. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: please upload python2.6 to unstable
On Tue, Jan 12, 2010 at 09:06, Steve Langasek wrote: > On Tue, Jan 12, 2010 at 08:56:08AM +0100, Sandro Tosi wrote: >> On Tue, Jan 12, 2010 at 08:39, Andreas Tille wrote: >> > I have no idea what makes you think that even more angry mails on public >> > mailing list will solve the problem. > >> Be quiet won't solve it either, sadly. That's proved by the long >> silent period that provides not advance on the python >> maintainership-side. At least i'm proposing to form a group (and be >> part of that) to take over maintainership. > > A group hijack is still a hijack. I don't know why you try to make this > sound like some sort of noble enterprise for the good of Debian. Where did I talk about hijack? If I wanted that, I'd have already done. 'take over' can be a wide concept: - form a team that contains Matthias and collaboratively maintain python - form a team that does not contain Matthias and collaboratively maintain python - ask the ctte to decide who's to maintain python, the new group or the current maint (that's what I was referring with "pushed further" in the initial reply) - something else What I (and many other people) want is a properly maintained python package, which is not now. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#543689: please upload python2.6 to unstable
On Tue, Jan 12, 2010 at 13:44, Andreas Tille wrote: > On Tue, Jan 12, 2010 at 12:21:34PM +0100, Bastian Venthur wrote: >> The information is there, it is unfortunately just well hidden: >> >> http://lists.debian.org/debian-release/2009/12/msg00207.html > > Ahh, that's a good catch. I can not tell whether the technical arguing > is correct but at least it gives some sign of activity. On the other > hand it shows that Matthias is ignorant about relevant communication > channels (like for instance CCing debian-python) and relies on > communication proxies as Bastian. Also, that's something not communicated/agreed/decided in concert with the python apps/modules teams. Additionally removing py2.4 before adding py2.6 only introduces a delay in py2.6 wide-availability with very few (if any) advantages over removing it after or at teh same time of py2.6 addition. > This does not sound promissing for > team maintenance. :-( you start seeing what I mean Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#561316: postr: diff for NMU version 0.12.3-1.1
Hi Ross, On Tue, Jan 12, 2010 at 09:10, Ross Burton wrote: > On Mon, 2010-01-11 at 23:30 +0100, Sandro Tosi wrote: >> Please also consider joining the PAPT [1] and maintain the package with us. >> >> [1] http://wiki.debian.org/Teams/PythonAppsPackagingTeam/ > > I was previously the upstream maintainer too but have passed that on to > someone else. I'd welcome the PAPT taking over packaging entirely. Thanks for your offer! I'm adding d-python in the loop, so that some guys there might take over the package. You might also consider filing a RFA bug, if you're no more interested in this package. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [Python-modules-team] Bug#557925: python-axiom: FTBFS with Python 2.6
Hello Vincent,
On Wed, Jan 13, 2010 at 21:31, Vincent Bernat wrote:
> OoO En cette fin de matinée radieuse du mercredi 25 novembre 2009, vers
> 11:49, Jakub Wilk disait :
>
>> Package: python-axiom
>> Version: 0.5.31-2
>> Severity: important
>> User: debian-python@lists.debian.org
>> Usertags: python2.6 ftbfs
>
>> Hello,
>
>> When rebuilt against python-all{,-dev,-dbg} (and thus python2.6) from
>> Debian experimental (and with python2.6 as the default one), your package
>> FTBFS.
>
> Hi!
>
> I am a bit lost with all those python2.6 FTBFS. From the log, it is not
> obvious why it fails here. I would like to test it myself. I have
> installed python-all{,-dev,-dbg} from experimental but default Python
> stays 2.5. If I change /usr/bin/python symlink to python2.6, CDBS calls
> python2.5 instead of python.
>
> I have also tried to update /usr/share/python/debian_defaults with no
> luck. What is the cleanest way to compile something with python2.6 as
> default?
The cleanest solution would have been to have Python 2.6 as default in
experimental, as a playground (since we can't have it in sid),
something I'm asking since weeks, but I have apparently not the
convincing-skill required.
> A pbuilder solution would be great to avoid to mess with my
> system.
I've created for testing and building a pbuilder chroot where Python
2.6 is the default:
- installing python2.6, -dev, -all-dev, -dbg, -all-dbg (& friends if
someone is missing) from experimental
- changing the symlinks in /user/bin/python* to point to the relevant
python2.6* binaries
- changing /usr/share/python/debian_defaults setting 2.6 as default
and 2.5 2.6 in supported
that chroot usually works.
In the axiom case, it currently FTBFS because twisted is not available
for Python 2.6:
cd . && python setup.py build
--build-base="/tmp/buildd/python-axiom-0.6.0/./build"
Traceback (most recent call last):
File "setup.py", line 1, in
from epsilon.setuphelper import autosetup
File "/usr/lib/pymodules/python2.6/epsilon/__init__.py", line 3, in
from epsilon._version import version
File "/usr/lib/pymodules/python2.6/epsilon/_version.py", line 2, in
from twisted.python import versions
ImportError: No module named twisted.python
make: *** [debian/python-module-stampdir/python-axiom] Error 1
(attached the full log). So you should first build twisted with 2.6,
retry axiom, loop on all the other (if any) depends needed to be
recompiled with 2.6, then debug teh FTBFS on axiom itself, if still
present.
HTH,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
python-axiom_0.6.0-1_amd64.build.bz2
Description: BZip2 compressed data
Re: Questions about PAPT and the uploading process
On Mon, Jan 18, 2010 at 02:32, Umang wrote: > I tried the updating etch to sid method. Here's what I got: ... >> E: Dynamic MMap ran out of room google for this error: you'll find out several explanations and resolutions. > So this fails too. > > Any ideas on what I should do now? I'm feeling pretty stuck right now. Since this are general questions, not particularly related to Python, I encourage to reroute such emails to debian-ment...@l.d.o , the correct ml. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Would like a sponsor to upload the new version of python-foolscap
On Fri, Jan 29, 2010 at 03:08, Ben Finney wrote: > Tristan Seligmann writes: > >> Are you even in the channel? > > Often, yes. > >> The topic of the channel seems like a perfectly reasonable place for >> this kind of list, too, so I'm not sure why you object to it so >> strongly. > > I would think a separate task tracker would be more appropriate; the > channel topic should remain primarily descriptive of the topic of the > channel, after all. Let the people (sponsoree & sponsors) who use that "tracker" decide what to use for it (you decided to not maintain your packages with us, and you can't sponsor packages). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-whisper
On Fri, Jan 29, 2010 at 00:47, Ben Finney wrote: > writes: > >> Today I have switched python-whisper to use python-support instead of >> python-central > […] > > Be aware that, for an package that was *already* in Debian, you would > need to modify your maintainer scripts to clean up after the mess left > by ‘python-central’ in previous versions of the package. See > http://lists.debian.org/debian-python/2009/03/msg00060.html> (view > the full thread for a discussion of why it's necessary). > > That's not strictly needed for a package that was never in Debian to > date, but it might be a good idea (and at any rate it does no harm) if > your package has ever been installed via other repositories. No. That only applies for packages that are in *stable* (with python-central) and are now in testing/unstable (with python-support). If the pacakge (it's an ITP so it was *never* in Debian) switches from central to support in testing/unstable is not needed. Document a bit better before suggesting such methods when not needed. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Would like a sponsor to upload the new version of python-foolscap
On Fri, Jan 29, 2010 at 14:15, Ben Finney wrote: > Sandro Tosi writes: > >> On Fri, Jan 29, 2010 at 03:08, Ben Finney wrote: >> > Tristan Seligmann writes: >> > >> >> Are you even in the channel? >> > >> > Often, yes. >> >> Let the people (sponsoree & sponsors) who use that "tracker" decide >> what to use for it (you decided to not maintain your packages with us, >> and you can't sponsor packages). > > I was under the impression that the ‘#debian-python’ channel was a > resource for use equally by anyone for discussion of maintaining Python > packages in Debian. When did it become an in-group-versus-out-group club > house, with credentials required for entry? Perhaps that should be > announced better. I don't even know what you're talking about, probably nothing related to what I said. I'll rephrase: we decided to use irc channel topic for RFS because it's easier for us (sponsors and sponsoree for DPMT/PAPT). You decided to not be part of those teams and still encouraging us to use something else for apparently no reason. Something strange, at least. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Please consider adopting python-{networkx,pygraphviz}
Hi Cyril & others,
On Sat, Jan 30, 2010 at 02:15, Cyril Brulebois wrote:
> Hi,
>
> Yaroslav Halchenko managed[1] to piss me off so badly that I'm not
> sure I want to have anything to do with python-{networkx,pygraphviz}
Sorry to read that.
> anymore. It would be nice to see some python-savvy folks take care of
> it from now on.
If you're decision is taken, I'd like to take the package back into
DPMT repo and take care of them with the team. If you still want to be
in Uploaders it would be nice (but I'll understand if you don't), and
if you prefer to maintain the current GIT repo (instead of reinjecting
in SVN DPMT repo) we'll sort it out somehow.
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
(again) Why default python is not 2.6 yet?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yes, again. Why the default Python interpreter is still 2.5 and not 2.6? No, don't tell me it's because of the first round of binNMUs: either someone's going to fix them or they will be FTBFS with 2.6 as default, and better explicit than implicit (how many people look at those binNMUs except us?). No, don't tell me it's because of Release Team, because they were (in the name of aba, many thanks!) very kind and responsive, and are waiting on our decisions. If there is a valid, technical reason, please let us know, but as of now I can't see any. So, let's just change the default to 2.6, kindly ask Lucas to do an archive-wide rebuild (I'm pretty sure he'll be happy to support us, but not certan, hey we still have to ask him ;) ), and deal with the fallback. Keep waiting and waiting is pointless, and does only harm for the target to support a stable release (there are very few people actively working on fixing these bugs, so the more the time, the better the release and the less the stess). Regards, - -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.10) iEYEARECAAYFAkt7JMIACgkQAukwV0RN2VAUSwCePby0ZL3KJyODi+IbO4CnGvZh oPwAmwXZqpIK8ydA8+a19AxOAYNo6EsJ =PfY9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1002161505w3eb75897l5d9171d439e7b...@mail.gmail.com
Re: (again) Why default python is not 2.6 yet?
On Wed, Feb 17, 2010 at 00:32, Cyril Brulebois wrote: > Sandro Tosi (17/02/2010): >> No, don't tell me it's because of the first round of binNMUs: either >> someone's going to fix them or they will be FTBFS with 2.6 as >> default, and better explicit than implicit (how many people look at >> those binNMUs except us?). > > While 2.5 is the default, one can use (with the default interpreter) > any package built against 2.5; meaning those FTBFSes don't matter > much. Sure it can be used, but we still have to fix them before the release. > Switching to 2.6 would mean that the packages currently FTBFSing can't > be used (with the default interpreter). > > So, sorry, but yes, I think the FTBFSes are holding up the transition, > and for a good reason. Hopefully, I guess a few NMUs should do the > trick. Ok, but those ~10 packages are only the tip of the iceberg. They were scheduled weeks ago, and if they're still there, they'll probably last longer. For example, are all the maintainers aware their packages are FTBFS? I took 'gammu' as example, and there is no RC bug filed, so probably Michael didn't even know gammu needs work. How many packages will FTBFS, fail to start or to work, generate weird errors or any other flavor of "won't work with 2.6"? Nobody knows, that's why having the switch sooner than later gives us more time to actually test the packages, let the users verify if they're working as expected, and for developers (wide meaning) to fix any problem. At the time of the switch, yes, the transition will start to grow, given the current "hidden" bugs, but just waiting won't make them go away/be fixed/noticed. That's my whole point: the more time with 2.6 as default, the more time we have to prepare squeeze better, making this transition less painful as it currently is. > (I might be missing something, I'm a bit laggy buildd-wise since past > week.) No problem :) Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1002162228j6b971733j2041a797be232...@mail.gmail.com
Re: (again) Why default python is not 2.6 yet?
On Wed, Feb 17, 2010 at 11:31, Michal Čihař wrote: > Hi > > Dne Wed, 17 Feb 2010 07:28:58 +0100 > Sandro Tosi napsal(a): > >> Ok, but those ~10 packages are only the tip of the iceberg. They were >> scheduled weeks ago, and if they're still there, they'll probably last >> longer. For example, are all the maintainers aware their packages are >> FTBFS? I took 'gammu' as example, and there is no RC bug filed, so >> probably Michael didn't even know gammu needs work. > > There is, but fixed in experimental. I just did not manage to extract > fixes to fix build of version in unstable (well the thing is that the > FTBFS is completely unrelated to Python version, it's just bad timing > in some test cases), so I will probably upload version from experimental > to unstable. Thanks for complete the missing info! Please note, however, that I was only running an example, extracting info at 7AM, and I was not meaning any personal offense of no-action upon RC bugs, not bugs filing or so. Also, it was not the important part of the email: I've received 2 replies for this point and none on the other, probably no-one else cares about it. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1002170330i2d67a656rdf575352757cb...@mail.gmail.com
Re: (again) Why default python is not 2.6 yet?
On Wed, Feb 17, 2010 at 15:49, Rene Engelhard wrote: > On Wed, Feb 17, 2010 at 12:05:56AM +0100, Sandro Tosi wrote: >> If there is a valid, technical reason, please let us know, but as of >> now I can't see any. > > Loads of RC bugfixes (partly on obsolete versions) waiting to enter testing > which would more blocked that it already is with the mips* buildd backlog. Those RC are still RC even in a month or 2, only that knowing them, they can be fixed. >> So, let's just change the default to 2.6, kindly ask Lucas to do an >> archive-wide rebuild (I'm pretty sure he'll be happy to support us, >> but not certan, hey we still have to ask him ;) ), and deal with the >> fallback. > > For months. At which time we'll still have the completely obsolete OOo 3.1.1 > (or whatever else example you find) in squeeze. No. That holds true any time we do the switch. So when should we change the default? the moment we freeze? You mentioned OOo, we have also libjpeg mess going on, and soon we'll have php5 probably. >> Keep waiting and waiting is pointless, and does only harm for the >> target to support a stable release (there are very few people actively > > That's true, though. But python's not alone in the world and if you did > it far earlier I understand, when you touch "core/big" packages, there are always consequences; but I don't get what you're suggesting to actually switch: at freeze time, when there are no other transition on sight (i.e. never), release squeeze with 2.5 as default, else? It was not done before, that's a fact. It should be done now, and deal with the damage it generates (of course, with the help of RT, if they agree to start the transition). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1002170718s39d7a65cy22eb6c6ee571a...@mail.gmail.com
Re: Towards Python 2.6: Architecture:all & XS-P-V:current packages
On Fri, Feb 19, 2010 at 19:43, Jakub Wilk wrote: > Hello, > > 14 packages in the archive have ‘XS-Python-Version: current’ field and build > ‘Architure: all’ binary packages containing Python modules. This is bad, > because such packages currently depend on ‘python (<< 2.6)’ (for no good > reason), thus they'll need sourceful uploads after switching default version > of Python. > > I am looking for a volunteer to do bug filing. I'm gonna file them. Thanks for your analysis! Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1002191102t43c4qe3c67e0b5986e...@mail.gmail.com
Re: RC severity for Python 2.6 related bugs
On Sun, Feb 28, 2010 at 15:29, Vincent Bernat wrote: > OoO Pendant le journal télévisé du samedi 27 février 2010, vers 20:19, > Luca Falavigna disait : > >> after some discussions on #debian-python, I'd like to propose >> increasing severity of Python 2.6 related bugs [1] to serious. > > Well, I disagree. Python 2.6 is not the default. Packages are currently > built with Python 2.5 and do not fail to build in a current pbuilder. I tend to concur: they should be RC when 2.6 is the default, which is still not, for no reason. > We > already had a bunch of bug reports about packages not building with > Python 2.6 as default a few months ago and it was a mess to setup a > pbuilder to build with Python 2.6 as default [1]. The solution is easier > now but not documented (to the best of my knowledge). It still needs manual setup, and it's not so known how to do, and of course there was no support from python maintainer in at least setting 2.6 as default in experimental, just to help people debug and fix those bugs. I've asked this in late December, no reply came, (but it's so difficult is to change 5 lines in debian/rules of python-default to help releasing with 2.6 as default...). > I am also still lost why Python transition communication is done in > debian-release@ and not in debian-pyt...@. Because Python maintainer is unable to communicate, with anyhow. The only audience he cares a bit is the Release Team. debian-python is completely ignored by him. > debian-python@ contains posts > like "Why default python is not 2.6 yet?" that got not really answered > because the transition seems to be managed behind the scene. the transition is simply not handled by the Python maintainer. It is handled by the people he ignores by filing bugs, preparing patches and NMU, and interacting with RT for binNMUs. Often it is done on irc, so no public trace is left. > It would be far easier to let Python 2.6 be the default, then file (or INDEED! > upgrade) serious bugs and solve them in a week or two. Most bug FTBFS > reports that I received for my Python packages is related to the build > process and does not hinder the package from working with Python 2.6. I > think this is the case for most simple packages because the hard work is > done by python-support. That's why setting 2.6 should have set as default *ages* ago: did anyone hear from Python maintainer about it (even after kind and less-kind queries)? Of course, no, thank you... Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1002280739q2941b4d0l3e0c311913ac6...@mail.gmail.com
Re: RC severity for Python 2.6 related bugs
On Sun, Feb 28, 2010 at 23:11, Vincent Bernat wrote: > I also tend to believe that there are a lot of packages that will just > fail to run with Python 2.6 but will have no problem to build, because > for most packages, building just means to copy files in the right > location. The later we switch to Python 2.6, the more difficult it will > be to catch those bugs. I absolutely agree with this (even though, for those packages that byte-compile the files they install, it's a smaller problem) and I fear there are several situations where there are hidden bugs only discovered with (long) *usage* of a system with 2.6 as default: waiting to do the switch, doesn't help to release a better squeeze, only a worst and buggier one. Additionally, as a side note, unstable is "unstable" by definition: its users knows it, and if something breaks in it, it will either be fixed or not in stable, so "break users apps" problem is less appealing (even though it exists). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1002281450h79524b79j3e99c410dcec...@mail.gmail.com
Re: RC severity for Python 2.6 related bugs
On Sun, Feb 28, 2010 at 23:17, Vincent Bernat wrote:
> OoO En ce début d'après-midi ensoleillé du dimanche 28 février 2010,
> vers 15:29, je disais:
>
>> Well, I disagree. Python 2.6 is not the default. Packages are currently
>> built with Python 2.5 and do not fail to build in a current pbuilder. We
>> already had a bunch of bug reports about packages not building with
>> Python 2.6 as default a few months ago and it was a mess to setup a
>> pbuilder to build with Python 2.6 as default [1]. The solution is easier
>> now but not documented (to the best of my knowledge).
thanks for sharing your tips! I did mine in #571551
> For whoever may be interested, I use this hook for pbuilder:
>
> ,[ /etc/pbuilder/hooks/A10python2.6 ]
> | #!/bin/sh
> |
> | [ ! -f /usr/bin/python ] || {
> | apt-get install -y --force-yes python2.6
> | ln -sf python2.6 /usr/bin/python
at least you need also
ln -sf python2.6-dbg /usr/bin/python-dbg
for those packages needing a debugging-enabled interpreter.
> | sed -i 's/^default-version =.*/default-version = python2.6/g' \
> | /usr/share/python/debian_defaults
> | }
> `
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/8b2d7b4d1002281453t4912e058w442d40b3252cb...@mail.gmail.com
Re: RC severity for Python 2.6 related bugs
On Tue, Mar 2, 2010 at 16:13, Yaroslav Halchenko wrote: > > On Sun, 28 Feb 2010, Sandro Tosi wrote: >> I absolutely agree with this (even though, for those packages that >> byte-compile the files they install, it's a smaller problem) and I >> fear there are several situations where there are hidden bugs only >> discovered with (long) *usage* of a system with 2.6 as default: >> waiting to do the switch, doesn't help to release a better squeeze, >> only a worst and buggier one. > Well, to catch those we have an extended army of beta-testers: > users of recent Ubuntu releases with 2.6 as default -- for me they > managed to hit 2.6 issues with fail2ban so upstream could resolve them > promptly year(s) before 2.6 to become the default in Debian ;) yeah, because our beloved python maintainer did the switch in Ubuntu first, instead of in Debian (and ah, right after 9.04 freeze started, releasing a mess, still present in 9.10)) > So, it might be worth for python package maintainers to have a peek at > their packages in Ubuntu to see if they got something fixed without > reporting upstream/ but I'd like to remember to critically (in the positive sense) review the patches and only apply them if they are worth: there were several clueless patches to fix 2.6 bugs. >> Additionally, as a side note, unstable is "unstable" by definition: >> its users knows it, and if something breaks in it, it will either be >> fixed or not in stable, so "break users apps" problem is less >> appealing (even though it exists). > although I totally agree with description of 'unstable', in reality, the > path from unstable into stable, closer to freeze it is, is shorter -- > just 10 days to migrate from unstable into testing. For the packages > with low users count it becomes more important since it becomes unlikely > that an important bug would get detected that rapidly So > lets switch to 2.6 now so we have more time! Exactly my point. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1003020721v230ccdc7w470431d07dc99...@mail.gmail.com
Re: python 2.6 deb for lenny ?
Hello Hermann, On Tue, Mar 30, 2010 at 17:00, Hermann Lauer wrote: > Dear pythonists on debian, > > probably this is not the right place, but knows anybody of > a way to build .deb packacks for python 2.6 on lenny ? The usually right move would be to write to the package maintainer. But given Python maintainer doesn't talk to anybody, you did the right choice and contacted us. > Installing 2.6 from testing fails after unpackaging in the scripts if you can cut&paste the error would be better. > and compiling the deb-source from testing fails in the documentation > with sphinx errors (see below. similar errors with lennys sphinx deinstalled, > which 0.4 is said to bee to old) you should backport also python-sphinx from testing/unstable to lenny, maybe also python-docutils. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1003300951u584107fdm6578be6933df2...@mail.gmail.com
Re: python 2.6 deb for lenny ?
Hello Hermann, On Wed, Mar 31, 2010 at 00:19, Hermann Lauer wrote: >> > and compiling the deb-source from testing fails in the documentation >> > with sphinx errors (see below. similar errors with lennys sphinx >> > deinstalled, >> > which 0.4 is said to bee to old) >> >> you should backport also python-sphinx from testing/unstable to lenny, >> maybe also python-docutils. > > Ok, compiling with python-sphinx 0.6.3-1~bpo50+2 worked ! cool > So the attached > build dependency patch has to be added. But the installation fails again > until I upgraded python-central to the testing version. So there are > more dependencies or a conflict to be added to python2.6-minimal. the people reading debian-python@lists.debian.org is not maintaining python2.6 (it's a bit conter-intuitive but that's it ;) ) so you should file a bug against python2.6 package so that the maintainer can fix it (not sure if he will, tho ). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8b2d7b4d1003302219g5267b1cdr5d6f59f314725...@mail.gmail.com
Re: source format 3.0
Hi Michael, On Thu, Apr 1, 2010 at 11:43, Michael Fladischer wrote: > As I'm using source format 3.0 for my packages, I discovered today that > svn-buildpackage does not support the new format. Am I right with this one? svn-inject doesn't support it (yet), but svn-bp should. > I've found #388567 whch contains a patch. How do you handle the new > format? Did you apply the patch? Is there another way? just prepare the first package in 1.0 format, inject and then switch to 3.0 Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/x2m8b2d7b4d1004010249nd053ba22rbcce497b18d2f...@mail.gmail.com
How to properly provide packages for python3.x
Hello, I've seen that some modules/extensions are starting to ship python3- packages, thus allowing to be installed for python3.x interpreter. Well, I didn't see a discussion about that so I'm starting one right away. In particular I'd want to ask: - was there a discussion and I simply don't remember about it? - do the python helper tools support python3 packages? - how to do that properly? simply build with python3.x and then ship the /usr/lib/python3.x/ dir? - shouldn't we just try to organize how to do that before creating such packages and then impose their structure/method because "we are already doing it this way" (in particular because the python maintainer was the first to ship py3 mod/ext for his packages)? Thanks & Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/n2z8b2d7b4d1004132220z3f62ed5fgd937e24eb2ef0...@mail.gmail.com
Re: python-twisted-core not getting updated on i386, but is updated on amd64 [was Re: Increasing number of conflicts]
Hello, On Wed, Apr 21, 2010 at 07:41, Rick Thomas wrote: > > On Apr 20, 2010, at 2:30 AM, Jimmy Johnson wrote: > >> If I was you I would start by finding out why python-twisted-core is not >> getting upgraded to the latest version that's in the repos and so on, with a >> little investigating I'm sure you will find what has broken your system, it >> may help to use Synaptic to look at the packages. > > > The reason seems to be that python-twisted-core version 10.0.0-3 is > available on amd64 Sid, but on i386 Sid it's only available at version > 10.0.0-2 . > > Maybe it needs to be rebuilt for i386 ? I've added in the loop the i386 buildd maintainers, so that they can give twisted a look (it's in Uploaded for 16d). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/h2n8b2d7b4d1004202358v1325296m7cb37b85d719...@mail.gmail.com
Re: join to python-x
On Tue, May 11, 2010 at 08:46, Sameer Rahmani wrote: > hi , > i'm new. i want to join python-module or python apps team to start > working on debian, how can i join one of these team ? http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i2h8b2d7b4d1005102355l2daed16cv134f83c44939e...@mail.gmail.com
Re: Python talks at DebConf
On Tue, May 11, 2010 at 19:51, Lino Mastrodomenico wrote: > Disclaimer: I'm a Python developer, not a package maintainer, so take > what I write with a grain of salt. > > 2010/5/10 Piotr Ożarowski : >> Why I think derivatives should not add new versions? >> * because it's mostly chasing numbers - I'm pretty sure there are not >> more than 10 packages that require Python >= 2.6 and are not easy to >> port to 2.5 in Ubuntu 10.04, > > Applications and libraries still widely supporting 2.5 doesn't > necessarily mean that Python developers are happy with it and 2.6+ is > not really required. In many cases it's just that there are too many > end users that only have 2.5 to drop backward compatibility with it. > > I'm NOT complaining about the 2.5->2.6 transition, I understand that > maintaining a distro with so many packages and a very high quality is > extremely difficult, but keeping up with the upstream Python releases > IMO it's not just "chasing numbers", see the changelogs for Python 2.6 > and 2.7. Indeed, that's what we expect from the python maintainer: - understand what changes between to major release - prepare a draft for the transition, checking packages that brake (reporting bugs and hopefully patches) - get consensus from the project (release team for formal ACK on starting the transition and from python community to support the transition with uploads and so) none of that has happened in the past. > A simple example: the b"foo" syntax. Apparently it's completely > useless in Python 2.x, since it's equivalent to "foo". But using it in > Python 2.x code makes supporting both 2.x and 3.x much easier since > 2to3 can use these "annotations" to decide whether a constant should > be converted to bytes or to a (unicode) string. > > So, yes, most programs will work with the Python version that's the > default in Debian stable, but that doesn't necessarily mean that using > an old version as default is harmless. It may prevent Python > developers from using new features they like. > > And there are many (mostly minor) bugs in 2.5 fixed in 2.6 that will > never be fixed in 2.5.x, similarly there are bugs in 2.6 that are only > fixed in 2.7 (e.g. the infamous DeprecationWarning for md5, sha1, > os.popen2, etc. in 2.6 are disabled by default in 2.7: no need to show > them to the end users since these modules will never be removed from > Python 2.x). > > [...] >> or no fixes at all (>100 packages that FTBFS, ignoring broken >> XS-Python-Version or debian/pyversions, packages that build >> correctly, pass all tests... and do not work[1]), > > Why is upgrading to a new default Python so difficult, more than 19 > months after 2.6 was released? because we have a quite "original" python maintainer, that doesn't care at all about Debian. On the other hand, he does care (to a certain point) about Ubuntu using the latest python version possible, of course not handling all the problems that that version can cause. Ah, just for the sake clarity: the Debian and Ubuntu python maintainers are the same person. > Are upstream programs badly written, e.g. relying on undocumented > implementation details of a particular Python version, and their > authors never fixed them? Sometimes (as in abandoned softwares, that we still maintain since we have users using them); sometimes there are package maintainer that didn't upgrade to the latest version, so we don't have the code to support a new version (even though the upstream authors released it) > Is the problem using an old version of a package while the more recent > upstream versions have already fixed the compatibility problems? yep, sometimes, but there are also new upstream release that drop support to a version to add support to a newer one, and we have to support them both. > Are Guido & c. way too happy to break backwards compatibility without > understand how many problems they are creating in the real world? > Should they be warned to be much more careful? > > Are there old unmaintained Debian packages or patches that > unnecessarily introduced incompatibilities, e.g. by hardcoding version > numbers? No, I don't think those are the problems. > I apologize if all this has already been discussed, but I hope that no problem. > the future transition to 2.7 and eventually to 3.x could be less > labour-intensive than the one to 2.6. Well, we hope several things will change on the python side of Debian; let's see if our dreams will come true. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/m2l8b2d7b4d100557le6090660ydae0e6a0cf097...@mail.gmail.com
Re: Python talks at DebConf
Hello anatoly, I'm quite tired of your emails where you're only capable of attacking without being able to provide valuable contributions to Debian. from my POV, if you don't like know we do things, then help us fix them and STOP complaining; otherwise, simply choose another distribution and leave us alone. On Tue, May 18, 2010 at 22:42, anatoly techtonik wrote: > On Mon, May 10, 2010 at 2:23 PM, Piotr Ożarowski wrote: >> >> Why I think derivatives should not add new versions? >> * because it's mostly chasing numbers - I'm pretty sure there are not >> more than 10 packages that require Python >= 2.6 and are not easy to >> port to 2.5 in Ubuntu 10.04, > > Backporting is a waste of time, Python 2.6 adds new tasty useful > functions that I use for my packages and do not want to support Python > 2.5. I won't add them to Debian, because: > > 1. No Python 2.6 > 2. I still do not know how > 3. Non-Python toolchain is obscure > 4. I do not feel like to wasting time learning Debian Policy Tomes > 5. I already know virtualenv So, given you're not interested in debian, why are you bothering us? on the other hand, if you are interested in debian, why don't you stop keep complaining and start giving help? for example by completing the transition from 2.5 to 2.6? Of course, if it's not a too big waste of your previous time... >> - breaking perfectly valid XS-Python-Version or debian/pyversions, > > Sorry, I am not DD. What is this perfection for? what question is this? if you know know what those concepts are, just google for them; if you know what they are, change their values just because it "seems" to fix the package is the wrong way to go. >> - hardcoding "-I /usr/include/python2.6" in debian/rules (yes, 2.5 was >> still in supported when I saw it) >> or no fixes at all (>100 packages that FTBFS, ignoring broken >> XS-Python-Version or debian/pyversions, packages that build >> correctly, pass all tests... and do not work[1]), > > Looks like a major failure of Debian to be a common base for > derivative distributions for Python apps. So help us fix it: complaining is not an option. >> * because new version often means changes in helper tools (cdbs, >> debhelper, python-central, python-support) and you're risking the >> situation where we will not like your implementation and will rewrite >> them in incompatible way (and that will mean you will have to rewrite >> them again), > > That's why helper tools should be Python based and crossplatform, like > the Python itself. No, helper tools must be compatible with Debian package build system, python happens to be the programming language of some of our packages, like java, C, perl and tons of others; oh, make and perl are cross-platform too. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikdar8nrhnrrkfu9ki9jelhog8geybcen0ee...@mail.gmail.com
