[pkg-go] golang-github-cespare-xxhash_2.1.1-1~bpo10+1_amd64.changes ACCEPTED into buster-backports->backports-policy, buster-backports

2021-03-16 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Mar 2021 23:19:28 +0530 Source: golang-github-cespare-xxhash Binary: golang-github-cespare-xxhash-dev Architecture: source all Version: 2.1.1-1~bpo10+1 Distribution: buster-backports Urgency: medium Maintainer:

[pkg-go] Bug#983874: gitaly: fails to install: Could not find gem 'rugged (~> 0.28)'

2021-03-16 Thread Kristof Csillag
Package: gitaly Followup-For: Bug #983874 I am seeing the same thing. This also makes gitlab unusable. Is there any update about this? A severe error has been reported, and there is no reply for two weeks. Is this package supposed to be actually used by people? -- System Information: Debian Rel

[pkg-go] Bug#985354: mtail: service unit fails to start on Bullseye

2021-03-16 Thread Filippo Giunchedi
Package: mtail Version: 3.0.0~rc43-1+b1 Severity: important mtail.service fails to start on Bullseye due to cgroup v2 / unified hierarchy: $ systemctl status mtail ● mtail.service - MTail Loaded: loaded (/lib/systemd/system/mtail.service; enabled; vendor preset: enabled) Active: failed

[pkg-go] Processing of mtail_3.0.0~rc43-2_source.changes

2021-03-16 Thread Debian FTP Masters
mtail_3.0.0~rc43-2_source.changes uploaded successfully to localhost along with the files: mtail_3.0.0~rc43-2.dsc mtail_3.0.0~rc43-2.debian.tar.xz mtail_3.0.0~rc43-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) _

[pkg-go] mtail_3.0.0~rc43-2_source.changes ACCEPTED into unstable

2021-03-16 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 16 Mar 2021 21:11:14 +0100 Source: mtail Architecture: source Version: 3.0.0~rc43-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Filippo Giunchedi Closes: 985354 Chang

[pkg-go] Bug#985354: marked as done (mtail: service unit fails to start on Bullseye)

2021-03-16 Thread Debian Bug Tracking System
Your message dated Tue, 16 Mar 2021 20:33:37 + with message-id and subject line Bug#985354: fixed in mtail 3.0.0~rc43-2 has caused the Debian Bug report #985354, regarding mtail: service unit fails to start on Bullseye to be marked as done. This means that you claim that the problem has been

[pkg-go] Bug#985379: podman: fails to run on freshly installed Bullseye, runtime "crun" not found: invalid argument

2021-03-16 Thread Filippo Giunchedi
Package: podman Version: 3.0.1+dfsg1-1 Severity: important This is the same as #971253. Specifically, 'runc' is installed as the first Depend, however podman defaults to 'crun'. I think podman should depend on 'crun' first so it works out of the box (and with cgroups v2). root@host1:~# podman ima