Your message dated Sun, 13 Sep 2026 15:13:06 -0500
with message-id <[email protected]>
and subject line Re: Bug#1147609: RFS: moraine/0.3.1-1 -- snapshot backup over
SSH/rsync and rclone (CLI + GTK desktop app)
has caused the Debian Bug report #1147609,
regarding RFS: moraine/0.3.1-1 -- snapshot backup over SSH/rsync and rclone
(CLI + GTK desktop app)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1147609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147609
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "moraine":
Package name: moraine
Version : 0.3.1-1
Upstream contact : Jonaz Thern <[email protected]>
URL: https://github.com/TheJonaz/moraine-backup
License: Expat
Vcs: https://github.com/TheJonaz/moraine-backup
Section: utils
The source builds the following binary packages:
moraine - snapshot backup over SSH/rsync and rclone (CLI + GTK
desktop app)
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/moraine/
Alternatively, you can download the package with 'dget' using this command:
dget -x
https://mentors.debian.net/debian/pool/main/m/moraine/moraine_0.3.1-1.dsc
Changes since the last upload:
moraine (0.3.1-1) unstable; urgency=medium
New upstream release 0.3.1.
- New `moraine recommend` command, and a "Suggest sources" button in the
desktop app, proposing what is worth backing up on the machine.
- Secret fields can reference environment variables (`env:`). The OS
keyring backend stays disabled, as its crates are not in Debian;
upstream decoupled it from the `gui` feature in 0.3.1 so that the
desktop app still builds without
- A dropped network connection no longer hangs an rsync/ssh backup.
- moraine(1) documents the `recommend` and `check` commands.
Refresh drop-windows-build-dependency.patch for the new Cargo.toml.
-- Jonaz Thern <[email protected]> Fri, 11 Sep 2026 22:02:38 +0200
This is a routine new upstream release. On the packaging side nothing
changed beyond refreshing the patch for the new Cargo.toml; debian/rules
only gained a comment explaining why the keyring feature stays off.
Build-Depends are unchanged.
Simon, you sponsored 0.2.2-1 (#1141175) -- if you have time for this one
too, I would be grateful.
One further question, if you don't mind me asking it here: once this
upload is out of the way, would you consider advocating a Debian
Maintainer application for me? moraine is the only package I maintain,
and DM upload permission for it would spare you a sponsoring round on
every upstream release. I am aware the key signature is the slow part. I
have not met a Debian Developer in person yet, so that is mine to sort
out first. Either way, thank you for the reviews so far.
--
Thern AI Solutions
Jonaz Thern
Thern AI Solutions
Webbutveckling · Cybersäkerhet · AI-tjänster · IT-konsulting
[email protected]
www.thern.io <https://www.thern.io>
Lindås 2, 342 52 Vislanda · Org.nr 781229-2733 · Innehar F-skatt
--- End Message ---
--- Begin Message ---
Hi Jonaz,
On 9/13/26 14:25, Thern AI Solutions wrote:
[snip]
This is a routine new upstream release. On the packaging side nothing changed
beyond refreshing the patch for the new Cargo.toml; debian/rules only gained a
comment explaining why the keyring feature stays off. Build-Depends are
unchanged.
Thanks for continuing to maintain the package!
Simon, you sponsored 0.2.2-1 (#1141175) -- if you have time for this one too, I
would be grateful.
Sure, done:
$ dput ssh-upload ../moraine_0.3.1-1_source.changes
Uploading moraine using sftp to ssh-upload (host: ssh.upload.debian.org;
directory: /srv/upload.debian.org/UploadQueue/)
running allowed-distribution: check whether a local profile permits uploads to
the target distribution
running protected-distribution: warn before uploading to distributions where a
special policy applies
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
Logging into host ssh.upload.debian.org as tsimonq2
Uploading moraine_0.3.1-1.dsc
Uploading moraine_0.3.1.orig.tar.xz
Uploading moraine_0.3.1-1.debian.tar.xz
Uploading moraine_0.3.1-1_source.buildinfo
Uploading moraine_0.3.1-1_source.changes
One further question, if you don't mind me asking it here: once this upload is
out of the way, would you consider advocating a Debian Maintainer application
for me? moraine is the only package I maintain, and DM upload permission for it
would spare you a sponsoring round on every upstream release. I am aware the
key signature is the slow part. I have not met a Debian Developer in person
yet, so that is mine to sort out first. Either way, thank you for the reviews
so far.
The key signature is definitely the blocker for considering any Debian
Maintainer application, so you're correct that you'd need to sort that out
first.
That being said, my bar for advocating someone for Debian Maintainer is
something like 10-15 uploads (+/- some heuristics depending on upload type,
responsiveness and resourcefulness of the person, and other factors). We are at
two uploads.
It would certainly help if you maintained more packages in Debian, or if you
helped with e.g. the Debian Rust Team. I would suggest reading up on the Debian
QA Team, and/or the Rust book: https://rust-team.pages.debian.net/book/
Also, since we've talked last, Debian has passed a General Resolution regarding
AI usage: https://lists.debian.org/debian-devel-announce/2026/08/msg00005.html
With you explicitly advertising AI solutions, and given that moraine is written
with the assistance of AI, it would be good for you to read that in full.
I don't personally have a problem with your AI usage, I just sincerely hope
that you're learning from this process. Maintaining another package (especially
without AI assistance) would instill confidence that you, as Jonaz, know what
you're doing.
All of that being said, feel free to either continue this conversation with me
1:1, or write to me again when you have your key signature(s).
(I know a copy of this goes to debian-mentors; this is *not* an invitation to
re-litigate the GR, especially here. ;) )
Best regards,
Simon Quigley
[email protected]
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
