Package Details: jrnl 2.4.2-1

Git Clone URL: https://aur.archlinux.org/jrnl.git (read-only, click to copy)
Package Base: jrnl
Description: A simple command line journal application that stores your journal in a plain text file
Upstream URL: https://jrnl.sh
Licenses: MIT
Submitter: Runiq
Maintainer: flocomkoko
Last Packager: flocomkoko
Votes: 25
Popularity: 1.34
First Submitted: 2015-08-20 13:11
Last Updated: 2020-05-26 13:27

Pinned Comments

flocomkoko commented on 2020-05-26 13:32

Jrnl 2.4.2 minor release is out. Jrnl should work again. Upstream is very supportive and I encourage you to report problems there.

Should it break again: I will try to work together with upstream to fix packaging issues as soon as possible but i will not support arch-specific out-of-tree patches.

Latest Comments

1 2 3 Next › Last »

flocomkoko commented on 2020-05-26 13:39

@noeontheend

I understand your idea but patching the source to get it working does seem like a pretty dangerous approach especially if we are talking about major version changes.

It would add unnecessary complexity to maintaing this package especially since upstream responds really well to bug reports. It would also go against the packaging guidelines of arch.

As a compromise I could pin your patch in the comments for those who want to go down this road next time we encounter something like that.

flocomkoko commented on 2020-05-26 13:32

Jrnl 2.4.2 minor release is out. Jrnl should work again. Upstream is very supportive and I encourage you to report problems there.

Should it break again: I will try to work together with upstream to fix packaging issues as soon as possible but i will not support arch-specific out-of-tree patches.

griffrawk commented on 2020-05-23 18:11

I was able to get jrnl 2.4.1 to work by changing the pytz deps as follows: 'python-pytz>=2019.1' 'python-pytz<=2020.1'

Don't know if pytz has had an update in the meantime since your problem, but its fine for me (so far...)

EDIT: Ah its maybe fine for me because jrnl upstream seem to have already patched something as per the new comments in https://github.com/jrnl-org/jrnl/issues/783#issuecomment-623292369

noeontheend commented on 2020-05-07 01:59

In the meantime, would you consider adding a patch step to the PKGBUILD to update the dependency for Arch users? This version worked on my machine, but if you know more about Python packaging than me, you may have a better approach.

flocomkoko commented on 2020-05-05 15:52

I sadly have to inform all of you that again jrnl 2.4.1 is not buildable because python-pytz did an update which makes it incompatible with the jrnl build process.

benoliver999 commented on 2020-05-04 06:59

Once more we are in dependency hell, this time because python-pytz has been updated. It is preventing pacman from updating.

I have reported this here.

benoliver999 commented on 2020-04-27 12:41

This is running for me now, thank you!

flocomkoko commented on 2020-04-19 17:57

I contacted the jrnl developers and with the next release (2.4.0) everything should build and work again. Note that atm this package is not working due to multiple problems pointed out below.

benoliver999 commented on 2020-04-10 16:13

Thank you for getting in touch with them! It sounds like it'll get sorted in the end.

One minor thing, I think your .SRCINFO needs updating to reflect the new upstream URL

flocomkoko commented on 2020-04-10 12:31

Hi! I updated all the dependencies so they match those specified in the pyproject.toml file. Sadly this means jrnl is not possible to build under Arch since the hotfix for the tzlocal problem isn't out yet AND the pyproject.toml file demands a python-keyring version lower then the one in the arch repos.