| Summary: | =app-admin/syslog-ng-3.5.4.1 stable request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Flogeras <dflogeras2> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Mr. Bones. (RETIRED) <mr_bones_> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | Keywords: | PMASKED, STABLEREQ |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
David Flogeras
2014-07-08 02:36:49 UTC
(General note about your stabilisation requests: this doesn't normally happen on a per-architecture basis. If one moves, every one moves.) profiles/package.mask: # Michael Sterrett <mr_bones_@gentoo.org> (16 Jan 2014) # testing mask for 3.5.x releases >=app-admin/syslog-ng-3.5 Apparently that version isn't going stable. OK I see The reason I use 3.5.x is because on uclibc it only builds with the (newly) added USE=amqp (well actually, only with that turned off). When it is unconditionally turned on, it failes due to missing spawn.h related functionality. Is it feasible to backport that USE flag to the 3.4.x series ebuild since 3.5.x wont be stabled? The issue with syslog-ng-3.5.4.1 is that there are known memory leaks with certain configs. If you want to unmask it and run it locally and it works ok for you, that's fantastic (I do this myself), but it's not a good version to just release on the general population. |
