Also includes a revert for the commit which broke the libinput devices
for consolekit session. I am still unsure of solution for both of the
problems to suggest upstream. But it is in my todo list.
Fixes#1585
See merge request postmarketOS/pmbootstrap!1613
Also includes a revert for the commit which broke the libinput devices
for consolekit session. I am still unsure of solution for both of the
problems to suggest upstream. But it is in my todo list.
Fixes#1585
This uses a variable configured in the gitlab project [settings->CI/CD->Variables]
to restrict when the qemu job will run. This should prevent the job from running
on repo forks where an appropriate runner has not been configured/registered.
Note that if this variable is set in a repo where there is no runner registered to
run qemu, then any CI jobs in that repo will ultimately fail the qemu tests since
no runner will be found.
* Travis and Coveralls badges
* aports: instead of <https://github.com/postmarketOS>, use
<https://postmarketos.org>
* References to full URLs to issues and pull requests replaced with
a hash and the number
* grsec check: simplify error message, remove link to github issue
(nobody is using that anymore anyway)
Alpine's firmware packages have been updated to include the latest
raspberry pi firmware. This commit adjusts our aports.
Details:
* remove obsolete `aports/temp/linux-firmware`
* `firmware/firmware-pi-bluetooth`: rename to `device/bluetooth-raspberry-pi`
and remove firmware files (they are part of Alpine's `linux-firmware` now)
* `device-raspberry-pi`: depend on `bluetooth-raspberry-pi`
* `device-raspberry-pi`: note that Alpine's kernels depend non free firmware
* `device-raspberry-pi`: remove non free firmware subpackage
Kernel is downstream. System boots. Flash the device using the netcat
method to an external SD (use the entire SD, not a partition, as the
target device) because the internal memory is too small.
This allows the user to talk to networkmanager to manage the system
connections. As it is mentioned in networkmanager pre-install.
```
Executing networkmanager-1.10.6-r0.pre-install
*
* To setup system connections, regular users must be member of 'plugdev' group.
```
The plugdev group gets created in the post-install hook of
networkmanager. Not all UIs depend on networkmanager, which means that
the group may not exist at installation time when we try to add the
user to the group in the python code. Therefore we create the group
first.
While this feature is nifty, it doesn't really work with most mobile
wireless drivers. Wireless drivers decide to go in "weird" state when
the mac address changes at runtime.
I remember talking to someone in IRC about this and getting it disabled.
not sure how this ended up here.
See: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513
This option is not working with most of the wireless drivers normally.
For example e.g it doesn't really play nice with one of my laptop's
wireless driver.
The ASUS MeMO Pad FHD 10 (ME302KL) is kinda like an enlarged version
of flo, all the unofficial Lineage / TWRP work has been derived from
flo. So eventually it should run mainline :) but let's start with this.
The linux APKBUILDs write the kernel config either to `$builddir`
(default from the template) or `$srcdir/build` (legacy, and I reverted
to that in #1556, which was not the proper fix for this regression).
With this commit, `pmbootstrap kconfig edit` is able to edit both
versions, and prints a note when the APKBUILD is still using the old
style.
Oliver Smith
ryang
Konrad Dybcio
deata
praticamentetilde
Bhushan Shah
Daniele Debernardi
Clayton Craft
Martijn Braam
Clayton Craft
yangxuan8282
myfreeweb
steamport