From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] printing pdfs
Date: Thu, 28 May 2020 19:34:04 -0400 [thread overview]
Message-ID: <GO7YK3DD.DXSHJPUJ.E35AEKZS@CCBZ272R.KLJQYPBS.2W77BMST> (raw)
In-Reply-To: <39db9d00-1fe2-3dfd-195a-f98b450478c4@verizon.net>
On 2020.05.28 19:04, james wrote:
> On 5/28/20 4:30 PM, Francesco Turco wrote:
>> On Thu, May 28, 2020, at 22:11, james wrote:
>>> So what application/strategy gets me past errors like this:
>>>
>>> "Cannot mix incompatible Qt library (version 0x50e01) with this
>>> library
>>> (version 0x50e02)"
>>
>> Which application are you printing from?
>> I guess it's a Qt application. In that case, please verify that all
>> packages in the dev-qt category on your system have the same version
>> number.
>>
>> You can use eix, for example:
>>
>> $ eix --category dev-qt --installed --compact
>>
>
> 35 matches. Yes I run lxde and many qt codes.
>
> Perhaps better these are currenly blocked (will not update) qt:
>
> U ~] dev-qt/qtcore-5.15.0 [5.14.2]
> U ~] dev-qt/qtxml-5.15.0 [5.14.2]
> U dev-qt/qtnetwork-5.15.0 [5.14.2] USE="-libressl%"
> U ~] dev-qt/qttest-5.15.0 [5.14.2]
> U ~] dev-qt/qtdbus-5.15.0 [5.14.2]
>
> U ~] dev-qt/qtgui-5.15.0 [5.14.2]
> U ~] dev-qt/qtx11extras-5.15.0 [5.14.2]
> U ~] dev-qt/qtwidgets-5.15.0 [5.14.2]
> U ~] dev-qt/qtdeclarative-5.15.0 [5.14.2]
> U ~] dev-qt/qtopengl-5.15.0 [5.14.2]
> U ~] dev-qt/linguist-tools-5.15.0 [5.14.2]
> U ~] dev-qt/qtmultimedia-5.15.0 [5.14.2]
> U ~] dev-qt/qtpositioning-5.15.0 [5.14.2]
> U ~] dev-qt/qtwayland-5.15.0 [5.14.2]
> U ~] dev-python/qtawesome-0.7.2 [0.7.1]
That's not output from the above command (dev-python wouldn't be
there.) Please show the output of the above eix command, or perhaps
try "eix-installed -a | grep dev-qt" for another look to be sure all
are at the same version.
>
> Not staying up with the very latest qt packages, causes even more
> problems. I usually have to wait, up to 7 days, as the others trickle
> in and the all the qt packages will install. Sometime I have to
> remove them all, then do the upgrade.
>
> This is the first time it has affected pdf files.
>
> Palemoon will not even load pdfs, at least this version::
>
> NewMoon: 28.9.3 (the unofficial build of PaleMoon.)
>
> I'll guess I just wait a few days and see what trickles in on qqt
> upgrades:
>
> <startsnip>
> (dev-qt/qtcore-5.15.0:5/5.15.0::gentoo, ebuild scheduled for merge)
> USE="icu -debug -old-kernel (-systemd) -test" ABI_X86="(64)"
> conflicts with
> ~dev-qt/qtcore-5.14.2:5/5.14.2= required by
> (dev-qt/qtnetwork-5.14.2:5/5.14::gentoo, installed) USE="ssl -bindist
> -connman -debug -gssapi -libproxy -networkmanager -sctp -test"
> ABI_X86="(64)"
> ^ ^^^^^^^^^^
> ~dev-qt/qtcore-5.14.2 required by
> (dev-qt/qtgraphicaleffects-5.14.2:5/5.14::gentoo, installed)
> USE="-debug -test" ABI_X86="(64)"
> ^ ^^^^^^
> ~dev-qt/qtcore-5.14.2:5= required by
> (dev-qt/qtxml-5.14.2:5/5.14::gentoo, installed) USE="-debug -test"
> ABI_X86="(64)"
> ^ ^^^^^^
> ~dev-qt/qtcore-5.14.2:5/5.14.2= required by
> (dev-qt/qtdiag-5.14.2:5/5.14::gentoo, installed) USE="network widgets
> -debug -test" ABI_X86="(64)"
> <endsnip>
What is trying to pull in qtcore-5.15.0? You started this with a
problem of pdf viewers all complaining about mismatched qt versions,
but this looks like a portage issue. If you are manually marking
dev-qt packages as ~, you have to be sure you have gotten them all.
All dev-qt packages (some, such as qt-creator are on a different number
scheme) must have the same version. They are generally released all at
the same time, so incomplete upgrades are likely due to a problem in
package.accepted_keywords.
next prev parent reply other threads:[~2020-05-28 23:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Abxaq-8iU-9@gated-at.bofh.it>
[not found] ` <Abxaq-8iU-7@gated-at.bofh.it>
[not found] ` <Abxk6-8m0-13@gated-at.bofh.it>
2020-05-28 23:04 ` [gentoo-user] printing pdfs james
2020-05-28 23:34 ` Jack [this message]
2020-05-29 22:30 ` james
2020-05-29 23:31 ` Jack
2020-05-30 7:58 ` Neil Bothwick
2020-05-30 12:54 ` james
2020-05-30 14:39 ` Francesco Turco
2020-05-29 0:05 ` Dale
2020-05-29 7:58 ` Francesco Turco
[not found] ` <AbFB0-4ZK-7@gated-at.bofh.it>
2020-05-30 13:06 ` james
2020-05-30 13:24 ` Ashley Dixon
2020-05-30 18:25 ` Neil Bothwick
2020-05-30 21:38 ` Peter Humphrey
[not found] <3f9a2e62-c430-5295-d2b9-1b7a30c1cfd2.ref@verizon.net>
2020-05-28 20:11 ` james
2020-05-28 20:21 ` Francesco Turco
2020-05-28 20:22 ` Arve Barsnes
2020-05-28 21:10 ` Dale
2020-05-28 22:25 ` Jens Reinemuth
2020-05-29 5:10 ` Ashley Dixon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=GO7YK3DD.DXSHJPUJ.E35AEKZS@CCBZ272R.KLJQYPBS.2W77BMST \
--to=ostroffjh@users.sourceforge.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox