[gentoo-dev] New tool for updating Bug summaries after package moves: bugsed

[gentoo-dev] New tool for updating Bug summaries after package moves: bugsed

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

Hi,

I've made a quick tool that can perform search-and-replacement
on Bugzilla bugs, so if you move a package, you can quickly update
hundreds of bugs filed against it.

https://github.com/projg2/bugsed

Note that it just does dumb text replacement with substring match, so it
can be greedy.  By default, it just does a dry-run, `-u` to update.

You may also want to try pkgmove from mgorny-dev-scripts, which is also
dumb as hell, greedy on seding stuff and requires you to rename ebuilds
inside the package directory first.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

Re: [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed

[Sam James]

Michał Górny <mgorny@gentoo.org> writes:

> Hi,
>
> I've made a quick tool that can perform search-and-replacement
> on Bugzilla bugs, so if you move a package, you can quickly update
> hundreds of bugs filed against it.

Nice!

>
> https://github.com/projg2/bugsed
>
> Note that it just does dumb text replacement with substring match, so it
> can be greedy.  By default, it just does a dry-run, `-u` to update.
>
> You may also want to try pkgmove from mgorny-dev-scripts, which is also
> dumb as hell, greedy on seding stuff and requires you to rename ebuilds
> inside the package directory first.

Could you run it over historical updates (at least from the last year)?
I can do it if you give me whatever recipe you used as well (or if not,
can get to it later again when bored).

Re: [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

On Thu, 2024-12-12 at 04:55 +0000, Sam James wrote:
> Could you run it over historical updates (at least from the last year)?
> I can do it if you give me whatever recipe you used as well (or if not,
> can get to it later again when bored).

It's literally:

  ./bugsed old/pkg new/pkg old/pkg2 new/pkg2...

Check the output, then the same with `-u`.

I've listed all replacement pairs for LLVM packages there, to avoid
multiple updates on bugs listing multiple LLVM packages.  For other
moves, where it is unlikely for different packages to be listed
together, this shouldn't be necessary.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

Re: [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed

[Alexander Neuwirth]

On 12/11/24 15:08, Michał Górny wrote:
> you can quickly update
> hundreds of bugs filed against it

Does it need to be added to the list of exceptions [1] or is it 
considered as a manual, i.e. non-automated, script?

Cheers,
APN

[1] https://bugs.gentoo.org/bots.html

Re: [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 552 bytes --]

On Thu, 2024-12-12 at 10:28 +0100, Alexander Neuwirth wrote:
> On 12/11/24 15:08, Michał Górny wrote:
> > you can quickly update
> > hundreds of bugs filed against it
> 
> Does it need to be added to the list of exceptions [1] or is it 
> considered as a manual, i.e. non-automated, script?

Well, I don't think it should really be considered a "bot", since it's
just a frontend script that does operations on your request.  It's not
that different from "change multiple bugs" function in Bugzilla.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]