All repositories are "bad"

opensuse v12.1

I went to check online updates today. ALL repositories are reported as “bad”. A typical message:

Bad media attach point: http://download.opensuse.org/distribution/12.1/repo/oss/

I can paste the URL into a browser and it connects just fine; there is no network error. How do I resurrect the repository connections?

On 2012-01-19 00:46, jimoe666 wrote:
>
> opensuse v12.1
>
> I went to check online updates today. ALL repositories are reported as
> “bad”. A typical message:

Using what software do you get that message?


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

I tried:
Yast :: Software :: Online Update
Yast :: Software :: Software Management
Yast :: Software :: Software Repositories

Had they been working OK previously?

What happens If you do

su -
zypper lu

Yes.

root:..lib/zypp> zypper lu
Bad media attach point: http://download.opensuse.org/distribution/12.1/repo/non-oss/

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

Please post result of

zypper lr -d
root:..sma-user1/diy> zypper lr -d
# | Alias                  | Name                       | Enabled | Refresh | Priority | Type   | URI                                                             | Service
--+------------------------+----------------------------+---------+---------+----------+--------+-----------------------------------------------------------------+--------
1 | openSUSE-12.1-12.1-1.4 | openSUSE-12.1-12.1-1.4     | Yes     | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-DVD_16X                      |        
2 | repo-debug             | openSUSE-12.1-Debug        | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/12.1/repo/oss/  |        
3 | repo-debug-update      | openSUSE-12.1-Update-Debug | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/12.1/                 |        
4 | repo-non-oss           | openSUSE-12.1-Non-Oss      | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.1/repo/non-oss/    |        
5 | repo-oss               | openSUSE-12.1-Oss          | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.1/repo/oss/        |        
6 | repo-source            | openSUSE-12.1-Source       | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/12.1/repo/oss/ |        
7 | repo-update            | openSUSE-12.1-Update       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.1/                       |        

My 12.1 x86-64 also started “Bad attach point” error yesterday… I’ve tried removing all the repositories and add them back… cant add them back.
Just like the original poster… I can paste the link in a browser and it works…
Anyone with suggestions?

I am having a different problem with the Update Repo. I keep a local mirror of the repos so I dont have 50 computers all trying to get through a firewall/proxy. When I tried to update a computer I just installed Tuesday I got a lot of “Wrong Digest” errors. I re-ran my mirrors and was seeing file shrunk or grew errors. I was pulling from ftp.anl.gov. I switched to osuosl.org. Mirror synced with not no errors. Still getting Digest errors on update.

Went to a computer that was already updated, opened Software Management and selected View Repositories. From that I selected Update Unconditionally from “All in this list”. Saw the same Digest Errors. I disabled the local Update repo and added the Update repo from openSUSE. I went back in to Software Magange and re select Unconditional Update. All packages came down ok except Dolphin, it gave a digest error. So I think some of the RPM’s are out of sync or are there are corrupt files in the Repos.

I did not have problem adding the Online Repo to my system.

Dave W

If it’s worked OK previously, it seems more likely to be something that has changed at your end than anything being wrong with the repos, a hypothesis which is further supported by the fact that there hasn’t been a reporting of this problem en mass.

Please post result of

uname -a
zypper ve
cat /etc/SuSE-release

I am sure something has changed here since the repositories themselves are accessible, and other computers here can access them to perform updates. The question is what? Or better, how can I resurrect a functioning system update function?

What is the “media attach point” that makes zypper is so dissatisfied?

user1> uname -a
Linux sma-station12l 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux

user1> zypper ve
Bad media attach point: http://download.opensuse.org/distribution/12.1/repo/non-oss/

Abort, retry, ignore? [a/r/i/?] (a): 
Repository 'openSUSE-12.1-Non-Oss' is out-of-date. You can run 'zypper refresh' as root to update it.
Bad media attach point: http://download.opensuse.org/distribution/12.1/repo/oss/

Abort, retry, ignore? [a/r/i/?] (a): 
Repository 'openSUSE-12.1-Oss' is out-of-date. You can run 'zypper refresh' as root to update it.
Bad media attach point: http://download.opensuse.org/update/12.1/

Abort, retry, ignore? [a/r/i/?] (a): 
Repository 'openSUSE-12.1-Update' is out-of-date. You can run 'zypper refresh' as root to update it.
Loading repository data...

Reading installed packages...

Dependencies of all installed packages are satisfied.
user1> 
user1> cat /etc/SuSE-release
openSUSE 12.1 (x86_64)
VERSION = 12.1
CODENAME = Asparagus

Try something for me:

Take a look at this: http://dl.dropbox.com/u/10573557/YaST%20level3/Level3%20boot%20and%20Yast.odp

If you boot that way. You can either start yast as the guide suggests or
Just try using zypper, Eg: zypper up (to run updates)

Just wondering if it works from that level

On 2012-01-20 05:56, jimoe666 wrote:
> What is the “media attach point” that makes zypper is so dissatisfied?

I don’t know, but I would look at the logs.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Googling “bad media attach point” turned up this: SLES 11 - Invalid Repositories - Bad media attach point.

I just downloaded filelist.xml.gz and libqt4 form openSUSE. There is a problem with the repodata files. See my post.

http://forums.opensuse.org/forums/english/get-technical-help-here/applications/471435-12-1-repo-data-incorrect.html

Dave W

Given that opensuse “went dark” in protest of SOPA/PIPA about the same time I’d suspect they have hosed the download.opensuse.org redirector or something on their end because I’m suddenly getting the same error on all my repo’s as well and I haven’t updated things in over a month.

On 2012-01-20 20:16, dwestf wrote:
>
> I just downloaded filelist.xml.gz and libqt4 form openSUSE. There is a
> problem with the repodata files. See my post.
>
> http://tinyurl.com/7ynqf57

… on which we asked questions you still have not replied to.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Today is 1/7/2014. I’m having this ‘bad attachment point’ problem also.

At this point I cannot reinstall Firefox to a SuSE 11.4 system. I’m using another working system to connect here.

SuSE repositories may have moved since my original install. I seem to be able to access all working and correctly addressed repositories on this working system.

On the non working system, my software installer shows available packages = installed packages. Firefox is not showing either as installed or as available. There are NO update or available packages. Only the installed packages. This working system shows numbers for ‘All Packages’, ‘Not Installed’, ‘Installed’, and ‘Upgrades’ so for that reason I believe there is nothing wrong with the correctly addressed repositories.

I get the ‘bad attachment point’ error whenever I try to access any repositories on the non working system.

So far, as near as I can tell, this is all related to the fact that I deleted the entire contents of my /tmp directory a few days ago.

This is as far as I’ve gotten so far. I’ll post more when I have a solution.

Support for openSUSE 11.4 was discontinued in November 2012. There have been no further updates or security patches, and most 11.4 repos will have been removed. I strongly suggest you upgrade to 12.3 or 13.1 ASAP. 13.1 will be supported long-term by the Evergreen Project, so it might be your best choice.

The other thing that’s curious and evidentiary, is that when the software manager or the repository manager are started, there is no offer to skip the refresh. I’m required to skip, abort, or retry each repository. At that time is when I get the bad attach point error.