From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Conflict: python3-prompt_toolkit1-1.0.15_3 with python3-prompt_toolkit2_2.0.9_3
Date: Tue, 25 Jun 2019 04:43:48 +0200 [thread overview]
Message-ID: <20190625024348.qVORrG4pSx17iLO2QZZ4HFrTSXbW9jO0-7F1bSgrWLI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12636@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Closed issue by zamlz on void-packages repository
https://github.com/void-linux/void-packages/issues/12636
Description: ### System
* xuname:
```
CONFLICT: python3-prompt_toolkit1-1.0.15_3 with python3-prompt_toolkit2-2.0.9_3 in transaction (matched by python3-prompt_toolkit2)
Transaction aborted due to conflicting packages.
Void 4.19.50_1 x86_64 AuthenticAMD uptodate rrFF
```
* package:
```
python3-prompt_toolkit1-1.0.15_3
python3-prompt_toolkit2_2.0.9_3
```
### Expected behavior
When running `sudo xbps-install -Su` I should be able to update the system cleanly.
### Actual behavior
```
[*] Updating `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
[*] Updating `https://alpha.de.repo.voidlinux.org/current/nonfree/x86_64-repodata' ...
CONFLICT: python3-prompt_toolkit1-1.0.15_3 with python3-prompt_toolkit2-2.0.9_3 in transaction (matched by python3-prompt_toolkit2)
Transaction aborted due to conflicting packages.
```
### Steps to reproduce the behavior
Unsure may be because of the packages I have installed, but its when I try to update as mentioned in the __Expected behaviour__ section.
prev parent reply other threads:[~2019-06-25 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 17:02 [ISSUE] " voidlinux-github
2019-06-23 19:32 ` voidlinux-github
2019-06-23 21:29 ` voidlinux-github
2019-06-24 20:30 ` voidlinux-github
2019-06-25 2:43 ` voidlinux-github
2019-06-25 2:43 ` voidlinux-github [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=20190625024348.qVORrG4pSx17iLO2QZZ4HFrTSXbW9jO0-7F1bSgrWLI@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).