Bug#730619: [PATCH] Add a transition collision detector.

Package: ben Version: 0.6.6 Severity: normal Le 09/02/2012 18:21, Niels Thykier a écrit : While this post-processing of generated HTML files is kind of ugly, it makes it easy to show which transitions might be entangled due to collisions. [...] I am in favor of using this as a temporary

Bug#710176: transition: libpqxx

On 2013-11-26 22:35:36, Julien Cristau wrote: calligra FTBFS: https://buildd.debian.org/status/package.php?p=calligra Hi Julien, Thx for the info, but I'm not sure if there is anything I can do about it as it looks like upstream bug. I just filled a bug (#730632) against calligra package. I

Bug#710176: Bug#730632: calligra: FTBFS with libpqxx-4.0

CCing the release.d.o bug. Marcin: As you already stated, Calligra won't switch to libpqxx4 but to libpq. But that will happen (hopefully) early next year. We really don't want to drop psql support. Is there any chance to have libpqxx3 back with a bigger epoch until that release? The dev

Re: Scheduling for 7.3

On 2013-11-16 15:57, Jonathan Wiltshire wrote: According to the normal schedule, the point release for 7.3 is due somewhere around 12th December. How does everybody look for the weekends of: 14th/15th Maybe; but I'd prefer one of the other two suggestions. 21st/22nd 28th/29th December?

A new metric for source package importance in ports

Hi, the following is a report of a successful implementation of what I have been talking about with Niels Thykier during debconf13. The question was how important it is for a source package to be compilable or exist in the first place given an incomplete port which is in the process of being

Processed: tagging 729071

Processing commands for cont...@bugs.debian.org: tags 729071 + pending Bug #729071 [release.debian.org] transition: libmatroska Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 729071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729071

Re: A new metric for source package importance in ports

Hi josch! On 27/11/13 17:58, Johannes Schauer wrote: http://mister-muffin.de/p/Gid8.txt One can see that now the amount of source packages which is needed to build the rest of the archive is only 383. So, there are 383 packages that share the same, maximum value (in this case 11657) in

Re: A new metric for source package importance in ports

Johannes Schauer wrote: Hi, the following is a report of a successful implementation of what I have been talking about with Niels Thykier during debconf13. The question was how important it is for a source package to be compilable or exist in the first place given an incomplete port which is in

Re: A new metric for source package importance in ports

On 28 November 2013 00:04, Steven Chamberlain ste...@pyro.eu.org wrote: Hi josch! On 27/11/13 17:58, Johannes Schauer wrote: http://mister-muffin.de/p/Gid8.txt One can see that now the amount of source packages which is needed to build the rest of the archive is only 383. So, there are

Re: A new metric for source package importance in ports

Instead of dwelling on this discovery, which is not productive, why not concentrate on what to do to improve Debian. The analysis has shown faults. Has Debian stopped working?  Has the world crashed?  The problems have been identified, the patches to address the issues are being evaluated

Re: A new metric for source package importance in ports

Hi, Quoting peter green (2013-11-28 01:12:57) One problem with these metrics is that you get source packages whose importance is artifically inflated because of the way our source packages work. If anything in a source package needs x then the whole source package has to build-depend on x.