| 1 |
On Fri, Jun 05, 2020 at 12:40:17PM -0700, Matt Turner wrote: |
| 2 |
> On Fri, Jun 5, 2020 at 9:55 AM Jonas Stein <jstein@g.o> wrote: |
| 3 |
> > |
| 4 |
> > On 04/06/2020 01.39, Aaron Bauman wrote: |
| 5 |
> > > # Aaron Bauman <bman@g.o> (2020-06-03) |
| 6 |
> > > # py2 only. dead upstream. m-n. |
| 7 |
> > > # Masked for removal in 15 days |
| 8 |
> > > app-cdr/sync2cd |
| 9 |
> > > |
| 10 |
> > |
| 11 |
> > is there a good reason to reduce the time to 15 days? |
| 12 |
> > |
| 13 |
> > https://devmanual.gentoo.org/ebuild-maintenance/removal/index.html |
| 14 |
> > "Wait 30 days (or more)" |
| 15 |
> |
| 16 |
> I think we all agree that Python 2-only packages are going to have to |
| 17 |
> be removed. |
| 18 |
> |
| 19 |
> This package is Python 2-only, and it was last released more than 13 |
| 20 |
> years ago, and the website even says that the project is dead |
| 21 |
> (http://c-space.org/). |
| 22 |
> |
| 23 |
> With that in mind, I don't expect it to gain Python 3 support, nor do |
| 24 |
> I expect an additional 15 days of waiting time to change that fact. 15 |
| 25 |
> vs 30 days doesn't seem worth squabbling over. |
| 26 |
> |
| 27 |
|
| 28 |
What Matt said. |
| 29 |
|
| 30 |
Just speeds up removal because it is highly unlikely to gain Py3 |
| 31 |
support. |
| 32 |
|
| 33 |
-- |
| 34 |
Cheers, |
| 35 |
Aaron |
Archives