nextcloud / nextcloud/client-building

build.bat failure at qtkeychain stage

Open
#35 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Batchfile
Stars
40
Forks
41
Avg merge
8h 2m
Merged PRs (30d)
2

Description

Hello,
I follow build installations in the README of this repo inside the recommended virtual machine.

$ BUILD_INSTALLER=0 USE_CODE_SIGNING=0 UPLOAD_BUILD=0 ./build.bat Release

build stops at : win32 build of qtkeychain
error: cannot pull with rebase: You have unstaged changes. error: please commit or stash them. "*** Build FAILED: qtkeychain Release Win32 (single-build-qtkeychain.bat)" "***** Build FAILED (build.bat)"

and indeed i have unstaged things that end up in qtkeychain directory :

`IEUser@MSEDGEWIN10 MINGW64 /c/Nextcloud/client-building/qtkeychain (master)
$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified: translations/qtkeychain_de.ts
modified: translations/qtkeychain_fr.ts
modified: translations/qtkeychain_ro.ts
modified: translations/qtkeychain_ru.ts
modified: translations/qtkeychain_zh.ts

Untracked files:
(use "git add ..." to include in what will be committed)
build/

no changes added to commit (use "git add" and/or "git commit -a")
`

These are put in place by the win64 build that happens before the win32 build

I had to use git config rebase.autostash true to work around the problem. I suggest that the script that builds the win64 clean properly behind itself before starting win32 build.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with build.bat and the qtkeychain stage referenced by single-build-qtkeychain.bat. Reproduce the command in the README and inspect the win64-to-win32 sequence, including the generated translation changes and build/ directory. Done means the win32 build starts without requiring rebase.autostash or manual cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.