Re: Setting hostnames with hostnamectl on AWS AMIs, missing dbus?

[Anders Jackson <anders.jackson@gmail.com>]

Den 21 feb. 2017 00:44 skrev "Anders Jackson" <anders.jackson@gmail.com>:

Den 19 feb. 2017 07:31 skrev "Charles Plessy" <plessy@debian.org>:

Le Sun, Feb 19, 2017 at 05:12:38AM +0100, Anders Jackson a écrit :
>
> Software that is packed and installed in Debian should, and must, work.

Hi Anders,

Hi

I think that you are conflating issues.  Ultimately, you are challenging
the semantics of Depends and Recommends.

Hey, don't t be condeming.  I know the difference, thank you.  The question that comes to mind, do you? 

What we shouldn't and can't accept in Debian is broken software when installed. Period. 

You package is broken,  and you refused to fix it, because you're to lazy to do it. That is what you wrote. 

Yes, it is the packer that need to fix it, not the users/administrators. 

If one installs Debian using the Debian Installer, where "Recommended"
dependencies are installed by default, everything works.

It is possible to install packages with only their strictest
dependencies, that is, without the "Recommended" ones.  This opens many
ways to customise Debian, and here it is used to make minimal images.
But it may be necessary to cherry-pick some extra packages to reach the
wanted result.  Here, it means adding dbus to the image.

Yes,  I know this.  I also know that what is installed should work,  even in a minimal installation.  Which it isn't now. Recommend shouldn't be needed to go from a broken command to a working one. As is the case now. 

Or are you seriously suggesting that this is what is excepted behaviour? 

Because it start to look pretty much like a behavior of a debugging flag we all know about... 

As I wrote,  it isn't acceptable with severe bugs in Debian stable...  

Have a nice day,

Charles

Have a nice day to you too.  Fixing this bug, I hope.

Anders Jackson