Woops, I forgot the attachment. Here it is.
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd";>
sample
John
Doe
sample
1
Sample
sample
FOO'BAR
Package: docbook-xml
Version: 4.5-13
Severity: normal
1. Save the attached file as sample.xml.
2. Run `xsltproc
/usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl sample.xml`
3. Observe that the output file sample.1 has this in it: `.SH "FOO\*(AQBAR"`
That should be `\*(Aq` rathe
I am confused about why this is filed against apt-listchanges rather
than apt. It's apt that's generating the error message when the
apt-listchanges command exits with a non-zero status. There's no way
apt-listchanges can influence what the error looks like; if we want it
to be prettier, we'll
This will be fixed in the next release of apt-listchanges to unstable.
apt-listchanges no longer calls less by default, it calls
sensible-pager. It feels to me like perhaps settings LESSSECURE should
be sensible-pager's job if anybody is going to do it, not
apt-listchanges's job. What do you think?
This will be fixed in the next release of apt-listchanges to unstable,
tentatively version 4.0, which is hopefully coming soon.
Control: reassign -1 apt
The timing of when apt-listchanges gets called vs. when packages get
installed is controlled by apt, not by apt-listchanges. While it would
certainly be possible to add an option to apt to call apt-listchanges
after rather than before the upgrade, and to omit the --con
The next release of apt-listchanges completely overhauls how it
determines which changelog and NEWS entries are displayed to users. The
overhaul addresses the issue identified in this bug.
Control: retitle -1 apt-listchanges should put separate version numbers
in seen DB for each binary package
It doesn't seem like adding a sanitise mode (or a sanitize mode for
those of us on this side of the pond ;-) ) is the right answer here.
Rather, I think we need to understand what is fail
Hmm.
A program should stop with an error when it encounters an error
condition (a) which is unexpected, (b) it doesn't know how to recover
from, and (c) action by the user is probably necessary to fully resolve
(in fact, (c) is a bonus; (a) and (b) are probably sufficient to justify
stopping
Thanks for the bug report and patch, will fix.
Do you want to be credited for the fix in the changelog, and if so, how
do you want to be identified?
I am not sure I agree with this.
Sure, when apt-listchanges is running out of apticron or
unattended-upgrades it should use the system locale, and indeed I assume
it does in those contexts. But it seems arguably correct to me that if
it is being run by a user who has it configured to send emai
I have a fix pending which merges changelog entries which are _entirely_
identical, which I implemented as part of addressing bug #383803, but I
gather that fix won't work here. If I'm understanding correctly, the
issue discussed here is the content of the changelog entry being
identical but th
Package: apt-listchanges
Version: 3.27
Severity: normal
The --filter option to apt-listchanges (and the corresponding
configuration file system), which is intended to be used with the log
frontend, can't possibly work. It causes a crash with a traceback when
it is used because the code to implemen
Package: apt-listchanges
Version: 3.27
Severity: normal
Under the documentation for the --which option in the apt-listchanges
man page, it claims, "The default is to display only news." I agree
that this _should_ be the default, but in fact it does not appear to
be. With no configuration changes t
Package: anacron
Version: 2.3-30
Tags: patch
There is a typo in the log message generated by anacron when it can't
send email. It says "ststus" when it should say "status".
>From 2c1a21af2eb173119187489e55605f1ec292d728 Mon Sep 17 00:00:00 2001
From: Jonathan Kamens
16 matches
Mail list logo
