Luca Falavigna wrote:
> Policy § 2.5 [0] states packages must not depend on other packages with
> lower priority values. In order to better adhere to it, FTP Team
> recently implemented a new tool that generates a list of override
> disparities[1] daily.
There's also:
http://qa.debian.org/debchec
Package: wnpp
Severity: wishlist
Owner: Janos Guljas
* Package name: python-mongoengine
Version : 0.4
Upstream Author : Harry Marr
* URL : http://mongoengine.org/
* License : MIT
Programming Lang: Python
Description : A Python Document-Object Mapper fo
Package: wnpp
Severity: wishlist
Owner: Vincent Cheng
* Package name: nevernote
Version : 0.9.6
Upstream Author : Randy Baumgarte
* URL : http://nevernote.sourceforge.net/
* License : GPL-2
Programming Lang: Java
Description : An open source clone des
Olaf van der Spek writes ("Re: Forwarding bugs upstream"):
> Maybe some tools (PTS) should warn about bugs that are older than X
> days and are still unclassified?
That's just a way to make more noise. They show up in the BTS
searches already.
Ian.
--
To UNSUBSCRIBE, email to debian-devel-req
Ian Jackson writes:
> As I understand it we are not in danger of having infrastructure
> capacity problems at the BTS due to these bugs, and the maintainers
> who think they are a very low priority don't want to see them can
> easily arrange that with the pretty sophisticated filtering and
> sear
On Thu, Jan 13, 2011 at 1:38 AM, Ian Jackson
wrote:
> But in this case I don't think we should be "expecting" maintainers to
> necessarily shepherd bug reports upstream. I don't think a maintainer
> who fails to do so is failing in their job as maintainer.
>
> The maintainer should decide whether
Felipe Sateler writes ("Re: Forwarding bugs upstream"):
> On Wed, 12 Jan 2011 16:56:56 +, Ian Jackson wrote:
> > I think it is always reasonable for the maintainer to forward the bug
> > upstream.
> >
> > But what I think is bad is _demanding_ or _requiring_ the maintainer to
> > forward the b
Olaf van der Spek writes ("Re: Forwarding bugs upstream"):
> On Thu, Jan 13, 2011 at 12:12 AM, Sune Vuorela wrote:
> >> Will this mean that the problem will somehow disappear from
> >> Debian? Because if it's a problem detected within Debian it's my
> >> feeling that it will have to be tracked wi
On Wed, 12 Jan 2011 16:56:56 +, Ian Jackson wrote:
> I think it is always reasonable for the maintainer to forward the bug
> upstream.
>
> But what I think is bad is _demanding_ or _requiring_ the maintainer to
> forward the bug upstream. If they don't want to do that for whatever
> reason t
Russ Allbery writes:
> What I think many people are saying in this thread is that, among all
> the things that a Debian package maintainer could do to improve the
> package and user experience of those using the package, being a
> go-between for Debian bug reporters and upstream is something they
On Tue, Jan 11, 2011 at 11:47:17PM +0100, Luca Falavigna wrote:
> Policy § 2.5 [0] states packages must not depend on other packages with
> lower priority values. In order to better adhere to it, FTP Team
> recently implemented a new tool that generates a list of override
> disparities[1] daily.
>
Ben Finney writes:
> Indeed, the Debian project can't demand or require any work of anyone. I
> think it's perfectly acceptable for any such volunteer to refuse to do
> the work.
> But if they do refuse, then to what extent is that person accomplishing
> the maintainer role?
I feel like it's ra
On Thu, Jan 13, 2011 at 12:12 AM, Sune Vuorela wrote:
>> Will this mean that the problem will somehow disappear from Debian? Because
>> if it's a problem detected within Debian it's my feeling that it will have to
>> be tracked within Debian till the problem is in Debian no more.
>
> No. but it i
Ian Jackson writes:
> I think it is always reasonable for the maintainer to forward the bug
> upstream.
>
> But what I think is bad is _demanding_ or _requiring_ the maintainer
> to forward the bug upstream. If they don't want to do that for
> whatever reason then asking the submitter to do so
On 2011-01-12, Jesús M. Navarro wrote:
>> I have considered to take this one step further. Close bugs reported in
>> Debian BTS with a severity of important or less that is a bug that
>> should primarily be fixed upstream.
>
> Will this mean that the problem will somehow disappear from Debian? Be
Anssi Kolehmainen wrote:
Hi all,
I just updated packages (which upgraded network-manager to 0.8.1-6) and then
rebooted computer. I was greeted with a five minute wait while ntpd tried to
query dns which was broken since network-manager decided to start, ignore
bridge mappings, do dhcp on physica
Package: wnpp
Severity: wishlist
Owner: Andrew Ross
* Package name: libitext5-java
Version : 5.0.5
Upstream Author : Bruno Lowagie, Paulo Soares, et al.
* URL : http://itextpdf.com/
* License : Various: AGPL-3, LGPL, BSD, Apache 2.0
Programming Lang: Java
Hi, Sune:
On Wednesday 12 January 2011 14:27:23 Sune Vuorela wrote:
> On 2011-01-11, brian m. carlson wrote:
> > I've noticed a trend lately that I am often asked to forward the bugs I
> > report to the Debian BTS upstream, either by the maintainers or
> > automatically by a bug script. I believ
Package: wnpp
Severity: wishlist
Owner: Miriam Ruiz
* Package name: deap
Version : 0.6
Upstream Author : DEAP Development Team
* URL : https://code.google.com/p/deap/
* License : LGPL-3+
Programming Lang: Python
Description : Distributed Evolutionary
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: drupal6-mod-views-groupby
Version : 1.0-rc2
Upstream Author : Irakli Nadareishvili (http://drupal.org/user/96826)
* URL : http://drupal.org/project/views_groupby
* License : GPL
Programming L
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: drupal6-mod-views-charts
Version : 1.1
Upstream Author : Irakli Nadareishvili (http://drupal.org/user/96826)
* URL : http://drupal.org/project/views_charts
* License : GPL
Programming Lang: P
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: drupal6-mod-flashnode
Version : 3.1
Upstream Author : Stuart Greenfield (http://drupal.org/user/54866)
* URL : http://drupal.org/project/flashnode
* License : GPL
Programming Lang: PHP
Desc
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: drupal6-mod-swftools
Version : 2.5
Upstream Author : Stuart Greenfield (http://drupal.org/user/54866)
* URL : http://drupal.org/project/swftools
* License : GPL
Programming Lang: PHP
Descri
On Wed, 2011-01-12 at 19:43 +0100, Christian PERRIER wrote:
> My plans are to upload before the end of the upcoming week-end an NMU
> for each of the affected package(s).
>
> I currently have:
fwiw, from a quick look at the list, at least boxbackup would need a
t-p-u upload in order to get fixed
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: drupal6-mod-charts-graphs
Version : 2.6
Upstream Author : Irakli Nadareishvili (http://drupal.org/user/96826)
* URL : http://drupal.org/project/charts_graphs
* License : GPL
Programming Lang:
Package: wnpp
Severity: wishlist
Owner: NeuroDebian Team
* Package name: pyxnat
Version : 0.6.2
Upstream Author : Yannick Schwartz
* URL : http://packages.python.org/pyxnat
* License : BSD
Programming Lang: Python
Description : interface to access neu
Hi all,
I just updated packages (which upgraded network-manager to 0.8.1-6) and then
rebooted computer. I was greeted with a five minute wait while ntpd tried to
query dns which was broken since network-manager decided to start, ignore
bridge mappings, do dhcp on physical port of the bridge (which
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: drupal6-thm-nokia-mobile
Version : 1.3
Upstream Author : Andrea Trasatti (http://drupal.org/user/170041)
* URL : http://drupal.org/project/nokia_mobile
* License : GPL
Programming Lang: PHP
Quoting Christian PERRIER (bubu...@debian.org):
> I have ready NMUs for most of the affeted packages. I can upload them
> soon.
My plans are to upload before the end of the upcoming week-end an NMU
for each of the affected package(s).
I currently have:
astk_1.8.0-1.2
bandwidthd_2.0.1+cvs200909
On ma, 2011-01-10 at 10:56 +0100, Stefano Zacchiroli wrote:
> So, the only timeframe during which the problem can be experienced is
> from now to the solution of #609160. I wonder if it is really worth to
> address this issue properly---by changing either the intended usage of
> Format: or by addin
On Wed, Jan 12, 2011 at 02:56:35PM +, brian m. carlson wrote:
[...]
> Also, if the BTS won't CC me when someone responds
> to the bug (even with an account), there is zero chance of me reporting
> the bug upstream, since I have better things to do with my life than
> constantly checking a slew
brian m. carlson writes ("Re: Forwarding bugs upstream"):
> On Tue, Jan 11, 2011 at 09:15:41PM -0600, John Goerzen wrote:
> > I think it is perfectly fine for a user to submit a bug report to
> > the Debian BTS first. They may not always be equipped to know what
> > is a Debian and what is an upst
John Goerzen writes ("Re: Forwarding bugs upstream"):
> I'm going to have a slightly different viewpoint on this.
I agree with John, basically.
> I'm adding zero value here. Zero. [...]
Some people have replied suggesting scenarios where the Debian
maintainer is adding something. That's fine
Package: facturinex2
Severity: wishlist
Owner: Nicolas Lopez de Lerma Aymerich
* Package name : facturlinex2debian-de...@lists.debian.org
Version : 2.0.0
Upstream Author : Nicolas Lopez de Lerma Aymerich
* URL : http://facturlinex.sourceforge.net/
* License : GPL
Description: Billing appl
Ben Finney dijo [Wed, Jan 12, 2011 at 04:01:46PM +1100]:
> (...)
> > I'm adding zero value here. Zero. It is a huge and frustrating waste
> > of my time.
>
> Not in my view. I appreciate the Debian package maintainer acting in the
> interest of “lower the barrier for each Debian user of this packa
On Tue, Jan 11, 2011 at 09:15:41PM -0600, John Goerzen wrote:
> I think it is perfectly fine for a user to submit a bug report to
> the Debian BTS first. They may not always be equipped to know what
> is a Debian and what is an upstream bug. And I also think it ought
> to be perfectly valid for t
Package: wnpp
Severity: wishlist
Owner: Adnan Hodzic
* Package name: light-themes
Version : 0.1.8.4
Upstream Author : Ubuntu Artwork Team
* URL : https://launchpad.net/light-themes
* License : (CCPL)
Programming Lang:
Description : Radiance and Ambi
(re-adding debian-project@ to the loop so both lists have the attendees info)
On Fri, Jan 7, 2011 at 10:33, Stefano Zacchiroli wrote:
> On Thu, Dec 30, 2010 at 11:58:05AM +0100, Stefano Zacchiroli wrote:
>> We're organizing a cross-distro meeting in January to discuss the
>> "application installe
On 2011-01-11, brian m. carlson wrote:
> I've noticed a trend lately that I am often asked to forward the bugs I
> report to the Debian BTS upstream, either by the maintainers or
> automatically by a bug script. I believe, and I continue to believe,
I have considered to take this one step furthe
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: osmpbf
Version: 1.1
Upstream Author: Scott A. Crosby.
URL: http://github.com/scrosby/OSM-binary
License: LGPL-3+
Description: Java access library for OpenStreetMap PBF fil
On Wed, Jan 12, 2011 at 07:53:09AM +0100, Christian PERRIER wrote:
> > Many of these packages errors are direct or indirect consequences of
> > my l10n work during the lenny-squeeze release cycle.
> >
> > Direct when the last uploaded version is an NMU of mine..
> >
> > Indirect when a maintainer
Drake Wilson, 2011-01-11 20:19:34 -0700 :
[...]
> This doesn't leave much in the way of good options:
>
> - Having the user report bugs twice
[...]
> - Having the maintainer be the reporter of record for upstream
[...]
> - Having the maintainer forward the bug report but make the user the
>
* Drake Wilson [2011-01-12 08:09] wrote:
> Quoth Paul Wise , on 2011-01-12 10:55:34 +0800:
> [among other responses]
> > Sourceforge and probably Gforge/FusionForge trackers.
> >
> > The only tracker I'm aware of which would work is Trac, some instances
> > of which allow anyone to put in anyone
Le mardi 11 janvier 2011 à 23:54 +, brian m. carlson a écrit :
> I've noticed a trend lately that I am often asked to forward the bugs I
> report to the Debian BTS upstream, either by the maintainers or
> automatically by a bug script. I believe, and I continue to believe,
> that maintainers
On Mi, 12 ian 11, 10:55:34, Paul Wise wrote:
> On Wed, Jan 12, 2011 at 9:29 AM, Drake Wilson wrote:
>
> > Which upstream bug trackers, if any, would make the above not work?
>
> Sourceforge and probably Gforge/FusionForge trackers.
>
> The only tracker I'm aware of which would work is Trac, som
45 matches
Mail list logo
