Package Details: opensnitch-git 1.6.3.r152.1984fb99-1

Git Clone URL: https://aur.archlinux.org/opensnitch-git.git (read-only, click to copy)
Package Base: opensnitch-git
Description: A GNU/Linux port of the Little Snitch application firewall
Upstream URL: https://github.com/evilsocket/opensnitch
Licenses: GPL3
Conflicts: opensnitch
Provides: opensnitch
Submitter: None
Maintainer: lsf
Last Packager: lsf
Votes: 43
Popularity: 0.49
First Submitted: 2017-05-03 14:15 (UTC)
Last Updated: 2024-07-25 10:25 (UTC)

Required by (3)

Sources (5)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 18 Next › Last »

lsf commented on 2020-08-13 07:38 (UTC)

Should be possible (the way the module is called from the code is always just with a string as an argument and no other options, and the module is called slugify with both packages, so it seems to not matter very much), although I'd probably first raise this as an issue / question on https://github.com/gustavo-iniguez-goya/opensnitch/issues – might make sense to have someone with more python knowledge look into this and/or see if an "upstream" switch to the other package would make sense.

It's a bit of an annoying situation caused (probably) by the identical naming of the python module by different packages.

lambdaclan commented on 2020-08-13 06:32 (UTC)

Is it possible to replace the python-unicode-slugify dependency with the version in community? According to the description "A Python slugify application that handles unicode" so I am assuming there will be no issues.

I have removed the AUR one and replaced it with the community version and opensnitch still seems to work.

tuqueque commented on 2020-07-28 00:40 (UTC)

@yochananmarqos oh, you're absolutely right!... I actually didn't know that keeping stuff like these in cache in could bring these type of problems. Good thing I'm learning today. Double thanks!

yochananmarqos commented on 2020-07-27 21:45 (UTC)

@tuqueque: You have an old cached version of the PKGBUILD from whatever AUR helper you're using. Remove the cache and try again or use makepkg.

tuqueque commented on 2020-07-27 16:20 (UTC) (edited on 2020-07-27 16:21 (UTC) by tuqueque)

Hello, I see that somebody reported a dependency problem and you said you fixed it, but today I tried to install OpenSnitch and I get this error:

==> Making package: opensnitch-git 1.0.0.rc5.r16.db22e83-1 (lun 27 jul 2020 12:04:43)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> python-libconfigparser
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
error making: opensnitch-git

I tried manually installing python-configparser-5.0.0-1, but still won't compile. (I'm using Manjaro)

yochananmarqos commented on 2020-07-16 23:05 (UTC)

@yoandrisolis: Fixed.

yoandrisolis commented on 2020-06-10 02:17 (UTC)

5.6.15-1-MANJARO

Preparing... Cloning opensnitch-git build files... Checking opensnitch-git dependencies... Resolving dependencies... Checking inter-conflicts... Edit opensnitch-git build files

Cloning opensnitch-git build files... Checking opensnitch-git dependencies... Resolving dependencies... Checking inter-conflicts...

Building opensnitch-git... ==> Making package: opensnitch-git 1.0.0rc6.r4.0c68365-1 (mar 09 jun 2020 21:51:13) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating opensnitch git repo... Fetching origin ==> Validating source files with sha256sums... opensnitch ... Skipped ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Creating working copy of opensnitch git repo... Cloning into 'opensnitch'... done. ==> Starting prepare()... The following issues were found in Gopkg.toml:

✗ unable to deduce repository and source type for "google.golang.org/grpc": unable to read metadata: unable to parse go-import metadata: XML syntax error on line 9: expected /> in element

ProjectRoot name validation failed ==> ERROR: A failure occurred in prepare(). Aborting...

someone help

nifty404 commented on 2020-04-11 04:29 (UTC)

Yep, followed directions from the Github page and was successful.