#6336 Tarball generation of PhpGedView SVN repository doesn't work [ss4244]

v1.1.0
closed
nobody
p3 (267) support (446) 42cc (432)
General
Tim Van Steenburgh
2015-08-20
2013-06-05
Chris Tsai
No

[forge:site-support:#4244]

I'm trying to download a Tarball Snapshot of the following:
https://sourceforge.net/p/phpgedview/svn/HEAD/tarball

I see the message that the system is generating the snapshot, but after 15 minutes of looking at this message, nothing has happened, and the dowload hasn't even started yet.

I'm told that the GIT download should work, but this project is still on SVN, and won't be moved anytime soon. The project is essentially in "maintenance" mode, with little new development taking place.

It's not working for me either, and I've checked the task_manager and it shows them "complete", but I'm still not getting the download.

I've tried both https://sourceforge.net/p/phpgedview/svn/HEAD/tarball and https://sourceforge.net/p/phpgedview/svn/7094/tarball

Related

Tickets: #6518

Discussion

  • Dave Brondsema

    Dave Brondsema - 2013-06-05 
    20:44:57,976 ERROR [allura.tasks.repo_tasks] Could not create tarball for repository phpgedview:svn revision 7094 path None
Traceback (most recent call last):
  File "/var/local/allura/Allura/allura/tasks/repo_tasks.py", line 133, in tarball
    repo.tarball(revision, path)
  File "/var/local/allura/Allura/allura/model/repository.py", line 557, in tarball
    self._impl.tarball(revision, path)
  File "/var/local/env-allura/lib/python2.7/site-packages/TimerMiddleware-0.4.2-py2.7.egg/timermiddleware/__init__.py", line 116, in wrapper
    return self.run_and_log(func, inst, *args, **kwargs)
  File "/var/local/env-allura/lib/python2.7/site-packages/TimerMiddleware-0.4.2-py2.7.egg/timermiddleware/__init__.py", line 141, in run_and_log
    return func(*args, **kwargs)
  File "/var/local/allura/ForgeSVN/forgesvn/model/svn.py", line 683, in tarball
    revision=pysvn.Revision(pysvn.opt_revision_kind.number, commit))
ClientError: Can't convert string from 'UTF-8' to native encoding:
/nfs/allura/code-snapshots/svn/p/ph/phpgedview/svn/phpgedview-svn-7094-trunk/phpGedView/places/ISR/ISR_?\195?\156?\195?\174-?\195?\135?\195?\188?\195?\171?\195?\188_?\195?\156?\195?\174-?\195?\135?\195?\188?\195?\171?\195?\188.txt
     

  • Anonymous - 2013-09-04

    Originally by: ggpauly

    Dave Brondsema,

    I read an apparently related posting at http://www.juretta.com/log/2007/05/09/svn_can_t_convert_string_from_utf-8_to_native_encoding_/

    However I'm not sure how this applies. Is the Israeli place name(s) cited in the traceback specifically a problem that must be addressed?

    Or is the inclusion of UTF-8 with multiple locales the issue?

     

  • Anonymous - 2013-09-04

    Originally by: canajun2eh

    It looks like the fancy new Sourceforge system can't handle file names that contain characters that aren't in the ASCII character set.

    They need to publish this restriction.

    I can get rid of the non-ASCII file names to make the project slightly less user-friendly (not that it is very user-friendly to begin with!)

     

  • Anonymous - 2013-09-05

    Originally by: canajun2eh

    Dave Brondsema:
    WHY did you not find the time to contact me (the original submitter of support ticket 4244)?????

    Yesterday, I deleted the files in the "places/ISR" directory that had Hebrew file names. They were not essential. I also changed several file names in the "images/flags" directory to remove accents. Now, all file names in the project have only unaccented letters in them.

    Today, I'm still having trouble downloading an SVN snapshot from this URL:
    https://sourceforge.net/p/phpgedview/svn/HEAD/tarball?path=/trunk/phpGedView

    The messages I see begin with "Checking snapshot status...". After a little while, the screen is updated with "We're having trouble finding that snapshot. Would you like to resubmit?" and a button "Resubmit Snapshot Request".

    If that "Resubmit" button is clicked, the process repeats.

     

  • Dave Brondsema

    Dave Brondsema - 2013-09-05

    Gerry, we haven't begun to work on fixing this bug, but we plan to. I posted the server-side error message a while ago, when I came across it, but didn't have anything else to say at the time.

    FYI the current error details are: ClientError: Can't convert string from 'UTF-8' to native encoding: /nfs/allura/code-snapshots/svn/p/ph/phpgedview/svn/phpgedview-svn-7096-trunk/phpGedView/places/FRA/flags/Franche-Comt?\195?\169.gif

    We are planning on fixing this, so you shouldn't have to rename your files unless you want a workaround in the mean time.

     

  • Anonymous - 2013-09-06

    Originally by: canajun2eh

    Dave Brondsema:
    Thank you. I removed the non-essential accented letters from several files in the "places/FRA/flags" directory, and the repository snapshot now works. The project is now using file names that contain only letters in the ASCII character set.

    I'm glad to know that you plan on fixing the bug in the SourceForge software that our project uncovered. There's no rush now, since the work-around ("don't use non-ASCII file names") works.

     

    Last edit: Anonymous 2015-08-19

  • Dave Brondsema

    Dave Brondsema - 2013-11-06
    • Labels: support, p3 --> p3, support, 42cc
    • Status: open --> in-progress
    • Milestone: limbo --> forge-backlog
     

  • Igor Bondarenko - 2013-11-12
    • status: in-progress --> code-review
     

  • Igor Bondarenko - 2013-11-12

    Closed #477.

    je/42cc_6336

    We've fixed it by setting proper locale (it's known pysvn issue). But there is one inconvenience, though. Unicode symbols in file names end up in zip archive as question marks, but if you unzip the archive, then you get proper names back. Question marks only appear when viewing inside zip with some file manager. We've didn't find a way to fix that.

     

  • Tim Van Steenburgh - 2013-11-19
    • QA: Tim Van Steenburgh
    • Milestone: forge-backlog --> forge-nov-29
     

  • Tim Van Steenburgh - 2013-11-20
    • status: code-review --> closed
     

Log in to post a comment.