Package: libept1.4.12
Version: 1.0.6~exp1
Hi
---
libept (1.0.6~exp1) experimental; urgency=low
* build against libapt in experimental
---
This has only been effective for alpha, amd64 binaries:
$ dpkg-deb -f libept1.4.12_1.0.6~exp1_amd64.deb depends
libapt-pkg4.12 (>= 0.8.16~exp12), libc6 (>= 2.4), libgcc1 (>=
1:4.1.1), libstdc++6 (>= 4.4.0), libxapian22, zlib1g (>= 1:1.1.4)
$ dpkg-deb -f libept1.4.12_1.0.6~exp1_i386.deb depends
libapt-pkg4.10, libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libstdc++6 (>=
4.4.0), libxapian22, zlib1g (>= 1:1.1.4)
The package builds fine against libapt-pkg4.12 on my i386 system.
The buildd logs show that each is using the aptitude-based resolver,
except:
- alpha: apt-based resolver
- amd64: no log; binary upload?
- hurd-i386: internal resolver
Looks like the aptitude-based resolver has opted to install a lower
version of libapt-pkg-dev than the apt-based resolver. With the
options passed to aptitude on these buildds[1] the resolver will
strongly avoid installing packages from experimental.
I have confirmed that aptitude will happily install
libapt-pkg-dev/experimental in a similar situation if asked.
I suspect this could be fixed by bumping libept's [Build-]Depends on
libapt-pkg-dev to (>= 0.8.16~)
Regards
[1] aptitude -y --without-recommends \
-o Dpkg::Options::=--force-confold \
-o Aptitude::CmdLine::Ignore-Trust-Violations=false \
-o Aptitude::ProblemResolver::StepScore=100 \
-o Aptitude::ProblemResolver::SolutionCost="safety, priority,
non-default-versions" \
-o Aptitude::ProblemResolver::Hints::KeepDummy="reject
sbuild-build-depends-libept-dummy :UNINST" \
-o Aptitude::ProblemResolver::Keep-All-Level=55000 \
-o Aptitude::ProblemResolver::Remove-Essential-Level=maximum \
install sbuild-build-depends-libept-dummy
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
