Re: [Mageia-dev] urpmi - strange read lock messages

2013-04-08 Thread Colin Guthrie
'Twas brillig, and Nicolas Lécureuil at 05/04/13 23:11 did gyre and gimble:
> Le vendredi 5 avril 2013 23:48:08 Jose Jorge a écrit :
>> Le 05/04/2013 14:29, Robert Fox a écrit :
>>> Thanks the point - I never aborted.  Assuming I did, is there a way to
>>> clean this up?  Rebuild rpm database??
>>
>> I get this warnings each time MageiaUpdate applet after was used, then
>> urpmi is used.
> 
> i NEVER reproduced .But, using your testcase i can.

Yeah, I frequently get these messages. I also use a mix of MageiaUpdate
and urpmi directly.

Col


-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/


Re: [Mageia-dev] urpmi - strange read lock messages

2013-04-05 Thread Nicolas Lécureuil
Le vendredi 5 avril 2013 23:48:08 Jose Jorge a écrit :
> Le 05/04/2013 14:29, Robert Fox a écrit :
> > Thanks the point - I never aborted.  Assuming I did, is there a way to
> > clean this up?  Rebuild rpm database??
> 
> I get this warnings each time MageiaUpdate applet after was used, then
> urpmi is used.

i NEVER reproduced .But, using your testcase i can.


Re: [Mageia-dev] urpmi - strange read lock messages

2013-04-05 Thread Jose Jorge

Le 05/04/2013 14:29, Robert Fox a écrit :

Thanks the point - I never aborted.  Assuming I did, is there a way to
clean this up?  Rebuild rpm database??


I get this warnings each time MageiaUpdate applet after was used, then 
urpmi is used.


Re: [Mageia-dev] urpmi - strange read lock messages

2013-04-05 Thread Robert Fox
On Fri, 2013-04-05 at 15:26 +0300, Thomas Backlund wrote:
> Robert Fox skrev 5.4.2013 15:23:
> > This is still occurring in latest Cauldron - I know the messages are
> > harmless, but maybe they should be suppressed?
> >
> 
> You shouldn't get read lock messages unless you manually have aborted 
> urpmi...
> 
> --
> Thomas
> 
> 

Thanks the point - I never aborted.  Assuming I did, is there a way to
clean this up?  Rebuild rpm database??

Cheers,
R.Fox




Re: [Mageia-dev] urpmi - strange read lock messages

2013-04-05 Thread Thomas Backlund

Robert Fox skrev 5.4.2013 15:23:

This is still occurring in latest Cauldron - I know the messages are
harmless, but maybe they should be suppressed?



You shouldn't get read lock messages unless you manually have aborted 
urpmi...


--
Thomas




[Mageia-dev] urpmi - strange read lock messages

2013-04-05 Thread Robert Fox
This is still occurring in latest Cauldron - I know the messages are
harmless, but maybe they should be suppressed?

Cheers,
R.Fox




Re: [Mageia-dev] urpmi - strange read lock messages

2013-02-11 Thread Barry Jackson

On 11/02/13 20:48, Marcus Zurhorst wrote:

Barry Jackson  writes:



On 10/02/13 14:27, Thierry Vignaud wrote:

On 10 February 2013 15:24, Barry Jackson  wrote:

I see this in a clean new installation of Cauldron (net install x86_64)
updated today. (although I saw this before the update).
Happens with any package.


You didn't C^c urpmi?


Not as I recall, however I now cannot reproduce.
If it recurs I will take better notes ;)





I see the same messages on my Cauldron installation since some days.
I just googled it and found several references in the Fedora bugzilla.
E.g.  https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=860500

What exactly does "C^c" mean, I don't get this?


Regards,
  Marcus





I understood him to be asking if I had interrupted a urpmi process by 
using CTRL/c.


Re: [Mageia-dev] urpmi - strange read lock messages

2013-02-11 Thread Marcus Zurhorst
Barry Jackson  writes:

> 
> On 10/02/13 14:27, Thierry Vignaud wrote:
> > On 10 February 2013 15:24, Barry Jackson  wrote:
> >> I see this in a clean new installation of Cauldron (net install x86_64)
> >> updated today. (although I saw this before the update).
> >> Happens with any package.
> >
> > You didn't C^c urpmi?
> >
> Not as I recall, however I now cannot reproduce.
> If it recurs I will take better notes ;)
> 
> 


I see the same messages on my Cauldron installation since some days.
I just googled it and found several references in the Fedora bugzilla.
E.g.  https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=860500

What exactly does "C^c" mean, I don't get this?


Regards,
 Marcus






Re: [Mageia-dev] urpmi - strange read lock messages

2013-02-10 Thread Barry Jackson

On 10/02/13 14:27, Thierry Vignaud wrote:

On 10 February 2013 15:24, Barry Jackson  wrote:

I see this in a clean new installation of Cauldron (net install x86_64)
updated today. (although I saw this before the update).
Happens with any package.


You didn't C^c urpmi?


Not as I recall, however I now cannot reproduce.
If it recurs I will take better notes ;)



[Mageia-dev] urpmi - strange read lock messages

2013-02-10 Thread Barry Jackson
I see this in a clean new installation of Cauldron (net install x86_64) 
updated today. (although I saw this before the update).

Happens with any package.

[baz@localhost ~]$ su
Password:
[root@localhost baz]# urpmi kate
BDB2053 Freeing read locks for locker 0xc63: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc65: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc66: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc67: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc68: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc69: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc6a: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc6b: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc6c: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc6d: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc6e: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc6f: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc70: 2497/140611879974656
BDB2053 Freeing read locks for locker 0xc37: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc39: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc3a: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc3b: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc3c: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc3d: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc3e: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc3f: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc40: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc41: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc42: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc43: 2497/140593642727168
BDB2053 Freeing read locks for locker 0xc44: 2497/140593642727168
To satisfy dependencies, the following packages are going to be installed:
  PackageVersion  Release   Arch
(medium "Core Release (zmrepo1)")
  kate   4.10.0   1.mga3x86_64
  kate-handbook  4.10.0   1.mga3noarch 
(suggested)

  ktexteditor4.10.0   1.mga3x86_64
  lib64kateinterfaces4   4.10.0   1.mga3x86_64
6.6MB of additional disk space will be used.
1.4MB of packages will be retrieved.
Proceed with the installation of the 4 packages? (Y/n)