Arch Linux User Repository

missingSleepDeps: That looks like network issues on your side.

==> Making package: slackdump 3.1.3-1 (Sun 08 Jun 2025 03:36:10 PM PDT)
==> Retrieving sources...
  -> Downloading slackdump-3.1.3.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 1056k    0 1056k    0     0  1375k      0 --:--:-- --:--:-- --:--:-- 4834k
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with b2sums...
    slackdump-3.1.3.tar.gz ... Passed
:: (1/1) Parsing SRCINFO: slackdump
==> Making package: slackdump 3.1.3-1 (Sun 08 Jun 2025 03:36:12 PM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found slackdump-3.1.3.tar.gz
==> Validating source files with b2sums...
    slackdump-3.1.3.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting slackdump-3.1.3.tar.gz with bsdtar
==> Starting prepare()...
==> Sources are ready.
==> Making package: slackdump 3.1.3-1 (Sun 08 Jun 2025 03:36:13 PM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
go: downloading modernc.org/sqlite v1.37.1
cmd/slackdump/main.go:19:2: modernc.org/sqlite@v1.37.1: Get "https://proxy.golang.org/modernc.org/sqlite/@v/v1.37.1.zip": dial tcp: lookup proxy.golang.org on 192.168.1.1:53: no such host
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: slackdump-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
slackdump - exit status 4
PAKtC

dreieck: ping me back when discussion is over. My opinion is that if you are so worried about caches and other files ending up in your home folder, always use makechrootpkg, or extra-x86_64-build.

@iyanmv:

Can you point me in the right direction to what you are asking? I cannot find anything in the Go guidelines.

I have looked at this. I cannot find either regarding the prepare() issue, but regarding the download location, I find something for Node.js packages in the ↗ Node.js package guidelines. If it applies there, I do not see why it should not apply elsewhere.

I have started a ↗ topic about this question in the Arch Linux forum.

Hi dreieck: Now I have some time to have a look at this. Can you point me in the right direction to what you are asking? I cannot find anything in the Go guidelines.

https://wiki.archlinux.org/title/Go_package_guidelines

Thanks

dreieck: I will also take a look at your suggestion.

I know this (and many other of the packages I maintain) are out of date. I've had almost no time these couple of weeks, but I will start taking care of them this weekend.

Ahoj, thanks for the package!

Can you transform the package so that the go-specific downloads are carried out in prepare(), so that after prepare() the sources are really ready?

And can you utilise go's environment variables so that the downloads are contained within $srcdir, not cluttering $HOME?

Regards!