Bug#1067451: libzip: please update to 1.10.1

2024-03-21 Thread Thomas Klausner
Package: libzip Version: 1.7.3-1.1 Upstream here. The libzip package in Debian is quite outdated (a release from 2020), can you please update it to the latest version (1.10.1 right now, from August 2023)? We take care that libzip is backwards-compatible, so the update should be painless. Let me

Bug#874010: libzip: CVE-2017-14107: memory allocation failure in _zip_cdir_grow (zip_dirent.c)

2017-09-02 Thread Thomas Klausner
libzip-1.3.0 fixing this and another CVE is now available. Thomas On Fri, Sep 01, 2017 at 11:14:02PM +0200, Salvatore Bonaccorso wrote: > Source: libzip > Version: 0.11.2-1.2 > Severity: important > Tags: security upstream patch fixed-upstream > > Hi, > > the following vulnerability was

Bug#662083: libzip: FTBFS on hurd-i386 (fixed ENOENT number in tests)

2016-01-15 Thread Thomas Klausner
This has been fixed differently in the latest libzip release -- the code returns error 9 now, errno is not printed, see http://hg.nih.at/libzip/file/54229f050761/regress/open_nosuchfile.test Thomas

Bug#784684: ziptorrent crashes with doublefree on git-archive produced zip files

2016-01-15 Thread Thomas Klausner
ziptorrent has been removed from libzip. The file format needs particular zlib/deflate settings that have been hard to reproduce across operating systems. For this reason, the ziptorrent files created by the ziptorrent program were not always the same. Please remove the ziptorrent package from

Bug#691310: bug in zip_add(3)

2014-08-07 Thread Thomas Klausner
I think this bug is fixed since libzip-0.11.2. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#739308: libzip-dev: include file in wrong place

2014-08-07 Thread Thomas Klausner
Hi! Upstream here. I found this bug report. We've put the header file in lib by purpose, because e.g. for multilib installations, /usr/include must be portable over all architectures; so architecture or machine-specific files must be somewhere else. One convention for that is

Bug#684193: Command names for Simon Tatham's puzzles

2012-08-13 Thread Thomas Klausner
On Mon, Aug 13, 2012 at 10:24:23AM +0200, Jakob Gruber wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/13/2012 01:36 AM, Ben Hutchings wrote: I would be happy to rename the commands like this, but: 1. I would like you to include the command prefix as an option in your own