Search Criteria
Package Details: informant 0.5.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/informant.git (read-only, click to copy) |
---|---|
Package Base: | informant |
Description: | An Arch Linux News reader and pacman hook |
Upstream URL: | https://github.com/bradford-smith94/informant |
Keywords: | news |
Licenses: | MIT |
Submitter: | bradford-smith94 |
Maintainer: | bradford-smith94 |
Last Packager: | bradford-smith94 |
Votes: | 91 |
Popularity: | 3.07 |
First Submitted: | 2018-02-27 18:54 (UTC) |
Last Updated: | 2023-09-13 20:22 (UTC) |
Latest Comments
1 2 3 4 Next › Last »
jongeduard commented on 2023-05-17 19:24 (UTC) (edited on 2023-05-17 19:27 (UTC) by jongeduard)
Hi! Today I noticed that Informant shows me an extra error message "Max retries exceeded with url" starting with "ERROR:" in uppercase red colored letters, just before it came up with the intended actual news interruption.
See below for the fragment of terminal output which makes it clear.
How do I need to interpret this? Is this a tiny issue in Informant or is it really just some weird short during internet connection issue that I was experiencing?
FranklinYu commented on 2023-05-17 15:34 (UTC) (edited on 2023-05-17 15:34 (UTC) by FranklinYu)
Do I understand it correctly that this (broken hook) applies to any AUR package that adds pacman hooks, not only informant?
(To be more precise, it would only happen to locally-built packages, be it AUR or not.)
jongeduard commented on 2023-05-06 21:10 (UTC)
@tocic
Thanks! I was having this Python error, followed by an exception trace with details.
In my case simply uninstalling was enough to see no error anymore. Turns out that it happened on package installation, not the actual build. However, just to be sure I decided to do one more time and also rebuild the thing.
bradford-smith94 commented on 2023-05-06 16:16 (UTC)
@tocic Thanks for the "!informant" idea, I don't know why I hadn't thought of that yet. Hopefully that will make handling Python updates easier.
tocic commented on 2023-05-06 10:21 (UTC)
@kullfar I agree that it's always worth to increment
pkgrel
to take the burden off the user, but note that in this case it'll still produce the error because you can't upgrade any package with the old hook, eveninformant
itself :). Maybe the upstream can circumvent that with the!informant
string in the Target field.kullfar commented on 2023-05-06 09:53 (UTC)
It's better to increment pkgrel, otherwise 50% of users will spend their time discovering what had happened until they realized that they need to uninstall/instal the package (as I did).
ssnailz commented on 2023-05-05 07:16 (UTC)
@tocic thank you! that worked
sshaikh commented on 2023-05-04 16:23 (UTC)
I feel this would have actually been helpful to do. Things like aurtools don't notice the new PKBUILD at the moment.
tocic commented on 2023-05-04 04:55 (UTC)
If you have the following error
, you need to uninstall
informant
(or manually disable the pacman hook), rebuild it againstpython3.11
, and install again.programegg commented on 2023-02-20 04:26 (UTC) (edited on 2023-02-20 04:26 (UTC) by programegg)
This PKGBUILD should not be flagged out of date.
0.4.5
is the latest version ofinformant
according to the upstream URL. The out-of-date report indicates a build failure but the package builds just fine on my system.1 2 3 4 Next › Last »