Re: Unicode License Additional Coverage

2019-01-03 Thread Paul Hardy
Yao Wei, On Thu, Jan 3, 2019 at 9:18 PM "Yao Wei (魏銘廷)" wrote: > > Never mind. I was wrongfully read as the license has the problem. > > (It is that, IVD files had no license attached to it, someone might think it > is "All rights reserved" by copyright law in most jurisdictions. Please > corr

Re: Unicode License Additional Coverage

2019-01-03 Thread Yao Wei (魏銘廷)
Never mind. I was wrongfully read as the license has the problem. (It is that, IVD files had no license attached to it, someone might think it is "All rights reserved" by copyright law in most jurisdictions. Please correct me if I am wrong again.) Yao Wei (This email is sent from a phone; sor

Re: Unicode License Additional Coverage

2019-01-03 Thread Yao Wei (魏銘廷)
Hi, Could you elaborate what part of license that someone might have concern? It looks like X11 license for me at the first glance. Yao Wei (This email is sent from a phone; sorry for HTML email if it happens.) > On Jan 4, 2019, at 04:49, Paul Hardy wrote: > > Dear Debian, > > Unicode, Inc

Unicode License Additional Coverage

2019-01-03 Thread Paul Hardy
Dear Debian, Unicode, Inc. has informed me that they just added the directory http://www.unicode.org/ivd/data/ to the list of directories explicitly mentioned as covered by their license; see http://www.unicode.org/copyright.html#License. Among other files, that directory contains IVD_Sequences.t

Work-needing packages report for Jan 4, 2019

2019-01-03 Thread wnpp
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1322 (new: 7) Total number of packages offered up for adoption: 157 (new: 0) Total number of packages reques

Help request: Contribute to MariaDB 10.3 in Debian efforts

2019-01-03 Thread Otto Kekäläinen
Hello! I've spent the last months preparing MariaDB 10.3 for Debian. I am almost done, but there are a bunch of smaller issues I need help with. I would be glad for anybody who can look into the issues and give solution ideas - or even file a merge request on Debian's Gitlab instance where the Deb

Bug#918152: ITP: kismon -- GUI client for kismet

2019-01-03 Thread Patrick Salecker
Package: wnpp Severity: wishlist Owner: Patrick Salecker * Package name: kismon Version : 0.9.0 Upstream Author : Patrick Salecker * URL : https://www.salecker.org/software/kismon.html * License : BSD Programming Lang: Python Description : GUI client f

Re: Nix and non-standard-toplevel-dir

2019-01-03 Thread Luke Faraone
On Wed, 2 Jan 2019 at 20:28, Russ Allbery wrote: > If anything, they probably already know > how Nix works and are expecting it to use those paths. There doesn't seem > to be much drawback in this carefully-chosen lack of compliance with the > FHS. > > I don't think it's worth writing an explicit

Bug#918120: ITP: bpftrace -- high-level tracing language for Linux eBPF

2019-01-03 Thread Vincent Bernat
Package: wnpp Severity: wishlist Owner: Vincent Bernat -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: bpftrace Version : git Upstream Author : IO Visor Project * URL : https://github.com/iovisor/bpftrace * License : Apache 2 Programming Lang

Bug#918111: ITP: luakit -- A webkit2-based web browser extensible by Lua

2019-01-03 Thread Markus Demleitner
Package: wnpp Severity: wishlist Owner: Markus Demleitner * Package name: luakit Version : 2017-08-10 Upstream Author : Aidan Holm https://luakit.github.io * License : GPLv3 Programming Lang: C, Lua Description : A webkit2-based web browser extensible by Lua Luaki

Re: Nix and non-standard-toplevel-dir

2019-01-03 Thread Ian Jackson
Russ Allbery writes ("Re: Nix and non-standard-toplevel-dir"): > I think this is a case where we should waive FHS for this package, due to > the unique nature of this package. I agree for the reasons Russ gives. > I don't think it's worth writing an explicit Policy exception for this, > since it'

Bug#793404: marked as done (massive waste of CPU time in debian/rules by inline commands)

2019-01-03 Thread Debian Bug Tracking System
Your message dated Thu, 03 Jan 2019 11:19:00 + with message-id and subject line Re: Bug#793404: massive waste of CPU time in debian/rules by inline commands has caused the Debian Bug report #793404, regarding massive waste of CPU time in debian/rules by inline commands to be marked as done.

Bug#793404: massive waste of CPU time in debian/rules by inline commands

2019-01-03 Thread Niels Thykier
Hi, In the past 3½ years, several things have been improved and I am therefore taking the liberty of closing this bug against general (remaining issues as I understand it will be in individual packages). In particular, I think we have identified all major issues, solved most of them and triaged/a