All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Knadle <Chris.Knadle@coredump.us>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] distribution "dead upstream" discussion
Date: Fri, 22 Jan 2021 03:57:25 +0000	[thread overview]
Message-ID: <9cb7668c-c404-b58c-a382-cb367cd76978@coredump.us> (raw)
In-Reply-To: <b6763fd2-a7ca-1c16-b304-43d1ce0b09da@coredump.us>

Eric Wong:
> Chris Knadle <Chris.Knadle@coredump.us> wrote:
[...]
>>  From the distribution point of view this appears to be "dead upstream" and
>> is a reason for package removal. Debian is about to do a "soft freeze" for
>> preparation for the next release whereby packages in the archive will need
>> bug support for 3 years.
> 
> As a mere user of Debian who doesn't care for popcon, I find
> the "dead upstream" reason annoying.  Sometimes software is just
> "done" and good :)  New features generally leads to more bugs,
> which can penalize existing users.

Debian Developers are intended to remain in contact with upstream developers for 
a number of reasons; DDs are not expected to fix non-Debian related bugs, for 
instance.

https://www.debian.org/doc/manuals/developers-reference/developer-duties.en.html#coordination-with-upstream-developers

And yes, the "dead upstream" reason for package removal is annoying, but it's 
one of the most common reasons I see cited for package removal when there's also 
bugs that upstream would normally be the one to handle handle.

> I've already lost "iprint" and "mp3gain" so just end up copying
> binaries from old installs, now.

Debian has quite a number of packages (1189) that are "orphaned" and still in 
the archive.

https://www.debian.org/devel/wnpp/orphaned

    -- Chris

-- 
Chris Knadle
Chris.Knadle@coredump.us


  parent reply	other threads:[~2021-01-22  3:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 10:35 [mlmmj] distribution "dead upstream" discussion Chris Knadle
2021-01-21 17:43 ` webmaster
2021-01-21 21:59 ` Geert Stappers
2021-01-21 22:09 ` Eric Wong
2021-01-21 22:40 ` Christof Thalhofer
2021-01-22  3:50 ` Chris Knadle
2021-01-22  3:57 ` Chris Knadle [this message]
2021-01-22  6:03 ` Mads Martin Jørgensen
2021-01-25 17:20 ` Thomas Goirand
2021-01-26  0:14 ` Mads Martin Jørgensen
2021-01-27 15:58 ` Chris Knadle
2021-02-02 17:14 ` Thomas Goirand
2021-02-03 21:02 ` Chris Knadle

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=9cb7668c-c404-b58c-a382-cb367cd76978@coredump.us \
    --to=chris.knadle@coredump.us \
    --cc=mlmmj@mlmmj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.