[arch-dev-public] [signoff] syslog-ng 2.0.6-1 - Arch-dev-public - lists.archlinux.org

newer
[arch-dev-public] kde4

[arch-dev-public] [signoff] syslog-ng 2.0.6-1

older
[arch-dev-public] libgpod update...

Eric Belanger

9 Dec 2007 9 Dec '07

12:43 a.m.

In testing for both arch. Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements Please signoff. Eric -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Show replies by date

Dan McGee

9 Dec 9 Dec

7:46 p.m.

On Dec 8, 2007 6:43 PM, Eric Belanger wrote:

In testing for both arch.

Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements

Works for me on i686, but not sure when that persist file gets created or used as it is non-existent on my machine. -Dan

Roman Kyrylych

11 Dec 11 Dec

3:18 p.m.

2007/12/9, Dan McGee :

On Dec 8, 2007 6:43 PM, Eric Belanger wrote:

...
In testing for both arch.

Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements

Works for me on i686, but not sure when that persist file gets created or used as it is non-existent on my machine.

Same here. Signed off (i686). -- Roman Kyrylych (Роман Кирилич)

Aaron Griffin

12 Dec 12 Dec

4:22 a.m.

On Dec 8, 2007 6:43 PM, Eric Belanger wrote:

In testing for both arch.

Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements

Please signoff.

Signed off, both arches - ditto with the persist file being missing with no indication as to why

Eric Belanger

4:18 a.m.

On Tue, 11 Dec 2007, Aaron Griffin wrote:

On Dec 8, 2007 6:43 PM, Eric Belanger wrote:

...
In testing for both arch.

Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements

Please signoff.

Signed off, both arches - ditto with the persist file being missing with no indication as to why

For the persist file, try restarting the daemon again. I had to restart it twice to get the file to appear. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Aaron Griffin

4:33 a.m.

On Dec 11, 2007 10:18 PM, Eric Belanger wrote:

On Tue, 11 Dec 2007, Aaron Griffin wrote:

...
On Dec 8, 2007 6:43 PM, Eric Belanger wrote:

...
In testing for both arch.

Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements

Please signoff.

Signed off, both arches - ditto with the persist file being missing with no indication as to why

For the persist file, try restarting the daemon again. I had to restart it twice to get the file to appear.

You're correct - is it possible that the dir is created the first time? Maybe including an empty dir in the package will fix this?

Eric Belanger

6 a.m.

On Tue, 11 Dec 2007, Aaron Griffin wrote:

On Dec 11, 2007 10:18 PM, Eric Belanger wrote:

...
On Tue, 11 Dec 2007, Aaron Griffin wrote:

...
On Dec 8, 2007 6:43 PM, Eric Belanger wrote:

...
In testing for both arch.

Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements

Please signoff.

Signed off, both arches - ditto with the persist file being missing with no indication as to why

For the persist file, try restarting the daemon again. I had to restart it twice to get the file to appear.

You're correct - is it possible that the dir is created the first time? Maybe including an empty dir in the package will fix this?

The empty directory is already in the package. Maybe adding an empty file will do the trick. It could be a normal behavior though as I don't know what this file is used for. I noticed that once created, it is afterward modified each time the daemon is restarted. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Eric Belanger

8 Jan 8 Jan

5:38 p.m.

On Wed, 12 Dec 2007, Eric Belanger wrote:

On Tue, 11 Dec 2007, Aaron Griffin wrote:

...
On Dec 11, 2007 10:18 PM, Eric Belanger wrote:

...
On Tue, 11 Dec 2007, Aaron Griffin wrote:

...
On Dec 8, 2007 6:43 PM, Eric Belanger wrote:

...
In testing for both arch.

Changes: upstream update, rebuilt against libol-less eventlog (close FS#8849), moved location of syslog-ng.persist from /var to /var/lib/syslog-ng, minor PKGBUILD improvements

Please signoff.

Signed off, both arches - ditto with the persist file being missing with no indication as to why

For the persist file, try restarting the daemon again. I had to restart it twice to get the file to appear.

You're correct - is it possible that the dir is created the first time? Maybe including an empty dir in the package will fix this?

The empty directory is already in the package. Maybe adding an empty file will do the trick. It could be a normal behavior though as I don't know what this file is used for. I noticed that once created, it is afterward modified each time the daemon is restarted.

I know I got the required sign-off to move it to core but I just want to be safe because of the persist file "issue" that was brought up. Is everything OK? If no one complains in the next few days or if I get additionnal sign-offs, I'll move it to core (with eventlog). -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

5946

Age (days ago)

5976

Last active (days ago)

Download

7 comments

4 participants

tags

participants (4)

Aaron Griffin
Dan McGee
Eric Belanger
Roman Kyrylych