bug#65720: Guile-Git-managed checkouts grow way too much

2023-09-05 Thread Josselin Poiret via Bug reports for GNU Guix
Hi Ludo,

Ludovic Courtès  writes:

> My inclination for the short term would be to work around this
> limitation by (1) finding a heuristic to determine is a checkout has
> likely accumulated too much cruft, and (2) considering such checkouts as
> expired (thereby forcing a re-clone) or running ‘git gc’ on them if
> ‘git’ is available.

I think using the git binary instead of libgit2 as a workaround is a
good idea.  We can consider building it directly as well, so that people
who don't have it in their profiles can still benefit from it.  We could
even consider using git commands in most places and using libgit2 only
where we really need the tight coupling.  IIUC, libgit2 is eternally
trying to catch up to git and often performs in a counter-intuitive way
(I expect the various bugs with stale deleted files in checkouts to be
caused by this).  Maybe it could also let us use bare repository and
directly extract the refs we want without having to mess with checkouts?

Best,
-- 
Josselin Poiret


signature.asc
Description: PGP signature


bug#65720: Guile-Git-managed checkouts grow way too much

2023-09-05 Thread Ludovic Courtès
Ludovic Courtès  skribis:

> $ du -hs 
> ~/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
> 6.7G
> /home/ludo/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq

Another data point, with Cuirass instances:

--8<---cut here---start->8---
ludo@berlin ~$ sudo du -hs 
/var/lib/cuirass/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
65G 
/var/lib/cuirass/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
ludo@berlin ~$ sudo stat 
/var/lib/cuirass/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
 | tail -1
 Birth: 2022-07-30 23:15:45.582559879 +0200
--8<---cut here---end--->8---

… and:

--8<---cut here---start->8---
ludo@guix-hpc4 ~$ sudo du -hs 
/var/lib/cuirass/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
86G 
/var/lib/cuirass/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
ludo@guix-hpc4 ~$ sudo stat 
/var/lib/cuirass/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
 | tail -1
  Créé : 2021-06-01 11:48:48.854669310 +0200
--8<---cut here---end--->8---

So yeah, problem we have.

Ludo’.





bug#65720: Guile-Git-managed checkouts grow way too much

2023-09-05 Thread Ludovic Courtès
Hi,

Josselin Poiret  skribis:

> I think using the git binary instead of libgit2 as a workaround is a
> good idea.  We can consider building it directly as well, so that people
> who don't have it in their profiles can still benefit from it.  We could
> even consider using git commands in most places and using libgit2 only
> where we really need the tight coupling.

Surely you’d agree that it would suck though: depending on two Git
implementations because one doesn’t have a proper API and the other one
lacks a bunch of features.

It would also be pretty bad for closure size:

--8<---cut here---start->8---
$ guix size guile-git | tail -1
total: 106.6 MiB
$ guix size guile-git git-minimal | tail -1
total: 169.8 MiB
--8<---cut here---end--->8---

It’s also not clear concretely how we’d add that dependency.  Try
invoking ‘git’ from $PATH and print a warning if it doesn’t work?
But then, what about applications like Cuirass and hpcguix-web?

Tricky, tricky.

Ludo’.





bug#65720: Guile-Git-managed checkouts grow way too much

2023-09-05 Thread Ludovic Courtès
Hello,

Jelle Licht  skribis:

>> On 4 Sep 2023, at 23:49, Ludovic Courtès  wrote:
>> 
>> Of course having to re-clone entire repositories every 9 months is
>> ridiculous, but storing gigabytes of packs is worse IMO (I’m
>> specifically thinking about the Guix repo, which every users copies via
>> ‘guix pull’).
>
> Please ignore if it doesn’t make sense, or would not make a practical 
> difference for the current issue, but wouldn’t a local clone do the trick 
> here? As in, clone from the ‘clogged’ local repo, move over fresh clone to 
> old location.

Good question.

--8<---cut here---start->8---
scheme@(guix git)> ,use(git)
scheme@(guix git)> (clone 
"/home/ludo/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq/"
 "/tmp/fresh-clone")
$7 = #
scheme@(guix git)> (system* "du" "-hs" "/tmp/fresh-clone")
6.7G/tmp/fresh-clone
$8 = 0
scheme@(guix git)> (system* "du" "-hs" "/tmp/fresh-clone/.git")
6.6G/tmp/fresh-clone/.git
$9 = 0
scheme@(guix git)> (system* "du" "-hs" 
"/home/ludo/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq/")
6.7G
/home/ludo/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq/
$10 = 0
--8<---cut here---end--->8---

Conclusion: it makes no difference.

Ludo’.





bug#65759: Bug

2023-09-05 Thread Sjors Provoost
While testing: https://github.com/bitcoin/bitcoin/pull/27099

But it's been a few months since I last ran a Guix build. The machine is an AMD 
running Ubuntu 23.04



$ HOSTS='x86_64-apple-darwin arm64-apple-darwin' ./contrib/guix/guix-build || 
echo -e "\a"
Found macOS SDK at 
'/home/guix/SDKs/Xcode-12.2-12B45b-extracted-SDK-with-libcxx-headers', using...
Checking that we can connect to the guix-daemon...

Hint: If this hangs, you may want to try turning your guix-daemon off and on
  again.

make: Entering directory '/home/guix/bitcoin/depends'
make[1]: Entering directory '/home/guix/bitcoin/depends'
Fetching clang+llvm-15.0.6-x86_64-linux-gnu-ubuntu-18.04.tar.xz from 
https://github.com/llvm/llvm-project/releases/download/llvmorg-15.0.6
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100  779M  100  779M0 0  47.9M  0  0:00:16  0:00:16 --:--:-- 50.2M
/home/guix/bitcoin/depends/work/download/native_clang-15.0.6/clang+llvm-15.0.6-x86_64-linux-gnu-ubuntu-18.04.tar.xz.temp:
 OK
make[1]: Leaving directory '/home/guix/bitcoin/depends'
make: Leaving directory '/home/guix/bitcoin/depends'
make: Entering directory '/home/guix/bitcoin/depends'
make[1]: Entering directory '/home/guix/bitcoin/depends'
make[1]: Leaving directory '/home/guix/bitcoin/depends'
make: Leaving directory '/home/guix/bitcoin/depends'
INFO: Building 8a6275ba6ea6 for platform triple x86_64-apple-darwin:
  ...using reference timestamp: 1668774980
  ...running at most 32 jobs
  ...from worktree directory: '/home/guix/bitcoin'
  ...bind-mounted in container to: '/bitcoin'
  ...in build directory: 
'/home/guix/bitcoin/guix-build-8a6275ba6ea6/distsrc-8a6275ba6ea6-x86_64-apple-darwin'
  ...bind-mounted in container to: 
'/distsrc-base/distsrc-8a6275ba6ea6-x86_64-apple-darwin'
  ...outputting in: 
'/home/guix/bitcoin/guix-build-8a6275ba6ea6/output/x86_64-apple-darwin'
  ...bind-mounted in container to: '/outdir-base/x86_64-apple-darwin'
Updating channel 'guix' from Git repository at 
'https://git.savannah.gnu.org/git/guix.git'...
Authenticating channel 'guix', commits 9edb3f6 to 160f78a (7724 new commits)...
building /gnu/store/pha3iazj4i3hhxc6j07g3gl68kiarg1v-module-import.drv...
building /gnu/store/rm5splyvkr1w3i21q6j4n9zrbgl4yic3-module-import.drv...
The following build is still in progress:
  /gnu/store/pha3iazj4i3hhxc6j07g3gl68kiarg1v-module-import.drv

building 
/gnu/store/55hx73ai8w2r7ww325v0f9wznsr1nm2z-module-import-compiled.drv...
The following build is still in progress:
  /gnu/store/55hx73ai8w2r7ww325v0f9wznsr1nm2z-module-import-compiled.drv

building 
/gnu/store/ijdhhif0jk6skdw259l2c77blrhb3482-module-import-compiled.drv...
The following build is still in progress:
  /gnu/store/55hx73ai8w2r7ww325v0f9wznsr1nm2z-module-import-compiled.drv

building 
/gnu/store/d0wyv6a8gjvycqslcx436nj1b39fxqfg-compute-guix-derivation.drv...
Computing Guix derivation for 'x86_64-linux'... /
building 
/gnu/store/cc265bcg6f019ipzc33a226ip1iq6997-coreutils-mesboot-9.1.drv...
building /gnu/store/3g5lsfrhmx2k37p1w6040bia3zbplqcc-git-2.41.0.tar.xz.drv...
building 
/gnu/store/dw9xlqhk94xsznf5birnq0s0aykvxk78-guile-gnutls-3.7.12.tar.gz.drv...
building /gnu/store/6x3x8h1sghn3r8rz6x35vzp2a2cih7zv-libssh-0.10.5.tar.xz.drv...
The following builds are still in progress:
  /gnu/store/cc265bcg6f019ipzc33a226ip1iq6997-coreutils-mesboot-9.1.drv
  /gnu/store/dw9xlqhk94xsznf5birnq0s0aykvxk78-guile-gnutls-3.7.12.tar.gz.drv

The following build is still in progress:
  /gnu/store/cc265bcg6f019ipzc33a226ip1iq6997-coreutils-mesboot-9.1.drv

The following build is still in progress:
  /gnu/store/cc265bcg6f019ipzc33a226ip1iq6997-coreutils-mesboot-9.1.drv

building /gnu/store/s1g7nm73ihp1sb8pa322n1a16qf6xjr1-make-boot0-4.3.drv...
building /gnu/store/jzf9d76xqii0nbgjyyx482yg0hij6b8z-coreutils-boot0-9.1.drv...
building /gnu/store/xfdmqahh02349l6ax8gqisnn8scly094-diffutils-boot0-3.8.drv...
building /gnu/store/xj0gqmg3jj3v0xfsj9njl5yb1fjzkmy7-file-boot0-5.44.drv...
building /gnu/store/lrd856zgqky0gq0xq1p8wcsqaw1bdhfr-gawk-boot0-5.2.1.drv...
building /gnu/store/vyqhl0rk69r5di33d5bd4alsi1x8nynl-patch-boot0-2.7.6.drv...
building /gnu/store/5zcrpv3lcydcn1bc5jg5s1s9dswkrvvg-sed-boot0-4.8.drv...
building /gnu/store/w8schnwd6fxplb9p3f0x41750q3x3as2-tar-boot0-1.34.drv...
The following builds are still in progress:
  /gnu/store/jzf9d76xqii0nbgjyyx482yg0hij6b8z-coreutils-boot0-9.1.drv
  /gnu/store/lrd856zgqky0gq0xq1p8wcsqaw1bdhfr-gawk-boot0-5.2.1.drv
  /gnu/store/w8schnwd6fxplb9p3f0x41750q3x3as2-tar-boot0-1.34.drv
  /gnu/store/5zcrpv3lcydcn1bc5jg5s1s9dswkrvvg-sed-boot0-4.8.drv
  /gnu/store/xfdmqahh02349l6ax8gqisnn8scly094-diffutils-boot0-3.8.drv
  /gnu/store/vyqhl0rk69r5di33d5bd4alsi1x8nynl-patch-boot0-2.7.6.drv

The following builds are still in prog

bug#65761: OpenBLAS ILP64 using `-ilp64` lib name suffix instead of the standard `64_`

2023-09-05 Thread Maya Tomasek via Bug reports for GNU Guix


The problem is as per official OpenBLAS docs
(https://github.com/xianyi/OpenBLAS/blob/c3f2a3c0ca8d4a3700f81f176dd3f1bc08cff3dd/docs/distributing.md?plain=1#L79)
that some applications expect a `libopenblas64_.so` name, but Guix
chooses it's custom `-ilp64`. This messes up with Julia for example. If
the suffix `-ilp64` is needed, there also needs to be a `64_`
suffix. Otherwise some apps inexplicably fail on a wrongly named file.

Maya





bug#65560: You found a bug:

2023-09-05 Thread Simon Tournier
Hi,

Thanks for your report.

On Sun, 27 Aug 2023 at 08:25, Rua via Bug reports for GNU Guix 
 wrote:
> guix pull

[...]

> 1. &store-protocol-error:
> message: "some substitutes for the outputs of derivation 
> `/gnu/store/gm8pw2qwi35d5nc5dz7gqagp0yjmjlp2-po4a-0.69.drv' failed (usually 
> happens due to networking issues); try `--fallback' to build derivation from 
> source "

Oups, so bad user experience and unfriendly message.  Sorry.

Have you tried

guix pull --fallback

?

Cheers,
simon





bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs

2023-09-05 Thread Simon Tournier
Hi,

On Thu, 31 Aug 2023 at 15:14, Ulf Herrman  wrote:

> I propose that we have the build system lower procedure (that is, the
> one that converts from package to bag) completely fill in the argument
> list with all defaults, and we modify build-system-with-package-mapping
> to transform all arguments that look like a package or a list of
> packages (or maybe even a tree containing packages).

On principle, this looks a good idea.

Do you already have an implementation?  Because transformations lead to
headache and sometimes the implementation is hard, well evil, details
and all that. :-)

Cheers,
simon





bug#65465: Something from recent commits is broken.

2023-09-05 Thread Simon Tournier
Hi,

On Wed, 23 Aug 2023 at 04:33, bashScript  wrote:
> While trying to run `guix pull` I am getting this this,

[...]

> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> error: license:arphic-1999: unbound variable

What is the Guix revision against which it happens?

I guess now this is solved.


Cheers,
simon





bug#65236: package/inherit records lack location for version field

2023-09-05 Thread Simon Tournier
Hi Maxim,

On Fri, 11 Aug 2023 at 21:27, Maxim Cournoyer  wrote:

> --8<---cut here---start->8---
> (use-modules (guix package)
>  (gnu packages qt))
>
> (package-field-location qtbase 'version)
>
> => #f
> --8<---cut here---end--->8---

[...]

> Now, package/inherit is bogus here, but the problems remains for other
> packages, such as zxing-cpp-1.2.

I think it is fixed by .

Cheers,
simon





bug#65522: Documentation for some home services disappeared from 1.4 manual

2023-09-05 Thread Simon Tournier
Hi,

On Fri, 25 Aug 2023 at 08:16, nils@landt.email wrote:

> I noticed some help nodes under 
> https://guix.gnu.org/en/manual/en/html_node/Home-Services.html disappeared 
> fairly recently.
> They are still available in the devel docs under 
> https://guix.gnu.org/en/manual/devel/en/html_node/Home-Services.html
>
> The following topics are missing:
> * GPG: GNU Privacy Guard.   Setting up GPG and related tools.
> * Fonts: Fonts Home Services.   Services for managing User's fonts.
> * Sound: Sound Home Services.   Dealing with audio.
> * Mail: Mail Home Services. Services for managing mail.
> * Messaging: Messaging Home Services.  Services for managing messaging.
> * Media: Media Home Services.   Services for managing media.
> * Networking: Networking Home Services.  Networking services.
> * Miscellaneous: Miscellaneous Home Services.  More services.
>
> This makes sense when looking at the 1.4.0 git tag, but I had a browser tab 
> open, and https://guix.gnu.org/manual/en/html_node/Mail-Home-Services.html 
> was definitely available just a day or two ago.
>
> I don't know if this is actually an issue or an intended change, but it 
> seemed better to report it than to ignore it.

I am sorry, I am not sure to understand what the bug is about. :-)

This webpage
 points
to the manual as it was for the last release.  It means, this manual
wepage is frozen and is only updated at each release.  If you have seen
something different, it is an artifact that should not be possible.

For instance, the service

* GPG: GNU Privacy Guard.   Setting up GPG and related tools.

had been added on Sat Apr 8 22:56:19 2023 +0200 which is after the
release 1.4.0.

There is no bug and I am favor to close it.  WDYT?


Cheers,
simon





bug#63170: The issue no longer exists.

2023-09-05 Thread Simon Tournier
Hi,

On Wed, 23 Aug 2023 at 06:19, Apoorv  wrote:
> The issue seems to be fixed now. It's been a while actually, I just forgot
> to respond here.

Thanks for the notification.  So I am closing.


Cheers,
simon





bug#65495: Error from compute-guix-derivation

2023-09-05 Thread Simon Tournier
Hi,

Thanks for your report.

On Thu, 24 Aug 2023 at 12:52, Richard Lawrence  wrote:

> I ran "guix pull" for the first time in a while this morning and got the
> following error, which guix asked me to report here:
>
> ./guix/store.scm:1417:15: In procedure loop:
> ERROR:
>   1. &store-protocol-error:
>   message: "build of 
> `/gnu/store/wfck89415b22gqq25fi0mypgrw8vw1c8-ghostscript-9.56.1.drv' failed"
>   status: 1
> guix pull: error: You found a bug: the program 
> '/gnu/store/2h6lpkk5030gcaavxpa54lgss0n5g0vz-compute-guix-derivation'
> failed to compute the derivation for Guix (version: 
> "39fa1ef033fda82cb1d122e0d1675b51acb1db34"; system: "x86_64-linux";
> host version: "a79950af1568c262a79fc0cdfd391b7328c058cf"; pull-version: 1).
>
> Complete output below. For what it's worth, I suspect this is related to
> the disk running out of space during the build. After guix errored out,
> df reports that my root partition is 100% full.

Maybe you could run “guix gc” for collecting some free space.

Well,

guix time-machine --commit=a79950af1568c262a79fc0cdfd391b7328c058cf \
  -- time-machine --commit=39fa1ef033fda82cb1d122e0d1675b51acb1db34 \
  -- describe

runs for me.  Maybe we could detect if enough free space is around
before launching the heavy computations and/or download.

Cheers,
simon





bug#64719: rxvt-unicode 9.31 prompt is in the wrong place

2023-09-05 Thread Leo Famulari
Fixed with commit 8b8607a9452b7690b15f7db2613abdc211d40cee





bug#65720: Guile-Git-managed checkouts grow way too much

2023-09-05 Thread Simon Tournier
Hi,

On Mon, 04 Sep 2023 at 23:47, Ludovic Courtès  wrote:

>> It would seem that libgit2 doesn’t do the equivalent of ‘git gc’.
>
> Confirmed: .

Ouch!

The goals of the project haven't changed, and neither have the
tradeoffs. If one were to rewrite git-gc on top of libgit2, the
best-case scenario is ending up with what we already had.

If you want to use regular maintenance on some repostories, use
git gc, that's what it's there for.

https://github.com/libgit2/libgit2/issues/3247#issuecomment-152508040

> My inclination for the short term would be to work around this
> limitation by (1) finding a heuristic to determine is a checkout has
> likely accumulated too much cruft, and (2) considering such checkouts
> as expired (thereby forcing a re-clone) or running ‘git gc’ on them if
> ‘git’ is available.

About (1) maybe we could add a “counter” and teach after X updates of
the checkout then let run (2).  Well, I guess the number of crufts is
more or less proportional with the number of checkout updates; that’s
the heuristic I would use.

The most annoying is (2).  Because forcing a re-clone does not appear to
me a solution; I prefer to waste disk space (and probably run myself and
manually ‘git gc’) than re-clone… Somehow this re-clone would always
happen when I am using a poor network.

Moreover, assuming this clean-up (2) would be run once every while, we
could imagine to invoke something like,

guix shell -C git-minimal
 -- git
 -C 
~/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
 gc

when the checkout is updated.  And maybe we could provide another “guix
pull” command-line option for turning off this and mark it as done
(reset the “counter”).

Well, that’s a poor solution but we can assume that git-minimal is at
worse available using “guix shell git-minimal”.  Note that the closure
of git-minimal is far less than re-cloning the full Guix repository.

Cheers,
simon





bug#65460: ghc/ghci are broken

2023-09-05 Thread Simon Tournier
Hi Maxim,

On Tue, 29 Aug 2023 at 17:07, Maxim Cournoyer  wrote:

> For building tools requiring a compiler, the current expectation across
> Guix packages is that the user provides the one it wants.  Even if using
> GCC, you may want to use a different version, and rebuilding GHC just to
> do so is... expensive.

Well, I have a patch series somewhere on my disk that adds ghc-toolchain
and hides ghc, similarly as gcc-toolchain.  Somehow, I think that, “guix
shell ghc-toolchain” should just work out-of-the-box.  And the
replacement of the C toolchain would be done with the package
transformation with-c-toolchain.

Bah, the series needs polishing…  arf!

Cheers,
simon





bug#65208: etc/teams.scm regexp

2023-09-05 Thread Simon Tournier
Hi Maxim,

On Tue, 29 Aug 2023 at 15:22, Maxim Cournoyer  wrote:

> Closing.  Thanks for the report and for Simon for fixing it.

Cool, thank you for the improvements.

Cheers,
simon





bug#65765: Celluloid is broken

2023-09-05 Thread Csepp
Guix commit: d6966b8 (5 days old)
Trying to run celluloid results in this error:
celluloid: ../stream/stream.c:416: stream_create_with_args: Assertion 
`args->url' failed.

both celluloid and mpv are up to date according to guix refresh

It doesn't matter what arguments celluloid gets, the result always seems
to be the same.

I thought it had tests turned off, but no, it looks like its testsuite
is just very incomplete, because it definitely should have caught this.





bug#64509: Guile packages should install versioned aliases for binaries (guile-X.Y, guild-X.Y, etc.)

2023-09-05 Thread Zack Weinberg
On Mon, Aug 21, 2023, at 3:37 AM, Janneke Nieuwenhuizen wrote:

> It's terrible that guile.m4 has this feature of preferring numbered
> binaries (even if they're later in PATH, and even if that binary
> doesn't match GUILE_LOAD_*PATHs)

I can see why it does this -- it wants to find the newest available
Guile and it wants to be sure that all the binaries it uses are a
matched set. The original design assumption was probably that, if you're
using numbered binaries, then the un-suffixed "guile" can't be relied on
to be the newest available.  (Not as strange as it might sound; I have a
login on a machine where un-suffixed "perl" still runs Perl 5.005_02,
because the admins want to make absolutely sure that they never break
any user's #! scripts.)

It would probably be a good idea for guile.m4 to be altered to take the
un-suffixed binaries if that's the only way it can get a full set, but
given how long it takes for Autoconf macro changes to propagate to the
world, I think Guix should provide the numbered binaries regardless.

> and that Guix doesn't provide them. What about a wrapper package that
> provides these?

Why bother with a wrapper?  It should be _easier_ to have the main guile
package supply the numbered binaries.

>> I think the solution is to use ‘guix shell -D guix -CP'
...
> Hmm, yeah -- that sounds like the proper way of doing things
...

Not an option for me, for reasons explained in my earlier reply to
Ludovic.

zw





bug#65769: greetd-wlgreet-sway-session result is blinking cursor

2023-09-05 Thread chris
Hello and thank you in advance for reading me. When defining 
wlgreet-sway-session in my system config, the result is a blinking cursor. 
There is no login screen. To login or issue any command, it is necessary to 
switch to a different tty with something like Alt+fn+F2.

In irc, I messaged the user who created greetd-wlgreet-sway-session and it 
seems other users have encountered the blinking cursor and no one knows of a 
solution. If possible, I would like help troubleshoot and resolve the issue.

My config file is here,
https://raw.githubusercontent.com/iambumblehead/guix-home/main/guix.system.scm

```bash
$ sudo tail -5 /var/log/greetd-1.log
2023-09-05 18:59:22 error: check_children: greeter exited without creating a 
session
2023-09-05 18:59:23 error: check_children: greeter exited without creating a 
session
2023-09-05 18:59:24 error: check_children: greeter exited without creating a 
session
2023-09-05 18:59:25 error: check_children: greeter exited without creating a 
session
2023-09-05 18:59:27 error: check_children: greeter exited without creating a 
session
```

I've tried defining some XDG vars in /home/greeter/.profile and sometimes this 
causes error messages to appear above the blinking cursor, but no positive 
result.

Please anyone feel free to give advice or suggest any things that I might try.





bug#65770: xdg-desktop-portal-kde only works if system is reconfigured with gnome-desktop-service-type

2023-09-05 Thread Nathan Dehnel
if gnome-desktop is enabled:
-kde file picker works
if gnome-dekstop is not installed:
Gtk-WARNING **: 22:04:20.326: Can't open portal file chooser:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process
org.freedesktop.portal.Desktop received signal 5

guix c3d48d0





bug#65772: kmail fails to start "unable to obtain agent type"

2023-09-05 Thread Nathan Dehnel
guix c3d48d0

~ $ kmail
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
QSqlDatabasePrivate::addDatabase: duplicate connection name
'initConnection', old connection removed.
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: DB initializer done
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadicontrol: Duplicated agent identifier
"akonadi_archivemail_agent" from file
"/gnu/store/imzbmaql230a69qn43p8cl3ivlsby54
k-kmail-23.04.3/share/akonadi/agents/archivemailagent.desktop"
org.kde.pim.akonadicontrol: Duplicated agent identifier
"akonadi_followupreminder_agent" from file
"/gnu/store/imzbmaql230a69qn43p8cl3ivl
sby54k-kmail-23.04.3/share/akonadi/agents/followupreminder.desktop"
org.kde.pim.akonadicontrol: Duplicated agent identifier
"akonadi_mailfilter_agent" from file
"/gnu/store/imzbmaql230a69qn43p8cl3ivlsby54k
-kmail-23.04.3/share/akonadi/agents/mailfilteragent.desktop"
org.kde.pim.akonadicontrol: Duplicated agent identifier
"akonadi_mailmerge_agent" from file
"/gnu/store/imzbmaql230a69qn43p8cl3ivlsby54k-
kmail-23.04.3/share/akonadi/agents/mailmergeagent.desktop"
org.kde.pim.akonadicontrol: Duplicated agent identifier
"akonadi_sendlater_agent" from file
"/gnu/store/imzbmaql230a69qn43p8cl3ivlsby54k-
kmail-23.04.3/share/akonadi/agents/sendlateragent.desktop"
org.kde.pim.akonadicontrol: Duplicated agent identifier
"akonadi_unifiedmailbox_agent" from file
"/gnu/store/imzbmaql230a69qn43p8cl3ivlsb
y54k-kmail-23.04.3/share/akonadi/agents/unifiedmailboxagent.desktop"
org.kde.pim.akonadicontrol: Duplicated agent identifier
"akonadi_knut_resource" from file
"/gnu/store/vyaabsl9z64x2z8z9709zhl5r35g9wxb-ak
onadi-23.04.3/share/akonadi/agents/knutresource.desktop"
org.kde.pim.akonadicontrol: Akonadi server is now operational.
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc54007690) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc54015af0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc54015e00) )
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc54015e00) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc540299e0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc5402a850) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc5402b650) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc5403cd90) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc5403e180) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc540574f0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc540584b0) )
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc54007690) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc54072d00) )
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc54015e00) )
org.kde.pim.akonadiserver: Subscriber "" disconnected
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc540299e0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7efc540172d0) )
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7efc54072d00) identified as
"SpecialCollectionsMonitor -
27760656"
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7efc54072d00) identified as
"SpecialCollectionsMonitor -
27760656"
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7efc54015e00) identified as
"MessageListTagMonitor - 2926
9232"
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7efc54015e00) identified as
"MessageListTagMonitor - 2926
9232"
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7efc540299e0) identified as
"MessageViewerMonitor - 28829
152"
o

bug#44450: Issues installing Avogadro

2023-09-05 Thread Maxim Cournoyer
Hi,

zimoun  writes:

> Dear,
>
> Thank you for the report.
>
> On Wed, 04 Nov 2020 at 19:17, Godefroy Vannoye  
> wrote:
>
>> First let me apologize if I have missed something, I'm a new user of
>> guix and know only the basics about compilation processes.
>
> Welcome! :-)
>
>
>> I am using guix on the Arch distribution, and installed it using the
>> shell installer script. My first tests seem to indicate that guix is
>> installed properly.
>
> The Guix Data Service indicates that the package avogrado is broken.
>
> https://data.guix.gnu.org/repository/1/branch/master/package/avogadro/output-history

We now have avogradro2, which builds correctly.

-- 
Thanks,
Maxim





bug#65773: html updater may fail when page has moved (guix refresh gambit-c)

2023-09-05 Thread Maxim Cournoyer
Hi,

Attempting to 'guix refresh gambit-c' currently fails like:

--8<---cut here---start->8---
./pre-inst-env guix refresh gambit-c
Backtrace:
In ice-9/eval.scm:
619:8 19 (_ #(#(#)))
In guix/ui.scm:
   2323:7 18 (run-guix . _)
  2286:10 17 (run-guix-command _ . _)
In ice-9/boot-9.scm:
  1752:10 16 (with-exception-handler _ _ #:unwind? _ # _)
  1752:10 15 (with-exception-handler _ _ #:unwind? _ # _)
In guix/store.scm:
   659:37 14 (thunk)
  2168:25 13 (run-with-store # …)
In guix/scripts/refresh.scm:
   632:14 12 (_ _)
In srfi/srfi-1.scm:
634:9 11 (for-each # …)
In guix/scripts/refresh.scm:
   402:10 10 (check-for-package-update #< package: # …)
In srfi/srfi-1.scm:
   858:15  9 (any1 # …)
In guix/import/utils.scm:
131:4  8 (call-with-networking-exception-handler _)
In ice-9/boot-9.scm:
  1752:10  7 (with-exception-handler _ _ #:unwind? _ # _)
In guix/gnu-maintenance.scm:
   643:18  6 (import-html-release _ _ #:rewrite-url? _ #:version _ # …)
568:6  5 (rewrite-url _ "4.9.5" #:to-version _)
In srfi/srfi-1.scm:
   460:18  4 (fold # …)
In guix/gnu-maintenance.scm:
   603:25  3 (_ _ _)
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:
no candidates found in rewrite-url
--8<---cut here---end--->8---

That's because http-fetch/cached doesn't following redirection:

--8<---cut here---start->8---
$ curl http://www.gambitscheme.org/4.9.4

301 Moved Permanently

301 Moved Permanently
nginx


--8<---cut here---end--->8---

which means the page is reachable but doesn't contain the expected
content.

-- 
Thanks,
Maxim





bug#65773: html updater may fail when page has moved (guix refresh gambit-c)

2023-09-05 Thread Maxim Cournoyer
Hi,

Maxim Cournoyer  writes:

> Hi,
>
> Attempting to 'guix refresh gambit-c' currently fails like:
>
> ./pre-inst-env guix refresh gambit-c
> Backtrace:
> In ice-9/eval.scm:
> 619:8 19 (_ #(#(#)))
> In guix/ui.scm:
>2323:7 18 (run-guix . _)
>   2286:10 17 (run-guix-command _ . _)
> In ice-9/boot-9.scm:
>   1752:10 16 (with-exception-handler _ _ #:unwind? _ # _)
>   1752:10 15 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/store.scm:
>659:37 14 (thunk)
>   2168:25 13 (run-with-store # …)
> In guix/scripts/refresh.scm:
>632:14 12 (_ _)
> In srfi/srfi-1.scm:
> 634:9 11 (for-each # …)
> In guix/scripts/refresh.scm:
>402:10 10 (check-for-package-update #< package: # …)
> In srfi/srfi-1.scm:
>858:15  9 (any1 # …)
> In guix/import/utils.scm:
> 131:4  8 (call-with-networking-exception-handler _)
> In ice-9/boot-9.scm:
>   1752:10  7 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/gnu-maintenance.scm:
>643:18  6 (import-html-release _ _ #:rewrite-url? _ #:version _ # …)
> 568:6  5 (rewrite-url _ "4.9.5" #:to-version _)
> In srfi/srfi-1.scm:
>460:18  4 (fold # …)
> In guix/gnu-maintenance.scm:
>603:25  3 (_ _ _)
> 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:
> no candidates found in rewrite-url

Mitigated with 589384102f ("gnu-maintenance: Do not error when there are
no candidates.").

-- 
Thanks,
Maxim





bug#65769: wlgreet-sway-session

2023-09-05 Thread chris
Attached to this message is the content of /tmp/sway-greeter.388.log
00:00:00.000 [INFO] [sway/main.c:338] Sway version 1.8.1
00:00:00.000 [INFO] [sway/main.c:339] wlroots version 0.16.2
00:00:00.003 [INFO] [sway/main.c:120] Linux guix-xps 6.4.12 #1 SMP 
PREEMPT_DYNAMIC 1 x86_64 GNU/Linux
00:00:00.003 [INFO] [sway/main.c:136] Contents of /etc/os-release:
00:00:00.003 [INFO] [sway/main.c:120] NAME="Guix System"
00:00:00.003 [INFO] [sway/main.c:120] ID=guix
00:00:00.003 [INFO] [sway/main.c:120] PRETTY_NAME="Guix System"
00:00:00.003 [INFO] [sway/main.c:120] LOGO=guix-icon
00:00:00.003 [INFO] [sway/main.c:120] HOME_URL="https://guix.gnu.org";
00:00:00.003 [INFO] [sway/main.c:120] 
DOCUMENTATION_URL="https://guix.gnu.org/en/manual";
00:00:00.003 [INFO] [sway/main.c:120] SUPPORT_URL="https://guix.gnu.org/en/help";
00:00:00.003 [INFO] [sway/main.c:120] 
BUG_REPORT_URL="https://lists.gnu.org/mailman/listinfo/bug-guix";
00:00:00.003 [INFO] [sway/main.c:108] LD_LIBRARY_PATH=
00:00:00.003 [INFO] [sway/main.c:108] LD_PRELOAD=
00:00:00.003 [INFO] [sway/main.c:108] 
PATH=/run/setuid-programs:/home/greeter/.config/guix/current/bin:/home/greeter/.guix-profile/bin:/run/current-system/profile/bin:/run/current-system/profile/sbin
00:00:00.003 [INFO] [sway/main.c:108] SWAYSOCK=
00:00:00.004 [INFO] [sway/main.c:376] Starting sway version 1.8.1
00:00:00.004 [DEBUG] [sway/server.c:67] Initializing Wayland server
00:00:00.004 [INFO] [wlr] [libseat] [libseat/libseat.c:73] Seat opened with 
backend 'seatd'
00:00:00.004 [INFO] [wlr] [libseat] [libseat/backend/seatd.c:212] Enabling seat
00:00:00.004 [INFO] [wlr] [backend/session/session.c:109] Successfully loaded 
libseat session
00:00:00.005 [INFO] [wlr] [backend/backend.c:220] Found 1 GPUs
00:00:00.005 [INFO] [wlr] [backend/drm/backend.c:200] Initializing DRM backend 
for /dev/dri/card0 (i915)
00:00:00.005 [DEBUG] [wlr] [backend/drm/drm.c:88] Using atomic DRM interface
00:00:00.005 [DEBUG] [wlr] [backend/drm/drm.c:100] ADDFB2 modifiers supported
00:00:00.005 [INFO] [wlr] [backend/drm/drm.c:253] Found 3 DRM CRTCs
00:00:00.005 [INFO] [wlr] [backend/drm/drm.c:180] Found 9 DRM planes
00:00:00.006 [INFO] [wlr] [render/egl.c:201] Supported EGL client extensions: 
EGL_EXT_client_extensions EGL_EXT_device_base EGL_EXT_device_enumeration 
EGL_EXT_device_query EGL_EXT_platform_base 
EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_EXT_platform_device 
EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_EXT_platform_x11 
EGL_KHR_platform_x11 EGL_EXT_platform_xcb EGL_MESA_platform_gbm 
EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
00:00:00.006 [DEBUG] [wlr] [render/egl.c:469] Using EGL device /dev/dri/card0
00:00:00.036 [INFO] [wlr] [render/egl.c:347] Using EGL 1.5
00:00:00.036 [INFO] [wlr] [render/egl.c:348] Supported EGL display extensions: 
EGL_ANDROID_blob_cache EGL_ANDROID_native_fence_sync 
EGL_EXT_create_context_robustness EGL_EXT_image_dma_buf_import 
EGL_EXT_image_dma_buf_import_modifiers EGL_IMG_context_priority 
EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_context_flush_control 
EGL_KHR_create_context EGL_KHR_create_context_no_error EGL_KHR_fence_sync 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace 
EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image 
EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image_base 
EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context 
EGL_EXT_pixel_format_float EGL_KHR_wait_sync EGL_MESA_configless_context 
EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_MESA_query_driver 
EGL_WL_bind_wayland_display 
00:00:00.036 [INFO] [wlr] [render/egl.c:350] Supported EGL device extensions: 
EGL_EXT_device_drm EGL_EXT_device_drm_render_node
00:00:00.036 [INFO] [wlr] [render/egl.c:352] EGL vendor: Mesa Project
00:00:00.036 [DEBUG] [wlr] [render/egl.c:121] Supported DMA-BUF formats:
00:00:00.036 [DEBUG] [wlr] [render/egl.c:165]   AB4H (0x48344241)
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] INVALID (0x00FF): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] LINEAR (0x): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] X_TILED (0x0101): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] Y_TILED (0x0102): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:165]   XB4H (0x48344258)
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] INVALID (0x00FF): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] LINEAR (0x): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] X_TILED (0x0101): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] Y_TILED (0x0102): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wlr] [render/egl.c:165]   AB48 (0x38344241)
00:00:00.036 [DEBUG] [wlr] [render/egl.c:104] INVALID (0x00FF): 
✓ texture  ✓ render
00:00:00.036 [DEBUG] [wl

bug#65769: wlgreet-sway-session

2023-09-05 Thread chris


In case the attachment is not-accessible, important last lines of 
sway-greeter.388.log are pasted here.
```
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-1.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-2.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-3.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-4.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-5.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-6.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-7.lock check permissions
00:00:00.066 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-8.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-9.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-10.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-11.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-12.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-13.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-14.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-15.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-16.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-17.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-18.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-19.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-20.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-21.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-22.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-23.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-24.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-25.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-26.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-27.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-28.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-29.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-30.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-31.lock check permissions
00:00:00.067 [INFO] [wlr] [wayland] unable to open lockfile 
/run/user/986/wayland-32.lock check permissions
00:00:00.067 [ERROR] [sway/server.c:231] Unable to open wayland socket
00:00:00.067 [DEBUG] [wlr] [types/wlr_drm_lease_v1.c:103] Destroying 
wlr_drm_lease_device_v1 for /dev/dri/card0
```





bug#65774: python updater clears inputs, leaves propagated-inputs empty

2023-09-05 Thread Maxim Cournoyer
Hi,

I've had the Python updater produce this when attempting to update
fontmake:

gnu/packages/fontutils.scm:780:2: warning: fontmake: 'propagated-inputs'
field not found; leaving it unchanged

gnu/packages/fontutils.scm:780:2: warning: fontmake: expected
'propagated-inputs' value: (python-attrs python-fontmath
python-fonttools python-glyphslib python-ufo2ft python-ufolib2)

--8<---cut here---start->8---
modified   gnu/packages/fontutils.scm
@@ -779,16 +779,16 @@ (define-public psautohint-font-data
 (define-public fontmake
   (package
 (name "fontmake")
-(version "3.4.0")
+(version "3.7.1")
 (source (origin
   (method url-fetch)
   (uri (pypi-uri "fontmake" version ".zip"))
   (sha256
(base32
-"0fc5c9csjpy1aa4c03p7nvjgls5wjplhmmf42n0cmvrlh6cm7wl3"
+"0ib7fvwgwazm7qfj4a3rkqkb40xfbj40rnvsmkvl2isg2ky3vg9m"
 (build-system python-build-system)
-(inputs (list python-fontmath python-glyphslib))
-(native-inputs (list unzip python-setuptools-scm))
+(inputs (list))
+(native-inputs (list zip))
 (home-page "https://github.com/googlefonts/fontmake";)
 (synopsis
  "Compile fonts from sources (UFO, Glyphs) to binary (OpenType, TrueType)")
--8<---cut here---end--->8---

The choice of using inputs here was conscious, as it is a command, not a
library.  Perhaps it could check if the name starts with 'python-' or
not?  It's a bit 'magic', but it would help.

-- 
Thanks,
Maxim





bug#65769: wlgreet-sway-session

2023-09-05 Thread chris
This directory for the greeter user does not exist in the system /run/user/986





bug#65769: wlgreet-sway-session

2023-09-05 Thread chris
The greeter works after creating /run/user/986/wayland-1.lock and changing the 
owner of /run/user/986 and /run/user/986/wayland-1.lock to "greeter". This 
seems to be a bug.