[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cross compiler ITP (armel)



On 23/03/2011 11:59, Goswin von Brederlow wrote:
Philipp Kern<trash@philkern.de>  writes:

On 2011-03-23, Goswin von Brederlow<goswin-v-b@web.de>  wrote:
Also does the testing transition consider the Built-Using? If I specify
'Built-Using: gcc-4.5 (= 4.5.2-5)' will the package be blocked from
entering testing until gcc-4.5 (= 4.5.2-5) has entered and block gcc-4.5
(= 4.5.2-5) from being replaced from testing?

It doesn't need to.  All we want is compliance on the archive side so that the
sources are not expired away, as long as that binary is carried in a suite.
No need to involve britney at that point.

Kind regards
Philipp Kern

Not quite. For ia32-libs it would be nice if ia32-libs could be blocked
from testing as long as the source packages it includes aren't in
testing. Currently that is solved by building against testing in the
first palce. But that is something we can live with.


It's correct that there is no need to consider Built-Using when migrating
packages from one distribution to another, because the information there
is too strict. Instead, we could check that Build-Depends are fulfilled
when migrating the package. But, this is a long standing known issue
(#145257).

Regards,

--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/


Reply to: