From mgrigull at redhat.com Tue Oct 9 00:49:41 2012 From: mgrigull at redhat.com (Marco Grigull) Date: Tue, 09 Oct 2012 10:49:41 +1000 Subject: [zanata-users] translate.zanata.org upgrade 12:00 GMT+10 Message-ID: <507374A5.20506@redhat.com> Hi, We will upgrade Zanata to 1.7.3 at midday today. Please tune into #zanata on freenode and save your work before the outage commences. Regards, Marco -- Marco Grigull, Systems Administrator, Engineering Operations 85 88229 / +61 7 3514 8229 From mgrigull at redhat.com Tue Oct 9 02:24:08 2012 From: mgrigull at redhat.com (Marco Grigull) Date: Tue, 09 Oct 2012 12:24:08 +1000 Subject: [zanata-users] translate.zanata.org upgrade 12:00 GMT+10 In-Reply-To: <507374A5.20506@redhat.com> References: <507374A5.20506@redhat.com> Message-ID: <50738AC8.6060600@redhat.com> outage complete. On Tue 09 Oct 2012 10:49:41 AM EST, Marco Grigull wrote: > Hi, > > We will upgrade Zanata to 1.7.3 at midday today. > Please tune into #zanata on freenode and save your work before the > outage commences. > > Regards, > Marco > > > -- Marco Grigull, Systems Administrator, Engineering Operations 85 88229 / +61 7 3514 8229 From alikins at redhat.com Tue Oct 9 15:06:33 2012 From: alikins at redhat.com (Adrian Likins) Date: Tue, 09 Oct 2012 11:06:33 -0400 Subject: [zanata-users] 404's on zanata push --disable-ssl-cert --srcdir . --no-copytrans Message-ID: <50743D79.50506@redhat.com> Trying a push with "--disable-ssl-cert" and "--no-copytrans" to try to work around the 503 errors I get otherwise. Adding "--no-copytrans" results in 404's zanata-python-client is latest from github (152170421690ae8b203f2f5636df548044bbc290 atm) [adrian at dhcp231-28 po (RHEL5.9 %)]$ zanata push --disable-ssl-cert --srcdir . --no-copytrans Loading zanata project config from: /home/adrian/src/subscription-manager-internal/po/zanata.xml Loading zanata user config from: /home/adrian/.config/zanata.ini zanata server: https://translate.zanata.org/zanata zanata python client version: 1.3.11, zanata server API version: 1.7.0 Project: subscription-manager Version: 1.0.X Username: alikins Source language: en-US Reuse previous translation on server:False PO directory (originals):. This will overwrite/delete any existing documents on the server. Are you sure (y/n)?y Deleting the : error: Error 404 - The requested resource is not available Please take a reference in https://github.com/zanata/zanata/wiki/Python-Client-Troubleshooting From sflaniga at redhat.com Wed Oct 10 03:09:13 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Wed, 10 Oct 2012 13:09:13 +1000 Subject: [zanata-users] 404's on zanata push --disable-ssl-cert --srcdir . --no-copytrans In-Reply-To: <50743D79.50506@redhat.com> References: <50743D79.50506@redhat.com> Message-ID: <5074E6D9.8090503@redhat.com> Again? That's the second time we've seen an empty file called ":" appear in a subscription manager project, which is then extremely difficult to delete. I've requested a sysadmin to delete the errant document. On 2012-10-10 01:06, Adrian Likins wrote: > Trying a push with "--disable-ssl-cert" and "--no-copytrans" to try to > work around > the 503 errors I get otherwise. Adding "--no-copytrans" results in 404's > > zanata-python-client is latest from github > (152170421690ae8b203f2f5636df548044bbc290 atm) > > > > [adrian at dhcp231-28 po (RHEL5.9 %)]$ zanata push --disable-ssl-cert > --srcdir . --no-copytrans > Loading zanata project config from: > /home/adrian/src/subscription-manager-internal/po/zanata.xml > Loading zanata user config from: /home/adrian/.config/zanata.ini > zanata server: https://translate.zanata.org/zanata > zanata python client version: 1.3.11, zanata server API version: 1.7.0 > Project: subscription-manager > Version: 1.0.X > Username: alikins > Source language: en-US > Reuse previous translation on server:False > PO directory (originals):. > This will overwrite/delete any existing documents on the server. > Are you sure (y/n)?y > Deleting the : > error: Error 404 - The requested resource is not available > Please take a reference in > https://github.com/zanata/zanata/wiki/Python-Client-Troubleshooting > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From sflaniga at redhat.com Wed Oct 10 06:51:32 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Wed, 10 Oct 2012 16:51:32 +1000 Subject: [zanata-users] 404's on zanata push --disable-ssl-cert --srcdir . --no-copytrans In-Reply-To: <5074E6D9.8090503@redhat.com> References: <50743D79.50506@redhat.com> <5074E6D9.8090503@redhat.com> Message-ID: <50751AF4.9090101@redhat.com> This has been done now. You should be able to push, using --no-copytrans. On 2012-10-10 13:09, Sean Flanigan wrote: > Again? That's the second time we've seen an empty file called ":" > appear in a subscription manager project, which is then extremely > difficult to delete. I've requested a sysadmin to delete the errant > document. > > > On 2012-10-10 01:06, Adrian Likins wrote: >> Trying a push with "--disable-ssl-cert" and "--no-copytrans" to try to >> work around >> the 503 errors I get otherwise. Adding "--no-copytrans" results in 404's >> >> zanata-python-client is latest from github >> (152170421690ae8b203f2f5636df548044bbc290 atm) >> >> >> >> [adrian at dhcp231-28 po (RHEL5.9 %)]$ zanata push --disable-ssl-cert >> --srcdir . --no-copytrans >> Loading zanata project config from: >> /home/adrian/src/subscription-manager-internal/po/zanata.xml >> Loading zanata user config from: /home/adrian/.config/zanata.ini >> zanata server: https://translate.zanata.org/zanata >> zanata python client version: 1.3.11, zanata server API version: 1.7.0 >> Project: subscription-manager >> Version: 1.0.X >> Username: alikins >> Source language: en-US >> Reuse previous translation on server:False >> PO directory (originals):. >> This will overwrite/delete any existing documents on the server. >> Are you sure (y/n)?y >> Deleting the : >> error: Error 404 - The requested resource is not available >> Please take a reference in >> https://github.com/zanata/zanata/wiki/Python-Client-Troubleshooting >> >> _______________________________________________ >> zanata-users mailing list >> zanata-users at redhat.com >> https://www.redhat.com/mailman/listinfo/zanata-users > > -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From alikins at redhat.com Wed Oct 10 20:15:55 2012 From: alikins at redhat.com (Adrian Likins) Date: Wed, 10 Oct 2012 16:15:55 -0400 Subject: [zanata-users] 404's on zanata push --disable-ssl-cert --srcdir . --no-copytrans In-Reply-To: <50751AF4.9090101@redhat.com> References: <50743D79.50506@redhat.com> <5074E6D9.8090503@redhat.com> <50751AF4.9090101@redhat.com> Message-ID: <5075D77B.8060102@redhat.com> On 10/10/2012 02:51 AM, Sean Flanigan wrote: > This has been done now. You should be able to push, using --no-copytrans. Back to 503's now... Adrian From alikins at redhat.com Wed Oct 10 20:23:08 2012 From: alikins at redhat.com (Adrian Likins) Date: Wed, 10 Oct 2012 16:23:08 -0400 Subject: [zanata-users] 404's on zanata push --disable-ssl-cert --srcdir . --no-copytrans In-Reply-To: <5074E6D9.8090503@redhat.com> References: <50743D79.50506@redhat.com> <5074E6D9.8090503@redhat.com> Message-ID: <5075D92C.90809@redhat.com> On 10/09/2012 11:09 PM, Sean Flanigan wrote: > Again? That's the second time we've seen an empty file called ":" > appear in a subscription manager project, which is then extremely > difficult to delete. I've requested a sysadmin to delete the errant > document. Yeah, not sure what's up with that. I can't find anything obvious that would be causing it. No ':' files in the tree. Nothing in the zanata.xml. Nothing in my shell history with zanata and ':' in the same line. Any info about who or when those files got pushed? Adrian From sflaniga at redhat.com Fri Oct 12 02:49:16 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Fri, 12 Oct 2012 12:49:16 +1000 Subject: [zanata-users] 404's on zanata push --disable-ssl-cert --srcdir . --no-copytrans In-Reply-To: <5075D92C.90809@redhat.com> References: <50743D79.50506@redhat.com> <5074E6D9.8090503@redhat.com> <5075D92C.90809@redhat.com> Message-ID: <5077852C.7060709@redhat.com> On 2012-10-11 06:23, Adrian Likins wrote: > On 10/09/2012 11:09 PM, Sean Flanigan wrote: >> Again? That's the second time we've seen an empty file called ":" >> appear in a subscription manager project, which is then extremely >> difficult to delete. I've requested a sysadmin to delete the errant >> document. > > Yeah, not sure what's up with that. I can't find anything obvious > that would be causing it. No ':' files in the tree. Nothing in > the zanata.xml. Nothing in my shell history with zanata and ':' in the > same line. Any info about who or when those files got > pushed? No, but it must be a bug in the python client. Zanata server 2.0 will reject such filenames, log a warning (with a username), and return an error to the client, so it should be a lot easier to track down then. -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From alikins at redhat.com Wed Oct 31 22:30:34 2012 From: alikins at redhat.com (Adrian Likins) Date: Wed, 31 Oct 2012 18:30:34 -0400 Subject: [zanata-users] Project-Id-Version should be set to...? Message-ID: <5091A68A.9030606@redhat.com> For subscription-manager, the po's metadata value "Project-Id-Version" sometimes get's reset to "PACKAGE VERSION" at least on RHEL6, "msgfmt -c" complains about and prints a warning: po/gu.po:4: field `Project-Id-Version' still has initial default value Should this be set to something, or can I just ignore it? Adrian