Created attachment 836284 [details] yum install LOG Description of problem: I cannon install ownCloud server whithout httpd, because it requires php-ZendFramework >> php >> httpd. Version-Release number of selected component (if applicable): Fedora 20 Beta i686 owncloud-5.0.13-1.fc20 How reproducible: (I have problem with php-symfony without testing repos. Now i use testing repo) # yum install --enablerepo=* owncloud-sqlite.noarch owncloud-nginx.noarch Steps to Reproduce: 1. Fedora 20 Beta with last updates 2013-12-13 2. run yum install --enablerepo=* owncloud-sqlite.noarch owncloud-nginx.noarch Actual results: ... --> Processing Dependency: httpd for package: php-5.5.7-1.fc20.i686 ... --> Processing Dependency: php >= 5.2.4 for package: php-ZendFramework-1.12.3-2.fc20.noarch ... --> Processing Dependency: php-ZendFramework for package: owncloud-5.0.13-1.fc20.noarch ... Expected results: I wont httpd! Additional info: I see some ways: 1. Remove php-ZendFramework require from ownCloud ? I dont see Zend require on http://doc.owncloud.org/server/5.0/admin_manual/installation/installation_source.html 2. Split php-ZendFramework into php-ZendFramework-common and php-ZendFramework, LIKE php-ZendFramework2 package. Php-ZendFramework will not require php.
3. May be change require php-ZendFramework to php-ZendFramework2 in ownCloud.spec. I'm not php-specialist.
Hello. I still see this bug. But i dont need *testing repo. For reproduce bug: # yum install owncloud-nginx.noarch owncloud-sqlite.noarch Is actual for someone else?
I can see the problem, yeah. But fixing doesn't look trivial and is not really OwnCloud's job. OwnCloud's 'search_lucene' app bundles some bits of the Zend framework. Looking at the bundled copy, it's clearly Zend 1, not Zend 2: just looking at the files included makes that obvious. [adamw@adam Zend]$ pwd /home/adamw/local/owncloud/apps/search_lucene/3rdparty/Zend [adamw@adam Zend]$ ls Cache.php Exception.php Memory Memory.php Pdf Pdf.php Search [adamw@adam Zend]$ ls ~/local/ZendFramework-1.12.3/library/Zend/Memory* /home/adamw/local/ZendFramework-1.12.3/library/Zend/Memory.php /home/adamw/local/ZendFramework-1.12.3/library/Zend/Memory: AccessController.php Container.php Manager.php Container Exception.php Value.php [adamw@adam Zend]$ [adamw@adam Zend]$ ls ~/local/ZendFramework-2.2.5/library/Zend/Memory* composer.json Container Exception MemoryManager.php README.md Value.php [adamw@adam Zend]$ pretty obvious that the OC app has Zend1, not Zend2 bits. So I don't think it would be safe to just dump Zend2 on it instead, presumably the two are still maintained separately upstream and packaged separately in Fedora because 2 is not a transparent replacement for 1. One thing we could do is sub-package the search-lucene app, I guess. I don't want to change that unilaterally, though. Gregor, WDYT?
(In reply to Adam Williamson from comment #3) > One thing we could do is sub-package the search-lucene app, I guess. I don't > want to change that unilaterally, though. Gregor, WDYT? screw it, i'm about to bump oc.fc20 to the new release 6.0. And I can't find any deps to zend in the new version so we can just drop zend. So guys look out for oc 6 in fc20-testing.
Yikes - I was just looking at OC 6 too and it looks like quite a big change. Have you looked at all the 3rdparty changes? I'll send a private mail with my findings in a bit. apps/search_lucene/3rdparty/Zend still exists in the OC 6 tarball, would they keep it there if the app didn't need it any more?
(In reply to Adam Williamson from comment #5) > apps/search_lucene/3rdparty/Zend still exists in the OC 6 tarball, would > they keep it there if the app didn't need it any more? silly me, of course you are right. anyway I don't think we should split search-lucene app. Thats too confusing. Why does zend require httpd? Is there a specific reason?
It requires 'php' which requires httpd. I don't know where, if anywhere, that chain could be broken, but it seems like an issue for Zend, not owncloud.
thats it. I've created a report for zend. By the way: owncloud 6 in rawhide. testers welcome
*** This bug has been marked as a duplicate of bug 1045904 ***