Re: Playing with git-buildpackage
I don't have the password for http://lists.alioth.debian.org/cgi-bin/mailman/admin/python-modules-commits I've tried going through Alioth's admin UI and reset the password via https://alioth.debian.org/mail/admin/?group_id=30714. There was a Reset admin password link there. I've clicked it and now it's gone but I haven't received any email (yet?). Alioth has emailed me my own reset password link (for Alioth itself) a couple of minutes before I tried to reset the mailing list pw so it shouldn't be due to any anti-spam filter on my side. Let me know if you want me to try something else. On Sat, Aug 23, 2014 at 12:15 AM, Raphael Hertzog hert...@debian.org wrote: On Fri, 22 Aug 2014, Barry Warsaw wrote: Why would you push your temporary branch? Only because `git push --all` seems like the obvious choice. But I think git's cli is akin to quantum mechanics, i.e. don't trust your intuition. :) Ideal is when a git push alone is enough, you can do git config push.default matching to make it push all the branches that exist on both sides. That used to be the default but it's counter-intuitive... I agree it's a pity that there's no git push --matching option instead of the non-explicit git push origin :. It would be nice if the admins could whitelist all mails containing an X-Git-Repo header. In Mailman, that's easy. Or at least whitelist all *@users.alioth.debian.org emails as those are in the From of those emails. (I just changed a setting so that it uses this domain now) In Mailman, that's easy. Alternatively you can subscribe to the list with your login@users.alioth.debian.org mail and disable mail delivery for that address. In Mailman, that's easy. Anybody know the maintainer of the mailing list? http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-commits = stra...@users.alioth.debian.org aka Gustavo Franco stra...@debian.org I'm not sure if Gustavo is still active or if someone else has the admin password... Gustavo? Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- -- Gustavo stratus Franco
Re: Playing with git-buildpackage
Ok, got the email. You can see I've added the project admins as list admins and hertzog. https://lists.alioth.debian.org/mailman/listinfo/python-modules-commits Hertzog, you should be able to get the password and change any settings. Let me know if you need anything else. Thanks, On Sat, Aug 23, 2014 at 12:05 PM, Gustavo Franco stra...@debian.org wrote: I don't have the password for http://lists.alioth.debian.org/cgi-bin/mailman/admin/python-modules-commits I've tried going through Alioth's admin UI and reset the password via https://alioth.debian.org/mail/admin/?group_id=30714. There was a Reset admin password link there. I've clicked it and now it's gone but I haven't received any email (yet?). Alioth has emailed me my own reset password link (for Alioth itself) a couple of minutes before I tried to reset the mailing list pw so it shouldn't be due to any anti-spam filter on my side. Let me know if you want me to try something else. On Sat, Aug 23, 2014 at 12:15 AM, Raphael Hertzog hert...@debian.org wrote: On Fri, 22 Aug 2014, Barry Warsaw wrote: Why would you push your temporary branch? Only because `git push --all` seems like the obvious choice. But I think git's cli is akin to quantum mechanics, i.e. don't trust your intuition. :) Ideal is when a git push alone is enough, you can do git config push.default matching to make it push all the branches that exist on both sides. That used to be the default but it's counter-intuitive... I agree it's a pity that there's no git push --matching option instead of the non-explicit git push origin :. It would be nice if the admins could whitelist all mails containing an X-Git-Repo header. In Mailman, that's easy. Or at least whitelist all *@users.alioth.debian.org emails as those are in the From of those emails. (I just changed a setting so that it uses this domain now) In Mailman, that's easy. Alternatively you can subscribe to the list with your login@users.alioth.debian.org mail and disable mail delivery for that address. In Mailman, that's easy. Anybody know the maintainer of the mailing list? http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-commits = stra...@users.alioth.debian.org aka Gustavo Franco stra...@debian.org I'm not sure if Gustavo is still active or if someone else has the admin password... Gustavo? Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- -- Gustavo stratus Franco -- -- Gustavo stratus Franco
Re: Please sponsor upload of python-gdata 2.0.16
Hi Dmitry, Thanks for your help. On Thu, Mar 8, 2012 at 12:32 AM, Dmitry Shachnev mity...@gmail.com wrote: Hello! Can you please review and sponsor changes I made to python-gdata package? python-gdata (2.0.16-1) unstable; urgency=low * Team upload. * New upstream release (closes: #655566) * Switch to dh and dh_python2 * debian/patches/remove_shebangs.patch: refreshed * Switch to the newest copyright format, fix lintian warnings * Bump Standards-Version to 3.9.3 -- Dmitry Shachnev mity...@gmail.com Thu, 08 Mar 2012 12:12:18 +0400 You can find the diff here: [1]. There was some *minor* API break in this release, I wrote a patch for my retext package and emailed maintainers of other rdepends, so I think it can be safely uploaded to unstable. You can download the orig tarball using uscan or from [2], packaging is available in the svn. I hope to get bug #619428 [3] fixed in the next upload, not in this one because it's already too big, the other existing bug [4] is blocked by upstream issue. @Gustavo: Can I please change the maintainer to the team? Are you still interested in maintaining this package? Please go ahead and change it to the team. My bad for not doing it many moons ago. :) regards, -- Gustavo stratus Franco -- 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/CAAAqP6+bj37coG+SNhaA2FpTM3Ksm231y=nofcdjwtnkxxq...@mail.gmail.com
Re: Preparing for the new python-support
[+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. 2009/3/26 Josselin Mouette j...@debian.org: Hi again, with finally proper support for the dist-packages and /usr/local changes in python2.6, I think python-support should be ready to move from experimental to unstable. Unfortunately, there are still a number of packages that will break when this happens: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=j...@debian.org;tag=pysupport-transition Until there are important objections against it, I will do this move, and bump the priorities of the remaining bugs to serious. Cheers, -- .''`. Debian 5.0 Lenny has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `- me that if you don't install Lenny, he'd melt your brain. thanks, -- Gustavo stratus Franco -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Making all DD members of the team by default
On 8/4/07, Raphael Hertzog [EMAIL PROTECTED] wrote: On Thu, 26 Jul 2007, Raphael Hertzog wrote: Hello, this mail is crossposted to two mailing lists. Please reply only to the one that concerns you (perl or python team). This warning is still valid. :-) As an Alioth admin, I can add those ACL. However I'd like to have your opinion and agreement first. Both projects agreed and I just added the ACL. It would be great if some people could update the respective documentation of each project to share this information. (...) Thanks Raphael, interesting change. Piotr, would you mind update our dpmt policy, please? If you're busy with other stuff ping me. :-) thanks in advance, -- stratus http://stratusandtheswirl.blogspot.com get debian @ http://get.debian.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: News from the python policy transition
On 6/29/06, Sam Morris [EMAIL PROTECTED] wrote: On Thu, 29 Jun 2006 16:25:17 +0200, Pierre Habouzit wrote: Le mer 28 juin 2006 23:20, Raphael Hertzog a écrit : So you don't have any excuse to not update your packages any more. About 60% of the Python modules have already been updated, but 109 are left to be done: http://bugs.debian.org/from:[EMAIL PROTECTED] The bugs have been filled two weeks ago, it is now time to NMU the remaining packages where the maintainer didn't gave any update plan in the bug report. We need your help for that. I've done 16 of them already. that has also fixed 2 RC bugs as a side effect (uninstallability bugs). 7 other person like me, and it's old story ! I noticed the original list didn't include the python-gmenu package. The source package (gnome-menus) produces some regular machine code packages as well as the python module package. Perhaps there are others like this? The gnome-menus bug is #373435, i dunno if there are others without the bugs, but you're welcome to redo the scan and let us know. thanks, -- stratus
Re: installation of scripts in the brave new Python world
On 6/27/06, Joe Wreschnig [EMAIL PROTECTED] wrote: On Tue, 2006-06-27 at 20:22 -0300, Gustavo Franco wrote: On 6/27/06, Carlo Segre [EMAIL PROTECTED] wrote: Hello All: As I was trying to implement the new Python policy, I noticed an effect which is not directly addressed in the policy. That is when a package contains modules and scripts, there have to be special precautions taken to make sure that the scripts are not installed with a first line of #!/usr/bin/pythonX.Y instead of #!/usr/bin/python (...) How it's that different than patch the source packages to s/python2.4/python/ as we do actually in some cases or replacing to python2.3 when it isn't 2.4 compatible code? distutils rewrites scripts at installation time. Patching the source package will not work. http://docs.python.org/dist/node10.html That's what we do and distutils needs to be fixed, IMHO. regards, -- stratus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installation of scripts in the brave new Python world
On 6/27/06, Carlo Segre [EMAIL PROTECTED] wrote: Hello All: As I was trying to implement the new Python policy, I noticed an effect which is not directly addressed in the policy. That is when a package contains modules and scripts, there have to be special precautions taken to make sure that the scripts are not installed with a first line of #!/usr/bin/pythonX.Y instead of #!/usr/bin/python (...) How it's that different than patch the source packages to s/python2.4/python/ as we do actually in some cases or replacing to python2.3 when it isn't 2.4 compatible code? regards, -- stratus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: on packaging TurboGears 0.8.9
On 6/3/06, Gustavo Noronha Silva [EMAIL PROTECTED] wrote:
Em Sex, 2006-06-02 às 18:55 -0300, Gustavo Franco escreveu:
Hi Kov,
Hey,
I've installed python-turbogears 0.9a6-1 from your repository[0] and i
see the following error message:
[...]
pkg_resources.DistributionNotFound: TurboGears==0.9a6
Could you run a python interpreter and type the following?:
import pkg_resources
pkg_resources.require ('TurboGears')
That'll tell you exactly what's the problem, then I can fix it in the
package deps or somewhere else =).
$ python2.4
Python 2.4.2 (#2, Nov 20 2005, 17:04:48)
[GCC 4.0.3 2005 (prerelease) (Debian 4.0.2-4)] on linux2
Type help, copyright, credits or license for more information.
import pkg_resources
pkg_resources.require ('TurboGears')
Traceback (most recent call last):
File stdin, line 1, in ?
File
/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/pkg_resources.py,
line 503, in require
needed = self.resolve(parse_requirements(requirements))
File
/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/pkg_resources.py,
line 487, in resolve
raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (setuptools 0.6a9
(/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg),
Requirement.parse('setuptools=0.6a11'))
In other words, it needs python-setuptools = 0.6a11-1, but the latest
in Debian is 0.6a9-1. :)
(...)
thanks,
-- stratus
Re: on packaging TurboGears 0.8.9
On 5/18/06, Gustavo Noronha Silva [EMAIL PROTECTED] wrote: Hey! Em Sáb, 2006-05-13 às 21:42 -0300, Gustavo Noronha Silva escreveu: Comments? Bug reports to my email address, please. May I go on and upload the packages to unstable? I'll upload TurboGears 0.9 to experimental, if it is ok, 'till it is released as stable. The modules will go straight to unstable. I am planning to upload the packages this weekend. If noone is against, I'll go ahead and upload all python modules which I had to package for the 0.8 and 0.9 versions to unstable, and TG 0.9 and closely related modules to experimetal. I'll take a look at what still needs changing in current packages and file bugs if they are still in need of updating. Hi Kov, I've installed python-turbogears 0.9a6-1 from your repository[0] and i see the following error message: $ tg-admin quickstart Traceback (most recent call last): File /usr/bin/tg-admin, line 5, in ? from pkg_resources import load_entry_point File /usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/pkg_resources.py, line 2195, in ? for dist in working_set.resolve( File /usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg/pkg_resources.py, line 483, in resolve raise DistributionNotFound(req) # XXX put more info here pkg_resources.DistributionNotFound: TurboGears==0.9a6 [0] = http://people.debian.org/~kov/tg0.9/ Something related with 'eggs' ? regards, -- stratus
Re: python 2.4?
On 5/13/06, Raphael Hertzog [EMAIL PROTECTED] wrote: On Fri, 12 May 2006, Andreas Barth wrote: How about, right now, just a statement this is what the issues are. Or even, this [URL here] is the mailing list post where the issues are outlined. I forgot about them. So, I need to collect them again. Even release managers don't have a superhuman brain (though we sometimes pretend we do :). The only issue is Matthias Klose who absolutely wants to push big packaging changes at the same time[1] whereas everybody else agree that we should take our time for those changes since we managed to live with the current python policy until now. Doko wants python-central but the python modules team uses mostly python-support: http://wiki.debian.org/DebianPythonTODO I certainly hope we can discuss that IRL at Debconf. I would welcome a Python BoF. I think the Python BoF happened, so is there a thread somewhere with what was discussed, a wiki article or even a blog entry ? I trust that the guys involved took non insane decisions but i would like to know, since we've more than 50 packages to keep ok for Etch just in the Debian Python Modules Team and a lot more that i would like to give attention too out of our team. Closing, who from dpmt was there? I hope buxy was, because i think he's the only dpmt admin in mx (gpastore and i weren't). Probably others dmpt members were too. Well, break the silence and give me updates, please. :) regards, -- stratus
Re: python 2.4?
On 5/16/06, Raphael Hertzog [EMAIL PROTECTED] wrote: On Tue, 16 May 2006, Gustavo Franco wrote: I think the Python BoF happened, so is there a thread somewhere with what was discussed, a wiki article or even a blog entry ? I trust that the guys involved took non insane decisions but i would like to know, since we've more than 50 packages to keep ok for Etch just in the Debian Python Modules Team and a lot more that i would like to give attention too out of our team. Closing, who from dpmt was there? I hope buxy was, because i think he's the only dpmt admin in mx (gpastore and i weren't). Probably others dmpt members were too. Well, break the silence and give me updates, please. :) I were, Matthias Klose was, and Josselin was (and many more people like Jeroen, Anthony, Andreas, ...). The discussion has been interesting and we have a kind of new python-policy. More on that later, hopefully from someone else than me... Hopefully soon. :) Matthias has some updates on python-central on his laptop and he should upload it somewhere so that we can take a look. Ok, but what's the point here? Are we going to drop python-support usage ? Will python-central provides python-support ? Can we technically keep using both (we shouldn't IMHO!) ? We agreed to switch to python-2.4 in the week following debconf (next week that is) and go on with whatever we have at that time. Great news, i just want to have an idea now, how much work we will need to put dpmt packages in shape for release. Thanks, -- stratus
Re: python 2.4?
On 5/16/06, Josselin Mouette [EMAIL PROTECTED] wrote: Le mardi 16 mai 2006 à 17:04 -0300, Gustavo Franco a écrit : Matthias has some updates on python-central on his laptop and he should upload it somewhere so that we can take a look. Ok, but what's the point here? Are we going to drop python-support usage ? Will python-central provides python-support ? Can we technically keep using both (we shouldn't IMHO!) ? Even after the talk, I have no idea of what python-central exactly does. It is supposed to help us in building the new policy, but I don't know how exactly. http://wiki.debian.org/DebianPythonTODO points out a thread were doko explain this. In short, the main decision has been to drop entirely python2.x-foo packages. They will, however, be provided as virtual packages, but only if something actually needs them. Great news. For python-only modules, it has been decided to use python-support. The python modules team already knows it and won't have anything to change in such packages. The necessary code for dh_python will be back soon. Well, i'm part of the dpmt and it wasn't really decided to stick with python-support after/while moving to python 2.4. I've recommended the group pick python-support for python-only modules because the pythonX.X-foo thing sucks, and it was clear that we were going to get rid of that. Of course, the python-support solution seemed to be a good one instead use python-all-dev and keep wit the versioned packages until 2.4 and after that start the move. buxy that is other group admin agreed too (based on my opinion about his words and wiki article). For C extensions, it was decided to build them for all available python versions in a single python-foo package. For example, currently we have python2.3 and python2.4. The package would contain /usr/lib/python2.[34]/site-packages/foo.so and depend on python (= 2.3), python ( 2.5). The python-all-dev package will be used to build this. Sounds good. Any comment about the policy changes and where python-central will fit there? Meanwhile, i'll check if dpmt group's policy needs update. regards, -- stratus
Re: importing a project currently under darcs into python-modules svn repo
On 5/3/06, Panu Kalliokoski [EMAIL PROTECTED] wrote: I have this Python package, python-selecting, which I'm also the upstream of and which I've been tracking is a Darcs repository. The instructions in http://python-modules.alioth.debian.org/python-modules-policy.html say that I should only bring in the debian/ files, preferably with svn-inject, and leave the .orig.tar.gz outside svn. There are some gotchas: - if I import the project with svn-inject, I'll lose the VC history from the darcs side for svn - I need to have some place to track the upstream source anyway What is the right way to approach this? I can think of some alternatives: Hi Panu, It would be better (as you pointed out) if you treat yourself as a different person and keep the upstream code in darcs with its current history intact. Just import the debian/ in dpmt svn repository, because it's possible that others will touch this part of the package too. With or without the current history, because when we import it 'from scratch' there's no history at all. Thanks, -- stratus
Re: python modules circular dependencies
On 4/20/06, Bill Allombert [EMAIL PROTECTED] wrote: Hello Debian Python packages Maintainers, From http://debian.semistable.com/debgraph.out.html, there are a number of Python libraries that are packaged in a way that create circular dependencies: (...) Thanks Bill. Btw, couldn't we just open bugs against these packages ? Cheers, -- stratus
Re: New python maintenance team
On 4/12/06, Bob Tanner [EMAIL PROTECTED] wrote: Raphael Hertzog wrote: (Please request the removal of pkg-turbogears on alioth once you don't need it any more) Waiting on confirmation and then I'll submit the remove request. Please, move cherrypy from pkg-turbogears svn repository first. :-) Thanks, -- stratus
Re: Joining the Python modules team
On 4/12/06, Torsten Marek [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'd like to join, too. Please add my account (shlomme). I bring in ElementTree, cElementTree and ElementTidy (currently in the NEW queue). Hi Torsten, Welcome to the python-modules! I've added you on the group at alioth. Any doubt or suggestion, ask us here. Thanks, -- stratus
Re: Joining the python modules team
On 4/12/06, Jan Lübbe [EMAIL PROTECTED] wrote: Hi! I'm currently in the NM-Process and maintain the packages python-pysnmp2 and pida. I'd like to join the python-modules team to help with comaintaining the packages. My alioth login is jluebbe-guest. Hi Jan, Welcome to the python-modules! You've svn commit access, so you're free to upload the packages you're maintaining to our repository. Read our policy, and if you've doubts or suggestions post it here or contact us at irc.oftc.net - #debian-python. Thanks, -- stratus
Re: Python-modules policy document + announce
On 4/11/06, Bob Tanner [EMAIL PROTECTED] wrote: Raphael Hertzog wrote: Hello everybody, I completed the documentation of the python-modules alioth project. How does this new project effect existing projects like pkg-turbogears? Good question. You can keep with pkg-turbogears (btw, what's the status?) and we (python-modules) shouldn't touch your stuff or if all the pkg-turbogears group members agree we can merge our efforts. Btw, i've just asked about turbogears in #debian-python (irc.oftc.net) and found the ITP and the alioth group. :-) -- stratus
Re: New python maintenance team
On 4/11/06, Piotr Ozarowski [EMAIL PROTECTED] wrote: Raphael Hertzog ([EMAIL PROTECTED]): Yeah, pkg-python would be just core python. But python-modules is more general purpose. Just want to make sure I understand the thread, python package projects, like pkg-turbogears are to remain separate? But I would really like turbogears maintained within python-modules since it's mainly good glue between several general-purpose Python modules. Does gaupol [1] qualify? It is rather standalone application than a python module but I would be glad to join the group. Hi Piotr, The simple rule is that if i can import gaupol and it will be really useful for any other python application (packaged or not), it could be into the team. I think that gaupol itself don't qualify, but what's the status of pyenchant ? It's a gaupol dependency, right ? Sounds like a python-modules valid candidate. Thanks, -- stratus
Re: Hypothetical pkg-python alioth project
Raphael Hertzog wrote: On Mon, 27 Mar 2006, Gustavo Franco wrote: python-modules is on hold for me, because i need some time to finnish our policy[0] discussing it with the current members. If somebody maintaining python modules wants to join the team and help with the documentation tell me then i'll reorganize this project in my own TODO, preparing a useful website and doing an announcement. Please add me to the project, I can help finish what's needed. There's really not many things to do given that pkg-perl has already written all the required documentation. hertzog account added, thanks! Btw, i wrote part of the pkg-perl documentation and we still lack (in both projects) some of the needed stuff. See the drafted python-modules policy i wrote. Here are my remarks however: debian-python@lists.debian.org should be the main discussion list and [EMAIL PROTECTED] should be the the contact info that we put into the Maintainer or Uploader field. I agree, and we already do that except for that [EMAIL PROTECTED] wasn't our main discussion list. This scheme works well: people with broad interest can subscribe to both lists and mark the adress of the team as maintainer field on their packages. Maintainers who want to maintain a few python modules of special interest for them within the team can keep their name in the Maintainer field and just put the team in the uploaders field (that way the package is listed on the DDPO page of the team). Sure, please write that in the policy. I would like to discuss the policy with the group members before an announcement and we need to define a procedure for new members approval. Suggestions are welcome. Thanks, Gustavo Franco - [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hypothetical pkg-python alioth project
Paul Wise wrote: On Tue, 2006-03-28 at 01:16 +0200, Carlos Galisteo wrote: (...) Anyone knowing about this project status? We have some packages in SVN[1] (and one package in debian). Only a few people involved[2]. We have yet to do a proper website[3], announcement and callout. (...) python-modules is on hold for me, because i need some time to finnish our policy[0] discussing it with the current members. If somebody maintaining python modules wants to join the team and help with the documentation tell me then i'll reorganize this project in my own TODO, preparing a useful website and doing an announcement. Btw, i'm more active in pkg-ltsp and pkg-gnome atm. I was planning to do some debtags and python-modules work in May. [0] = http://svn.debian.org/wsvn/python-modules/www/python-modules-policy.rst?op=filerev=0sc=0 Thanks, Gustavo Franco [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
