<DocScrutinizer05>
all I'll see from ubuntu is the kicad window, fullscreen in the VM window
<wpwrak>
DocScrutinizer05: since the issue at hand is to get it to run in your suse setup, i'm not really sure what you expect me to do. i mean, i can help you google for suse + keyword, but even there you probably know better than me what to do. and i have no experience with suse.
<DocScrutinizer05>
no, the ssue at hand is to get it running in an ubuntu system of which you please provide a disk image when done
<wpwrak>
enyc: i think the more "mainstream" the better in this case :)
<enyc>
unity is slow graphics dependent mess tbh
<wpwrak>
sorry, i won't give you disks :) way too much personal stuff on them ...
* DocScrutinizer05
headdesks, severely
<wpwrak>
s/disks/my disks/
<DocScrutinizer05>
that's why I asked you to create a vagrant box. Or use virtualbox if you don't like vagrant, I can turn it into vagrant in no time
<DocScrutinizer05>
vagrant is just a wrapper around all the VM providers they support, which are roundabout all known ones
<wpwrak>
DocScrutinizer05: the way i do things here is that i 1) add the ppa repository: add-apt-repository ppa:js-reynaud/ppa-kicad
<DocScrutinizer05>
so please could you install virtualbox (which maybe you never touched), install an ubuntu you consider right (which I never touched), and install and configure kicad on that ubuntu (which also I never did)
<wpwrak>
DocScrutinizer05: then apt-get update and apt-get install kicad that's it. i don't have any VMs or such stuff
<DocScrutinizer05>
then provide the VM disk image
<wpwrak>
``\`\================================
<wpwrak>
i
wpwrak has quit [Quit: Leaving]
<DocScrutinizer05>
o.O
<enyc>
i have virtualbox but not diskspace, but can advise on doing it
<enyc>
its not hard
<DocScrutinizer05>
if course virtualbox isn't hard
<enyc>
DocScrutinizer05: hrrm i've not looked into vagrant either hrrm
<DocScrutinizer05>
in the end it's not much different to virtualbox anyway, after all it uses virtualbox and just takes care about downloading disk images retc
<DocScrutinizer05>
etc, like starting virtualbox, ssh into the box, and similar stuff
<DocScrutinizer05>
it's pretty strange how Argentina fibertel hit the sack
lobito has joined #neo900
* DocScrutinizer05
ponders to run an X-server on our server
<enyc>
DocScrutinizer05: Xvnc ?
<DocScrutinizer05>
yep
<DocScrutinizer05>
or just tunnel ssh -X
<enyc>
DocScrutinizer05: anyway if you create a virtual machine via vagrant i can help with ppa install kicad and also how to build to packages i(and how to patch / create debian patched variants of source/binary packages)
<DocScrutinizer05>
ssh -X devel@Neo900 kicad
<enyc>
that will likely be very sloooooooooooooooooow over x11 over network
<DocScrutinizer05>
it will be fast ebnough to allow wpwrak to configure kicad in the way he needs it
<enyc>
i think from what he said there was no 'configure' needed per-se, just install ppa and install hat version of package to start with, off you go
<DocScrutinizer05>
then everybody can download the VM disk image form server, which is way faster than uploading it to server when wpwrak does the install locally
<enyc>
or indeed once you have your own vm copies just get updated deb's of kicad
<enyc>
which makes it much easier to swap 'versions'
<enyc>
not re-downloading whole vm ecah time or so
<DocScrutinizer05>
sure, once we got same insatllation base everywhere, we can do same upgrades in sync everywhere
<enyc>
it just needs to be amd64 ubuntu-xenial-variant i expect
<DocScrutinizer05>
no idea
<enyc>
i'd definetyl suggest trying to create a vagrant of ubuntu-mate 16.04(xenial long term support) 64bit
<enyc>
and install the ppa as above, see what happens
<enyc>
then i can show you the rebuild process
<enyc>
also useful
<DocScrutinizer05>
anyway time for me to have some food and possibly a nap, it's getting 'late' here, and I had my share of fun with two times installing kicad
<enyc>
then work out good idea dont panic
<enyc>
wowee -- looooads of build-dependencies but installing happily apparentyl can satisfy
<enyc>
it *looks* like the ubuntu xenial variant can be built on devuan-jessie
<enyc>
about to find out.. =)
<enyc>
waiting for build-deps to finisd installing ia package system
<enyc>
DocScrutinizer05: you ready to use that vagrant instance for building -- it install a LOT of packages -- some keep theing build chroot separtae from where they 'use' package but i suspect that sharing is not an issue here
<DocScrutinizer05>
I can just give it a try
<enyc>
DocScrutinizer05: ok for starters "apt-get install dpkg-dev fakeroot" <- standard stuff for building/compiling in short
<enyc>
devscripts could be useful later if using dpkg-source and all that to sign changes of source package
<DocScrutinizer05>
after apt-get update it seems to work
<DocScrutinizer05>
done
<enyc>
now... there are neater ways to do this but...
<enyc>
get most of dependencies first
<enyc>
apt-get build-dep kicad
<enyc>
(this may only get the deps for the version in debian jessie, but that gets much of them)
<enyc>
and apt-get update -- it will complain about key
<DocScrutinizer05>
hmm, I wonder if that works in devuan, but prolly should
<enyc>
it would (outwardly) appear its possible to compile that xenial (ubuntu LTS) version of kicad source on devuan jessie (at least according to published dependencies)
<enyc>
if that doesn't work you could create an ubuntu-mate-16.04 vagrant and try that of course
<enyc>
i reccomend/prefer creating a parallel login here and adduser compile and su - compile (do all compile work as a normal user) but you can use root if you prefer for some reason
<enyc>
if using your VMs maybe running as root is fine anyway
<DocScrutinizer05>
aah yepa warning: >>W: GPG error: http://ppa.launchpad.net xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 83FBAD2D910F124E<<
<enyc>
but, normally, debian packages can be built as any user with aid of fakeroot
<enyc>
debian package building quite helpful and strict qa etc
<enyc>
make decision, be in user account // directory reade to get source package
<enyc>
then "apt-get source kicad" <- we may need to disable checking for key though
<enyc>
of coruse the may be proper way to get the special ppa key but ... please try this for now first to learn
<enyc>
i have done many many cases of fiddling source packages and compiling across debian//ubuntu variants over the years with much success
<DocScrutinizer05>
9 upgraded, 366 newly installed, 0 to remove and 102 not upgraded.
<DocScrutinizer05>
Need to get 899 MB of archives.
<DocScrutinizer05>
After this operation, 1,693 MB of additional disk space will be used.
<enyc>
;p
<enyc>
yep loads ;p
<enyc>
but at least it is ''satisfiable'' without 'fiddling'
<enyc>
sometimse you end up backporting +installing some other package too etc etc first
<DocScrutinizer05>
jessie/main texlive-latex-extra-doc all 2014.20141024-1 [327 MB] o.O
<enyc>
hehhe
<enyc>
every... single.. little... thing ;p
<DocScrutinizer05>
Fetched 899 MB in 7min 43s (1,940 kB/s)
<enyc>
MAYBE for ''developing kicad'' itself would be better off with using the source tree (copy from there) separately somehow.. so can keep rerunning 'make' and not having to recomile *everything*
<enyc>
but its good to learn how to patch / commit to debian 'source' package
<enyc>
and build deb's using dpkg tools
<enyc>
after much fiddling with source pkg's we got mythtv ppa so it works on debian/devuan/ubuntu many variants=)
<enyc>
has to have sysvinit+upstart+systemd startup for mythbackend etc =)
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #neo900
pagurus has quit [Ping timeout: 276 seconds]
pagurus has joined #neo900
pagurus has quit [Remote host closed the connection]
pagurus has joined #neo900
illwieckz has quit [Quit: Ça va couper chérie…]
lkcl has quit [Ping timeout: 276 seconds]
lkcl has joined #neo900
<enyc>
DocScrutinizer05:
<enyc>
cc1plus: out of memory allocating 3143748 bytes after a total of 30662656 bytes
<enyc>
DocScrutinizer05: ontop of an ubuntu-trusty *64bit* (with updated kernel out of xenial), I successfully compiled ppa-xenial-kicad, on devuan stable chroot
<enyc>
DocScrutinizer05: same procedure as you did
<enyc>
DocScrutinizer05: some amount of ''warnings'' when compiling where normal
paulk-collins has joined #neo900
R0b0t1_ has quit [Read error: Connection reset by peer]
ecloud has quit [Ping timeout: 260 seconds]
ecloud has joined #neo900
mordac has quit [Ping timeout: 246 seconds]
arcean has joined #neo900
<enyc>
DocScrutinizer05: I wonder if your vagrant simply needs more ram allocated =)
<DocScrutinizer05>
I guess I could port the shell history
<DocScrutinizer05>
actually I should write a job for building anyway
<DocScrutinizer05>
what sucks is the dpkg-buildpackage -rfakeroot -b command nuking resp not resuming on all already build interim binaries
<DocScrutinizer05>
s/build/built/
bemyak has joined #neo900
<enyc>
no indeed thats for building redistributable packages consistently
<enyc>
if doing interim-work, just compile // make it (chcek what commands they are using, of course)
<enyc>
main thing is its been conviencet to get all the correct build deps sorted
<enyc>
and able to "pull" from the same repo wpwrak been using
<enyc>
(though, i don't know if wpwrak been using 16.04xenial or 14.04trusty ...)
<enyc>
also, now you've apparently got the right 'build environment' you can equually manually pull from git/svn/nightlies/etc source from upsteam directly and build that, if that later helps
<DocScrutinizer05>
default: Progress: 3% (Rate: 614k/s, Estimated time remaining: 0:16:43)
<DocScrutinizer05>
then writing scripts to automate the manual work done yesterday. Will be fun to get all the packages to install out of the error message
<DocScrutinizer05>
sidenote: [ 75%] Building CXX object pcbnew/CMakeFiles/_pcbnew.dir/menubar_pcbframe.cpp.o
<DocScrutinizer05>
a 2GB RAM helps a lot ;-)
<DocScrutinizer05>
I wonder if wpwrak will eventually come back
<enyc>
hopefully =) patience =)
arcean has quit [Read error: Connection reset by peer]
rjeffries has quit [Read error: Connection reset by peer]
<enyc>
so they really are using a logical-volume-manager partition on that single virtual disk
<enyc>
the QUESTION is --- is this (a) setup at vagrant local installation of machine time -- in which case can rebuild it with different config
<DocScrutinizer05>
the .box file gets nuked after box initialized
<enyc>
OR --- (b) does the box file contain a pre-prepared fixed-size disk-image, and we will need to actually resize from that ?
<enyc>
well get the box file or logon to server where it is, test list it... 7z t filename.box
<enyc>
or tar tvzf or zip --whatever-papameter-it-is ...
<enyc>
we see if it actually just came with the vdi or what
<DocScrutinizer05>
or (c) could we mount an additional diskimage on host into the vbox
<enyc>
yes, can do too... which you can do via virtualbox gui
<DocScrutinizer05>
downloading the file takes 20 min
<enyc>
to do (b) will need vboxmanage resize, parted resize (lvm container partition), and lvm internal resize, and ext4 online resize -- all very doable tbh just a case of figuring out
<enyc>
nb: for future ref you can do "dpkg-source -x kicad_4.0.2+e4-6225~38~ubuntu16.04.1.dsc" sort of thing extracting sources from dsc file directly iirc but carry on as you were
<enyc>
looks promising though you'd need some other terminal to tail -f the log
<DocScrutinizer05>
got that
<enyc>
should work with any luck =)
<enyc>
HOPEFULLY it will 'just' squeeze inside size limitations
xman has quit [Remote host closed the connection]
<enyc>
but I really really really think you need to get more _space_ in 64bit box to be sensible
<enyc>
in any case seeing kicad builds/installs/works on devuan following standard deb approach like that will be very helpful start
<DocScrutinizer05>
how about dpkg-buildpackage -rfakeroot -b &|tee -a ../kicad_4.0.2+e4-6225~38~ubuntu16.04.1.binary-build.log
<enyc>
probably ... theresa spurious & in there and you need 2>&1 in there SOMEWHERE so not sure
<enyc>
use what you first gave, that will certainly work i think
<enyc>
and catch both stdout+stderr in same file correctly
<DocScrutinizer05>
err sorry
<DocScrutinizer05>
how about dpkg-buildpackage -rfakeroot -b 2>&1 |tee -a ../kicad_4.0.2+e4-6225~38~ubuntu16.04.1.binary-build.log
<enyc>
PROBABLY
<enyc>
but not 100% sure not tried that lately
<DocScrutinizer05>
I guess it should work
<enyc>
HOPEFULLY
<enyc>
=)
<enyc>
let that get on
<enyc>
if you can do it, at the same time, start adding disk image to the 64bit box anyway
<DocScrutinizer05>
how would I do that?
<enyc>
looking in history...
<enyc>
15:33 < enyc> I suggest trying to get virtualbox gui to just add another hdd to the vm
<DocScrutinizer05>
hmmm
<enyc>
the 64bit vm should be shut-down, then add disk, basically... create it for you and everything
xman has joined #neo900
<enyc>
you can go to disk management and all that
<enyc>
add new disk -- create new disk from scratch -- etc
<enyc>
easy
<enyc>
then... fdisk and mkfs.ext4 and edit /etc/fstab and mount ....
<DocScrutinizer05>
that would imply I manage that VM via VBox GUI
<enyc>
hrrm i suspect you can do it that way if you just launch virtualbox
<DocScrutinizer05>
>>config.vm.synced_folder - Configures synced folders on the machine, so that folders on your host machine can be synced to and from the guest machine. Please see the page on synced folders for more information on how this setting works.<<
xes has quit [Ping timeout: 272 seconds]
<enyc>
DocScrutinizer05: you could try that approach too =)
<enyc>
DocScrutinizer05: but that sounds synced not *shared*
<enyc>
DocScrutinizer05: network mounted smb shared is a reasonable approach
<enyc>
DocScrutinizer05: but if you are doing all that.... i'd probably just do the whole resize vmdk thing instead =)
<enyc>
i think its likely as simple as Please verify that
<enyc>
the guest additions are properly installed in the guest
<enyc>
they may well just not be
<enyc>
virtualbox guest additions for linux
<enyc>
depending on your virtualbox install, you may have an iso image available
<DocScrutinizer05>
yes, been there tried that, when VM GUI was up. "install extensions" -> "No CD drive available in VM, please install CD"
<enyc>
e.g. using debian//ubuntu packages for virtualbox has a virtualbox-guest-addinions-iso package that provides exactly that
<enyc>
yes, go to disk drives, add a chrom drive, then do that
<enyc>
then we can mount that maunally easily (support will be in the kernel etc already) and go from there
<DocScrutinizer05>
again, needs management via VBox utils
<enyc>
you can probably just launch "VirtualBox" or "virtualbox" binary to get the gui up
<enyc>
its just a sort of frontend to manage vms running in backend basically
<DocScrutinizer05>
yep
<DocScrutinizer05>
been there done that, but it sucks from a vagrant perspective
<DocScrutinizer05>
you can't manage a ruining machine, regarding *any* config
<DocScrutinizer05>
you need to stopit first
<enyc>
hrrm no but then i guess this is a fiddly/hard problem ?
<enyc>
yes do that, stop the 64bit machine (obviously leave the 32bit machine compiling away =) )
<DocScrutinizer05>
in which case the window with the VB menus disappears
<enyc>
restart virtualbox gui ?
<enyc>
you should get a list of virtual machines ? right click on one and say 'settings' etc
<enyc>
if this approach doesn't work... dont panic, we use any other method available to us to copy iso in there (including http transfer) and loopback mount to access its contents instead
<enyc>
Next, make sure that the guest additions image is available by using the GUI and clicking on "Devices" followed by "Install Guest Additions". Then mount the CD-ROM to some locatio
<enyc>
yes, which you said gave error no cd drive
<enyc>
did you succeed in adding cd drive, and then doing "install guest additions" ????
<DocScrutinizer05>
just about to follow the instructions
<enyc>
yes, it tells you to do the same thing i already pointed at -- click the install guest additions button
<DocScrutinizer05>
>> Before installing the guest additions, you will need the linux kernel headers and the basic developer tools. On Ubuntu, you can easily install these like so: $ sudo apt-get install linux-headers-$(uname -r) build-essential dkms<< which is still running
<enyc>
yes that will also need to happen before we can actually do the ./run part
<enyc>
but in any case can attach the cdrom image to that vm, which needs adding a cd drive to that vm, (when shut down) with any luck
<DocScrutinizer05>
>> To install via the command line: You can find the appropriate guest additions version to match your VirtualBox version by selecting the appropriate version here. The examples below use 4.3.8, which was...<<
<enyc>
yes you can go wget it if plan a doesnt work
<enyc>
it should already be provided in your system
<enyc>
that commandline example is doing loopback-mount, as i was also suggeshing
<enyc>
what virtualbox version do you have on your opensuse // vagrant setup ?
<DocScrutinizer05>
cat .vbox_version
<DocScrutinizer05>
5.0.18
<enyc>
oooh good recent ish
<enyc>
well anyway... you have 2 paths you can try to get the iso in there
<DocScrutinizer05>
fakeroot is already the newest version.
<DocScrutinizer05>
fakeroot set to manually installed.
<DocScrutinizer05>
:-)
<enyc>
add the sources.list.d entry same as other m
<enyc>
vm
<DocScrutinizer05>
aah yep
<enyc>
apt-get update
<enyc>
it will complain about key
<enyc>
then, as the user, change to the special /home/compile/kicad directory
<enyc>
iirc something like "apt-get --allow-unauthenticated source kicad"
<enyc>
then... hopefully you can ...cd into source ... run the dpkg-buildpackage directed to logfile... and watch it fail but tell you what you need to install ...
<enyc>
then start build directed to logfile again ....
<enyc>
trouble is that won't work because you'd need sudo or something -- need to do the apt-get bit as root
<enyc>
just copy the packagelist to install manually, its only a once-off, not part of repeated builds
<enyc>
is it building away now?
<DocScrutinizer05>
dang! I fail to run apt-get install under root while getting correct output from dpkg-buildpackage under user:compile
<DocScrutinizer05>
for sudo compile isn't in sudoers, with su no dice, I'm too tired, should have a break
<enyc>
there are special tools like dpkg-checkbuilddeps and things to do clever stuff
<enyc>
BUT
<DocScrutinizer05>
ooh you already noticed that too
<enyc>
DONT BOTHER -- just run apt-get as root now
<enyc>
and then get it building away while you break
<DocScrutinizer05>
I need to write a script in parallel, for next time
<enyc>
i wouldn't *try* to automated it like that... there are pbuilders and allsorts for this that have lal that sorted already
<enyc>
if you want to write a completed scrpt you'd investigate dpkg-checkbuilddeps and pbuilder tools that create the build chroots automatically etc etc
<DocScrutinizer05>
this can't be that hard to fix this silly little troule
<enyc>
yes you could execute as root a command that does "su - compile" or similar
<enyc>
but it really will be a timesink fiddle if brain not clear now
<enyc>
whereas you can just apt-get install ... and run the build and leave it going
<DocScrutinizer05>
ooh, you got a point in it being a one-off
<enyc>
put a comment in scrept
<enyc>
yes indeed
<DocScrutinizer05>
already did (put comment in script)
<enyc>
yes so...
<enyc>
did you install the packages now?
<DocScrutinizer05>
2 upgraded, 493 newly installed, 0 to remove and 23 not upgraded.
<DocScrutinizer05>
Need to get 936 MB of archives.
<DocScrutinizer05>
After this operation, 1,997 MB of additional disk space will be used.
<DocScrutinizer05>
Do you want to continue? [Y/n]
<DocScrutinizer05>
this will take a while
<enyc>
so... get another login as compile user ready
<DocScrutinizer05>
already got that
<enyc>
just do a sleep 25m; dpkg-buildpackage -rfakeroot -b 2>&1 |tee ../kicad_4.0.2+e4-6225~38~ubuntu16.04.1.binary-build.log
<DocScrutinizer05>
as simple as vagrant ssh
<enyc>
then it will start in 25mins when download hopefully done ;p
<enyc>
or wait for it asnd start it, or something
<enyc>
anyway
<enyc>
s the 32bit vm // builder going ok still without runnig out of space too ?
<enyc>
wpwrak: ok well have to see if doc's built debs on devuan jessie work equivalently, at least
<enyc>
the key thing is it has a configured build-tree, so is possible to fiddle/recompile kicad as desired, if required
<enyc>
wpwrak: personally i didn't think a whole VM was needed, a chroot would do to avoid packaging systems getting confused/mixed, but anyay doc happily got a vagrant vm with virtualbox based shared folder ....
<wpwrak>
yeah, i'd be a bit worried about gfx performance in a VM. you can quickly end up with a lot of things that need drawing, and performance issues that may not be noticeable on a native install (thus, nobody else even sees them) could be disastrous
<wpwrak>
but let's see
<enyc>
can always copy it out to chroot ... its all there, built, etc etc
<R0b0t1>
if you emulate the processor it ends up being fine, if slow
<R0b0t1>
iOS has problems as Apple opted to "simulate" the phone OS
<enyc>
R0b0t1: =) using virtualbox doesnt simulate processor, will typically use virtualization extenisons etooo ... but otherwise paravirtualized pagetables andall that, but normal 'usermode code' is running natively
<R0b0t1>
oh I thought this was of the phone
<enyc>
R0b0t1: this is just about eda tools ;p
<R0b0t1>
oh huh
<enyc>
R0b0t1: or whatever the right wording is
<R0b0t1>
should switch to gentoo
<R0b0t1>
DocScrutinizer05: ^
<enyc>
R0b0t1: some fun over linux distro versions and being able to compile//recompile//use consistent kicad version
<R0b0t1>
yeagh
<enyc>
R0b0t1: gentoo good and bad in all its' own ways too =)
<R0b0t1>
I hate it. The least. :D
<enyc>
R0b0t1: gentoo chroots' can be really handy for building latest stuff / nonstandard use flags etc... but generally a paint to maintain for security updates etc -- you ned up making your own rolling release
<enyc>
R0b0t1: then thats fine for you
<R0b0t1>
:p
<enyc>
hybrid systetms can be really handy of cours for these reasons
<R0b0t1>
I just make a vm for everything
<R0b0t1>
I use qemu though
<enyc>
fine
<enyc>
qemu-kvm uses cpu extensions and kernel based hypervisor...
<R0b0t1>
my focus was mainly security research, not other kinds of development
<R0b0t1>
but can also softemulate
<R0b0t1>
I misread the convo, thought it was about doing device development
<enyc>
R0b0t1: hopefully wpwrak//DocScrutinizer05 will sort out kicad usability soon
<enyc>
R0b0t1: project could do with some help writing artices for site explaining these decisions and feasibilyt to complete etc....
<R0b0t1>
I need to give it a look again
<R0b0t1>
if I see anything I can help with I'll jot something down
<R0b0t1>
recently started working again
<enyc>
R0b0t1: a lot ridse of wpwrak//DocScrutinizer05 being able to do the layout themselves via kicad *hopeuflly* or others' help with some altium variant or something
<R0b0t1>
kicad can handle it, it's just boring as all hell
<R0b0t1>
do I need to find a russian guy with an altium key or
<R0b0t1>
there is azonenberg who idles in ##electronics and ##embedded
<R0b0t1>
he can answer questions, about autorouting and stuff
<R0b0t1>
he has made boards with high pincount FPGAs on them
<enyc>
wpwrak: is there a texst project you can get doc tno load and run and experienment wiht... and convert, etc etc ... to get good idea kicad not misbehaving ??
<Wizzup>
R0b0t1: nope, not yet
<enyc>
R0b0t1: getting right people together at right time will be helpful
<Wizzup>
R0b0t1: why are they low res and a screenshot
<Wizzup>
link me better pic later ;)
<Wizzup>
afk
<enyc>
R0b0t1: but be careful of right time, see when wpwrak/doc ready etc etc
<R0b0t1>
Wizzup: huh oh yeah
<R0b0t1>
I got another phone, I'll record me coldbooting it to SIMless
<R0b0t1>
I tweeted it at @NSAGov and @DoD, black helicopters showed up
<DocScrutinizer51>
plus carajillo for the finish
<R0b0t1>
sounds delicious
<DocScrutinizer51>
was delicius
<R0b0t1>
Wizzup: there's a vid of me booting it on my yt but I cba to go find it
<wpwrak>
enyc: i basically use whatever i worked on last as "test project". these days it's anelok. which needs a new layout anyway. so that's my test case for the push router and the "new" workflow. ("new" because some things are different in legacy and opengl mode)
<wpwrak>
DocScrutinizer51: grmbl. food pictures are evil.
pagurus has quit [Remote host closed the connection]
<DocScrutinizer51>
~ping
<infobot>
1 packet transmitted, 1 packet received, 0.0% packet loss
<enyc>
DocScrutinizer51: hoooooooray
<DocScrutinizer51>
vagrant ssh -X kicad ?
<enyc>
DocScrutinizer51: could try, i dont know how slow that will be
Pangolin has quit [Ping timeout: 258 seconds]
<DocScrutinizer51>
not that slow, it's all local
<enyc>
DocScrutinizer51: may be Xvnc better or copy to more minimal (not for building) chroot or whatever in host system later ... all sorts of options
<enyc>
DocScrutinizer51: yes, but it tends to bypass shared memory iirc
<enyc>
DocScrutinizer51: experiment =)
<enyc>
DocScrutinizer51: you would need to install deb package(s)
<enyc>
dpkg -i kicad[......].deb
<enyc>
which may well want some apt-get -f install to install some of the runtime dependencies
<DocScrutinizer51>
ok
<enyc>
you have *just* complied the standard deb packages thats' it
Pangolin has joined #neo900
<enyc>
they could go in apt repos for others or ..etc... but you can just dpkg -i manually
<DocScrutinizer51>
ack
<enyc>
if thasts' usable, then that whole sourcetree is ideal for making changes / manual compiles of different binaries for the program in future // etc
<enyc>
if really_weird consitency / threading sorts of problems happen may need to try a xenial chroot to compare with, but hopefully not =)
<DocScrutinizer51>
sorry, got DC
paulk-collins has quit [Quit: Leaving]
<DocScrutinizer05>
dang, lost sent and RX posts
<DocScrutinizer05>
gotta fix my ZNC
<DocScrutinizer05>
now... let's find(1) that .deb
<DocScrutinizer05>
hmph... dpkg-deb: building package `kicad' in `../kicad_4.0.2+e4-6225~38~ubuntu16.04.1_amd64.deb'.
<DocScrutinizer05>
wasn't ssh -X supposed to set $DISPLAY accordingly?
<DocScrutinizer05>
ohmy, missed >>X11 forwarding request failed on channel 0<<
<wpwrak>
"X11 forwarding request failed on channel 0" suggests that the unde...
<wpwrak>
yup
<DocScrutinizer05>
why?
<wpwrak>
dunno :)
<DocScrutinizer05>
freaking crap. So back to [2016-07-13 Wed 15:56:26] <DocScrutinizer05> anybody fluent with vagrant/virtualbox around to help me out? I want to configure the VM display to be native screen resolution (1960*1024) and grant the VM 4 CPU cores, how to say that in lingua Vagrantfile?
<zakx>
not sure about the resolution
<wpwrak>
but ... i don't think you'll be happy with kicad over SSH
<zakx>
cores is easy though
<zakx>
config.vm.provider "virtualbox" do |v|
<zakx>
v.cpus = 4
<zakx>
end
<wpwrak>
heh, that's actually a way to crash it :)
<DocScrutinizer05>
zakx: 1000 TA
<zakx>
DocScrutinizer05: if you know the VBoxManage argument to archieve the screen resolution, you can pass it with v.customize ["modifyvm", :id, "--arg", "value"]
<DocScrutinizer05>
TATATA
<DocScrutinizer05>
:-)
<wpwrak>
(crash) at least pcbnew. (in the opengl canvas)
<wpwrak>
rest of kicad seems to be reasonably remote-x-friendly, according to a quick test (not only in terms of working at all, but in terms of responsiveness. at least for simple stuff, like anelok.)
<DocScrutinizer05>
wpwrak: stuff is always as simple as "what needs to get displayed"
<zakx>
for RAM there's also the shortcut "v.memory = 1024"
<zakx>
that's about the time i started using it too (it was on CD with some magazine)
<DocScrutinizer05>
x11-common - X Window System (X.Org) infrastructure
<DocScrutinizer05>
?
<zakx>
i got annoyed by RPM pretty quickly though and after a brief period of apt-rpm i moved to debian
<zakx>
(and, of course, YaST)
<DocScrutinizer05>
YaST was a royal pain in the 2000-2009 times
<DocScrutinizer05>
since then it improved drastically, now even YaST haters start to love it
<DocScrutinizer05>
it no longer messes with core files in /etc
<DocScrutinizer05>
everything pretty cool about /etc management at large
<DocScrutinizer05>
should I apt-get install x11-common?
<DocScrutinizer05>
given my goal is to start kicad as sole X11 app
Kabouik has joined #neo900
<zakx>
does it hurt? i mean, you can trivially recreate the VM :)
<DocScrutinizer05>
can I?
<DocScrutinizer05>
I prolly should do a vagrant save
<Kabouik>
I did not follow apkenv, so sorry if my question is silly. Is it like Alien dalvik, and if so, can we hope running Android applications on Neo900?
<Kabouik>
Or is it just a proof of concept?
<zakx>
DocScrutinizer05: why would you be using vagrant if you couldn't?
<DocScrutinizer05>
apkenv is prolly just a chroot. There's however some other stuff I forgot the name of, which is supposed to support android
<DocScrutinizer05>
zakx: sorry?
<zakx>
AFAIK the whole point of vagrant is to have a sane way to provide receipes that recreate VMs as intended by their creators
<zakx>
you take a base box and some provisioning files and vagrant puts it together
<zakx>
for example, to have a development environment with all necessary dependencies etc.
<DocScrutinizer05>
I didn't do provisioning, I built kicad inside the box
<zakx>
instead of setting a linux VM up and manually installing packages off a list, you just checkout the vagrantfile + provisioning files and `vagrant up`
<DocScrutinizer05>
which took like 3h for compiling, plus another 2h for mountig an extended shared storage to make enough space for compiler
<zakx>
so what advantage do you gain by using vagrant as opposed to just creating a VM using the virtualbox gui? :)
<DocScrutinizer05>
I'm planning to use provisioning eventually
<Kabouik>
But is it actually reasonable to hope running apks on Neo900 DocScrutinizer05, or will it never be ported/developped, even if not theoretically impossible?
<DocScrutinizer05>
for now vargant was the already established and working way to get a devuan VM
<zakx>
ah, i see. well you could've just used the image they provide to import it into virtualbox
<DocScrutinizer05>
Kabouik: how could I tell?
<zakx>
saves you the hassle of configuring virtualbox through vagrant
<Kabouik>
You have all the answers!
<DocScrutinizer05>
I wish I had :-)
<DocScrutinizer05>
anyway, vagrant push I found, vagrant save I didn't
<Kabouik>
You have the leadership and good knowledge of which developpers are doing what on TMO, plus who's going to buy a Neo900, might help figuring whether this would be reasonable to hope for apks on Neo900 :p
<DocScrutinizer05>
*I* hope for them
<DocScrutinizer05>
but that doesn't mean a thing
<DocScrutinizer05>
check out pyra
<Kabouik>
Reasonable was the keyword, not hope :]
<Kabouik>
No, Pyra is too big for me
<DocScrutinizer05>
they gave me tjhe idea of that tool I forgot the name of
<Kabouik>
Also, I noticed that *all* my N900 batteries are dead. How are the batteries you got with those new N900 you sourced recently?
<DocScrutinizer05>
didn't test them yet
<DocScrutinizer05>
I assume they should be decent
<DocScrutinizer05>
now what the heck?
<DocScrutinizer05>
SNAPSHOT SAVE
<DocScrutinizer05>
Command: vagrant snapshot save NAME
<DocScrutinizer05>
This command saves a new named snapshot. If this command is used, the push and pop subcommands cannot be safely used.
<Kabouik>
There are no "new" batteries in this format being built, right? I'm afraid even compatible batteries bought "brand new" on the internet would be bad because actually old and not stored with storage charge
<DocScrutinizer05>
vs:
<DocScrutinizer05>
jr@saturn:~/vagrant-test/kicad-devuan-amd64> vagrant snapshot save with-kicad
<Kabouik>
Ok. I knew they were common, but thought only for old devices, and hence that there were only old stocks with "never used" batteries, but still with bad health