Bug#840680: dirmngr: Dirmngr not always responding

Package: dirmngr Version: 2.1.15-4 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrade to 2.1.15-4, I find dirmngr is not always responding which makes command like `gpg --refresh-keys` stuck. I test dirmngr with the following steps: First run

Bug#870683: ghc: DFSG incompatible file included in src

problem, and I asked at debian-legal. Someone suggests this license fails the DFSG[1]. Please consider to remove this file from source. [1] https://lists.debian.org/debian-legal/2017/08/msg1.html Thanks, Shengjing Zhu signature.asc Description: PGP signature

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

to reproduce it on ppc64, but I failed even I run `go-7 version`. IIRC, gccgo-7 7.2.0-2 works fine. Thanks shengjing Zhu signature.asc Description: PGP signature

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

Since there's only 7.2.0-1 on http://snapshot.debian.org/archive/debian-ports/ I can confirm this version works on ppc64 Thanks Shengjing Zhu

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

> please could you recheck with gcc-snapshot? Thanks, gcc-snapshot works # /usr/lib/gcc-snapshot/bin/go version go version go1.9 gccgo (Debian 20170917-1) 8.0.0 20170917 (experimental) [trunk revision 252892] linux/ppc64 -- Best regards, Shengjing Zhu

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

> is this limited to big endian 64bit systems? Maybe somebody could check on > ppc64el, sparc64 and mips64el as well? AFAICT, ppc64el works fine. mips, s390x, ppc64 fail in same reason on buildd -- Best regards, Shengjing Zhu

Bug#878771: golang-github-spf13-cobra FTBFS on mips: error: redefinition of 'AF_ALG'

bb8f8e16490ce03ce084c8e170ea4c9e79f53ba2 > ___ > Pkg-go-maintainers mailing list > pkg-go-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers -- Best regards, Shengjing Zhu

Bug#874009: rkt FTBFS: cannot find package "github.com/aws/aws-sdk-go/private/signer/v4"

aws account to test). Please let me know if you need help. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869800 [2] https://anonscm.debian.org/cgit/pkg-go/packages/rkt.git/commit/?id=9058b4f2a2d7388a53c43b43580b0a461173b64f Thanks Shengjing Zhu

Bug#876875: golang-github-gin-gonic-gin FTBFS with Go 1.9

On Tue, 26 Sep 2017 18:05:49 +0300 Adrian Bunk wrote: > Source: golang-github-gin-gonic-gin > Version: 1.2+dfsg1-2 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-gin-gonic-gin.html > > ... > === RUN TestPanicInHandler >

Bug#877008: golang-github-mattn-go-sqlite3: FTBFS: FAIL: TestShortTimeout

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/golang-github-mattn-go-sqlite3.html --- FAIL: TestShortTimeout (5.60s) sqlite3_go18_test.go:83: Executing db initializing statements sqlite3_go18_test.go:128: context deadline exceeded -- Best regards, Shengjing Zhu

Bug#877146: update to runc (1.0.0~rc4) breaks docker

newer than 1.0.0-rc4. Packaging the lasted docker release is hard, but eventually we will do. And the runc/docker-runc in Debian will become duplicated. CCing docker.io maintainers, so they will be aware of this. -- Best regards, Shengjing Zhu

Bug#867358: mips/mipsel: mips-linux-gnu-gccgo-7: waitid: bad address

so I won't apply it until > it's either accepted upstream or reviewed by Aurelien or another MIPS > porter. > Ben, James' two patches are included in 4.13. Forget to close this bug in latest upload to unstable? Best regards, Shengjing Zhu

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers -- Best regards, Shengjing Zhu

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

ccgo reports mipsel and mips both as `mipso32`. So we need pass another `-tags` to distinguish the two archs. Unless gccgo has corrent build tip, we can only manually add `-tags mips` or `-tags mipsel`. BTW, let me down grade this bug's severity first since I think we have workaround for that :) -- Best regards, Shengjing Zhu

Bug#873486: fcitx can not be start after upgrade to Debian buster

1 > ii fcitx-frontend-all 1:4.2.9.1-6 > ii fcitx-ui-classic 1:4.2.9.1-6 > ii im-config [im-switch] 0.30-1 > > Versions of packages fcitx suggests: > pn fcitx-m17n > pn fcitx-tools > > -- no debconf information > > ___ > Pkg-ime-devel mailing list > pkg-ime-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ime-devel -- Best regards, Shengjing Zhu

Bug#898149: Recommends: freerdp-x11 won't be in buster

Package: krdc Version: 4:17.08.3-1 Severity: serious Justification: Policy 2.2.1 Dear Maintainer, Due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890928 freerdp-x11 won't be in buster, was superseded by freerdp2-x11. Policy 2.2.1: the packages in main must not require or recommend a

Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

Hi team, Here is the patch to skip this test. -- Shengjing Zhu diff -Nru golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog --- golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian

Bug#902467: [pkg-go] Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

instead of rewriting the logic... -- Best regards, Shengjing Zhu

Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

le. It of cause prints the "/tmp/go-buildnnn/b001/osext.test (deleted)". ^ Besides in go >= 1.8, this package's Executable function just fallback to go system os package. -- Best regards, Shengjing Zhu signature.asc Description: PGP signature

Bug#903808: leela-zero: Not functional without downloading extra resources

Package: leela-zero Severity: serious Justification: Policy 2.2.1 Dear Maintainer, When I try to run leela-zero, it tells me there's no weights file, and I need to download extra file to make it functional. Thus I think this package breaks the policy 2.2.1 > In addition, the packages in main >

Bug#907714: golang-x-text: FTBFS in buster/sid (failing tests)

used, so I don't think the test is so important to kick packages out of testing. Can we skip this test? -- Shengjing Zhu

Bug#908055: docker.io: CVE-2017-14992

doesn't have buildinfo for amd64. But I guess it was built with golang-github-vbatts-tar-split 0.10.2-1(which was uploaded at 2017-11-30). Thus the docker.io version in testing/unstable is not affected by this security issue. -- Regards, Shengjing Zhu

Bug#908055: docker.io: CVE-2017-14992

On Thu, Sep 6, 2018 at 9:40 AM Arnaud Rebillout wrote: > > > On 09/05/2018 10:22 PM, Shengjing Zhu wrote: > > Dear docker.io maintainer, > > > > I'm not sure why the Built-Using field in docker.io doesn't contain > > golang-github-vbatts-tar-

Bug#891822: elvish: failed to build on arm64/mips64el

Package: elvish Version: 0.11+ds1-3+b1 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) Forwarded: https://github.com/elves/elvish/issues/612 Dear Maintainer, Failed to build with Go 1.10 on arm64 and mips64el

Bug#907298: CVE-2018-15869

Control: found -1 1.0.2+dfsg-1 The dynamic source ami is introduced in https://github.com/hashicorp/packer/pull/3817 So the affected upstream version is 0.12 and later. signature.asc Description: PGP signature

Bug#911434: prometheus: FTBFS with golang-google-grpc/1.11.0-1

: TestStartupInterrupt (10.51s) main_test.go:97: prometheus didn't shutdown gracefully after sending the Interrupt signal I'm not sure how this test is related to golang-google-grpc. And upstream has a similar issue, "Flaky shutdown test" https://github.com/prometheus/prometheus/issues/4587 -- Shengjing Zhu

Bug#907298: CVE-2018-15869

https://bugzilla.redhat.com/show_bug.cgi?id=1623095 -- Shengjing Zhu signature.asc Description: PGP signature

Bug#907298: CVE-2018-15869

On Thu, Oct 18, 2018 at 08:54:51AM +0100, Ian Campbell wrote: > On Thu, 2018-10-18 at 11:48 +0800, Shengjing Zhu wrote: > > Package: awscli > > Followup-For: Bug #907298 > > > > The corresponding bug on Redhat is closed as > > > > > Closing this bu

Bug#910935: cmake-extras: GMockConfig.cmake doesn't work with googletest/1.8.1-1

IBRARIES gtest) set(GTEST_MAIN_LIBRARIES gtest_main) -- Shengjing Zhu

Bug#911436: prometheus-haproxy-exporter: FTBFS undefined: prometheus.NewProcessCollectorPIDFn

: prometheus.NewProcessCollectorPIDFn github.com/prometheus/client_golang removed NewProcessCollectorPIDFn in https://github.com/prometheus/client_golang/commit/773f502 This problem is fiexed in upstream https://github.com/prometheus/haproxy_exporter/commit/be645b2a6c65d2b443528c6f1cda858a343ae87d -- Shengjing Zhu

Bug#911439: prometheus-bind-exporter: FTBFS undefined: prometheus.NewProcessCollectorPIDFn

: prometheus.NewProcessCollectorPIDFn github.com/prometheus/client_golang removed NewProcessCollectorPIDFn in https://github.com/prometheus/client_golang/commit/773f502 -- Shengjing Zhu

Bug#911440: syncthing: FTBFS too many arguments in call to prometheus.NewProcessCollector

to prometheus.NewProcessCollector have (int, string) want (prometheus.ProcessCollectorOpts) NewProcessCollector changed API in golang-github-prometheus-client-golang/0.9.0-1 -- Shengjing Zhu

Bug#911437: gitlab-ci-multi-runner: FTBFS with golang-github-prometheus-client-golang/0.9.0-1

to "github.com/prometheus/client_golang/prometheus".NewProcessCollector have (int, string) want ("github.com/prometheus/client_golang/prometheus".ProcessCollectorOpts) -- Shengjing Zhu

Bug#911434: prometheus: FTBFS with golang-google-grpc/1.11.0-1

Control: retitle -1 prometheus: FTBFS flaky shutdown test On Sat, Oct 20, 2018 at 2:33 PM Shengjing Zhu wrote: > I'm not sure how this test is related to golang-google-grpc. > And upstream has a similar issue, "Flaky shutdown test" > https://github.com/prometheus/prometheus/

Bug#915821: Needs to be built against lxc 3.x

r this package. I've requested a binNMU for anbox, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915956 -- Shengjing Zhu

Bug#907432: [pkg-go] Bug#907432: golang-github-cloudflare-redoctober: FTBFS (too many arguments in call to activation.Listeners)

ers(true) >From the go-systemd commit comment, they just removed the arg, and assume it's default is true. -- Best regards, Shengjing Zhu

Bug#923866: aptly: unable to delete local repositories

Control: tags -1 patch Hi, This is caused by using new github.com/ugorji/go/codec. Please see patch in attachment. Repo created before still can't be deleted, but new repo can be deleted after patch. -- Shengjing Zhu aptly.debdiff Description: Binary data

Bug#924119: Bug #924119 in notary marked as pending

Control: tag -1 pending Hello, Bug #924119 in notary reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#926380: golang-github-puerkitobio-purell: FTBFS (failing tests)

there's no way to fix it (so should > be deprecated in favour of NormalizeURL). > Thus intentionally *not* tagging patch, as this is rather a "proof of > concept". > > Regards, > Andreas Henriksson Thanks for your great work! However it's already fixed by upstream, https://github.com/PuerkitoBio/purell/pull/29 If someone is going to upload the new version, please take upstream patch instead :/ -- Shengjing Zhu

Bug#924115: golang-gopkg-data-dog-go-sqlmock.v1-dev: directory vs. symlink conflict: /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1

is not in src:golang-github-data-dog-go-sqlmock's Go-Import-Path field, this should be fixed in golang-github-data-dog-go-sqlmock. I think that's why you were not aware, and upload a new one. I think file a RM request for ftp-master is the solution here. -- Shengjing Zhu

Bug#924115: golang-gopkg-data-dog-go-sqlmock.v1-dev: directory vs. symlink conflict: /usr/share/gocode/src/gopkg.in/DATA-DOG/go-sqlmock.v1

On Tue, Mar 12, 2019 at 11:25 PM rajudev wrote: > > > Shengjing Zhu writes: > > > Hi Raju, > > Ni Hao :) > > > > This package seems problematic in other perspective, > Indeed it is confusing. > > > > golang-github-data-dog-go-sqlmock-dev is alre

Bug#923804: Bug #923804 in golang-github-ncw-swift marked as pending

Control: tag -1 pending Hello, Bug #923804 in golang-github-ncw-swift reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#922050: Bug #922050 in runc marked as pending

Control: tag -1 pending Hello, Bug #922050 in runc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#915311: dumb-init FTBFS on mips*: test failures

to keep this in buster? -- Shengjing Zhu diff -Nru dumb-init-1.2.2/debian/changelog dumb-init-1.2.2/debian/changelog --- dumb-init-1.2.2/debian/changelog2019-01-27 14:30:06.0 +0800 +++ dumb-init-1.2.2/debian/changelog2019-02-14 00:50:21.0 +0800 @@ -1,3 +1,10 @@ +dumb-init (1.2.2

Bug#921753: librime-dev: wrong libdir in /usr/lib/x86_64-linux-gnu/pkgconfig/rime.pc

/{LIB_INSTALL_DIR} This causes fcitx-rime and ibus-rime FTBFS. -- Shengjing Zhu signature.asc Description: PGP signature

Bug#915311: dumb-init FTBFS on mips*: test failures

Hi, I've uploaded this NMU to DELAYED/2-day. Hope it works. On Thu, Feb 14, 2019 at 1:03 AM Shengjing Zhu wrote: > > diff -Nru dumb-init-1.2.2/debian/changelog dumb-init-1.2.2/debian/changelog > --- dumb-init-1.2.2/debian/changelog2019-01-27 14:30:06.0 +0800 > +++ dum

Bug#917723: golang-github-mitchellh-mapstructure-dev: regression in 1.1.2 caused packer FTBFS

since golang-github-mitchellh-mapstructure-dev 1.1.2-1. The regression is described in upstream issue. I've sent the patch to upstream but haven't got ack. The patch has passed all the tests, so I'm going to upload it to Debian later. But any review is appreciated. -- BR, Shengjing Zhu

Bug#917723: golang-github-mitchellh-mapstructure-dev: regression in 1.1.2 caused packer FTBFS

Package: golang-github-mitchellh-mapstructure-dev Version: 1.1.2-1 Followup-For: Bug #917723 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Control: severity -1 normal I just found one critical library[1][2] was already patched to depend on this bug behaviour. So I vendored the old

Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method

, this may be the reason. Please reassign to ruby-ronn if you think it's the bug in ruby-ronn instead. - -- Shengjing Zhu -BEGIN PGP SIGNATURE- iQFEBAEBCgAuFiEE85F2DZP0aJKsSKyHONAPABi+PjUFAlxcR7IQHHpoc2pAZGVi aWFuLm9yZwAKCRA40A8AGL4+NTqRB/0TMPE3oaR0kUXa78k6HUizl9

Bug#923866: aptly: unable to delete local repositories

just push the NMU to the git repo, it's in debian/ namesapce, thus there's no permission problem. And I'm going to prepare another NMU for #911924, and plan to push changes to git directly. -- Shengjing Zhu

Bug#923866: aptly: unable to delete local repositories

On Sat, Apr 13, 2019 at 11:17 PM Shengjing Zhu wrote: > > Hi, > > Sorry to say that my patch has a minor issue. > > ``` > Uploaders *Uploaders `code:"Uploaders,omitempty" json:"-"` > ``` > Should be > ``` > Uploaders *Uploaders `codec:"Up

Bug#929584: Not suitable for buster

Source: golang-github-rackspace-gophercloud Version: 1.0.0+git20160603.920.934dbf8-1 Severity: serious Please don't ship this package in buster. There's no {build-,}rdepends in buster, and it's suppressed by golang-github-gophercloud-gophercloud. -- Shengjing Zhu signature.asc Description

Bug#929716: notary: FTBFS: dh_auto_test: cd _build && go test -vet=off -v -p 4 github.com/theupdateframework/notary [...] github.com/theupdateframework/notary/version returned exit code 1

Received unexpected error: > > listen tcp 127.0.0.1:: bind: address > > already in use > > Test: TestSetupNetListener > > FAIL This test need to listen on . I don't think this would be RC, so I will downgrade this bug. -- Shengjing Zhu

Bug#929721: golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gin-gonic/gin/gin

; > > github.com/gin-gonic/gin.setupHTMLGlob.func1.2 (1 handlers) > > [GIN-debug] Listening and serving HTTPS on : > > [GIN-debug] [ERROR] listen tcp :: bind: address already in use This test needs to listen on . I don't think this would be RC, so I will downgrade this bug. -- Shengjing Zhu

Bug#929717: golang-fsnotify: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/fsnotify/fsnotify returned exit code 1

han 128*1024. This is usually fine, as the default is 16384. Thus I also don't think this is RC. -- Shengjing Zhu

Bug#929781: rkt: CVE-2019-10144 CVE-2019-10145 CVE-2019-10147

. And RedHat has more interests in other container related tools, like podman. Although rkt is now hosted by CNCF, but it doesn't attract more contributors. So I would suggest we remove rkt from buster. -- Shengjing Zhu

Bug#929781: rkt: CVE-2019-10144 CVE-2019-10145 CVE-2019-10147

Sorry, typo... On Sun, Jun 16, 2019 at 11:47 PM Shengjing Zhu wrote: > > Hi Dmitry, > > Upstream doesn't have any update for these 3 CVE for more than 2 > weeks(after the CVE published). > > So I'm afraid that rkt is longer maintained, with 2 other concerns: s/is longer/

Bug#929781: rkt: CVE-2019-10144 CVE-2019-10145 CVE-2019-10147

On Sun, Jun 16, 2019 at 11:47 PM Shengjing Zhu wrote: > So I would suggest we remove rkt from buster. > Which means the acbuild and nomad(build-rdepends) will also be removed. For acbuild, it is also discontinued by upstream[1]. For nomad, you can disable the rkt driver, by patching

Bug#865975: docker.io changes iptables default FORWARD policy to DROP, breaks VM and others

Control: severity -1 normal On Tue, Jun 11, 2019 at 6:09 PM Shengjing Zhu wrote: > > Hi, > > I checked more carefully on https://github.com/moby/moby/pull/28257 > and https://github.com/moby/moby/issues/14041 > Then I concluded that docker does nothing

Bug#929983: ipxe-qemu: virtio booting no longer works after upgrade to buster

On Wed, Jun 05, 2019 at 01:24:06AM +0200, Thorsten Glaser wrote: [...] > I’ll attach the virsh dumpxml output below; I had reinstalled Debian > using an e1000 NIC and netboot in the meantime and reverted to virtio > afterwards, but I’m pretty sure this is reproducible even on other >

Bug#865975: docker.io changes iptables default FORWARD policy to DROP, breaks VM and others

.ip_forward=1 to /etc/sysctl.conf, then reboot. And my FORWARD policy is ACCEPT. So as for your VM scenario, why didn't you set ip_forward manually? How docker know it's not a vulnerability if it didn't set FORWARD chain to DROP when it enables ip_forward. -- Shengjing Zhu

Bug#903635: This is RC; breaks unrelated software

SER -j RETURN COMMIT # Completed on Mon Jun 10 01:22:35 2019 ``` The FORWARD policy is ACCEPT. The origin bug is true that, docker still adds an empty chain, when iptables=false is set. But IMHO your justification is not real. -- Shengjing Zhu signature.asc Description: PGP signature

Bug#930302: installing and starting docker changes iptables FORWARD policy, breaking unrelated things

clone 903635 -1 > retitle -1 installing and starting docker changes iptables FORWARD policy, > breaking unrelated things > severity 903635 important > found 903635 18.09.1+dfsg1-7 > found -1 18.09.1+dfsg1-7 > thanks > > On Mon, Jun 10, 2019 at 01:27:45AM +0800, Shengjing Z

Bug#929662: docker.io: CVE-2018-15664 - upstream backport of patch for 18.09

by upstream cause wield results. I'm not sure if changing ulimit really works. But my desktop crashes(run out of pids)... outside the schroot... Anyway, I uploaded NMU to apply upstream patch, but the wield tests are omitted. -- Shengjing Zhu

Bug#930332: FTBFS on arm64: FAIL: peer_test.go:79: PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise

.. I can reproduce it on porterbox(amdahl.d.o). I checked the code, it should be correct... -- Shengjing Zhu signature.asc Description: PGP signature

Bug#927227: RFS: golang-gopkg-sourcemap.v1/1.0.5-2 [RC]

this package in buster, please open an unblock request by running `reportbug release.debian.org`. Thanks for your contributions. -- Shengjing Zhu

Bug#818366: synaptic: fails to start under Wayland

It's not the regression of synaptic, it's GNOME. Well, shouldn't it be enough to add a d/NEWS to make user aware of this? or in release notes. However I want to known if it's too late for buster, given the fact that synaptic is popular... If it's too late whatever, I'll just stop here. -- Shengjing Zhu

Bug#874950: New version stable?

Hi Diego, On Wed, Jul 24, 2019 at 12:32 AM Shengjing Zhu wrote: > > On Mon, 22 Jul 2019 01:09:00 -0300 Diego Sarzi wrote: > > Thank you Shenging Zhy for the contribution. > > > > Can you tell me how is the stability of keepassx with its modifications, > > referri

Bug#874950: New version stable?

(CC previous sponsor as well) Hi, On Thu, Aug 29, 2019 at 5:36 PM Shengjing Zhu wrote: > > Hi Diego, > > On Wed, Jul 24, 2019 at 12:32 AM Shengjing Zhu wrote: > > > > On Mon, 22 Jul 2019 01:09:00 -0300 Diego Sarzi wrote: > > > Thank you Shenging Zhy for the

Bug#933958: The golang FTBFS on amd64 should be fixed

in dh-golang won't fix the compiler itself. -- Shengjing Zhu

Bug#932582: anbox: ignores mouse input

the debian version. P.S. the snap version has a software emulation mode, which is not available in debian version, but it would help if you hardware is doing something weird. -- Shengjing Zhu

Bug#943654: anbox: GUI crashes after "starting"

Control: tags -1 + moreinfo unreproducible Control: severity -1 normal On Sun, Oct 27, 2019 at 10:52 PM Shengjing Zhu wrote: > > On Sun, Oct 27, 2019 at 10:48 PM Matheus Mello > wrote: > > > > Package: anbox > > Version: 0.0~git20190124-1 > > Severity: grave &

Bug#942403: #942403 golang-github-hashicorp-raft breaks golang-github-canonicalltd-raft-membership autopkgtest

ckage depends on them. > Agreed. I packaged them at Debconf18, helping @nodens for packaging lxd. Since the latest version of lxd doesn't need them, I think they can be removed. -- Shengjing Zhu

Bug#943623: objects in libclangIndex.a are llvm ir bitcode

Package: libclang-9-dev Version: 1:9.0.0-1 Severity: serious Control: affects -1 ccls As for 1:9.0.0-1 ar x /usr/lib/llvm-9/lib/libclangIndex.a file *.o CodegenNameGenerator.cpp.o: LLVM IR bitcode CommentToXML.cpp.o: LLVM IR bitcode FileIndexRecord.cpp.o: LLVM IR bitcode

Bug#943654: anbox: GUI crashes after "starting"

of two systemd services. Please run following commands and give back your results. ls /var/lib/anbox/android.img systemctl status anbox-container-manager.service systemctl --user status anbox-session-manager.service -- Shengjing Zhu

Bug#942026: runc: CVE-2019-16884

Package: runc Severity: grave Tags: security upstream Justification: user security hole Control: affects -1 docker.io Control: clone -1 -2 Control: retitle -2 golang-github-opencontainers-selinux-dev: CVE-2019-16884 https://github.com/opencontainers/runc/issues/2128 runc through 1.0.0-rc8, as

Bug#942027: golang-github-opencontainers-selinux-dev: CVE-2019-16884

Package: runc Followup-For: Bug #942027 Control: reassign -1 golang-github-opencontainers-selinux-dev Forget to reassign...

Bug#951249: marked as pending in panicparse

Control: tag -1 pending Hello, Bug #951249 in panicparse reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#952173: golang-gopkg-gorethink-gorethink.v3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 returned exit code 1

On Tue, Feb 25, 2020 at 1:35 AM Anthony Fok wrote: > > Hi Shengjing, > > Thanks for looking into this too. I'm sorry for not recording my findings > here before going to bed, causing duplication of work... > Nevermind, I have learned some (surprising) Perl knowledge... -- Shengjing Zhu

Bug#952173: golang-gopkg-gorethink-gorethink.v3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 returned exit code 1

on go1\.([0-9]+)/); if (_go1_has_minor(10)) { $this->doit_in_builddir("go", "test", "-vet=off", "-v", @_, get_targets()); } else { This package can be built. But how could this line affect the result. -- Shengjing Zhu

Bug#952173: marked as pending in dh-golang

Control: tag -1 pending Hello, Bug #952173 in dh-golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#952173: marked as pending in dh-golang

Control: tag -1 pending Hello, Bug #952173 in dh-golang reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#951249: panicparse: FTBFS on arch:all

github-maruel-panicparse-dev and bin:panicparse. Now the logs says it can't find golang-github-maruel-panicparse-dev. Is there any change in debci/autopkgtest recently? I think such problem hasn't occurred previously, and the code in autopkgtest-pkg-go hasn't been changed for a long time. -- Shengjing Zhu

Bug#948734: The package should be in contrib section

Source: cyphesis-cpp Version: 0.7.0~snap1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This package now installs the real program via snap. This shouldn't be in main. -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCXhtRIBAcemhzakBkZWJp

Bug#954565: marked as pending in golang-github-grpc-ecosystem-go-grpc-prometheus

Control: tag -1 pending Hello, Bug #954565 in golang-github-grpc-ecosystem-go-grpc-prometheus reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#956502: docker: Error response from daemon: no status provided on response: unknown.

://buildd.debian.org/status/fetch.php?pkg=docker.io=amd64=19.03.6%2Bdfsg1-3=1586598671=0 -- Shengjing Zhu

Bug#956502: docker: Error response from daemon: no status provided on response: unknown.

m/moby/moby/blob/19.03/hack/dockerfile/install/containerd.installer It seems they just build from containerd upstream tree. -- Shengjing Zhu

Bug#956502: docker: Error response from daemon: no status provided on response: unknown.

On Mon, Apr 13, 2020 at 2:52 PM Shengjing Zhu wrote: > > On Mon, Apr 13, 2020 at 12:05 PM Arnaud Rebillout > wrote: > [...] > > It's unfortunate that upstream does not provide a source package for > > containerd.io, they only provide the binary package AFAIK. > &g

Bug#956955: 0.21.0 causes FTBFS in Vault

On Fri, Apr 17, 2020 at 5:10 PM Shengjing Zhu wrote: > > On Fri, Apr 17, 2020 at 4:30 PM Dmitry Smirnov wrote: > > > > Source: golang-google-api > > Version: 0.21.0-1 > > Severity: serious > > Control: affects -1 src:vault > > > > Recent up

Bug#956955: 0.21.0 causes FTBFS in Vault

t/04e895daa125587fbfc577d745cca1b223a74ed7 Since vault is experimental only, I didn't notice this when run ratt before uploading... -- Shengjing Zhu

Bug#956955: 0.21.0 causes FTBFS in Vault

On Fri, Apr 17, 2020 at 6:01 PM Dmitry Smirnov wrote: > > On Friday, 17 April 2020 7:13:02 PM AEST Shengjing Zhu wrote: > > While golang-github-hashicorp-go-gcp-common-dev has been packaged, and > > the packaged version includes this fix, I think you can use this > > i

Bug#959685: security concerns for stable release

heir options. -- Shengjing Zhu

Bug#960759: golang-1.14: FTBFS on mipsel

even when error occurred > > I'm not sure if it will fix the issue or not, but we might need it anyway to > cope with slow machines > I think it may fix the timeout issue on armhf, https://buildd.debian.org/status/logs.php?pkg=golang-1.14=1.14.3-1=armhf -- Shengjing Zhu

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

I can see both php-fpm and systemctl maintainers have good reasons to do what they did. So taking one step back, does it make sense to dpkg-divert /usr/bin/systemctl?

Bug#969227: FTBFS with new runc 1.0.0~rc92 and libcap2 2.43

ldd. Indeed, it's skipped. Seems sbuild gives me a shell with root when building fails, which makes this test to be run. -- Shengjing Zhu

Bug#971789: FTBFS: Could not determine section for ./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1

Package: docker.io Version: 19.03.13+dfsg1-2 Severity: serious X-Debbugs-Cc: z...@debian.org Maybe due to the go-md2man v2 transition, docker.io is now FTBFS. dh_installman: warning: Section for ./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1 is computed as "2020", which is not a

Bug#971868: Should be removed now?

Package: golang-1.14 Severity: serious X-Debbugs-Cc: z...@debian.org So, we have updated golang-defaults to 1.15. Like buster, bullseye seems to be having only one version of Go compiler. Let's see if anyone wants 1.14 for bullseye. Or later we can convert this to RM bug for ftp.d.o.

Bug#952536: marked as pending in etcd

Control: tag -1 pending Hello, Bug #952536 in etcd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#971163: marked as pending in golang-github-containers-ocicrypt

Control: tag -1 pending Hello, Bug #971163 in golang-github-containers-ocicrypt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#971168: marked as pending in golang-gopkg-square-go-jose.v2

Control: tag -1 pending Hello, Bug #971168 in golang-gopkg-square-go-jose.v2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

  1   2   3   4   >