Your message dated Fri, 12 Oct 2007 10:22:25 +0200 with message-id <[🔎] 1192177345.27009.12.camel@localhost> and subject line [Pkg-octave-devel] Bug#446331: Octave forge package has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Octave forge package
- From: Stefan Söffing <soeffing@gmx.de>
- Date: Fri, 12 Oct 2007 09:52:42 +0200
- Message-id: <[🔎] 1192175562.12196.2.camel@localhost>
- Reply-to: soeffing@gmx.de
Package: octave2.9 Version: 1:2.9.14-1 Hi, what happened to the octave2.9-forge package? Please re-add this package... Do I really have to install them manually from source now? - Stefan
--- End Message ---
--- Begin Message ---
- To: soeffing@gmx.de, 446331-done@bugs.debian.org, Debian Octave Group <pkg-octave-devel@lists.alioth.debian.org>
- Subject: Re: [Pkg-octave-devel] Bug#446331: Octave forge package
- From: Thomas Weber <thomas.weber.mail@gmail.com>
- Date: Fri, 12 Oct 2007 10:22:25 +0200
- Message-id: <[🔎] 1192177345.27009.12.camel@localhost>
- In-reply-to: <[🔎] 1192175562.12196.2.camel@localhost>
- References: <[🔎] 1192175562.12196.2.camel@localhost>
Hi, I'm closing this bug-report. It's simply not a bug in Octave or any other package in Debian. Please use the pkg-octave-devel address for discussing this further. Am Freitag, den 12.10.2007, 09:52 +0200 schrieb Stefan Söffing: > Package: octave2.9 > Version: 1:2.9.14-1 > > Hi, > > what happened to the octave2.9-forge package? It was removed, after not working for, uh, 6 months?. I think the last working version of it was against Octave 2.9.9; though I may be wrong here. By working I mean that it was actually compiled against the then current Octave with a matching API number. This means that its .oct files didn't load. The .m files might be working, though. > Please re-add this package... Using which source? There is no monolithic upstream tarball anymore. > Do I really have to install them manually from source now? For the time being: yes. Regards Thomas
--- End Message ---