Processed: tagging 1008827

2022-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1008827 + pending
Bug #1008827 [kde-standard] KDE Applications 21.12.3
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1008827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processing of umbrello_22.12.0-3_source.changes

2022-12-26 Thread Debian FTP Masters
umbrello_22.12.0-3_source.changes uploaded successfully to localhost
along with the files:
  umbrello_22.12.0-3.dsc
  umbrello_22.12.0-3.debian.tar.xz
  umbrello_22.12.0-3_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



umbrello_22.12.0-3_source.changes ACCEPTED into unstable

2022-12-26 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2022 10:44:22 +0100
Source: umbrello
Architecture: source
Version: 4:22.12.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Changes:
 umbrello (4:22.12.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Make the test suite non-fatal on mipsel, and powerpc:
 - on mipsel it started to fail recently, and I cannot reproduce the failure
   on the porterbox
 - on powerpc it has been always failing since the test suite was enabled
Checksums-Sha1:
 4df8486d5e08d46c88b20d5e69f3c4a00a55221f 2550 umbrello_22.12.0-3.dsc
 e59106e648ff40cb191177bb55a6525768903100 18376 umbrello_22.12.0-3.debian.tar.xz
 45b4401e351d7cc72fef46fe32cbe601998b98e7 19608 
umbrello_22.12.0-3_source.buildinfo
Checksums-Sha256:
 62912d0835afa2e5efbd1eaac090da16aafd89a2058fdfeb3688200b5071a7f5 2550 
umbrello_22.12.0-3.dsc
 1ea38ca83051c9dbd86c32c2f9f08c033731123793b76968eba8a756d9688457 18376 
umbrello_22.12.0-3.debian.tar.xz
 6b3c7c51fdebca51bec27aec8fe57bf73effaee3d222e92d3ca584150b57e1ea 19608 
umbrello_22.12.0-3_source.buildinfo
Files:
 ac2513a6d473318d60c4ed936aee03cf 2550 kde optional umbrello_22.12.0-3.dsc
 c88afafa37e32655c5489800d4c80c10 18376 kde optional 
umbrello_22.12.0-3.debian.tar.xz
 8ee0b104b84d36ff2b990efcd22a6838 19608 kde optional 
umbrello_22.12.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmOpbSkACgkQLRkciEOx
P00tohAAgEpwotR4m5DymDfeJT4NmETLjPqjZxjlC5oYBKs8Ux8+n83NfjouM1f8
YKIFMpkzdMl5BPMP+PK5D3vRVVXTYPEAjQJO9FzCLOPyDF6c3DOz9LiOX9RsHnPW
9M9Y/1diE9GChdHrSHDdm4/6AxMFKmKZPGtbzLhSe4JIu3Ok2Yeh6VXExeIg/sRp
SDThiuPOhDJ2xatK+ZSJkPOv4yuNcAqUgKdgqIek842Oe8mFJJv4A1RphhN3lqOB
8NqwxRddMBAIFqPgd33SFzexefibUuq4vIdlDdUDkK+LqGYNxUnGOYS2Clv4snep
czqnHbBW3YBSNX1FT0ogTblZD2pM9JtekN6NZeOgh5B55vmlilXdZLM5wbmxHQeR
Gnt/a7UzgiRJ40Zyy6e+GMjDhBM9HL8OYOmxkfXVv+CrIqo4BGlCh+NjAAq1VGj4
YRS77WuyjCAtbTpMyzHV5n8u3okiPI6yb+pOINFQ/hqs90dCvOaFgkefn/n/W3CC
iaPMvyE471Dg5gcOa4UU/5Jo6qMrvPRTnSJw5H6/HPUV/f0i3oyAi661/YewQ02D
RH8p2i2SySe/Mr9He0Bb3/vo9MkdtqbCgVc7Reig94uShu6WE97W3udIg2VHGzN/
A1dIxJpouGLCCdFFmvsxOgjJKwn9JFvUv4rZT7h2+S72IDYS938=
=rCC4
-END PGP SIGNATURE-



Processing of meta-kde_136_source.changes

2022-12-26 Thread Debian FTP Masters
meta-kde_136_source.changes uploaded successfully to localhost
along with the files:
  meta-kde_136.dsc
  meta-kde_136.tar.xz
  meta-kde_136_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#1008827: marked as done (KDE Applications 21.12.3)

2022-12-26 Thread Debian Bug Tracking System
Your message dated Mon, 26 Dec 2022 10:38:27 +
with message-id 
and subject line Bug#1008827: fixed in meta-kde 5:136
has caused the Debian Bug report #1008827,
regarding KDE Applications 21.12.3
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.)


-- 
1008827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-standard
Version: 5:120

Please update the KDE applications elisa, kdepim-addons, src:libkcddb,
src:libkf5kdcraw, src:libkf5kexiv2, src:libkf5kipi, src:kitinerary and
sweeper.
Also consider bumping the dependency version annotations in
kde-standard from 21.08.0 to 21.12.3.
--- End Message ---
--- Begin Message ---
Source: meta-kde
Source-Version: 5:136
Done: Pino Toscano 

We believe that the bug you reported is fixed in the latest version of
meta-kde, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated meta-kde package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2022 11:05:31 +0100
Source: meta-kde
Architecture: source
Version: 5:136
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 1008827
Changes:
 meta-kde (5:136) unstable; urgency=medium
 .
   * Bump the minimum KDE Application version to 4:22.12.0. (Closes: #1008827)
   * Update standards version to 4.6.2, no changes needed.
Checksums-Sha1:
 485ed145bb5a43d01d3ebdf218f123450edb4df7 2510 meta-kde_136.dsc
 bc62eed6759a33abb7f9bd67abb5a58a57302870 16752 meta-kde_136.tar.xz
 1a6e09c5c706e75e6c099ba515ceb1dc429d2690 6256 meta-kde_136_source.buildinfo
Checksums-Sha256:
 95894f1b576c64e51e99309e6dc9dec2c61ab296491886f551373e1a76284276 2510 
meta-kde_136.dsc
 3e5bc0126c2747dd9ac5169679009d2c130eb2a97f0ac449b76961944cccdb36 16752 
meta-kde_136.tar.xz
 aedcaf7d93a6dede45816a06ebab3b570668630ae6afa18f43b510b80620919d 6256 
meta-kde_136_source.buildinfo
Files:
 fa6e6f2954b669e38a5526dedb97c587 2510 metapackages optional meta-kde_136.dsc
 644eb6187a343914d6d42091459b4d69 16752 metapackages optional 
meta-kde_136.tar.xz
 10ca46c4ae25fae3406cdb70e2529e00 6256 metapackages optional 
meta-kde_136_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmOpciEACgkQLRkciEOx
P00zfw//TiBrQDcCtuYNvLaq9dosTWpq2alPPy6SjpzkV2sMxKtUQlhLKtS3JPX1
1qKx0AMTG5whrQXpMY3Sb/swdB1HE09BHwPt6lFVeFvTykErOrcNpyQurBs9pZXo
botyPBPAdYsKD/mdKkEKc6tqHmQzHlKod48K3mG5qAe3IolkVTy0GK8yoXyCSfJ7
lZT9acNOKz3QJxZs2yKScsrunR4BT1cGuUPkLLr1gysr/BnfXAGbz/4Ed0blbdFE
VBIk+633jdu1vDU6fyK2bc+mi6zKj2mYPNdTlkNf+CcW0ilc5r+BPkcTCAgTRN4W
zCBt6XhvFmSwPqwyG1X3xAqrdtDyJIIDtNTKB2bf45YoFIgC7gVm9LAoCawfbd2P
hcFWX8EU9EtdAPjQR4w8k8tULGg+X5O11YxQ2kdwJAi6yjlPkX8XszntktXj5+O5
pmNlVFNsAtau5iVvaiVC46+rYeofKI0vTLlqkMmY3qFLhHjAwCZLWcCW4UalgtMZ
Xoqj3QGg7WZSPKWSo0RNrpWOuw5QYciqhTyY3XS5w/k9CA2EWUfAIhulSeCIjhDG
tWz3JLoO4IeqWPo8WfJAB0oCvS6TMdXj5p3YjgFV3ATWJQkQxO2Crig44F3Gc3By
BQrSO2XOA2UESirXGp9fnYmGC3o0pUeQ2dWYra3lRGHNqyRPoxw=
=MgnM
-END PGP SIGNATURE End Message ---


meta-kde_136_source.changes ACCEPTED into unstable

2022-12-26 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2022 11:05:31 +0100
Source: meta-kde
Architecture: source
Version: 5:136
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 1008827
Changes:
 meta-kde (5:136) unstable; urgency=medium
 .
   * Bump the minimum KDE Application version to 4:22.12.0. (Closes: #1008827)
   * Update standards version to 4.6.2, no changes needed.
Checksums-Sha1:
 485ed145bb5a43d01d3ebdf218f123450edb4df7 2510 meta-kde_136.dsc
 bc62eed6759a33abb7f9bd67abb5a58a57302870 16752 meta-kde_136.tar.xz
 1a6e09c5c706e75e6c099ba515ceb1dc429d2690 6256 meta-kde_136_source.buildinfo
Checksums-Sha256:
 95894f1b576c64e51e99309e6dc9dec2c61ab296491886f551373e1a76284276 2510 
meta-kde_136.dsc
 3e5bc0126c2747dd9ac5169679009d2c130eb2a97f0ac449b76961944cccdb36 16752 
meta-kde_136.tar.xz
 aedcaf7d93a6dede45816a06ebab3b570668630ae6afa18f43b510b80620919d 6256 
meta-kde_136_source.buildinfo
Files:
 fa6e6f2954b669e38a5526dedb97c587 2510 metapackages optional meta-kde_136.dsc
 644eb6187a343914d6d42091459b4d69 16752 metapackages optional 
meta-kde_136.tar.xz
 10ca46c4ae25fae3406cdb70e2529e00 6256 metapackages optional 
meta-kde_136_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmOpciEACgkQLRkciEOx
P00zfw//TiBrQDcCtuYNvLaq9dosTWpq2alPPy6SjpzkV2sMxKtUQlhLKtS3JPX1
1qKx0AMTG5whrQXpMY3Sb/swdB1HE09BHwPt6lFVeFvTykErOrcNpyQurBs9pZXo
botyPBPAdYsKD/mdKkEKc6tqHmQzHlKod48K3mG5qAe3IolkVTy0GK8yoXyCSfJ7
lZT9acNOKz3QJxZs2yKScsrunR4BT1cGuUPkLLr1gysr/BnfXAGbz/4Ed0blbdFE
VBIk+633jdu1vDU6fyK2bc+mi6zKj2mYPNdTlkNf+CcW0ilc5r+BPkcTCAgTRN4W
zCBt6XhvFmSwPqwyG1X3xAqrdtDyJIIDtNTKB2bf45YoFIgC7gVm9LAoCawfbd2P
hcFWX8EU9EtdAPjQR4w8k8tULGg+X5O11YxQ2kdwJAi6yjlPkX8XszntktXj5+O5
pmNlVFNsAtau5iVvaiVC46+rYeofKI0vTLlqkMmY3qFLhHjAwCZLWcCW4UalgtMZ
Xoqj3QGg7WZSPKWSo0RNrpWOuw5QYciqhTyY3XS5w/k9CA2EWUfAIhulSeCIjhDG
tWz3JLoO4IeqWPo8WfJAB0oCvS6TMdXj5p3YjgFV3ATWJQkQxO2Crig44F3Gc3By
BQrSO2XOA2UESirXGp9fnYmGC3o0pUeQ2dWYra3lRGHNqyRPoxw=
=MgnM
-END PGP SIGNATURE-



Bug#1025663: qmake6: how should users query for QT_INSTALL_PLUGINS?

2022-12-26 Thread Lisandro Damián Nicanor Pérez Meyer
Hi!

As usual I'm a little bit behind this with emails, so I just saw this.

On Thu, 8 Dec 2022 at 08:48, Helmut Grohne  wrote:
[snip]
> I'd like to get some reply from Patrick before moving forward with this
> though. And it would be super awesome if this could be included in
> bookworm, so time isn't infinite here.

I would very much prefer (a). Now, as you said, timing is important
here. Do we need a pass through NEW? If that's the case then that will
need to happen after the next transition, if time allows it. If it can
be easily added to the existing packaging without the need of NEW then
we might add it right now.

Last time you did the packaging with DMitry, so I'm kind of lost here.

Regards, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/



Bug#1025663: qmake6: how should users query for QT_INSTALL_PLUGINS?

2022-12-26 Thread Dmitry Shachnev
Hi all,

as I was mentioned in this discussion...

On Mon, Dec 26, 2022 at 10:27:18AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> I would very much prefer (a). Now, as you said, timing is important
> here. Do we need a pass through NEW? If that's the case then that will
> need to happen after the next transition, if time allows it. If it can
> be easily added to the existing packaging without the need of NEW then
> we might add it right now.
>
> Last time you did the packaging with DMitry, so I'm kind of lost here.

...I would also prefer if Qt 6 used a similar setup to Qt 5. This way the
transition from Qt 5 to Qt 6 would be more transparent for the reverse
dependencies. E.g. they will only need to replace ${DEB_HOST_GNU_TYPE}-qmake
with ${DEB_HOST_GNU_TYPE}-qmake6.

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries

2022-12-26 Thread Dmitry Shachnev
Hi all!

(And sorry for the late response. debian-qt-kde@lists.debian.org is a
list for bots, so I didn't get it in my inbox. It's better to use
pkg-kde-t...@alioth-lists.debian.net or @packages.debian.org.)

On Tue, Dec 13, 2022 at 10:43:06AM -0700, Soren Stoutner wrote:
> Can one of the Debian Qt/KDE maintainers weigh in on the feasibility of
> either creating a meta package that depends on the most recent package
> that includes qwebengine_convert_dict or creating an unversioned package
> that installs qwebengine_convert_dict?  Also, either having
> qwebengine_convert_dict being installed in an unversioned location or
> having a symlink that is unversioned?  That would make it easier for
> Hunspell language packages to build-depend on qwebengine_convert_dict and
> wouldn’t require reworking all of those packages’ build scripts every time
> the version of Qt in Debian changes.

I think we can do this, but why do you think such tool should be provided by
Qt WebEngine, not by Chromium itself?

Chromium is the main upstream for convert_dict tool, while Qt WebEngine is one
of several wrappers around it (e.g. another one is Electron). Also having it
in Chromium will help to avoid the problem with versions, as there is always
only one version of Chromium.

Source code for convert_dict is present in the Chromium tarball [1], so it
shouldn't be hard to provide a new binary package for it.

(Maybe this was already discussed in the thread, but I did not read every
message, please give me a link if it's the case.)

[1]: 
https://sources.debian.org/src/chromium/108.0.5359.124-1/chrome/tools/convert_dict/

--
Dmitry Shachnev


signature.asc
Description: PGP signature


Bug#1027036: O: libiodbc2 -- iODBC Driver Manager

2022-12-26 Thread Aurélien COUDERC
Package: wnpp
Severity: normal
X-Debbugs-Cc: libiod...@packages.debian.org, Debian Qt/KDE Maintainers 

Control: affects -1 + src:libiodbc2

I intend to orphan the libiodbc2 package.

The package used to be required by the KDE stack but it’s not the case
anymore since a couple of releases and so the Qt/KDE Team hasn’t been
updating it.

The project is not dead upstream and has seen several new releases since
the last upstream version we packaged in 2014.


The package description is:
 The iODBC (intrinsic Open Database Connectivity) driver manager is compatible
 with the ODBC 2.x and 3.x specification and performs all the jobs of a
 ODBC driver manager (i.e. driver loading, parameters and function sequence
 checking, driver's function invoking, etc). Any ODBC driver working with
 ODBC 2.0 and 3.x driver manager will also work with iODBC driver manager
 and vice versa.
 .
 Applications (using ODBC function calls) linked with iODBC driver manager
 will be able to simultaneously access different types of data sources within
 one process through suitable iODBC drivers.
 .
 This package contains the library files. Look for the iodbc package, too!


Processing of libkeduvocdocument_22.12.0-1_source.changes

2022-12-26 Thread Debian FTP Masters
libkeduvocdocument_22.12.0-1_source.changes uploaded successfully to localhost
along with the files:
  libkeduvocdocument_22.12.0-1.dsc
  libkeduvocdocument_22.12.0.orig.tar.xz
  libkeduvocdocument_22.12.0.orig.tar.xz.asc
  libkeduvocdocument_22.12.0-1.debian.tar.xz
  libkeduvocdocument_22.12.0-1_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



libkeduvocdocument_22.12.0-1_source.changes ACCEPTED into unstable

2022-12-26 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Dec 2022 22:17:57 +0100
Source: libkeduvocdocument
Architecture: source
Version: 4:22.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Aurélien COUDERC 
Changes:
 libkeduvocdocument (4:22.12.0-1) unstable; urgency=medium
 .
   [ Aurélien COUDERC ]
   * New upstream release (22.12.0).
   * Update build-deps and deps with the info from cmake.
   * Bump Standards-Version to 4.6.2, no change required.
Checksums-Sha1:
 64e51a1c9178bc9f7c0545a9925973e76d43443c 2789 libkeduvocdocument_22.12.0-1.dsc
 05f0a31cae3d93cf0c87bbb3d3241d0b359fcebc 230244 
libkeduvocdocument_22.12.0.orig.tar.xz
 9e57109f7c5f4fa774523862bf2b8fbc87fa2c18 833 
libkeduvocdocument_22.12.0.orig.tar.xz.asc
 944b0b59eedfed1080ff593e6b873aced0e19132 14176 
libkeduvocdocument_22.12.0-1.debian.tar.xz
 08d2f7da4e3fef3bbe3fa82887808a249e6253d2 16137 
libkeduvocdocument_22.12.0-1_amd64.buildinfo
Checksums-Sha256:
 7c79f88916353ae70fdc90865241c379fc3167f6fa5cfe22526efe42ff50eb66 2789 
libkeduvocdocument_22.12.0-1.dsc
 909b2adcb9ec64d3d78e0c8e8228d3969b367efc32eec8030e78f8bf91fd 230244 
libkeduvocdocument_22.12.0.orig.tar.xz
 c79420a255a30d43bbe2ff707aea32c2f717adb1c27db589d3da27bbfa2d9ea1 833 
libkeduvocdocument_22.12.0.orig.tar.xz.asc
 57c771360bc49160525d87cb519af89cf39e58b33db40e4e761eba6ac4d3bbc8 14176 
libkeduvocdocument_22.12.0-1.debian.tar.xz
 c1b3368325cc3ca4dcbb4128aa682ea31bb0e3756dc33edca5879708d3af0b7a 16137 
libkeduvocdocument_22.12.0-1_amd64.buildinfo
Files:
 f362e78a9cd0a94fd526d228e0d963d3 2789 libs optional 
libkeduvocdocument_22.12.0-1.dsc
 0d21a7f0659a7cb028c91bc1c748d830 230244 libs optional 
libkeduvocdocument_22.12.0.orig.tar.xz
 66cb1dd5a75677126c985179526078a0 833 libs optional 
libkeduvocdocument_22.12.0.orig.tar.xz.asc
 b1900d7cccf1c3ddac8e889634d1d4ec 14176 libs optional 
libkeduvocdocument_22.12.0-1.debian.tar.xz
 44c6e8544ab0e5a29d5663530b694218 16137 libs optional 
libkeduvocdocument_22.12.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmOqD9oTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJIqYEACdzMxTNBIbMZQYWmBbRhfP21JZ65r2
O9tDNFhZCuOm4tQ1ngxTAnHx6pAX1xvRW4tU/y9OuC3besu0fhCPXQFSfdp8gYcH
v1QtFFiDLi58MQXafLhpq1f9nI9d1nHYSbc0rL0+a7uJTc03UHFRFAOijzrknSr8
ja1WR6JMxVFwMkr2NpCJdP/Rq8eCWIdHr5PDS6OniVLfNUE+eS4WTyfFMw4r4Nxc
jFTz3VkPaCpVZR5vy17XT8WYrqjwwu1hWYj+4IPHyqT/AN9gyXyhG1GF0gClVzA4
I4EaKkAbHyUuyQ46a1Fvb/tkqbG5qMbp09MvJUlA+O0oVnR8bEl0WTEWizqfvUpX
ZSgV5BvZq1hW/6cSpUDkeTXRnxEi4zrZJicG2IokJ5fsSRQTMC9HMHmVF4+5MWIw
ycIL7LqQcXMDXa+NGUgKyrLEo3ywPtfA63YlSCcJyQakweLnRRjAYNnd94+kW9dI
h07AQOQf/i7uydjHZaCg0WBtAvUhYqRoHETMiUCh/v5wJWAs2MNijwwtI46TXSEa
DpLHFFAvoxkva6FAiNNNonUim3zIoIL1wtaY+cGS/vApW6/VgDbKTraAFIcBBsVX
pPJCgf4MjO1PCZCGQNWbwMlR8OgFrUQ090TaQuokHgelJ1p4oB+x51pO067jtrMn
f33lJ0ENwXbTeQ==
=J6oX
-END PGP SIGNATURE-



Processed: tagging 1015619, tagging 1015621, tagging 1015620, tagging 1015618, tagging 1015614, tagging 1015616 ...

2022-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1015619 - bookworm sid
Bug #1015619 {Done: Patrick Franz } [src:qt6-declarative] 
qt6-declarative: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015621 - bookworm sid
Bug #1015621 {Done: Patrick Franz } [src:qt6-multimedia] 
qt6-multimedia: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015620 - bookworm sid
Bug #1015620 {Done: Patrick Franz } [src:qt6-lottie] 
qt6-lottie: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015618 - bookworm sid
Bug #1015618 {Done: Patrick Franz } [src:qt6-charts] 
qt6-charts: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015614 - bookworm sid
Bug #1015614 {Done: Patrick Franz } [src:qt6-3d] qt6-3d: 
ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015616 - bookworm sid
Bug #1015616 {Done: Patrick Franz } [src:qt6-5compat] 
qt6-5compat: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015623 - bookworm sid
Bug #1015623 {Done: Patrick Franz } [src:qt6-svg] qt6-svg: 
ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015627 - bookworm sid
Bug #1015627 {Done: Patrick Franz } [src:qt6-wayland] 
qt6-wayland: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm and sid.
> tags 1015629 - bookworm sid
Bug #1015629 {Done: Patrick Franz } [src:qt6-webchannel] 
qt6-webchannel: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> tags 1015625 - bookworm sid
Bug #1015625 {Done: Patrick Franz } [src:qt6-tools] 
qt6-tools: ftbfs with LTO (link time optimization) enabled
Removed tag(s) sid and bookworm.
> fixed 1000158 2:4.16.0+dfsg-1
Bug #1000158 {Done: Michael Tokarev } [samba] samba: random 
segfaults since upgrading to bullseye
Marked as fixed in versions samba/2:4.16.0+dfsg-1.
> tags 1027013 - sid bookworm
Bug #1027013 [src:llvm-toolchain-14] llvm-toolchain-14 autopkg test fails
Removed tag(s) bookworm and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1000158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000158
1015614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015614
1015616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015616
1015618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015618
1015619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015619
1015620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015620
1015621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015621
1015623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015623
1015625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015625
1015627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015627
1015629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015629
1027013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1025663: qmake6: how should users query for QT_INSTALL_PLUGINS?

2022-12-26 Thread Helmut Grohne
Control: tags -1 + patch

On Mon, Dec 26, 2022 at 10:27:18AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> I would very much prefer (a). Now, as you said, timing is important
> here. Do we need a pass through NEW? If that's the case then that will
> need to happen after the next transition, if time allows it. If it can
> be easily added to the existing packaging without the need of NEW then
> we might add it right now.

No, (a) does not require going through NEW. There already is qmake6-bin.
qmake6 and qmake6-bin even have the needed Multi-Arch values already.

> Last time you did the packaging with DMitry, so I'm kind of lost here.

Dmitry also expressed being in favour of (a). Notably missing is a
response from Patrick.

In any case, I've attached a patch for it now. It is based on what we do
for qt5.

I caution though that selecting version 5 or 6 is kinda messed up. If
you run qmake6 or -qmake6, it'll use qt6 as expected. If you
run plain qmake, it'll go through qtchooser and select the relevant
version via QT_SELECT. Howeve, -qmake is presently owned by
qt5-qmake only and will bypass qtchoser without honouring QT_SELECT. If
we want "QT_SELECT=6 -qmake" to run the cross qt6 qmake, we'll
also have to modify qtchooser and qt5-qmake.

Helmut
diff -Nru qt6-base-6.3.1+dfsg/debian/changelog 
qt6-base-6.3.1+dfsg/debian/changelog
--- qt6-base-6.3.1+dfsg/debian/changelog2022-10-01 18:58:47.0 
+0200
+++ qt6-base-6.3.1+dfsg/debian/changelog2022-12-26 22:56:51.0 
+0100
@@ -1,3 +1,10 @@
+qt6-base (6.3.1+dfsg-10.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install -qmake6 cross wrapper. (Closes: #1025663)
+
+ -- Helmut Grohne   Mon, 26 Dec 2022 22:56:51 +0100
+
 qt6-base (6.3.1+dfsg-10) unstable; urgency=medium
 
   [ Lisandro Damián Nicanor Pérez Meyer ]
diff -Nru qt6-base-6.3.1+dfsg/debian/qmake-cross-wrapper.in 
qt6-base-6.3.1+dfsg/debian/qmake-cross-wrapper.in
--- qt6-base-6.3.1+dfsg/debian/qmake-cross-wrapper.in   1970-01-01 
01:00:00.0 +0100
+++ qt6-base-6.3.1+dfsg/debian/qmake-cross-wrapper.in   2022-12-26 
22:56:51.0 +0100
@@ -0,0 +1,27 @@
+#!/bin/sh
+
+if [ "x$1" = x-qt6 ] || [ "x$1" = "x-qt=6" ] || [ "x$1" = "x-qt=qt6" ]; then
+   shift
+fi
+
+QMAKE_MODE=
+
+if [ "x$1" = x-query ]; then
+   exec /usr/lib/qt6/bin/qmake "$@" -qtconf 
/usr/lib/@DEB_HOST_MULTIARCH@/qt6/qt6.conf
+elif [ "x$1" = x-makefile ] || [ "x$1" = x-project ]; then
+   QMAKE_MODE="$1"
+   shift
+fi
+
+exec /usr/lib/qt6/bin/qmake6 \
+   $QMAKE_MODE \
+   -qtconf /usr/lib/@DEB_HOST_MULTIARCH@/qt6/qt6.conf \
+   -early \
+   QMAKE_CC=${CC:-@DEB_HOST_GNU_TYPE@-gcc} \
+   QMAKE_CXX=${CXX:-@DEB_HOST_GNU_TYPE@-g++} \
+   QMAKE_LINK=${CXX:-@DEB_HOST_GNU_TYPE@-g++} \
+   QMAKE_STRIP=${STRIP:-@DEB_HOST_GNU_TYPE@-strip} \
+   QMAKE_QMAKE=/usr/bin/@DEB_HOST_GNU_TYPE@-qmake6 \
+   PKG_CONFIG=@DEB_HOST_GNU_TYPE@-pkg-config \
+   -before \
+   "$@"
diff -Nru qt6-base-6.3.1+dfsg/debian/qmake6.install 
qt6-base-6.3.1+dfsg/debian/qmake6.install
--- qt6-base-6.3.1+dfsg/debian/qmake6.install   2022-04-22 19:50:08.0 
+0200
+++ qt6-base-6.3.1+dfsg/debian/qmake6.install   2022-12-26 22:56:45.0 
+0100
@@ -1,3 +1,4 @@
+usr/bin/*-qmake6
 usr/lib/${DEB_HOST_MULTIARCH}/qt6/mkspecs/aix-g++-64/qmake.conf
 usr/lib/${DEB_HOST_MULTIARCH}/qt6/mkspecs/aix-g++-64/qplatformdefs.h
 usr/lib/${DEB_HOST_MULTIARCH}/qt6/mkspecs/aix-g++/qmake.conf
diff -Nru qt6-base-6.3.1+dfsg/debian/rules qt6-base-6.3.1+dfsg/debian/rules
--- qt6-base-6.3.1+dfsg/debian/rules2022-09-17 19:21:11.0 +0200
+++ qt6-base-6.3.1+dfsg/debian/rules2022-12-26 22:56:51.0 +0100
@@ -89,6 +89,12 @@
sed 's/@DEB_HOST_MULTIARCH@/$(DEB_HOST_MULTIARCH)/' debian/qt.conf.in \
> debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/qt6/qt6.conf
 
+   mkdir -p debian/tmp/usr/bin
+   sed -e 's/@DEB_HOST_MULTIARCH@/$(DEB_HOST_MULTIARCH)/g' \
+   -e 's/@DEB_HOST_GNU_TYPE@/$(DEB_HOST_GNU_TYPE)/g' \
+   < debian/qmake-cross-wrapper.in > 
debian/tmp/usr/bin/$(DEB_HOST_GNU_TYPE)-qmake6
+   chmod +x debian/tmp/usr/bin/$(DEB_HOST_GNU_TYPE)-qmake6
+
 override_dh_makeshlibs:
dh_makeshlibs -XlibQt6EglFSDeviceIntegration -XlibQt6EglFsKmsGbmSupport 
-XlibQt6EglFsKmsSupport -XlibQt6XcbQpa
 


Processed: Re: Bug#1025663: qmake6: how should users query for QT_INSTALL_PLUGINS?

2022-12-26 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1025663 [qmake6] qmake6: how should users query for QT_INSTALL_PLUGINS?
Added tag(s) patch.

-- 
1025663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1025663: qmake6: how should users query for QT_INSTALL_PLUGINS?

2022-12-26 Thread Patrick Franz
Hi,

I agree that solution a) sounds like the better option, especially since 
we've gone this route with Qt 5.

However, I will revisit this issue once we have transitioned 6.4 into 
unstable.


-- 
Med vänliga hälsningar

Patrick Franz



Bug#1025663: qmake6: how should users query for QT_INSTALL_PLUGINS?

2022-12-26 Thread Lisandro Damián Nicanor Pérez Meyer
Hi,

On Mon, 26 Dec 2022 at 20:07, Helmut Grohne  wrote:
[snip]
> In any case, I've attached a patch for it now. It is based on what we do
> for qt5.

Thanks!

> I caution though that selecting version 5 or 6 is kinda messed up. If
> you run qmake6 or -qmake6, it'll use qt6 as expected. If you
> run plain qmake, it'll go through qtchooser and select the relevant
> version via QT_SELECT. Howeve, -qmake is presently owned by
> qt5-qmake only and will bypass qtchoser without honouring QT_SELECT. If
> we want "QT_SELECT=6 -qmake" to run the cross qt6 qmake, we'll
> also have to modify qtchooser and qt5-qmake.

We don't want to mix qtchooser and Qt 6. qtchooser is currently
deprecated and will disappear with Qt 5. It's not worth the effort to
remove it right now (I think). so the current behavior makes sense.

Thanks!




-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/



Bug#1025663: qmake6: how should users query for QT_INSTALL_PLUGINS?

2022-12-26 Thread Lisandro Damián Nicanor Pérez Meyer
Hi,

On Mon, 26 Dec 2022 at 20:36, Patrick Franz  wrote:
>
> Hi,
>
> I agree that solution a) sounds like the better option, especially since
> we've gone this route with Qt 5.
>
> However, I will revisit this issue once we have transitioned 6.4 into
> unstable.

It's up to you, but the patch is straightforward and will not
introduce any problems with the transition.


-- 
Lisandro Damián Nicanor Pérez Meyer
https://perezmeyer.com.ar/