Re: should all bug reports be filed against /source/ packages?

2019-10-26 Thread Paul Wise
On Wed, Oct 23, 2019 at 2:32 PM Ansgar wrote: > It gets confused if a source & binary package with the same name, but > otherwise unrelated exist; or when the same binary is built from > different sources on different architectures; or when binary and source > versions don't match (version trackin

Re: [RFC] Proposal for new source format

2019-10-26 Thread Russ Allbery
"Theodore Y. Ts'o" writes: > I do think, though that we should allow the specification of *multiple* > git repositories, with some kind of type specifier so it can be clear > whether a particular repository is just a read-only clone versus a > read/write "master" repository, and whether a reposit

Re: [RFC] Proposal for new source format

2019-10-26 Thread Theodore Y. Ts'o
On Wed, Oct 23, 2019 at 11:40:06AM -0700, Russ Allbery wrote: > Marvin Renich writes: > > > The source package has historically (prior to the widespread use of VCS) > > also provided the basis for future development. Since most development > > these days is done using VCS, it's natural to try to

Re: should all bug reports be filed against /source/ packages?

2019-10-26 Thread Bernd Zeimetz
On 10/23/19 11:53 PM, Moritz Mühlenhoff wrote: > Fully agreed. It's also hard for users to pinpoint the correct binary > package and they tend to get stale with changes to binary names anyway > (soname changes to libs etc.) I think its easier for users to find the binary package name, as the pa

Re: should all bug reports be filed against /source/ packages?

2019-10-26 Thread Guillem Jover
Hi! On Wed, 2019-10-23 at 08:32:11 +0200, Ansgar wrote: > the thread about naming (source) packages reminded me of an other thing: > Debian's bug tracking system currently (mostly) tracks bugs against > binary packages and (less often) against source packages. > It gets confused if a source & bin

Bug#943559: ITP: python3-sphinx-click -- A Sphinx plugin to automatically document click-based applications

2019-10-26 Thread Drew Parsons
Package: wnpp Severity: wishlist Owner: Drew Parsons * Package name: python3-sphinx-click Version : 2.1.0 Upstream Author : Stephen Finucane http://that.guru/ * URL : https://github.com/click-contrib/sphinx-click * License : MIT Programming Lang: Python Des

Bug#943556: ITP: roc-roct-thunk-interface -- Radeon Open Compute Thunk Interface

2019-10-26 Thread Mo Zhou
Package: wnpp Severity: wishlist Owner: Mo Zhou X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: roc-roct-thunk-interface Version : 2.9.0 Upstream Author : AMD * URL : https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface * License : MIT/X11 and

Bug#943552: ITP: tracecompass -- trace viewer and analyzer

2019-10-26 Thread Sudip Mukherjee
Package: wnpp Severity: wishlist Owner: Sudip Mukherjee X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: tracecompass Version : 5.1.0 * URL : https://www.eclipse.org/tracecompass/ * License : Eclipse Public License Programming Lang: Java Descriptio

rocm-team: in support of AMD's free CUDA counterpart and end NVIDIA monopoly

2019-10-26 Thread Mo Zhou
Hi fellow developers, As mentioned in a couple of previous mails, e.g. "... tensorflow ...", and "... anaconda ...". The license of software stack on nvidia's hardware accelerator is always a problem. In the past, I helped Debian's nvidia-team update the nvidia-cuda-toolkit several times, and pack

Re: should all bug reports be filed against /source/ packages?

2019-10-26 Thread Sune Vuorela
On 2019-10-23, Ansgar wrote: > So I'm wondering if we should start just filing all bug reports against > source packages? Reportbug could probably be easily changed to use > `Source: ...` instead of `Package: ...`; more places could follow later. Have you ever maintained source packages where a