Bug#995607: ITP: libfreeaptx -- Free implementation of Audio Processing Technology codec (aptX)

2021-10-02 Thread Kentaro Hayashi
Package: wnpp Severity: wishlist Owner: Kentaro Hayashi X-Debbugs-Cc: debian-devel@lists.debian.org, ken...@xdump.org * Package name: libfreeaptx Version : 0.1.1 Upstream Author : Hunter Wardlaw * URL : https://github.com/iamthehorker/libfreeaptx * License : L

Re: Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Jonas Smedegaard
Quoting Sean Whitton (2021-10-02 22:32:18) > On Sat 02 Oct 2021 at 03:03PM +02, Jonas Smedegaard wrote: > > > Quoting Kentaro Hayashi (2021-10-02 14:19:17) > >> I want to know about the best practice of +dfsg and +ds extension. > >> As far as I know, it is not well documented as a policy or devre

Re: Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Sean Whitton
Hello, On Sat 02 Oct 2021 at 03:03PM +02, Jonas Smedegaard wrote: > Quoting Kentaro Hayashi (2021-10-02 14:19:17) >> I want to know about the best practice of +dfsg and +ds extension. >> As far as I know, it is not well documented as a policy or devref. > > When upstream codebase in its pristine

Re: Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Russ Allbery
Jonas Smedegaard writes: > I use ~ (tilde) as delimiter when possible, to make room for an eventual > later release with the issues fixed, without needing ugly versioning or > being forced to wait for a later upstream release. The other advantage to using tilde is that if the repackaging to re

Re: Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Adam Borowski
On Sat, Oct 02, 2021 at 03:12:04PM +0200, Timo Röhling wrote: > * Jonas Smedegaard [2021-10-02 15:03]: > > I use ~ (tilde) as delimiter when possible, to make room for an eventual > > later release with the issues fixed, without needing ugly versioning or > > being forced to wait for a later upstr

Re: Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Jonas Smedegaard
Quoting Timo Röhling (2021-10-02 15:12:04) > * Jonas Smedegaard [2021-10-02 15:03]: > >I use ~ (tilde) as delimiter when possible, to make room for an > >eventual later release with the issues fixed, without needing ugly > >versioning or being forced to wait for a later upstream release. > Has t

Re: Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Timo Röhling
* Jonas Smedegaard [2021-10-02 15:03]: I use ~ (tilde) as delimiter when possible, to make room for an eventual later release with the issues fixed, without needing ugly versioning or being forced to wait for a later upstream release. Has this actually ever happened? I would expect that most up

Re: Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Jonas Smedegaard
Quoting Kentaro Hayashi (2021-10-02 14:19:17) > I want to know about the best practice of +dfsg and +ds extension. > As far as I know, it is not well documented as a policy or devref. When upstream codebase in its pristine form would violate the Debian Free Software Guidelines (DFSG), I would use

Q. What is the best practice about +dfsg and +ds extension?

2021-10-02 Thread Kentaro Hayashi
Hi, I want to know about the best practice of +dfsg and +ds extension. As far as I know, it is not well documented as a policy or devref. In practical side of view, it seems that it varies on each maintainer. Most well formalized document is "Choose a repack suffix" [2], addtionally, mentors.d.n

Bug#995564: ITP: golang-github-bytedance-gopkg -- Universal Utilities for Go

2021-10-02 Thread Yanhao Mo
Package: wnpp Severity: wishlist Owner: Yanhao X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org * Package name: golang-github-bytedance-gopkg Version : 0.0~git20210910.e4efae9-1 Upstream Author : Bytedance Inc. * URL : https://github.com/bytedanc

Porter roll call for Debian Bookworm

2021-10-02 Thread Graham Inggs
Hi We are doing a roll call for porters of all prospective release architectures. If you are an active porter behind one of these architectures [1] and intend to continue for the development cycle of Debian Bookworm (est. release mid-2023), please respond with a signed email containing the follow