Your message dated Sat, 29 Aug 2026 07:02:04 +0200
with message-id <[email protected]>
and subject line Re: Maintenance of golang-github-chromedp-cdproto
has caused the Debian Bug report #1142395,
regarding maintenance of golang-github-chromedp-cdproto
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1142395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142395
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: golang-github-chromedp-cdproto
Severity: wishlit
Hi,
I've uploaded golang-github-chromedp-chromedp some time ago, it's needed
for git-pages. While I have much interest in git-pages, I don't really
care about golang-github-chromedp-chromedp.
However, golang-github-chromedp-chromedp and
golang-github-chromedp-cdproto always go in lockstep, in order to update
chromedp you need to update cdproto.
Given that I'm actively updating chromedp continuesly to make sure we
have the current version in Debian, this becomes quite tedious to always
ask and wait for cdproto to be updated first.
Would you mind taking over chromedp and keep them both updated, or would
you like me to take over cdproto instead?
Regards,
Daniel
--- End Message ---
--- Begin Message ---
On 8/28/26 22:13, Simon Josefsson wrote:
It sounds like you would be a good (co)-maintainer/uploader of them?
We're going in circles. To summarize, I understand that the Go team
isn't maintaining this concrete package as active as I would like it to
be (and doesn't want to take over the other two), and I don't want to
join the Go team at this point. So I will continue the bug+NMU way for
the time being.
Regards,
Daniel
--- End Message ---
