Upstream 5.0.23 fixed this issue. There is no separate upstream bug
report.
http://ftp-
master.metadata.debian.org/changelogs/main/w/whois/unstable_changelog
** Changed in: whois (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member o
(iconv tells me it cannot convert from EUC-KR to UTF-8 from the old
input so I'm not sure if that's actually true, but the domain should be
set up to use the new, well-defined server anyway.)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Additionally, the message from the old server is misleading.
precise$ whois devunt.kr | less
...
湲 蹂대 UTF-8
몄⑸
鍮ㅻ怨
듬.
EUC-KR 몄
鍮ㅻ
oldwhois.kisa.or.kr
鍮
怨 듬
.
The above information is encoded with UTF-8
EUC-KR encoding WHOIS is being serviced in this URL:oldwhois.kisa.or.kr
- KISA/KRNIC Wh
Is this a duplicate of bug #1100177?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1039598
Title:
dependency problems - leaving unconfigured
To manage notifications about this bug go
Turns out the problem was that I lacked the precise-updates repo for
main.
** Changed in: krb5 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/11001
I imagine this may be a duplicate of bug #1100177 but it was rather
messy so I opted to create a new bug report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1100177
Title:
krb5-user
Public bug reported:
After enabling precise-updates for universe, krb5-user is not
installable. It depends on libkrb5-3 = 1.10+dfsg~beta1-2ubuntu0.3 but
there is no such version in the repositories.
precise# apt-cache policy krb5-user
krb5-user:
Installed: (none)
Candidate: 1.10+dfsg~bet
Public bug reported:
Binary package hint: whois
I'm speculating the "Connection refused" means the server name in whois
is wrong. There is a whois server at whois.aeda.net.ae which appears
authoritative. They offer a web lookup at http://whois.aeda.net.ae/ as
well.
ubu...@ubuntu$ whois example
I spent a lot of time investigating this, and would have avoided that if
it had been documented. I'd still like to request the addition of a
small snippet to README.Debian but since I'm an Ubuntu user I didn't
want to take this directly upstream. If I submit this upstream, with a
small patch, can
The error message suggests that the fact that you have uninstalled Samba
(possibly after removing its configuration file by hand?) might be the
cause of the problem here. Could you try to completely purge it from
your system, then reinstall?
--
bug of samba
https://bugs.launchpad.net/bugs/267671
** Changed in: samba (Ubuntu)
Status: Incomplete => New
--
Incorrect hyperlink in samba-docs
https://bugs.launchpad.net/bugs/260424
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing lis
I'm taking the liberty to set this to Incomplete as the question from
2007 about whether this is still a problem has gone unanswered.
** Changed in: samba (Ubuntu)
Status: Triaged => Incomplete
--
Printing does not work: PID 23402 (/usr/lib/cups/backend/smb) crashed on signal
6
https://b
Public bug reported:
Binary package hint: samba-common
The directory /etc/samba contains a spurious file gdbcommands which does
not appear to be documented. To the extent that I am able to guess what
it's for, it should probably simply be removed, or else documented e.g.
in the /usr/share/doc/sa
> (The documentation is vague on this, and I'm too chicken to confirm my
> interpretation,
> but I take it "StrictHostKeyChecking no" will permit you to connect to a host
> whose
> key has changed.)
Okay, I confirmed this under controlled conditions now. You do get a
warning, with big old ugl
Maybe this could be rephrased: add an alternative "StrictHostKeyChecking
silent" and, ideally, make it the default. Like with
"StrictHostKeyChecking no", add hosts silently; but still be strict when
a key has changed, and refuse to connect.
(The documentation is vague on this, and I'm too chicken
On Thu, 27 Mar 2008 22:13:04 -, "Mathias Gug" <[EMAIL PROTECTED]>
said:
> On Thu, Mar 27, 2008 at 07:23:56PM -, era wrote:
> > + It's a usability problem that openssh-client behaves differently
> > the first time you connect to a host, particul
** Description changed:
- It's a usability problem that openss-client behaves differently the
+ Binary package hint: openssh-client
+
+ It's a usability problem that openssh-client behaves differently the
first time you connect to a host, particularly if you hop between client
machines all th
Public bug reported:
It's a usability problem that openss-client behaves differently the
first time you connect to a host, particularly if you hop between client
machines all the time and might or might not have connected from that
particular client before. It would be an improvement if it would j
18 matches
Mail list logo
