Should be fixed in [1].
Thanks for pointing this out.
[1]
https://github.com/yade/trunk/commit/2bee700259ac4bcfb3151d0fb95cd45be491e114
Anton
** Changed in: yade
Status: New => Fix Released
--
You received this bug notification because you are a member of Yade
developers, which is subs
Klaus,
I have just tested Ubuntu 16.04 and used standard package and yadedaily
and I could not reproduce the problem.
The only warning I get is the following:
OpenGL Warning: No pincher, please call crStateSetCurrentPointers() in your SPU
QColor::setRgbF: RGB parameters out of range
But it has
Klaus,
it is just standard package, installed by apt-get install yade.
Nothing more.
I will try to install Kubuntu on another machine during the next
few days.
Best regards
Anton
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
ht
I can confirm this behavior but I would restrict it only for Kubuntu. I
still have the same feeling that the problem is in Qt-incompatibility
somewhere...
Regards
Anton
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.l
2016-07-27 16:43 GMT+02:00 Václav Šmilauer :
> I am correcting what I said about IPython 5.0. The first version
> supporting qt5 is 3.x. 4.x will probably work with Yade, but with some
> warnings. 5.0 is not compatible due to API changes (custom prompt,
> shortcuts, eventloop integration). That is
2016-09-06 12:12 GMT+02:00 Bruno Chareyre :
> It is packaged for debian to (you can "sudo apt-get install coinor-clp"). So
> I don't think it is a big problem to have it; neither a barrier to share.
> Still a bit more packaging work though.
There almost no packaging work as it is already packaged.
Hi Jerome,
from my point of view, it is not a problem to push those scripts to
the trunk as they are just scripts and you think they can be
useful to other user too.
Of course, they need to get a description in documentation or
(and) have a good example, how to use them. Yes, they can
be pushed t
Hi Bruno,
the only more-less relevant commit is the following [1]. Try to comment
that line and check, whether the regression is no more visible. If it
is so, that problem (described in commit log) should be solved by
more elegant way.
[1]
https://github.com/yade/trunk/commit/07940b52ac31597c07d
re the same, relative
> times are different.
>
> It could be that the counting is wrong. Something system/hardware dependent.
>
> We have troubles with openMP at the moment. So forget it.
>
> Thanks for the link anyway Anton.
>
> B
>
>
>
> On 15 September 2016 a
That is very strange. Normally, you are not able to build Yade
with VTK-support without -dev-package, because you are missing
headers and *.so files which is required by build system.
The problem seems to be in conflict between vtk and eigen3.
Try to use the latest eigen or from the packages. What
I reverted your commit with the hope that nobody pulled it
already.
Please be careful with the "push" command and double
check, what you commit.
Best regards
Anton
2016-09-25 7:46 GMT+02:00 Chia Weng Boon :
> In other words, too many files were committed and the Diffs cannot be
> displayed ont
Hi all,
there is definitely a problem with yade and coming ipyhon5 [1].
Has anybody time and wish to let yade work with ipython5?
[1] https://bugs.debian.org/840527
Best regards
Anton
___
Mailing list: https://launchpad.net/~yade-dev
Post to : ya
2016-11-16 17:58 GMT+01:00 Bruno Chareyre :
> We are actually changing this at the moment. If I'm not wrong (still
> possible because it is a bit intricate): previously the builds were
> triggered manually, by Anton, then the doc uploaded and yadedaily released.
Buildbot built and uploaded the doc
Hi Robert,
thanks for sharing this information with us! It can be really
useful for somebody. There are three opportunities to attach
your guide:
- place it on Yade's wiki
- integrate it into the Yade`s official documentation (into the source code)
- publish it somewhere and add the link into t
Yea, it looks like the buildbot does not build docs and Yade itself.
Remi, could you please have a look?
Thanks
Anton
2017-01-02 19:39 GMT+01:00 Jerome Duriez :
> Hi guys,
>
>
> It seems to me the documentation update frequency is definitely an issue,
> now.
>
> From my PC, the website [*] has
Dear Yade devs,
we have to release the new Yade version soon for two reasons:
- the stable one is already 6 months and 80 commits old.
- the freeze for Debian Stretch is coming soon, so to get
a newer version for the next stable distribution is desirable.
Please try to commit all of your for
Dear Yade dev,
it seems Yade is not working properly on the new (not released)
Debian Stretch. "from yade import qt ; qt.View()" just opening the
window, but it is empty, black screen. qt.Controller shows the same
result.
It is definitely due to some newer libraries, coming with the Debian
and wi
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.
https://bug
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
201
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 r
> as far as I know. No emergency of any sort, just curious about what can
> happen on this side.
> Bruno
>
>
> On 04/04/2017 08:02 PM, Anton Gladky wrote:
>>
>> Hi Bruno,
>>
>> I have no information whether it is planned to develop it further
>> and w
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 at looking at what
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 commit [1] fixed a critical bug of c
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 parame
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 :
> Ok so
LV 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,
>>>
>>> the Y
Dear Yade developers,
I have protected master branch of Yade: disabled force-pushes to this branch
and prevented it from being deleted. Some more information you can
find here [1].
You will not be able to remove any pushed commits. So please think twice
and check all diffs before pushing to escap
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 code import was just like
a backup
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 :
> 2017-06-19 14:42 GMT+02:00 Bruno Chareyre :
>> There is probably a way to make github (instead of launchpad) send the
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 boost::detail::sp_counte
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.
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 list:
ce?
>>
>> 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 2017 21:22:51 +0100)
>>
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 laun
Hi all,
there is an intend to remove Qt4 from the next stable Debian version [1].
If it happens, it will disappear from Ubuntu as well.
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
provide backport of
:00 Bruno Chareyre :
>
>
> 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
>> provide backport of libqglviewer-qt5-dev fo
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.
> 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.
>>
>> If the newer Yade version sho
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 compiling yade with CGAL 4.11, I c
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
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 ;)
>>
>> Best rega
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 remark: the latest fix seems
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 18.0
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 of
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 "Debia
Associate
> 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 Debia
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 des
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] https://
(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
>
dependency 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
>
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.,
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>;
CGT::_Tessela
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 pass
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 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.
--> develop
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 ext
s from somewhere.
>
> 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:
gt;
>
>
> 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
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 wi
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 12.02.20
egards
> 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
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 we
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. T
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.
R
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 '/builds/yade
lude from QT libraries?
>
> btw, did you notice:
> https://salsa.debian.org/science-team/libqglviewer/merge_requests/1 ?
>
> best regards
> Janek
>
> Anton Gladky said: (by the date of Sat, 8 Jun 2019 18:34:49 +0200)
>
> > Hello all,
> >
> > there is an anno
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 Sa
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
06cd32ba8e7
>
> 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 mor
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 follow
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] https://
trunk/blob/master/scripts/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 grea
ich will be very
> 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 difficult
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" >> /etc/apt/sources.list.d/y
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 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] https://yade-dem.org/doc/installation.html#packa
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 i
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 nee
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
lightly) different editing tools and auto-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:
>>
>>
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 "clang-fo
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 corrup
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
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 page
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,
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 env
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 python
r with
> 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 wrot
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
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 reques
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%] index-toctree-boo
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:
> >
> > >
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
t. Thank 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.
>
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 (yade)
:
>
rovence Cedex 5 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.
>
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] https://github.com/e
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, the
ek
>> >
>> >
>> > [*] 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
>> >
>> &g
v/minieigen/-/jobs/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
>
1 - 100 of 2121 matches
Mail list logo