Package Details: pycam-git 0.7.0pre0.r297.g55e3129f-1

Git Clone URL: https://aur.archlinux.org/pycam-git.git (read-only, click to copy)
Package Base: pycam-git
Description: Toolpath generator for 3-axis CNC machining, written in Python.
Upstream URL: https://github.com/SebKuzminsky/pycam
Keywords: cam cnc toolpath
Licenses: GPL3
Conflicts: pycam
Submitter: ByteHamster
Maintainer: ByteHamster
Last Packager: ByteHamster
Votes: 1
Popularity: 0.000000
First Submitted: 2021-01-08 12:58 (UTC)
Last Updated: 2022-03-19 21:29 (UTC)

Latest Comments

1 2 Next › Last »

oxplot commented on 2022-12-18 02:21 (UTC)

Get an error on launch:

Traceback (most recent call last):
  File "/usr/share/pycam-git/pycam/run_gui.py", line 48, in <module>
    from pycam.Flow.history import DataHistory, merge_history_and_block_events
  File "/usr/share/pycam-git/pycam/Flow/history.py", line 7, in <module>
    from pycam.Flow.parser import dump_yaml, parse_yaml
  File "/usr/share/pycam-git/pycam/Flow/parser.py", line 5, in <module>
    import pycam.Plugins
  File "/usr/share/pycam-git/pycam/Plugins/__init__.py", line 79, in <module>
    class PluginBase:
  File "/usr/share/pycam-git/pycam/Plugins/__init__.py", line 86, in PluginBase
    _imports = _get_plugin_imports()
  File "/usr/share/pycam-git/pycam/Plugins/__init__.py", line 68, in _get_plugin_imports
    import OpenGL.GLUT
  File "/usr/lib/python3.10/site-packages/OpenGL/GLUT/__init__.py", line 5, in <module>
    from OpenGL.GLUT.fonts import *
  File "/usr/lib/python3.10/site-packages/OpenGL/GLUT/fonts.py", line 20, in <module>
    p = platform.getGLUTFontPointer( name )
  File "/usr/lib/python3.10/site-packages/OpenGL/platform/baseplatform.py", line 350, in getGLUTFontPointer
    raise NotImplementedError(
NotImplementedError: Platform does not define a GLUT font retrieval function

MarsSeed commented on 2022-03-23 20:49 (UTC) (edited on 2022-06-22 23:12 (UTC) by MarsSeed)

Thank you for the updates and refinements!

I appreciate your work on this fine build.

ByteHamster commented on 2022-03-19 21:30 (UTC)

I find it not really clear from the description here but you are right that the examples reset their revision number as well. Updated to your suggestion.

MarsSeed commented on 2022-03-19 21:21 (UTC)

It should be monotonically increasing since the last tag, not since the beginning commit. :)

ByteHamster commented on 2022-03-19 21:18 (UTC)

But what is this r2196? It should be r297.

The guidelines say that the reference number should be monotonically increasing and unique. The number you suggested resets to zero whenever a new release is tagged.

MarsSeed commented on 2022-03-19 21:15 (UTC) (edited on 2022-03-19 21:17 (UTC) by MarsSeed)

There is a good reason why I created my suggested pkgver() code the way I did: to properly align with Arch and Pacman versioning guidelines, and to make sure it is future-compatible with prospective release tags. :) Why did you reject my proposed code?

MarsSeed commented on 2022-03-19 21:12 (UTC) (edited on 2022-03-19 21:15 (UTC) by MarsSeed)

Hey,

Thanks for the update.

But what is this r2196? It should be r297.

Also, it shouldn't be 0.7.0.pre0 because that is a higher version than the prospective 0.7.0. The pre0 tag is a pre-release one, not a finalized release tag.

For Pacman, 0.7.0pre0 < 0.7.0 < 0.7.0.pre0.

MarsSeed commented on 2022-02-28 22:29 (UTC) (edited on 2022-03-10 17:22 (UTC) by MarsSeed)

Please kindly modernize the pkgver() in PKGBUILD. :)

You can create more meaningful version numbers with my suggested code below.

E.g. this should be the version as of now: 0.7.0pre0.r297.g55e3129f.

(Code adapted from Arch wiki guidelines).

pkgver() {
  cd pycam

  # Generate git tag based version. Use only tags created on current branch (--first-parent).
  git describe --long --tags --first-parent | sed 's/^v//;s/^\([0-9][0-9.]*\)-\([a-zA-Z]\+\)/\1\2/;s/\([0-9]\+-g\)/r\1/;s/-/./g'
}

Then run these commands in the directory containing the PKGBUILD to refresh the pkgver field:

makepkg --nodeps --nobuild
makepkg --printsrcinfo > .SRCINFO

MarsSeed commented on 2022-02-28 21:43 (UTC) (edited on 2022-03-10 17:06 (UTC) by MarsSeed)

Just tried this package, and it builds and runs correctly for me.

jalovisko commented on 2021-06-04 02:54 (UTC)

@ByteHamster, interestingly, this installation failed because of the following error. Maybe that is the root cause for me.

ImportError: /tmp/pip-build-env-z6f9xzvk/overlay/lib/python3.8/site-packages/cairo/_cairo.cpython-38-x86_64-linux-gnu.so: undefined symbol: cairo_svg_surface_set_document_unit
  ----------------------------------------
  ERROR: Failed building wheel for PyGObject
Failed to build PyGObject
ERROR: Could not build wheels for PyGObject which use PEP 517 and cannot be installed directly