ownCloud 9.0.2 with PHP 7
-
I get this error while updating:
--> Processing Dependency: php-mysql for package: owncloud-deps-php5-9.0.2-1.1.noarch Package php-mysql-5.4.16-36.el7_1.x86_64 is obsoleted by php-mysqlnd-7.0.6-3.el7.remi.x86_64 which is already installedThere appears to be a dependency error in the ownCloud package. It is looking for an obsoleted packaged. Should be easy to work around, but it would be nicer if it knew that the right package was there and did not cause automatic updating to fail.
This is RPM based install on CentOS 7 with PHP 7 added.
-
This is a new package added with ownCloud 9.0.2 that appears to exist only to remove compatibility with PHP 7 which was promoted with ownCloud 9. Why this new package was added is not clear, but it means that there are problems for anyone working with YUM and PHP 7.
-
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
This is a new package added with ownCloud 9.0.2 that appears to exist only to remove compatibility with PHP 7 which was promoted with ownCloud 9. Why this new package was added is not clear, but it means that there are problems for anyone working with YUM and PHP 7.
From what I've been seeing, they "just" have a horrible process in place to create the repository packages. It's been known since PHP 7 came out that php_mysql has been replaced with php_mysqlnd, so what's so hard about requiring either one instead of just the old one?
I'd really like to get this running on PHP7, but apparently it's gonna be a bit yet.
-
Where are you guys getting your accurate information about the repository packages?
-
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
Where are you guys getting your accurate information about the repository packages?
Personal experience with it in this case. Just try installing owncloud via the repository on CentOS with PHP7. It doesn't work.
-
@travisdh1 said in ownCloud 9.0.2 with PHP 7:
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
This is a new package added with ownCloud 9.0.2 that appears to exist only to remove compatibility with PHP 7 which was promoted with ownCloud 9. Why this new package was added is not clear, but it means that there are problems for anyone working with YUM and PHP 7.
From what I've been seeing, they "just" have a horrible process in place to create the repository packages. It's been known since PHP 7 came out that php_mysql has been replaced with php_mysqlnd, so what's so hard about requiring either one instead of just the old one?
I'd really like to get this running on PHP7, but apparently it's gonna be a bit yet.
On ownCloud 9.0.0 it was fine. Only died now.
-
@travisdh1 said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
Where are you guys getting your accurate information about the repository packages?
Personal experience with it in this case. Just try installing owncloud via the repository on CentOS with PHP7. It doesn't work.
I mean in general. I find that there is a lot of mixed information online and you can't rely on the company/group themselves admitting wrongdoing in a lot of cases.
-
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
@travisdh1 said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
Where are you guys getting your accurate information about the repository packages?
Personal experience with it in this case. Just try installing owncloud via the repository on CentOS with PHP7. It doesn't work.
I mean in general. I find that there is a lot of mixed information online and you can't rely on the company/group themselves admitting wrongdoing in a lot of cases.
I guess that I am not sure what you are asking, exactly. In this example, we are looking at the ownCloud repo failing because they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
-
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
@travisdh1 said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
Where are you guys getting your accurate information about the repository packages?
Personal experience with it in this case. Just try installing owncloud via the repository on CentOS with PHP7. It doesn't work.
I mean in general. I find that there is a lot of mixed information online and you can't rely on the company/group themselves admitting wrongdoing in a lot of cases.
I guess that I am not sure what you are asking, exactly. In this example, we are looking at the ownCloud repo failing because they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
What I mean is I can't take most websites at their word due to a lot of mixed information (Spiceworks is an example). Outside of me creating a VM and testing it myself I don't really know how to get accurate information regarding software packages. Some people say x some people say y. How do I know which is accurate to learn in a conceptual way?
-
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
Yes Scott, they are out to get you and break it on purpose.
-
@JaredBusch said in ownCloud 9.0.2 with PHP 7:
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
Yes Scott, they are out to get you and break it on purpose.
Are you saying that the package name is wrong, or that they made the package on accident?
The NAME of the package says what I just stated.
-
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
@travisdh1 said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
Where are you guys getting your accurate information about the repository packages?
Personal experience with it in this case. Just try installing owncloud via the repository on CentOS with PHP7. It doesn't work.
I mean in general. I find that there is a lot of mixed information online and you can't rely on the company/group themselves admitting wrongdoing in a lot of cases.
I guess that I am not sure what you are asking, exactly. In this example, we are looking at the ownCloud repo failing because they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
What I mean is I can't take most websites at their word due to a lot of mixed information (Spiceworks is an example). Outside of me creating a VM and testing it myself I don't really know how to get accurate information regarding software packages. Some people say x some people say y. How do I know which is accurate to learn in a conceptual way?
We aren't taking anyone at their word. We are getting the information from the thing itself. the repo contains the files, the files contain the info. We aren't "trusting" anyone, we are looking right at the issue.
-
Here is the package that has been added: owncloud-deps-php5
Deps is standard abbreviation for "depends" or "dependencies". It's name implies, and its behaviour implies, that its purpose is to introduce a PHP5 dependency.
-
And the package description supports that too:
Name : owncloud-deps-php5 Arch : noarch Version : 9.0.2 Release : 1.1 Size : 7.2 k Repo : ce_stable Summary : Dependencies for php5 URL : http://www.owncloud.org License : AGPL-3.0 and MIT Description : Dependencies for php5. -
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
@JaredBusch said in ownCloud 9.0.2 with PHP 7:
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
Yes Scott, they are out to get you and break it on purpose.
Are you saying that the package name is wrong, or that they made the package on accident?
The NAME of the package says what I just stated.
No, I am stating that you are intentionally using inflammatory verbiage in your description of the problem.
-
@JaredBusch said in ownCloud 9.0.2 with PHP 7:
No, I am stating that you are intentionally using inflammatory verbiage in your description of the problem.
Do you feel that it has another purpose other than enforcing PHP 5 instead of PHP 7? I'm unclear why you feel that it is inflammatory and/or incorrect. From what I can tell, they wanted to have a package that made sure that, for some reason, we are using PHP 5. The only other option that they had was PHP 7. So, from what I can tell in behaviour, name and description, this package adds nothing itself, it exists only to remove PHP 7 as an option.
I'm not in the slightest trying to be inflammatory, as far as I know that is the only way to describe what I think the intent is.
-
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
@travisdh1 said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
Where are you guys getting your accurate information about the repository packages?
Personal experience with it in this case. Just try installing owncloud via the repository on CentOS with PHP7. It doesn't work.
I mean in general. I find that there is a lot of mixed information online and you can't rely on the company/group themselves admitting wrongdoing in a lot of cases.
I guess that I am not sure what you are asking, exactly. In this example, we are looking at the ownCloud repo failing because they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
What I mean is I can't take most websites at their word due to a lot of mixed information (Spiceworks is an example). Outside of me creating a VM and testing it myself I don't really know how to get accurate information regarding software packages. Some people say x some people say y. How do I know which is accurate to learn in a conceptual way?
We aren't taking anyone at their word. We are getting the information from the thing itself. the repo contains the files, the files contain the info. We aren't "trusting" anyone, we are looking right at the issue.
I'm not directing it at anyone. I'm saying I see claims made online and I wanted to know where you guys get your information when it isn't spelled out. Sorry if I'm not being clear.
-
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
I'm not directing it at anyone. I'm saying I see claims made online and I wanted to know where you guys get your information when it isn't spelled out. Sorry if I'm not being clear.
We are looking at the software itself and seeing what it is doing. The repo information cannot be hidden or anything, because it has to be exposed for it to work with the package system.
-
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
@JaredBusch said in ownCloud 9.0.2 with PHP 7:
No, I am stating that you are intentionally using inflammatory verbiage in your description of the problem.
Do you feel that it has another purpose other than enforcing PHP 5 instead of PHP 7? I'm unclear why you feel that it is inflammatory and/or incorrect. From what I can tell, they wanted to have a package that made sure that, for some reason, we are using PHP 5. The only other option that they had was PHP 7. So, from what I can tell in behaviour, name and description, this package adds nothing itself, it exists only to remove PHP 7 as an option.
I'm not in the slightest trying to be inflammatory, as far as I know that is the only way to describe what I think the intent is.
yes, you are choosing to be intentionally confrontational
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
that appears to exist only to remove compatibility with PHP 7
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
In this example, we are looking at the ownCloud repo failing because they added a bad package to it whose sole purpose appears to be to break PHP7 compatibility.
-
@scottalanmiller said in ownCloud 9.0.2 with PHP 7:
@wirestyle22 said in ownCloud 9.0.2 with PHP 7:
I'm not directing it at anyone. I'm saying I see claims made online and I wanted to know where you guys get your information when it isn't spelled out. Sorry if I'm not being clear.
We are looking at the software itself and seeing what it is doing. The repo information cannot be hidden or anything, because it has to be exposed for it to work with the package system.
I realized that after a few of your previous posts. Sorry. I'm working on my knowledge every day!
