[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [frankie@debian.org: Re: HDF5 migration to 1.8.4]



On Tue, Feb 23, 2010 at 12:34:25PM +0100, Marc 'HE' Brockschmidt wrote:
> "Adam D. Barratt" <adam@adam-barratt.org.uk> writes:
> > On Mon, 2010-02-22 at 20:19 +0100, Francesco P. Lovergine wrote:
> >> On Mon, Feb 22, 2010 at 02:45:36PM -0000, Adam D. Barratt wrote:
> >> > Salvatore Bonaccorso wrote, Mon, 22 Feb 2010 15:30:41 +0100:
> >> > >What is the status about this? Should individual binNMU be
> >> > >requested? (@RMs)
> >> > binNMUs were scheduled earlier today.
> >> > 
> >> > See http://lists.debian.org/debian-release/2010/02/msg00234.html and
> >> > the follow-up.
> >> Note that octave is not the only build-rdep. If you prefer so, I would
> >> fill in a complete set of binNMU snippets updated to today.
> > Yes, please.
> 
> I've now constructed my own list and scheduled the following binNMUs:
> nmu 1 yorick-hdf5_0.8.0-1 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 2 udav_0.5.2-1 . kfreebsd-amd64 mips ia64 kfreebsd-i386 amd64 . -m "Rebuild against new hdf5"
> nmu 1 udav_0.5.2-1 . s390 alpha hppa powerpc mipsel sparc armel i386 . -m "Rebuild against new hdf5"
> nmu 2 plplot_5.9.2-3 . kfreebsd-amd64 s390 alpha hppa kfreebsd-i386 powerpc sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 2 h5py_1.2.1-2 . mips mipsel sparc . -m "Rebuild against new hdf5"
> nmu 2 pygpiv_2.0.0-1 . mips . -m "Rebuild against new hdf5"
> nmu 1 mpb_1.4.2-14 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 4 tessa_0.3.1-4 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 1 octave3.0_1:3.0.5-7 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 1 libgpiv_0.6.1-3 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 1 hdf-eos5_5.1.12.dfsg.2-2 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 3 minc_2.0.18-1 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 1 octave-optim_1.0.6-1 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 2 pytables_2.1.2-3 . mips mipsel sparc . -m "Rebuild against new hdf5"
> nmu 1 mathgl_1.9-2 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 1 pfstools_1.8.1-1.1 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 2 labplot_1.6.0.2-3 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 1 meep_1.1.1-3 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> nmu 1 r-cran-hdf5_1.6.9-2 . kfreebsd-amd64 mips s390 alpha hppa powerpc mipsel ia64 kfreebsd-i386 sparc amd64 armel i386 . -m "Rebuild against new hdf5"
> 

AFAIK there are still missings:

gnudatalanguage                                                                                                                                              
mpb                                                                                                                                                          
gpivtools (apparently pre-depends on libgpiv?)                                                                                                                                                   
h5utils                                                                                                                                                      

-- 
Francesco P. Lovergine


Reply to: