From: derrickcreamer <derrickcreamer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] msbuild-bin breaks after update
Date: Sat, 29 Feb 2020 22:51:57 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19641@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
New issue by derrickcreamer on void-packages repository
https://github.com/void-linux/void-packages/issues/19641
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.4.23_1 x86_64 AuthenticAMD notuptodate rrrmFFFFF
* package:
msbuild-bin-16.5_1
### Expected behavior
Files installed to /usr/lib/mono.
### Actual behavior
Files installed to /usr/lib/lib/mono causing package to not work correctly.
### Steps to reproduce the behavior
Do a typical package installation using xbps-install. Can also verify file locations with xbps-query -Rf msbuild-bin.
The /usr/lib/lib/mono location is not correct and does not reflect the usual working configuration, nor does it reflect the result of rebuilding this package from source.
Anecdotally, this problem MIGHT only appear on certain void repos. I believe I'm connecting to alpha.de.repo.voidlinux.org while another user reported this issue on US repos.
next reply other threads:[~2020-02-29 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 21:51 derrickcreamer [this message]
2020-02-29 23:41 ` ahesford
2020-03-02 9:22 ` [ISSUE] [CLOSED] " xtraeme
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-19641@inbox.vuxu.org \
--to=derrickcreamer@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).