Sign in

Gitlab Pages glitch: A file with this name already exists

Viewing 19 posts - 1 through 19 (of 19 total)
  • Author
    Posts
  • #2066
    j2l2

    Everything was working fine with Publii on gitlab until today’s website update:

    “A file with this name already exists”

    The server is responding OK to tests. See my screenshots.

    I even deleted all files except one in the file manager, no luck.

    Any ideas?

    Attachments:
    #2071
    j2l2

    OK, I deleted everything (except .gitlab-ci.yml and README.md) with Gitlab Web IDE and synced again and it went through.

    This is radical!

    There might be another way. Any ideas?

    #2074
    Tomasz DziudaTomasz Dziuda
    Moderator

    Hi,

    Do you have the same problem while you are trying to sync your website again?

    --
    Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

    #2077
    j2l2

    Hi Tomasz,

    Aargh, yeah, it happened again. You’re right to ask to test again.

    I think there’s something wrong when merging publii branch with master, I don’t see CI errors though. It didn’t happen before, maybe gitlab changed something recently about merging existing files?

    Please, please, can you test on your side and debug it? I’m not gitlab fluent enough.

    #2079
    Tomasz DziudaTomasz Dziuda
    Moderator

    Please check Tools -> Log viewer and check if there are some useful informations about the issue – especially I mean connection-*.log files.

    --
    Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

    #2095
    j2l2

    I don’t see “Tools -> Log viewer”

    Operations > Logs is empty

    In CI/CD jobs`, all jobs are passed`

    No issues

    Last task is:

    Merge branch ‘publii-deploy-1584327528716’ into ‘master’

    it claims pipeline passed, deployed (and request pages states it was merged)

    but there are lots of active branches beside master. Especially the last commit is still an active branch.

    I tried to delete all merged branches, including the successful one of yesterday. All branches but master are gone.

     

     

    I made a tiny change and tried again to sync from Publii. It failed again.

    It REOPENS the last branch merge operation from 22h ago!

    I confirm it was deleted and the merge request reappeared again.

    Like if Publii was pushing again the same commit.

     

    Since I don’t really care to delete gitlab content anymore, I tried deleting publii-files.json only. It didn’t help.

    I deleted /media and synced again. It didn’t help.

    I deleted each folder and files and synced again. It didn’t help.

    Until I deleted /public

    So, even one file in /public is enough to break Publii sync.

     

     

    Can you test on your side, please?

    #2113
    mrjk05

    I can confirm Iā€™m having the exact same problem.

    the sync between publii and gitlab fails if the public folder exists.

    I have to continually delete the public folder for it to work.

    #2238
    publii-me

    Also having the same problem here. Must delete the public folder to be able to sync.

    #2239
    j2l2

    I didn’t find any other way but delete /public
    Publii, please, please, fix it and let us know šŸ™‚

    #2240
    BobBob
    Support

    I think it has been infected with a coronavirus and is not working now. šŸ™‚

    --
    Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

    #2241
    yanlinnthor

    I have set up my first Publii and Gitlab pages website today and got the same error. Hope we have a solution soon.

    #2243
    yanlinnthor

    After reading the messages in this thread, I found where the publii logs are stored. Here are my logs for reference.

    connection-files-log-to-delete.txt = []

    connection-files-log-to-upload.txt = attached

    screenshot_32

    deployment-errors.log = This log file is empty…

    deployment-process.log = attached

    screenshot_33

    The rest are probably not necessary for debugging. I will share if anyone wanted to see though.

    I am using v.0.35.3 (build 12104) Beta on Linux Mint.

    #2250
    westsonoma

    Same on win 7

    v.0.36.0 (build 13098) Prerelease 5

    #2329
    notedbynoel

    New here but I think it has something to do with the master branch in gitlab being protected. I tried changing the branch on which Publii commits (and which the gitlab-ci.yml checks) and seems to have resolved it for me.

    #2330
    publii-me

    New here but I think it has something to do with the master branch in gitlab being protected. I tried changing the branch on which Publii commits (and which the gitlab-ci.yml checks) and seems to have resolved it for me.

    I just tried pushing to a branch other than master and unfortunately I still get the same error. I also tried unprotecting the master branch, which did not affect the result.



    @notedbynoel
    can you retry pushing to that alternative branch again?

    #2331
    notedbynoel

    New here but I think it has something to do with the master branch in gitlab being protected. I tried changing the branch on which Publii commits (and which the gitlab-ci.yml checks) and seems to have resolved it for me.

    I just tried pushing to a branch other than master and unfortunately I still get the same error. I also tried unprotecting the master branch, which did not affect the result.

    @notedbynoel can you retry pushing to that alternative branch again?

    Works with me.

     

    Attachments:
    #2333
    notedbynoel

    I think i spoke too soon. after few more tries to sync. No longer working aswell. getting the same error in this thread. sorry

    #2334
    notedbynoel

    I think i spoke too soon. after few more tries to sync. No longer working aswell. getting the same error in this thread. sorry

    So far, a workaround that consistently works with me is that i need to delete the public directory as well as the <span class=”position-relative”>publii-files</span><span class=”position-relative”>.</span><span class=”position-relative”>json file manually then sync the site again.</span>

    #2410
    Tomasz DziudaTomasz Dziuda
    Moderator

    Hi,

    This issue will be fixed in the next Publii release – after deeper analyze I have found a reason of the issue – path to the publii-files.json started with ‘/’ and it seems that Gitlab changed their API and now does not allow such paths :/

    --
    Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

Viewing 19 posts - 1 through 19 (of 19 total)
  • You must be logged in to reply to this topic.