Bug#887484: ITP: r-cran-rlist -- GNU R toolbox for non-tabular data manipulation
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-rlist Version : 0.4.6.1 Upstream Author : Kun Ren * URL : https://cran.r-project.org/package=rlist * License : MIT Programming Lang: GNU R Description : GNU R toolbox for non-tabular data manipulation Provides a set of functions for data manipulation with list objects, including mapping, filtering, grouping, sorting, updating, searching, and other useful functions. Most functions are designed to be pipeline friendly so that data processing with lists can be chained. Remark: This package will be maintained by the r-pkg-team at https://salsa.debian.org/r-pkg-team/r-cran-rlist.git
Re: Release Critical Kernel bug - Lenovo E550 laptop locks up repeatedly running systemctl daemon-reload
On Wed, 2018-01-17 at 20:31 +1300, Matt Grant wrote: > My guess as a developer this is a release critical show stopper > bug. Please see https://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2 and https://wiki.debian.org/DebianKernelReportingBugs for guidance on reporting a bug against the kernel. Ian.
Bug#865283: ITP: fontmake -- Compile fonts from sources (UFO, Glyphs) to binary (OpenType, TrueType)
Package: wnpp Followup-For: Bug #865283 Control: retitle -1 ITP: fontmake -- Compile fonts from sources (UFO, Glyphs) to binary (OpenType, TrueType) Owner: Yao Wei (魏銘廷) The dependencies are uploaded and it can finally be packaged! Yao Wei signature.asc Description: PGP signature
Re: udftools, pktsetup and init scripts
Ok, that you for opinion. I drop init script and include upstream udev rule which replace it. And because there is no feature request for splitting package into more, I let it as is to not complicate it. -- Pali Rohár pali.ro...@gmail.com
Bug#887527: ITP: pico2wave -- command line text-to-speech converter
Package: wnpp Severity: wishlist Owner: Paolo Greppi * Package name: pico2wave Version : 1.0.0 Upstream Author : Paolo Greppi * URL : https://salsa.debian.org/paolog-guest/pico2wave * License : Apache-2.0 Programming Lang: C Description : command line text-to-speech converter pico2wave is a command-line utility to convert text to speech using the SVOX Pico engine. It accepts the text either on the command line or from stdin, and writes to a WAV file. The pico2wave utility is already available in debian. The binary ATM is somewhat confusingly provided by libttspico-utils. AS per https://bugs.debian.org/883156, svox version 1.0+git20130326-8 already includes my patch to support stdin, albeit up to 32767 characters. The idea is to separate the libttspico-utils binary package from the svox source package. In this way it will have its own version number, plus the code would not be in a patch but in plaintext. It will produce a new binary pico2wave and a transitional libttspico-utils as per: https://wiki.debian.org/RenamingPackages The plan is also to overcome the 32767 characters limitation by: 1. breaking up the text in chunks of < 32767 characters using some sort of elementary Sentence Boundary Detection algorithm 2. process the chunks in the synthesis loop sthibault has agreed to sponsor the upload. Paolo
Re: Why do we list individual copyright holders?
On Tue, Jan 16, 2018 at 10:53 AM, Ian Jackson < ijack...@chiark.greenend.org.uk> wrote: > > But I'm a hardy soul who is quite prepared to see a warning and decide > to ignore it :-). > > My view is that the purpose of a warning is to alert you to something, > so you can decide what to do about it. What is the difference between "warn" and "info", then? -m
Bug#886238: Build-Profiles purpose, mechanism vs policy (was Re: Bug#886238: Please introduce official nosystemd build profile)
On Tue, Jan 09, 2018 at 07:29:51PM -0500, Sam Hartman wrote: > > "Adrian" == Adrian Bunk writes: > > Adrian> On Tue, Jan 09, 2018 at 01:23:32PM +0100, Guillem Jover wrote: > >> ... Given the background of build-profiles, I'm very much in > >> favor of introducing the equivalent usage as Gentoo USE flags, > >> which was its main intention! :) It could make Debian a viable > >> source-based distribution to use or base on, could make many of > >> the embedded specific distribution solutions obsolete, ... > > Adrian> Who would then implement, maintain and support this in all > Adrian> packages? > > No one. People would implement and test the feature where it was > sufficiently useful to implement and test. I don't think all of the use > flags combinations are tested in source distributions that have them > today. > > Even so, users find those flags useful enough to spend a fair bit of > work on them. To "make many of the embedded specific distribution solutions obsolete", Debian would have to provide all this in stable releases at a quality comparable to Yocto. > A build profile seems like a great way to express the flag, and like > many things in Debian, the work would fall on those who would benefit > from it. > > So, I do support the use of build profiles for use flags. > I also believe there's sufficient utility for downstreams and users to > justify this. For many use flags the only benefit is an unused library less on the system when the flag is disabled, and this also applies to the proposed nosystemd profile discussed in this bug. Support for nosystemd in only 95% of all libsystemd-using packages would still result in libsystemd being installed - if just one maintainer would refuse to apply a nosystemd patch, the people working on nosystemd in Debian basically have to rely on CTTE overruling the maintainer. Your "build profiles for use flags" can easily require changes to hundreds of packages just for one flag, often including non-trivial changes to e.g. debian/rules or .install files. This only makes sense if there is consensus that this is a useful direction, and that this should be fully supported in future stable releases of Debian. > --Sam cu Adrian [1] Raspberry Pi Zero is already big enough to not require use flags -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#887561: ITP: ries -- find algebraic equations, given their solution
Package: wnpp Severity: wishlist Owner: Nicolas Braud-Santoni X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: ries Version : 2017.02.12 Upstream Author : Robert P. Munafo * URL : https://mrob.com/pub/ries/ * License : GPL-3+ Programming Lang: C Description : find algebraic equations, given their solution Given a number, ries searches for algebraic equations in one variable that have a solution (root) near that number. It avoids trivial or reducible solutions like ``x/x = 1''. If rhe input is an integer, ries can find an exact solution expressed in terms of single-digit integers. The output gives progressively ``more complex'' equations that come progressively closer to matching the input number. signature.asc Description: PGP signature
Bug#886238: Build-Profiles purpose, mechanism vs policy (was Re: Bug#886238: Please introduce official nosystemd build profile)
On Tue, Jan 09, 2018 at 07:29:51PM -0500, Sam Hartman wrote: > A build profile seems like a great way to express the flag, and like > many things in Debian, the work would fall on those who would benefit > from it. > So, I do support the use of build profiles for use flags. > I also believe there's sufficient utility for downstreams and users to > justify this. Okay. As you think they are worth to think about: Please take one such a flag; provide a description what it should do, both for the user and on the system level; describe both the advantages and the drawbacks. Oh, and please provide a list of packages you would start with applying this change. Bastian -- Suffocating together ... would create heroic camaraderie. -- Khan Noonian Singh, "Space Seed", stardate 3142.8
