Your message dated Tue, 13 Jun 2023 02:01:48 +0530
with message-id <0dq5wr.yq7trji8k...@onenetbeyond.org>
and subject line Re: gitaly: fails to install: Could not find gem 'rugged (~>
0.28)'
has caused the Debian Bug report #983874,
regarding gitaly: fails to install: Could not find gem 'rugged (~> 0.28)'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitaly
Version: 13.4.6+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Setting up gitaly (13.4.6+dfsg1-2) ...
[ESC][31mCould not find gem 'rugged (~> 0.28)' in any of the gem sources
listed in your
Gemfile.[ESC][0m
dpkg: error processing package gitaly (--configure):
installed gitaly package post-installation script subprocess returned error
exit status 7
Processing triggers for ca-certificates (20210119) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
gitaly
cheers,
Andreas
gitaly_13.4.6+dfsg1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On Tue, 02 Mar 2021 16:07:21 +0100 Andreas Beckmann <a...@debian.org>
wrote:
> Setting up gitaly (13.4.6+dfsg1-2) ...
> [ESC][31mCould not find gem 'rugged (~> 0.28)' in any of the gem
sources listed in your
> Gemfile.[ESC][0m
Fixed long back. Closing the bug.
--- End Message ---
