Re: File bugzilla-4.0-1.fc14.src.rpm uploaded to lookaside cache by eseyman

[Rahul Sundaram]

On 03/28/2011 03:44 AM, Emmanuel Seyman wrote:
>  A file has been added to the lookaside cache for bugzilla:
>
>  c5f119e869193ae58893f8fc7a0373a2  bugzilla-4.0-1.fc14.src.rpm 
Why are you uploading srpm to lookaside cache instead of the source tarball?

Rahul

File bugzilla-4.0-1.fc14.src.rpm uploaded to lookaside cache by eseyman

[Emmanuel Seyman]

* Rahul Sundaram [28/03/2011 00:23] :
>  
>  Why are you uploading srpm to lookaside cache instead of the source tarball? 
It's a mistake. I wanted to upload the source tarball and picked the
wrong file. Is there anything for me to undo?

Emmanuel

File bugzilla-4.0-1.fc14.src.rpm uploaded to lookaside cache by eseyman

[Jason L Tibbitts III]

> >>>> "ES" == Emmanuel Seyman
> <emmanuel.seyman(a)club-internet.fr&gt; writes: 
ES> It's a mistake. I wanted to upload the source tarball and picked the
ES> wrong file. Is there anything for me to undo?

It is pretty much permanently in the git repository, and anyone who
does a non-shallow clone of the package will have to download that file.

There's a way to rewrite past history, but it has so many drawbacks that
we may not be able to use it.

And before anyone asks, I already created a hook that prevents this kind
of thing.  What remains is to actually hook that up to all of the
existing repositories.

 - J<

File bugzilla-4.0-1.fc14.src.rpm uploaded to lookaside cache by eseyman

[Jason L Tibbitts III]

Erm, I guess I misread.  I thought the file had been checked into git,
rather than uploaded to the lookaside.  Checking big binaries into git
is a problem, uploading them to the lookaside isn't.

I can remove it from the lookaside if that's really necessary, but
there's really not much reason since it has essentially no impact except
for a small amount of disk usage on the server.

 - J<