git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jeff King <peff@peff.net>
Cc: Christian Strasser <christian@avr-fun.de>, git@vger.kernel.org
Subject: Re: Git install crashed nearly whole System
Date: Thu, 18 Mar 2021 17:24:26 +0000	[thread overview]
Message-ID: <YFOMylgx9paP5anv@camp.crustytoothpaste.net> (raw)
In-Reply-To: <YFOHFABji5/sDZod@coredump.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]

On 2021-03-18 at 17:00:04, Jeff King wrote:
> On Thu, Mar 18, 2021 at 04:33:52PM +0000, brian m. carlson wrote:
> > If everything's working for you, there's no need to change it.  It's
> > _possible_ to install git-all and not have this problem, but because of
> > the way modern versions of Debian and the packages in question are
> > configured it ends up tending to have this problem by default.
> > 
> > In this case, it may be that git-daemon is installed but not configured
> > to start, or it may have been removed when you reinstalled GNOME since
> > it's not a hard dependency.
> 
> Yeah. I think fundamentally this is a packaging issue. It looks like
> "git-daemon-*" has been downgraded to "Suggests" in Debian unstable. It
> looks like this was done in 1:2.26.0-2 last April. From the changelog:
> 
>     * debian/control: downgrade Recommends by git-all on git-daemon-run
>     to Suggests. The git-all package is a "batteries included" full
>     installation of Git. Automatically running a daemon is not useful
>     to most of its users.
> 
> So they are already aware of and addressed the problem, but older
> releases will still show it.

Yeah, and I think that https://bugs.debian.org/953875 has fixed the
problem where installing runit (by using git-daemon-run) would switch
the default init system.  So in bullseye, this will probably be
fixed even if the daemon does get installed.

I think the person who previously maintained both Git and runit in
Debian was busy with other things for a while, which prevented this
issue from being fixed.  Now Jonathan is maintaining Git (and is doing a
great job, especially with the next builds in experimental) and someone
else has taken over runit and fixed the problem mentioned above, which
occasionally caused this same problem with other packages as well.

So I think this will sort itself out in the next release, and in the
meantime, just be careful with git-all in buster and older.
-- 
brian m. carlson (he/him or they/them)
Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2021-03-18 17:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 18:23 Git install crashed nearly whole System Christian Strasser
2021-03-14 18:52 ` Santiago Torres Arias
2021-03-18 11:34   ` Christian Strasser
2021-03-14 20:20 ` brian m. carlson
2021-03-18 10:37   ` Christian Strasser
2021-03-18 16:33     ` brian m. carlson
2021-03-18 17:00       ` Jeff King
2021-03-18 17:24         ` brian m. carlson [this message]
2021-03-19 15:50           ` Christian Strasser
2021-03-14 21:17 ` Randall S. Becker
2021-03-18  9:54   ` Christian Strasser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YFOMylgx9paP5anv@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=christian@avr-fun.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).