Hi Skyler,
On Sun, Feb 18 2024, Skyler Ferris wrote:
> Am I using the `--rounds` flag wrong, do I misunderstand this tool, or
> is this actually a bug?
I'm not sure if this is considered a bug or not, but the solution to
your problem is to use --check. Using your test file running:
guix build
Hi Andy,
On Sun, Feb 18 2024, Andy Tai wrote:
> multiple issues created... now I will go to merge them,
You can do so with "forcemerge" via the control server but if no one has
commented yet, I would instead close the duplicate bugs via messages to
xxx-d...@debbugs.gnu.org that state:
Dup
Hi, my patches now get acknowledged and multiple issues created... now
I will go to merge them,
On Sun, Feb 18, 2024 at 9:42 AM Felix Lechner
wrote:
>
> Hi Andy,
> Hi Artyom,
>
> > sending a patch to guix-patches does not seem to result in the
> > creation of a new debbugs issue
>
> > I'm hav
Hello,
Checking a package for reproducibility is one important part of patch
review. Based on the documentation for the `--rounds=N`, I expect that a
line such as `guix build foo --rounds=2` will build the package at least
once and at most twice (assuming that, if the output is already present
Hi Andy,
Hi Artyom,
> sending a patch to guix-patches does not seem to result in the
> creation of a new debbugs issue
> I'm having the same issue
You are not alone. [1][2]
Please note that I do not maintain Debbugs. I would like to, but lost
an internal appeals process, which was non-public.
Indeed apparently it works for my VLC when I specify any non-existent
driver. Anyway. You could:
Try
export MESA_LOADER_DRIVER_OVERRIDE=crocus
If it does not work, open a bug by writing a mail to bug-g...@gnu.org
Of course the driver must be free by FSDG, but I believe this is not the
issue h
Hello,
FWIW, I'm having the same issue since yesterday. I've tried to send a
patch from Gmail twice but to no avail.
- avp
--
Artyom "avp" Poptsov
Home page: https://memory-heap.org/~avp/
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE B57C E9C5 A2D9 0898 A02
У сб, 2024-02-17 у 11:53 -0800, Ian Eure пише:
> When I log into my EXWM session, it doesn’t unlock the Gnome
> keychain. This causes the first program I open which needs
> something from the keychain to prompt me to unlock it.
I use GNOME and observe the same behaviour. Maybe this issue in Gui
