[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706546: marked as done (unblock: httrack/3.47.9-1)



Your message dated Wed, 01 May 2013 20:10:38 +0100
with message-id <1367435438.28602.20.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#706546: unblock: httrack/3.47.9-1
has caused the Debian Bug report #706546,
regarding unblock: httrack/3.47.9-1
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 owner@bugs.debian.org
immediately.)


-- 
706546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706546
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package httrack from sid to testing/wheezy, or block current testing/wheezy version if this is too late (which is something I am fearing)

As reminder, httrack is a website copier (ie. same category as wget)

The current stable/squeeze version (3.43.9-1) is a bit old, and has several bugs:
- random corruption of files during updates (#607704)
- random crash when interrupting a mirror (#657878)
- buffer overflow while repairing cache (#614966)

But OTOH, the current testing/wheezy release (3.46.1-1) also has serious issues:
- random closing of files/sockets, leading to break randomly download of files of produce files with garbage (#706535) ; 3.46 and 3.43 issue
- UTF-8 conversion bug on Linux that may lead to buggy filenames and invalid filenames in current working directory (#706536) ; 3.46 speficic issue
- memory leak in hashtable, that may lead to excessive memory consumption (#706537) ; 3.46 and 3.43 issue

BUG #706536 (testing-version specific) is especially annoying, as it randomly breaks downloaded filenames if they contain non-ascii characters, and can create garbage files in current working directory (might be more than "important").

BUG #706535 (stable/testing specific, fixed in sid) is also annoying (random breakage of downloaded files), but impacts all versions prior to sid.

I therefore would suggest either to accept current SID version (3.47.7-1) in testing, or, considering the very late delay (and the fact that the sid version is new), blocking the testing version. The diff between stable and sid is important, due to new features (such as UTF-8 filenames handling), but the diff between testing and sid is reasonnable.

Sorry for the very late notification  - I have been tricked by the timing again!


-- System Information:
Debian Release: 6.0.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8.4-grsec (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
On Wed, 2013-05-01 at 17:06 +0200, Xavier Roche wrote:
> Le 01/05/2013 17:01, Adam D. Barratt a écrit :
> > That's not really practical at this point, no.
> 
> Yep, seems logical.
> 
> Then we can either let the 3.46.1-1 release (and have an update later -
> in such case please close this ticket) or unblock 3.47.7-1 when possible.

Looking through the upload history, there appear to have been nine
uploads in around two weeks. On that basis, I'm afraid I'm not
particularly happy to unblock the package at this point.

Let's stick with 3.46.1-1 for now and revisit which fixes might be
suitable for a stable update after the release.

Regards,

Adam

--- End Message ---

Reply to: