Hello Jim,

It turns out that our nginx configuration setting for file size was too small 
to allow for your new archive and the nginx error page to report the problem 
was missing (hence, the 404).  This has all now been corrected, so you should 
have no problem uploading your new version for defuse.  Thanks for discovering 
this problem, and sorry for any inconvenience this may have caused.

Greg Von Kuster

On Nov 9, 2011, at 10:14 PM, Jim Johnson wrote:

> Greg,
> 
> I had been trying  to push from my local clone, as I had before.  That failed 
> with a 404 error.
> I next tried uploading the tarball, which also resulted in a 404 error.   
> 
> My original upload that opened the repository had a defuse subdir.  
> I moved the contents of the subdir to the toplevel with the changeset 1 ( 
> 1:36306d8086fa)  
> 
> This update was for the latest release of DeFuse version 0.4.3.
> 
> Feel free to try whatever you need to.  I granted you permissions on the 
> repository if that helps.   
> I imagine we could delete the repository and recreate it need be.   
> 
> Thanks,
> 
> JJ
> 
> 
> 
> 
> On 11/9/11 8:32 PM, Greg Von Kuster wrote:
>> 
>> Hi Jim,
>> 
>> Thanks for sending your archive.
>> 
>> I can successfully clone your defuse repository, but I have not tried 
>> pushing anything to it - I don't want to write to your repository.  I 
>> noticed that your last change set removed the defuse directory.  Did you do 
>> that by uploading a new tarball that did not include the defuse directory or 
>> did you have a locally cloned defuse repository from which you were pushing 
>> changes?
>> 
>> Did the 404 error occur when you attempted to upload the tarball (you sent 
>> me) to the repository, or was it a specific file from the tarball?
>> 
>> Thanks!
>> 
>> 
>> On Nov 9, 2011, at 8:13 PM, Jim Johnson wrote:
>> 
>>> Here it is.
>>> JJ
>>> 
>>> On 11/9/11 5:14 PM, Greg Von Kuster wrote:
>>>> Hi Jim,
>>>> 
>>>> Would you mind attaching a tarball of the changed files you were 
>>>> attempting to upload or push and send them to me?  It would help me figure 
>>>> out the problem.
>>>> 
>>>> Thanks!
>>>> 
>>>> Greg
>>>> 
>>>> On Nov 9, 2011, at 4:35 PM, Jim Johnson wrote:
>>>> 
>>>>> I successfully pushed updates to my gmap and mothur toolshed repositories 
>>>>> yesterday,
>>>>> but got an error when I tried to push changes to defuse.
>>>>> 
>>>>> % hg push
>>>>> pushing to http://jjohn...@toolshed.g2.bx.psu.edu/repos/jjohnson/defuse
>>>>> searching for changes
>>>>> abort: HTTP Error 404: Not Found
>>>>> 
>>>>> 
>>>>> I also tried uploading via the webform and got the same 404 error from 
>>>>> nginx/1.1.4
>>>>> 
>>>>> Any insights?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> JJ
>>>>> 
>>>>> 
>>>>> 
>>>>> ___________________________________________________________
>>>>> Please keep all replies on the list by using "reply all"
>>>>> in your mail client.  To manage your subscriptions to this
>>>>> and other Galaxy lists, please use the interface at:
>>>>> 
>>>>> http://lists.bx.psu.edu/
>>>> Greg Von Kuster
>>>> Galaxy Development Team
>>>> g...@bx.psu.edu
>>>> 
>>>> 
>>>> 
>>> <defuse_update.tar.gz>
>> Greg Von Kuster
>> Galaxy Development Team
>> g...@bx.psu.edu
>> 
>> 
>> 
> 

Greg Von Kuster
Galaxy Development Team
g...@bx.psu.edu



___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/

Reply via email to