Dear maintainer of hyperspec,
On Friday, February 10, 2012 I sent you a notice announcing my intent to upload
an
NMU of your package to fix its pending l10n issues, after an initial
notice sent on Sunday, February 05, 2012.
You either agreed for this NMU or did not respond to my notices.
I wil
hyperspec_1.30+nmu2_i386.changes uploaded successfully to localhost
along with the files:
hyperspec_1.30+nmu2.dsc
hyperspec_1.30+nmu2.tar.gz
hyperspec_1.30+nmu2_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
_
Your message dated Sat, 18 Feb 2012 16:17:43 +
with message-id
and subject line Bug#621377: fixed in clisp 1:2.49-8.1
has caused the Debian Bug report #621377,
regarding Still uses libdb4.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Accepted:
clisp-dev_2.49-8.1_amd64.deb
to main/c/clisp/clisp-dev_2.49-8.1_amd64.deb
clisp-doc_2.49-8.1_all.deb
to main/c/clisp/clisp-doc_2.49-8.1_all.deb
clisp-module-berkeley-db_2.49-8.1_amd64.deb
to main/c/clisp/clisp-module-berkeley-db_2.49-8.1_amd64.deb
clisp-module-bindings-glibc_2.49
clisp_2.49-8.1_amd64.changes uploaded successfully to localhost
along with the files:
clisp_2.49-8.1.dsc
clisp_2.49-8.1.debian.tar.gz
clisp-doc_2.49-8.1_all.deb
clisp_2.49-8.1_amd64.deb
clisp-dev_2.49-8.1_amd64.deb
clisp-module-berkeley-db_2.49-8.1_amd64.deb
clisp-module-pcre_2.49-8.1
