Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

proot-me/devs

chroot, mount --bind, and binfmt_misc without privilege/setup for Linux, https://proot-me.github.io

People

Repo info

Activity

Sep 12 10:54

oxr463 labeled #188
Sep 12 10:54

oxr463 labeled #188
Sep 12 06:31

5ghz opened #188
Aug 29 21:34

GitLab | Lucas Ramage pushed 1 commits to PRoot
Aug 29 21:20

oxr463 assigned #187
Aug 29 21:20

oxr463 opened #187
Aug 29 21:19

oxr463 on fix-mktemp

Replace mktemp with mkstemp Bu… (compare)
Aug 22 08:08

loveshack commented #186
Aug 21 18:09

oxr463 commented #186
Aug 21 18:06

oxr463 labeled #186
Aug 21 18:06

oxr463 labeled #186
Aug 21 18:06

oxr463 labeled #186
Aug 21 18:05

oxr463 commented #186
Aug 21 14:42

loveshack opened #186
Aug 14 11:25

oxr463 commented #138
Aug 14 08:54

christophe-lyon commented #138
Aug 14 03:16

oxr463 commented #106
Aug 14 02:12

sr229 commented #106
Aug 14 02:12

sr229 commented #106
Aug 07 19:19

oxr463 edited #185

vincenthage

@vincenthage

the other branches are run with 4.4.0-93-generic, and they all fail with the same tests: test-230f47cf

So it looks like it's an old bug that appeared with a 4.X kernel and hasn't been detected because the tests haven't been ran since

OH OH

proot-me/PRoot#100

this pull request's tests ran on the 4.4.0-93-generic kernel

and don't have this issue

I don't know if it's because it's a relatively old PR, or if it's because it's being merged to the next branch, or if it simply fixes the proot proot call

jopasserat

@jopasserat

@vincenthage but ain't that gonna disable coverity completely?

so you mean there must be a commit in next that fixes the tests

jopasserat

@jopasserat

i've manually triggered new builds on next

if it runs fine, maybe we could start by merging next in master

then rebase the PRs on the new master

and restart a dev cycle by creating a new dev branch against which all new PRs should be opened

vincenthage

@vincenthage

but ain't that gonna disable coverity completely? =>

it depends on how this env variable works

if coverity sets this value to true when all is covered

then having it set to true before shouldn't change it maybe

And yep, I agree above dev

let's get a sane master first, and then branch out from here

Hum, that's interesting

next is fine, even with 4.4.0-93

so that means it's one of the most recent commits on master that has broken the test

vincenthage

@vincenthage

ah, nevermind, indeed

there are like a lot of new commits on next

I don't know why I thought next was behind master

vincenthage

@vincenthage

You're free to do some git magic @jopasserat .

jopasserat

@jopasserat

git magic done :sparkles:

so now next is merged into master

i'll ditch next for the sake of clarity (will keep an offline copy on my repo just in case)

all the PRs are now based on the new master

jopasserat

@jopasserat

i've also cleared two branches fixing the loader problem that have been merged

the new travis build in my branch is ready, generating the static binaries on each push

we just have to agree on some sort of tagging for the artefacts generated and this can be automatically deployed to github releases by Travis

so we'll always have some build ready to fetch for new users

vincenthage

@vincenthage

:clap:

Lucas Ramage

@oxr463

The filename loader.exe is confusing to me. Why not name it loader.bin or loader.so, or something of that nature. Am I the only one who feels this way?

https://en.wikipedia.org/wiki/Executable_and_Linkable_Format

Lucas Ramage

@oxr463

It appears that the exe extension was added to address a shortcoming of the build system regarding 32bit binaries on 64 bit hosts.

Lucas Ramage

@oxr463

Just updated my kernel to 5.1 two days ago, and now almost all tests are failing :facepalm:

Lucas Ramage

@oxr463

https://stackoverflow.com/questions/56535083/how-to-fix-segsegv-with-recent-kernel-and-seccomp

matrixbot

@matrixbot

@ashledombos:matrix.org Hello

Lucas Ramage

@oxr463

Greetings

I didn't know there was a Gitter/Matrix bridge!

matrixbot

@matrixbot

@oxr463:matrix.org Greetings from the matrix!

Lucas Ramage

@oxr463

This is lovely

matrixbot

@matrixbot

@ashledombos:matrix.org Lucas Ramage (Gitter): yes, bridges are good things

Lucas Ramage

@oxr463

I've been using the IRC/Matrix bridge for over a year now. I like it because it makes the logs persistent for all the channels I join on Freenode.

Vladimir

@5ghz

Hi all, I have a problem with install software in proot environment
Host Ubuntu 18.04 Amd64
Target L4T 32.2 (JetPack 4.2.2), arm64
switch in proot environment
proot -R /home/unknown/tegra_linux/ -v 2 -q qemu-aarch64
Install software via apt
apt install cmake -y
Logs after command
https://gist.github.com/5ghz/d24272a3bb96ab7e152bb3de8f98f513
Install via dpkg works normal

Lucas Ramage

@oxr463

Greetings, I saw your issue, (proot-me/proot#188).

Lucas Ramage

@oxr463

I plan on looking at it later this evening. Interesting that dpkg works correctly though. Have you tried running PRoot with the -0 flag, https://github.com/proot-me/proot/issues/156#issuecomment-452506903?