Bug 557913

I went into Yast and tried to do a manual download of updates and this is the message I got.
........................

Download failed:

    File '/content' not found on medium 'http://download.opensuse.org/repositories/openSUSE:/11.2:/NonFree/standard/'



History:

 -  [AbstractCommand.cc:195] URI=http://download.opensuse.org/distribution/11.2/repo/non-oss/suse/conten
...............................

Could you please attach y2logs according to http://en.opensuse.org/Bugs/YaST.
Thanks.

I tried to follow the directions on the link you provided.
This is what happened.....

steve@user-24-236-91-100:~> su
Password: 
user-24-236-91-100:/home/steve # save_y2logs /temp/y2logs.tgz
Saving y2logs to /temp/y2logs.tgz
tar: /temp/y2logs.tgz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
FATAL: Error creating archive /temp/y2logs.tgz
user-24-236-91-100:/home/steve #

Not sure how to proceed.
Do I need to be in a different file?

UPDATE - 
I removed/unchecked NonFree repositories from my Enabled and Autorefresh list in Yast.
This seems to have allowed auto updates to resume.
Since doing this I have received and installed application updates and kernel security updates.

You can manually compress /var/log/YaST2 to a  tar archive and attach it.
Such like: tar zcf /tmp/y2logs.tgz /var/log/YaST2/

I copied into Gnome Terminal what you gave me.
This is what I got - 

user-24-236-91-100:/home/steve # tar zcf /tmp/y2logs.tgz /var/log/YaST2/
tar: Removing leading `/' from member names
user-24-236-91-100:/home/steve # tar zcf tmp/y2logs.tgz var/log/YaST2/
tar: tmp/y2logs.tgz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: var/log/YaST2: Cannot stat: No such file or directory

I am not exactly sure what is "member names" and what is a command in this.
I have never seen/heard the term "member names" before.
Is that the same as file names?

Sorry to be so stupid.

There is already a y2log.tgz in your /tmp by your first command,please check.
"tar: Removing leading `/' from member names":this is a warning because you use the absolute path,not error.
You can avoid this warning by -P option:tar zcfP /tmp/y2logs.tgz /var/log/YaST2/,or use the relative path:
#cd /var/log
#tar zcf /tmp/y2logs.tgz YaST2/

Here is my latest adventures in command line....
Per your instruction I moved to /var/log and tested the -p option to see what would happen.
I used the -p syntax, you presented it as zcfP.
I have never seen that syntax before.
As you see, I did not try that method.
Anyway, nothing happened/worked.

user-24-236-91-100:/home/steve # cd /var/log

user-24-236-91-100:/var/log # tar zcf /tmp/y2logs.tgz YaST2/

user-24-236-91-100:/var/log # tar zcf -p /tmp/y2logs.tgz YaST2/

tar: Removing leading `/' from member names

user-24-236-91-100:/var/log # tar zcf /tmp/y2logs.tgz YaST2

user-24-236-91-100:/var/log # ls

acpid       faillog        mail.info       -p                 warn

apparmor    firewall       mail.warn       pk_backend_zypp    wtmp

audit       gdm            mcelog          pk_backend_zypp-1  Xorg.0.log

boot.log    krb5           messages        pm-powersave.log   Xorg.0.log.old

boot.msg    lastlog        NetworkManager  pm-suspend.log     YaST2

boot.omsg   localmessages  news            rpm-qa             zypp

ConsoleKit  mail           nscd.log        samba

cups        mail.err       ntp             scpm

user-24-236-91-100:/var/log # cd wtmp

bash: cd: wtmp: Not a directory

user-24-236-91-100:/var/log # faillog

user-24-236-91-100:/var/log # ls faillog

faillog

user-24-236-91-100:/var/log # cd YaST2

user-24-236-91-100:/var/log/YaST2 # ls

_dev_sda             macro_inst_initial.ycp  y2changes         y2logmkinitrd

_dev_sda2            mkinitrd.log            y2log             y2log.SuSEconfig

disk_sda             perl-BL-standalone-log  y2log-1           y2start.log

macro_inst_cont.ycp  volume_info             y2log_bootloader

user-24-236-91-100:/var/log/YaST2 # y2log

If 'y2log' is not a typo you can use command-not-found to lookup the package that contains it, like this:

    cnf y2log

user-24-236-91-100:/var/log/YaST2 # cd /log

bash: cd: /log: No such file or directory

user-24-236-91-100:/var/log/YaST2 # cd /var/log

user-24-236-91-100:/var/log # 

user-24-236-91-100:/var/log # cd YaST2

user-24-236-91-100:/var/log/YaST2 # cnf y2log

y2log: command not found                      

user-24-236-91-100:/var/log/YaST2 # 

/var/log showed a wtmp file, which I thought might be the tmp file/directory you were referring to.
When I tried to open it - no success.
Looking in Yast2, there are several y2log's listed.
I tried to open y2log but, as you see, it did not work.
I do not know the command to open these and look at them.
And none of them show any suffix like .tgz, so I don't know what I am looking at exactly.
What is the command to compress a file, and what is the command to attach it?

(In reply to comment #7)
> What is the command to compress a file

Ok,just do follow steps:
#cd /var/log/
#tar zcvf y2logs.tgz YaST2/
#ls 
you will find the file y2logs.tgz in your current directory.

>and what is the command to attach it?

There is a menu "add an attachment" on the left foot corner of this page.
Click this menu and submit the file /var/log/y2logs.tgz in your local machine.

Created attachment 331740 [details]
y2logs

Provided per instructions.
Hope this helps.

As noted above, since disabling the non-free repositories, I no longer see the error message and have received several application and security updates with no problems.  But Banshee is totally broken (will not play any type of file) and some of the codecs that might fix it may be in the non-free repositories.  So I would like to get this problem fixed.

Thanks.

The repo maybe update to http://download.opensuse.org/distribution/11.2/repo/non-oss/suse/.
I suggest you reinstall Banshell or open a new bug for Banshee.

Yesterday, I enabled the non-free repositories and checked Auto refresh, to see if anything had changed/been fixed.
Within a few hours I received the same error message that started this bug report.

After receiving the error message, I disabled the non-free repositories and turned off Auto refresh again.
A couple of new updates were received within a few hours and installed with no apparent problems. 
This means that this issue is NOT "resolved".

Regarding Banshee.
It worked on this machine on OS 11.1.
Now it is broken. (it will not play any type of file)
I submitted a bug - #555298 - on November 13, 2009, but so far, I have received no response and nothing has been done about it.
On the chance that the problem had been fixed in a subsequent update after the release of OS 11.2, I downloaded Banshee from their website two days ago.
It still does not work.

I am not happy with the support for this issue or that of Banshee.