In data sabato 19 gennaio 2019 10:19:15 CET, Maximilian Engelhardt ha scritto: > On Samstag, 19. Januar 2019 08:15:20 CET Pino Toscano wrote: > > In data sabato 19 gennaio 2019 01:12:38 CET, Debian Bug Tracking System ha > scritto: > > > Processing commands for control@bugs.debian.org: > > > > fixed 914211 5.54.1-1 > > > > > > Bug #914211 [src:kio] [src:kio] please remove insecure TLS version > > > fall-back mechanism Marked as fixed in versions kio/5.54.1-1. > > > > > > > thanks > > > > > > Stopping processing here. > > > > Closing the bug then. > > > > Maximilian, please follow the right procedure for closing bugs: > > https://www.debian.org/Bugs/Developer.en.html#closing > > > > Thanks, > > Hi Pino, > > I didn't close the bug because the version in stable is still affected by it. > I filed my initial report against both versions, stable and testing/unstable at > that time, because I was told on #debian-devel IRC to do so. > So if this bug is closed how can/should the version in stable be tracked? The version that fixes the bug is not in stable, and the bug has a version present in stable as "found". I'd personally add the tag for the stable version, since I don't see how leaving a bug open will change anything (maxy does not do fixes to stable, and the rest of the "team" does not have the capacity to do so). I don't see how this is different from any other bug reported in the past that gets fixed only in unstable: it is not obviously not fixed in stable, and leaving it open will not magically make it fixed for stable. -- Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.