Your message dated Tue, 16 Apr 2013 11:10:51 +0100
with message-id <500a3ff77dfaa3d81e4f409dbbbd1...@mail.adsl.funky-badger.org>
and subject line Re: Bug#690067: Bug#702195: symlink conffiles are not
supported, causing problems for dpkg on upgrade/removal and incorrect debsums
reports
has caused the Debian Bug report #690067,
regarding symlink conffiles are not supported, causing problems for dpkg on
upgrade/removal and incorrect debsums reports
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
690067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.16.8
Severity: important
User: debian...@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
--- End Message ---
--- Begin Message ---
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
--- End Message ---
