[Bug 1663716] Re: package kaccounts-providers (not installed) failed to install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-options.d/accounts.google.com.conf“, který je také v balíku accou

2017-02-10 Thread Hans Joachim Desserud
*** This bug is a duplicate of bug 1622499 *** https://bugs.launchpad.net/bugs/1622499 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1622499, so it is being marked as such. Please

[Bug 1663716] [NEW] package kaccounts-providers (not installed) failed to install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-options.d/accounts.google.com.conf“, který je také v balíku acc

2017-02-10 Thread David Jezek
Public bug reported: package kaccounts-providers (not installed) failed to install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit- options.d/accounts.google.com.conf“, který je také v balíku account- plugin-google 0.13+16.10.20160929.1-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu

[Bug 1612835] Re: Please remove jasper from Zesty

2017-02-10 Thread Adam Conrad
Removing packages from zesty: jasper 1.900.1-debian1-2.4+deb8u1 in zesty libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty amd64 libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty arm64 libjasper-dev 1.900.1-debian1-2.4+deb8u1 in zesty armhf

[Bug 1612835] Re: Please don't depend on jasper

2017-02-10 Thread Tyler Hicks
** Description changed: Jasper is being removed from Debian. It would be great if this could be - done in Ubuntu too before 16.10 is released. + done in Ubuntu too before 17.04 is released. https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html

[Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-10 Thread Andre Heinecke
Ah but now armhf and arm64 fail because of the same problem. The connects in the Qt Testsuite fail. As I already mentioned I think its some incompatibility between the Qt buildflags and the QGpgME buildflags: https://bugreports.qt.io/browse/QTBUG-36129 but I'm not sure what the suggestion from