headers
Stephen Vance | 1 Dec 2006 01:42

Re: [p4] how to find out who has what checked out?

p4 opened -a

Steve

Hamid Ghassemi wrote:
> I am trying to move a directory from one location to another and I get
> the following message;
>
>  
>
> Rename/Move could not be performed
>
> Files within this directory are already checked out:
>
> //depot/development/internal/
>
>  
>
> How can I find out who has files checked out in this directory without
> trying to run "p4 opened" against every workspace?  We have a lot of
> them.
>
>  
>
> Thanks in advance.
>
>  
>
> Hamid Ghassemi
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ryan Dooley | 1 Dec 2006 03:21
Picon
Favicon

Re: [p4] how to find out who has what checked out?

Hamid Ghassemi wrote:
> I am trying to move a directory from one location to another and I get
> the following message;
> 
>  
> 
> Rename/Move could not be performed
> 
> Files within this directory are already checked out:
> 
> //depot/development/internal/
> 
>  
> 
> How can I find out who has files checked out in this directory without
> trying to run "p4 opened" against every workspace?  We have a lot of
> them.

p4 opened -a //depot/development/internal/...

should do the trick.

Cheers,
Ryan
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
David Weintraub | 1 Dec 2006 03:56
Picon
Gravatar

Re: [p4] how to find out who has what checked out?

Have you tried the "-a" parameter with "p4 opened?":

   $ p4 opened -a //depot/my/path/...

This will list the files opened on the path in all workspaces with the
name of the user and the workspace.

I take it that you're using "P4V" or "p4win" to do this because the
"p4 integrate" command will allow you to do the rename/move even with
open files:

    $ p4 integrate //depot/old/path/... //depot/new/path/...
    $ p4 delete //depot/old/path/...

Of course, it'll throw those people who had open files on the old path
in for a loop.

On 11/30/06, Hamid Ghassemi <hghassemi <at> uievolution.com> wrote:
> I am trying to move a directory from one location to another and I get
> the following message;
>
>
>
> Rename/Move could not be performed
>
> Files within this directory are already checked out:
>
> //depot/development/internal/
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Patrick Bennett | 1 Dec 2006 04:05
Gravatar

Re: [p4] PowerShell Integration

Geesh... It just took *8* hours for my message to show up on the list!  :(

Bennett, Patrick wrote:
> Actually, Powershell is a completely new command shell paradigm.  It
> really is.
> It's insanely verbose (but you can fix that with aliases) and *very*
> different but it has some immense potential.
>
> ...although I think whoever said it was like Ruby should take it back.
> Powershell is nothing like Ruby.  Powershell made some very... odd
> language design choices in their language.  Particularly if you're a
> Ruby lover like myself.  ;)
>
>
> Patrick Bennett
>   

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 0 comments |
headers
Paul M. Goorskis | 1 Dec 2006 09:35
Picon

[p4] Delete depot problem

$ p4 depot -d MyDepot
Depot MyDepot isn't empty; clear it with 'p4 obliterate' first.
$ p4 obliterate -y //MyDepot/...
No records to delete.

Server version: P4D/LINUX26X86/2006.1
Kernel version: Linux perforce 2.6.9-5.ELsmp
FS Type: ext3
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 9 comments |
headers
Sweeney, Tony | 1 Dec 2006 10:40
Favicon

Re: [p4] Triggers and best practice authentication from scripts

Per the Administrators's Guide:

"After an auth-check trigger is in place and the server restarted, the
Perforce security counter is ignored; because authentication is now
under the control of the trigger script, the server's default mechanism
for password strength requirements is redundant."

Tony.

quis custodiet ipsos custodes -- Juvenal VI, 347-8  

> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com 
> [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Steven Bougon
> Sent: 30 November 2006 17:44
> To: Stephen Vance; Finn Normann Pedersen
> Cc: perforce-user <at> perforce.com
> Subject: Re: [p4] Triggers and best practice authentication 
> from scripts
> 
> >you can shut down the server, delete db.trigger and restart 
> the server
> This approach is also the one Perforce Support recommended when I 
> was facing the same problem (last week):
> - shut down p4d
> - mv db.trigger db.trigger.tmp
> - restart server
> - mv db.trigger.tmp db.trigger
> (since the auth check get activated after a restart only)
>
(Continue reading)

Permalink | Reply | 501 comments |
headers
mancaus.40868864 | 1 Dec 2006 11:32
Favicon

Re: [p4] PowerShell Integration

Hi Patrick,

I think you mean me... I said it pays a homage to Ruby, which
I think it does. I wouldn't at all be suprised if some of the syntax and features
where Ruby inspired. But you're correct, in the most part it's not like Ruby.

To keep this relevant... here's a section of code you can add to the default
TabExpansion function that comes with powershell. It adds auto-completion
of perforce depot specs. The implementation may be naive as I'm only a powershell
beginner. It can also suffer from an timeout problem in that completion does
nothing if the "p4 dirs" takes too long.

# Complete perforce specs

'^//.*$'
{

  $specs = (p4 dirs ($lastWord + '*'))

  if ( $specs -ne $null ) {

    if ( $specs.GetType() -eq "Object[]" ) {

      $specs

    } else {

      ($specs + '/')

    }
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Weintraub | 1 Dec 2006 15:43
Picon
Gravatar

Re: [p4] Delete depot problem

Anything opened on that depot? Any pending changelists that have
something on that depot?

On 12/1/06, Paul M. Goorskis <pmg <at> rimako.lv> wrote:
> $ p4 depot -d MyDepot
> Depot MyDepot isn't empty; clear it with 'p4 obliterate' first.
> $ p4 obliterate -y //MyDepot/...
> No records to delete.
>
>
> Server version: P4D/LINUX26X86/2006.1
> Kernel version: Linux perforce 2.6.9-5.ELsmp
> FS Type: ext3
> _______________________________________________
> perforce-user mailing list  -  perforce-user <at> perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>

--

-- 
--
David Weintraub
qazwart <at> gmail.com
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 3 comments |
headers
Paul M. Goorskis | 1 Dec 2006 15:54
Picon

Re: [p4] Delete depot problem


Hi David,

How could I check for this? I've removed all clients who worked with 
this depot, but i could miss something.

David Weintraub wrote:

> Anything opened on that depot? Any pending changelists that have
> something on that depot?
>
> On 12/1/06, Paul M. Goorskis <pmg <at> rimako.lv> wrote:
>
>> $ p4 depot -d MyDepot
>> Depot MyDepot isn't empty; clear it with 'p4 obliterate' first.
>> $ p4 obliterate -y //MyDepot/...
>> No records to delete.
>>
>>
>> Server version: P4D/LINUX26X86/2006.1
>> Kernel version: Linux perforce 2.6.9-5.ELsmp
>> FS Type: ext3
>> _______________________________________________
>> perforce-user mailing list  -  perforce-user <at> perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>
>
>
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
(Continue reading)

Permalink | Reply | 2 comments |
headers
Greg Pan | 1 Dec 2006 16:48
Picon

Re: [p4] p4label task of ANT - owner was not created

It turned out the fix to this issue was straight forward. Please see the
following added codes as compared to the original one. 

Thanks,

Greg Pan

--- P4Label.java

+++ new/P4Label.java    

***************

*** 47,52 ****

--- 47,53 ----

      protected String name;

      protected String desc;

      protected String lock;

+     protected String user;

      /**

       * The name of the label; optional, default "AntLabel"

***************
(Continue reading)

Permalink | Reply | 0 comments |

Gmane