Bug 1634377

Summary: wrong Russian translation
Product: [Fedora] Fedora Reporter: z117
Component: hddtempAssignee: Dominik 'Rathann' Mierzejewski <dominik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: dominik, jaromir.capik, vascom2
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: FutureFeature
Fixed In Version: hddtemp-0.3-0.46.beta15.fc32 hddtemp-0.3-0.46.beta15.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-24 01:13:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the proposed fix none

Description z117 2018-09-30 11:15:42 UTC
Description of problem:

hddtemp message "drive is sleeping" has wrong Russian translation. In fact, looking in ru/LC_MESSAGES/hddtemp.mo, the message translation is just copied from the neighbor message "no sensor". So when the drive is sleeping, and LANG is ru_RU, hddtemp misinforms a user saying "no sensor".

The correct translation should be something like "диск в состоянии сна".

Comment 1 Ben Cotton 2019-05-02 20:48:07 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 z117 2019-05-05 07:59:49 UTC
Created attachment 1563785 [details]
the proposed fix

Comment 3 z117 2019-05-05 08:00:27 UTC
Come on, guys. It's just to change a single line. Here is the patch.

Comment 4 Vasiliy Glazov 2019-10-22 07:55:27 UTC
Are you asked upstream?

Comment 5 Dominik 'Rathann' Mierzejewski 2019-12-03 11:51:34 UTC
Upstream is dead. There are a couple of forks, but most are dead, too. The one with most life left in it is https://github.com/kdave/hddtemp . I contacted the author some time ago and he was open to cross-distro collaboration and having his fork serve as the upstream. Feel free to open a PR there. I plan to rebase the Fedora package to that fork eventually.

Comment 6 Vasiliy Glazov 2019-12-04 06:38:22 UTC
Domimik are you plan to maintain epel8 builds?
Because I did not seen your reaction to this https://bugzilla.redhat.com/show_bug.cgi?id=1764034

Comment 7 Dominik 'Rathann' Mierzejewski 2019-12-04 10:09:56 UTC
No, I don't have time for EPEL8, sorry.

Comment 8 Vasiliy Glazov 2019-12-04 10:22:59 UTC
So please add me as comaintainer for this branch.
My FAS: vascom

Comment 9 Dominik 'Rathann' Mierzejewski 2019-12-04 11:06:10 UTC
Added to the project. I don't see an option to give you commit ACL for a specific branch only.

Comment 10 Vasiliy Glazov 2019-12-04 11:18:24 UTC
Thanks.
There is no ACL for a specific branch.

Comment 11 Ben Cotton 2020-04-30 20:39:36 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Dominik 'Rathann' Mierzejewski 2020-04-30 20:45:45 UTC
Bumping to rawhide, I still intend to fix this unless another co-maintainer beats me to it.

Comment 13 Ben Cotton 2020-08-11 15:29:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 14 Fedora Update System 2020-08-22 23:09:31 UTC
FEDORA-2020-cad2321c3e has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-cad2321c3e

Comment 15 Fedora Update System 2020-08-22 23:09:32 UTC
FEDORA-2020-cae1cf62f0 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-cae1cf62f0

Comment 16 Fedora Update System 2020-08-23 01:09:56 UTC
FEDORA-2020-cae1cf62f0 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-cae1cf62f0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cae1cf62f0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 17 Fedora Update System 2020-08-23 02:09:15 UTC
FEDORA-2020-cad2321c3e has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-cad2321c3e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cad2321c3e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 18 Fedora Update System 2020-08-24 01:13:10 UTC
FEDORA-2020-cae1cf62f0 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 Fedora Update System 2020-08-31 16:00:16 UTC
FEDORA-2020-cad2321c3e has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.