GNU gettext - Bugs: bug #64527, Vague error message about ITS files
You are not allowed to post comments on this tracker with your current authentication level.
bug #64527: Vague error message about ITS files
| Submitter: | Phillip Susi <psusi> | ||
| Submitted: | Mon 07 Aug 2023 07:18:42 PM UTC | ||
| Category: | XML | Severity: | 3 - Normal |
| Item Group: | None | Status: | Answer Provided |
| Privacy: | Public | Assigned to: | haible |
| Open/Closed: | Closed | ||
Jump to the original submission
|
Thu 10 Aug 2023 07:14:42 PM UTC, comment #7: |
Phillip Susi <psusi> |
|
Thu 10 Aug 2023 02:57:06 PM UTC, comment #6:
|
Bruno Haible <haible> |
Thu 10 Aug 2023 02:41:49 PM UTC, comment #5:
|
Phillip Susi <psusi> |
|
Tue 08 Aug 2023 05:21:10 PM UTC, comment #4:
|
Bruno Haible <haible> |
|
Tue 08 Aug 2023 04:11:43 PM UTC, comment #3: Ok, it sounds like this file is for gparted to configure policykit to run it as root, and policykit used to ship the files policy.its and policy.log in /usr/share/gettext/its to assist with translation of policykit config files such as this one in gparted. For some reason, these files are no longer packaged in debian 12. This may be a packaging error in some big policykit transition that is taking place.
|
Phillip Susi <psusi> |
|
Mon 07 Aug 2023 09:16:26 PM UTC, comment #2: Some (not in depth) documentation is at https://www.gnu.org/software/gettext/manual/html_node/Preparing-ITS-Rules.html |
Bruno Haible <haible> |
|
Mon 07 Aug 2023 09:14:37 PM UTC, comment #1: The error "cannot locate ITS rules for org.gnome.gparted.policy.in" means that the file org.gnome.gparted.policy.in is an XML file, but an ITS file (which describes which parts of this XML file should be localized) was not found. Such a file is being searched for, taking into account
|
Bruno Haible <haible> |
|
Mon 07 Aug 2023 07:18:42 PM UTC, original submission:
I'm trying to compile gparted 1.5 and get the error:
|
Phillip Susi <psusi> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
| Date | Changed by | Updated Field | Previous Value | => | Replaced by |
|---|---|---|---|---|---|
| 2023-08-08 | haible | Status | Need Info | Answer Provided | |
| Open/Closed | Open | Closed | |||
| 2023-08-07 | haible | Category | End-user / runtime | XML | |
| Status | None | Need Info | |||
| Assigned to | None | haible |
Powered by Savane 3.12.
Corresponding source code

Could --verbose print the name of the file when it is found? At least that way I could have built it on an older system that worked, found out the name of the file, then searched for that file in the new release.