public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Achim Gratz <Stromeko-i47jiTeKxPI@public.gmane.org>
Subject: Re: [HEADSUP] requires to obsolete Perl packages
Date: Thu, 17 Dec 2015 17:03:00 -0000	[thread overview]
Message-ID: <5672EAF7.5020401@dronecode.org.uk> (raw)
In-Reply-To: <87egel11f1.fsf@Rainer.invalid>

On 17/12/2015 16:32, Achim Gratz wrote:
> Achim Gratz writes:
>> Achim Gratz writes:
>>>> There are a number of packages still requiring obsoleted Perl packages
>>>> that I want to delete now, so these setup.hint files need to be fixed.
>>>> Here is what I've found so far with a proposed replacement in
>>>> parenthesis.
>>>>
>>>>
>>>> perl_vendor (only on 32bit since it never existed on 64bit):
>>>> ===========
>>>> docbook2X			(perl-XML-SAX)
>>>> fvwm, xmltoman	        (perl-XML-Parser)
>>>> intltool, svn_load_dirs	(perl-URI)
>>>> snownews			(perl-XML-LibXML)
>>>> html2ps	                (perl-HTTP-Cookies perl-HTTP-Message)
>
> libexo1_0                       (perl-URI)
> pl                              (I have no idea where this even uses Perl)
>

Thanks for the list.

I've restored the upgrade helper perl_vendor until this can be resolved.

Please ping the individual package maintainers to get the hints fixed.

  reply	other threads:[~2015-12-17 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-01  9:25 Achim Gratz
2015-09-26 10:07 ` Achim Gratz
2015-11-24 18:52 ` Achim Gratz
2015-12-17 16:23   ` Achim Gratz
2015-12-17 16:32     ` Achim Gratz
2015-12-17 17:03       ` Jon Turney [this message]
2015-12-17 18:28         ` Please fix your setup.hint files (was: [HEADSUP] requires to obsolete Perl packages) Achim Gratz
2015-12-17 20:12           ` Corinna Vinschen
2015-12-17 20:22             ` Please fix your setup.hint files Achim Gratz
2016-01-29  6:24 ` [HEADSUP] requires to obsolete Perl packages Yaakov Selkowitz
2016-01-29 19:13   ` 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=5672EAF7.5020401@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Stromeko-i47jiTeKxPI@public.gmane.org \
    --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).