translate.fedoraproject.org cannot find any catalogue

[Petr Pisar]

Hello,

am I the only one who cannot get any catalogue from Fedora transifex web?
Whenever I click to view or download a catalogue, I get after long time `Not
found' error page. Example URL:
https://translate.fedoraproject.org/projects/p/fedora-web/c/master-fedora...

-- Petr

[Yuri Chornoivan]

написане Wed, 10 Nov 2010 17:10:11 +0200, Petr Pisar <ppisar(a)redhat.com&gt;:

>  Hello,
>
>  am I the only one who cannot get any catalogue from Fedora transifex web?
>  Whenever I click to view or download a catalogue, I get after long time  
>  `Not
>  found' error page. Example URL:
>
> https://translate.fedoraproject.org/projects/p/fedora-web/c/master-fedora...
>
>  -- Petr 
Hi!

Fedora Transifex is almost completely broken. Please use webgit to  
download catalogues:

http://git.fedorahosted.org/git?p=fedora-web.git;a=blob_plain;f=fedorapro...

Best regards,
Yuri

[Petr Pisar]

On Wed, Nov 10, 2010 at 06:46:34PM +0200, Yuri Chornoivan wrote:
>  Fedora Transifex is almost completely broken. Please use webgit to  
>  download catalogues:
>  
>
> http://git.fedorahosted.org/git?p=fedora-web.git;a=blob_plain;f=fedorapro...
>   
And pushes? I got an complain from public about a typo on main web page, thus
I wanted to fix it.

-- Petr

[Yuri Chornoivan]

написане Wed, 10 Nov 2010 19:30:26 +0200, Petr Pisar <ppisar(a)redhat.com&gt;:

>  On Wed, Nov 10, 2010 at 06:46:34PM +0200, Yuri Chornoivan wrote:
> > Fedora Transifex is almost completely broken. Please use webgit to
> > download catalogues:
> >
> >
> http://git.fedorahosted.org/git?p=fedora-web.git;a=blob_plain;f=fedorapro...
> >
>  And pushes? I got an complain from public about a typo on main web page,  
>  thus
>  I wanted to fix it. 
Pushes work... sometimes (if you have enough patience).

[Piotr Drąg]

2010/11/10 Yuri Chornoivan <yurchor(a)ukr.net&gt;:
>  написане Wed, 10 Nov 2010 19:30:26 +0200, Petr Pisar
> <ppisar(a)redhat.com&gt;:
> > On Wed, Nov 10, 2010 at 06:46:34PM +0200, Yuri Chornoivan wrote:
> >> Fedora Transifex is almost completely broken. Please use webgit to
> >> download catalogues:
> >>
> >>
> http://git.fedorahosted.org/git?p=fedora-web.git;a=blob_plain;f=fedorapro...
> >>
> > And pushes? I got an complain from public about a typo on main web page,
> > thus
> > I wanted to fix it.
>
>  Pushes work... sometimes (if you have enough patience).
>  
I've cleaned this particular module's cache and it should work for now.

Something is broken though and we need someone knowing Tx to look into
this. Modules are not refreshing for weeks, there are HTTP Errors 408
and Page not founds everywhere, submitting rarely works. Maybe it
hasn't got enough resources or something, I don't know, I'm not a
developer nor a sysadmin.

It would also be just awesome if we could update to 0.9.2 release [1],
but it appears no one have time and knowledge to do this, since it's
harder then updating the packages [2]. I know upstream developers are
very busy. I just wish they could find some time for us to guide us
through it. But for this to happen, we need to update Transifex
packages in Fedora and EPEL first. Domingo, do you need any help to
push the updates?

[1] This bugfix release for 0.9.x series will be released soon. I
don't think 1.0 is an option for now, fo several reasons: it's a
massive workflow change, we need at least 0.9.1 deployed first either
way, and 1.0 has some problems on its own (even tx.net has not been
ported yet).

[2] https://fedorahosted.org/fedora-infrastructure/ticket/2285

-- 
Piotr Drąg
http://raven.pmail.pl/

[Domingo Becker]

2010/11/10 Piotr Drąg <piotrdrag(a)gmail.com&gt;:
>  2010/11/10 Yuri Chornoivan <yurchor(a)ukr.net&gt;:
> > написане Wed, 10 Nov 2010 19:30:26 +0200, Petr Pisar <ppisar(a)redhat.com&gt;:
> >> On Wed, Nov 10, 2010 at 06:46:34PM +0200, Yuri Chornoivan wrote:
> >>> Fedora Transifex is almost completely broken. Please use webgit to
> >>> download catalogues:
> >>>
> >>>
> http://git.fedorahosted.org/git?p=fedora-web.git;a=blob_plain;f=fedorapro...
> >>>
> >> And pushes? I got an complain from public about a typo on main web page,
> >> thus
> >> I wanted to fix it.
> >
> > Pushes work... sometimes (if you have enough patience).
> >
>
>  I've cleaned this particular module's cache and it should work for now.
>
>  Something is broken though and we need someone knowing Tx to look into
>  this. Modules are not refreshing for weeks, there are HTTP Errors 408
>  and Page not founds everywhere, submitting rarely works. Maybe it
>  hasn't got enough resources or something, I don't know, I'm not a
>  developer nor a sysadmin.
>  
It seems that a script to refresh/clean the module's cache is not
working from cron for some reason.
I've been talking about this issue to diegobz at #fedora-latam-rpmdev
and he said we should ping fedora-admin guys at the appropriate
channel.
If they can't solve the issue, they will ask upstream (diegobz and
glezos), and they will help solving it.
I think we need to have a wiki page to explain translators how to ask
for help to fedora-admin people about Transifex issues. Perhaps it
exists, but nobody seems to find it.

>  It would also be just awesome if we could update to 0.9.2 release
> [1],
>  but it appears no one have time and knowledge to do this, since it's
>  harder then updating the packages [2]. I know upstream developers are
>  very busy. I just wish they could find some time for us to guide us
>  through it. But for this to happen, we need to update Transifex
>  packages in Fedora and EPEL first. Domingo, do you need any help to
>  push the updates?
>  
I needed a packager a month and a half ago.
But finally, I submitted myself the packages for review [1], a month
later than the problem was identified and solved [2],  so I'm becoming
a Fedora packager now.

Fedora build system has it's own time.
So we have to wait a little bit more, until the packages reach the repos.
The tracking bug is the one for Transifex update [3].
Django-south has concluded [4].
django-addons [5] and django-threadedcomments [6] are on their way to
the repos. They have been approved and the SCM request is in progress.
django-ajax-selects [7] and django-staticfiles [8] are still under review.
Once the dependencies are finished, Transifex [3] package will be
rebuilt, and I'll be able to test it once more, to make sure we didn't
break anything in the process.
Then, fedora-admin guys will use these packages to upgrade Transifex
right out of the Fedora-EPEL repos.

After we have t.fp.o running Tx 0.9.1, I will start working to upgrade
it to 0.9.2.
I hope things will be easier from then on.


[1] https://fedorahosted.org/fedora-infrastructure/ticket/2389#comment:42

[2] https://fedorahosted.org/fedora-infrastructure/ticket/2389#comment:27

[3] https://bugzilla.redhat.com/show_bug.cgi?id=645752

[4] https://bugzilla.redhat.com/show_bug.cgi?id=645759

[5] https://bugzilla.redhat.com/show_bug.cgi?id=645764

[6] https://bugzilla.redhat.com/show_bug.cgi?id=645761

[7] https://bugzilla.redhat.com/show_bug.cgi?id=645760

[8] https://bugzilla.redhat.com/show_bug.cgi?id=645762


kind regards

Domingo Becker (es)

[Ruediger Landmann]

On 11/11/2010 02:46 AM, Yuri Chornoivan wrote:
>  Hi!
>
>  Fedora Transifex is almost completely broken. Please use webgit to
>  download catalogues: 
Just a note, too, that any  translators who want to work on 
Documentation (including the release notes) should let me know either on 
this list or on the docs list, and I am happy to provide access to the 
documentation git repos and show you how to commit your translations 
directly. Zoltan, I think you were asking about this recently?

Similarly, I would love to hear from language teams who want to take 
responsibility for publishing documentation in their language. We have 
set up a wiki page[0] to track who is responsible for publishing 
documentation in that language. So far, we have everything set to 
"docs", although I think the Spanish and Dutch teams are now 
self-sufficient. Gradually, we would like each language team to "own" 
their own docs and function independently. You can get an overview of 
the process here[1].

Thanks everyone for your hard work under adversity :)

Cheers
Rudi


[0] https://fedoraproject.org/wiki/Publishing_docs_by_language

[1] http://fedoraproject.org/wiki/Publishing_a_document_with_Publican

[Gerd Koenig]

Hello Rüdiger,

regarding your note, I wanted to ask for granting access and a small
tutorial for "how to deal with it"
to be able to continue translation-work.

many thanks in advance....::GERD::....

On 10 November 2010 23:57, Ruediger Landmann <r.landmann(a)redhat.com&gt; wrote:

>  On 11/11/2010 02:46 AM, Yuri Chornoivan wrote:
>  > Hi!
>  >
>  > Fedora Transifex is almost completely broken. Please use webgit to
>  > download catalogues:
>
>  Just a note, too, that any  translators who want to work on
>  Documentation (including the release notes) should let me know either on
>  this list or on the docs list, and I am happy to provide access to the
>  documentation git repos and show you how to commit your translations
>  directly. Zoltan, I think you were asking about this recently?
>
>  Similarly, I would love to hear from language teams who want to take
>  responsibility for publishing documentation in their language. We have
>  set up a wiki page[0] to track who is responsible for publishing
>  documentation in that language. So far, we have everything set to
>  "docs", although I think the Spanish and Dutch teams are now
>  self-sufficient. Gradually, we would like each language team to "own"
>  their own docs and function independently. You can get an overview of
>  the process here[1].
>
>  Thanks everyone for your hard work under adversity :)
>
>  Cheers
>  Rudi
>
>
>  [0] https://fedoraproject.org/wiki/Publishing_docs_by_language
>
>  [1] http://fedoraproject.org/wiki/Publishing_a_document_with_Publican
>  --
>  trans mailing list
>  trans(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/trans
>

[Piotr Drąg]

2010/11/10 Domingo Becker <domingobecker(a)gmail.com&gt;:
>  It seems that a script to refresh/clean the module's cache is
> not
>  working from cron for some reason.
>  I've been talking about this issue to diegobz at #fedora-latam-rpmdev
>  and he said we should ping fedora-admin guys at the appropriate
>  channel.
>  If they can't solve the issue, they will ask upstream (diegobz and
>  glezos), and they will help solving it.
>  I think we need to have a wiki page to explain translators how to ask
>  for help to fedora-admin people about Transifex issues. Perhaps it
>  exists, but nobody seems to find it.
>  
It has been filed several times at different places (Infra trac,
Bugzilla, mailing lists), but sure we can do it once more. I'll file a
new ticket about cron job at Infra trac instance tomorrow after work,
if no one will do it to then.

-- 
Piotr Drąg
http://raven.pmail.pl/

[Domingo Becker]

2010/11/11 Piotr Drąg <piotrdrag(a)gmail.com&gt;:
>  2010/11/10 Domingo Becker <domingobecker(a)gmail.com&gt;:
> > It seems that a script to refresh/clean the module's cache is not
> > working from cron for some reason.
> > I've been talking about this issue to diegobz at #fedora-latam-rpmdev
> > and he said we should ping fedora-admin guys at the appropriate
> > channel.
> > If they can't solve the issue, they will ask upstream (diegobz and
> > glezos), and they will help solving it.
> > I think we need to have a wiki page to explain translators how to ask
> > for help to fedora-admin people about Transifex issues. Perhaps it
> > exists, but nobody seems to find it.
> >
>
>  It has been filed several times at different places (Infra trac,
>  Bugzilla, mailing lists), but sure we can do it once more. I'll file a
>  new ticket about cron job at Infra trac instance tomorrow after work,
>  if no one will do it to then.
>  
I mean it should be easy for a translator with this problem to find
out how to get help from admin people.
If a document already exists commenting how to do it, then it is not
reached by translators facing this problem, and that's why they are
using this list. Admin people normally do not read this list, or if
they do, they expect us to follow their rules.

What can we do to improve this?

I guess a reference at the L10N page [1] to another page that document
how to proceed in case of a Transifex issue.
If that page already exists, it's just a matter to add a link.

The fact that this error was informed before and it was solved by
someone, doesn't mean that it will not appear anymore.
It would probably be fixed by an upgrade. It's what we are trying to do.
In the meantime, in order to keep the current Transifex instance
alive,  errors should be informed as many times as necessary.

It think the real problem is (and I may be wrong) that the cron job
for refreshing cache is overwhelmed by the number of modules,
languages and files it actually has.
If the cron job runs four times a day, with a very low priority to let
translators work in the meantime, it's probably not enough time to
complete it.
It may start over and over again, resulting in a deadlock and
consuming too much resources.
If I see a cron job that starts over and over again without
terminating the previous one, I would disable it, no matter what it
does. Perhaps that's what it's happening.
But, as I said, I may be wrong.

[1] https://fedoraproject.org/wiki/L10N#Bug_Reporting.2C_Testing.2C_and_Quali...

kind regards

Domingo Becker (es)

[Thomas Canniot]

Le 10/11/2010 23:57, Ruediger Landmann a écrit :
>  On 11/11/2010 02:46 AM, Yuri Chornoivan wrote:
> > Hi!
> >
> > Fedora Transifex is almost completely broken. Please use webgit to
> > download catalogues:
>
>  Just a note, too, that any  translators who want to work on
>  Documentation (including the release notes) should let me know either on
>  this list or on the docs list, and I am happy to provide access to the
>  documentation git repos and show you how to commit your translations
>  directly. Zoltan, I think you were asking about this recently?
>
>  Similarly, I would love to hear from language teams who want to take
>  responsibility for publishing documentation in their language. We have
>  set up a wiki page[0] to track who is responsible for publishing
>  documentation in that language. So far, we have everything set to
>  "docs", although I think the Spanish and Dutch teams are now
>  self-sufficient. Gradually, we would like each language team to "own"
>  their own docs and function independently. You can get an overview of
>  the process here[1].
>
>  Thanks everyone for your hard work under adversity :)
>
>  Cheers
>  Rudi
>  
Hello,

I have a few question about all this:
- why isn't publication not automated like it is for website ofr example?
- is there still "a bug in Publican when publishing books on a system 
where the locale is not set to American English (en-US)"


Thanks

Thomas

[Ruediger Landmann]

On 11/14/2010 05:06 PM, Thomas Canniot wrote:
>  Hello,
>
>  I have a few question about all this:
>  - why isn't publication not automated like it is for website ofr example? 
We are working towards a greater level of automation, but this requires 
us to have a version of Publican available for Red Hat Enterprise Linux 
5 (since this is the OS on the web server), and we have dependency 
issues that have prevented this so far. You can track progress on this 
work here.[0] Once this is complete, translators should be able to 
publish their work with two commands on the command line: a "publican 
package" command to build an RPM package of the document and a "koji 
tag-pkg" command to tag the document for release on the website.

However, I doubt we will ever implement a system where automation will 
attempt to publish a translation as soon as completion reaches 100% -- 
the nature of XML is such that even when a translation is 100% complete, 
it might include tagging errors that break the XML structure and prevent 
a document from building at all. Furthermore, given the length and 
complexity of these documents, no document (in English or in 
translation) should ever go live to the public until it has been built 
and proofread, which means some kind of deliberate, manual process.

>  - is there still "a bug in Publican when publishing books on a
> system
>  where the locale is not set to American English (en-US)" 
We believe the bug still exists, but the problem is poorly understood 
right now, because we on the Publican team haven't researched it 
properly.[1] Last week, Piotr posted to docs-list to report that typing 
"LANG=C" in your terminal before running the Publican commands seems to 
work around the problem without logging in under the en_US locale [2], 
which makes sense.

I'd love to hear from translators who can verify the bug and verify that 
the workaround works. There are some instructions in that first email I 
linked.[1]

Cheers
Ruediger



[0] http://fedoraproject.org/wiki/Automating_publishing
[1] http://lists.fedoraproject.org/pipermail/trans/2010-November/008367.html
[2] http://lists.fedoraproject.org/pipermail/docs/2010-November/012916.html

[Ruediger Landmann]

On 11/11/2010 03:59 PM, Gerd Koenig wrote:
>  Hello Rüdiger,
>
>  regarding your note, I wanted to ask for granting access and a small
>  tutorial for "how to deal with it"
>  to be able to continue translation-work.
>
>  many thanks in advance....::GERD::.... 
Very sorry for the late reply Gerd -- I will take care of this for you 
later today. I have been distracted away from trans-list this last week...

Cheers
Rüdiger

[Thomas Canniot]

Le 18/11/2010 00:06, Ruediger Landmann a écrit :
>  On 11/14/2010 05:06 PM, Thomas Canniot wrote:
> >
> > Hello,
> >
> > I have a few question about all this:
> > - why isn't publication not automated like it is for website ofr example?
>
>  We are working towards a greater level of automation, but this requires
>  us to have a version of Publican available for Red Hat Enterprise Linux
>  5 (since this is the OS on the web server), and we have dependency
>  issues that have prevented this so far. You can track progress on this
>  work here.[0] Once this is complete, translators should be able to
>  publish their work with two commands on the command line: a "publican
>  package" command to build an RPM package of the document and a "koji
>  tag-pkg" command to tag the document for release on the website.
>
>  However, I doubt we will ever implement a system where automation will
>  attempt to publish a translation as soon as completion reaches 100% --
>  the nature of XML is such that even when a translation is 100% complete,
>  it might include tagging errors that break the XML structure and prevent
>  a document from building at all. Furthermore, given the length and
>  complexity of these documents, no document (in English or in
>  translation) should ever go live to the public until it has been built
>  and proofread, which means some kind of deliberate, manual process.
>
> > - is there still "a bug in Publican when publishing books on a system
> > where the locale is not set to American English (en-US)"
>
>  We believe the bug still exists, but the problem is poorly understood
>  right now, because we on the Publican team haven't researched it
>  properly.[1] Last week, Piotr posted to docs-list to report that typing
>  "LANG=C" in your terminal before running the Publican commands seems to
>  work around the problem without logging in under the en_US locale [2],
>  which makes sense.
>
>  I'd love to hear from translators who can verify the bug and verify that
>  the workaround works. There are some instructions in that first email I
>  linked.[1]
>
>  Cheers
>  Ruediger
>  

OK Ruediger thanks for your answer. I would like to be able to use the 
Documentation git repo for all the French Team.

Many thanks,

Thomas