Github messages for voidlinux
 help / color / mirror / Atom feed
From: Requion <Requion@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] guake - vsed in do_check fails
Date: Wed, 27 Sep 2023 13:37:19 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46288@inbox.vuxu.org> (raw)

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

New issue by Requion on void-packages repository

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

Description:
Hello,

i saw the subject line mentioned in #46170 . I like Guake and am actively using it, thus i would like to keep it working. Unfortunately my journey with Void and package maintenance just started and i lack the knowledge to fix it myself currently. For this reason, i wanted to provide my findings so far to help fixing the template as good as i can.

From what i could gather so far, the `vsed -i 's/from mock/from unittest.mock/g' guake/tests/test_quick_open.py` line fails because the directory `quake/tests/` does not exist in the tarball downloaded from pypi.org (it is included in the github tarball though). The `distfiles` property was changed from github to pypi in https://github.com/void-linux/void-packages/commit/eee156e480a0f5b5f89e94c9f59bb90e4bdd3cf9 [^1] by @Johnnynator , which, as per Guakes docs, is the correct approach to [build from source](https://guake.readthedocs.io/en/latest/user/installing.html#install-from-source).

There are multiple options to fix this, which is where i am uncertain about the correct approach.
1. Ask [upstream](https://github.com/Guake/guake) to include the tests in the tarball published on pypi
2. Remove the tests from the template (which were probably added for a reason)
3. Others which i personally see as *too hacky* like sideloading the tests

This said, i am looking forward on any feedback helping to fix the issue and improving my know-how on how to contribute.

Regards
Requion

[^1]: I searched / linked the commit to understand the turn of events, not to point fingers.

             reply	other threads:[~2023-09-27 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 11:37 Requion [this message]
2023-09-27 16:45 ` mhmdanas
2023-09-28  7:46 ` Requion
2023-12-28  1:45 ` github-actions
2024-01-11  1:47 ` [ISSUE] [CLOSED] " github-actions

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46288@inbox.vuxu.org \
    --to=requion@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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).