bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities
Hello Leo, Leo Famulari writes: > On Sat, Oct 20, 2018 at 11:24:24PM -0400, Maxim Cournoyer wrote: >> l...@gnu.org (Ludovic Courtès) writes: >> > On closer inspection, it seems that there’s nothing “fatal” here: if you >> > let it run for a while (1 or 2 minutes), it ends up silently cloning the >> > whole repo and the derivation build eventually succeeds. >> >> It did end up working fine, although it took a large amout of time for >> doing what seems to be a checkout (4 min 46 s). I did some experiments >> and this is really the time it took to do a full clone of the libssh >> project. > > Great, you figured it out :) > > More explanation: > > Git has a few different server protocols: git, dumb HTTP, smart HTTP, > and SSH: > > https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols > > The dumb HTTP protocol is slow and does not show any progress status or > other informative message while it works, but if you monitor your > network traffic you can see it working. > > For obvious reasons, it's rare to see the dumb HTTP protocol deployed > nowadays, but you may still find it on legacy installations. Thanks for the extra bits of information :) Cheers, Maxim
bug#33100: [libssh] fatal: dumb http transport does not support shallow capabilities
On Sat, Oct 20, 2018 at 11:24:24PM -0400, Maxim Cournoyer wrote: > l...@gnu.org (Ludovic Courtès) writes: > > On closer inspection, it seems that there’s nothing “fatal” here: if you > > let it run for a while (1 or 2 minutes), it ends up silently cloning the > > whole repo and the derivation build eventually succeeds. > > It did end up working fine, although it took a large amout of time for > doing what seems to be a checkout (4 min 46 s). I did some experiments > and this is really the time it took to do a full clone of the libssh > project. Great, you figured it out :) More explanation: Git has a few different server protocols: git, dumb HTTP, smart HTTP, and SSH: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols The dumb HTTP protocol is slow and does not show any progress status or other informative message while it works, but if you monitor your network traffic you can see it working. For obvious reasons, it's rare to see the dumb HTTP protocol deployed nowadays, but you may still find it on legacy installations. signature.asc Description: PGP signature
bug#33110: Maxima build fails during check phase
Hello Guix, After the recent (commit: 82cbe4e0467304e5d8f5931ca4d70617a0e323ba) update of maxima to version 5.42.0 ‘guix build maxima’ fails during the ‘check’ phase. I have attached tests/test-suite.log. I run GuixSD (commit: 2c17bd7b2955beef4130d11b33e07e4fb3b234dc) on an x86_64 machine. Greetings, Diego test-suite.log Description: tests/test-suite.log
bug#32997: Kodi phones home to check for updates
Fixed in 2c17bd7b2955beef4130d11b33e07e4fb3b234dc -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
bug#33105: cups Can't create temporary file or stopped "Filter failed"
On Sat, Oct 20, 2018 at 09:36:57PM +0300, Oleg Pykhalov wrote: > Hello Guix, > > I've spotted a bug in CUPS service “Can't create temporary file”. If I > gave ‘765’ permissions to ‘/var/spool/cups/tmp/’ directory then an error > is “stopped "Filter failed"”. ‘777’ for /var/spool/cups/tmp/ is > required to print a test page via CUPS WEB interface. > > > I read gnu/services/cups.scm and found that the /var/spool/cups/ > directory should be owned by ‘lp’ user: > --8<---cut here---start->8--- > (define %cups-activation > ;; Activation gexp. > (with-imported-modules '((guix build utils)) > #~(begin > (use-modules (guix build utils)) > (define (mkdir-p/perms directory owner perms) > (mkdir-p directory) > (chown "/var/run/cups" (passwd:uid owner) (passwd:gid owner)) > ;; ^^ > (chmod directory perms)) > ;; … > (let ((user (getpwnam "lp"))) > ;; … > (mkdir-p/perms "/var/spool/cups/tmp" user #o755) ; <-- > ;; … > > --8<---cut here---end--->8--- > > > Maybe we should make /var/spool/cups/tmp directory owned by ‘lp’ user, > too? WDYT? currently /var/spool/cups is root:lp, my first thought is to change it to lp:lpadmin (not sure where I got lpadmin from) and make it 775. > > Test page was printed successfully with: > --8<---cut here---start->8--- > $ sudo ls -ld /var/spool/cups/tmp > drwxr-xr-x 2 lp lp 4096 Oct 20 21:20 /var/spool/cups/tmp > --8<---cut here---end--->8--- > > > From cups-files.conf(5) man page: > > TempDir directory > Specifies the directory where short-term temporary files are > stored. The default is "/var/spool/cups/tmp". > > User username > Specifies the user name or ID that is used when running external > programs. The default is "lp". > > > Oleg. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
