On 01/27/15 22:09, Matthias Kilian wrote:
> Hi,
>
> last week, I noticed some build problems while running dpb -uR on
> my build machine (sorry, no list of affected ports, because that
> machine is now inop after a disk failure). If i remember correctly,
> the ports in question
>
> - indirectly depend on textpric/libxml
>
> - lack a liblzma entry in WANTLIB
>
> It probably only hits people like me (running dpb -uR), but with
> enough bad karma, it *may* also hit updates from 5.6 to 5.7 (very
> unlikely, though).
>
> I'd run a make lib-depends-check for all ports, but I have to fix
> my broken build machine first, and I don't know when I'll have the
> time to do it.
>
> Until then, it would be nice if anyone with a complete set of current
> packages and a current ports tree could do that check (and watch
> out for missing liblzma notices).
>
> Ciao,
> Kili
>
>
I hit the same problems as I use dpb -R. I did do fixes for some, not
put in the ports tree.
converters/wv
devel/libgsf
geo/geocode-glib
multimedia/libbluray
textproc/libxml++
textproc/libxslt
www/libcroco
x11/gnome/libxklavier
Quite a few still left...
Using slightly old check-lib-depends run. I used this to give a list of
packages to remove and rebuild that dpb -R would not find.
$ awk -f cld_lzma.awk tmp/c.1 | wc
162 162 6768
$ awk -f cld_lzma.awk tmp/c.1 | head -40
amide-1.0.5p1(graphics/amide):
calf-0.0.18.5p9(audio/calf):
castget-1.0.1p3(net/castget):
compiz-0.8.8p0(x11/compiz/core):
compiz-plugins-main-0.8.8p0(x11/compiz/plugins-main):
compizconfig-python-0.8.4p0(x11/compiz/compizconfig-python):
conky-1.9.0p4-no_x11(sysutils/conky,no_x11):
conky-1.9.0p4-xmms2(sysutils/conky,xmms2):
conky-1.9.0p4(sysutils/conky):
dclib-0.3.7p5(net/dclib):
devhelp-3.14.0p1(x11/gnome/devhelp):
dia-0.97.3(graphics/dia):
drgeo-1.1.0p18(education/drgeo):
droplet-1.1p2(devel/droplet):
emerillon-0.1.90p5(geo/emerillon):
emotion-1.7.9p2(x11/e17/emotion):
etherape-0.9.13p1(net/etherape):
farstream-0.2.6(net/farstream):
flickcurl-1.25(net/flickcurl):
folks-0.10.1(net/telepathy/folks):
fontforge-20120731(print/fontforge):
foxtrotgps-1.2.0(geo/foxtrotgps):
fuse-1.1.1(emulators/fuse):
gconf2-3.2.6p4(devel/gconf2):
gdal-1.11.1p0(geo/gdal,-main):
gdl-3.14.0(x11/gnome/gdl):
gegl-0.2.0p2(graphics/gegl,-main):
geoclue-0.12.99p2(geo/geoclue):
geoclue2-2.1.10p0(geo/geoclue2):
gimmix-0.5.7.1p4(audio/gimmix):
gimp-2.8.14(graphics/gimp/stable):
glade-3.18.3(devel/glade):
gmdb-20070603p15(databases/mdbtools/snapshot,-gmdb):
gmpc-11.8.16p8(audio/gmpc):
gnome-clocks-3.14.1(x11/gnome/clocks):
gnome-system-monitor-3.14.1(x11/gnome/system-monitor):
gnome-vfs2-2.24.4p11(x11/gnome/vfs2):
gnumeric-1.12.18(math/gnumeric):
goffice-0.10.18(devel/goffice):
goffice08-0.8.17p3(devel/goffice08):
The runtime problems can be hit between snapshots, between 5.6 and 5.7
there are two many other changes such as libc chances are very small of
a runtime issue, not impossible.
