Le 04/07/2023 à 03:30, Pellegrino Prevete a écrit :
Hello,
Hi,
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 wa
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 t
To the aur general list,
to confirm Pellegrino Prevete's statements, I built the sushi-git
PKGBUILD as of commit 6ec6fd1ff4f873c6e3a16d5cb90c5d01448b032b. This
was Prevete's last commit before losing control, and it happened June
18, two months after Prevete was notified of the dependency issue by
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:
Date: lun 19 giu 2023 all
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 interac
Hey Ross!
> 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 dir
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
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 --
