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

Bug#624179: marked as done (eigen2: New upsteam: 3.0.0)



Your message dated Tue, 26 Apr 2011 10:35:14 +0200
with message-id <BANLkTi=-kXUFrwNkX4+qiKYx9kmYzCOx3Q@mail.gmail.com>
and subject line Re: Bug#624179: eigen2: New upsteam: 3.0.0
has caused the Debian Bug report #624179,
regarding eigen2: New upsteam: 3.0.0
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
624179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624179
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: eigen2
Version: 3.0.0
Severity: normal
Tags: upstream


Hi !

  It would be nice to package eigen 3.0.0:

http://eigen.tuxfamily.org/index.php?title=Main_Page#Download

http://eigen.tuxfamily.org/index.php?title=3.0

 There will be an API change:

http://eigen.tuxfamily.org/dox/Eigen2ToEigen3.html

Thanks !

-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.37-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
Closing bug then.

On Tue, Apr 26, 2011 at 10:31 AM, Anton Gladky <gladky.anton@gmail.com> wrote:
> Hi,
>
> an effort is already done [1], and there is an ITP bug for it [2].
> It requires final reviewing and uploading.
>
> Anton
>
> [1] http://git.debian.org/?p=pkg-kde/krap/eigen3.git
> [2] http://bugs.debian.org/619784
>



-- 
Mathieu


--- End Message ---

Reply to: