From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed
Date: Wed, 11 Dec 2024 15:08:25 +0100 [thread overview]
Message-ID: <92d7c9ee507b349771f5efe67231a2fc3a3dff58.camel@gentoo.org> (raw)
[-- 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 --]
next reply other threads:[~2024-12-11 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 14:08 Michał Górny [this message]
2024-12-12 4:55 ` [gentoo-dev] New tool for updating Bug summaries after package moves: bugsed Sam James
2024-12-12 12:17 ` Michał Górny
2024-12-12 9:28 ` Alexander Neuwirth
2024-12-12 12:18 ` Michał Górny
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=92d7c9ee507b349771f5efe67231a2fc3a3dff58.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@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