IRC log for #devuan on 20170910

00:10.16*** join/#devuan debdog (~debdog@ip-37-201-5-223.hsi13.unitymediagroup.de)
00:10.39*** join/#devuan cioran89__ (~cioran89@p5DDF0134.dip0.t-ipconnect.de)
00:28.33*** join/#devuan Guest1754 (~Guest@83.220.238.169)
00:37.08*** join/#devuan shwsh (~shwsh@171.248.107.116)
01:08.50*** join/#devuan rrq (~ralph@60-242-139-200.static.tpgi.com.au)
01:37.37*** join/#devuan Humpelst1lzchen (erik@x4e366b8c.dyn.telefonica.de)
01:38.14*** join/#devuan rdav (~rdav@61.181.148.122.sta.dodo.net.au)
02:10.40*** join/#devuan Hoshpak (~Hoshpak@p200300C90BDFC600004109FFFE40D1E1.dip0.t-ipconnect.de)
02:22.40*** join/#devuan MDrights (~MDrights@31.220.42.234)
02:33.59*** join/#devuan Drugo (~Drugo@62-11-1-95.dialup.tiscali.it)
02:39.22*** join/#devuan debdog (~debdog@ip-37-201-5-223.hsi13.unitymediagroup.de)
02:50.01*** join/#devuan Drugo (~Drugo@62-11-1-95.dialup.tiscali.it)
03:32.24*** join/#devuan debdog (~debdog@ip-37-201-5-223.hsi13.unitymediagroup.de)
03:43.23bozoniussticks gold star on himself -- thank you golinux -- but accidentally stabs himself with it and dies
03:46.04*** join/#devuan Guest1527 (~Guest@83.220.236.78)
03:47.44golinuxbozonius: Nooooo!  This place would be very quiet without you.  :)
04:05.24*** join/#devuan Carmen (~Carmen@static-68-235-41-123.cust.tzulo.com)
04:05.41*** join/#devuan XuR (~quassel@2600:8800:980:e490:55d2:cdc6:1445:4e1a)
04:06.40Carmenhi
04:06.52Carmen_systemd_is_evil, that is a fantastic username.
04:14.23bozonius(if you enjoy typing nicks, yes it is)
04:14.58bozoniusgolinux:  It is hardly my fault if I talk a lot here.   I am only reporting what I see.
04:16.08fromportis the forum very active ? do people ask questions/report "glitches"
04:16.10fromport?
04:19.09golinuxfromport: Yes.
04:19.43golinuxBut everything is a little slow atm.  Still in summer mode.
04:22.51fromportis very impressed with devuan this far. running unstable and see updates come by almost every day. very impressive, keep up the good work devuan developers !
04:26.33*** join/#devuan debdog (~debdog@2a02:8070:4182:a200:7a24:afff:fe8a:d04d)
05:12.03MDrightsHi , am curious to ask, Refractasnapshot, and live-sdk, which do you prefer?
05:14.19MDrightsand live-build
05:20.05gnarfacerefracta is easy
05:45.49*** join/#devuan debdog (~debdog@ip-37-201-5-223.hsi13.unitymediagroup.de)
06:02.40MDrightsgnarface, thanks for responding )
06:03.33MDrightsAnd....anyone knows about some mirros of Devuan's repo ? I can hardly find them from the official websites....(
06:04.51golinuxI see over 40 options on devuan.org index page
06:06.57golinuxMDrights: ^^^
06:09.06MDrightsgolinux, aren't those the download mirrors , not the repo mirror....?
06:15.56golinuxMy bad for misreading.  There are no repo mirros yet.  But several are in the works.
06:27.00*** join/#devuan Irrwahn (UNKNOWN@p5797D8FB.dip0.t-ipconnect.de)
06:48.26*** join/#devuan pillepalle (~Thunderbi@5.146.73.225)
06:51.05*** join/#devuan rsx (~rsx@ppp-46-244-244-141.dynamic.mnet-online.de)
06:53.32*** join/#devuan Ltem (~ltem@h081217057026.dyn.cm.kabsi.at)
07:02.15*** join/#devuan debdog (~debdog@ip-37-201-5-223.hsi13.unitymediagroup.de)
07:19.16DocScrutinizer05MDrights: repo mirrors are not exactly simple, due to:
07:19.19DocScrutinizer05!amprolla
07:19.19infobotnextime gave an excellent explanation how amprolla works, at https://botbot.me/freenode/devuan/2016-05-07/?msg=65646427&page=4, or https://git.devuan.org/devuan-infrastructure/amprolla
07:20.59MDrightsgolinux, DocScrutinizer05 , I see...(thanks though ~
07:24.03DocScrutinizer05I got to correct myself: repo mirrors are simple enough, but not standard as any other existing mirroring solution
07:25.18DocScrutinizer05afaik it needs control over the webserver (apache) rewrite rules in mirror
07:26.03*** join/#devuan rdav__ (~rdav@61.181.148.122.sta.dodo.net.au)
07:26.58DocScrutinizer05also afaik a 2 tier architecture is planned: 1st level mirrors get push-synced, 2nd level pull-syncs from 1st
07:37.21*** join/#devuan p4cman (uid171740@gateway/web/irccloud.com/x-mbngepdhxfnlvpvf)
08:06.59*** join/#devuan DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
08:09.21*** join/#devuan aitor (~aitor@171.85-84-183.dynamic.clientes.euskaltel.es)
08:09.24aitormoin
08:27.20*** join/#devuan Fervi (~fervi@89-76-224-228.dynamic.chello.pl)
08:46.50dethaDocScrutinizer05: do you happen to know who is working on that?
08:48.28DocScrutinizer05not exactly
08:48.32DocScrutinizer05ask parazyd
08:48.51DocScrutinizer05or Centurion-Dan
08:48.59DocScrutinizer05or jaromil
08:49.42DocScrutinizer05or KatolaZ
08:50.08parazydwhat's up?
08:50.26DocScrutinizer05who's working on repo mirror implementation?
08:50.52parazydKatolaZ needs to setup a httpd and we need to build a new devuan-keyring with the new key
08:51.02parazydshould be ready throughout this week
08:51.08DocScrutinizer05:-)
08:51.42dethaThat sounds promising. That means I may eventually be able to move some of the lab stuff to devuan
08:59.29*** join/#devuan Pali (~pali@Maemo/community/contributor/Pali)
09:04.20*** join/#devuan Ipe (~Ipe@85-76-10-147-nat.elisa-mobile.fi)
09:16.21*** join/#devuan Levure (~quassel@109.133.217.186)
09:47.51*** join/#devuan telst4r (~telst4r@fsf/member/telst4r)
10:07.41*** join/#devuan debdog (~debdog@ip-37-201-5-223.hsi13.unitymediagroup.de)
10:23.32aitorhi, rsyslog is not instalable in ascii because it depends on libjson-c2 and liblognorm2 and neither of them exist
10:24.16aitorthe names of these packages changed to libjson-c3 and liblognorm5, respectively
10:25.22aitorplease, change both dependencies, because live-build (or debootstrap) doesn't work for me in ascii
10:37.52aitorall the packaging configuration stuff of live-build is related with chroot and binary, tasks which are carried out at a late stage of bootstrap
10:38.02aitorhttp://complete.sisudoc.org/manual/html/live-manual/customizing-package-installation.en.html
10:41.28aitorneed to reboot
10:44.12*** join/#devuan Dowzee (~Dowzee@xocekim.com)
10:49.25fsmithredaitor, use rsyslog from jessie-backports for ascii. Download the deb and put it in the chroot_packages dir. (or wherever debs go)
10:52.24fsmithredor else use syslog-ng or busybox-syslogd
10:53.10*** join/#devuan aitor (~aitor@171.85-84-183.dynamic.clientes.euskaltel.es)
10:54.18aitorhi fsmithred, now i'm trying with live-sdk using the simplest blend "devuan-live"
10:54.34fsmithredhi
10:54.51fsmithredyou saw my note?
10:55.26aitori'm looking at your howto in dev1g: https://dev1galaxy.org/viewtopic.php?id=551
10:55.37fsmithredoh, ok
10:56.02fsmithredjust after you left...   <fsmithred> aitor, use rsyslog from jessie-backports for ascii. Download the deb and put it in the chroot_packages dir. (or wherever debs go)
10:56.02fsmithred<fsmithred> or else use syslog-ng or busybox-syslogd
10:56.19aitorhuh! the filesystem.squasfsh has only 16,4 Mb
10:56.34fsmithredsounds like just a boot menu
10:56.38fsmithredoh
10:56.44fsmithredno, not in the squash
10:57.04fsmithredanything useful in the output?
10:57.31aitori downloaded your jessie-oblx
10:58.08aitori can add the d-i to the blend
10:58.24aitori'll try it
10:58.29fsmithredok
10:59.19aitorhow can i reverse the situation?
10:59.59fsmithredreverse what?
11:00.07fsmithredremove d-i from the blend?
11:01.11aitorno, the content generated by:
11:01.39aitorload devuan <arch> <blend_name>
11:01.42aitorand:
11:01.49aitorbuild_iso_dist
11:02.14fsmithredsudo rm -r tmp/*
11:02.15aitorsomething like lb --purge in live-build
11:02.19aitorok
11:02.27fsmithredyou could get more selective
11:02.45fsmithredremove tmp/devuan...
11:02.51fsmithredand keep the bootstrap tarball
11:03.07fsmithredsecond run will go a little faster
11:03.20fsmithredbut you may get some debconf dialogs to answer
11:03.37aitoris it possible to use several blends with blend_map=( ... )?
11:03.44fsmithredwhy is squashfs so small?
11:04.05aitori still don't knowo
11:04.09aitorknow*
11:04.10fsmithredyes, you can have several blends and call the one you want
11:04.30fsmithredcheck logs and terminal output
11:04.58fsmithredscroll up a little to see the output for mksquashfs
11:05.07fsmithreddid you run out of hard drive space?
11:05.37aitorthere is nothing strange in the cmd output
11:06.56aitorCreating 4.0 filesystem on binary/live/filesystem.squashfs, block size 131072
11:07.14aitorExportable Squashfs 4.0 filesystem, xz compressed, data block size 131072
11:07.39aitorFilesystem size 15982.67 Kbytes (15.61 Mbytes)
11:08.08fsmithredlook in the bootstrap dir and make sure there's a full filesystem
11:08.20fsmithredunless you already deleted it
11:09.08aitori still haven't deleted anything
11:11.34aitorthere are some .debs: refracta, firmware...
11:11.53aitorthe empty folders boot, sys, proc...
11:12.06fsmithredusr?
11:12.11fsmithredetc?
11:12.19aitorthe usr folder containig yad and some refracta scripts
11:12.20fsmithredshould all be there ready to get squashed
11:12.50aitorno etc
11:13.11aitorthere are also the dev folder and the home
11:13.15fsmithredcheck logs. um, thirdstage.log or something like that
11:13.37aitorthe log folder is empty
11:13.57fsmithredwhat live-sdk are you using?
11:14.07fsmithredmost recent, or older?
11:14.30aitorhttps://github.com/parazyd/live-sdk.git
11:15.11fsmithredwhen did you get it?
11:15.50aitortoday
11:15.55aitorthe code looks nice
11:15.56fsmithredhang on
11:16.02fsmithredyeah, he writes good code
11:16.07aitoryes
11:16.11*** join/#devuan thaller (~thaller@host17-168-static.38-79-b.business.telecomitalia.it)
11:16.59aitorlet me play with it and we'll talk in a few hours, see you later
11:17.15fsmithredtry the april version
11:17.34fsmithredI can't get the newest one to run, either
11:17.45aitorok, where is it, in gitlab?
11:17.54fsmithredno. same place
11:17.58fsmithredI'm trying to find it now.
11:18.55aitorthere are no tags in git
11:19.25fsmithredyeah, I'm seeing that. I think there were some a couple weeks ago.
11:20.04aitordevuan-sdk, maybe?
11:20.13aitori also downloaded it
11:20.22fsmithredI think I'm using it the way it was April 23.
11:21.32*** join/#devuan peetaur (~peter@p57AAA2E4.dip0.t-ipconnect.de)
11:27.35aitorthis is yours: https://github.com/fsmithred/example-live-sdk
11:27.49fsmithredyeah, don't use that. It's not up to date
11:28.19fsmithredI'm looking at my build dirs now, figuring out what to exclude to make it small enough to send you a tarball
11:29.04aitorok, thanks and bbl
11:44.17aitorOops...
11:44.42aitorlib/libdevuansdk/extra/debootstrap/debootstrap disappears !!
11:44.48aitorsee you later
12:02.53*** join/#devuan Ltem (~ltem@h081217057026.dyn.cm.kabsi.at)
12:13.27*** join/#devuan justinsm (~justinsm@82-69-63-196.dsl.in-addr.zen.co.uk)
12:25.08Humcurseofwar shows ansicodes or similiar: "6H.;9H" I need a better reportbug
12:26.05HumI don't know the package: curseofwar or urxvt. reportbug: If you don't know what package the bug is in, please contact debian-user@lists.debian.org for assistance.
12:26.27Humshould I really ask the debian-user@?
12:28.47*** join/#devuan p4cman (uid171740@gateway/web/irccloud.com/x-hnnjzichwqmkpaeo)
12:36.45*** join/#devuan XuR_ (~quassel@2600:8800:980:e490:55d2:cdc6:1445:4e1a)
12:45.31*** join/#devuan rdav__ (~rdav@61.181.148.122.sta.dodo.net.au)
13:24.40*** join/#devuan poppageek (~poppageek@2602:30d:14ca:3960:855b:a2e1:fb24:e22d)
13:31.48*** join/#devuan mobinmob_ (~mobinmob@2a02:582:741f:d100:a5fc:7fd5:1e46:d984)
13:32.39*** join/#devuan rdav__ (~rdav@61.181.148.122.sta.dodo.net.au)
14:06.30*** join/#devuan guru (~guru@2601:196:8700:c91:3252:cbff:fec5:6f94)
14:17.01*** join/#devuan furrywolf (~randyg@172.56.39.109)
14:17.49*** join/#devuan telst4r (~telst4r@fsf/member/telst4r)
14:24.27*** join/#devuan ibispi_ (~quassel@cable-188-246-35-48.dynamic.kdsinter.net)
14:28.02*** join/#devuan shwsh (~shwsh@171.248.107.116)
14:32.40ibispi_hello, everyone, my friend has this error happen to her when she tries to run some program via wine https://pastebin.com/aQghDr5u one of the things we've found on the internet is that she'd have to install 'lib32-mesa-libgl', but that seems to be unavailable as a package for devuan, what do we do?
14:40.07*** join/#devuan furrywolf (~randyg@mce0536d0.tmodns.net)
14:52.37*** join/#devuan tarbz2 (~Thunderbi@181.44.164.227)
15:01.13fsmithredibispi_, install libgl1-mesa-dri
15:01.52ibispi_hey fsmithred, thanks!
15:17.53*** join/#devuan Katnija (~KittenGNU@208.209.9.46.customer.cdi.no)
15:18.33*** join/#devuan saptech (~saptech@unaffiliated/saptech)
15:21.25*** part/#devuan mobinmob_ (~mobinmob@2a02:582:741f:d100:a5fc:7fd5:1e46:d984)
15:27.30*** join/#devuan EHeM (~ehem@mailhost.m5p.com)
15:29.06EHeMWhat are the status of mipsel and arm64 ports?  Any plans for Devuan/kFreeBSD?
15:29.41*** join/#devuan pillepalle (~Thunderbi@5.146.73.225)
15:34.00*** join/#devuan jathan (~jathan@189.216.207.255)
15:57.47*** join/#devuan jord (~jord@185.103.96.135)
16:20.14*** join/#devuan clemens3 (~clemens@178-82-248-142.dynamic.hispeed.ch)
16:22.30*** join/#devuan clemens3 (~clemens@178-82-248-142.dynamic.hispeed.ch)
16:31.33*** join/#devuan nighty- (~nighty@s229123.ppp.asahi-net.or.jp)
16:58.25*** join/#devuan dienecks (~dienecks@2a04:2413:8202:e680:512e:8ad8:1c15:43f1)
17:00.10*** join/#devuan AntoFox (~Thunderbi@dynamic-adsl-78-12-46-77.clienti.tiscali.it)
17:04.29*** join/#devuan Guest1278 (~Guest@83.220.238.140)
17:23.02*** join/#devuan matlock (~matlock@user-24-214-145-29.knology.net)
17:24.44*** join/#devuan menip (~menip@c-73-53-122-132.hsd1.wa.comcast.net)
17:26.33*** join/#devuan matlock (~matlock@gateway/vpn/privateinternetaccess/matlock)
17:34.57*** join/#devuan LEXOmx (~lexo@gateway/tor-sasl/lex0)
17:41.25*** join/#devuan jathan (~jathan@189.216.207.255)
17:55.19*** join/#devuan AntoFox1 (~Thunderbi@dynamic-adsl-78-12-46-77.clienti.tiscali.it)
18:37.54*** part/#devuan lex0 (~lexo@gateway/tor-sasl/lex0)
18:45.57*** join/#devuan justinsm (~justinsm@82-69-63-196.dsl.in-addr.zen.co.uk)
18:46.46*** join/#devuan Ipee (~Ipe@n8eyq5k4xggya4axd-2.v6.elisa-mobile.fi)
18:55.38*** join/#devuan reetspetit (~john@239.red-80-59-216.staticip.rima-tde.net)
18:59.54*** join/#devuan Drugo (~Drugo@62-11-1-95.dialup.tiscali.it)
19:02.24*** join/#devuan eliasr (uid27497@gateway/web/irccloud.com/x-jafrzwhklwadfcsu)
19:07.14*** join/#devuan Ipe (~Ipe@n99yq1j7e7mb5dn2y-2.v6.elisa-mobile.fi)
19:07.18*** join/#devuan f-a (~f-a@151.38.38.175)
19:13.03bozoniusgnarface, et al:  I've decided to back out the openrc (which was a mistake anyway) and just move forward with sysv-rc
19:13.15*** part/#devuan f-a (~f-a@151.38.38.175)
19:13.28bozoniusthis eliminates a lot of support issues and allows me to move forward with the porting of omv
19:13.50*** join/#devuan Ipee (~Ipe@nbmbv6ek50noh7pnp-2.v6.elisa-mobile.fi)
19:14.04bozoniusI really don't want to get into that whole morass of openrc and where they are headed, or even getting a current spec
19:14.32bozoniusI was able to write a systemctl shim like the one I wrote for openrc, so no problems there.
19:15.47p4cmanand where is openrc headed to?
19:16.15bozoniusI, for one, don't know.
19:16.49bozoniusI can't even get a full spec on the current implementation.  But for the moment, I dont need to worry with respect to the omv port
19:17.20bozoniusI'm just posting here to let folks in the channel know that I've decided to give that up for this port
19:20.10gnu_srsbozonius: What version of openrc did you install? I don't think you need any systemctl shim for either sysv-rc or openrc. Does your sources.list contain debian??
19:21.04bozoniusgnu_srs you are late to the party.   You see, omv v3 is on Debian with systemd, so the omv package itself is using systemctl calls.
19:21.15bozoniusso, yes, it needs a shim
19:21.23bozonius(just for omv, though)
19:22.37gnu_srsif omv needs systemd, there is something wrong with devuan setup. It should not be installable from devuan
19:23.05gnu_srsSo how did you get that package?
19:23.05bozoniusomv's package has a dependency (I kid you not) of systemd
19:23.30bozoniusso I had to remove that dependency from the package.  Trouble is, the application ware is full of systemd calls
19:23.34gnu_srsthen you must have debian repos in your sources.list
19:23.57gnu_srsAre you building from source or not?
19:24.10bozoniusso to simplify porting, I repackaged it to exclude the systemd dependency, and included the shim
19:24.21bozoniusit's mostly js and php (web app)
19:25.20bozoniusthe port works, and it works just as well as the systemd (Debian jessie) implemetation
19:25.22*** join/#devuan Ipeee (~Ipe@85-76-6-218-nat.elisa-mobile.fi)
19:26.06gnu_srsapt-cache search/shoiwsrc omv in debian does not show a source called omv??
19:26.27bozoniusopenmediavault, sorry.  It's a long name, so I abbreviate.
19:27.26gnu_srsapt-cache search openmediavault: <empty>
19:27.39bozoniusI think you need to add a repo
19:27.48bozoniuswhy, are you interested in this project?
19:28.17*** join/#devuan Ipe (~Ipe@n7ivwtvcjdhkkvb8l-2.v6.elisa-mobile.fi)
19:28.42gnu_srsI don't even know what it does. But is is not in debian main contrib or non-free
19:29.04bozoniusit's a nas, kind of like opennas
19:29.15bozoniusopennas is based on berkeley I think
19:29.27bozoniusomv is debian (and now, on devuan)
19:29.50gnu_srsNevertheless, it does not seem to be packaged for debian (and not devuan either)
19:29.52bozoniustry openmediavault.org if you are curious
19:30.07bozoniusas I said, you have to get th package from a diferent repo
19:31.23bozoniusit is generally distributed as an appliance, so you can download the iso from their site and install it, maybe on hardware, maybe in a VM
19:31.36*** join/#devuan Guest1356 (~Guest@83.220.239.219)
19:31.41gnu_srsI still don't understand why you complain about openrc referring to a package not available in debian??
19:31.51bozoniusI didn't
19:32.01bozoniusopenrc has nothing to do with it, actually.
19:32.11bozoniusforget openrc.  That's now a dead issue
19:32.18gnu_srsok, then.
19:32.53bozoniusthe port consists of a working systemctl shim for the omv web app which has embedded systemctl calls
19:33.19bozoniusthe shim approach is an easy fix, and this way, I don't need to support the app itself
19:35.49ibispi_hey guys
19:36.45ibispi_some time today my friend had this problem https://pastebin.com/aQghDr5u and fsmithred said that she installs libgl1-mesa-dri
19:36.57ibispi_but it didn't work, the error is still the same
19:37.04ibispi_why would this be?
19:38.04*** join/#devuan aml (~vu@dslb-088-064-112-082.088.064.pools.vodafone-ip.de)
19:39.07fsmithredibispi_, the error message says some files are missing. Did you check to see if they exist? They should have been provided by the package you installed.
19:39.35bozoniusfsmithred: ldconfig?  I'm not sure about X11 modules, though.
19:39.40ibispi_ok, we'll check if they exist
19:39.43fsmithredhuh?
19:39.51fsmithredno - two .so files
19:40.27bozoniusI thought they might be modules
19:41.50fsmithredi965_dri.so and swrast_dri.so
19:42.08fsmithredapt-file says they are in libgl1-mesa-dri
19:42.20fsmithredbut maybe there's a -dev package for that
19:45.02fsmithredI've got them in /usr/lib/x86_64-linux-gnu/dri/ (not sure where they are in i386)
19:45.16aml/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so can be found
19:45.28amlstill searching for i965_dri.so
19:46.37fsmithredbrb
19:47.22ibispi_another thing, not sure if relevant, but we're running this program via wine, does that mean that we'd have to have this drivers on the wine drive?
19:50.17*** join/#devuan Ryushin (chris@2001:470:4b:38f:777::876c)
19:51.24amlwhen looking into the path /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so, then there is a i965_dri.so file, 6,9mb
19:51.33aml*-swrast_dri.so
19:52.13amlso actually both needed files are present, but Wine does not find i965_dri
19:52.37amlconsole output: libGL error: unable to load driver: i965_dri.so
19:54.45amlNevermind, I will better try a more specific, general-use distro
19:55.14amlbut many thanks for friendly offering your time and expertise, highly appreciated
19:55.27amltrue Linux spirit! :)
19:56.17fsmithreddoes it work in debian?
19:56.27fsmithredif so, it should work in devuan.
19:56.43fsmithredI don't know wine well enough to help with it.
19:56.47amlidk, I will test, and report back in case of success
19:57.47amlthat's fine, thanks you still, fsmithred
19:58.25fsmithredmaybe there's a wine package that needs to be installed.
19:58.42amlyes, I will look into that a bit
19:58.45fsmithredthere's a pretty long list of them. 'aptitude search wine'
19:58.58amlbest would be to get along without Wine
19:59.08fsmithredwhat do you want to do?
19:59.23fsmithred(what windows program do you use?)
19:59.39amlIt's just a hobbyist game engine, Adventure Game Studio
19:59.44amlno big deal really
19:59.49amlit's not mission critically
20:00.06fsmithredgnarface might know something ^^^
20:00.24ibispi_ags is not a problem, we managed to run ags
20:00.39ibispi_but she can't run games compiled with ags > something graphic driver related
20:01.21fsmithredwhat graphics card is it?
20:01.43ibispi_aml^
20:01.56amlsec looking it up
20:02.09fsmithredlspci | grep VGA
20:03.36aml00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
20:03.39aml01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2)
20:03.49amlthx for the commandline snippet
20:04.06amlit's an old IdeaPad
20:04.09fsmithredintel onboard plus separate nvidia card?
20:04.18amlapparently
20:04.21fsmithredand you're using the nvidia?
20:04.35fsmithredwhich one did you plug the monitor into?
20:04.45amluhm, it's a notebook,
20:05.02amlI think it's just the Integrated Graphics Controller one
20:05.58*** join/#devuan ebrasca (~user@host-198.58.elzappero.net)
20:06.07amlfeels sorry to use even more of precious dev time
20:06.33fsmithredI'll bet you're using the nvidia
20:06.53fsmithredand might benefit from using the proprietary driver
20:06.58fsmithredbut that's a guess
20:07.10fsmithreddebian wiki has instructions
20:07.20amlI see, nice, I loook it up
20:07.45amlactually, very nice
20:07.51fsmithredlspci -k
20:08.05fsmithredwill show all your hardware and the drivers being used
20:09.17fsmithred"all" is a slight exaggeration.
20:11.17amlI can post the two relevant entries
20:11.33fsmithredok
20:11.53aml00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
20:11.56amlSubsystem: Lenovo Core Processor Integrated Graphics Controller
20:11.59amlKernel driver in use: i915
20:12.01amlKernel modules: i915
20:12.25amland
20:12.26aml01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2)
20:12.29amlSubsystem: Lenovo GT218M [GeForce 310M]
20:12.32amlKernel driver in use: nouveau
20:12.34amlKernel modules: nouveau
20:13.20fsmithredI don't understand how that works. How many monitor jacks are on this laptop?
20:13.49amllooks with bold eyes
20:14.03fsmithredoh, maybe i do get it
20:14.03amlSorry, I'm also not sure
20:14.23fsmithredintel for the laptop screen, nvidia for external monitor or hdmi
20:14.28fsmithredor some other combination
20:14.43amlyes, that sounds reasonable
20:15.28fsmithredsearch for a debian solution and it will most likely work in devuan
20:15.34amlok, will do
20:15.41fsmithredgood luck
20:15.45amlbut thanks, I learned quite something
20:16.07amlDevuan rocks
20:16.16fsmithred:)
20:18.36*** join/#devuan doverZ (~dover@246.red-88-24-145.staticip.rima-tde.net)
20:37.00*** part/#devuan aml (~vu@dslb-088-064-112-082.088.064.pools.vodafone-ip.de)
20:38.54*** join/#devuan chomwitt (~chomwitt@2a02:587:dc00:2100:900d:7535:965:50f7)
20:45.18*** join/#devuan aitor (~aitor@171.85-84-183.dynamic.clientes.euskaltel.es)
20:45.39aitorfsmithred: live-sdk worked fine
20:45.48fsmithredcool
20:46.03aitori like its design
20:46.37fsmithredI found it pretty easy to figure out what's going on
20:47.04fsmithredand where to change stuff
20:47.51aitorgive me a few minutes, i'm with my father
20:47.59fsmithredok
20:49.31*** join/#devuan Guest1347 (~Guest@83.220.237.73)
21:01.30aitorhi again
21:04.10aitori was using $PWD instead of $R in my script for devuan-installer
21:04.25aitori'll replace it
21:08.35aitortherre are two options in your devuan-live blend: uefi or bios
21:09.17aitorhow can i configure it? setting the mkefi to "yes or "no" in the config file?
21:09.39fsmithredyes
21:10.38fsmithredlooks like you need to set grubversion, too
21:10.45aitorthere is another one: "all"
21:11.04fsmithredshould be same as devuan-live.blend
21:11.40fsmithredyeah, same. There's a test for mkefi yes/no in the xorriso command
21:11.58fsmithredyou don't have to do anything in the .blend file for uefi/bios
21:12.08aitoroh, yes, depending on the value of mkefi, the version of grub will be grub-efi-$arch or grub-pc
21:12.33fsmithredoh did I make that automatic?
21:12.58aitornope
21:13.06fsmithredok, yeah, I'm looking now
21:13.22fsmithredoh, I don't want that to be automatic
21:13.40fsmithredyou can make uefi-bootable iso and have grub-pc installed
21:14.10aitorthen, it has its sense :)
21:14.36aitorfsmithred: it will not be difficult to add a blend for devuan-installer
21:14.37fsmithredyeah, I made refracta isos that way. grub-efi debs are included if you need them. Same iso does both uefi and bios install.
21:14.46fsmithredok
21:15.06fsmithredozi did add it, and it mostly worked. You saw that and fixed some of the issues.
21:16.36aitori can't find code related with d-i in live-sdk, only in devuan-sdk
21:17.01fsmithredit's not in the one I sent you
21:17.07aitorok
21:17.23fsmithredbut I did send you the blend and config for including d-i a few weeks ago
21:18.13aitoryes, i know, but this is my first attempt with live-sdk :(
21:19.33*** join/#devuan alph4 (uid189461@gateway/web/irccloud.com/x-heoipdyqqgvwfbji)
21:19.33aitori downloaded all the .udeb packages from jessie an ascii this afternoon, and i'll build my own repository
21:20.28aitordebmirror will download them from this repo
21:20.48fsmithredright now I'm working on the cli refractainstaller to do uefi installs.
21:21.13fsmithredI think I'm almost done enough to test it.
21:21.28aitorgood!
21:24.31aitori'll also include cpio as a dependency for the customization of the banner and the appearance of d-i
21:24.40aitorand the preseed.cfg file
21:28.13aitorthe banner had been removed from rootskel-gtk
21:28.26EHeMOne thing I very much liked with Debian is https://packages.debian.org/<package> would tell you about the named package.
21:39.30aitorEHeM: really all the features of packages.debian.org..., often i wonder which software they are using for that
21:45.48*** join/#devuan g4570n (~g4570n@host2.190-228-106.telecom.net.ar)
21:47.21aitori'm reading the latest posts in the DNG mailing list
21:47.41aitorthey are talking about a new Gtk theme for ascii
21:48.10aitorhi, g4570n
21:49.47g4570nhi, aitor :)
21:49.54aitorhola
21:50.11g4570nque tal?
21:50.45aitorbien
21:51.59aitorhe visitado hace un rato #devuan-mx, pero sólo estaba tarbz2
21:51.59g4570naitor: I'm playing with the urxvt configuration in devuan
21:52.08aitorgood
21:52.21aitori still didn't try it
21:53.25g4570naitor: I'm already in #devuan-mx, in case you want to speak in Spanish
21:54.08aitorok
21:54.23*** join/#devuan aitor_ (~aitor@171.85-84-183.dynamic.clientes.euskaltel.es)
22:13.26*** join/#devuan dreamer (~henk@unaffiliated/dreamer)
22:16.42*** join/#devuan jord (~jord@h88-150-241-20.host.redstation.co.uk)
22:23.20*** join/#devuan debdog (~debdog@ip-37-201-5-223.hsi13.unitymediagroup.de)
22:25.51gnarfacefsmithred: the only other guess i have about that wine issue aml and ibispi_ were having is maybe they only had the 64-bit versions of the intel opengl/glx driver.  stuff in wine often needs multi-arch enabled and the 32-bit version installed too (of the opengl driver as well as several other key mesa things) i think that can cause the same basic error
22:26.33ibispi_gnarface: she just recently managed to run the program, so it's ok
22:26.36ibispi_<PROTECTED>
22:26.53gnarfaceoh, good to know.  any idea what fixed it?
22:26.58ibispi_idk let me ask her
22:27.13gnarfacesince multi-arch isn't enabled by default on Debian/Devuan it's a common complication
22:28.03gnarfaceit's a common stumbling block for Windows users especially who are surprised to find out Microsoft blithely ships 32-bit software with all their fancy 64-bit computers
22:28.17fsmithredthey were initially looking for a 32-bit lib
22:28.36gnarfacesome Wine environments need both to work properly (also Steam for Linux)
22:30.02ibispi_she says: <aml> I updated the repos to unstable, and installed practically all packages anew
22:30.21fsmithredoh
22:30.22gnarfaceeh, well that will do it
22:30.38fsmithredshe has only ceres in sources now?
22:32.04ibispi_i think so
22:32.22gnarfaceibispi_: we're leery of magic fixes.  there's a lot of fixes that can make bigger messes in the long run
22:32.41ibispi_ok
22:35.24fsmithredupgrade from jessie to ascii and ceres is not smooth and easy right now. She may have a mix of stable/testing/unstable
22:35.57fsmithredjust testing/unstable mix is ok, but with stable in there could be trouble
22:36.27gnarfacethere's also a strong influence in times like these to "just grab the driver package from [some ubuntu 3rd party PPA]" which is almost always a catastrophe in the making during the next attempt at a clean upgrade
22:36.42EHeMaitor: Given how those features have been there 15-20+ years, it is likely something pretty simple, just need to figure out where the scripts are and grab them.
22:37.47fsmithredcheck jessie-backports if newer versions are needed
22:43.02EHeMI'm sure there is a good reason why using "stable" in /etc/apt/sources.list is considered deprecated, but at the same time it is quite handy; using "stable" means you quickly become aware of when updates are available, and means you don't have to update the file when you upgrade.
22:44.46aitorEHeM, sorry, i've been kidnapped in #devuan-mx, lol
22:45.41*** join/#devuan matlock (~matlock@user-24-214-145-29.knology.net)
22:45.58gnarfaceEHeM: the issue with that is, it causes a basic race condition.  when stable is changed to a new release, some of the packages in that release may have only been tested with the most recent versions of packages from the previous stable, which you may have skipped accidentally if you didn't update&upgrade, and the preinst/postinst hooks may possibly make invalid assumptions - i know it seems like a slim chance but all the
22:45.58gnarfacepackage scripts are a very fragile web of carefully tested behaviors at corresponding release versions, only to the degree they're expected to really overlap feasibly...
22:46.34gnarfaceEHeM: so basically, if you update& upgrade fast enough, with luck, using "stable" instead of the release name keyword will usually work, but it's advised against because it's known to break upgrades in ways that can't be feasibly predicted or tested for
22:47.22gnarfaceEHeM: (and frankly, in practice, succeeding at this reasonably safely would require running "apt-get update" more often than is really advised)
22:47.26koollmanI never use stable, controlling when you want to dist-upgrade is important
22:48.07koollmanand the typical step before dist-upgrade is 'update + upgrade' for the oldstable
22:48.29koollmanwhich would not work if you use stable. the upgrade would be the beginning of almost a dist-upgrade :)
22:48.53EHeMgnarface: In order to miss a release like that you'd have to update less than once a year; which is insane given the need for security updates.
22:48.53koollmannow, if you upgrade every day it does not matter. but it's rarely the case
22:49.13koollmanEHeM: there could be a bugfix at the worst possible time :)
22:49.37koollmanthere are publications of packages more than once a year :)
22:49.47gnarfacebozonius: (sorry to hear you gave up on it, but i guess if it works right using sysv-rc but not openrc that's pretty damning evidence in favor of it being a problem with openrc)
22:50.22EHeMkoollman: I've noticed.
22:50.52gnarfacebozonius: (i still feel someone needs to protect and preserve basic LSB header behavior as a neutral third party before this becomes a tug-of-war standard)
22:50.52koollmanI'm actually reading documentations for aptly right now, to have more controls about when packages are really upgraded in my environment :)
22:51.40koollmanwith the idea of upgrading always from my local mirrors/repo, and using snapshots to make sure changes happen in a controlled way, and are first tested on a less important subset of servers
22:51.46EHeMProblem is while breaking usage of "stable" protects a few people who update/upgrade less than once a year, it is a distinct pain for people who want to avoid modifying sources.list and *do* bother to keep up to date.
22:52.41gnarfaceEHeM: you're free to do as you please, i'm just telling you why we all learned to stop doing it that way
22:53.00gnarfaceyou practically have to update&upgrade twice a day at minimum
22:53.28gnarfaceand even then it doesn't completely reduce the chances of bad behavior if you don't pay close attention to the package versions coming in so that you notice when they change releases on you
22:53.43EHeMwonders if/when he will get around to implementing the magical include directive for init.
22:53.56koollmanand even if you keep up to date, maybe you want ot read the release not before your morning upgrade that will break stuff :)
22:54.03koollman*release notes
22:54.05gnarfacebut you're right, it's far more of a risk for people who just forget to upgrade and only do it once a year or so
22:54.26koollman"oh, well, apache is upgraded and now it will not start. have fun" :)
22:54.51EHeMIs bad behavior for some people reason to *break* a behavior valued by other people?
22:54.53koollman(and that was during a controlled upgrade, with absolute latest version before :) )
22:58.32gnarfaceEHeM: don't mistake us for people who can do anything about it.  we didn't build the mountain.  think of us more like guides just trying to keep less travellers from dying on the way to the top of it.
22:59.01EHeMAnother benefit is you don't need to know magic keywords (release names) when you decide to go ahead and upgrade.
22:59.26EHeMgnarface: I was hoping you were in position to pass along opinions.   :-)
23:00.46gnarfacei have opinions but they're not worth anything if people don't heed them
23:01.32DocScrutinizer05build a package "auto-upgrade-stable"!
23:02.04gnu_srsgnarface: A package not even packaged by debian is not a reason to complain on openrc. You have to provide sane init scripts for every new package.
23:02.34EHeMseems to recall seeing a package along the lines of a cron `auto-upgrade-stable`.
23:03.30gnarfacegnu_srs: i brought up the possibility it was a problem with his package script several times.  he knew it was a possibility.  the problem was that he became frustrated trying to find a behavior that made both inits happy, when ostensibly they should both have been treating those LSB headers the same exact way
23:04.43gnarfacegnu_srs: this does suggest there's a bigger problem than just the pedigree of his package.
23:06.57gnarfacegnu_srs: if it was just something he pulled out of his ass that would be one thing, but he claimed it was a package that was previously in debian working fine, and it's default init script indeed worked fine with sysv but not openrc, which i realize is just hearsay and circumstantial evidence as far as i know, but it does further highlight potential problems if Devuan were to blindly switch the default init to openrc
23:06.57gnarfaceunder the *mistaken* assumption they work the same where it matters
23:07.46gnarfacegnu_srs: try to see the big picture before you just give the form-letter "not made here" response
23:09.48gnarfacei'm sorry, that came out more hostile than i intended it to sound, but this is a serious issue and it shouldn't be trivialized
23:10.44*** join/#devuan DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
23:10.50gnarfacenothing would make Debian fanatics more smug right now than to see our next release faceplant due to an ill-conceived init system switch
23:11.00DocScrutinizer05fails to understand if sysvinit scripts are even supposed to work exactly same in unmodified version under openrc
23:11.45gnu_srsThe more people testing openrc, the better of course. I really hope the people authorized to build packages fixes the problems to make it installable.
23:11.45gnarfaceDocScrutinizer05: also hearsay, i admit.  maybe that was never openrc's intent.  but if so, then the openrc advocates over here in OUR camp need to get aware of that fast.
23:13.11gnu_srsUntil a proper bug on openrc has been filed, nothing can be acted on :(
23:14.06*** join/#devuan Drugo (~Drugo@62-11-1-95.dialup.tiscali.it)
23:14.46EHeMSo looks like stable-backports and stable-updates work, but stable-security is broken.
23:14.47DocScrutinizer05I'd think there mist be a manpage or doc or at least reference implementation of a canonical openrc init script, right?
23:14.53DocScrutinizer05must*
23:16.29DocScrutinizer05and iirc/aiui the real problem was with insserv, or am I mistaken?
23:16.34gnu_srsCurrently there is a Debian patch making openrc following the same rules as sysv-rc: Mainly LSB scripts.
23:16.58koollmanDocScrutinizer05: https://wiki.debian.org/Debate/initsystem/openrc is probably a decent starting point (since it was written as a comparison to systemd and sysvinit)
23:17.26gnu_srsRewriting all scripts according to gentoo standard is a major effort.
23:17.56gnu_srsYou're welcome to provide patches :D
23:18.23DocScrutinizer05muses about a generic "init script crosscompiler"
23:19.01koollmanDocScrutinizer05: https://github.com/jordansissel/pleaserun :)
23:19.01DocScrutinizer05I mean the info in there is often identical, just different representatiom. Or at very least one a subset of the other
23:19.51DocScrutinizer05hey nice :-)
23:21.41*** join/#devuan LEX0 (~lexo@gateway/tor-sasl/lexomx)
23:23.14gnarfaceDocScrutinizer05: it seemed at least at face value to me to be the type of issue where parties maintaining omv and insserv were gonna argue and both blame the other party, and the outcome ends up accidentally deciding whether historical precedent has any weight on LSB header parsing behavior going forward
23:24.12gnarfacemy argument would by default be in favor of historical precedent rather than letting Gentoo decide standards on ANYTHING whatsoever
23:24.34gnarfacebut i have absolutely no authority in the matter so it's just another opinion that only carries as much weight as the people willing to carry it for me
23:26.06gnarfacebut i think bozonius's basic issue in bringing it up is the same as mine; it seems like the truth of this matter may invalidate a lot of misplaced loyalty in openrc
23:26.17gnarfaceso i think it's an important matter for Devuan to discuss officially
23:26.28gnarfacelight needs to be shined on THESE types of issues early rather than late
23:26.53gnarfacethe fix would be easy
23:26.59gnarfaceagreeing on where to fix it might not be
23:28.31*** join/#devuan matlock (~matlock@2600:1005:b11d:7ba9:4875:a01e:9f2a:d476)
23:28.31gnarfacebut yea, i think everyone should be able to easily see the sense in NOT forking ALL the init scripts over stupid stuff like this
23:30.13*** join/#devuan uidzer0 (~uidzer0@2604:180:2:130d::dead:beef)
23:45.43bozoniusgnarface:  +1
23:46.34bozoniusI am actually relieved (now) that I chose to unwork openrc from my port.   Partly to avoid lack of standardization with Devuan, but also to avoid the support pitfalls we discussed at length prior
23:47.21bozoniusthe sysv-rc/sysv-init port (standard Devuan, i.e.) is going smoothly.  In fact, rewriting the shim for systemctl did not take long at all.
23:47.56bozoniusI'm even thinking of building a couple of dummy packages for sytemctl so that apt-get won't barf  on install.
23:48.23bozoniusRather than trying to maintain a separate omv package for Devuan and other sysv-rc based systems
23:56.40bozoniusthe debate page on openrc is more than 3 1/2 years old.  The 3 people listed at the bottom:  Are those devuan devs or maints?   There is no attribution to them there.
23:56.54bozonius(I think the page should be updated to point out who these folks are.)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.