From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] xbps-src will accept packages from remote repos as fullfilling dependencies even when they aren't available in srcpkgs/
Date: Wed, 16 Jun 2021 18:29:49 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31526@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
New issue by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/31526
Description:
Writing a template to depend on `zstd-devel` (removed in d481489dae9449f5212f4e2b5fab74e858962242) should fail because `srcpkgs/zstd-devel/template` doesn't exist. Instead, if it's still available in remote repositories because it hasn't been cleaned up, it will be enough to satisfy the dependency.
An example from adding `zstd-devel` to `depends` for `kicad-library`.
```
[target] zstd-devel: found (https://alpha.de.repo.voidlinux.org/current/musl)
[runtime] kicad-footprints-5.1.10_1: found (https://alpha.de.repo.voidlinux.org/current/musl)
[runtime] kicad-packages3D-5.1.10_1: found (https://alpha.de.repo.voidlinux.org/current/musl)
[runtime] kicad-symbols-5.1.10_1: found (https://alpha.de.repo.voidlinux.org/current/musl)
[runtime] kicad-templates-5.1.10_1: found (https://alpha.de.repo.voidlinux.org/current/musl)
```
This can lead to issues such as 5898b6cbe0efcf6c129799a0993943fc7128f1a7 (fixed in d0ae88846bf833a5e1171dff6dd44a65c4891466), where a package can be made to depend on another one that's no longer available.
When fixing this, care should be taken to not break virtual packages or others depending on the `provides=` mechanism (though arguably packages which are `provides`d by something are valid only in `depends`).
next reply other threads:[~2021-06-16 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 16:29 ericonr [this message]
2022-05-22 2:11 ` github-actions
2022-05-23 16:38 ` Chocimier
2022-08-22 2:13 ` github-actions
2022-11-21 2:11 ` github-actions
2023-02-20 2:02 ` github-actions
2023-05-22 1:57 ` github-actions
2023-06-05 2:04 ` [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-31526@inbox.vuxu.org \
--to=ericonr@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).