Marc Sherman wrote:
My worry there is that listchanges.conf is owned by another package,
though it doesn't appear to be a conffile. Does that mean that you're
allowed to write to it in your maintainer scripts? I'm not sure.
Really, listchanges.conf should be listchanges.d, which each [foo]
se
On Tue, Mar 22, 2005 at 01:18:41PM -0500, Marc Sherman wrote:
> Colm MacCarthaigh wrote:
> >On this front, I've been thinking it would be better to use
> >apt-listchanges --profile option, ie use --profile=apticron and allow
> >end-users to pick the output they desire that way. with defaults
> >som
Colm MacCarthaigh wrote:
On this front, I've been thinking it would be better to use
apt-listchanges --profile option, ie use --profile=apticron and allow
end-users to pick the output they desire that way. with defaults
somewhat like:
[apticron]
which=both
headers=1
I presum
On this front, I've been thinking it would be better to use
apt-listchanges --profile option, ie use --profile=apticron and allow
end-users to pick the output they desire that way. with defaults
somewhat like:
[apticron]
which=both
headers=1
I presume such a solution woul
Package: apticron
Version: 1.1.7
Severity: normal
Congratulations on finally getting this into the archive! :)
apt-listchanges should have the following additional command-line
switches:
--which=both --headers
The first is already the default, but it should be specified on the cmd
line in case
5 matches
Mail list logo