Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8.0.2 packages missing in Debian repo #14850

Closed
jbiddy opened this issue Mar 12, 2015 · 37 comments

Comments

@jbiddy
Copy link

commented Mar 12, 2015

Steps to reproduce

  1. Have a working 8.0.0-9/8.0.1-1 install on Debian Wheezy
  2. Set up the package manager to point to the Debian Wheezy ownCloud OBS repo
  3. Run the upgrade through the package manager (apt-get update, apt-get upgrade)

Expected Behavior

apt-get should prompt you y/n to install new owncloud packages

Actual Behavior

apt-get returns "packages already up to date."

Server Configuration

Debian Wheezy fully updated

web server: apache 2.2.22

database: MariaDB 5.5.42

PHP version: 5.4.36

ownCloud version: 8.0.0-9/8.0.1-1

@blizzz

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2015

from OBS repo

cc @jnweiger

@jnweiger

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2015

No linux packages for 8.0.2 are released by now. QA approval pending.

@jbiddy

This comment has been minimized.

Copy link
Author

commented Mar 12, 2015

Oh darnet, thanks @blizzz that was the most important part and I forgot it! Fail for first issue report :(

@deMattin

This comment has been minimized.

Copy link

commented Mar 13, 2015

jnweiger commented:

No linux packages for 8.0.2 are released by now. QA approval pending.

It seems to be a good idea to check reliability of the package update very well.

jbiddy commented:

Oh darnet, thanks @blizzz that was the most important part and I forgot it! Fail for first issue report :(

I don't think, it's a fail because now we have an answer why there's no repo update... 😉

@jnweiger

This comment has been minimized.

Copy link
Contributor

commented Mar 13, 2015

The original plan was to announce Linux packages next week.
Sorry that tar-ball releases were announced earlier.

@jnweiger jnweiger self-assigned this Mar 13, 2015

@blizzz

This comment has been minimized.

Copy link
Contributor

commented Mar 13, 2015

@jbiddy no worries, i think @jnweiger would have guessed it either way. Next time ;)

@jbiddy

This comment has been minimized.

Copy link
Author

commented Mar 13, 2015

That is so okay! I am not in a hurry. I've just been getting the update is available message when I go into the WebUI. After ignoring it for a day I finally logged into the server via ssh and tried to do an update.

Anyway, thanks for letting us know what the situation is so quickly. We appreciate it :)

@shoeper

This comment has been minimized.

Copy link

commented Mar 14, 2015

The webui should then probably query another api to determine if there is a new version.

@jnweiger

This comment has been minimized.

Copy link
Contributor

commented Mar 15, 2015

Then the webui would also need to know the difference between a tar-ball installation and a deb/rpm installation.

Anyway, your package manager should tell you when there is an update available.

@deMattin

This comment has been minimized.

Copy link

commented Mar 15, 2015

I think it's usefull to get the information even though you update from repo.
For both installation variants you might have reasons to wait with the update and so the message should appear but hide itself after some seconds to not disturb usage of this account.

@shoeper

This comment has been minimized.

Copy link

commented Mar 15, 2015

@jnweiger the package manager is not the problem. The problem is the message in the web ui.

Furthermore upgrading via package manager is the recommended way but updates come out a week later.

Especially because this was in the announcement email.

The releases contain a lot of important and security fixes and improvements for ownCloud 8.
Update is strongly recommended!

It does not make sense to announce security fixes on the one hand and updating repositorys a week later on the other hand.

@ghost

This comment has been minimized.

Copy link

commented Mar 15, 2015

If you're using your package manager just disable the update check:

https://github.com/owncloud/core/blob/v8.0.2/config/config.sample.php#L428-L432

as you're getting the update via the package manager. That was something Debian had done with their own packages.

@deMattin

This comment has been minimized.

Copy link

commented Mar 15, 2015

But then we get no infos and checks any more.
As I mentioned above, the information is or can be also relevant for user of repositories.
Only a message timeout (per session) should be implemented.

@ghost

This comment has been minimized.

Copy link

commented Mar 15, 2015

@deMattin
It you think this should be implemented then i think you should create a new issue / feature request for this. Thats nothing what should be discussed in an issue about missing packages in a repo. :-)

@karlitschek

This comment has been minimized.

Copy link
Member

commented Mar 15, 2015

Well I think the best option is to provide the packages again at the same time as the tar/zip releases. We have to make this happen again.

@Akhenaton

This comment has been minimized.

Copy link

commented Mar 16, 2015

Yes ! Because actually if you go on the ownCloud.org download page it advertise version 8.0.2 but if you click on "Packages (for auto updates)" you'll get a 8.0.0.9 version.
https://owncloud.org/install/ ==> Latest stable version: 8.0.2

@enoch85

This comment has been minimized.

Copy link
Member

commented Mar 16, 2015

Well I think the best option is to provide the packages again at the same time as the tar/zip releases. We have to make this happen again.

Agree with you @karlitschek

@enoch85

This comment has been minimized.

Copy link
Member

commented Mar 17, 2015

Any update here? 8.0.2 has been official for like one week now. @jnweiger

@boltronics

This comment has been minimized.

Copy link

commented Mar 17, 2015

I just had to disable the update warning notification. It was getting really annoying. Still feeling nervous about not having security patches applied. Security issues should not be announced by a project if patched packages are not yet available!

@jackyes

This comment has been minimized.

Copy link

commented Mar 18, 2015

"No linux packages for 8.0.2 are released by now. QA approval pending."

@jnweige does it take more than 5 days? it's the first time i use the auto update package...is it normal that it takes so long?

@deMattin

This comment has been minimized.

Copy link

commented Mar 18, 2015

In the past the suse repository updates often have been faster than the official announcements!

But it would be nice to get a short status, if there is a reason for this delay.
A working and proved update is better than a fast update with errors!

(Ok, fast AND working update would be best)

@jackyes

This comment has been minimized.

Copy link

commented Mar 18, 2015

Yes! working is better....better late than never

@jnweiger

This comment has been minimized.

Copy link
Contributor

commented Mar 18, 2015

Sorry for the long delay here. Today I saw that the test results are all good. I hope for a go-ahead today or tomorrow.

@deMattin I fully agree: 'fast and working' is the goal next time!

@cortopy

This comment has been minimized.

Copy link

commented Mar 18, 2015

I'm experiencing all these issues in Ubuntu too. I've opened a bug issue about the messaging system and the inaccuracy in the docs

#14990

Apart from that, looking forward to the update. Thanks @jnweiger !!

@jnweiger jnweiger closed this Mar 18, 2015

@etiess

This comment has been minimized.

Copy link

commented Mar 18, 2015

@etiess

This comment has been minimized.

Copy link

commented Mar 18, 2015

OK, now it works :)

@jnweiger

This comment has been minimized.

Copy link
Contributor

commented Mar 18, 2015

@etiess the build service was slow with publishing.... thanks for double-checking!

@enoch85

This comment has been minimized.

Copy link
Member

commented Mar 18, 2015

apt-get update
apt-get upgrade

Doesn't work on Ubuntu 14.04. Did I miss something here?

EDIT

Never mind, all ok now. Thanks.

@boltronics

This comment has been minimized.

Copy link

commented Mar 19, 2015

Thanks @jnweiger for fixing this. Downloading the update now (for Debian).

@JB1985

This comment has been minimized.

Copy link

commented Mar 19, 2015

.htaccess file has the wrong version. Please upload the correct version. Maybe you forgot to replace it after updating?

Who have the new .htaccess? I dont have overwrite it :(

@ghost

This comment has been minimized.

Copy link

commented Mar 19, 2015

Who have the new .htaccess?

Github :)

https://github.com/owncloud/core/blob/v8.0.2/.htaccess

@JB1985

This comment has been minimized.

Copy link

commented Mar 19, 2015

Ok, I have download it from the sources.

@ghost

This comment has been minimized.

Copy link

commented Mar 19, 2015

@JB1985 Btw. if the .htaccess file wasn't overwritten during the package update from 8.0.0 to 8.0.2 consider to create a new issue for this to avoid that you're getting the same at the next update.

@daryltucker

This comment has been minimized.

Copy link

commented May 28, 2015

I just want to mention, after having upgraded through various means and having installed owncloud through various means, that it is extermely frustrating to move to the recommended method (ie: System Package Manager), and attempt to update via the recommended method (ie: System Package Manager), for ownCloud to refuse connections until a release which is not yet available through my package manager is installed on my system. phew!

Please think about providing checks for various channels, as well as continuing to provide web access before an upgrade (ie: Do not alert about an update that is available on another channel (git/source) that is not yet available on your current channel).

I am also experiencing issues with API access, but I can't imagine ownCloud would refuse API connections if it is out of date... or would it?

I appreciate all that you guys are doing and I hope this comes across as constructive.

Debian 8

Edit:

I'm sorry, maybe I have a misunderstanding. Even after upgrading through a package manager (apt), does one need to run ./occ upgrade? If so, most systems will not let you run the script as www-data, as that user doesn't have a shell. I was forced to give it a shell, su, and then remove shell for that user.

@jnweiger

This comment has been minimized.

Copy link
Contributor

commented May 29, 2015

@daryltucker An equivalent of occ upgrade is triggered, when a user visits the web page after the upgrade was installed. The first user to do so is presented with a dialog that should look like this:

ownCloud will be updated to version 8.1 beta 2.
Please make sure that the database, the config folder and the data folder have been backed up before proceeding.
[Start update]
To avoid timeouts with larger installations, you can instead run the following command from your installation directory:
./occ upgrade

That should get the update going. As an alternative to clicking [Start update], The following shell command should work on ubuntu to perform the update (without adding a shell to www-data):

sudo -u www-data php /var/www/owncloud/occ upgrade
@daryltucker

This comment has been minimized.

Copy link

commented Jun 4, 2015

Thanks for the clarification and tips, @jnweiger

@lock lock bot locked as resolved and limited conversation to collaborators Aug 11, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
You can’t perform that action at this time.