Pleace, fix PKGBUILD. 'mv' can't move not empty folder. I replaced it with:
rsync -a "$srcdir"/fritzing-parts-${partsrev}/* "$srcdir"/fritzing-app-${pkgver}/parts
rm -rf "$srcdir"/fritzing-parts-${partsrev}
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.033216 |
First Submitted: | 2009-05-31 14:31 (UTC) |
Last Updated: | 2024-10-11 15:11 (UTC) |
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 18 Next › Last »
Pleace, fix PKGBUILD. 'mv' can't move not empty folder. I replaced it with:
rsync -a "$srcdir"/fritzing-parts-${partsrev}/* "$srcdir"/fritzing-app-${pkgver}/parts
rm -rf "$srcdir"/fritzing-parts-${partsrev}
thanks,
fritzing it's ok
lifala: Please install all packages from the base-devel group:
pacman -S --needed base-devel
This includes the patch utility. Having base-devel installed in assumed for all packages in the AUR.
hi.
i problem with prepare and patch, ligne 34, command not found
/tmp/yaourt-tmp-lifala/aur-fritzing/./PKGBUILD: ligne 34: patch : commande introuvable
thanks
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.
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.
Bevan, thanks for the speedy fix, it works fine now.
danson: Should be fixed now. Could you please retry?
==> 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?
Below comment is obsolete. Fritzing does not update the parts library anymore so the patches have been removed. See: https://github.com/fritzing/fritzing-app/issues/3454#issuecomment-878852716
/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.
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.