From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [Attn. MAINTAINERS] Heads up: Perl 5.36.1 is imminent
Date: Sun, 7 May 2023 13:39:17 +0200 [thread overview]
Message-ID: <4e1301f5-9bc0-fd85-fb38-fb78480e6317@gmail.com> (raw)
In-Reply-To: <fc033db1-2965-6e81-0fc1-2657c709cd89@dronecode.org.uk>
On 06.05.2023 15:12, Jon Turney wrote:
> On 06/05/2023 06:37, Marco Atzeri wrote:
>> On 05.05.2023 22:44, Jon Turney wrote:
>>> On 05/05/2023 21:15, Marco Atzeri via Cygwin-apps wrote:
>>>> On 02.05.2023 21:47, Achim Gratz via Cygwin-apps wrote:
>>>>> Achim Gratz via Cygwin-apps writes:
>>>>>> I'm going to release Perl 5.36.1 to Cygwin in a few days.
>>>>>
>>>>> Done.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Achim.
>>>>
>>>> I do not succeed to upgrade.
>>>> Setup complains that perl 5.36.1 requires perl_0536 but
>>>> nothing provides it
>>>
>>> Please can you run setup with '-v', and mail me the setup.log.full?
>>>
>>
>> attached
>
> Thanks.
>
> It looks like the conflict is over subversion-perl, which has yet to be
> rebuilt.
>
> If you uninstall that, you should be able to upgrade perl.
>
> I'm not quite sure why that's not indicated as a possible solution in
> the dependency conflict report.
>
only pratical solution seems to force perl and perl_base upgrade
so I can now work to upgrade the packages with perl dependecy
Regards
Marco
next prev parent reply other threads:[~2023-05-07 11:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 20:00 Achim Gratz
2023-05-01 20:28 ` Marco Atzeri
2023-05-02 6:36 ` ASSI
2023-05-02 19:47 ` Achim Gratz
2023-05-05 20:15 ` Marco Atzeri
2023-05-05 20:44 ` Jon Turney
[not found] ` <43354da8-65cc-7224-fcee-81fe38afb512@gmail.com>
2023-05-06 13:12 ` Jon Turney
2023-05-07 11:39 ` Marco Atzeri [this message]
2023-05-02 20:34 ` Jon Turney
2023-05-02 20:45 ` Achim Gratz
2023-05-03 12:19 ` Ken Brown
2023-05-03 13:33 ` Jon Turney
2023-05-03 14:47 ` Ken Brown
2023-05-03 16:51 ` Achim Gratz
2023-05-03 18:41 ` Achim Gratz
2023-05-03 16:55 ` Achim Gratz
2023-05-03 22:01 ` Ken Brown
2023-05-06 13:34 ` Jon Turney
2023-05-06 18:31 ` Ken Brown
2023-05-09 20:15 ` Jon Turney
2023-05-20 7:57 ` Achim Gratz
2023-10-23 18:53 ` Jon Turney
2023-12-15 17:15 ` Jon Turney
2024-01-28 16:40 ` Jon Turney
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=4e1301f5-9bc0-fd85-fb38-fb78480e6317@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).