repo-add command existing entry, when no entry is within the database
Hello, So yesterday I have encountered an issue when updating my Unofficial Repository (PolarRepo). Onedev is a split package, into onedev (the actual package) and onedev-new (only contains new files). (see https://aur.archlinux.org/pkgbase/onedev) They both do not conflict each other when installed, and was working on the repository for the last 5 updates, but forever what reason now, it stopped working. The following occurs when trying to add the entry: polarian in ~/polarrepo at PolarianServer … ➜ repo-add polarrepo.db.tar.gz onedev-new-8.0.5-1-x86_64.pkg.tar.zst ==> Extracting polarrepo.db.tar.gz to a temporary location... ==> Extracting polarrepo.files.tar.gz to a temporary location... ==> Adding package 'onedev-new-8.0.5-1-x86_64.pkg.tar.zst' ==> WARNING: An entry for 'onedev-8.0.5-1' already existed -> Adding package signature... -> Computing checksums... -> Removing existing entry 'onedev-8.0.5-1'... -> Creating 'desc' db entry... -> Creating 'files' db entry... ==> Creating updated database file 'polarrepo.db.tar.gz' I have already attempted to delete the entry before adding it using repo-delete, but this issue persists. If you inspect the repository database (https://polarrepo.polarian.dev/polarrepo.db.tar.gz) you will see onedev-new is not actually in the database anymore, and yet when I try to add it, it is never added... Anyone have any idea what is going on? Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On 03-03-2023 09:58, Polarian wrote:
==> Adding package 'onedev-new-8.0.5-1-x86_64.pkg.tar.zst' ==> WARNING: An entry for 'onedev-8.0.5-1' already existed
Look carefully, it's not onedev-new that already exists, but onedev. That suggests that something in onedev-new-8.0.5-1-x86_64.pkg.tar.zst is not what it should be. Check the .PKGINFO file in onedev-new package , especially the pkgbase and pkgname fields . LW
Ah, Another case of Polarian not being able to read properly, thanks for pointing that out, I will go check the .PKGINFO on both of them. Will having the same pkgbase cause issues, it should work because applications such as postgresql also are split packages with the same pkgbuild and yet can still be hosted on the official mirrors provided by Arch Linux. -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On 03-03-2023 10:13, Polarian wrote:
Will having the same pkgbase cause issues
No, they are intended to be the same for split packages. it's pkgname that needs to be unique. If looking at .PKGINFO doesn't give clues what is wrong, check the changes in the PKGBUILD since the last version that worked. LW
No, they are intended to be the same for split packages. it's pkgname that needs to be unique.
I am aware about the fact the pkgname needed to be unique but I was just double checking that there is no issues with sharing pkgbase's when using the repo-add command, elimination of possible reasons :)
If looking at .PKGINFO doesn't give clues what is wrong, check the changes in the PKGBUILD since the last version that worked.
The thing is, I was the last one to change the code, but it appears the merge of the latest version might have not worked properly, the vcs does not seem to reflect the changes. Will need to investigate before I can comment on this more. -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
Hello, So I have inspected the package a little more, and fixed the vcs issues, however I do not see any issues with the .SRCINFO, so I will let you take a look at this: pkgbase = onedev pkgver = 8.0.5 pkgrel = 1 url = https://code.onedev.io/onedev/server arch = x86_64 license = MIT license = BSD license = Apache license = LGPL2.1 license = MPL2 license = custom:Oracle Technology Network License license = custom:Microsoft Software License license = custom:Sun Microsystems Inc Binary Code License license = custom:Jetty License makedepends = gzip makedepends = tar depends = java-runtime-headless>11.0.0 depends = git>2.11.1 depends = fontconfig depends = ttf-dejavu backup = opt/onedev/conf/hibernate.properties backup = opt/onedev/conf/logback.xml backup = opt/onedev/conf/server.properties backup = opt/onedev/conf/wrapper.conf backup = opt/onedev/conf/wrapper-license.conf source = https://code.onedev.io/~downloads/projects/160/builds/3476/artifacts/onedev-... source = sysusers.conf source = onedev.service sha256sums = 716d034607f51145871cc6c60ea8a1227013d69b0746b69449e209b3dcdbccc0 sha256sums = ed8573826c9c89d7a35e3f8b52d4de69c9377fc713b5227bf30f12a45f0c2c82 sha256sums = 56c7dea1e61cf81d6dddc34fa098fa5a7ed892b1d3e506cf003b0c2c71bb5866 pkgname = onedev pkgdesc = A self-hosted Git server with CI/CD and Kanban pkgname = onedev-new pkgdesc = Latest version of onedev, installed to a different directory, used to update onedev I have checked the packages, and these settings are being reflected, so I am not sure what is going on here... -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
Nevermind I found the issue, the .SRCINFO DOES NOT reflect these, onedev-new contains pkgname of onedev, not -new, and I do not know why this is, I will attempt to rebuild the package right now to see if it was copied incorrectly. -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On 03-03-2023 10:59, Polarian wrote:
Nevermind I found the issue, the .SRCINFO DOES NOT reflect these,
onedev-new contains pkgname of onedev, not -new, and I do not know why this is, I will attempt to rebuild the package right now to see if it was copied incorrectly.
.SRCINFO is used by AUR, not by local repos . You need to look at .PKGINFO inside the build package (or pkg folder) . Rebuilding to verify what exactly is in the build package is a good idea. LW
participants (2)
-
Lone_Wolf
-
Polarian