Package Details: fritzing 0.9.3b-4

Git Clone URL: https://aur.archlinux.org/fritzing.git (read-only)
Package Base: fritzing
Description: PCB layout prototyping application
Upstream URL: http://fritzing.org
Licenses: GPL3
Submitter: phects
Maintainer: Bevan
Last Packager: Bevan
Votes: 194
Popularity: 1.085451
First Submitted: 2009-05-31 14:31
Last Updated: 2018-04-07 19:29

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 https://github.com/fritzing/fritzing-app/pull/3238 for a discussion on this. This package basically applies the changes of the pull-request to implement this functionality.

Latest Comments

Bevan commented on 2018-04-09 22:16

salvatoreG: That's weird. For me the checksums are still identical. Could you delete parts-667a5360e53e8951e5ca6c952ae928f7077a9d5e.tar.gz and try again? If it still does not work, please check if it is a text file instead of the expected tar-gz and if so what the content is.

salvatoreG commented on 2018-04-09 09:22

I guess upstream package was updated because it doesn't match the expected checksum

==> Building and installing package ==> Making package: fritzing 0.9.3b-4 (lun. avril 9 11:18:00 CEST 2018) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found 0.9.3b.tar.gz -> Found parts-667a5360e53e8951e5ca6c952ae928f7077a9d5e.tar.gz -> Found 0001-Squashed-commit-of-the-following.patch -> Found fritzing.desktop.patch -> Found fritzing.xml ==> Validating source files with sha256sums... 0.9.3b.tar.gz ... FAILED parts-667a5360e53e8951e5ca6c952ae928f7077a9d5e.tar.gz ... Passed 0001-Squashed-commit-of-the-following.patch ... Passed fritzing.desktop.patch ... Passed fritzing.xml ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build fritzing.

danson commented on 2018-04-07 21:37

Bevan, thanks for the speedy fix, it works fine now.

Bevan commented on 2018-04-07 19:30

danson: Should be fixed now. Could you please retry?

danson commented on 2018-04-07 19:19

==> ERROR: Failure while downloading https://github.com/fritzing/fritzing-parts/archive/667a5360e53e8951e5ca6c952ae928f7077a9d5e.tar.gz

/archive doesn't exist. Any idea where to get the parts?

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 https://github.com/fritzing/fritzing-app/pull/3238 for a discussion on this. This package basically applies the changes of the pull-request to implement this functionality.

Bfg commented on 2017-09-24 05:52

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?

Bevan commented on 2017-09-13 12:56

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

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

This package needs to be rebuilt after the latest libgit2 update.

All comments