Re: [owncloud-user] EPEL-6 packages for ownCloud 7

2015-03-06 Thread Chris
Hi,

see here for a description for the decision why to provide a OC8 package for
system which doesn't ship PHP 5.4 by default:

https://github.com/owncloud/core/issues/13917#issuecomment-73052468



--
View this message in context: 
http://owncloud.10557.n7.nabble.com/EPEL-6-packages-for-ownCloud-7-tp14717p14721.html
Sent from the Users mailing list archive at Nabble.com.
___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


Re: [owncloud-user] EPEL-6 packages for ownCloud 7

2015-03-06 Thread ~Stack~
On 03/06/2015 06:24 PM, Chris wrote:
 see here for a description for the decision why to provide a OC8 package for
 system which doesn't ship PHP 5.4 by default:
 
 https://github.com/owncloud/core/issues/13917#issuecomment-73052468

That was actually an interesting read. Thanks!


We have too many things that we can't take big risks on so we keep to
the Enterprise grade type of stuff. We are still waiting on several big
vendors to properly adopt to RHEL 7 before we jump ship. I am /really/
hoping to stick it out on RHEL 6 till at least the end of the year with
a migration next year, but more and more it is getting challenging to do so.

It is kinda funny. Two years ago I led the crusade to get rid of RHEL 4
and last year I started the hard push to migrate off of RHEL 5. I just
wanted a year break before starting the push to get off RHEL 6. :-D


~Stack~



signature.asc
Description: OpenPGP digital signature
___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


Re: [owncloud-user] EPEL-6 packages for ownCloud 7

2015-03-06 Thread ~Stack~

On 03/06/2015 02:23 PM, Matěj Cepl wrote:
 Packaging software which depends on php54 
 for platform which doesn't have php54...

To be fair, they have advertised dumping php53.
To be honest, if you look at my history on this forum you will see a
recent post where I too got blindsided by this very thing.

The Software Collections route I went to was something new to me, but it
ended up not being too bad. Now I have httpd24 and php55 running on
Scientific Linux in production with owncloud 8. The post shouldn't be
too hard to find, but if you need help let me know. I will be happy to
do what I can.


 I would think that E in RHEL means that the packager should be careful
 about screwing up your users.

Trust me. This is one of my biggest pet-peeves. Especially with the
absurd notion recently of pushing bleeding-edge packages that haven't
hit a one year birthday yet into Enterprise grade OS and LTS support.
This really frightens me. But I would also expect that an admin who
joins me in the fight for keeping that E of highest importance would
break a dev box...not a production one...

~Stack~



signature.asc
Description: OpenPGP digital signature
___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


Re: [owncloud-user] Can not share calendars anymore

2015-03-06 Thread Chris
Hi,

some plugins like adblock or ublock are currently blocking the share buttons
of ownCloud. Try again after disabling those plugins.



--
View this message in context: 
http://owncloud.10557.n7.nabble.com/Can-not-share-calendars-anymore-tp14713p14714.html
Sent from the Users mailing list archive at Nabble.com.
___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


Re: [owncloud-user] Can not share calendars anymore

2015-03-06 Thread Yvan Masson
Thanks Chris !

I keep getting surprised how solutions can be simple sometimes...

Maybe this tip should also appear in the official documentation, if
someone knows who to contact.

Thanks again all, have a good continuation,
Yvan

Le vendredi 06 mars 2015 à 07:44 -0700, Chris a écrit :
 Hi,
 
 some plugins like adblock or ublock are currently blocking the share buttons
 of ownCloud. Try again after disabling those plugins.
 
 
 
 --
 View this message in context: 
 http://owncloud.10557.n7.nabble.com/Can-not-share-calendars-anymore-tp14713p14714.html
 Sent from the Users mailing list archive at Nabble.com.
 ___
 User mailing list
 User@owncloud.org
 http://mailman.owncloud.org/mailman/listinfo/user


___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


Re: [owncloud-user] Blogposts for upgrade problems or usage hints

2015-03-06 Thread ~Stack~
On 03/05/2015 10:52 AM, Chris wrote:
 Something to discuss:
 
 Recently i've seen some blogposts about upgrade problems or ownCloud usage
 and mostly havn't found those in the core bugtracker as a bugreport or at
 the documents tracker as an enhancement.
 
[snip]
 
 I really don't get it why people spend so much time in writing blogposts and
 just don't report it back to the project itself.
 
 Language barriers?
 I don't care?
 No knowledge where / how to report this?
 Anything else?

I can't speak for anyone but myself here, but there have been a couple
of times where I have done similar.

* Some require too many hoops to jump through to just report a bug.

I don't use Red Hat directly, but I do use a few derivatives and I have
been told on multiple occasions You need to report this upstream to Red
Hat. I can never remember that Bugzilla account/password and it used to
be a colossal pain to get the password reset so I have always just
created a new user/password. (although I did start using KeePass2 so
maybe this won't be much of an issue in the future).

Another example from a few weeks ago, I was messing around with a
program I saw mentioned on another list. Though I had no use for the
program it looked interesting and I wanted to poke at it. I found a bug.
I also recognized how to fix it as I had recently fixed something _very_
similar. Perfect example for Open Source, right? Well this little
private never-heard-of-it-before bugtracker only accepted Twitter and
Facebook log ins...wtf? I have neither. I unsuccessfully tried to use
one of my spam throw away accounts to sign up for Twitter but it really
didn't like that. I puttzed around until it was no longer worth my time
and I sent an email to the *one* email address listed on the site. Never
heard anything back. I have no idea if it got fixed or not...

Last example I will mention for an official bug tracker being terrible
is from a company that has both an Open Source version and a corporate
version. My company bought the corporate version. When we bought it they
asked us to go through their bug tracker to report issues instead of
taking it to the community side because the community bug tracker
rarely gets looked at by any developer internally. I thought that was
strange, but ok, whatever. Maybe the paid for developers are working on
other things? Dunno... Then I found a big bug. It took months of dealing
with a really crappy tracker and almost no forward progress before I
went to the community. Someone way more familiar than I with the
software on the mailing list recognized my problem and was able to
easily recreate it w/ instructions for others. Someone else knew where
to look in the code. Within _4_hours_ the mailing list had reproduced
the problem, narrowed the scope, and someone had a patch to try. The
Open Source version is great but the corporate version wasn't for us.
This was one of the _many_ issues we had with this company and I made
sure it was on the list that we reported when we dumped the product. I
am not going to name-n-shame the company because I have been told that
within the last year many of the items on my list, including how they
respond to bugs, has been greatly improved.

* Unintentionally by writing a post on an experience. I have two
experiences from my personal blog.

One time I was just comparing my experiences between two different but
similar products. What I thought was just a bad design I later
discovered was actually a bug (thanks to a dev who commented). I hadn't
used the product nearly enough to recognize it as a bug so I didn't
report it.

Another time I had an issue and it really stumped me. The TL;DR was I
thought it was me picking a bad configuration which I tweaked until it
started working. I later discovered that it was actually a bug and
someone commented on the post asking me to file a bug report (which I did).

* Lastly, not knowing where to report a bug and getting pointed to wrong
locations.

I found a nasty kernel bug once. I really tried tracking it down, but
that is SO far outside of my scope of abilities. I reported it to my
distro. They said that was to be reported upstream to Red Hat. I really
didn't want to deal with Red Hat Bugzilla again...so I replicated the
problem with CentOS and went to the CentOS guys because I know some of
them are pretty hard core kernel guys. They said to go see Red Hat.
Dang. Fine...Went to Red Hat and they said, the patch causing problems
came from Fedora and since you aren't using proper Red Hat, go see
Fedora. Ugh. Fine. Went to Fedora and verified that the problem still
existed, they said that it was a kernel problem. I very carefully and
nervously made a report to the kernel list (didn't want to get flamed
for making a dumb newbie post to the kernel list). They said that it
wasn't in the kernel, but a patch on top of the kernel by the distro
devs and to go see whoever my distro was...damn...back at square one.
After two months of trying (with a lot of effort 

Re: [owncloud-user] Can not share calendars anymore

2015-03-06 Thread Chris
Hi,

this is a problem of a external plugin so its probably better fixed there
rather than documented in the ownCloud docs.



--
View this message in context: 
http://owncloud.10557.n7.nabble.com/Can-not-share-calendars-anymore-tp14713p14716.html
Sent from the Users mailing list archive at Nabble.com.
___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


[owncloud-user] EPEL-6 packages for ownCloud 7

2015-03-06 Thread Matěj Cepl
Given the complete ineptude of the whoever packages owncloud on 
the OpenSUSE builder for RHEL-6 I have build my own package to 
be included into EPEL-6 proper. It is just owncloud7, but that 
seems to work correctly with php53 which is what we have on 
RHEL-6.

Particular bug is 
https://bugzilla.redhat.com/show_bug.cgi?id=1199486 (with link 
to Koji build).

Best,

Matěj

___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


Re: [owncloud-user] EPEL-6 packages for ownCloud 7

2015-03-06 Thread Daniel Molkentin
Hi Matěj,

On 06.03.2015 15:56, Matěj Cepl wrote:
 Given the complete ineptude of the whoever packages owncloud on 
 the OpenSUSE builder for RHEL-6 I have build my own package to 
 be included into EPEL-6 proper. It is just owncloud7, but that 
 seems to work correctly with php53 which is what we have on 
 RHEL-6.
While I appreciate your efforts, I would like to remind you of our Code
of Conduct (https://owncloud.org/community/code-of-conduct/). I think
you're around Open Source projects long enough to know that insulting
people is, for a good reason, frowned upon outside the realm of LKML.

That said, I think whoever packages ownCloud on OBS would have
appreciated a hint. A patch like this should be easy enough to
integrate, but not obvious to someone who doesn't know all distributions
and their
RPM extensions by heart. So if the purpose of thise post was to be
helpful, rather than just bashing OBS, please consider contributing to
our packages next to the Koji ones.

Cheers,
  Daniel

-- 
www.owncloud.com - Your Data, Your Cloud, Your Way!

ownCloud GmbH, GF: Markus Rex, Holger Dyroff
Schloßäckerstrasse 26a, 90443 Nürnberg, HRB 28050 (AG Nürnberg)


___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user


Re: [owncloud-user] EPEL-6 packages for ownCloud 7

2015-03-06 Thread Matěj Cepl
On 2015-03-07, 00:24 GMT, Chris wrote:
 see here for a description for the decision why to provide a OC8 package for
 system which doesn't ship PHP 5.4 by default:

 https://github.com/owncloud/core/issues/13917#issuecomment-73052468

Well, I will stay with EPEL-6 packages and I'll hope to keep 
them running at least for some time.

Couple of notes on idea staying with php54 from the Software 
Collections (official or not):

 * Requires: php54
   (Software Collections are all based around the idea that two 
   versions of packages should stay on the system, so its PHP 
   package will never provide plain php)
 * You have to remind your users, that Apache cannot load two 
   versions of mod_php at once, so if they want to have other 
   packages depending on the system PHP53 they must somehow 
   reconfigure them (probably using cgit?). I don't know about 
   ngnix, but I guess the situation will be similar.
   Lovely to do it on the production system!

There are certainly other disasters looming on the horizon.

Best,

Matěj

___
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user