Your message dated Sun, 29 Dec 2019 09:33:17 +1100
with message-id <8428295.vGiKvgYaFQ@deblab>
and subject line Done: golang-github-elazarl-goproxy: Please update CA data
has caused the Debian Bug report #884148,
regarding golang-github-elazarl-goproxy: Please update CA data
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 ow...@bugs.debian.org
immediately.)


-- 
884148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-elazarl-goproxy
Version: 1.0-1
Severity: important
Tags: patch upstream

Hi,

When building a package in the latest environment, we can see the
following error.

----
github.com/elazarl/goproxy/transport
   debian/rules override_dh_auto_test
make[1]: Entering directory
'/home/iwamatsu/dev/debian/go/t/golang-github-elazarl-goproxy-1.0'
dh_auto_test
        cd obj-x86_64-linux-gnu && go test -v -p 1
github.com/elazarl/goproxy github.com/elazarl/goproxy/ext/auth
github.com/elazarl/goproxy/ext/html
github.com/elazarl/goproxy/ext/image
github.com/elazarl/goproxy/regretable
github.com/elazarl/goproxy/transport
panic: Error parsing builtin CA x509: RSA key missing NULL parameters

goroutine 1 [running]:
github.com/elazarl/goproxy.init.1()
        
/home/iwamatsu/dev/debian/go/t/golang-github-elazarl-goproxy-1.0/obj-x86_64-linux-gnu/src/github.com/elazarl/goproxy/certs.go:10
+0x1e3
github.com/elazarl/goproxy.init()
        
/home/iwamatsu/dev/debian/go/t/golang-github-elazarl-goproxy-1.0/obj-x86_64-linux-gnu/src/github.com/elazarl/goproxy/signer_test.go:88
+0x252
main.init()
        github.com/elazarl/goproxy/_test/_testmain.go:104 +0x53
exit status 2
FAIL    github.com/elazarl/goproxy      0.004s
panic: Error parsing builtin CA x509: RSA key missing NULL parameters

goroutine 1 [running]:
github.com/elazarl/goproxy.init.1()
        github.com/elazarl/goproxy/certs.go:10 +0x1e3
github.com/elazarl/goproxy.init()
        github.com/elazarl/goproxy/signer.go:86 +0x243
github.com/elazarl/goproxy/ext/auth.init()
        github.com/elazarl/goproxy/ext/auth/basic.go:77 +0x5d
main.init()
        github.com/elazarl/goproxy/ext/auth/_test/_testmain.go:54 +0x53
exit status 2
FAIL    github.com/elazarl/goproxy/ext/auth     0.004s
----

This is a problem caused by CA data being old.
This problem was fixed with the following bugs in upstream.

    https://github.com/elazarl/goproxy/issues/188

Please update CA data,, or please create package with the latest code.

Best regards,
  Nobuhiro

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8),
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

--- End Message ---
--- Begin Message ---
Package: src:golang-github-elazarl-goproxy
Version: 1.1-1

I think this problem should have been fixed by the new upstream release 1.1 
that I've uploaded few days ago. If not then please re-open this ticket.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to