Project

General

Profile

Packaging Request #3355

[toxcore] Package upgrade to prepare for new release

Tha_14 - over 1 year ago - . Updated over 1 year ago.

Status:
wont-fix
Priority:
bug
Assignee:
-
% Done:

100%


Description

Hello,

Due to recent changes to the DHT code in c-toxcore the network does not provide enough reliability for new features to work properly.
I would like to ask for a package upgrade to 0.2.18 in order to prepare the network for our new release where the new features will be available for use(including support for the clients).

Thank you


Subtasks

Packaging Request #3356: [qtox] Update package due to CVEwont-fix

Actions

History

#1

Updated by Tha_14 over 1 year ago

I selected the wrong type of issue, this is a packaging request. Please change if possible.
Thank you.

#2

Updated by bill-auger over 1 year ago

  • Status changed from unconfirmed to open
  • Tracker changed from Bug to Packaging Request
#3

Updated by bill-auger over 1 year ago

it is not a packaging request really - packaging request is for packages which are not yet in the repos - this is a request to upgrade the version of an existing package - normally, that should be done on the packages website, with the "flag out-of-date" button, unless the outdated package causes some bug

however, the "flag out-of-date" button on the packages website is disabled for this package, because this package comes from arch - that would need to be done on the arch packages website (and it is already flagged "out-of-date" on the arch packages website) - we normally do not over-ride arch packages, unless there is a bug of some kind, which arch will not fix - however, it was flagged "out-of-date" over 6 months ago, so it does appear to need some attention from someone

#4

Updated by bill-auger over 1 year ago

  • Status changed from open to info needed

toxore is used by the following clients, packaged by arch:

  • qtox
  • toxic
  • tuntox
  • utox

so the relevant question to ask is, does this cause a bug in one of those clients? - if it does, then i could escalate this to a bug report against the arch package

arch has only one bug report about any of these packages (utox) in the past two years; and that is only about an expired GPG key

toxore is used by the following clients, packaged by parabola:

  • tox-prpl

does this cause a bug in 'tox-prpl'? - if so, perhaps we could do something about that now

#5

Updated by bill-auger over 1 year ago

  • Status changed from info needed to wont-fix

from IRC:

<Tha_14> I've tried contacting both current maintainers of toxcore for arch and I'm still waiting for a reply on those. I'll update the issue when I have more info regarding bugs.
<Tha_14> You can go ahead and close both #3355 and #3356 since I was being too hasty.

Also available in: Atom PDF