Are you referring to the ...and one Front-Cover Text: ``Available free
from http:openfoam.org[openfoam.org]'' part?
I'm afraid that this really means that freefoam-doc would have to move
to unstable. I'm very sure upstream would not consider removing that
sentence, as newer versions of the
On 05/20/2013 01:40 PM, Bastien ROUCARIES wrote:
On Mon, May 20, 2013 at 1:37 PM, Michael Wild
them...@users.sourceforge.net wrote:
I'm afraid that this really means that freefoam-doc would have to move
to unstable.
Non free you means ?
Ugh, yeah. Sorry, complete lapse of mind
That's very strange, it looks like a bug with CMake or GNU Make to me.
Any way I can get access to that hardware? Is there other CMake-based
software failing with similar errors on these architectures? I have
never had this problem before with CMake, but then I also don't have
access to exotic
I just found out that this directory should have been created by CMake
during the configure/generation phase, i.e. before the actual build even
starts.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Bart
On 08/02/2012 07:35 AM, Bart Martens wrote:
Hi Michael,
About your package freefoam at mentors uploaded there on 2012-08-01 08:37.
If nobody increases the bug severities to at least important then I suggest
that you reduce the changes to what is likely acceptable for an unblock.
On 08/01/2012 07:00 PM, Bart Martens wrote:
On Wed, Aug 01, 2012 at 12:15:18PM +0200, Michael Wild wrote:
Some of the bugs are fixed in the upload at m.d.n are not RC, but still
pretty annoying. To get a freeze-exception, would I need to remove those
changes?
What are the bug severities
: Linux 3.2.0-27-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL
set to C)
Shell: /bin/sh linked to /bin/dash
From 6ba7fe4ed4cf45de8edd362bea123acb89bfab82 Mon Sep 17 00:00:00 2001
From: Michael Wild them...@users.sourceforge.net
Date: Fri
Package: freefoam
Version: 0.1.0-1
Severity: serious
Justification: Policy 2.1
Dear Maintainer,
The source package contains several non-free files. Namely, these are:
* Removed by upstream in commit e0497b96c7c179ff85d76a06245171a119e291ba:
-
Package: freefoam
Version: 0.1.0-1
Severity: serious
Justification: fails to build from source
Dear Maintainer,
Building the Doxygen documentation fails because of a missing build-dependency
on graphviz. Without the dot utility Doxygen is not able to generate the graphs.
-- System Information:
/FoamHeader.html.in
Copyright: 2008-2012, Michael Wild them...@users.sf.net
License: GPL-3+
Files:
doc/UserGuide/*.asy
doc/UserGuide/*.png
doc/UserGuide/images/tut_plateHole_leftPatch_sigmaxx.xy
doc/UserGuide/images/post_Ux_0
doc/js/MathJaxMacros.js
Copyright: Copyright (C) 2008-2012 Michael Wild them
Package: freefoam
Version: 0.1.0-1
Severity: serious
Justification: Policy 8.1
Dear Maintainer,
According to policy section 8.1, shared library packages must have the SOVERSION
appended to the base package name. I.e. it should be called libfreefoam1.
-- System Information:
Debian Release:
On 07/27/2012 09:28 PM, Bart Martens wrote:
user sponsorship-reque...@packages.debian.org
usertags 682968 fit-for-wheezy
stop
Hi Michael,
I had a look at your package at mentors uploaded there on 2012-07-27 13:32.
The change to debian/gbp.conf is not mentioned in debian/changelog.
Just uploaded a new version to m.d.n with the d/changelog entry.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 07/26/2012 10:23 PM, Sebastian Ramacher wrote:
Hi Karl,
On 26/07/12 21:48, Karl Rupp wrote:
thanks for the patch. Just two short questions:
* Which compiler (version) did you use?
gcc 4.7
* Do you happen to know whether the error shows up with ViennaCL 1.3.0 as
well?
ViennaCL
On 07/27/2012 12:45 AM, Sebastian Ramacher wrote:
Hi Michael,
On 26/07/12 22:39, Michael Wild wrote:
How should I proceed? Should I upload viennacl-1.2.0-2 to mentors and
ask for sponsorship? I don't suppose that 1.3.0-1 would be uploadable
due to the freeze, right?
Michael
The diff
Oops, sent to the wrong address... Here we go again:
AFAIK clang-2.9 can't deal with libstdc++6-4.6-dev (at least without
backporting r130057): http://llvm.org/bugs/show_bug.cgi?id=9472.
That's why I proposed the build-dep on libstdc++6-4.5-dev in the first
place.
Michael
--
To UNSUBSCRIBE,
16 matches
Mail list logo
