Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Please remove $Id$ from config files (Richard Kettlewell)
2. Re: Please remove $Id$ from config files (Grant Taylor)
3. Re: Please remove $Id$ from config files (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Mon, 18 Feb 2019 07:52:15 +0000
From: Richard Kettlewell <[email protected]>
To: [email protected]
Subject: Please remove $Id$ from config files
Message-ID: <[email protected]>
Content-Type: text/plain
Each time INN upgrades on my Debian systems I get redundant config file
update queries from dpkg. For example:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
inn2 inn2-dev inn2-inews libjs-sphinxdoc nbd-client
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,749 kB of archives.
After this operation, 9,216 B disk space will be freed.
Do you want to continue? [Y/n] y
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 227408 files and directories currently installed.)
Preparing to unpack .../inn2_2.6.3-1_amd64.deb ...
Unpacking inn2 (2.6.3-1) over (2.6.2-1+b1) ...
Preparing to unpack .../inn2-dev_2.6.3-1_amd64.deb ...
Unpacking inn2-dev (2.6.3-1) over (2.6.2-1+b1) ...
Preparing to unpack .../inn2-inews_2.6.3-1_amd64.deb ...
Unpacking inn2-inews (2.6.3-1) over (2.6.2-1+b1) ...
Preparing to unpack .../libjs-sphinxdoc_1.8.4-1_all.deb ...
Unpacking libjs-sphinxdoc (1.8.4-1) over (1.8.3-2) ...
Preparing to unpack .../nbd-client_1%3a3.19-3_amd64.deb ...
Unpacking nbd-client (1:3.19-3) over (1:3.19-2) ...
Setting up libjs-sphinxdoc (1.8.4-1) ...
Setting up inn2-dev (2.6.3-1) ...
Setting up inn2-inews (2.6.3-1) ...
Configuration file '/etc/news/inn.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** inn.conf (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/news/inn.conf 2017-11-15 20:20:19.006138000 +0000
+++ /etc/news/inn.conf.dpkg-new 2019-02-17 16:52:36.000000000 +0000
@@ -1,4 +1,4 @@
-## $Id: inn.conf.in 10049 2016-08-05 11:40:25Z iulius $
+## $Id: inn.conf.in 10301 2018-11-11 14:42:17Z iulius $
##
## inn.conf -- INN configuration data
##
@@ -18,10 +18,10 @@
# defaults generated by configure may be reasonable.
mta: "/usr/sbin/sendmail -oi -oem %s"
-organization: "A wobbly pile of bits running InterNetNews"
+organization: "A poorly-installed InterNetNews site"
ovmethod: tradindexed
hismethod: hisv6
-pathhost: deodand.anjou.terraraq.org.uk
+pathhost: server.example.net
pathnews: /usr/lib/news
#runasuser:
@@ -29,10 +29,11 @@
Essentially no other software has the same issue. It's just a waste of
time. Please could the $Id$ lines be removed from the INN configuration
files.
ttfn/rjk
------------------------------
Message: 2
Date: Mon, 18 Feb 2019 13:04:39 -0700
From: Grant Taylor <[email protected]>
To: [email protected]
Subject: Re: Please remove $Id$ from config files
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 2/18/19 12:52 AM, Richard Kettlewell wrote:
> Each time INN upgrades on my Debian systems I get redundant config file
> update queries from dpkg. For example:
?
> Essentially no other software has the same issue. It's just a waste of
> time. Please could the $Id$ lines be removed from the INN configuration
> files.
This seems to be like it's not a problem / bug with INN. Or rather it
seems like an issue with how the Debian package is handling what comes
from the INN source code.
As such, I'd think that taking this up with the Debian package
maintainer would be a better place to start.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4008 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20190218/94c0a983/attachment-0001.bin>
------------------------------
Message: 3
Date: Mon, 18 Feb 2019 13:32:01 -0800
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Please remove $Id$ from config files
Message-ID: <[email protected]>
Content-Type: text/plain
Grant Taylor <[email protected]> writes:
> This seems to be like it's not a problem / bug with INN. Or rather it
> seems like an issue with how the Debian package is handling what comes
> from the INN source code.
> As such, I'd think that taking this up with the Debian package
> maintainer would be a better place to start.
It's fallout from a fairly reasonable approach Debian takes with
configuration files, and doing something better (three-way merges, like
ucf does) also carries a rather high complexity cost.
Are the $Id$ strings in configuration files useful to anyone?
The version control world has generally moved on from VCS markers like
$Id$, in part because Git doesn't support them without pretty awful hacks,
they make three-way merges excessively complicated, and there are
reasonable philosophical objections to either modifying files during the
commit process or, as Subversion does, having one's checked-out files be
different than the contents of the repository.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 112, Issue 2
*******************************************
