Bug#1069310: marked as pending in golang-github-hanwen-go-fuse

Control: tag -1 pending Hello, Bug #1069310 in golang-github-hanwen-go-fuse 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#1071035: marked as pending in golang-github-fatih-semgroup

Control: tag -1 pending Hello, Bug #1071035 in golang-github-fatih-semgroup 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#1071038: golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock

Control: tag -1 patch On 5/13/24 9:15 AM, Reinhard Tartler wrote: I suspect this issue may be triggered by the upload of golang-golang-x-sync 0.7.0 to sid. #1071035 is another issue related to code changes in the semaphore implmentation. in google-api-go, I've found exactly one upstream

Bug#1071038: golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock

I suspect this issue may be triggered by the upload of golang-golang-x-sync 0.7.0 to sid. #1071035 is another issue related to code changes in the semaphore implmentation. in google-api-go, I've found exactly one upstream commit that we don't currently have in debian in the 'support/bundler'

Bug#1071035: FAIL: TestGroup_deadlock

Control: reassign -1 golang-golang-x-sync 0.7.0 Control: affects -1 golang-github-fatih-semgroup This seems to be related to upgrading golang-golang-x-sync to 0.7.0. This is how to reproduce is using pristine upstream sources: siretart@x1:/tmp/docker.io $ git clone

Bug#1071035: FAIL: TestGroup_deadlock

Control: tag -1 patch I've filed https://github.com/fatih/semgroup/pull/7 as a workaround. Anthony, what's your take on this, should we include that patch in the Debian Package? -rt From bb5f94c0d8e6ddf1f24f673303d73e84c285e1ac Mon Sep 17 00:00:00 2001 From: Reinhard Tartler Date: Mon, 13

Bug#1071038: golang-google-api: timeout in test TestBundlerTimeBasedFlushDeadlock

Source: golang-google-api Version: 0.61.0-4 Severity: serious Justification: FTBFS I am unable to build the package (reliably) on my laptop. It turns out that the test TestBundlerTimeBasedFlushDeadlock times out after 10 minutes: It seems that the test introduced by 6114940 is

Bug#1071035: FAIL: TestGroup_deadlock

Source: golang-github-fatih-semgroup Version: 1.2.0-2 Severity: serious Justification: FTBFS Your package fails to build from source, more specifically, when running the test suite. I can reproduce on my amd64 laptop. Here is the relevant part of the log: dh_auto_test

Bug#1070821: Turns out to be flaky tests

Control: Severity -1 important Control: Retitle -1 testsuite is flaky Looking at the build failures, there appears to be at least two tests that are flaky. One being in daemon/logger: https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-3/engine/daemon/logger/copier_test.go/#L261-L265 The

Bug#1068755: closing 1068755

close 1068755 20.10.25+dfsg1-3 thanks docker.io 20.10.25+dfsg1-3 comes with a backported patch that addresses this FTBFS

Bug#1069310: FTBFS: tests failed

I spent about half an hour looking at this, and wanted to share my thoughts: - the build / tests succeed on all architectures but mips64el - the panic in question appears to come from here: https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13 -- a

Bug#1068755: FTBFS: tests failed

please ignore the above, it was meant to be sent to #1069310 instead On Mon, May 6, 2024 at 6:34 AM Reinhard Tartler wrote: > I spent about half an hour looking at this, and wanted to share my > thoughts: > > - the build / tests succeed on all architectures but mips64el &

Bug#1068755: FTBFS: tests failed

I spent about half an hour looking at this, and wanted to share my thoughts: - the build / tests succeed on all architectures but mips64el - the panic in question appears to come from here: https://sources.debian.org/src/golang-github-hanwen-go-fuse/2.4.2-2/fuse/print_linux.go/#L13 -- a

Bug#1068755: docker.io: FTBFS: failing tests

/d33659365984dbb47b6aac2836727e507c1ce737 to let the salsa pipeline work on it. I plan to make a team-upload tomorrow or later in the week. Please let me know if you have concerns or thoughts on this. Thanks -rt On Sun, May 5, 2024 at 11:20 AM Reinhard Tartler wrote: > I've been looking at this t

Bug#1068755: marked as pending in docker.io

Control: tag -1 pending Hello, Bug #1068755 in docker.io 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#1068755: docker.io: FTBFS: failing tests

I've been looking at this test failure, but remain puzzled. Basically, the source for this test is here: https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-2/engine/distribution/xfer/download_test.go/#L364-L429. This test is testing code in

Bug#1061032: Not reproducible

Control: severity -1 normal Control: tags -1 unreproducible Hey Lucas, I've been unable to reproduce, please see my build log attached to this email. Maybe some test is flaky? I'm lowering severity as I am unconvinced that removing this package from testing, along with all of its reverse

Bug#1058795: Docker.io breaks libvirt/qemu bridge network

Control: severity -1 minor Control: tag -1 wontfix Control: retitle -1 Docker.io breaks libvirt/qemu bridge network Please review the package's postinst script to convince yourself that the Debian docker.io package does not ship any firewall rules:

Bug#1054755: closing 1054755

close 1054755 4.7.1+ds4-4 thanks Fixed in earlier upload

Bug#1054460: marked as pending in libpod

Control: tag -1 pending Hello, Bug #1054460 in libpod 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#1050299: rust-webpki: RUSTSEC-2023-0052

Hi Salvatore, thanks for filing this bug. > Please see https://rustsec.org/advisories/RUSTSEC-2023-0052.html . This page is giving a very general description of the problem: >> When this crate is given a pathological certificate chain to validate, it >> will spend CPU time exponential with

Bug#1042194: netavark: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~)

Thank you so much for these patches. May I ask you to NMU this and and potentially aardvark-dns as necessary? -- I'm about to start traveling, and will have very limited internet access. No need to wait for NMU delays or things. Your diff looks great to me! best, -rt On 8/10/23 8:37 PM,

Bug#1038870: marked as pending in golang-github-grpc-ecosystem-grpc-gateway

Control: tag -1 pending Hello, Bug #1038870 in golang-github-grpc-ecosystem-grpc-gateway 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#1041040: Fwd: Bug#1041040: aspectc++ autopkg tests fail with GCC 13

On 7/23/23 9:13 AM, Reinhard Tartler wrote: Turns out, the fix only works on amd64/i386, but not for instance on Arm, Matthias, our GCC maintainer has filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041040 for this. I looked over the patch and couldn't find anything architecture

Bug#1028810: aspectc++: FTBFS: ld: cannot find -lPolly: No such file or directory

Control: reassign -1 llvm-14 Control: affects -1 aspectc++ Hi Lucas, thanks for filing this report. My understanding of this issue is that a recent change in llvm 14 leads to the list of libraries listed by `llvm-config-14 --libs` to be incomplete. I think that this build would succeed if it

Bug#1026588: Fix pending in the NEW queue

Control: tag 1026588 pending Control: block 1026598 by 1026588 I really should have mentioned this bug in debian/changelog before uploading. It is currently pending at https://ftp-master.debian.org/new/rust-trust-dns-server_0.22.0-1.html Dear ftp-master, happy holidays! Any chance you could

Bug#1027116: marked as pending in golang-github-containers-storage

Control: tag -1 pending Hello, Bug #1027116 in golang-github-containers-storage 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#1026598: blocked by NEW queue

In order to fix this issue, I'm waiting for https://ftp-master.debian.org/new/rust-trust-dns-server_0.22.0-1.html to make it out of (binary) NEW. -- regards, Reinhard

Bug#1024032: rust-criterion: FTBFS: needs to be compiled against librust-cast (>> 0.3)

Package: librust-criterion+async-futures-dev Severity: serious X-Debbugs-Cc: none, Reinhard Tartler The rust-cast crate has been updated from version 0.2 to 0.3 on 2022/11/11. Can you please build against that new version of rust-cast? -rt -- System Information: Debian Release: bookworm/sid

Bug#1019206: librust-criterion+async-std-dev: Package is uninstallable, rust-async-std missing in debian

Package: librust-criterion+async-std-dev Severity: serious Justification: packages must be installable, prevents other packages from reaching testing X-Debbugs-Cc: d...@jones.dk, debian-r...@lists.debian.org The package librust-criterion+async-std-dev is currently uninstallable in unstable and

Bug#1011869: marked as pending in golang-github-containers-buildah

Control: tag -1 pending Hello, Bug #1011869 in golang-github-containers-buildah 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#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

My hunch might have been correct, the fresh upload did build successfully on buildds. yay! On Sun, Jun 5, 2022 at 7:12 AM Reinhard Tartler wrote: > Just a hunch, is it possible that your build environment did not have the > package 'ca-certificates' present whereas mine does? > &

Bug#1011875: marked as pending in golang-github-opencontainers-runtime-tools

Control: tag -1 pending Hello, Bug #1011875 in golang-github-opencontainers-runtime-tools 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#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

Just a hunch, is it possible that your build environment did not have the package 'ca-certificates' present whereas mine does? I wonder whether I need to add 'ca-certificates' to "Build-Depends". What do you think? On Sun, Jun 5, 2022 at 7:10 AM Reinhard Tartler wrote: >

Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

Please find the buildlog of my attempt attached to this email As far as I can tell, the tests are executing in the same way as in your logs, but I may be missing something. golang-github-opencontainers-runtime-tools_0.9.0+git20220423.g0105384-1_amd64-2022-06-05T02:02:05Z.build Description:

Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

Control: tags -1 = moreinfo unreproducible Hi Lucas, Thank you for reaching out. I've been looking into this report and am a bit confused. I'm trying to reproduce it on my laptop, but it builds just fine for me. Can you please help me understand why it would fail on your end? -- regards,

Bug#1010000: marked as pending in libpod

Control: tag -1 pending Hello, Bug #101 in libpod 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#1009374: marked as pending in libpod

Control: tag -1 pending Hello, Bug #1009374 in libpod 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#1005147: marked as pending in golang-github-sylabs-sif

Control: tag -1 pending Hello, Bug #1005147 in golang-github-sylabs-sif 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#1008396: marked as pending in consul

Control: tag -1 pending Hello, Bug #1008396 in consul 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#889714: marked as pending in etcd

Control: tag -1 pending Hello, Bug #889714 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#994451: marked as pending in golang-github-opencontainers-specs

Control: tag -1 pending Hello, Bug #994451 in golang-github-opencontainers-specs 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#1003663: marked as done (golang-github-containers-image: FTBFS: tests fail with 'key has been revoked')

> > > Hi Andreas, thank you for your report, > > I've tried rebuilding the package on my laptop in a clean sid chroot, > and for some reason, it works just fine. > > Can you please have a look at my build log and help me understand why > the build is failing for you but not for me? > > I looked a

Bug#1000318: docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile

On 11/21/21 8:14 AM, Reinhard Tartler wrote: > Source: docker.io > Version: 20.10.5+dfsg1-1 > Severity: serious > Justification: FTBFS - prevents depending packages from migrating > > the docker.io package FTBFS on mipsen in the same way: > > - > https://buildd.

Bug#1000318: docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile

Source: docker.io Version: 20.10.5+dfsg1-1 Severity: serious Justification: FTBFS - prevents depending packages from migrating the docker.io package FTBFS on mipsen in the same way: - https://buildd.debian.org/status/fetch.php?pkg=docker.io=mips64el=20.10.10%2Bdfsg1-1=1636015943=0 -

Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue

Control: tag -1 patch On Wed, Nov 10, 2021 at 7:55 AM Shengjing Zhu wrote: > > > > Cloud you backport following commit? > > > > > > > https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b > > > > > This patch updates libocispec/Makefile.am, which is needed to

Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue

s that have actually been tested. I don't think it is a good use of Debian's developers' time to play this game of catching up. On Wed, Nov 10, 2021 at 7:27 AM Reinhard Tartler wrote: > That's not sufficient. > > the commit you point out does two things: > > - update the submo

Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue

you backport following commit? > > https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b > > > (Sent on my mobile phone) > > Reinhard Tartler 于 2021年11月10日周三 07:05写道： > >> I took a look at the issue and here are my thoughts: >> >>

Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue

I took a look at the issue and here are my thoughts: - the build error is a failure to link some test binaries. excluding them from the build might be possible with some patching. - I've upgraded the package to the latest upstream 1.3, and was seeing exactly the same build failure - the build

Bug#997133: More information in the ubuntu bugtracker

the ubuntu tracker claims this is golang 1.16 related: https://bugs.launchpad.net/debian/+source/consul/+bug/1940152 not sure how to proceed here, though... -- regards, Reinhard

Bug#997133: Relevant part of the consul log

Here is the actual relevant part of the build log: === RUN TestDynamicTLSConfig tls_test.go:263: Error Trace: tls_test.go:263 tls_test.go:339 Error: Not equal: expected:

Bug#994451: golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm

. On Mon, Sep 27, 2021 at 12:08 PM Reinhard Tartler wrote: > > On Thu, Sep 16, 2021 at 4:18 AM Bastien Roucariès < > roucaries.bast...@gmail.com> wrote: > >> Package: golang-github-containers-common >> Version: 0.33.4+ds1-1 >> Severity: critical >> Tags: up

Bug#994451: golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm

On Thu, Sep 16, 2021 at 4:18 AM Bastien Roucariès < roucaries.bast...@gmail.com> wrote: > Package: golang-github-containers-common > Version: 0.33.4+ds1-1 > Severity: critical > Tags: upstream > Forwarded: > https://github.com/containers/common/commit/42d1db16bfc0dbaee5781d230dc2bcbaa0849c6e >

Bug#987207: podman not running out-of-the-box as root

Control: tag -1 pending Control: severity -1 important Control: retitle -1 Missing dependency on "iptables" On Wed, Apr 21, 2021 at 6:07 AM Laurent Bigonville wrote: > So the problem here is, again, linked to the fact that I'm using a test > SELinux policy that doesn't contain all the needed

Bug#987207: podman not running out-of-the-box as root

Control: tag -1 moreinfo Hi Laurent, I've downloaded the Bullseye Alpha 3 debian installer and installed using kvm to have a super clean new system. Unfortunately, I was unable to reproduce the issue that you described below. (I did find some issues with rootless podman outside of a

Bug#983395: podman lacks a runtime dependency on rootlesskit

Control: retitle -1 Please print nicer error message if newuidmap is not installed Control: severity -1 wishlist Control: tag -1 upstream Andrey, please stop this bug ping-pong. Feel free to escalate this to the TC, but I don't think you are being reasonable here. -- regards, Reinhard

Bug#982967: FTBFS: unsat-dependency: golang-github-rsc-letsencrypt-dev:amd64

Source: docker.io Version: 19.03.4+dfsg2-2 Severity: serious Justification: FTBFS During a test rebuild of the docker.io package, I noticed that it declares a build-depends relationship on a non-existing package: , | Install main build dependencies (apt-based resolver) |

Bug#982957: FTBFS: unsat-dependency: golang-github-rsc-letsencrypt-dev:amd64

Source: docker-registry Version: 2.7.1+ds2-7 Severity: serious Justification: FTBFS In a rebuild, I noticed that this package fails to build from source: , | Install main build dependencies (apt-based resolver) | | | Installing build

Bug#977542: golang-github-revel-revel: Depends on network in tests

Got it. On Tue, Feb 16, 2021 at 4:03 PM Sebastian Ramacher wrote: > Control: severity -1 serious > > [...] > Tests are executed as part of the binary target: > > dh binary --no-act | grep auto_test >dh_auto_test > > So the "no required targets may attmept network access" rule applies. >

Bug#977542: marked as pending in golang-github-revel-revel

Control: tag -1 pending Hello, Bug #977542 in golang-github-revel-revel 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#977542: golang-github-revel-revel: Depends on network in tests

Control: severity -1 important Dear release team, I'm writing as a member of the pkg-go team and am mostly concerned about potential removal of depending packages. The package itself appears to be fine. The tests fail if and only if the test setup doesn't provide (proper) internet connectivity.

Bug#982288: podman: Can't run caontainers - failed to connect to container's attach socket

Control: tag -1 upstream Control: severity important Control: retitle -1 rootless podman fails with very long uids On Mon, Feb 8, 2021 at 6:09 AM Sam Morris wrote: > Package: podman > Version: 3.0.0~rc2+dfsg1-2+b1 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc:

Bug#979313: marked as pending in libpod

Control: tag -1 pending Hello, Bug #979313 in libpod 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#976924: Test timeouts on ppc64el not RC

Control: severity -1 normal Looking at the logs, it really looks like timeouts in the testsuite. We could disable the tests on problematic architectures, patches welcome. As a workaround, I'd suggest building the package with export DEB_BUILD_OPTIONS=notest. With this, I'm downgrading the

Bug#976509: marked as pending in golang-github-shirou-gopsutil

Control: tag -1 pending Hello, Bug #976509 in golang-github-shirou-gopsutil 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#977502: marked as pending in libpod

Control: tag -1 pending Hello, Bug #977502 in libpod 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#977502: marked as pending in libpod

Control: tag -1 pending Hello, Bug #977502 in libpod 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#977502: podman,golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz

Hi Valentin, I just received the bug below. It seems that the manpage duplication is actually upstream: - https://github.com/containers/common/blob/master/docs/containers-mounts.conf.5.md - https://github.com/containers/podman/blob/master/docs/source/markdown/containers-mounts.conf.5.md They

Bug#976943: golang-github-seccomp-libseccomp-golang: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 github.com/seccomp/libsec

> === RUN TestRuleAddAndLoad > seccomp_test.go:588: Syscall should have returned error code! > --- FAIL: TestRuleAddAndLoad (0.00s) Source code is here: https://sources.debian.org/src/golang-github-seccomp-libseccomp-golang/0.9.1-2/seccomp_test.go/#L529-L589 This test is basically

Bug#976543: marked as pending in golang-github-rcrowley-go-metrics

Control: tag -1 pending Hello, Bug #976543 in golang-github-rcrowley-go-metrics 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#976509: golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/

Control: forwarded -1 https://github.com/shirou/gopsutil/issues/881 I'm having a hard time seeing bugs like this as RC-critical. Looking at the testsuite more specifically, I strongly believe this is upstream bug https://github.com/shirou/gopsutil/issues/881 Lucas, can you please post

Bug#975584: marked as pending in consul

Control: tag -1 pending Hello, Bug #975584 in consul 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#976410: glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ...

On Fri, Dec 4, 2020 at 3:24 PM Aurelien Jarno wrote: > > I have tried and for me the issue is reproducible with both old and new > glibc. I am therefore reassign the bug to libpod. > This is because of an upstream update in a dependency. It should be very straight-forward to fix. Unfortunately,

Bug#968207: marked as pending in libpod

Control: tag -1 pending Hello, Bug #968207 in libpod 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#961814: Debian Bugs information: logs for Bug#961814

Thanks! Will incorporate in the next upload.

Bug#961814: Debian Bugs information: logs for Bug#961814

On Mon, Aug 3, 2020 at 8:30 AM Shengjing Zhu wrote: > If I read the comments in upstream issue correctly, it will be solved in 2 > months (they said 6 months later at April). What's the urgent thing we need > to address in this two months? > I realized that podman 2.0 requires this newer

Bug#961814: Debian Bugs information: logs for Bug#961814

>From: Shengjing Zhu >To: Debian Bug Tracking System >Subject: Not ready for using >Date: Fri, 29 May 2020 23:36:43 +0800 > > Package: golang-google-protobuf > Severity: serious > > Though it has been packaged, it's not ready for using. > > The current version will generate

Bug#966501: 2.0.3 REST API regression: Failed to parse parameters for /v1.12/libpod/events: unexpected end of JSON input

Control: severity -1 important Hi Martin, On Wed, Jul 29, 2020 at 8:42 AM Martin Pitt wrote: > Package: podman > Version: 2.0.3+dfsg1-1 > Severity: serious > Tags: upsteam fixed-upstream > > Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman > and > any other API user.

Bug#950816: marked as pending in mpv

Control: tag -1 pending Hello, Bug #950816 in mpv 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#965114: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency

Package: golang-github-shenwei356-bwt Severity: serious Justification: FTBFS While trying to rebuild this package, it appears it build depends on the package golang-github-shenwei356-bpool-dev Find the buildlog attached to this email. golang-github-shenwei356-bwt_0.0~git20200418.ae79c98-2

Bug#964870: snapd: FTBFS: FAIL: squashfs_test.go:130: SquashfsTestSuite.TestInstallSimpleNoCp

Package: snapd Version: 2.44.1-2 Severity: serious While trying to rebuild the package, I noticed that one of the tests in the testsuite fails: === RUN Test -- FAIL: squashfs_test.go:130:

Bug#964045: marked as pending in golang-github-shirou-gopsutil

Control: tag -1 pending Hello, Bug #964045 in golang-github-shirou-gopsutil 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#964045: marked as pending in golang-github-shirou-gopsutil

Control: tag -1 pending Hello, Bug #964045 in golang-github-shirou-gopsutil 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#963346: marked as pending in golang-github-openshift-api

Control: tag -1 pending Hello, Bug #963346 in golang-github-openshift-api 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#961421: marked as pending in libpod

Control: tag -1 pending Hello, Bug #961421 in libpod 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#953540: [Aspectc-developers] Fwd: Bug#953540: aspectc++: FTBFS on armel

to be on most other platforms. > > (2) Why is "--as-needed ... --no-as-needed" necessary? > > (3) Could -latomic also be placed at the end of the list of libraries > (behind the additional libraries needed for Clang 9.0.x)? > > Cheers, > > Olaf > > A

Bug#947486: FTBFS due to failing test case TestDefaultCache

Thanks for this bug report. Your snippet above unfortunately skips the actual error that is happening. Here is the relevant error: === RUN TestDefaultCache time="2019-12-28T16:50:03Z" level=error msg="/tmp/TestDefaultCache173385111/unwritable: {name:\"unwritable\", size:4096, mode:0x8140,

Bug#938818: whatthepatch: diff for NMU version 0.0.5-2.1

Thanks for the upload, Sandro. Happy holidays! rt On December 23, 2019 11:22:37 PM GMT+01:00, Sandro Tosi wrote: >Control: tags 938818 + patch > > >Dear maintainer, > >I've prepared an NMU for whatthepatch (versioned as 0.0.5-2.1). The >diff >is attached to this message. > >Regards. -- Sent

Bug#929697: fixed in pyglet 1.3.0-2.1

On 6/13/19 3:15 AM, Paul Gevers wrote: > Hi, > > On Tue, 04 Jun 2019 21:03:47 + Reinhard Tartler > wrote: >>* Disable ClockTimingTestCase (Closes: #929697) > > ^^ If this is supposed to go into buster, somebody has to prepare a > targeted upload to unstab

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys

Agreed! In this case, the bug was reported on Aug 24 2018 by Adrian Bunk. It was removed about a months later, namely on September 23, for failing to build from source. Four weeks is arguably quite fast. Or quite slow, depending on whom you talk to. I probably could have reacted by disabling the

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys

On Wed, Jun 5, 2019 at 7:46 PM Chris Wilson wrote: > Hi Reinhard, > > Could you have a look at this patch > (documented > here > ) > to see if it's

Bug#928948: hostapd: syslog is spammed every two seconds

Hi, I'm trying to help out with remaining RC bugs for buster. > The postinst is set up in a way so that if /etc/hostapd/hostapd.conf > is not readable or missing, the hostapd.service is masked during the > package installation unless it was already running. I wonder if that is really necessary

Bug#929697: pyglet: diff for NMU version 1.3.0-2.1

is allowed in Python2.6 + + [ Reinhard Tartler ] + * Non-Maintainer upload. + * Disable ClockTimingTestCase (Closes: #929697) + + -- Reinhard Tartler Sun, 02 Jun 2019 15:17:34 -0400 + pyglet (1.3.0-2) unstable; urgency=medium [ Scott Kitterman ] diff -Nru pyglet-1.3.0/debian/rules pyglet

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys

On Fri, May 31, 2019 at 5:03 PM Chris Wilson wrote: > Hi Reinhard, > > Presumably the many other affected packages have had similar difficulty in > developing a comprehensive solution? I also wasn't aware of a time > constraint. Not that it would have helped me much, as I was moving house, > but

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys

Hi Chris, On Sun, May 19, 2019 at 12:21 PM Chris Wilson wrote: > Hi Reinhard and all, > > Good news, I have just finished fixing this problem, and merged it into > master with https://github.com/boxbackup/boxbackup/pull/36. Please could > you cut a new Debian package release and see if the

Bug#926103: Freeze-exception for pcsc-cyberjack 3.99.5final.sp09-2

+ + * Acknoledge NMU. + * Bug fix: "driver breaks with pcsc-lite versions >= 1.8.21", thanks +to Peter Wienemann (Closes: #926103). + + -- Reinhard Tartler Mon, 08 Apr 2019 17:58:31 -0400 + pcsc-cyberjack (3.99.5final.sp09-1.1) unstable; urgency=medium * Non-maintainer

Bug#907135: [Box Backup] Debian now requires 2048bit RSA keys

> > On Mon, Jan 7, 2019, 16:58 Chris Wilson > >>> Hi Reinhard, >>> >>> If I make the workaround suggested on this thread >>> (change >>> SECLEVEL to 1 in /etc/ssl/openssl.cnf) then test/basicserver passes again. >>> This is at least a good

Bug#893227: libbluray FTBFS with openjdk-9

Hi Adrian, On Wed, Jan 23, 2019 at 12:54 PM Adrian Bunk wrote: > Due to popcon (and reverse dependencies) libbluray is a key package > that won't be autoremoved (otherwise it would have been autoremoved > from buster 9 months ago). > That's good to know, thanks for pointing it out. > A

Bug#893227: libbluray FTBFS with openjdk-9

Control: severity -1 important On Tue, Jan 22, 2019 at 7:48 AM Emmanuel Bourg wrote: > OpenJDK 8 will be kept in Buster but it should be used in exceptional > cases (for example the lombok package requires both OpenJDK 8 and 11 to > build). The default Java runtime for Buster is OpenJDK 11 and

Bug#893227: libbluray FTBFS with openjdk-9

t apparently we are just not quite there yet, please see Petri's message below. Can you please give us an update on the roadmap for Java? What's the status on removing openjdk-8 from buster? Best, -rt On Tue, Jan 22, 2019 at 3:02 AM Petri Hintukainen wrote: > Hello, > > On Wed, Jan 16, 2019

  1   2   3   4   5   >