Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
Hi, let me try to summarize where we stand and what options and open questions we have. I see the following options to package the bdic-Files (seems not all of them were already mentioned before): a) Bundle the bdic files in the existing hunspell- files. - Pro: no new packages needed - Con: Duplicate size of existing ~80 packages b) Create new packages hunspell-bdic-. - Pro: User can install what is needed - Con: ~80 new packages necessary c) Add a mechanism to dictionaries-common, which extends update-dictcommon-hunspell to build the bdic file in hunspell-.postinst. - Pro: No changes in hunspell- - Pro: No redundancy in Archive - Con: Wastes space on users disk, unless QtWebEngine is used - Con: May slow down hunspell- installation - Con: Pulls in qtwebengine5-dev-tools for all hunspell- packages d) Add a new package (hunspell-bdic-generator or the like), that builds bdic files for all hunspell- packages if it is installed. This requires some dpkg/apt-hook to trigger building bdic if a new hunspell- package is installed or upgraded. All packages using bdic files have to depend on hunspell-bdic-generator. - Pro: No changes in hunspell- - Pro: No redundancy in Archive - Pro: Only used/installed when needed - Con: Complex hook mechanism I'm not sure what option I prefer myself, they all have disadvantages, but I personally prefer b) over a), while c) and d) could reduce the effort for hunspell- maintainers (in trade-off to the efforts in dictionaries-common). Except this I see the following open points: - Is bdic really arch:all or do we have some endiane issue? For option c) and d) this is irrelevant. - Where should the bdic files be placed? 1) /usr/share/hunspell-bdic 2) /usr/share/qtwebengine-dict 3) /usr/share/bdic 4) /usr/share/hunspell 5) something else (The order mentions my personal preference) - Is there some commandline client for auto-testing the bdic files? - How to reuse the bdic files with chromium? - 3 bugs in qwebengine_convert_dict reported by Soren Stoutner - Do we target this this to bookworm or trixie? Greetings Roland
Processing of plasma-workspace_5.26.0-2_source.changes
plasma-workspace_5.26.0-2_source.changes uploaded successfully to localhost along with the files: plasma-workspace_5.26.0-2.dsc plasma-workspace_5.26.0-2.debian.tar.xz plasma-workspace_5.26.0-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
plasma-workspace_5.26.0-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Oct 2022 15:01:15 +0200 Source: plasma-workspace Architecture: source Version: 4:5.26.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: plasma-workspace (4:5.26.0-2) unstable; urgency=medium . [ Aurélien COUDERC ] * Really fix the login screen issue. Checksums-Sha1: e2f1770b5c924e7b1fdd9556ac657408fc5d8d42 5891 plasma-workspace_5.26.0-2.dsc 304a9698134d25d8c3514e18ec8cff23f554 52136 plasma-workspace_5.26.0-2.debian.tar.xz c7ff125e94a45c3cd548e1948a23b0da077ca42e 34035 plasma-workspace_5.26.0-2_amd64.buildinfo Checksums-Sha256: cbf0a10758ad1125a01ff3776b1f1cf8225ae39260b831c1d8757031dff8e4c2 5891 plasma-workspace_5.26.0-2.dsc 9df90d04b3a38f50d27326d45749ff1ee7a056efea7b134ad8d4bb830bdbb5c3 52136 plasma-workspace_5.26.0-2.debian.tar.xz 70c73d112a040642c71c634b6042203866122fcc7eebdfe49fa1df3621d2f44a 34035 plasma-workspace_5.26.0-2_amd64.buildinfo Files: 340369b9b1d96e49d04940052f4fc1ec 5891 kde optional plasma-workspace_5.26.0-2.dsc bcf496d44fda31d1dc56e14c49911978 52136 kde optional plasma-workspace_5.26.0-2.debian.tar.xz 412d87cb8eb3215c7c6dd101a4ca7f1f 34035 kde optional plasma-workspace_5.26.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmNJbhkTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJLvWD/0TehT5g1fA9wOTDkRBCexbaHu51+5c lrunsCD0LH8DpyYBBDfMixuNhGZUjNamD6FVpF5DdIhherBA9wNhY99rVlQLVQxF Zoa0qIwwJ0opLEEo2iRNCRAsGfVj+gPtMjA8I+iTpIr39PPCkCVGcwrBr/uFDeCr ZQNCnlhbpw1GBYw41iuMXjR7baVbecwuhV4abzdjeyRYw4Y1DC8jfuXTs28oHPtR Uh/yNUh5TD1xxNp01k/UtE3raoWb80puc2MVMBGngyYIAKxiuZAErSHCH28KwUuS XmU0r/NmuLU1eqI0DhOcFmCAn9DGrFogZNALac15RQQwuEU5agkGPhfQvee5ykIB WNULPjhER3b9mH7mBfYHR1PJ8h1HIV8qOmGvXIDmkNTrkZxFMxjd65N4OgZOncKu ZjN1ECSxh+ciPW68HCEafbQAm9XOmZbaPYgH34qEF6EVlDmCVFxsflFG+WoFWVPj xzcaGGwucBayzVagQvakzJKqk0FxRiynXUNVU6gvGTJkbS7yL8xO89ybRhCWuEXZ lJnMgO9kxBtnTIdd+ld7jiyGORn/6rIjWEvYHn3StRRjeZ5P9sKrbWqgW4Yeij87 C1+w3DFqFV337cxw+k2Xj3Qdjrrbk+CKwgzF6UzkDvmaZxGcZ6pTOqZGHfvo9o9C UXq/QC6ig+xfVQ== =lpWO -END PGP SIGNATURE- Thank you for your contribution to Debian.
Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
On Friday, October 14, 2022 3:54:53 AM MST Roland Rosenfeld wrote: > - Where should the bdic files be placed? > 1) /usr/share/hunspell-bdic I like this option because it would eliminate the need to wait to find out if Chromium can use the files before deciding where to put them. On a separate note, I am in the process of filing upstream bug reports with Google as recommended by Qt. Once I get those filed I will place links to them in the Qt bug reports. I don’t think we need to wait for these bugs to be fixed before adding packages to Debian as they only affect three languages, but if the .bdic files are going to be generated automatically we need some mechanism to specify that they shouldn’t attempt to be generated for these three languages until the bugs are fixed. Alternatively, we could patch the files so that the errors are avoided. In the case Aragonese with tabs in the .aff, we could change them all to be spaces. I can find no Hunspell file spec that says either tabs or spaces are required, and I am assuming that Hunspell itself doesn’t have problems with tabs because there are no nasty bugs filed against the current Aragonese Debian package, but it should also work fine with spaces as that is what all the other Hunspell packages appear to use. The errors in the other two files could be fixed by removing one line from ar.aff and 31 lines from gl_ES.dic. That makes them slightly less correct, but most people using the .bidc would probably not notice. If we go this route we need to make sure we are only editing temporary files used to generate the .bdic as those using the standard Hunspell system should not end up with an inferior experience just to accommodate a custom binary format. -- Soren Stoutner so...@stoutner.com signature.asc Description: This is a digitally signed message part.
Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
This is Google’s page describing the .bdic format: https://sites.google.com/a/chromium.org/dev/developers/how-tos/editing-the-spell-checking-dictionaries[1] It doesn’t directly address the topic of endianess, but it does say the following: "The .bdic files are always UTF-8 internally, and the convert_dict tool converts things appropriately when it runs.” I must admit that the topic of endianess goes a bit beyond my expertise, but my understanding is that it is primarily an issue for executable files. As the .bdic is only a data file, and as the data encoded inside it is in UTF-8 as described above, would that mean that it is safe to assume that these are arch:all? -- Soren Stoutner so...@stoutner.com [1] https://sites.google.com/a/chromium.org/dev/developers/how-tos/editing-the-spell-checking-dictionaries signature.asc Description: This is a digitally signed message part.
qt6-tools_6.4.0-1_amd64.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 13 Oct 2022 14:03:37 +0200 Source: qt6-tools Binary: assistant-qt6 assistant-qt6-dbgsym designer-qt6 designer-qt6-dbgsym libqt6designer6 libqt6designer6-dbgsym libqt6designercomponents6 libqt6designercomponents6-dbgsym libqt6help6 libqt6help6-dbgsym libqt6uitools6 libqt6uitools6-dbgsym linguist-qt6 linguist-qt6-dbgsym qdbus-qt6 qdbus-qt6-dbgsym qt6-documentation-tools qt6-documentation-tools-dbgsym qt6-l10n-tools qt6-l10n-tools-dbgsym qt6-tools-dev qt6-tools-dev-tools qt6-tools-dev-tools-dbgsym qt6-tools-private-dev Architecture: source amd64 Version: 6.4.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Description: assistant-qt6 - Qt 6 Assistant designer-qt6 - Qt 6 Designer libqt6designer6 - Qt 6 Designer library libqt6designercomponents6 - Qt 6 Designer Components library libqt6help6 - Qt 6 Help library libqt6uitools6 - Qt 6 UI tools library linguist-qt6 - Qt 6 Linguist qdbus-qt6 - Qt 6 D-Bus application qt6-documentation-tools - Qt 6 documentation tools qt6-l10n-tools - Qt 6 translation tools qt6-tools-dev - Qt 6 Tools - development files qt6-tools-dev-tools - Qt 6 development tools qt6-tools-private-dev - Qt 6 Tools - private development files Changes: qt6-tools (6.4.0-1) experimental; urgency=medium . [ Lisandro Damián Nicanor Pérez Meyer ] * Split qdbus out of qt6-tools-dev-tools, as it might be required by an applications as a helper binary. - Make qt6-tools-dev-tools depend upon qdbus-qt6. * Bump minimum CMake version in order to get pkg-config's .pc files. . [ Patrick Franz ] * Increase CMake verbosity level. * New upstream release (6.4.0). * Bump Qt B-Ds to 6.4.0. * Update ABI to 6.4.0. * Update B-Ds. * Update list of installed files. * Update symbols from buildlogs. * Update d/copyright. Checksums-Sha1: d814078cf19fec723513fb288d9f50c4b037a7e0 3183 qt6-tools_6.4.0-1.dsc a1717b501d59352695a6be9ad0e062e029b77c13 8738432 qt6-tools_6.4.0.orig.tar.xz 3488a02241d70cf979f26e71120d5522befdff9f 36688 qt6-tools_6.4.0-1.debian.tar.xz 5f8b9cda1074dbcb4e3027255e46389f8899fabd 10563864 assistant-qt6-dbgsym_6.4.0-1_amd64.deb 7080f525772897ed80bf66b84e3c71b78d7ffda2 492220 assistant-qt6_6.4.0-1_amd64.deb 6a9613052a417493e98c229cdf44068ab9053418 4895064 designer-qt6-dbgsym_6.4.0-1_amd64.deb f00fe7dc764b9c9c3ec2c2c9ddab36958ae1179b 168312 designer-qt6_6.4.0-1_amd64.deb fe2c4b11ba06678674e221a7d1ea4a3cb5f77dcd 28740248 libqt6designer6-dbgsym_6.4.0-1_amd64.deb a49ca3a4ea66f67233a461482f96d77fdde7580c 2858304 libqt6designer6_6.4.0-1_amd64.deb 638b226121f26832076405b56ecc46f4bcb268b8 32079808 libqt6designercomponents6-dbgsym_6.4.0-1_amd64.deb 01911de689088590cc8ae9832306e035296f7c09 834020 libqt6designercomponents6_6.4.0-1_amd64.deb e39c38b444fde49f8acd29a485144317c1ec98fc 4891452 libqt6help6-dbgsym_6.4.0-1_amd64.deb 547ee668b47ed4d5fa1bf06c10027ecc1df4abcb 179512 libqt6help6_6.4.0-1_amd64.deb 3b9a29b59168c38d14326b11be842349f7d4ae55 4269956 libqt6uitools6-dbgsym_6.4.0-1_amd64.deb e1d700b623a0a7080d404edc44820ffc808766d3 158592 libqt6uitools6_6.4.0-1_amd64.deb 4dfa6c171b9567b4152d336137f09adebdf8 7674760 linguist-qt6-dbgsym_6.4.0-1_amd64.deb f288a1c192579024a06c60c8268a1e36ee59f3ef 360536 linguist-qt6_6.4.0-1_amd64.deb 0808cdb03ad5244e3f29ddbcfb61a6466adcbb6b 449604 qdbus-qt6-dbgsym_6.4.0-1_amd64.deb dcbd1ce02715534717ad4d6a7348fcf885bc601c 29552 qdbus-qt6_6.4.0-1_amd64.deb d6c159090aa1d5972cd198964fc6461bf5eab1af 19254768 qt6-documentation-tools-dbgsym_6.4.0-1_amd64.deb 4832498d1eb0b57ef8678084846bc386d24490f3 659668 qt6-documentation-tools_6.4.0-1_amd64.deb 5ca7e470a28ee20b840c86607e2f8df6045dc246 16211416 qt6-l10n-tools-dbgsym_6.4.0-1_amd64.deb 879059c7e6d19d079294728d74a722e6b67915b9 414952 qt6-l10n-tools_6.4.0-1_amd64.deb 3374b0b1e87a2867b0eb0beafe91050e70937c2f 6034064 qt6-tools-dev-tools-dbgsym_6.4.0-1_amd64.deb d902c909edea666c044471e133c5bd28e0b48ccf 263016 qt6-tools-dev-tools_6.4.0-1_amd64.deb 9f999b6ee7a0df409d72201fc3eb75fba39d5223 67244 qt6-tools-dev_6.4.0-1_amd64.deb 89aa07974160c7a0bbaed0827a56e0f597d102d8 71712 qt6-tools-private-dev_6.4.0-1_amd64.deb 30f23c1d2ee2a25b3d06b250196091a75c078718 21400 qt6-tools_6.4.0-1_amd64.buildinfo Checksums-Sha256: 667b4bda4d05edacf0ea7b1dea4c31e4d8a7695fc8a95ccd8e80b06a27098124 3183 qt6-tools_6.4.0-1.dsc 97f3d5f88c458be7a8f7b7b08efc06c4ebad39ca51669476b18bf9e4c11afba2 8738432 qt6-tools_6.4.0.orig.tar.xz 24346f49e8481aba93dfdc0b4ee9e3358a44708d05b752e681452f0a59f77a2e 36688 qt6-tools_6.4.0-1.debian.tar.xz ad7b6b803c422d11e26602e09fa4a8deeb2ae737274a59555f3fd4dc8d897a13 10563864 assistant-qt6-dbgsym_6.4.0-1_amd64.deb 0871d29f8ecc9654f48ab375423ff96035abebdca90481a35bc5434e4644a1dd 492220 assistant-qt6_6.4.0-1_amd64.deb 9a2d5a80077cd76c2cc795e4fb379b9e2f03ced9d549042722fb22190f42f574 4895064 de
Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
> It doesn’t directly address the topic of endianess, but it does say > the following: > > "The .bdic files are always UTF-8 internally, and the convert_dict > tool converts things appropriately when it runs.” > > I must admit that the topic of endianess goes a bit beyond my > expertise, but my understanding is that it is primarily an issue for > executable files. As the .bdic is only a data file, and as the data > encoded inside it is in UTF-8 as described above, would that mean > that it is safe to assume that these are arch:all? I'm also not very familiar with this, so I tried to check out. I noted that s390x is big endian (in contrast to nearly all other supported architectures) and so I logged into a s390x porter box to build a bdic file and compare it with one build on other architectures. When I tried to install qtwebengine5-dev-tools I had to notice, that this package is not available for s390x. Checking https://tracker.debian.org/pkg/qtwebengine-opensource-src I noticed, that the package is limited to amd64, arm64, armhf, i386, mips64el and mipsel. Which means, that it is not available on armel, ppc64el and s390x (and all other non release relevant architectures). That's a big drawback, since we want to support the hunspell dictionaries on all architectures. I checked, whether the convert_dict tool (mentioned in the chromium page "Editing the spell checking dictionaries") may be available in Debian for other architectures, but I only found qt6-webengine-dev-tools, which supports an even shorter architecture list (only amd64, arm64, armhf and i386)... Greetings Roland
Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
FYI: Chromium includes an embedded copy of the hunspell library, which they've forked to ignore dic/aff files and instead use bdic files. The patch and google additions can be found here: https://sources.debian.org/src/chromium/106.0.5249.119-1/third_party/hunspell/google.patch/ https://sources.debian.org/src/chromium/106.0.5249.119-1/third_party/hunspell/google/ You'll note that bdict.h in the google directory mentions right up front that offsets in bdict format are little endian, and also describes endianness of integer fields themselves. That means putting bdic files into arch:all should be fine, as the tools should convert them automatically on big-endian platforms (and if they don't, it's a bug that chromium devs would accept a fix for). On Fri, Oct 14 2022 at 08:34:25 PM +0200, Roland Rosenfeld wrote: It doesn’t directly address the topic of endianess, but it does say the following: "The .bdic files are always UTF-8 internally, and the convert_dict tool converts things appropriately when it runs.” I must admit that the topic of endianess goes a bit beyond my expertise, but my understanding is that it is primarily an issue for executable files. As the .bdic is only a data file, and as the data encoded inside it is in UTF-8 as described above, would that mean that it is safe to assume that these are arch:all? I'm also not very familiar with this, so I tried to check out. I noted that s390x is big endian (in contrast to nearly all other supported architectures) and so I logged into a s390x porter box to build a bdic file and compare it with one build on other architectures. When I tried to install qtwebengine5-dev-tools I had to notice, that this package is not available for s390x. Checking https://tracker.debian.org/pkg/qtwebengine-opensource-src I noticed, that the package is limited to amd64, arm64, armhf, i386, mips64el and mipsel. Which means, that it is not available on armel, ppc64el and s390x (and all other non release relevant architectures). That's a big drawback, since we want to support the hunspell dictionaries on all architectures. I checked, whether the convert_dict tool (mentioned in the chromium page "Editing the spell checking dictionaries") may be available in Debian for other architectures, but I only found qt6-webengine-dev-tools, which supports an even shorter architecture list (only amd64, arm64, armhf and i386)... Greetings Roland
Processed: Reassigning
Processing commands for cont...@bugs.debian.org: > reassign 1012871 src:qt6-multimedia Bug #1012871 [src:libcamera] libcamera: Breaks Qt camera support when installed Bug reassigned from package 'src:libcamera' to 'src:qt6-multimedia'. No longer marked as found in versions libcamera/0~git20200629+e7aa92a-8. Ignoring request to alter fixed versions of bug #1012871 to the same values previously set > forwarded 1012871 https://bugreports.qt.io/browse/QTBUG-104226 Bug #1012871 [src:qt6-multimedia] libcamera: Breaks Qt camera support when installed Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-104226'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012871 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
On Fri, Oct 14 2022 at 12:54:53 PM +0200, Roland Rosenfeld wrote: Hi, let me try to summarize where we stand and what options and open questions we have. I see the following options to package the bdic-Files (seems not all of them were already mentioned before): a) Bundle the bdic files in the existing hunspell- files. - Pro: no new packages needed - Con: Duplicate size of existing ~80 packages b) Create new packages hunspell-bdic-. - Pro: User can install what is needed - Con: ~80 new packages necessary c) Add a mechanism to dictionaries-common, which extends update-dictcommon-hunspell to build the bdic file in hunspell-.postinst. - Pro: No changes in hunspell- - Pro: No redundancy in Archive - Con: Wastes space on users disk, unless QtWebEngine is used - Con: May slow down hunspell- installation - Con: Pulls in qtwebengine5-dev-tools for all hunspell- packages d) Add a new package (hunspell-bdic-generator or the like), that builds bdic files for all hunspell- packages if it is installed. This requires some dpkg/apt-hook to trigger building bdic if a new hunspell- package is installed or upgraded. All packages using bdic files have to depend on hunspell-bdic-generator. - Pro: No changes in hunspell- - Pro: No redundancy in Archive - Pro: Only used/installed when needed - Con: Complex hook mechanism I'm not sure what option I prefer myself, they all have disadvantages, but I personally prefer b) over a), while c) and d) could reduce the effort for hunspell- maintainers (in trade-off to the efforts in dictionaries-common). I don't have a strong opinion about a) vs b). Except this I see the following open points: - Is bdic really arch:all or do we have some endiane issue? For option c) and d) this is irrelevant. There shouldn't be endian issues, as I mentioned elsewhere. - Where should the bdic files be placed? 1) /usr/share/hunspell-bdic 2) /usr/share/qtwebengine-dict 3) /usr/share/bdic 4) /usr/share/hunspell In my opinion, chromium's (, or QT's, or whoever's) bdic support should be merged upstream into hunspell, and hunspell should be shipping bdic files in /usr/share/hunspell alongside the .aff and .dic files. I don't know how active hunspell upstream is, though, and how amenable they'd be to patches. I see at least one person created an hunspell-with-bdic-support fork a decade ago: https://github.com/sheremetyev/hunspell That would allow chromium and other hunspell users to link against a system hunspell when desired, dropping all the bdict versioning stuff and the custom paths. I'm pretty sure I could get a patch to link against system hunspell into chromium upstream, provided bdic support made it into upstream hunspell. I wouldn't want to see debian carrying bdic patches in its hunspell package, though; nor would I want to see the security team needing to deal with a hunspell fork package. 5) something else (The order mentions my personal preference) - Is there some commandline client for auto-testing the bdic files? - How to reuse the bdic files with chromium? - 3 bugs in qwebengine_convert_dict reported by Soren Stoutner I just took a peek at qtwebengine-opensource-src-5.15.10+dfsg, and I see that they're using the exact same hunspell fork from chromium. :( - Do we target this this to bookworm or trixie? Greetings Roland
Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
On Fri, Oct 14, 2022 at 02:58:17PM -0400, Andres Salomon wrote: > In my opinion, chromium's (, or QT's, or whoever's) bdic support should be > merged upstream into hunspell, and hunspell should be shipping bdic files in > /usr/share/hunspell alongside the .aff and .dic files. I don't know how > active hunspell upstream is, though, and how amenable they'd be to patches. > I see at least one person created an hunspell-with-bdic-support fork a > decade ago: https://github.com/sheremetyev/hunspell > > That would allow chromium and other hunspell users to link against a system > hunspell when desired, dropping all the bdict versioning stuff and the > custom paths. I'm pretty sure I could get a patch to link against system > hunspell into chromium upstream, provided bdic support made it into upstream > hunspell. > > I wouldn't want to see debian carrying bdic patches in its hunspell package, > though; nor would I want to see the security team needing to deal with a > hunspell fork package. I think you are the first to mention "integrating" bdic into hunspell itself, and to mention that effectively the parser is based on hunspell itself… From what I know, the hunspell project is basically in maintenance mode, with nobody actively doing anything to it. Pretty much all changes in the past years were done by drive-by contributors. This is to say, I can't deny that somebody proposing MRs upstream might actually see them merged. > > 5) something else > > (The order mentions my personal preference) > > - Is there some commandline client for auto-testing the bdic files? > > - How to reuse the bdic files with chromium? > > - 3 bugs in qwebengine_convert_dict reported by Soren Stoutner > > > I just took a peek at qtwebengine-opensource-src-5.15.10+dfsg, and I see > that they're using the exact same hunspell fork from chromium. :( Not surprising since afaik qtwebengine is basically a fork of chromium itself... -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processing of qt6-declarative_6.4.0+dfsg-3_source.changes
qt6-declarative_6.4.0+dfsg-3_source.changes uploaded successfully to localhost along with the files: qt6-declarative_6.4.0+dfsg-3.dsc qt6-declarative_6.4.0+dfsg-3.debian.tar.xz qt6-declarative_6.4.0+dfsg-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
qt6-declarative_6.4.0+dfsg-3_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Oct 2022 21:44:10 +0200 Source: qt6-declarative Architecture: source Version: 6.4.0+dfsg-3 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Changes: qt6-declarative (6.4.0+dfsg-3) experimental; urgency=medium . [ Patrick Franz ] * Update symbols from buildlogs. Checksums-Sha1: 112e97f18258ea50cf6e9140a63cd190d31b59ff 6616 qt6-declarative_6.4.0+dfsg-3.dsc 4a7e27f9b19b73fa0d4b890b927505247124cec4 135720 qt6-declarative_6.4.0+dfsg-3.debian.tar.xz e845ffd1d26764a237c2e79e5cfc40e5b774dd80 8985 qt6-declarative_6.4.0+dfsg-3_source.buildinfo Checksums-Sha256: 08f2652c25006f61bbd589bb81eea34ad1866ac1145e663a60458223facd6138 6616 qt6-declarative_6.4.0+dfsg-3.dsc 626d0080fe1e2d09bee9da5f55010e716743176cd97be7a6e7d700f6e3f673c9 135720 qt6-declarative_6.4.0+dfsg-3.debian.tar.xz 74ee1b1f2e11ea7b1c998db03e49042c322fd76e78342604977bd00fa3ea25c2 8985 qt6-declarative_6.4.0+dfsg-3_source.buildinfo Files: 9fe40e002626c878e217e57dde65dca9 6616 libs optional qt6-declarative_6.4.0+dfsg-3.dsc 94202bc9a16a4e101b492724987667a1 135720 libs optional qt6-declarative_6.4.0+dfsg-3.debian.tar.xz 52164b5f0a8857b46e051273e36cbc48 8985 libs optional qt6-declarative_6.4.0+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmNJvCQACgkQnp96YDB3 /laWvg/8Ct56NTLt0mdf0bCcmfi0zDVHQM8l10eqr12aRl8wUvP/7xCEMvS149qs rzOkQEvQ9ARXS1mbxA+DTk5u5ENHKNgn4GNyF5o4WfGL4Wr+s64qjchTkVeD9dFd Irz2PWW36ngOoSkDZNuL+VSoisu5IycqVuG6Vgj1V8fiQDtW9KUDzP/dXPyA4/xA iS13IwOIANGFhJBNZ49Q7yWfTCYSOt9iWTazuNwz7tENr1FbHX8wAFa6JKTRcE/4 vA+9BJJFq6ozNUsa4zpiJD6xGz/Uykq8HK40N0CCuk5WIemQsfhPkOy8I4roX9lr EsVOqpbvUgzn1NNyx6iHwSGXSiGkCBvuP4OWheCqmCnkuCTkU6y44FGCOwwfxCID lMhnOxN0oyRPMQeWAH43JyVF6wky1C2rdyZueICNrHQ4/2EhAWtLf7yFUSB+apFe y0tAC8591eO1qmvnRqCw5apJxUdwQiWcjOrYNjE+alX2khc7QTu3aY2nFCjngiAq f/dVzY4pwYNK0mD1uE1jIfbYbX2ZQ4MozMp2JxE1czk6svVf9Qhj/vnky8wmncWj IRRPrMs6iPvD5lW98HzguNDBZZ95Np+MZHpBVv2OejdyXbFDWMOtc32loLX6e7k5 zdVdqb742KjG6P5L37YWD6hiKsakkCKIfLoJqePstc0GLkU80lE= =QtB6 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Re: Bug#1020387: dictionaries-common: Consensus regarding the packaging of the Qt WebEngine hunspell binary dictionaries
On Friday, October 14, 2022 11:58:17 AM MST Andres Salomon wrote: > That would allow chromium and other hunspell users to link against a > system hunspell when desired, dropping all the bdict versioning stuff > and the custom paths. I'm pretty sure I could get a patch to link > against system hunspell into chromium upstream, provided bdic support > made it into upstream hunspell. I think that would be the way to go if both the upstreams would support it. -- Soren Stoutner so...@stoutner.com signature.asc Description: This is a digitally signed message part.
Processing of qt6-virtualkeyboard_6.4.0+dfsg-1_source.changes
qt6-virtualkeyboard_6.4.0+dfsg-1_source.changes uploaded successfully to localhost along with the files: qt6-virtualkeyboard_6.4.0+dfsg-1.dsc qt6-virtualkeyboard_6.4.0+dfsg.orig.tar.xz qt6-virtualkeyboard_6.4.0+dfsg-1.debian.tar.xz qt6-virtualkeyboard_6.4.0+dfsg-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
qt6-virtualkeyboard_6.4.0+dfsg-1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 14 Oct 2022 23:18:03 +0200 Source: qt6-virtualkeyboard Architecture: source Version: 6.4.0+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Changes: qt6-virtualkeyboard (6.4.0+dfsg-1) experimental; urgency=medium . [ Lisandro Damián Nicanor Pérez Meyer ] * Bump minimum CMake version in order to get pkg-config's .pc files. . [ Patrick Franz ] * Increase CMake verbosity level. * New upstream release (6.4.0). * Bump Qt B-Ds to 6.4.0. * Adjust patches. * Update list of installed files. * Update symbols from buildlogs. Checksums-Sha1: 12f5e3499759fca16c671228b945f98145f797b5 2961 qt6-virtualkeyboard_6.4.0+dfsg-1.dsc b1cabc7d7911a82e19e930a23400a4f14579ee20 1448792 qt6-virtualkeyboard_6.4.0+dfsg.orig.tar.xz e95e019908a1ac896d8659ba2f842b0856d13d40 11728 qt6-virtualkeyboard_6.4.0+dfsg-1.debian.tar.xz 771c3de41f87cfbdeeb8e15cfede3cad3fde5a61 10996 qt6-virtualkeyboard_6.4.0+dfsg-1_source.buildinfo Checksums-Sha256: ca017275844859cd5ed86ff95754f144b87bb38290bda4973294b2fed3cca036 2961 qt6-virtualkeyboard_6.4.0+dfsg-1.dsc 432f5a7d1b4c5bae1aab1c7f451caa3ec6b68b96d93c211c9a8e82000e17a591 1448792 qt6-virtualkeyboard_6.4.0+dfsg.orig.tar.xz 36d462efff686fb81fb0de82ea9be2311764e08e1cc42da27c0d6bf25106ee5c 11728 qt6-virtualkeyboard_6.4.0+dfsg-1.debian.tar.xz f0e41b355ae689e5e0aa3dda8c95a766e9ea86fb34cc962da000ff92785e4fde 10996 qt6-virtualkeyboard_6.4.0+dfsg-1_source.buildinfo Files: 343d6c8e96869b346743f459b66972e9 2961 libs optional qt6-virtualkeyboard_6.4.0+dfsg-1.dsc 348bfc604c072c3bc91c5888ff2c26b6 1448792 libs optional qt6-virtualkeyboard_6.4.0+dfsg.orig.tar.xz 0c78cb806fcbe0cec7131cfb97290d4f 11728 libs optional qt6-virtualkeyboard_6.4.0+dfsg-1.debian.tar.xz c4aff8d896fb68034e939882280b79ec 10996 libs optional qt6-virtualkeyboard_6.4.0+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmNJ0iMACgkQnp96YDB3 /lbUhRAAucPQg72aNLyE/WepT4CT0mtZR1u/8613dWGW1fyStVVfX2nuFS/O8wBQ 0qYm0JzDmdzKiTO9X+B392pfHYreW2VgFUfZwVXxzB+iyiu/F7k8X5QF/VtaUFx2 Gc9UbXdvVbGWjkqz1LFmb8Q24S5hDXMJCaeHGVx0pn52YR6dOrvn97OZpv+j5wtm Br0DJK3NphrtOZXQil/U+aG6AICo2rY1BTUqOBdREVhxKzNIksLuZAF73bhuoQCP OIjSzpDJU6Q816QB+HENNaNRvn8c/wtIG6sXIVM5PoAFObvTknmCsAVz8GbHqTgG lM9hy1WkJKAfDiNucHFVzq1FvYbmRdYfCAuloUDY0cOjQglB//8etcybRHgro1E6 OVJ8EPrpbtFa0iCeRseAHydb9rlAwImuNJXdJ96BSvzIycH6706g3axAWVccPkrJ YG+ocedwV1iE3KzRGjF/DnVrMNUw+TonDT6FjM3Q0ILR+huIjZVpBx+DSKTv59x5 BD7U1Fxc+TCaUq6THarKMz+slWB9O+qw3LfVQITzt9Qh3lS7FO5GAhUHzvMOMB6V T+cUjyxA6Zjjow0i8YvrCuxdCGtt+4n+ZOrtQthcXgpaLP5P1XCxgEwOA2NKIR0I uuxj8HUUnRbHUNl9I/Cmd0jbW0aV5WlQdMjF6cpcjeYBcGflqow= =xLrJ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#1021404: marked as done (qt6-base: FTBFS on hppa - Unknown Q_PROCESSOR_xxx macro)
Your message dated Sat, 15 Oct 2022 06:06:24 + with message-id and subject line Bug#1021404: fixed in qt6-base 6.4.0+dfsg-4 has caused the Debian Bug report #1021404, regarding qt6-base: FTBFS on hppa - Unknown Q_PROCESSOR_xxx macro 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.) -- 1021404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qt6-base Version: 6.3.1+dfsg-10 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The build fails here: [357/1566] /usr/bin/c++ -DBACKTRACE_HEADER=\"execinfo.h\" -DCore_EXPORTS -DELF_INTERPRETER=\"/lib/ld.so.1\" -DQT_ASCII_CAST_WARNINGS -DQT_BUILDING_QT -DQT_BUILD_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DEPRECATED_WARNINGS_SINCE=0x06 -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_MOC_COMPAT -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_USING_NAMESPACE -DQT_TYPESAFE_FLAGS -DQT_USE_QSTRINGBUILDER -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I/<>/obj-hppa-linux-gnu/src/corelib/Core_autogen/include -I/<>/obj-hppa-linux-gnu/include -I/<>/obj-hppa-linux-gnu/include/QtCore -I/<>/src/corelib -I/<>/obj-hppa-linux-gnu/src/corelib -I/<>/obj-hppa-linux-gnu/src/corelib/global -I/<>/obj-hppa-linux-gnu/src/corelib/kernel -I/<>/src/corelib/../3rdparty/tinycbor/src -I/<>/obj-hppa-linux-gnu/include/QtCore/6.3.1 -I/<>/obj-hppa-linux-gnu/include/QtCore/6.3.1/QtCore -I/<>/src/corelib/../3rdparty/forkfd -I/<>/mkspecs/linux-g++ -isystem /usr/include/double-conversion -isystem /usr/include/glib-2.0 -isystem /usr/lib/hppa-linux-gnu/glib-2.0/include -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -Wsuggest-override -std=c++17 -Winvalid-pch -include /<>/obj-hppa-linux-gnu/src/corelib/CMakeFiles/Core.dir/cmake_pch.hxx -MD -MT src/corelib/CMakeFiles/Core.dir/text/qregularexpression.cpp.o -MF src/corelib/CMakeFiles/Core.dir/text/qregularexpression.cpp.o.d -o src/corelib/CMakeFiles/Core.dir/text/qregularexpression.cpp.o -c /<>/src/corelib/text/qregularexpression.cpp [358/1566] /usr/bin/c++ -DBACKTRACE_HEADER=\"execinfo.h\" -DCore_EXPORTS -DELF_INTERPRETER=\"/lib/ld.so.1\" -DQT_ASCII_CAST_WARNINGS -DQT_BUILDING_QT -DQT_BUILD_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DEPRECATED_WARNINGS_SINCE=0x06 -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_MOC_COMPAT -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_USING_NAMESPACE -DQT_TYPESAFE_FLAGS -DQT_USE_QSTRINGBUILDER -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I/<>/obj-hppa-linux-gnu/src/corelib/Core_autogen/include -I/<>/obj-hppa-linux-gnu/include -I/<>/obj-hppa-linux-gnu/include/QtCore -I/<>/src/corelib -I/<>/obj-hppa-linux-gnu/src/corelib -I/<>/obj-hppa-linux-gnu/src/corelib/global -I/<>/obj-hppa-linux-gnu/src/corelib/kernel -I/<>/src/corelib/../3rdparty/tinycbor/src -I/<>/obj-hppa-linux-gnu/include/QtCore/6.3.1 -I/<>/obj-hppa-linux-gnu/include/QtCore/6.3.1/QtCore -I/<>/src/corelib/../3rdparty/forkfd -I/<>/mkspecs/linux-g++ -isystem /usr/include/double-conversion -isystem /usr/include/glib-2.0 -isystem /usr/lib/hppa-linux-gnu/glib-2.0/include -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra -Wsuggest-override -std=c++17 -Winvalid-pch -include /<>/obj-hppa-linux-gnu/src/corelib/CMakeFiles/Core.dir/cmake_pch.hxx -MD -MT src/corelib/CMakeFiles/Core.dir/io/qfilesystemwatcher.cpp.o -MF src/corelib/CMakeFiles/Core.dir/io/qfilesystemwatcher.cpp.o.d -o src/corelib/CMakeFiles/Core.dir/io/qfilesystemwatcher.cpp.o -c /<>/src/corelib/io/qfilesystemwatcher.cpp [359/1566] /usr/bin/c++ -DBACKTRACE_HEADER=\"execinfo.h\" -DCore_EXPORTS -DELF_INTERPRETER=\"/lib/ld.so.1\" -DQT_ASCII_CAST_WARNINGS -DQT_BUILDING_QT -DQT_BUILD_CORE_LIB -DQT_DEPRECATED_WARNINGS -DQT_DEPRECATED_WARNINGS_SINCE=0x06 -DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_MOC_COMPAT -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_JAVA_STYLE_ITERATORS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_USING_NAMESPACE -DQT_TYPESAFE_FLAGS -DQT_USE_QSTRINGBUILDER -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I/<>/obj-hppa-linux-gnu/src/corelib/Core_autogen/include -I/<>/obj-hppa-l
Processing of qt6-base_6.4.0+dfsg-4_source.changes
qt6-base_6.4.0+dfsg-4_source.changes uploaded successfully to localhost along with the files: qt6-base_6.4.0+dfsg-4.dsc qt6-base_6.4.0+dfsg-4.debian.tar.xz qt6-base_6.4.0+dfsg-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
qt6-base_6.4.0+dfsg-4_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 15 Oct 2022 07:43:54 +0200 Source: qt6-base Architecture: source Version: 6.4.0+dfsg-4 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 1021404 Changes: qt6-base (6.4.0+dfsg-4) experimental; urgency=medium . * Team upload. * Backport upstream commit e81cba0cd9c2e5f5e3c670741605264b21c2 to support HPPA; patch upstream_Add-HPPA-detection.patch. (Closes: #1021404) * Backport upstream commit ac17a394a5701174c705050640e26c9cb95d289b to support M68k; patch upstream_Add-M68k-detection.patch. Checksums-Sha1: 0b0e81c45dab82881f7ab761824aabc33ee6b677 4801 qt6-base_6.4.0+dfsg-4.dsc 74c290a9cc1411733ee6d09154000f19338e6b6a 175480 qt6-base_6.4.0+dfsg-4.debian.tar.xz ecd5c363546d36891ad721ee28c861b4c75cafa3 15577 qt6-base_6.4.0+dfsg-4_source.buildinfo Checksums-Sha256: 3326a9b3a77cf850dc6c5ed0e29229b5680d82b9f93024f5e8de5df15d26ad90 4801 qt6-base_6.4.0+dfsg-4.dsc 4ffa26d0cfb08d5b8e67950896d762af9646c23dfc6aeaa9527a53cf324b787f 175480 qt6-base_6.4.0+dfsg-4.debian.tar.xz 3859dc4be3cbcb2566df8bfdcdaab682e169c27e4b2af273153d5ed4db590035 15577 qt6-base_6.4.0+dfsg-4_source.buildinfo Files: c4b835e5679c795444615ceebc1379f3 4801 libs optional qt6-base_6.4.0+dfsg-4.dsc 8907d2fbce45a0bee66408d4c7c154f7 175480 libs optional qt6-base_6.4.0+dfsg-4.debian.tar.xz 35fe3d4ff17669a93a99c078ea5294b7 15577 libs optional qt6-base_6.4.0+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmNKSOwACgkQLRkciEOx P03F5Q//U6lUORV+YnV6KfqNJ+08A1CkzMZ22UIgm5Up5+7ghvd6g2/TePCOK53G 42N12OUhPrUcVHlv5ow56IKYovdf8xRgw3fy6GDX35AuzPO8AvHYY8YYSmfSLYwW cJC7Rw+uLe2GG51F7N7HCoaLxnh27R8/yNiXlHPBiu2FlYEy6AntoK2mUPBwc/oi SfDTCodzx2wX3tFq7sUrDCIEQYkYkoZV9EuxyTEl9RwAgn5NYEG2RdZookZ1PrS6 gxC/+g7Os/MQMvNf6zJCCnAZ10QJCQJZwQlNaZdQDJBq55b8DhcZyvuSeg4bhgyM UpGifv4RAh1sHCqIWdPQ4OFzts8mIDo70aMZkg20Z4Gfu2IiAfdAdES+8Fd2fY2Z 8yQtREKAl5CBSgYGUFqHiXbca44RWga0aUbEKoiByfPRBUciJvoE4ymTtXjipNju ZYaokcs4kLjEMXHtms6TnKMqZ7i07a06dtnv6Hm8pmAzZ6jyGFRZQRgAnRH1+K6F gl2N6vTC1/6cKdQi/E9XR/+LOfyLO5b4JA+yJgs3E8zWikfrp7hKCwjIkU0jBlYs mlooIWklJyEa8+/4uZUOzIeh94UU+W799KsYG/QSvncamnYa1riyn2tDNNeKw+5w 8wtbNr/XMNvk1NXoiJghupiSeGTMRxSbpiKAiXgw1DOht9f7NuI= =9dc2 -END PGP SIGNATURE- Thank you for your contribution to Debian.
