@MindlessMutagen: Thanks for the report. I will have a look into this. Unfortunately I won't have the opportunity to do so before Monday.
Search Criteria
Package Details: fritzing 1.0.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/fritzing.git (read-only, click to copy) |
---|---|
Package Base: | fritzing |
Description: | PCB layout prototyping application |
Upstream URL: | http://fritzing.org |
Licenses: | GPL3 |
Submitter: | phects |
Maintainer: | Bevan |
Last Packager: | Bevan |
Votes: | 243 |
Popularity: | 0.018376 |
First Submitted: | 2009-05-31 14:31 (UTC) |
Last Updated: | 2024-10-11 15:11 (UTC) |
Dependencies (9)
- libgit2 (libgit2-gitAUR)
- ngspice (ngspice-gitAUR)
- polyclippingAUR
- qt6-serialport
- qt6-svg
- quazip-qt6
- boost (boost-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- qt6-tools (make)
Required by (0)
Sources (6)
- 0001-Quick-Dirty-patch-to-allow-finding-quazip-qt6-on-Arc.patch
- 0002-Quick-Dirty-patch-to-allow-finding-ngspice-on-Arch-L.patch
- 0003-Quick-Dirty-patch-to-allow-finding-Clipper1-on-Arch-.patch
- git+https://github.com/fritzing/fritzing-app.git#commit=a8c6ef7cf66f7a42b9b233d6137f1b70a9573a25
- git+https://github.com/fritzing/fritzing-parts.git#commit=76235099ed556e52003de63522fdd74e61d53a36
- svgpp-1.3.1.tar.gz
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 18 Next › Last »
Bevan commented on 2017-02-17 20:45 (UTC)
MindlessMutagen commented on 2017-02-17 20:30 (UTC)
@Bevan I am having issues with libgit2
MindlessMutagen commented on 2017-02-17 18:44 (UTC)
I am not albe to build the package and the issue is related to libgit2. I have tried building with both libgit2 and libgit2-git installed.
This is all of the terminal output when building with pacaur:
:: Proceed with installation? [Y/n]
:: Retrieving package(s)...
:: fritzing build files are up-to-date -- skipping
:: Checking fritzing integrity...
==> Making package: fritzing 0.9.3b-3 (Fri Feb 17 12:37:12 CST 2017)
==> Retrieving sources...
-> Found 0.9.3b.tar.gz
-> Found 667a5360e53e8951e5ca6c952ae928f7077a9d5e.tar.gz
-> Found 0001-Squashed-commit-of-the-following.patch
-> Found fritzing.xml
==> Validating source files with sha256sums...
0.9.3b.tar.gz ... Passed
667a5360e53e8951e5ca6c952ae928f7077a9d5e.tar.gz ... Passed
0001-Squashed-commit-of-the-following.patch ... Passed
fritzing.xml ... Passed
:: Building fritzing package(s)...
==> Making package: fritzing 0.9.3b-3 (Fri Feb 17 12:37:14 CST 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Project MESSAGE: Fritzing requires libgit2
Project MESSAGE: Build it from the repo at https://github.com/libgit2
Project MESSAGE: See https://github.com/fritzing/fritzing-app/wiki for details.
Project ERROR: libgit2 include path not found in ../libgit2/include
==> ERROR: A failure occurred in build().
Aborting...
:: failed to build fritzing package(s)
perost commented on 2016-09-24 11:18 (UTC)
@Bevan: Sorry for the late reply, I didn't get a notification about your message for some reason. But the new package release seems to work just fine for me at least.
Bevan commented on 2016-09-16 17:16 (UTC)
@perost: Thanks a lot for tracking this down! Instead of just changing the patch I would like to test a more general solution to what the patch is trying to fix:
https://github.com/fritzing/fritzing-app/pull/3238
Could you please test the new package release (-3) if it solves the problem?
perost commented on 2016-09-15 18:27 (UTC) (edited on 2016-09-15 18:29 (UTC) by perost)
This package has a pretty annoying bug where all the bins in /usr/share/fritzing/parts/bins/more are duplicated each time Fritzing is started, leading to the bin manager filling up more and more. The issue is caused by 0003-Provide-a-sane-default-for-parts-path.patch, which introduces the line:
FolderUtils::setAppPartsPath("/usr/share/fritzing/parts/");
to fapplication.cpp. This path is then used in binmanager.cpp:81 where it's concatenated with "/more" and used to determine the type of location of a bin. The path then becomes "/usr/share/fritzing/parts/bins//more", and the // causes the string comparison to fail against actual system paths.
The fix is to simply remove the last / in the path:
FolderUtils::setAppPartsPath("/usr/share/fritzing/parts");
Bevan commented on 2016-07-04 18:51 (UTC)
@kierdavis: I cannot reproduce this issue. Is you system fully up to date? Please double check running pacman -Syu. (The update I just pushed is not related to your issue.)
kierdavis commented on 2016-07-04 13:45 (UTC)
I'm getting a linker error when building this package (version 0.9.3b-1):
/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libQt5SerialPort.so: undefined reference to `qt_version_tag@Qt_5.7'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libQt5SerialPort.so: undefined reference to `qt_safe_poll(pollfd*, unsigned long, timespec const*)@Qt_5'
(full log at https://gist.github.com/kierdavis/8ee38a58c81353e32f9e069a00f2efe1)
At first glance it doesn't look like it's caused by the libgit2/boost-libs problem @Bevan mentioned recently, but I could quite likely be wrong.
Bevan commented on 2016-06-10 18:35 (UTC)
Feel free to build one :)
<deleted-account> commented on 2016-06-10 18:29 (UTC)
Maybe a fritzing-bin would be ok in the meantime. I'm using a precompiler version and works reasonably well.
Pinned Comments
Bevan commented on 2023-09-25 08:41 (UTC) (edited on 2023-11-02 19:48 (UTC) by Bevan)
Please do not flag this package out of date unless there is source code available for a newer version than represented here. Unfortunately, upstream is very reluctant in releasing their GPL3 licensed code to the public.
See:
https://github.com/fritzing/fritzing-app/issues/3876
https://github.com/fritzing/fritzing-app/issues/3881
https://forum.fritzing.org/t/can-t-find-source-code/19723
https://github.com/fritzing/fritzing-app/issues/4070
Bevan commented on 2022-04-02 08:37 (UTC)
ericfont: No need to downgrade libgit2. You just need to rebuild Fritzing after the libgit2 update. This happens regularly.