Package Details: pacdiffviewer 0.3.1-2

Git Clone URL: https://aur.archlinux.org/pacdiffviewer.git (read-only, click to copy)
Package Base: pacdiffviewer
Description: Pacfiles manager
Upstream URL: https://github.com/Morganamilo/pacdiffviewer
Keywords: pacnew pacsave
Licenses: GPL3
Conflicts: yaourt
Submitter: Morganamilo
Maintainer: Morganamilo
Last Packager: Morganamilo
Votes: 4
Popularity: 0.040155
First Submitted: 2019-07-02 17:24 (UTC)
Last Updated: 2021-09-10 19:31 (UTC)

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

ArteS commented on 2024-08-07 13:24 (UTC) 

error: failed to run custom build command for `alpm v2.1.1`

Caused by:
  process didn't exit successfully: `/home/artes/.cache/yay/pacdiffviewer/src/pacdiffviewer-0.3.1/target/release/build/alpm-443e5e288f6571e0/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at /home/artes/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alpm-2.1.1/build.rs:25:13:
  this version of alpm.rs does not support libalpm v14.0.0 only v13.x.x is supported
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

Please fit it.

tronicdude commented on 2024-05-17 05:36 (UTC)

Submitted PR https://github.com/Morganamilo/pacdiffviewer/pull/3

In the meantime my fork is here https://github.com/aidan-gibson/pacdiffviewer

mib1982 commented on 2024-03-17 12:29 (UTC)

Hello,

I'm not sure if I'm the only one still using this package to deal with *.pacnew-files, but with the release of pacman 6.1, libalpm v14 has been introduced. However, the alpm.rs version 2.1.1 used by this package requires libalpm v13.x.x. Is there a possibility that this issue could be addressed to ensure compatibility with the latest version of libalpm?

sekret commented on 2021-09-10 18:47 (UTC) (edited on 2021-09-10 18:48 (UTC) by sekret)

Doesn't build right now (building in a clean chroot with makechrootpkg):


[...]
   Compiling term_size v0.3.2
error: failed to run custom build command for `alpm v2.0.3`

Caused by:
  process didn't exit successfully: `/build/pacdiffviewer/src/pacdiffviewer-0.3.0/target/release/build/alpm-15004566e303180a/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'this version of alpm.rs does not support libalpm v13.0.1 only v13.x.0 is supported', /build/.cargo/registry/src/github.com-1ecc6299db9ec823/alpm-2.0.3/build.rs:18:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /home/sekret/.chroot/sekret/build

alerque commented on 2021-06-18 13:59 (UTC) (edited on 2021-06-18 14:01 (UTC) by alerque)

From the Wiki here:

In some cases this is not necessary and may or may not be listed, for example glibc cannot be uninstalled as every system needs some C library

That wording is a big vague, but I asked about it on IRC a while back and was instructed by several TUs that I shouldn't be including it. I guess I don't' know what the answer is of if it's up to personal preference. In the spirit of not including makedepends=() for anything in the base-devel group I've been trying to avoid specifying anything in base as a depends=() unless there is some special circumstance.

Maybe I'm the one doing it wrong?

Morganamilo commented on 2021-06-18 12:55 (UTC)

Going through package review right now and got told to add the dep so just following that :P

alerque commented on 2021-06-18 12:41 (UTC)

Pardon if this is my ignorance, but I was under the impression explicitly depending on glibc in AUR packages was considered uncouth, no?

cherkaba commented on 2021-06-10 19:57 (UTC)

@caleb You're right, i'm using manjaro. thanks for your reply and the way to solve this issue.

alerque commented on 2021-06-09 11:28 (UTC)

@cherkaba Your system is out of date, you don't have a new enough version of pacman to build this. Either you haven't updated your base system recently or you are using Manjaro or some other derivative distribution that is behind. Either way the problem isn't with this package, you should sort out your issues in the appropriate forum for your distribution.

cherkaba commented on 2021-06-04 10:27 (UTC) (edited on 2021-06-04 10:29 (UTC) by cherkaba)

failling to build:

error: failed to run custom build command for alpm v2.0.3

Caused by:

process didn't exit successfully: /var/tmp/pamac-build-sagitarius/pacdiffviewer/src/pacdiffviewer-0.3.0/target/release/build/alpm-3ce6aedcd6af220e/build-script-build (exit code: 101) --- stderr

thread 'main' panicked at 'this version of alpm.rs does not support libalpm v12.0.2 only v13.x.0 is supported', /home/sagitarius/.cargo/registry/src/github.com-1ecc6299db9ec823/alpm-2.0.3/build.rs:18:9

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace warning: build failed, waiting for other jobs to finish...

error: build failed

==> ERREUR : Une erreur s’est produite dans build(). Abandon… ''

1 2 Next › Last »