Github messages for voidlinux
 help / color / mirror / Atom feed
From: AlgebraicFeline <AlgebraicFeline@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: package request: OpenTabletDriver
Date: Sun, 11 Dec 2022 00:12:29 +0100	[thread overview]
Message-ID: <20221210231229.Zz8YRhywAX7TdTvszUAb5JijV2ayDanLLZXC_JtkAKs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25728@inbox.vuxu.org>

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

New comment by AlgebraicFeline on void-packages repository

https://github.com/void-linux/void-packages/issues/25728#issuecomment-1345405328

Comment:
> > from what I can see currently, dotnet6 has been merged to the repos.
> 
> https://voidlinux.org/packages/?arch=x86_64&q=dotnet where? I don't see anything. From my understanding [void-dotnet#1](https://github.com/void-dotnet/void-packages/issues/1) will contain info about latest status for .NET Core 6/7 packaging, but it's certainly still not merged.

I just noticed what I wrote, I'm so sorry about that; I wrote this early in the morning my time and wasn't exactly very awake, I misread the void post you linked. Apologies on my part. Yea dotnet isn't merged yet, whoops.

  parent reply	other threads:[~2022-12-10 23:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  6:30 [ISSUE] " darkralts
2020-10-20 14:27 ` InfinityGhost
2020-12-02 21:02 ` martnnw
2020-12-02 21:03 ` martnnw
2020-12-02 21:05 ` martnnw
2020-12-02 21:06 ` martnnw
2021-11-14 20:37 ` notthewave
2022-12-10 18:27 ` AlgebraicFeline
2022-12-10 19:09 ` JamiKettunen
2022-12-10 23:11 ` AlgebraicFeline
2022-12-10 23:12 ` AlgebraicFeline [this message]
2022-12-10 23:24 ` AlgebraicFeline
2022-12-10 23:24 ` AlgebraicFeline
2022-12-21 14:59 ` rmboggs
2022-12-21 15:14 ` JamiKettunen
2023-07-22 12:12 ` nvkomimi
2023-07-22 12:31 ` JamiKettunen
2023-01-29  6:37 [ISSUE] Package " LMFuture-Me
2024-06-14  6:27 ` 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=20221210231229.Zz8YRhywAX7TdTvszUAb5JijV2ayDanLLZXC_JtkAKs@z \
    --to=algebraicfeline@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).