Bug#1011716: libbluray: continue to FTBFS and VLC crash in stable

2022-09-21 Thread Christian Barcenas
On Wed, Sep 21, 2022 at 10:21 AM Sebastian Ramacher wrote: > Yes, that's all correct. But as you can see from the version graph at > the top of the bug report at https://bugs.debian.org/1011716, the > version in stable is not marked as fixed. There is no need to reopen > this bug report because

Bug#1011716: libbluray: continue to FTBFS and VLC crash in stable

2022-09-21 Thread Christian Barcenas
Hi. I am not an expert on Debian policy, so the following may be incorrect, but this was my reasoning for re-opening the bug: On Wed, Sep 21, 2022 at 2:21 AM Sebastian Ramacher wrote: > Please don't reopen it. We have version tracking to track this kind of > thinks. For the bullseye version,

Bug#1011716: libbluray: continue to FTBFS and VLC crash in stable

2022-09-20 Thread Christian Barcenas
reopen 1011716 tags 1011716 bullseye patch thanks Re-opening because I still see FTBFS on Bullseye 11.5 (stable), and this library causes a crash in VLC when certain Blu-rays are opened. I think an upload to stable-updates is necessary. Backporting the following patch from the packaging

Bug#999888: RFP: websocat -- A command line client for WebSockets

2021-11-17 Thread Christian Barcenas
Package: wnpp Severity: wishlist X-Debbugs-Cc: pkg-rust-maintain...@alioth-lists.debian.net * Package name: websocat Version : 1.9.0 Upstream Author : Vitaly "_Vi" Shukela * URL : https://github.com/vi/websocat * License : MIT Programming Lang: Rust

Bug#960650: InspIRCd Security Advisories 2019-02 and 2020-01

2020-09-11 Thread Christian Barcenas
I have prepared a draft 2.0.27-1+deb10u1 release for buster-security and uploaded it to mentors: https://mentors.debian.net/debian/pool/main/i/inspircd/inspircd_2.0.27-1+deb10u1.dsc Just need a maintainer to review and sponsor it, and to work with the Security team to get this uploaded to

Bug#960650: InspIRCd Security Advisories 2019-02 and 2020-01

2020-08-31 Thread Christian Barcenas
Control: retitle -1 InspIRCd Security Advisories 2019-02 and 2020-01 In addition to the 2020-01 advisory I also noticed that this package hasn't yet patched the 2019-02 advisory which is a similar crash/DoS bug. (https://docs.inspircd.org/security/2019-02/) 2019-02 and 2020-01 both affect

Bug#896165: ITP: bpftool -- utility for querying and updating BPF objects

2020-03-21 Thread Christian Barcenas
Control: reassign -1 wnpp Control: notfound -1 linux/4.16.5-1 Control: affects -1 src:linux Control: retitle ITP: bpftool -- utility for querying and updating BPF objects Control: owner -1 ! Hi all, I'm restructuring this as an ITP. I'm very keen to get bpftool in Debian as well, now that the

Bug#936911: librdkafka: Python2 removal in sid/bullseye

2020-03-13 Thread Christian Barcenas
Control: tags -1 patch Python is only used in a few small build scripts which are easy to patch for Python 3. I have submitted a merge request on Salsa containing (among other things) a fix for this issue: https://salsa.debian.org/kafka-team/librdkafka/-/merge_requests/1 Christian

Bug#945604: linux-source-5.4: Failed to build linux-source-5.4 in efi_set_secure_boot

2020-02-17 Thread Christian Barcenas
like it was originally supposed to gate the lock_kernel_down call(). I've attached a patch to honor this flag again, which should fix this issue. From de06de54508caf6bb1d3f25d4ef652d1360a43e0 Mon Sep 17 00:00:00 2001 From: Christian Barcenas Date: Mon, 17 Feb 2020 02:50:58 -0800 Subject: [PATCH

Bug#950760: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)

2020-02-06 Thread Christian Barcenas
I just noticed that your packaging repo is currently empty. Would you be able to push your current progress to Github so that it's easier to review the source package? On Thu, Feb 6, 2020 at 2:34 PM Sudip Mukherjee wrote: > So, do we also use epoch or shall I try the way which Paul suggested >

Bug#950760: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)

2020-02-05 Thread Christian Barcenas
Because this changes the versioning scheme from kernel releases (libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf version numbers (0.0.6-1), the epoch needs to be incremented to 1 I believe. CC'ing debian-devel for discussion/consensus, per Debian Policy Manual 5.6.12.

Bug#948260: RFS: golang-github-russellhaering-gosaml2/0.3.1-1 [ITP] -- Pure Go implementation of SAML 2.0 (library)

2020-01-08 Thread Christian Barcenas
Thanks for the review! On Wed, Jan 8, 2020 at 12:24 AM Dmitry Smirnov wrote: > I gave you "developer" access to the team repository. Could you please try to > push there? Great, I pushed successfully. I omitted the release tag/commit b007372 (UNRELEASED->unstable) in case further packaging

Bug#948260: RFS: golang-github-russellhaering-gosaml2/0.3.1-1 [ITP] -- Pure Go implementation of SAML 2.0 (library)

2020-01-05 Thread Christian Barcenas
ang-github-russellhaering-gosaml2/golang-github-russellhaering-gosaml2_0.3.1-1.dsc Changes since the last upload: * Initial release (Closes: #948190) * Backport patch for AuthnRequest ordering (upstream bug #45). Regards, -- Christian Barcenas

Bug#948190: ITP: golang-github-russellhaering-gosaml2 -- Pure Go implementation of SAML 2.0

2020-01-04 Thread Christian Barcenas
Package: wnpp Severity: wishlist Owner: Christian Barcenas * Package name: golang-github-russellhaering-gosaml2 Version : 0.3.1-1 Upstream Author : Russell Haering * URL : https://github.com/russellhaering/gosaml2 * License : Apache-2.0 Programming Lang: Go

Bug#948173: golang-thrift-dev: Go sources are installed into the wrong path

2020-01-04 Thread Christian Barcenas
Package: golang-thrift-dev Version: 0.13.0-2 Severity: important Right now Go source files are installed into /usr/share/gocode/src/thrift. This means that Debian packages trying to build via dh-golang must refer to the golang-thrift-dev sources using the import path "thrift". However, the Go

Bug#947281: inspircd: fails to start due to apparmor policy

2019-12-23 Thread Christian Barcenas
Source: inspircd Version: 3.4.0-1 Severity: important Tags: patch Dear Maintainer, The AppArmor policy that is included with the unstable inspircd package specifies an incorrect path to the pidfile for the inspircd daemon. As a result AppArmor blocks inspircd from writing its own pidfile during

Bug#945756: ITP: golang-github-flynn-noise -- Go implementation of the Noise Protocol Framework

2019-11-27 Thread Christian Barcenas
Package: wnpp Severity: wishlist Owner: Christian Barcenas * Package name: golang-github-flynn-noise Version : 0.0~git20180327.2492fe1-1 Upstream Author : Flynn * URL : https://github.com/flynn/noise * License : BSD-3-Clause Programming Lang: Go