From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 68475@debbugs.gnu.org
Subject: [bug#68475] [PATCH] Update python-evdev to 1.5.0.
Date: Sun, 21 Jan 2024 23:12:26 -0500 [thread overview]
Message-ID: <878r4i6m6t.fsf@gmail.com> (raw)
In-Reply-To: <87jzo4oorh.fsf@gmail.com> (Sharlatan Hellseher's message of "Sat, 20 Jan 2024 00:02:42 +0000")
Hi Sharlatan,
Sharlatan Hellseher <sharlatanus@gmail.com> writes:
> It triggers an expensive build, potentially for core updates?
>
>
> piper@0.7 plasma-phone-components@5.23.4 plasma-mobile@5.24.3 plasma-bigscreen@5.27.7 plasma@5.27.7
> kodi-wayland@19.5 touchegg@2.0.14 synthpod@0.1.6507 velox@0-1.fcc0412 show-me-the-key@1.8.0
> gpaste@42.2 arc-theme@20221218 gnome-shell-extension-gsconnect@50 numix-gtk-theme@2.6.7
> gnome-terminal@3.44.1 gnome@42.4 wacomtablet@3.2.0 xkeysnail@0.4.0
Our old guidelines for master was that <= 300 rebuilds is fair game for
the master branch.
> There tests in git checkout but they need access to /dev/uinput
Perhaps these can be skipped; pytest has a convenient -k 'not test_name'
switch to do so.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-01-22 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 15:01 [bug#68475] [PATCH] Update python-evdev to 1.5.0 Wicki Gabriel (wicg)
2024-01-15 16:07 ` [bug#68475] guix refresh -l build tests Wicki Gabriel (wicg)
2024-01-20 0:02 ` [bug#68475] [PATCH] Update python-evdev to 1.5.0 Sharlatan Hellseher
2024-01-22 4:12 ` Maxim Cournoyer [this message]
2024-01-22 21:37 ` bug#68475: " Sharlatan Hellseher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r4i6m6t.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=68475@debbugs.gnu.org \
--cc=sharlatanus@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).