Bug#812536: marked as done (nmu: suitesparse transition)

Your message dated Tue, 26 Jan 2016 17:10:12 +0100 with message-id <56a79a64.5070...@debian.org> and subject line Re: Bug#812536: nmu: suitesparse transition has caused the Debian Bug report #812536, regarding nmu: suitesparse transition to be marked as done. This means that you claim th

Bug#812536: nmu: suitesparse transition

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: pkg-julia-de...@lists.alioth.debian.org Dear Release Team, Please schedule binNMUs for the ongoing suitesparse transition (https://release.debian.org/transitions/html/auto

Re: Suitesparse transition

On 31/03/2008, Rafael Laboissiere wrote: > Sure, it could. I took the opportunity to do some fixes and fix > Bug#473438, which were pending in SVN. Have you announced the binNMus > somewhere? I probably missed the announcement. As always, http://ftp-master.debian.org/~vorlon/transition-binnmus.

Re: Suitesparse transition

-> 1.6.6 > > transition came in the way of the suitesparse transition. This move made > > octave3.0 uninstallable in sid, on all architectures. > > Erm, but that could have been handled by binNMUs, surely? (Which I had > already scheduled, and which had already been suc

Re: Suitesparse transition

This upload was necessary because the libhdf5 1.6.5 -> 1.6.6 > transition came in the way of the suitesparse transition. This move made > octave3.0 uninstallable in sid, on all architectures. Erm, but that could have been handled by binNMUs, surely? (Which I had already scheduled, and

Re: Suitesparse transition

the way of the suitesparse transition. This move made octave3.0 uninstallable in sid, on all architectures. Notice that the autobuilders for arm, hppa, mips, mipsel, and s390 will have to wait for hdf5 1.6.6. A bug report with severity level set to serious addressing the problem has been filed agains

Re: Suitesparse transition

* Rene Engelhard <[EMAIL PROTECTED]> [2008-03-27 10:19]: > Sorry, needed a new OOo upload because > - it fixes a important calc calculation bug which we should not impose >on testing > - it most probably wouldn't have gone in anyway without disabling the >build on arm > - openoffice.org

Re: Suitesparse transition

On Wed, Mar 19, 2008 at 3:22 PM, Torsten Werner <[EMAIL PROTECTED]> wrote: > the shogun developer (Sören) is still on vacation but I will contact him > ASAP. Shogun has now been built on all important architectures except hppa where the buildd is very slow. I do not know what we can do here. Ch

Re: Give back petsc [was: Re: Suitesparse transition]

* Adam C Powell IV <[EMAIL PROTECTED]> [2008-03-20 16:06]: > I uploaded new spooles and petsc this morning. Spooles has built > successfully on arm. petsc was tried on hppa, but failed because of > missing lam. lam has not failed on hppa, but 7.1.2-1.3 has not been > attempted; same with armel.

Re: [Pkg-octave-devel] broken buildd (was: Suitesparse transition)

* Torsten Werner <[EMAIL PROTECTED]> [2008-03-22 20:49]: > On Sat, Mar 22, 2008 at 7:07 PM, Rafael Laboissiere <[EMAIL PROTECTED]> wrote: > > Could someone please give shogun back on arm, hoping that cats will not > > pick > > it up? > > I did a binary only upload because cats did pick it up.

Re: [Pkg-octave-devel] broken buildd (was: Suitesparse transition)

On Sat, Mar 22, 2008 at 7:07 PM, Rafael Laboissiere <[EMAIL PROTECTED]> wrote: > Could someone please give shogun back on arm, hoping that cats will not pick > it up? I did a binary only upload because cats did pick it up. Cheers, Torsten -- http://twerner.blogspot.com -- To UNSUBSCRIBE, e

Re: [Pkg-octave-devel] broken buildd (was: Suitesparse transition)

ld someone please give shogun back on arm, hoping that cats will not pick it up? This is blocking both the suitesparse transition and Bug#469701. Thanks, -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Give back petsc [was: Re: Suitesparse transition]

* Rafael Laboissiere <[EMAIL PROTECTED]> [2008-03-20 22:43]: > * Adam C Powell IV <[EMAIL PROTECTED]> [2008-03-20 16:06]: > > > One other note: libmesh and petsc4py may need to be rebuilt after petsc > > goes in, didn't see those on your igloo. Let me know if you want to > > bin-NMU them; otherw

Re: Give back petsc [was: Re: Suitesparse transition]

* Adam C Powell IV <[EMAIL PROTECTED]> [2008-03-20 16:06]: > I uploaded new spooles and petsc this morning. Spooles has built > successfully on arm. petsc was tried on hppa, but failed because of > missing lam. lam has not failed on hppa, but 7.1.2-1.3 has not been > attempted; same with armel.

Re: Give back petsc [was: Re: Suitesparse transition]

On Wed, 2008-03-19 at 22:52 -0400, Adam C Powell IV wrote: > On Wed, 2008-03-19 at 20:29 +0100, Rafael Laboissiere wrote: > > Adam Powell uploaded version 2.3.3-7 of petsc that build-depends > > alternatively on liopenmpi-dev or lam4-dev. This should fix the Dep-Wait > > status on some arches, lik

Re: broken buildd (was: Suitesparse transition)

On 20/03/08 09:19 +0100, Torsten Werner wrote: > Hi, > > please see > : > > lrwxrwxrwx 1 root root 29 May 23 2007 /etc/alternatives/octave-config > -> /usr/bin/octave-config-2.1.71 > > That is

broken buildd (was: Suitesparse transition)

Hi, please see : lrwxrwxrwx 1 root root 29 May 23 2007 /etc/alternatives/octave-config -> /usr/bin/octave-config-2.1.71 That is fully broken. Who can be contacted about the problem? Cheers, T

Re: Give back petsc [was: Re: Suitesparse transition]

On Wed, 2008-03-19 at 20:29 +0100, Rafael Laboissiere wrote: > Adam Powell uploaded version 2.3.3-7 of petsc that build-depends > alternatively on liopenmpi-dev or lam4-dev. This should fix the Dep-Wait > status on some arches, like arm, mips, mipsel, and s390. > > Will the autobuilds automatica

Give back petsc [was: Re: Suitesparse transition]

Adam Powell uploaded version 2.3.3-7 of petsc that build-depends alternatively on liopenmpi-dev or lam4-dev. This should fix the Dep-Wait status on some arches, like arm, mips, mipsel, and s390. Will the autobuilds automatically happen on these arches or should the package be given back on them?

Re: Suitesparse transition

Thomas Weber <[EMAIL PROTECTED]> writes: > On 19/03/08 13:11 +0100, Marc 'HE' Brockschmidt wrote: >> shogun_0.5.1-1 FTBFSed on arm > > Please give shogun back on ARM, latest octave3.0 should fix that. Sorry > for mipsel, no idea. Done. Marc -- BOFH #16: somebody was calculating pi on the server

Re: python-central file moves (was: Re: Suitesparse transition)

Philipp Kern writes: > On Wed, Mar 19, 2008 at 04:58:51PM +0100, Ondrej Certik wrote: > > > And python-scipy FTBFSes on mips... > > python-scipy FTBFSes everywhere, not just mips. The problem is that > > pycentral has moved some files recently. I am about to fix this this > > evening. > > Do you

Re: Suitesparse transition

On 19/03/08 13:11 +0100, Marc 'HE' Brockschmidt wrote: > Rafael Laboissiere <[EMAIL PROTECTED]> writes: > > The suitesparse transition is involving a quite large number of packages. I > > prepared an igloo URL [1] with the ones I think are involved. Please, >

Re: python-central file moves (was: Re: Suitesparse transition)

On Wed, Mar 19, 2008 at 5:27 PM, Philipp Kern <[EMAIL PROTECTED]> wrote: > On Wed, Mar 19, 2008 at 04:58:51PM +0100, Ondrej Certik wrote: > > > And python-scipy FTBFSes on mips... > > python-scipy FTBFSes everywhere, not just mips. The problem is that > > pycentral has moved some files recently

python-central file moves (was: Re: Suitesparse transition)

On Wed, Mar 19, 2008 at 04:58:51PM +0100, Ondrej Certik wrote: > > And python-scipy FTBFSes on mips... > python-scipy FTBFSes everywhere, not just mips. The problem is that > pycentral has moved some files recently. I am about to fix this this > evening. Do you think that this will also cause pac

Re: Suitesparse transition

* Rene Engelhard <[EMAIL PROTECTED]> [2008-03-19 16:21]: > And python-scipy FTBFSes on mips... Reported as Bug#471549 today. The maintainer replied already and (I hope) a fix is in its way. -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Cont

Re: Suitesparse transition

On Wed, Mar 19, 2008 at 4:21 PM, Rene Engelhard <[EMAIL PROTECTED]> wrote: > Hi Rafael, > > Rene Engelhard wrote: > > Marc 'HE' Brockschmidt wrote: > > > > Rafael Laboissiere <[EMAIL PROTECTED]> writes: > > > > The suitesparse tr

Re: Suitesparse transition

> Rene Engelhard wrote: > > Marc 'HE' Brockschmidt wrote: > > > Rafael Laboissiere <[EMAIL PROTECTED]> writes: > > > > The suitesparse transition is involving a quite large number of > > > > packages. I > > > >

Re: Suitesparse transition

[shogun] On Wed, Mar 19, 2008 at 3:16 PM, Rene Engelhard <[EMAIL PROTECTED]> wrote: > But given that arm and mips(el) FTBFSed anyway... the shogun developer (Sören) is still on vacation but I will contact him ASAP. Cheers, Torsten -- http://twerner.blogspot.com

Re: Suitesparse transition

Hi Rafael, Rene Engelhard wrote: > Marc 'HE' Brockschmidt wrote: > > Rafael Laboissiere <[EMAIL PROTECTED]> writes: > > > The suitesparse transition is involving a quite large number of packages. > > > I > > > prepared an igloo URL [1] with t

Re: Suitesparse transition

Hi, Marc 'HE' Brockschmidt wrote: > Rafael Laboissiere <[EMAIL PROTECTED]> writes: > > The suitesparse transition is involving a quite large number of packages. I > > prepared an igloo URL [1] with the ones I think are involved. Please, > > correct me if I

Re: Suitesparse transition

Rafael Laboissiere <[EMAIL PROTECTED]> writes: > The suitesparse transition is involving a quite large number of packages. I > prepared an igloo URL [1] with the ones I think are involved. Please, > correct me if I am wrong. The mips arch seems to be the main blocker now, >

Suitesparse transition

Dear maintainers, The suitesparse transition is involving a quite large number of packages. I prepared an igloo URL [1] with the ones I think are involved. Please, correct me if I am wrong. The mips arch seems to be the main blocker now, followed by hppa. The arm, mipsel, and s390 arches have