Re: [p4] Broker config: Cannot get version to match

Michael Mirman <[email protected]>
Newsgroups gmane.comp.version-control.perforce
Message-ID <BLUPR0501MB10606142BFC904F2097D8AD28A710@BLUPR0501MB1060.namprd05.prod.outlook.com>
> Is the version matching broken...
This was my understanding a while ago.
We tried to prevent leaking processes caused by the old version.
Ended up rejecting the "most popular" versions and chasing other users individually (getting their names from the log - fortunately, grep matches whatever we tell it to.)

--
Michael Mirman
MathWorks, Inc.
508-647-7555

-----Original Message-----
From: perforce-user [mailto:[email protected]] On Behalf Of roadkills_r_us
Sent: Wednesday, October 4, 2017 5:55 PM
To: [email protected]
Subject: [p4] Broker config: Cannot get version to match

Posted on behalf of forum user 'roadkills_r_us'.

Due to a bug that appears to be tied to older p4v clients and the 2017.1 server,
we are requiring new client software to be used. While we have pushed it out to
Linux systems, the users still manage their own Windows and OSX systems. We have
been sending emails explaining the situation, with instructions on upgrading,
but not everyone has done this. We want to bar older clients with the broker.[1]
To this end, we have an entry in the broker config file:

command: .* {
    prog =   P4V;    # case
does not seem to matter here.
        version
=       2015;
    action =     reject;
    message =    "You must use a 2017.1 or
later client. If you need help upgrading your client, please file a ticket or
contact [email protected] .";
}
We cannot get the version field to work. We have tried:

  
-  2015
  
-  2015.2
  
-  2015.*
  
-  .*2015.*
  
-  2015.2/LINUX26X86_64/1458499

If we comment out the version line, the broker happily rejects all p4v clients.
Is the version matching broken, or is there an undocumented trick to make this
work?

[1] We cannot just set the overall minimum client version in the server, as it
will take a bit longer to get the p4 command line client upgrades done.



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5505-broker-config-cannot-get-version-to-match
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.