Package Details: topgrade 9.0.1-1

Git Clone URL: (read-only, click to copy)
Package Base: topgrade
Description: Invoke the upgrade procedure of multiple package managers
Upstream URL:
Keywords: ugprade
Licenses: GPL3
Submitter: darwish
Maintainer: darwish (idanski)
Last Packager: darwish
Votes: 45
Popularity: 2.58
First Submitted: 2018-06-10 09:51 (UTC)
Last Updated: 2022-05-28 17:13 (UTC)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

Drew commented on 2022-09-08 21:47 (UTC)

All dependencies should be handled by the PKGBUILD. This is not OK:

error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.

You shouldn't have some requirement like "the user must first run command xyz before building." It needs to work on a clean installation of arch as long as all the dependencies have been installed via pacman. Otherwise you're just blocking people from automating system upgrades. Doesn't that defeat the purpose of this product?

Anyway, you should make sure this is building with the proper toolchain regardless. Something like this would be more reliable:

cargo +stable build --release

or put it in Cargo.toml

And you'll need to make sure it's available on the user's system. This works:

rustup install stable
cargo +stable build --release

That doesn't work for people who satisfy the rust dependency with something other than rustup, but frankly there's no good reason to do that. Attempting to accommodate users who set up their system incorrectly is only introducing unnecessary complexity. I would make rustup itself a dependency rather than just rust.

Moo-Crumpus commented on 2022-05-11 11:01 (UTC)

compiling error with:

error: rustc -vV didn't have a line for host:, got:

randomnerd commented on 2022-04-17 05:29 (UTC) (edited on 2022-04-18 15:31 (UTC) by randomnerd)

diff --git a/PKGBUILD b/PKGBUILD
index 7bf945b..0fac5ed 100644
@@ -1,7 +1,7 @@
 # Maintainer: Roey Darwish Dror <>

 pkgdesc='Invoke the upgrade procedure of multiple package managers'
 arch=('x86_64' 'aarch64' 'armv7')
@@ -9,7 +9,7 @@ url=''

 build() {
   cd "$pkgname-$pkgver"

haawda commented on 2022-03-24 18:27 (UTC)

Okay, it builds in a clean chroot. I guess, it is a rust vs. rustup thingy. But namcap tells me, gcc-libs is a dependency.

haawda commented on 2022-03-24 06:32 (UTC)

8.3.0 does not build:

   Compiling futures-task v0.3.21
   Compiling atty v0.2.14
   Compiling dirs-sys-next v0.1.2
   Compiling terminal_size v0.1.17
error[E0599]: no function or associated item named `as_ptr` found for type `std::sync::Arc<_>` in the current scope
  --> /home/haawda/.cargo/registry/src/
58 |     let ptr = Arc::as_ptr(wake).cast::<()>();
   |                    ^^^^^^ function or associated item not found in `std::sync::Arc<_>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
error: could not compile `futures-task`.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> FEHLER: Ein Fehler geschah in build().
    Breche ab...

focusaurus commented on 2022-03-07 14:07 (UTC)

Having rust compiler errors trying to build topgrade recently. Most are "not allowed in a const fn" flavors.

error[E0658]: `match` is not allowed in a `const fn`
    --> /home/plyons/.cargo/registry/src/
936  | /         match e {
937  | |             libc::EPERM => EPERM,
938  | |             libc::ENOENT => ENOENT,
939  | |             libc::ESRCH => ESRCH,
...    |
1070 | |             _   => UnknownErrno,
1071 | |         }
     | |_________^
     = note: see issue #49146 <> for more information

error[E0658]: `if` is not allowed in a `const fn`
  --> /home/plyons/.cargo/registry/src/
28 | / libc_bitflags! {
29 | |     pub struct AtFlags: c_int {
30 | |         AT_REMOVEDIR;
31 | |         AT_SYMLINK_FOLLOW;
...  |
39 | |     }
40 | | }
   | |_^
   = note: see issue #49146 <> for more information
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

I had to manually install a binary from github as a workaround.

Superjolly002 commented on 2021-01-18 13:54 (UTC)

How can I fix it?

==> Starting build () ...
error: no override and no default toolchain set
==> ERROR: An error occurred in build ().
     The operation is about to be stopped ...
error making: topgrade