Package Details: fritzing 0.9.6-1

Git Clone URL: (read-only, click to copy)
Package Base: fritzing
Description: PCB layout prototyping application
Upstream URL:
Licenses: GPL3
Submitter: phects
Maintainer: Bevan
Last Packager: Bevan
Votes: 226
Popularity: 2.12
First Submitted: 2009-05-31 14:31
Last Updated: 2021-03-27 11:46

Pinned Comments

Bevan commented on 2017-09-24 08:07

/usr/share/fritzing/parts contains the parts db which is provided by the package, which should not be updated by the user. Instead, the user can run the command "fritzing_clone_parts" once which clones the parts db into the user's home (located under ~/.local/share/fritzing). On next start, Fritzing will use this parts db instead of the one under /usr/share. From now on updating the db should work.

This is somehow a workaround to provide both a package that works out-of-the-box and the self-update functionality of Fritzing. See for a discussion on this. This package basically applies the changes of the pull-request to implement this functionality.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

flolilo commented on 2021-03-27 00:57

For 0.9.6 (currently, there is no CD-xxx version number), you have to change the following things in PKGBUILD (only relevant lines mentioned):

# patch -p1 < "${srcdir}"/472951243d70eeb40a53b1f7e16e6eab0588d079.patch

(in fact, you can delete every mention of 472951[...].patch).

txtsd commented on 2020-11-24 13:48

I've already run fritzing_clone_parts. Here's what happens when I try to regenerate the parts database:

Visually, the loading bar gets stuck about 2/5ths of the way, then the program just crashes.

TheSaint commented on 2020-11-06 04:18


Fritzing builds fine against the current version of libgit2.

Rebuilding has corrected the flaw. Sorry if I didn't remember that trial, I was trying to reinstall libgit2, without thinking to rebuild the entire package. Thanks

Bevan commented on 2020-11-05 13:26

@TheSaint: Have you tried rebuilding the Fritzing package? Often this is sufficient to fix these kind of issues. I will try myself later today.

Edit: I confirmed that rebuilding the package fixes this issue. Fritzing builds fine against the current version of libgit2.

TheSaint commented on 2020-11-05 11:48

Fritzing: error while loading shared libraries: cannot open shared object file: No such file or directory

It seems that libgit2 got an upgrade

ls -l /usr/lib/libgit2*
lrwxrwxrwx 1 root root      14 15 ott 22.39 /usr/lib/ ->
lrwxrwxrwx 1 root root      16 15 ott 22.39 /usr/lib/ ->
-rwxr-xr-x 1 root root 1146864 15 ott 22.39 /usr/lib/

Bevan commented on 2020-05-13 12:04

All packages in the base-devel group are expected to be installed when using the AUR. They must not be included in the list of dependencies.


Lasse_Ristig commented on 2020-05-13 12:03

pkg-config was not installed and now fritzing is compiling. Thank you! In my opinion pkg-config must be included in the dependencies. It seems only be needed during compiling, so if not oncluded as dependency it would be useful to check to give a hint to install it temporary.

Bevan commented on 2020-05-13 11:43

Can you please check the output of the following command?

pkg-config --path libgit2

If this command is not installed on your machine this would explain the behavior. In that case please install all packages in base-devel.

Lasse_Ristig commented on 2020-05-13 11:14

The problem with this error notification persists:

Project ERROR: libgit2 include path not found in /fritzing/src/fritzing-app-CD-498/../libgit2/include

I tested to compile with: - git clone ... makepkg - trizen -S fritzing

Bevan commented on 2020-05-02 16:05

@guitsi: That is a different issue. I can reproduce it by removing/commenting the following line in the PKGBUILD:

sed -i 's/LIBGIT_STATIC = true/LIBGIT_STATIC = false/'

Did you by accident do that? Apart from that I see that you build in a chroot. Can you briefly describe how you build this package?