Bug#892524: ITP: r-bioc-pcamethods -- BioConductor collection of PCA methods

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-bioc-pcamethods Version : 1.70.0 Upstream Author : Henning Redestig * URL : https://bioconductor.org/packages/pcaMethods/ * License : GPL Programming Lang: GNU R Description : BioC

Bug#892522: ITP: r-bioc-bitseq -- transcript expression inference and analysis for RNA-seq data

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-bioc-bitseq Version : 1.22.0 Upstream Author : Peter Glaus, Antti Honkela and Magnus Rattray * URL : https://bioconductor.org/packages/BitSeq/ * License : Artistic-2.0 Programming Lang: G

Bug#892513: ITP: r-cran-wavethresh -- GNU R wavelets statistics and transforms

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-wavethresh Version : 4.6.8 Upstream Author : Guy Nason * URL : https://cran.r-project.org/package=wavethresh * License : GPL Programming Lang: GNU R Description : GNU R wavele

Bug#892506: ITP: r-cran-waveslim -- GNU R wavelet routines for 1-, 2- and 3-D signal processing

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-waveslim Version : 1.7.5 Upstream Author : Brandon Whitcher * URL : https://cran.r-project.org/package=waveslim * License : BSD Programming Lang: GNU R Description : GNU R wav

Re: BuildProfileSpec: noguile profile?

2018-03-09 Thread Adam Borowski
On Fri, Mar 09, 2018 at 05:08:36PM +0100, Karsten Merker wrote: > I'm thinking about submitting patches to add support for a > "noguile" profile to some packages to make bootstrapping a bit > easier. That can of course be done with a profile in the > so-called "extension namespace", i.e. with a pr

Re: FHS: Where to store user specific plugins / code

2018-03-09 Thread Georg Faerber
Hi Jonas, On 18-03-09 19:18:50, Jonas Meurer wrote: > Am 09.03.2018 um 14:23 schrieb Georg Faerber: > >> Ian's comments are good for admin-installed plugins that the users can > >> use. In fact there is good precedent for an app checking > >> /usr/lib/pkg/... for plugins installed from Debian pac

Bug#892501: ITP: r-cran-snowfall -- GNU R easier cluster computing (based on snow)

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-snowfall Version : 1.84-6.1 Upstream Author : Jochen Knaus * URL : https://cran.r-project.org/package=snowfall * License : GPL Programming Lang: GNU R Description : GNU R easi

Re: FHS: Where to store user specific plugins / code

2018-03-09 Thread Enrico Weigelt, metux IT consult
On 09.03.2018 14:23, Georg Faerber wrote: Hi, > I guess we'll go with /usr/local/lib/schleuder then? Does this sound> like a reasonable choice? That would be my choice. OTOH, it might be nice to have a helper that automatically creates deb packages. (would also be nice for other applications,

Bug#892498: ITP: r-cran-samr -- GNU R significance analysis of microarrays

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-samr Version : 2.0 Upstream Author : R. Tibshirani, G. Chu, Balasubramanian Narasimhan, Jun Li * URL : https://cran.r-project.org/package=samr * License : LGPL Programming Lang: GNU

Re: FHS: Where to store user specific plugins / code

2018-03-09 Thread Jonas Meurer
Am 09.03.2018 um 14:23 schrieb Georg Faerber: >> Ian's comments are good for admin-installed plugins that the users can >> use. In fact there is good precedent for an app checking >> /usr/lib/pkg/... for plugins installed from Debian packages, >> /usr/local/lib/pkg/... for plugins installed by the

Re: BuildProfileSpec: noguile profile?

2018-03-09 Thread Helmut Grohne
On Fri, Mar 09, 2018 at 05:08:36PM +0100, Karsten Merker wrote: > the Build Profile Spec (https://wiki.debian.org/BuildProfileSpec) > currently defines the following set of standard "no${lang}" build > profiles to allow disabling specific language bindings / language > support in packages when boot

Bug#892495: ITP: python3-aiohttp-swagger -- Swagger API Documentation builder for aiohttp server

2018-03-09 Thread Joel Cross
Package: wnpp Severity: wishlist Owner: Joel Cross * Package name: python3-aiohttp-swagger Version : 1.0.5 Upstream Author : Daniel Garcia * URL : https://github.com/cr0hn/aiohttp-swagger * License : BSD Programming Lang: Python Description : Swagger A

Bug#892486: ITP: golang-github-coreos-bbolt -- An embedded key/value database for Go, especially CoreOS's etcd.

2018-03-09 Thread Anthony Fok
Package: wnpp Severity: wishlist Owner: Anthony Fok * Package name: golang-github-coreos-bbolt Version : 1.3.1-coreos.5-1 Upstream Authors: Ben Johnson, CoreOS Inc * URL : https://github.com/coreos/bbolt * License : Expat Programming Lang: Go Description

Re: FHS: Where to store user specific plugins / code

2018-03-09 Thread Georg Faerber
Hi, On 18-02-28 18:14:17, Marvin Renich wrote: > If a user get to install his/her own plugins, they should go in the > user's home directory, e.g. /home/user/.config/scheduler/plugins/. > Non-root users should not generally be given write permission to > /usr/local, and definitely not to /usr/lib.

Re: FHS: Where to store user specific plugins / code

2018-03-09 Thread Georg Faerber
Hi, On 18-03-01 07:55:08, Peter Silva wrote: > -- it is best practice for daemons/services not to run as root. They > should have an application specific user. Schleuder does use a dedicated user, called schleuder. $HOME is set to /var/lib/schleuder. Inside there mailing list specific data is st

Re: FHS: Where to store user specific plugins / code

2018-03-09 Thread Georg Faerber
Hi all, Thanks for your replies, and sorry for the delay in answering. (Note to myself: Don't write such mails while traveling..) That said, I think I wasn't clear regarding "user specific": On 18-02-28 18:54:14, Georg Faerber wrote: > Currently, we allow users to run / execute their own plugins

Bug#892478: ITP: r-cran-rwave -- GNU R time-frequency analysis of 1-D signals

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-rwave Version : 2.4-8 Upstream Author : Jonathan M. Lees * URL : https://cran.r-project.org/package=Rwave * License : GPL Programming Lang: GNU R Description : GNU R time-freq

Bug#892476: ITP: r-cran-aplpack -- Another Plot PACKage: stem.leaf, bagplot, faces, spin3R and others

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-aplpack Version : 1.3.0 Upstream Author : Hans Peter Wolf * URL : https://cran.r-project.org/package=aplpack * License : GPL Programming Lang: GNU R Description : Another Plot

Re: Bug#891939: ITP: python-gitlab -- GitLab API client library for Python

2018-03-09 Thread Andreas Tille
Hi Federico, On Fri, Mar 02, 2018 at 08:20:15PM +, Federico Ceratto wrote: > Package: wnpp > Severity: wishlist > Owner: Federico Ceratto > > * Package name: python-gitlab > Version : 1.3.0 > Upstream Author : Gauvain Pocentek > * URL : https://github.com/python-

Bug#892469: ITP: r-cran-tinytex -- GNU R helper to compile LaTeX documents

2018-03-09 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-tinytex Version : 0.4 Upstream Author : Yihui Xie * URL : https://cran.r-project.org/package=tinytex * License : MIT Programming Lang: GNU R Description : GNU R helper to comp

Re: What can Debian do to provide complex applications to its users?

2018-03-09 Thread Holger Levsen
On Fri, Mar 09, 2018 at 02:07:19AM +0100, gregor herrmann wrote: > We might need an archive area which is independent of our release > suites. .oO( PPAs ) -- cheers, Holger signature.asc Description: PGP signature

Re: Bug#892386: ITP: python3-pgzero -- pygame zero, environment for zero-boilerplate programming of 2D games.

2018-03-09 Thread Ghislain Vaillant
Le jeudi 08 mars 2018 à 17:26 +, plugwash a écrit : > Package: wnpp > Severity: wishlist > Owner: plugwash > > * Package name: python3-pgzero Please consider using the name "pgzero" or "python-pgzero" for the source package. The binary packages may get a different prefix based on the ta