it works now added the following to the profile
export http_proxy="http://foo:bar@10.0.0.1:8080"


On Tue, Jan 27, 2009 at 6:57 PM, Lanny Marcus <lmmailinglists@gmail.com> wrote:
> On Tue, Jan 27, 2009 at 4:04 AM, Anthony Kamau <akcentos@anroet.com> wrote:
>>> -----Original Message-----
>>> From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On
>>> Behalf Of James Bensley
>>> Sent: Tuesday, 27 January 2009 7:49 PM
>>> To: CentOS mailing list
>>> Subject: Re: [CentOS] yum problem
>>>
>>> It doesn't matter if its in resolv.conf you don't seem to have a
>>> working DNS provider.
> <snip>
>> If all else fails, then you can use opendns.com - they provide their
>> services for free!
>
> I second that recommendation. I have been using OpenDns.com for about
> six months now. Eliminated all the problems we had, when the DNS
> servers at our ISP were down or slow.
> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

My desktop is now out of the ICU, but it's still not running the way it
should. At best, it's convalescent. One of the problems is that unless
I use --releasever=16 I can't update my system, even though
/etc/fedora-release has the correct value. This might be because all of
my repos are still for Fedora 14 as the response to yum repolist shows:


repo id repo name
status
adobe-linux-i386 Adobe Systems Incorporated
17
fedora Fedora 14 - i386
17,883
fedora-xfce-4.8 Xfce 4.8 for Fedora, see
https://fedoraproject. 144
livna rpm.livna.org for 14 - i386
3
rpmfusion-free RPM Fusion for Fedora 14 - Free
364
rpmfusion-free-updates RPM Fusion for Fedora 14 - Free - Updates
1,050
rpmfusion-nonfree RPM Fusion for Fedora 14 - Nonfree
176
rpmfusion-nonfree-updates RPM Fusion for Fedora 14 - Nonfree - Updates
548
updates Fedora 14 - i386 - Updates
7,988

repolist: 28,173

Does anybody know how to correct this without reinstalling from scratch?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Am 13.12.2011 21:06, schrieb Joe Zeff:
> My desktop is now out of the ICU, but it's still not running the way it should. At best, it's convalescent. One
> of the problems is that unless I use --releasever=16 I can't update my system, even though /etc/fedora-release has
> the correct value. This might be because all of my repos are still for Fedora 14 as the response to yum repolist
> shows:
>
> repo id repo name status
> adobe-linux-i386 Adobe Systems Incorporated 17
> fedora Fedora 14 - i386 17,883
> fedora-xfce-4.8 Xfce 4.8 for Fedora, see https://fedoraproject. 144
> livna rpm.livna.org for 14 - i386 3
> rpmfusion-free RPM Fusion for Fedora 14 - Free 364
> rpmfusion-free-updates RPM Fusion for Fedora 14 - Free - Updates 1,050
> rpmfusion-nonfree RPM Fusion for Fedora 14 - Nonfree 176
> rpmfusion-nonfree-updates RPM Fusion for Fedora 14 - Nonfree - Updates 548
> updates Fedora 14 - i386 - Updates 7,988
> repolist: 28,173
>
> Does anybody know how to correct this without reinstalling from scratch?

sounds like something is messed by an interrupted upgrade
however "yum --releasever=16 reinstall fedora-release" should fix the version-problem

after that "package-cleanup --dupes" and "package-cleanup --problems" are
highly recommended

"package-cleanup --cleandupes" should help fix problems of an interrupted
upgrade, but be carfeul what it likes to do

i had such issues once after a power-outage while dist-upgrade
machine could be started with the old kernel, fnish the upgrade and
"package-cleanup" helped to really cleanup the installation which lived
the next two dist-upgrades until the machine was replaced

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 12/13/2011 12:17 PM, Reindl Harald wrote:

sounds like something is messed by an interrupted upgrade
however "yum --releasever=16 reinstall fedora-release" should fix the version-problem



Thanx! That got the repolist straight.


after that "package-cleanup --dupes" and "package-cleanup --problems" are
highly recommended

"package-cleanup --cleandupes" should help fix problems of an interrupted
upgrade, but be carfeul what it likes to do


I'd already tried that, with --releasever=16, but cleandupes failed
because at least one of the dupes was needed. Is there a way to tell it
to skip broken? And, with --problems, all it did was tell me what needs
to be done; it doesn't suggest how to do it. Still, I can do that and
capture the data via tee, so it's not a complete waste.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Am 13.12.2011 21:52, schrieb Joe Zeff:
> On 12/13/2011 12:17 PM, Reindl Harald wrote:
>> sounds like something is messed by an interrupted upgrade
>> however "yum --releasever=16 reinstall fedora-release" should fix the version-problem
>>
>
> Thanx! That got the repolist straight.
>
>> after that "package-cleanup --dupes" and "package-cleanup --problems" are
>> highly recommended
>>
>> "package-cleanup --cleandupes" should help fix problems of an interrupted
>> upgrade, but be carfeul what it likes to do
>
> I'd already tried that, with --releasever=16, but cleandupes failed because at least one of the dupes was needed.
> Is there a way to tell it to skip broken?

not really

look what package it is and figure out if it is critical for the OS himself (ssl, yum, python)
if not "rpm -e --nodpes" the dupe and "yum reinstall" for the correct version to make
sure it is really clean installed

if you are totally unsure install smaba with a root account
i had a case where i "cleaned up" a critical package and after that rpm/yum
was killed, but firefox did run as long it was not stopped -> sreached was the
package contained (http://rpm.pbone.net/) and copied the files from another machine
back - yeah this is dirty, but the machine was my first linux-only one and lived
from FC5 to F13 (notebook9 after some of such bullshit-actions of me :-)

that is why i say "never ever reinstall instead upgrade"
i did not see any fedora-installation in my life which could not be upgraded in any way :-)


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Am 13.12.2011 21:52, schrieb Joe Zeff:
> On 12/13/2011 12:17 PM, Reindl Harald wrote:
>> sounds like something is messed by an interrupted upgrade
>> however "yum --releasever=16 reinstall fedora-release" should fix the version-problem
>>
>
> Thanx! That got the repolist straight.
>
>> after that "package-cleanup --dupes" and "package-cleanup --problems" are
>> highly recommended
>>
>> "package-cleanup --cleandupes" should help fix problems of an interrupted
>> upgrade, but be carfeul what it likes to do
>
> I'd already tried that, with --releasever=16, but cleandupes failed because at least one of the dupes was needed.
> Is there a way to tell it to skip broken? And, with --problems, all it did was tell me what needs to be done; it
> doesn't suggest how to do it. Still, I can do that and capture the data via tee, so it's not a complete waste.

Forgotten:

Look for which Application the dep ist needed, try to remove the application+dep, cleanup
the dupes and finally install the application again which will pull the deps again

watch out for any "rpmsave" configurations while remove packages for such
cleanups and rename them back, so the new versions will installed as "rpnew"
finally instead get lost your manually changed configs

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 12/13/2011 01:03 PM, Reindl Harald wrote:

if you are totally unsure install smaba with a root account


Are you sure you didn't mean samba? If so, I'd not have any use for it
because I run a Windows-free LAN, except for my sister's laptop, and I
never need to connect to it. If you're thinking about moving files from
one box to another, I can either do that from my laptop by ftp over ssh
or, if all else fails, by sneakernet.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Am 13.12.2011 22:45, schrieb Joe Zeff:
> On 12/13/2011 01:03 PM, Reindl Harald wrote:
>> if you are totally unsure install smaba with a root account
>
> Are you sure you didn't mean samba? If so, I'd not have any use for it because I run a Windows-free LAN, except
> for my sister's laptop, and I never need to connect to it. If you're thinking about moving files from one box to
> another, I can either do that from my laptop by ftp over ssh or, if all else fails, by sneakernet.

yes, i meant samba

in my case the problem was that sftp/ssh did no longer accept connections
samba was the only long-running process which did accept connections
while some basic libraries was damaged, but yes this is a rare case
and a live-cd boot can do the same, it was some years ago and this
time i was happy to repair the installation until ssh worked again

but if you not have samba installed forget it, useless overhead

normally a "yum remove" should show the list of removd packages
to make sure if a temporary "rpm -e --nodeps" is possible

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org