From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] hydrus has useless files
Date: Sun, 17 Mar 2024 18:20:49 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49338@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
New issue by Eloitor on void-packages repository
https://github.com/void-linux/void-packages/issues/49338
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.22_1 x86_64 GenuineIntel uptodate hold rFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
### Package(s) Affected
hydrus-544_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
No useless files in wydrus package
### Actual behaviour
```
$ xls hydrus | rg windows
/usr/lib/hydrus/static/build_files/windows/InnoSetup.iss
/usr/lib/hydrus/static/build_files/windows/file_version_info_maker.py
/usr/lib/hydrus/static/build_files/windows/hydrus_client.spec
/usr/lib/hydrus/static/build_files/windows/hydrus_server.spec
/usr/lib/hydrus/static/build_files/windows/requirements.txt
/usr/lib/hydrus/static/build_files/windows/sqlite3.dll
/usr/lib/hydrus/static/build_files/windows/sqlite3.exe
/usr/lib/hydrus/static/requirements/advanced/requirements_windows.txt
/usr/lib/hydrus/static/requirements/hydev/requirements_windows_build.txt
```
### Steps to reproduce
Run `xls hydrus | rg windows`.
next reply other threads:[~2024-03-17 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 17:20 Eloitor [this message]
2024-03-18 8:59 ` meator
2024-05-04 8:28 ` [ISSUE] [CLOSED] " classabbyamp
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-49338@inbox.vuxu.org \
--to=eloitor@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).