I need your help! I'm trying to install

desktop version on my Arch system. I am getting

internal error: payload not recognized!

while building package for

-server

(which is required by pgadmin4-desktop) using

-si

command. Also, I've tried to install pgadmin4 using these 2 commands:

clone https://aur.archlinux.org/pgadmin4-py.git 

, and

pgadmin4-py/ && makepkg -si --noconfirm

, but continue to get the same error. I can't finish compiling, because this error appears and compiling process goes into a loop of these errors and I need to stop it myself by pressing

+

. I don't understand where is the problem. Would be grateful for your help.

I'm trying to hack a MSYS package, so I found https://www.msys2.org/wiki/Creating-Packages/ - as an example:

git clone "https://github.com/msys2/MSYS2-packages "
cd MSYS2-packages/flex
makepkg -sCLf

So, if I run this, I get the sources built, and I get a package. Now, let's say, I change something in the source of the flex package, and I want to rebuild. I tried the makepkg -sCLf, but that command actually deletes the source directory - including my hacks - and so, that command in particular, cannot be used to build a package with hacks/changed source files. What command could I use instead, to build (hopefully only) the changed files in the source, and to build a package from that source?

When I run makepkg -cf, I get an error: ==> ERROR: PKGBUILD does not exist. But if I run makepkg -p PKGBUILD.asc it works. Can someone explain to me someone why the first doesn't work?

I'm trying to install [hhvm-git](https://aur.archlinux.org/packages/hhvm-git/) package from AUR and getting an error. There is a bug in one of submodules. This bug is fixed already and I want to specify revision contains that fix for the submodule. How can I do that? In PKGBUILD I tried to specify revision as suggested in [Arch Wiki](https://wiki.archlinux.org/index.php/VCS_package_guidelines) (line in source array): "git+https://github.com/facebook/proxygen#7e37f926d922b55c85537057b57188dea9694c32 " Result: -> Creating working copy of proxygen git repo... remote: Counting objects: 6, done. remote: Compressing objects: 100% (6/6), done. remote: Total 6 (delta 4), reused 0 (delta 0) Unpacking objects: 100% (6/6), done. From /tmp/yaourt-tmp-german/aur-hhvm-git/proxygen 7e2a49c..3395064 master -> origin/master ==> ERROR: Unrecognized reference: 7e37f926d922b55c85537057b57188dea9694c32

Is it possible to use resources exchanged with the BitTorrent protocol in pacman's PKGBUILDs?

The latest release of Brackets (v1.13) is not available in the AUR. So I downloaded the official .deb package from the official site. Now how do I go about installing it ? Do I have to write a PKGBUILD? I won't know it's dependency and all. I have converted it to an arch package with Debtap. But pacman -U throws unresolvable dependency for the following: warning: cannot resolve "libudev>=147", a dependency of "brackets" warning: cannot resolve "lsb-base>=3.2", a dependency of "brackets" How should I go about this ?

I created a custom repository on my manjaro machine (to make a custom Manjaro ISO) with adding:

[manjaro-mate-aur-packages]
SigLevel = Never
Server = https://github.com/FreaxMATE/manjaro-mate-aur-packages/blob/main/manjaro-mate-aur-packages/x86_64/manjaro-mate-aur-packages.db.tar.gz?raw=true 

to pacman.conf. sudo pacman -Syu runs without any issues:

:: Synchronising package databases...
 core                                       172,1 KiB   637 KiB/s 00:00 [########################################] 100%
 extra                                     1903,1 KiB  1710 KiB/s 00:01 [########################################] 100%
 community                                    6,7 MiB  1883 KiB/s 00:04 [########################################] 100%
 multilib                                   177,2 KiB  1441 KiB/s 00:00 [########################################] 100%
 manjaro-mate-aur-packages                    2,5 KiB  7,11 KiB/s 00:00 [########################################] 100%

When I try to install a package from this repo I get this error:

:: Retrieving packages...
 mate-layouts-0.0.5-2-any                     2,5 KiB  21,6 KiB/s 00:00 [########################################] 100%
(1/1) checking keys in keyring                                          [########################################] 100%
(1/1) checking package integrity                                        [########################################] 100%
:: File /var/cache/pacman/pkg/mate-layouts-0.0.5-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (checksum))
Errors occurred, no packages were upgraded.

although I set SigLevel = Never. Do I have to sign the packages when creating them with buildpkg? If that is the case how do I add them to the Manjaro custom ISO? I used this doc: https://wiki.manjaro.org/index.php/Buildiso_with_AUR_packages:_Using_buildpkg and https://wiki.manjaro.org/index.php?title=Build_Manjaro_ISOs_with_buildiso

Follow this link , I build **Slack** in Arch by makepkg -sri. Unfortunately, it won't start and I decided to remove it. Issue: When I use pacman -Qm slack it returns error: package 'slack' was not found, and pacman -Rns slack surely won't work as well. How can I remove the package and its dependencies? PS which slack cmd returns /usr/bin/slack

I am using Arch. Last night I started installing a package whose repo size is ~2GB, but my internet connection is very slow, so I let it run overnight. It finished the download, but timed out at the sudo password prompt. Normally I would simply rerun it and let it do its thing, but when I tried that, the installation failed because the partition where yay's cache resides is quite full, so the package cannot be built there. That would've happened anyway, obviously, regardless of the timeout. I'm curious is it possible to move the downloaded repo to a different partition, and tell yay to continue where it left off, or, alternatively, if I can finish the build manually without breaking anything (e.g. yay's awareness of installed packages). I googled around a bit, and found the --builddir flag, so I tried simply giving it an alternate build directory on another partition. That did what I expected, but it still had to redownload everything. So I aborted it and copied the package repository (the one downloaded overnight) to that directory and ran yay again, hoping it would recognize the repository and continue where it left off. But it got confused because the branch name was the same as the directory name:

error resetting : fatal: ambiguous argument 'HEAD': both revision and filename
Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'

Finally, I tried running the installation manually by running makepkg -si in that alternative builddir, and I got the following error:

ERROR: /path/to/builddir/package is not a clone of git://
    Aborting...

I'll just delete everything and redownload it to the alternate builddir, but I'm curious what would be the best way to install the package without redownloading everything if I really had to.

IntelliJ IDEA Ultimate is not available as an Arch Linux core package, and has a built-in upgrade mechanism. For these reasons it would be convenient to install it into my home directory, letting it upgrade itself without needing to rebuild the AUR package or running anything as root. Is this possible? As far as I can tell from the PKGBUILD it refers to a pkgdir variable, but I can't find any makepkg flags to control it and export pkgdir="${HOME}/bin" doesn't seem to help.

I was building font-manager package from AUR on my Arch system. It is throwing a warning while the process :

==> WARNING: Package contains reference to $srcdir 
usr/lib/font-manager/libfontmanager.so.0.7.9

Should I worry about this warning ? Is it harmful to my system anyway ?

From Arch Wiki : > Packages in Arch Linux are built using the

utility. When makepkg is run, it searches for a

file in the current directory and follows the instructions therein to either compile or otherwise acquire the files to build a package archive (pkgname.pkg.tar.xz). The resulting package contains binary files and installation instructions, readily installable with pacman.

is a GNU utility that is used to build and install packages from source and to do so it searches for a makefile in the appropriate directory which feeds in the requiured inputs to

. So

is used to make pacman installable binaries and optionally

-si

can resolve dependencies(mainly used for AUR packages). Is the difference just in this dependency resolution and pacman specific stuff? It is just automation of stuff which could be manually done by

but on every distro. Am I correct? Sorry if this is a dumb question.

I know the latest Neofetch is available in the official arch repository but I want to build it from the git clone. Since it doesn't have the PKGBUILD so makepkg is out of question and the global step ( make install) doesn't do anything. I have read that Yaourt compiles it with makepkg. But how to do that without any AUR helper?

I have a tree which I need to install with a foder named /usr. This folder exists in src folder. Now I need to write a function in PKGBUILD that installs to the fakeroot before the *.pkg.tar.gz is built. What needs to go in > PKGBULD package() { # I need to copy the 'usr' dir in 'srcdir' to PKGBUILD's fakeroot }

In Manjaro is there any functional difference between using makepkg -s followed by then running pacman -U .tar.xz instead of just using makepkg -si ? I've seen them both used in instructions for installing programs from AUR, and I was curious if there was any significant difference between the two processes.

I'm trying to build an Arch Linux package for some icon theme, so I used this PKGBUILD file : pkgname=masalla pkgver=1.1 pkgrel=1 pkgdesc="A flat design icon theme by Hayder Majid" arch=('any') url="https://github.com/masalla-art/masalla-icon-theme " license=('GPL3') makedepends=('git') conflicts=('masalla-icon-theme-git' 'masalla-icon-theme' 'masalla') source=("${url}/releases/download/${pkgver}/${pkgname}_${pkgver}.tar.xz") md5sums=('8c11f0fd04abc6c7f9086f7275d939be') package() { cd $srcdir install -d -m 755 ${pkgdir}/usr/share/icons cp -r ${srcdir}/${pkgname}_${pkgver}/masalla ${pkgdir}/usr/share/icons cp -r ${srcdir}/${pkgname}_${pkgver}/masalla-dark ${pkgdir}/usr/share/icons } and the compiling process is work fine, but when i installing it, i got this message : (1/2) Updating icon theme caches... gtk-update-icon-cache: The generated cache was invalid. error: command failed to execute correctly (2/2) Arming ConditionNeedsUpdate... so,what i missed in my PKGBUILD file, and what should i change to fix this error

I want to install the CUPS driver for the Brother QL-1060N label printer on Arch Linux. Fortunately, there is an AUR package available. (Arch is amazing.) However, the AUR package is a bit out of date. My question is, how can I edit the PKGBUILD file to install the latest driver version? Here is the AUR package. It is for version 1.0.1r0 Here is the Brother driver download link. The current version is 1.0.5-0. Below is the PKGBUILD: # Maintainer: Karol Babioch # Inspired by package brother-dcp130c pkgname='brother-ql1060n' pkgver=1.0.1r0 pkgrel=1 pkgdesc='LPR and CUPS driver for Brother QL-1060N label printer' url='http://solutions.brother.com/linux/en_us/ ' arch=('i686' 'x86_64') license=('custom') depends='cups' if [ "$CARCH" = 'x86_64' ]; then depends+=('lib32-glibc') fi install="$pkgname.install" source=("http://download.brother.com/welcome/dlfp002231/ql1060nlpr-${pkgver/r/-}.i386.rpm " "http://download.brother.com/welcome/dlfp002233/ql1060ncupswrapper-${pkgver/r/-}.i386.rpm " 'LICENSE') sha256sums=('f2c2f919ec15b6159e13bfec60bb2d515f8c77a812e349a0ed1ec68ac29f5a25' 'bf7a1d86234d643547fc9052df55524a5e4ddbd4bf07799988c18666e7d2d3eb' 'cdd1955a9996bc246ba54e84f0a5ccbfdf6623962b668188762389aa79ef9811') prepare() { # do not install in '/usr/local' if [ -d $srcdir/usr/local/Brother ]; then install -d $srcdir/usr/share mv $srcdir/usr/local/Brother/ $srcdir/usr/share/brother rm -rf $srcdir/usr/local sed -i 's|/usr/local/Brother|/usr/share/brother|g' grep -lr '/usr/local/Brother' ./ fi # setup cups directories install -d "$srcdir/usr/share/cups/model" install -d "$srcdir/usr/lib/cups/filter" # go to the cupswrapper directory and find the source file from wich to generate a ppd- and wrapper-file cd find . -type d -name 'cupswrapper' if [ -f cupswrapper* ]; then _wrapper_source=ls cupswrapper* sed -i '/^\/etc\/init.d\/cups/d' $_wrapper_source sed -i '/^sleep/d' $_wrapper_source sed -i '/^echo lpadmin/d' $_wrapper_source sed -i '/^lpadmin/d' $_wrapper_source sed -i 's|/usr|$srcdir/usr|g' $_wrapper_source sed -i 's|/opt|$srcdir/opt|g' $_wrapper_source sed -i 's|/model/Brother|/model|g' $_wrapper_source sed -i 's|lpinfo|echo|g' $_wrapper_source export srcdir=$srcdir ./$_wrapper_source sed -i 's|$srcdir||' $srcdir/usr/lib/cups/filter/*lpdwrapper* sed -i "s|$srcdir||" $srcdir/usr/lib/cups/filter/*lpdwrapper* rm $_wrapper_source fi # /etc/printcap is managed by cups rm find $srcdir -type f -name 'setupPrintcap*' } package() { cd "$srcdir" cp -R usr $pkgdir if [ -d opt ]; then cp -R opt $pkgdir; fi install -Dm0644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE" } The .install file in the package archive include only this: post_install() { post_upgrade; } post_upgrade() { echo "Restart CUPS to load the new files" echo "You can now register your new printer using the web interface at:" echo " http://localhost:631/" } Some questions include: Why isn't rpmextract required in the PKGBUILD code? I don't understand how the install is working given that the packages are RPMs and this is Arch. Regarding the sha256sums, I assume I just manually download the rpm files and calculate those sums given that the Brother download page doesn't list them (afaik). The values I come up with are: 05d786b9a5b2cf374d5c286ae8feb77e2a79619cc5b2f6ca2695dbd549eec0a3 ql1060ncupswrapper-1.0.5-0.i386.rpm bf20a00f723d0e12cf055ae359d0e03e2c1bd839bacd52f02b3cc5a63bc652e5 ql1060nlpr-1.0.5-0.i386.rpm I assume the license file and it's sha256sum can remain unchanged. Given that, is updating the PKGBUILD as simple as replacing the sha256sums and updating this one value? pkgver=1.0.1r0 with pkgver=1.0.5-0 #UPDATE The package maintainer has updated the package already. Here is a diff: 5c5 pkgver=1.0.5r0 19,20c19,20 sha256sums=('bf20a00f723d0e12cf055ae359d0e03e2c1bd839bacd52f02b3cc5a63bc652e5' > '05d786b9a5b2cf374d5c286ae8feb77e2a79619cc5b2f6ca2695dbd549eec0a3' However, I'll leave the question up because I would like to understand how this PKGBUILD works and how an RPM package can be installed using this method.

I'm at a stage in a project where it would be really handy to have a debug version of a system package installed. On Ubuntu at least, adding the debug symbols to a library is a piece of cake. Practically every package has a -dbg variant that provides all the symbols you'd need for a useful backtrace. However, I'm currently on Arch linux, where the general concensus is to edit the user makepkg.conf file, adding whatever debug flags to (C|CXX|CPP|LD)FLAGS. Then re-build the package yourself, and replace the current, optimised version with the debug build. Well, I suppose that's fair enough with a "source-based distribution", but it gets tedious pretty quickly. So, what is / are the best practices for attaching debug symbols to a system package? How do other packagers do it? I think I've seen that strip can extract debug symbols and save them in external files. Is it possible for gdb to pick up those symbol files during backtraces, with system applications not even bothering to look for them? How does that work, from a packagers perspective? It's just an idea, but is it a good idea to create a chroot environment in which to develop? (I have a problem atm where a package has an ABI incompatibility between its debug and release builds, which is a bit of a pain. Everything linked to its shared lib also complains about missing symbols, so reverted to optimised build..)

In a [previous question](https://unix.stackexchange.com/questions/152368/create-pkgbuild-from-deb) , I asked about how to write a PKGBUILD to install a binary .deb package. The solution was to extract the contents of the .deb and copy the data to the archlinux package fakeroot, "${pkgdir}/". That means if the .deb contains a data.tar.gz with the binaries stored in a usr/lib directory, the process to install this package is (In the PKGBUILD): package() { cd $srcdir tar -xvzf data.tar.gz install -dm755 "${pkgdir}/usr/lib" cp -r -f "${srcdir}/usr/lib" "${pkgdir}/" } However if I do that the package is installed successfully, but I cannot open the binaries (Written in python). If I execute a binary installed in that way, returns this error: > Cannot open self [path to executable] or file [path to executable].pkg On the other hand, if I write the PKGBUILD in the wrong way, that is, copying the binaries directly to the system root during package(): cp -r -f "${srcdir}/usr/lib "/" The programs work perfectly. **Is there something I'm missing?** [Here](https://github.com/Manu343726/biicode-aur) is the package.

I want to use arch with sysvinit. As stated in Arch wiki , I downloaded and extracted sysvinit and initscripts-fork. I makepkg'd sysvinit with success, but afterwards initscripts-fork makepkg fails with the claim that dependency sysvinit is missing. How does makepkg check dependency existence? How can I make it see the install (or better still, do you know other practical ways to use arch with sysvinit)?