public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowi@redhat.com>
To: cygwin-apps@cygwin.com
Subject: Re: [Bug] python-imaging
Date: Tue, 31 Jul 2018 19:40:00 -0000	[thread overview]
Message-ID: <86d9d89723ca6608836c742f2c9e72da8d803f89.camel@redhat.com> (raw)
In-Reply-To: <87d0v3b3rj.fsf@Rainer.invalid>

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	other threads:[~2018-07-31 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 19:32 Achim Gratz
2018-07-31 19:40 ` Yaakov Selkowitz [this message]
2018-07-31 20:05   ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86d9d89723ca6608836c742f2c9e72da8d803f89.camel@redhat.com \
    --to=yselkowi@redhat.com \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).