libzen wasn't compiled with large file support

This bug was fixed in the package libzen - 0.4.35-1

---------------
libzen (0.4.35-1) experimental; urgency=medium

  * [015b0fa] Imported Upstream version 0.4.35

 -- Chow Loong Jin <email address hidden> Tue, 04 Apr 2017 00:39:46 +0800

> some -D compilation flags that aren't even directly referenced in the codebase

FYI impact is on the 32-bit libc usage, _FILE_OFFSET_BITS=64 enabling the libc file API with "off_t" of 64-bit instead of 32-bit.
No other interaction.

Example of impacted user (+ I got 2 emails with same bug report, no web link):
https://sourceforge.net/p/mediainfo/discussion/297610/thread/8893b38f/

Whoops, uploaded with a wrong version number (0.4.34-1ubuntu0.16.04.1) to zesty. I've fixed it with another upload (0.4.34-1ubuntu0.17.04.1).

Fix confirmed by end user to work, also on 16.04, see
https://sourceforge.net/p/mediainfo/discussion/297610/thread/8893b38f/#4075

Do we know that this change won't be ABI impacting? Is this known, or has anybody looked into this?

There is no ABI impacting, as it is only internal (communication between the lib and libc API). libzen API uses 64-bit integers whatever is the presence of the flag, the flag is only for libc.
And actually, the ABI break would have been seen previously, when the compilation flag was removed (switch from Automake to CMake), as the flag was present in previous versions, and it was not the case.

In https://sourceforge.net/p/mediainfo/discussion/297610/thread/8893b38f/#4075 you can see that a user backported himself the new binary to an old platform of Debian without API break.

Yeah I tested it using mediainfo on a large file in chroots of the target distributions without rebuilding mediainfo.

Hi,
I was looking at the ABI question asked by Robie in #5.
The package fortunately has a symbols file and it would pop up there if the breakage would affect the symbols themselve.
There might be a fix behind stable symbols - like the actually desired fix for huge files. But that should be a no-op or an improvement IMHO.
So I'd expect the ABI impact to be ok.

Hello Chow, or anyone else affected,

Accepted libzen into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libzen/0.4.32-1ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Chow, or anyone else affected,

Accepted libzen into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libzen/0.4.33-3ubuntu0.16.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-yakkety to verification-done-yakkety. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-yakkety. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Chow, or anyone else affected,

Accepted libzen into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libzen/0.4.34-1ubuntu0.17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Tested and verified on xenial, yakkety and zesty.

This bug was fixed in the package libzen - 0.4.32-1ubuntu0.16.04.1

---------------
libzen (0.4.32-1ubuntu0.16.04.1) xenial-proposed; urgency=medium

  * [8601742] Import large files patch (LP: #1693850)

 -- Chow Loong Jin <email address hidden> Tue, 30 May 2017 00:39:22 +0800

The verification of the Stable Release Update for libzen has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package libzen - 0.4.34-1ubuntu0.17.04.1

---------------
libzen (0.4.34-1ubuntu0.17.04.1) zesty-proposed; urgency=medium

  * [ed99500] Import large files patch (LP: #1693850)

 -- Chow Loong Jin <email address hidden> Sat, 27 May 2017 01:17:40 +0800

This bug was fixed in the package libzen - 0.4.33-3ubuntu0.16.10.1

---------------
libzen (0.4.33-3ubuntu0.16.10.1) yakkety-proposed; urgency=medium

  * [57d99f9] Import large files patch (LP: #1693850)

 -- Chow Loong Jin <email address hidden> Tue, 30 May 2017 00:24:00 +0800