[Pkg-owncloud-maintainers] OC4 for wheezy!

Thomas Müller thomas.mueller at tmit.eu
Sat May 19 21:21:35 UTC 2012


Hi Thomas,

thanks a lot for your feedback - please find my comments below.

Am Freitag, dem 18.05.2012 um 17:42 schrieb Thomas Goirand:
> On 05/18/2012 02:52 PM, Thomas Müller wrote:
> > Hi,
> > 
> > as you probably know: I want OC4 in wheezy! ;-)
> > And that's gone be a tough task - as you might know - the NEW queue will stop processing after May 20th! [0]
> > 
> > Currently we have two unresolved dependencies:
> > sabredav: 
> > An initial package has been uploaded to mentors [1]. 
> > Thomas Goirand volunteered to sponsor/maintain.
> > Unfortunately Thomas didn't react to my mails in the past days.
> > 
> > mdb2_schema:
> > Thomas Goirand is working on that as well. And there is still an unresolved 
> > licensing issue with one of it's dependencies (xml_dtd). [2]
> > 
> > @Thomas: Are you  there? ;-)
> 
> Yes I am.
> 

Good! ;-)

> But since there's no news from the XML_DTD upstream author, I see no
> point in going further. We need that to be fixed first.
>

I fully understand that - no problem.
 
> > @pkg-owncloud-maintainers:
> > How do we proceed?
> > For sabredav we have two options:
> > 1.) keep it within the owncloud package as 3rdparty - just like *still* some other
> > 2.) we push sabredav ourself
> 
> I'd have helped if I had time. Currently, I'm busy with other stuff,
> sorry. BTW, I don't think it's a good idea to rush in before Wheezy is
> frozen. Usually, it's a much better idea to rush to do your package *at
> the beginning* of a Debian development, not at the end. That is, I think
> you should aim at Wheezy +1, not Wheezy. Anyway, even if you miss the
> target of Wheezy, you can always work on backports later on!
> 

Paul and myself invested some time into the package and we are ready for upload.
You don't need to worry about that any more.

> > For mdb2_schema we actually have only the option to keep it in the package for now.
> > Afaik the licensing issue will not hit us, because xml_dtd is not required with owncloud.
> 
> It is. XML_DTD is a hard dependency of mdb2_schema, and there's no way
> you will be able to upload mdb2_schema without xml_dtd. Have a look at
> the pear.php.net site, or download the package.xml from mdb2_schema if
> you don't believe me.
> 

I totally believe you that mdb2_schema has a dependency to xml_dtd.
I never questioned that.
But from having a look at the way mdb2_schema is used within ownCloud and the total lack of 
xml_dtd with the ownCloud sources I had the feeling it's not used.
By now we know that this piece of code is not used and we can ship it within ownCloud.

> Cheers,
> 
> Thomas
> 
> _______________________________________________
> Pkg-owncloud-maintainers mailing list
> Pkg-owncloud-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-owncloud-maintainers



More information about the Pkg-owncloud-maintainers mailing list