Debian Bug report logs - #690067
symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <debian@abeckmann.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: symlink-conffiles: dpkg stores md5sum of target file in its database and does not update it on upgrades

Date: Tue, 09 Oct 2012 16:12:16 +0200

Package: dpkg
Version: 1.16.8
Severity: important
User: debian-qa@lists.debian.org
Usertags: piuparts
Control: affects -1 syslog-ng-core


Hi,

the syslog-ng-core is one of the few packages using symlink conffiles,
causing trouble for piuparts and debsums because dpkg does not properly
handle this. There are several other issues with symlink-conffiles, but
none seemed to match this.

The following files are shipped by the syslog-ng-core package in sid:
lrwxrwxrwx 1 root root  37 Oct  3 15:49 /etc/systemd/system/multi-user.target.wants/syslog-ng.service -> /lib/systemd/system/syslog-ng.service
lrwxrwxrwx 1 root root  37 Oct  3 15:49 /etc/systemd/system/syslog.service -> /lib/systemd/system/syslog-ng.service
-rw-r--r-- 1 root root 251 Oct  3 15:49 /lib/systemd/system/syslog-ng.service

The symlinks in /etc/ are conffiles.

And syslog-ng.service is having these md5sums:
3933398f3e6cf91d25e515977876208b  /lib/systemd/system/syslog-ng.service  <== 3.3.6-1, sid
41541800d349863ddd9f4279211ec4b3  /lib/systemd/system/syslog-ng.service  <== 3.3.5-2, wheezy

dpkg -s syslog-ng-core  (relevant parts extracted)

# fresh installation on wheezy:
Package: syslog-ng-core
Version: 3.3.5-2
Conffiles:
 /etc/systemd/system/multi-user.target.wants/syslog-ng.service 41541800d349863ddd9f4279211ec4b3
 /etc/systemd/system/syslog.service 41541800d349863ddd9f4279211ec4b3

# fresh installation on sid:
Package: syslog-ng-core
Version: 3.3.6-1
Conffiles:
 /etc/systemd/system/multi-user.target.wants/syslog-ng.service 3933398f3e6cf91d25e515977876208b
 /etc/systemd/system/syslog.service 3933398f3e6cf91d25e515977876208b

# fresh installation on wheezy and distupgrade to sid:
Package: syslog-ng-core
Version: 3.3.6-1
Conffiles:
 /etc/systemd/system/multi-user.target.wants/syslog-ng.service 41541800d349863ddd9f4279211ec4b3
 /etc/systemd/system/syslog.service 41541800d349863ddd9f4279211ec4b3

The md5sum for the symlink-conffiles does not get updated during package
upgrades - the link itself does not change, but the link target (that
was hashed and is not a conffile in this example) has been updated.
And of course debsums claims there are modified conffiles ...


Andreas

Message #12 received at 690051@bugs.debian.org (full text, mbox, reply):

From: Guillem Jover <guillem@debian.org>

To: Andreas Beckmann <debian@abeckmann.de>, 690051@bugs.debian.org

Subject: Re: Bug#690051: symlink-conffiles: dpkg stores md5sum of target file in its database and does not update it on upgrades

Date: Tue, 9 Oct 2012 17:10:00 +0200

Control: forcemerge 421344 -1

Hi!

On Tue, 2012-10-09 at 16:12:16 +0200, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.16.8
> Severity: important
> User: debian-qa@lists.debian.org
> Usertags: piuparts
> Control: affects -1 syslog-ng-core

> the syslog-ng-core is one of the few packages using symlink conffiles,
> causing trouble for piuparts and debsums because dpkg does not properly
> handle this. There are several other issues with symlink-conffiles, but
> none seemed to match this.

symlink conffiles have never been supported, packages using that are
buggy and should be fixed (see also 421344 and 312846).

> The following files are shipped by the syslog-ng-core package in sid:
> lrwxrwxrwx 1 root root  37 Oct  3 15:49 /etc/systemd/system/multi-user.target.wants/syslog-ng.service -> /lib/systemd/system/syslog-ng.service
> lrwxrwxrwx 1 root root  37 Oct  3 15:49 /etc/systemd/system/syslog.service -> /lib/systemd/system/syslog-ng.service
> -rw-r--r-- 1 root root 251 Oct  3 15:49 /lib/systemd/system/syslog-ng.service

I guess there's something to be said about symlinked configuration
shipped in /lib, but in any case the above is just wrong and goes
against the current system.

> The symlinks in /etc/ are conffiles.
> 
> And syslog-ng.service is having these md5sums:
> 3933398f3e6cf91d25e515977876208b  /lib/systemd/system/syslog-ng.service  <== 3.3.6-1, sid
> 41541800d349863ddd9f4279211ec4b3  /lib/systemd/system/syslog-ng.service  <== 3.3.5-2, wheezy

> The md5sum for the symlink-conffiles does not get updated during package
> upgrades - the link itself does not change, but the link target (that
> was hashed and is not a conffile in this example) has been updated.
> And of course debsums claims there are modified conffiles ...

Well, once this is natively supported by dpkg, what would be stored
would be the target of the symlink not its hash. The conffile prompt
interface would need to be adapted to show the difference in symlink
targets, etc.

thanks,
guillem

Message #27 received at 690051@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <debian@abeckmann.de>

To: Guillem Jover <guillem@debian.org>

Cc: 690051@bugs.debian.org

Subject: Re: Bug#690051: symlink-conffiles: dpkg stores md5sum of target file in its database and does not update it on upgrades

Date: Tue, 09 Oct 2012 18:07:22 +0200

Control: clone -1 -2
Control: reassign -2 syslog-ng-core 3.3.5-2
Control: found -2 3.3.6-1
Control: severity -2 serious
Control: retitle -2 symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

On 2012-10-09 17:10, Guillem Jover wrote:
> On Tue, 2012-10-09 at 16:12:16 +0200, Andreas Beckmann wrote:
>> Package: dpkg
>> Version: 1.16.8

>> the syslog-ng-core is one of the few packages using symlink conffiles,
>> causing trouble for piuparts and debsums because dpkg does not properly
>> handle this. There are several other issues with symlink-conffiles, but
>> none seemed to match this.
> 
> symlink conffiles have never been supported, packages using that are
> buggy and should be fixed (see also 421344 and 312846).

Thanks for this clarification. No need to patch debsums to just ignore
symlink-conffiles :-)
Cloning and reassigning to syslog-ng.

Andreas

Message #56 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: 690067@bugs.debian.org

Subject: syslog-ng-core: symlink conffile issues

Date: Sun, 14 Oct 2012 13:22:06 +0200

Control: tag -1 + pending

The easy fix is to remove debian/syslog-ng-core.conffiles. That has the
downside of not allowing the user to easily change the symlink to point
somewhere else (like a custom unit file) unless he diverts the file,
which is kind of awkward.

But alas, that's still less trouble than causing a mess with symlink
conffiles, apparently.

I've fixed it in my git tree, will poke GCS to pick it over for the next
syslog-ng upload.

-- 
|8]

Message #63 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: 690067@bugs.debian.org

Subject: Re: Bug#690067: syslog-ng-core: symlink conffile issues

Date: Mon, 15 Oct 2012 11:56:16 +0200

Gergely Nagy <algernon@balabit.hu> writes:

> The easy fix is to remove debian/syslog-ng-core.conffiles. That has the
> downside of not allowing the user to easily change the symlink to point
> somewhere else (like a custom unit file) unless he diverts the file,
> which is kind of awkward.
>
> But alas, that's still less trouble than causing a mess with symlink
> conffiles, apparently.
>
> I've fixed it in my git tree, will poke GCS to pick it over for the next
> syslog-ng upload.

Mostly for myself, but replacing the symlinks with real conffiles that
.include the former symlink targets may be an even better course of
action. I'll test that over the next few days, and see how upgrades
behave.

-- 
|8]

Message #70 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Enrico Zini <enrico@enricozini.org>

To: Gergely Nagy <algernon@balabit.hu>, 690067@bugs.debian.org

Subject: Re: Bug#690067: syslog-ng-core: symlink conffile issues

Date: Sat, 24 Nov 2012 13:52:40 +0100

[Message part 1 (text/plain, inline)]

On Mon, Oct 15, 2012 at 11:56:16AM +0200, Gergely Nagy wrote:

> Mostly for myself, but replacing the symlinks with real conffiles that
> .include the former symlink targets may be an even better course of
> action. I'll test that over the next few days, and see how upgrades
> behave.

Hi, any news?

Ciao,

Enrico

-- 
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>

[signature.asc (application/pgp-signature, inline)]

Message #75 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: Enrico Zini <enrico@enricozini.org>

Cc: 690067@bugs.debian.org

Subject: Re: Bug#690067: syslog-ng-core: symlink conffile issues

Date: Mon, 26 Nov 2012 12:57:26 +0100

Enrico Zini <enrico@enricozini.org> writes:

> On Mon, Oct 15, 2012 at 11:56:16AM +0200, Gergely Nagy wrote:
>
>> Mostly for myself, but replacing the symlinks with real conffiles that
>> .include the former symlink targets may be an even better course of
>> action. I'll test that over the next few days, and see how upgrades
>> behave.
>
> Hi, any news?

Sorry, I forgot to follow up on this it seems. I tested the unit files
that simply .include'd the real ones, and that works nicely. Tested the
upgrade path too, seems smooth.

I promised the maintainer to prepare patches suitable for wheezy,
including this one, but did not get around to do them yet. With a bit of
luck, I'll have some free time to make this happen around next week.

(For what it's worth, the fix is available in my git tree at [1] and
[2])

 [1]: https://github.com/algernon/syslog-ng/commit/cd7611244c818ccc14328cddb20467adb9d7851f.patch
 [2]: https://github.com/algernon/syslog-ng/commit/da0cd112858fef0b6263233877edee13ff890d90.patch

-- 
|8]

Message #80 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Csillag Tamas <cstamas@digitus.itk.ppke.hu>

To: 690067@bugs.debian.org

Cc: Gergely Nagy <algernon@balabit.hu>

Subject: what is to be done?

Date: Mon, 10 Dec 2012 21:49:16 +0100

Hi,

The patch seems fine to me.
Is something missing? Is something still needs to be done?

Regards,
  cstamas
-- 
CSILLAG Tamas (cstamas) - http://cstamas.hu/

Message #85 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: Csillag Tamas <cstamas@digitus.itk.ppke.hu>

Cc: 690067@bugs.debian.org

Subject: Re: Bug#690067: what is to be done?

Date: Tue, 11 Dec 2012 12:13:37 +0100

Csillag Tamas <cstamas@digitus.itk.ppke.hu> writes:

> The patch seems fine to me.
> Is something missing? Is something still needs to be done?

I still need to prep the other things. I most likely will have time this
coming friday.

For the record, pretty much everything that needs to be fixed, is fixed
in my tree[1], on either on my packaging/debian/3.3 or
packaging/debian/3.4 branches - all the work left now is to diff the
packaging against those trees, and pick the relevant fixes for this bug,
and others.

 [1]: https://github.com/algernon/syslog-ng/

-- 
|8]

Message #92 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Dominic Hargreaves <dom@earth.li>

To: Gergely Nagy <algernon@balabit.hu>, 690067@bugs.debian.org

Cc: Csillag Tamas <cstamas@digitus.itk.ppke.hu>, control@bugs.debian.org

Subject: Re: Bug#690067: what is to be done?

Date: Sat, 2 Mar 2013 12:21:09 +0000

[Message part 1 (text/plain, inline)]

tags 690067 +patch
thanks

On Tue, Dec 11, 2012 at 12:13:37PM +0100, Gergely Nagy wrote:
> Csillag Tamas <cstamas@digitus.itk.ppke.hu> writes:
> 
> > The patch seems fine to me.
> > Is something missing? Is something still needs to be done?
> 
> I still need to prep the other things. I most likely will have time this
> coming friday.
> 
> For the record, pretty much everything that needs to be fixed, is fixed
> in my tree[1], on either on my packaging/debian/3.3 or
> packaging/debian/3.4 branches - all the work left now is to diff the
> packaging against those trees, and pick the relevant fixes for this bug,
> and others.
> 
>  [1]: https://github.com/algernon/syslog-ng/

I've prepared an NMU based on the changes in that git repository;
debdiff attached. I will do a delayed upload later on today.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

[syslog-ng_3.3.6-1.1.debdiff (text/plain, attachment)]

Message #99 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Dominic Hargreaves <dom@earth.li>

To: 690067@bugs.debian.org

Subject: syslog-ng: diff for NMU version 3.3.6-1.1

Date: Sat, 2 Mar 2013 15:57:50 +0000

[Message part 1 (text/plain, inline)]

Dear maintainer,

I've prepared an NMU for syslog-ng (versioned as 3.3.6-1.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

[syslog-ng-3.3.6-1.1-nmu.diff (text/x-diff, attachment)]

Message #104 received at 690067-close@bugs.debian.org (full text, mbox, reply):

From: Laszlo Boszormenyi (GCS) <gcs@debian.hu>

To: 690067-close@bugs.debian.org

Subject: Bug#690067: fixed in syslog-ng 3.3.6-2

Date: Sat, 02 Mar 2013 16:03:01 +0000

Source: syslog-ng
Source-Version: 3.3.6-2

We believe that the bug you reported is fixed in the latest version of
syslog-ng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 690067@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <gcs@debian.hu> (supplier of updated syslog-ng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 02 Mar 2013 16:03:18 +0100
Source: syslog-ng
Binary: syslog-ng syslog-ng-dbg libsyslog-ng-3.3.6 libsyslog-ng-dev syslog-ng-core syslog-ng-mod-json syslog-ng-mod-mongodb syslog-ng-mod-sql
Architecture: source amd64 all
Version: 3.3.6-2
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) <gcs@debian.hu>
Changed-By: Laszlo Boszormenyi (GCS) <gcs@debian.hu>
Description: 
 libsyslog-ng-3.3.6 - Next generation system logging daemon (private library)
 libsyslog-ng-dev - Next generation system logging daemon (development files)
 syslog-ng  - Next generation system logging daemon (metapackage)
 syslog-ng-core - Next generation system logging daemon (core)
 syslog-ng-dbg - Next generation system logging daemon (debug symbols)
 syslog-ng-mod-json - Next generation system logging daemon (JSON plugin)
 syslog-ng-mod-mongodb - Next generation system logging daemon (MongoDB plugin)
 syslog-ng-mod-sql - Next generation system logging daemon (SQL plugin)
Closes: 690067 692056 697042
Changes: 
 syslog-ng (3.3.6-2) unstable; urgency=low
 .
   [ Gergely Nagy <algernon@madhouse-project.org> ]
   * Use /dev/ttyva on kFreeBSD as the target of the d_console_all
     destination (closes: #697042).
   * Use the standard /var/log/mail.{info,err,warn} location for the
     various mail-related logs (closes: #692056).
   * Don't mark systemd symlinks in /etc as conffiles.
   * Instead of installing systemd service file symlinks, install a
     conffile, that includes the real service file (closes: #690067).
   * Do not forcibly remove the systemd service files, that code is not
     needed anymore.
Checksums-Sha1: 
 018d39503f04939091784cb80caa765514cb0767 1934 syslog-ng_3.3.6-2.dsc
 b9e4c5c1c871a5d0a4f6819b1c873310e8c23029 26144 syslog-ng_3.3.6-2.debian.tar.xz
 5ca189f7bbea5e51919504bf39715d1b996f53cd 1332806 syslog-ng-dbg_3.3.6-2_amd64.deb
 00ccd8b5a19cda2e9fb657d0f4c1ff4af9e60d1e 176280 libsyslog-ng-3.3.6_3.3.6-2_amd64.deb
 37663301b3a28939d3cf6d1d4e9850f2089b3360 68982 libsyslog-ng-dev_3.3.6-2_amd64.deb
 f302f6db5b3e53dba6663f1387e567c8be22a192 199106 syslog-ng-core_3.3.6-2_amd64.deb
 7197dbc541ddace2c02c8a51037c2dca96223371 32194 syslog-ng-mod-json_3.3.6-2_amd64.deb
 d8d8ebb3145d8e4ede6cacb15d764e0da416903b 40450 syslog-ng-mod-mongodb_3.3.6-2_amd64.deb
 62fb292d6b955d112b0533ba0bca4b9f8155cb77 45478 syslog-ng-mod-sql_3.3.6-2_amd64.deb
 4bea4d17399a1853340cf513b9aabb76519a1528 30046 syslog-ng_3.3.6-2_all.deb
Checksums-Sha256: 
 a2840032f82dce6b6253b9e620328e91704716b27709119e027d66d0d8cf6baa 1934 syslog-ng_3.3.6-2.dsc
 d67cf252fdbdc7214732132b83bdd70f747066d65685333202645b01bf63dea1 26144 syslog-ng_3.3.6-2.debian.tar.xz
 23d89e2d87245c8340f49bb3326a321d0eab0cde62cfdda20a6c3848848ec380 1332806 syslog-ng-dbg_3.3.6-2_amd64.deb
 7c4e780a9070d5140b918f23d58b73805869ed7205de235ea1a1ff081177a97b 176280 libsyslog-ng-3.3.6_3.3.6-2_amd64.deb
 f3940a32d8b8a8581732354cba01e505c234adf3fa51ceb2ce64b0f0f77e4944 68982 libsyslog-ng-dev_3.3.6-2_amd64.deb
 986d7b801936130e7f3eba2c23509fb0402db486c5a1e52e82761589bba20db2 199106 syslog-ng-core_3.3.6-2_amd64.deb
 c621d168999d69308175b549f575ae3184a59b75f3f87020864d844397bcd35a 32194 syslog-ng-mod-json_3.3.6-2_amd64.deb
 3cd5d55f578529cd5379d0557c3a47c0e90a57447463724885183f48bedd37ce 40450 syslog-ng-mod-mongodb_3.3.6-2_amd64.deb
 d4e31828dc19bed2cf41532602e2e7e6de8f20c0ed9eee40b7192c0249bfe42e 45478 syslog-ng-mod-sql_3.3.6-2_amd64.deb
 1ac6a70041b741b66e3e0453702821e3203a0d8df22b34efbf3d53e86787a822 30046 syslog-ng_3.3.6-2_all.deb
Files: 
 1e2a387d5a9500ab7cc6c38267185b4a 1934 admin extra syslog-ng_3.3.6-2.dsc
 52c992f786c2ea97638d2a43d61907b8 26144 admin extra syslog-ng_3.3.6-2.debian.tar.xz
 6947882c3ca21b05881615be346b486a 1332806 debug extra syslog-ng-dbg_3.3.6-2_amd64.deb
 b564b509df242187ea7efff7cdcb0ffb 176280 libs extra libsyslog-ng-3.3.6_3.3.6-2_amd64.deb
 6bff2aebdcb68bdcfc9d738b3b4c988d 68982 libdevel extra libsyslog-ng-dev_3.3.6-2_amd64.deb
 4c28f3044b3d8baad2e84534471dac30 199106 admin extra syslog-ng-core_3.3.6-2_amd64.deb
 f167f2f25264199539be9bc0fa03c55e 32194 admin extra syslog-ng-mod-json_3.3.6-2_amd64.deb
 ad40f85d453581ae9afb8d13862722b8 40450 admin extra syslog-ng-mod-mongodb_3.3.6-2_amd64.deb
 58cd13af6ec138dd693f7f01eb3a4629 45478 admin extra syslog-ng-mod-sql_3.3.6-2_amd64.deb
 25c2337f07d2638253bc0ce6339b5849 30046 admin extra syslog-ng_3.3.6-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlEyIHAACgkQMDatjqUaT90ACgCgj3oc1qMkjAFybANRwMZ7da3f
Ed4An0n/+6efGlZ8VU1UIlxCaXuSX3WE
=nko0
-----END PGP SIGNATURE-----

Message #109 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Dominic Hargreaves <dom@earth.li>

To: 690067@bugs.debian.org

Cc: 690067-submitter@bugs.debian.org

Subject: Re: syslog-ng: diff for NMU version 3.3.6-1.1

Date: Sun, 3 Mar 2013 01:04:33 +0000

On Sat, Mar 02, 2013 at 03:57:50PM +0000, Dominic Hargreaves wrote:
> Dear maintainer,
> 
> I've prepared an NMU for syslog-ng (versioned as 3.3.6-1.1) and
> uploaded it to DELAYED/4. Please feel free to tell me if I
> should delay it longer.

Note: this patch does seem to trigger a dpkg prompt about a changed
config file (since the preinst removes the symlinks). Without the
preinst doing that, however, the new files don't get installed at
all.

At this point I'm not inclined to cancel the NMU, as it's an
improvement over what we currently have, but I would welcome advice
on whether it's possible to avoid the dpkg prompt in this edge case.

Dominic.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

Message #117 received at 690067-quiet@bugs.debian.org (full text, mbox, reply):

From: Andreas Beckmann <anbe@debian.org>

To: Dominic Hargreaves <dom@earth.li>, 690067-quiet@bugs.debian.org

Subject: Re: Bug#690067: syslog-ng: diff for NMU version 3.3.6-1.1

Date: Sun, 03 Mar 2013 08:40:21 +0100

On 2013-03-03 02:04, Dominic Hargreaves wrote:
> On Sat, Mar 02, 2013 at 03:57:50PM +0000, Dominic Hargreaves wrote:
>> Dear maintainer,
>>
>> I've prepared an NMU for syslog-ng (versioned as 3.3.6-1.1) and
>> uploaded it to DELAYED/4. Please feel free to tell me if I
>> should delay it longer.
> 
> Note: this patch does seem to trigger a dpkg prompt about a changed
> config file (since the preinst removes the symlinks). Without the
> preinst doing that, however, the new files don't get installed at
> all.
> 
> At this point I'm not inclined to cancel the NMU, as it's an
> improvement over what we currently have, but I would welcome advice
> on whether it's possible to avoid the dpkg prompt in this edge case.

I see three possibilities:

* install the new conffiles with a new name
* preinst: remove the symlink and create a file that matches dpkg's
expected md5sum - which probably means querying for the expected md5 and
embedding several old copies in the preinst script to allow smooth upgrades
* manage the configuration file with ucf

I'd prefer the second. It has the most work to do now, but it's a
temporary fix, i.e. it can be removed again for jessie or jessie+1.


Andreas

Message #122 received at 690067-close@bugs.debian.org (full text, mbox, reply):

From: Laszlo Boszormenyi (GCS) <gcs@debian.hu>

To: 690067-close@bugs.debian.org

Subject: Bug#690067: fixed in syslog-ng 3.3.5-3

Date: Sun, 03 Mar 2013 20:48:30 +0000

Source: syslog-ng
Source-Version: 3.3.5-3

We believe that the bug you reported is fixed in the latest version of
syslog-ng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 690067@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <gcs@debian.hu> (supplier of updated syslog-ng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 03 Mar 2013 17:57:00 +0100
Source: syslog-ng
Binary: syslog-ng syslog-ng-dbg libsyslog-ng-3.3.5 libsyslog-ng-dev syslog-ng-core syslog-ng-mod-json syslog-ng-mod-mongodb syslog-ng-mod-sql
Architecture: source all amd64
Version: 3.3.5-3
Distribution: testing-proposed-updates
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) <gcs@debian.hu>
Changed-By: Laszlo Boszormenyi (GCS) <gcs@debian.hu>
Description: 
 libsyslog-ng-3.3.5 - Next generation system logging daemon (private library)
 libsyslog-ng-dev - Next generation system logging daemon (development files)
 syslog-ng  - Next generation system logging daemon (metapackage)
 syslog-ng-core - Next generation system logging daemon (core)
 syslog-ng-dbg - Next generation system logging daemon (debug symbols)
 syslog-ng-mod-json - Next generation system logging daemon (JSON plugin)
 syslog-ng-mod-mongodb - Next generation system logging daemon (MongoDB plugin)
 syslog-ng-mod-sql - Next generation system logging daemon (SQL plugin)
Closes: 690067 692056 697042 702131
Changes: 
 syslog-ng (3.3.5-3) testing-proposed-updates; urgency=low
 .
   [ Gergely Nagy <algernon@madhouse-project.org> ]
   * Don't mark systemd symlinks in /etc as conffiles.
   * Instead of installing systemd service file symlinks, install a
     conffile, that includes the real service file (closes: #690067).
   * Do not forcibly remove the systemd service files, that code is not
     needed anymore.
   * Use the standard /var/log/mail.{info,err,warn} location for the various
     mail-related logs (closes: #692056).
   * Use /dev/ttyva on kFreeBSD as the target of the d_console_all
     destination (closes: #697042).
 .
   [ Laszlo Boszormenyi (GCS) ]
   * Fix ivykis fallback on eventfd2 errors with the addition of
     ivykis_fallback_fix.patch (closes: #702131).
Checksums-Sha1: 
 1ab67a318cd7989e06bb876bf2fde200d012fc98 1907 syslog-ng_3.3.5-3.dsc
 8ce3b7fef8cbfb0495a75cae2c185c11013a2d8a 22192 syslog-ng_3.3.5-3.debian.tar.xz
 a9c0957c1fa376160601c9615324716127233e09 28672 syslog-ng_3.3.5-3_all.deb
 0ee0dbb9e87272d0a98c5e5401f43fad4813e551 1368704 syslog-ng-dbg_3.3.5-3_amd64.deb
 f86e2f5d8ffbe4b623265f8c04582894d562da23 185380 libsyslog-ng-3.3.5_3.3.5-3_amd64.deb
 6510576f44aed5e78c4631f35865b478dd55eb2e 70368 libsyslog-ng-dev_3.3.5-3_amd64.deb
 9cf34d438e3a4456666ff5635e7b5cb2ea8e0c0a 194586 syslog-ng-core_3.3.5-3_amd64.deb
 4933910106e7a4e0afa24783a9953c74f824f7c8 30878 syslog-ng-mod-json_3.3.5-3_amd64.deb
 88f6818942bf6007b34e7c16e23284305681a5d3 39118 syslog-ng-mod-mongodb_3.3.5-3_amd64.deb
 ae0b627919833d36e0c541e630d2c22468b380c6 44128 syslog-ng-mod-sql_3.3.5-3_amd64.deb
Checksums-Sha256: 
 483a56d7618211a56bfa3c365bfd8afb54fad7d03aa420f7abbf9093064f6163 1907 syslog-ng_3.3.5-3.dsc
 d4e26108ed32103c42e185881913e32c64af95c31c4af3fb54a42a181ae6b6e1 22192 syslog-ng_3.3.5-3.debian.tar.xz
 9079f46bdca644ae4e1ccdf075f0fedd8ffc19508473f9301078a53e71826e3c 28672 syslog-ng_3.3.5-3_all.deb
 723c9847513113626a6aefdcbf7c724d60e51f45d94c8bcf81ab969ecab09c9d 1368704 syslog-ng-dbg_3.3.5-3_amd64.deb
 81d20e49126c76cb492076bf0b4394dfcf15babd5df5c4eec38cb9f8718f1bcc 185380 libsyslog-ng-3.3.5_3.3.5-3_amd64.deb
 45b6f5d7899a9660fb8d1da0aa6a2d8e872f74f329e116fb932f8f6bc8d96d0e 70368 libsyslog-ng-dev_3.3.5-3_amd64.deb
 957b24dc413934f2a496883f10dd43e94fff4af61f146379f8aaf16ac76389df 194586 syslog-ng-core_3.3.5-3_amd64.deb
 437ad6bd586e1f87e76af73a008bea63261042a3f2db97cb5b7b41864eea69ec 30878 syslog-ng-mod-json_3.3.5-3_amd64.deb
 572b4751e8943d60f79e3ec41b33c1f246513d47de67ad1ae8238ad73e7b2dce 39118 syslog-ng-mod-mongodb_3.3.5-3_amd64.deb
 748ec3dd2e56c83f4a6ef0206074d51191b52db17a437fca00f6c9b6a09891de 44128 syslog-ng-mod-sql_3.3.5-3_amd64.deb
Files: 
 4c5a9fe5be6a9a61ea8380f14ba3b35f 1907 admin extra syslog-ng_3.3.5-3.dsc
 91758057cc6a952b2a2821bd1ba592e8 22192 admin extra syslog-ng_3.3.5-3.debian.tar.xz
 4667aaf88a9be1e2eeca8cab326a482e 28672 admin extra syslog-ng_3.3.5-3_all.deb
 794e9a03416b449834dacdd7b477d507 1368704 debug extra syslog-ng-dbg_3.3.5-3_amd64.deb
 fda3f57c1a059de67a0dd4c7555fc056 185380 libs extra libsyslog-ng-3.3.5_3.3.5-3_amd64.deb
 ed49bbf1b860dfa32ab73fcc91444d11 70368 libdevel extra libsyslog-ng-dev_3.3.5-3_amd64.deb
 89a5230d5bdb0670d7e3ae8302b92622 194586 admin extra syslog-ng-core_3.3.5-3_amd64.deb
 d406918ab8e4ce038724046abd43b8c5 30878 admin extra syslog-ng-mod-json_3.3.5-3_amd64.deb
 12fc8112009843835935da954f87df96 39118 admin extra syslog-ng-mod-mongodb_3.3.5-3_amd64.deb
 ca48942fa9b5d6a6b4aa24b4d3f6cc79 44128 admin extra syslog-ng-mod-sql_3.3.5-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlEzq7oACgkQMDatjqUaT90uZACdEyOHIStBTLchzJIlMHXef/V2
a3AAoK4kYlzZEuBgbqFKUsAlj1qqjo63
=h0xi
-----END PGP SIGNATURE-----

Message #127 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 690067@bugs.debian.org, 702195@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Cc: Andreas Beckmann <debian@abeckmann.de>, control@bugs.debian.org, Tollef Fog Heen <tfheen@err.no>, Michael Stapelberg <stapelberg@debian.org>

Subject: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Sun, 03 Mar 2013 22:53:50 +0100

[Message part 1 (text/plain, inline)]

found 690067 3.3.5-3
thanks

I quickly talked to algernon on IRC and did let him know that the
proposed fix to use real conffiles for the systemd symlinks is not good.
symlinks in .wants directories should never be real files.
That will only cause problems in the future.

Specifically the syslog.service symlink, which points to the default
syslog provider, can't be a real file as this will break upgrades from
syslog-ng to rsyslog or vice versa.

I think we should get away with not installing any symlinks in
syslog-ng, and let my auto-enabler [1] do the symlink bits.
Since /etc/systemd/system/syslog.service is a shared ressource between
rsyslog and syslog-ng, this one probably needs some special handling.

Seeing the poor handling of symlinked conffiles, I'm wondering if we
should also remove them for the other affected packages, which do that:

acpid:
 /etc/systemd/system/sockets.target.wants/acpid.socket
avahi-daemon:
 /etc/systemd/system/dbus-org.freedesktop.Avahi.service
 /etc/systemd/system/multi-user.target.wants/avahi-daemon.service
 /etc/systemd/system/sockets.target.wants/avahi-daemon.socket
avahi-dnsconfd:
 /etc/systemd/system/multi-user.target.wants/avahi-dnsconfd.service
hal:
 /etc/systemd/system/dbus-org.freedesktop.Hal.service
live-config-systemd:
 /etc/systemd/system/basic.target.wants/live-config.service
rsyslog:
 /etc/systemd/system/multi-user.target.wants/rsyslog.service
 /etc/systemd/system/syslog.service
syslog-ng-core:
 /etc/systemd/system/multi-user.target.wants/syslog-ng.service
 /etc/systemd/system/syslog-ng.service

I think my auto-enabler should work well enough, until we have proper
tools support in jessie.

Michael, Tollef: any thoughts?


[1]
http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commit;h=d7e5781795296c24f0f311a7227bfb5e86dc51fa
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #134 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 690067@bugs.debian.org, 702195@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Cc: Andreas Beckmann <debian@abeckmann.de>, Tollef Fog Heen <tfheen@err.no>, Michael Stapelberg <stapelberg@debian.org>

Subject: Re: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Sun, 03 Mar 2013 23:00:14 +0100

[Message part 1 (text/plain, inline)]

On 03.03.2013 22:53, Michael Biebl wrote:
> syslog-ng-core:
>  /etc/systemd/system/multi-user.target.wants/syslog-ng.service
>  /etc/systemd/system/syslog-ng.service
> 

Oh, and btw, converting the /etc/systemd/system/syslog.service symlink
to a real file named /etc/systemd/system/syslog-ng.service is broken
too. The name *needs* to be syslog.service as this name is referenced in
other places.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #141 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Michael Biebl <biebl@debian.org>, 702195@bugs.debian.org

Cc: 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>, Andreas Beckmann <debian@abeckmann.de>, control@bugs.debian.org, Tollef Fog Heen <tfheen@err.no>, Michael Stapelberg <stapelberg@debian.org>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Mon, 4 Mar 2013 10:12:32 +0100

[Message part 1 (text/plain, inline)]

On Sun, Mar  3, 2013 at 22:53:50 +0100, Michael Biebl wrote:

> found 690067 3.3.5-3
> thanks
> 
> I quickly talked to algernon on IRC and did let him know that the
> proposed fix to use real conffiles for the systemd symlinks is not good.
> symlinks in .wants directories should never be real files.
> That will only cause problems in the future.
> 
That sounds so terribly wrong...

Cheers,
Julien

[signature.asc (application/pgp-signature, inline)]

Message #146 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 690067@bugs.debian.org, 702195@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Tue, 05 Mar 2013 21:05:07 +0100

[Message part 1 (text/plain, inline)]

On 03.03.2013 22:53, Michael Biebl wrote:
> 
> Seeing the poor handling of symlinked conffiles, I'm wondering if we
> should also remove them for the other affected packages, which do that:
> 
> acpid:
>  /etc/systemd/system/sockets.target.wants/acpid.socket
> avahi-daemon:
>  /etc/systemd/system/dbus-org.freedesktop.Avahi.service
>  /etc/systemd/system/multi-user.target.wants/avahi-daemon.service
>  /etc/systemd/system/sockets.target.wants/avahi-daemon.socket
> avahi-dnsconfd:
>  /etc/systemd/system/multi-user.target.wants/avahi-dnsconfd.service
> hal:
>  /etc/systemd/system/dbus-org.freedesktop.Hal.service
> live-config-systemd:
>  /etc/systemd/system/basic.target.wants/live-config.service
> rsyslog:
>  /etc/systemd/system/multi-user.target.wants/rsyslog.service
>  /etc/systemd/system/syslog.service

After a closer look, all those packages do *not* mark the symlinks as
conffiles, so are not affected by this problem. So I wouldn't suggest
any changes at this stage of the release.
As for syslog-ng-core, I think the simplest solution for wheezy is to
add the symlinks back to the package
/etc/systemd/system/syslog.service
/etc/systemd/system/multi-user.target.wants/syslog-ng.service
but does *not* mark them as conffiles.
+ the usual cleanup of the existing conffiles via preinst.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #151 received at 690067@bugs.debian.org (full text, mbox, reply):

From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

To: Michael Biebl <biebl@debian.org>, 702195@bugs.debian.org

Cc: 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Tue, 05 Mar 2013 22:10:28 +0000

On Tue, 2013-03-05 at 21:05 +0100, Michael Biebl wrote:
> On 03.03.2013 22:53, Michael Biebl wrote:
> > 
> > Seeing the poor handling of symlinked conffiles, I'm wondering if we
> > should also remove them for the other affected packages, which do that:
[...]
> After a closer look, all those packages do *not* mark the symlinks as
> conffiles, so are not affected by this problem. So I wouldn't suggest
> any changes at this stage of the release.
> As for syslog-ng-core, I think the simplest solution for wheezy is to
> add the symlinks back to the package
> /etc/systemd/system/syslog.service
> /etc/systemd/system/multi-user.target.wants/syslog-ng.service
> but does *not* mark them as conffiles.
> + the usual cleanup of the existing conffiles via preinst.
 The first iteration is ready to check[1]. I don't recall previous
conffiles, but on purge the files are removed.

Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc

Message #156 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Dominic Hargreaves <dom@earth.li>

To: 690067@bugs.debian.org

Cc: 690067-submitter@bugs.debian.org

Subject: Re: syslog-ng: diff for NMU version 3.3.6-1.1

Date: Wed, 6 Mar 2013 01:02:38 +0000

On Sun, Mar 03, 2013 at 01:04:32AM +0000, Dominic Hargreaves wrote:
> On Sat, Mar 02, 2013 at 03:57:50PM +0000, Dominic Hargreaves wrote:
> > Dear maintainer,
> > 
> > I've prepared an NMU for syslog-ng (versioned as 3.3.6-1.1) and
> > uploaded it to DELAYED/4. Please feel free to tell me if I
> > should delay it longer.
> 
> Note: this patch does seem to trigger a dpkg prompt about a changed
> config file (since the preinst removes the symlinks). Without the
> preinst doing that, however, the new files don't get installed at
> all.
> 
> At this point I'm not inclined to cancel the NMU, as it's an
> improvement over what we currently have, but I would welcome advice
> on whether it's possible to avoid the dpkg prompt in this edge case.

I'm cancelling this NMU as, although noone replied to me, there
have been various discussions on this bug and others about whether
the fix is correct.

Dominic.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

Message #164 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

Cc: 702195@bugs.debian.org, 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Wed, 06 Mar 2013 13:17:45 +0100

[Message part 1 (text/plain, inline)]

On 05.03.2013 23:10, Laszlo Boszormenyi (GCS) wrote:
> [1] dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc

A couple of comments:

1/ as you no longer mark the symlinks as conffiles, the cleanup in
syslog-ng-core.postrm is not necessary.

2/ you need to remove the existing conffile symlinks in
syslog-ng-core.preinst so dpkg converts it to non-conffiles on upgrades

3/ please drop the line
ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
from syslog-ng.service. The systemd-kmsg-syslogd.service service has
been removed a long time ago and future versions of systemd will
generate an error if you stop a non-existing service. Gergely told he
had this change in his Git repo already.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #169 received at 690067@bugs.debian.org (full text, mbox, reply):

From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

To: Michael Biebl <biebl@debian.org>

Cc: 702195@bugs.debian.org, 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Wed, 06 Mar 2013 17:45:11 +0000

On Wed, 2013-03-06 at 13:17 +0100, Michael Biebl wrote:
> 1/ as you no longer mark the symlinks as conffiles, the cleanup in
> syslog-ng-core.postrm is not necessary.
 Removed.

> 2/ you need to remove the existing conffile symlinks in
> syslog-ng-core.preinst so dpkg converts it to non-conffiles on upgrades
 Remove those in preinst.

> 3/ please drop the line
> ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
> from syslog-ng.service. The systemd-kmsg-syslogd.service service has
> been removed a long time ago and future versions of systemd will
> generate an error if you stop a non-existing service. Gergely told he
> had this change in his Git repo already.
 Line removed, added other fixes from the Git repo.

Please re-check it from:
dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc

Message #174 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

Cc: 702195@bugs.debian.org, 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Wed, 06 Mar 2013 20:44:48 +0100

[Message part 1 (text/plain, inline)]

I'd say, we're almost there

On 06.03.2013 18:45, Laszlo Boszormenyi (GCS) wrote:
> On Wed, 2013-03-06 at 13:17 +0100, Michael Biebl wrote:
> 
>> 2/ you need to remove the existing conffile symlinks in
>> syslog-ng-core.preinst so dpkg converts it to non-conffiles on upgrades
>  Remove those in preinst.

I would add a version check here, so this is not run on every upgrade again.

I'm not sure, if you want to use the same fix for the unstable package.
If so, keep in mind that syslog-ng-core in unstable uses real files. For
simplicities sake, I'd use 3.3.6-3 as minimum fixed version, and don't
check wether it's a symlink or not, since 3.3.6-2 has real files.
For 3.3.6-2 you also want to rm /etc/systemd/system/syslog-ng.service

>> 3/ please drop the line
>> ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
>> from syslog-ng.service. The systemd-kmsg-syslogd.service service has
>> been removed a long time ago and future versions of systemd will
>> generate an error if you stop a non-existing service. Gergely told he
>> had this change in his Git repo already.
>  Line removed, added other fixes from the Git repo.

The wheezy version of systemd doesn't yet support Documentation=, so you
might want to apply this change for unstable only. systemd will skip
unknown fields, so the unit file will work, but it will log a warning like:
 systemd[1]: [/etc/systemd/system/test.service:4] Unknown lvalue
'Documentation' in section 'Unit'. Ignoring

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #179 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

Cc: 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Wed, 06 Mar 2013 21:36:03 +0100

[Message part 1 (text/plain, inline)]

On 06.03.2013 20:44, Michael Biebl wrote:
> I'd say, we're almost there
> 
> On 06.03.2013 18:45, Laszlo Boszormenyi (GCS) wrote:
>> On Wed, 2013-03-06 at 13:17 +0100, Michael Biebl wrote:
>>
>>> 2/ you need to remove the existing conffile symlinks in
>>> syslog-ng-core.preinst so dpkg converts it to non-conffiles on upgrades
>>  Remove those in preinst.
> 
> I would add a version check here, so this is not run on every upgrade again.
> 
> I'm not sure, if you want to use the same fix for the unstable package.
> If so, keep in mind that syslog-ng-core in unstable uses real files. For
> simplicities sake, I'd use 3.3.6-3 as minimum fixed version, and don't
> check wether it's a symlink or not, since 3.3.6-2 has real files.
> For 3.3.6-2 you also want to rm /etc/systemd/system/syslog-ng.service

On second thought, it's probably less confusing if you use
dpkg --compare-versions "$2" lt 3.3.5-3 for testing and
dpkg --compare-versions "$2" lt 3.3.6-3 for unstable as fixed versions

This way wheezy uploads via stable-proposed and security will not
trigger the removal again.

Michael

[dropped the unblock bug from CC for now]
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #184 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

Cc: 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Wed, 06 Mar 2013 22:31:59 +0100

[Message part 1 (text/plain, inline)]

On 06.03.2013 21:36, Michael Biebl wrote:
> On 06.03.2013 20:44, Michael Biebl wrote:
>> I'd say, we're almost there
>>
>> On 06.03.2013 18:45, Laszlo Boszormenyi (GCS) wrote:
>>> On Wed, 2013-03-06 at 13:17 +0100, Michael Biebl wrote:
>>>
>>>> 2/ you need to remove the existing conffile symlinks in
>>>> syslog-ng-core.preinst so dpkg converts it to non-conffiles on upgrades
>>>  Remove those in preinst.
>>
>> I would add a version check here, so this is not run on every upgrade again.
>>

..
> On second thought, it's probably less confusing if you use
> dpkg --compare-versions "$2" lt 3.3.5-3 for testing and

I think something like this should do:
if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt "3.3.5-3"; then
..
fi


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #189 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: "Laszlo Boszormenyi \(GCS\)" <gcs@debian.hu>

Cc: Michael Biebl <biebl@debian.org>, 702195@bugs.debian.org, 690067@bugs.debian.org

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Thu, 07 Mar 2013 15:53:53 +0100

"Laszlo Boszormenyi (GCS)" <gcs@debian.hu> writes:

> On Wed, 2013-03-06 at 13:17 +0100, Michael Biebl wrote:
>> 1/ as you no longer mark the symlinks as conffiles, the cleanup in
>> syslog-ng-core.postrm is not necessary.
>  Removed.
>
>> 2/ you need to remove the existing conffile symlinks in
>> syslog-ng-core.preinst so dpkg converts it to non-conffiles on upgrades
>  Remove those in preinst.
>
>> 3/ please drop the line
>> ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
>> from syslog-ng.service. The systemd-kmsg-syslogd.service service has
>> been removed a long time ago and future versions of systemd will
>> generate an error if you stop a non-existing service. Gergely told he
>> had this change in his Git repo already.
>  Line removed, added other fixes from the Git repo.

I checked just now, and some things were picked from the merge-queue/3.5
branch (the default branch on github), namely Type=notify - that is not
supported by syslog-ng 3.3, and will be new in 3.5.

Other than that, Michael already said what I would've, just better.

-- 
|8]

Message #194 received at 690067@bugs.debian.org (full text, mbox, reply):

From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

To: Michael Biebl <biebl@debian.org>

Cc: 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Sat, 09 Mar 2013 19:27:20 +0000

On Wed, 2013-03-06 at 22:31 +0100, Michael Biebl wrote:
> I think something like this should do:
> if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt "3.3.5-3"; then
> ..
> fi
 Done.

On Thu, 2013-03-07 at 15:53 +0100, Gergely Nagy wrote:
> I checked just now, and some things were picked from the merge-queue/3.5
> branch (the default branch on github), namely Type=notify - that is not
> supported by syslog-ng 3.3, and will be new in 3.5.
 Updated.

It builds fine in Wheezy pbuilder and if you do agree, I'll upload
it[1].

Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc

Message #199 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>, 702195@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>, 690067@bugs.debian.org

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Tue, 12 Mar 2013 18:16:58 +0100

[Message part 1 (text/plain, inline)]

On 09.03.2013 20:27, Laszlo Boszormenyi (GCS) wrote:
> On Wed, 2013-03-06 at 22:31 +0100, Michael Biebl wrote:
>> I think something like this should do:
>> if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt "3.3.5-3"; then
>> ..
>> fi
>  Done.
> 
> On Thu, 2013-03-07 at 15:53 +0100, Gergely Nagy wrote:
>> I checked just now, and some things were picked from the merge-queue/3.5
>> branch (the default branch on github), namely Type=notify - that is not
>> supported by syslog-ng 3.3, and will be new in 3.5.
>  Updated.
> 
> It builds fine in Wheezy pbuilder and if you do agree, I'll upload
> it[1].

looks good to me.
If you want to be extra nice, you can also clean up the
/etc/systemd/system/syslog.service.dpkg-new and
/etc/systemd/system/multi-user.target.wants/syslog-ng.service.dpkg-new
symlinks in preinst.
Those are created, when the target the symlink was pointing to, has
changed, so dpkg thought the "conffile" had changed.
Another reason why it wasn't a good idea to mark the symlinks as
conffiles...

Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #204 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Gilbert <mgilbert@debian.org>

To: 690067@bugs.debian.org

Subject: re: symlink conffiles are not supported

Date: Sun, 17 Mar 2013 16:20:45 -0400

control: tag -1 -patch

Removing tag since there's still ongoing work to actually get the
patch in shape.

Best wishes,
Mike

Message #211 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>, 702195@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>, 690067@bugs.debian.org

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Wed, 20 Mar 2013 11:37:31 +0100

[Message part 1 (text/plain, inline)]

Hi,

Am 12.03.2013 18:16, schrieb Michael Biebl:
> On 09.03.2013 20:27, Laszlo Boszormenyi (GCS) wrote:
>>
>> It builds fine in Wheezy pbuilder and if you do agree, I'll upload
>> it[1].
> 
> looks good to me.

Did you have a chance to prepare the upload in the mean time?

Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #216 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

Cc: 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Mon, 25 Mar 2013 23:23:10 +0100

[Message part 1 (text/plain, inline)]

Hi,

Am 09.03.2013 20:27, schrieb Laszlo Boszormenyi (GCS):
> On Wed, 2013-03-06 at 22:31 +0100, Michael Biebl wrote:
> On Thu, 2013-03-07 at 15:53 +0100, Gergely Nagy wrote:
>> I checked just now, and some things were picked from the merge-queue/3.5
>> branch (the default branch on github), namely Type=notify - that is not
>> supported by syslog-ng 3.3, and will be new in 3.5.
>  Updated.
> 
> It builds fine in Wheezy pbuilder and if you do agree, I'll upload
> it[1].
> 
> Laszlo/GCS
> [1] dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc
> 

are you planning on uploading those fixes to unstable as well?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #221 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

Cc: 690067@bugs.debian.org, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Mon, 25 Mar 2013 23:34:54 +0100

[Message part 1 (text/plain, inline)]

Am 25.03.2013 23:23, schrieb Michael Biebl:
> Hi,
> 
> Am 09.03.2013 20:27, schrieb Laszlo Boszormenyi (GCS):
>> On Wed, 2013-03-06 at 22:31 +0100, Michael Biebl wrote:
>> On Thu, 2013-03-07 at 15:53 +0100, Gergely Nagy wrote:
>>> I checked just now, and some things were picked from the merge-queue/3.5
>>> branch (the default branch on github), namely Type=notify - that is not
>>> supported by syslog-ng 3.3, and will be new in 3.5.
>>  Updated.
>>
>> It builds fine in Wheezy pbuilder and if you do agree, I'll upload
>> it[1].
>>
>> Laszlo/GCS
>> [1] dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc
>>
> 
> are you planning on uploading those fixes to unstable as well?

"those fixes": of course for unstable the preinst has to be changed
accordingly, as those are real files in sid and not symlinks.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #226 received at 690067@bugs.debian.org (full text, mbox, reply):

From: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>

To: Michael Biebl <biebl@debian.org>, 690067@bugs.debian.org

Cc: Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#690067: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Mon, 25 Mar 2013 23:49:16 +0000

On Mon, 2013-03-25 at 23:34 +0100, Michael Biebl wrote:
> Am 25.03.2013 23:23, schrieb Michael Biebl:
> > Am 09.03.2013 20:27, schrieb Laszlo Boszormenyi (GCS):
> >> On Wed, 2013-03-06 at 22:31 +0100, Michael Biebl wrote:
> >> On Thu, 2013-03-07 at 15:53 +0100, Gergely Nagy wrote:
> >>> I checked just now, and some things were picked from the merge-queue/3.5
> >>> branch (the default branch on github), namely Type=notify - that is not
> >>> supported by syslog-ng 3.3, and will be new in 3.5.
> >>  Updated.
> >>
> >> It builds fine in Wheezy pbuilder and if you do agree, I'll upload
> >> it[1].
> >>
> >> Laszlo/GCS
> >> [1] dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc
> >>
> > 
> > are you planning on uploading those fixes to unstable as well?
 Answering your previous mail, -4 is uploaded and accepted to Wheezy by
Julien. I plan to upload the fixes for unstable as well. I wait for the
fix of #703639 [1]. Filed as normal severity, but duplicated messages
after a SIGHUP reload can be RC as well. Algernon could reproduce it
with a minimum configuration. As I know, he is working on the fix.
I would like to wait for it and upload all the fixes at once for Sid and
an other t-p-u for Wheezy.

> "those fixes": of course for unstable the preinst has to be changed
> accordingly, as those are real files in sid and not symlinks.
 It's passed midnight here, so don't count on me; but as far as I
remember, the fix includes a package version check already.

Laszlo/GCS
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703639

Message #231 received at 690067-done@bugs.debian.org (full text, mbox, reply):

From: "Adam D. Barratt" <adam@adam-barratt.org.uk>

To: "Laszlo Boszormenyi (GCS)" <gcs@debian.hu>, <690067-done@bugs.debian.org>

Cc: Michael Biebl <biebl@debian.org>, Gergely Nagy <algernon@balabit.hu>

Subject: Re: Bug#690067: Bug#702195: symlink conffiles are not supported, causing problems for dpkg on upgrade/removal and incorrect debsums reports

Date: Tue, 16 Apr 2013 11:10:51 +0100

Version 3.3.5-4

On 26.03.2013 00:49, Laszlo Boszormenyi (GCS) wrote:
> On Mon, 2013-03-25 at 23:34 +0100, Michael Biebl wrote:
>> Am 25.03.2013 23:23, schrieb Michael Biebl:
>> > Am 09.03.2013 20:27, schrieb Laszlo Boszormenyi (GCS):
>> >> On Wed, 2013-03-06 at 22:31 +0100, Michael Biebl wrote:
>> >> On Thu, 2013-03-07 at 15:53 +0100, Gergely Nagy wrote:
>> >>> I checked just now, and some things were picked from the 
>> merge-queue/3.5
>> >>> branch (the default branch on github), namely Type=notify - that 
>> is not
>> >>> supported by syslog-ng 3.3, and will be new in 3.5.
>> >>  Updated.
>> >>
>> >> It builds fine in Wheezy pbuilder and if you do agree, I'll 
>> upload
>> >> it[1].
>> >>
>> >> Laszlo/GCS
>> >> [1] dget -x http://www.barcikacomp.hu/gcs/syslog-ng_3.3.5-3.dsc
>> >>
>> >
>> > are you planning on uploading those fixes to unstable as well?
>  Answering your previous mail, -4 is uploaded and accepted to Wheezy 
> by
> Julien.

Thus marking as fixed in that version.

Regards,

Adam

Message #238 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: 690067@bugs.debian.org

Subject: #690067: This problem is still present in 3.3.9-1

Date: Mon, 27 May 2013 13:11:35 +0200

Control: found -1 3.3.9-1

This problem was fixed in Wheezy, but the same fixes should be applied
to 3.3.9-1 aswell in order to fix it in unstable too.

-- 
|8]

Message #245 received at 690067@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: 690067@bugs.debian.org, 713982@bugs.debian.org

Subject: pending

Date: Tue, 02 Jul 2013 14:20:14 +0200

Control: tag -1 pending

I adapted the patch sent for #713982, the change is available in git[1],
so the next syslog-ng upload will use dh-systemd, and have all the
remaining systemd-related shortcomings fixed.

 [1]: https://github.com/algernon/syslog-ng/commits/packaging/debian/3.3

Thanks a lot for the patches and the help!

(It will likely take a few more days to upload syslog-ng, and it will
have to go through NEW as well.)

-- 
|8]

Message #252 received at 690067-close@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@madhouse-project.org>

To: 690067-close@bugs.debian.org

Subject: Bug#690067: fixed in syslog-ng 3.5.1-1

Date: Mon, 04 Nov 2013 18:00:06 +0000

Source: syslog-ng
Source-Version: 3.5.1-1

We believe that the bug you reported is fixed in the latest version of
syslog-ng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 690067@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gergely Nagy <algernon@madhouse-project.org> (supplier of updated syslog-ng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 04 Nov 2013 15:27:37 +0100
Source: syslog-ng
Binary: syslog-ng syslog-ng-dbg syslog-ng-dev syslog-ng-core syslog-ng-mod-json syslog-ng-mod-mongodb syslog-ng-mod-sql syslog-ng-mod-smtp syslog-ng-mod-amqp syslog-ng-mod-geoip syslog-ng-mod-redis syslog-ng-mod-stomp
Architecture: source amd64 all
Version: 3.5.1-1
Distribution: unstable
Urgency: low
Maintainer: syslog-ng maintainers <syslog-ng-maintainers@lists.alioth.debian.org>
Changed-By: Gergely Nagy <algernon@madhouse-project.org>
Description: 
 syslog-ng  - Next generation system logging daemon (metapackage)
 syslog-ng-core - Next generation system logging daemon (core)
 syslog-ng-dbg - Next generation system logging daemon (debug symbols)
 syslog-ng-dev - Next generation system logging daemon (development files)
 syslog-ng-mod-amqp - Next generation system logging daemon (AMQP plugin)
 syslog-ng-mod-geoip - Next generation system logging daemon (GeoIP plugin)
 syslog-ng-mod-json - Next generation system logging daemon (JSON plugin)
 syslog-ng-mod-mongodb - Next generation system logging daemon (MongoDB plugin)
 syslog-ng-mod-redis - Next generation system logging daemon (Redis plugin)
 syslog-ng-mod-smtp - Next generation system logging daemon (SMTP plugin)
 syslog-ng-mod-sql - Next generation system logging daemon (SQL plugin)
 syslog-ng-mod-stomp - Next generation system logging daemon (STOMP plugin)
Closes: 650814 690067 699942 713982 714254 719910 722746
Changes: 
 syslog-ng (3.5.1-1) unstable; urgency=low
 .
   [ Gergely Nagy <algernon@madhouse-project.org> ]
   * New upstream release.
     + Support auto-loading modules (Closes: #650814)
     + The SMTP module is available in syslog-ng-mod-smtp (Closes: #722746)
     + New modules: amqp, geoip, stomp, redis and smtp.
     + Multi-line input support (indented multiline and regexp-based)
     + Template type hinting for the MongoDB destination and $(format-json)
     + Support for unit suffixes in the configuration file
     + New filters, template functions and other miscellaneous changes
   * New (team) maintainer, Laszlo Boszormenyi, Attila Szalay and myself
     added to Uploaders.
   * Ship /var/lib/syslog-ng in the syslog-ng-core package, instead of
     creating it in the init script. Thanks Michael Biebl
     <biebl@debian.org> for the report & assistance. (Closes: #699942, #719910)
   * Use dh-systemd for proper systemd-related maintainer scripts. Based on
     a patch by Michael Biebl <biebl@debian.org>. (Closes: #713982,
     #690067)
   * Do not wait for syslog-ng to settle down during installation / update.
     This also fixes installing via debootstrap and a fake
     start-stop-daemon. (Closes: #714254)
Checksums-Sha1: 
 f683ae07c19794972f03213c5d162a5e58b0cb48 3139 syslog-ng_3.5.1-1.dsc
 7fe9beed612876c84eb021fe928491cfc4299744 695276 syslog-ng_3.5.1.orig.tar.xz
 52b32798fe31a65395d9d0fd88aebf4f0a306e0a 36200 syslog-ng_3.5.1-1.debian.tar.xz
 2e0fa688bbb4404c1f8b39d53d41bb9762aeb8d0 1742024 syslog-ng-dbg_3.5.1-1_amd64.deb
 a7bd31e0543c505f76ae1e15a759a386f80e1324 71728 syslog-ng-dev_3.5.1-1_amd64.deb
 c83a1dc1accc04567412fdd872cbd4c6c350820c 364310 syslog-ng-core_3.5.1-1_amd64.deb
 6a91f5fb132f58275f95997a8671a3a4efdfad82 32790 syslog-ng-mod-json_3.5.1-1_amd64.deb
 e46c9c75a9798a95ab0150ff8e2032d066192526 34702 syslog-ng-mod-mongodb_3.5.1-1_amd64.deb
 e24a989a73e95d9e90d6a8b3db7125a98274af27 38410 syslog-ng-mod-sql_3.5.1-1_amd64.deb
 5c29541be700b426873aa6b6524c08df8ae15cb1 32866 syslog-ng-mod-smtp_3.5.1-1_amd64.deb
 1e73c9c754b54d3037c2ea4896f74ef34cc04b4f 57246 syslog-ng-mod-amqp_3.5.1-1_amd64.deb
 4ac6e4d5169c802a188bc9d7d3a5ea10cd40de81 24336 syslog-ng-mod-geoip_3.5.1-1_amd64.deb
 787c02c5896cb5e1a2ad7b9792e0d1d30adc4504 31426 syslog-ng-mod-redis_3.5.1-1_amd64.deb
 6c41b2aad5d30910caed30edabd39ceca8265d59 35182 syslog-ng-mod-stomp_3.5.1-1_amd64.deb
 e60c76b3c9245071329974091c7f3e3bba7768a5 22660 syslog-ng_3.5.1-1_all.deb
Checksums-Sha256: 
 392e332dd434ab96ba3967894e8f9568d6a0b6ea0ba6a9bc948ff3c768c251dc 3139 syslog-ng_3.5.1-1.dsc
 dc378e9a09e5349401ca69dcda7c715c1ec2a596d62c2043ccc8d4cd182e44d7 695276 syslog-ng_3.5.1.orig.tar.xz
 39ea71e8d484f20a5e4ba4cebb78e21e242c31ea67bdc3b358d5943354b08332 36200 syslog-ng_3.5.1-1.debian.tar.xz
 23db8ad6ddb136de32c96bd927b0be1bbae2ccf32e9721929803164d660822d3 1742024 syslog-ng-dbg_3.5.1-1_amd64.deb
 7e5986d24858293258b1a6bfa7b15d4c4747ef3d713129b348e311f4350436fb 71728 syslog-ng-dev_3.5.1-1_amd64.deb
 f4d333e289a9f3a0cd9ce02f4a9d4d3a574ef92683cca22397b49915daf1e2f5 364310 syslog-ng-core_3.5.1-1_amd64.deb
 7d94e8820f7988bb48c30de87bd3ab6bdf9ab3a43c8ed18d534e41631b46e139 32790 syslog-ng-mod-json_3.5.1-1_amd64.deb
 a2afb1391a05c1a37ea139d79fe7840b099a97bd63e3a80df9e20e96c3eab317 34702 syslog-ng-mod-mongodb_3.5.1-1_amd64.deb
 251e8ac5e0deebbec8bf04ee0c4c7af58511ba703acee211c7e3cb3f2ba16e55 38410 syslog-ng-mod-sql_3.5.1-1_amd64.deb
 536821a39e443530577e87a03411c0ab02fff0994374e58e37a18edf09de89ba 32866 syslog-ng-mod-smtp_3.5.1-1_amd64.deb
 cc9dbddc9adc3c22b5d7db1108f783afad93f9108072c869e81adf11b0097b17 57246 syslog-ng-mod-amqp_3.5.1-1_amd64.deb
 9483d118e4ccda0c0b1b23fc961c099f2b004dd00d70a1ead0adc8b83334e324 24336 syslog-ng-mod-geoip_3.5.1-1_amd64.deb
 7859f39c8138a9842b79fc94eb65e09b89e810462e6987e37d034fc61230d513 31426 syslog-ng-mod-redis_3.5.1-1_amd64.deb
 40685bba12e1fef2c7cc441f74e55a569b88e221d87945426516833daee452ee 35182 syslog-ng-mod-stomp_3.5.1-1_amd64.deb
 c2b922987a865d0e938e43c1b718066d2389357ef773f0db3dd9e146d491c89c 22660 syslog-ng_3.5.1-1_all.deb
Files: 
 6578238409d03cae7319423d94f625f9 3139 admin extra syslog-ng_3.5.1-1.dsc
 f725e666a805dd2b1c109848ad92041b 695276 admin extra syslog-ng_3.5.1.orig.tar.xz
 3f3e299969a89a803f9a8ba7872f1653 36200 admin extra syslog-ng_3.5.1-1.debian.tar.xz
 5c39cfacd967d53c4dff2c1dbc77daed 1742024 debug extra syslog-ng-dbg_3.5.1-1_amd64.deb
 416e0d6f9b5476df9dad16bd413776d7 71728 libdevel extra syslog-ng-dev_3.5.1-1_amd64.deb
 9bc40ec8c24408dc665ca02af5b4d263 364310 admin extra syslog-ng-core_3.5.1-1_amd64.deb
 95a4ac994ba87c04dd64d94f6a4a65ae 32790 admin extra syslog-ng-mod-json_3.5.1-1_amd64.deb
 c68a0600b07b9d4b51eeb32bacd2ce05 34702 admin extra syslog-ng-mod-mongodb_3.5.1-1_amd64.deb
 146f7691c62af35c6fea7ec71f09bfed 38410 admin extra syslog-ng-mod-sql_3.5.1-1_amd64.deb
 9f5dd6476eba7bd93807e179c0642374 32866 admin extra syslog-ng-mod-smtp_3.5.1-1_amd64.deb
 2ad7763beeee4ff484352e8423e8d9f5 57246 admin extra syslog-ng-mod-amqp_3.5.1-1_amd64.deb
 0a3f800cc783bac9ba362b43c2477f5e 24336 admin extra syslog-ng-mod-geoip_3.5.1-1_amd64.deb
 7939bdf82db1b101c86abe0b490f7451 31426 admin extra syslog-ng-mod-redis_3.5.1-1_amd64.deb
 06405f5f09c2b97014fe55a43adc26ca 35182 admin extra syslog-ng-mod-stomp_3.5.1-1_amd64.deb
 9ab0c5a993b983dc5f448b21589b7685 22660 admin extra syslog-ng_3.5.1-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBAgAGBQJSd72WAAoJEKwekLrEM/aPI7gQAJLX/7JKAowE+ipV3W5aVLpm
ZVtWh1ML1uQpX9dghIxP0555I3k4FVDxRHobPHpQzV+G1CHUCMHmVxBCDupef2rM
6cy+ItZ2CyfTdNMrGsToxMdW79cNZec0EW1U2uFJgd/Q2eSSRaD5ZnhsRbgVpx0e
7RvvGu/p/60fV63G2qG61Bq6ro/7/ZNfmx3L8+dsaHu7jEJ4breRt5lk2O7YOQcQ
geaNGrehgWDPWgBiv7Rb3+8Z+t8RvrRwtlC6JXZq8fglcbwXz6q1m4EejvuearO+
Of292ocKaTqauH8wiTU22b7qZQPhvTu0KA2V/L79kTt564Qs0wBykl9zminASIlO
bTI+zr/l0l+nSWOg5wD7mnkEsLJp30Z+CJuibq1HPxtScZPjKjSBGSGLhZHk9Vnc
LEmou8BTkQzrzuKHENaxrHq84iDly1/KyxSkHwiUcOACUdCT41AABcUE1XU1SBoB
Gqa8+A87NTTQuU9adxea47G1yqkg9PBYEwmhWEf54/dnsW4CNqt5zoPIUe/vFhCJ
hiNA2vFJ6BUpB7uLmmJigNKcC6Clo04RLOlQbGmx/xbBLd6KLr5sKShowY8Cj4Eo
7JSxcS+LhAVs5Ffa1v95QH1T8TYsVYgS4ZwTS4oxRNqI9ruBjLZHueMEWmJR9tpS
AYlegxTXZEnEQWzD2A+5
=cPZe
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.