Hi,
On Fri, 17 Jul 2015 09:31:53 +0200 (CEST) Thorsten Glaser t.gla...@tarent.de
wrote:
using build profiles breaks debian-ports architectures, all of them:
http://buildd.debian-ports.org/status/package.php?p=x264
[...]
So this means that because someone added the build profiles thing,
Hi,
Quoting Steven Chamberlain (2013-11-28 01:04:56)
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
Hi,
Quoting Dmitrijs Ledkovs (2013-11-28 01:15:06)
On 28 November 2013 00:04, Steven Chamberlain ste...@pyro.eu.org wrote:
I also find it interesting to see openjdk-7 listed but not gcj; or even
gcc-4.8. Was this computed for jessie or sid?
I guess implicit relationships are not
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
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.
Hi Peter,
Quoting peter green (2013-10-27 01:11:24)
Johannes Schauer wrote:
Until these two issues are fixed we will not be able to get an algorithmic
answer to the question of what constitutes the minimum required set of
packages.
There is also the complication of what I will call
Hi,
(I was not able to find the debian-ports list on lists.debian.org (so I
subscribed via email) did I just miss it?)
Quoting Steven Chamberlain (2013-10-23 22:04:59)
I had a play with the 'botch' tool (see description[1]) for determining build
order when bootstrapping an architecture.
botch
7 matches
Mail list logo
