Bug 12937 - gtk-gnutella package update to 1.0.1
Summary: gtk-gnutella package update to 1.0.1
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Joseph Wang
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-03-04 22:46 CET by Anderson Carvalho
Modified: 2015-10-27 06:57 CET (History)
0 users

See Also:
Source RPM: gtk-gnutella-1.0.0-3.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Anderson Carvalho 2014-03-04 22:46:02 CET
31 December 2013, Version 1.0.1 Released

This is a minor release correcting a grave bug causing gtk-gnutella to think all other gtk-gnutella out there are hostile.

Other minor improvements are present, as well as low-level bug fixes. The most visible change is that filenames with parentheses are now mangled to have the parentheses turned into brackets, instead of being left as-is. This allows filename cut-n-paste into shell commands, without having to use the shell auto-completion to escape the parentheses.
Improvements

    Generate a NM/1.0 HTTP-like header at the top of the pre-computed nm list.
    [GTK] Avoid GUI flickering when widget sensitivity is changing quickly.
    Replace "()" with "[]" in filenames for easier cut-n-paste in shell commands.
    Windows: improved stack unwinding.

Bug Fixes

    Fixed grave bug, making all GTKGs appear hostile.
    qrp_close(): must disable periodic monitoring during shutdown.
    filename_to_utf8_normalized(): fixed broken if/else logic in loop.

Under the Hood

    Updated the GeoIP databases.
    Added a Keywords entry for lintian in the gtk-gnutella.desktop file.
    Fixed license link to point to GPL-2 on Debian systems.
    Added gtk-gnutella.appdata.xml for distributions that need such a file.
    Renamed icon.xpm as icon.48x48.xpm and icon.32x32.xpm as icon.xpm.
    TLS: disabled SVN signature verification code, since we no longer use SVN.
    Define our own G_STRFUNC, do not use the version from GLib.
    vmm_resize(): fixed wrong implementation when vmm_crashing is true.
    Semi-reliable UDP: drop traffic to host temporarily if we can't send messages.
    Use a 5-minute TLS ban to avoid reconnecting to host with TLS when it failed.
    download_mark_active(): do not reset fi->recv_last_rate on HTTP follow-ups
    bsched_heartbeat(): fixed wrong delay computatation, use tm_elapsed_ms().
    gtk_gnutella_exit(): always emit final "cleanly exited" info.
    zalloc_stack_accounting_ctrl(): used wrong lookup key, leading to crashes.
    mingw_valloc(): handle initial non-hinted allocations larger than page.
    signal_trap_with(): fixed improper return value computation for sigaction().

http://gtk-gnutella.sourceforge.net/


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-03-06 00:38:57 CET

Keywords: (none) => Triaged
Assignee: bugsquad => joequant

Comment 1 Samuel Verschelde 2015-09-21 13:20:12 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 2 Marja Van Waes 2015-10-27 06:57:27 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.