From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] protobufs upgrade fails
Date: Wed, 19 Aug 2020 18:13:11 +0200 [thread overview]
Message-ID: <20200819161311.3P9R2V4snMATU3CxO_9gIXnl83b_NxQKvATfC-1Mp5s@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: 1463 bytes --]
Closed issue by Noah-Huppert on void-packages repository
https://github.com/void-linux/void-packages/issues/24344
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:
*output of ``xuname`` (part of xtools)*
```
Void 5.4.50_1 x86_64 GenuineIntel notuptodate rrrmFFFFFFFFFFF
```
* package:
*affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
```
protobuf24-3.13.0_1
protobuf23-3.12.4_1
protobuf-3.13.0_1
```
### Expected behavior
Upgrading protobufs (when upgrading my system via `xbps-install -Syu`) should not fail due to a newer version of protobufs providing the same binary which the older version provides.
### Actual behavior
```
% xbps-install -Syu
...
protobuf24-3.13.0_1: collecting files...
protobuf-3.13.0_1: collecting files...
protobuf23-3.12.4_1: collecting files...
ERROR: protobuf23-3.12.4_1: file `/usr/bin/protoc' already installed by package protobuf2
4-3.13.0_1.
Transaction failed! see above for errors.
```
[full output](https://gist.github.com/Noah-Huppert/b010256dbb6b8b31a402d7db9c84fedb)
It seems like it fails to upgrade from protobuf23 to protobuf24 bc they provide the same binary.
### Steps to reproduce the behavior
1. Have `protobuf23` installed.
2. Try to upgrade to `protobuf24`
next prev parent reply other threads:[~2020-08-19 16:13 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 ` sgn [this message]
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
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=20200819161311.3P9R2V4snMATU3CxO_9gIXnl83b_NxQKvATfC-1Mp5s@z \
--to=sgn@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).