Arch Linux User Repository

If the package is outdated, please report it with the 'Flag outdated package' above.

If there is an issue regarding packaging, please report it here:

https://github.com/ItachiSan/linux_packaging/issues/

As I do not use this package (I use a Docker container for Debian packaging) please tell me whenever a dependency is missing, so that I can move it from a make dependency to a normal dependency.

FYI aur/sensible-utils has been reunified since Aug 2024. The compatibility provides will be dropped with the next release.

The flag is likely invalid as I just pushed a sensible-utils that should work with this package. See https://github.com/ItachiSan/linux_packaging/issues/14.

However, @xiota remains right that the dep is dubious.

Thanks @yrlf, had time now to work on the package.

All the suggestions are sound, I applied all of them and gave you credit as contributor :)

@yrlf, thanks, works for me. Maintainer should take your patch and bump the package version.

Hi! The latest PKGBUILD has a few issues:

1. you misspelled the conflicts variable as conflicst
2. you misspelled the package name checkbashisms as checkbashism

Additionally, I want to say that I can reproduce the issues @sa7dse, @Excalibur, and @agraef encountered. Here is a quick rundown of the cause:

• devscripts/scripts/setup.py tries to import devscripts.test from devscripts/scripts/devscripts/test/__init__.py
• python looks for devscripts
• python instead finds the installed /usr/lib/python3.10/site-packages/devscripts/__init__.py (root cause)
• python looks for devscripts.test in the found package
• python errors out because the test subpackage was not not installed with the rest (symptom)

I haven't found out why python prefers the installed version over the local one here, since usually it's the other way round; I will dig further into this.

For now, a workaround is to uninstall devscripts and reinstalling it, at least that works for me.

EDIT: I found it! devscripts/scripts/devscripts/__init__.py does not exist. python checks for the existence of a devscripts.py or a devscripts/__init__.py before looking in site-packages, but this package just doesn't have that file. This works fine if the package is not installed, but breaks if it is already installed.

All changes in a single patch:

diff --git a/PKGBUILD b/PKGBUILD
index a7f2dcc..506b64e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -37,8 +37,8 @@ optdepends=(
     'perl-ipc-run: Required for uscan'
     'perl-lwp-protocol-https: Required for uscan'
 )
-provides=(checkbashism)
-conflicst=(checkbashism)
+provides=(checkbashisms)
+conflicts=(checkbashisms)
 options=('!makeflags')
 source=(
     "https://deb.debian.org/debian/pool/main/${pkgname:0:1}/${pkgname}/${pkgname}_${pkgver}.tar.xz"
@@ -50,6 +50,9 @@ sha256sums=('54eb392b18818460e56c052e40602bc9a1ba33c5349a58017c57b1d312b3ed9a'
 prepare(){
     cd "$pkgname"
     patch -p1 -i "$srcdir/fixes.patch"
+
+    # fix local script not being found when already installed
+    touch "$srcdir/devscripts/scripts/devscripts/__init__.py"
 }

 build() {

The build also fails on all of my machines with:

python3 setup.py install --root="/home/dp/git/devscripts/pkg/devscripts" --no-compile
Traceback (most recent call last):
  File "/home/dp/git/devscripts/src/devscripts/scripts/setup.py", line 8, in <module>
    from devscripts.test import SCRIPTS
ModuleNotFoundError: No module named 'devscripts.test'

and that is with git cloning this repo and running makepkg

Hi @Excalibur,

I had a similar error reported on Github:

https://github.com/ItachiSan/linux_packaging/issues/12

I simply cannot reproduce. Building "the official way" with makepkg leads to no issue. Maybe cleaning the yay cache folder can solve the issue?

I got the following error when trying to upgrade 2.23.0-1 -> 2.23.1-2:

==> Starting package()...
make -C scripts/ install DESTDIR=/home/excalibur/.cache/yay/devscripts/pkg/devscripts
make[1]: Entering directory '/home/excalibur/.cache/yay/devscripts/src/devscripts/scripts'
cp bts.bash_completion bash_completion/bts
cp chdist.bash_completion bash_completion/chdist
cp checkbashisms.bash_completion bash_completion/checkbashisms
cp debchange.bash_completion bash_completion/debchange
cp debdiff.bash_completion bash_completion/debdiff
cp debi.bash_completion bash_completion/debi
cp debsign.bash_completion bash_completion/debsign
cp debuild.bash_completion bash_completion/debuild
cp dscextract.bash_completion bash_completion/dscextract
cp dscverify.bash_completion bash_completion/dscverify
cp list-unreleased.bash_completion bash_completion/list-unreleased
cp mk-origtargz.bash_completion bash_completion/mk-origtargz
cp pkgnames.bash_completion bash_completion/pkgnames
cp plotchangelog.bash_completion bash_completion/plotchangelog
cp salsa.bash_completion bash_completion/salsa
cp uscan.bash_completion bash_completion/uscan
cp uupdate.bash_completion bash_completion/uupdate
python3 setup.py install --root="/home/excalibur/.cache/yay/devscripts/pkg/devscripts" --no-compile
Traceback (most recent call last):
  File "/home/excalibur/.cache/yay/devscripts/src/devscripts/scripts/setup.py", line 8, in <module>
    from devscripts.test import SCRIPTS
ModuleNotFoundError: No module named 'devscripts.test'
make[1]: *** [Makefile:154: install] Error 1
make[1]: Leaving directory '/home/excalibur/.cache/yay/devscripts/src/devscripts/scripts'
make: *** [Makefile:70: install_scripts] Error 2
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: devscripts

It seems that perl-moo , perl-ipc-run and perl-lwp-protocol-https are also required for uscan.

Thanks for the tip zadkiel. I needed to add:

mkdir -p $pkgdir/usr/{bin,lib}

before the make DESTDIR="$pkgdir" install line before it would install successfully.