Your message dated Tue, 15 Jul 2008 00:32:37 +0900
with message-id <[EMAIL PROTECTED]>
and subject line This is bug in old package
has caused the Debian Bug report #486584,
regarding debian-reference-es : maybe file lists or something like that is not
correct
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 [EMAIL PROTECTED]
immediately.)
--
486584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486584
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: debian-reference-es
Version: 2.03
Severity: minor
I was upgrading and I saw this:
Preparando para reemplazar debian-reference-es 1.12 (usando
.../debian-reference-es_2.03_all.deb) ...
Desempaquetando el reemplazo de debian-reference-es ...
dpkg: atención - no se puede borrar el directorio antiguo
`/usr/share/doc/Debian/reference': El directorio no está vacío
dpkg: atención - no se puede borrar el directorio antiguo
`/usr/share/doc/Debian': El directorio no está vacío
Seems that the package tried to delete two folders. I assume that if it tried,
the folders does not belong to other package, but still they could not were
deleted.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debian-reference-es depends on:
ii debian-reference-common 2.03 Debian system administration guide
debian-reference-es recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: debian-reference-es
Version: 2.03
AS original post was upgrade from 1.12 and bug was in 1.12, I am closing
this bug now while marking it found for those.
I am not so clear how version tracking of BTS works. Let's see.
Osamu
--- End Message ---
