Re: RFC: threading-aware virtual BLAS/LAPACK

Mo Zhou writes: > Please comment: > 1. Do we have a better solution where we can retain high performance and > avoid threading trouble at the same time? > 2. If we don't have a better solution, is my proposal acceptable? > 3. In which way can my proposal be improved? Hi Mo, Your proposal

Re: Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))

On Wed, May 13, 2020 at 08:33:07PM +0200, Thorsten Glaser wrote: > > I remember times when such a web page (actually some autogenerated text > > file) existed which was **extremely** helpful. I wished this would be > > back! > > > > > … I just volunteerd, didn’t I? > > Here you are: > > https://

Bug#960544: ITP: vim-vader -- simple vimscript test framework

Package: wnpp Severity: wishlist Owner: Nicholas Guriev * Package name: vim-vader Upstream Author : Junegunn Choi * URL : https://github.com/junegunn/vader.vim * License : Expat (MIT-like) Programming Lang: VimScript Description : simple vimscript test framework

Bug#960543: ITP: vim-ale -- Asynchronous Lint Engine for Vim 8 and NeoVim

Package: wnpp Severity: wishlist Owner: Nicholas Guriev Control: forwarded -1 https://github.com/dense-analysis/ale/issues/3160 * Package name: vim-ale Version : 2.6.0 Upstream Author : w0rp * URL : https://github.com/dense-analysis/ale * License : BSD-2-Claus

Maven packages in Debian (was Re: Progress in preparing the Bazel Build System for Debian (COVID-19 Biohackathon follow-up))

On Wed, 6 May 2020, Andreas Tille wrote: > > Or perhaps we need a webpage or wiki page generated by parsing the > > Contents file and listing the matching Debian package for each class > > or, at least, Java package (unless split across multiple packages)… > > I remember times when such a web page

Re: reopening bugs closed by removal after package reintroduction?

On Wed, May 13, 2020 at 09:27:33AM -0400, jrb3-beckenbach.us wrote: > Offering a naive implementation idea: > On package reintroduction, something (bot?) files a low-priority bug > against the reintroduced package, titled eg “triage bugs from previous > packaging”, > containing explanatory text

RFC: threading-aware virtual BLAS/LAPACK

Hi fellow devs, I'm asking advice on a system design issue specific to Debian, which is whether we should introduce threading-aware BLAS/LAPACK virtual package. This question is important because it affects a reverse dependency tree with > 1 million popcon. (One week ago I asked for comment in -s

Bug#960526: ITP: azure-kusto-python -- Microsoft Azure Kusto (Azure Data Explorer) SDK for Python

Package: wnpp Severity: wishlist Owner: "Luca Boccassi" X-Debbugs-CC: debian-devel@lists.debian.org * Package name: azure-kusto-python Version : 0.0.45 Upstream Author : Microsoft * URL : https://github.com/Azure/azure-kusto-python * License : MIT * Programming

Re: reopening bugs closed by removal after package reintroduction?

[Two cents inbound from a lurker] Greetings, Enrico Zini! On 13 May 2020, at 05:07, you wrote: > > I would however guess that, for a majority of cases, we are probably > talking about a bunch of bugs to triage, and I would rather introduce a > practice of risking having to triage some bugs more,

Re: reopening bugs closed by removal after package reintroduction?

On Wed, May 13, 2020 at 05:13:45AM -, Sune Vuorela wrote: > But I guess it also depends on if it is one bug that needs work, or a > "Thanks for your contribution to Debian by maintainig this package. Now > also walk thru these 1000 old crap that probably is irellevant > today"-experience I se

Bug#960486: ITP: gnome-chatty -- XMPP and SMS messaging

Package: wnpp Severity: wishlist Owner: Evangelos Ribeiro Tzaras * Package name: gnome-chatty Version : 0.0.8 Upstream Author : Mohammed Sadiq * URL : https://source.puri.sm/Librem5/chatty * License : GPL-3+ Programming Lang: C Description : XMPP and S