Git crash during new install

[Just an Illusion]

Binary package hint: git-core

I have do an update with the development version the 28-29/08/2009.

During install process, when the install try to run git it crash and propose me to send the message to developpers
Even if the tag amd64 and architecture will be automatically inserted, I have not a Amd64 Cpu but an Intel one.
I have do nothing to choose the Amd64 architecture instead of Intel, if that can explain the problem.

ProblemType: Package
Architecture: amd64
Date: Sat Aug 29 01:57:01 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: problèmes de dépendances - laissé non configuré
NonfreeKernelModules: nvidia
Package: git-daemon-run 1:1.6.3.3-2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.28-14.47-generic
SourcePackage: git-core
Title: package git-daemon-run 1:1.6.3.3-2 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Uname: Linux 2.6.28-14-generic x86_64

[Anders Kaseorg (andersk)]

The amd64 architecture refers to all x86-64 CPUs, made by either Intel or AMD. That isn’t a problem.

Although I don’t know French, it looks like the real error was in the runit package, which is a dependency of git-daemon-run. (You only need git-daemon-run if you want to publicly serve a Git repository via the git:// protocol; you don’t need it for normal operation of Git.)

Préparation du remplacement de runit 2.0.0-1ubuntu2 (en utilisant .../runit_2.0.0-1ubuntu3_amd64.deb) ...

stop: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connexion refusée

dpkg : avertissement : ancien script pre-removal a retourné une erreur de sortie d'état 1

dpkg - tentative d'exécution du script du nouveau paquet à la place ...

stop: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connexion refusée

dpkg : ... on dirait que tout a fonctionné correctement.

[Just an Illusion (jai4forum)]

Hello,
You have certainly right, but I have not the time for investigation.

In fact, I was unable to use git since the first working installation (one version before 9.04.13, I thinks that was the 9.04.09)
During the installation, I have select the git package install, but I did not need it in "production usage".
I had done it to be able to test it between 2 others tasks (I had 2 CPU, then I can do at least 2 things in parallel: normal task and testing task).

In conclusion: if this was a runit package bug, then it must be reported to the development team that must provide i) the correction, or ii) a (temporary) workaround.
If the git-daemon-run was unusefull for normal operation of Git, then it must be disabled in default configuration, and proposed only during git configuration; if the user defined a publicly serve directory and chose the git::// protocol for it, following your explanation.

FYI, I always install more than strictly "production" requirement because I made lot of test of programs/materials/networks/systems/configuration,... (it seems usefull because I have found at least this bug, without any specific configuration)
I had done it since more 10 years now (for Linux and others OS), but only Ubuntu versions give me so bugs at install.

[Anders Kaseorg (andersk)]

I have already reassigned this bug to the runit package, so no further report is necessary.

git-daemon-run is a separate package from the rest of Git. It _is_ disabled in the default configuration, unless you have explicitly requested its installation.

Despite this runit failure, you should still be able to use Git. The only functionality you are missing if git-daemon-run failed to install is serving public git:// repositories. To restore your package manager to a good state, just uninstall the runit and git-daemon-run packages.

If you have any other problem with Git, please report it as a separate bug. Otherwise, further information is not needed at this time. Thanks for your report.