public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: Python 3.5 and 3.6 removal (was Re: Bonfire of the Packages)
Date: Sat, 6 Apr 2024 08:17:22 +0900	[thread overview]
Message-ID: <20240406081722.5934eef30300cd24edbc2bf2@nifty.ne.jp> (raw)
In-Reply-To: <cce2dd6d-b156-4e44-b563-4aae2463cd5c@dronecode.org.uk>

On Fri, 5 Apr 2024 13:46:18 +0100
Jon Turney wrote:
> On 02/04/2024 15:58, Takashi Yano via Cygwin-apps wrote:
> > On Tue, 2 Apr 2024 15:38:25 +0100
> > Jon Turney wrote:
> >> On 01/04/2024 18:16, David Rothenberger via Cygwin-apps wrote:
> >>> 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.
> >>
> >> Done.  Thanks for all your work on these in the past.
> > 
> > Hi, I would like to take over the maintenance of:
> >>>> flac                                         David Rothenberger
> >>>> libao                                        David Rothenberger
> >>>> libogg                                       David Rothenberger
> >>>> libtheora                                    David Rothenberger
> >>>> libvorbis                                    David Rothenberger
> >>>> speex                                        David Rothenberger
> >>>> speexdsp                                     David Rothenberger
> >>>> vorbis-tools                                 David Rothenberger
> > if anyone would not.
> > 
> 
> Thanks. I added these to your packages.

Thanks!

> I generated missing packaging history repos for some of these from the 
> CTM history.  Please let me know if there's any errors or if you'd like 
> those removed.
> 
> I didn't check, but if any of these are no longer carried by recent 
> linux distros, maybe think about if it's actually useful to keep on 
> having a package for it...

All these packages are required by my other packages such as ffmpeg,
timidity++, pulseaudio, etc. except for vorbis-tools.
Also, these still exist in fedora rpms repos.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2024-04-05 23:17 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
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 [this message]
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=20240406081722.5934eef30300cd24edbc2bf2@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).