Re: convention on listen port local or all network interfaces etc.

Am 21.02.2017 um 01:55 schrieb Patrick Schleizer: > for file_name in /usr/lib/server-config.d/*.conf ; do >file_list="$file_list $file_name" > done > > for file_name in /etc/server-config.d/*.conf ; do >file_list="$file_list $file_name" > done > > for file_name in

Accepted slimit 0.8.1-3 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Feb 2017 17:47:50 +1100 Source: slimit Binary: slimit python-slimit python3-slimit Architecture: source all Version: 0.8.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

Bug#855683: ITP: golang-github-makenowjust-heredoc -- Convert strings to here documents in Go

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-makenowjust-heredoc Version : 0.0~git20140704.0.1d91351-1 Upstream Author : TSUYUSATO Kitsune *

Accepted libdap 3.18.3-1 (source amd64 all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 12:45:00 + Source: libdap Binary: libdap23 libdapclient6v5 libdapserver7v5 libdap-bin libdap-dev libdap-doc Architecture: source amd64 all Version: 3.18.3-1 Distribution: experimental Urgency: medium

Bug#855682: ITP: golang-github-xanzy-go-cloudstack -- CloudStack API client for Go

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-xanzy-go-cloudstack Version : 2.1.1+git20160728.1.1e2cbf6-1 Upstream Author : Sander van

Bug#855680: ITP: golang-github-vmware-photon-controller-go-sdk -- VMware Photon Controller API library

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-vmware-photon-controller-go-sdk Version : 0.0~PROMOTED-339-1 Upstream Author : VMware, Inc. *

Bug#855679: ITP: golang-github-lpabon-godbc -- Design-by-contract library for Go

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-lpabon-godbc Version : 1.0+git20140613.1.9577782-1 Upstream Author : Luis Pabón * URL

Rappel : BeMyStreet devient gratuit pour les pros

BeMyStreet devient gratuit pour les pros. Nous avons une bonne nouvelle pour vous ! BeMyStreet devient gratuit pour les professionnels pour votre plus grand plaisir. Alors ne vous en privez surtout pas, vendez en ligne facilement et profitez de tous les avantages BeMyStreet :

Accepted libcpan-perl-releases-perl 3.10-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 Feb 2017 06:46:51 +0100 Source: libcpan-perl-releases-perl Binary: libcpan-perl-releases-perl Architecture: source Version: 3.10-1 Distribution: experimental Urgency: medium Maintainer: Debian Perl Group

Re: Help requested: Packages which FTBFS randomly

On Tue, Feb 21, 2017 at 11:50:15AM +0800, Paul Wise wrote: > On Tue, Feb 21, 2017 at 6:36 AM, Christoph Biedl wrote: > > > This is a charming idea altough I have doubt it will work out: As > > usual the information has to be kept up-to-date, so unless it is > > collected and verified every now

Accepted libmodule-corelist-perl 5.20170220-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 Feb 2017 06:40:08 +0100 Source: libmodule-corelist-perl Binary: libmodule-corelist-perl Architecture: source Version: 5.20170220-1 Distribution: experimental Urgency: medium Maintainer: Debian Perl Group

Accepted rsymphony 0.1-26-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 20 Feb 2017 21:39:36 -0600 Source: rsymphony Binary: r-cran-rsymphony Architecture: source amd64 Version: 0.1-26-1 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk

Re: Help requested: Packages which FTBFS randomly

On Tue, Feb 21, 2017 at 6:36 AM, Christoph Biedl wrote: > This is a charming idea altough I have doubt it will work out: As > usual the information has to be kept up-to-date, so unless it is > collected and verified every now and then automatically, it will > become unsuable pretty soon. FYI the

Accepted tseries 0.10-38-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 20 Feb 2017 20:53:38 -0600 Source: tseries Binary: r-cran-tseries Architecture: source amd64 Version: 0.10-38-1 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel

Accepted chron 2.3-50-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 20 Feb 2017 21:01:00 -0600 Source: chron Binary: r-cran-chron Architecture: source amd64 Version: 2.3-50-1 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel

Accepted date 1.2.37-1 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 20 Feb 2017 20:57:26 -0600 Source: date Binary: r-cran-date Architecture: source amd64 Version: 1.2.37-1 Distribution: unstable Urgency: medium Maintainer: Dirk Eddelbuettel Changed-By: Dirk Eddelbuettel

Accepted r8168 8.044.02-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Feb 2017 03:05:24 +0100 Source: r8168 Binary: r8168-dkms Architecture: source all Version: 8.044.02-1 Distribution: unstable Urgency: medium Maintainer: Andreas Beckmann Changed-By: Andreas Beckmann

Re: Help requested: Packages which FTBFS randomly

On Mon, 2017-02-20 at 23:36 +0100, Christoph Biedl wrote: > Niels Thykier wrote... > > [ topic shift ] > > > On a related note: Having some way to declare minimum requirements for > > e.g. disk space and memory (a la "base GB usage + GB usage/core") used > > would be great. > >   Especially if

Bug#855666: ITP: peek -- create animated GIF screencasts

Package: wnpp Severity: wishlist Owner: "Paulo Roberto Alves de Oliveira (aka kretcheu)" * Package name: peek Version : 0.8.0 Upstream Author : Philipp Wolfer * URL : https://github.com/phw/peek * License : GPL-3+

convention on listen port local or all network interfaces etc.

A convention on listen port local or all network interfaces etc. would be desirable. At the moment it looks like there is no convention for where server applications are configured to listen by default, on localhost vs. all interfaces. Looks like deciding that is up to the upstream author of the

convention on listen port local or all network interfaces etc.

A convention on listen port local or all network interfaces etc. would be desirable. At the moment it looks like there is no convention for where server applications are configured to listen by default, on localhost vs. all interfaces. Looks like deciding that is up to the upstream author of the

Re: Help requested: Packages which FTBFS randomly

Santiago Vila writes: > The following packages FTBFS for me randomly. First column is the bug > number, second column is the estimated probability of failure in my > build environment, which is described here: > https://people.debian.org/~sanvila/my-building-environment.txt >

Re: Help requested: Packages which FTBFS randomly

Holger Levsen writes: > On Mon, Feb 20, 2017 at 09:59:29PM +, Ian Jackson wrote: >> + A FTBFS bug is still RC even if: >> + it doesn't happens on buildd.debian.net; >> + it only happens randomly; >> + it only happens on machines with one (virtual)

Accepted glabels 3.4.0-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2017 23:52:38 +0100 Source: glabels Binary: glabels glabels-data glabels-dev Architecture: source Version: 3.4.0-2 Distribution: unstable Urgency: medium Maintainer: Jakob Haufe Changed-By: Jakob Haufe

Accepted diploma 1.2.13 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 23:46:58 +0100 Source: diploma Binary: diploma Architecture: source all Version: 1.2.13 Distribution: unstable Urgency: medium Maintainer: Andreas Franzen Changed-By: Andreas Franzen

Re: Help requested: Packages which FTBFS randomly

Santiago Vila wrote... > I fully agree with the underlying idea, however: If we can measure the > failure rate, then it means it already fails too often to be acceptable. Cannot deny I somehow like that approach. > For that to happen, the around 50 packages which FTBFS randomly should > do so

Accepted lttng-modules 2.9.1-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2017 17:24:31 -0500 Source: lttng-modules Binary: lttng-modules-dkms Architecture: source Version: 2.9.1-1 Distribution: unstable Urgency: medium Maintainer: Jon Bernard Changed-By: Michael Jeanson

Re: Help requested: Packages which FTBFS randomly

Niels Thykier wrote... [ topic shift ] > On a related note: Having some way to declare minimum requirements for > e.g. disk space and memory (a la "base GB usage + GB usage/core") used > would be great. > Especially if it is available in metadata, so wanna-build can see > whether it makes

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 09:59:29PM +, Ian Jackson wrote: > My advice would be to avoid asking the TC such general questions. My advice too. > There are two sensible questions: > > * Should the following bugs be RC ? > [ list of 20 bugs or whatever ] with a list of 20 bugs I dont

Accepted soundmanager2 2.97a.20150601+dfsg2-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 22:22:49 +0100 Source: soundmanager2 Binary: libjs-soundmanager2 Architecture: source Version: 2.97a.20150601+dfsg2-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers

Re: Help requested: Packages which FTBFS randomly

Santiago Vila writes ("Re: Help requested: Packages which FTBFS randomly"): > Maybe this one for a start?: > > Should building Debian source packages on a single-CPU machine be > supported at the same level as building on a multi-core machine, to > the point that a FTBFS bug on a single-CPU

Re: Help requested: Packages which FTBFS randomly

Vincent Bernat writes ("Re: Help requested: Packages which FTBFS randomly"): > ❦ 20 février 2017 21:13 GMT, Ian Jackson  : > > With the correct infrastructure (which is not that hard) the causes > > can be completely eliminated. I don't ever experience random

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 09:22:35PM +, Ian Jackson wrote: > If you do not get good answers, please take this to the TC.[1] Thanks a lot for your support, Ian. What kind of question do you think I could make to the TC? Maybe this one for a start?: Should building Debian source packages on

Re: Help requested: Packages which FTBFS randomly

❦ 20 février 2017 21:13 GMT, Ian Jackson  : > With the correct infrastructure (which is not that hard) the causes > can be completely eliminated. I don't ever experience random build > failures of any of my own packages and if I did I would hunt them down > with

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

Ian Jackson writes: > Russ Allbery writes: >> The point is that they don't randomly fail in the sense that they don't >> fail n% of the time when run in any possible build environment. >> Rather, in the subset of cases we're talking about in this thread, the >>

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

Russ Allbery writes ("Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)"): > The point is that they don't randomly fail in the sense that they don't > fail n% of the time when run in any possible build environment. Rather, > in the subset of cases

Re: Help requested: Packages which FTBFS randomly

Santiago Vila writes ("Re: Help requested: Packages which FTBFS randomly"): > I don't think that's what we want. Picking on this message at random: Many of the messages in this thread are IMO defending the indefensible, using unreasonable arguments. Reading them, and some of the bug reports you

Accepted soundmanager2 2.97a.20150601+dfsg-2 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 21:02:45 +0100 Source: soundmanager2 Binary: libjs-soundmanager2 Architecture: source Version: 2.97a.20150601+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers

Accepted ri-li 2.0.1+ds-7 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2017 21:43:00 +0100 Source: ri-li Binary: ri-li ri-li-data Architecture: source Version: 2.0.1+ds-7 Distribution: unstable Urgency: medium Maintainer: Debian Games Team

Re: Help requested: Packages which FTBFS randomly

Christoph Biedl writes ("Re: Help requested: Packages which FTBFS randomly"): > Ian Jackson wrote... > > IMO all of these bugs should be RC. A randomly-reproducible build > > failure with more than negligible probabilty is likely to show up for > > some of Debian's users and downstreams and cause

Re: changelog practice, unfinalised vs UNRELEASED vs ~version

Guido Günther writes ("Re: changelog practice, unfinalised vs UNRELEASED vs ~version"): > On Sun, Feb 12, 2017 at 12:48:35PM +, Ian Jackson wrote: > > We do not seem to have a coherent approach to how to handle > > debian/changelog in trees (eg, vcs branches) which are not yet ready > > for

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

On Mon, Feb 20, 2017 at 06:46:25PM +, Holger Levsen wrote: > On Mon, Feb 20, 2017 at 10:29:28AM -0800, Russ Allbery wrote: > > The point is that they don't randomly fail in the sense that they don't > > fail n% of the time when run in any possible build environment. We don't really know. Some

Accepted quicktun 2.2.6-2 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 20:16:23 +0100 Source: quicktun Binary: quicktun Architecture: source amd64 Version: 2.2.6-2 Distribution: unstable Urgency: low Maintainer: Bartosz Fenski Changed-By: Bartosz Fenski

Accepted pg-repack 1.3.4-3 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 15 Feb 2017 11:59:14 +0100 Source: pg-repack Binary: postgresql-9.6-repack Architecture: source Version: 1.3.4-3 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers

Accepted fiona 1.7.4-1~exp1 (source all amd64) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 20 Feb 2017 19:49:22 +0100 Source: fiona Binary: python-fiona python3-fiona fiona fiona-doc Architecture: source all amd64 Version: 1.7.4-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian GIS Project

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

Holger Levsen writes: > On Mon, Feb 20, 2017 at 10:29:28AM -0800, Russ Allbery wrote: >> This is, in a sense, an unreliable test, but it's not unreliable in a >> way that directly affects the main line of package development. > until someone affected wants to contribute…

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

On Mon, Feb 20, 2017 at 10:29:28AM -0800, Russ Allbery wrote: > The point is that they don't randomly fail in the sense that they don't > fail n% of the time when run in any possible build environment. …but point taken, not all FTBFS bugs are RC(!) as

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

On Mon, Feb 20, 2017 at 10:29:28AM -0800, Russ Allbery wrote: > This is, in a sense, an unreliable test, but it's not unreliable in a way > that directly affects the main line of package development. until someone affected wants to contribute… -- cheers, Holger signature.asc

Re: Bug#855597: ITP: phyx -- phylogenetic analyses on trees and sequences for UNIX

Hi Afif, On Mon, Feb 20, 2017 at 08:30:15AM -0800, Afif Elghraoui wrote: > > On Mon, Feb 20, 2017 at 08:14:30AM -0800, Afif Elghraoui wrote: > >> Description : phylogenetic analyses on trees and sequences for UNIX > > > > Please drop " for UNIX" here - since this is redundant on a Debian

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

Holger Levsen writes: > While I agree with Niels that it would be very worthwhile to be able to > define ressource requirements for a package to build (and thus know I > have to life with some packages having trouble sometimes) I find it > *very* strange to be content with

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 11:45:00AM +0100, Vincent Bernat wrote: > Time is a limited resource and we need to set our priorities. Having > test suites that work 100% of the time with constrained resources is not > a goal I find worthy of the time I can spend on Debian. Unfortunately, > those bugs

Accepted libgudev 231-2 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 19:04:01 +0100 Source: libgudev Binary: libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev Architecture: source Version: 231-2 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

On Mon, Feb 20, 2017 at 06:10:23PM +0100, Vincent Bernat wrote: > ❦ 20 février 2017 13:44 GMT, Holger Levsen  : > > >> As a rule of thumb, upstream usually knows better than me which tests > >> are important. Tests are quite important for the packager to know if > >> they

Accepted fonts-nanum 20161025-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Feb 2017 02:27:21 +0900 Source: fonts-nanum Binary: fonts-nanum fonts-nanum-extra Architecture: source all Version: 20161025-1 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force

Re: Help requested: Packages which FTBFS randomly

Le 20 février 2017 16:55:49 GMT+01:00, Julien Cristau a écrit : >On 02/20/2017 07:57 AM, Niels Thykier wrote: >> Vincent Bernat: >>> [...] >>> >>> [...] The policy doesn't state that a package >>> must build when there is not enough disk space or memory. Maybe it >would

Re: Help requested: Packages which FTBFS randomly

On Mon, 2017-02-20 at 08:30 +, Simon McVittie wrote: > On Mon, 20 Feb 2017 at 01:00:33 +0100, Santiago Vila wrote: > > Wait a moment. How we do define "common" when applied to a "build > > environment"? > > Do we rely on it for Debian to function, or was it set up to determine > what works

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 03:24:10PM +, Simon McVittie wrote: > On Mon, 20 Feb 2017 at 10:41:49 +0100, Santiago Vila wrote: > > You are somehow trying to equate RC-ness with "it FTBFS in > > buildd.debian.org". > > No, I'm saying that a sufficiently repeatable FTBFS on buildd.debian.org > is

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

❦ 20 février 2017 13:44 GMT, Holger Levsen  : >> As a rule of thumb, upstream usually knows better than me which tests >> are important. Tests are quite important for the packager to know if >> they didn't make an obvious mistake when updating a package (e.g new >>

Accepted libstring-compare-constanttime-perl 0.312-1 (source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2017 11:02:22 +0100 Source: libstring-compare-constanttime-perl Binary: libstring-compare-constanttime-perl Architecture: source Version: 0.312-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group

Re: Bug#855597: ITP: phyx -- phylogenetic analyses on trees and sequences for UNIX

Hi, Andreas, على الإثنين 20 شباط 2017 ‫08:26، كتب Andreas Tille: > Hi Afif > > On Mon, Feb 20, 2017 at 08:14:30AM -0800, Afif Elghraoui wrote: >> Description : phylogenetic analyses on trees and sequences for UNIX > > Please drop " for UNIX" here - since this is redundant on a Debian

Re: Bug#855597: ITP: phyx -- phylogenetic analyses on trees and sequences for UNIX

Hi Afif On Mon, Feb 20, 2017 at 08:14:30AM -0800, Afif Elghraoui wrote: > Description : phylogenetic analyses on trees and sequences for UNIX Please drop " for UNIX" here - since this is redundant on a Debian system. May be s/ for UNIX/ at command line enabling pipes/ or something

Bug#855597: ITP: phyx -- phylogenetic analyses on trees and sequences for UNIX

Package: wnpp Severity: wishlist Owner: Debian Med Packaging Team * Package name: phyx Version : 0.99 Upstream Author : Joseph W. Brown, Joseph F. Walker, and Stephen A. Smith * URL : https://github.com/FePhyFoFum/phyx *

Bug#855594: ITP: bidi-clojure -- bidirectional URI routing for Clojure

Package: wnpp Severity: wishlist Owner: Apollon Oikonomopoulos Control: block 673515 by -1 * Package name: bidi-clojure Version : 1.25.1 Upstream Author : JUXT LTD. * URL : https://github.com/juxt/bidi * License : MIT/X11 Programming

Re: Help requested: Packages which FTBFS randomly

On 02/20/2017 07:57 AM, Niels Thykier wrote: > Vincent Bernat: >> [...] >> >> [...] The policy doesn't state that a package >> must build when there is not enough disk space or memory. Maybe it would >> be far simpler to allow packages to fail to build if there is not enough >> CPUs. >> > > On a

Accepted radvd 1:2.16-1 (source armhf) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 13:38:42 +0100 Source: radvd Binary: radvd Architecture: source armhf Version: 1:2.16-1 Distribution: unstable Urgency: medium Maintainer: Geert Stappers Changed-By: Geert Stappers

Re: Help requested: Packages which FTBFS randomly

On Mon, 20 Feb 2017 at 10:41:49 +0100, Santiago Vila wrote: > You are somehow trying to equate RC-ness with "it FTBFS in buildd.debian.org". No, I'm saying that a sufficiently repeatable FTBFS on buildd.debian.org is effectively release-critical whether Policy says it is or not, because if we

Accepted libhangul 0.1.0-4 (source all amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 23:48:36 +0900 Source: libhangul Binary: libhangul1 libhangul-data libhangul1-dbg libhangul-dev Architecture: source all amd64 Version: 0.1.0-4 Distribution: unstable Urgency: low Maintainer: Debian Korean L10N

Accepted buku 2.9.0-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2017 22:45:20 +0800 Source: buku Binary: buku Architecture: source all Version: 2.9.0-1 Distribution: unstable Urgency: medium Maintainer: SZ Lin (林上智) Changed-By: SZ Lin (林上智)

Accepted hunspell-dict-ko 0.6.0-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 22:44:40 +0900 Source: hunspell-dict-ko Binary: hunspell-ko Architecture: source all Version: 0.6.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Korean L10N

Accepted fonts-unfonts-extra 1.0.2-080608+dfsg-7 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 23:21:26 +0900 Source: fonts-unfonts-extra Binary: fonts-unfonts-extra Architecture: source all Version: 1.0.2-080608+dfsg-7 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force

Accepted binaryornot 0.4.0+dfsg-0.1 (all source) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Feb 2017 21:07:15 +0900 Source: binaryornot Binary: python-binaryornot python3-binaryornot Architecture: all source Version: 0.4.0+dfsg-0.1 Distribution: unstable Urgency: medium Maintainer: Vincent Bernat

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

On Mon, Feb 20, 2017 at 01:46:20PM +0100, Vincent Bernat wrote: > As a rule of thumb, upstream usually knows better than me which tests > are important. Tests are quite important for the packager to know if > they didn't make an obvious mistake when updating a package (e.g new > dependency

Accepted suricata 3.2.1-1~exp2 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2017 13:29:37 +0100 Source: suricata Binary: suricata suricata-oinkmaster suricata-dbg libhtp-0.5.23-1 libhtp-dev Architecture: source Version: 3.2.1-1~exp2 Distribution: experimental Urgency: medium Maintainer: Pierre

Accepted gitsome 0.6.0-2 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2017 13:46:13 +0800 Source: gitsome Binary: gitsome Architecture: source all Version: 0.6.0-2 Distribution: unstable Urgency: high Maintainer: SZ Lin (林上智) Changed-By: SZ Lin (林上智)

Accepted sklearn-pandas 1.3.0-1 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 12:30:53 + Source: sklearn-pandas Binary: python-sklearn-pandas python3-sklearn-pandas Architecture: source all Version: 1.3.0-1 Distribution: unstable Urgency: medium Maintainer: Christopher Baines

Re: aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

❦ 20 février 2017 11:03 GMT, Holger Levsen  : >> Time is a limited resource and we need to set our priorities. Having >> test suites that work 100% of the time with constrained resources is not >> a goal I find worthy of the time I can spend on Debian. > > While I agree

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 11:33:23AM +, Ghislain Vaillant wrote: > I share the same feelings towards a similar intermittent FTBFS with > src:python-qtpy (#8544936). I admit I have no clue what is going on, > neither does upstream, nor does the reporter (Santiago). That would be #854496. It

Accepted openstack-debian-images 1.17 (source amd64) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 11:36:49 + Source: openstack-debian-images Binary: openstack-debian-images Architecture: source amd64 Version: 1.17 Distribution: unstable Urgency: medium Maintainer: PKG OpenStack

Re: Help requested: Packages which FTBFS randomly

On Mon, 2017-02-20 at 11:45 +0100, Vincent Bernat wrote: > ❦ 20 février 2017 10:05 GMT, Jonathan Dowland  : > > > None of the FTBFS problems I've seen in this thread have been because the > > tests *required* multiple cores, by the way; more so that they were racy > > or buggy

Accepted fastaq 3.15.0-1 (source all) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 12:27:52 +0100 Source: fastaq Binary: fastaq Architecture: source all Version: 3.15.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Med Packaging Team

Re: Help requested: Packages which FTBFS randomly

On 02/20/2017 11:05 AM, Jonathan Dowland wrote: > On Mon, Feb 20, 2017 at 01:57:52AM +0100, Adam Borowski wrote: >> * single-CPU machines have gone the way of the dodo. Even the crummiest >> machine I could find while dumpster-diving looking for a non-sse3 one >> already has HT and builds

Accepted nginx 1.11.10-1~exp1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 11:53:45 +0200 Source: nginx Binary: nginx nginx-doc nginx-common nginx-full nginx-light nginx-extras libnginx-mod-http-geoip libnginx-mod-http-image-filter libnginx-mod-http-xslt-filter libnginx-mod-mail

aren't unreliable tests worse than none? (Re: Help requested: Packages which FTBFS randomly)

On Mon, Feb 20, 2017 at 11:45:00AM +0100, Vincent Bernat wrote: > Time is a limited resource and we need to set our priorities. Having > test suites that work 100% of the time with constrained resources is not > a goal I find worthy of the time I can spend on Debian. While I agree with Niels that

Re: Help requested: Packages which FTBFS randomly

On 02/15/2017 09:45 PM, Santiago Vila wrote: > Building a package is like following an algorithm. It may take less or > more time, but it always has to finish. For this reason, "your CPU is > too slow to build my package" is always a very poor excuse, and I hope > you are not trying to set a

Re: [PKG-Openstack-devel] [openstack-dev] The end of OpenStack packages in Debian?

On 02/19/2017 06:44 AM, gustavo panizzo wrote: > On Sun, Feb 19, 2017 at 01:10:21AM +0100, Thomas Goirand wrote: >> On 02/18/2017 05:14 PM, Andrew Bogott wrote: >>> Does this >>> announcement mean that the Mirantis apt servers (e.g. >>> mitaka-jessie.pkgs.mirantis.com) will also be discontinued >>

Re: Help requested: Packages which FTBFS randomly

❦ 20 février 2017 10:05 GMT, Jonathan Dowland  : > None of the FTBFS problems I've seen in this thread have been because the > tests *required* multiple cores, by the way; more so that they were racy > or buggy in some other fashion. If uniprocessor buildds are finding these >

Accepted poedit 1.8.12-1 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 11:16:09 +0100 Source: poedit Binary: poedit poedit-dbg poedit-common Architecture: source Version: 1.8.12-1 Distribution: experimental Urgency: medium Maintainer: Debian l10n developers

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 01:57:52AM +0100, Adam Borowski wrote: > * single-CPU machines have gone the way of the dodo. Even the crummiest > machine I could find while dumpster-diving looking for a non-sse3 one > already has HT and builds your examples successfully. Same for ARM SoCs > -- my

Accepted six 1.10.0-4 (all source) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 19 Feb 2017 16:30:19 + Source: six Binary: python-six python3-six pypy-six python-six-doc Architecture: all source Version: 1.10.0-4 Distribution: unstable Urgency: medium Maintainer: Colin Watson

Accepted pyicloud 0.9.1-1 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 19 Feb 2017 18:54:20 +0100 Source: pyicloud Binary: python3-pyicloud Architecture: source all Version: 0.9.1-1 Distribution: sid Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 08:30:04AM +, Simon McVittie wrote: > Debian is an operating system, not an academic exercise. If a package > builds successfully reliably enough on buildds, porterboxes, and > developers' hardware or VMs that we can prepare security updates and > other urgent patches

Accepted console-setup 1.161 (source all) into unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 08:35:32 +0100 Source: console-setup Binary: keyboard-configuration console-setup console-setup-mini console-setup-linux console-setup-freebsd bdf2psf console-setup-udeb console-setup-amiga-ekmap

Accepted case 1.5.2+dfsg-2 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 16 Feb 2017 14:04:44 + Source: case Binary: python3-case python-case-doc Architecture: source all Version: 1.5.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team

Accepted pyvenv-el 1.9-1 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 18 Feb 2017 21:32:53 +0500 Source: pyvenv-el Binary: elpa-pyvenv Architecture: source all Version: 1.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Emacs addons team

Accepted pytest-mpl 0.7-1 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Feb 2017 16:58:54 -0500 Source: pytest-mpl Binary: python-pytest-mpl python3-pytest-mpl Architecture: source all Version: 0.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Maintainers

Accepted libhttp-server-simple-cgi-prefork-perl 6-1 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 27 Jan 2017 16:38:40 +0100 Source: libhttp-server-simple-cgi-prefork-perl Binary: libhttp-server-simple-cgi-prefork-perl Architecture: source all Version: 6-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group

Accepted golang-github-bsphere-le-go 0.0~git20170215.0.7a984a8-1 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 20 Feb 2017 07:36:13 +1100 Source: golang-github-bsphere-le-go Binary: golang-github-bsphere-le-go-dev Architecture: source all Version: 0.0~git20170215.0.7a984a8-1 Distribution: unstable Urgency: medium Maintainer: Debian Go

Accepted rubocop 0.47.1+dfsg-1 (source all) into unstable, unstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 Feb 2017 19:37:00 + Source: rubocop Binary: rubocop Architecture: source all Version: 0.47.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers

Re: Help requested: Packages which FTBFS randomly

On Mon, Feb 20, 2017 at 01:57:52AM +0100, Adam Borowski wrote: > * single-CPU machines have gone the way of the dodo. Even the crummiest > machine I could find while dumpster-diving looking for a non-sse3 one > already has HT and builds your examples successfully. Same for ARM SoCs > --

Accepted synergy 1.8.7-stable+dfsg.1-2 (source) into experimental

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 Feb 2017 22:58:36 -0600 Source: synergy Binary: synergy Architecture: source Version: 1.8.7-stable+dfsg.1-2 Distribution: experimental Urgency: medium Maintainer: Joshua Honeycutt Changed-By:

  1   2   >