Github messages for voidlinux
 help / color / mirror / Atom feed
From: dnic <dnic@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Tier 1 Kansas City Repo Not Syncing
Date: Fri, 02 Dec 2022 02:09:46 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40872@inbox.vuxu.org> (raw)

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

New issue by dnic on void-packages repository

https://github.com/void-linux/void-packages/issues/40872

Description:
### Is this a new report?

Yes

### System Info

Void 6.0.8_1 x86_64-musl AuthenticAMD uptodate rFF

### Package(s) Affected

"All"

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

N/A

### Expected behaviour

Running `xbps-install -Suv` should pull down new package information as of today.

### Actual behaviour

No new package information is pulled down.

### Steps to reproduce

The Tier 1 repository in [Kansas City](https://repo-us.voidlinux.org/) hasn't synced since November 11th (as seen by the latest update file [here](https://repo-us.voidlinux.org/void-updates/void-updates_2022-11-11.txt)). The mirror in Chicago appears to have synced today (as seen by the latest update file [here](https://mirrors.servercentral.com/voidlinux/void-updates/void-updates_2022-12-01.txt)).

             reply	other threads:[~2022-12-02  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  1:09 dnic [this message]
2022-12-02  1:40 ` classabbyamp
2022-12-02  1:40 ` [ISSUE] [CLOSED] " classabbyamp
2022-12-02 21:41 ` dnic
2022-12-02 22:33 ` classabbyamp

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40872@inbox.vuxu.org \
    --to=dnic@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).