From: Thomas Goirand <thomas@goirand.fr>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] distribution "dead upstream" discussion
Date: Tue, 02 Feb 2021 17:14:21 +0000 [thread overview]
Message-ID: <c5ba7335-440e-ac03-2a09-fc684e61fd87@goirand.fr> (raw)
In-Reply-To: <b6763fd2-a7ca-1c16-b304-43d1ce0b09da@coredump.us>
On 1/27/21 4:58 PM, Chris Knadle wrote:
>> MLMMJ is of very low need for maintenance, both upstream or in the
>> Debian package. So much that our Debian source package is bit-rotting,
>> and would need a real clean-up (to switch to the dh sequencer, for a
>> start, and probably many other stuff...).
>
> Yes, the Debian mlmmj package is bit-rotting some, because there's no
> new versions to upload nor new bugs to prompt making a new upload. I
> don't see the point of updating the debian/rules file to dh unless MLMMJ
> development is picked up again, but I am interested in doing that if
> that happens.
The point is that it helps to keep your package up-to-date for new
stuff. For example, the current version of the package doesn't call
dh_strip_nondeterminism which is a new thing, and which dh calls.
Cheers,
Thomas Goirand (zigo)
next prev parent reply other threads:[~2021-02-02 17:14 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
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 [this message]
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=c5ba7335-440e-ac03-2a09-fc684e61fd87@goirand.fr \
--to=thomas@goirand.fr \
--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.