From: David Rothenberger <daveroth@acm.org>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin-apps@cygwin.com
Subject: Re: Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages)
Date: Mon, 1 Apr 2024 10:16:02 -0700 [thread overview]
Message-ID: <119e8725-4306-4557-8672-2aa31c6e720f@acm.org> (raw)
In-Reply-To: <c512ad7d-7543-4a25-b603-dd1ba5220c8f@dronecode.org.uk>
On 3/30/2024 8:25 AM, Jon Turney wrote:
> On 29/03/2024 18:32, David Rothenberger via Cygwin-apps wrote:
>> On 3/28/2024 10:50 AM, Jon Turney via Cygwin-apps wrote:
> [...]
>>> David,
>>>
>>> Is it possible to update/rebuild rdiff-backup, which replies upon the
>>> soon-to-be removed python36?
>>>
>>> (Or indicate that you are no longer interested in maintaining this
>>> package, which will probably lead to it's removal).
>>
>> Please remove me as the maintainer from that package. I no longer use
>> it, and no longer have an environment for building packages for Cygwin.
>
> No problem. Thanks for maintaining it in the past.
>
> Is the same true for your other packages?
>
> $ grep Rothenberger cygwin-pkg-maint | grep -v ORPHANED
> cyrus-sasl David Rothenberger
> flac David Rothenberger
> libao David Rothenberger
> libapr1 David Rothenberger
> libaprutil1 David Rothenberger
> libkate David Rothenberger
> libogg David Rothenberger
> librsync David Rothenberger
> libtheora David Rothenberger
> libvorbis David Rothenberger
> rdiff-backup David Rothenberger
> speex David Rothenberger
> speexdsp David Rothenberger
> vorbis-tools David Rothenberger
> which David Rothenberger
> whois David Rothenberger
Yes, I'm afraid it is.
Regards,
David
--
David Rothenberger ---- daveroth@acm.org
next prev parent reply other threads:[~2024-04-01 17:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 12:32 Bonfire of the Packages Jon Turney
2023-09-24 18:20 ` gs-cygwin.com
2023-09-24 20:13 ` Thomas Wolff
2024-03-24 14:07 ` Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages) Jon Turney
2024-03-24 17:31 ` Marco Atzeri
2024-03-24 17:46 ` Jon Turney
2024-03-24 18:51 ` Brian Inglis
2024-03-27 20:07 ` Jon Turney
2024-03-28 17:50 ` Jon Turney
2024-04-18 6:01 ` Ake Rehnman
2024-04-19 12:16 ` Jon Turney
2024-03-28 17:50 ` Jon Turney
2024-03-29 18:32 ` David Rothenberger
2024-03-30 15:25 ` Jon Turney
2024-04-01 17:16 ` David Rothenberger [this message]
2024-04-02 14:38 ` Jon Turney
2024-04-02 14:58 ` Takashi Yano
2024-04-05 12:46 ` Jon Turney
2024-04-05 23:17 ` Takashi Yano
2024-04-01 15:22 ` Jon Turney
2024-03-27 21:18 Brian Inglis
2024-03-28 17:49 ` Jon Turney
2024-03-28 19:08 ` Brian Inglis
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=119e8725-4306-4557-8672-2aa31c6e720f@acm.org \
--to=daveroth@acm.org \
--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).