Re: [Announce] stdeb - Python to Debian source package conversion utility
Mikhail Sobolev wrote: > Hi Andrew > > On Mon, Jun 19, 2006 at 09:16:14AM -0700, Andrew Straw wrote: > >> stdeb - Python to Debian source package conversion utility >> [ description skipped ] >> > > How stdeb differs from easy-deb (http://easy-deb.sourceforge.net/)? > Hi Misha, 1) license - stdeb is MIT, easy-deb is GPL (if I remember correctly) 2) I couldn't get easy-deb to work (easily) 3) stdeb is being actively developed/maintained (last commit yesterday). AFAICT, last commit in easy-deb was 10 months ago. I don't know about the feature list, since, as I said, I couldn't get easy-deb to work. You might want to have a look at the features I've added since the last release. I'm debugging a few details and will make a new release soon. Here's the changelog so far since the last release: 2006-07-19 Get .egg-info directory locations from setuptools rather than guessing (wrongly). 2006-07-09 Ability to specify MIME-Desktop-Files, MIME-File, and Shared-MIME-File in configuration file. 2006-07-09 Use of dh_python for generation of postinst and prerm scripts. 2006-07-05 Auto-generation of debian/postinst and debian/prerm scripts that create and remove .pyc and .pyo files. 2006-06-21 Upstream .tar.gz files can be used exactly, allowing md5sums to match. 2006-06-21 Expanded source directory is only deleted when commandline option is set. Anyhow, I'm using stdeb extensively for my own packages and it's meeting my needs pretty well. I hope others find it useful, too. Cheers! Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lilypond and python
Hi Matthias, On Thu, 20 Jul 2006, Matthias Klose wrote: > well, there's curently only one person spreading lies and fud about > python packaging, so please don't talk about "lies" as well. Please stop ranting against Josselin, in particular if you have nothing precise/factual to criticize. You're not making it easy to colloborate with you. I expect more from you. > I'm still testing uprades and fixing upgrade issues. experimental has a > python-defaults pointing to 2.4, so you can prepare your package and > upload it to experimental. "pending" doesn't imply "will be fixed in x > days". You sent an announce to debian-devel-announce announcing the upload of the new python2.4 by default more than a month ago. You're not living up to your own promise. I tried to help you in numerous ways: - I've done the new dh_python and handled the initial bugs in a timely fashion - I coordinated the discussion between you and Josselin while you refused to discuss together - I tried to help you setup a real Python team and you promised me to start using "pkg-python" SVN repository and you never did that. Now, please accept the blame of Thomas, you're late and it's your fault. You are the python maintainer and nobody is forcing you to keep that responsibility and I explicitely asked you to share it with other people having more time than you have but you haven't done anything to help that process... Would you please, accept the facts, open your eyes and start making efforts to setup a real python maintenance team? I'll gladly assist you in that process. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#378604: dh_python generates dependencies on unversioned python versions for versioned python modules
On Tue, Jul 18, 2006 at 11:53:26AM +0200, Matthias Klose wrote:
> Raphael Hertzog writes:
> > tag 378604 + patch
> > thanks
> >
> > On Mon, 17 Jul 2006, Matthias Klose wrote:
> > > Package: debhelper
> > > Version: 5.0.37.3
> > > Severity: important
> > >
> > > Looking at python2.4-schoolbell, ${python:Depends} is expanded to
> > >
> > > python-central (>= 0.5), python (<< 2.5), python (>= 2.4) | python2.4
> > >
> > > which is wrong.
> >
> > It's not really wrong... but it's not really optimized for the purpose of
> > the package.
> >
> > The package puts files in /usr/lib/python2.4/site-packages so it won't
> > work with python2.5 ... the "python (<< 2.5)" guarantees that.
> >
> > There's no script using "#!/usr/bin/python2.4" otherwise you would have
> > had a dependency "python2.4" ...
> >
> > In theory, looking at the package it should have gotten a "python (>=
> > 2.4), python (<< 2.5)" dependency however since that's not satisfiable in
> > sid right now, it has been loosened to the dependency above.
> >
> > If modules are meant for public uses, they should work with all python
> > versions and in that case the dependency they get is the right one. But in
> > this case, we have public modules which are not really meant to be used by
> > the end-user and which are only used by one application and thus compiled
> > for the version that this application uses.
>
> all the modules are for public use. however zope3 is only available
> for python2.4 (and not above), so the same is needed for packages
> depending on zope3. You have two hints that a dependency on a
> unversioned python is unwanted:
>
> - XS-Python-Version is explicitely set
> - the package is named python2.4-xxx
FYI, in the schooltool packages for the next upstream release, the
package name will take the form python-xxx.
However the XS-Python-Version will continue to be set to a subset of the
python versions of the its dependencies (zope3 being the main culprit).
--
Brian Sutherland
Metropolis - "it's the first movie with a robot. And she's a woman.
And she's EVIL!!"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
