Dear Yade users and developers,
As is customary at the beginning of January, we aim to release a new version
of Yade. The release process takes some time, so we kindly request that you
commit all your planned features by the *end of the day on January 19, 2023*
,
so that we can prepare the
"daily" package repository as well, or just to freeze the versions
> there?
>
> Cheers
>
> Bruno
>
>
> On 20/11/2023 20:52, Anton Gladky wrote:
>
> Dear all,
>
> We are adding more and more releases to be supported.|
> Debian Trixie is being added in th
Dear all,
We are adding more and more releases to be supported.|
Debian Trixie is being added in the near future, and later
next year, Ubuntu 24.04 LTS will also be included.
My proposal is to deprecate at least Debian Stretch, Ubuntu 16.04,
and Ubuntu 18.04. We need to free up some resources,
Dear Yade users and developers,
We are excited to announce the release of Yade 2023.02a!
This latest version comes with several new features and improvements
that we hope will enhance your experience with the software.
Thanks to all our developers and users for their contributions to this
created update Changelog MR for this:
>
> https://gitlab.com/yade-dev/trunk/-/merge_requests/917/diffs
>
> best regards
> Janek
>
> Anton Gladky said: (by the date of Mon, 16 Jan 2023 21:16:59 +0100)
>
> > Dear all,
> >
> > as always at the beginning
Dear all,
as always at the beginning of the year we are preparing
the stable Yade Release.
Please, push your changes through merge requests till this Friday,
20.01.2023 and think about adding some more notes into the
Changelog [1].
[1] https://pad.systemli.org/p/yade-2023-changelog
Thank you
enabled in all projects that
> you linked below, it should work? I only checked in docker-prod and
> it seems to work:
>
> https://gitlab.com/yade-dev/docker-prod/-/jobs/3178115457
>
> best regards
> Janek
>
> Anton Gladky said: (by the date of Sat, 15 Oct 2022 11:46:18
Hi.
as you probably know, gitlab is changing its business modell.
Right now we are affected by this change through the usage
of shared runners for some projects.
@Janek, @Bruno or maybe somebody else, could you please
your runner-instances for the following projects:
- Docker-Prod:
Hello Bruno,
thanks for this initiative! I do really support it.
I am personally affected by this situation and my life is being splitted
now on "before" and "after".
Thanks you all for support.
Anton
Am Do., 3. März 2022 um 18:16 Uhr schrieb Bruno Chareyre
:
>
> Hi guys,
>
> My heart is
Dear all,
As discussed during the last meeting of yade-devs, I have prepared
a list of TODO-tasks [1] for Yade, which can be completed during the student
works, Google summer of code and other similar contests and springs.
Feel free to add new ideas (even crazy ones!) into this list. If somebody
Dear Yade users and developers,
As always at the beginning of the year we are releasing the new Yade version.
Yade 2022.01a has just been released [1]!
Thanks all developers and users for contributions! Special thanks to Janek for
his contribution and preparing the release notes!
Last year we
Dear Yade users and developers,
as always at the beginning of January we want to release a new Yade version.
Release process takes some time, so please commit all your planned features
till the end of the December 2021, so we can prepare tarball, test it on all
supported architectures and upload
Dear all,
I am travelling now, but I will try to join.
Regards
Anton
Am Do., 15. Juli 2021 um 11:13 Uhr schrieb Bruno Chareyre <
bruno.chare...@3sr-grenoble.fr>:
> Dear Yade devs,
> For a few months now some of us started holding meetings to discuss dev
> aspects.
> We figured it would be
Hi Bruno,
I have created several branches for all supported distributions (ubuntu and
debian).
Both (yade and yadedaily) are installed, but the doc-packages were dropped,
I
do not think they are needed for production.
Also I tried to reduce the size of the images, so they are just a little
more
Hi Bruno,
this is very interesting! I have never heard about singularity yet. Thanks
for information.
>From my point of view, it is not a problem at all to build docker-images
with yadedaily
inside, if it is helpful for you and anybody. I have some concerns about
large dev-images,
but I am also
Dear Yade users and developers,
As always at the beginning of the year we are releasing
the newer Yade version. A couple of days ago Yade 2021.01a
was released [1]! Thanks all for contributions!
Special thanks to Janek for his contribution and preparing the
release notes! French team thanks for
t; GUI (3 MRs):
> Draw grid label coordinates, allow custom change of grid density.
> remove unaligned margins in GUI inspect.
> Add enum support for GUI dropdown menus.
>
> ===
> Are the extra debian packages yade-long-double or yade-float128, maybe even
> yade-mpfr1
> INRAE, RECOVER
> 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE
> +33 (0)4 42 66 99 21
> https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez
>
> On 12/11/2020 22:18, Anton Gladky wrote:
> > Dear Yade users and develop
Dear Yade users and developers,
backport repositories of Debian 10 Buster (stable) [1]
and Debian 9 Stretch (oldstable) [2] have got an updated
yade_2020.01a.
If you use one of those distributions, you can install updated
Yade from backports:
sudo apt-get install yade -t stretch-backports
or
release notes.
Current git-workflow has too many small log-messages, so it is
difficult to get meaningful information from there. Please use this
link to add some notes [2].
[1] https://wiki.debian.org/DebianBullseye
[2] https://pad.systemli.org/p/yade-2021-release-notes
Thank you
Anton Gladky
Hello Janek,
I think it is a time already to drop qt4 support completely.
> If we decided to remove qt4, then we need to decide which version of
> GLViewer::postSelection(…)
If we drop qt4 directory completely, then we will have only qt5-version
of this method, right?
Regards
Anton
Am So.,
s/444927466
>
> [2] https://gitlab.com/cosurgi/minieigen-real/pipelines/118211208 - I used
> this to test HP
>
> [3] In the pipeline with ccache it's usually not a problem. On
> debian build servers: it won't be a problem until we decide to
> make yade-float128 package.
>
>> > [*] pybind11 is a new dependency and a new package, boost is well
>> > integrated with itself, it was guaranteed to work.
>> >
>> > [1] https://gitlab.com/yade-dev/minieigen/-/jobs/444927466
>> >
>> > [2] https://gitlab.com
Hi Janek,
we have misunderstanding here. python3-minieigen is the __binary__
package and it is a bad idea to ship the source code with the package.
Adding minieigen-src binary package is possible, but it looks like very
undesired way.
As I see, only Yade is using minieigen in the Debian. So,
Hi Janek,
I habe backported both of your patches [1], [2] into the
existing in Debian minieigen-package and uploaded into
the Debian.
The newer minieigen can now be polished, new version released and
uploaded with no rush.
[1] https://github.com/eudoxos/minieigen/pull/24
[2]
FRANCE
> +33 (0)4 42 66 99 21
> https://www6.paca.inrae.fr/recover/personnel/equipes/jerome-duriez
>
> On 27/06/2019 21:15, Anton Gladky wrote:
>
> Dear all,
>
> yadedaily packages are being under renovation at the moment. And now they
> need to be tested.
> I wa
ere in Yade tree many years
ago and we managed to drop them, introducing minieigen packages.
It would not be the best variant to put them in the source again.
[1] https://gitlab.com/yade-dev/trunk/-/merge_requests/396
Regards
Anton
Am Mo., 27. Jan. 2020 um 16:26 Uhr schrieb Janek Kozicki
ank you very much for your hard work!
>>
>>
>> Anton Gladky said: (by the date of Mon, 6 Jan 2020 21:04:35 +0100)
>>
>> > Dear Yade developers,
>> >
>> > I am starting to tag the new release. It happens within the next few
>> days.
>>
i support. Minimal doc for mpi should be complete by
> that time.
>
> I was also planning to name a 3rd edition of the doc with additional authors.
>
> Cheers
>
> Bruno
>
> Le lun. 9 déc. 2019 21:56, Anton Gladky a écrit :
>>
>> Dear Yade developers,
>>
&g
rt.cgi?att=1;bug=946481;filename=python3.8.patch;msg=5
>
>
>
> Anton Gladky said: (by the date of Tue, 31 Dec 2019 15:35:16 +0100)
>
> > This is ipython problem.
> >
> > On Tue, Dec 31, 2019, 13:46 Janek Kozicki (yade)
> > wrote:
> >
> > >
This is ipython problem.
On Tue, Dec 31, 2019, 13:46 Janek Kozicki (yade)
wrote:
> It seems that now we have the same doc building problem as before:
>
> https://gitlab.com/yade-dev/trunk/-/jobs/391247986
>
> reading sources... [ 24%] index-toctree
> reading sources... [ 26%]
Dear Yade developers,
at the beginning of January 2020 I am planning to tag
newer Yade version. After that it will be uploaded into
the Debian and automatically synced into the next
Ubuntu LTS 20.04.
If you are planning some more changes to be pushed into
this version, please prepare merge
The problem was really in python3.8 and ipython in Debian Sid.
See:
https://bugs.debian.org/946481
Anton
Am Di., 3. Dez. 2019 um 21:58 Uhr schrieb Anton Gladky :
>
> Hi Bruno,
>
> thanks for the hint. It looks like the problem is due to
> ongoing Python3.7->Python3.8 tra
> commenting a line in sphinx), it's easily reverted if you want to check.
> Nothing else comes to mind.
> B
>
> [1]
> https://gitlab.com/yade-dev/trunk/commit/33601df81df0a74f5d4618bc8dbf4e54159f6352
>
> On Mon, 2 Dec 2019 at 22:02, Anton Gladky wrote:
>&g
Hmm,
it looks like the problem is in debian:sid, in debian:bullseye everything is
working as expected.
Anton
Am Mo., 2. Dez. 2019 um 20:02 Uhr schrieb Anton Gladky :
>
> Hello all,
>
> I am preparing the newer Yade for the Debian and upcoming Ubuntu LTS.
> It will be pyt
Hello all,
I am preparing the newer Yade for the Debian and upcoming Ubuntu LTS.
It will be python3-only build. A couple of weeks ago the build worked fine.
But now, the compilation stucks on building docs:
==
building [mo]: all of 0 po files
building [html]: all source files
updating
Hallo Bruno,
could you please send me a script, which is doing the download/upload?
Actually, when I do
"wget
https://gitlab.com/yade-dev/trunk/-/jobs/artifacts/master/download?job=pages;
I get right now the error code 8.
Actually, if you use the symbol &&, it will not execute the next step,
Ok, found, changed the path to memoizeDb. ASAN says:
=
==5085==ERROR: AddressSanitizer: SEGV on unknown address 0x (pc
0x7f7d59ac2c6f bp 0x7f7d40cf7ac0 sp 0x7f7d40cf61d0 T16777215)
==5085==The signal is caused by a READ memory access.
==5085==Hint: address points to the zero
I am getting this error:
Traceback (most recent call last):
File "./../inst/bin/yade-trunk", line 337, in runScript
execfile(script,globals())
File "/usr/lib/python3/dist-packages/past/builtins/misc.py", line 82, in
execfile
exec_(code, myglobals, mylocals)
File "2.py", line 41, in
Dear Yade developers,
last weekend [1] we enabled the new target in the pipeline: make_asan.
Also the new Yade option ENABLE_ASAN was added into the Cmake.
Documentation is updated correspondingly.
ASAN - is the abbreviation of AddressSanitizer [2] - memory error detector,
which finds heap
Uhr schrieb Bruno Chareyre
:
>
> Thanks Anton, it makes sense to me.
>
> On Mon, 21 Oct 2019 at 21:02, Anton Gladky wrote:
>>
>> If we do a one-shot-reformatting - it is also OK. But I would then prefer
>> to set the author of this commit, something to "cl
o-formating settings end up in
> committing conflicting auto-formats?
>
> Bruno
>
> [1] https://gitlab.com/yade-dev/trunk/merge_requests/298#note_233001456
>
>
>
> On Sun, 20 Oct 2019 at 21:47, Anton Gladky wrote:
>>
>> Dear all,
>>
>> there are se
l add some
> unreadable diffs. But later it will be a refreshing breeze :)
>
> -- Janek Kozicki
> On 17 Oct 2019, 18:59 +0200, Anton Gladky , wrote:
>
> Hi,
>
> I propose to use the clang-format [1], which automatically formats
> the code according to the pre-defined
Hi,
I propose to use the clang-format [1], which automatically formats
the code according to the pre-defined rules. It has a nice support
by most of IDEs and can also be used through command line.
There are some pre-defined styles (LLVM, Google, Chromium, Mozilla, WebKit),
and i think we just
Hi,
without stack trace it is difficult to analyze.
Please compile Yade with debug symbols,
run your script till it crashes and provide
the stack trace.
Regards
On Mon, Oct 7, 2019, 16:46 William Chèvremont <
william.chevrem...@univ-grenoble-alpes.fr> wrote:
> Dear Yade dev,
>
> I'm facing an
Dear all,
after months of work and tests yadedaily packages
are available again. Thanks all especially to the team
in 3sR in Grenoble and Janek.
Instructions are here [1]. If you find some problems with
it, please file an issue on gitlab [2].
[1]
Dear all,
I have set up the regular rebuilt of all docker images:
for the stable distributions - once a month, fo Debian testing
- weekly. The schedules can be seen and adjusted here [1].
Also the master branch of the trunk is being now rebuilt daily [2].
I hope it will increase the integrity
Dear all,
packages for Debian 11 Bullseye are ready for testing.
In addition to the original mail [1], this action needs to be
done for this distribution:
- *Debian 11 Bullseye*:
sudo bash -c 'echo "deb http://yadedaily.s3.amazonaws.com/debian
bullseye main" >>
y
> useful: a normal user will be able to send us crash reports with
> debug symbols.
>
> cheers
> Janek
>
> Anton Gladky said: (by the date of Wed, 17 Jul 2019 20:17:18 +0200)
>
> > Hi Bruno,
> >
> > > Was there specific difficulties with ubuntu
/ppa_ci/aptly/Dockerfile
Regards
Anton
Am Mo., 15. Juli 2019 um 18:23 Uhr schrieb Bruno Chareyre
:
>
> Hi Anton,
>
> On Fri, 12 Jul 2019 at 19:03, Anton Gladky wrote:
>>
>> Comments, critic are
>> very welcome.
>
>
> This is great! Thank you very much.
&
Dear all,
thank you for testing! It looks like we do not have major problems
with the DEB-packages. The packaging should surely be improved
(especially python3-yadepackage), but it is more less usable now.
That is why I prepared a merge request [1]. Comments, critic are
very welcome.
[1]
Dear all,
yadedaily packages are being under renovation at the moment. And now they
need to be tested.
I want to ask you to do it and give a feedback.
3 Distributions are supported:
- Debian Buster
- Debian Stretch
- Ubuntu 18.04 Bionic
Packages are hosted on Amason S3 for the moment.
The
306cd32ba8e7
>
> To stay on track it is usefu to bookmark this page:
> https://gitlab.com/groups/yade-dev/-/activity
>
> best regards
> Janek
>
>
> Anton Gladky said: (by the date of Sun, 9 Jun 2019 08:00:44 +0200)
>
> > I think the problem is that two or more
I think the problem is that two or more
processes are concurrently creating
moc-files and overwriting it, breaking
the structure.
On Sat, Jun 8, 2019, 21:39 Anton Gladky wrote:
> > Maybe investigating the difference between the "regular" setup and
> > "deb-packages&q
hat mocs compilation always goes first, separately before the
> > rest of the compilation.
> >
> > I didn't investigate how to achieve this in CMakeLists.txt
> > maybe this would solve it.
> >
> >
> > Anton Gladky said: (by the date of Sat, 8
Hello all,
there is an annoying error during the Yade compilation
for Deb-Packages, which appears often, but sporadically [1]:
py/CMakeFiles/_utils.dir/build.make:89: recipe for target
'py/CMakeFiles/_utils.dir/_utils_autogen/mocs_compilation.cpp.o'
failed
make[3]: Leaving directory
Sorry for causing those problems. Yes, I did not check this
change on older distributions.
Anyway, the pngmath is deprecated in sphinx_1.8, so this
change is necessary for the newer distributions, where 1.8
is used.
If imgmath is not working properly, we need to investigate
the problem deeper.
Hi guys,
I committed those changes. pngmath is not part of sphinx any more,
so the change is really necessary
Anton
Am Fr., 1. Feb. 2019 um 18:25 Uhr schrieb Robert Caulk
<1814...@bugs.launchpad.net>:
>
> Yes, Mathjax seems cleaner. Does it result in better resolution of math
> on the web.
Hello yade devs,
as far as I understand we are moving (have moved already) to
GitLab. But I saw some commits on github as well.
Some questions:
- Should we disable commits on github?
- Should all links in the Yade code be updated to GitLab variants?
- Do we prepare release from GitLab?
Also
t; best regards
> Janek
>
>
> Bruno Chareyre said: (by the date of Wed, 16 Jan 2019 11:13:02 +0100)
>
> > Hi Anton,
> > I think current code is stable and it is a good time to freeze.
> >
> > @All
> > Does someone have hot stuff to be included (shor
Dear Yade developers,
the previous Yade version was released almost a year ago.
What is the state of the code right now? Would it be possible
to make a new release within the next a couple of weeks?
The new Debian release is being prepared at the moment and
the soft freeze is planned for
n 2019 at 21:40, Anton Gladky wrote:
>>
>> Sorry guys, I still cannot understand, what brings:
>> - renaming master->develop
>> - having potentially broken/not-mergable experimental branch.
>
>
>
> Oh yes, it's confused. Things will become more clear w
;
>
>
>
> Janek Kozicki said: (by the date of Wed, 9 Jan 2019 15:24:18 +0100)
>
> > Anton Gladky said: (by the date of Tue, 8 Jan 2019 20:45:15 +0100)
> >
> > > Hi Bruno,
> > >
> > > > Anton, do you have comments on MR on Gitlab interface
t;
> Anton, do you have comments on MR on Gitlab interface? Do you confirm that
> they are a must? Did you ever hack the API to trigger them from CLI (that
> would mae Janek happy ;) )?
> Thx
> Bruno
>
>>
>> On 07/01/2019 20:36, Anton Gladky wrote:
>> > -
Hi all,
please do not forget, that Yade has already a rich opportunity
to create semi-unit-tests (yade --test) and nice semi-integration-tests
(yade --check). Sure, one can create unit tests for pure C++-functions
using boost::unit_test, cppunit or googletest etc., but I would propose
first to
Hello all,
last several years I did Yade releases and the process was
the following. Before the release was done I created the corresponding
release-branch (for example 0.60 [1]) and just tagged the new
Yade version there. It worked relatively good.
-->
Hello Janek,
thanks for the fix! I have checked it and it really resolves the problem
with the newer CGAL. I will reactivate CGAL-function for the
Debian-build again.
Regards
Anton
Am Mo., 7. Jan. 2019 um 13:44 Uhr schrieb Janek Kozicki :
>
> Bruno Chareyre said: (by the date of Sun, 6 Jan
Hello,
I would vote for the option with merge requests. Yade
has enough core developers to review, comment and
accept those requests. And it is not a problem if the MR
will take 2-3 days for the review process.
In this case one can see in the GitLab-pipeline, whether the code
compiles, tests
Dear Yade developers,
Yade fails to compile against newest CGAL_4,13,
The corresponding bug on Debian tracker is [#911685].
[#911685] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911685
Some relevant lines are here.
===
CGT::SimpleVertexInfo, CGT::SimpleCellInfo>;
Hi,
I think it is a very good idea to migrate the code to GirLab.
After >2 years of using this project I can only say the positive
about it.
Simple setup of CI/CD, automatic check of merge requests and
approve-technique can really improve the code quality and stability.
Regards
Anton
Am Di.,
ndency on
> python-pyqt5.qtwebkit since it has to be installed manually on the top
> of yadedaily on fresh install? I can try and add it to [1] if you,
> Anton, agree - best way for me to learn.
> Cheers
> Bruno
>
> [1] https://github.com/yade/yadedaily/blob/master/control
>
> On 10
(Moving discussion to yade-dev).
@Remi, would it be possible for you to add 18.04 repo for yadedaily?
It should work out-of-box.
Regards
Anton
Am Mi., 10. Okt. 2018 um 12:22 Uhr schrieb Robert Caulk
:
>
> Question #674958 on Yade changed:
> https://answers.launchpad.net/yade/+question/674958
>
I workarounded it on Weekend [1]. I wanted to test it before the commit
into the Yade's trunk. There are really problems with the new numpy
1.14, python 2 and bz2. tar.gz works.
Also there were some problems with the new sphinx [2]. It should also be
backported into the Yade's trunk.
[1]
Workaround is to use tar.gz instead of bz2.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1774065
Title:
doctests fail with numpy 1.14
Status in Yade:
New
Status in Debian:
Confirmed
Bug
iate
> Irstea, RECOVER
> 3275 route de Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE
> +33 (0)4 42 66 99 21
>
> On 07/05/2018 20:09, Anton Gladky wrote:
>
> Dear Yade developers,
>
> Python 2 reaches end of life and will probably removed
> soon from De
Hi Jerome,
thanks for catching it. This section can be completely removed, because
it is obsolete since many years.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1773337
Title:
Doc section
Dear Yade developers,
Python 2 reaches end of life and will probably removed
soon from Debian [1] and then most probably from Ubuntu-Mint
etc archives too. It is only the question of time. I think it will unlikely
happen till the Buster release (mid 2019), but it will probably
happen at the end
Dear Yade developers,
the new minor Yade 2018.02b was released on 20-th of February.
It allows us to compile Yade against CGAL_4.11 and fixes some
bugs. Tarballs are available on GitHub [1] and Launchpad [2].
Also the new version was uploaded to Debian [3] and even synced
into the Ubuntu LTS
Dear all,
thanks all for the effective and fast
contribution resolving CGAL issue!
I will try to fix polyhedron-crash test
as soon as possible and release
the new minor Yade version.
Best regards
Anton
On Feb 16, 2018 17:27, "Luc Scholtes" wrote:
Hi guys,
Just a
Bruno,
>>
>> I am glad that I can help, and use this opportunity to get back in track
>> ;) So I will do this entire Saturday after I get back home on friday night.
>>
>> Should I work on latest yade trunk?
>>
>> BTW: I'm writing this from an airport ;)
king about here.
> Yade 2018.02a is the candidate source code for producing a binary
> yade-stable in Ubuntu 18.04, correct (approximately)?
> If yes, can we build yade-stable with CGAL at the moment?
> Bruno
>
>
>
> On 02/08/2018 06:35 PM, Anton Gladky wrote:
>>
>>
Well, if we find a way to fix it within the next 2 weeks,
I think there is a chance to get it pushed into Debian->Ubuntu.
Regards
Anton
2018-02-08 15:23 GMT+01:00 Bruno Chareyre :
>
>
> On 02/07/2018 05:35 PM, Janek Kozicki (yade-dev) wrote:
>>
>>
>> Regarding
ednesday this week.
> Cheers
> Bruno
>
>
> On 02/03/2018 05:49 PM, Anton Gladky wrote:
>>
>> Dear Yade developers,
>>
>> the freeze for the next 18.04 LTS version of Ubuntu
>> (stop sync from Debian) will be on the 1st of March.
>>
>> I
Dear Yade developers,
the freeze for the next 18.04 LTS version of Ubuntu
(stop sync from Debian) will be on the 1st of March.
If the newer Yade version should appear here, one
need to release it ASAP and to be pushed in Debian.
Please let me know we if there some reasons not
to release it now.
:00 Bruno Chareyre <bruno.chare...@grenoble-inp.fr>:
>
>
> On 11/29/2017 07:31 PM, Anton Gladky wrote:
>>
>> The question is, how long does Yade want to support Ubuntu 14.04 LTS,
>> where QT5 version of libqglviewer does not exist. Another option is to
>> p
Hi all,
is there any progress on fixing this issue? I have disabled CGAL for
Debian builds, but it would be good to switch it on again.
Also the stable Yade version is almost one year old. It is time to release
something newer soon. If there are some volunteers to go through
existing bugs on
have maybe some useful advice?
>>
>> Am I correct that this FTBFS is about yade in (clean install of)
>> stretch with CGAL 4.11 pulled from experimental?
>>
>> best regards
>> Janek
>>
>>
>> Anton Gladky said: (by the date of Thu, 2 Nov 201
Hi all,
it looks like Yade is not compatible with the new CGAL 4.11 and
it blocks the upload of new CGAL into the Debian [1].
It would be good if somebody could try to fix this issue.
[1] https://bugs.debian.org/876524
Thanks
Anton
___
Mailing
Hi,
I think it makes sense to enable "warnung-as-errors" for buildbot-builds.
So the build will fail if new warnings were introduced in the last commits.
Something like:
cmake -DCMAKE_CXX_FLAGS="-Werror -Wall" ../src/to/yade
Of course one need to fix all warnings before switching it on hardly.
Thanks for bug report. Backtrace is here:
==
#0 0x557b10ddd180 in ()
#1 0x7fac49e31cf9 in
boost::python::converter::shared_ptr_deleter::operator()(void const*) () at
/usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.62.0
#2 0x7fac4bbb951a in
It does not work unfortunately. So, we need an assistance from
Remi to send mails from the buildbot.
Best regards
Anton
2017-06-19 20:53 GMT+02:00 Anton Gladky <gladky.an...@gmail.com>:
> 2017-06-19 14:42 GMT+02:00 Bruno Chareyre <bruno.chare...@grenoble-inp.fr>:
>> Th
2017-06-19 14:42 GMT+02:00 Bruno Chareyre :
> There is probably a way to make github (instead of launchpad) send the
> commit messages.
> Maybe time for a migration?
I have just enabled them. Let's see, whether it will work with
launchpad mailing list. Launchpad
esn't include LINSOLV since yadedaily has it (I
> think??).
> I'll try and have a look.
>
> Bruno
>
> On 05/02/2017 11:34 PM, Janek Kozicki wrote:
>>
>> Anton Gladky said: (by the date of Tue, 2 May 2017 22:38:29 +0200)
>>
>>> Hi Robert,
>&g
Hi Robert,
the Yade should work in any combination of enabled features and should
not fail to compile or to crash. I did not look into your changes, but I think
you need to add a couple of #ifdef guards to make it compilable.
Best regards
Anton
2017-05-02 21:45 GMT+02:00 Robert Caulk
Could you please try to use "O.stop()" insntead of "exit()"?
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1685735
Title:
Exception KeyError
Status in Yade:
New
Bug description:
I run
Hi Bruno,
thanks for the catch and for the fix. This commit was pushed
into the frozen Debian to have it fixed in Stretch [1].
[1] https://tracker.debian.org/news/843733
Best regards
Anton
2017-04-14 12:28 GMT+02:00 Bruno Chareyre :
> Hello all,
> A recent
That issue is already fixed.
Anton
2017-04-13 20:21 GMT+02:00 Janek Kozicki :
> Ouch, this is bad. Did you manage to fix this so far? If not, is
> there still a chance to push a fix to stretch?
> I will have a look at that.
>
> From my previous graphics problems I would start
Hi Bruno,
I have no information whether it is planned to develop it further
and whether somebody is using it. As far as I remember, all
SPH-relevant changes are guarded by the YADE_SPH
macroses.
It looks like isActive is used also in ViscoelasticPM and LudingPM and
ViscoelasticCapillarPM.
Best
Hi guys,
just FYI. I needed to drop PDF-file from the Debian version of yade
for now, because it caused compilation failures and there was a
chance for yade to be dropped from the next stable Debian.
If it is fixed already, I will resurrect PDF file later after release.
Best regards
Anton
Hi,
it can also be a bug in a specific version of CGAL. To exclude a
compiler error, you can try to compile the Yade using Clang
(instructions in the documentation).
Anton
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
1 - 100 of 1673 matches
Mail list logo