On 2015-05-11 16:52, Kevin Fenzi wrote:
OK, I'll wait until I see that announcement here then, no big deal
for me.
Things should be back to normal now since last night. ;)
confirmed, thanks.
Marco
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription opti
On Mon, 11 May 2015 08:57:59 +0200
"M. Fioretti" wrote:
> On 2015-05-10 17:58, Kevin Fenzi wrote:
> > There's an issue with the f20 updates repo metalink in
> > mirrormanager.
> >
> > We were hoping to have it fixed up quickly, but it's of course
> > proving more difficult than it seems at first
On 2015-05-10 17:58, Kevin Fenzi wrote:
There's an issue with the f20 updates repo metalink in mirrormanager.
We were hoping to have it fixed up quickly, but it's of course proving
more difficult than it seems at first. ;(
Anyhow, folks are working on it, and we hope to have it fixed later
toda
I do believe we all appreciate your efforts very much Kevin and all!!!
I often see “trying another mirror” for various reasons as I do “sudo yum
update” when I boot to the F20 drives (most often flash or mSATA SSD
converted to USB). My thinking has been that mirror management is a slow
and ongoi
There's an issue with the f20 updates repo metalink in mirrormanager.
We were hoping to have it fixed up quickly, but it's of course proving
more difficult than it seems at first. ;(
Anyhow, folks are working on it, and we hope to have it fixed later
today.
I'd suggest just waiting to grab up
Same problem here - results in no working mirrors apparently found so reads
no updates needed (for many days on one machine). I hope it is a mirror
management glitch they fix soon but if otherwise may they let us know.
On Sun, May 10, 2015 at 6:49 AM, M. Fioretti wrote:
> Greetings,
>
> I have,
Greetings,
I have, on a Fedora 20 x86_64 box, "yum update" failing with
lots of messages like the one in the subject, and others like:
ftp://ftp.ciril.fr/pub/linux/fedora/linux/updates/20/x86_64/repodata/repomd.xml:
[Errno -1] repomd.xml does not match metalink for updates
Trying other mirror.
> For future reference The reason you had to execute the commands
one by one is due to the nature of the one line command given to you.
> The && in the one liner is a conditional. The next command in line
will only be executed if the previous command returns an exit code of 0.
> If you want t
On 10/16/14 20:51, William wrote:
> The solution provided by Alchemist worked, though each command had to be
> entered separately like this:
>
> pkill yum
> pkill rpm
> rm -rf /var/lib/rpm/__db.00*
> rpmdb --rebuilddb
> sync
>
> rather than all on one command line.
For future reference
The
On 10/15/2014 02:48 PM, William wrote:
I have F20 on a 64-bit system. I'm a home user with no sysadmin
training and no real sysadmin experience. I tried to do my weekly
patches, and got this:
bash.6[~]: yum update
error: rpmdb: BDB0113 Thread/process 2156/140591811774272 failed:
BDB1507 Thr
>/ Follow-up question...
/> >/ I know that the packages on my work station came from at least two
/> >/ repositories. I don't recall which. I have a graphics card driver
which I
/> >/ think came from an external(?) repository. I have "xeyes", "xv", and
/> >/ "xcdroast", which also might
2014-10-15 23:31 GMT+03:00 William :
> I have F20 on a 64-bit system. I'm a home user with no sysadmin training
>> and no real sysadmin experience. I tried to do my weekly patches, and got
>> this:
>>
>> bash.6[~]: yum update
>> error: rpmdb: BDB0113 Thread/process 2156/140591811774272 failed: B
I have F20 on a 64-bit system. I'm a home user with no sysadmin
training and no real sysadmin experience. I tried to do my weekly
patches, and got this:
bash.6[~]: yum update
error: rpmdb: BDB0113 Thread/process 2156/140591811774272 failed:
BDB1507 Thread died in Berkeley DB library
error: d
On Wed, 15 Oct 2014 14:48:51 -0400 William wrote:
> Good afternoon,
>
> I have F20 on a 64-bit system. I'm a home user with no sysadmin
> training and no real sysadmin experience. I tried to do my weekly
> patches, and got this:
>
> bash.6[~]: yum update
> error: rpmdb: BDB0113 Thread/proce
2014-10-15 21:48 GMT+03:00 William :
> Good afternoon,
>
> I have F20 on a 64-bit system. I'm a home user with no sysadmin training
> and no real sysadmin experience. I tried to do my weekly patches, and got
> this:
>
> bash.6[~]: yum update
> error: rpmdb: BDB0113 Thread/process 2156/1405918117
Good afternoon,
I have F20 on a 64-bit system. I'm a home user with no sysadmin
training and no real sysadmin experience. I tried to do my weekly
patches, and got this:
bash.6[~]: yum update
error: rpmdb: BDB0113 Thread/process 2156/140591811774272 failed:
BDB1507 Thread died in Berkeley D
16 matches
Mail list logo
