http://hendry.iki.fi/debian/unstable/flup_0.2015-1_i386.changes
sam$ sudo dpkg -i python-flup_0.2015-1_all.deb
(Reading database ... 133811 files and directories currently installed.)
Preparing to replace python-flup 0.1968-1 (using python-flup_0.2015-1_all.deb)
...
Unpacking replacement python-f
http://hendry.iki.fi/debian/unstable/webpy_0.138-2_i386.changes
I am a little wary of the new lintian error rule to build depend on
python-all-dev|python-dev|python
What should I be using in my package's case? Could someone clarify. I
have read the new policy, though perhaps I missed something.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kai Hendry wrote:
> http://hendry.iki.fi/debian/unstable/flup_0.2015-1_i386.changes
>
> sam$ sudo dpkg -i python-flup_0.2015-1_all.deb
> (Reading database ... 133811 files and directories currently installed.)
> Preparing to replace python-flup 0.1968
Kai Hendry writes:
> http://hendry.iki.fi/debian/unstable/flup_0.2015-1_i386.changes
> python-flup: Depends: python (>= 2.4) but 2.3.5-10 is to be installed
> E: Unmet dependencies. Try #apt-get -f install# with no packages (or specify
> a solution).
> sam$
>
> Do you know how I am supposed to
On 2006-06-19T09:45+0200 Matthias Klose wrote:
> flup was probably built with python as found in experimental.
It was built on unstable.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Adeodato =?utf-8?B?U2ltw7M=?= writes:
> Hi,
>
> I noticed that python-crypto had undergone the new Python Policy
> transition thanks to a NMU from Matthias Klose [1]. However, I could not
> update to this version, since python2.4-paramiko Depends: python2.4-crypto,
> but the new python-crypto pack
Adeodato Simó ([EMAIL PROTECTED]):
> Hi,
>
> I noticed that python-crypto had undergone the new Python Policy
> transition thanks to a NMU from Matthias Klose [1]. However, I could not
> update to this version, since python2.4-paramiko Depends: python2.4-crypto,
> but the new python-crypto package
On Mon, Jun 19, 2006 at 04:49:10PM +0900, Kai Hendry wrote:
> On 2006-06-19T09:45+0200 Matthias Klose wrote:
> > flup was probably built with python as found in experimental.
> It was built on unstable.
By whom?
There is no such package in unstable. It is certainly possible to *build*
a package
Steve Langasek ([EMAIL PROTECTED]):
> On Mon, Jun 19, 2006 at 04:49:10PM +0900, Kai Hendry wrote:
> > On 2006-06-19T09:45+0200 Matthias Klose wrote:
> > > flup was probably built with python as found in experimental.
>
> > It was built on unstable.
>
> By whom?
>
> There is no such package in un
On Mon, Jun 19, 2006 at 10:22:17AM +0200, Piotr Ozarowski wrote:
> Steve Langasek ([EMAIL PROTECTED]):
> > On Mon, Jun 19, 2006 at 04:49:10PM +0900, Kai Hendry wrote:
> > > On 2006-06-19T09:45+0200 Matthias Klose wrote:
> > > > flup was probably built with python as found in experimental.
> > > It
Steve Langasek ([EMAIL PROTECTED]):
> > > There is no such package in unstable. It is certainly possible to *build*
> > > a package against unstable which depends on python (>= 2.4), but such a
> > > package is not installable in unstable right now and therefore unsuitable
> > > for upload.
>
> >
* Matthias Klose [Mon, 19 Jun 2006 09:54:27 +0200]:
> > I prepared a python-crypto NMU to fix this, but before uploading I
> > had a look
> please do, please fix the rules file as well.
Except that I can't see what's missing in the rules file, sorry. Other
than that, I left the .changes file sig
* Josselin Mouette ([EMAIL PROTECTED]) [060618 11:13]:
> * Automatic dependency generation in dh_pysupport, removing the
> need to run dh_python.
You mean, this change breaks compatibility with the previous versions of
python-support? I strongly recommend to not make such a change.
* Josselin Mouette ([EMAIL PROTECTED]) [060618 23:56]:
> Le dimanche 18 juin 2006 à 23:12 +0200, Raphael Hertzog a écrit :
> > This sucks because:
> > - you didn't voice any concern when I worked on dh_python
> > - you have let me NMU debhelper for that dh_python and then you work
> > against it
Coin,
Ron Johnson <[EMAIL PROTECTED]> writes:
> Making a symlink from python2.4 to python would probably do the trick.
Are you root of the world and gonna do this ugly hack on every computer
on earth ???
Now please stop with the python symlinks, this has no common sense ;
you're giving bad ide
Le lundi 19 juin 2006 à 12:09 +0200, Andreas Barth a écrit :
> * Josselin Mouette ([EMAIL PROTECTED]) [060618 11:13]:
> > * Automatic dependency generation in dh_pysupport, removing the
> > need to run dh_python.
>
> You mean, this change breaks compatibility with the previous versio
Le lundi 19 juin 2006 à 12:15 +0200, Andreas Barth a écrit :
> Don't you think it might be a good idea to explain the policy better if
> it is not understood correctly?
If high-grade developers need explanations, you can't expect the policy
to be widely understood in the long term.
> Also, please
Coin,
Andreas Barth <[EMAIL PROTECTED]> writes:
> Don't you think it might be a good idea to explain the policy better if
> it is not understood correctly? (And you might remember that I did such
> suggestions for the policy already.)
Even the CDBS class was not as easy to use as i wanted, this
* Josselin Mouette ([EMAIL PROTECTED]) [060619 13:03]:
> Le lundi 19 juin 2006 à 12:09 +0200, Andreas Barth a écrit :
> > Eh, I'm sure you can explain where somebody messed up with dpkg's
> > database? What you can see is "only" that some programs postinst failed
> > to run successfully. You can ge
* Josselin Mouette ([EMAIL PROTECTED]) [060619 13:12]:
> Le lundi 19 juin 2006 à 12:15 +0200, Andreas Barth a écrit :
> > Don't you think it might be a good idea to explain the policy better if
> > it is not understood correctly?
>
> If high-grade developers need explanations, you can't expect the
Hi,
* Marc Dequènes ([EMAIL PROTECTED]) [060619 13:17]:
> Andreas Barth <[EMAIL PROTECTED]> writes:
>
> > Don't you think it might be a good idea to explain the policy better if
> > it is not understood correctly? (And you might remember that I did such
> > suggestions for the policy already.)
>
Le lundi 19 juin 2006 à 13:28 +0200, Andreas Barth a écrit :
> > Calling /bin/false doesn't entirely break the system.
>
> It seems that you are unaware with the way dpkg works. If a package's
> postinst fails, the package is marked is unconfigured. Any dependent
> packages are also not configured
On Mon, 19 Jun 2006, Andreas Barth wrote:
> > * Automatic dependency generation in dh_pysupport, removing the
> > need to run dh_python.
>
> You mean, this change breaks compatibility with the previous versions of
> python-support? I strongly recommend to not make such a change.
Jos
Andreas Barth <[EMAIL PROTECTED]> writes:
> I'm always all for improving things. I just don't see it as right
> solution to break stuff and expectations. If one wants to improve
> policy, IMHO the way to go is to send out a mail like "possible
> improvements to policy". (And, BTW, I *definitly* do
Andreas Barth <[EMAIL PROTECTED]> writes:
> Can't we have both? Actually, I think a policy is quite an important
> tool because it shows definitly what one can expect from a package. Of
> course, policy can be changed, but just ignoring policy is only breaking
> expectations. And if you want to ch
Raphael Hertzog writes:
> Indeed but the number of postinst failures due to python-central have been
> quite high recently. python-central is quite new and nobody helped
> doko to test it... so it's self-evident that we would run into some
> problems while it matures. doko has been very responsive
On Mon, Jun 19, 2006 at 04:13:52PM +0900, Kai Hendry wrote:
> I am a little wary of the new lintian error rule to build depend on
> python-all-dev|python-dev|python
>
> What should I be using in my package's case? Could someone clarify. I
> have read the new policy, though perhaps I missed somethi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Dequènes (Duck) wrote:
> Coin,
>
> Ron Johnson <[EMAIL PROTECTED]> writes:
>
>> Making a symlink from python2.4 to python would probably do the
>> trick.
>
> Are you root of the world and gonna do this ugly hack on every
> computer on earth ???
I would like to announce the initial public release of stdeb, which may
be found at http://stdeb.python-hosting.com/ . I send this email to the
debian-python list with a little hesitation because I know this utility
does not (yet) produce Debian source packages that adhere to Python
Python policy.
Hi all,
given that nobody complained to my proposal of last evening, I went ahead
and implemented it.
I've updated dh_python (and the upcoming debhelper NMU 5.0.37.2) here:
http://people.debian.org/~hertzog/python/
Here's what has changed in this dh_python (taken from my debhelper
changelog):
Hello,
as you may have read in the previous mail, the latest dh_python uses
a "debian/pyversions" file to find out the Python versions that the
packages supports but uses as fallback the XS-Python-Version field in
order to not break compatibility with packages that have already been
updated.
For
Ron Johnson <[EMAIL PROTECTED]> writes:
> python-flup is not an official package (yet?), so what's wrong with
> giving a bit of an ad-hoc work-around?
Because we'll see again a young maintainer giving such advice to his
bugreporter like if it was a real solution in a proper Debian system.
So ple
Coin,
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> What still needs to be done:
> - pyversions needs to be modified to not fail if the field
> XS-Python-Version is not present. He should in that case
> use the information of the debian/pyversions file. I will
> hopefully soon provide a pa
On Mon, 2006-06-19 at 19:24 +0200, Raphael Hertzog wrote:
> Hello,
>
> as you may have read in the previous mail, the latest dh_python uses
> a "debian/pyversions" file to find out the Python versions that the
> packages supports but uses as fallback the XS-Python-Version field in
> order to not b
Hello,
a last remark/discussion. Given that the XS-Python-Version field is no
more required, I think it shouldn't be mentionned as part of the official
policy but only as example on how to implement the policy with the help of
python-central.
I will update the wiki page as soon as the updated pac
* Raphael Hertzog ([EMAIL PROTECTED]) [060619 19:31]:
> a last remark/discussion. Given that the XS-Python-Version field is no
> more required, I think it shouldn't be mentionned as part of the official
> policy but only as example on how to implement the policy with the help of
> python-central.
>
Hi everyone,
I am no longer going to be involved in Python module packaging.
I've orphaned feedparser and the GStreamer Python bindings (the 0.8 and
0.10 versions). These are used by several packages, and so I hope
someone adopts them. feedparser is a pretty easy package, the GStreamer
ones aren'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Dequènes (Duck) wrote:
> Ron Johnson <[EMAIL PROTECTED]> writes:
>
>> python-flup is not an official package (yet?), so what's wrong
>> with giving a bit of an ad-hoc work-around?
>
> Because we'll see again a young maintainer giving such advice
Hello Joe.
I could be interested about adopting feedparser since I use it in a couple
programs.
Bad news are that I'm a really new mantainer and could need some initial help
(no problem about looking for a sponsor).
If you have no problems about that I'll adopt it and start working on i
Hi Andy,
On Mon, 19 Jun 2006, Andreas Barth wrote:
> We shouldn't have two vastly different ways to do it.
Life would be best if we had already taken a decision... we know this but it is
not going to happen until we have more experience with both python-central and
python-support.
> Either, XS-P
On Mon, 19 Jun 2006, Joe Wreschnig wrote:
> So you're removing one of the control fields while adding yet another
> one in your previous mail?
I'm not removing it... I'm transfering responsibility of that field
to python-central. I want dh_python to be used by everybody so that we
have sane and co
* Josselin Mouette ([EMAIL PROTECTED]) [060619 13:49]:
> Le lundi 19 juin 2006 à 13:28 +0200, Andreas Barth a écrit :
> > > Calling /bin/false doesn't entirely break the system.
> >
> > It seems that you are unaware with the way dpkg works. If a package's
> > postinst fails, the package is marked
* Joe Wreschnig ([EMAIL PROTECTED]) [060619 19:47]:
> The Python policy SGML document is available at
> http://people.debian.org/~piman/python-policy, I suggest someone with
> more patience adopts it and finds a new canonical home for it. Please
> give the first bullet point in the "Upgrade Procedu
* Raphael Hertzog ([EMAIL PROTECTED]) [060619 21:08]:
> On Mon, 19 Jun 2006, Andreas Barth wrote:
> > We shouldn't have two vastly different ways to do it.
>
> Life would be best if we had already taken a decision... we know this but it
> is
> not going to happen until we have more experience wit
On Mon, Jun 19, 2006 at 12:31:25PM -0500, Joe Wreschnig wrote:
> On Mon, 2006-06-19 at 19:24 +0200, Raphael Hertzog wrote:
> > Hello,
> >
> > as you may have read in the previous mail, the latest dh_python uses
> > a "debian/pyversions" file to find out the Python versions that the
> > packages su
On Mon, Jun 19, 2006 at 09:07:00PM +0200, Raphael Hertzog wrote:
> BTW, the syntax of the Python-Version field comes directly from
> python-central and it has not been discussed if the current syntax is the
> best needed to achieve the second point.
This is a valid point. But if it is found to b
On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> - pyversions needs to be modified to not fail if the field
> XS-Python-Version is not present. He should in that case
> use the information of the debian/pyversions file. I will
> hopefully soon provide a patch for this.
Here's a patch and the re
On Mon, 19 Jun 2006, Floris Bruynooghe wrote:
> On Mon, Jun 19, 2006 at 09:07:00PM +0200, Raphael Hertzog wrote:
> > BTW, the syntax of the Python-Version field comes directly from
> > python-central and it has not been discussed if the current syntax is the
> > best needed to achieve the second po
On Mon, 19 Jun 2006, Andreas Barth wrote:
> My impression was that we *did* a decision how to handle the
> meta-information, and just didn't decide about the implementation.
You can review the video of the BoF but I don't have time for that.
> > common denominator that I have found on which both
On Mon, 19 Jun 2006, Matthias Klose wrote:
> Raphael Hertzog writes:
> > What Josselin is criticizing is the fact that python-central heavily
> > relies on the P-V field, it looks it up in /var/lib/dpkg/status and also
> > uses /var/lib/dpkg/info/package.list to find out files to byte-compile.
> >
On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> - uses "XS-Python-Standards-Version: 0.4" as reference field to run in
> new
>policy mode. The presence of XS-Python-Version will also trigger the
> new
>policy mode (this is for short-term compatibility, it may be removed in
>
On Tue, Jun 20, 2006 at 01:34:35AM +0200, Raphael Hertzog wrote:
> On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > - uses "XS-Python-Standards-Version: 0.4" as reference field to run in new
> >policy mode. The presence of XS-Python-Version will also trigger the new
> >policy mode (this is
* Joe Wreschnig <[EMAIL PROTECTED]> [2006-06-19 12:48:22 -0500]:
> I've orphaned feedparser and the GStreamer Python bindings (the 0.8 and
> I've also put python-mutagen up for adoption. I'm upstream for this
> to a regression in Pygame/SDL) or quodlibet please let me know.
I would be intereste
* Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:02]:
> On Mon, 19 Jun 2006, Andreas Barth wrote:
> > > I only know two reasons for those headers:
> > > - python-central use them for its internal work
> > > - it may help track a transition and discover which packages need to be
> > > updated
> >
* Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:20]:
> On Mon, 19 Jun 2006, Matthias Klose wrote:
> > Raphael Hertzog writes:
> > > What Josselin is criticizing is the fact that python-central heavily
> > > relies on the P-V field, it looks it up in /var/lib/dpkg/status and also
> > > uses /var/li
* Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > - uses "XS-Python-Standards-Version: 0.4" as reference field to run in
> > new
> >policy mode. The presence of XS-Python-Version will also trigger the
> > new
> >policy mod
On Tue, 2006-06-20 at 06:49 +0200, Andreas Barth wrote:
> * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > - uses "XS-Python-Standards-Version: 0.4" as reference field to run
> > > in new
> > >policy mode. The presence of XS-P
* Joe Wreschnig ([EMAIL PROTECTED]) [060620 07:14]:
> On Tue, 2006-06-20 at 06:49 +0200, Andreas Barth wrote:
> > * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > > - uses "XS-Python-Standards-Version: 0.4" as reference field to
> >
On Tue, 2006-06-20 at 07:27 +0200, Andreas Barth wrote:
> * Joe Wreschnig ([EMAIL PROTECTED]) [060620 07:14]:
> > On Tue, 2006-06-20 at 06:49 +0200, Andreas Barth wrote:
> > > * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > > > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > > > -
On Tue, 20 Jun 2006, Andreas Barth wrote:
> * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > - uses "XS-Python-Standards-Version: 0.4" as reference field to run
> > > in new
> > >policy mode. The presence of XS-Python-Version
Le mar 20 juin 2006 06:49, Andreas Barth a écrit :
> * Raphael Hertzog ([EMAIL PROTECTED]) [060620 01:35]:
> > On Mon, 19 Jun 2006, Raphael Hertzog wrote:
> > > - uses "XS-Python-Standards-Version: 0.4" as reference field
> > > to run in new policy mode. The presence of XS-Python-Version will
* Joe Wreschnig ([EMAIL PROTECTED]) [060620 07:35]:
> What does it mean? This thread more or less started when Raphael updated
> dh_python to change behavior based on the presence/absence of the
> Python-Standards-Version field -- exactly analogous to what debhelper's
> compat levels are.
Well, I
62 matches
Mail list logo
