- Aur-general - lists.archlinux.org

Fwd: [PRQ#43592] Deletion Request for vte-git
by Pellegrino Prevete 05 Jul '23

05 Jul '23

Now there is a troll on `vte-git` marking the package as duplicate despite being the most correct one. Reporter says the package is used to bother the original maintainer, when the opposite happened from the beginning. This request also comes from an anonymous account. I think what is happening is more than shameful. Not good, not good at all. I don't want years of peaceful contributions and reputation building ruined by an anonymous troll who uses aur technical shortcomings (difficulty in comparing time of events across packages) to attack others and then acts as the victim. ---------- Forwarded message --------- Da: <notify(a)aur.archlinux.org> Date: mar 4 lug 2023 alle ore 23:53 Subject: [PRQ#43592] Deletion Request for vte-git To: <aur-requests(a)lists.archlinux.org> Cc: <pellegrinoprevete(a)gmail.com>, <masonspeck1(a)gmail.com> msnspk [1] filed a deletion request for vte-git [2]: Duplicates the vte3-git and vte4-git packages already found in the AUR. Maintainer seems to be using these packages to harass other maintainers [1] https://aur.archlinux.org/account/msnspk/ [2] https://aur.archlinux.org/pkgbase/vte-git/

2 1

Fwd: [PRQ#41328] Orphan Request for sushi-git Accepted
by Pellegrino Prevete 04 Jul '23

04 Jul '23

This statement is false; the package has been orphaned one day after I updated it. Gromit is the same person who rejected request to merge conflicting vte3-git and vte4-git into non-conflicting vte-git metapackage the other day. ---------- Forwarded message --------- Da: <notify(a)aur.archlinux.org> Date: lun 19 giu 2023 alle ore 13:30 Subject: [PRQ#41328] Orphan Request for sushi-git Accepted To: <aur-requests(a)lists.archlinux.org> Cc: <pellegrinoprevete(a)gmail.com>, <aur(a)mentalfossa.com> Request #41328 has been Accepted by gromit [1]: Maintainer did not fix dependency issues in over a month, even when being repeatedly asked to do so. [1] https://aur.archlinux.org/account/gromit/

2 2

vte-git, vte-common and toxic trolls
by Pellegrino Prevete 04 Jul '23

04 Jul '23

Hello, upstream ('extra' repo), at some point the vte3 package has been split into vte-common, vte3 and vte4. vte3 and vte4 do not conflict and they both depend on vte-common. On the aur, the vte3-git package was recently orphaned and was adopted by that absurd guy I had the misfortune to interact with a couple months ago already. You know, the one who has kept its obscene insults towards me online in that package comments without any shame. So, this person hoards both vte3-git and vte4-git and keeps them conflicting. Now a couple days ago even a trusted user intervened erroneously; I assume he didn't pay much attention to dates or changes upstream. What's happening bothers me to the point I think I'd like to ask two of you to act as trustees for a TU election round. I maintain around 700 packages and I will maintain way more very soon.

2 1

Re: pkgbuild
by Robin Candau 04 Jul '23

04 Jul '23

Le 03/07/2023 à 22:20, james smith a écrit : > one last question before adding it to the aur 1) can I have multiple > emails for the maintainer so that I have a backup incase one email > goes down 2) if the package goes to the main repos will I be the > maintainer or will the person who brought it to the main repos be the > maintainer 1) I'm not sure what you mean by "goes down". The email you filled in is a gmail address, I doubt it will often (if not "ever") go down :p If you meant that as if you ever decide to take that email down for any reason, then you can just update your email address in the PKGBUILD. Anyway, you /could/ have multiple emails in the PKGBUILD but the idea here is mostly to have a way to contact you directly if you're not responding to comments on the package's AUR webpage. One email address is fine :) 2) AUR packages are contributions made to the Arch Linux project and does not "belong" to the person who submitted or maintain them. In that sense, if an AUR package is moved to the main repos, the Arch package maintainer who did it becomes the new maintainer but you'll be listed as a "contributor" in the PKGBUILD. However, this cannot happen with that particular package because VCS/git packages are not allowed on the main repos, so "lemoa*-git*" won't ever go to the main repos. > > On Mon, Jul 3, 2023 at 7:12 AM Robin Candau <antiz(a)archlinux.org> wrote: > > Le 03/07/2023 à 07:00, james smith a écrit : >> Now after making those changes running it, it doesn't correctly >> git clone Neither source directory 'source' nor build directory >> 'build' contain a build file meson.build. and I believe this >> command is the culprit |printf "%s.r%s.%s" "$(git describe --tags >> --abbrev=0 | sed 's/^v//')" "$(git rev-list --count HEAD)" "$(git >> rev-parse --short HEAD)"| because it git clones it "empty" as >> just the .git folder. Not all files https://bpa.st/XA5JI >> apologies for the redundant questions > The culprit is that you copied the "meson setup" command from the > wiki without actually adapting it to your case. The "source" and > "build" statements in it have to be replaced by the actual > "source" and "build" directory of the repo you're trying to build > (notice how "source" and "build" are written in /italic/ in the > wiki [1], indicating that they have to be adapted to your case). > Also, you have to `cd` first to the cloned repo before launching > build instructions. > > Finally, "libadwaita" should be an actual dependency (not simply a > make one) I think. > > Here's a fixed PKGBUILD: > https://bpa.st/BTXWE > > I allowed myself to also make some small "best practices" and > "style" improvements to it as well: re-add the trailing ".git" at > the end of the source, switch to sha256 instead of md5 (I know the > checksum is skipped there, but better take the habit to use a > stronger algorithm for the potential future), better indentation > in functions, etc... > > [1] > https://wiki.archlinux.org/title/Meson_package_guidelines#Using_meson_binar… > > -- > Regards, > Robin Candau / Antiz > -- Regards, Robin Candau / Antiz

1 0

PKGBUILD for pissircd-git
by Ross Burton 03 Jul '23

03 Jul '23

Hey and hello, new here, and am wondering how to submit a patch to a file... specifically the PKGBUILD for the package pissircd-git -- I've been copying my own PKGBUILD file over during the generation of a package build to avoid having it try to create a socket file in my home directory. Been doing this for a long time, and am wondering how to make it more permanent. I've included the patch, but again, I'm new and don't know where to send it. It's very simple (adding one line to the configuration) and I'm putting the file in /run/pissircd/ircd.sock, which unrealircdctl communicates to correctly. Anyway, again, I'm new to this. Help would be appreciated Thanks, -- Ross (headrift) Burton

2 1

Re: pkgbuild
by Robin Candau 03 Jul '23

03 Jul '23

Le 03/07/2023 à 07:00, james smith a écrit : > Now after making those changes running it, it doesn't correctly git > clone Neither source directory 'source' nor build directory 'build' > contain a build file meson.build. and I believe this command is the > culprit |printf "%s.r%s.%s" "$(git describe --tags --abbrev=0 | sed > 's/^v//')" "$(git rev-list --count HEAD)" "$(git rev-parse --short > HEAD)"| because it git clones it "empty" as just the .git folder. Not > all files https://bpa.st/XA5JI apologies for the redundant questions The culprit is that you copied the "meson setup" command from the wiki without actually adapting it to your case. The "source" and "build" statements in it have to be replaced by the actual "source" and "build" directory of the repo you're trying to build (notice how "source" and "build" are written in /italic/ in the wiki [1], indicating that they have to be adapted to your case). Also, you have to `cd` first to the cloned repo before launching build instructions. Finally, "libadwaita" should be an actual dependency (not simply a make one) I think. Here's a fixed PKGBUILD: https://bpa.st/BTXWE I allowed myself to also make some small "best practices" and "style" improvements to it as well: re-add the trailing ".git" at the end of the source, switch to sha256 instead of md5 (I know the checksum is skipped there, but better take the habit to use a stronger algorithm for the potential future), better indentation in functions, etc... [1] https://wiki.archlinux.org/title/Meson_package_guidelines#Using_meson_binar… -- Regards, Robin Candau / Antiz

1 0

Re: pkgbuild
by Robin Candau 02 Jul '23

02 Jul '23

/Transferring OP's reply to the proper mailing list/. > On Sun, Jul 2, 2023 at 6:59 PM Robin Candau <antiz(a)archlinux.org> wrote: > > Le 02/07/2023 à 04:20, james smith a écrit : >> I am trying to package this https://github.com/lemmygtk/lemoa >> this is my pkgbuild any tips on how to improve it before I send >> it to aur is appreciated > > Hi James, > > _/Quick note before reviewing your PKGBUILD:/_ > /When asking for a review, try to make your PKGBUILD publicly > readable somewhere (by posting it in paste service for instance, > like https://bpa.st/ or https://gist.github.com/) This is way > easier to track as the discussion progresses and way more "trust > worthy" than an attached file sent to a mailing list. > //For everyone's context, here's the initial PKGBUILD provided for > a review:/ > https://bpa.st/TXEW2 > > In it's current state, your PKGBUILD won't work and needs some > modifications and improvements. > Here's what I can list after a quick review: > > - The comments at the top provided by the PKGBUILD example file > should be removed. > > - You can remove variables/arrays that are empty/unused in your > PKGBUILD (epoch, groups, checkdepends, etc...). > > - Consider filling out the maintainer info at the top of the > PKGBUILD. This isn't mandatory but it is recommended and appreciated. > > - The pkgname you chose refers to a VCS package ("lemoa*-git*"). > If you indeed want your package to be a VCS package (meaning that > it relies on the latest upstream commit instead of a specific > tag/release) then you have to adapt your PKGBUILD accordingly with > a proper "pkgver()" function [1]. > Otherwise, switch your "pkgname" to "lemoa" and update the rest of > the PKGBUILD accordingly. > > - 'GNU' isn't a valid license. The correct license for "lemoa" > currently is 'GPL3' [2]. See also the license section of the > PKGBUILD wiki page for more information [3]. > > - The 'Gtk' package listed in the "depends" array isn't a valid > package. "Lemoa" seems to depends on GTK-4 [4] which can be > installed via the "gtk4" package in Arch [5]. > > - Upstream documentation also lists "rust, cargo and pkg-config" > as "Build dependencies" [4]. According to that, you should add the > "cargo" package (which also provides "rust") to your "makedepends" > array. > However, you don't have to explicitly list the "pkg-config" > package (provided by the "pkgconf" package in Arch [6]) because it > is a member of the "base-devel" meta-package [7] which is assumed > installed during build-time [8]. > > - The "install" variable expects the name of an optional > ".install" script used to perform tasks before or after the > install, the upgrade and/or the removal of the package [9], it > isn't meant to store a "raw" command like you did. At first > glance, there's no need for an install script in your case so you > can remove that variable. > > - The "source" array is wrong and will fail to download the repo. > It should be "git*+*$url" instead of "git*=*$url". See the VCS > sources section of the wiki for more information [10]. Just for > the sake of it, I'll add the usual trailing ".git" at the end, > like so: source=("git+${url}.git") > > - Because the sources are not static in a VCS package, you have > to explicitly skip the checksum by adding 'SKIP' to the "md5sums" > array [11]. Letting it empty will not work. > On a side note, I recommend switching to a more modern and secure > hash algorithm generally speaking ("sha256sums" for instance). > > - You shouldn't "git clone" the repo inside the "build()" > function. This is implicitly done beforehand by filling the > correct/proper sources in the "source" array. > > - The "ninja -C _build install" part as to be called within the > "package()" function. You'll also need to setup the destination > directory to "$pkgdir" which is the temporary directory where > "makepkg" builds and bundles the package [12]. See the "package()" > section of the Meson packaging guidelines for more information [13]. > > Overall, I advice you to read closely the three following Arch > wiki pages which should contain most of the information you'll > need to write a proper PKGBUILD for "lemoa-git": > - PKGBUILD [14] > - VCS Packaging Guidelines [15] > - Meson Packaging Guidelines [16] > > I hope this helps :) > Don't hesitate to ask for details or further questions if needed! > > [1] > https://wiki.archlinux.org/title/VCS_package_guidelines#The_pkgver()_functi… > [2] https://github.com/lemmygtk/lemoa/blob/main/LICENSE > [3] https://wiki.archlinux.org/title/PKGBUILD#license > [4] https://github.com/lemmygtk/lemoa#build-dependencies > [5] https://archlinux.org/packages/extra/x86_64/gtk4/ > [6] https://archlinux.org/packages/core/x86_64/pkgconf/ > [7] https://archlinux.org/packages/core/any/base-devel/ > [8] https://wiki.archlinux.org/title/PKGBUILD#makedepends > [9] https://wiki.archlinux.org/title/PKGBUILD#install > [10] > https://wiki.archlinux.org/title/VCS_package_guidelines#VCS_sources > [11] > https://wiki.archlinux.org/title/VCS_package_guidelines#Authentication_and_… > [12] > https://wiki.archlinux.org/title/Creating_packages#Defining_PKGBUILD_variab… > [13] > https://wiki.archlinux.org/title/Meson_package_guidelines#package() > [14] https://wiki.archlinux.org/title/PKGBUILD > [15] https://wiki.archlinux.org/title/VCS_package_guidelines > [16] https://wiki.archlinux.org/title/Meson_package_guidelines > > -- > Regards, > Robin Candau / Antiz > Le 02/07/2023 à 21:26, james smith a écrit : fixed some of the suggestions you had https://mystb.in/AuroraStreamAdjacent is it ok that my email is md5 hashed instead of just the email? Well, according to the fact that filling your email address at the top of the PKGBUILD isn't mandatory per say, this is better than nothing but not so "accessible". If this is a matter of protecting yourself from eventual bots or something, you could do something like "address[at]mail[dot]com" which is eventually more accessible. But the final decision is up to you, no obligation there. Regarding your PKGBUILD, there are still some modifications to make as far as I can see: - The maintainer information has to be contained inside a comment, otherwise your PKGBUILD won't work: # Maintainer: Your Name <Your email address> - The "pkgver()" function does not replace the "pkgver" variable, it just updates it automatically each time makepkg is ran against the PKGBUILD (according to the latest upstream commit). You should put back the "pkgver" variable where it was and put the "pkgver()" function before the "build()" function. Once done, building the package against the PKGBUILD will automatically update the "pkgver" value. - Generally speaking, you should list every first level dependencies even if some are already implicitly satisfied by another package. However, some exceptions can be done when you're absolutely sure that a package cannot ever stop pulling another one as a dependency. According to that, you don't necessarily have to explicitly list "rust" as a dependency as it is already pulled by "cargo" and we're sure that "cargo" won't ever stop pulling "rust" as a dependency since "cargo" is the "rust package manager". See the "depends" section of the PKGBUILD wiki page for more information [1]. - No need to keep the empty "noextract" array. - One thing I forgot to mention in my initial reply is that your package has to "conflict" and "provide" the "lemoa" package in order to avoid issues if someone tries to install both on the same system (even though the "lemoa" package does not exists */yet/*). To do so you have to use a "provides" and "conflicts" arrays in your PKGBUILD. See the related section of the PKGBUILD arch wiki page [2] [3]. [1] https://wiki.archlinux.org/title/PKGBUILD#depends [2] https://wiki.archlinux.org/title/PKGBUILD#provides [3] https://wiki.archlinux.org/title/PKGBUILD#conflicts -- Regards, Robin Candau / Antiz

1 0

Re: pkgbuild
by Robin Candau 02 Jul '23

02 Jul '23

Also, the proper mailing list to ask for a PKGBUILD review is aur-general(a)lists.archlinux.org. I haven't noticed you used aur-dev(a)lists.archlinux.org instead when I replied the first time so I forwarded the discussion to the proper mailing list this time via this reply. Let's continue this discussion here please :) For everyone's context, here's the initial PKGBUILD provided for a review: https://bpa.st/TXEW2 -- Regards, Robin Candau / Antiz Le 02/07/2023 à 20:59, Robin Candau a écrit : > Le 02/07/2023 à 04:20, james smith a écrit : >> I am trying to package this https://github.com/lemmygtk/lemoa this is >> my pkgbuild any tips on how to improve it before I send it to aur is >> appreciated > > Hi James, > > _/Quick note before reviewing your PKGBUILD:/_ > /When asking for a review, try to make your PKGBUILD publicly readable > somewhere (by posting it in paste service for instance, like > https://bpa.st/ or https://gist.github.com/) This is way easier to > track as the discussion progresses and way more "trust worthy" than an > attached file sent to a mailing list. / > > In it's current state, your PKGBUILD won't work and needs some > modifications and improvements. > Here's what I can list after a quick review: > > - The comments at the top provided by the PKGBUILD example file should > be removed. > > - You can remove variables/arrays that are empty/unused in your > PKGBUILD (epoch, groups, checkdepends, etc...). > > - Consider filling out the maintainer info at the top of the PKGBUILD. > This isn't mandatory but it is recommended and appreciated. > > - The pkgname you chose refers to a VCS package ("lemoa*-git*"). If > you indeed want your package to be a VCS package (meaning that it > relies on the latest upstream commit instead of a specific > tag/release) then you have to adapt your PKGBUILD accordingly with a > proper "pkgver()" function [1]. > Otherwise, switch your "pkgname" to "lemoa" and update the rest of the > PKGBUILD accordingly. > > - 'GNU' isn't a valid license. The correct license for "lemoa" > currently is 'GPL3' [2]. See also the license section of the PKGBUILD > wiki page for more information [3]. > > - The 'Gtk' package listed in the "depends" array isn't a valid > package. "Lemoa" seems to depends on GTK-4 [4] which can be installed > via the "gtk4" package in Arch [5]. > > - Upstream documentation also lists "rust, cargo and pkg-config" as > "Build dependencies" [4]. According to that, you should add the > "cargo" package (which also provides "rust") to your "makedepends" array. > However, you don't have to explicitly list the "pkg-config" package > (provided by the "pkgconf" package in Arch [6]) because it is a member > of the "base-devel" meta-package [7] which is assumed installed during > build-time [8]. > > - The "install" variable expects the name of an optional ".install" > script used to perform tasks before or after the install, the upgrade > and/or the removal of the package [9], it isn't meant to store a "raw" > command like you did. At first glance, there's no need for an install > script in your case so you can remove that variable. > > - The "source" array is wrong and will fail to download the repo. It > should be "git*+*$url" instead of "git*=*$url". See the VCS sources > section of the wiki for more information [10]. Just for the sake of > it, I'll add the usual trailing ".git" at the end, like so: > source=("git+${url}.git") > > - Because the sources are not static in a VCS package, you have to > explicitly skip the checksum by adding 'SKIP' to the "md5sums" array > [11]. Letting it empty will not work. > On a side note, I recommend switching to a more modern and secure hash > algorithm generally speaking ("sha256sums" for instance). > > - You shouldn't "git clone" the repo inside the "build()" function. > This is implicitly done beforehand by filling the correct/proper > sources in the "source" array. > > - The "ninja -C _build install" part as to be called within the > "package()" function. You'll also need to setup the destination > directory to "$pkgdir" which is the temporary directory where > "makepkg" builds and bundles the package [12]. See the "package()" > section of the Meson packaging guidelines for more information [13]. > > Overall, I advice you to read closely the three following Arch wiki > pages which should contain most of the information you'll need to > write a proper PKGBUILD for "lemoa-git": > - PKGBUILD [14] > - VCS Packaging Guidelines [15] > - Meson Packaging Guidelines [16] > > I hope this helps :) > Don't hesitate to ask for details or further questions if needed! > > [1] > https://wiki.archlinux.org/title/VCS_package_guidelines#The_pkgver()_functi… > [2] https://github.com/lemmygtk/lemoa/blob/main/LICENSE > [3] https://wiki.archlinux.org/title/PKGBUILD#license > [4] https://github.com/lemmygtk/lemoa#build-dependencies > [5] https://archlinux.org/packages/extra/x86_64/gtk4/ > [6] https://archlinux.org/packages/core/x86_64/pkgconf/ > [7] https://archlinux.org/packages/core/any/base-devel/ > [8] https://wiki.archlinux.org/title/PKGBUILD#makedepends > [9] https://wiki.archlinux.org/title/PKGBUILD#install > [10] https://wiki.archlinux.org/title/VCS_package_guidelines#VCS_sources > [11] > https://wiki.archlinux.org/title/VCS_package_guidelines#Authentication_and_… > [12] > https://wiki.archlinux.org/title/Creating_packages#Defining_PKGBUILD_variab… > [13] https://wiki.archlinux.org/title/Meson_package_guidelines#package() > [14] https://wiki.archlinux.org/title/PKGBUILD > [15] https://wiki.archlinux.org/title/VCS_package_guidelines > [16] https://wiki.archlinux.org/title/Meson_package_guidelines > > -- > Regards, > Robin Candau / Antiz

1 0

Rename AUR package
by Aditya Mahajan 29 Jun '23

29 Jun '23

Hi, I am the maintainer of the AUR package [luametatex](https://aur.archlinux.org/packages/luametatex) which provides the luametatex binary + the context macro package. Recently, a new package named [luametatex](https://archlinux.org/packages/extra/x86_64/luametatex/) was added to extra, which provides the luametatex binary. I realize now that the name of my AUR package is not appropriate and I should have used a more elaborate name (either context-luametatex or context-lmtx). Is it possible to rename the package? Or should I delete the current package and simply create a new one with a more elaborate name? Thanks, Aditya

3 3

llvm 16.x
by Mohan R 24 Jun '23

24 Jun '23

Hi, What happened to llvm 16.x? It was released three months ago. I tried to update the PKGBUILD locally to 16.x, this is what I got https://paste.rs/9R0Mk This issue should have been prevented if we used Source.tar.gz with a single PKGBUILD and should build different packages from this single source (like clang, lld, llvm, llvm-libs etc). Instead, we have three different PKGBUILD files (one for clang, one for lld, one for llvm+llvm-libs). why? I'm a long time arch user, when I started arch, I loved it because of how easy it was to take an official PKGBUILD file for an upstream project, bump the version and get the latest binaries in a single package, it was fairly simple. Now, lot of upstream projects was split into multiple packages (eg: qemu), I can understand the reason for the qemu package split, at least we have a single PKGBUILD to generate multiple qemu packages but this llvm split with multiple PKGBUILD is not helping us to move forward easily. It is stuck at 15.x. I think this is not supposed to be Arch's way. Thanks, Mohan R

3 4