Description of problem: After updating to isync-1.1.2-1.fc21 I can no longer sync my mailbox with the following errors: $ mbsync rh Reading configuration file /home/contyk/.mbsyncrc Channel rh Opening master rh-remote... Resolving *... ok Connecting to * (*)... Opening slave rh-local... Connection is now encrypted Logging in... Selecting master Sent... Selecting slave Sent... Loading master... Loading slave... Maildir error: UID 679379 is beyond highest assigned UID 3312. Selecting master INBOX... Selecting slave INBOX... Loading master... Loading slave... Maildir error: UID 679549 is beyond highest assigned UID 425626. Version-Release number of selected component (if applicable): isync-1.1.2-1.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. Upgrade from isync-1.1.1-3.fc21 to 1.1.2-1.fc21 2. Try to sync your mail Actual results: UID errors (see above). Expected results: Everything works just like before. Additional info: Downgrading back to 1.1.1-3.fc21 resolves the issue for me.
isync-1.2.0-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/isync-1.2.0-1.fc21
isync-1.2.0-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/isync-1.2.0-1.fc22
isync-1.2.0-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/isync-1.2.0-1.fc20
isync-1.2.0-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/isync-1.2.0-1.el7
Package isync-1.2.0-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing isync-1.2.0-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5624/isync-1.2.0-1.fc22 then log in and leave karma (feedback).
This release doesn't fix the issue at all.
isync-1.2.0-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/isync-1.2.0-2.fc22
isync-1.2.0-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/isync-1.2.0-2.fc21
isync-1.2.0-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/isync-1.2.0-2.fc20
isync-1.2.0-2.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/isync-1.2.0-2.el7
Package isync-1.2.0-2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing isync-1.2.0-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5771/isync-1.2.0-2.fc22 then log in and leave karma (feedback).
1.2.0-2 doesn't do anything about it either. Please, don't include this bug in updates that don't even attempt to fix it.
I've already spent ~50 hours to pull my mailbox with the new mbsync and it works -- I can use my mail again; I'm still keeping the old directory for testing this, though. The problem is mailboxes created with pre-1.1.2 releases don't work with the new versions (or that's my case, at least). This wouldn't be that bad if this didn't land in stable releases without a warning or migration tools. If nothing is going to be done about this, just close the bug with WONTFIX, I suppose. Better than keeping it open forever or closing it as a part of an unrelated update.
Package isync-1.2.0-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing isync-1.2.0-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5842/isync-1.2.0-2.fc21 then log in and leave karma (feedback).
Bug reported upstream: https://sourceforge.net/p/isync/bugs/19/
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.