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
Ch
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)
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 pro
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
Change
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
Greetin
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 hunsp
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_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.d
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
> act
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 i
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+
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://sour
> 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 u
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
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 c
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
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:
pl
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)
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
19 matches
Mail list logo
