Package Details: fritzing 0.9.3b-3

Git Clone URL: (read-only)
Package Base: fritzing
Description: PCB layout prototyping application
Upstream URL:
Licenses: GPL3
Submitter: phects
Maintainer: Bevan
Last Packager: Bevan
Votes: 172
Popularity: 2.406365
First Submitted: 2009-05-31 14:31
Last Updated: 2016-09-16 17:16

Latest Comments

ArsenArsen commented on 2017-03-20 12:45

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().
:: failed to build fritzing package(s)

Could you change `mkdir' to `mkdir -p'? Thanks.

Bevan commented on 2017-02-20 20:49

@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
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.

Bevan commented on 2017-02-17 20:45

@MindlessMutagen: Thanks for the report. I will have a look into this. Unfortunately I won't have the opportunity to do so before Monday.

MindlessMutagen commented on 2017-02-17 20:30

@Bevan I am having issues with libgit2

MindlessMutagen commented on 2017-02-17 18:44

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
Project MESSAGE: See for details.
Project ERROR: libgit2 include path not found in ../libgit2/include
==> ERROR: A failure occurred in build().
:: failed to build fritzing package(s)

perost commented on 2016-09-24 11:18

@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

@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:

Could you please test the new package release (-3) if it solves the problem?

perost commented on 2016-09-15 18:27

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:


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:


Bevan commented on 2016-07-04 18:51

@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

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/ undefined reference to `qt_version_tag@Qt_5.7'
/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/ undefined reference to `qt_safe_poll(pollfd*, unsigned long, timespec const*)@Qt_5'

(full log at

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.

All comments