Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]>
Subject: Re: [ISSUE] [CLOSED] gcc and libada-devel
Date: Tue, 24 May 2022 04:12:14 +0200	[thread overview]
Message-ID: <20220524021214.-eajkDfTmJh62XUH1hpQfK8j6avF19NGkwss2IDeh10@z> (raw)
In-Reply-To: <>

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

Closed issue by unspecd on void-packages repository

<!-- Don't request update of package. We have a script for that. . However, a quality pull request may help. -->
### System

* xuname:  
  *Void 5.10.25_1 x86_64-musl GenuineIntel uptodate rrrnFFFFFFFFFFF*
* package:

### Expected behavior
$ xbps-query --repository=$(xdistdir)/hostdir/binpkgs -f gcc | grep /ada  # empty output
### Actual behavior

$ xbps-query --repository=$(xdistdir)/hostdir/binpkgs -f gcc | grep /ada
Note that this file should be in the `libada-devel` package.

### Steps to reproduce the behavior
$ ./xbps-src -o ~ada pkg gcc

      parent reply	other threads:[~2022-05-24  2:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 16:31 [ISSUE] " unspecd
2021-03-24  3:09 ` ericonr
2021-03-24 11:24 ` sgn
2022-05-10  2:00 ` github-actions
2022-05-24  2:12 ` github-actions [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220524021214.-eajkDfTmJh62XUH1hpQfK8j6avF19NGkwss2IDeh10@z \ \

* 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).