Re: Concerns about infrastructure for Alioth replacement

2017-10-19 Thread Paul Wise
On Wed, Oct 18, 2017 at 2:13 PM, Alexander Wirt wrote: > Please don't get me wrong, but even if gitlab packages are recent tomorrow > (which I > don't think) we won't migrate. The work is done and we have all the things in > place to maintain them. So please do me a favour and don't mention aliot

getconf(1) interface considered cross-harmful

2017-10-19 Thread Guillem Jover
Hi! I recently noticed that the getconf(1) interface is broken by design when it comes to cross-compiling. It always returns the information for the build system (GNU/dpkg terms), via the build system libc. This means that any package using getconf(1) to get build-specific information such as LFS

Re: getconf(1) interface considered cross-harmful

2017-10-19 Thread Simon McVittie
On Thu, 19 Oct 2017 at 10:50:36 +0200, Guillem Jover wrote: > When it comes to LFS, starting with dpkg 1.19.0 you can now use the > new «lfs» feature from the «future» feature area ... or if your upstream uses Autotools, ask them to add AC_SYS_LARGEFILE to configure.ac, which as far as I can tell

Re: Concerns about infrastructure for Alioth replacement

2017-10-19 Thread Pirate Praveen
On ബുധന്‍ 18 ഒക്ടോബര്‍ 2017 02:59 രാവിലെ, Francesco Poli wrote: > Unfortunately, I have basically zero knowledge about Rails, JavaScript > and Node.js: I could not be of much help in packaging GitLab. If you are interested, I could mentor you in learning Node.js packaging. Many Node.js modules are

Re: Concerns about infrastructure for Alioth replacement

2017-10-19 Thread Pirate Praveen
On ബുധന്‍ 18 ഒക്ടോബര്‍ 2017 04:08 രാവിലെ, Nicholas D Steeves wrote: > Dear Javascript Team, > > Would you please consider maintaining the "numerous [...] nodejs > modules" necessary for Debian's Alioth replacement to run on a > Debian-built GitLab package? We are facing a scenario that confirms >

Re: [Pkg-javascript-devel] Concerns about infrastructure for Alioth replacement

2017-10-19 Thread Pirate Praveen
On ബുധന്‍ 18 ഒക്ടോബര്‍ 2017 01:39 വൈകു, Ondřej Surý wrote: > Also please note that Ruby programs are usually very picky about > particular versions of their dependencies. > > I call it a "gem hell" and it was a reason why I gave up helping with > Ruby packaging and switched to redmine from source

Bug#879101: ITP: node-uniqid -- Unique ID Generator

2017-10-19 Thread Pirate Praveen
Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-uniqid Version : 4.1.1 Upstream Author : Halász Ádám (http://adamhalasz.com/) * URL : http://github.com/adamhalasz/diet-uniqid/ * License :

Bug#879103: ITP: doctest -- Light and feature-rich C++ testing framework

2017-10-19 Thread Didier 'OdyX' Raboud
Package: wnpp Severity: wishlist Owner: Didier 'OdyX' Raboud Package name: doctest Version : 1.2.5 Upstream Author : Viktor Kirilov URL : https://github.com/onqtam/doctest License : MIT Programming Lang: C++ Description : Light and feature-rich C++ testing fr

Re: Unsustainable debian/rules as official build entry point?

2017-10-19 Thread Simon Richter
Hi, On 18.10.2017 11:36, Guillem Jover wrote: > Using dpkg-buildpackage as the official build entry point would allow > for much debian/rules refactoring and reduction, and optimizations. The important bit isn't whether dpkg-buildpackage is the official entry point, because that isn't what Polic

Re: Easy discovery of ‘debian/rules’ build problems (was: Unsustainable debian/rules as official build entry point?)

2017-10-19 Thread Ian Jackson
Ben Finney writes ("Easy discovery of ‘debian/rules’ build problems (was: Unsustainable debian/rules as official build entry point?)"): > From the rest of your message I infer that the mention of “one consumer” > there refers to (current or future) ‘dpkg-buildpackage’, is that correct? Yes. > Ia

Bug#879125: ITP: python-requests-file -- File transport adapter for Requests

2017-10-19 Thread Antoine Beaupre
Package: wnpp Severity: wishlist Owner: Antoine Beaupre * Package name: python-requests-file Version : 2017-04-28 Upstream Author : David Shea * URL : https://pypi.python.org/pypi/requests-file * License : Apache 2.0 Programming Lang: Python Description

Bug#879154: ITP: r-bioc-protgenerics -- S4 generic functions for Bioconductor proteomics infrastructure

2017-10-19 Thread Andreas Tille
Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-bioc-protgenerics Version : 1.8.0 Upstream Author : Laurent Gatto * URL : https://bioconductor.org/packages/ProtGenerics/ * License : Artistic-2.0 Programming Lang: GNU R Description

Work-needing packages report for Oct 20, 2017

2017-10-19 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: 1131 (new: 4) Total number of packages offered up for adoption: 156 (new: 0) Total number of packages reques