From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Protecting init.d files from auto-update
Date: Tue, 21 Jan 2025 11:14:49 +0000 [thread overview]
Message-ID: <5874817.DvuYhMxLoT@cube> (raw)
In-Reply-To: <87frld2gwp.fsf@gmail.com>
On Monday 20 January 2025 23:40:22 Greenwich Mean Time Alexis wrote:
> Peter Humphrey <peter@prh.myzen.co.uk> writes:
> > On Wednesday 15 January 2025 11:50:02 Greenwich Mean Time I
> >
> > wrote:
> >> https://bugs.gentoo.org/948143
> >
> > That bug now has a patch, which proposes to move from
> > sci-misc/boinc-7.24.1-r1 to -r2. 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?
>
> Well, as the person who submitted that patch, i'd like to comment
> on this.
--->8
> So:
>
> * The move from -r1 to -r2 is required because a revision change
> is required when there any changes to an ebuild, including to
> Gentoo-provided files, that don't come from upstream. This in
> turn requires a new ebuild file, which makes up a significant
> amount of the patch.
You misunderstand. I'm saying that the version change should be bigger, not
just from -r1 to -r2. Perhaps 7.24.2? 7.25?
> * There are small changes to the boinc.conf and boinc.init files,
> which i consider to be the minimum required to address the
> suggestions that were made.
OK.
> Specifically:
--->8
> i find your post here quite odd, discouraging, and an example of
> why i'm increasingly disinclined to devote so much time to
> volunteer ICT work, - that i would instead be better served by
> increasing my other volunteer work in other areas, where my
> experience is of people's gratitude rather than of
> entitlement. Rather than being appreciative of someone
> volunteering to take on the work, and rather than asking
> clarifying questions on the bug itself about what you don't
> understand, you've written a post on a public list effectively
> dismissing my work, assuming that it's fundamentally wrong. Okay
> then.
Where on earth did you get that idea? I only said I couldn't see what to do,
and asked for help with it.
--
Regards,
Peter.
next prev parent reply other threads:[~2025-01-21 11:15 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 [this message]
2025-01-21 11:59 ` Alexis
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=5874817.DvuYhMxLoT@cube \
--to=peter@prh.myzen.co.uk \
--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