On Wed, Dec 28, 2016 at 11:11 PM, Rich Mattes wrote:
> > polymake-0:3.0r2-1.fc25.src
> FTBFS, segfault in ppc64. Attempting a rebuilt in case it was a
> transient error.
It is not a transient error. It happens every time. I have had no
luck at all in tracking down the source of the problem. I
I spent the day working on the rebuilds required for eigen3-3.3.1, as
outlined by Sandro. Below is a summary of my progress:
On Wed, Nov 23, 2016 at 4:45 PM, Sandro Mani wrote:
> avogadro-0:1.2.0-2.fc26.src
> -> #error Eigen2-support is only available up to version 3.2. Please go to
> "http://ei
On 11.12.2016 22:44, Kevin Kofler wrote:
Hmmm, what will that do to Kalzium, which currently uses both Avogadro
and
Eigen3? I think that will have to move back to Eigen2 as well, which might
require actually reverting upstream porting patches.
Uhm, or I could add a compat-eigen32 subpackage to
Sandro Mani wrote:
> Actually, given the dependency on eigen headers in the public avogadro
> headers, I suppose the only way forward is indeed to revive eigen2.
Hmmm, what will that do to Kalzium, which currently uses both Avogadro and
Eigen3? I think that will have to move back to Eigen2 as wel
Actually, given the dependency on eigen headers in the public avogadro headers,
I suppose the only way forward is indeed to revive eigen2.
Anyone care to swap review with
https://bugzilla.redhat.com/show_bug.cgi?id=1403554?
Thanks
Sandro
___
devel mai
Hi Christian
Could you ping him again? Considering that the viennacl review is going
forward nicely, I'm planning to move forward with the eigen3 update some
time next week, unless Björn needs more time to prepare the shogun update.
Thanks
Sandro
On 25.11.2016 21:08, Christian Dersch wrote:
Hi Sandro,
I've contacted him via Facebook and told him that you're trying to
contact him. I think he'll response soon.
Greetings,
Christian
On 11/25/2016 01:00 PM, Sandro Mani wrote:
> I've seen that the mails to shogun-ow...@fedoraproject.org aka
> fed...@besser82.io are bouncing back becaus
On Friday, 25 November 2016 at 12:58, Sandro Mani wrote:
>
>
> On 25.11.2016 03:44, Kevin Kofler wrote:
> > Sandro Mani wrote:
> > > AFAICS avogadro can still be built against eigen2, so sure, that would
> > > also be a plan. Not sure if reviving the package is better than bundling
> > > though,
I've seen that the mails to shogun-ow...@fedoraproject.org aka
fed...@besser82.io are bouncing back because the besser82.io domain
isn't valid anymore. Does anyone know another way to contact him?
___
devel mailing list -- devel@lists.fedoraproject.org
On 25.11.2016 03:44, Kevin Kofler wrote:
Sandro Mani wrote:
AFAICS avogadro can still be built against eigen2, so sure, that would
also be a plan. Not sure if reviving the package is better than bundling
though, since eigen2 is completely unsupported upstream and its use not
recommended [1]. I
Sandro Mani wrote:
> - avogadro relies on the eigen-2.x compatibility which was removed in
> eigen-3.3, and there is not progress upstream so far in resolving the
> issue.
https://github.com/cryos/avogadro/issues/842
Kevin Kofler
___
devel maili
Sandro Mani wrote:
> - avogadro relies on the eigen-2.x compatibility which was removed in
> eigen-3.3, and there is not progress upstream so far in resolving the
> issue.
https://github.com/cryos/avogadro/issues/842
Kevin Kofler
___
devel maili
Sandro Mani wrote:
> - avogadro relies on the eigen-2.x compatibility which was removed in
> eigen-3.3, and there is not progress upstream so far in resolving the
> issue.
https://github.com/cryos/avogadro/issues/842
Kevin Kofler
___
devel maili
Sandro Mani wrote:
> AFAICS avogadro can still be built against eigen2, so sure, that would
> also be a plan. Not sure if reviving the package is better than bundling
> though, since eigen2 is completely unsupported upstream and its use not
> recommended [1]. I wouldn't want people starting to use
On 24.11.2016 12:56, Dominik 'Rathann' Mierzejewski wrote:
On Wednesday, 23 November 2016 at 22:45, Sandro Mani wrote:
Hi
eigen-3.3.0 was released a a couple of weeks ago, and I've investigated the
consequences of updating in rawhide in this [1] COPR repo. The detailed
analysis is below, the
On Wednesday, 23 November 2016 at 22:45, Sandro Mani wrote:
> Hi
>
> eigen-3.3.0 was released a a couple of weeks ago, and I've investigated the
> consequences of updating in rawhide in this [1] COPR repo. The detailed
> analysis is below, the summary is:
>
> - five dependent packages fail to bui
Hi
eigen-3.3.0 was released a a couple of weeks ago, and I've investigated
the consequences of updating in rawhide in this [1] COPR repo. The
detailed analysis is below, the summary is:
- five dependent packages fail to build due to the eigen3 update:
avogadro, ceres-solver, kalzium, shogun
17 matches
Mail list logo
