Unable to refresh repository on fresh 12.3 openSuse Desktop KDE version

Hi All,
I have spent days on this but I lost my patient on this matter :(.
I really need your precious help. I have installed suse on a virtual box veriosn 4.2.2 with 2cpu and as a x64.
I have tried lots of things which I found on this forum already.
I deleted almost all my repositories while I was trying to find a solution.
Currently I have these repositories

linux-ow27:~ # zypper lr -d

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

–±------------------±----------------------±--------±--------±---------±------±---------------------------------------------------------------------±-------
1 | openSUSE-12.3-1.7 | openSUSE-12.3-1.7 | No | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-VBOX_CD-ROM_VB2-01700376,/dev/sr0 |
2 | repo-non-oss | openSUSE-12.3-Non-Oss | No | Yes | 99 | yast2 | Index of /distribution/12.3/repo/non-oss |
3 | repo-oss | openSUSE-12.3-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/12.3/repo/oss

And I get the following errors:

Cannot access installation media
http://download.opensuse.org/distribution/12.3/repo/oss/│
(Medium 1).
Check whether the server is accessible.
Show details
URL tp://download.opensuse.org/distribution/12.3/repo/oss/
File ‘/media.1/media’ not found on medium 'http://download.opensuse.org/distribution/12.3/repo/oss/

By the way, I configure my proxy settings in yast, I disabled ipv6, I can find above files via friefox but I can’t find is with yast.

Regards,
Faonur

Hello and welcome here.

Please next time use CODE tags around your copied/pasted computer text. It is the # button in the toolbar of the post editor. I agree not obvious to find, thus we have to explain it to you.

Second is that, alltough it can be found by reading all of what you have, we prefer that you tell us to begin with that you use openSUSE 12.3.

Then we have a special (sub)forum for Virtualization. Are you sure you do not want to offer your problem to your fellow Virtualization users? That must mean that you are sure it has nothing to do with the fact that you use virtualization. Are you? I doubt. I, and IMHO most people, do not have problems using the standard repos, not using virtualization and/or proxy.

Please when, as an afterthought, you think that this would better go in Virtualization, then ask here for moving it (and do not double post there!).

Hi Henk van Velden,

First of all thank you for your quick response and suggestions. I will be more careful on that.

As you said I had checked the virtualization threads in the beginning before I submit my post but I thought they might be discussing how to virtualize machines on openSuSe rather than using virtualised version of openSuse. I thought it is rather a configuration problem. I am not sure which one suits best. But, if you think virtualization threads are more suitable it might be useful to move that section.

What I can see, the two repos you have are OK (except that the non-OSS is disabled). MIsing are the two Update repos and the (normaly switched off) debug and source repos).

As said the two you have do hav the correct URL. That means that IMHO it has somethingto do with your special environment (virtalization and yoy talk about proxy). I think this is better off in the Virtualization forum and it will be moved there.

Please everybodu, this is CLOSED for the moment.

Moved from Applications and open again.

On 2013-04-22 16:16, hcvv wrote:
>
> hcvv;2549948 Wrote:
>>
>> Please everybodu, this is CLOSED for the moment.
> Moved from Applications and open again.

Faonur, you mention that you use a proxy. This may be relevant.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

I would be very happy if one of our experienced friends can comment/answer about my question.

Disable others
and use these

Main Repository (NON-OSS) - http://download.opensuse.org/distribution/12.3/repo/non-oss/
Main Repository (OSS) - http://download.opensuse.org/distribution/12.3/repo/oss/
Update Repository (Non-Oss) - http://download.opensuse.org/update/12.3-non-oss/
Main Update Repository - http://download.opensuse.org/update/12.3/

and do

zypper clean --all
zypper ref -f

Typically,
I troubleshoot the error you posted in this manner…

  1. Open a web browser and attempt to browse to a website I have not visited before. This verifies a working network connection supporting a web protocol (http in this instance. Some repos are configured with ftp and others with http).

If you fail at this point, then you have a fundamental VBox or Host Network configuration problem.

If you are successful, then go to the next step

  1. Copy the repo URL into your web browser, this should verify you can reach the specified URI.

Re your original post…

  1. I notice you only have your oss repo enabled. First, you should have your non-oss repo enabled.
    I see that vazhavandan noticed what I also noticed about your missing repos, so either add through YAST or if you’re unable then I or someone else can post the “zypper ar” command to make sure you have your necessary repos (remember to do a “lr” afterwards to verify they’re enabled and optionally auto refresh).

HTH,
TSU

I am new to open suse. When I issue the command

zypper update
Following error message displays:

Download (curl) error for ‘http://repo.meego.com/MeeGo/builds/trunk/latest/repos/oss/ia32/packages/repodata/repomd.xml’:
Error code: Connection failed
Error message: Could not resolve host: repo.meego.com; Name or service not known

Abort, retry, ignore? [a/r/i/?] (a):

KIndly help me. Yast is also working. Is there any bug? DO i need to install SUSE again?

open YaST and disable Meego repos
Aalso post output of

zypper lr -d

within

 tags ,use "#" tag in post editor.

On 2013-05-07 04:06, avrs wrote:
>
> I am new to open suse. When I issue the command
>
> zypper update
> Following error message displays:

Ok, first, computer outputs like commands have to go inside code tags.
Advanced editor, ‘#’ button.
Posting in
Code Tags - A Guide

> Download (curl) error for
> ‘http://repo.meego.com/MeeGo/builds/trunk/latest/repos/oss/ia32/packages/repodata/repomd.xml’:
> Error code: Connection failed
> Error message: Could not resolve host: repo.meego.com; Name or service
> not known
>
> Abort, retry, ignore? [a/r/i/?] (a):
>
> KIndly help me. Yast is also working. Is there any bug? DO i need to
> install SUSE again?

It is normally best to post your problem into a new thread unless you
are absolutely sure that it is the same problem as the one in the first
post of the thread.

If we continue, we will get a mixtup of different problems with
different people.

Are you using virtualization? If so, what? If not, you are posting in
the wrong forum.

Then, the next step is seeing if you can open that file in a web
browser, like firefox. I can, so if you can not, you have a network
problem, and you should then go to the networking forum here.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On Tue, 07 May 2013 02:06:02 +0000, avrs wrote:

> repo.meego.com; Name or service not known
>
> Abort, retry, ignore? [a/r/i/?] (a):
>
> KIndly help me. Yast is also working. Is there any bug?

No, this is not a bug.

> DO i need to
> install SUSE again?

No, a reinstall won’t help.

The problem (indicated in the first quoted line above) is that
repo.meego.com” is not able to be resolved.

A quick check here with whois and nslookup shows that that domain name is
invalid. It doesn’t resolve, and that’s not a bug, that’s because the DNS
entry is no longer valid.

Remove that repository, and the problem will stop happening.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

Please, start a new thread of your own and do NOT hang your problem at the end of an old thread because:
. new threads will be advertised as such and thus draw the attention of many, a new post to an old thread will at the maximum be seen by those following that old thread;
. the resulting discussion in the mixed thread will be a mess.

And please the others that answered here to a new problem in an old thread. Please next time encourage the new OP in such a situation to start a new thread and do not add to the confusion.

And please do not post the same question in different threads. You are wasting people’s time.
Btw, I answered there:
https://forums.opensuse.org/english/get-technical-help-here/applications/486268-updated-today-now-error-could-not-create-python-scriptengine-widget-2.html#post2554541

On 2013-05-07 07:42, Jim Henderson wrote:

> A quick check here with whois and nslookup shows that that domain name is
> invalid. It doesn’t resolve, and that’s not a bug, that’s because the DNS
> entry is no longer valid.

It resolves fine here:



> cer@Telcontar:~> host repo.meego.com
> repo.meego.com has address 140.211.166.227
> cer@Telcontar:~> wget "http://repo.meego.com/MeeGo/builds/trunk/latest/repos/oss/ia32/packages/repodata/repomd.xml"
> asking libproxy about url 'http://repo.meego.com/MeeGo/builds/trunk/latest/repos/oss/ia32/packages/repodata/repomd.xml'
> libproxy suggest to use 'direct://'
> --2013-05-08 02:51:15--  http://repo.meego.com/MeeGo/builds/trunk/latest/repos/oss/ia32/packages/repodata/repomd.xml
> Resolving repo.meego.com (repo.meego.com)... 140.211.166.227
> Connecting to repo.meego.com (repo.meego.com)|140.211.166.227|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 3967 (3,9K) [text/xml]
> Saving to: `repomd.xml'
>
> 100%====================================================================================>] 3.967       --.-K/s   in 0,03s
>
> 2013-05-08 02:51:16 (139 KB/s) - `repomd.xml' saved [3967/3967]
>
> cer@Telcontar:~>


However:



cer@Telcontar:~> l repomd.xml
-rw-r--r-- 1 cer users 3967 Aug 24  2011 repomd.xml
cer@Telcontar:~> l repomd.xml


It is not openSUSE, by the way. The vendor string of the rpms is
“meego”, that’s a different distribution.


http://en.wikipedia.org/wiki/MeeGo

+++························

MeeGo was a Linux-based free mobile operating system project, which
lives on in a fork called Mer.[1] Primarily targeted at mobile devices
and information appliances in the consumer electronics market, MeeGo was
designed to act as an operating system for hardware platforms such as
netbooks, entry-level desktops, nettops, tablet computers, mobile
computing and communications devices, in-vehicle infotainment devices,
SmartTV / ConnectedTV, IPTV-boxes, smart phones, and other embedded
systems.[2] MeeGo is currently hosted by the Linux Foundation.[3]

The Linux Foundation canceled MeeGo in September 2011 in favor of
Tizen.[4] A new Finnish start-up, Jolla, announced in July 2012 that
they will pick up MeeGo’s community-driven successor Mer,[5] to develop
a new operating system called Sailfish OS, and launch a smartphone in
2013.[6]

························+±

So, why are we trying to solve a problem of a different distribution here?


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On 2013-05-07 09:46, hcvv wrote:

> Please, start a new thread of your own and do NOT hang your problem at
> the end of an old thread because:
> . new threads will be advertised as such and thus draw the attention of
> many, a new post to an old thread will at the maximum be seen by those
> following that old thread;
> . the resulting discussion in the mixed thread will be a mess.

Absolutely.

Even worse, Meego is a different distribution.

> And please the others that answered here to a new problem in an old
> thread. Please next time encourage the new OP in such a situation to
> start a new thread and do not add to the confusion.

I did, 22 hours ago :wink:


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On Wed, 08 May 2013 01:08:06 +0000, Carlos E. R. wrote:

> On 2013-05-07 07:42, Jim Henderson wrote:
>
>> A quick check here with whois and nslookup shows that that domain name
>> is invalid. It doesn’t resolve, and that’s not a bug, that’s because
>> the DNS entry is no longer valid.
>
> It resolves fine here:

Now it is resolving here. Odd.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C