[Owncloud] Owncloud on Fedora/RHEL 6

[Matěj Cepl]

[This message has also been posted to gmane.comp.kde.devel.owncloud.]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2014-01-12, 20:32 GMT, Klaas Freitag wrote:
> Where is that package, who maintains it and how long does it 
> take until it is updated after we released a new ownCloud 
> version? It is a problem for us if downstream falls behind 
> with the versions provided for the systems in question.

You can get all these information from 
https://admin.fedoraproject.org/pkgdb/acls/name/owncloud
(e.g., http://pkgs.fedoraproject.org/cgit/owncloud.git/ shows 
all packaging files, 
https://admin.fedoraproject.org/updates/owncloud shows current 
updates in stable repos, 
http://koji.fedoraproject.org/koji/packageinfo?packageID=15599 
shows builds (note, that F21 is current Rawhide)).

I am not sure what is the name of the package maintainer 
(his/her Fedora login name is brummbq and he is also helped by 
Adam Williams, one of the Fedora QA people, who uses ownCloud 
for his own use), but what stops you from comaintaining the 
package? I couldn’t imagine any complaints if you stepped up and 
provided patches for (not that many) bugs against owncloud 
packages 
(https://bugzilla.redhat.com/buglist.cgi?quicksearch=component%3Aowncloud) 
or to start to comaintain the packages.

Also, I am a Fedora provenpackager, so if there were any delays 
with building packages or something of that sort, I have power 
to push it through (of course, I would seek first advice from 
the current package maintainer).

> We use the build system that suits us best to provide packages to the 
> ownCloud users very fast, and currently that is the openSUSE 
> Build Service.

I am not big fan of the third party repos created by people who 
are not willing to work with the distro community (and looking 
at http://packages.debian.org/search?keywords=owncloud I am not 
alone).

I don’t understand the word “very fast” here. It certainly 
doesn’t mean speed literally. Koji (Fedora build system) builds 
not slower than any other build system I know about (or not 
significantly slower).  Do you mean that your own repo allows 
you to create sloppy packages which break rest of the system? Do 
you mean that instead of proper resolving the issues you can 
introduce new versions of libraries incompatible with the rest 
of the system?  (is it finally possible to build owncloud client 
on RHEL-6 without introducing new versions of the third party 
libraries?) Do you mean that by hiding issue tracker you can 
happily ignore complaints of your users (where is the issue 
tracker of the Fedora/RHEL packages)?

> If the packages are not behaving well, please help us fixing.

Why should I help to split Fedora/EPEL distro by supporting 
incompatible packages (and if they are not incompatible, what 
they are good for)?

I don’t know where this mentality of splitting distro into 
thousand of incompatible subcommunities growth from? Ubuntu, 
with its PPAs, because Canonical doesn’t allow you to fix bugs 
in the core libraries, or what (not trying to libel them, just 
really honestly don’t know why you need to separate yourself 
from the rest of the Fedora/RHEL community)?

What is the source of the perceived speed of the building?

> Fully agreed. The problem is probably that nobody had time and 
> knowledge enough to get that fixed. Can you help us and test 
> and tell us what needs to be done to make it work well with 
> SELinux?

Well, if you were using packages build together with the rest of 
the distro (so they would have proper configuration files, 
etc.), then you won’t need that time and knowledge yourself. You 
just file bugs to RH BZ. That’s what sharing is all about.

Best,

Matěj

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iD8DBQFS1CM34J/vJdlkhKwRAvymAJ4u4fcibku5o4pET2yGipwCgbW+MwCcCN1o
w3JZk538EO00LlWzW5RBA5A=
=M9rf
-----END PGP SIGNATURE-----