Bug#847319: ITP: python-keepalive -- urllib keepalive support for python

Package: wnpp Severity: wishlist Owner: Ghislain Antony Vaillant * Package name: python-keepalive Version : 0.5 Upstream Author : Sergio Fernández * URL : https://github.com/wikier/keepalive * License : LGPL Programming Lang: Python Description : urlli

armel after Stretch (was: Summary of the ARM ports BoF at DC16)

[ intentionally keep d-d CCed ] On Fri, 22 Jul 2016 02:36:05 +0100 Steve McIntyre wrote: > [ Please note the cross-post and Reply-To ] > > Hi folks, > > As promised, here's a quick summary of what was discussed at the ARM > ports BoF session in Cape Town. Thanks for the summary! I'm ARM port

Bug#847361: ITP: node-resolve-from -- Resolve the path of a module like require.resolve() but from a given path

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-resolve-from Version : 2.0.0 Upstream Author : Sindre Sorhus (sindresorhus.com) * URL : https://github.com/sindresorhus/resolve-from * License

Bug#847363: ITP: node-pkg-up -- Find the closest package.json file

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-pkg-up Version : 1.0.0 Upstream Author : Sindre Sorhus (sindresorhus.com) * URL : https://github.com/sindresorhus/pkg-up#readme * License :

Bug#847362: ITP: node-resolve-pkg -- Resolve the path of a package regardless of it having an entry point

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-resolve-pkg Version : 0.2.0 Upstream Author : Sindre Sorhus (sindresorhus.com) * URL : https://github.com/sindresorhus/resolve-pkg#readme * License

Bug#847364: ITP: node-load-grunt-tasks -- Load multiple grunt tasks using globbing patterns

Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-load-grunt-tasks Version : 3.5.2 Upstream Author : Sindre Sorhus (sindresorhus.com) * URL : https://github.com/sindresorhus/load-grunt-tasks#readme

Bug#847367: ITP: node-grunt-contrib-requirejs -- Optimize RequireJS projects using r.js

Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-grunt-contrib-requirejs Version : 1.0.0 Upstream Author : Grunt Team (http://gruntjs.com/) * URL : https://github.com/gruntjs/grunt-contrib-requirejs

Re: armel after Stretch (was: Summary of the ARM ports BoF at DC16)

On Wed, Dec 07, 2016 at 08:50:40PM +0900, Roger Shimizu wrote: >[ intentionally keep d-d CCed ] > >On Fri, 22 Jul 2016 02:36:05 +0100 >Steve McIntyre wrote: > >> [ Please note the cross-post and Reply-To ] >> >> Hi folks, >> >> As promised, here's a quick summary of what was discussed at the ARM

Re: https://manpages.debian.org/man/1/uscan

On 06/12/16 09:21, Javier Fernandez-Sanguino wrote: > Dear Geert, > > On 3 December 2016 at 14:33, Geert Stappers > wrote: > > Hi, > > The URL https://manpages.debian.org/man/1/uscan > gives me a 403 error. > >

Re: armel after Stretch

On 07/12/16 16:53, Steve McIntyre wrote: > * It will need somebody happy to dive into the lower levels of the >various toolchains to verify support for atomics and make things >work where it's not already, by adding support for the kernel >helpers. There has been some recent work on t

Re: https://manpages.debian.org/man/1/uscan

On 7 December 2016 at 16:58, Emilio Pozuelo Monfort wrote: > You may want to add some contact information to > https://manpages.debian.org/ > > Already available here: https://manpages.debian.org/cgi-bin/man.cgi?query=info.html (Which is linked from the main page) and here: https://wiki.debian.o

Re: armel after Stretch

On Wed, Dec 07, 2016 at 05:05:58PM +0100, Emilio Pozuelo Monfort wrote: >On 07/12/16 16:53, Steve McIntyre wrote: >> * It will need somebody happy to dive into the lower levels of the >>various toolchains to verify support for atomics and make things >>work where it's not already, by addin

Bug#847384: ITP: docopt.cpp -- C++11 port of docopt

Package: wnpp Severity: wishlist Owner: Ghislain Antony Vaillant * Package name: docopt.cpp Version : 0.6.2 Upstream Author : Jared Grubb * URL : https://github.com/docopt/docopt.cpp * License : MIT / BSL Programming Lang: C++ Description : C++11 port o

Bug#847385: ITP: tendermint-go-process -- Tendermint process library

Package: wnpp Severity: wishlist Owner: Alessio Treglia * Package name: tendermint-go-process Version : git snapshot Upstream Author : the Tendermint Project * URL : http://www.tendermint.com/ * License : Apache-.20 Programming Lang: Go Description : Te

Re: https://manpages.debian.org/man/1/uscan

Hello, Le 6 déc. 2016 9:21 AM, "Javier Fernandez-Sanguino" a écrit : The URL now should work fine. If you have any future issues, please report them. The home page has a note explaining the service does not really work. I tested it (with 'man' and 'uscan') and it works correctly. Perhaps I

Re: Congratulations ldta1209 , Your Roof is Covered. Thank You!Mmcl

Sorry I don't have a roof. Unsubscribe me now On Dec 7, 2016 12:43 PM, "Steve McIntyre" wrote: > kufg > > Congratulations ldta1209, > The Home Warranty Limited time event. > Never pay for covered home repairs again! > Your Roof is Covered - FREE! > Click Here > > Unsub > Opt Out > > > > > > > >

Re: https://manpages.debian.org/man/1/uscan

On Wed, 2016-12-07 at 19:59 +0100, Stéphane Blondon wrote: > The home page has a note explaining the service does not really work. > I tested it (with 'man' and 'uscan') and it works correctly. Perhaps I > missed something but the note should be removed, no ? Where? Assuming that by "home page"

Re: Test instance of our infrastructure

Hi, On 28/11/16 at 12:04 +, Ian Jackson wrote: > We are running a multitude of services. > > Our usual approach to these services is that we fix things when they > break, test our client code against the live instance (with perhaps a > special area of the database - eg the `experimental' suit

Re: Test instance of our infrastructure

Lucas Nussbaum: > Hi, > > On 28/11/16 at 12:04 +, Ian Jackson wrote: >> [...] > > No. > > I think that we should rather push for using tools such as Vagrant or > Docker to provide a way to easily create development environments for > services. > > [...] > > Lucas > So I happily agree tha

Re: Test instance of our infrastructure

Lucas Nussbaum writes: > On 28/11/16 at 12:04 +, Ian Jackson wrote: >> We are running a multitude of services. >> Our usual approach to these services is that we fix things when they >> break, test our client code against the live instance (with perhaps a >> special area of the database - eg

Re: Release impact of introducing a new archive section?

Josh Triplett: > [Please CC me on replies.] > > [...] > > Does it seem reasonable to attempt to introduce these new sections > before the release, so that these pieces of software in stable can > successfully work with upcoming sections that will appear in > testing/unstable/backports? > > I'd b

Re: https://manpages.debian.org/man/1/uscan

Le 07/12/2016 à 20:10, Adam D. Barratt a écrit : > Assuming that by "home page" you mean > https://manpages.debian.org/cgi-bin/man.cgi (which is where > https://manpages.debian.org/ redirects and where the "home" link on > subpages links to), I see no text such as you describe. Sorry, I fail to se

Re: Release impact of introducing a new archive section?

On Wed, Dec 07, 2016 at 09:36:00PM +, Niels Thykier wrote: > Josh Triplett: > > [Please CC me on replies.] > > > > [...] > > > > Does it seem reasonable to attempt to introduce these new sections > > before the release, so that these pieces of software in stable can > > successfully work with

Re: Release impact of introducing a new archive section?

On 14515 March 1977, Josh Triplett wrote: >> Longer version: I think we should patch the tools first and /if/ we are >> in time before the release, we can add the sections. To my knowledge, >> there are basically no ill effects of tools knowing sections that does >> not yet exist. > That's a good

Re: Test instance of our infrastructure

On 07/12/16 at 20:27 +, Niels Thykier wrote: > Lucas Nussbaum: > > Hi, > > > > On 28/11/16 at 12:04 +, Ian Jackson wrote: > >> [...] > > > > No. > > > > I think that we should rather push for using tools such as Vagrant or > > Docker to provide a way to easily create development environm