Problems with upgrade path to F28 for kdepim

[José Abílio Matos]

Hi,
	I have updated to F28 (~ 2 weeks ago). kde/plasma is working very well, there are several
previous problems that have been fixed on updates (like the use of pagedown/space to read
messages in kmail).

The only issues that I have to report are the following:

# dnf upgrade
 Problem 1: package kdepim-7:16.12.2-6.fc28.x86_64 requires blogilo >= 16.12, but none
of the providers can be installed
  - package kf5-kblog-17.12.3-2.fc28.x86_64 obsoletes blogilo < 17.08.3-10 provided by
blogilo-17.08.1-1.fc28.x86_64
  - cannot install the best update candidate for package kdepim-7:16.12.2-6.fc28.x86_64
  - cannot install the best update candidate for package blogilo-17.08.1-1.fc28.x86_64
...
 Problem 4: problem with installed package kdepim-7:16.12.2-6.fc28.x86_64
  - package kdepim-7:16.12.2-6.fc28.x86_64 requires blogilo >= 16.12, but none of the
providers can be installed
  - package kf5-kblog-17.12.3-2.fc28.x86_64 obsoletes blogilo < 17.08.3-10 provided by
blogilo-17.08.1-1.fc28.x86_64
  - cannot install the best update candidate for package
blogilo-libs-17.08.1-1.fc28.x86_64

Is this known or reported?

Regards,
-- 
José Abílio

[Rex Dieter]

José Abílio Matos wrote:

>  Hi,
>  I have updated to F28 (~ 2 weeks ago). kde/plasma is working very well,
>  there are several previous problems that have been fixed on updates (like
>  the use of pagedown/space to read messages in kmail).
>  
>  The only issues that I have to report are the following:
>  
>  # dnf upgrade
>   Problem 1: package kdepim-7:16.12.2-6.fc28.x86_64 requires blogilo >=
>   16.12, but none of the providers can be installed
>    - package kf5-kblog-17.12.3-2.fc28.x86_64 obsoletes blogilo < 17.08.3-10
>    provided by blogilo-17.08.1-1.fc28.x86_64 - cannot install the best
>    update candidate for package kdepim-7:16.12.2-6.fc28.x86_64 - cannot
>    install the best update candidate for package
>    blogilo-17.08.1-1.fc28.x86_64
>  ...
>   Problem 4: problem with installed package kdepim-7:16.12.2-6.fc28.x86_64
>    - package kdepim-7:16.12.2-6.fc28.x86_64 requires blogilo >= 16.12, but
>    none of the providers can be installed - package
>    kf5-kblog-17.12.3-2.fc28.x86_64 obsoletes blogilo < 17.08.3-10 provided
>    by blogilo-17.08.1-1.fc28.x86_64 - cannot install the best update
>    candidate for package blogilo-libs-17.08.1-1.fc28.x86_64
>  
>  Is this known or reported? 
blogilo was retired, but I'm not sure if anything replaced/Obsoletes'd it.  
Mind filing a bug ?

-- Rex

[Rex Dieter]

Rex Dieter wrote:

>  blogilo was retired, but I'm not sure if anything
> replaced/Obsoletes'd it.
>  Mind filing a bug ? 
Ah, and kdepim metapackage still exists with references to blogilo as well.

:(

I can probably fix both, was hoping to retire the metapackage, but I think 
we can keep it for at least one more release.

-- Rex

[Rex Dieter]

Rex Dieter wrote:

>  Rex Dieter wrote:
>  
> > blogilo was retired, but I'm not sure if anything replaced/Obsoletes'd
> > it. Mind filing a bug ?
>  
>  Ah, and kdepim metapackage still exists with references to blogilo as
>  well.
>  
>  :(
>  
>  I can probably fix both, was hoping to retire the metapackage, but I think
>  we can keep it for at least one more release. 
Should be resolved with kdepim update:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-5f76cb33ea

-- Rex

[José Abílio Matos]

On Monday, 9 April 2018 15.52.36 WEST Rex Dieter wrote:
>  Should be resolved with kdepim update:
>  https://bodhi.fedoraproject.org/updates/ 
FEDORA-2018-5f76cb33ea

Thank you, I can confirm that it fixes the upgrade path. :-)

Best regards,
-- 
José Abílio

[Kevin Kofler]

Rex Dieter wrote:
>  blogilo was retired, but I'm not sure if anything
> replaced/Obsoletes'd it. 
And how am I supposed to post to my blog now?

The split tarballs were supposed to avoid applications going away when they 
don't get new releases anymore, why is that not working?

        Kevin Kofler

[Luigi Toscano]

Kevin Kofler ha scritto:
>  Rex Dieter wrote:
> > blogilo was retired, but I'm not sure if anything replaced/Obsoletes'd it.
>  
>  And how am I supposed to post to my blog now?
>  
>  The split tarballs were supposed to avoid applications going away when they 
>  don't get new releases anymore, why is that not working? 
The maintainer requested its move to unmaintained defining it "broken". From
the thread:

https://mail.kde.org/pipermail/release-team/2017-September/010636.html

-- 
Luigi

[Kevin Kofler]

Luigi Toscano wrote:
>  The maintainer requested its move to unmaintained defining it
> "broken".
>  From the thread:
>  
>  https://mail.kde.org/pipermail/release-team/2017-September/010636.html 
So the breakage starts with 17.04, let's try reverting it to 16.12 then?

        Kevin Kofler

[Rex Dieter]

Kevin Kofler wrote:

>  Luigi Toscano wrote:
> > The maintainer requested its move to unmaintained defining it "broken".
> > From the thread:
> > 
> > https://mail.kde.org/pipermail/release-team/2017-September/010636.html
>  
>  So the breakage starts with 17.04, let's try reverting it to 16.12 then? 
Currently for f28+, kblogilo was also FTBFS 

given that upstream dropped it combined with FTBFS I did perhaps jump too 
quickly to retirement rather than orphaning

You're welcome to pick it up and maintain it (and work to fix this issues).

-- Rex