Arch Linux User Repository

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

ericfont: No need to downgrade libgit2. You just need to rebuild Fritzing after the libgit2 update. This happens regularly.

Thank you for being so quick to update! It's a great help and is greatly appreciated.

When opening old *.fzz, the program began to crash, I can’t figure out how to fix it:

Fritzing
kf.kio.gui: Cannot read information about filesystem under path "/home/test/.cache/thumbnails/"
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
kf.kio.gui: Cannot read information about filesystem under path "/home/test/.cache/thumbnails/"
Segmentation fault (core dumped)

in fritzing-1.0.0-1 there is no such problem

Unfortunately, version 1.0.2 crashes when opening some files. Is this a common problem?

@Bevan Thanks, it works!

khvalera: Thanks! This is fixed now in 1.0.2-2.

Translations into other languages have disappeared from the catalog: translations

@Bevan: Thanks for the info. I do not know much of anything regarding the inner-workings of this but it seems that one of two things should be true...

1. After an install completes, it cleans up after itself (or pamac does this automatically).
2. Before an install starts it cleans up in case a previous build/install failed (or pamac does this automatically).

Based on what you said, it sounds like my assumptions are incorrect!

@joshm: Caching old copies of $srcdir is one of the unexpected things some AUR helpers do. To fix this issue between version updates, we could rename the extracted directories so that they contain the version number. But the problem will still occur on pkgrel bumps or manual rebuilds of the same version. So I guess the best we can do is to explicitly remove any leftover build directory before compilation...

Updating this package is giving me the following error:

==> Sources are ready.
:: Building fritzing package(s)...
==> Making package: fritzing 1.0.1-1 (Tue 07 Nov 2023 06:02:48 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
mkdir: cannot create directory ‘build’: File exists
***Cannot detect .pro file in directory '..'.

QMake expects the file '../...pro' or exactly one .pro file in the given directory.

After rm -rf ~/.cache/pacaur/fritzing and then installing again, it worked.

The commits for 1.0.1 are available on Github:

--- PKGBUILD    2023-11-03 21:09:03.009977018 +0100
+++ PKGBUILD-1.0.1  2023-11-03 21:08:58.369949848 +0100
@@ -10,7 +10,7 @@
 # We drop the "b" at the end of the version number. It probably means beta
 # while there is also "d" for development versions. This would not be correctly
 # parsed by `pkgver` anyway (d > b), so let's leave out the b suffix entirely.
-pkgver=1.0.0
+pkgver=1.0.1
 pkgrel=1

 # Tag version can be obtained from github release page. Sometimes this is the
@@ -20,7 +20,7 @@
 #_tagver=0.9.8

 # This is probably closest to what has been released as 1.0.0.
-_gitrev=fe6d2f9c8b58d981a0e119ca251da54dc5959c24
+_gitrev=8f5f1373835050ce014299c78d91c24beea9b633

 # Parts come from a different respository and are not versioned anymore since
 # 2016. Sometimes we can get the revision by downloading the release build,
@@ -28,7 +28,7 @@
 # release build seems to be hidden behind a paywall. Then we need to guess
 # based on the master branch of the fritzing-parts repository and the date when
 # the release archive was created.
-_partsrev=9597553a1adc09019b4a42fe7929196abff18133
+_partsrev=f82a5a0eef56bc6ca24c4b25868a27e7da477b89

 pkgdesc='PCB layout prototyping application'
 arch=('aarch64' 'i686' 'x86_64')

Unfortunately when just exchanging the commit hashes and bumping the version I get:

$ makepkg -cC
==> Making package: fritzing 1.0.1-1 (Fri Nov  3 21:14:49 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating fritzing-app git repo...
  -> Updating fritzing-parts git repo...
  -> Found 0001-Quick-Dirty-patch-to-allow-finding-quazip-qt5-on-Arc.patch
==> Validating source files with sha256sums...
    fritzing-app ... Skipped
    fritzing-parts ... Skipped
    0001-Quick-Dirty-patch-to-allow-finding-quazip-qt5-on-Arc.patch ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of fritzing-app git repo...
Cloning into 'fritzing-app'...
done.
Switched to a new branch 'makepkg'
  -> Creating working copy of fritzing-parts git repo...
Cloning into 'fritzing-parts'...
done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
patching file pri/quazipdetect.pri
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Info: creating stash file /home/uwe/AUR/fritzing/src/fritzing-app/build/.qmake.stash
Info: creating cache file /home/uwe/AUR/fritzing/src/fritzing-app/build/.qmake.cache
Project WARNING: Using dynamic linking for libgit2.
Project MESSAGE: Using fritzing boost detect script.
Checking for boost... yes
Project MESSAGE: using installed Boost library
Project MESSAGE: Using fritzing ngspice detect script.
Project ERROR: ngspice not found in /home/uwe/AUR/fritzing/src/ngspice-40
==> ERROR: A failure occurred in build().
    Aborting...

$ pacman -Qs ngspice
local/ngspice 41-1
    Mixed-level/Mixed-signal circuit simulator based on Spice3f5, Ciber1b1, and Xspice