Bug 1398380 - Claws Mail after Fedora 25 upgrade non-functional
Summary: Claws Mail after Fedora 25 upgrade non-functional
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: 25
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1398482 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 15:46 UTC by Edward
Modified: 2016-12-01 00:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-25 10:36:33 UTC
Type: Bug


Attachments (Terms of Use)

Description Edward 2016-11-24 15:46:04 UTC
Description of problem:

After Claws Mail was upgraded during an upgrade from Fedora 24 to 25, it was discovered that all of the saved e-mail accounts were changed from IMAP to POP3 and this designation cannot be changed back. 

During the upgrade process, dnf indicated Claws Mail and a few of its related plugins were being "downgraded", the installed version remains at 3.13.2-1, yet will not install 3.14.

A bug report on this problem was filed at http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3733

However, the suggested remedy in that report (amongst other comments) to change protocol=0 to protocol=1 in the accountrc file, did not fix this problem and Claws Mail remains unusable.

Version-Release number of selected component (if applicable):

3.13.2-1

How reproducible:

See above.

Comment 1 Edward 2016-11-24 15:56:48 UTC
This also resulted in the account passwords being deleted for every account.

Comment 2 Michael Schwendt 2016-11-25 10:36:33 UTC
> During the upgrade process, dnf indicated Claws Mail and a few of its
> related plugins were being "downgraded",

Bad luck. 

Downgrades like that can break the installation in unknown ways, since forced downgrades of packages are untested. Upgrading an up-to-date installation with the very latest distribution release so shortly after its release has always been a risk due to downgrading installed packages as a result of missing zero day updates.

The newer Claws Mail for F25 had been in updates-testing already,
  https://bodhi.fedoraproject.org/updates/FEDORA-2016-70d5230795
but the F24 package has been automatically pushed to stable after reaching the tester feedback karma threshold.

Meanwhile, the F25 update is on its way into the stable updates repo, so either wait until it appears there, or get it while it's still in updates-testing:

  dnf --enablerepo=updates-testing update claws\*

As long as the Fedora Updates System is unable to ensure that older releases of the distribution cannot get ahead of the very latest release of the distribution, pushing updates to multiple distribution releases would need to be a manual task for the maintainers.

There is nothing that can be done about it anymore. Except that shortly before the release of the latest distribution (with all its freeze stages and update release hurdles), package maintainers must be more careful and avoid relying on the karma system in the Fedora Updates System for pushing updates to multiple dists.

Comment 3 Michael Schwendt 2016-11-25 10:52:20 UTC
*** Bug 1398482 has been marked as a duplicate of this bug. ***

Comment 4 David Gibson 2016-11-29 01:02:37 UTC
Looks like I've now updated to claws-mail-3.14.0-1.fc25.x86_64.  I'm not sure if it was that, but for whatever reason, claws got the type of the mailbox wrong *again*.

Screwing this up on upgrade is much less forgivable that screwing it up on downgrade.

Comment 5 Michael Schwendt 2016-11-29 13:22:19 UTC
And?

Comment 6 David Gibson 2016-11-30 00:13:50 UTC
..and some acknowledgement that there's a real bug here, causing real frustration would be nice.

Comment 7 Michael Schwendt 2016-11-30 11:36:35 UTC
Real frustration? Don't turn this into your pet peeve bug, please.

Blame the Fedora release process for not avoiding the package downgrade and for not even warning package maintainers about an update that's been stuck in updates-testing instead of becoming a zero-day update. What has happened to the upgrade path violations checker?

The downgrade is completely untested and unsupported. It should not have happened.

As whether downgrading, breaking the config and then upgrading again causes more side-effects, I don't know. The update needed to get out. It would have worked fine without doing any downgrade.

Btw, 3.14.1 is in updates-testing meanwhile, too.

Comment 8 David Gibson 2016-12-01 00:45:46 UTC
Ok, fair enough.


Note You need to log in before you can comment on or make changes to this bug.