bug#57068: Resizing mcron job in vm-image.tmpl interferes with settings

2022-11-01 Thread Mathieu Othacehe


Hey,

> Oh, I wasn’t aware of that, that should certainly be fixed.  (I fixed a
> similar issue in GNOME some years ago, and I’m confident it’ll be easier
> to fix in Xfce because it doesn’t have all those layers and daemons and
> JavaScript and DBus interfaces.  :-))

Fixing this behaviour in Xfce seems like the right thing to do to
conserve SPICE support and fix the QEMU resizing issue.

This also looks like a large development, so I propose to unblock the
release with this ticket.

Thanks,

Mathieu





bug#49508: Implement --allow-insecure-transport for `guix pull`

2022-11-01 Thread Mathieu Othacehe


Hello,

> ‘verify_server_cert’ in src/streams/openssl.c is called
> unconditionally.  So it seems that the first thing to do would be to
> submit a patch upstream that would allow users to disable certificate
> checks via ‘git_libgit2_opts’.

While this seems like something that we definitely want, I think we
shouldn't block the release with a contribution that can take time to be
upstreamed in libgit2.

Unblocking #53214.

Mathieu





bug#49862: While downloading substitutes: Wrong type argument in position 1 (expecting struct): #f

2022-11-01 Thread Maxim Cournoyer
Hi,

Adding yet another backtrace of that problem, that was triggered while
running './pre-inst-env guix build python-astroquery@0.4.6 vorta@0.8.7
cura@4.13.1 komikku@1.2.0 jrnl@1.9.7 pantalaimon@0.10.5
python-harmony@0.7.1 caja-extensions@1.24.1 gourmet@0.17.4-0.8af29c8
python-swiftclient@4.0.1 dbxfs@1.0.63 orange@3.32.0 linuxdcpp@1.1.0
ikiwiki@3.20200202.3 breezy@3.2.2 python-nanopb@0.4.6.4
openconnect-sso@0.7.3 qtile@0.18.1' with python-keyring having been
modified:

--8<---cut here---start->8---
diff --git a/gnu/packages/python-crypto.scm b/gnu/packages/python-crypto.scm
index 7b7aac6201..def347c06d 100644
--- a/gnu/packages/python-crypto.scm
+++ b/gnu/packages/python-crypto.scm
@@ -49,6 +49,7 @@ (define-module (gnu packages python-crypto)
   #:use-module (guix gexp)
   #:use-module (guix git-download)
   #:use-module (guix build-system cargo)
+  #:use-module (guix build-system pyproject)
   #:use-module (guix build-system python)
   #:use-module (guix utils)
   #:use-module (gnu packages)
@@ -326,29 +327,34 @@ (define-public python-kerberos
 (define-public python-keyring
   (package
 (name "python-keyring")
-(version "22.0.1")
+(version "23.9.3")
 (source
  (origin
-  (method url-fetch)
-  (uri (pypi-uri "keyring" version))
-  (sha256
-   (base32
-"1pvqc6may03did0iz98gasg7cy4h8ljzs4ibh927bfzda8a3xjws"
-(build-system python-build-system)
+   (method url-fetch)
+   (uri (pypi-uri "keyring" version))
+   (sha256
+(base32
+ "19f4jpsxng9sjfqi8ww5hgg196r2zh1zb8g71wjr1xa27kc1vc39"
+(build-system pyproject-build-system)
 (arguments
- `(#:phases
-   (modify-phases %standard-phases
- (replace 'check
-   (lambda* (#:key tests? #:allow-other-keys)
- (when tests?
-   (invoke "pytest" "-vv" "-c" "/dev/null" "tests")))
+ (list
+  #:test-flags '(list "-c" "/dev/null") ;avoid extra test dependencies
+  #:phases
+  #~(modify-phases %standard-phases
+  (add-before 'check 'workaround-test-failure
+(lambda _
+  ;; Workaround a failure in the test_entry_point test (see:
+  ;; https://github.com/jaraco/keyring/issues/526).
+  (delete-file-recursively "keyring.egg-info"))
 (native-inputs
  (list python-toml
python-pytest
python-setuptools
python-setuptools-scm))
 (propagated-inputs
- (list python-secretstorage))
+ (list python-importlib-metadata
+   python-jaraco-classes
+   python-secretstorage))
 (home-page "https://github.com/jaraco/keyring;)
 (synopsis "Store and access your passwords safely")
 (description
--8<---cut here---end--->8---

--8<---cut here---start->8---
Backtrace:
In guix/store.scm:
   1300:8 19 (call-with-build-handler _ _)
   1300:8 18 (call-with-build-handler # …)
In guix/ui.scm:
462:3 17 (_)
In ice-9/boot-9.scm:
  1747:15 16 (with-exception-handler # _ # _ # …)
  1752:10 15 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _)
In guix/ui.scm:
449:6 14 (_)
In guix/scripts/build.scm:
714:5 13 (_)
In srfi/srfi-1.scm:
   673:15 12 (append-map _ _ . _)
   586:17 11 (map1 ("x86_64-linux"))
In guix/scripts/build.scm:
   716:21 10 (_ _)
In guix/store.scm:
   1403:5  9 (map/accumulate-builds # 
# …)
  1419:15  8 (_ # _ _)
   739:14  7 (process-stderr _ _)
In unknown file:
   6 (display "@ substituter-succeeded 
/gnu/store/wjbisajny3c9pwj4crqyq3yd77gf2pfl-qtdeclarat…" …)
In guix/status.scm:
   733:16  5 (write! _ _ _)
   645:15  4 (_ (download-succeeded 
"/gnu/store/qwds28f6pqq5aaw90678v9qzfj6qiivq-texlive-amsf@" "s…" …) …)
   272:33  3 (compute-status _ #< building: (#< 
derivation: "/gnu/store/xc34bvzi…> …)
In ice-9/boot-9.scm:
  1685:16  2 (raise-exception _ #:continuable? _)
  1685:16  1 (raise-exception _ #:continuable? _)
  1685:16  0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
--8<---cut here---end--->8---

-- 
Thanks,
Maxim





bug#58146: podman issues

2022-11-01 Thread Hartmut Goebel

For rootlessport:

Quick work-around:

export CONTAINERS_HELPER_BINARY_DIR=$(realpath $(dirname $(which 
podman))/../libexec/podman)


Proper solution: Add an entry to the config file:

    // HelperBinariesDir is a list of directories which are used to 
search for

    // helper binaries.
    HelperBinariesDir []string `toml:"helper_binaries_dir"`

For catatonit:

Patch path in pkg/rootless/rootless_linux.c

--
Regards
Hartmut Goebel

| Hartmut Goebel  |h.goe...@crazy-compilers.com|
|www.crazy-compilers.com  | compilers which you thought are impossible |


bug#57589: Guix hands on GDM with wayland

2022-11-01 Thread Grigory Shepelev
Update. I can log into "Gnome on Xorg", change ownership of /tmp/.X11-unix
to root:gdm, log out, and them login into "Gnome". This will enable
Wayland.

вт, 6 сент. 2022 г. в 11:05, Grigory Shepelev :

> Creating new user didn't helped.
>
> I created new user (did this Guix way, via adding to config and
> reconfiguring the system) and logged it as a new user. Still X11 system
> displays with `xrandr`, and `echo $XDG_SESSION_TYPE`. I don't think
> there is a need to try moving all home files, creating new user should
> be enough to test provided option.
>
> Although I noticed a gear icon below in the right of the gdm screen when
> logging in as a default user (saw that in Ubuntu) with options "GNOME"
> or "GNOME on Xorg". Trying to login in "GNOME" (Wayland supposedly)
> gives a black screen for ~2s.  After couple attempts logged back into
> "GNOME on Xorg".
>
> Attached logs again. They says something about DBUS. Any ideas?
>
> ---
>
> (gsd-keyboard:5189): dbind-WARNING **: 13:35:36.273: AT-SPI: Error
> retrieving accessibility bus address:
> org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not
> provided by any .service files
> (gsd-xsettings:5219): dbind-WARNING **: 13:35:36.476: AT-SPI: Error
> retrieving accessibility bus address:
> org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not
> provided by any .service files
> GNOME Shell-Message: 13:35:36.777: Registering session with GDM
> The XKEYBOARD keymap compiler (xkbcomp) reports:
>  > Warning:  Unsupported maximum keycode 708, clipping.
>  >   X11 cannot support keycodes above 255.
> Errors from xkbcomp are not fatal to the X server
> (gnome-shell:5099): mutter-WARNING **: 13:36:02.454: Connection to
> xwayland lost
> ---
>
> On 05.09.2022 20:55, Grigory Shepelev wrote:
> > Had some info from Guix Matrix channel:
> > > GDM does wayland too with the option set to #t. I was able to get it
> > to work going back from sddm, but I had to remove the home folder and
> > recreate it from scratch, since gnome session was crashing on login. I
> > had no problem starting gnome on a new account so i figured something
> > was hanging around that cause a problem even after deleting all caches
> > and configs etc.
> > > By “home folder” I mean my user’s directory /home/use
> >
> >
> https://matrix.to/#/!jivGmMiiorFwdgwaxc:matrix.org/$W4HJQCzv8G0aHM3_PAFrtUaj6Q3aS18vMZCwlMch71I?via=matrix.org=hummingbard.com=privacytools.io
> > <
> https://matrix.to/#/!jivGmMiiorFwdgwaxc:matrix.org/$W4HJQCzv8G0aHM3_PAFrtUaj6Q3aS18vMZCwlMch71I?via=matrix.org=hummingbard.com=privacytools.io>
>
> >
> >
> > Most likely will try for new user tomorrow
> >
> > пн, 5 сент. 2022 г., 16:24 Grigory Shepelev :
> >
> >Oops. I accidentally replied privately to d...@jpoiret.xyz, not
> >mentioning 57...@debbugs.gnu.org. I hope the history can be recovered
> >from this message.
> >
> >Josselin recommended to
> >
> >- check permissions on /tmp/.X11-unix/ (gdm user should have r+w
> >permissions)
> >
> >  shegeley@zone51 /tmp$ ls -lah .X11-unix/
> >  total 0
> >  drwxrwxrwt 2 gdm  gdm80 сен  5 16:12 ./
> >  drwxrwxrwt 6 root root  160 сен  5 16:16 ../
> >  srwxrwxrwx 1 shegeley users   0 сен  5 16:12 X1
> >  srwxr-xr-x 1 gdm  gdm 0 сен  5 16:12 X1024
> >
> >-  check /var/lib/gdm/, doesn't have the proper permissions
> >
> > Hm. That's really strange. For some reason /var/lib/gdm had
> > "transmission" as user-group. I assure you that I didn't
> > explicitly
> > do any "dirty stuff" like that permission changing in my config
> >
> >
> > shegeley@zone51 /tmp$ sudo ls -lah /var/lib/gdm
> > total 0
> > drwx-- 1 gdm  gdm   38 авг 26 21:46 .
> > drwxr-xr-x 1 root root 248 авг 28 18:37 ..
> > drwxr-xr-x 1  973 transmission  62 авг 26 21:46 .cache
> > drwx-- 1  973 transmission  44 авг 26 21:46 .config
> > drwx-- 1  973 transmission  10 авг 26 21:46 .local
> > shegeley@zone51 /tmp$ sudo chown -R gdm:gdm /var/lib/gdm
> > shegeley@zone51 /tmp$ sudo ls -lah /var/lib/gdm
> > total 0
> > drwx-- 1 gdm  gdm   38 авг 26 21:46 .
> > drwxr-xr-x 1 root root 248 авг 28 18:37 ..
> > drwxr-xr-x 1 gdm  gdm   62 авг 26 21:46 .cache
> > drwx-- 1 gdm  gdm   44 авг 26 21:46 .config
> > drwx-- 1 gdm  gdm   10 авг 26 21:46 .local
> >
> >
> >After changing it was able to launch into GDM, but with X11 as display
> >manager :( Attached new logs.
> >
> >
> >On 05.09.2022 10:23, Josselin Poiret wrote:
> > > Hi again,
> > >
> > > Grigory Shepelev writes:
> > >
> > >> My config is heavily depends on it's directory (passing it with
> > >> --load-path). I can (and will) publish it all (I've been
> >planning to do
> > >> so) but I'd like to polish few parts.