Peforce GitLFS like features

[Robin]

Hi, I use SVN for gamedev projects, it works great but our repository 
size is growing towards 1TB size. A lot of the files are binary taking 
up bulk of space. For bigger projects in game industry, peforce is 
commonly used,  and they have a few features which are quite neat.


1. User can specify certain files that don't need to store full history. 
Server keep only X number of rev history cos the older revisions are not 
needed.  e.g a artist photoshop file, we don't need full history, 
usually only the latest or a few revisions.


2. Server don't keep a duplicate copy of those files on client, client 
get 1 copy only. This would be similar to git LFS.


If SVN has these  features natively, it would be greatest tool. 
Otherwise, how would it  be possible to make such a setup?


Robin

Re: Subversion 1.14.2 on Linux how to enable plaintext password store?

[Mark Phippard]

On Fri, Dec 1, 2023 at 4:27 PM Daniel Sahlberg
 wrote:
>
> fre 1 dec. 2023 kl. 22:15 skrev Mark Phippard :
>>
>> Correct me if I am wrong Nathan, but there is no option that allows
>> plaintext passwords on Linux.
>> https://subversion.apache.org/docs/release-notes/1.14.html#plaintext-passwords-disabled
>
>
> In the original post there was a quote from svn —version showing that 
> plaintext cache was one of the available stores. I guess svn was built with 
> the
> --enable-plaintext-password-storage option. Then plaintext password cache 
> would be enabled, unless disabled in the config files, right?

I would think so, yes. I was not aware of anyone that packaged SVN
with this compiled in. I seem to recall it was not easy to do so.
Sorry for the noise.

Mark

Re: Subversion 1.14.2 on Linux how to enable plaintext password store?

[Daniel Sahlberg]

fre 1 dec. 2023 kl. 22:15 skrev Mark Phippard :

> Correct me if I am wrong Nathan, but there is no option that allows
> plaintext passwords on Linux.
>
> https://subversion.apache.org/docs/release-notes/1.14.html#plaintext-passwords-disabled


In the original post there was a quote from svn —version showing that
plaintext cache was one of the available stores. I guess svn was built with
the
--enable-plaintext-password-storage option. Then plaintext password cache
would be enabled, unless disabled in the config files, right?


> I thought that was a change in trunk to put that back as an option for
> 1.15?  https://svn.apache.org/repos/asf/subversion/trunk/CHANGES


Wasn’t this change just to revert to the old default to enable plaintext
cache unless disabled by configure?

Kind regards
Daniel



>
>
> Mark
>
>
>
> On Fri, Dec 1, 2023 at 12:55 AM Nathan Hartman 
> wrote:
> >
> > On Thu, Nov 30, 2023 at 6:43 PM Bo Berglund 
> wrote:
> > >
> > > When I installed subversion on a Raspberry Pi4B and checked the
> installed
> > > version afterwards it printed this:
> > >
> > > $ svn --version
> > > svn, version 1.14.2 (r1899510)
> > >compiled Nov 12 2022, 20:30:30 on arm-unknown-linux-gnueabihf
> > >
> > > Copyright (C) 2022 The Apache Software Foundation.
> > > This software consists of contributions made by many people;
> > > see the NOTICE file for more information.
> > > Subversion is open source software, see http://subversion.apache.org/
> > >
> > > < cut >
> > >
> > > The following authentication credential caches are available:
> > >
> > > * Plaintext cache in /home/bosse/.subversion
> > > * Gnome Keyring
> > > * GPG-Agent
> > > * KWallet (KDE)
> > >
> > > I have had a lot of problems with password caching for a number of
> years since I
> > > am working on these devices mainly on the command line via ssh and
> when I issue
> > > a svn command against a server on our LAN what happens is that svn
> pops up a
> > > password entry dialog on the (invisible) **GUI screen**!
> > > And the operation started on the command line fails...
> > >
> > > It was not always so but some svn update changed the way svn
> operates
> > >
> > > Now I see the banner above where it looks like it is again available:
> > >
> > > * Plaintext cache in /home/bosse/.subversion
> > >
> > > The problem is that in the config file there is no example of the
> syntax for
> > > enabling this
> > >
> > > So my question here is:
> > > How do I enable the plaintext cache in svn client version 1.14.2 on a
> Raspberry
> > > Pi4B running Pi-OS?
> > >
> > >
> > > --
> > > Bo Berglund
> > > Developer in Sweden
> >
> >
> > In the user's home directory, there should be a subdirectory called
> > .subversion which contains a file called config. In that file, there
> > is a section called [auth] which contains a setting called
> > "password-stores". It might be commented, or it might say something
> > like "password-stores = gpg-agent,gnome-keyring,kwallet". This setting
> > determines the order in which the different password stores
> > (credential caches) are used. You could set this to "password-stores =
> > plaintext". Make sure you don't have "store-passwords = no" or
> > "store-plaintext-passwords = no". I think this will solve the issue --
> > though note that if the password has not been saved to the plaintext
> > cache yet, the SVN client should prompt for it once, and then prompt
> > whether you accept the risk to save it in the plaintext cache. This
> > should take place on the command line, so I think you won't have the
> > issue with the inaccessible GUI dialog box on the remote machine. Once
> > saved, it shouldn't prompt for it anymore.
> >
> > Note: In addition to the user's ~/.subversion/config file I mentioned
> > above, there is also a systemwide /etc/subversion/config. If changes
> > in the user-level file don't appear to work, check the systemwide one
> > as well.
> >
> > Hope this helps,
> > Nathan
>

Re: Subversion 1.14.2 on Linux how to enable plaintext password store?

[Mark Phippard]

Correct me if I am wrong Nathan, but there is no option that allows
plaintext passwords on Linux.
https://subversion.apache.org/docs/release-notes/1.14.html#plaintext-passwords-disabled

I thought that was a change in trunk to put that back as an option for
1.15?  https://svn.apache.org/repos/asf/subversion/trunk/CHANGES


Mark



On Fri, Dec 1, 2023 at 12:55 AM Nathan Hartman  wrote:
>
> On Thu, Nov 30, 2023 at 6:43 PM Bo Berglund  wrote:
> >
> > When I installed subversion on a Raspberry Pi4B and checked the installed
> > version afterwards it printed this:
> >
> > $ svn --version
> > svn, version 1.14.2 (r1899510)
> >compiled Nov 12 2022, 20:30:30 on arm-unknown-linux-gnueabihf
> >
> > Copyright (C) 2022 The Apache Software Foundation.
> > This software consists of contributions made by many people;
> > see the NOTICE file for more information.
> > Subversion is open source software, see http://subversion.apache.org/
> >
> > < cut >
> >
> > The following authentication credential caches are available:
> >
> > * Plaintext cache in /home/bosse/.subversion
> > * Gnome Keyring
> > * GPG-Agent
> > * KWallet (KDE)
> >
> > I have had a lot of problems with password caching for a number of years 
> > since I
> > am working on these devices mainly on the command line via ssh and when I 
> > issue
> > a svn command against a server on our LAN what happens is that svn pops up a
> > password entry dialog on the (invisible) **GUI screen**!
> > And the operation started on the command line fails...
> >
> > It was not always so but some svn update changed the way svn operates
> >
> > Now I see the banner above where it looks like it is again available:
> >
> > * Plaintext cache in /home/bosse/.subversion
> >
> > The problem is that in the config file there is no example of the syntax for
> > enabling this
> >
> > So my question here is:
> > How do I enable the plaintext cache in svn client version 1.14.2 on a 
> > Raspberry
> > Pi4B running Pi-OS?
> >
> >
> > --
> > Bo Berglund
> > Developer in Sweden
>
>
> In the user's home directory, there should be a subdirectory called
> .subversion which contains a file called config. In that file, there
> is a section called [auth] which contains a setting called
> "password-stores". It might be commented, or it might say something
> like "password-stores = gpg-agent,gnome-keyring,kwallet". This setting
> determines the order in which the different password stores
> (credential caches) are used. You could set this to "password-stores =
> plaintext". Make sure you don't have "store-passwords = no" or
> "store-plaintext-passwords = no". I think this will solve the issue --
> though note that if the password has not been saved to the plaintext
> cache yet, the SVN client should prompt for it once, and then prompt
> whether you accept the risk to save it in the plaintext cache. This
> should take place on the command line, so I think you won't have the
> issue with the inaccessible GUI dialog box on the remote machine. Once
> saved, it shouldn't prompt for it anymore.
>
> Note: In addition to the user's ~/.subversion/config file I mentioned
> above, there is also a systemwide /etc/subversion/config. If changes
> in the user-level file don't appear to work, check the systemwide one
> as well.
>
> Hope this helps,
> Nathan

Re: Subversion 1.14.2 on Linux how to enable plaintext password store?

[Bo Berglund]

On Fri, 1 Dec 2023 09:25:55 +0100, Daniel Sahlberg 
wrote:

>Den fre 1 dec. 2023 kl 08:35 skrev Bo Berglund :
>
>> As it has been for some time now when I enter a command window svn command
>> that
>> requires authentication it pops up a dialog on the GUI window which is
>> invisible
>> to me at that point.
>> It took a while before I understood what was going on, at first I thought
>> svn
>> had crashed or similar. It just hung there on the command window. :(
>>
>
>What does echo $DISPLAY return? I think it is awfully strange that an SSH
>session on the PiOS would start a graphical program, but if DISPLAY is set,
>maybe you can unset it and at least the GUI part would be solved?

echo $DISPLAY returns nothing at all

>
>> So on this new system I want to avoid this from happening and was
>> encouraged by
>> the output shown when I checked the svn version.
>>
>> I have no idea if any of the allowed stores mentioned (gnome-keyring,
>> kwallet,
>> gpg-agent) will work inside an SSH command line section...
>>
>
>I don't think any of those stores works on the command line. No idea what
>Subversion will do but I assume it will fall back to inputting the password
>on the command line.

OK, I will have to test it again.

But I have so many RPi units and some have this problem whereas others don't so
I have to somehow figure out how to test it on all to look for commonality/diff
between those that pop the GUI dialog and those that don't.

On one where the svn commands work without popping up anything I have this:

Inside ~/.subversion/auth are these dir/files:

svn.simple/03994a04eb338a432667e51f0e0720bf
svn.ssl.server/52e60f46d8c02303aea5256b18eb7aac

The other dirs are empty.

And the svn.simple/03994a04eb338a432667e51f0e0720bf file contains a reference to
gnome-keyring, could that be a non-GUI way of saving the login on a command line
operation?

Here it is:

cat auth/svn.simple/03994a04eb338a432667e51f0e0720bf
K 8
passtype
V 13
gnome-keyring
K 15
svn:realmstring
V 45
 VisualSVN Server
K 8
username
V 5
bosse
END

The auth/svn.ssl.server/52e60f46d8c02303aea5256b18eb7aac file contains a block
of data looking like a cert of some kind (encrypted password maybe).
It also references the server connection, but not the username.

So maybe these two together is the store for text based access logins?



-- 
Bo Berglund
Developer in Sweden

Re: Subversion 1.14.2 on Linux how to enable plaintext password store?

[Daniel Sahlberg]

Den fre 1 dec. 2023 kl 08:35 skrev Bo Berglund :

> As it has been for some time now when I enter a command window svn command
> that
> requires authentication it pops up a dialog on the GUI window which is
> invisible
> to me at that point.
> It took a while before I understood what was going on, at first I thought
> svn
> had crashed or similar. It just hung there on the command window. :(
>

What does echo $DISPLAY return? I think it is awfully strange that an SSH
session on the PiOS would start a graphical program, but if DISPLAY is set,
maybe you can unset it and at least the GUI part would be solved?


> So on this new system I want to avoid this from happening and was
> encouraged by
> the output shown when I checked the svn version.
>
> I have no idea if any of the allowed stores mentioned (gnome-keyring,
> kwallet,
> gpg-agent) will work inside an SSH command line section...
>

I don't think any of those stores works on the command line. No idea what
Subversion will do but I assume it will fall back to inputting the password
on the command line.

Kind regards,
Daniel