From: yopito <yopito@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] seafile-{client-qt,libclient}: update to 8.0.1
Date: Sun, 25 Apr 2021 12:25:42 +0200 [thread overview]
Message-ID: <20210425102542.-UOA_PXv3auiJhyPv0PBfghteIGqYxOqDMwxtTyTtWA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30384@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
New review comment by yopito on void-packages repository
https://github.com/void-linux/void-packages/pull/30384#discussion_r619788021
Comment:
uneeded: runtime constraints are managed either on producing binary package (looks after common/shlibs for lib) and while installing/upgrading.
Edit: about common/shlibs
Since your PR update libsearprc, package upgrade will find it.
Simulating (a kind of) what will happens once this PR merged and officially build: I've built all this PR locally **without** your constraint "`libsearpc-devel>=3.2.0.20200318`", so upgrade looks like:
Edit: reword to make me understandable
```
$ sudo xbps-install -Su --repo=/build/packages/hostdir/binpkgs/pr/30384.seafile.8.0.1
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
Name Action Version New version Download size
libsearpc update 3.2.0_4 3.2.0.20200318_1 -
seafile-client-qt update 7.0.10_1 8.0.1_1 -
seafile-libclient update 7.0.10_2 8.0.1_1 -
Size required on disk: 4414KB
Space available on disk: 4998MB
Do you want to continue? [Y/n]
```
next prev parent reply other threads:[~2021-04-25 10:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 12:25 [PR PATCH] Seafile update lonwillett
2021-04-20 14:12 ` [PR PATCH] [Updated] " lonwillett
2021-04-23 22:52 ` yopito
2021-04-23 22:56 ` yopito
2021-04-24 7:03 ` lonwillett
2021-04-24 7:22 ` lonwillett
2021-04-24 14:10 ` yopito
2021-04-24 14:49 ` [PR PATCH] [Updated] " lonwillett
2021-04-24 15:53 ` [PR PATCH] [Updated] seafile-{client-qt,libclient}: update to 8.0.1 lonwillett
2021-04-24 22:09 ` [PR REVIEW] " yopito
2021-04-24 22:09 ` yopito
2021-04-24 22:09 ` yopito
2021-04-24 22:09 ` yopito
2021-04-24 23:52 ` lonwillett
2021-04-24 23:52 ` lonwillett
2021-04-25 0:09 ` [PR PATCH] [Updated] " lonwillett
2021-04-25 9:40 ` [PR REVIEW] " yopito
2021-04-25 10:01 ` yopito
2021-04-25 10:03 ` yopito
2021-04-25 10:25 ` yopito [this message]
2021-04-25 10:28 ` [PR PATCH] [Updated] " lonwillett
2021-04-26 18:13 ` yopito
2021-04-26 19:12 ` ericonr
2021-04-26 19:12 ` [PR PATCH] [Merged]: " ericonr
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=20210425102542.-UOA_PXv3auiJhyPv0PBfghteIGqYxOqDMwxtTyTtWA@z \
--to=yopito@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).