Search Criteria
Package Base Details: sozi
Package Actions
Git Clone URL: | https://aur.archlinux.org/sozi.git (read-only, click to copy) |
---|---|
Submitter: | linkmauve |
Maintainer: | sbmomeni |
Last Packager: | sbmomeni |
Votes: | 74 |
Popularity: | 0.006641 |
First Submitted: | 2010-10-28 11:53 (UTC) |
Last Updated: | 2022-03-31 16:05 (UTC) |
Latest Comments
zeroconf commented on 2022-03-28 20:00 (UTC)
New, fixed version of Sozi has been published on 25th March 2022 - https://github.com/sozi-projects/Sozi/releases
zeroconf commented on 2022-02-25 21:05 (UTC)
Yes, this parameter works - thank you! Sounds like Chromium CLI parameter https://peter.sh/experiments/chromium-command-line-switches/
Just wondering, why such issue appeared and how this GPU sandbox disabling affects sozi work - https://www.electronjs.org/docs/latest/tutorial/sandbox/
sbmomeni commented on 2022-02-24 12:47 (UTC)
@zeroconf Yes, this package compiles sozi sources with Electron v9.4.4 (bundled as a single binary executable).
I'll update this package when upstream settles on a non-beta release. By the way, the https://github.com/sozi-projects/Sozi/commit/8c32c2214dce4f07398497143b07ccf0334fb310 shows that the current "beta" fix is to disable the GPU sandbox. You can achieve/test the same effect with v21.12.06 using the same command line option:
sozi --disable-gpu-sandbox
zeroconf commented on 2022-02-22 22:00 (UTC) (edited on 2022-02-22 22:26 (UTC) by zeroconf)
Sozi developer says, that Sozi uses Electron and it comes as bundled with Sozi. Does Sozi in AUR have also bundled version of electron? If not, then this may the issue. There in discussion at https://github.com/sozi-projects/Sozi/issues/603#issuecomment-1048182509 is also listed electron versions used by Sozi versions.
zeroconf commented on 2022-02-21 18:05 (UTC)
Sounds like last issue is Sozi bug - https://github.com/sozi-projects/Sozi/issues/603
zeroconf commented on 2022-02-20 16:52 (UTC)
Hopefully works newer version better - https://github.com/sozi-projects/Sozi/releases
zeroconf commented on 2022-02-20 16:51 (UTC)
Currently cannot start Sozi 21.12.06-1.
If to start from CLI, then:
Running it via gdb for debugging purposes:
sbmomeni commented on 2021-12-24 18:07 (UTC)
@cmonty14 This error means that some of the source files were not downloaded correctly. You can find the offending file by this command:
Remove the invalid files and retry.
cmonty14 commented on 2021-12-13 07:54 (UTC)
Build error...
sbmomeni commented on 2021-10-27 07:04 (UTC)
@zeroconf It should be fixed now.
zeroconf commented on 2021-10-18 14:17 (UTC)
I got error messages: error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'python2-lxml' required by sozi-extras_texts2paths -> exit status 1
medmedin commented on 2021-07-15 12:26 (UTC)
@sbmomeni, that was fast and excellent work, it's installed without problems, thanks really for making it easy to install this needed app :)
sbmomeni commented on 2021-07-15 09:51 (UTC)
Here you are @medmedin https://aur.archlinux.org/packages/sozi-bin/
medmedin commented on 2021-06-22 09:53 (UTC)
@sbmomeni, now, most arch packages are based on binary releases and don't require any compilation, the compilation is just waste of time and space, it's insane to wait 30min for sozi to finish installing ! This app has already deb and generic linux installers for both 32bits and 64bits so compiling it is not required anymore, it would be great to provide sozi-bin that downloads the installer so it becomes easy and fast. Concerning the dependency with Electron runtime, from version 18.01 the provided generic installer already embeds the runtime so it doesn't need any external Electron runtime or libraries.
sbmomeni commented on 2021-06-22 05:07 (UTC)
@medmedin Binary AUR packages (those packages which have the -bin suffix) download and repackage already built binaries (e.g., converting a .deb file to .pkg). However, this package is source-based, that is, it compiles the binary files on the machine which runs the makepkg command with no network access (after downloading the sources files).
About three years ago our installation script was merged in the upstream repo allowing a -bin package to be built, but it will not necessarily keep working on ArchLinux due to continuous updates (e.g., sometime we had to use a different electron version to keep Sozi working).
medmedin commented on 2021-06-21 20:59 (UTC) (edited on 2021-06-21 21:01 (UTC) by medmedin)
@sbmomeni The installation is slow and takes really long times due to compilation and dependencies building, Pamac gives a log with more than 10000 lines to finish the install process https://drive.google.com/file/d/13KUk-ShUu4D02zAsAG69oMQZRiMex8dp/view?usp=sharing Why do we need to compile this app while the generic installer for Linux is already available ? https://sozi.baierouge.fr/pages/20-install.html#installing-for-gnulinux
sbmomeni commented on 2021-04-30 11:21 (UTC)
@christianlupus The current sha1sum value of the SHASUMS256.txt file is 5e42a721dbdb5304b4f186a9278987d41f411f95 and package builds normally
What error message are you getting there? Also try removing the SHASUMS256.txt file in order to force a fresh download.
christianlupus commented on 2021-04-28 17:51 (UTC)
The file SHASUMS256.txt currently causes trouble with the checksums. Can you please correct this?
sbmomeni commented on 2020-09-17 15:48 (UTC)
@osc what is the issue? It builds here normally.
osc commented on 2020-08-26 15:03 (UTC)
Hi there seems to be an issue and the package is not building.
sbmomeni commented on 2020-07-04 05:30 (UTC)
@indodwi The error 416 indicates an unsatisfiable resumption range. So, find and empty your package build cache folder to abandon the corrupted file. If not fixed, test that URL in a browser to ensure that you can download it normally.
indodwi commented on 2020-07-03 23:14 (UTC)
Excuse me. I have a problem when installing sozi in manjaro When i build sozi from add/remove software gui suddenly stoped and this information:
camecurl: (22) The requested URL returned error: 416 ==> ERROR: Failure while downloading https://registry.npmjs.org/@babel%2Fplugin-proposal-object-rest-spread/-/plugin-proposal-object-rest-spread-7.10.1.tgz 2 Aborting... Failed to build sozi.
could you help me? Thanks before
Reido commented on 2020-06-18 08:11 (UTC)
I got an error because I don't have the zip package installed. You might want to add it in the build dependencies.
BrunoSpy commented on 2020-06-03 08:23 (UTC)
Thx ! FYI I was using nodejs-lts maybe changing dependencies ?
sbmomeni commented on 2020-06-01 05:51 (UTC) (edited on 2020-06-01 05:53 (UTC) by sbmomeni)
@aurmyster @BrunoSpy
aurmyster commented on 2020-05-29 03:45 (UTC)
I have the exact same problem........ Any solutions yet?
BrunoSpy commented on 2020-05-28 15:00 (UTC)
Unable to build latest update :
Loading "Gruntfile.js" tasks...ERROR
Running tasks: electron-build Warning: Task "electron-build" not found. Use --force to continue.
2000 commented on 2019-09-01 17:25 (UTC) (edited on 2019-09-02 20:04 (UTC) by 2000)
EDIT: Never mind; stupid error on my side. Upgraded system and sozi built just fine after that, Please excuse!
I have problems with the last update of sozi (with babel-core-6.26.3):
[...] node: symbol lookup error: node: undefined symbol: uv_os_free_environ
Installing babel-core- ...
bsdtar: Error opening archive: Failed to open '[...]/TEMPCOMPILE/sozi/src/babel-core-.tgz'
==> ERROR: A failure occurred in build().
sbmomeni commented on 2019-08-14 17:44 (UTC)
@fran5ois Fixed. Retest. The updated ttf-droid package has moved files to /usr/share/fonts/droid/ folder.
fran5ois commented on 2019-08-14 16:31 (UTC)
Hi here,
I cannot install sozi on Manjaro KDE.
here is the message I get:
patching file package.json install: cannot stat '/usr/share/fonts/TTF/DroidSans.ttf': No such file or directory == ERROR: A failure occured in prepare(). Aborting... :: Unable to build sozi - makepkg exited with code: 4
Thank you in advance for your help!
caos21 commented on 2019-05-31 03:55 (UTC)
Sozi takes 1.4Gb installed size. Only texlive-fontsextra has 1Gb in my box. Is this ok?
sbmomeni commented on 2019-04-26 08:17 (UTC)
Building version 19.04 needs about 10GB temp space.
sbmomeni commented on 2018-10-27 16:48 (UTC)
@Ray Updated.
Ray commented on 2018-10-27 05:58 (UTC)
I was not able to install SOZI. I received the errors:
error: target not found: nodejs-grunt-cli ==> ERROR: 'pacman' failed to install missing dependencies. :: Unable to build sozi - makepkg exited with code: 8
Is there a way to update this build recipe? I've tried installing SOZI from Sozi-18.04-1523042682-linux-x64.tzg but was unable to get to run.
rplanchuelo commented on 2018-06-13 22:00 (UTC)
@sbmomeni It's OK now. Thanks a lot
sbmomeni commented on 2018-06-13 19:14 (UTC)
@rplanchuelo It should be fixed now.
rplanchuelo commented on 2018-06-13 16:59 (UTC)
I have problems with the last update of sozi (with babel-core-6.26.0):
Installing babel-core-6.26.0 ... bsdtar: Error opening archive: Failed to open '/tmp/yaourt-tmp-rober/aur-sozi/src/babel-core-6.26.0.tgz' ==> ERROR: Se produjo un fallo en build(). Cancelando... ==> ERROR: Makepkg no ha podido compilar sozi.
a1rolo commented on 2018-03-14 19:18 (UTC)
@sbmomeni Great, it worked for me, thanks.
sbmomeni commented on 2018-03-09 16:52 (UTC)
@nibor @a1rolo Updated. Please test again.
nibor commented on 2018-03-07 14:17 (UTC)
First I had the same problem lylambda (tmp: not enough space on device), which can't be true as my tmp is set to 6.5 GB and still had 6.3 GB free space in the moment of (repeatable) error. Anyways, changing the build path in /etc/yaourtrc to /home/"user"/tmp helped to solve it.
But now I am getting the same error as a1rolo and don't have a solution yet:
Any ideas?
a1rolo commented on 2018-02-26 16:40 (UTC)
Please help, I get this error compiling:
Running tasks: electron-build Warning: Task "electron-build" not found. Use --force to continue.
Aborted due to warnings. ==> ERROR: Se produjo un fallo en build().
lylambda commented on 2018-02-19 20:56 (UTC)
After change the build path and a reboot, that's works. Thanks sbmomeni !
sbmomeni commented on 2018-02-14 16:30 (UTC)
@lylambda The error message is saying "Aucun espace disponible sur le périphérique" which means "No available space on the device." You should either free some space on that device or change the build path to another device.
lylambda commented on 2018-02-12 18:50 (UTC) (edited on 2018-02-12 18:53 (UTC) by lylambda)
Thanks for your response sbmomeni.
I test your command : [lylambda@nobody ~]$ semver -r "^6.14.0" "6.24.1" "5.4.2" node: error while loading shared libraries: libicui18n.so.57: cannot open shared object file: No such file or directory
So I install icu.57 with aur (my system have icu.60). Then : [lylambda@nobody ~]$ semver -r "^6.14.0" "6.24.1" "5.4.2" 6.24.1
Great ! I try to install sozy and : ==> Lancement de build()... Installing babel-preset-es2015-6.24.1 ... dep babel-preset-es2015-6.24.1 -> babel-plugin-check-es2015-constants-6.22.0 ... [...] cp: impossible de créer le lien direct 'node_modules/babel-plugin-transform-es2015-modules-umd/.is-completely-installed' vers '/tmp/pamac-build-lylambda/sozi/src/build/babel-plugin-transform-es2015-modules-umd-6.24.1/.is-completely-installed': Aucun espace disponible sur le périphérique ==> ERREUR : Une erreur s’est produite dans build(). Abandon...
More here : https://framabin.org/?5e3f4f461e58c84d#fE26l/s62+blz4XtgAwfnGwMjQhgM1uaGpQFt/bLFEE=
That's not the same error than before but... can you help me ?
sbmomeni commented on 2018-02-11 19:23 (UTC) (edited on 2018-02-11 19:26 (UTC) by sbmomeni)
@lylambda The "semver" program is used for detecting package versions. In ArchLinux, "semver" depends on "nodejs" which depends on "icu" which provides the "libicui18n.so" file which is missing in your system. Search for "/usr/lib/libicui18n.so" file and install the package which provides it in Manjaro OS.
You can test your system by running
semver -r "^6.14.0" "6.24.1" "5.4.2"
which should output
6.24.1
lylambda commented on 2018-02-11 11:51 (UTC)
[...] node: error while loading shared libraries: libicui18n.so.57: cannot open shared object file: No such file or directory Installing babel-preset-es2015- ... bsdtar: Error opening archive: Failed to open '/tmp/pamac-build-lylambda/sozi/src/babel-preset-es2015-.tgz' ==> ERREUR : Une erreur s’est produite dans build(). Abandon...
<hr>Something didn't works for me :( (OS = Manjaro) What can I do ?
rplanchuelo commented on 2018-02-10 14:51 (UTC)
@sbmomeni: It's OK. Thanks.
sbmomeni commented on 2018-02-10 12:03 (UTC)
@rplanchuelo: fixed.
rplanchuelo commented on 2018-02-10 11:33 (UTC)
Maybe it isn't neccesary. From https://www.npmjs.com/package/acorn5-object-spread:
acorn5-object-spread Spread and rest properties support in acorn 5
NPM version
Since spread and rest properties are part of ECMAScript 2018, acorn now supports them out of the box. Just make sure that you use acorn >= 5.4.1 and set ecmaVersion >= 9. This plugin is deprecated.
rplanchuelo commented on 2018-02-10 11:29 (UTC)
I cann't update because there is a error with acorn5-object-spread-5.0.1.tgz:
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 Warning: Transient problem: HTTP error Will retry in 3 seconds. 3 retries Warning: left. 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 Warning: Transient problem: HTTP error Will retry in 3 seconds. 2 retries Warning: left. 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 Warning: Transient problem: HTTP error Will retry in 3 seconds. 1 retries Warning: left. 0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0 curl: (22) The requested URL returned error: 500 ==> ERROR: Hubo fallos durante la descarga de https://registry.npmjs.org/@browserify%2facorn5-object-spread/-/acorn5-object-spread-5.0.1.tgz
macxcool commented on 2017-12-12 11:32 (UTC)
@sbmomeni Thanks for the explanation. I appreciate it. I may try a bin package, just for the fun of it ;-)
sbmomeni commented on 2017-12-12 10:51 (UTC) (edited on 2017-12-12 10:53 (UTC) by sbmomeni)
@macxcool Now that our installation script is merged in upstream repo, a "-bin" package can use that approach. But it does not necessarily work as the ArchLinux continues updating. For example, we had to use a different electron version previously.
a1rolo commented on 2017-09-08 01:10 (UTC)
mathieu.clabaut commented on 2017-08-21 08:27 (UTC)
macxcool commented on 2017-07-27 21:36 (UTC)
sbmomeni commented on 2017-07-27 20:14 (UTC)
mathieu.clabaut commented on 2017-07-27 07:23 (UTC)
sbmomeni commented on 2017-05-30 06:11 (UTC)
luuuciano commented on 2017-05-29 15:21 (UTC)
Distag commented on 2017-05-29 14:52 (UTC)
sbmomeni commented on 2016-12-03 12:56 (UTC)
oberon2007 commented on 2016-12-02 17:10 (UTC) (edited on 2016-12-02 17:17 (UTC) by oberon2007)
oberon2007 commented on 2016-12-02 16:08 (UTC)
carmelom commented on 2016-11-20 17:57 (UTC) (edited on 2016-11-20 18:03 (UTC) by carmelom)
fsiegert commented on 2016-08-29 08:31 (UTC)
sbmomeni commented on 2016-08-28 10:49 (UTC)
fsiegert commented on 2016-08-26 07:58 (UTC)
sbmomeni commented on 2016-06-30 15:34 (UTC)
dodomorandi commented on 2016-06-30 08:05 (UTC)
Distag commented on 2016-06-29 07:19 (UTC)
luuuciano commented on 2016-06-09 13:47 (UTC)
sbmomeni commented on 2016-06-09 07:11 (UTC)
luuuciano commented on 2016-06-08 14:04 (UTC)
sbmomeni commented on 2016-05-25 08:21 (UTC)
grandchild commented on 2016-05-18 21:19 (UTC) (edited on 2016-05-18 21:19 (UTC) by grandchild)
sbmomeni commented on 2016-02-15 12:58 (UTC)
macxcool commented on 2015-12-22 14:36 (UTC)
sbmomeni commented on 2015-12-22 12:05 (UTC)
macxcool commented on 2015-12-21 16:25 (UTC)
luuuciano commented on 2015-12-21 00:25 (UTC)
sbmomeni commented on 2015-12-20 21:17 (UTC)
luuuciano commented on 2015-12-20 20:04 (UTC)
sbmomeni commented on 2015-12-19 08:36 (UTC)
qqqqqqqqq9 commented on 2015-11-08 19:50 (UTC)
qqqqqqqqq9 commented on 2015-09-29 11:07 (UTC)
qqqqqqqqq9 commented on 2015-09-28 13:37 (UTC)
orschiro commented on 2014-12-08 06:55 (UTC)
rabarrett commented on 2014-12-07 23:27 (UTC)
BrunoSpy commented on 2014-04-06 10:52 (UTC)
xrchz commented on 2013-11-02 17:23 (UTC)
Clauz commented on 2013-03-21 10:39 (UTC)
commented on 2012-04-30 09:56 (UTC)
commented on 2012-04-30 09:54 (UTC)
BrunoSpy commented on 2012-04-06 06:33 (UTC)
commented on 2012-03-07 10:59 (UTC)
orbisvicis commented on 2011-04-13 19:24 (UTC)
Cilyan commented on 2011-03-24 21:06 (UTC)
linkmauve commented on 2010-12-04 21:29 (UTC)
unhammer commented on 2010-12-01 13:54 (UTC)