Let's start salvaging packages -- Summary of the BoF Session.

2018-08-04 Thread Tobias Frost
Hello everyone, tl;dr: at the BoF the proposal seems to be uncontroversial at the session. So we will go forward with discussing it and propose a patch to e.g dev-ref (if we're still aiming for dev-ref then) Generally, the people at the BoF seemed to be supportive of the proposal, but a few thin

Bug#905462: ITP: boohu -- Break Out Of Hareka's Underground -- a roguelike game

2018-08-04 Thread Adam Borowski
Package: wnpp Severity: wishlist Owner: Adam Borowski * Package name: boohu Version : 0.9.0 Upstream Author : Yon * URL : https://download.tuxfamily.org/boohu/index.html * License : ISC Programming Lang: Go Description : Break Out Of Hareka's Undergrou

Bug#905460: ITP: opencamlib -- C++ library for creating 3D toolpaths for CNC machines

2018-08-04 Thread Kurt Kremitzki
Package: wnpp Severity: wishlist Owner: Kurt Kremitzki * Package name: opencamlib Version : 2018.08 Upstream Author : Anders Wallin * URL : https://github.com/aewallin/opencamlib * License : LGPL-2.1 Programming Lang: C++ Description : C++ library for

Re: Let's start salvaging packages!

2018-08-04 Thread David Bremner
gregor herrmann writes: > On Sun, 29 Jul 2018 17:40:49 +0800, Tobias Frost wrote: > >> A package is eligible for salvaging if it is in clear need of some love >> and care, i.e. there are open bugs, missing upstream releases, or there >> is work needed from a quality-assurance perspective; AND the

Re: Let's start salvaging packages!

2018-08-04 Thread David Bremner
Guillem Jover writes: > >> [c] Level of activity should be defined in favor of the maintainer if in >> doubt. A maintainer may ask for help or welcome a NMU. This counts as >> activity with respect to salvage criteria. If a package lacks uploads, >> there is no visible bug triaging, and - if app

Re: Bug#905427: go-sendxmpp -- Go package for sending single messages to an XMPP contact or groupchat

2018-08-04 Thread W. Martin Borgert
On 2018-08-04 14:49, Martin Dosch wrote: > How should I continue? Zip the folder and send to a member of the go-team? The best thing is probably to make yourself a guest account at https://salsa.debian.org/ and host your packaging repository there. Both the Go team (https://salsa.debian.org/go-tea

Re: Bug#905427: go-sendxmpp -- Go package for sending single messages to an XMPP contact or groupchat

2018-08-04 Thread Hilmar Preuße
Am 04.08.2018 um 14:49 teilte Martin Dosch mit: Hi Martin, I followed this tutorial: https://people.debian.org/~stapelberg/2015/07/27/dh-make-golang.html But, obviously as I am no Debian member, I can not process the last step: `ssh git.debian.org "/git/pkg-go/setup-repository go-sendxmpp 'Pa

Re: Bug#905427: go-sendxmpp -- Go package for sending single messages to an XMPP contact or groupchat

2018-08-04 Thread Martin Dosch
Dear all, I followed this tutorial: https://people.debian.org/~stapelberg/2015/07/27/dh-make-golang.html But, obviously as I am no Debian member, I can not process the last step: `ssh git.debian.org "/git/pkg-go/setup-repository go-sendxmpp 'Packaging for go-sendxmpp'"` How should I continue

Re: Let's enable AppArmor by default (why not?)

2018-08-04 Thread intrigeri
Hi, a year ago, on August 4 2017, intrigeri wrote: > tl;dr: I hereby propose we enable AppArmor by default in testing/sid, > and decide one year later if we want to keep it this way in the > Buster release. Here are some data points relevant to this decision making process. I think we're in a goo

go-sendxmpp -- Go package for sending single messages to an XMPP contact or groupchat

2018-08-04 Thread Martin Dosch
Package: wnpp Severity: wishlist Owner: Martin Dosch * Package name: go-sendxmpp Version : 0.0~git20180804.acb3759-1 Upstream Author : Martin Dosch * URL : https://salsa.debian.org/mdosch-guest/go-sendxmpp * License : MIT Programming Lang: Go Description

Re: intended MBF: wrong redirections in maintainer scripts

2018-08-04 Thread Carsten Leonhardt
Hi, > as announced in our talk at debconf'18 [1] we intend a MBF about wrong > redirections in maintainer scripts. In general these are of the form > > foo 2>&1 1> /dev/null > > Here it was probably intended to send both stderr and stdout to /dev/null. > In reality the effect of this is to send