Re: Packaging not the latest release

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

 



Hi Miro,

On Monday, 02 December 2013 at 08:37, Miro Hrončok wrote:
> Hi,
> 
> I'm trying to package httpretty [0] for Python 2 and 3. However, the
> latest upstream release 0.7.0 seems to not work with Python 3 (at
> least the tests are failing). Version 0.6.5 however works fine (or
> at least way better) with Python 3.
> 
> What should I do now?
> 
> 1) Create separate packages python-httpretty (0.7.0) and
> python3-httpretty (0.6.5)
> 2) Create one package with both (0.6.5)
> 3) Do not package httpretty for Python 3 at all
> 
> I need this package working with Python 3 and I only package Python
> 2 version as well because it's appropriate :) So 3) is not really
> good for me and if I choose 1) I might not package Python 2 version
> at all.
> 
> What does guidelines say about packaging latest upstream release? I
> somehow remeber that being checked in the review, but I cannot find
> it in the guidelines.
> 
> Is it OK to package older release when the new one is broken? Do I
> need FPC approval/exception for that?

I'd say it's common sense not to package the latest version if it's
broken, so I'd go for option 2 in your case and updated to the latest
when it's fixed.

Is there an upstream bug open for the failing tests?

Regards,
Dominik
-- 
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu
"Faith manages."
        -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging





[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux