Bug#995696: ITP: casa-formats-io -- Code to handle I/O from/to data in CASA format

[Ole Streicher]

Package: wnpp
Severity: wishlist
Owner: Ole Streicher 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org, 
debian-as...@lists.debian.org

* Package name: casa-formats-io
  Version : 0.1
  Upstream Author : Thomas Robitaille
* URL : http://casa-formats-io.readthedocs.org
* License : LGPL
  Programming Lang: Python
  Description : Code to handle I/O from/to data in CASA format

The casa-formats-io package is a small package which implements functionality 
to read data stored in CASA formats (such as .image datasets). This 
implementation is independent of and does not use casacore. The motivation for 
this package is to provide efficient data access via dask arraye, 
cross-platform data access, and data access with all modern Python versions.

It is a new build dependency of the "spectral-cube" package. I will maintain it
within the Debian Astro team in Salsa:

https://salsa.debian.org/debian-astro-team/casa-formats-io

Best regards

Ole

Bug#995704: ITP: golang-github-cloudwego-netpoll -- A high-performance non-blocking I/O networking framework, which focused on RPC scenarios

[Yanhao Mo]

Package: wnpp
Severity: wishlist
Owner: Yanhao 
X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org

* Package name: golang-github-cloudwego-netpoll
  Version : 0.0.4-1
  Upstream Author : Bytedance Inc.
* URL : https://github.com/cloudwego/netpoll
* License : Apache-2.0
  Programming Lang: Go
  Description : A high-performance non-blocking I/O networking
framework, which focused on RPC scenarios, developed by ByteDance.

 Netpoll is a high-performance non-blocking I/O networking framework,
 which focused on RPC scenarios, developed by ByteDance.

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

[Kentaro Hayashi]

Hi,

Thank you for your explanation.
Very informative.

Reply in this thread talks about +/~, but
I'm curious about repacking count. (Subject may be misleading...)

What do you think about it?

1. We should use +dfsg-1 style
2. We should use +dfsgN-1 style
3. We should use +dfsg.N-1 style
4. Other

Regards,




2021年10月2日(土) 22:03 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 the hint "dfsg"-
>
> When upstream codebase require repackaging for (only) other reasons than
> DFSG compliance I instead use the hint "ds" (as in "derived source").
>
> 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.
>
> I use + (plus) as delimiter when I cannot use ~ (tilde).
>
> Since you tried mentioned some statistics: It is indeed more popular to
> favor + over ~ but "popular practice" does not equal "best practice".
>
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private

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

[Russ Allbery]

Kentaro Hayashi  writes:

> What do you think about it?

> 1. We should use +dfsg-1 style
> 2. We should use +dfsgN-1 style
> 3. We should use +dfsg.N-1 style
> 4. Other

I would start with +dfsg-1 because it's fairly rare to have to iterate on
the repackaging.  You can then switch to +dfsgN-1 with the second and
subsequent repackagings if needed.  (Although if I knew in advance I would
probably need to iterate, I'd start with +dfsgN-1.)

There's an argument for consistency to always use +dfsgN-1, I guess, but I
don't think it matters enough to bother.

I would not use +dfsg.N-1.  It's not consistent with the other places
where we add suffixes, such as backporting and stable updates.

-- 
Russ Allbery (r...@debian.org)