[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#346316: marked as done (Typo in new warning message "There are no key availalable ...")



Your message dated Sun, 16 Sep 2007 17:43:48 -0400
with message-id <8e2a98be0709161443t18615ef2r909ad7d3ea44f5ea@mail.gmail.com>
and subject line close #399652
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: apt
Version: 0.6.43.1
Severity: minor
Tags: patch

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


In apt-pkg/acquire-item.cc in pkgAcqMetaIndex::VerifyVendor() the new
warning message is:

| There are no public key available ...

I think, you see the typo (There is ... or There are no public keys
...).

Regards, Daniel


- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.04051127
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages apt depends on:
ii  libc6                         2.3.5-11   GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-6  GCC support library
ii  libstdc++6                    4.0.2-6    The GNU Standard C++ Library v3

apt recommends no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDvwNkdg0kG0+YFBERAkUOAJwIPUh5SIOeSR+zwtS67BvvNWnNNQCeIEkd
ocs49mYt6vNNSb9Z+Na4ygQ=
=2mMs
-----END PGP SIGNATURE-----


--- End Message ---
--- Begin Message ---
i've checked the latest version of the apt source, and found that this
grammar mistake has indeed been fixed.


--- End Message ---

Reply to: