Release file for own backport repository?

2017-03-09 Thread Joerg Desch
Hi. I currently maintain a repository with my own backports for Jessie. Therefore I have a Release file with a suite entry "stable". Since my backports should be overwriteable by the official backport repository, I want change the "name" of the origin von "stable" to "jessie-backports". How do I

Re: USA TODAY: Google weighs in on WikiLeaks bombshell

2017-03-09 Thread Jan Žolík
Dňa 9. 3. 2017 9:58 používateľ "Jan Žolík" napísal: >From USA TODAY: Google weighs in on WikiLeaks bombshell Google is the latest company to weigh in on WikiLeaks' stunning disclosure yesterday that it is among several high-profile tech companies whose products canbe turned into spying devices.

Re: Release file for own backport repository?

2017-03-09 Thread Joerg Desch
I've just tried it without "Version:" and with "Suite:" and "Codename:" set to jessie-backports. After this, "apt-get update" prints the error (jessie expected but jessie- backports received): W: Konflikt bei Distribution: http://debian.jdesch.de jessie/ Release (jessie erwartet, aber jessie-ba

Virus spam in the bug tracker

2017-03-09 Thread Francois Gouget
This has been mentionned before but today I discovered that a lot of Debian bugs have a bunch of spam emails on their tail end. What's worse, these actually contain a virus in an attachment. Do a web search for: site:bugs.debian.org FedEx site:bugs.debian.org USPS delivery site:bug

Fwd: Virus spam in the bug tracker

2017-03-09 Thread Holger Levsen
- Forwarded message from Francois Gouget - Date: Thu, 9 Mar 2017 14:23:52 +0100 (CET) From: Francois Gouget To: debian-devel@lists.debian.org Subject: Virus spam in the bug tracker User-Agent: Alpine 2.20 (DEB 67 2015-01-07) List-Id: This has been mentionned before but today I discove

Bug#857282: ITP: golang-github-golang-geo -- S2 geometry library in Go

2017-03-09 Thread Michael Stapelberg
Package: wnpp Severity: wishlist Owner: Michael Stapelberg * Package name: golang-github-golang-geo Version : 0.0~git20170112.0.f819552-1 Upstream Author : Google Inc. * URL : https://github.com/golang/geo * License : Apache-2.0 Programming Lang: Go Descrip

Re: Depends/Recommends from libraries

2017-03-09 Thread Adrian Bunk
On Wed, Mar 08, 2017 at 11:33:21PM +, Ian Jackson wrote: > Adam Borowski writes ("Depends/Recommends from libraries"): > > I'd like to discuss (and then propose to -policy) the following rule: > > > > # Libraries which don't provide a convenient means of conditionally loading > > # at runtime

Re: Depends/Recommends from libraries

2017-03-09 Thread Thibaut Paumard
Le 08/03/2017 à 23:33, Adam Borowski a écrit : > Hi, mortals and paultag! > > I'd like to discuss (and then propose to -policy) the following rule: > > # Libraries which don't provide a convenient means of conditionally loading > # at runtime (this includes most libraries for languages such as C)

Bug#857291: ITP: golang-golang-x-debug -- debugging tools

2017-03-09 Thread Michael Stapelberg
Package: wnpp Severity: wishlist Owner: Michael Stapelberg * Package name: golang-golang-x-debug Version : 0.0~git20160621.0.fb50892-1 Upstream Author : The Go Authors * URL : https://golang.org/x/debug * License : BSD-3-clause Programming Lang: Go Descript

Re: Depends/Recommends from libraries

2017-03-09 Thread Ian Jackson
Thibaut Paumard writes ("Re: Depends/Recommends from libraries"): > There are quite legitimate uses for dependencies or recommendations in > libraries. For instance, tne library that I maintain (libgyoto) has the > option to provide MPI paralellisation. This requires an external > executable, which

Re: Depends/Recommends from libraries

2017-03-09 Thread Ian Jackson
Russ Allbery writes ("Re: Depends/Recommends from libraries"): > I feel like the problem here is that people are failing to fix bugs in > their packages (unnecessary dependencies on libraries that have heavy > dependencies), No. The problem is that for an ordinary library, if package foo ever wan

Re: Depends/Recommends from libraries

2017-03-09 Thread Russ Allbery
Jonas Smedegaard writes: > Quoting Russ Allbery (2017-03-09 04:24:09) >> In general, I don't want to see us place too many restrictions on >> Recommends. If you don't want additional helpful programs, disable >> installing Recommends by default. I think it's very odd to worry >> about bloat

Re: Depends/Recommends from libraries

2017-03-09 Thread Russ Allbery
Ian Jackson writes: > I think the right way to solve this problem is to declare that: > * When a library package is installed, the Depends and Recommends >of the library should be appropriate on the assumption that: > - the library package is only installed because it is the dormant >

Re: Depends/Recommends from libraries

2017-03-09 Thread Holger Levsen
On Thu, Mar 09, 2017 at 10:14:13AM -0800, Russ Allbery wrote: > Well, I strongly disagree with you. I think this would take things in the > wrong direction; I like that software is fully useful when Recommends are > enabled at the cost of some bloat. > > If you don't want possibly unused software

Re: Depends/Recommends from libraries

2017-03-09 Thread Andrey Rahmatullin
On Thu, Mar 09, 2017 at 10:14:13AM -0800, Russ Allbery wrote: > If you don't want possibly unused software installed, we have a supported > mechanism for that: disable automatic installation of Recommends. Which explodes from time to time, like when ntpdate and ntpd only recommended lockfile-progs

Re: Depends/Recommends from libraries

2017-03-09 Thread Russ Allbery
Andrey Rahmatullin writes: > On Thu, Mar 09, 2017 at 10:14:13AM -0800, Russ Allbery wrote: >> If you don't want possibly unused software installed, we have a >> supported mechanism for that: disable automatic installation of >> Recommends. > Which explodes from time to time, like when ntpdate an

Re: Depends/Recommends from libraries

2017-03-09 Thread Andrey Rahmatullin
On Thu, Mar 09, 2017 at 12:22:17PM -0800, Russ Allbery wrote: > >> If you don't want possibly unused software installed, we have a > >> supported mechanism for that: disable automatic installation of > >> Recommends. > > > Which explodes from time to time, like when ntpdate and ntpd only > > recom

Re: Depends/Recommends from libraries

2017-03-09 Thread Michael Lustfield
On Mar 9, 2017 12:22 PM, "Russ Allbery" wrote: Sure, but hopefully we find and report those as bugs. I personally run without recommends on Debian unstable on several different types of systems and report these problems whenever I run into them. I'm in this same boat. I disable installing rec

Re: Depends/Recommends from libraries

2017-03-09 Thread Adam Borowski
On Thu, Mar 09, 2017 at 10:14:13AM -0800, Russ Allbery wrote: > Jonas Smedegaard writes: > > Quoting Russ Allbery (2017-03-09 04:24:09) > > >> In general, I don't want to see us place too many restrictions on > >> Recommends. If you don't want additional helpful programs, disable > >> installi

Re: Depends/Recommends from libraries

2017-03-09 Thread Russ Allbery
Andrey Rahmatullin writes: > On Thu, Mar 09, 2017 at 12:22:17PM -0800, Russ Allbery wrote: >> Sure, but hopefully we find and report those as bugs. I personally run >> without recommends on Debian unstable on several different types of >> systems and report these problems whenever I run into the

Re: Depends/Recommends from libraries

2017-03-09 Thread Russ Allbery
Adam Borowski writes: > What's wrong in the current state is that it looks only from the point > of view of the library: libwrap1 is useless without tcpd, thus it's > natural for it to have an elevanted severity. But that dependency is > wrong from a more global point of view. That's why I'm pr

Re: Depends/Recommends from libraries

2017-03-09 Thread Marvin Renich
* Russ Allbery [170309 13:19]: > I think this would be a great way of introducing spurious bugs in our > distribution from people who don't happen to read the README file and miss > dependencies they actually need... I think you are missing Ian's meaning. Currently foo Depends libbar, and libbar

Re: Depends/Recommends from libraries

2017-03-09 Thread Nick Phillips
On Thu, 2017-03-09 at 10:19 -0800, Russ Allbery wrote: > > I think this would be a great way of introducing spurious bugs in our > distribution from people who don't happen to read the README file and > miss > dependencies they actually need because they're used to Debian > properly > picking up s

AppStream Re: Depends/Recommends from libraries

2017-03-09 Thread Rebecca N. Palmer
appstream itself is installed on ~60% of sid/stretch desktops [0], but isenkram on only ~5% (and most of those are the -cli version). When beignet-opencl-icd added AppStream metadata (black line in [1]), there was no noticeable increase in its installs. As it's for popular hardware (~33% of s

Re: AppStream Re: Depends/Recommends from libraries

2017-03-09 Thread Jeremy Bicha
On Thu, Mar 9, 2017 at 6:23 PM, Rebecca N. Palmer wrote: > When beignet-opencl-icd added AppStream metadata (black line in [1]), there > was no noticeable increase in its installs. As it's for popular hardware I think a lot of those appstream installs are from KDE and GNOME which install plasma-

Work-needing packages report for Mar 10, 2017

2017-03-09 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: 1055 (new: 5) Total number of packages offered up for adoption: 167 (new: 0) Total number of packages reques

Bug#857318: ITP: golang-github-optiopay-kafka -- Go client library for Apache Kafka

2017-03-09 Thread Potter, Tim
X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Package: wnpp Severity: wishlist Owner: Tim Potter * Package name: golang-github-optiopay-kafka Version : 0.0~git20150921.0.bc8e095-1 Upstream Author : Piotr Husiatyński * URL : ht

Bug#857319: ITP: golang-gopkg-olivere-elastic.v3 -- Elasticsearch client for Golang

2017-03-09 Thread Potter, Tim
X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Package: wnpp Severity: wishlist Owner: Tim Potter * Package name: golang-gopkg-olivere-elastic.v3 Version : 3.0.41-1 Upstream Author : Oliver Eilhard * URL : https://github.com/ol

Bug#857320: ITP: kubernetes-addon-heapster -- Resource usage analysis and monitoring addon for Kubernetes

2017-03-09 Thread Potter, Tim
X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Package: wnpp Severity: wishlist Owner: Tim Potter * Package name: kubernetes-addon-heapster Version : 1.2.0 Upstream Author : Vish Kannan, Marcin Wielgus, Piotr Szczesniak * URL :

Re: Release file for own backport repository?

2017-03-09 Thread Paul Wise
On Thu, Mar 9, 2017 at 7:36 PM, Joerg Desch wrote: > After this, "apt-get update" prints the error (jessie expected but jessie- > backports received): Did you also update your sources.list? -- bye, pabs https://wiki.debian.org/PaulWise

Symbol specific dependencies (was Re: Depends/Recommends from libraries)

2017-03-09 Thread Guillem Jover
Hi! On Thu, 2017-03-09 at 17:29:09 +, Ian Jackson wrote: > I think the right way to solve this problem is to declare that: […] > * If a library needs or wants additional software installed, >if and when functions in that library are called, this >should be documented in the /usr/share

Re: Release file for own backport repository?

2017-03-09 Thread Joerg Desch
Am Fri, 10 Mar 2017 11:04:40 +0800 schrieb Paul Wise: > Did you also update your sources.list? No, because I use the directory name for it. Or isn't an entry with an trailing slash an directory? deb http://debian.jdesch.de/repositories/experimental/ jessie/

Re: Depends/Recommends from libraries

2017-03-09 Thread Russ Allbery
Marvin Renich writes: > If libbar-dev documents that it requires bar-daemon (and under what > circumstances, if appropriate), but libbar does not declare the Depends, > then it becomes the Debian maintainer of foo who decides to add an > appropriate Depends, Recommends, or Suggests for bar-daemon