Hi,
The "remote: Found another file with the destination path" is not actually
an error, I actually have thousands of those and it is normal. It's simply
suppose to be a warning that was added in version 1.9:
https://github.com/django/django/commit/5304494585c58b0c9245ea9896a6d6122a8673a2
"Added warning to collectstatic when static files have clashing names"
It should not make the code crash... but somehow maybe the logger become
unavailable and it is why I get exception "Resource temporarily
unavailable" ?
I will try turning down verbosity (so shouldn't be logging this anymore),
and see if it help... (verbosity=0)
On Wednesday, February 3, 2016 at 6:34:47 AM UTC-8, Sergiy Khohlov wrote:
>
> Hello Denis,
>
> This issue is not related to the django-require. Look like you have
> two files (with same name ) at the different paths. New collect static
> is trying to colelct both files and can not decided which one should be
> used.
> Could you please send part of the section STATICFILES_DIRS and
> INSTALLED_APP ?
>
> Many thanks,
>
> Serge
>
>
> +380 636150445
> skype: skhohlov
>
> On Wed, Feb 3, 2016 at 9:19 AM, Denis >
> wrote:
>
>> Hi,
>>
>> I'm looking at upgrading my application from 1.6 to 1.9.2... An issue I'm
>> encountering now is that on Heroku, running collectstatic doesn't work on
>> 1.9.2. The odd things is that if I try 1.8.7 instead, it work great...
>>
>>
>> Running:
>> remote: python manage.py collectstatic -i docs -i tests --noinput -v 3
>> remote: Copying '/app/accounts/static/...js'
>> remote: Copying '/app/accounts/static/js'
>> remote: Copying '/app/accounts/static/js'
>> ... [ Thousands of lines... ]
>> remote: Found another file with the destination path
>> 'app/controllers/...js'. It will be ignored since only the first
>> encountered file is collected. If this is not what you want, make sure
>> every static file has a unique path.
>> remote: Found another file with the destination path
>> 'app/controllers/js'. It will be ignored since only the first
>> encountered file is collected. If this is not what you want, make sure
>> every static file has a unique path.
>> remote: Traceback (most recent call last):
>> remote: output = self.handle(*args, **options)
>> remote: File
>> "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
>>
>> line 176, in handle
>> remote: collected = self.collect()
>> remote: File
>> "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
>>
>> line 114, in collect
>> remote: level=1,
>> remote: File
>> "/app/.heroku/python/lib/python2.7/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py",
>>
>> line 201, in log
>> remote: self.stdout.write(msg)
>> remote: File
>> "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/base.py",
>>
>> line 111, in write
>> remote: self._out.write(force_str(style_func(msg)))
>> remote: IOError: [Errno 11] Resource temporarily unavailable
>>
>>
>> I do have a lot of static file... Unsure that matter.
>>
>> An other things is that it doesn't seem to fail at the same point in the
>> collectstatic command every time I run it. So look like it's failing on
>> different file every time I run it...
>>
>>
>> I did find this: https://github.com/etianen/django-require/issues/20
>> But I actually don't use django-require... (It's not in my
>> requirement.txt of what I install on Heroku)
>>
>>
>> I also see it fail (sometime but much less often as the "Resource
>> temporarily unavaible" error this way:
>> remote: Found another file with the destination path 'accounts/..html'.
>> It will be ignored since only the first encountered file is collected. If
>> this is not what you want, make sure every static file has a unique path.
>> remote: Found another file with the destination path 'accounts/...js'. It
>> will be ignored since only the first encountered file is collected. If this
>> is not what you want, make sure every static file has a unique path.
>> remote: Traceback (most recent call last):
>> remote: File "manage.py", line 10, in
>> remote: execute_from_command_line(sys.argv)
>&g
