I wish to limit my testing role as each time I start X, there's
the snap/crackle/pop ... if my mountaintop terminal blows, I must make
a two day journey to the city to buy a new one.
Also as I use the terminal then the laptop, then the terminal, with a
two day gap between each, full testing would
Package: pdftohtml
Severity: minor
The file temporarily in
http://jidanni.org/test/pdfbug.pdf
can be read with
$ xpdf -opw '' pdfbug.pdf
However,
$ pdftohtml -opw '' pdfbug.pdf
gives
Error: Incorrect password
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Package: poppler-utils
Version: 0.5.4-6.1
Severity: minor
The file temporarily in
http://jidanni.org/test/pdfbug.pdf
can be read with
$ xpdf -opw '' pdfbug.pdf
However,
$ pdftotext -opw '' pdfbug.pdf
just makes a one byte file.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
After
The following command starts scim in daemon mode, using the
simple configure module, Pinyin IM engine module,
X11 frontend module:
scim -c simple -e pinyin -f x11 --no-socket -d
perhaps add:
In fact, those are the current default options, so the
OK. I give up. I'm so stupid, the only way I can type ， or 。 in
chewing is CTRL-0 1 and CTRL-0 3.
D == Derek B Noonburg [EMAIL PROTECTED] writes:
D On 5 Sep, [EMAIL PROTECTED] wrote:
Perhaps you can look at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440747
even thought it might not be your fault :-)
D Looks like font subsets without any useful encoding info.
I see, no matter what
D (converting text to Unicode) doesn't work, and your choice of output
D text encoding doesn't matter at all.
I see. The reason I can still read the electric bill using xpdf is
it must be stored in some wasteful image-like format, but not
a pdfimages kind of image. OK.
And if a chars are to be
(By the way there's also
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440746 but that is a
pdftohtml bug, so never mind.)
Last I checked, pdftohtml was based on an old version of Xpdf (version
2.x), and was no longer being maintained. My guess would be that
there's some bug in the
Package: grep
Version: 2.5.3~dfsg-1
Severity: normal
In http://lists.gnu.org/archive/html/bug-grep/2007-08/msg00027.html
but nobody replied, so must be a Debian bug.
$ printf Me\\nji\\n|LC_ALL=zh_TW.utf8 egrepMe\|ji
Me
ji
$ printf Me\\nji\\n|LC_ALL=zh_TW.utf8 egrep -i Me\|ji
ji
$ printf
Thanks, however I dare not test if the bug is still there, as I would
certainly damage my website. Please test it for me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: spamassassin
Version: 3.2.1-1
Severity: wishlist
Removing spamassassin ...
SpamAssassin Mail Filter Daemon: disabled, see /etc/default/spamassassin
Purging configuration files for spamassassin ...
dpkg - warning: while removing spamassassin, directory
YGAN If this sounds OK, this bug is probably a wontfix.
You're the boss. My head is 1 miles away these days.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hurmf, compared to
# #448494: fontconfig: Latest upgrade broke antialiasing in Qt4 apps.
# #448504: fontconfig: Some fonts won't render correctly after upgrade to
2.4.91-1
where one can still read all the ASCII, some Chinese characters (one
out of 200 perhaps) can't even be read. They have to be
Package: fontconfig
Version: 2.4.91-1
All I know is
Preparing to replace fontconfig 2.4.2-1.4 (using
.../fontconfig_2.4.91-1_i386.deb) ...
Cleaning up font configuration of fontconfig...
Cleaning up category cid..
Cleaning up category truetype..
Cleaning up category type1..
Package: gimp
Version: 2.4.0-2
Severity: wishlist
Saw message:
(gimp:8994): Gimp-Tools-CRITICAL **: gimp_tool_set_active_modifier_state:
assertion `display == tool-focus_di
play' failed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Duh, OK
# dpkg -i libfontconfig1_2.4.2-1.2_i386.deb
dpkg - warning: downgrading libfontconfig1 from 2.4.91-1 to 2.4.2-1.2.
# dpkg -i libfontconfig1-dev_2.4.2-1.2_i386.deb
dpkg - warning: downgrading libfontconfig1-dev from 2.4.91-1 to 2.4.2-1.2.
P.S. Looks like those packages also lost baggage.
Darn, I wanted to install something unrelated but
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
libfontconfig1: Depends: fontconfig-config (= 2.4.91-1) but 2.4.2-1.2 is to
be installed
E: Unmet dependencies. Try 'apt-get -f install'
KP Yeah, looking at the two images it's fairly clear that you're using a
KP different font for chinese in the new environment. Check your terminal
KP configuration to see which font family it's using, then compare
my terminal, uxterm is fine, iceweasel is what suffers.
KP $ fc-match
Package: xdm
Version: 1:1.1.6-3
Severity: wishlist
I noticed something this time while happening to be starting at the
screen when xdm starts:
*Twice* during the oh, two seconds that xdm takes to start, the screen
has this being powered off look to it, where there is this tide of
powered off
edit- preferences-Content-Fonts Colors-Advanced
KP It's probably just set to 'Sans Serif', in which case running
Indeed, I see a lot of Sans Serif in there. I can even
$ grep something ~/.mozilla/firefox/*/some_file if you wish.
KP $ fc-match 'Sans Serif'
KP on each version of fontconfig will
AP Could you give me a bit more information about this? What were you doing
AP when the warning happened?
I chose rectangle select, and when I finally release the mouse after
pulling out the rectangle, that message pops up.
AP Were you prevented from doing anything?
No. Just looks bad in the
OK, we look at this line
其他訴求，例如，工寮材 料放寬認定為鐵皮及烤漆板、
attachment: c.png
e.g.,寬 and 烤 look ugly
KP Can you attach before and after pictures? Can you explain which Chinese
KP font you are using? Can you attach runs of
KP $ FC_DEBUG=1 xfd -fa family-name
I don't know what fonts I'm using. All I know
File: /usr/share/man/man1/checkinstall.1.gz
Package: checkinstall
Version: 1.6.1-4
Severity: wishlist
Perhaps note on the man page that the program must be run as root, and
therefore also move the man page to section 8 of the manual.
Or mention when to run and not run as root.
Also give an
KP Looks like your locale doesn't include a territory; fontconfig will
KP select an appropriate type of character (tradtional/simplified) based on
KP the territory in your locale. If your territory is set to something
KP other than cn, hk, mo, sg or tw, then fontconfig won't know the which
KP type
By the way
$ cat /tmp/test.html
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN
http://www.w3.org/TR/html4/strict.dtd;
html
head
titleTEST/title
meta http-equiv=Content-Type content=
text/html; charset=utf-8
/head
body
p
其他訴求，例如，工寮材
料放寬認定為鐵皮及烤漆板、
租地內灌溉水塔或水
池施設、租地內墳墓、/p
/body
/html
$
Indeed, one needs both
set realname=
my_hdr From: [EMAIL PROTECTED]
if one wishes to have just
From: [EMAIL PROTECTED]
on outgoing messages from any machine, I find.
This should be documented.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Package: mutt
Version: 1.5.16-3
Severity: wishlist
14. User defined headers in the manual makes one think one can do
my_hdr From: [EMAIL PROTECTED]
When in fact one needs to do
set realname=
if one wants to get rid of their English name from outgoing mail and
just say From: [EMAIL PROTECTED]
Package: general
Severity: wishlist
This message made by several programs is misleading:
# ed /etc/fonts/conf.d/61-traditional.conf
/etc/fonts/conf.d/61-traditional.conf: No such file or directory
q
# ls /etc/fonts/conf.d/61-traditional.conf
ls: /etc/fonts/conf.d/61-traditional.conf: No such
Right you are, the /etc/fonts/conf.d/61-traditional.conf fixed it.
More effective than meta http-equiv=Content-Language
content=zh-tw. Of course please do one day remind me to remove
61-traditional.conf when a real fix comes. OK, will be back to
test more on Nov. 6
--
To UNSUBSCRIBE, email to
I guess what bothers me is
# ed /etc/fonts/conf.d/61-traditional.conf
/etc/fonts/conf.d/61-traditional.conf: No such file or directory
makes me need to check do I need to create the directory? instead of
just proceeding to edit the file.
$ vi /zzz/qqq is worse. It only checks when it's time to
LC You can still create the necessary directories before closing the
LC editor if writing the file doesn't succeed...
Yes, but it is quite a shock to learn at that late stage.
Now #448593.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
I don't quite get why it would be a shock as you can still create
the necessary directories before trying to save a second time...
Not e.g., if you don't have permissions to write where you intended.
You now are in the perilous state of have a lot of code typed and not
saved and waiting for
Package: linux-2.6
Similar to 437420, which you have surely forgotten.
Removing linux-image-2.6.22-1-686 ...
Purging configuration files for linux-image-2.6.22-1-686 ...
rmdir: /lib/modules/2.6.22-1-686: Directory not empty
dpkg - warning: while removing linux-image-2.6.22-1-686, directory
There I was,
$ xpdf files*.pdf
Enter Passwd [...]
And when I hit q, it was like nobody cared I had put more than one
file on the command line. And it turns out passwords also have nothing
to do with this ... old bug.
So why not do e.g.,
$ xpdf files*.pdf
xpdf: Holmes, this is not less(1), please
I also notice some ^K's sometimes. Here I have replaced them with
ASCII ^+K, The other chars are normal UTF-8 Chinese.
當下，想想，試著回答這些問題: ^K1.說出世界上最富裕的5個人。BR
2.說出上5屆環球小姐比賽中的得勝者。BR
3.說出上5屆諾貝爾獎的得獎者。 ^K.說出上5屆奧斯卡的最佳演員。BR
X-debbugs-CC: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED]
Package: xterm
Version: 229-1
Some very common Chinese characters, e.g., the first of
$ echo 絕對|
perl -C -nwe 'use Unicode::Normalize q(decompose); print decompose($_)'
絕對
are missing from what font xterm uses, and are as shown
X-Debbugs-No-Ack: please
Package: apt
Version: 0.7.9
Severity: wishlist
I notice the modification date of /var/lib/apt/lists/*_Packages is
frozen for no good reason and does not reflect the freshness of that
file's contents, under your new Diffs updating system.
No big deal you might say, but
X-Debbugs-No-Ack: please
Package: apt
Version: 0.7.9
Severity: wishlist
Poking around /etc/apt with ls -o,
/etc/apt:
drwxr-xr-x 2 root 1024 Nov 7 01:11 apt.conf.d
-rw--- 1 root0 Jan 23 2007 secring.gpg
-rw-r--r-- 1 jidanni 491 Nov 7 01:25 sources.list
drwxr-xr
X-Debbugs-No-Ack: please
Package: fetchmail
Version: 6.3.8-10
Severity: wishlist
I discovered installing fetchmail also starts it.
I have START_DAEMON=yes in /etc/default/fetchmail, so I can use
/etc/init.d/fetchmail start when I please.
* File /etc/default/fetchamil has been added to stablish
N Maybe I misunderstood you, but what is the bug or the wish?
N Fetchmail does not start again if it is already started:
I meant _upon apt-get upgrade_, currently you probably do:
1. stop any running daemons
2. install new version
3. restart according to your rules
instead you should
0. make a
Package: klogd
Version: 1.5-1
Severity: wishlist
The only files in /etc/default with the executable bit set are
drwxr-xr-x 2 root 2048 2007-11-07 01:19 .
drwxr-xr-x 107 root 8192 2007-11-07 01:49 ..
-rwxr-xr-x 1 root 289 2006-05-25 17:38 klogd
-rwxr-xr-x 1 root 186 2006-05-25 17:38
Another common missing char is
$ echo 鄉|uni2ascii
0x9109
N And where is the difference apart from the note in /tmp for
N which I fail to see the use?
Then one need not say
START_DAEMON=yes
to be able to say
/etc/init.d/fetchmail start.
If one does not want
/etc/init.d/fetchmail start
to work, then one should just not invoke
/etc/init.d/fetchmail
T ...in a UTF-8 locale, I see the second character of the first number is
T colored incorrectly.
Yes. Glad to see my bug is in good hands.
okcolors.html is OK.
T actually there's a glitch that I see on the right-margin of the first
T line (locale en_US.UTF-8)
Glad to see my bug is in great
Package: scim-chewing
Version: 0.3.1-2
Severity: normal
KB_HANYU_PINYIN 深難輸入標點符號 ，。、 etc.
Using CTRL-O is very hard.
Obviously the keys ,. etc. have not been fully mapped.
Compare this with scim-pinyin, which gets this right.
(Also in /usr/share/doc/scim-chewing/README.Debian mention
For Hanyu
I get these too daily,
/etc/cron.daily/man-db:
mandb: warning: /usr/share/man/man1/x-terminal-emulator.1.gz is a
dangling symlink
I have an idea: instead of just warning, why doesn't the script take
some action to fix up the problem, so yes, the user will still get the
message, but only once,
Help, I cannot finish installing new kernels.
dpkg: dependency problems prevent configuration of linux-image-2.6.21-2-k7:
linux-image-2.6.21-2-k7 depends on module-init-tools (= 0.9.13); however:
Package module-init-tools is not configured yet.
dpkg: error processing linux-image-2.6.21-2-k7
There is no way I am making mandb go around randomly unlinking
stuff.
Or perhaps add some lines of advice to the message, telling the user
the best way of dealing with the problem, purge and reinstall what
package, etc.?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
I did
# rm /usr/share/man/fr/man5/modules.5.gz
# apt-get install
and now things are OK again.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=bugs.debian.org;[EMAIL
PROTECTED]
OK, please document that it in
/usr/share/doc/debian/bug-log-mailserver.txt etc., and on the website
form too. But when giving the example, use an average package name,
and an average user name, not nonaverage
Then you have to install all forthcoming versions of
module-init-tools with force,
So what shall we do? I also don't have modutils installed. Do we just
go on with life with this 1 not fully installed or removed forever?
What is the official solution? Thank you.
--
To UNSUBSCRIBE, email to
Package: exim4-config
Version: 4.67-3
Also it seems a shame that exim says User unknown while the real
problem is logged only in mainlog. Please just say the more honest
Not going to tell you what went wrong, instead of the dishonest
User unknown!
reopen 432618
thanks
On the man page we find pairs like
keep -k Don’t delete seen messages from
no keep-K Delete seen messages from server
But only
ssl Connect to server over the speci‐
No
Can you please send a proposed text to include
Something like the below, the details of which I am not sure about.
This is the Debian Sid[?] incoming packages directory. Its purpose is to
. After which will be removed. It is for all main,
non-free... ??, for more information see
(I also found I had to dpkg-reconfigure a lot of emacs stuff to get
bbdb back working again, etc.)
SJ Here you have been hit by a bug in update-alternatives, which does not
SJ update the symlink to the last alternative. That's bug #76295.
I see. I shall CC #76295.
--
To UNSUBSCRIBE, email to
Package: apt-file
Version: 2.1.2
Severity: wishlist
Sorry to be rude but I notice dlocate is faster mainly because it uses
some pre-made indexing step that apt-file apparently doesn't. So
perhaps use a similar step.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Then kindly on the ifconfig man page and package description mention
warn that one should now be using ip and the iproute package.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: linux-image-2.6-686
Version: 2.6.25+14
Severity: wishlist
Maybe having a backup kernel in sid would be wise?:
Apparently there is now only one linux-image-2.6.*-*-686 available on
sid. Each time a new kernel comes out all older ones are removed.
This is nice except in the case where
OK, the ruling for
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481283 is in:
CW After having had a chance to think about it, it's clear they belong
CW under /usr/share/$PACKAGE (I've gone for /usr/share/ssh), with
CW administrative overrides in /etc (/var is inappropriate since data
CW
m Keep a kernel that you know works installed then.
Good thing I do, as one needed to run dpkg-reconfigure by hand on
linux-image-2.6.25-2-686 in order to boot very far.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: openssh-client
Version: 1:4.7p1-12
Severity: wishlist
File: /usr/bin/ssh-vulnkey
Add a --help option that prints usage. Mention it on the man page and
usage message. And detect unknown options, printing the usage message.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Package: openssh-client
Version: 1:4.7p1-12
Severity: wishlist
File: /usr/bin/ssh-vulnkey
X-debbugs-cc: [EMAIL PROTECTED]
Upon the next upgrade of this package, a screen should greet the
administrator asking him if we shall run ssh-vulnkey -a right now, or
will he remember to run it later
After root goes thru the ssh-vulnkey -a forced experience, a file
should be saved somewhere noting this so as not to bother him upon
further upgrades. However a number should be stored in that file: 1,
indicating forced experience #1, just in case additional somethings
are discovered that we want
m 'ssh-vulnkey -h' prints usage text.
Please add this to the man page.
By the way the usage text doesn't mention it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
CW But that's OK; any keys that would be detected by ssh-vulnkey will also
CW be blacklisted automatically by sshd.
Well all I know is that I do my sid upgrades, and my friends emailed
me to tell me I had things needing replacing on their machines.
I don't run sshd but often use ssh...
CW (Did
CW Sure, but that's a problem with *their* machine (i.e. it allows access
CW from unauthorised persons) rather than a problem with your machine.
But from us regular users point of view it is *my* account on their
machine that is the problem (if the administrator is not the up to
date type.)
CW
Another question arises: what are all the remote machines where I have
established a ~/.ssh/ directory (that needs to be cleaned up to plug
the hole there if root there is not up to date)?
Well, one finds a list in .ssh/known_hosts, but on sshd(8):
Alternately, hostnames may be stored in a
Package: apt
Version: 0.7.14
Severity: wishlist
Please fix
# apt-get --no-download update
to just use the files the user has accumulated via
APT::Get::List-Cleanup false; or has copied to this machine and put
into lists/partial etc., instead of insisting on connecting to the
network. Also mention
system is not as sensitive as one thinks anyway:
$ touch K k
touch: cannot touch `k': File exists
$ mount
/dev/sdb1 on /mnt/usb/cf type vfat (rw,shortname=mixed,..)
$ touch Kk KK
$ touch bb BB
$ find -type f -mmin -11 -ls
133 14 drwxr-xr-x 2 jidanni jidanni 14336 5月 31 08:45 .
2080
S Not allowed access as much as found a compromised key in ~/.ssh and warned
S him. He has another - perfectly good and uncompromised - key he appears to
S have been using .
I login to machine C from machines A and B. The B-C key was bad, the
A-C key was good. I use machine A then two days later
All I know is
# apt-get dselect-upgrade
The following packages will be upgraded:
deborphan initramfs-tools libilmbase6 libxcomposite1 ucf x11-common
x11-utils xbase-clients xorg xserver-xorg xserver-xorg-input-mouse xutils
...
rmdir: failed to remove `/etc/X11/rstart/commands/x11r6/':
S == Suresh Ramasubramanian [EMAIL PROTECTED] writes:
Having a compromised key in ~/.ssh/authorized_keys (if that's what it
was) is effectively equivalent to allowing access to that account from
the entire Internet.
S Obviously. Which is why I found it. Removed it. Told him to reupload it.
S
AEP Try creating files with non-ASCII characters in the name to see the effect.
I did and everything worked just like on ext3. Perhaps you can give me
an example.
AEP Ignore the warning, it is completely bogus...
OK, sure wish it wouldn't get printed by upstream.
--
To UNSUBSCRIBE, email to
Package: initscripts
Version: 2.86.ds1-58
Severity: wishlist
File: /etc/init.d/bootlogd
If one boots Single User Mode, the end of /var/log/boot looks like
Mon Jun 2 00:23:56 2008: Setting up ICE socket directory /tmp/.ICE-unix
Mon Jun 2 00:23:56 2008:
I would put a
-*- boot log truncated
Package: acpid
Version: 1.0.6-9
Severity: minor
In /var/log/boot:
Loading ACPI modules...Unable to load module: asus_acpi
Unable to load module: bay
Unable to load module: toshiba_acpi
Well that makes sense, as my computer is not those brands, or has a
bay, I guess. But wait, why is it attempting
OK, here's the complete /var/log/dpkg.log transcript. I didn't even
run uniq(1) on it.
upgrade.gz
Description: Binary data
OK, thank you for documenting the test cases.
(No wonder I never stumbled into problems: I use Chinese, which
probably has very few upper/lower case pairs.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
OK, thanks. Anyway
http://www.useit.com/alertbox/designer-user-differences.html . OK, bye.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: openssh-client
Version: 1:4.7p1-12
Severity: wishlist
Perhaps ssh-vulnkey should be mentioned on one or two more of these,
e.g., ssh(1). At least in SEE ALSO.
$ zgrep -c vulnkey /usr/share/man/man*/ssh*|perl -lnwe '[EMAIL
PROTECTED]/@@;@F=split /:/;print @F[1,0]'|sort -r
2
Package: libgdk-pixbuf2
Severity: minor
Version: 0.22.0-14
# deborphan|xargs dpkg -P
Removing libgdk-pixbuf2 ...
Purging configuration files for libgdk-pixbuf2 ...
dpkg - warning: while removing libgdk-pixbuf2, directory
`/usr/share/doc/libgdk-pixbuf2' not empty so not removed.
# ll -R
Package: dpkg
Version: 1.14.18
Severity: minor
Please make all and create new /var/log/dpkg.log* in 644 mode.
I see no reason for not letting users see what is going on.
The can do dpkg -l anyway, and the only files not readable by the user
in e.g., /var/lib/dpkg/ are some 0 byte lock files too.
Package: man-db
Version: 2.5.2-1
Severity: minor
With any pipe or redirection:
$ man perldelta | wc
standard input:1010: `\-' is not allowed in an escape name
11858039 58334
$ man perldelta|:
standard input:1010: `\-' is not allowed in an escape name
$ man perldelta /dev/null
standard
Also consider when there is a symlink:
-f man #eats CPU, killed
-f `which man` #caused 441099
-f /usr/lib/man-db/man #only one of the three that works
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: perl-doc
Version: 5.10.0-10
File: /usr/share/man/man1/perlrun.1.gz
$ man perldelta|grep -- -C\ o
The -C option can no longer be used on the #! line.
Perlrun doesn't warn the user that -C cannot be used there anymore! It just
says:
2. Contained in the file specified by
Package: perl-doc
X-Debbugs-Cc: [EMAIL PROTECTED]
Version: 5.10.0-9.1
Severity: wishlist
I was going to send this To: [EMAIL PROTECTED]:
!Subject: Man-reference-regexp should recognize perl unnumbered man pages
!
!I hit r whilst in man mode, and get
! byte-code: There are no references in the
CW I'm sure I've asked you this before, but once again: please stop filing
CW bugs against man-db about warning messages on individual manual pages.
Ah no wonder:
CW man-db (2.5.0-1) unstable; urgency=low
CW - Discard stderr from formatting processes when outputting to a pager,
CW to
Please document that stderr is now special on the man man page, and
give the user a MANOPT to restore the standard behavior.
/dev/null
That is nice to know but is not something that one can put in a say, MANOPT.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
X-Debbugs-Cc: [EMAIL PROTECTED]
Package: perl-doc
Version: 5.10.0-10
UTF8 gets turned into X by pod2man, besides other disturbing issues:
$ set \\n=encoding utf8\\n\\n=head1 中文\\n
$ echo -e $@|uni2ascii -wq|grep 0x
=head1 0x4E2D 0x6587
$ echo -e $@|pod2text
Wide character in print at
Package: perl
Version: 5.10.0-10
Severity: minor
File: /usr/bin/pod2html
pod2html always leaves two three byte long files,
-rw-r--r-- 1 3 2008-05-13 05:31 pod2htmd.tmp
-rw-r--r-- 1 3 2008-05-13 05:31 pod2htmi.tmp
in the current directory. Please use proper /tmp tmpfiles and remove them
when
X-Debbugs-cc: [EMAIL PROTECTED]
Package: eyed3
Version: 0.6.14-1
Severity: minor
From all one sees, it looks like we successfully set the title:
$ eyeD3 --no-color -t 'Once Upon A Time In The Projects' file
Setting title: Once Upon A Time In The Projects
Writing tag...
ID3 v1.1:
title: Once Upon
Also please mention on perlrun if a feature will go away soon.
There was no warning on perlrun that #!/usr/bin/perl -C was about to
break next upgrade, and we were coding new programs with it right up
until the day it broke.
Also,
$ man perldelta
Too late for -T option
The error
Package: openssh-blacklist
Version: 0.1.0
Severity: wishlist
X-debbugs-Cc: [EMAIL PROTECTED]
Shouldn't those large lists go into /var/lib instead of /etc which is
perhaps a tiny root partition, with backup and NFS sharing policies
different than what those big files deserve?
I did read a bit of
Yes, those
http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/2008-May/006589.html
etc. are all the same bug. You can merge them. It says
it does not occur on ibm laptops
yes it does, and also on
product: AMD Duron(tm) processor
size: 1GHz
$ COLUMNS= dlocate -l
Dear sirs,
# grep upg.*suppo /var/log/dpkg.log
2008-05-16 03:01:03 upgrade python-support 0.7.7 0.8.1
dpkg: warning - unable to delete old directory
`/usr/lib/python2.3/site-packages': Directory not empty
dpkg: warning - unable to delete old directory `/usr/lib/python2.3': Directory
not empty
Package: procps
Version: 1:3.2.7-8
Severity: wishlist
File: /usr/bin/watch
Try watch with an non-existent command. You'll see the message is
wrapped in the wrong place. Try these:
$ watch no_such_program
$ TERM=dumb watch no_such_program #here you forget the CR and just send LF
$ COLUMNS=75
Package: eyed3
Version: 0.6.14-1
Severity: wishlist
Maybe this error should be better handled. I worked around it with
--remove-comments afterwards.
$ eyeD3 --no-color --to-v1.1 file.mp3
Converting tag to ID3 version v1.1
Writing tag...
Traceback (most recent call last):
File /usr/bin/eyeD3,
JM == Josselin Mouette [EMAIL PROTECTED] writes:
JM Le jeudi 15 mai 2008 à 22:11 +0200, Josselin Mouette a écrit :
These are presumably .pyc files and/or .py symlinks let here by
python-central, so you should probably check from which package they are
coming, and, if appropriate, open a bug
Package: ghostscript
X-debbugs-Cc: [EMAIL PROTECTED]
Version: 8.62.dfsg.1-2.1
Severity: wishlist
I wish this error message would say what the root cause is and what I
should do about it.
Setting up ghostscript (8.62.dfsg.1-2.1) ...
...Updating category cmap..
W: Following package's configuration
Package: transmission
Version: 1.20-1
Severity: wishlist
+ IP blocking using the Bluetack Level1 blocklist
Please document how to use this, and other features.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: perl-doc
Version: 5.10.0-10
Severity: wishlist
In perlfunc
use Module VERSION LIST
use Module VERSION
use Module LIST
use Module
use VERSION
Imports some semantics into the current package from the named
module, generally
401 - 500 of 3665 matches
Mail list logo
