Re: unrar doesn't work under current
On 18-Dec-2002 (07:33:03/GMT) Kris Kennaway wrote:
>> But what about rar/unrar ports that overwrite one each other?
> I don't know what you mean here.
Try to install /usr/ports/archivers/{rar,unrar} in any order...
And then (or even better, before then) look at installed files:
# cd /usr/ports/archivers && grep bin/unrar {un,}rar/pkg-plist
unrar/pkg-plist:bin/unrar
rar/pkg-plist:bin/unrar
At this point removing one of each port (rar,unrar) destroy the
other bin/unrar. Is this a desidered feature?
> And _why_ rar port works (on same file) and unrar not?
> (at least this is a but in rar that doesn't do correct locking?)
Ooppss, s/but/bug/ (as stated before I need a vacancy :-)
Riccardo.
PS: we have the same problem at least with autoconf*/automake* pair,
where installed files names overlapping. IMVHO think this is a
Bad Thing(tm). (Anyway this is not a -CURRENT-only problem)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: unrar doesn't work under current
On Wed, Dec 18, 2002 at 08:20:21AM +0100, Riccardo Torrini wrote: > On 18-Dec-2002 (06:52:54/GMT) Kris Kennaway wrote: > > > This is due to lack of rpc.lockd running on the nfs client and/or > > server. > > Yes, I tryed on a nfs mounted dir from my -CURRENT home machine. > This means that this is a pilot error? Again? :-( > I'm sorry. I think that I must sleep a little more... Yes (though the failure message could be more explicit). > But what about rar/unrar ports that overwrite one each other? I don't know what you mean here. > And _why_ rar port works (on same file) and unrar not? > (at least this is a but in rar that doesn't do correct locking?) Presumably rar doesn't perform any file locking (it may or may not need to), Kris msg48981/pgp0.pgp Description: PGP signature
Re: unrar doesn't work under current
On 18-Dec-2002 (06:52:54/GMT) Kris Kennaway wrote: > This is due to lack of rpc.lockd running on the nfs client and/or > server. Yes, I tryed on a nfs mounted dir from my -CURRENT home machine. This means that this is a pilot error? Again? :-( I'm sorry. I think that I must sleep a little more... But what about rar/unrar ports that overwrite one each other? And _why_ rar port works (on same file) and unrar not? (at least this is a but in rar that doesn't do correct locking?) Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unrar doesn't work under current
On Tue, Dec 17, 2002 at 06:44:56PM +1100, Edwin Groothuis wrote: > Think it has something to do with this one: > 46353 unrarCALL open(0xbfbf98e3,0,0xbef6d8) > 46353 unrarNAMI "../rar/sample.rar" > 46353 unrarRET open 3 > 46353 unrarCALL flock(0x3,0x6) > 46353 unrarNAMI "/var/run/lock" > 46353 unrarRET flock -1 errno 45 Operation not supported > 46353 unrarCALL close(0x3) > 46353 unrarNAMI "/var/run/lock" > 46353 unrarRET close 0 > 46353 unrarCALL write(0x2,0xbfbed670,0x1e) > 46353 unrarGIO fd 2 wrote 30 bytes >" > Cannot open ../rar/sample.rar" > > That's in file.cpp:73, LOCK_EX is in /usr/include/fcntl.h > Haven't looked at the rest. This is due to lack of rpc.lockd running on the nfs client and/or server. Kris msg48976/pgp0.pgp Description: PGP signature
Re: unrar doesn't work under current
On Tue, Dec 17, 2002 at 06:33:04PM +1100, Tim Robbins wrote:
> On Tue, Dec 17, 2002 at 01:44:44AM +0100, Riccardo Torrini wrote:
>
> > Trying to extract a single or multi volume archive doesn't work.
> > Same archive can be extracted fine with unrar under 4.7-STABLE.
> > My -CURRENT from 10 day ago. Tryed to remove and rebuild unrar
> > without luck. rar on -CURRENT also works. Any idea?
> [...]
> > # uname -v
> > FreeBSD 5.0-RC #47: Sun Dec 8 18:09:42 CET 2002 ...
> >
> > # unrar t sample.rar
> >
> > UNRAR 3.10 beta 1 freeware Copyright (c) 1993-2002 Eugene Roshal
> >
> > Cannot open sample.rar
> > No files to extract
> [...]
>
> I tried to reproduce this but could not with these two versions of unrar:
>
> UNRAR 3.00 freeware (from source)
> UNRAR 3.10 beta 1 freeware (from ports)
>
> The output of ktrace/kdump or truss would be useful in investigating this.
It fails on ref5:
[~/ports/archivers/unrar] edwin@ref5>work/unrar/unrar t ../rar/sample.rar
UNRAR 3.10 beta 1 freeware Copyright (c) 1993-2002 Eugene Roshal
Cannot open ../rar/sample.rar
No files to extract
[~/ports/archivers/unrar] edwin@ref5>
Think it has something to do with this one:
46353 unrarCALL open(0xbfbf98e3,0,0xbef6d8)
46353 unrarNAMI "../rar/sample.rar"
46353 unrarRET open 3
46353 unrarCALL flock(0x3,0x6)
46353 unrarNAMI "/var/run/lock"
46353 unrarRET flock -1 errno 45 Operation not supported
46353 unrarCALL close(0x3)
46353 unrarNAMI "/var/run/lock"
46353 unrarRET close 0
46353 unrarCALL write(0x2,0xbfbed670,0x1e)
46353 unrarGIO fd 2 wrote 30 bytes
"
Cannot open ../rar/sample.rar"
That's in file.cpp:73, LOCK_EX is in /usr/include/fcntl.h
Haven't looked at the rest.
Edwin
--
Edwin Groothuis |Personal website: http://www.MavEtJu.org
[EMAIL PROTECTED]|Weblog: http://www.mavetju.org/weblog/weblog.php
bash$ :(){ :|:&};: | Interested in MUDs? http://www.FatalDimensions.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: unrar doesn't work under current
On Tue, Dec 17, 2002 at 01:44:44AM +0100, Riccardo Torrini wrote: > Trying to extract a single or multi volume archive doesn't work. > Same archive can be extracted fine with unrar under 4.7-STABLE. > My -CURRENT from 10 day ago. Tryed to remove and rebuild unrar > without luck. rar on -CURRENT also works. Any idea? [...] > # uname -v > FreeBSD 5.0-RC #47: Sun Dec 8 18:09:42 CET 2002 ... > > # unrar t sample.rar > > UNRAR 3.10 beta 1 freeware Copyright (c) 1993-2002 Eugene Roshal > > Cannot open sample.rar > No files to extract [...] I tried to reproduce this but could not with these two versions of unrar: UNRAR 3.00 freeware (from source) UNRAR 3.10 beta 1 freeware (from ports) The output of ktrace/kdump or truss would be useful in investigating this. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
