From: Alexis <flexibeast@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Protecting init.d files from auto-update
Date: Tue, 21 Jan 2025 22:59:11 +1100 [thread overview]
Message-ID: <87sepc2x9s.fsf@gmail.com> (raw)
In-Reply-To: <5874817.DvuYhMxLoT@cube> (Peter Humphrey's message of "Tue, 21 Jan 2025 11:14:49 +0000")
Peter Humphrey <peter@prh.myzen.co.uk> writes:
> You misunderstand. I'm saying that the version change should be
> bigger, not just from -r1 to -r2. Perhaps 7.24.2? 7.25?
No, because those component numbers are specified by upstream -
i.e. the BOINC project itself - not by Gentoo. But it's Gentoo
that provides the OpenRC boinc.init and boinc.conf files - in the
sci-misc/boinc/files folder of the Gentoo repository - not
upstream. (If this were about files provided by upstream, rather
than by Gentoo, an issue would need to have been raised with the
BOINC project, not on the Gentoo bug tracker.) It's not Gentoo's
place to change version numbers of the software that Gentoo
packages, but Gentoo _can_ indicate revisions of how specific
versions of the software are packaged. That's what numbers like
-r1, -r2, etc. indicate.
> Where on earth did you get that idea? I only said I couldn't see
> what
> to do, and asked for help with it.
You wrote, as i quoted in my previous email:
> The scale of the changes proposed seems to me too big for such a
> minor revision bump, but more than that, it has several diffs
> against
> separate files, and I'm not /au-fait/ enough with patching to
> know
> what to do with them all.
>
> Would anyone here like to have a go at it?
You didn't write:
> what to do with them all, and I need someone to explain it to
> me. Would anyone here like to have a go at it?
or
> what to do with them all. Would anyone here like to have a go at
> explaining to me what I need to do?
and so i read "it" as referring to the scale of the changes
proposed being too big, and that you were asking for someone else
to put together a patch - particularly because people who need
help with something related to a bug report they've opened usually
ask for that help on the bug report itself, rather than asking for
help in some other venue.
Alexis.
next prev parent reply other threads:[~2025-01-21 12:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 11:28 [gentoo-user] Protecting init.d files from auto-update Peter Humphrey
2025-01-14 12:01 ` Michael
2025-01-14 16:31 ` Peter Humphrey
2025-01-14 12:36 ` Arve Barsnes
2025-01-14 14:18 ` Michael Orlitzky
2025-01-14 16:28 ` Peter Humphrey
2025-01-14 16:53 ` Michael Orlitzky
2025-01-15 11:50 ` Peter Humphrey
2025-01-20 13:24 ` Peter Humphrey
2025-01-20 23:40 ` Alexis
2025-01-21 11:14 ` Peter Humphrey
2025-01-21 11:59 ` Alexis [this message]
2025-01-21 12:45 ` Michael
2025-01-30 15:50 ` Peter Humphrey
2025-01-30 15:47 ` Peter Humphrey
2025-01-31 2:53 ` Alexis
2025-01-31 14:24 ` Peter Humphrey
2025-01-31 14:34 ` Peter Humphrey
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=87sepc2x9s.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=gentoo-user@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