After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 749931 - geary 0.10.x is removed upon installing libgcr update
geary 0.10.x is removed upon installing libgcr update
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: general
0.10.x
Other Linux
: Normal critical
: 0.11.0
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-05-26 21:08 UTC by Behrooz Nobakht
Modified: 2016-05-15 07:27 UTC
See Also:
GNOME target: ---
GNOME version: 3.15/3.16


Attachments
Depend on actual libgcr packages, not transitional one (879 bytes, patch)
2015-05-27 17:22 UTC, Robert Schroll
committed Details | Review

Description Behrooz Nobakht 2015-05-26 21:08:20 UTC
Today I update my GNOME installation via https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging. This removes `libgcr-3-1` and installs `libgcr-base-3-1` and `libgcr-ui-3-1`. This leads to removing geary from daily PPA and then it cannot be installed because it seems libgcr packaging has changed. 

$ sudo apt-get install geary

The following packages have unmet dependencies:
 geary : Depends: libgcr-3-1 (>= 3.10.1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Comment 1 Robert Schroll 2015-05-27 05:23:40 UTC
It looks like as of Ubuntu 14.04, libgcr is a transitional package that requires -base and -ui.  We should be able to change our dependencies without any problem.
Comment 2 Robert Schroll 2015-05-27 17:22:41 UTC
Created attachment 304092 [details] [review]
Depend on actual libgcr packages, not transitional one

I assume this will do what we need, but I don't know how we build debian 
packages, so I haven't tested it.
Comment 3 Behrooz Nobakht 2015-06-01 15:55:42 UTC
Hi Robert, 

Thank you for your patch on this. Any chance you might know how this bug can be prioritized a bit more? I'd be more than happy to open a PR on GitHub if necessary. 

My reason is quite simple. All users like me that use GNOME staging ppa on Ubuntu would face the same situation and would be imposed to remove Geary. Unless, they revert to way older versions to get it again.

Thanks,
Behrooz

P.S. increasing priority to 'critical'.
Comment 4 pulpo69 2015-06-02 12:38:57 UTC
The same thing happens when using geary from stable ppa and https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging.
Comment 5 Behrooz Nobakht 2015-06-09 06:02:01 UTC
I opened a PR at GitHub: 

https://github.com/GNOME/geary/pull/2

I hope it can be merged soon.
Comment 6 Robert Schroll 2015-06-10 01:53:48 UTC
Attachment 304092 [details] pushed as af5dc85 - Depend on actual libgcr packages, not transitional one
Comment 7 Behrooz Nobakht 2015-06-10 11:32:04 UTC
Thanks. I confirm that I could install it via daily ppa from Yorba.
Comment 8 Robert Schroll 2015-06-10 23:09:33 UTC
Good to hear.

For future reference: we don't, at the moment, follow pull-requests on Github.  This is an automatic mirror largely our of our control.