> After some testing, I determined that the bug is not present in
> 5.15.5+dfsg-3 but is present in 5.15.6+dfsg-1.
Control: tags -1 patch fixed-upstream
Control: found -1 5.15.6+dfsg-1
Control: notfound -1 5.15.5+dfsg-3
Okay, I have finally found the bug. It was introduced in the following commit
> After some testing, I determined that the bug is not present in
> 5.15.5+dfsg-3 but is present in 5.15.6+dfsg-1.
Control: tags -1 patch fixed-upstream
Control: found -1 5.15.6+dfsg-1
Control: notfound -1 5.15.5+dfsg-3
Okay, I have finally found the bug. It was introduced in the following commit
While we wait for answers as to whether these dictionaries can be used by the
Chromium package and how they might possibly be integrated with upstream
Hunspell, I would recommend that we move forward with packaging them in /usr/
share/hunspell-bdic. This location provides flexibility for whateve
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 11 Oct 2022 00:39:13 +0200
Source: kpipewire
Binary: libkpipewire-dev libkpipewire5 libkpipewire5-dbgsym libkpipewirerecord5
libkpipewirerecord5-dbgsym qml-module-org-kde-pipewire
qml-module-org-kde-pipewire-dbg
binary:itinerary is NEW.
binary:itinerary is NEW.
source:itinerary is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Pack
itinerary_22.08.2-1_amd64.changes uploaded successfully to localhost
along with the files:
itinerary_22.08.2-1.dsc
itinerary_22.08.2.orig.tar.xz
itinerary_22.08.2.orig.tar.xz.asc
itinerary_22.08.2-1.debian.tar.xz
itinerary-dbgsym_22.08.2-1_amd64.deb
itinerary_22.08.2-1_amd64.buildinfo
6 matches
Mail list logo
