Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Many pycompile_dir definitions use absolute path instead of relative one
@ 2020-12-15 20:59 ericonr
  2020-12-18 22:42 ` Chocimier
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: ericonr @ 2020-12-15 20:59 UTC (permalink / raw)
  To: ml

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

New issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/27188

Description:
### Expected behavior

Installing a package with python files, such as `gdb`, into an alternate root should try to compile the python files in the alternate root.

### Actual behavior

The hook uses the alternate root's python, `usr/bin/python3`, but the GDB template specifies `pycompile_dirs="/usr/share/gdb/python"`, which makes it try to build the system's python files, with the wrong python even. I noticed because I was running xbps-install as a user and it gave me multiple permission errors. Multiple templates have this same issue.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Many pycompile_dir definitions use absolute path instead of relative one
  2020-12-15 20:59 [ISSUE] Many pycompile_dir definitions use absolute path instead of relative one ericonr
@ 2020-12-18 22:42 ` Chocimier
  2020-12-19  2:44 ` ericonr
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: Chocimier @ 2020-12-18 22:42 UTC (permalink / raw)
  To: ml

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/issues/27188#issuecomment-748354417

Comment:
Given that all other variables take absolute path, I would rather take absolute here too and ensure operating in rootdir, like mkdirs do now.

#27265

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Many pycompile_dir definitions use absolute path instead of relative one
  2020-12-15 20:59 [ISSUE] Many pycompile_dir definitions use absolute path instead of relative one ericonr
  2020-12-18 22:42 ` Chocimier
@ 2020-12-19  2:44 ` ericonr
  2022-05-01  2:14 ` github-actions
  2022-05-16  2:07 ` [ISSUE] [CLOSED] " github-actions
  3 siblings, 0 replies; 5+ messages in thread
From: ericonr @ 2020-12-19  2:44 UTC (permalink / raw)
  To: ml

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

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/27188#issuecomment-748407897

Comment:
Thanks for looking into it.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Many pycompile_dir definitions use absolute path instead of relative one
  2020-12-15 20:59 [ISSUE] Many pycompile_dir definitions use absolute path instead of relative one ericonr
  2020-12-18 22:42 ` Chocimier
  2020-12-19  2:44 ` ericonr
@ 2022-05-01  2:14 ` github-actions
  2022-05-16  2:07 ` [ISSUE] [CLOSED] " github-actions
  3 siblings, 0 replies; 5+ messages in thread
From: github-actions @ 2022-05-01  2:14 UTC (permalink / raw)
  To: ml

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

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/27188#issuecomment-1114104642

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [ISSUE] [CLOSED] Many pycompile_dir definitions use absolute path instead of relative one
  2020-12-15 20:59 [ISSUE] Many pycompile_dir definitions use absolute path instead of relative one ericonr
                   ` (2 preceding siblings ...)
  2022-05-01  2:14 ` github-actions
@ 2022-05-16  2:07 ` github-actions
  3 siblings, 0 replies; 5+ messages in thread
From: github-actions @ 2022-05-16  2:07 UTC (permalink / raw)
  To: ml

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

Closed issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/27188

Description:
### Expected behavior

Installing a package with python files, such as `gdb`, into an alternate root should try to compile the python files in the alternate root.

### Actual behavior

The hook uses the alternate root's python, `usr/bin/python3`, but the GDB template specifies `pycompile_dirs="/usr/share/gdb/python"`, which makes it try to build the system's python files, with the wrong python even. I noticed because I was running xbps-install as a user and it gave me multiple permission errors. Multiple templates have this same issue.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-05-16  2:07 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-15 20:59 [ISSUE] Many pycompile_dir definitions use absolute path instead of relative one ericonr
2020-12-18 22:42 ` Chocimier
2020-12-19  2:44 ` ericonr
2022-05-01  2:14 ` github-actions
2022-05-16  2:07 ` [ISSUE] [CLOSED] " github-actions

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 NNTP newsgroup(s).