Repository navigation
Package version from the build date, so testing accepts it - #12
Merged
Merged
Conversation
Job 62182 built 1:3.0.1-1 from testing-2026-10-10-2 and uploaded it without errors, but the repository server never published it in testing (the file is 404 at the origin; chatai-plasmoid, uploaded later by the same steps, was published). Every package in both testing and stable has a date version newer than stable's; no package with an epoch is in testing while stable has an older version. The server-side step reads 1:3.0.1-1 without its epoch, finds it older than 26.06.18-0104 and drops it. biglinux-settings and earlier biglinux-welcome use date versions. - PKGBUILD: pkgver=$(date +%y.%m.%d), pkgrel=$(date +%H%M), no epoch. APP_VERSION stays 3.0.1 for About and --version. - GitLab Status: after the upload, wait for the file in repo.biglinux.com.br/<repo>/x86_64 (testing and stable) and fail if it never appears. The directory page is cached by the CDN for days, so the file itself is requested. - Docs: evidence, the unstable 1:3.0.1-1 leftover, the stale page.
Package version from the build date, so testing accepts it
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Job 62182 built
1:3.0.1-1fromtesting-2026-10-10-2and uploaded it with no error, but the repository server never published it in testing: the file is 404 at the origin. The testing step reads the version without its epoch (3.0.1-1< stable26.06.18-0104) and drops it. Details and evidence:docs/ci-packaging.md.pkgver=$(date +%y.%m.%d),pkgrel=$(date +%H%M), no epoch, the same as biglinux-settings. The application version stays 3.0.1.repo.biglinux.com.br.Tested in ruscher#5.