I've just installed the package and when I run and try, from menu, to check update a popup window say me that I have to enable write permission on folder: /usr/share/fritzing/parts
Can you suggest me there is a way to make this works?
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 .. 4 5 6 7 8 9 10 11 12 13 14 .. 18 Next › Last »
bfg commented on 2017-09-24 05:52 (UTC)
Bevan commented on 2017-09-13 12:56 (UTC)
I have seen this multiple times that release tarballs from github change their checksum. Seems to be the case here, as well. I currently get the following for 0.9.3b.tar.gz: 2475a95aad2c1536eef3fdb72665c5c16590644b45bd110a0cde223c916625b8
I will update the PKGBUILD later today.
Franek commented on 2017-09-13 12:20 (UTC)
The main tarball failed its checksum for me. Is anyone else getting this? Weird, was the 0.9.3b release changed without changing the release number?
This is the sha256sum I get for 0.9.3b.tar.gz:
2475a95aad2c1536eef3fdb72665c5c16590644b45bd110a0cde223c916625b8
Bevan commented on 2017-05-16 19:14 (UTC)
This package needs to be rebuilt after the latest libgit2 update.
Bevan commented on 2017-04-16 17:33 (UTC)
@peste88: Well, that is an upstream decision. We would have to explicitly change this in this package, but I tend to stick to upstream as close as possible.
peste88 commented on 2017-04-16 14:22 (UTC)
Hello, I was wondering...
Why does it has to be an upper case letter to call that Fritzing thing.
Bevan commented on 2017-04-09 06:55 (UTC)
@ctag: Please see my comment from 2017-02-20 20:49 and follow the steps there.
ctag commented on 2017-04-08 22:59 (UTC)
Received this error while building:
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
Despite libgit2 being an installed dependency.
ArsenArsen commented on 2017-03-20 12:45 (UTC)
Hello, I was wondering was it just me that gets
==> Extracting sources...
-> Extracting 0.9.3b.tar.gz with bsdtar
-> Extracting 667a5360e53e8951e5ca6c952ae928f7077a9d5e.tar.gz with bsdtar
==> Starting prepare()...
mkdir: cannot create directory ‘/home/arsen/.cache/pacaur/fritzing/src/fritzing-app-0.9.3b/parts’: File exists
==> ERROR: A failure occurred in prepare().
Aborting...
:: failed to build fritzing package(s)
Could you change `mkdir' to `mkdir -p'? Thanks.
Bevan commented on 2017-02-20 20:49 (UTC)
@MindlessMutagen: What seems to be going on here is that pkg-config does not see your installed libgit2. Please try the following two things:
1. Run "pkg-config --print-variables libgit2". It should output
includedir
libdir
pcfiledir
prefix
If it claims that libgit2 was not found you need to figure out why.
2. Remove the src directory before building. I noticed the line "WARNING: Using existing $srcdir/ tree" in your output. This can actually cause issues.
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.