Your message dated Sat, 22 Feb 2025 14:37:33 +0100
with message-id <[email protected]>
and subject line Incorrect report
has caused the Debian Bug report #1096178,
regarding aptly: Segfault with database corruption on arm64
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.)
--
1096178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096178
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptly
Version: 1.6.0+ds1-3+b1
Severity: important
Control: found -1 1.6.0-1
Control: tag -1 + upstream
Control: forwarded -1 https://github.com/aptly-dev/aptly/issues/1172
Aptly 1.6.x segfaults on arm64, and end up corrupting its
database. It's actually an issue in libraries that aptly depend on,
see:
https://github.com/golang/snappy/issues/62
https://github.com/syndtr/goleveldb/pull/365
Cheers,
--
Seb
--- End Message ---
--- Begin Message ---
notfound 1096178 1.6.0-1
thanks
Turns out this was already fixed in Debian, through
golang-github-golang-snappy version 0.0.2-3, after discussing it with
the upstream author, we've both now confirmed no version in Debian was
ever affected, and upstream's conclusion is that their initial tests
concluding aptly 1.6.0-1 was affected must have been incorrect.
Cheers,
--
Seb
--- End Message ---
