On Sat, 5 Aug 2023 at 09:42, Christophe Marin wrote:
> Worth mentioning:
> - kdepim-runtime fails to build on stable openSUSE versions with:
> resources/google-groupware/googlesettingswidget.h:11:10: fatal error:
> ui_googlesettingswidget.h: No such file or directory
I got exactly the same error
On Sat, 4 Sept 2021 at 23:11, David Faure wrote:
>
> KDE Frameworks 5.86.0 has been uploaded to the usual place.
>
kwayland-5.86.0 depends on unreleased plasma-wayland-protocols-1.4.0,
from commit be955bee.
Hi,
kdeconnect-kde-20.11.90 fails to build with -DBLUETOOTH_ENABLED=ON, an
option that is by default disabled:
core/backends/bluetooth/bluetoothlinkprovider.cpp:184:101: error:
invalid new-expression of abstract class type ‘BluetoothDeviceLink’
See also:
These announcements continue to be problematic it seems. In the
'Announcements' part on kde.org front page, all it says is '20.08.3
Releases Source Info Page' which I doubt is the intended title, and
with no link to the actual release info page.
Regards,
Andreas
On Sat, 8 Aug 2020 at 00:42, Albert Astals Cid wrote:
>
> This needs to go to release-team which is where the dropping/adding stuff is
> discussed.
>
> El dijous, 6 d’agost de 2020, a les 22:27:10 CEST, Tobias Leupold va escriure:
> > Quite some time ago, we dropped libkface support, and --
On Sat, 6 Jan 2018 at 21:23, Sandro Knauß wrote:
>
> Hey,
>
> with a short discussion with Laurent ( the author of kblog), we decided to
> keep kblog
>
Hi,
It is two and a half years later, and kblog can be dropped from
Release Service for not being used anywhere.
[15:47] montel: does it make
On Thu, 26 Mar 2020 at 14:07, Jonathan Riddell wrote:
>
> Ralf, I'm seeing build failures in Umbrello introduced by your commit of
> March 12
>
> 6c475a1037ddbb51650e70d72582c94dbaac7ce9
Needless to say, that is also recorded in build.kde.org for a few days:
On Wed, 6 Nov 2019 at 00:34, Andreas Sturmlechner
wrote:
> lskat-19.08.3 fails to build against Qt-5.14, would you want to pick
> two commits from master and respin?
Well, okay, this probably goes beyond the scope of this release.
Similar Qt-5.14 backports are needed for multiple pa
lskat-19.08.3 fails to build against Qt-5.14, would you want to pick
two commits from master and respin?
d2eae3d524bf84b843eacdf45ecfc77908e12ad8 (Make it compiles against qt5.14)
7361a17fa8ffe607ad7f050062a5e4a1eda24f26 (Make it compile against
qt5.15, This enum is unused)
In fact both commits
On Sat, 2 Nov 2019 at 09:43, wrote:
>
> Beta 1 is out, you can find it on:
> http://download.kde.org/unstable/calligra/calligraplan-3.1.90.tar.xz.mirrorlist
What's the plan wrt the currently disabled (but fixed?) kcalendarcore code?
Hi,
as a packager I would appreciate more releases of not only yakuake.
That does not necessarily mean moving all to KDE Applications is the
solution, certainly not all of them...
When I look at what else I need to carry around patches for:
calligra - 20kB worth of patches just to build against
Hello,
something in Zanshin's dependencies had been implicitly providing
KF5:AkonadiContact but isn't anymore. Even if it is easy enough to
patch, a new release would be nice, not least considering the much
improved dependency situation.
Regards,
Andreas
On Sat, 2 Mar 2019 at 16:48, David Faure wrote:
> Dear packagers,
>
> KDE Frameworks 5.56.0 has been uploaded to the usual place.
syntax-highlighting should be respun to include commit 84d78a05
("guard target link libraries for older CMake version")
Regards,
Andreas
We got a downstream kcoreaddons-5.53 build failure report with
GCC-7.3.0 and Qt-5.11.3:
moc_kaboutdata.cpp:311:69: error: invalid use of incomplete type
‘class QVariant’
It was fixed by commit e53254a009982c379a5ad713139e88a881ca02fb, I
believe this should be part of a 5.53.1 bump.
Regards,
On Monday, 13 November 2017 at 09:33, Pali Rohár wrote:
> Hi! Kopete should have finally ready KF5 port, but that lands in
> separate branch, not in master. I would like to ask for dependency
> freeze exception so I could move KF5 port to master for upcoming KDE
> Applications release. As current
On 12 November 2017 at 23:57, Albert Astals Cid wrote:
> I don't understand why you want to move it to extragear if it is unmaintained,
> who is going to do releases?
Maybe I don't understand either, I'm fine with it going the same way as blogilo.
On 12 November 2017 at 20:33, Albert Astals Cid wrote:
> My suggestions:
If it's not too late, I propose to move libkface to extragear, considering
https://bugs.kde.org/show_bug.cgi?id=377425
and
https://mail.kde.org/pipermail/release-team/2016-July/009641.html
It has been
On Thursday, 5 October 2017 at 18:48, Albert Astals Cid wrote:
> El dijous, 7 de setembre de 2017, a les 20:02:47 CEST, Albert Astals Cid va
> > https://community.kde.org/Schedules/Applications/17.12_Release_Schedule
> Approved.
Following up on that, tomorrow is scheduled 17.12 dependency freeze
On Wednesday, 1 November 2017 at 16:59, laurent Montel wrote:
> Le mercredi 1 novembre 2017, 12:30:45 CET Albert Astals Cid a écrit :
> > Ok, done
> >
> > https://cgit.kde.org/sysadmin/release-tools.git/commit/?id=8b77a4f1315fdab20
> > 94c5203938eb0ad192c0b08
> >
> > Cheers,
> > Albert
>
>
On 10 August 2017 at 23:18, David Faure wrote:
> Hmm. What's the headache, if the framework name is simply "kirigami2", just
> like kcoreaddons is kcoreaddons? Now that my scripts have hacks, yours
> shouldn't need any...
It's a minor inconvenience that repo name and tarball
On Thursday, 10 August 2017 at 21:16, Rik Mills wrote:
> Indeed it would. For example I have kirigami (v1) and kirigami2 source
> packages in ubuntu, so human level confusion aside, now renaming
> kirigami2 tarballs to just kirigami is going to give scripting and
> tooling a headache.
Gah, I
On Sunday, 6 August 2017 at 23:41, David Faure wrote:
> KDE Frameworks 5.37.0 has been uploaded to the usual place.
>
> New frameworks: kirigami.
Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION 5.35.0, I
don't think that's intentional?
Regards
On Wednesday, 2 August 2017 at 22:47, David Faure wrote:
> According to the policy that KF5 should work with the last 3 releases of
> Qt5.x, it is time now for upcoming releases of KF5 to drop support for Qt
> 5.6.
> Packagers: is that acceptable?
Certainly no objection from Gentoo. Qt 5.7.1 is
On Saturday, 22 July 2017 at 16:57, Frederik Gladhorn wrote:
> On mandag 17. juli 2017 13.32.32 CEST Jonathan Riddell wrote:
> > it has an optional dep on libkdeaccessibilityclient which has a
> > release in 2014 as libqaccessibilityclient.
>
> Let's do it together here and now at Akademy. I'm a
---Original Message---
On Wednesday, 19 April 2017 at 21:48, Luigi Toscano wrote:
> Should we rename the new version? I wonder if it could be just
> akonadi_indexer.po.
Duplicate po-files are nothing new, I've been removing the following list from
the '4' part all the time (and that's ignoring
---Original Message---
On Saturday, 11 March 2017 at 17:30, Albert Astals Cid wrote:
> El divendres, 10 de març de 2017, a les 14:14:35 CET, Andreas Sturmlechner
> > va escriure:
> > Merge commit c8f9b01c480de6bc561fa96289260e2bb82d4a1e bumped cmake min
> > version and
Merge commit c8f9b01c480de6bc561fa96289260e2bb82d4a1e bumped cmake min version
and PIM_VERSION.
Attached patch might fix it, unless you want to blacklist.
Regards,
Andreas
---Original Message---
On Friday, 10 March 2017 at 14:10, Andreas Sturmlechner wrote:
> master was merged tw
> master was merged twice into Applications/16.12 branch and bumped
> KF5_VERSION,
> cmake minimum version and PIM_VERSION.
>
> Bad (version bumping/dropping) commits:
> c714ab94bc5d3f82e6de135798f905f27f19fc64
> 065c4028f97268466b22afb59eae2cbb37994a40
>
master was merged twice into Applications/16.12 branch and bumped KF5_VERSION,
cmake minimum version and PIM_VERSION.
Bad (version bumping/dropping) commits:
c714ab94bc5d3f82e6de135798f905f27f19fc64
065c4028f97268466b22afb59eae2cbb37994a40
4594308464a3ee8386c6e85e643dc7dac052e250
This will need
On Sunday, 26 February 2017 at 22:53, Albert Astals Cid wrote:
> > kfilereplace
> > kimagemapeditor
> > klinkstatus
>
> And? Apps that work don't need a large amount of commits.
>
> If you want us to stop releasing apps personally I need more reasons than
> "there's not many commits".
>
Oh,
---Original Message---
On Tuesday, 4 October 2016 at 23:42, Albert Astals Cid wrote:
> So it's 2.5 months later now.
>
> I would like to get them moved to git if possible, get them released
> for KDE Applications 16.12 and tell people they need to start caring
> about them if they don't want to
---Original Message---
On Wednesday, 22 February 2017 at 23:05, Wolfgang Bauer wrote:
> My plan (now) is to query Solid for removable devices (not only Floppy
> drives), and offer them in the chooser too.
> But this needs more thoughts...
+1 on that - I have an actual use case for this where
Hi,
khotkeys-5.8.5 fails to build with KF-5.31, a fix is available in 5.9 branch
(commit 617de4bd3fd080d43cce9bdc8af82963960d5c3a) but not in 5.8.
For reference: https://bugs.gentoo.org/show_bug.cgi?id=610040
It would be good to have that backported for 5.8.6 release.
Regards,
Andreas
I've picked one commit from master for libkexiv2 and libkface each to fix build
with KDE Frameworks 5.31 (-fno-operator-names), you may want to respin
tarballs there.
Regards,
Andreas
On Friday, 11 November 2016 at 12:29, Sandro Knauß wrote:
> But Debian list more reverse dependencies against kdepimlibs-4, if I request
> kdepimlibs4 to go. (Okay Debian is based on Application 16.08)
For sure there are external dependencies but that doesn't concern KDE
Applications decisions
On Thursday, 10 November 2016 at 23:42, Albert Astals Cid wrote:
> I know lots of you would want to see this happen *now* but remember there's
> people using those apps so dropping them makes them no good.
It is probably a good countdown for kdelibs4-based removal.
But I would have liked to get
On Monday, 7 November 2016 at 00:07, Albert Astals Cid wrote:
> What happens with kdepasswd then? We stop releasing it? Where was this
> discussed?
*Some* discussion appears to have happened here: https://mail.kde.org/
pipermail/plasma-devel/2016-October/061215.html
If I understand it
Hi,
This one has seen the last actual code change in... 2011. No one has bothered
to even make it independent from kdepimlibs-4, which itself has not been
released anymore since 4.14.10, more than a year ago. There is no frameworks
branch. I'd say, for anyone still depending on user/group
On Thursday, 3 November 2016 at 11:45, Sandro Knauß wrote:
> You may got the notice, that the cpp(gpgme++) and qt (QGpgme) interface,
> previously build by KDEPIM in the libgpgmepp package, moved down to GpgME
> directly. That's why KDEPIM depends on very recent GpgME.
>
> Together with Andre
On Friday, 29 July 2016 at 22:48, Gilles Caulier wrote:
> Andreas,
>
> Same situation for libkgeomap. This library can be also moved to
> extragear-libs as only kphotoalbum use it.
>
> Best
> Gilles Caulier
Just bringing this up again before 16.12 freeze for consideration. I'm
obviously not
On Monday, 17 October 2016 at 20:31, Nicolás Alvarez wrote:
> It's done! Please review:
> kde:scratch/nalvarez/kdewebdev-kfilereplace
> kde:scratch/nalvarez/kdewebdev-kimagemapeditor
> kde:scratch/nalvarez/kdewebdev-klinkstatus
> kde:scratch/nalvarez/kdewebdev-kommander
>
> The history seems to
On Friday, 29 July 2016 at 16:04, Leslie Zhai wrote:
> I merged kf5 branch to libkcddb UPSTREAM
> https://quickgit.kde.org/?
p=libkcddb.git=shortlog=275de8e8d7d446ef02c0194de8703cfcf0699385
> and I updated all dependes on KF5Cddb projects' CMakeLists.txt about
> KF5Cddb property, tellico have
---Original Message---
On Saturday, 16 July 2016 at 16:13, Leslie Zhai wrote:
> I want to help those projects (audex, kaudiocreator, audiocd-kio and
> soundkonverter) for migrating to KF5 and Qt5, trust me, I experienced
> and good at qt3 -> migrate -> qt4 -> migrate ->qt5
First of all, thanks
---Original Message---
On Monday, 25 July 2016 at 13:57, laurent Montel wrote:
> So kdgantt2 will not release for 16.12 (it's still use for 16.08).
+1 for PIM cleanup :)
Does that mean kdiagram is going to be part of the KDE Applications 16.12
release as well, or will it be similar to libkgapi
Hi,
Obviously libkface is not a dependency of digikam anymore since porting to
kf5, it looks like similar functionality is now bundled there. One of the last
commits it received > 9 months ago was OpenCV3 support, which already needs
downstream patching to build with OpenCV 3.1 (released in
On Friday, 8 July 2016 at 11:11, Luigi Toscano wrote:
> On Friday 08 of July 2016 11:03:05 Andreas Sturmlechner wrote:
> > None of them were ported yet, in fact they haven't seen commits in years.
> > They should probably be converted to git, still, but imo no need to keep
&
Hi,
Is there any reason not to drop kdewebdev from upcoming 16.08 release?
It contains the following applications:
kfilereplace
kimagemapeditor
klinkstatus
kommander
None of them were ported yet, in fact they haven't seen commits in years. They
should probably be converted to git, still, but
Also, in release notes, "kdgantt2" should be added to new tarballs.
https://community.kde.org/Applications/16.04_Release_Notes
Regards,
Andreas
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
---Original Message---
On Sunday, 20 March 2016 at 12:58, laurent Montel wrote:
> Le dimanche 20 mars 2016, 12:47:01 CET Albert Astals Cid a écrit :
> > El diumenge, 20 de març de 2016, a les 8:29:06 CET, laurent Montel va
> >
> > escriure:
> > > Hi,
> > > Some kdepim are missing:
> > >
> > >
---Original Message---
On Sunday, 13 December 2015 at 20:59, Nicolás Alvarez wrote:
>
> What do you mean "backported to 15.08.3"? I don't see anything in the
> 15.08 git branch. Do you just mean you tested backporting it locally
> and it works, or that you did it in a distro patch?
>
> --
>
50 matches
Mail list logo