Le lun 28 août 2006 08:33, Steve Langasek a écrit :
> On Sat, Aug 26, 2006 at 11:18:15AM +0200, Josselin Mouette wrote:
> > Le vendredi 25 août 2006 à 17:09 -0700, Steve Langasek a écrit :
> > > > As long as these fields don't even have clear semantics,
> > > > implementing them is, at best, useles
Le lun 28 août 2006 09:12, Pierre Habouzit a écrit :
> so to me, the harm looks quite small, given the fact that my
> current experiments show that only a few packages do have an upper
> bound, and do not use XS-P-V already.
the list of suck packages (run on a fresh local miror) is:
avahi
Le samedi 26 août 2006 à 16:12 +0200, Floris Bruynooghe a écrit :
> You'll never need to update a package for just modifying the P-V
> fields.
Why use the future tense? This has already happened. Dozens of packages
were NMUed to add these fields while this was not necessary. Most of
these packages
Le dimanche 27 août 2006 à 23:33 -0700, Steve Langasek a écrit :
> > As they are fundamentally broken (especially by bringing things at the
> > package level when they should have stayed at the module level), the
> > best fix is to remove them instead of asking package maintainers to
> > change all
Le dimanche 27 août 2006 à 19:12 +0200, Adeodato Simó a écrit :
> bzrtools > 0.9 does not put files under /usr/lib/python2.4, since it
> uses python-support; and its maintainer scripts for < 0.9 did not
> bytecompile the modules, so the most plausible explanation for .pyc
> files in /usr/lib/python
On Mon, Aug 28, 2006 at 09:53:20AM +0200, Josselin Mouette wrote:
> Le dimanche 27 août 2006 à 23:33 -0700, Steve Langasek a écrit :
> > the questions of their utility likewise seems
> > to have only been raised in private. I think you have tried to kill off
> > these fields because you personally
Le lundi 28 août 2006 à 09:12 +0200, Pierre Habouzit a écrit :
> While working on the tool I promised I'll work on, I indeed agree that
> the debian/pyversions beeing hidden is a major PITA.
I'm afraid that looking for this information in debian/pyversions is not
going to give any better results
Le lun 28 août 2006 12:27, Josselin Mouette a écrit :
> Le lundi 28 août 2006 à 09:12 +0200, Pierre Habouzit a écrit :
> > While working on the tool I promised I'll work on, I indeed agree
> > that the debian/pyversions beeing hidden is a major PITA.
>
> I'm afraid that looking for this information
On Mon, Aug 28, 2006 at 09:53:20AM +0200, Josselin Mouette wrote:
> Le dimanche 27 août 2006 à 23:33 -0700, Steve Langasek a écrit :
> > changing from day to day in unstable. I have never heard anyone object that
> > any single proposal was too complicated.
> This is the general impression I get
tags 380914 + help
quit
Hi,, I need help with this migration.
I did all steps that are in
http://wiki.debian.org/DebianPython/NewPolicy
When I run lintian
If I put python as dependence, I receive a msg showing duplicated
python dependence.
And if I just ${python:Depends} I receive msg that I
tags 380914 + patch
thanks
Attached patch will only make necessary changes for the new python
policy, some other issues still has not been resolved, i.e.
* old Standards-Version
* missed space before Homepage pseudo header (dev ref 6.2.4)
* file permission problems, after saving scores I'm getti
11 matches
Mail list logo
