User Details
- User Since
- Oct 23 2016, 10:57 AM (496 w, 5 d)
Yesterday
Run-tested this and also did a mini-exp run, which looks fine.
Thu, Apr 30
Mon, Apr 27
Sun, Apr 26
Given the existing backlog of actual framework and ports issues, I'd rather see effort directed there
Thu, Apr 23
Wed, Apr 22
I don't think removing entries without checking how long they have been unused is a good idea,
Mon, Apr 20
Those commits should probably be in Scribus 1.7.3, which is already in the ports tree. Is that not the case?
We're updating from 25.10, so
https://github.com/scribusproject/scribus/commit/9e0a29e950195ca674581362675a8d35e1f7dc51
https://github.com/scribusproject/scribus/commit/28bd3be104c06b9d4532affe150f7b74fe5b3e59
https://github.com/scribusproject/scribus/commit/ef7e975d6ea58c6afdddfdd1edb601a145cd9fd0
are also required.
Sun, Apr 19
- Rebase after gdal update
Fri, Apr 17
@pkubaj I did not patch scribus-devel as it feels not worth the effort. Maybe just disable the PDF option for a while?
Thu, Apr 16
Wed, Apr 15
Sorry for breaking it in the first place. I have no idea how I missed it when going over gnulib dependents.
Tue, Apr 14
Mon, Apr 13
- Address some comments
Sat, Apr 11
Fri, Apr 10
Thu, Apr 9
Wed, Apr 8
Mar 30 2026
I'm seriously afraid of introducing a security hole with this change, so I highlighted places in the code I'm not sure about.
- More TODOs
Mar 29 2026
Mar 27 2026
Mar 26 2026
Mar 25 2026
If I understand it correctly, this change does not affect nextboot either?
Mar 21 2026
Mar 20 2026
I don't see a point in doing this. You shouldn't run make cabal-extract and friends on quarerly branches.
Fixed too.
How do I reproduce the problem?
Mar 19 2026
This change is still not merged in.