Packages repository not found

[oparoz]

Trying to keep the VM up2date via apt I get this:

$ sudo apt-get update && sudo apt-get upgrade
Err http://download.opensuse.org  Packages
  404  Not Found [IP: 195.135.221.134 80]
W: Failed to fetch http://download.opensuse.org/repositories/isv:/ownCloud:/community:/8.1:/testing:/merged/xUbuntu_14.04/Packages  404  Not Found [IP: 195.135.221.134 80]

Sure enough, that repo is empty. Glitch with an older VM?

[karlitschek]

@jnweiger What is going on here?

[karlitschek]

@dragotin

[dragotin]

the url is wrong, the component merged does not make sense.

[oparoz]

Well, it doesn't matter if it doesn't make sense, it's part of the 8.1 VM. People using it can't cleanly update it with that sort of error in the sources.

So, has the sources list been modified for newer versions? Current users still need some documentation in order to fix this problem. 8.1 is not EOL yet.

[enoch85]

@jnweiger Wrong repos? https://github.com/owncloud/vm/blob/master/vagrant/oc8ce/build-ubuntu-vm.sh#L7-L10

[oparoz]

@enoch85 - Thanks for the link. It seems the problem was fixed via https://github.com/owncloud/vm/commit/49c0c54d65d61185f86492d5a8c7d91015cb9fbc

The general problem remains. How do you push these fixes to current users of the VM who supposedly are not IT pros and want to use a low maintenance VM to serve their ownCloud.

[enoch85]

@oparoz It's @jnweiger that handles the building of the appliance. Regarding the update, we could link my script without the activating of the apps. Right now, it's the normal update/upgrade procedure in Ubuntu, or via the Updater app.

[enoch85]

@oparoz To answer your question. How did all the other users do when the reops where changed? (They googled I suppose and found this where I decribe how to change the repos, it's also decribed in a blog post @jospoortvliet did for ownCloud that I can't find right now) Even I didn't know about the changed until I checked the repos. AFAIK there are no way unless there is a decision to keep the old repos as well, and that's not likely to happen. :/

[oparoz]

That's fine for fixing the current problems, but I'm thinking: How can we make sure it doesn't happen again? I'm putting myself in the shoes of users who wants to have ownCloud at home, but don't want to become sysadmins. There is probably a script included now which auto-updates the instance, but one day it stops working and they have to look for solution. Of course, there will always be bugs, but how can we be proactive and push fixes for these cases?

[enoch85]

@oparoz I agree with you. But since the repo change to owncloud, I don't think this will be an issue anymore, hence owncloud won't change repos now when they are on the owncloud server itself. Please correct me if you think otherwise.

[oparoz]

I have no idea, but let's close this until the next incident ;)

[enoch85]

@oparoz A solution would be to not install owncloud from the repos... Just for the record.

[jnweiger]

Changed subject. This was not about source code, this was a bout a wrong repository.

[oparoz]

:+1: