From: Noah-Huppert <Noah-Huppert@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: protobufs upgrade fails
Date: Thu, 20 Aug 2020 02:18:54 +0200 [thread overview]
Message-ID: <20200820001854.nlbjk53H0-uKFcV-9orvHuuMb0xlDW6B1g3Ne7Z2pD4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24344@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
New comment by Noah-Huppert on void-packages repository
https://github.com/void-linux/void-packages/issues/24344#issuecomment-676825018
Comment:
Thanks! I understand now.
El mié., 19 de agosto de 2020 8:15 p. m., Danh Doan <
notifications@github.com> escribió:
> Yes, it shouldn't fail. Hence, we should have protobuf24 conflicts with
> protobuf23 and prorovides protobuf23.
>
> The original change forgot to do it, and it's fixed in c260514
> <https://github.com/void-linux/void-packages/commit/c260514218c02130e1e5f65664a5dce205b4c754>
> (protobuf24: update conflicts list, 2020-08-18)
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/24344#issuecomment-676824120>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAZLM4FVSLIVUM4DCI535YTSBRTLTANCNFSM4QD665FQ>
> .
>
prev parent reply other threads:[~2020-08-20 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 19:17 [ISSUE] " Noah-Huppert
2020-08-18 19:27 ` Noah-Huppert
2020-08-19 16:13 ` [ISSUE] [CLOSED] " sgn
2020-08-19 16:13 ` sgn
2020-08-19 16:20 ` Noah-Huppert
2020-08-20 0:15 ` sgn
2020-08-20 0:18 ` Noah-Huppert [this message]
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=20200820001854.nlbjk53H0-uKFcV-9orvHuuMb0xlDW6B1g3Ne7Z2pD4@z \
--to=noah-huppert@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).