bug#67914: Error dump installer-dump-1b86ea91
Oh, yes please close it. Should I do something ? Regards, Santiago On 2024-02-15 17:15, Simon Tournier wrote: > Hi, > > On mer., 20 déc. 2023 at 14:13, Santiago Payà Miralta > wrote: > >> Successfully installed. Only change: VPN disabled. > > Cool! So closing? Because I am not sure to get if there is a bug in > the report? > > Cheers, > simon
bug#63250: package dante : socksify: error: dante client not built with preloading support
Hi, On mer., 20 déc. 2023 at 16:18, Nguyễn Gia Phong via Bug reports for GNU Guix wrote: > Could you take a look at https://issues.guix.gnu.org/67675 > if it fixes it for you? Since patch#67675 is merged, is it fixed now? Cheers, simon
bug#67914: Error dump installer-dump-1b86ea91
Hi, On mer., 20 déc. 2023 at 14:13, Santiago Payà Miralta wrote: > Successfully installed. Only change: VPN disabled. Cool! So closing? Because I am not sure to get if there is a bug in the report? Cheers, simon
bug#67806: guix pull error
Hi, On jeu., 28 déc. 2023 at 10:02, Josselin Poiret via Bug reports for GNU Guix wrote: > Hi Qingyun, > > qy.tao--- via Bug reports for GNU Guix writes: > >> 1. &store-protocol-error: >> message: >> "`/gnu/store/5kj8lyybjrdl7xd0fx9g9vzkz8sklqsy-guix-1.4.0/bin/guix >> substitute' died unexpectedly" >> status: 1 > > This seems to be a transient substitute error, can you retry? What is the status of this bug? Cheers, simon
bug#69129: sbcl-mcclim broke on upgrade to sbcl@2.4.0
Hi, to reproduce, run demodemo as you have done, and then click/tap the Stream test button. When the new window appears, start to move your graphical cursor over it and it will throw the error. I observed that this is now happening with at least several other of the demodemo test applications, and it was happening in my private application as well, which I have not yet released, on multiple computers. I haven't done much research into the exact cause of the problem, as in my mind it was more of an excuse to request an update to the latest release of mcclim. -- Christopher Howard
bug#65441: leptonica 1.83.1 ioformats_reg test failure
Greetings, I looked into this and can see that running tests in parallel causes random failures. I've seen the same thing on Debian also. I've sent in a patch series[1] that includes a fix for this. Thanks, Ahmad 1: https://issues.guix.gnu.org/69166
bug#69125: python-trio transient test failures
Hi Oleg, Sharlatan Hellseher writes: > Maybe it's time to update it or disable some shaky tests. > > WDYT? I agree, I was looking into this on core-updates but didn't want to commit to updating this as it also needs some dependency upgrades. Best, -- Josselin Poiret signature.asc Description: PGP signature
bug#69127: guix pull bug
Hi Ryan Ryan Barber writes: > guix pull requested I send over this bug report. fresh debian bookworm > install as a vm in google cloud. guix installed via apt. vm has minimal > specs - 1gb ram, single core, which might be the issue. That's most likely it, `guix pull` requires quite a lot of RAM unfortunately. It's something everyone would like to fix but it requires a non-trivial amount of work that no-one has committed to for now :( Best, -- Josselin Poiret signature.asc Description: PGP signature
bug#69129: sbcl-mcclim broke on upgrade to sbcl@2.4.0
Christopher Howard skribis: > Hello, sbcl-mcclim library broke on the upgrade to sbcl@2.4.0. Something > changed so that many applications (include :clim-examples demos) break in > runtime with an error like so: > > ``` > invalid keyword argument: :CLIPPING-REGION (valid keys are :INK, > :TEXT-STYLE). >[Condition of type SB-INT:SIMPLE-PROGRAM-ERROR] > ``` > > The problem is not present if I time-machine back to a commit with sbcl@2.3.7. > > Rather than troubleshooting this problem, I would recommend upgrading > sbcl-mcclim to the latest official release, which is Version 0.9.8. Hi. I don't reproduce the issue. I tried with: --8<---cut here---start->8--- guix shell sbcl sbcl-mcclim -- sbcl --no-userinit (require :asdf) (asdf:load-system "clim-examples") (clim-demo:demodemo) --8<---cut here---end--->8--- and it worked. What command did you use to get the error? signature.asc Description: PGP signature
bug#39885: Bioconductor tarballs are not archived
Hi, On ven., 19 janv. 2024 at 09:46, Timothy Sample wrote: > $ git clone https://git.ngyro.com/preservation-of-guix > $ cd preservation-of-guix > $ wget https://ngyro.com/pog-reports/latest/pog.db > > [Wait a long time because my server is slw.] > > $ guile -L . etc/sources.scm pog.db > missing-sources.json Cool! Can we consider that this report is now done? Because: 1. SWH supports ExtID and nar hash lookup. 2. Missing origins are currently ingested by SWH. (via specific sources.json) Cheers, simon
bug#68595: VLANs in static-networking-service-type hangs shepherd
Ludovic Courtès writes: > Ouch. Could you check what /var/log/messages reports? > > Once you’ve reproduced the hang, could you attach GDB to shepherd and > get a backtrace? > > gdb -p 1 > bt > > (I recommend doing that in a VM rather than on your main machine!) > I have unfortunately been unable to reproduce the full shepherd hang, even though I have followed the exact same procedure as before. I still experience that the command `herd restart networking` hangs indefinitely the first time after adding a VLAN, but now this has not triggered the whole shepherd to hang afterwards anymore. The basic error 17 still comes any time I try to start networking service while having a VLAN configured. > > You mentioned in your other message that the example from the manual > works fine. Could you try and reduce your config until you find which > bit makes it fail? The configuration I have already attached is as minimal as it is possible. It only includes the mandatory OS fields and a minimal static-networking-configuration. I have already found which bit makes it fail. It is the use of VLAN for any normal network link. VLANs seem to only work for bond devices as in the example. The reproduction steps are maybe a little over-complicated however, and are only necessary in order to reproduce the full "shepherd hangs" bug, which I now am unable to reproduce anyway. But what I believe is the root of the problem is the error 17 on starting the networking service. This can be reproduced much more simply and reliably by just starting a VM the normal way with the static-networking snippet already enabled when building it. So here are the new simplified reproduction steps for reproducing only the error 17 and unfunctional VLAN networking: Use the OS config from my first post, but uncomment the static networking block. Build and run the VM with `$(guix system vm minimal.scm)`. That's it. > Cc’ing Alexey and Julien who may know more. > > Thanks, > Ludo’. Alexey Abramov writes: > Hi Lars, > > I see, Could you please, replace the device name to "myvlan" and not > "myvlan@eth0" in the network-address. > > Even though ip link (iproute2) shows you 'myvlan@eth0' this is not an > actual name of the interfaces. > I have tried with your suggestion, but everything behaves exactly the same.
