Alexandre,
On 05/06/2024 21:35, Alexandre Rossi wrote:
Now that transmission is back in testing, that's an option.
Will do if I fin sponsorship for this.
I would be happy to sponsor you if you commit to maintaining it
long-term (as per the backports rules)
--
Martina Ferrari
Hi,
> I saw that you just closed this bug a couple of hours ago. Coincidentally,
> last night I finally had the time to recompile the package for
> bullseye/arm64 and install it on my raspberry pi (I could not use your
> backport as it is a different arch). I tested this problem, and I can
> confi
Hi!
I saw that you just closed this bug a couple of hours ago.
Coincidentally, last night I finally had the time to recompile the
package for bullseye/arm64 and install it on my raspberry pi (I could
not use your backport as it is a different arch). I tested this problem,
and I can confirm th
Hi,
> I suppose it must be fixed in 4.x then. Sadly, I cannot test this as my box
> running transmission-daemon is on stable..
backporting is straightforward (no change) and I publish[1] a built backport
if you want to try.
[1] http://deb.zincube.net/
Thanks,
Alex
Hi,
I suppose it must be fixed in 4.x then. Sadly, I cannot test this as my
box running transmission-daemon is on stable..
On 12/04/2024 11:01, Alexandre Rossi wrote:
Hi,
Today I noticed transmission-daemon being down after a reboot, and saw it is
crashing with a malloc error. After some de
Hi,
> Today I noticed transmission-daemon being down after a reboot, and saw it is
> crashing with a malloc error. After some debugging, I found out that this only
> happens if I am using the `--portmap` option *and* a local minissdpd is
> running.
Does this still happen with 4.x?
What is the se
Package: transmission-daemon
Version: 3.00-1
Severity: normal
X-Debbugs-Cc: t...@debian.org
Today I noticed transmission-daemon being down after a reboot, and saw it is
crashing with a malloc error. After some debugging, I found out that this only
happens if I am using the `--portmap` option *and*
7 matches
Mail list logo
