Your message dated Fri, 16 Sep 2016 14:19:45 -0300
with message-id <5176285.MyD69q1Mza@tonks>
and subject line Re: Bug#837890: libqt5sql5-sqlite: 
/usr/lib/x86_64-linux-gnu/cmake/Qt5Sql/Qt5Sql_QSQLiteDriverPlugin.cmake is 
missing
has caused the Debian Bug report #837890,
regarding libqt5sql5-sqlite: 
/usr/lib/x86_64-linux-gnu/cmake/Qt5Sql/Qt5Sql_QSQLiteDriverPlugin.cmake is 
missing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
837890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5sql5-sqlite
Version: 5.3.2+dfsg-4+deb8u1
Severity: normal

Dear Maintainer,

The /usr/lib/x86_64-linux-gnu/cmake/Qt5Sql/Qt5Sql_QSQLiteDriverPlugin.cmake 
file is missing (it's loaded by 
/usr/lib/x86_64-linux-gnu/cmake/Qt5Sql/Qt5SqlConfig.cmake) to populate 
Qt5::QSQLiteDriverPlugin (which then could be used to locate the plugin withing 
cmake).
I found the issue on debian 8 and 7 with backports, both on x86 and amd64.


-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5sql5-sqlite depends on:
ii  libc6              2.19-18+deb8u4
ii  libqt5core5a       5.3.2+dfsg-4+deb8u1
ii  libqt5sql5         5.3.2+dfsg-4+deb8u1
ii  libsqlite3-0       3.8.7.1-1+deb8u1
ii  libstdc++6         6.1.1-9
ii  multiarch-support  2.19-18+deb8u4

libqt5sql5-sqlite recommends no packages.

libqt5sql5-sqlite suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
tag 837890 wontfix
thanks

On viernes, 16 de septiembre de 2016 11:59:21 A. M. ART Lisandro Damián 
Nicanor Pérez Meyer wrote:
> tag 837890 - moreinfo
> thanks
> 
> On viernes, 16 de septiembre de 2016 8:58:56 A. M. ART Paul Labedan wrote:
> > Hi Lisandro Damián Nicanor,
> > 
> > In fact, locating the plugin to ship it on a bundled app is my point: I
> > build a Qt5 application and I would like to make it available for Wheezy
> > without backports (some of the machines I'm targeting have limited
> > internet
> > access and won't have access to backports easily), for this purpose I have
> > to ship Qt5 libs and plugins within the app.
> 
> Mmm, definitely not what one would expect in Debian, but I see your use case
> here. OK, we will discuss this with the team.

We discussed this with the team and reached the conclusion that we do indeed 
want to avoid this kind of usage. Don't get us wrong: there are better ways to 
handle this.

In your case you have (at least) two options:

1) Backport Qt and use proper Debian packaging. Even if you have limited 
access you still have to ship the necessary libs within your app, so you can 
still ship the necessary packages.

2) Compile your own static Qt and use it to compile your application.

By the way:

- we can't provide backports anymore because shipping them would mean 
necessary rebuilds of some stuff which doesn't seems to be the idea behind 
debian-backports.

- Plugins files are referred in CMake files with globing, thus if no plugin's 
cmake config file is found stuff should still work.

Kinds regards, Lisandro.

-- 
<rata> hmm, el enchufe hace chispas...
<-- rata ha dejado este servidor ("Leaving").
<marga> ouch
  Visto en #lugfi, irc.freenode.net

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to