Search results for "pikaur-" - lists.archlinux.org

[PRQ#58850] Deletion Request for pikaur-aurnews

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for pikaur-aurnews [2]: Please don't defy PM's decision by resubmitting an already deleted unneeded mod of AUR/pikaur which is also a disguised VCS package. Submit suggestions to the maintainer of AUR/pikaur, who is also upstream. [PRQ#49120] Deletion Request for pikaur-aurnews, submitted: 17 Oct 2023, accepted: 19 Mar 2024. https://lists.archlinux.org/archives/list/aur- requests(a)lists.archlinux.org/thread/2FUODFBMJLIHB3443HIPBLHFTUMYVX4C [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/pikaur-aurnews/

8 months, 2 weeks

[PRQ#49120] Deletion Request for pikaur-aurnews

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for pikaur-aurnews [2]: Unspecified mod/duplicate of pikaur ("with the live aurnews eggzpatch", say pkgdesc). Deliberately a VCS package in disguise (without a pkgver function), which have been asked to be rectified by @haawda in a comment on 2022-11-28, but maintainer refused. [a] At this point it's obvious that maintainer created this package only for himself and does not care about anyone else. Not useful to keep. There's already the proper AUR/pikaur and pikaur-git. If there's any improvement idea, it could be submitted to upstream, who is the same person who maintains the just-mentioned AUR pikaur builds. [a]: https://archive.ph/tOWi2#comment-891634 [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/pikaur-aurnews/

1 year, 2 months

[PRQ#59778] Deletion Request for pikaur-aurnews

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for pikaur-aurnews [2]: Disguised VCS package, 3rd resubmit after 2 deletions. [a] It is btw a one-line modded duplicate of AUR/pikaur{,-git}, [b], maintained on AUR by upstream, who in my experience is amenable to user suggestions and collaboraiton. @eggz has done this kind of thing multiple times now, see e.g. the continuously broken mate-wayland-session-git (2nd resubmit), [c] or the currently (and typically) broken ffmpeg-nocuda, duplicate of Arch/extra/ffmpeg. [d] [a]: https://lists.archlinux.org/archives/search?q=pikaur- aurnews&mlist=aur-requests%40lists.archlinux.org&sort=date-desc [b]: https://aur.archlinux.org/packages?K=pikaur [c]: https://lists.archlinux.org/archives/search?q=mate-wayland-session- git&mlist=aur-requests%40lists.archlinux.org&sort=date-desc [d]: https://lists.archlinux.org/archives/list/aur- requests(a)lists.archlinux.org/thread/NVZTMTOTO3RELF75PW5MQ4HE4PEKBRIQ [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/pikaur-aurnews/

7 months, 3 weeks

[aur-general] Strange pikaur behaviour

by Peter Nabbefeld

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

3 years, 4 months

Re: [aur-general] Strange pikaur behaviour

by Peter Nabbefeld

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.

3 years, 4 months

Re: [aur-general] Strange pikaur behaviour

by Peter Nabbefeld

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. :-(

3 years, 4 months

Re: [aur-general] Help with python-magic-wormhole PKGBUILD

by Eli Schwartz

On 12/10/18 10:42 AM, Bert Peters via aur-general wrote: > I can confirm that pikaur does not properly handle the package. The > problem appears to be that the PKGBUILD requires both the python- and > python2-versions of dependencies, but both of the splits then define > their own depends. > > Pikaur then installs only the depends for the version that I specify (I > tried python 3 first) and ignores the python 2 versions. Then when > "makepkg -s" is called, it complains that the python2 versions of the > AUR packages cannot be found. (repo packages are fine, of course) > > I don't know if this is a bug, but you can probably work around this by > moving all those dependencies to the makedepends if you need them > during the build or remove them altogether otherwise. For me, the > latter option works. The package_*() depends override globally listed depends. If pikaur does not try to install the global depends together with the makedepends before the build happens... this is a bug in pikaur and pikaur is broken. This is regardless of whether the PKGBUILD "should" use global depends. -- Eli Schwartz Bug Wrangler and Trusted User

6 years

Re: [aur-general] Strange pikaur behaviour

by Peter Nabbefeld

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

3 years, 4 months

Re: [aur-general] Strange pikaur behaviour

by Oskar Roesler

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 > > >

3 years, 4 months

[PRQ#49120] Deletion Request for pikaur-aurnews Accepted

by notify＠aur.archlinux.org

Request #49120 has been Accepted by muflone [1]: [Autogenerated] Accepted deletion for pikaur-aurnews. [1] https://aur.archlinux.org/account/muflone/

9 months

Search results for query "pikaur-"