Getting an error with newest installation "configparser.NoSectionError: No section: 'settings'" The full errordump is at pastebin
Resolved by adding the [settings] section in the config-file
Git Clone URL: | https://aur.archlinux.org/papis.git (read-only, click to copy) |
---|---|
Package Base: | papis |
Description: | Command-line document and bibliography manager |
Upstream URL: | https://github.com/papis/papis |
Licenses: | GPL-3.0-or-later |
Submitter: | JP-Ellis |
Maintainer: | gesh (tuurep) |
Last Packager: | gesh |
Votes: | 18 |
Popularity: | 0.100511 |
First Submitted: | 2018-08-13 20:42 (UTC) |
Last Updated: | 2025-04-23 18:31 (UTC) |
Getting an error with newest installation "configparser.NoSectionError: No section: 'settings'" The full errordump is at pastebin
Resolved by adding the [settings] section in the config-file
Version 0.11.1
has been updated, and is patched to allow the current version of python-isbnlib
.
To Update to Version 0.11 change pkgver=0.11 sha256sums=('e54739a1771ba4da4afe30b0b52dfc220543926765f975d14e8ddce508f4fdf9' '261f466e0a1765621877eef3b2b6498a2e54576d52b6fac66e52b7322d0d5608') and comment out patch on line 40
@johnabs The convention is that pkgname
should track the latest released version while pkgname-git
tracks master. Having said that, I will consider including patches for certain bugs (usually specific to Arch Linux), and will do so by including the commit patches from upstream. General fixes/improvements that are part of the usual software development will usually not be included.
For example, the two patch files currently included have been pushed upstream and will be included in the next release, but were only of relevance for Arch Linux (hence why you noticed they are no longer necessary for this newer version).
You are quite welcome to create your own papis-git
AUR package, meanwhile, I will wait until the next official release of papis (which will hopefully arrive sooner rather than later).
Thanks for pointing out the missing python-stevedore
. I will add it to the PKGBUILD.
@JP-Ellis,
There's a new update in master that Alex and Ale helped me get working with the bug where this hangs after using the picker. Also, there are 2 missing dependencies (python-stevedore, and python-typing_extensions(the latter required for the new commit, it would seem). Additionally, it seems that the two patches that are present are no longer necessary for this newer version. I have an updated PKGBUILD that addresses these issues and pulls from the master branch by default. Would it be more appropriate to create this build I've worked on as a papis-git pkg, or would you like a copy of this updated version to update this particular pkg? (Sorry, I hope this doesn't come off as rude, I'm a bit new to AUR etiquette) Thank you for your time and consideration.
--johnabs
@JP-Ellis It works now, thanks for your reply.
Just to make sure, so I know what the issue was: you mean reinstall all AUR packages, but there was only papis
in site packages. The command you posted also only included papis.
Do I have any control over where the package is installed, or do these python compatiblity issues need to be resolved by package maintainers only?
@jtlab When there's a major Python update (Python 3.7 -> 3.8), you have to re-install all AUG packages. Until you have done so, you will still have packages in /usr/lib/python3.7
). There were some incompatibilities with papis 0.9 which I have now fixed, so perhaps you still had papis in python3.7
simply because it failed to install correctly. It installs correctly into /usr/lib/python3.8
for me now.
In case you need to check for other packages with Python 3.8, you can get a list of all packages which with:
find /usr/lib/python3.7 -exec pacman -Qoq '{}' + | sort -u
The new release (0.9-2
) includes two upstream patches that fixes compatibility issues with Arch Linux's Python packages.
Pinned Comments