Ubuntu 16.04 LTS Upgrade Failing

apt is showing an update for owncloud server (community version) (Ubuntu Server 16.04) is available however when I run the update it cannot find file locations. Has the ppa changed? I've checked the owncloud site and it's still pointing to download.owncloud.org however when I browser threre I get a redirect to main site.

Error messages is this:

Err:1 http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04  owncloud 10.0.0-1.1
  404  Not Found [IP: 80]
Err:2 http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04  owncloud-files 10.0.0-1.1
  404  Not Found [IP: 80]
Err:3 http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04  owncloud-deps-php7.0 10.0.0-1.1
  404  Not Found [IP: 80]
E: Failed to fetch http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04/./all/owncloud_10.0.0-1.1_all.deb  404  Not Found [IP: 80]

E: Failed to fetch http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04/./all/owncloud-files_10.0.0-1.1_all.deb  404  Not Found [IP: 80]

E: Failed to fetch http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04/./all/owncloud-deps-php7.0_10.0.0-1.1_all.deb  404  Not Found [IP: 80]


If this is a productive environment please wait for the release of 10.0.1 or 10.0.2 before doing any upgrades as advised in [1]. Until that time they probably have fixed the repositories.

Disclaimer: for production systems we recommend to wait for the first update release. it is to be expected in about 4 weeks.

[1] https://owncloud.org/blog/introducing-owncloud-x/

It's not a production environment. Purely for personal use however I'll wait until the ppa is working properly again as I don't wan to manage the updates myself.


Personal use is also productive use / environment :slight_smile: Its just a term to differ between:

"productive" where you can't loose any data or don't want to risk that the installation doesn't work anymore

"testing" where you don't care if something is breaking

@kljhlkhglklfgh, something is amiss here, I think. I'm getting this error too; since I'm just using the recommended PPA on Xenial, I take the fact that apt attempts to update owncloud-deps-php7.0 to mean that it has been configured to offer that update, as part of the stable release.

Or else, I might have some misunderstanding? If I understand correctly, the recommended update method on Ubuntu is to use apt as packages become available, then occ to configure those updates. Remarks?

Just wait until they have fixed the repositories as already pointed out above. Also make sure that you're not upgrading a productive environment to 10.0.0 and wait for 10.0.1 or 10.0.2 as also pointed out above.

It wasn't clear to me that that's what you were saying, that there's a bug in the repository. Especially when you follow that up with a warning not to upgrade to 10.0 until it's out of beta, because that shouldn't be a concern if the expected behavior of the repositories is not to offer it up until then.

If there is an active step users should take to avoid having their production server upgraded to 10.0 RC1, who are using the stable repository, please correct me.

That's a good point (you could consider 10.0.0 as a very advanced RC version). Can you open a bug report on the bug tracker? https://github.com/owncloud/core/issues

Just so I understand, what's the expected behavior? Is 10.0 really not yet in the "stable" line?

There are normally beta versions and release candidates before, they are supposed to be tested thoroughly, so the 10.0.0 should be stable. Experience over the last versions has shown, that you should wait for the first updates of major versions on productive systems.

Some of the previous upgrades were quite messy and there has been some improvement. Why this time they are missing the LDAP module, and during the testing phase the marketplace was not available, is not really clear. They could just have waited one more week...

1 Like

But 10.0.0 should never have hit the "stable" release channel at [1]. This wasn't expected and they never did pushed the first release of a new major version there.

I think that was just a human mistake to push that release out that early.

[1] https://download.owncloud.org/download/repositories/stable/owncloud/

I never said that. I just recommended that you should wait to upgrade productive environments until 10.0 gets the first or second maintenance release 10.0.1/10.0.2 (which is valid for every software out there, not only ownCloud).

And after the waiting time they probably have sorted out the 404 issue initially reported in this thread.

1 Like

Again, this recommendation is confusing, because the uninitiated assumes untested software doesn't make it into the stable repository. Hence, one doesn't expect to make these decisions.

If what you intend to say is that even when software makes it into the stable repository, you suggest that users hold off on upgrading, then we need more information; which packages to defer? How to avoid having components of non-production-ready software installed on one's server?

See the previous comment:

There is nothing what you could have done from user side. They just made a mistake by releasing this version directly in the "stable" channel.

I'm not sure if I did it well, but it's done (issue 27775). Thank you.

@yoniy0 thanks for raising issue on the issue tracker. Just wanted to point out that for me I am already on 9.1.5 therefore you may have missed an intermediate update before this 10.0 failing one was released.

Please comment on GitHub, and let them know:

  1. Are you also using the stable PPA as upgrade path?
  2. Assuming so, when have you upgraded to 9.1.5? (I probably skipped updates for about 2 weeks, so it's possible 9.1.5 went up there before I got around to it.)
  3. Are you also seeing the upgrade to 10.0.0 now?

That's all I can think of, but (being completely inexperienced with this sort of thing) I imagine that could be helpful to the PPA maintainers.

For anyone having this issue, I found that running 'apt-get upgrade --fix-missing' or 'apt-get dist-upgrade --fix-missing' (I don't know why this works in this situation) causes update to bypass the ownCloud update, allowing other updates to go through.

This was actually causing updates to fail on several production systems that I maintain, but using the option allowed me to finish running other updates.

1 Like

Perhaps better than changing apt-get's behavior is to hold oC packages for the time being

sudo apt-mark hold owncloud owncloud-files owncloud-deps-php7.0

You can always view held packages with sudo apt-mark showhold, and release them with sudo apt-mark unhold <package>.

Also of note is that the "Stable" PPA actually includes releases that are in advanced beta, and aren't considered suitable for production setting. Consider following only production-ready major releases, by changing your sources list. On Ubuntu, e.g., that's likely at /etc/apt/sources.list.d/owncloud.list, and you can change it from

deb http://download.owncloud.org/download/repositories/stable/<version>/

to, e.g.,

deb http://download.owncloud.org/download/repositories/9.1/<version>/

How did I not know about this?
I've actually looked for commands that did this before, and never found them. Thank you, and yes, that would be better!

Stable repo now contains 9.1.5 again.

(I contend that most won't really want to use it anyway, since oC interprets "stable" to be consistent with software one shouldn't install in a production environment, but that's for each to decide on their own.)