We had one more of this in the Dutch forums. While we tried to help the OP there, he installed anew because of different other reasons. Thus we do not know if our suggestions were worthwhile.
The idea was that some mirror is broken. It was detected yesterday, but waiting for the mirror to recover until today did not help.
it’s good of you to provide a translation service for ignorant brits like me who only speak english !
well meaning suggestion are always worthwhile … and very welcome too!
that sounds like a great suggestion to me.
i’m not in a rush so i think i’ll give it a chance to be fixed on Monday morning
… besides, i’ve not told it to use a specific mirror (so i guess it must be using a default)
plus
i’ve not a clue how to change the setting
Well, I told (what I thought that are) the basics of it instead of translating the full discussion.
I also explained that our suggestions involved:
. waiting;
. going to another mirror.
As the first was done for about half a day and did not work and the second wasn’t tried by the OP there, there isn’t much more to say IMHO.
BTW the default mirror is different for different people depending on an algorithm that should find the one “nearest” to you (Internet wise). THus you indeed do not know which one you use.
The suggestion was to disable the current non-OSS in YaST > Software > Repo management (not to remove it, what we do is only a bypass). And then use e.g.
This could be the same as in the dutch forums -a solution isn’t there, the OP reinstalled-, but it could also be that the install medium is still in the repo list.
I had the same error with non-oss. I disabled it since I didn’t use much software from it, but after seeing this thread I decided to just pick a static mirror for it and it worked. I just replaced the default mirror with: Index of /pub/opensuse/opensuse/distribution/12.2/repo/non-oss
I’ve had this problem for a couple weeks now. My first reaction was to reinstall the system, but the problem was still there after the reinstall. I’ve just been skipping the non-oss repo during updates in the meantime although the process was becoming a bit annoying. When I copy and pasted the url for the repo ( Index of /distribution/12.2/repo/non-oss ) into firefox, I saw that I needed to descend from there into suse/repodata to find the repomd.xml. I tried adding those directories to the repo’s url but it didn’t work, but for some reason when I just add the suse directory with no trailing slash, I get successful results.
On 10/29/2012 02:26 PM, zaol wrote:
> ( ‘Index of
> /distribution/12.2/repo/non-oss’
> (http://download.opensuse.org/distribution/12.2/repo/non-oss/) ) into
> firefox, I saw that I needed to descend from there into suse/repodata to
> find the repomd.xml. I tried adding those directories to the repo’s url
> but it didn’t work, but for some reason when I just add the suse
> directory with no trailing slash, I get successful results.
by the way, this sure sounds like a bug against the server…some
(several) 12.2 user(s) should confirm and log it…
amazing!
many, MANY thanks for your help … it worked perfectly.
but that’s not all.
your reply - and the fact i managed to get it to work perfectly for me,
this has given me the confidence, the push, the drive, the additional understanding that i needed to get my network printer working.
don’t get me wrong, i had tried to get it working.
i have installed, un-installed & re-installed the printer at least 3 or 4 times.
everything i tried seemed to work fine. i could see the printer. i had a queue. i could send prints to the queue. it simply didn’t print!
i was going to post here asking for help … but i didn’t want to be asking for two truck loads of help at the same time.
it had even been a toss-up which of my problems i should ask for help with first.
now i don’t need. my printer works fine.
you’ve even saved me making another post.
happy you got it fixed, and VERY happy you found more confidence, but
one more comment on your
> get my network printer working. don’t get me wrong, i had
> tried to get it working. i have installed, un-installed &
> re-installed the printer at least 3 or 4 times.
big hint: this is Linux, generally it is dependable, reliable and
predictable…which means that while some other operating systems
routinely “fix themselves” in the standard and recommended process of
-install
-try
-uninstall
-reinstall
-try
-make changes
-try
-uninstall
-reinstall
-try
-repeat until it fixes itself
that process is usually a waste of time with dependable hardware and
software!!
that is, if you repeat the same steps over and over and over and do NOT
get the same results over and over and over then you MUST assume
something is WRONG!
either the hardware is broken;
or the hardware is intermittently broken;
or the software is broken;
or the software is intermittently broken;
or the phase of the moon or maybe sunspot activity is interfering with
and dislodging atoms in your ROM, RAM, CPU, GPU or whatever…
nah, i wasn’t doing the “other” os ‘bang your head against the wall and see if the right brick comes out’ thing.
and i knew that the hardware was working fine with ubuntu. it was obviously my [lack of] understanding.
i was trying the various choices for installing a network printer, i.e. tcp, idp, etc - well, as far as i could get before i tripped and fell.
i even tried playing with the printers config and it’s address in my router.
after your confidence boost i just did some of the same again, however, because of you, i was able to go further; i found the magic (port) number (9100); and even corrected what i could see was obviously (that’s me getting cocky) an error … and it worked.
no interference from any of the lunar deities.
no entrails of a goat.
not even a quick stroke of Schrödinger’s cat.
Sorry to drag up this old thread but it fixed my one box.
This problem was driving me nuts on my one machine and removing the trailing slash solved the problem here too. Where would one report such an error?
Curiously my other 3 openSUSE installs do not have this problem.