[Pkg-owncloud-maintainers] You want users to lose data?!?!

Martin Steigerwald martin at lichtvoll.de
Sat Feb 27 20:38:52 UTC 2016

On Samstag, 27. Februar 2016 12:29:46 CET Jos Poortvliet wrote:
> Guys and girls,


I considered again and again to follow-up on the thread I started but in the 
end I thought it would be pointless, cause its the actual packages of both 
sides needing to speak to each other what can be done.

> We just noticed you made a patch to remove the check the skipping of
> releases on upgrade. We don't test skipping releases on upgrade and don't
> support it for that reason - you really want to subject users to that
> massive risk of data loss?
> Our highest priority is to never cause data loss for users. We made massive
> progress in that area over the last years and a properly administered and
> installed ownCloud is unlikely to lose you data, even when you're running
> it with 10K users and 10TB of files.

Jos, did you notice the amount of effort David put into making sure upgrade to 
new Owncloud will work within Debian?

Do you also know that this work is not yet completed and the new version of 
Debian is not even near to being frozen?

So how about trying to *work* together, instead of *flaming* at the people who 
work to make Owncloud available within Debian?

> I understand you have a problem caused by the slow release cycle of Debian
> but risking user data is NOT a good way of dealing with that. This is
> exactly the kind of thing I was writing a blog about earlier - a blog wich
> made many of you rather angry, and I understand that, so I decided to do
> you the courtesy to email you before we would publish another blog post
> telling people not to use (debian) packages... This risks user data, risks
> our reputation - could I please ask you not to do this?

What is the alternative?

Deploying Owncloud in a docker container and upgrading it from git master each 

I stand by it that I don´t want to run a docker container just to be able to 
run Owncloud from git master each day and that a tarball stuffed into a *.deb 
is also not going to do it for me.

A first start would be that Owncloud´s own packagers speak with Debian 
Owncloud maintainers about what can be done to improve the situation while 
taking both upstream *and* Debian needs into as well as supportability into 


More information about the Pkg-owncloud-maintainers mailing list