On 9/14/19 1:06 PM, Alec Warner wrote:
>
> - There appears to be some expectation that consensus is required on
> the ML; this has (IMHO) never been true. The 'decider' for what to do
> isn't the mailing list (by GLEP, it's the council). So this idea that
> you can object on the ML and stop a
# Michał Górny (2019-09-14)
# Unmaintained. All of them were not bumped since 2016. No reverse
# dependencies.
# Removal in 30 days. Bug #694398.
dev-go/cli
dev-go/go-gitlab-client
dev-go/toml
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
On Fri, Sep 13, 2019 at 4:45 PM Michael Orlitzky wrote:
> (Replying to both messages at once.)
>
>
> On 9/13/19 4:17 PM, Patrick McLean wrote:
> >>
> > I don't think anyone here has suggested that any go packages are
> > installed in the stage3 tarballs, or included in profiles. Something's
> >
# Michał Górny (2019-09-14)
# sci-biology/goby has been removed. This package makes little sense
# without it.
# Removal in 30 days.
sci-biology/goby-cpp
--
Best regards,
Michał Górny
signature.asc
Description: This is a digitally signed message part
# Michał Górny (2019-09-14)
# Unmaintained. Vulnerable to arbitrary code execution. Debian (being
# its current upstream) removed it. The recommended replacement
# is net-misc/dhcpcd.
# Removal in 30 days. Bug #694314.
net-misc/pump
--
Best regards,
Michał Górny
signature.asc
# Michał Górny (2019-09-14)
# The following packages are unmaintained and have not been tested
# with Python 3.7. Most of them are either in need of version bumps,
# a few have been declared discontinued upstream. None of them has
# any reverse dependency.
# Removal in 30 days. Bug #694280.
# Michał Górny (2019-09-14)
# The following packages are unmaintained and do not declare support
# for Python 3. Most of them are either in need of version bumps,
# or are dead upstream (haven't had a release since 2009-2015).
# None of them have any reverse dependencies.
# Removal in 30 days.
> On Fri, 13 Sep 2019, Patrick McLean wrote:
> Something's presence in the tree does not mean that you are required
> to install it. A package's presence in the tree really has little to
> zero effect on any user that does not use the package.
I wonder if that's always true. Distros adopting
