From: MGlolenstine <MGlolenstine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] rpi-kernel: Support for Raspberry Pi 4
Date: Mon, 17 Aug 2020 00:08:31 +0200 [thread overview]
Message-ID: <20200816220831.1rrLtY7PcUXMfhKsOlnqIjIbOJsbMlYy9MNvSJqew7I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23541@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
New comment by MGlolenstine on void-packages repository
https://github.com/void-linux/void-packages/pull/23541#issuecomment-674584091
Comment:
> > > @MGlolenstine you need to rebase this branch on top of latest upstream/master, otherwise it will try to install old dependencies.
> >
> >
> > Oh you're right. Thanks!
> > So I'm correct to be compiling that package on my laptop?
>
> Sorry to bother, but how have you fixed the issue? Getting the exact same error
You're not bothering at all...
First clone the PR, then add "upstream" repository(add original one using `git remote add upstream https://github.com/void-linux/void-packages), then do `git fetch upstream` and lastly do `git rebase upstream/master` to move this commit to the top of the upstream and merge it with new changes.
Then just repeat steps.
I hope this helped and if you manage to create a bootable image, please report back, as I've been having some problems myself, which you can see above.
Kind regards, MGlolenstine
next prev parent reply other threads:[~2020-08-16 22:08 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 1:52 [PR PATCH] " agausmann
2020-07-13 1:52 ` agausmann
2020-07-13 1:57 ` pbui
2020-07-13 9:26 ` [NOMERGE] " Piraty
2020-07-13 13:14 ` Piraty
2020-07-13 13:15 ` Piraty
2020-07-14 1:38 ` fosslinux
2020-07-14 5:11 ` agausmann
2020-07-14 5:12 ` agausmann
2020-07-14 5:12 ` agausmann
2020-07-14 5:13 ` agausmann
2020-07-14 9:24 ` fosslinux
2020-07-18 19:41 ` nathanblair
2020-07-18 19:55 ` nathanblair
2020-07-18 19:56 ` nathanblair
2020-07-19 0:03 ` nathanblair
2020-08-09 15:14 ` MGlolenstine
2020-08-09 15:15 ` MGlolenstine
2020-08-09 16:00 ` ericonr
2020-08-09 16:01 ` MGlolenstine
2020-08-09 18:40 ` ericonr
2020-08-09 19:01 ` MGlolenstine
2020-08-16 20:12 ` Yuvalhad12
2020-08-16 22:08 ` MGlolenstine [this message]
2020-08-17 7:59 ` agausmann
2020-08-17 8:00 ` agausmann
2020-08-17 8:09 ` MGlolenstine
2020-08-17 16:05 ` PaperMountainStudio
2020-08-17 16:05 ` PaperMountainStudio
2020-08-17 16:08 ` MGlolenstine
2020-08-22 19:31 ` aisecat
2020-08-27 12:12 ` PaperMountainStudio
2020-08-27 13:20 ` aisecat
2020-08-27 13:22 ` MGlolenstine
2020-08-27 13:27 ` aisecat
2020-08-27 15:22 ` PaperMountainStudio
2020-08-27 20:15 ` PaperMountainStudio
2020-08-27 20:43 ` aisecat
2020-08-27 20:54 ` aisecat
2020-08-27 23:12 ` br0qn
2020-08-27 23:14 ` ericonr
2020-08-27 23:43 ` br0qn
2020-08-28 1:37 ` br0qn
2020-08-28 1:45 ` br0qn
2020-08-28 6:50 ` PaperMountainStudio
2020-08-28 7:04 ` PaperMountainStudio
2020-08-28 13:29 ` jsumners
2020-08-28 17:24 ` [PR PATCH] [Updated] " agausmann
2020-08-28 17:25 ` agausmann
2020-08-28 21:18 ` jsumners
2020-08-29 22:07 ` br0qn
2020-08-29 22:15 ` br0qn
2020-08-29 23:31 ` br0qn
2020-08-29 23:33 ` br0qn
2020-08-30 0:54 ` jsumners
2020-08-30 8:38 ` PaperMountainStudio
2020-08-30 16:43 ` jsumners
2020-10-05 18:57 ` Frick-David
2020-10-06 8:17 ` Piraty
2020-10-28 18:51 ` BikyAlex
2020-10-28 19:37 ` agausmann
2020-10-28 19:37 ` agausmann
2020-10-28 19:37 ` agausmann
2020-11-01 20:48 ` Piraty
2020-11-01 20:49 ` Piraty
2020-11-01 20:49 ` Piraty
2020-11-01 20:49 ` [PR PATCH] [Closed]: " Piraty
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=20200816220831.1rrLtY7PcUXMfhKsOlnqIjIbOJsbMlYy9MNvSJqew7I@z \
--to=mglolenstine@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).