Control: tag -1 pending
Hello,
Bug #976385 in octave-vibes reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-vibes/-/commit/3784be9e9a7eb6f
Control: tag -1 pending
Hello,
Bug #977357 in libgdf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/neurodebian-team/libgdf/-/commit/e1ecf1858c67cdf55bc1520493
Control: tag -1 pending
Hello,
Bug #976436 in octave-ltfat reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-ltfat/-/commit/b0cb4862e4f8766
Control: tag -1 pending
Hello,
Bug #976198 in octave-image reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-image/-/commit/30c72bef7fa4a3b
Control: tag -1 pending
Hello,
Bug #974099 in octave-database reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-database/-/commit/4bfc7b345
Control: tag -1 pending
Hello,
Bug #957627 in octave-optiminterp reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-optiminterp/-/commit/f8d
Control: tag -1 pending
Hello,
Bug #964210 in octave-nan reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-nan/-/commit/b4c7362a6c398613170
Control: tag -1 pending
Hello,
Bug #964211 in octave-instrument-control reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-instrument-contro
Control: tag -1 pending
Hello,
Bug #962217 in libgdf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/neurodebian-team/libgdf/-/commit/51a737871ecc665c70c8be6733
Control: tag -1 pending
Hello,
Bug #960402 in mwrap reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/mwrap/-/commit/60d8f18ba09b242be7c6953f16668
Control: tag -1 pending
Hello,
Bug #952274 in octave-queueing reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-queueing/-/commit/2ded09889
Control: tag -1 pending
Hello,
Bug #945976 in octave-dicom reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-dicom/commit/b7964318613ba4182
Control: tag -1 pending
Hello,
Bug #944718 in octave-dicom reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-dicom/commit/3eee9cf27b1d7fbca
Control: tag -1 pending
Hello,
Bug #931914 in octave-octproj reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-octproj/commit/a683eb8245a9d
Control: tag -1 pending
Hello,
Bug #935584 in octave-octclip reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-octclip/commit/2c8351f28f59f
Control: tag -1 pending
Hello,
Bug #925791 in octave-octclip reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-octclip/commit/0b6a9c0df5128
Control: tag -1 pending
Hello,
Bug #932975 in octave reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave/commit/21f5c108e9f777220526461d718d0
Control: tag -1 pending
Hello,
Bug #919764 in octave-image reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-image/commit/139f9f6522c80f0a5
Control: tag -1 pending
Hello,
Bug #918559 in octave-geometry reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-geometry/commit/8a46637b83e
Control: tag -1 pending
Hello,
Bug #905370 in octave-queueing reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/octave-queueing/commit/6138410441
Control: tag -1 pending
Hello,
Bug #897816 in mwrap reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/pkg-octave-team/mwrap/commit/a314a77d14aea1974840b40b57eb6c
tag 874143 pending
thanks
Date: Mon Sep 11 06:24:22 2017 -0300
Author: Rafael Laboissiere
Commit ID: e009cf318c5d7f02f0d104ef3ebc105cbf4251db
Commit URL:
https://anonscm.debian.org/cgit/pkg-octave/octave-odepkg.git;a=commitdiff;h=e009cf318c5d7f02f0d104ef3ebc105cbf4251db
Patch URL:
https
tag 874138 pending
thanks
Date: Sat Sep 9 14:28:21 2017 -0300
Author: Rafael Laboissiere
Commit ID: a9988b3b911a35b08b045e6b38923a7fefcfa3f2
Commit URL:
https://anonscm.debian.org/cgit/pkg-octave/octave-msh.git;a=commitdiff;h=a9988b3b911a35b08b045e6b38923a7fefcfa3f2
Patch URL:
https
tag 874144 pending
thanks
Date: Mon Sep 4 13:00:30 2017 -0300
Author: Rafael Laboissiere
Commit ID: 394d4c8c32a2a39c83605396c687cbd963b5e04d
Commit URL:
https://anonscm.debian.org/cgit/pkg-octave/octave-control.git;a=commitdiff;h=394d4c8c32a2a39c83605396c687cbd963b5e04d
Patch URL:
https
tag 874139 pending
thanks
Date: Mon Sep 4 12:39:42 2017 -0300
Author: Rafael Laboissiere
Commit ID: 28028a1076fe8e32f9492207b0f8d00f691129f5
Commit URL:
https://anonscm.debian.org/cgit/pkg-octave/octave-signal.git;a=commitdiff;h=28028a1076fe8e32f9492207b0f8d00f691129f5
Patch URL:
https
tag 871214 pending
thanks
Date: Sat Aug 12 06:30:37 2017 -0300
Author: Rafael Laboissiere
Commit ID: d383f06a10084cf511f385f46d569071fb2feef1
Commit URL:
https://anonscm.debian.org/cgit/pkg-octave/octave-image.git;a=commitdiff;h=d383f06a10084cf511f385f46d569071fb2feef1
Patch URL:
https
tag 865241 pending
thanks
Date: Tue Jun 20 03:42:13 2017 -0300
Author: Rafael Laboissiere
Commit ID: 08de6ed4d742af56f276c7fe6b56eb0c4fee7599
Commit URL:
https://anonscm.debian.org/cgit/pkg-octave/octave-ocs.git;a=commitdiff;h=08de6ed4d742af56f276c7fe6b56eb0c4fee7599
Patch URL:
https
tag 826390 pending
thanks
Date: Sun Jun 5 11:19:49 2016 -0300
Author: Rafael Laboissiere
Commit ID: 1715b67a05640bd6738157ca6250b785a08d0a3e
Commit URL:
https://anonscm.debian.org/gitweb/?p=pkg-octave/octave-pkg-dev.git;a=commitdiff;h=1715b67a05640bd6738157ca6250b785a08d0a3e
Patch URL:
https
* Francesco Poli (wintermute) [2016-02-22 22:41]:
Package: isympy
Version: 0.7.6.1-1
Severity: grave
Justification: renders package unusable
I think binary isympy lacks a dependency on python-sympy | python3-sympy.
Without this dependency, installing it leaves the package in an unusable
stat
Control: severity -1 normal
* Hormet Yiltiz [2015-12-12 19:29]:
Package: octave-optim
Version: 1.4.1-1+b1
Severity: serious
Justification: Policy 7.2
octave-optim suggests lyx, which is a office suite that makes working
with LaTeX easy, and implements a way for reproducable research.
Ho
affects 803958 octave
stop
This is just to register the fact that the graphicsmagick's
soversion-bump-without-package-rename is also affecting Octave and the
plethora of packages depending on it.
Please, fix this bug as soon as possible.
Rafael Laboissière
* Simon McVittie [2015-09-04 10:16]:
On Fri, 04 Sep 2015 at 10:00:04 +0100, Simon McVittie wrote:
Looking at the C++ library build-dependencies of octave, it is
waiting for hdf5 (#791067) but everything else seems to be ready.
Looking more closely at this, hdf5 has both a C and a C++ API,
a
Control: tags -1 wontfix
Hi Mike,
Thanks for your thorough reply. There is nothing that we can do as
maintainers regarding this bug. I am hereby tagging this bug report,
accordingly.
Best,
Rafael
* Mike Miller [2015-05-26 22:19]:
On Tue, May 26, 2015 at 14:53:42 +0200, Christoph Egger
tag 778745 pending
thanks
Date: Sun Mar 22 08:25:00 2015 -0300
Author: Rafael Laboissiere
Commit ID: b2d9a2f0206b19bcd3a961d3210595f0fe5c5f5a
Commit URL:
http://anonscm.debian.org/gitweb/?p=pkg-octave/octave-symbolic.git;a=commitdiff;h=b2d9a2f0206b19bcd3a961d3210595f0fe5c5f5a
Patch URL:
http
ere should (1a) be an explicit license embedded in those
man page files, and also (1b) present in the pages displayed by the man
application? If so, I know one way to deal with (1a) which is to
prepend
.\"
.\" Copyright (C) 2001-2004 Rafael Laboissiere
.\"
.\" This progr
tag 740984 pending
thanks
Date: Mon Mar 10 13:57:48 2014 +0100
Author: Rafael Laboissiere
Commit ID: b376eda9a11fb685d96d5f259cec35cc18feb48f
Commit URL:
http://anonscm.debian.org/gitweb/?p=pkg-octave/octave.git;a=commitdiff;h=b376eda9a11fb685d96d5f259cec35cc18feb48f
Patch URL:
http
* Matthias Klose [2014-02-26 15:07]:
Am 26.02.2014 14:15, schrieb Rafael Laboissiere:
Is there a simple way to get your 5.10.0 preliminary package, for instance by
using dget?
found in this ppa:
deb http://ppa.launchpad.net/doko/toolchain/ubuntu trusty main
deb-src http
* Matthias Klose [2014-02-25 16:44]:
Am 25.02.2014 12:08, schrieb Matthias Klose:
trying to fix this in Ubuntu trusty (14.04), ...
- applied the octave patch in swig2.0 (2.0.11-1ubuntu2)
- plplot still fails to build, apparently with the
very same error messages.
https://launchpad.net
* Graham Dennis [2014-01-29 16:09]:
[snip]
I have rewritten the offending code, which I release under the same
license as the rest of XMDS2, i.e. GPL2.
Great, thanks, this was the critical issue. I will soon release a new
version of the package with the changes, and xmds2 will hopefully b
Dear XMDS developers,
A bug with severity level "serious" has been filed against the Debian
package for xmds2, regarding the licensing conditions of several files.
You can find the details in http://bugs.debian.org/736413 (BTW, thanks to
Thorsten Alteholz, who had the patience of verifying the
Package: octave-plplot
Version: 5.9.9-5+b1
Severity: serious
Tags: upstream
Justification: fails to build from source
Control: block 735557 by -1
The current version of the plplot package FTBFS when built against the
octave package 3.8.0-2, currently in experimental. This will block the
transi
* Thomas Weber [2012-12-23 18:09]:
On Thu, Dec 20, 2012 at 07:08:27AM +0100, Andreas Beckmann wrote:
Package: octave3.2
Version: 3.2.4-8
Severity: serious
Tags: squeeze
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + octave-ad octave-zenity
during a test with
package octave
tags 695551 unreproducible moreinfo
stop
* Drew Parsons [2012-12-10 13:03]:
Package: octave
Version: 3.6.2-5
Severity: grave
Justification: renders package unusable
octave has just started failing to start, with the error message:
$ octave -q
panic: Segmentation fault -
* Rafael Laboissiere [2012-07-11 19:58]:
> * Jordi Gutiérrez Hermoso [2012-07-11 13:02]:
>
> > On 11 July 2012 12:44, Rafael Laboissiere wrote:
> > > At any rate, the following is a reproducible bug:
> > >
> > > $ sudo rmdir /usr/share/octave/pac
* Jordi Gutiérrez Hermoso [2012-07-11 13:02]:
> On 11 July 2012 12:44, Rafael Laboissiere wrote:
> > At any rate, the following is a reproducible bug:
> >
> > $ sudo rmdir /usr/share/octave/packages/
> > $ sudo octave --silent --no-history --no-init-file --n
* Santiago Vila [2012-07-11 16:02]:
> On Tue, 10 Jul 2012, Rafael Laboissiere wrote:
>
> > I suspect that your system has some file left over from another package
> > that may be causing the problem. If this is true, then what you are
> > reporting is a real bug that
package octave
reassign 676614 libatlas3-base 3.8.4-5
tags 676614 - unreproducible
tags 676614 + patch
thanks
* Sébastien Villemot [2012-06-08 11:02]:
> Arnaud Installe writes:
>
> > Package: octave
> > Version: 3.6.2-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > D
* Lucas Nussbaum [2009-12-24 11:50]:
> Source: xmds-doc
> Version: 0~svn.1884-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20091213 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> am
* John W. Eaton [2009-06-17 14:24]:
> Are you sure you would want this? It won't tell you if the printing
> is correct without manual inspection, and will clutter the output from
> running "make check" with
>
> src/pr-output.cc ...ans = 0 + 0i
> ans =
* Rafael Laboissiere [2009-06-15 21:55]:
> * John W. Eaton [2009-06-15 13:25]:
>
> > On 15-Jun-2009, Rafael Laboissiere wrote:
> >
> > | Anyway, it is funny to see how long this bug lived in the code and was
> > | just awakened by the crappy mips/mipsel archite
* John W. Eaton [2009-06-15 13:25]:
> On 15-Jun-2009, Rafael Laboissiere wrote:
>
> | Anyway, it is funny to see how long this bug lived in the code and was
> | just awakened by the crappy mips/mipsel architecture...
>
> Also strange that it didn't show up until now,
* John W. Eaton [2009-06-15 09:31]:
> To be consistent with what is done int "set_format (double, ...)", I
> think this should be
>
> diff --git a/src/pr-output.cc b/src/pr-output.cc
> --- a/src/pr-output.cc
> +++ b/src/pr-output.cc
> @@ -851,10 +851,10 @@
>double r_abs = rp < 0.0 ? -rp : rp
* Rafael Laboissiere [2009-06-14 22:45]:
> Now, I am wondering whether the code in set_format() makes sense. The
> function reads:
>
> ///
> static void
> set_format (const Complex& c
* Rafael Laboissiere [2009-06-14 15:39]:
> * Rafael Laboissiere [2009-06-14 12:25]:
>
> > I think that the different values of x_max and x_min explain the bug on
> > the mips system. I guess that this is caused by the following lines in
> > pr-output
* Rafael Laboissiere [2009-06-14 12:25]:
> I think that the different values of x_max and x_min explain the bug on
> the mips system. I guess that this is caused by the following lines in
> pr-output.cc (function set_format):
>
> int x_max =
* Rafael Laboissiere [2009-06-13 09:15]:
> So, even if log2 returns a wrong value, the bug happens elsewhere. At any
> rate, the following works as expected:
>
> complex (NaN, NaN)
> complex (0, NaN)
> complex (NaN, Inf)
>
> I am puzzled with this problem a
* Rafael Laboissiere [2009-06-12 23:09]:
> * John W. Eaton [2009-06-12 13:20]:
>
> > On 11-Jun-2009, Rafael Laboissiere wrote:
> > | (gdb) bt
> > | #0 0x2e17ae24 in std::num_put > std::char_traits > >::_M_insert_float () from
> > /usr/lib/libstdc++.so
* John W. Eaton [2009-06-12 13:20]:
> On 11-Jun-2009, Rafael Laboissiere wrote:
> | (gdb) bt
> | #0 0x2e17ae24 in std::num_put std::char_traits > >::_M_insert_float () from
> /usr/lib/libstdc++.so.6
> | #1 0x2e17b048 in std::num_put std::char_traits > >::do_put () f
* John W. Eaton [2009-06-11 15:42]:
> Did you compile the simpler program with the same options used to
> build Octave?
Probably not.
> Can you run Octave under gdb and find where it hangs, either by
> running
>
> log2 (complex (0, inf))
>
> and interrupting it when the hang happens and get
* John W. Eaton [2009-06-11 11:27]:
> So first, can you determine precisely where Octave is actually
> hannging? Does the following program work, or does it also hang in
> the same way?
>
> #include
> #include
> #include
>
> typedef std::complex Complex;
>
> Complex
> xlog2 (co
* Rafael Laboissiere [2009-06-11 16:07]:
> * Rafael Laboissiere [2009-06-11 01:08]:
>
> > * Peter De Schrijver [2009-06-10 19:40]:
> >
> > > Package: octave3.2
> > > Version: 3.2.0-1
> > > Severity: serious
> > >
> >
* Rafael Laboissiere [2009-06-11 01:08]:
> * Peter De Schrijver [2009-06-10 19:40]:
>
> > Package: octave3.2
> > Version: 3.2.0-1
> > Severity: serious
> >
> > There was an error while trying to autobuild your package:
> >
> > > Automati
* Ralf Treinen [2009-06-10 21:25]:
> Package: libsofa1-dev,libsuitesparse-dev
> Version: libsofa1-dev/1.0~beta4-1
> Version: libsuitesparse-dev/1:3.4.0-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
>
> Date: 2009-06-10
> Architecture: amd64
> Distribution: sid
* Peter De Schrijver [2009-06-10 19:40]:
> Package: octave3.2
> Version: 3.2.0-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
> > Automatic build of octave3.2_3.2.0-1 on mayr by sbuild/mips 99.999
> > Build started at 20090607-1015
Thanks, we are already
* Savvas Radevic [2009-06-03 12:51]:
> > Rafael, you are right, it probably will. But I'm worried about these:
> > (1) Is the remaining /etc/udev/libmtp.rules (and symlink
> > /etc/udev/rules.d/libmtp.rules) going to affect libmtp8? We'll have to
> > ask upstream I guess.
>
> http://sourceforge.
* Raphael Hertzog [2009-06-03 08:54]:
> On Tue, 02 Jun 2009, Rafael Laboissiere wrote:
> > The libmtp7 package contains the file /etc/udev/rules.d/libmtp7.rules. This
> > file is not touched by libmtp8, AFAIK.
> >
> > On the other hand, libmtp5 seems to be affected
[Cc:ing to the BTS, this time, sorry.]
* Savvas Radevic [2009-06-02 15:51]:
> Ah wait, now I get it. Rafael, is "Breaks" allowed on older libmtp* packages?
No, for the same reason Replaces is not allowed.
> It seems like libmtp5-7 might require the older rules (not in /lib)
The libmtp7 packag
* Savvas Radevic [2009-06-02 12:50]:
> I'm not completely sure, but I think the package is missing
> "Conflicts" and "Replaces" for older libmtp* packages?
>
> Something like:
>
> Conflicts: libmtp7, libmtp6, libmtp5
> Replaces: libmtp7, libmtp6, libmtp5
>
> ..in debian/control.in and debian/c
* Adam C Powell IV [2009-05-13 09:34]:
> On Wed, 2009-05-13 at 15:06 +0200, Rafael Laboissiere wrote:
> >
> > This has been already reported as Bug#526422 and the fix is already in
> > Git [1]. I am hereby merging the bug reports accordingly.
>
> I'm sorry,
package octave-ad
tags 528506 confirmed
reassign 528506 octave-dev-pkg
thanks
* Bastian Blank [2009-05-13 12:45]:
> Package: octave-ad
> Version: 1.0.4-2
> Severity: serious
>
> octave-ad and several other octave packages writes files outside the
> build directory.
>
> The build was done, acco
* Luk Claes [2009-05-09 12:55]:
> Rafael Laboissiere wrote:
>
> > I am really frustrated with this bug and I have the impression we
> > are going nowhere. I cannot believe that there is something wrong with
> > the packages, since some of them had successful build
* Philipp Kern [2009-05-08 11:13]:
> On Fri, May 08, 2009 at 09:51:05AM +0200, Adeodato Simó wrote:
> > + Rafael Laboissiere (Fri, 08 May 2009 08:51:05 +0200):
> > > > That's caused by a kernel bug on the mipsen buildds. It's not fixed, but
> > > > a wo
* Rafael Laboissiere [2009-05-02 17:42]:
> * Luk Claes [2009-05-02 14:19]:
>
> > There is only one of them really stalled on the buildd, the others just
> > did not get retried. It being stalled is to debug the problem and it's
> > kind of waiting on you
* Martin Michlmayr [2009-05-05 11:19]:
> * Thomas Weber [2009-05-05 11:10]:
> > On Tue, Apr 28, 2009 at 06:31:32PM +0200, Martin Michlmayr wrote:
> > > Just for the record, I see the same problem on an amd64 system (Intel
> > > EM64T chip).
> >
> > Is this a normal installation or as part of a
* Luk Claes [2009-05-02 14:19]:
> There is only one of them really stalled on the buildd, the others just
> did not get retried. It being stalled is to debug the problem and it's
> kind of waiting on your input how to debug it AFAIK.
I am afraid, I have no idea on how to debug this, speciall
I am revisiting this buildd problem conerning the postinst script of the
octave3.0. I see in the buildd status page for mipsel [1], the following:
State: Building (16)
tbb (26d 00:44, 3/7, mayer) octave-communications (18d 00:24, 10/10, rem)
octave-financial (18d 00:24, 11/11, rem) o
* Martin Michlmayr [2009-04-28 18:31]:
> Just for the record, I see the same problem on an amd64 system (Intel
> EM64T chip).
Thanks for your report.
This bug is driving me crazy. It seems to be a random problem and I have
no clue on how to debug this. Out of desperation, I just upload
octave
* Stephen Gran [2009-04-26 18:50]:
> We currently have another process wedged on mayer.debian.org:
>
> ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -opost -isig -icanon echo ...}) = 0
> ioctl(0, TIOCNXCL, {0x1000 /* B??? */ -op
* Martin Zobel-Helas [2009-04-23 13:17]:
> On Thu Apr 23, 2009 at 12:07:58 +0200, Rafael Laboissiere wrote:
>
> > I am simply lost here and have no idea on how I can debug this random
> > bug.
>
> As soon as i have that bug again on the buildd, i will inform you, so
Hi,
I am contacting you guys who gave me feedback on Bug#524745. I asked
debian-admin to install octave3.0 on the sid chroot of some architectures
where the bug happened. They did it on merulo (ia64) and pescetti
(powerpc).
I can perfcetly launch octave on those machines and successfully run
* Thomas Weber [2009-04-22 23:04]:
> On Wed, Apr 22, 2009 at 12:01:19PM +0200, Laurent Mazet wrote:
> > Package: octave3.0
> > Version: 1:3.0.1-7
> > Arch: i386
> > Severity: grave
> >
> > Hi,
> >
> > I've just realized that I can multiply a real 2x2 matrix by a complex
> > vector.
>
> Uh, yes.
* Stephen Gran [2009-04-21 23:55]:
> This one time, at band camp, Rafael Laboissiere said:
> > * Martin Zobel-Helas [2009-04-21 21:17]:
> >
> > > here some more infos:
> > >
> > > 21029 ?S 0:00 \_ sh -c /usr/bin/sudo /usr/bin/a
* Martin Zobel-Helas [2009-04-21 21:17]:
> here some more infos:
>
> 21029 ?S 0:00 \_ sh -c /usr/bin/sudo /usr/bin/apt-get
> --purge -o
> Dir::State::status=/home/buildd/build/chroot-unstable/var/lib/dpkg/status -o
> DPkg::Options::=--root=/home/buildd/build/chroot-unstable
* Barry deFreese [2009-04-16 11:27]:
> My apologies but I cannot see keeping freetype1 in Debian just for
> ttf2tex. Especially since ttf2tex has not been part of any recent stable
> releases.
>
> Do you have any other thoughts or options before I request removal of
> freetype1 and probably
* Thomas Weber [2009-04-20 00:11]:
> On Sun, Apr 19, 2009 at 05:47:11PM +0200, Luk Claes wrote:
> > Package: octave3.0
> > Version: 1:3.0.5-2
> > Severity: grave
> >
> > Hi
> >
> > The postinst of octave3.0 seems to hang on at least the mipsel buildds (for
> > unstable) [1].
> >
> > This issu
* Aaron M. Ucko [2009-04-10 13:04]:
> Package: octave3.0-headers
> Version: 1:3.0.5-1
> Severity: grave
> Justification: renders package unusable (uninstallable)
>
> octave3.0-headers now aims to depend on exact upstream gcc versions,
> but its approach is somewhat off, in that the dependencies
* John W. Eaton [2009-04-08 21:19]:
> On 9-Apr-2009, Drew Parsons wrote:
>
> | About the severity, I appreciate you need to get the new version across
> | to testing but I don't think I could justify it with this bug.
>
> I agree that we should limit the spread of 3.0.4 as much as possible.
>
package octave3.0
severity 523042 important
thanks
* Rafael Laboissiere [2009-04-08 08:53]:
> I am hereby lowering the severity level of this bug report, [snip]
Doing it now. There was a typo in the header of my previous message.
--
Rafael
--
To UNSUBSCRIBE, email to debian-bugs
package octave3.0
tags 523042 upstream confirmed pending
severity normal
thanks
* Drew Parsons [2009-04-08 11:54]:
> Package: octave3.0
> Version: 1:3.0.4~rc7-1
> Severity: grave
> Justification: causes non-serious data loss
>
> Using the load function to read in a data file, it now skips every
age to unstable.
Cheers,
Rafael Laboissiere
= debian/rules ==
pymtp (0.0.4-1.1) unstable; urgency=low
* Non-maintainer upload, for unblocking the libmtp7 -> libmtp8
transition (closes: #521726), with approval of the package main
* Thomas Perl [2009-04-02 14:37]:
> I am fine with you NMUing pymtp. I can test your modifications locally
> with an MTP device here before you upload, if you want (or tell me if
> the debdiff you posted above is already what you intend to upload).
Please, test my changes.
Yes, it is what I int
* Adeodato Simó [2009-04-02 12:32]:
> * Rafael Laboissiere [Tue, 31 Mar 2009 03:03:29 +0200]:
>
> > [snip]
> > I merged both version for pymtp.py and the resulting debdiff is attached
> > below. I tested it with a Zen Creative device and creation of a track
> &
* Rafael Laboissiere [2009-03-30 16:31]:
> * Thomas Perl [2009-03-30 13:00]:
>
> > The following seems to work for users of MTP devices so far (see the
> > attachment to that bug):
> >
> > http://bugs.gpodder.org/show_bug.cgi?id=307
>
> Thanks for th
* Thomas Perl [2009-03-30 13:00]:
> The following seems to work for users of MTP devices so far (see the
> attachment to that bug):
>
> http://bugs.gpodder.org/show_bug.cgi?id=307
Thanks for the info. The changes to pymtp.py are different from those
that I proposed before. I will test both ve
* Adeodato Simó [2009-03-29 20:08]:
> Package: python-pymtp
> Version: 0.0.4-1
> Severity: serious
> X-Debbugs-CC: Rafael Laboissiere
>
> pymtp hardcodes a dependency on libmtp7, which has been dropped in
> favour of libmtp8. Please take a look into uploading a pack
The RC Bug#514655 against gtick is damn easy to fix for lenny. Should a
fixed package be uploaded to stable-proposed-updates?
--
Rafael
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
* Ralf Treinen [2009-03-19 23:28]:
> Subject: liblapack-doc: tries to overwrite file owned by qdbm-util
> Package: qdbm-util,liblapack-doc
> Severity: serious
Thanks for the heads up. This is indeed a bug in liblapack-doc.
I am taking care of it. There is a bug in debian/rules that makes all
Package: octave3.0
Version: 1:3.0.4~rc5-2
Severity: serious
This version of the octave3.0 package is based on a release candidate
snapshot for the upcoming 3.0.4 version. The upstream authors have told
us [1] that release candidates should not be distributed as Debian packages.
Let us keep this
* Jaroslav Hajek [2009-03-11 09:46]:
> I removed the march=native flag from Makeconf. I have also uploaded an
> updated source tarball containing this fix and all the fixes to
> makefiles & configuration files contributed by Jordi (no actual source
> code changed).
Thanks.
Jordi, are you plan
package octave3.0
tags 517642 confirmed pending
thanks
* Daniel Schepler [2009-02-28 22:09]:
> Package: octave3.0
> Version: 1:3.0.1-7
> Severity: serious
>
> When I tried to rebuild octave3.0 against the new suitesparse libraries, I got
> this in my pbuilder build log (on amd64):
This problem
1 - 100 of 230 matches
Mail list logo
