On Sat, 2016-02-20 at 20:53 +0100, Andreas Beckmann wrote: > On 2016-02-20 19:00, Adam D. Barratt wrote: [...] > > Would a jessie2proposed test pull in just the > > single package being tested from p-u, or should it also install versions > > of dependent packages from p-u as well? > > jessie2proposed won't help here. > That test starts with a installation from plain jessie, which already fails. > Thereafter jessie-proposed-updates would get added to the sources.list > and a dist-upgrade would be performed. So dependencies would be resolved > from pu as well. > > But jessie-pu does: > https://piuparts.debian.org/jessie-pu/pass/ruby-activesupport-2.3_2:4.1.8-1+deb8u1.log > (initial installation from jessie + jessie-proposed-updates)
Ack, thanks. Our tools were only highlighting the jessie2proposed issue, I just wasn't sure if there was anything we could do about it or if we'd just have to ignore it as we know that it's fixed in p-u. Thanks for confirming. Regards, Adam
