Bug 914940 - [PATCH] Build with system zlib instead of bundled copy, enable bzip2 support
Summary: [PATCH] Build with system zlib instead of bundled copy, enable bzip2 support
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: freetype
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-23 16:22 UTC by Ville Skyttä
Modified: 2014-03-13 09:32 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-11 14:31:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Build with system zlib instead of bundled copy, enable bzip2 support (3.77 KB, patch)
2013-02-23 16:22 UTC, Ville Skyttä
no flags Details | Diff

Description Ville Skyttä 2013-02-23 16:22:09 UTC
Created attachment 701657 [details]
Build with system zlib instead of bundled copy, enable bzip2 support

- Build with system zlib, enable bzip2 support.
- Fix bogus dates in %changelog.

Ok if I commit + build this for devel?

Comment 1 Fedora End Of Life 2013-04-03 16:22:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Marek Kašík 2014-03-11 14:31:31 UTC
Hi,

I've enabled the bzip2 support today. Commit the fix of dates if you want. I'm closing this with resolution rawhide.

Thank you

Marek

Comment 3 Ville Skyttä 2014-03-12 21:15:23 UTC
Looks like you already fixed the dates in last August, 2.5.0-3.

Comment 4 Marek Kašík 2014-03-13 09:32:56 UTC
(In reply to Ville Skyttä from comment #3)
> Looks like you already fixed the dates in last August, 2.5.0-3.

I'm sorry for the noise then :).


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