What's the rationale for this? Packages which are built against 1.34
need to get their dependencies changed and rebuilt against 1.35. Mere
transitional packages are confusing, and wrong in my opinion.
** Changed in: boost1.35 (Ubuntu)
Status: New = Incomplete
--
jaunty - boost (1.34) to
I forgot to update it - ignore this bug report, it was solved by
rebuilding the packages.
transitional packages are confusing
Thanks for the tip :)
** Changed in: boost1.35 (Ubuntu)
Status: Incomplete = Invalid
--
jaunty - boost (1.34) to boost1.35 transitional dummy packages
This is the list of the transitional dummy packages:
libboost-dbg
libboost-dev
libboost-doc
libboost-date-time-dev
libboost-filesystem-dev
libboost-graph-dev
libboost-iostreams-dev
libboost-program-options-dev
libboost-python-dev
libboost-regex-dev
libboost-serialization-dev
libboost-signals-dev
** Attachment added: boost1.35_1.35.0-8ubuntu5.debdiff
http://launchpadlibrarian.net/22913866/boost1.35_1.35.0-8ubuntu5.debdiff
** Changed in: boost1.35 (Ubuntu)
Sourcepackagename: boost = boost1.35
--
jaunty - boost (1.34) to boost1.35 transitional dummy packages
** Description changed:
Binary package hint: libboost-dev
I have created a patch for boost1.35 source package to include
transitional dummy packages from boost (1.34).
- Testing packages are available in my PPA:
+ Testing packages are available in my PPA (boost1.35 -
Seems I may have done a mistake, libboost-system-dev might not be
required, since it doesn't exist in 1.34. Comments?
This is the apt-cache policy:
$ apt-cache policy libboost-dbg libboost-dev libboost-doc
libboost-date-time-dev libboost-filesystem-dev libboost-graph-dev
libboost-iostreams-dev
