The officially official Devuan Forum!

You are not logged in.

#26 Re: Other Issues » [SOLVED] Git hangs on cloning » 2023-01-29 23:54:04

TCH

This Perl code

#!/usr/bin/perl

use strict;
use LWP::UserAgent; 

my $token="";

my $uri = 'https://github.com/punesemu/puNES'; 
my $json => '{"username":"user","password":"pwd"}'; 
my $req = HTTP::Request->new('POST', $uri ); 
$req->header( 'Content-Type' => 'application/json'); 
$req->content( $json );

my $lwp = LWP::UserAgent->new;

my $message = $lwp->request( $req ); 

if ( $message->is_success ) {
    my $token= $message->content;
    print "\n Received POST Response:\n$token\n";
} else {
    print "error code:",    $message->code,"\n";
    print "error message:", $message->as_string(), "\n"; 
}

gives back 403, because of cookies. Stupid question, but this cannot be the reason behind git's hanging, right?

error code:403
error message:HTTP/1.1 403 Forbidden
Cache-Control: no-cache
Connection: close
Date: Sun, 29 Jan 2023 23:51:36 GMT
Server: GitHub.com
Vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame
Vary: Accept-Encoding, Accept, X-Requested-With
Content-Type: text/plain; charset=utf-8
Client-Date: Sun, 29 Jan 2023 23:51:40 GMT
Client-Peer: 140.82.121.3:443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=US/O=DigiCert Inc/CN=DigiCert TLS Hybrid ECC SHA384 2020 CA1
Client-SSL-Cert-Subject: /C=US/ST=California/L=San Francisco/O=GitHub, Inc./CN=github.com
Client-SSL-Cipher: TLS_AES_128_GCM_SHA256
Client-SSL-Socket-Class: IO::Socket::SSL
Client-SSL-Version: TLSv1_3
Client-Transfer-Encoding: chunked
Content-Security-Policy: default-src 'none'; base-uri 'self'; block-all-mixed-content; child-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com objects-origin.githubusercontent.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com cdn.optimizely.com logx.optimizely.com/v1/events *.actions.githubusercontent.com wss://*.actions.githubusercontent.com online.visualstudio.com/api/v1/locations github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com; font-src github.githubassets.com; form-action 'self' github.com gist.github.com objects-origin.githubusercontent.com; frame-ancestors 'none'; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com; img-src 'self' data: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com objects-origin.githubusercontent.com secured-user-images.githubusercontent.com/ opengraph.githubassets.com github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com *.githubusercontent.com; manifest-src 'self'; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/; script-src github.githubassets.com; style-src 'unsafe-inline' github.githubassets.com; worker-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/
Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
Set-Cookie: _gh_sess=E%2FXP3lgu582cURwnByOLH4bQXxdIustR7%2BLLYoM8LvAsVLIZ6J%2FwP2xKdOdXTdOT7bSQvwHRfZDdwgKVWZ83aM5Tw4jD4hgvuWw4FJipikDAIBfx7bIRxDT%2BHu%2B6v3mPD%2BpbnezQkJHXBDFzHCln2cBx%2FfnjdjDu%2Buw7%2Fa1X7%2FIcl%2BIYKDM79mNnYmkL8VZCiJPwJw%3D%3D--ttDckMfA7a%2BcG5o7--ijrpO2QavxKMiStaaoG1Mw%3D%3D; path=/; secure; HttpOnly; SameSite=Lax
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Content-Type-Options: nosniff
X-Frame-Options: deny
X-GitHub-Request-Id: D87C:9AD5:1EDD5F5:202975C:63D70688
X-XSS-Protection: 0

Cookies must be enabled to use GitHub.

#27 Re: Hardware & System Configuration » Disk blockdevice detecting order scrambled after every boot » 2023-01-29 23:35:11

TCH

What could cause that the order only started to be random after upgrading to Devuan 4?

#28 Re: Other Issues » [SOLVED] Git hangs on cloning » 2023-01-29 23:27:13

TCH
aluma wrote:

Probably a stupid suggestion... smile
There is a ready Devuan with TDE https://exegnulinux.net/
Works without problems.
Might be easier to install?

TDE was installed in 2015, when i migrated to SSD-s and switched to Debian 7 from Ubuntu 10.04. Since then i just update it without problems. But seriously, what has TDE do with git being unable to connect? big_smile
But thanks for the tip, i did not know about that distro.

alexkemp wrote:

I'm on Chimaera & an upgrade included git just now (minutes earlier). However, no idea if that will have fixed *your* problem.

The update came down here too, but nothing has changed unfortunately... sad

#29 Re: Hardware & System Configuration » Disk blockdevice detecting order scrambled after every boot » 2023-01-29 15:46:24

TCH

Well, the order was the same for 11 years, across several versions of several distributions, including Devuan. Is there a chance that this was only coincidence?

#30 Other Issues » [SOLVED] Git hangs on cloning » 2023-01-29 15:02:36

TCH
Replies: 26

I've upgraded my system from Devuan 2 to Devuan 4 and now git hangs on cloning any repository. Example:

# GIT_TRACE=1 GIT_CURL_VERBOSE=1 git clone --verbose https://github.com/punesemu/puNES
02:04:36.418257 git.c:444               trace: built-in: git clone --verbose https://github.com/punesemu/puNES
Cloning into 'puNES'...
02:04:36.420737 run-command.c:664       trace: run_command: git remote-https origin https://github.com/punesemu/puNES
02:04:36.423321 git.c:730               trace: exec: git-remote-https origin https://github.com/punesemu/puNES
02:04:36.423418 run-command.c:664       trace: run_command: git-remote-https origin https://github.com/punesemu/puNES
02:04:36.434643 http.c:756              == Info: Couldn't find host github.com in the .netrc file; using defaults
02:04:36.440239 http.c:756              == Info:   Trying 140.82.121.3:443...
02:04:36.466931 http.c:756              == Info: Connected to github.com (140.82.121.3) port 443 (#0)
02:04:36.514346 http.c:756              == Info: found 384 certificates in /etc/ssl/certs
02:04:36.514423 http.c:756              == Info: ALPN, offering h2
02:04:36.514429 http.c:756              == Info: ALPN, offering http/1.1

I did upgrade to Devuan 3 first, i did not skipped it. cURL is able to fetch pages without errors. I do not know if git is able to clone if HTTP is used instead of HTTPS, because every repo i know instantly redirects the request to HTTPS.

# apt policy git
git:
  Telepítve: 1:2.30.2-1
  Jelölt:    1:2.30.2-1
  Verziótáblázat:
 *** 1:2.30.2-1 500
        500 http://devuan.bio.lmu.de/merged chimaera/main amd64 Packages
        100 /var/lib/dpkg/status
# apt policy ca-certificates
ca-certificates:
  Telepítve: 20210119
  Jelölt:    20210119
  Verziótáblázat:
 *** 20210119 500
        500 http://devuan.bio.lmu.de/merged chimaera/main amd64 Packages
        500 http://devuan.bio.lmu.de/merged chimaera/main i386 Packages
        100 /var/lib/dpkg/status

I do not use firewall or proxy.

Any tips on this?

#31 Hardware & System Configuration » Disk blockdevice detecting order scrambled after every boot » 2023-01-29 14:54:24

TCH
Replies: 12

Hello there,

For the last 11 years, Ubuntu 10.04, Debian 7, Debian 8 and finally Devuan 2 all detected my disk devices in this order (save for Ubuntu, when i did not have the SSD-s yet, but the disk detecting order was constant there too):
/dev/sda: primary SSD where the system resides
/dev/sdb: secondary SSD where i back up the system with rsync regularly
/dev/sdc: secondary HDD where i back up the data with rsync regularly
/dev/sdd: primary HDD where the data resides
This order was constant, it never changed. This is the same order as the disks are plugged into the motherboard. (Yes, this is the same motherboard from 2012.) Clean, obvious, logical. Working.

A few days ago i've upgraded to Devuan 4 and now the order is entirely random. At every boot.
I tried to check how can i set up a persistent order, but all i found is how to write fstab entries by disk id; but this is not a partition problem, it is a disk blockdevice detecting order problem, it cannot be solved from fstab.

Any tips on this?

Board footer

Forum Software