[bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.

[bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.

[Christopher Baines]

To allow gdb to be updated more easily.

* gnu/packages/python-xyz.scm (python-pydevd)[inputs]: Use gdb/pinned.

Change-Id: Icf417f89933bc190bf4c0d869c199cfe50d463ef
---
 gnu/packages/python-xyz.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index 92566abfed..a19422aa4a 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -16471,7 +16471,7 @@ (define-public python-pydevd
              python-pytest-xdist
              python-trio
              python-untangle))
-      (inputs (list coreutils gdb procps))
+      (inputs (list coreutils gdb/pinned procps))
       (home-page "https://github.com/fabioz/PyDev.Debugger/")
       (synopsis "Python debugger")
       (description "PyDev.Debugger is a capable Python debugger used in PyDev

base-commit: 4e7337536ba41e888a601c92fada8a4adca9d2c6
-- 
2.41.0

[bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.

[Ludovic Courtès]

Hi!

Christopher Baines <mail@cbaines.net> skribis:

> To allow gdb to be updated more easily.
>
> * gnu/packages/python-xyz.scm (python-pydevd)[inputs]: Use gdb/pinned.
>
> Change-Id: Icf417f89933bc190bf4c0d869c199cfe50d463ef

[...]

> -      (inputs (list coreutils gdb procps))
> +      (inputs (list coreutils gdb/pinned procps))
>        (home-page "https://github.com/fabioz/PyDev.Debugger/")
>        (synopsis "Python debugger")

If PyDev uses GDB, then it’ll be stuck with an older version of GDB?
Maybe that’s OK?  (I know nothing about PyDev and how it uses GDB so I
can’t really judge whether it’s OK.)

Ludo’.

[bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.

[Christopher Baines]

[-- Attachment #1: Type: text/plain, Size: 831 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Christopher Baines <mail@cbaines.net> skribis:
>
>> To allow gdb to be updated more easily.
>>
>> * gnu/packages/python-xyz.scm (python-pydevd)[inputs]: Use gdb/pinned.
>>
>> Change-Id: Icf417f89933bc190bf4c0d869c199cfe50d463ef
>
> [...]
>
>> -      (inputs (list coreutils gdb procps))
>> +      (inputs (list coreutils gdb/pinned procps))
>>        (home-page "https://github.com/fabioz/PyDev.Debugger/")
>>        (synopsis "Python debugger")
>
> If PyDev uses GDB, then it’ll be stuck with an older version of GDB?
> Maybe that’s OK?  (I know nothing about PyDev and how it uses GDB so I
> can’t really judge whether it’s OK.)

I don't really know either, but at least this will allow updating gdb
without rebuilding a bunch of Python things.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

[bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.

[Lars-Dominik Braun]

Hi Chris,

> > If PyDev uses GDB, then it’ll be stuck with an older version of GDB?
> > Maybe that’s OK?  (I know nothing about PyDev and how it uses GDB so I
> > can’t really judge whether it’s OK.)
> 
> I don't really know either, but at least this will allow updating gdb
> without rebuilding a bunch of Python things.

I don’t see anything that would prevent pydevd running on a pinned/older
GDB version. We might want to verify when we update python-pydevd, but
right now it just attaches to the process and injects a shared object
– that’s all. So, LGTM.

Lars

[bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.

[Ludovic Courtès]

Hi,

Lars-Dominik Braun <lars@6xq.net> skribis:

>> > If PyDev uses GDB, then it’ll be stuck with an older version of GDB?
>> > Maybe that’s OK?  (I know nothing about PyDev and how it uses GDB so I
>> > can’t really judge whether it’s OK.)
>> 
>> I don't really know either, but at least this will allow updating gdb
>> without rebuilding a bunch of Python things.
>
> I don’t see anything that would prevent pydevd running on a pinned/older
> GDB version. We might want to verify when we update python-pydevd, but
> right now it just attaches to the process and injects a shared object
> – that’s all. So, LGTM.

OK, thanks for checking.  Go for it, Chris!

Ludo’.

[bug#70393] [PATCH v2] gnu: python-pydevd: Use gdb/pinned.

[Ludovic Courtès]

From: Christopher Baines <mail@cbaines.net>

To allow gdb to be updated more easily.

* gnu/packages/python-xyz.scm (python-pydevd)[inputs]: Use gdb/pinned.

Change-Id: Icf417f89933bc190bf4c0d869c199cfe50d463ef
Signed-off-by: Ludovic Courtès <ludo@gnu.org>
---
 gnu/packages/python-xyz.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Dear qa.guix, could you please build this for us?

Ludo'.

diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index b58eb1ff88..95c33342b6 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -17093,7 +17093,7 @@ (define-public python-pydevd
              python-pytest-xdist
              python-trio
              python-untangle))
-      (inputs (list coreutils gdb procps))
+      (inputs (list coreutils gdb/pinned procps))
       (home-page "https://github.com/fabioz/PyDev.Debugger/")
       (synopsis "Python debugger")
       (description "PyDev.Debugger is a capable Python debugger used in PyDev

base-commit: f125143d64c3fac8c9576a55b48331cbf6096460
-- 
2.46.0

[bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.

[Nicolas Graves via Guix-patches via]

Hi Ludo,

I have two/three patches updating python-debugpy to its latest version,
also refreshing pydevd in the process.  Can I append them in this patch
series ?  I've checked that it updates properly until python-ipykernel,
so it is probably correct for other packages that most likely rely on
ipykernel rather than pydevd api.

Also, this have more than 400 rebuilds, will that not abort the build on
QA once the derivation is evaluated? 

By the way, is there a way to make QA prioritize some builds?  Like
[security fixes] or [important] tags?  I guess that would be welcome if
users don't take advantage of that too much.

-- 
Best regards,
Nicolas Graves