[Bug] python-imaging

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug] python-imaging

ASSI

The package python-imaging is obsolete and replaced by python2-imaging.
However, the directory structure in the repo still has python-imaging at
the toplevel and python2-imaging as a sub-package of that.  This should
be reversed so that python-imaging is a sub-package of python2-imaging
as all other obsoletions are structured.


Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Reply | Threaded
Open this post in threaded view
|

Re: [Bug] python-imaging

Yaakov Selkowitz-2
On Tue, 2018-07-31 at 21:32 +0200, Achim Gratz wrote:
> The package python-imaging is obsolete and replaced by python2-imaging.
> However, the directory structure in the repo still has python-imaging at
> the toplevel and python2-imaging as a sub-package of that.  This should
> be reversed so that python-imaging is a sub-package of python2-imaging
> as all other obsoletions are structured.

This is not a bug, and is how many other python-foo -> python2-foo
transitions are structured.  The source package (which is top-level) is
python-foo, and the subpackages are python{2,3}-foo.

--
Yaakov Selkowitz
Software Engineer - Platform Enablement Group
Red Hat, Inc.


Reply | Threaded
Open this post in threaded view
|

Re: [Bug] python-imaging

ASSI
Yaakov Selkowitz writes:

> On Tue, 2018-07-31 at 21:32 +0200, Achim Gratz wrote:
>> The package python-imaging is obsolete and replaced by python2-imaging.
>> However, the directory structure in the repo still has python-imaging at
>> the toplevel and python2-imaging as a sub-package of that.  This should
>> be reversed so that python-imaging is a sub-package of python2-imaging
>> as all other obsoletions are structured.
>
> This is not a bug, and is how many other python-foo -> python2-foo
> transitions are structured.  The source package (which is top-level) is
> python-foo, and the subpackages are python{2,3}-foo.

Well, if you want to play it that way (I still think that an obsolete
package should _never_ be at the top level poackage directory), then at
least there should be no python-imaging-debuginfo directory and probably
a python2-imaging-debuginfo in its place.  Or better yet, python-imaging
should not be obsolete, but rather an empty package that depends on
sibling package python2-imaging.


Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada