[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1013752: marked as done (Transition KDE PIM 22.04)

Your message dated Wed, 6 Jul 2022 20:42:30 +0200
with message-id <YsXXlgDfGO5TC9ng@ramacher.at>
and subject line Re: Bug#1013752: Transition KDE PIM 22.04
has caused the Debian Bug report #1013752,
regarding Transition KDE PIM 22.04
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1013752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013752
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: deltaone@debian.org, debian-qt-kde@lists.debian.org

Hi Release team,

we would like to request a transition for KDE PIM 22.04.

We have uploaded KDE PIM 22.04 to experimental, but since KDE PIM
does not provide ABI stability and some packages outside
KDE PIM depend on it, we need a transition.

The packages depending on KDE PIM are:

* digikam
* kgpg
* kio-gdrive
* kjots
* kmymoney
* kraft
* zanshin

kio-gdrive, kmymoney, kraft and zanshin simply need a rebuild against
KDE PIM 22.04.

A fixed version of kgpg is in experimental and just needs to be uploaded
to unstable once KDE PIM 22.04 is uploaded there. There are patches
available for both digikam and kjots. I can patch kjots myself and point
the digikam maintainers to the existing patch.

Here is the Ben file:

---
title = "KDEPIM 22.04";

is_affected = .depends ~ /libkf5.*-21.12/ | .depends ~ /libkf5.*-22.04/;
is_good = .depends ~ /libkf5.*-22.04/;
is_bad = .depends ~ /libkf5.*-21.12/;
---

Thank you.


-- 
Med vänliga hälsningar

Patrick Franz

--- End Message ---
--- Begin Message --- 
On 2022-06-26 23:22:14 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2022-06-26 12:11:16 -0500, Steven Robbins wrote:
> > Hello,
> > 
> > Patrick suggested I chime in here, as the Digikam maintainer.
> > 
> > 
> > On Sat, 25 Jun 2022 23:42:47 +0200 Sebastian Ramacher <sramacher@debian.org> 
> > wrote:
> > > On 2022-06-25 20:45:37 +0200, Patrick Franz wrote:
> > > > Hi Sebastian,
> > > > 
> > > > Am Samstag, 25. Juni 2022, 20:30:32 CEST schrieb Sebastian Ramacher:
> > > > [...]
> > > > > > A fixed version of kgpg is in experimental and just needs to be
> > > > > > uploaded to unstable once KDE PIM 22.04 is uploaded there. There
> > > > > > are patches available for both digikam and kjots. I can patch kjots
> > > > > > myself and point the digikam maintainers to the existing patch.
> > > > > 
> > > > > Just to be clear: is the patch for digikam for kdepim compat or does
> > > > > it also fix the build failure with ffmpeg 5.0?
> > > > 
> > > > It would be purely for KDE PIM (https://invent.kde.org/graphics/
> > > > digikam/-/commit/51efe295a222070743187af0367b0bf957879337).
> > > 
> > > I see. If you (and the KDE team) are okay with temporarly removing
> > > digikam from testing, then please feel free to go ahead.
> > 
> > I'm comfortable with digikam being temporarily removed from testing.  As was 
> > pointed out, we still have the ffmpeg issue to deal with and I don't see any 
> > value in holding up kdepim for that.
> 
> ACK, then please go ahead. I'll add a hint to remove digikam from
> testing once kdepim is ready to migrate.

All uploads from this transition migrated to testing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: