All I did was a run a few commands which are documented on a Debian wiki
page advised by someone else here on the list and that's how I got a
working update package. I did run into something else after
updating the remmina package, but that's more likely because of of
something being done differently in the newer version or something like
that. Also how I use remmina is bit odd going connecting to the first
host, via rdp and then the second host also via rdp before connecting
via ssh to another host where a tmux session is started. Where certain
keys don't work anymore with the new version, While that did work
with the older version of the package, with the new version of the
package different keys don't work in the tmux session. Like my arrow
keys and my pageup/pagedown keys, so I don't think I could figure out
what the cause of something like that would be to fix that. So I don't
think I'm qualified to be packaging for Debian or updating packages for
Debian as I can't even figure out why the new version doesn't behave
the same way as the old one did for my setup, but I appreciate the help
I got to be able to be using a new version of remmina on Debian 13.
Kind regards,
Maarten
On 9/18/26 18:06, Norwid Behrnd wrote:
That is great news. If you are up for a bit more of a challenge you
could seek a sponsor to upload it as a backport to trixie-backports.
I think probably debian-mentors mailing list is better place to ask
about that.
While I agree it is nice to read the issues are locally resolved, the usual
sequence here is to get first the update migrated to branch `testing`, and then
(initiated by `dch --bpo`) rebuild the package as backport. For both, seeking a
sponsor (RFS bug ticket) via the mentors page is straight forward; the duration
to find a sponsor however can vary by time at disposition of volunteering Debian
developers who opt-in to sponsor others' work. I do so for `ruby-mdl` -
sometimes it got done (i.e., accepted to start the 5 day clock) the same day,
other times about a week or two.
By the package tracker page, `remmina` is a team maintained; for one, if Maarten
is not / not yet a known uploader (file `d/control` and perhaps commit history
in the repository _to package_ on salsa), this calls for a NMU (a non maintainer
upload). @Maarten: don't worry, the mentors page may generate the template for
the email to seek a sponsor. This includes how to proceed to label the RFS as a
NMU, too. On the other hand, it is possible (read: can ease to find a sponsor)
to cc the email about the RFS ticket to the corresponding team (here: Debian
Remote Maintainers, https://wiki.debian.org/DebianRemote,
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-remote-team).
Regards,
Norwid
