Re: [Plplot-devel] PLplot Debian package

Dear Alan, On 12.07.2017 09:05, Alan W. Irwin wrote: > On 2017-07-11 13:43-0700 Alan W. Irwin wrote: >> I agree this confusion between upstream and Debian is not ideal. >> However, Debian packaging is important to us since it does reveal some >> deficiencies (at least from the Debian point of

Re: [Plplot-devel] PLplot Debian package

Dear Alan, On 13.07.2017 11:27, Alan W. Irwin wrote: >> I already have a few small questions. First language bindings: Currently >> the following are disabled: >> >> ENABLE_ada: OFF >> ENABLE_d: OFF >> ENABLE_octave: OFF >> ENABLE_pdl: OFF >>

Re: [Plplot-devel] PLplot Debian package

On 13.07.2017 21:49, Alan W. Irwin wrote: > Excellent. However, too be sure all is well with Ada and the other > computer languages we support you should build the test_diff_psc > target (which compares the plot output files for our psc device for > all our standard examples for all our

Re: [Plplot-devel] PLplot Debian package

Dear Alan, thank you very much for your quick (and very positive) answer! Concerning the upstream changes: you could for the moment just drop the "debian/" subdir. It will be replaced anyway during the packaging process, and therefore no longer maintained in your git and may be misleading for

[Plplot-devel] PLplot Debian package

Hi, I am a member of the Debian Astro and Debian Science teams. As you may know, PLplot has a Debian package that was also shipped with the latest Debian release [1]. However, the package is outdated and not properly maintained anymore, and so our MIA team decided to "orphan" the package [2],

Re: [Plplot-devel] PLplot Debian package

Dear Alan and all, On 12.07.2017 23:28, Alan W. Irwin wrote: > On 2017-07-12 11:00+0200 Ole Streicher wrote: > I think we are done here with all the current Debian-related topics, > but there will likely be more such topics we need to discuss in the > near future as you continue

Re: [Plplot-devel] PLplot Debian package

Hi Alan, thanks for the answers, and thanks for connecting with Orion. I hope to keep everything together here. > Yes. We have long since implemented a CMake-based build system for > the installed example source code + installed binary libraries that > implements the test_diff_psc, etc.,

Re: [Plplot-devel] PLplot Debian package

Hi Alan, On 15.07.2017 20:37, Alan W. Irwin wrote: > Sometimes our bindings libraries have the same core name (e.g., > wxwidgets, qt) as the device driver, but bindings libraries and > device drivers are completely different and there is no chance of a > nameclash between them. So there should

Re: [Plplot-devel] PLplot Debian package

On 14.07.2017 22:48, Orion Poplawski wrote: > Well, it compiles. There are longstanding test failures though: > > 5: *** PLPLOT ERROR, ABORTING OPERATION *** > 5: UTF-8 string is malformed: �M��, aborting operation Just for the records, and to keep you informed about the Debian packaging

Re: [Plplot-devel] PLplot Debian package

Hi Alan, On 18.07.2017 20:45, Alan W. Irwin wrote: > To Ole and Orion: > > Here is what I suggest you do to decide whether you want to package > the Octave bindings of PLplot until this UTF-8 error is fixed. The > octave examples that are run in our tests are controlled by >

Re: [Plplot-devel] Install location logic substantially updated

Hi Alan, On 22.07.2017 10:59, Alan W. Irwin wrote: > So the user now has complete freedom to make a mess by attempting > to specify inconsistent install location variables I am very happy with that freedom :-) Thank you for these changes. > @Orion: > > In particular, does Fedora have policy

Re: [Plplot-devel] This next release cycle should finish in early 2018

Dear Alan, On 09.09.2017 20:35, Alan W. Irwin wrote: > I did take a quick look at the above URL but saw no obvious issues. So > it appears your Debian repackaging efforts have been a complete > success for our latest version of PLplot. Congratulations on that > achievement! Yesterday, the

Re: [Plplot-devel] This next release cycle should finish in early 2018

Ole Streicher <debian-de...@liska.ath.cx> writes: [...] I forgot to attach the URL with all build logs: https://buildd.debian.org/status/package.php?p=plplot=experimental Cheers Ole -- Check out the vibran

Re: [Plplot-devel] This next release cycle should finish in early 2018

"Alan W. Irwin" writes: > I did take a quick look at the above URL but saw no obvious issues. So > it appears your Debian repackaging efforts have been a complete > success for our latest version of PLplot. Congratulations on that > achievement! Hopefully. Maybe our

Re: [Plplot-devel] This next release cycle should finish in early 2018

ld still change things, we can. Best regards, and already thank you for your help so far! Ole From: Ole Streicher <oleb...@debian.org> Date: Wed, 6 Sep 2017 20:53:52 +0200 Subject: Build bindings for all Python versions --- CMakeLists.txt | 19 ++

Re: [Plplot-devel] This next release cycle should finish in early 2018

Hi Alan, "Alan W. Irwin" writes: > The 5.13.0 release has now been completed. (See my recent post to > plplot-general for links to the details). > > I encourage all of you to test the website (I already know of one dead > external link there to Homebrew packaging of

[Plplot-devel] Qt(5) problems

Hi, on my path to get plplot compiled for Debian, I have a number of problems during the execution to the Qt tests. I first was trying to use Qt5, since Qt4 is going to be deprecated very soon in Debian [1], but I see the same problems with Qt4. Occasionally, I get now lots messages like Qt:

Re: [Plplot-devel] This next release cycle should finish in early 2018

Hi Alan, On 28.08.2017 00:13, Alan W. Irwin wrote: > On 2017-08-27 11:00+0200 Ole Streicher wrote: >> One point there however remains: I need to support all Python 3 >> versions we have in Debian; currently Python 3.5 and Python 3.6. >> The difference are just the shared

Re: [Plplot-devel] Qt(5) problems

Hi Alan, "Alan W. Irwin" writes: > Hi Ole: > > [...] > > To investigate this potential issue further, I have just now built and > tested PLplot in an environment (Linux console mode) where no X server > is running at all (although all the X headers, etc., were

[Plplot-devel] Help needed for plplot runtime tests

Hi, in the Debian package, we usually try to run CI tests regularly on each dependency change. This gives us the opportunity to early find problems with the package or one of its dependencies. However, I have some difficulties to do that; this may be connected with my limited knowledge of cmake.

Re: [Plplot-devel] Plplot now working well with Debian Buster + release timing

Hi Alan, I am very happy to read this, however I am currently stuck with a problem that I can't build the package due to a problem in octave which is still unresolved in unstable. Once this is fixed, I will upload a new package. Thank you very much for your

Re: [Plplot-devel] plplot-5.14.0 has been released

Hi Alan, "Alan W. Irwin" writes: > A comprehensive test and some additional specific tests of my fix for the > release critical bug went well, and as a result I have now released > 5.14.0. See my forthcoming post to plplot-general for the details > concerning that release. thank you very much

Re: [Plplot-devel] Help needed for plplot runtime tests

Hi Alan, "Alan W. Irwin" writes: > On 2018-11-22 20:54+0100 Ole Streicher wrote: >> "Alan W. Irwin" writes: >>> On 2018-11-13 18:23+0100 Ole Streicher wrote: >>> Upstream PLplot installs all examples configured in the core build in >>> one

Re: [Plplot-devel] Help needed for plplot runtime tests

Hi Alan, back from the US (ADASS), I found an hour to look further into the CI tests problem: "Alan W. Irwin" writes: > On 2018-11-13 18:23+0100 Ole Streicher wrote: > Upstream PLplot installs all examples configured in the core build in > one place which contains a self-co

Re: [Plplot-devel] Help needed for plplot runtime tests

Hi Alan, On 23.11.18 22:17, Alan W. Irwin wrote: > On 2018-11-23 08:28+0100 Ole Streicher wrote: >> -- Could NOT find Qt5Svg (missing: Qt5Svg_DIR) >> CMake Warning at >> /usr/lib/x86_64-linux-gnu/cmake/plplot/plplotConfig.cmake:5 >> (find_package): >>