Your message dated Mon, 6 Jan 2020 15:56:05 -0800
with message-id <[email protected]>
and subject line Re: git: Please move the packaging repository to salsa.d.o
has caused the Debian Bug report #897378,
regarding git: Please move the packaging repository to salsa.d.o
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 [email protected]
immediately.)
--
897378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897378
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git
Version: 1:2.17.0-1
Severity: normal
Dear git maintainers,
The packaging repository for git, as indicated by the Vcs-Git field in
debian/control, is https://repo.or.cz/r/git/debian.git/
repo.or.cz uses an invalid and expired certificate chain [0], so cloning over
HTTPS does not work (at least not without passing --insecure or somesuch).
Since salsa.d.o was recently set up and is the new prefered location for Debian
packaging repositories that use Git, it would be a good opportunity to move the
packaging repository there, if you would be ammenable to it :)
Best,
nicoo
[0]: Since the certificate chain use a homemade root CA that expired in 1999,
I think we can safely assume that this is not a transient issue, but that
this repository host is essentially unmaintained.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages git depends on:
ii git-man 1:2.17.0-1
ii libc6 2.27-3
ii libcurl3-gnutls 7.58.0-2
ii liberror-perl 0.17025-1
ii libexpat1 2.2.5-3
ii libpcre2-8-0 10.31-3
ii perl 5.26.2-2
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages git recommends:
ii less 487-0.1
ii openssh-client [ssh-client] 1:7.7p1-2
ii patch 2.7.6-2
Versions of packages git suggests:
ii gettext-base 0.19.8.1-6
pn git-cvs <none>
pn git-daemon-run | git-daemon-sysvinit <none>
pn git-doc <none>
pn git-el <none>
pn git-email <none>
pn git-gui <none>
pn git-mediawiki <none>
pn git-svn <none>
pn gitk <none>
pn gitweb <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
Anatoly Pugachev wrote:
> just to say that i would like to see git package sources on salsa as
> well. thanks.
One of the features I value in Git is that it is a distributed version
control system, which means that projects do not have to be singly
homed.
To that end, I'm not planning to make Vcs-Git point to salsa for this
package. That said, if there are ways this is affecting your work,
please don't hesitate to let me know and I'll look into what I can do.
Nicolas Braud-Santoni wrote:
> repo.or.cz uses an invalid and expired certificate chain [0], so cloning over
> HTTPS does not work (at least not without passing --insecure or somesuch).
Thanks for reporting. This has been fixed by using Let's Encrypt, so
closing.
Sincerely,
Jonathan
--- End Message ---
