Page MenuHomeSoftware Heritage

investigate gnu.org tarball ingestion failures
Closed, MigratedEdits Locked

Description

Some tarballs were unsuccessfully loaded (4 if i remember correctly).

This task is about investigating why and how to overcome such limitations.

Event Timeline

ardumont claimed this task.
ardumont raised the priority of this task from to High.
ardumont updated the task description. (Show Details)
ardumont added a subscriber: ardumont.
ardumont lowered the priority of this task from High to Normal.Nov 3 2015, 12:24 PM
ardumont lowered the priority of this task from Normal to Low.Nov 3 2015, 1:51 PM
olasd changed the visibility from "All Users" to "Public (No Login Required)".May 13 2016, 5:07 PM

I've no idea what this task means. @ardumont: can you clarify or close it if not relevant anymore?

I've no idea what this task means.

Yes, clearly unclear!

I believe it's related to 4 tarballs that we were not able to inject.
For example, one was about unsupported zip format...

I'll update the description.

ardumont renamed this task from logging replay error limitation investigation to Investigate the failure in tarball ingestion.Feb 9 2017, 5:11 PM
ardumont updated the task description. (Show Details)
zack renamed this task from Investigate the failure in tarball ingestion to investigate gnu.org tarball ingestion failures.Feb 12 2017, 6:16 PM
zack added a project: Origin-GNU.

is this still going? can it be closed as obsolete, maybe just noting down here the 4 failed tarballs? (we're going to do a full swipe soon anyway with the new listers/loaders)

zack claimed this task.

oh, the info is in T192 already
closing