Since upgrading to 7.3, I get "The requested URL returned error: 404 Not Found" warning popup. Though the download/update's do complete successfully, I think it might be a false flag. It doesn't seem to be reproducible in previous versions or using a terminal.
Search Criteria
Package Details: pamac-aur 11.7.2-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/pamac-aur.git (read-only, click to copy) |
---|---|
Package Base: | pamac-aur |
Description: | A Gtk frontend, Package Manager based on libalpm with AUR and Appstream support |
Upstream URL: | https://github.com/manjaro/pamac |
Keywords: | gui installer libalpm package pacman yay |
Licenses: | GPL-3.0-or-later |
Conflicts: | pamac, pamac-cli, pamac-tray-appindicator |
Provides: | pamac, pamac-cli |
Submitter: | Zeph |
Maintainer: | Zeph |
Last Packager: | Zeph |
Votes: | 403 |
Popularity: | 3.31 |
First Submitted: | 2013-12-05 12:57 (UTC) |
Last Updated: | 2024-11-28 12:33 (UTC) |
Dependencies (20)
- desktop-file-utils (desktop-file-utils-gitAUR)
- git (git-gitAUR, git-glAUR)
- gnutls (gnutls-gitAUR)
- gtk4 (gtk4-customizableAUR, gtk4-paper-planeAUR, gtk4-gitAUR)
- libadwaita (libadwaita-gitAUR, libadwaita-without-adwaita-gitAUR)
- libhandy (libhandy-gitAUR)
- libnotify (libnotify-gitAUR)
- libpamac-aurAUR
- asciidoc (asciidoc-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- gobject-introspection (make)
- itstool (make)
- meson (meson-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- systemd (systemd-chromiumosAUR, systemd-selinuxAUR, systemd-gitAUR, systemd-fmlAUR) (make)
- vala (vala-gitAUR) (make)
- xorgproto (xorgproto-gitAUR) (make)
- lxsession (lxsession-gitAUR) (optional) – needed for authentification in Xfce, LXDE etc.
- polkit-gnome (xfce-polkit-gitAUR, xfce-polkitAUR, polkit-gnome-gitAUR) (optional) – needed for authentification in Cinnamon, Gnome
Required by (7)
- cleanupdate-git (requires pamac-cli) (optional)
- cmd-not-found (requires pamac-cli) (optional)
- debtap-mod (requires pamac)
- mintmenu (requires pamac) (optional)
- pamac-all (requires pamac-cli)
- rpmtoarch (requires pamac)
- update-notifier (requires pamac) (optional)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 40 Next › Last »
Pillgar commented on 2018-11-21 05:33 (UTC) (edited on 2018-11-21 05:35 (UTC) by Pillgar)
SpectralMemories commented on 2018-11-17 16:20 (UTC)
Hey, is it possible to add a desktop entry for pamac-manager? Would be quite useful
Zeph commented on 2018-09-27 16:28 (UTC) (edited on 2018-09-27 16:31 (UTC) by Zeph)
@blackhole: Use issue on repo for software error
blackhole commented on 2018-09-27 14:22 (UTC)
Today, trying to update some AUR package: ERROR:../src/transaction.vala:140:pamac_transaction_check_authorization_co: code should not be reached
manuel-192 commented on 2018-09-16 08:44 (UTC)
Package pamac-7.0.1-1.tar.gz:
$ LANG=en_US pamac-updater
(pamac-updater:7109): Gtk-WARNING **: 11:40:30.621: Locale not supported by C library. Using the fallback 'C' locale.
(pamac-updater:7109): GLib-GObject-CRITICAL **: 11:40:30.807: g_object_new_valist: invalid object type 'PamacManagerWindow' for value type 'PamacDatabase'
(pamac-updater:7109): CRITICAL : 11:40:30.819: pamac_database_get_config: assertion 'self != NULL' failed
(pamac-updater:7109): CRITICAL : 11:40:30.819: pamac_config_get_environment_variables: assertion 'self != NULL' failed
(pamac-updater:7109): GLib-CRITICAL **: 11:40:30.819: g_hash_table_iter_init: assertion 'hash_table != NULL' failed Memory overflow (core file created) <== translated this
FredBezies commented on 2018-09-09 06:51 (UTC)
@j0hannes: just open a bug on pamac bug tracker. More useful than posting a comment here.
j0hannes commented on 2018-09-05 21:50 (UTC)
My /tmp partition (tmpfs) has a size of 7.6 GB. Installing big packages with pamac makes my machine unresponsive and eventually leads to segfaults and reboot (if the fakeroot environment grows bigger than the available space in /tmp.
Downloading the snapshot and making the package in a different location manually is a workaround, but do I need to see my system crashing to realize that a package probably won't build in /tmp? Could pamac maybe monitor the available space there and cancel its build process when it's running low? Maybe also offering the user to build it again in a different location?
brenosilveira1 commented on 2018-09-01 21:46 (UTC)
Uninstalled with "aurman -Rnsuv pamac-aur" and inslled again with "aurman -S pamac-aur". Worked fine.
brenosilveira1 commented on 2018-09-01 18:42 (UTC)
Same as andrelevou1980.
andrelevou1980 commented on 2018-09-01 14:09 (UTC)
An error occurred while updating: The transaction is not ready
Pinned Comments
Zeph commented on 2022-06-04 13:58 (UTC) (edited on 2024-10-29 07:25 (UTC) by Zeph)
For some problems with pamac, check or create issues on