Package Details: stig-git 0.11.2a0.r14.a059b0b9-3

Git Clone URL: (read-only, click to copy)
Package Base: stig-git
Description: TUI and CLI client for the Transmission daemon
Upstream URL:
Keywords: bittorrent terminal torrent transmission tui
Licenses: GPL
Conflicts: stig
Provides: stig
Submitter: kazuo
Maintainer: christian97
Last Packager: christian97
Votes: 4
Popularity: 0.000002
First Submitted: 2017-01-26 01:05 (UTC)
Last Updated: 2020-12-02 08:50 (UTC)

Latest Comments

1 2 Next › Last »

christian97 commented on 2020-12-02 09:05 (UTC)

If the application doesn't run after the 3.9 Python update, try to clean build the package

christian97 commented on 2020-07-30 11:54 (UTC)

Thanks for reporting the problem. It should now be solved.

Alda commented on 2020-07-30 11:41 (UTC)

There is an error in the prepare function :

rm: cannot remove '.python-version': No such file or directory

Removing the faulty line makes the package build properly

bowhuntr commented on 2018-12-14 22:16 (UTC)

I am getting an error: pkgbase should not be an array When trying to build the package.

kazuo commented on 2017-10-20 18:56 (UTC)

The reasoning is: 1) pyxdg is already packaged in extra 2) pyxdg and xdg are not compatible and they can't be installed at same time, they both install under the xdg module (i.e. `import xdg`) I'm don't know why stig uses xdg instead of pyxdg, I'm not familiar with any of the packages.

cgirard commented on 2017-10-20 17:52 (UTC)

Nice thank you. Yes I agree with you but what is the reasoning of using pyxdg over xdg except it is needed on Arch Linux?

kazuo commented on 2017-10-20 17:02 (UTC)

@cgirard I'm sorry I forgot about it. I pushed a fix that allow stig-git to run on Arch using `extra/python-xdg`. The use of the package is very minimal, only used to grab the variables, so I just patched the stig source to use the syntax of the one packaged by Arch. A proper try/import/except fix would be better if submited upstream.

cgirard commented on 2017-10-20 13:27 (UTC)

@kazuo did you got any chance to look at this?

kazuo commented on 2017-09-06 01:40 (UTC)

One ideia is to write a patch to stig to use either the pyxdg one or the xdg. I'm little busy right now but I will see if I can do this on the weekend.

kazuo commented on 2017-09-06 01:38 (UTC)

@cgirard Thanks for the heads up. The error is caused because stig uses and `python-xdg` packages The problem is, I packaged the xdg needed by stig, but if you have both, and they don't file conflict, you still get the error because `import xdg` import the pyxdg one. I'm not sure how to fix or here to fix.