[aur-general] Strange pikaur behaviour
Hello, I'm currently trying to build meshroom-git. I removed the old installation to replace alembic-qfix by community/alembic, and I'm able to build meshroom-git (with some problems). 1. For installation, I use "pikaur -Sa meshroom-git". 2. pikaur tells me about missing alembic-qfix, though latest PKGBUILD does not refer to it as a dependency. 3. I can only build meshroom-git after making some change (commenting/uncommenting a print instruction). 4. When I try again, I'm again told about dependency alembic-qfix not found in AUR. Also, when building meshroom-git, two outdated dependencies are built first and removed after the build. Obviously, there's still an earlier version of PKGBUILD located somewhere which is not deleted (and I don't know where to find it, as removing ~/.local/share/pikaur/aur_repos/meshroom-git and ~/.cache/pikaur/{build,pkg}/meshroom-git does not seem to be enough). Any idea? Kind regards, Peter
Am 01.08.21 um 16:07 schrieb Peter Nabbefeld via aur-general:
Hello,
I'm currently trying to build meshroom-git. I removed the old installation to replace alembic-qfix by community/alembic, and I'm able to build meshroom-git (with some problems).
1. For installation, I use "pikaur -Sa meshroom-git". 2. pikaur tells me about missing alembic-qfix, though latest PKGBUILD does not refer to it as a dependency. 3. I can only build meshroom-git after making some change (commenting/uncommenting a print instruction). 4. When I try again, I'm again told about dependency alembic-qfix not found in AUR.
Also, when building meshroom-git, two outdated dependencies are built first and removed after the build.
Obviously, there's still an earlier version of PKGBUILD located somewhere which is not deleted (and I don't know where to find it, as removing ~/.local/share/pikaur/aur_repos/meshroom-git and ~/.cache/pikaur/{build,pkg}/meshroom-git does not seem to be enough).
Any idea?
Kind regards, Peter
I've tried to use aura, but same problems. PKGBUILD (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=meshroom-git) does not contain any dependency on alembic-qfix, so it's probably a repository/versioning problem. P.
On Sun, 1 Aug 2021 17:20:01 +0200, Peter Nabbefeld wrote:
I've tried to use aura, but same problems. PKGBUILD (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=meshroom-git) does not contain any dependency on alembic-qfix, so it's probably a repository/versioning problem.
Hi, I've taken a look at the tarball, .SRCINFO contains "depends = alembic-qfix", so I added a comment, https://aur.archlinux.org/packages/meshroom-git/#comment-819919 . Regards, Ralf
Am 01.08.21 um 17:20 schrieb Peter Nabbefeld via aur-general:
Am 01.08.21 um 16:07 schrieb Peter Nabbefeld via aur-general:
Hello,
I'm currently trying to build meshroom-git. I removed the old installation to replace alembic-qfix by community/alembic, and I'm able to build meshroom-git (with some problems).
1. For installation, I use "pikaur -Sa meshroom-git". 2. pikaur tells me about missing alembic-qfix, though latest PKGBUILD does not refer to it as a dependency. 3. I can only build meshroom-git after making some change (commenting/uncommenting a print instruction). 4. When I try again, I'm again told about dependency alembic-qfix not found in AUR.
Also, when building meshroom-git, two outdated dependencies are built first and removed after the build.
Obviously, there's still an earlier version of PKGBUILD located somewhere which is not deleted (and I don't know where to find it, as removing ~/.local/share/pikaur/aur_repos/meshroom-git and ~/.cache/pikaur/{build,pkg}/meshroom-git does not seem to be enough).
Any idea?
Kind regards, Peter
I've tried to use aura, but same problems. PKGBUILD (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=meshroom-git) does not contain any dependency on alembic-qfix, so it's probably a repository/versioning problem.
P.
PKGBUILD does not contain the dependency, but .SRCINFO does. :-(
On Sun, 1 Aug 2021 17:35:54 +0200, Peter Nabbefeld wrote:
PKGBUILD does not contain the dependency, but .SRCINFO does. :-(
Hi, that's no big deal. ".SRCINFO files contain package metadata in a simple, unambiguous format, so that tools such as the AUR's Web back-end or AUR helpers may retrieve a package's metadata without parsing the PKGBUILD directly." https://wiki.archlinux.org/title/.SRCINFO On Sat, 31 Jul 2021 12:39:59 +0200, Ralf Mardorf wrote:
the very first thing to do by yourself [...] is trying to build without an AUR helper. https://lists.archlinux.org/pipermail/arch-general/2021-July/049129.html
Don't replace one AUR helper by another, if an AUR helper fails. You can build it using "makepkg". Regards, Ralf
Am 01.08.21 um 17:26 schrieb Ralf Mardorf via aur-general:
On Sun, 1 Aug 2021 17:20:01 +0200, Peter Nabbefeld wrote:
I've tried to use aura, but same problems. PKGBUILD (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=meshroom-git) does not contain any dependency on alembic-qfix, so it's probably a repository/versioning problem. Hi,
I've taken a look at the tarball, .SRCINFO contains "depends = alembic-qfix", so I added a comment, https://aur.archlinux.org/packages/meshroom-git/#comment-819919 .
Regards, Ralf Thank You for taking care of the problem! :)
Kind regards, P.
Am 01.08.21 um 17:47 schrieb Ralf Mardorf via aur-general:
On Sun, 1 Aug 2021 17:35:54 +0200, Peter Nabbefeld wrote:
PKGBUILD does not contain the dependency, but .SRCINFO does. :-( Hi,
that's no big deal.
".SRCINFO files contain package metadata in a simple, unambiguous format, so that tools such as the AUR's Web back-end or AUR helpers may retrieve a package's metadata without parsing the PKGBUILD directly." https://wiki.archlinux.org/title/.SRCINFO It's only been the first time for me I noticed a conflict between PKGBUILD and .SRCINFO - next time I will look into both files, when I notice such suspicious behaviour. ;-) On Sat, 31 Jul 2021 12:39:59 +0200, Ralf Mardorf wrote:
the very first thing to do by yourself [...] is trying to build without an AUR helper. https://lists.archlinux.org/pipermail/arch-general/2021-July/049129.html
Don't replace one AUR helper by another, if an AUR helper fails. You can build it using "makepkg". I thought, pikaur fails because of a problem with some caching; then it makes sense to check by using some other AUR helper, and aura failing finally led me to the correct point, too - but it was the last one I checked, and it took me quite some time.
BTW, I've now installed meshroom-git using the following command: pikaur -Sa --assume-installed alembic-qfix meshroom-git After building, this results in the following strange pacman command for installation: 'sudo pacman --color=always --assume-installed alembic-qfix --upgrade --assume_installed /home/peter/.cache/pikaur/pkg/meshroom-git-2021.1.0.r134.gf1331c6a-1-x86_64.pkg.tar.zst' That causes pacman to abort, but I could continue installing after removing "--assume-installed", i.e. using: sudo pacman --color=always --upgrade /home/peter/.cache/pikaur/pkg/meshroom-git-2021.1.0.r134.gf1331c6a-1-x86_64.pkg.tar.zst However, that should probably be fixed ... Regards, Peter
Regards, Ralf
Shouldn't the AURweb git hooks deny commits where only the PKGBUILD but not the .SRCINFO got updated? Am Sonntag, 1. August 2021 18:24:53 CEST schrieb Peter Nabbefeld via aur-general:
Am 01.08.21 um 17:47 schrieb Ralf Mardorf via aur-general:
On Sun, 1 Aug 2021 17:35:54 +0200, Peter Nabbefeld wrote: ... It's only been the first time for me I noticed a conflict between PKGBUILD and .SRCINFO - next time I will look into both files, when I notice such suspicious behaviour. ;-) On Sat, 31 Jul 2021 12:39:59 +0200, Ralf Mardorf wrote:
the very first thing to do by yourself [...] is trying to build without an AUR helper. https://lists.archlinux.org/pipermail/arch-general/2021-July/049129.html
Don't replace one AUR helper by another, if an AUR helper fails. You can build it using "makepkg". I thought, pikaur fails because of a problem with some caching; then it makes sense to check by using some other AUR helper, and aura failing finally led me to the correct point, too - but it was the last one I checked, and it took me quite some time.
BTW, I've now installed meshroom-git using the following command: pikaur -Sa --assume-installed alembic-qfix meshroom-git
After building, this results in the following strange pacman command for installation: 'sudo pacman --color=always --assume-installed alembic-qfix --upgrade --assume_installed /home/peter/.cache/pikaur/pkg/meshroom-git-2021.1.0.r134.gf1331c6a-1-x86_64.pkg.tar.zst'
That causes pacman to abort, but I could continue installing after removing "--assume-installed", i.e. using: sudo pacman --color=always --upgrade /home/peter/.cache/pikaur/pkg/meshroom-git-2021.1.0.r134.gf1331c6a-1-x86_64.pkg.tar.zst
However, that should probably be fixed ...
Regards, Peter
Regards, Ralf
On 02/08/2021 17.56, Oskar Roesler via aur-general wrote:
Shouldn't the AURweb git hooks deny commits where only the PKGBUILD but not the .SRCINFO got updated?
It produces a warning, but accepts the commit (because not all PKGBUILD changes result in a .SRCINFO change). It can be debated whether any PKGBUILD change should also coincide with at least a pkgrel (and thus .SRCINFO) change, but that's currently not implemented at all.
participants (4)
-
Oskar Roesler
-
Peter Nabbefeld
-
Ralf Mardorf
-
Xiretza