Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: libevent repository inconsistency
Date: Wed, 23 Oct 2019 19:44:54 +0200	[thread overview]
Message-ID: <20191023174454.JdGu5m7uBHAc_EkvhArt7T_GS6VOogkiY-1M_BMugos@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15745@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]

New comment by xtraeme on void-packages repository

https://github.com/void-linux/void-packages/issues/15745#issuecomment-545558357

Comment:
Hi,

Well, this is really weird because I know in what state we are in... And
this is because the builder admin removed some files while xbps was
working... Heh

El mié., 23 oct. 2019 19:41, Helmut Pozimski <notifications@github.com>
escribió:

> The repositories are in an inconsistent state right now because there is a
> massive rebuild going on which among other includes all major browsers and
> qt5. While this incosistency lasts, updated might fail with an error
> message like:
>
> [*] Updating `https://alpha.de.repo.voidlinux.org/current/x86_64-repodata' ...
> MISSING: libevent>=2.1.11_1
> Transaction aborted due to unresolved dependencies.
>
> The status of the rebuild can be observed at
> https://build.voidlinux.org/waterfall. Once the status of all build
> servers is changed to green, everything should work again. In the meantime,
> please be patient and postpone updating your system until the repositories
> are in a consistent state again. This issue will be closed when all builds
> are finished.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/issues/15745?email_source=notifications&email_token=AAGR7KPLY4D6YKXTHB74GP3QQCEFZA5CNFSM4JEFUMXKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HT4PPQQ>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAGR7KIDAAGYSFWEB74E2MDQQCEFZANCNFSM4JEFUMXA>
> .
>


  reply	other threads:[~2019-10-23 17:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 17:41 [ISSUE] " voidlinux-github
2019-10-23 17:44 ` voidlinux-github [this message]
2019-10-23 17:45 ` voidlinux-github
2019-10-23 19:43 ` voidlinux-github
2019-10-24  6:06 ` voidlinux-github
2019-10-26 10:25 ` voidlinux-github
2019-10-26 10:29 ` voidlinux-github
2019-10-26 10:36 ` voidlinux-github
2019-10-26 12:54 ` voidlinux-github
2019-10-26 12:54 ` [ISSUE] [CLOSED] " voidlinux-github

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=20191023174454.JdGu5m7uBHAc_EkvhArt7T_GS6VOogkiY-1M_BMugos@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).