Hi, Since there are a nice number of fixes accumulated on the 3.3 tree, I'd like to prepare for the 3.3.2 release. Before doing the actual release though, I'd appreciate any kind of feedback you can give. The current state is in git right now, I'll try to create a timestamped tarball later this weekend. Thanks. -- Bazsi
Balazs Scheidler <bazsi@balabit.hu> writes:
Since there are a nice number of fixes accumulated on the 3.3 tree, I'd like to prepare for the 3.3.2 release.
Before doing the actual release though, I'd appreciate any kind of feedback you can give.
I'll be building Debian & Ubuntu packages in about half an hour, so they'll hit my repository by midnight latest. I don't have any pending issues for 3.3, so if my machines survive with current git head 'till tomorrow night, I'll be eagerly waiting for the 3.3.2 tag to land. ;)
The current state is in git right now, I'll try to create a timestamped tarball later this weekend.
For the time being, I still have the script that autogenerates a tarball from git each night, and I triggered it now to create a snapshot right away: http://packages.madhouse-project.org/syslog-ng/syslog-ng-3.3-1319904599-c7fb... That is one horrible timestamp + sha1 combo there. I'll update the script at some point to include the latest tag and the contents of the VERSION file in there somewhere. So we'll end up with something like syslog-ng-3.3.1+${VERSION}-${TIMESTAMP}-${SHA1}.tar.gz. Even longer, but slightly clearer about what version it is. (The above is a make dist tarball, by the way, with ivykis and libmongo-client included. It's not a simple git export that needs additional bootstrapping!) -- |8]
Gergely Nagy <algernon@balabit.hu> writes:
Balazs Scheidler <bazsi@balabit.hu> writes:
Since there are a nice number of fixes accumulated on the 3.3 tree, I'd like to prepare for the 3.3.2 release.
Before doing the actual release though, I'd appreciate any kind of feedback you can give.
I'll be building Debian & Ubuntu packages in about half an hour, so they'll hit my repository by midnight latest.
Actually, I spoke too soon. I enabled systemd support in the latest version, and that depends on a package that is not part of anything but Debian sid. So I'll have to make a separate branch for the other distros, disabling systemd support. That'll take a little longer, and I don't think I will be able to work on this before tuesday. -- |8]
On 10/29/2011 05:51 PM, Balazs Scheidler wrote:
Hi,
Since there are a nice number of fixes accumulated on the 3.3 tree, I'd like to prepare for the 3.3.2 release.
Before doing the actual release though, I'd appreciate any kind of feedback you can give.
The current state is in git right now, I'll try to create a timestamped tarball later this weekend.
Thanks.
Hi, there seems to be a patch of mine missing from both the 3.3 and 3.4 trees, that fixes a mistake that I did while implementing the 'pdbtool test' explicit rule id check. Right now if no rule-id is supplied to test, pdbtool always prints and error message and quits with exit code 3. Most probably this went unnoticed in mailing list traffic, can you please apply before releasing 3.3.2? Thanks, Balint commit d6b94979493c4871fac712525ab9b516a824d376 Author: Balint Kovacs <blint@balabit.hu> Date: Wed Aug 31 15:30:52 2011 +0200 pdbtool: fix missing check in pdbtool test ruleid warning Signed-off-by: Balint Kovacs <blint@balabit.hu> diff --git a/modules/dbparser/pdbtool.c b/modules/dbparser/pdbtool.c index 1c5d818..35b502c 100644 --- a/modules/dbparser/pdbtool.c +++ b/modules/dbparser/pdbtool.c @@ -759,7 +759,7 @@ pdbtool_test(int argc, char *argv[]) return 1; if (failed_to_match) return 2; - if (failed_to_find_id) + if (failed_to_find_id && test_ruleid) { printf("Could not find the specified ID, or the defined rule doesn't have an example message.\n"); return 3;
On Mon, 2011-10-31 at 14:51 +0100, Balint Kovacs wrote:
On 10/29/2011 05:51 PM, Balazs Scheidler wrote:
Hi,
Since there are a nice number of fixes accumulated on the 3.3 tree, I'd like to prepare for the 3.3.2 release.
Before doing the actual release though, I'd appreciate any kind of feedback you can give.
The current state is in git right now, I'll try to create a timestamped tarball later this weekend.
Thanks.
Hi,
there seems to be a patch of mine missing from both the 3.3 and 3.4 trees, that fixes a mistake that I did while implementing the 'pdbtool test' explicit rule id check. Right now if no rule-id is supplied to test, pdbtool always prints and error message and quits with exit code 3. Most probably this went unnoticed in mailing list traffic, can you please apply before releasing 3.3.2?
hmm.. I was quite sure I merged it previously. But I did it now anyway: commit 571e71aaf42beb3170ed9cec588a918f05afc8bb Author: Balazs Scheidler <bazsi@balabit.hu> Date: Mon Oct 31 21:54:40 2011 +0100 pdbtool: fix missing check in pdbtool test ruleid warning Signed-off-by: Balint Kovacs <blint@balabit.hu> -- Bazsi
participants (3)
-
Balazs Scheidler
-
Balint Kovacs
-
Gergely Nagy