Re: [Slackbuilds-users] Strange problem with KeePass 2.39.1

[Shrivats]

Hey,

That may be true only if you download the binary release. But in the
SlackBuild, we use the Source release and I don't include
KeePass.config.xml in the package at all.

There are a couple things you can do as an user, if you don't prefer
keeping the config xml globally:

* Pass the path to your local configuration file through the command line
argument: '-cfg-local:' and override defaults.
* Keep your local configuration file in `~/.config/KeePass`

I'll think about including this file for global configuration (In the
source, it's `true` by default)

Thanks,

Shrivats

On 14 June 2018 at 23:01, Thomas Szteliga  wrote:

> Hello,
>
> I've noticed a strange problem with KeePass.
> I see now in the description, that's the portable version.
> https://slackbuilds.org/repository/14.2/misc/KeePass/
>
>
> This version will not save user settings by default.
>
> So it won't remember the last opened file or any settings
> changed by a user without write permissions
> in /usr/lib/KeePass/Release/.
>
> The problem is caused by `PreferUserConfiguration`
> which is by default set to false in
> `/usr/lib/KeePass/Release/KeePass.config.xml`
>
>
> ~~~
> ...
> false
> ...
> ~~~
>
> Changing value to true will fix the problem and users
> will be able to have individual configs.
>
>
> Found this bit related:
> https://sourceforge.net/p/keepass/discussion/329221/thread/d8c595ac/
>
>
>
> --
> Best regards
>
> Thomas Szteliga
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Why did git report everything as a conflict lust now?

[Robby Workman]

On Fri, 15 Jun 2018 12:06:01 +1000
Duncan Roe  wrote:

> Hi everyone,
> 
> I just did a git pull in my clone of
> git://git.slackbuilds.org/slackbuilds.git and every single change was
> reported as a conflict. I checked the first one:
> 
> ... 
> 
> Where's the conflict in that? It's just a straightforward update.
> 
> Anyone have any idea what's going on here?


https://lists.slackbuilds.org/pipermail/slackbuilds-users/2018-June/021612.html

and

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2018-June/021605.html

-RW


pgph8KfkFhbuo.pgp
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Why did git report everything as a conflict lust now?

[Duncan Roe]

Hi everyone,

I just did a git pull in my clone of git://git.slackbuilds.org/slackbuilds.git
and every single change was reported as a conflict. I checked the first one:

> Auto-merging system/spman/spman.info
> CONFLICT (add/add): Merge conflict in system/spman/spman.info

> less -N system/spman/spman.info
>  1 PRGNAM="spman"
>  2 <<< HEAD
>  3 VERSION="1.5.3"
>  4 HOMEPAGE="https://github.com/MyRequiem/spman;
>  5 
> DOWNLOAD="https://github.com/MyRequiem/spman/archive/1.5.3/spman-1.5.3.tar.gz;
>  6 MD5SUM="b43a1def97283d7346ce88bd217a0e24"
>  7 ===
>  8 VERSION="1.5.4"
>  9 HOMEPAGE="https://github.com/MyRequiem/spman;
> 10 
> DOWNLOAD="https://github.com/MyRequiem/spman/archive/1.5.4/spman-1.5.4.tar.gz;
> 11 MD5SUM="9096f25e2909be7ca3b8823b53f82699"
> 12 >>> a31868bb76cca8c30498b60dc2fd685c64bfe00a
> 13 DOWNLOAD_x86_64=""
> 14 MD5SUM_x86_64=""
> 15 REQUIRES="python3"
> 16 MAINTAINER="Vladimir MyRequiem"
> 17 EMAIL="mrvladislavov...@gmail.com"

Where's the conflict in that? It's just a straightforward update.

Anyone have any idea what's going on here?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] pcsc-lite - download url not working

[Didier Spaier]

Hello,

Le 13/06/2018 à 17:43, Thomas Szteliga a écrit :
> there's a problem with
> 
> which is unavailable.
> 
> Maybe https://pcsclite.apdu.fr/files/ will be a better mirror?

Alioth is closing and for this reason e.g. po4a has moved both its home
page and repository (I just submitted an update for this one).

If there is an easy way to check all .info, maybe dropping a line to the
maintainers in concern would help?

Greetings,

Didier
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Strange problem with KeePass 2.39.1

[Thomas Szteliga]

Hello,

I've noticed a strange problem with KeePass.
I see now in the description, that's the portable version.
https://slackbuilds.org/repository/14.2/misc/KeePass/


This version will not save user settings by default.

So it won't remember the last opened file or any settings
changed by a user without write permissions
in /usr/lib/KeePass/Release/.

The problem is caused by `PreferUserConfiguration`
which is by default set to false in
`/usr/lib/KeePass/Release/KeePass.config.xml`


~~~
...
false
...
~~~

Changing value to true will fix the problem and users
will be able to have individual configs.


Found this bit related:
https://sourceforge.net/p/keepass/discussion/329221/thread/d8c595ac/



--
Best regards

Thomas Szteliga
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[B Watson]

On 6/14/18, Nate Bargmann  wrote:

> Do I just need to do the nuclear option of deleting my GitHub fork
> and creating a new fork and then setting up a new clone?

Just did this, at sbosrcarch. The archive is still sitting at 99.9%
complete...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Nate Bargmann]

Thanks, David.

I followed your commands and everything looks proper in the master
branch and I simply deleted the already merged local branches on GitHub,
so that should be clean now.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: http://www.n0nb.us  GPG key: D55A8819  GitHub: N0NB


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Panagiotis Nikolaou via SlackBuilds-users]

> Hi Nate, Hi everybody,
>
> On 14/06/18 13:39, Nate Bargmann wrote:
>> * On 2018 13 Jun 16:05 -0500, Matteo Bernardini wrote:
>>> git checkout master
>>> git fetch --all
>>> git reset --hard origin/master
>> I did those commands and still have the files remaining in my local
>> tree.
> Sorry about that, we're still working out what are the best commands for
> people to use 
>
> If your remote 'origin' is your own fork at Github, instead of one of
> the SBo repos, then this is probably the quickest and safest way:
>
>> Do I just
>> need to do the nuclear option of deleting my GitHub fork and creating a
>> new fork and then setting up a new clone?
>
>
> Alternatively, you can add another remote for our repo and fetch it:
>
> git checkout master
> git remote add sbo https://git.slackbuilds.org/slackbuilds/
> git fetch --all
> git fetch --tags sbo
> git reset --hard sbo/master
> git push -f origin master
> git push -f --tags origin master
>
> If you have other branches (like 14.2) you need to delete them too.
>
> Hope this is ok, thanks for the feedback!
> -D.

I did this to my branches to delete the history:

git filter-branch --force --index-filter 'git rm --cached
--ignore-unmatch audio/jack-tools/aeffect*' --prune-empty
--tag-name-filter cat -- --all

It took me a long time since I have 3 different branches, but at the end
it delete completely the history.

I didn't have enough time yesterday to sync with SBo I just delete for
the time the affected SlackBuild.

P.S. Sorry David I just noticed that accidentally reply on you instead of the 
list.

Regards
Panagiotis

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[David Spencer]

Hi Nate, Hi everybody,

On 14/06/18 13:39, Nate Bargmann wrote:
> * On 2018 13 Jun 16:05 -0500, Matteo Bernardini wrote:
>> git checkout master
>> git fetch --all
>> git reset --hard origin/master
> 
> I did those commands and still have the files remaining in my local
> tree.

Sorry about that, we're still working out what are the best commands for
people to use :(

If your remote 'origin' is your own fork at Github, instead of one of
the SBo repos, then this is probably the quickest and safest way:

> Do I just
> need to do the nuclear option of deleting my GitHub fork and creating a
> new fork and then setting up a new clone?

:)

Alternatively, you can add another remote for our repo and fetch it:

git checkout master
git remote add sbo https://git.slackbuilds.org/slackbuilds/
git fetch --all
git fetch --tags sbo
git reset --hard sbo/master
git push -f origin master
git push -f --tags origin master

If you have other branches (like 14.2) you need to delete them too.

Hope this is ok, thanks for the feedback!
-D.



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] dmca takedown notice?!

[Nate Bargmann]

* On 2018 13 Jun 16:05 -0500, Matteo Bernardini wrote:
> git checkout master
> git fetch --all
> git reset --hard origin/master

I did those commands and still have the files remaining in my local
tree.

I had not WIP so I was sync'ed with Willy's 2 June update.  Do I just
need to do the nuclear option of deleting my GitHub fork and creating a
new fork and then setting up a new clone?

I'm not fluent enough with Git to know what to do in this circumstance.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: http://www.n0nb.us  GPG key: D55A8819  GitHub: N0NB


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] pcsc-lite - download url not working

[Willy Sudiarto Raharjo]

>> there's a problem with
>> > .tar.bz2>
>> which is unavailable.
>>
>> Maybe https://pcsclite.apdu.fr/files/ will be a better mirror?

I have this fixed on my branch

Thanks


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/