The latest 5.x-2.2 is missing the /po directory with the translation files. Older releases have it packaged together!?

Comments

hass’s picture

hass commented
Title: PO directory is missing in release! » PO directory is missing!

Aside i have updated D6 translation folder in CVS to the new structure (po > translations)... and updated the German D5 and D6 translation, too

hass’s picture

hass commented
Title: PO directory is missing! » PO directory is missing in release!
pwolanin’s picture

pwolanin commented
Title: PO directory is missing! » PO directory is missing in release!
Project: Node clone » Drupal.org infrastructure
Version: 5.x-2.2 »
Component: Code » CVS

odd- I did get a CVS error about the tagging however - something about no write permission to the repository for everything in /po. Can you tag those files?

The files are listed as being updated by you:

http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/node_clone/...

pwolanin’s picture

pwolanin commented
Project: Drupal.org infrastructure » Node clone
Version: » 5.x-2.x-dev
Component: CVS » Miscellaneous
Status: Active » Fixed

apparently there was a problem with the checkout I was using to commit changes. Making a .3 release that should have the .po files.

pwolanin’s picture

pwolanin commented
Status: Fixed » Active

odd - even though the tagging seemed to have worked, I still don't see the files in the 5.x-2.3 (they are there in 5.x-1.3).

hass’s picture

hass commented

I don't know what you have done, but now you have added the D6 "translations" directory to a D5 release what is wrong. If i sync DRUPAL-5--2 of node_clone i see a "po" directory what is correct... i thing you have wrongly tagged the HEAD translation files as DRUPAL-5--2-3... not sure what client you are using, but my Eclipse "view" looks as it should (branches are not mixed)

Ups... additional you have added the 2.x po files to 1.x branch... that's not correct... i haven't updated the 1.x branch. These files are very different to 2.x... remember who many strings you have changed in 2.x :-)

pwolanin’s picture

pwolanin commented

bah, ok - I think I had a bad checkout and apparently running the commit from there has broken many things. Can you delete and then add/commit the right files on the 2 branches and HEAD?

hass’s picture

hass commented

Sounds like a misunderstanding.

Not my box or CVS is wrong... it's your box. All files are in the correct folders in CVS... you must fix your box, application or how you tag files for a new release. If you replace your local version with CVS all should be ok...

pwolanin’s picture

pwolanin commented

@hass - I had done a fresh checkout before I tagged for the -2.3 and -1.3, so I thought I had done so.

hass’s picture

hass commented

If you give me access to CVS it will took me ~5 minutes to tag all correctly again... but this wouldn't fix the issue for you next time. This is why i don't like to do this only to fix this. Maybe you should use Eclipse? :-) As i said - CVS is correctly branched... only tagging of files was wrong - what resulted in mixed releases.

pwolanin’s picture

pwolanin commented

@hass - I use the CLI CVS. It's the first time I've had such a problem...

pwolanin’s picture

pwolanin commented

I've just enabled -dev releases so hopefully we can sort this out without making any more "bad" point releases.

I think if the files are wrong there, it speaks of some deeper problem that now exists in the repository.

pwolanin’s picture

pwolanin commented

Ok, well this should be partially sorted out now. Apparently I had HEAD checked out and then tagged for DRUPAL-5--2-3 - a dumb mistake.

hass’s picture

hass commented
Status: Active » Fixed

Ok, 2.4 seems good now. I think you should unpublish 2.3 if this is a head... thx

pwolanin’s picture

pwolanin commented

@hass - I'm not going to be online much this weekend - can you open an infrastructure issue to get that release unpublished?

hass’s picture

hass commented
Title: PO directory is missing in release! » Unpublish node_clone 5.x-2.3
Project: Node clone » Drupal.org infrastructure
Version: 5.x-2.x-dev »
Component: Miscellaneous » Packaging

Could someone from infrastructure unpublish the node_clone 5.x-2.3 release (http://drupal.org/node/255566) build from a D6 version, please?

hass’s picture

hass commented
Status: Fixed » Active
hunmonk’s picture

hunmonk commented
Status: Active » Closed (won't fix)

we don't unpublish release nodes. the problem should be fixed going forward. if there's now a 2.4 release, then there should be no issue. feel free to edit the 2.3 release node to say it shouldn't be used.

hass’s picture

hass commented

I was not aware about this and don't know why... i have already unpublished release nodes and it tell update_status users this release is "unsupported" if users have it installed. That is what this release should receive - an "unsupported" status.

pwolanin should change the text on the release node if not possible.

pwolanin’s picture

pwolanin commented
Project: Drupal.org infrastructure » Node clone
Version: » 5.x-2.3
Component: Packaging » Miscellaneous
Status: Closed (won't fix) » Fixed

I did add text to it already.

pwolanin’s picture

pwolanin commented
Status: Fixed » Closed (fixed)