Anarcat recently
wrote about
Qalculate, and I think I m a convert, even though
I ve only barely scratched the surface.
The thing I almost immediately started using it for is time calculations.
When I
started tracking my time, I
quickly found that
Timewarrior was good at
keeping all the data I needed, but I often found myself extracting bits of
it and reprocessing it in variously clumsy ways. For example, I often don t
finish a task in one sitting; maybe I take breaks, or I switch back and
forth between a couple of different tasks. The raw output of
timew
summary is a bit clumsy for this, as it shows each chunk of time spent as
a separate row:
$ timew summary 2025-02-18 Debian
Wk Date Day Tags Start End Time Total
W8 2025-02-18 Tue CVE-2025-26465, Debian, 9:41:44 10:24:17 0:42:33
next, openssh
Debian, FTBFS with GCC-15, 10:24:17 10:27:12 0:02:55
icoutils
Debian, FTBFS with GCC-15, 11:50:05 11:57:25 0:07:20
kali
Debian, Upgrade to 0.67, 11:58:21 12:12:41 0:14:20
python_holidays
Debian, FTBFS with GCC-15, 12:14:15 12:33:19 0:19:04
vigor
Debian, FTBFS with GCC-15, 12:39:02 12:39:38 0:00:36
python_setproctitle
Debian, Upgrade to 1.3.4, 12:39:39 12:46:05 0:06:26
python_setproctitle
Debian, FTBFS with GCC-15, 12:48:28 12:49:42 0:01:14
python_setproctitle
Debian, Upgrade to 3.4.1, 12:52:07 13:02:27 0:10:20 1:44:48
python_charset_normalizer
1:44:48
So I wrote this Python program to help me:
#! /usr/bin/python3
"""
Summarize timewarrior data, grouped and sorted by time spent.
"""
import json
import subprocess
from argparse import ArgumentParser, RawDescriptionHelpFormatter
from collections import defaultdict
from datetime import datetime, timedelta, timezone
from operator import itemgetter
from rich import box, print
from rich.table import Table
parser = ArgumentParser(
description=__doc__, formatter_class=RawDescriptionHelpFormatter
)
parser.add_argument("-t", "--only-total", default=False, action="store_true")
parser.add_argument(
"range",
nargs="?",
default=":today",
help="Time range (usually a hint, e.g. :lastweek)",
)
parser.add_argument("tag", nargs="*", help="Tags to filter by")
args = parser.parse_args()
entries: defaultdict[str, timedelta] = defaultdict(timedelta)
now = datetime.now(timezone.utc)
for entry in json.loads(
subprocess.run(
["timew", "export", args.range, *args.tag],
check=True,
capture_output=True,
text=True,
).stdout
):
start = datetime.fromisoformat(entry["start"])
if "end" in entry:
end = datetime.fromisoformat(entry["end"])
else:
end = now
entries[", ".join(entry["tags"])] += end - start
if not args.only_total:
table = Table(box=box.SIMPLE, highlight=True)
table.add_column("Tags")
table.add_column("Time", justify="right")
for tags, time in sorted(entries.items(), key=itemgetter(1), reverse=True):
table.add_row(tags, str(time))
print(table)
total = sum(entries.values(), start=timedelta())
hours, rest = divmod(total, timedelta(hours=1))
minutes, rest = divmod(rest, timedelta(minutes=1))
seconds = rest.seconds
print(f"Total time: hours:02 : minutes:02 : seconds:02 ")
$ summarize-time 2025-02-18 Debian
Tags Time
CVE-2025-26465, Debian, next, openssh 0:42:33
Debian, FTBFS with GCC-15, vigor 0:19:04
Debian, Upgrade to 0.67, python_holidays 0:14:20
Debian, Upgrade to 3.4.1, python_charset_normalizer 0:10:20
Debian, FTBFS with GCC-15, kali 0:07:20
Debian, Upgrade to 1.3.4, python_setproctitle 0:06:26
Debian, FTBFS with GCC-15, icoutils 0:02:55
Debian, FTBFS with GCC-15, python_setproctitle 0:01:50
Total time: 01:44:48
Much nicer. But that only helps with some of my reporting. At the end of a
month, I have to work out how much time to bill Freexian for and fill out a
timesheet, and for various reasons those queries don t correspond to single
timew tags: they sometimes correspond to the sum of all time spent on
multiple tags, or to the time spent on one tag minus the time spent on
another tag, or similar. As a result I quite often have to do basic
arithmetic on time intervals; but that s surprisingly annoying! I didn t
previously have good tools for that, and was reduced to doing things like
str(timedelta(hours=..., minutes=..., seconds=...) + ...) in Python,
which gets old fast.
Instead:
$ qalc '62:46:30 - 51:02:42 to time'
(225990 / 3600) (183762 / 3600) = 11:43:48
I also often want to work out how much of my time I ve spent on Debian work
this month so far, since Freexian pays me for
up to 20% of my work time on
Debian; if I m
under that then I might want to prioritize more Debian projects, and if I m
over then I should be prioritizing more Freexian projects as otherwise I m
not going to get paid for that time.
$ summarize-time -t :month Freexian
Total time: 69:19:42
$ summarize-time -t :month Debian
Total time: 24:05:30
$ qalc '24:05:30 / (24:05:30 + 69:19:42) to %'
(86730 / 3600) / ((86730 / 3600) + (249582 / 3600)) 25.78855349%
I love it.
Dear Debian community,
this is bits from DPL for February.
Ftpmaster team is seeking for new team members
In December, Scott Kitterman announced his retirement from the project.
I personally regret this, as I vividly remember his invaluable support
during the Debian Med sprint at the start of the COVID-19 pandemic. He
even took time off to ensure new packages cleared the queue in under 24
hours. I want to take this opportunity to personally thank Scott for his
contributions during that sprint and for all his work in Debian.
With one fewer FTP assistant, I am concerned about the increased
workload on the remaining team. I encourage anyone in the Debian
community who is interested to consider reaching out to the FTP masters
about joining their team.
If you're wondering about the role of the FTP masters, I'd like to share
a fellow developer's perspective:
This year I'll be participating of 
[I d like to stop writing posts like this. I ve been trying to work out what to say now for nearly 2 months (writing the mail to 
by por Andrew Gon alves
Getting things ready for the event.
Intro to GELOS talk.
A ~~not so~~ Brief Introdution to the Debian Project talk.
Everyone already knew Debian!
Debian and the Free Culture talk
People in the auditorium space.
Free Software: the paths to a free life talk
Coffee Break.
The FOSS Ecosystem and You talk.
Group photo.
Celebration goes on in the bar.
Nova gera o: uma entrevista com iniciantes no projeto Debian
Instala o personalizada e automatizada do Debian com preseed
Manipulando patches com git-buildpackage
debian.social: Socializando Debian do jeito Debian
Proxy reverso com WireGuard
Celebra o dos 30 anos do Debian!
Instalando o Debian em disco criptografado com LUKS
O que a equipe de localiza o j conquistou nesses 30 anos
Debian - Projeto e Comunidade!
Design Gr fico e Software livre, o que fazer e por onde come ar
Another short status update of what happened on my side last
month. One larger blocks are the 
So there are only 2 web browser engines, and it seems likely there will
soon only be 1, and making a whole new web browser from the ground up is
effectively impossible because the browsers vendors have weaponized web
standards complexity against any newcomers. Maybe eventually someone will
succeed and there will be 2 again. Best case. What a situation.
So throw out all the web standards. Make a browser that just runs WASM
blobs, and gives them a surface to use, sorta like Wayland does. It has
tabs, and a throbber, and urls, but no HTML, no javascript, no CSS.
Just HTTP of WASM blobs.
This is where the web browser is going eventually anyway, except in the
current line of evolution it will be WASM with all the web standards
complexity baked in and reinforcing the current situation.
Would this be a mass of proprietary software? Have you looked at any
corporate website's "source" lately? But what's important is that this
would make it easy enough to build new browsers that they would stop
being a point of control.
Want a browser that natively supports RSS? Poll the feeds, make a UI,
download the WASM enclosures to view the posts. Want a browser that
supports IPFS or gopher? Fork any browser and add it, the mantenance load
will be minimal. Want to provide access to GPIO pins or something? Add an
extension that can be accessed via the WASI component model. This would
allow for so many things like that which won't and can't happen with the
current market duopoly browser situation.
And as for your WASM web pages, well you can still use HTML if you like. Use
the WASI component model to pull in a HTML engine. It doesn't need to
support everything, just the parts of web standards that you want to use.
Or you can do something entitely different in your WASM that is not HTML
based at all but a better paradigm (oh hi Spritely or display postscript
or gemini capsules or whatever).
Dual innovation sources or duopoly? I know which I'd prefer. This is not my
project to build though.
For quite a few years, I ve been using pattern weights instead of pins
when cutting fabric, starting with random objects and then mostly using
some big washers from the local hardware store.
However, at about 22 g per washer, I needed quite a few of them, and
dealing with them tended to get unwieldy; I don t remember how it
happened, but one day I decided to make myself some bigger weights with
a few washers each.
I suspect I had seen somebody online with some nice hexagonal pattern
weights, and hexagonal of course reminded me of the 
Many years ago I made myself a 
Then a few years ago the cheap cotton had started to get worn, and I
decided I needed to replace it. I found a second choice (and thus
cheaper :) ) version of a 
This time I skipped a few pockets that I had found I didn t use that
much, and I didn t add a hood, which didn t play that well when worn
over a hoodie, but I added some detached sleeves, for additional wind
protection.
This left about 60 cm and some odd pieces of leftover fabric in my
stash, for which I had no plan.
And then February
I did however have a spool of reflector thread made of glass fibre by
Rico Design, which I think was originally sold to be worked into
knitting or crochet projects (it is now discontinued) and I had never
used.
I decided to try and sew a decorative blanket stitch border, a decision
I had reasons to regret, since the thread broke and tangled like crazy,
but in the end it was done, I like how it looks, and it seems pretty
functional. I hope it won t break with time and use, and if it does I ll
either fix it or try to redo with something else.
Of course, the day I finished sewing the reflective border it stopped
raining, so I haven t worn it yet, but I hope I ll be able to, and if it
is an horrible failure I ll make sure to update this post.