| Commit message (Collapse) | Author | Age |
|\
| |
| | |
pympress: init at 1.2.0
|
| |
| |
| |
| | |
Co-Authored-By: Jan Tojnar <jtojnar@gmail.com>
|
|\ \
| | |
| | | |
todoman: 3.6.0 -> 3.7.0
|
| |/
| |
| |
| |
| |
| |
| | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/todoman/versions
|
|\ \
| | |
| | | |
softmaker-office: 970 -> 972
|
| | |
| | |
| | |
| | |
| | | |
Changes:
https://www.softmaker.com/en/servicepacks-office-changelog
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/qownnotes/versions
|
|\ \
| |/
|/| |
skrooge: Fix build
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SoftMaker/FreeOffice collects some system information upon unlocking the
product. But in doing so, it attempts to execute /bin/ls. If the execve
syscall fails, the whole unlock procedure fails. This works around that
by rewriting /bin/ls to the proper path.
SoftMaker Office restarts itself upon some operations, such changing the
theme and unlocking. Unfortunately, we do not have control over its
environment then and it will fail with an error. Starting SoftMaker
Office from scratch will then work.
Fixes #71228
|
| | |
|
|\ \
| | |
| | | |
flexibee: 2019.2.5 -> 2019.3.0.3
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/flexibee/versions
|
| |/
|/|
| |
| | |
See: https://github.com/Philip-Scott/Spice-up/pull/288
|
|\ \
| | |
| | |
| | | |
Hydra nixpkgs: ?compare=1548439
|
| | |
| | |
| | |
| | | |
Co-authored-by: worldofpeace <worldofpeace@protonmail.ch>
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
elementary OS's ecosystem is curated around Ubuntu's LTS releases.
This means the development platform for their curated applications
always includes a LTS version of vala (in 18.04 it's 0.40).
Because of how vala development works it suspect some of these
applications to have serious issues if complied with the latest vala.
However in the past year or so, for Pantheon at least, I don't think
their applications will have much issues with latest vala, and if there
is I don't think they'd be difficult to fix. In this single regard they've
become more responsive since their preferred language is vala.
As for the curated applications I have less of this confidence in.
So I'd have to be accept less applications, but that's something
I'm willing to compromise on. And this is easily reversible or
could be done on a per-application basis. And nix already makes
this trivial.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Refs:
e6754980264fe927320d5ff2dbd24ca4fac9a160
1e9cc5b9844ef603fe160e9f671178f96200774f
793a2fe1e8bb886ca2096c5904e1193dc3268b6d
c19cf65261639f749012454932a532aa7c681e4b
f6544d618f30fae0bc4798c4387a8c7c9c047a7c
|
|\| | |
|
| |\ \
| | | |
| | | | |
timetable: 1.0.8 -> 1.0.9
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/qownnotes/versions
|
| |\ \
| | |/
| |/| |
zim: 0.71.1 -> 0.72.0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/zim/versions
|
|\| | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/watson/versions
|
|\ \ \
| |/ /
|/| | |
|
| |\ \
| | |/
| |/| |
gtk3.setupHook: clear icon-theme.cache in preFixup
|
| | |
| | |
| | |
| | |
| | | |
This was either for the setup-hook to remove caches or added
even though the respective icon theme propagated it.
|
|\ \ \
| |/ /
|/| | |
|
| |\ \
| | | |
| | | | |
ledger-autosync: 1.0.0 -> 1.0.1
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/ledger-autosync/versions
|
| |\ \ \
| | | | |
| | | | | |
impressive: 0.12.0 -> 0.12.1
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/impressive/versions
|
| |\ \ \
| | | | |
| | | | | |
homebank: 5.2.7 -> 5.2.8
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/homebank/versions
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/gnucash/versions
|
|/ /
| |
| |
| | |
This reverts commit f8a8fc6c7c079de430fa528f688ddac781bcef16.
|
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 41af38f3728bd64b80721c44ed1fb019978cbc1b, reversing
changes made to f0fec244ca380b9d3e617ee7b419c59758c8b0f1.
Let's delay this. We have some serious regressions.
|
|\ \
| |/
|/| |
kexi: patch error due to Qt 5.13
|
| | |
|
|\| |
|
| |\
| | |
| | | |
paperwork: include setuptools to fix startup
|
| | | |
|
| | | |
|
|\| | |
|