On Sat, Feb 27, 2016 at 8:04 AM, Steven Chamberlain wrote:
> As far as the dashboard goes, I've started out with:
> https://kfreebsd.eu/dashboards/ports/
Seems like that should be moved here:
https://buildd.debian.org/status/
> I want to add pages per-arch that list the packages that FTBFS,
Al
Some thoughts after reading the thread:
I would have thought porters would be following the buildd/piuparts/CI
pages for their port (where available) and thus would not need to be
notified about arch-specific FTBFS or testing issues. If porters are
relying on package maintainers or some automation
Thanks you for your response, much appreciated
Very useful information we are going to digest...
eric
From: Josh Max [mailto:joshu...@hotmail.com]
Sent: Monday, February 22, 2016 11:38 AM
To: debian-devel@lists.debian.org
Cc: Eric Mittelette ; j...@debian.org
Subject: RE: Debian package on Window
Thanks you very much for your response, that make sense... let us refine our
thinking on that
Keep you posted
eric
-Original Message-
From: paul.is.w...@gmail.com [mailto:paul.is.w...@gmail.com] On Behalf Of Paul
Wise
Sent: Thursday, February 25, 2016 4:20 AM
To: debian-devel@lists.debi
Steven Chamberlain wrote:
> I envisage some kind of a scoreboard, graphs, or those weather symbols
> we all love to see.
As far as the dashboard goes, I've started out with:
https://kfreebsd.eu/dashboards/ports/
I want to add pages per-arch that list the packages that FTBFS,
one-per-line, showing
Hi Simon,
Thanks you very much for your comments and information.
We are digesting it and will come back later on these
eric
-Original Message-
From: Simon Richter [mailto:s...@debian.org]
Sent: Thursday, February 25, 2016 9:27 AM
To: debian-devel@lists.debian.org; Eric Mittelette
Subj
Ian Jackson wrote:
> Sorry to be discouraging, but I don't think this is the right
> approach.
That's ok, I'm happy to be talked out of the auto-removals part.
> [...] I definitely don't want to see us routinely dropping packages
> from an arch, without anyone having taken a decision about whethe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Fri, Feb 26, 2016 at 09:02:48PM +, Steven Chamberlain wrote:
> > Removing the package from the breaking port is an option, and it
> > should be easy to trigger, but it should not be automatic. If we make
> > the process easy and the mainta
Hi Antonio,
Quoting Antonio Terceiro (2016-02-26 21:47:03)
> On Fri, Feb 26, 2016 at 07:59:29PM +0100, Jonas Smedegaard wrote:
>> Do we favor tracking the true upstreams when packaging for Debian?
>>
>> Concretely I need¹ a javascript library for server-side use, but the
>> maintainer considers i
Steven Chamberlain writes ("Re: Making Debian ports less burdensome"):
> I think the testing autoremoval thing started out the same way, it
> merely reported long-standing RC bugs, but removal was manual in the
> beginning.
>
> Okay, perhaps I should start working on:
>
> * A report of out-of-d
Package: wnpp
Severity: wishlist
Owner: Bas Couwenberg
* Package name: mapbox-variant
Version : 1.1.0
Upstream Author : MapBox (https://github.com/mapbox/variant/issues)
* URL : https://github.com/mapbox/variant
* License : BSD-3-Clause
Programming Lang: C++
Package: wnpp
Severity: wishlist
Owner: "Jeremías Casteglione"
* Package name: git-arr
Version : 0.14
Upstream Author : Alberto Bertogli
* URL : http://blitiri.com.ar/p/git-arr/
* License : MIT
Programming Lang: Python
Description : git repository brows
Hi,
Bas Wijnen:
> Removing the package from the breaking port is an option, and it
> should be easy to trigger, but it should not be automatic. If we make
> the process easy and the maintainer doesn't do it (and also doesn't
> fix the bug), I think it is reasonable to auto-remove the package from
On Fri, Feb 26, 2016 at 07:59:29PM +0100, Jonas Smedegaard wrote:
> Hi,
>
> Do we favor tracking the true upstreams when packaging for Debian?
>
> Concretely I need¹ a javascript library for server-side use, but the
> maintainer considers it adequate² to package that project only
> browser-opti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Fri, Feb 26, 2016 at 07:59:29PM +0100, Jonas Smedegaard wrote:
> Do we favor tracking the true upstreams when packaging for Debian?
There was some discussion about this on the list recently, but this is a
question that didn't really come up, A
Hi,
Do we favor tracking the true upstreams when packaging for Debian?
Concretely I need¹ a javascript library for server-side use, but the
maintainer considers it adequate² to package that project only
browser-optimized.
I personally feel it is a bug to not track the true upstream of a
proje
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I like your suggestions in general, but am a bit worried about the results of
this:
On Thu, Feb 25, 2016 at 05:41:57PM +, Steven Chamberlain wrote:
> * If left unfixed, the bugs should trigger an auto-removal from
> unstable so that the
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-positional
Version : 1.0.1
Upstream Author : Morgan Fainberg
* URL : https://github.com/morganfainberg/positional
* License : Apache-2.0
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: kss-node
Version : 2.4.0
Upstream Author : John Albin Wilkins
* URL : https://kss-node.github.io/kss-node/
* License : Expat or GPL-2
Prog
Control: reassign -1 qa.debian.org
Control: retitle -1 UDD: upstream watch file checker is broken with devscripts
2.16.1
On Fri, 2016-02-26 at 11:45 +0100, Vincent Danjean wrote:
> Package: tracker.debian.org
> Severity: normal
>
> Hi,
>
> In the PTS, all packages I currently look at displa
Package: tracker.debian.org
Severity: normal
Hi,
In the PTS, all packages I currently look at display the following
"action needed" item:
* Problems while searching for a new upstream version
When looking at the details, it seems to be a connectivity problem
(and I checked for a few packag
Package: wnpp
Severity: wishlist
Owner: Edward Betts
* Package name: python-nameparser
Version : 0.3.11
Upstream Author : Derek Gulbranson
* URL : https://github.com/derek73/python-nameparser
* License : LGPL-2.1+
Programming Lang: Python
Description :
22 matches
Mail list logo
