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: Wed, 03 Feb 2021 21:02:36 +0000	[thread overview]
Message-ID: <ab4827fa-27ca-5e1e-b770-00ffc414ff63@coredump.us> (raw)
In-Reply-To: <b6763fd2-a7ca-1c16-b304-43d1ce0b09da@coredump.us>

Thomas Goirand:
> 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.

I think this is a "red herring".

- The purpose of dh_strip_nondeterminism is to remove build-time changes
   that would cause the package not to be reproducible -- but the mlmmj
   package has been reproducible for a long time.

    https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mlmmj.html

- dh_strip_nondeterminism could be called without switching to dh
- A switch to dh in debian/rules is an invasive change (i.e. it commonly
   causes some bugs to start with) and so it's not something I'd want to do
   close to freeze time, which is exactly where we are.



I haven't heard any reply about bug #622621 which is something that I think 
would be good to address before the Debian release. I'm making a second request: 
can you please look at that bug and discuss it?

    -- Chris

-- 
Chris Knadle
Chris.Knadle@coredump.us


      parent reply	other threads:[~2021-02-03 21:02 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
2021-02-03 21:02 ` Chris Knadle [this message]

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=ab4827fa-27ca-5e1e-b770-00ffc414ff63@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.