From: Stefan Strogin <steils@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last-rites: net-misc/wicd
Date: Wed, 5 Feb 2020 16:16:44 +0200 [thread overview]
Message-ID: <278eeefe-bac1-694d-ea57-af879f4cd50e@gentoo.org> (raw)
In-Reply-To: <1f8cef03-2270-0733-1be6-bc799f4df204@gentoo.org>
Hi,
On 05/02/2020 09:11, Joonas Niilola wrote:
>
> # Stagnant upstream with latest release from 2016, python2-only, no
> maintainer
> # in Gentoo, no notable ebuild action in years, multiple bugs open. Blocks
> # pygtk removal.
> # Switch to alternatives such as,
> # net-misc/connman, net-misc/dhcpcd, net-misc/netifrc,
> net-misc/NetworkManager
> # and so on. Removal in ~90 days. #
>
> 90-day removal window due it possibly being used in low-maintenance servers.
>
> Updated openrc ebuilds to not suggest installing wicd anymore but
> connman instead,
> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a1a177f32dc3c792f5fc69f144b1728a705e1fba
>
The upstream git is alive, it seems it is ported to Python 3,
but not released yet: https://git.launchpad.net/wicd/log/
Its git version is uploaded to Debian experimental:
https://salsa.debian.org/debian/wicd/tree/python3
https://packages.debian.org/experimental/wicd
So I am going to test if wicd-gtk from git works without pygtk and, if it does,
resurrect the ebuild.
next prev parent reply other threads:[~2020-02-05 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 7:11 [gentoo-dev] Last-rites: net-misc/wicd Joonas Niilola
2020-02-05 14:16 ` Stefan Strogin [this message]
2020-02-09 22:43 ` Stefan Strogin
2020-02-11 9:37 ` Mart Raudsepp
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=278eeefe-bac1-694d-ea57-af879f4cd50e@gentoo.org \
--to=steils@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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