From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: phoc-0.4.2 calls-0.1.7 purism-chatty-0.1.15
Date: Sun, 28 Feb 2021 21:05:33 +0100 [thread overview]
Message-ID: <20210228200533.Ek9JQNMoD2XVn-qYfdbT8JhhlX15-tMhhNLPPSCn7gw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24538@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/24538#issuecomment-787513596
Comment:
https://github.com/jcgruenhage/void-packages/tree/pinephone <- has updates for:
- phosh and phoc
- megapixels
- calls (but it's broken, because my package for callaudiod doesn't split out the devel and lib packages yet)
- squeekboard
- mobile-config-firefox
I haven't been able to update pinephone-wys yet, since the patch doesn't apply anymore, haven't found an updated version of the patch yet.
Aside of that, after running phosh for the first time, my pinephone crashed, and now void isn't booting anymore. I think that's everything for now, but to move this forward, I'll split up the PR into multiple ones for each unrelated item, so one for calls, one for squeekboard, one for phoc and phosh, one for mobile-config-firefox and so on.
next prev parent reply other threads:[~2021-02-28 20:05 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 20:46 [PR PATCH] New packages: phoc-0.4.2 calls-0.1.7 purism-chatty--0.1.15 julio641742
2020-08-29 22:12 ` [PR REVIEW] " fosslinux
2020-08-29 22:12 ` fosslinux
2020-08-30 0:21 ` [PR PATCH] [Updated] " julio641742
2020-08-30 1:36 ` julio641742
2020-08-30 3:47 ` New packages: phoc-0.4.2 calls-0.1.7 purism-chatty-0.1.15 julio641742
2020-08-30 3:56 ` [PR REVIEW] " fosslinux
2020-08-30 3:56 ` fosslinux
2020-08-30 4:08 ` ericonr
2020-08-30 4:10 ` ericonr
2020-08-30 17:10 ` PaperMountainStudio
2020-08-31 0:27 ` [PR PATCH] [Updated] " julio641742
2020-08-31 0:32 ` julio641742
2020-08-31 0:35 ` [PR REVIEW] " julio641742
2020-08-31 0:39 ` [PR PATCH] [Updated] " julio641742
2020-08-31 0:41 ` julio641742
2020-08-31 1:06 ` [PR REVIEW] " ericonr
2020-09-12 18:00 ` [PR PATCH] [Updated] " julio641742
2020-09-12 18:19 ` julio641742
2020-09-12 18:46 ` julio641742
2020-09-12 18:52 ` julio641742
2020-09-12 21:46 ` [PR PATCH] [Updated] " julio641742
2020-09-12 22:08 ` julio641742
2020-09-12 22:23 ` julio641742
2020-09-12 22:32 ` julio641742
2020-09-12 23:17 ` julio641742
2020-09-13 5:35 ` [PR PATCH] [Updated] " julio641742
2020-09-13 5:53 ` julio641742
2020-09-13 7:42 ` julio641742
2020-09-13 12:08 ` jjsullivan5196
2020-09-13 12:08 ` jjsullivan5196
2020-09-19 8:24 ` [PR PATCH] [Updated] " julio641742
2020-09-20 2:14 ` julio641742
2020-09-20 4:57 ` julio641742
2020-09-21 11:11 ` jjsullivan5196
2020-09-21 11:11 ` jjsullivan5196
2020-09-21 11:12 ` jjsullivan5196
2020-09-23 21:47 ` [PR PATCH] [Updated] " julio641742
2020-09-23 21:49 ` julio641742
2020-09-25 9:23 ` jjsullivan5196
2020-10-02 21:44 ` Frick-David
2021-02-27 14:20 ` jcgruenhage
2021-02-28 10:36 ` jcgruenhage
2021-02-28 20:05 ` jcgruenhage [this message]
2021-02-28 21:32 ` jcgruenhage
2022-04-19 2:12 ` github-actions
2022-05-03 2:13 ` [PR PATCH] [Closed]: " github-actions
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=20210228200533.Ek9JQNMoD2XVn-qYfdbT8JhhlX15-tMhhNLPPSCn7gw@z \
--to=jcgruenhage@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).