Summary: | mail-filter/postgrey-1.35 version bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rambaldi <gentoo> |
Component: | Current packages | Assignee: | Andreis Vinogradovs ( slepnoga ) <andreis.vinogradovs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | barzog, damien, hydrapolic, net-mail+disabled, proxy-maint, qnikst |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 504786 |
Description
Rambaldi
2014-07-29 09:51:45 UTC
*** Bug 518684 has been marked as a duplicate of this bug. *** As Perl 5.18 has been marked stable few days ago, how may I help to stabilize this version? As you know Perl 5.18 broke 1.34 version :-( Thanks! For 1.34 version to work with perl 5.18 either this stabilization is needed or you can manually apply patch from https://github.com/schweikert/postgrey/issues/3 +*postgrey-1.35 (06 Aug 2014) + + 06 Aug 2014; Mikle Kolyada <zlogene@gentoo.org> +postgrey-1.35.ebuild: + Version bump wrt bug #518470. Thanks to Andreis Vinogradovs + small typo: --- postgrey-1.35.ebuild 2014-08-06 20:18:36.000000000 +0200 +++ postgrey-1.35.ebuild.new 2014-08-07 15:19:55.000000000 +0200 @@ -66,5 +66,5 @@ insopts -o root -g root -m 755 newinitd "${FILESDIR}"/${PN}.rc.new ${PN} insopts -o root -g root -m 640 -newconfd "${FILESDIR}"/${PN}.conf.new_run ${PN} +newconfd "${FILESDIR}"/${PN}.conf.new ${PN} } how on earth this could be marked 'RESOLVED FIXED' when 1.35 is sill not stable? perl 5.18 went stable on amd64 and all of a sudden postgrey stopped working! (In reply to Nick Soveiko from comment #6) > how on earth this could be marked 'RESOLVED FIXED' when 1.35 is sill not > stable? perl 5.18 went stable on amd64 and all of a sudden postgrey stopped > working! it is version bump bug, not stable request. |