Is there a fix for this? I just upgraded my entire setup and I'm stuck here.

_________________
R6.04, dual core 3ghz, 3 gig memory, Zotac 8400 passive heat sink dvi/hdmi out video, 500 gig sata, dual tuner hdhomerun, streamzap remote

Abby

Thanks tjc,

I did, here it is:

http://linhes.org/bugs/issues/762

This issue seems to only occur when running "sudo pacman -Syu".

Instead I ran "sudo linhes_upgrade.sh" and voila, no issues.


So what's the difference? Should I always use Cecil's script instead of calling pacman directly?

Thanks, -Abs

_________________
R6.04, dual core 3ghz, 3 gig memory, Zotac 8400 passive heat sink dvi/hdmi out video, 500 gig sata, dual tuner hdhomerun, streamzap remote

Abby

I got around this by:



Then started the update again. It was a week or two ago - so I think this was all I did!

Hope it helps.
Rob

Nice! I would say that is just the workaround people need.

COOOL!

Works like a charm thanks a bunch Rob!

Serge

I started having a problem with a pacman upgrade on a new install from the 6.02 cd.

Looks like this:


I tried linhes.org repos too, same result.

What causes this ? It worked on another machine a couple days ago ? ...

Working fine here:


Either km.net was down for a short while or something is wrong with your network connection.

_________________
Mike
My Hardware Profile

Thanks for ths sanity check...While it ran mythfilldatabase OK, I've had problems with the current nameserver of my cable co... I'll fiddle with that some.

Looks like a name server problem. Any time you see "resolver" or "DNS" or "host lookup" or any of a dozen similar messages it generally means the application was trying to look up (resolve) the IP address of the remote host and couldn't. Either because you have a bad address for your domain name server (DNS) somewhere, you can't find a path to the DNS, the DNS is dead or not responsive, the first tier DNS deferred the query upstream and didn't get a response, ...

Most ISPs have periodic DNS problems.

Since it was a new setup, I re-did the network in LinHes setup in service menu. It looked correct, but after re-doing the same nameserver address, it worked. I suspect an invisible character in the address...

Pacman =Syu promises to work now....


Thank You gentlemen, for pointing me the right way, as usual ...

The upgrade is not working for me. Any suggestions?

error: failed retrieving file 'mythtv-contrib-0.23-6-i686.pkg.tar.gz' from knoppmyth.net : Not Found
warning: failed to retrieve some files from extra
error: failed to commit transaction (Not Found)
Errors occurred, no packages were upgraded.

==

sudo pacman -U mythtv-contrib-0.23-7-i686.pkg.tar.gz
loading package data...
checking dependencies...
(1/1) checking for file conflicts [#####################] 100%
(1/1) upgrading mythtv-contrib [#####################] 100%

==


Proceed with installation? [Y/n] y
:: Retrieving packages from extra...
error: failed retrieving file 'mythtv-contrib-0.23-6-i686.pkg.tar.gz' from knoppmyth.net : Not Found
warning: failed to retrieve some files from extra
error: failed to commit transaction (Not Found)
Errors occurred, no packages were upgraded.

Check a previous post in this thread.



Then try again.

But I did do that. I just didn't show the wget portion, but I did post the results of the second part and then tried upgrading again with the same results.

Hi,


As far as I understand, standard repositories are all we need, as users. Rolling releases are pushed there. You are right, there is no easy way to compare the LinHES version running on our PVR against the last one available in standard repositories, as it is displayed nowhere in the Service Menu. The best way I found to check if my mythbox is synchronised with standard repositories, is by checking version number of LinHES-system and LinHES-config:



Regarding testing repositories, they are full of tempting stuff (in my case, up to date versions of Transmission and Xorg), but I doubt there is a safe way for the average user to take advantage of that.