Getting transmission 2.93 in Bionic

Bug #1758459 reported by Schwert
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
transmission (Debian)
Fix Released
Unknown
transmission (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

As referenced on #1752940 some trackers have started blacklisting Transmission versions below 2.93 on the basis that they have no way of telling if an older version has been patched for CVE-2018-5702 or not.

Can we try to get 2.93 in Bionic before the final freeze, especially since this is an LTS and 2.92 is starting to get old (Apr 9, 2016).

Schwert (schw3rt)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in transmission (Ubuntu):
status: New → Confirmed
Revision history for this message
eris23 (jdkatz23) wrote :

A private tracker I belong to now requires 2.93 or above.

tags: added: upgrade-software-version
Changed in transmission (Debian):
status: Unknown → New
Changed in transmission (Debian):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote : Re: [ffe] Getting transmission 2.93 in Bionic

The changes from 2.93 seem mostly bugfixes,
https://github.com/transmission/transmission/releases/tag/2.93

summary: - Getting 2.93 in Bionic
+ [ffe] Getting transmission 2.93 in Bionic
Changed in transmission (Ubuntu):
importance: Undecided → Wishlist
importance: Wishlist → Low
Changed in transmission (Debian):
status: Confirmed → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you have an example that could be used to write a testcase for a SRU?

summary: - [ffe] Getting transmission 2.93 in Bionic
+ Getting transmission 2.93 in Bionic
Jeremy Bícha (jbicha)
tags: added: rls-bb-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

The report got no duplicate or user activity so it doesn't seem important for our users, also there is no testcase so it's difficult to verify a SRU until we get one, tagging as rls-not-fixing but we can still do the update later if someone describe how to trigger the issue

tags: added: rls-bb-notfixing
removed: rls-bb-incoming
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Changed in transmission (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.