On Mon, Jul 28, 2014 at 03:40:46PM +0200, Joachim Breitner wrote:
> Unfortunately, the upstream author believes that programs expecting a
> fully qualified domain names to exist are broken. So I guess we should
> add a conflicts to affected packages.
One of the affected packages happens to be Debi
Still not added as a conflict with exim4, I believe (at least not reported by
apt-listbugs to me):
> What programs are affected?
exim4
> What precisely do these program look up, what do they expect, and what
> do they get with libnss-myhostname?
After installing libnss-myhostname, exim failed to
On 2014-09-08 13:18:17 -0400, Daniel Dickinson wrote:
> I think you're wrong. Setting hostname via dhcp (usually not enabled)
> is different than getting domain from dhcp (usually enabled AIUI).
I meant that if the hostname (nodename) is not changed, then it
will resolve with the right domain via
On 08/09/14 01:18 PM, Daniel Dickinson wrote:
> I think you're wrong. Setting hostname via dhcp (usually not enabled)
> is different than getting domain from dhcp (usually enabled AIUI).
>
> They are completely configuration items in the dhclient and similar tools.
Speaking of which, perhaps to
On 08/09/14 01:18 PM, Daniel Dickinson wrote:
> I think you're wrong. Setting hostname via dhcp (usually not enabled)
> is different than getting domain from dhcp (usually enabled AIUI).
>
> They are completely configuration items in the dhclient and similar tools.
Sorry, I meant completely diff
I think you're wrong. Setting hostname via dhcp (usually not enabled)
is different than getting domain from dhcp (usually enabled AIUI).
They are completely configuration items in the dhclient and similar tools.
Regards,
Daniel
On 08/09/14 05:54 AM, Vincent Lefevre wrote:
> On 2014-09-08 04:53
On 2014-09-08 04:53:08 -0400, Daniel Dickinson wrote:
> On 28/07/14 09:40 AM, Joachim Breitner wrote:
> > BTW, what should the FQDN even be here? My laptop doesn’t have a FQDN
> > that resolves to it, so the concept seems to be dubious at least.
>
> Actually unless your laptop is not connected to
On 28/07/14 09:40 AM, Joachim Breitner wrote:
>
> BTW, what should the FQDN even be here? My laptop doesn’t have a FQDN
> that resolves to it, so the concept seems to be dubious at least.
Actually unless your laptop is not connected to a network via DHCP there
is a 90% probability that if libnss-
On 2014-09-03 02:04:58 +0200, Vincent Lefevre wrote:
> On 2014-09-02 15:29:28 -0400, Tom H wrote:
> > Put the FQDN into "/etc/hostname"
>
> No, that's not the usual way of configuring the machine. Some software
> may break. FYI, the hostname(1) man page says:
>
> /etc/hostname Historically this
On 2014-09-02 15:29:28 -0400, Tom H wrote:
> Put the FQDN into "/etc/hostname"
No, that's not the usual way of configuring the machine. Some software
may break. FYI, the hostname(1) man page says:
/etc/hostname Historically this file was supposed to only contain the
hostname and not the ful
Hi,
On 2014-09-02 23:03:50 +0200, Joachim Breitner wrote:
> Am Dienstag, den 02.09.2014, 18:33 +0200 schrieb Vincent Lefevre:
> > I had "files" first in "hosts:" (I suppose that this corresponds
> > to /etc/hosts), and still first after libnss-myhostname got
> > installed. This means that libnss-m
Hi,
Am Dienstag, den 02.09.2014, 18:33 +0200 schrieb Vincent Lefevre:
> > The whole point of the package is that you do _not_ need a /etc/hosts.
> >
> > Maybe something about the order in /etc/nsswitch.conf can be tweaked.
>
> I had "files" first in "hosts:" (I suppose that this corresponds
> t
Put the FQDN into "/etc/hostname"
tom ~ # dpkg-query -W -f '${Status}\n' libnss-myhostname
install ok installed
tom ~ # cat /etc/hosts
127.0.0.1 localhost
tom ~ # cat /etc/hostname
tom.deb.sid
tom ~ # hostname
tom.deb.sid
tom ~ # hostname -s
tom
tom ~ # hostname -f
tom.deb.sid
tom ~ # hostna
On 2014-09-02 18:07:44 +0200, Joachim Breitner wrote:
> Well, if you have that in /etc/hosts, you don’t need libnss-myhostname.
So, the "Recommends:" by gnome-control-center should be dropped.
Then installing libnss-myhostname or not should be the job of
the Debian installer, because /etc/hosts is
On 2014-09-02 17:49:10 +0200, Joachim Breitner wrote:
> yes, that shouldn’t happen. I need to investigate this carefully (but
> that won’t happen for at least one week or more).
If I have some time, I'll try to see what happens.
> Also it seems that upstream has stopped publishing nss-myhostname
Hi,
Am Dienstag, den 02.09.2014, 18:00 +0200 schrieb Vincent Lefevre:
> On 2014-07-29 23:27:27 +0200, Joachim Breitner wrote:
> > So what is the suggested fix?
>
> I would say: if there is already a FQDN[*] without libnss-myhostname,
> then do not try to change anything. Really, users should hav
On 2014-07-29 23:27:27 +0200, Joachim Breitner wrote:
> So what is the suggested fix?
I would say: if there is already a FQDN[*] without libnss-myhostname,
then do not try to change anything. Really, users should have a
(locally) resolvable FQDN by default e.g. just with something like:
127.0.1.1
Control: tag -1 + help
Hi,
Am Dienstag, den 02.09.2014, 17:43 +0200 schrieb Vincent Lefevre:
> > BTW, what should the FQDN even be here? My laptop doesn’t have a FQDN
> > that resolves to it, so the concept seems to be dubious at least.
>
> You may find the concept dubious on a laptop (though s
On 2014-07-28 15:40:46 +0200, Joachim Breitner wrote:
> Unfortunately, the upstream author believes that programs expecting a
> fully qualified domain names to exist are broken.
In any case, this is unrelated to the problem here. Without
libnss-myhostname, there was a working FQDN on my machine.
A
For me the installation of libnss-myhostname as a Recommends of
gnome-control-center broke local mail delivery to a smart host using
aliases in /etc/aliases and exim. Purging libnss-myhostname fixes the
problem.
Interesting is that the position of myhostname in the following
~$ grep myhostname /e
Package: libnss-myhostname
Version: 0.3-9
Followup-For: Bug #756224
Dear Maintainer,
* What led up to the situation?
upgrading my testing system yesterday
* What exactly did you do (or not do) that was effective (or
ineffective)?
only normal upgrade and it looks gnome-control-ce
Please note there are other 'basic networking type apps (which is what I
consider email/postfix)' that break without FQDN I just cannot remember
the details since at the time I was more concerned with getting my
network behaving and I thought libnss-myhostname was a fringe project
that sounded good
Hi,
Am Dienstag, den 29.07.2014, 11:10 -0400 schrieb Daniel Dickinson:
> Here is a specific for-instance:
>
> Evolution does not send a FQDN in EHLO unless it has an FQDN.
>
> Postfix for example is generally configured to require an FQDN from
> email sender (as a spam prevention measure).
>
>
Might I add that even Winblows systems that are attached to a network
with DHCP-supplied domain name (or which are configured manually with a
domain name and use static addresses) have FQDN's
The only things that don't have FQDN on normal networks are link-local
networks and brokenly configured *n
Here is a specific for-instance:
Evolution does not send a FQDN in EHLO unless it has an FQDN.
Postfix for example is generally configured to require an FQDN from
email sender (as a spam prevention measure).
Therefore sending mail from Evolution via a reasonably configured
Postfix fails with lib
Fair enough, but the argument seems to consist of 'if you don't obey the
rules bad behaviour results, ergo the rule is bad' which is kind of like
arguing that making people obey the law is bad because some people got
to jail. Basically the arguments are political not technical, even if
it is dress
Hi,
Am Dienstag, den 29.07.2014, 00:22 -0400 schrieb Daniel Dickinson:
> Yeah but the guy claiming FQDN broken is the same Lennart who seems hell
> bent on destroying every *nix idiom. I wouldn't go by his opinion.
and I won’t discuss technical issues on this level.
Greetings,
Joachim
--
Joa
Yeah but the guy claiming FQDN broken is the same Lennart who seems hell
bent on destroying every *nix idiom. I wouldn't go by his opinion.
Regards,
Daniel
On 28/07/14 09:40 AM, Joachim Breitner wrote:
> Hi,
>
>
> Am Montag, den 28.07.2014, 09:21 -0400 schrieb Daniel Dickinson:
>> On 27/07/14
On 27/07/14 02:25 PM, Joachim Breitner wrote:
> Hi,
>
>
> Am Sonntag, den 27.07.2014, 13:53 -0400 schrieb Daniel Dickinson:
>> Package: libnss-myhostname
>> Version: 0.3-6
>> Severity: serious
>>
>> Takes over names resolution of local host's name and causes apps that
>> need FQDN instead of just
Hi,
Am Sonntag, den 27.07.2014, 13:53 -0400 schrieb Daniel Dickinson:
> Package: libnss-myhostname
> Version: 0.3-6
> Severity: serious
>
> Takes over names resolution of local host's name and causes apps that
> need FQDN instead of just
> hostname to fail (becuase myhostname fails to include a
Package: libnss-myhostname
Version: 0.3-6
Severity: serious
Takes over names resolution of local host's name and causes apps that need FQDN
instead of just
hostname to fail (becuase myhostname fails to include a domain).
This is now pulled in by Gnome which means it's bad behviour will break a l
31 matches
Mail list logo
