[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#955236: marked as done (ibus-libthai: Migrate from /usr/lib/ibus to /usr/libexec)

Your message dated Thu, 23 Apr 2020 08:21:30 +0000
with message-id <E1jRX6w-000IrI-0c@fasolo.debian.org>
and subject line Bug#955236: fixed in ibus-libthai 0.1.4-6
has caused the Debian Bug report #955236,
regarding ibus-libthai: Migrate from /usr/lib/ibus to /usr/libexec
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 owner@bugs.debian.org
immediately.)


-- 
955236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955236
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ibus-libthai
Version: 0.1.4-5
Severity: wishlist


Hello,

ibus-libthai uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-libthai has setup in /usr/lib/ibus but it was specified in the <setup> in
the XML so you don't have to change other things.


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit <setup> in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have <setup> in /usr/share/ibus/<NAME>.xml,
it is encouraged to patch your package to have <setup> in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without <setup> or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,

--- End Message ---
--- Begin Message --- 
Source: ibus-libthai
Source-Version: 0.1.4-6
Done: Theppitak Karoonboonyanan <thep@debian.org>

We believe that the bug you reported is fixed in the latest version of
ibus-libthai, 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 955236@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Theppitak Karoonboonyanan <thep@debian.org> (supplier of updated ibus-libthai 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 23 Apr 2020 15:01:30 +0700
Source: ibus-libthai
Architecture: source
Version: 0.1.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Theppitak Karoonboonyanan <thep@debian.org>
Closes: 955236
Changes:
 ibus-libthai (0.1.4-6) unstable; urgency=medium
 .
   * d/watch: Update to version 4
   * Migrate setup program to /usr/libexec
     ibus 1.5.22-2 starts running IME setup programs at /usr/libexec
     instead of /usr/lib/ibus. As a result, custom --libexec-dir
     is no longer needed. (Closes: #955236)
   * Add upstream metadata
   * d/gbp.conf: Remove the 'buildpackage' section.
     This should be for per-user options.
   * d/copyright: Update years on packaging
   * Declare compliance with Debian Policy 4.5.0 (no changes)
Checksums-Sha1:
 d26b4f3929d732bc8858fade524d8658f59d803c 2100 ibus-libthai_0.1.4-6.dsc
 6d11000ae74702479308f40ad658f4973045b02f 3024 ibus-libthai_0.1.4-6.debian.tar.xz
 75a73e5a026ac0de7182927d61321ef59ab122e1 13973 ibus-libthai_0.1.4-6_amd64.buildinfo
Checksums-Sha256:
 ad50ac476dbf5c1e7b341fe5b1732137270b2173baf22c9820efd2fa5dba65da 2100 ibus-libthai_0.1.4-6.dsc
 684b6fcc5e3819aef3cdcec81ab00d49fe647baf169f8753b9ba4174e8289d5d 3024 ibus-libthai_0.1.4-6.debian.tar.xz
 35c37c597252ff8a0d2ef3dbd0d6ef578c4eb9bb2143645e9febc0aa7aa7c75c 13973 ibus-libthai_0.1.4-6_amd64.buildinfo
Files:
 5f1a1e9a4700d1b75644380556a66373 2100 utils optional ibus-libthai_0.1.4-6.dsc
 ce30495f43f314b65e09aa2430d4aeef 3024 utils optional ibus-libthai_0.1.4-6.debian.tar.xz
 84aca7942b5d2a82d5f9ee78d1e211ef 13973 utils optional ibus-libthai_0.1.4-6_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEMsxJDlpwsj3Wqlqyouuu0bb5AkEFAl6hTPkACgkQouuu0bb5
AkGJHhAAoyj0h/RqBlEkUkn76665pVbnNr1L00k3Dr7I72ts7Z4W+RhTOetuzexh
HFKVr82vCLZKwKiXD51RZAPYBWYBdflWsLPeOp/d1Oe2rJASUBObt+mt93IRq8WI
9R+A9sLZ2a82oIsLOa+rze7FCOlPXgoiBzeej/6rWLezoSPm5jAApMhA29Ew10mr
zcMD7MsV4nZbRxPtkf+v1bZqEBBKmuFH5XQBRRsU8YEJqskRzU5PM97oCVNv1okH
S5U08/yARQxOLt5ggkHdAcxI96gg79bTUp8bmFQd6BIaERCixjrEbU+3PrR4S2I9
xG60mgoS+lFpfQME49LGHfB3Iu1Yb1r+xypi86ADCKVcTYp55nIuyM6RB8OH2ImE
MsMdh9A3byr7cMUdAr1Gdw7q559fdZ2sHfm4YldnWpv8eK1N8qFgmmp35UnNxCn2
S1ATYQH5lk5x/7Eh6hiFjbnPumQij24B1xB5W8PnI5DDa8CZ0Jqid2wK8Mu4iMhA
LpshYfUvo2sRJXe9Q1dDKXInYF4snjSKRAGTPDvI6+qB4KQ7xltXI60GIZwyOU7r
dx9jicgdv5b234cjtyIhM/o+la0sry7XofriHfgMEJ6Br/7vtdERHVREdnW0WgiN
ScDy9EZWFkLLXSwkN7OUMZpxrKlgkTZzEbhKtSY9IjJXjOu8kD4=
=7yMC
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: