Versions of dependencies for coming releases (Re: phonon version required for bindings?)

[just bringing this topic out of private mail and onto the release team 
list.]

Dirk Müller wrote:
> On Monday 01 June 2009, Simon Edwards wrote:
>> Sure, no problem. I find the versioning of things in kdesupport -- which
>> are needed to build KDE from SVN -- to be very unclear when it comes to
>> approaching releases. During most of the dev cycle kdesupport is needed
>> and works fine until around the end when all sorts of different versions
>> of things from all over the KDE SVN repository are selected as being THE
>> version. Where is this stuff documented? Google can't seem to find it.
> 
> This is currently not really documented. for release branches we have 
> tags/kdesupport-for-4.1/2 which contains the recommended versions. for /trunk 
> this is currently in flux, so it depends on Matthias what the plans are. 

This is a problem for me at least and maybe others. The Python bindings 
includes bindings for a number of things from kdesupport such as phonon, 
akonadi and soprano. To get ready for release I need to know which 
branch/tag of these libraries will be the minimum requirement for the 
coming KDE release. IMHO, by soft freeze it should be pretty clear which 
versions/branches are in going to be in good enough shape to be a 
requirement for the next KDE release. The decision just needs to be made 
an documented on techbase.

Can we have this stuff settled by soft freeze in the future?

cheers,

--

-- 

KDE 4.3 Beta2 tagging tomorrow

Hi, 

We have a KDE 4.3 Beta2 tagging milestone tonight at 23:59 UTC. I will, 
assuming that trunk compiles, perform tagging tomorrow morning (12 hours from 
now).

If there are urgent outstanding issues not ready until then, please tell 
release-team@... 

Thanks,
Dirk

Re: [Kde-pim] kdepim runtime

On Thursday 07 May 2009 23:47:03 Tom Albers wrote:
> Hi DIrk, *
>
> As discussed today, we would like to have a kdepim-runtime tarball, we
> would like to have it contain the content of /trunk/KDE/kdepim/akonadi. It
> should be able to compile stand alone and only contains the stuff that is a
> runtime dependency for akonadi application.
>

This is *almost* possible since rev. 976113.

akonadi/resources/imap and akonadi/resources/kolabproxy still include some 
files from libkdepim.

Christophe.

On Thursday 07 May 2009 23:47:03 Tom Albers wrote:
> Hi DIrk, *
>
> As discussed today, we would like to have a kdepim-runtime tarball, we
> would like to have it contain the content of /trunk/KDE/kdepim/akonadi. It
> should be able to compile stand alone and only contains the stuff that is a
> runtime dependency for akonadi application.
>

This is *almost* possible since rev. 976113.

akonadi/resources/imap and akonadi/resources/kolabproxy still include some 
files from libkdepim.

Re: KDE 4.2.5?

On Saturday 30 May 2009 6:51:15 am Sebastian Kügler wrote:
> On Friday 29 May 2009 22:51:08 Sune Vuorela wrote:
> > On Friday 29 May 2009 18:26:26 Allen Winter wrote:
> > > Howdy,
> > >
> > > Can we decide now if there will be a 4.2.5 release?
> > > If not, then that saves us some unneeded backporting work.
> > >
> > > Recall we stopped at 4.1.4.
> > > IMO we should stop at 4.2.4.
> > >
> > > Let's decide very soon and I'll communicate the decision to all
> > > developers.
> >
> > I would like to request something in between; still do some backports, but
> > only in some special cases, at least until 4.3final is out.
> >
> > The special cases I could imagine would probably be something like:
> >  - "grave" bugs (dataloss & too frequent crashes to make the app usable and
> > such) - and maybe with a CCMAIL: kde-packager
> >  - gcc 4.4 (and such)  compile fixes.
> >  - maybe other cases that I haven't yet thought of, but of a similar
> > "severity" and impact.
> >
> > That way, distributions and others who cares can get "blessed" backport
> > patches of the problems, which is kind of preferred.
> 
> Yep, for grave problems, we might want to consider a 4.2.5, otherwise I think 
> we should stop at 4.2.4 and fully concentrate on 4.3.
> 

Re: KDE 4.2.5?

Em Sábado 30 de maio 2009, às 07:51:15, Sebastian Kügler escreveu:
> >
> > That way, distributions and others who cares can get "blessed" backport
> > patches of the problems, which is kind of preferred.
>
> Yep, for grave problems, we might want to consider a 4.2.5, otherwise I
> think we should stop at 4.2.4 and fully concentrate on 4.3.

Security issues always got CVE and we do a regular patch.
I think is highly unlikeable we will have some outstanding issue not detected 
yet that will force us to provide a full release.

[]'

--

-- 
Helio Chissini de Castro
Mandriva Research and Development
_______________________________________________
release-team mailing list
release-team <at> kde.org
https://mail.kde.org/mailman/listinfo/release-team

KDE 4.3 Beta2 tagged and tarballs uploaded (try#1)

Hi, 

I just finished uploading the first set of KDE 4.3 Beta2 tarballs. let kde-
packager@... know of any issues. kde-l10n comes a few hours later. 

you need the python-sip/python-qt4 snapshots of 20090601 to build and an 
akonadi snapshot. I will try to collect releases of the dependencies now asap.

Greetings,
Dirk

Re: KDE 4.3 Beta2 tagged and tarballs uploaded (try#1)

On Wednesday 03 June 2009, Dirk Mueller wrote:

> you need the python-sip/python-qt4 snapshots of 20090601 to build and an
> akonadi snapshot. I will try to collect releases of the dependencies now
> asap.

you need akonadi 1.1.90 downloadable from download.akonadi-project.org. I've 
updated kdepimlibs to require it: 

5a4700a1e36724efa4d50fa4db111f35  kdepimlibs-4.2.90.tar.bz2

Greetings,
Dirk

Re: KDE 4.3 Beta2 tagged and tarballs uploaded (try#1)

On Wed, Jun 03, 2009 at 08:22:34PM +0200, Dirk Mueller wrote:
> On Wednesday 03 June 2009, Dirk Mueller wrote:
> 
> > you need the python-sip/python-qt4 snapshots of 20090601 to build and an
> > akonadi snapshot. I will try to collect releases of the dependencies now
> > asap.
> 
> you need akonadi 1.1.90 downloadable from download.akonadi-project.org. I've 
> updated kdepimlibs to require it: 
> 
> 5a4700a1e36724efa4d50fa4db111f35  kdepimlibs-4.2.90.tar.bz2
> 
> Greetings,
> Dirk

At least kdebase-runtime [1], and kdebindings [2] fail here if I use the latest
soprano release. Is soprano trunk required or will a soprano release
follow?

Thanks Dirk!

[1]
/var/tmp/paludis/build/kde-kdebase-runtime-4.2.90/work/kdebase-runtime-4.2.90/nepomuk/services/queryservice/searchthread.cpp:
In function 'QString<unnamed>::wrapInInstanceBaseGraphQuery(const QString&, int)':
/var/tmp/paludis/build/kde-kdebase-runtime-4.2.90/work/kdebase-runtime-4.2.90/nepomuk/services/queryservice/searchthread.cpp:164:
error: 'resourceToN3' is not a member of 'Soprano::Node'
/var/tmp/paludis/build/kde-kdebase-runtime-4.2.90/work/kdebase-runtime-4.2.90/nepomuk/services/queryservice/searchthread.cpp:
In function 'QString<unnamed>::createGraphPattern(const Nepomuk::Search::SearchNode&, int&,
const QString&)':
/var/tmp/paludis/build/kde-kdebase-runtime-4.2.90/work/kdebase-runtime-4.2.90/nepomuk/services/queryservice/searchthread.cpp:213:

Re: KDE 4.3 Beta2 tagged and tarballs uploaded (try#1)

On Wednesday 03 of June 2009 22:24:05 Ingmar Vanhassel wrote:

> At least kdebase-runtime [1], and kdebindings [2] fail here if I use the
> latest soprano release. Is soprano trunk required or will a soprano release
> follow?

Further "yet unstatisfied" (but at least listed in CMakeLists.txt) 
dependencies for 4.3 seem to be:
- yet unreleased eigen for kdeedu/step
- yet unreleased sip/PyQt4 for pykde4
- trunk phonon for mplayerthumbs to work with phonon backend (and not mplyer 
executable - this one is optional though)

If some of them are not going to be released before 4.3, well... packagers 
(for source based distros at least  - eigen is purely build time dependency so 
may not bother binary distros) may need to either hold 4.3 releases or release 
snapshots of dependencies on their own.

--

-- 
regards
MM

On Wednesday 03 of June 2009 22:24:05 Ingmar Vanhassel wrote:

> At least kdebase-runtime [1], and kdebindings [2] fail here if I use the
> latest soprano release. Is soprano trunk required or will a soprano release
> follow?

Further "yet unstatisfied" (but at least listed in CMakeLists.txt) 

Re: KDE 4.3 Beta2 tagged and tarballs uploaded (try#1)

2009/6/3 Maciej Mrozowski <reavertm@...>:
> On Wednesday 03 of June 2009 22:24:05 Ingmar Vanhassel wrote:
>
>> At least kdebase-runtime [1], and kdebindings [2] fail here if I use the
>> latest soprano release. Is soprano trunk required or will a soprano release
>> follow?
>
> Further "yet unstatisfied" (but at least listed in CMakeLists.txt)
> dependencies for 4.3 seem to be:
> - yet unreleased eigen for kdeedu/step

Armin Berres drew my attention on this on #eigen. Though I'm
subscribed to this list, I don't read it frequently so please CC me if
you want to make sure I read it...

kdeedu (step) relies on the development version of eigen, that will
become eigen 2.1.
but eigen 2.1 won't be released before kde 4.3.

Possible solutions:

a) you package whatever is in kdesupport at a given time. We guarantee
that, until the eigen 2.1 release, we keep in kdesupport whatever is
needed to build trunk/KDE. We resync it as needed (refresher: eigen
development now happens outside of kde svn and the kdesupport version
will be removed after our 2.1 release)

or:

b) we can make unstable releases, like "eigen 2.0.60", as needed. Ask