Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 721830 - dev-embedded/esptool-2.1: remove amd64 stable version without stabilizing another version
Summary: dev-embedded/esptool-2.1: remove amd64 stable version without stabilizing ano...
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Andreas Sturmlechner
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-09 10:08 UTC by Martin Dummer
Modified: 2020-05-13 00:36 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Dummer 2020-05-09 10:08:07 UTC
Today I discovered that dev-embedded/esptool on my KEYWORD=amd64 system is outdated and not willing to update.

Current package on my system is dev-embedded/esptool-2.1, keyworded amd64 ~arm ~x86

Package in tree is now only dev-embedded/esptool-2.8 keyworded ~amd64 ~arm ~x86


Why do you remove stable packages without stabilizing another version before? I see no bug reports justifying this.
Comment 1 Jonas Stein gentoo-dev 2020-05-12 22:15:17 UTC
commit ea86ff88c494c3551724324f4f48d0cc5b79d595
Author: Andreas Sturmlechner <asturm@gentoo.org>
Date:   Thu May 7 23:19:49 2020 +0200

    dev-embedded/esptool: Drop 2.1 and 2.6, py36-only
    
    No maintainer, no more stable.
Comment 2 Andreas Sturmlechner gentoo-dev 2020-05-13 00:15:39 UTC
There is no maintainer of this package to keep up the stable keyword.
Comment 3 Andreas Sturmlechner gentoo-dev 2020-05-13 00:36:35 UTC
To be clear, this was dropped because even though random people did commit version bumps on the package in the pasts, no one bothered to do stabilisation in 2,5 years. Now it became a liability for having a stable py36-only version in the tree.

Without the maintainer situation changing, there is no reason to believe this will be different the next time default python target will be raised.