Bug 795781 - Update the POT file under transifex (file corrupted)
Summary: Update the POT file under transifex (file corrupted)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-21 14:22 UTC by Kevin Raymond
Modified: 2014-03-17 03:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 20:42:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kevin Raymond 2012-02-21 14:22:58 UTC
Hi, we are in string freeze, that's the translator period.

Pulling our translation will fail because of a corrupted source file (pot).

tx pull give us 

Pulling translations for resource fedora-initscripts.default (source: None)
 -> fr: translations/fedora-initscripts.default/fr.po
Exception: Remote server replied: Error compiling the translation file: 'utf8' codec can't decode byte 0xa0 in position 29036: invalid start byte
Pulling translations for resource fedora-elections-guide.Appendix (source: None)

If we try to download the original pot it will fail also.

If your tx push -s fails, please get in touch with the transifex.net team, or I will.

Thanks,

Comment 1 Kevin Raymond 2012-02-21 15:08:43 UTC
Just resolved by mpessas (seen by #transifex).
The binary character was still present cause the last update was not different, it was not overridden. 
He has removed it from their side, should not appear again.

Everything fine: http://fpaste.org/dhzq/

Cheers

Comment 2 Kevin Raymond 2012-02-26 12:48:49 UTC
(In reply to comment #1)
> He has removed it from their side, should not appear again.
> 

Unfortunately, it's back.
Have you uploaded a new pot? If not, we have to see with the indifex guys.

Comment 3 Bill Nottingham 2012-02-27 16:59:00 UTC
Last time I pushed was a week or two ago, nothing since.

Comment 4 Kevin Raymond 2012-02-28 14:14:14 UTC
We get an update on the mailing list:
lists.fedoraproject.org/pipermail/trans/2012-February/009689.htmle 

Should be fixed by the end of this week.

Comment 5 Kevin Raymond 2012-03-02 10:16:44 UTC
Fixed and verified by mpessas.
(He is right, my previous comment was linking to another bug not related…)

Should not appear again… He will check if that could appear again. If so, please come by irc #transifex (Freenode) and ask mpessas.

Comment 6 Fedora End Of Life 2013-07-04 08:04:53 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 7 Fedora End Of Life 2013-08-01 20:43:00 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 Kevin Raymond 2013-08-04 11:37:45 UTC
was fixed


Note You need to log in before you can comment on or make changes to this bug.