Package Details: dive 0.10.0-1

Git Clone URL: (read-only, click to copy)
Package Base: dive
Description: A tool for exploring each layer in a docker image
Upstream URL:
Keywords: docker
Licenses: MIT
Conflicts: dive-git
Submitter: starkers
Maintainer: bulletmark
Last Packager: bulletmark
Votes: 33
Popularity: 0.54
First Submitted: 2018-10-31 22:13 (UTC)
Last Updated: 2021-04-24 21:20 (UTC)

Latest Comments

aminvakil commented on 2021-08-31 09:34 (UTC)

aude: Correct!

aude commented on 2021-08-31 08:35 (UTC)

podman-docker provides docker, not podman.

Anyway, optdepends=("docker" "podman") resolves the issue.

aminvakil commented on 2021-08-30 14:53 (UTC)

podman provides docker, so if it is installed, docker will not be installed.

But dive does not need docker at all.

aude commented on 2021-08-30 14:22 (UTC) (edited on 2021-08-30 14:28 (UTC) by aude)

This package depends on Docker, causing Docker to be installed in case you have a Podman system.

Moving from depends=("docker") to optdepends=("docker" "podman") resolves it.

dbirks commented on 2020-01-10 15:21 (UTC) (edited on 2020-01-10 15:21 (UTC) by dbirks)


flag provided but not defined: -trimpath

Could you double-check that you're on Go 1.13?

masterkorp commented on 2020-01-10 14:51 (UTC)

I cannot build this: ==> Making package: dive 0.9.1-1 (sex 10 jan 2020 14:47:42 WET) ==> Retrieving sources... -> Downloading dive-0.9.1.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 122 0 122 0 0 232 0 --:--:-- --:--:-- --:--:-- 231 100 2791k 0 2791k 0 0 1304k 0 --:--:-- 0:00:02 --:--:-- 4451k ==> Validating source files with sha256sums... dive-0.9.1.tar.gz ... Passed ==> Making package: dive 0.9.1-1 (sex 10 jan 2020 14:47:45 WET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found dive-0.9.1.tar.gz ==> Validating source files with sha256sums... dive-0.9.1.tar.gz ... Passed ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Extracting dive-0.9.1.tar.gz with bsdtar ==> Sources are ready. ==> Making package: dive 0.9.1-1 (sex 10 jan 2020 14:47:46 WET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting build()... flag provided but not defined: -trimpath usage: go build [-o output] [-i] [build flags] [packages] Run 'go help build' for details. ==> ERROR: A failure occurred in build(). Aborting... Error making: dive

JoeCool commented on 2019-09-24 13:36 (UTC) (edited on 2019-11-05 14:33 (UTC) by JoeCool)

Upstream is up-to-date now and so is this package.


Last Updated: 2019-09-07 16:45

Yes, the AUR package hasn't been updated yet.

If you build <> manually it will install correctly. There is no tagged upstream release that fixes it yet.

The Makefile and dist path was changed so you need to either make build instead of go build now or provide an output dir.

quick and dirty patch: only use if you know what you are doing

petrbel commented on 2019-09-24 12:08 (UTC)

@starkers it doesn't seem to fixed (tried right now):

go: invalid pseudo-version: revision is longer than canonical (93e082742a00)

starkers commented on 2019-09-18 15:26 (UTC)

@Thrilleratplay yes.. looks like this is fixed now

Thrilleratplay commented on 2019-09-16 12:16 (UTC)

I believe this pending PR is relevant to the error we are all getting with Go 1.13

mlamm commented on 2019-09-16 08:17 (UTC)

Same here, compiling with go 1.13.

Building via yaourt and also manually cloning the project from github failed for me with: invalid pseudo-version: does not match version-control timestamp (2019-05-26T07:48:19Z)

Afterwards, I looked for any ~/.go, ~/go directories, nuked them all, now I am getting the same error as in

starkers commented on 2019-09-12 11:34 (UTC)

Just a thought.. I'm on a fresh arch install right now.. and I had no luck replicating the issue.. so I can only assume its down to local config somehow?

dive seems to have a go.mod which is good.. ...could it be as simple as ensuring that we export GO111MODULE=on in build() ?

I'm not entirely sure if peoples local GOPATH could be used by the build but maybe just ensuring that GO111MODULE is on would help some users?

lotia commented on 2019-09-12 07:18 (UTC)

This may well be due to a transitive dependency failing to compile with go 1.13. Would be good to see if people experiencing this problem are also compiling with go 1.13.

The following github issue about golangci-lint may be of use since that was the error I was seeing when attempting to update dive. dive depends on golangci-lint which in turn depends on go-critic.

JoeCool commented on 2019-09-11 23:46 (UTC) (edited on 2019-09-11 23:47 (UTC) by JoeCool)

I am getting a different error when trying to upgrade from 0.7.2-1 ==> 0.8.1-1

==> Starting build()...
go: requires invalid pseudo-version: does not match version-control timestamp (2019-05-26T07:48:19Z)
==> ERROR: A failure occurred in build().

aroc commented on 2019-09-11 06:10 (UTC)

@dbirks Is there any information that can help you reproduce the error?

dbirks commented on 2019-09-10 18:19 (UTC)

Just an update: I'm trying to reproduce and fix the error that lots of people are getting right now.

dbirks commented on 2019-09-10 18:17 (UTC)

@aroc I'm glad it's been helpful. And as for not using the makefile, I only did that to be able to inject the version number.

aroc commented on 2019-09-10 17:40 (UTC)

@adequate Exactly the same error and situation.

johnramsden commented on 2019-09-08 22:25 (UTC)

@adequate I'm getting it as well.

adequate commented on 2019-09-06 18:44 (UTC)

I get the following error with the upgrade from dive 0.7.2-1 to 0.8.0-1:

go: invalid pseudo-version: revision is longer than canonical (93e082742a00)

Anybody facing the same error?

aroc commented on 2019-09-05 10:30 (UTC)

@dbirks Thanks for maintaining this package, is really useful having this in the AUR.

I don't understand this change: 076659685f1e, if the author of dive is using a makefile, why should this package be built different?

dbirks commented on 2019-05-03 19:40 (UTC)

@the-k Thank you for the offer. I've changed it to build from source, and added dive-git as a conflicting package.

the-k commented on 2019-05-03 16:34 (UTC)

Thanks, @starkers. @dbirks I've fixed pretty much all the problems with this package and I'm ready to push. Could you make a co-maintainer or disown the package, please?

starkers commented on 2019-05-03 10:59 (UTC)

disowning as sadly I do not have the bandwidth to maintain or automate this

the-k commented on 2019-04-25 18:18 (UTC)

@starkers It's been nearly a month since the package was flagged as out-of-date. Also, the comments below are still relevant. If you're not interested in the maintenance, please, disown the package.

fauno commented on 2019-01-04 18:42 (UTC)

you should rename this to dive-bin :)

svalo commented on 2018-12-03 13:33 (UTC)

Hi, thanks for the package. I noticed that the package does not conflict with dive-git wich provides the same binary and so issues arise when trying to switch from release to developement. May I ask to update the PKGBUILD? I'm asking the maintainer of dive-git to to the same.