* Russ Allbery [EMAIL PROTECTED] [2005-10-11 19:22]:
Here is the current status of the mpich/hdf5/lam migration.
The following are uploaded, but some have build problems:
Source: blacs-mpi
Source: hdf5
Source: illuminator
Source: lam
Source: mpb
Source: mpich
Source: netpipe
Source:
(Please note that I'm currently on vacation and won't have Internet access
for another week in about 15 minutes. Just checking in on things while
I'm gone.)
Rafael Laboissiere [EMAIL PROTECTED] writes:
I guess we are getting quite close now (only rmpi on hppa is blocking
now) but shouldn't
fvwm needs a binNMU on ARM for its own sake; it shouldn't be waiting for
libpng, but it is, becaue one of the ARM autobuilders had an old version
of libpng12-dev hanging around.
How does one suggest such a thing?
Likewise gif2png, dillo, ygraph.
(libgdk-pixbuf does too, but it's part of GNOME
I suggest commenting out the KDE/JACK/unixodbc hint for now, since we know
it won't go in for (a) at least two days and (b) until libpng does (barring
gobs of binNMUs), and we further know that it won't give useful information
until then.
Meanwhile, I suggest uncommenting the imlib/libpng hint so
Mozilla has two RC bugs, but they're both present in the version in 'testing'
already. Might as well unclog spidermonkey, epiphany-browser, etc.
force mozilla/2:1.7.12-1
--
Nathanael Nerode [EMAIL PROTECTED]
This space intentionally left blank.
--
To UNSUBSCRIBE, email to [EMAIL
I'm so pleased, I found an easy one.
# Bug #334843
remove php4-maxdb/7.5.00.30-1
easy maxdb-7.5.00/7.5.00.30-3 libdbd-maxdb-perl/7.5.00.32-1
--
Nathanael Nerode [EMAIL PROTECTED]
This space intentionally left blank.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
llvm was compiled with g++ 3.3 on i386, g++-4.0 everywhere else (bug
#330638). As such it is sort of an ugly annoyance in the C++ transition.
Perhaps a binNMU, or a removal, is appropriate. This mismatch is present
in testing as well as unstable since the same version is present in both.
--
7 matches
Mail list logo
