Package: lzma

On Sat, Oct 10, 2009, Szymon Juraszczyk wrote:
> Hello,
> 
> You're not bothered to fix it any time soon, are you? I can't believe
> the bug is still both in Etch and Lenny. Keep up the good work!

Hi Szymon,

did you report the bug on bugs.debian.org?

I can't manage to find it and this must be the reason why I hadn't had
the chance to include your patch (I was very busy back then and I am
again quite busy right now).

I currently don't have any Debian box to build and sign a new package
and I've been without Internet access at home until this week. So this
may take a long time before I upload the fix.

For the record and my comaintainers, I am filing a bug.

> -------- Original message --------
> Subject: A patch for lzma 4.43-14
> Date: Wed, 23 Jul 2008 03:17:22 +0200
> Sender: Szymon Juraszczyk <[email protected]>
> Recipient: [email protected]
> 
> Hello again,
> 
> Here is a very simple patch for the bug I've just reported. Lines got
> wrapped in the email but it's just an addition to one line of code so
> you don't need to apply the patch - you can simply change it manually. I
> could not be bothered to attach it as a file - sorry, too much hassle
> compared to copy&paste :D
> 
> Hope it helps.
> 
> diff -Nru lzma-4.43/debian/patches/02_lzmp.diff
> lzma-4.43/debian/patches/02_lzmp.diff
> --- lzma-4.43/debian/patches/02_lzmp.diff       2008-07-23
> 02:45:43.000000000 +0200
> +++ lzma-4.43/debian/patches/02_lzmp.diff       2008-07-23
> 02:53:11.540972726 +0200
> @@ -831,7 +831,7 @@
>  +                      }
>  +                      catch (Exception e) {
>  +                              cerr << argv[0] << ": " << e.what() <<
> endl;
> -+                              unlink(output_filename.c_str());
> ++                              if (program_mode != PM_TEST)
> unlink(output_filename.c_str());
>  +                              delete(decoderSpec);
>  +
>  +                              return STATUS_ERROR;
> 
> 

-- 
Mohammed Adnène Trojette



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to