Gitlab Pages glitch: A file with this name already exists

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?

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.

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?

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

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

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

deployment-process.log = attached

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.

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.

publii-me wrote:

[anonymous] wrote:

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.

[anonymous] wrote:

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>