From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] qt6-location template needs to be fixed (wrong distfiles)
Date: Fri, 15 Sep 2023 23:11:16 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46073@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
New issue by chrysos349 on void-packages repository
https://github.com/void-linux/void-packages/issues/46073
Description:
### Is this a new report?
Yes
### System Info
Void 6.3.13_1 x86_64 GenuineIntel uptodate rrFFFFF
### Package(s) Affected
qt6-location-6.5.2_1, qt6-location-devel-6.5.2_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
I expect qt6-location to be compiled and packaged.
Proper link for qt6-location:
`distfiles="http://download.qt.io/official_releases/qt/${version%.*}/${version}/submodules/qtlocation-everywhere-src-${version}.tar.xz"`
Proper makedepends for qt6-location:
`makedepends="qt6-declarative-devel qt6-positioning-devel"`
### Actual behaviour
The package compiled is actually qt6-positioning
Wrong link for qt6-location:
`distfiles="http://download.qt.io/official_releases/qt/${version%.*}/${version}/submodules/qtpositioning-everywhere-src-${version}.tar.xz"`
### Steps to reproduce
@Johnnynator
1. Compile the template for qt6-location
2. You will get `qt6-location` package with `qt6-positioning` contents (there is no proper `qt6-positioning` in the repository).
Solution
1. The template needs to be renamed to qt6-positioning. The proper template for qt6-location needs to be created.
next reply other threads:[~2023-09-15 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 21:11 chrysos349 [this message]
2023-09-16 4:22 ` [ISSUE] [CLOSED] " sgn
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-46073@inbox.vuxu.org \
--to=chrysos349@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).