[00:34] <ruben23> hi guys , i have issue with my ubuntu server 12.04 LTS, when i boot it wont directly boot instead i need to select first then on the booting process and loading it just freezed on the boot process part ---->http://s17.postimg.org/6k37qen7j/20141119_081525.jpg
[00:38] <ruben23> any idea guys..?
[03:18] <ojeq> @find ubuntu 12 lts
[03:18] <ojeq> !ping me
[08:18] <lordievader> Good morning.
[08:42] <blackyboy> In our Production server i can't login, Its a Ubuntu VM
[08:42] <blackyboy> While i login its login and immediately log-outs
[08:43] <lordievader> blackyboy: Tty or a gui?
[08:43] <blackyboy> What may be the issue, Even i have tried recovery mode its giving some error
[08:43] <blackyboy> lordievader: no its CLI server
[08:43] <lordievader> "its giving some error" what error?
[08:44] <blackyboy> wait 1 min sir let me take the error a screenshot
[08:44] <lordievader> !screenshot
[08:48] <blackyboy> lordievader: http://i57.tinypic.com/2drvt6o.png
[08:49] <blackyboy> imgur site not working now. so uploaded in tinypic
[08:50] <lordievader> blackyboy: Do you have a backup?
[08:50] <blackyboy> yes i have a backup
[08:51] <blackyboy> But now i have copied this vm to other server
[08:51] <lordievader> blackyboy: Good :) Grab a live-cd and check the drive. It looks to me like the disk is a bit broken (or the fs on it ofcourse).
[08:52] <blackyboy> oh ok let me try sir thankyou
[09:23] <blackyboy> lordievader: i have booted using a live cd, while i try to edit my network interface the file was reonly even i have executed this command , mount -o remount rw / and / have been mounted so i can't run fsck -y -C too
[09:23] <blackyboy> Any idea ?
[09:24] <lordievader> blackyboy: Err, you don't need to mount the install's /, so you can fsck it.
[09:26] <blackyboy> lordievader: i got these following Device to use as root file system menu
[09:26] <blackyboy> /dev/sda1
[09:26] <blackyboy> /dev/sda5
[09:26] <blackyboy> /dev/arrweb-vg/root
[09:27] <blackyboy> /dev/arwebs-vg/swap
[09:27] <lordievader> !paste
[09:27] <blackyboy> assemble RAID Array
[09:28] <blackyboy> lordievader: http://i.imgur.com/BgdmAc1.png
[09:29] <blackyboy> after choosing do not use root im getting this http://i.imgur.com/FCg4e6y.png
[09:30] <lordievader> Yeah, I suppose that first option is okay. What you want is a shell in an environment where you can check the filesystem on the harddrive.
[09:32] <blackyboy> yes i have choosed it and which executing the command fsck.ext4 /dev/sda5 its says cannot continue aborting
[09:32] <blackyboy> is in use
[09:33] <lordievader> blackyboy: You want /dev/arrweb-vg/root
[10:39] <caribou> rbasak: is the cloud-guest-utils package systematically in our cloud images ?
[10:39] <caribou> well rbasak or anyone who can answer
[11:09] <soren> caribou: cloud-guest-utils is part of the cloud-image task, so yes.
[11:09] <caribou> soren: thanks
[11:12] <soren> caribou: Since August 2013: http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.vivid/revision/2156
[11:45] <blackyboy> lordievader: can't fit :(
[11:45] <blackyboy> Three vms recoverd just i have moved those vm to other host
[11:45] <lordievader> blackyboy: Can't fit? Can't fit what?
[11:46] <blackyboy> using live cd you told me to fix the filesystem
[11:46] <lordievader> blackyboy: Yes...
[11:46] <blackyboy> when ever using fsck -y -C it saying resource busy
[11:49] <lordievader> blackyboy: What is the exact command you are using?
[11:50] <blackyboy> lordievader: now i ran the this command fsck.ext4 /dev/arrwebs--vg-root and it said clean
[11:51] <lordievader> blackyboy: Okay that is good :)
[11:52] <blackyboy> let me restart the vm and check whether  its work now
[11:54] <blackyboy> oh no
[11:54] <blackyboy> my login screen came, while entering the username and password its just kicking me out
[12:16] <neurotus> 2014 Nov 19 14:15:51 vps74689 PAM service(sshd) ignoring max retries; 6 > 3
[12:16] <neurotus> what is this ?
[12:16] <neurotus> keeps popping up on terminal now constantly
[12:16] <Vladislav> exit
[12:16] <Vladislav> quit
[12:16] <Vladislav> quit
[12:16] <neurotus> between few seconds
[12:17] <neurotus> someone bruteforcing ?
[12:17] <lordievader> neurotus: Is your sshd accessible from everywhere?
[12:17] <neurotus> lordievader: yes
[12:17] <lordievader> Then likely, yes.
[12:17] <neurotus> it just started. have been having this server for years.
[12:18] <neurotus> well all idents are not usernames
[12:18] <lordievader> Then you've had them for years, install fail2ban.
[12:19] <neurotus> some one is trying to root-login
[12:19] <neurotus> from <IP_ADDRESS>
[12:20] <neurotus> gonna disable it
[12:20] <lordievader> That is the most common username ;)
[12:20] <neurotus> okay, knows my usenames
[12:20] <neurotus> which it cant
[12:20] <neurotus> because the idents are different than usernames
[12:21] <neurotus> no. that was just cron-job
[12:21] <neurotus> panic just made paranoid
[12:21] <lordievader> As I said, install fail2ban.
[12:23] <neurotus> i just made root-login disabled
[12:23] <neurotus> lordievader: gonna do it
[12:23] <mardraum> it is by default anyway.
[12:23] <neurotus> wasnt able to read clearly
[12:25] <neurotus> 14:18:40 user=root authentication failure
[12:25] <neurotus> havent seen anything after that in auth.log
[12:26] <neurotus> all logged users are from known ip's
[12:26] <neurotus> so everything is fine
[12:26] <neurotus> fail2ban log somewhere ?
[12:27] <neurotus> 2014-11-19 14:25:28,483 fail2ban.actions: WARNING [ssh] Ban <IP_ADDRESS>
[12:27] <neurotus> nice
[12:27] <neurotus> banned
[12:27] <lordievader> neurotus: Err, you can also let it email you.
[12:27] <lordievader> It can include whois info too.
[12:28] <neurotus> i prefer tail -f /var/log/auth.log
[12:28] <neurotus> one terminal for that :)
[12:28] <neurotus> always ready
[12:28] <neurotus> retired so have the time
[12:30] <neurotus> that ip-range is from china
[12:30] <neurotus> is there a tor-filter ?
[12:30] <neurotus> and known public vnp's :)
[12:31] <neurotus> would like to disable those
[12:31] <lordievader> Firewall the subnet ;)
[12:32] <neurotus> fail2ban already made fail2ban-ssh chain
[12:33] <neurotus> so its enough for me
[12:33] <neurotus> bruteforcing root :P
[12:33] <neurotus> its possible but needs alot of luck :)
[12:33] <neurotus> in theory
[12:35] <phix> hi
[12:35] <lordievader> o/
[12:36] <phix> \o
[12:37] <phix> what's up?
[12:41] <phix> so how about that open source, pretty left wing right?
[14:14] <nunizacu> bttter turn off root loogin
[14:14] <nunizacu> and change shell to /bin/true
[14:15] <nunizacu> just in case
[14:16] <nunizacu> and use geoip to block all cn
[15:24] <yossarianuk> hi - is anyone aware how long packages are supported for from the mysql.com apt repo ?
[15:24] <yossarianuk> i.e http://dev.mysql.com/downloads/repo/apt/
[15:25] <lordievader> yossarianuk: That is up to Oracle.
[15:27] <yossarianuk> lordievader: thanks - I guess the version in the normal ubuntu repo is guaranteed till 2019 (the 14.04 packages anyway)
[16:21] <yossarianuk> if I am upgrading from Mysql 5.0 -> 5.6 - should I upgrade from 5.1 -> 5.5 -> 5.6 or can a just from 5.0 -> 5,6 ?
[16:21] <lordievader> !info mysql-server
[16:22] <lordievader> yossarianuk: Err, 5.6?
[16:24] <yossarianuk> lordievader: ubuntu 14.04 has in its normal repo MySQL 5.5/MySQL5.6 + mariadb 5.5
[16:26] <yossarianuk> i.e - http://packages.ubuntu.com/trusty/mysql-server-5.6  - http://packages.ubuntu.com/trusty/mysql-server
[16:27] <lordievader> !info mysql-server trusty
[16:27] <lordievader> !info mysql-server-5.6 trusty
[16:27] <lordievader> Ah, check.
[16:28] <lordievader> yossarianuk: http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html
[16:40] <yossarianuk> lordievader: thank you.
[16:45] <yossarianuk> and by all accounts I should be able to go from 5.0 -> 5.6 ...
[17:02] <jvwjgames> hi
[17:03] <jvwjgames> i need help
[17:03] <jvwjgames> I did a distribution upgrade from 13.10 to 14.04
[17:03] <jvwjgames> and my websites that used to live at /var/www is gone
[17:03] <jvwjgames> and now 14.04 uses /var/www/html
[17:04] <jvwjgames> how do i switch it back to /var/www
[17:04] <jvwjgames> or migrate my site to /vaw/www/html
[17:04] <nunizacu> ln -s
[17:04] <nunizacu> or edit apache2.conf
[17:05] <jvwjgames> ok
[17:05] <nunizacu> 000-default in enabled sites maybe
[17:05] <jvwjgames> just wondering
[17:05] <jvwjgames> whitch is better ln -s symlinking or editing apahe2.conf
[17:06] <nunizacu> whatever you like
[17:07] <nunizacu> but i think path is in enables-sites/000-*
[17:07] <lordievader> jvwjgames: http://httpd.apache.org/docs/2.4/upgrading.html
[17:08] <jvwjgames> found it
[17:08] <jvwjgames> 000-default.conf reads DocumentRoot /var/www/html
[17:12] <jvwjgames> :)
[17:13] <jvwjgames> i fixed it yay thanks guys
[17:14] <jvwjgames> i don't have ssl on apache
[17:14] <jvwjgames> how do i enable my website for ssl
[17:14] <jvwjgames> cause i have an ssl cert
[17:15] <lordievader> jvwjgames: https://www.digitalocean.com/community/tutorials/how-to-create-a-ssl-certificate-on-apache-for-ubuntu-14-04
[17:17] <lordievader> jvwjgames: You can skip step two ;)
[17:17] <jrwren> jvwjgames: didn't debconf ask you about overwriting those files in /etc/apache2 ?
[17:19] <jvwjgames> yes
[17:19] <jcastro> utlemming, hey the vagrant boxes are 14.04, not 14.04.1, who do I ping?
[17:20] <jvwjgames> i fixed the problems thanks everyone
[17:20] <jvwjgames> my website and ssl are fixed
[17:22] <jvwjgames> why must updates change everything
[17:22] <jvwjgames> one last problem to be fixed
[17:22] <jvwjgames> url rewrite is deactivated
[17:22] <jvwjgames> i need it other wise my websites goes no where
[17:23] <qwaserdf> sudo a2enmod rewrite
[17:23] <lordievader> jvwjgames: You upgraded from 13.10 to 14.04, change should be expected.
[17:24] <jvwjgames> Module rewrite already enabled
[17:24] <jvwjgames> but still not working
[17:24] <qwaserdf> sudi service apache2 restart
[17:24] <qwaserdf> sudo*
[17:26] <jvwjgames> you guys can check for your self http://jvwjgames.net
[17:26] <jrwren> jvwjgames: next time when debconf asks, just say "no" to replacing config files :)
[17:26] <jvwjgames> ok
[17:27] <jrwren> jvwjgames: the conf files will still be written along side the functioning conf files, but with a dpkg-dist file extension. Then you can diff and merge as you see fit.
[17:27] <jrwren> with zero downtime.
[17:27] <jvwjgames> ok
[17:28] <qwaserdf> https works I guess
[17:31] <jvwjgames> should apache have been updated to latest version when i updated to 14.04
[17:31] <jvwjgames> cause this site is reporting that i have outdated apache software http://sitecheck.sucuri.net/results/jvwjgames.net/
[17:35] <lordievader> !info apache2 trusty
[17:35] <lordievader> jvwjgames: Do you have 2.4.7?
[17:35] <jvwjgames> yes
[17:36] <jvwjgames> but just to make sure how do i check
[17:36] <lordievader> jvwjgames: apt-cache policy apache2
[17:36] <jvwjgames> Installed: 2.4.7-1ubuntu4.1
[17:36] <jvwjgames>   Candidate: 2.4.7-1ubuntu4.1
[17:37] <jrwren> jvwjgames: that site is using FUD to sell you firewalls.
[17:38] <jvwjgames> hmm
[17:38] <jvwjgames> i wish the websit web of tust didn't use that site then
[17:39] <jvwjgames> cause my site is being evaluwated by a web of trust site
[17:39] <jvwjgames> and this is what they had to say
[17:40] <jvwjgames> https://www.mywot.com/en/forum/51594-jvwjgames-net
[17:43] <jrwren> jvwjgames: odds are that they are reading Server line out of HTTP headers.  Really sad that a 3rd party is using that to verify something.
[17:51] <patdk-wk> more sad they are using it to *sell* something :)
[17:51] <jrwren> patdk-wk: That is all it is, is a sales tactic.
[17:51] <jrwren> "Look, you aren't secure. Buy our magic pixie dust."
[17:52] <jvwjgames> lol
[17:52] <jvwjgames> good one
[17:52] <jrwren> my previous job was in the security industry. I quickly learned that it is a racket.
[17:52] <patdk-wk> I would guess restricting version info works
[17:52] <patdk-wk> cause it doesn't detect mine is HORRIBLE old :)
[17:53] <patdk-wk> jrwren, worst yet is, 99% of security companies, distribute their software over http, without protection
[17:54] <jrwren> patdk-wk: we did not. :)  We used SSL and even used client certificate authentication.
[17:55] <jvwjgames> nice
[17:55] <jvwjgames> i still need my rewrite to work otherwise my site is broken
[17:55] <patdk-wk> heh?
[17:55] <patdk-wk> what rewrite?
[17:57] <jrwren> jvwjgames: oh, your old conf files should be there with a .dpkg-old extension if you would like to compare them or put them back.
[18:17] <mgz> smoser: review please! https://code.launchpad.net/~gz/simplestreams/setup_user_install/+merge/242248
[18:22] <smoser> mgz, done
[18:23] <mgz> smoser: ta!
[18:31] <jvwjgames> jrwren: where is the old conf located
[18:33] <jrwren> jvwjgames: apache config is in many files. find /etc/apache2 -name '*.dpkg-old'
[18:38] <jvwjgames> ok irestored old config
[18:38] <jvwjgames> but apache fails to start
[18:38] <jvwjgames> [Wed Nov 19 11:37:17.907774 2014] [ssl:emerg] [pid 10365] AH01892: Illegal attempt to re-initialise SSL for server (SSLEngine On should go in the VirtualHost, not in global scope.)
[18:39] <jvwjgames> i have it in virtual host
[18:52] <jvwjgames> nevermind i fixed it
[18:52] <jvwjgames> ewrite is still deactivated
[18:54] <teward> jvwjgames: you might have to turn on the rewrite mod...  a2enmod rewrite
[19:07] <jvwjgames> still not working
[19:07] <jrwren> confirm that rewriteengine on is where you think it should be?
[19:07] <jrwren> grep -iR rewriteengine /etc/apache2/
[19:09] <jvwjgames> error
[19:09] <jvwjgames> when typing that command
[19:09] <jvwjgames> but no listings
[19:11] <jvwjgames> jrwren: any ideas
[19:14] <jrwren> jvwjgames: i don't know about the error. If you get zero results, then you must enable turn on the rewrite engine somewhere.
[19:14] <jvwjgames> ok
[20:00] <jvwjgames> ok i got rewrite working parshaly
[20:01] <jvwjgames> i edited the file apache2.conf and added server tokens prod and serversigniture off but it is still there
[20:01] <jvwjgames> and yes i did a restart and reload of apache
[20:04] <jrwren> jvwjgames: i just changed mine and it works for me. You must not be editing the correct files or correct virtual hosts.
[20:36] <miccheck> hi. i'm new to linux and recently setup a vps running ubuntu to host a web blog. i'm running UFW. is that good enough for a simple blog server? i also don't have a IDS installed. is that necessary?
[20:37] <sarnold> miccheck: ufw is good, there's no real need for an IDS though it never hurts to keep an eye on your logs
[20:37] <lordievader> miccheck: Do you have an sshd running on it? If so fail2ban might be a nice addition.
[20:38] <miccheck> ok, cool. yeah, i setup fail2ban as well.
[20:38] <teward> lordievader: he could also restrict SSH to his IPs, `iptables -A INPUT -p tcp --dport 22 -s HISNET -j ACCEPT` or something, but still.
[20:38] <teward> only owrks if you have a static set of IPs.
[20:38] <teward> (not the case in most instances)
[20:38] <miccheck> i'm a bit nervous maintaining my own vps without knowing much about it, but sounds like i'm doing some of the right things
[20:39] <lordievader> teward: True, but with ssh I like to apply blacklisting as I use a few different dhcp addresses in different locations.
[20:39] <lordievader> miccheck: One learns it somewhere ;)
[20:40] <teward> lordievader: indeed.  'Course, in my case, my VPSes are key-auth-only which helps a bit
[20:40] <miccheck> yep, in the process now! coming along. i'm really digging linux and the command line stuff, although not sure what i'm doing completely yet
[20:42] <Kartagis> teward: speaking of which, when do we need -m tcp in iptables?
[20:42] <teward> Kartagis: `-p tcp` implies `-m tcp` i believe
[20:44] <Kartagis> I've got iptables -A INPUT -s my.ip.add.ress/32 -p tcp -m tcp --dport 8983 -j ACCEPT. is -m tcp extra here?
[20:44] <gbkersey> Kartagis: no it is not.
[20:45] <teward> gbkersey: it's not extra, but it's implied as part of `-p tcp` - for instance, this rule I added with `iptables -A INPUT -p tcp --dport 18333 -j ACCEPT`: A INPUT -p tcp -m tcp --dport 18333 -j ACCEPT
[20:45] <miccheck> here's another one. suppose i want to write a script to copy files from my mac to my ubuntu vps via ssh. how is that done given that ssh will ask for a password when running the ssh user@vpsIP part?
[20:45] <teward> at least, afaik it's implied by -p tcp
[20:45] <Kartagis> man says -m is match
[20:46] <miccheck> i've tried to do it manually via scp and sftp and keep getting permission denied errors when trying to copy directly into my site directory
[20:46] <miccheck> i think i've got the wrong permissions
[20:47] <gbkersey> teward: you are correct, it is implied...
[20:47] <sarnold> miccheck: feel free to chown -R your site's htdocs directory to your user account, just be sure to keep the permissions such that the web server can read the files
[20:47] <teward> Kartagis: you're right, it does mean match.  However, in the case of -p tcp, -m tcp is implied.  it's not extra, but it is implied with just `-p tcp`
[20:47] <teward> gbkersey: right, that's what I thought :)
[20:48] <Kartagis> k
[20:48] <teward> TBH i'm far from an iptables expert, my firewall on my networks is a pfSense appliance, the only system with its own iptables ruleset is this one laptop I take offsite
[20:48] <teward> but for my uses i know what i need to know :)
[20:48] <miccheck> ok, thanks. it's running nginx, so different directory structure, but i think same process
[20:49] <miccheck> what about for running a copy script that uses ssh, will the terminal just ask for the vps login when it gets to that part?
[20:50] <sarnold> miccheck: it's worth setting up ssh keys and running a local ssh agent so you don't have to supply login passwords all the time
[20:50] <teward> ^
[20:51] <miccheck> hmm, i thought i did that and that's what allowed me to ssh into the vps in the first place, but it does still ask for a password. hmm.
[21:37] <K4k> The new way of configuring networks in 14.04 really confuses me... I've got a if-up.d config that sets the static route for eth0 but with I ifup eth0 && ifdown eth0 I receive and error 2 on that file. If I try to run the ip route add command manually I receive "RTNETLINK answers: File exists" but there is no route currently set for eth0
[21:37] <K4k> What am I doing wrong here?
[21:40] <rbasak> Details please. What's the error exactly? What's the command that fails exactly? etc.
[21:41] <K4k> The whole error is "RTNETLINK answers: File exists" The command inside the if $IFACE = "eth0" in the if-up.d file is `ip route add <IP_ADDRESS>/<IP_ADDRESS> via <IP_ADDRESS> dev eth0`
[21:42] <K4k> when the if-up.d script runs as part of `ifup eth0` I receive a return code 2
[21:43] <K4k> which I assume is because `ip route add ...` fails
[21:44] <rbasak> Your route to <IP_ADDRESS>/24 is via <IP_ADDRESS>? How do you expect that to work?
[21:44] <rbasak> Are you sure you got that right?
[21:45] <K4k> er... not 100% sure
[21:45] <rbasak> That's a recursive route.
[21:45] <rbasak> How do you get to <IP_ADDRESS>?
[21:45] <K4k> that's the gateway for the network this system is on
[21:46] <K4k> but because of the puppet module I'm using, I can't set a gateway in /etc/network/interfaces
[21:46] <K4k> I have to set it in as a route
[21:46] <rbasak> Maybe you want a default route.
[21:46] <K4k> which I thought was kind of dumb but I'm trying to go with it
[21:46] <rbasak> What you're asking it for makes no sense.
[21:47] <K4k> I didn't think so but that follows the example on the module README
[21:47] <rbasak> Probably best to fix your puppet module though.
[21:47] <rbasak> Sounds like the README is wrong then.
[21:47] <K4k> :) glad we've come to the same conclusion about that
[21:48] <K4k> now that I know how it's translating what I put into the class into the if-up.d script I think I can make it work. Thanks!
[21:52] <jvwjgames> is there a way for a device to emit a cetain hostname


[00:22] <infinity> tron103: Define "the latest kernel"?
[01:16] <Fudge> thanks cyphermox  and cjwatson
[01:23] <cyphermox> Fudge: np. lemme see if I can find something out quick
[02:16] <Fudge> :)
[02:52] <cyphermox> there may be a trick, by enabling espeakup as a module early on (you'd need to add things to the command line, or roll your own d-i image)
[02:52] <cyphermox> but I found some hints that it might be broken because of kernel changes
[03:19] <cyphermox> Fudge: so, the additional command-line entry you'd probably need would be "modules=espeakup-udeb", but it's not shipped on the server CD, so in a current case, at best you'd have to get online somehow through the menus before it would download the udeb
[03:20] <cyphermox> so, the answer is most likely that if you want to make this work, for the time being it means building your own ISO if you want espeakup-udeb to be available
[03:21] <cyphermox> (or rebuild d-i, making it included in the mini.iso, but that means you'll need to bump the disk size it allows
[03:21]  * cyphermox goes to bed
[03:23] <tron103> I've installed ubuntu-server 14.04 with the 3.16.0-30-generic kernel and a custom network driver that is needed. Is there a way to build an initrd/kernel combo for this version? The downloaded netboot installer is an older version of the kernel and won't accept my kernel modules.
[03:24] <Fudge> cyphermox:  that is very helpful mate, thank you so much
[11:20] <infinity> tron103: There's no way the netboot installer uses an older kernel than that (In fact, I'm looking right now, and it's 3.16.0-45, currently).
[11:21] <infinity> tron103: You're building for a kernel that's 7 months old.
[16:19] <tron103> Infinity: My cd ISO installed ubuntu-server 14.04 is at 3.16.0-30-generic, the real problem is that the netinstaller initrd is version 3.13.0-24-generic at http://us.archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/netboot.tar.gz
[16:20] <cjwatson> you want to use trusty-updates not trusty
[16:20] <tron103> lol
[16:20] <tron103> why is that?
[16:20] <cjwatson> trusty is the version released with 14.04 on release day, it doesn't get updated
[16:20] <cjwatson> just like the archives, post-release updates go in trusty-updates
[16:22] <tron103> thank you cj, ill keep that in mind
[16:23] <tron103> I ended up finding the kernel-version specific modules and can now bring up the inifiniband interface, but it won't get dhcp for some reason. seems to only see ipv6
[16:24] <tron103> I could try and rebuild everything with http://us.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz
[16:30] <tron103> wow... the current netboot is at 3.13.0-61-generc
[16:30] <tron103> grrr
[16:30] <tron103> still smaller than my install version
[16:31] <infinity> tron103: There are netboot directories for each of 3.13, 3.16, and 3.19
[16:31] <infinity> tron103: http://cdimage.ubuntu.com/netboot/trusty/
[16:32] <tron103> thank you a bunch for that
[16:32] <tron103> so I have to look at cdimage instead of the archive
[16:33] <infinity> tron103: That page links to the archive, it's just nicer than remembering the deep links.
[16:34] <tron103> ah. its something called "vivid"... not just trusty
[16:34] <infinity> tron103: 3.16 would be lts-utopic, actually, not lts-vivid.
[16:35] <tron103> right you are :)
[16:41] <tron103> nice. its 3.16.0-45-generic.
[16:42] <cjwatson> Not sure the lts-utopic kernel is still supported though, since utopic isn't
[16:43] <tron103> hmm now i wonder if the kernel modules from  3.16.0-30-generic will insert into 3.16.0-45-generic
[16:44] <cjwatson> No
[16:44] <cjwatson> At least I doubt it, the point of changing the ABI number is that the ABI changed
[16:44] <infinity> lts-utopic is supported until 3mo after 16.04 comes out.
[16:44] <cjwatson> infinity: oh really?  ok
[16:45] <infinity> cjwatson: Says so on the handy cdimage/netboot page. :)
[16:45] <infinity> So it must be true, cause I wrote it.
[16:45] <infinity> *handwave*
[16:45] <cjwatson> fair enough
[16:46] <infinity> cjwatson: But, basically, we support all the lts-N kernels until the .5 point release, where lts-next-lts becomes the only one supported with a highly-encouraged and annoying upgrade message.
[16:59] <tron103> thats a nope to inserting 3.16.0-30-generic modules into 3.16.0-45-generic
[17:00] <tron103> so my secret way of finding my compiled modules is to google: site:http://packages.ubuntu.com/ ib_addr.ko 3.13.0-24-generic
[17:01] <infinity> tron103: Err, wait.  What?  ib_addr should be included already, why do you need to compile your own?
[17:02] <tron103> ib_addr is not included in any of the netboot initrds ive looked at
[17:03] <tron103> and im not compiling them though, someone else helpfully did it and put it up on packages.ubuntu.com
[17:04] <tron103> I'm merely trying to add them into my netboot so i can bring up ib0 and dhcp it.
[17:05] <infinity> tron103: That "someone else" is us. :P
[17:06] <tron103> <3
[17:06] <infinity> tron103: But indeed, infiniband stuff seems to be missing from d-i.  Have you filed a bug about your use-case so we can fix it?
[17:06] <tron103> ... no, i just assumed noone cares about infiniband haha
[17:06] <tron103> how do i file?
[17:08] <tron103> if you guys add it, I've been reading in the mellanox documentation that a "specially compiled version of dhclient is needed". tho i'm not sure if that is true since the redhat dracut-based setup was able to np
[17:08] <infinity> tron103: "ubuntu-bug linux" and mention something about needing infiniband support in d-i.  It might not be something we can fix without some investigation (as you mention, it might be more than just pulling in some modules), but a bug is still nice.
[17:10] <infinity> tron103: Perhaps best to hold off on filing the bug until you've proven yourself that adding some modules does or doesn't work, so you have a bit more data for us than just "please fix".
[17:10] <tron103> yeah
[17:10] <tron103> just setting up launchpad for now
[17:10] <infinity> tron103: Especially since I think we have exactly two machines with the right hardware to test, and I don't have access to them, so I'd be working slightly blind. :P
[17:11] <tron103> again, i'm able to bring up the interfaces once I load the 10+ modules in the super-specific order
[17:11] <tron103> its just no dhcp
[17:11] <tron103> sigh
[17:12] <tron103> maybe itll work on this new kernel
[17:13] <infinity> Bah, who needs DHCP?  Kids and your modern whiz-bang gadgets.
[17:13] <tron103> theforeman uses it to provision
[17:13] <infinity> (I was being sarcastic)
[17:13] <tron103> thank you for your help tho infinity and cj
[17:16] <infinity> apw: Actually, you might know, since Chris seems AFK and you decided to join. :P
[17:16] <apw> heh ... i missred the line and alert :)
[17:16] <infinity> apw: We have a user here who's trying to do infiniband in d-i which, at the very least, requires a bunch of modules we don't ship in the initrd.
[17:17] <infinity> apw: Chris was working with people on that at some point, right?  I feel like we also needed userspace changes that we've not yet made, but I have no idea if someone has a checklist of stuff that still needs doing.
[17:17] <apw> yeah i think you had the right victom :)
[17:17] <apw> i think i think the same as you, but have no details for you
[17:17] <infinity> Fair enough.
[17:18] <infinity> tron103: So... WIP, no ETA.  But I'll poke around to see if it got stalled/forgotten. :P
[17:18] <infinity> Would certainly be nice to sort it by 16.04, if feasible.
[17:19] <tron103> jah jah. I'll probably get infiniband support. I'll make sure to post the fix..... somwhere
[17:19] <infinity> arges: Oh sure, join now, after I grill Andy on your behalf.
[17:19] <infinity> apw: We have a user here who's trying to do infiniband in d-i which, at the very least, requires a bunch of modules we don't ship in the initrd.
[17:19] <infinity> apw: Chris was working with people on that at some point, right?  I feel like we also needed userspace changes that we've not yet made, but I have no idea if someone has a checklist of stuff that still needs doing.
[17:19] <infinity> arges: ^-- s/apw/arges/
[17:20] <arges> infinity: ok let me try to remember which bug this was...
[17:20] <infinity> arges: And, to be clear, I think he's doing IPoIB, not using any ethernet emulation layers.
[17:20] <infinity> arges: And, AFAIR, pure IB support was still a WIP.
[17:20] <tron103> yes. ipoib is correct
[17:21] <infinity> tron103: FWIW, I think doing ethernet or whatever on mellanox cards Just Works, which might be a workaround.  Run d-i in ethernet emulation mode, switch to IB post-install.
[17:21] <arges> infinity: bug 1469482
[17:21] <infinity> tron103: Though you might still hit the DHCP issue on the installed system.
[17:23] <infinity> arges: Oh good, a proper bug.
[17:23] <infinity> tron103: You might want to just subscribe to that bug instead of filing a new one.
[17:23] <infinity> arges: I suspect there are still userspace changes we need to make too, to enable DHCP over IB.  But I guess we'll find out, if someone's actually working on testing this.
[17:23] <arges> infinity: yea so tinoco was going to work on that and give some proper information about impact etc. He has access to the hardware which makes it a bit easier for him to confirm
[17:24] <infinity> arges: Thanks for the pointer, at any rate.
[17:25] <tron103> subscribed. Thank you arges infinity!
[17:27] <arges> no problem
[18:00] <tron103> smh. on the initrd of 3.16.0-45-generic, modprobe ib_ipoib just hangs lol. Guess ill go back to 3.13.0-x
[18:13] <tron103> yes!
[18:13] <tron103> nm I got it
[18:13] <tron103> ib_ipoib doesn't hang when I don't screw with modules.d
[18:17] <tron103> to recap: when using the 3.16.0-45-generic initrd.gz (aka utopic), manually loading the infiniband modules allows me to use dhcp with ipoib
[18:18] <tron103> last question: how in the world do I get my script that loads the modules in the proper order to run at init time before the installer tries to detect my net hardware?
[18:18] <tron103> sorry if thats a super n00b question, I just can't figure it out
[18:20] <tron103> anyone in pacific northwest? I'll get a round
[21:05] <tron103> so how do I properly load my infiniband modules during netboot? I added them to /init but it just gives kernel panic and hangs....
[21:06] <tron103> (added right before the last line that says exec $init)
[21:07] <tron103> lib/debian-installer[-startup].d/S99loadinfiniband didn't run as well as adding in a line for inittab


[09:40] <Lord_Phoenix> Hello guys
[19:56] <Sangeeth> Hi everyone...
[19:56] <Sangeeth> I would like to join the ubuntu laptop dev team...
[19:59] <Sangeeth> How can i join in your team?..


[06:25] <derek[] > hi
[11:50] <AndyFitz> ogra,  is brisgeek.com/fonts/ubuntu-title.otf    updated in the  ubuntu-title package ?   the TTF version is old and incorrect


[11:18] <sakrecoer> thanks for fixing the topic Unit193 :)
[11:45] <olinuxx> hi all
[11:45] <olinuxx> hi sakrecoer
[11:45] <olinuxx> :)
[12:22] <antto> hello, i've installed lxde (amongst other desktop environments).. however, i need to add a custom resolution for this monitor, but it isn't remembered after reboot.. where is a suitable place to put it?
[12:24] <antto> xorg.conf?
[12:30] <zequence> antto: Try aRandR
[12:31] <zequence> the package is named arandr
[12:31] <zequence> You should pretty much never do any configs in xorg.conf anymore
[12:31] <antto> i already have that
[12:32] <antto> it opens a GUI window where i can select output (VGA/HDMI/blahbla) and choose from the known resolutions
[12:33] <antto> but i need to add 1366x768, cuz it's not available as an option
[12:35] <zequence> antto: Ah, well, that could perhaps require some xorg.conf editing.
[12:36] <antto> but i can't seem to find where xorg.conf is located
[12:37] <antto> it's not in /etc/X11/
[12:38] <zequence> antto: There isn't one, by default, so you'll need to create one. But, the smartest place is probably /etc/X11/xorg.conf.d/yourownconf.conf
[12:38] <zequence> Though, you should be fine creating /etc/X11/xorg.conf
[12:46] <antto> hm
[12:46] <antto> now after a reboot, it throws me into text mode
[12:47] <antto> normally it goes to a screen where i login and choose which desktop environment to use
[12:56] <autumna> antto: https://wiki.ubuntu.com/X/Config/Resolution might help if you haven't already checked it out yet.
[12:58] <antto> ah
[12:58] <autumna> and as suggested there putting the start up script could be workaround until you figure out how to fix your .conf file?
[12:58] <antto> xorg.conf is not meant for scripts
[12:58] <antto> i created xorg.conf and added two xrandr calls
[12:58] <autumna> haha no sorry to mix things together. What i meant is that you can make your xrandr command to a script that is executed on login.
[12:59] <antto> yes, that's what i tried to do, but i saved it as xorg.conf
[13:00] <autumna> antto, xorg conf, is not for scripts as you just discovered. has its own syntax. there are some information on the wiki page, and you can also look at the other files in the xorg.conf.d/ folder to see more examples of the syntax perhaps?
[13:01] <antto> i don't have anything in /etc/X11/ with "xorg" in the name at all
[13:03] <autumna> ok.. correction
[13:03] <autumna> go to /usr/share/X11
[13:07] <autumna> (for the examples of syntax I mean)
[13:11] <antto> okay, added the xrandr commands to ~/.profile
[13:11] <autumna> try that.
[13:12] <antto> now i have the custom resolution as an option
[13:12] <djaccy> o/ all
[13:13] <djaccy> anyone tried the new 16.04 yet?
[13:13] <autumna> ok, and if you want to go the xorg.conf route, apparently you can add the xorg.conf to the usr/share/X11/xorg.conf.d
[14:27] <sakrecoer> welcome, olinuxx :)
[14:47] <olinuxx> :)
[15:35] <josanmc> 21
[15:40] <olinuxx> half-42 maybe ? :)
[16:55] <Hobbyboy> is it known that there are versions missing from the ubuntu archive?
[18:58] <OvenWerks> Hobbyboy: Versions? please explain.
[18:58] <OvenWerks> links are nice too :)
[19:44] <Hobbyboy> versions like 10.04, 8.04, and others are missing
[20:31] <corsario> hola
[20:32] <corsario> hello
[22:57] <OvenWerks> Hobbyboy: I think it is only versions that still have some support like security upgrades. You may find Studio's support cycle is less than vanilla or server.
[22:58] <OvenWerks> Hobbyboy: I am assuming you mean http://cdimage.ubuntu.com/ubuntustudio/releases/ ?
[23:29] <izzaboo> hello. been plying google for info to no avaiIl. installing ubuntustudio 16.04 (I think). No progress bar on install window. Is that normal??
[23:29] <izzaboo> *no avail
[23:30] <izzaboo> all I get is the slideshow that does not advance automatically
[23:31] <izzaboo> I guess I could reboot and try again...


[09:09] <czajkowski> http://lwn.net/Articles/460796/
[10:04] <tdr112> czajkowski: it is a good quote
[10:04] <czajkowski> thanks
[10:04] <czajkowski> tdr112: if you were a member you could vote!
[10:04] <czajkowski> *HINT*!
[10:07] <ebel> hehe, cool
[10:08] <czajkowski> subtle as a brick I am
[10:34] <tdr112> czajkowski: i will i will
[10:35] <czajkowski> https://bugs.launchpad.net/ubuntu-community/+bug/862162
[10:36] <czajkowski> tdr112: get it in so >:(
[10:36] <BenChapman> czajkowski: How do you join?
[10:36] <czajkowski> BenChapman: join what ?
[10:37] <czajkowski> BenChapman: https://wiki.ubuntu.com/Membership
[10:37] <BenChapman> that'd be it. Thank you :)
[10:39] <BenChapman> Ah good good. better start contributing :)
[10:44] <czajkowski> it's about becoming more involved and having a say in the community
[10:45] <BenChapman> exactly :)


[04:28] <lolzadam> JanC:  yes, but I couldn't find a -2 so i assumed. Any clue what -2 is then?
[04:54] <cypherpunks> Question about upstart start conditions: are events instantaneous never-to-be-repeated things, or long-lasting conditions?  If the former, how do "and" start conditions work?  IF the latter, how to get a list of the current conditions?  (I'm trying to figure out why a job isn't starting.)
[06:07] <cypherpunks> Ping?
[07:09] <cypherpunks> Ping?
[07:57] <cypherpunks> Sigh, it's quiet.
[09:55] <cypherpunks> Anyone actually here?
[10:04] <ion> They are instantaneous. Upstart was supposed to gain support for states (which would have made “and” much better) but development has been kind of slow and now even Ubuntu is going to switch to systemd.
[10:32] <cypherpunks> ion: Wow, thanks!  So if I have an and condition, like the one in stock Ubuntu tty2: "start on runlevel [23] and (not-container or container CONTAINER=lxc or container CONTAINER=lxc-libvirt)", it might not ever start because I can have the "runlevel" and "not-container" events both trigger, just not simultaneously?
[10:35] <cypherpunks> I wish the cookbook was a little clearer on this point.  I have a mostly 12.04 system that refuses to start any console login process (getty or lightdm) until I ssh in and do it manually.  Very annoying.
[10:35] <ion> IIRC the job keeps track of the events and when both conditions have been triggered it’ll get started. The problem with events (compared to states) is that if the job is stopped by an event, i think both events may need to happen again for it to start again, even though you never left the state whose start one of the events represents.
[10:36] <cypherpunks> Ah, so an event *can* be pending, but it's kept in the job's condition parse tree?  And there's no way to see them?
[10:39] <cypherpunks> (I'm just trying to figure out "why the @#$$@$# is this not running", and it's a real bother to reboot, but I guess "--debug" is the only way.)
[10:39] <cypherpunks> (to reboot this particular machine, FWIW.  There's a second bug I'm tying to debug where the kernel isn't finding the root file system, requiring manual intervention at the initrd shell prompt.)
[10:41] <ion> Someone who has paid more attention to the and/or condition handling code than me can probably give more definite answers.
[10:44] <cypherpunks> But thanks.  That does help clarify things.
[13:40] <bingsucks> JanC: FYI I dug through the kernel source last night and error codes are negated before returned. The -2 I got is in fact equal to 2, which if you take a look at include/uapi/asm-generic/error-base.h, corresponds to ENOENT. I assume that means no inode entry for that file, because it is commented as no such file or directory.
[13:43] <bingsucks> However I do need to look again to see if ENOENT is assigned to another constant.
[13:52] <lolzadam> cypherpunks: if nothing else, have each event trigger a task job that sets an env var. Change that and to an or and just make the job check both vars
[13:59] <jodh> xnox: Hi - could you review https://code.launchpad.net/~jamesodhunt/upstart/bug-1288243/+merge/209693 (and maybe knock off https://code.launchpad.net/~jamesodhunt/upstart/restrict-debug-stanza/+merge/204363 too?)
[14:00] <xnox> jodh: i'm confused about the debug stanza =))) hence i didn't review it =)))
[14:00] <xnox> jodh: aha, so re-exec didn't keep the name. Maybe re-exec should keep the name?
[14:00] <jodh> xnox: that 2nd branch simply makes the debug stanza a NOP unless you boot with --debug.
[14:01] <xnox> jodh: such that e.g. if i booted /sbin/init.dima it would stay init.dima after re-exec?
[14:01] <xnox> jodh: and is the same binary re-execed?
[14:02] <jodh> xnox: yes, it always re-execs its original argv[0].
[14:02] <jodh> xnox: hence the problem in the test env :)
[14:02] <xnox> jodh: hm, create test_init symlink?! =))))
[14:02] <jodh> xnox: nooooooooo....!
[14:03] <xnox> ok. =)
[14:35] <lolzadam> On a kernel + busybox setup, I compiled upstart with an Arch disc. Used the /opt/upstart prefix, changed kernel line to include upstart init location. Now getting kernel panic "Failed to execute /opt/upstart/sbin/init (error -2)"
[14:37] <lolzadam> Error -2 is commented in the kernel source as no such file. I have verified the rootfs is mounting successfully, and the old init on the same partition still works. Any ideas?
[14:37] <lolzadam> BTW also verified the file is there and size is non zero
[14:38] <jodh> lolzadam: boot using init=/bin/sh then after checking the file exists and ldd is happy with it, 'exec /opt/upstart/sbin/init --debug </dev/console >/dev/console 2>&1
[14:38] <jodh> lolzadam: ' :-)
[14:38] <lolzadam> Lol thanks.
[14:40] <lolzadam> Haven't tried ldd, but did try 'exec <path> --verbose' per troubleshooting info on website and got 'init must be PID 1' erroe
[14:40] <jodh> xnox: thanks for the reviews. The final https://code.launchpad.net/~jamesodhunt/upstart/bug-1258098/+merge/202458 should now complete the tests successfully.
[14:40] <lolzadam> I will give that a shot though
[14:42] <lolzadam> BTW is the upstart project going to be dropped after Ubuntu switches to systemd?
[14:43] <lolzadam> systemd is too heavy and over complicated. Great for desktop, not so much for server OS imho
[14:44] <xnox> lolzadam: systemd software collection is about ~30 daemons. /all/ of them are two heavy, but just the init is actually ok for a server.
[14:44] <jodh> lolzadam: huh? when you boot with init=/bin/sh, you should be pid 1 ("echo $$")
[14:44] <xnox> s/two/too/
[14:46] <lolzadam> xnox: ah makes sense. So any predictions/insight on continued upstart development?
[14:46] <jodh> lolzadam: regarding the upstart project - yes Ubuntu are switching to systemd, but we have not yet decided *when*. Also, even after we switch we still have years of support for releases containing upstart. After that, "I don't know" I'm afraid.
[14:46] <lolzadam> jodh: I'll check, hang on
[14:46] <lolzadam> Hmmm
[14:48] <lolzadam> 158
[14:48] <xnox> lolzadam: for the next 5-7 years, upstart will still be developed. Which is long enough for anything to happen.
[14:48] <jodh> lolzadam: um, if that's a pid, that's your problem :)
[14:49] <lolzadam> Lol sorry, wrong VM o.O
[15:05] <lolzadam> Aha... ldd reveals some missing libs. Guess those wouldn't have been copied to the mounted partition with make install
[15:05] <lolzadam> Doh! Lol
[16:05] <lolzadam> Will it build and run right with --enable-static
[18:00] <xnox> jodh: so, upstart bugfix release will be happening this week, right? i'm thinking to use inet6 socket activation =)


[01:46] <wizzy> fp
[01:54] <cliebow> pfff
[03:17] <flubber> sljf
[03:17] <flubber> sorry
[05:10] <kinema> I'm looking into the possibility of setting up a few Edubuntu based kiosks in public library.
[05:10] <kinema> Are there any tools to enable session time limits?
[05:46] <sbalneav> Evening all
[07:20] <atu-> hai,wanna ask please, can anyone tell me where i can find the guidelance for translating edubuntu wiki to my local language?
[07:20] <atu-> *guidelines *sorry*
[09:27] <allee> AFAIR the clients use an NFS mounted root fs, right?  In case I'm right, which pkg contains this edu-client kernel that supports NFS root fs?
[09:30] <juliux> morning
[10:18] <LinuxProbie> hey folks
[10:18] <LinuxProbie> so I did the walkthrough to get my wireless card on my inspiron working in feisty and now it doesn't even show up in iwconfig. can anyone help?
[10:22] <LinuxProbie> So, I am getting totally turned off to linux now because of this issue.
[10:46] <Tm_T> LinuxProbie: for that issue, you prolly have more help in #ubuntu etc
[12:54] <frandavid101> hiya!
[12:55] <frandavid101> I installed thin-client-manager-gnome and am trying to try it, but I don't know how
[12:55] <frandavid101> is there a command I need to run?
[01:25] <cliebow> frandavid101, re tcm..cbx33 should be able to help you
[01:43] <juliux> ogra, ping
[01:56] <knix_> morning all
[03:20] <chowmeined> Hello, I have been assigned the task of figuring out if we can implement edubuntu in our school's labs.. Could any of you provide some advice or pointers to documentation for integrating edubuntu into our windows environment (active directory)?
[03:21] <jsgotangco> well you have to go to a different type of documentation that is specific to samba
[03:22] <chowmeined> I understand working with samba but I mean are there any specific tools available in edubuntu to make this process easier?
[03:22] <cliebow_> years ago for several years we used winbind to authenticate to ad
[03:23] <cliebow_> it was not trivial..and toward the end had to cron a samba/winbind restart every hour
[03:24] <chowmeined> with the terminals is there any way to configure specific terminals permanently?
[03:25] <chowmeined> such as.. the terminals in this lab always get that printer set as default etc
[03:30] <jsgotangco> chowmeined: none at the moment unfortunately
[03:30] <jsgotangco> but if you look at future developments, there is one
[03:30] <jsgotangco> http://www.advogato.org/person/Burgundavia/diary.html?start=126
[03:31] <chowmeined> ah, how interesting
[03:38] <sbalneav> Morning all
[03:38] <sbalneav> ogra: Hey, loaded the latest nightly build last night, looked OK
[03:38] <sbalneav> ltsp chroot built properly
[03:38] <highvoltage> sbalneav: yay!
[03:40] <sbalneav> The /etc/network/interfaces got updated properly too,
[03:40] <sbalneav> but NetworkMangler is still interfering with it.
[03:41] <sbalneav> And! I was so proud of myself, I actually figured out why my USB audio card wasn't showing up as /dev/dsp, and instead was showing up as /dev/dsp1
[03:41] <sbalneav> in /etc/modprobe.d/alsa-base:
[03:41] <sbalneav> # Prevent abnormal drivers from grabbing index 0
[03:41] <sbalneav> options snd-usb-audio index=-2
[03:42] <sbalneav> I don't know if that's a bug or not.  One supposes there should be some kind of logic there to ensure that onboard gets selected first, THEN a usb audio card, if there is one, and if no onboard audio, then just fall through.
[03:43] <highvoltage> sbalneav: that's interesting
[03:43] <sbalneav> There's a long story with this USB audio card of mine.
[03:44] <sbalneav> It's a SoundBlaster Audigy NX 2, really nice unit.  Lots of inputs and outputs.
[03:44] <sbalneav> I bought it 3 years ago.  And at the time, Linux didn't know what to do with it.
[03:44] <highvoltage> I considered getting a usb soundcard/phone for skype/ekiga at some point though
[03:44] <highvoltage> heh
[03:45] <cliebow_> i fiddled with one in breezy and edgy for a customer..
[03:45] <cliebow_> the sb
[03:45] <sbalneav> So I sat on it.  For 2 years.  Every time a new kernel would come out, I'd try it again.  Nope, still not working.
[03:45] <sbalneav> Then, about a year ago, it started getting functional.  So I'm happy :)
[03:48] <highvoltage> usb devices in general seems to be more standardised and faster supported all the time
[03:49] <cbx33> sbalneav: w00t
[03:49] <cbx33> that works great in linux ;)
[03:49] <cbx33> 10 in 10 out
[03:49] <sbalneav> cbx33: See my blog post?
[03:49] <cbx33> no
[03:49] <cbx33> link me
[03:51] <jsgotangco> brb
[03:52] <highvoltage> jsgotangco: don't lie. we all know you're loaded!!!
[03:52] <highvoltage> ;)
[03:52] <cbx33> ["Rock Hard! Ride Free! All day, all night!"]  - see I knew he was lying
[03:54] <highvoltage> heh
[03:57] <bddebian> Heya
[03:59] <highvoltage> hey bddebian!
[04:00] <bddebian> Heya highvoltage
[04:00] <highvoltage> bddebian: will we be seeing you in Sevilla?
[04:00] <bddebian> Probably not. :'-(
[04:00] <bddebian> Hopefully Boston though
[04:00] <highvoltage> ok :(
[04:00] <cliebow_> Boston?
[04:01] <bddebian> I've heard that that is where the feisty+1 UDS will be
[04:01] <highvoltage> bddebian: I believe feisty+1 UDS will be in Sevilla
[04:02] <bddebian> Well feisty +2? :-)
[04:02] <highvoltage> (since feisty will already be released by then)
[04:02] <highvoltage> ah, ok
[04:32] <knix_> I havent setup up edubuntu server in awhile and need alittle help.  I am trying to setup the dhcp server part.  Do I edit dhcpd.conf to specify the ip range and all?
[04:43] <cliebow_> knix_:seens so...if you've done ltsp-server-standalone the relevant file will be /etc/lts/dhcpd.conf
[04:44] <knix_> ty, let me see how it goes
[04:44] <knix_> every time i start the dhcp server it fails, where can i see the log for this?
[04:45] <cliebow_> err syslog or messages?
[04:45] <knix_> ty
[04:45] <cliebow_> your subnet must match the clients ip address
[04:47] <knix_> great
[06:40] <knix_> Is it possible to import a text file for the users?
[06:41] <LaserJock> knix_: what do you mean?
[06:42] <knix_> I should of clarified more
[06:42] <knix_> I have many students here at my job, and instead of creating each user manually, is there any other way to import windows users in edubuntu?
[06:46] <LaserJock> ah
[06:46] <LaserJock> I don't know of a tool to do that
[06:46] <knix_> ok, just checking
[06:46] <LaserJock> but I put up a project idea for the Google Summer of Code to such a tool
[06:46] <knix_> great
[06:48] <cliebow_> knix_:should be able to do an ldifde from active directory and do agrep to get usernames..if that is where you are coming from
[06:49] <cliebow_> passwords will not transfer...but you can generate new ones and pass em out
[06:49] <knix_> greatness
[06:49] <knix_> ty
[06:56] <knix_> sorry for all the ? but, how do I get x11vnc installed on the client?  I did install it on the server
[06:58] <LaserJock> I don't think you need it installed on the client do you?
[06:58] <cliebow_> this 4.2?
[06:58] <LaserJock> or maybe you do
[06:58] <LaserJock> I'll just shut up and let cliebow_ do all the talking
[06:58] <cliebow_> you only need it on client..
[06:58] <LaserJock> ;-)
[06:58] <cliebow_> blahblahblahdeblah
[06:59] <knix_> lol, ok how do you install it on the client? If the client resides on the server
[06:59] <cliebow_> but it "could"be used to see the :0 desktop on sever
[07:00] <cliebow_> well install inthe chroot
[07:00] <cliebow_> no one listens to me anyway..
[07:01] <knix_> install in the chroot?
[07:02] <cliebow_> welll that will be the clients filesystem..
[07:03] <knix_> hmmm
[07:09] <sbalneav> Back
[07:17] <knix_> ok, If i have the internet nic unplugged, my thin client can connect to the server.  If I plug the internet nic in, my dhcp-server fails
[07:20] <cliebow_> if student-control-panel says import studentcontrolpanel.ltcm but what exists is /tcm/ltcm.py
[07:21] <knix_> i have no idea what your talking about cliebow
[07:23] <knix_> i dont have scp installed
[07:25] <sbalneav> knix_: Do you have a dhcp server on your internet gateway box?
[07:25] <sbalneav> They may be conflicting
[07:26] <mcsd> does anyone know the default root password for the live cd 6.10?
[07:26] <knix_> sbalneav, yes
[07:27] <knix_> sbalneav, how do I reslove this?
[07:29] <sbalneav> Well, how many nics does your edubuntu box have?
[07:29] <LaserJock> mcsd: there is no root password in Ubuntu
[07:29] <knix_> sbalneav, 2
[07:29] <LaserJock> mcsd: the default user is ubuntu I *think*, although it could be different for edubuntu
[07:31] <sbalneav> knix_: What's the IP address of each of them?
[07:31] <mcsd> I installed the live cd to my harddrive creating a user called test
[07:32] <sbalneav> Then log in as the user test
[07:32] <sbalneav> That user will have admin rights.
[07:32] <mcsd> so I show test@test which means I have a user test that belongs to the test group right?
[07:32] <mcsd> so there is no root user by defualt?
[07:33] <sbalneav> No, there isn't
[07:33] <mcsd> !commands
[07:33] <ubotu> The linux terminal or command-line interface is very powerful. Open a terminal via Applications -> Accessories -> Terminal (Gnome) or K-menu -> System -> Konsole (KDE).  Manuals: https://help.ubuntu.com/community/BasicCommands
[07:34] <knix_> well the one is which is DCHP on my network in my school is <IP_ADDRESS>, and the dhcp-server on edubuntu is <IP_ADDRESS>
[07:35] <sbalneav> mcsd: https://help.ubuntu.com/community/RootSudo
[07:35] <sbalneav> knix_: Have you been in here before for this?
[07:35] <knix_> maybe like a year agao
[07:36] <knix_> but my memory is shot
[07:36] <knix_> :)
[07:36] <mcsd> when I do a sudo passwd root does that create a root profile because it prompts for the root=test password then the password change
[07:37] <sbalneav> mcsd: Creating a root password isn't really recommended, but yes, that will enable root to log in.
[07:38] <sbalneav> knix_: What I'd do is, go into /etc/default/dhcp3-server, and set the interface to only be for the ethx that the terminals are on.
[07:39] <mcsd> so I dont have to use adduser I can just do passwd and assign a password and it will create that user by default...is this bad practice
[07:40] <knix_> sbalneav, i did that,
[07:40] <sbalneav> You haven't got the internet nic and the thin client nic connected to the same switches, do you?
[07:41] <knix_> nope, dif switches
[07:42] <sbalneav> So, what happens when you try to boot a thin client?
[07:42] <knix_> well if the dhcp-server fails to start, obviously nothing
[07:43] <LaserJock> mcsd: it's not the Ubuntu recommendation to enable the root password
[07:43] <LaserJock> but that's the way to do it if you want it
[07:43] <sbalneav> Well, when the dhcpd server fails to start, what messages do you get in /var/log/daemon.log?
[07:43] <knix_> let me check
[07:43] <sbalneav> mcsd: The root user already exists.  It just has the password disabled.
[07:44] <mcsd> does my user test have less permission than root?
[07:45] <knix_> no subnet declaration for eth0
[07:45] <LaserJock> mcsd: not really
[07:45] <LaserJock> mcsd: it does, but sudo allows you to "act" as root
[07:46] <sbalneav> knix_: Please paste the contents of your /etc/default/dhcp3-server, /etc/network/interfaces, and /etc/ltsp/dhcpd.conf file to the pastebin.
[07:46] <sbalneav> !pastebin
[07:46] <ubotu> pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic)
[07:46] <knix_> i will, i have to setup for a meeting in a few minutes, ill brb
[07:46] <mcsd> which is what I should be doing anyway right?... I should never be loged in as root for security reasons rigjt
[07:47] <sbalneav> mcsd: It's best to run as root as little as possible.
[07:48] <sbalneav> I run an entire network of Ubuntu machines, and I don't have any root passwords set.
[07:48] <mcsd> sbalneav: thanks
[08:03] <Burgwork> mcsd: setting root passwords is a great way to get yourself into trouble
[08:06] <LaserJock> Burgwork: but .. but ... Linux has been doing it for years ;-)
[08:07] <Burgwork> LaserJock: ....
[08:13] <sbalneav> It's not so much as having a root password will get you into any MORE trouble, if it's a GOOD root password.  However...
[08:13] <sbalneav> Nothing you do as root is logged.
[08:13] <sbalneav> Whereas, EVERYTHING you do as sudo is logged.
[08:14] <sbalneav> So, if you muck something up, you can go back in the logs, and see what happened.
[08:14] <sbalneav> And, even better, sudo allows fine grained control over what commands
[08:14] <Burgwork> plus, if you have an employee leave, pulling root privs is so much easier
[08:14] <sbalneav> Yep
[08:15] <Burgwork> now I just wish that switches and routers could auth against ldap
[08:15] <sbalneav> And, in a branch office, I might decide to give the head secretary access to the lprm command, so that they can delete mucked up print jobs from anyone.
[08:16] <sbalneav> So, it just provides SO much more flexibility than the all-or-nothing root password.
[08:16] <LaserJock> exactly
[08:27] <knix_> sbalneav, i think the issue is with the subnet and netmask be for and ip of <IP_ADDRESS>?
[08:30] <sbalneav> Can you paste /etc/network/interfaces, /etc/default/dhcp3-server, and /etc/ltsp/dhcpd.conf to the pastebin?
[08:31] <knix_> it will take some work, i have to email it to my self so please give me a second
[08:33] <sbalneav> sure
[08:34] <knix_> sbalneav, http://paste.ubuntu-nl.org/12778
[08:35] <sbalneav> in your dhcpd.conf
[08:36] <sbalneav> should be "subnet <IP_ADDRESS> netmask <IP_ADDRESS>"
[08:36] <knix_> yup, just realized that and changed it.
[08:36] <knix_> dhcp server is still failing
[08:37] <sbalneav> Also, uncomment authoritative.
[08:37] <sbalneav> Did you restart the dhcpd server?
[08:38] <knix_> sbalneav, yes, it fails
[08:38] <knix_> would you like to the log for the fail?
[08:38] <sbalneav> Yes, please
[08:39] <knix_> sbalneav, http://paste.ubuntu-nl.org/12781
[08:41] <knix_> do i need to edit /etc/dhcpd3/dchpd.conf?
[08:42] <sbalneav> no, /etc/ltsp/dhcpd.conf
[08:43] <sbalneav> What does ifconfig eth0 return?
[08:43] <knix_> the static ip does not show up
[08:45] <sbalneav> Well, that'd be a problem then.
[08:45] <sbalneav> What version of edubuntu are you running?
[08:45] <knix_> fesity beta
[08:45] <sbalneav> HAHAHAHAHAHAHAHAHAHAHAHAHAHA
[08:45] <knix_> y
[08:45] <sbalneav> NetworkMangler is borken
[08:45] <sbalneav> I have the same problem.
[08:46] <knix_> jesus christmas
[08:46] <knix_> hahahahahahaha
[08:46] <knix_> well i want to thank you for trying to help me
[08:46] <sbalneav> Wondered why you were having this, I assumed you were edgy
[08:46] <knix_> nah, i wanted to try the new one
[08:47] <sbalneav> Network Manager is currently screwing up static interfaces.
[08:47] <sbalneav> We are VERY aware of this problem :)
[08:47] <knix_> great
[08:47] <knix_> i am happy
[08:47] <knix_> i just wont use the inet
[08:47] <sbalneav> If you're looking for something to work NOW, then use edgy.  Otherwise, keep doing those updates. :)
[08:47] <knix_> how about x11vnc on feisty?  having that issue to?
[08:48] <knix_> roger
[08:48] <sbalneav> I haven't tried doing that, so if there are issues, I haven't seen them yet.
[08:48] <sbalneav> I know cbx33 put a lot of work into TCM, and it's supposed to work.
[08:48] <sbalneav> But I haven't gotten that far in my testing yet :)
[08:49] <knix_> ok, i install x11vnc on the server and it says that i have to install it on the client
[08:49] <knix_> God, i love the artwork for feisty
[09:30] <highvoltage> goodnight edubuntuland!
[09:30] <highvoltage> edubuntugirl: goodnight
[09:30] <edubuntugirl> goodnight, highvoltage. I'll keep an eye out for the MS spies while you sleep.
[09:30] <highvoltage> great
[09:30] <highvoltage> edubuntugirl: choose tomorrow will be a good day or tomorrow will be a bad day
[09:30] <edubuntugirl> I choose tomorrow will be a good day, highvoltage
[09:30] <highvoltage> makes sense, it is Friday afterall
[09:31] <LaserJock> wow, you really need a life ;-)
[09:32] <highvoltage> I think what I need is a good night's sleep, been only having 3-5 hours a night for the last week
[09:32] <highvoltage> LaserJock: http://jonathancarter.co.za/ubuntu-certified
[09:32] <highvoltage> ^^^^ in your face!
[09:33] <highvoltage> goodnight LaserJock
[09:33] <LaserJock> haha
[11:25] <telexicon> cool


[00:55] <nacc> rbasak: remind me after/before standup to ask about mocking
[01:07] <hehehe> https://www.wired.com/story/james-damore-google-memo-harvard/
[01:16] <hehehe> http://www.telegraph.co.uk/news/2017/01/29/dont-call-pregnant-women-expectant-mothers-might-offend-transgender/
[01:16] <hehehe> I recommend buying a shotgun
[01:16] <hehehe> mass insanity is around the corner lol
[06:24] <cpaelzer> jamespage: dpdk is in a-p likely to fail on tests soon, but ready for you to put the OVS-2.8 you have to its side
[07:59] <lordievader> Good morning
[08:02] <jamespage> cpaelzer: ack - I'll do a snapshot upload today
[11:15] <cpaelzer> jamespage: with the.1 in 17.05.1 it seems that the OVS dep8 tests also successfully run against the current OVS 2.7
[11:16] <cpaelzer> jamespage: I didn't expect that, but more likely it still finds the OLD libs that it was built against
[11:17] <cpaelzer> jamespage: yeah it does, once your new OVS 2.8 is in we want to drop the old 16.xx DPDK binaries that are left
[11:17] <cpaelzer> we now use version named libs - so all new ones will have 17.05 and such in their names
[11:18] <cpaelzer> jamespage: anyway that makes the new one a valid candidate in a-p, and as discussed is waiting for your snapshot upload
[11:19] <cpaelzer> I'm scheduling myself a check next week if we need/want to remove old binaries then or if all clears automatically
[12:05] <sdeziel> mdeslaur: good morning! If you have a couple of minutes, I'd appreciate if you could guide me a little in getting https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1709193 fixed
[12:07] <mdeslaur> hi sdeziel
[12:08] <sdeziel> hey
[12:08] <mdeslaur> sdeziel: hrm, looks like an SRU....is there no patch pilot today that can upload it?
[12:08] <mdeslaur> let me see if we have gnutls updates pending, one sec
[12:08] <sdeziel> mdeslaur: yes, SRU'ing this to Xenial/Trusty is my end goal
[12:09] <sdeziel> mdeslaur: thanks fro letting me know about patch pilot, I didn't know that, joining ubuntu-devel now
[12:10] <mdeslaur> sdeziel: I'm on patch piloting duty tomorrow, I can look at it then
[12:11] <mdeslaur> just realized tomorrow is my turn :)
[12:11] <sdeziel> mdeslaur: that would be awesome. Until then, should I provide you more debdiffs and attach them to the bug?
[12:14] <mdeslaur> zesty would be nice
[12:15] <sdeziel> mdeslaur: OK, I'll have zesty and trusty done then, thanks again!
[12:15] <mdeslaur> gnutls28 in trusty is in universe and is missing a crapload of security updates...adding this may be a bit futile
[12:15] <sdeziel> oh, I would have hope to drop support for TLSv1.0 all around but still have some Trusty boxes...
[12:16] <sdeziel> sSMTP has always annoyed me for only supporting TLSv1.0 max ;)
[12:16] <mdeslaur> ssmtp in trusty is probably linked to gnutls26
[12:18] <sdeziel> you are right
[12:19] <mdeslaur> looks like the same patch would apply to libextra/gnutls_openssl.c in gnutls26
[12:20] <sdeziel> alright, thanks for looking
[14:09] <sammyg> how to tell if a web server is installed?
[14:10] <dlloyd> any or a specific one
[14:11] <sammyg> any
[14:12] <sammyg> made a fresh vps install with ubuntu
[14:12] <sammyg> apache is not installed because /usr/share/httpd is missing?
[14:12] <sammyg> same goes for all?
[14:13] <lordievader> sammyg: Check if there is a program listening to port 80/443.
[14:13] <sammyg> port listener? what command?
[14:14] <sammyg> nmap?
[14:14] <dlloyd> netstat -natu |grep 80
[14:16] <sammyg> dlloyd, returned something starting with fe80: with 80 colored red
[14:16] <lordievader> Or the more recent `ss`: `ss -pln|grep '80\|443'`
[14:16] <sammyg> not a lot to list there, if i only use netstat -natu
[14:17] <dlloyd> dpkg -l |grep 'nginx\|apache'
[14:17] <sammyg> lordievader, command not found
[14:17] <sammyg> ubuntu 16.04
[14:17] <dlloyd> if you are root, netstat -natupd |grep 80
[14:17] <dlloyd> will give you the process
[14:17] <dlloyd> or sudo that
[14:18] <lordievader> O.o
[14:18] <sammyg> lordievader, yup not found
[14:18] <sammyg> what's the output supposed to look like?
[14:19] <sammyg> ports are not listed
[14:19] <sammyg> proto, rec, send, local, foreign, state
[14:19] <lordievader> Custom image install, I suppose?
[14:20] <sammyg> probably, it's from vultr
[14:20] <sammyg> <IP_ADDRESS>:22 so this would be the port? 22?
[14:20] <sammyg> of course this is the ssh
[14:22] <sammyg> nmap not installed but suggest installing it
[14:22] <sammyg> so what commands can i use for port listening?
[14:23] <sammyg> nmap? dpkg? ss-pln? netstat?
[14:23] <sammyg> spkg is a package manager?
[14:23] <sammyg> where do linux boxes put their web root?
[14:24] <sammyg> "/usr/share/httpd"?
[14:24] <sammyg> perhaps this is the safest way? for noobs?
[14:24] <sammyg> to make sure
[14:24] <hateball> literally what
[14:29] <lordievader> sammyg: Ubuntu puts the webroot, by default, at `/var/www`.
[14:29] <nacc> rbasak: around?
[14:39] <rbasak> nacc: o/
[14:39] <rbasak> Sorry was otp
[14:40] <nacc> rbasak: cool, give me one sec
[14:41] <nacc> rbasak: so i'm trying to add a unit test for lint::derive_target_branch (new function)
[14:41] <nacc> it currently takes a list of branch of objects
[14:42] <rbasak> OK
[14:42] <nacc> what's the best way to mock that?
[14:42] <nacc> as my parameterized unit test just has a list of strings (e.g., 'pkg/ubuntu/devel'
[14:42] <rbasak> Does the implementation call many methods on the branch objects?
[14:42] <nacc> only two of them
[14:42] <nacc> b.branch_name
[14:42] <nacc> b.peel().id
[14:43] <rbasak> I think you could do something like:
[14:43] <rbasak> b.branch_name = unittest.mock.Sentinel
[14:43] <rbasak> b.peel().id = unittest.mock.Sentinel
[14:43] <rbasak> Oh, b = unittest.Mock() first, sorry.
[14:43] <rbasak> You might need branch_name to be a string, actually, if derive_target_branch relies on that.
[14:44] <nacc> yeah, it needs to be astring
[14:44] <rbasak> Do you not also need to mock a debian/changelog inside there? Or does derive_target_branch not need to look?
[14:44] <nacc> so that will create a singleton for each value?
[14:44] <nacc> nope
[14:44] <nacc> (at least not in the current implementation)
[14:44] <rbasak> Yeah each time you use unittest.mock.Sentinel, it gives you a new value, for comparison purposes later.
[14:44] <jamespage> cpaelzer: done - https://launchpad.net/ubuntu/+source/openvswitch/2.8.0~git20170809.7aa47a19d-0ubuntu1
[14:44] <nacc> what if i want two of them to have the same b.peel().id ?
[14:45] <rbasak> Then point them to the same object.
[14:45] <nacc> e.g. for the test of xenial-devel and xenial-updates being the same treeish
[14:45] <jamespage> thatnks for your help on expediting the dpdk uploads for 17.05.1
[14:45] <rbasak> Either b2.peel().id = b1.peel().id
[14:45] <nacc> rbasak: right, but then i need to change my parameterization?
[14:45] <rbasak> Or same_id = unittest.mock.Sentinel
[14:45] <rbasak> b1.peel().id = same_id
[14:45] <rbasak> b2.peel().id = same_id
[14:45] <nacc> rbasak: i mean, the test-runner currently doesn't know which case i'm testing :)
[14:46] <rbasak> I see.
[14:46] <nacc> rbasak: which *type of test-case
[14:46] <nacc> rbasak: i mean, i can put that in as a parameter
[14:46] <nacc> but that seems a bit kludge-y?
[14:46] <nacc> [list of branch-names], same_hash
[14:47] <rbasak> I can't think of a better way to fix this except by using real strings (bytes?) that are different, or by representing that you need them to be the same somehow in the data structure and then creating the mocks appropriately in the test function.
[14:47] <rbasak> Another way might be to make a function that creates the structure, and make the parameters calls to that function. That's essentially the same thing though.
[14:48] <nacc> yeah, i think that's where i was getting stuck
[14:50] <rbasak> HO if you like, and we can try it in a pad?
[14:50] <nacc> rbasak: joining standup early
[14:50] <rbasak> omw
[14:50] <nacc> cpaelzer: can you think of a reason that http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php-crypt-gpg is only failing on s390x?
[14:51] <rbasak> nacc: I'm there but brb.
[14:51] <nacc> rbasak: ack
[15:13] <cpaelzer> nacc: looking
[15:48] <mdeslaur> nacc: https://usn.ubuntu.com/usn/usn-3382-1/
[15:48] <mdeslaur> nacc: thanks!
[15:49] <sdeziel> mdeslaur: nacc: thank you both!
[15:50] <nacc> mdeslaur: nice, thanks!
[16:44] <rbasak> nacc_: would you expect me to get the mapping from series codename to distribution from distro-info or from Launchpad?
[16:45] <rbasak> distro-info has the advantage that it is faster, but gets blocked on a distro-info-data SRU when a new series is opened.
[16:45] <rbasak> (including in Debian)
[16:45] <rbasak> I suppose falling back to Launchpad might be an idea.
[17:23] <nacc_> rbasak: where distribution is an object? or the xx.yy ?
[17:24] <nacc_> rbasak: i would expect we would not add a new dependency on distro-info unless we had an explicit reason to do so (i don't believe we use it at all currently)
[17:41] <nacc> rbasak: i feel like sentinel is not behaving like i expected
[17:41] <nacc> rbasak: if you're around, i'd like to clarify
[18:06] <rbasak> nacc: o/
[18:06] <nacc> rbasak: i think i figured it out, but i'd like to clarify -- standup HO?
[18:07] <rbasak> omw
[20:19] <ahasenack> nacc: need some help here, I can't figure out what git ubuntu lint is complaining about
[20:19] <ahasenack> it just says
[20:19] <ahasenack> ((0855986...))andreas@nsn7:~/git/merges/samba$ git ubuntu lint
[20:19] <ahasenack> Some lint checks failed. Please investigate.
[20:19] <ahasenack> let me paste a -v output
[20:21] <ahasenack> nacc: http://pastebin.ubuntu.com/25285660/
[20:27] <Epx998> I think I need a new way to clean a puppet cert at netboot provisioning, sigh.
[20:46] <nacc> ahasenack: have you pushed your branch anywhere?
[20:46] <nacc> ahasenack: i can try and debug locally
[20:46] <ahasenack> nacc: yes
[20:46] <ahasenack> nacc: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+ref/merge-samba-take2-1700644
[20:46] <nacc> ahasenack: ok, one sec
[20:47] <ahasenack> thx
[20:52] <nacc> ahasenack: and that's with the snap?
[20:52] <ahasenack> yes
[20:52] <ahasenack> r115
[20:58] <nacc> ahasenack: ok, reproduced with the snap but not with master, checking still
[21:00] <ahasenack> nacc: ok
[21:00] <nacc> ahasenack: ok, reproduced with master on my bastion, i can debug it now
[21:01] <ahasenack> thx
[21:01] <ahasenack> and good luck :)
[21:12] <nacc> ahasenack: can you file a bug? i have the fix, but i need to figure out why it fixes it
[21:12] <ahasenack> ok, will do
[21:15] <ahasenack> nacc: done, https://bugs.launchpad.net/usd-importer/+bug/1710015
[21:17] <nacc> ahasenack: thank you
[21:23] <nacc> ahasenack: ok, i think i see what's up
[21:23] <nacc> ahasenack: the linter is missing a check
[21:23] <ahasenack> yes?
[21:26] <nacc> ahasenack: there's a debian/rules change dropped from your deconstruct to your logical
[21:26] <ahasenack> yes, that famous one
[21:26] <ahasenack> winbind static buld?
[21:26] <ahasenack> build*
[21:26] <nacc> right, but that is not how our workflow works
[21:26] <ahasenack> I keep hitting edge cases
[21:26] <nacc> deconstruct should match logical exactly except for d/changelog and d/control
[21:27] <nacc> i think you just dropped it in the wrong place
[21:27] <nacc> the logical delta should be exactly what was uploaded before?
[21:27] <ahasenack> then I will have "add fix/drop fix" both under "remaining changes"
[21:27] <nacc> and then you would drop that bit on the rebase to new/debian
[21:27] <nacc> ahasenack: logical is unrelated to the remaining
[21:27] <nacc> ahasenack: it's not part of the new delta, it's all about hte old delta
[21:29] <nacc> ahasenack: that is, there was a bit of delta (afaict), which was this extra d/rules bit
[21:29] <ahasenack> ok, will try that way
[21:29] <nacc> ahasenack: it's not correct for that bit to not be in the logical delta
[21:29] <nacc> ahasenack: but it might be correct to drop it on the rebase to new/debian
[21:29] <nacc> does that make sense?
[21:30] <ahasenack> we'll see :)
[21:30] <nacc> i mean, just thoughts-wise, the above idea :)
[21:30] <ahasenack> I don't recall what we did last time
[21:30] <ahasenack> just that it was a drop with an empty commit
[21:31] <ahasenack> which felt very odd to me, because the empty commit was talking about removing that line from d/rules
[21:31] <nacc> right, i think that was on the rebase to new/debian
[21:31] <ahasenack> but was, you know, empty
[21:31] <ahasenack> so it was lying a bit
[21:31] <nacc> no, a drop should always be an empty commit (the way I do it)
[21:31] <nacc> as it's a removal of delta that used to exist
[21:31] <nacc> what you're dropping is the delta, which since you're rebasing onto debian means it's now an empty change
[21:31] <nacc> it's a 'documentation' commit :)
[21:32] <ahasenack> the edge case is that dropping this delta required two drops, in essence
[21:32] <ahasenack> in different points in time
[21:32] <ahasenack> I wonder if just uploading this simple fix to artful right now, removing that line from d/rules, and *then* doing this merge, wouldn't be clearer
[21:40] <nacc> ahasenack: right, the point is you can't do that in a merge in the 'old state'
[21:41] <nacc> ahasenack: you do it as part of the merge, in the new state
[21:41] <nacc> ahasenack: right, now, you're changing the delta in the old state
[21:48] <nacc> ahasenack: you absolutely can do what you're suggesting, but what i've been suggesting the whole time was to do it as part of the merge. You had that correct in your old merge. The only mistake (if you want to call it that) in the new merge is you did the change too 'early' :)
[21:50] <ahasenack> in another revision of the merge I did it later, but that got stale and I had no idea anymore about what was going on
[21:50] <ahasenack> (today)
[21:50] <ahasenack> I'll go back to deconstruct and don't drop the two commits, then get logical, and rebase on new/debian
[21:51] <nacc> ahasenack: yeah -- i mean, technically, your merge itself is fine :)
[21:51] <ahasenack> the end result
[21:51] <nacc> ahasenack: it's the workflow that got borked, which is what the linter is checking
[21:51] <nacc> yeah
[21:51] <ahasenack> I did check the cmocka builddep today, it's fine for us to keep it
[21:51] <ahasenack> and I'll explain in the MP what I checked and why it's fine
[21:51] <ahasenack> nacc: so this still warrants a linter fix?
[21:52] <nacc> ahasenack: yeah, i'm fixing the linter -- basically it hsould have detected a d/rules diff between logical and deconstruct
[21:52] <nacc> it actually was detecting it, just not telling you (becuase of an implicit return)
[21:53] <ahasenack> nacc: what I keep finding confusing is that by dropping both the commit that added that patch and d/rules, and the one that removed it partially,
[21:53] <ahasenack> I'm essentially stopping the bug from being introduced
[21:53] <ahasenack> so there is never a commit that drops just the d/rules bit
[21:54] <ahasenack> so I keep thinking "hm, let's see the commit that dropped the d/rules change. Oh my, it's emtpy, why?"
[21:55] <nacc> ahasenack: right, there wouldn't be, because you'd either be introducing a 'new' change to old ubuntu or not dropping something that doesn't exist on new debian
[21:55] <nacc> ahasenack: i think it's important to keep those two states distinct in your head (the old and new states)
[21:55] <nacc> ahasenack: old is essentially never changed, it might be refactored/reordered, etc., but the contentful changes are static
[21:56] <nacc> ahasenack: new can be whatever it needs to be to be correct :)
[22:27] <nacc> rbasak: ok, i pushed my branch of bug fixes and refreshed the MP to be ready-to-review, so i think you have 3 pending reviews from me
[22:27] <nacc> ahasenack: --^ that branch (bug-fixes-2 in my namespace) has the fix for your linter issue
[22:33] <nacc> rbasak: also, if you do need  achangelog object, then i think we want to land https://code.launchpad.net/~nacc/usd-importer/+git/usd-importer/+merge/328607 before your branch, at least, so you can use git_repository::Changelog.from_treeish
[22:33] <nacc> rbasak: istr you mentioning that in our HO
[22:50] <ahasenack> nacc: ok
[22:58] <nacc> sarnold: who should I talk to on security about potential removal of nagios3 (already not in debian) but also promotion of icinga2 so we have a monitoring package in main?
[22:58] <nacc> sarnold: i can file the MIR, but just curious how security feels about nagios3 being in ubuntu and not in debian at this point
[22:59] <sarnold> nacc: file a bug against nagios3 in launchpad asking for it to be removed, subscribe the ubuntu archive administrators
[22:59] <sarnold> nacc: might not hurt to run it past IS first
[22:59] <nacc> sarnold: yes, that's already done :)
[22:59] <nacc> sarnold: but it's seeded
[22:59] <nacc> sarnold: so i probably will need to replace the seed with icinga2
[22:59] <nacc> which will end up requiring a MIR, etc.
[23:00] <nacc> so might not happen til 18.04
[23:00] <nacc> given where we are in the cycle?
[23:00] <nacc> tyhicks: --^ you may have an opinion here too
[23:00] <sarnold> could be .. I've lost track of the backlog
[23:00] <nacc> sarnold: yeah, and it's rather late to add another one, i realize
[23:00] <nacc> sarnold: just trying to get my thoughts in order, so, at least, it can get done ASAP in 18.04
[23:01] <nacc> (well, in that cycle, i mean)
[23:14] <ahasenack> nacc: still here?
[23:15] <nacc> ahasenack: yes
[23:15] <ahasenack> nacc: my rebase on new/debian: http://pastebin.ubuntu.com/25286639/ the troublesome commits are 3558c58 and 4b54cdb which I already ordered nicely one after the other
[23:16] <ahasenack> nacc: so the plan is to drop those two (d), then add an empty commit saying something like http://pastebin.ubuntu.com/25286633/
[23:17] <ahasenack> nacc: or maybe change 4b54cdb to include the d/rules bit, and then both really cancel out, and then drop
[23:17] <nacc> reading
[23:18] <nacc> ahasenack: to be clear, both lines 11 and 12 are in the old delta?
[23:18] <ahasenack> yes, they are in the deconstruct tag
[23:18] <ahasenack> and logical
[23:19] <ahasenack> I can push it as it is now
[23:19] <tyhicks> nacc: I don't have any strong opinions here
[23:20] <nacc> ahasenack: that's ok, i'm just trying to understand
[23:20] <ahasenack> so say we all :)
[23:20] <nacc> ahasenack: it seems like they should be in the deconstruct but not the logical
[23:20] <nacc> ahasenack: oh but now i remember, they don't actually cancel themselves out all the way?
[23:20] <ahasenack> no, that's where I dropped them before
[23:20] <tyhicks> nacc: there's some benefit from focusing on the same system monitoring daemon as Debian but I wouldn't consider it to be a huge benefit from the security team's POV
[23:20] <ahasenack> nacc: correct
[23:20] <ahasenack> they don't cancel each other out
[23:20] <ahasenack> they should, but they don't
[23:20] <tyhicks> nacc: if icinga makes sense from a market share perspective, it is probably a good move
[23:21] <achiang> does anyone know how to really prevent apt-daily.service from running when booting a cloud-init image?
[23:21] <achiang> the answer here does not work - https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image
[23:22] <nacc> tyhicks: well, there hasn't been a release of nagios3 in ... 4 years
[23:22] <achiang> i passed the script as user-data to my ec2 instance and i still see evidence that the unit ran (by examining syslog)
[23:22] <nacc> tyhicks: that sort of feels ... not great for currency purposes
[23:22] <nacc> tyhicks: but yeah, we should figure that part out
[23:22] <nacc> tyhicks: ok, i'll defer to 18.04 on this, will probably re-engage your team at some point
[23:23] <tyhicks> nacc: right - Ubuntu would need to move to nagios4 (and maintain it all ourselves) or something else entirely
[23:23] <tyhicks> nacc: thanks for bringing it up early
[23:23] <nacc> tyhicks: yeah, i think the debian monitoring folks were basically orphaning it, so they let it die (and icinga2 is still maintained)
[23:23] <nacc> tyhicks: np, thanks for responding!
[23:25] <nacc> ahasenack: so this is my initial impression (or what I would expect). I would see in the logical tag's history (but not the deconstruct) a commit that replaces liness 11 and 12 with a commit containing just the change corresponding to http://pastebin.ubuntu.com/25286633/ except it would read "d/rules: compile windbind statically..."
[23:25] <nacc> ahasenack: then in the rebase to new/debian, i woudl expect to see that commit be transformed to an empty commit and dropped
[23:26] <nacc> ahasenack: oftentimes, i put in the [] in my logical something liek [previously undocumented] which is equivalent to your textual explanation
[23:26] <nacc> ahasenack: that way, the logical log still has a line per logical delta
[23:26] <nacc> and i can track each of those bits to commits (empty or not) in the new delta
[23:26] <ahasenack> nacc: but the removal of the d/rules line is not even in artful now
[23:26] <ahasenack> I can't put that in the logical
[23:26] <nacc> ahasenack: right, that's why mine doesn't have it as a Drop or anthing else
[23:26] <nacc> ahasenack: it is a literal " d/rules: compile statically"
[23:27] <nacc> ahasenack: which is is in the logical delta, as a difference from debian, in artful as it is now
[23:27] <ahasenack> isn't logical == deconstruct - changelog - metadata - duplicates?
[23:27] <ahasenack> duplicate == add and remove
[23:27] <nacc> contentfully (logical == deconstruct - changelog - metadata)
[23:28] <nacc> - duplicates would be a no-op if they are the sum of adds and removes
[23:28] <ahasenack> there is no add and remove in this case, so I left them in logical
[23:28] <ahasenack> this rule:
[23:28] <ahasenack> "An additional goal in this step is to consolidate the delta, e.g. sometimes a change is added in one Ubuntu release and then removed in a subsequent Ubuntu release. The changes, in this case, should simply be dropped.
[23:28] <ahasenack> "
[23:28] <ahasenack> doesn't apply
[23:28] <nacc> ahasenack: wait, i thought you just said there was?
[23:28] <ahasenack> it's an incomplete remove, it didn't remove the "add" fully
[23:28] <nacc> ahasenack: maybe a HO is in order? or we can talk tmrw if you'd rather
[23:28] <nacc> ahasenack: right, so it's still an add and remove
[23:29] <nacc> it just may not fit into the above sentence completely
[23:29] <rbasak> Yeah we never figured out good wording for what we mean there.
[23:29] <ahasenack> logical is the "old state", right
[23:29] <ahasenack> it's just the delta trimmed down
[23:29] <ahasenack> it represents an existing state in that package in ubuntu at that version/release
[23:29] <nacc> logical is a description of the logical delta
[23:29] <nacc> yeah
[23:30] <ahasenack> I can only change that once I apply it to new/debian
[23:30] <nacc> no
[23:30] <ahasenack> then it becomes a new delta
[23:30] <nacc> well, sort of
[23:30] <nacc> you can change the *wording* as much as makes snese
[23:30] <rbasak> Logical should be the previous delta made concise.
[23:30] <nacc> like in this case, where you have an incmpolete revert
[23:30] <ahasenack> this:
 ahasenack: yeah, i'm fixing the linter -- basically it hsould have detected a d/rules diff between logical and deconstruct
[23:30] <nacc> your'e not changing the patch, just the description
[23:30] <ahasenack> that's what broke the linter before
[23:30] <ahasenack> if you are saying now that I should change the logical to drop those "fake dupes", then it will happen again
[23:31] <nacc> ahasenack: well "broke" :) it just didn't tell you why you had incorrect logical :)
[23:31] <ahasenack> still, incorrect
[23:31] <ahasenack> something I should fix
[23:31] <nacc> ahasenack: no, it won't happen again
[23:31] <nacc> i'm not telling yout to *drop* anything
[23:32] <ahasenack> but now you are saying I should indeed drop those two commits at the logical step?
[23:32] <nacc> ahasenack: i'm saying if you combine your two commits into one, there will be a change leftover!
[23:32] <nacc> not drop, combine
[23:32] <rbasak> squash :)
[23:32] <nacc> if they were correct, the combine would be a drop
[23:32] <nacc> but they are not
[23:32] <nacc> yeah :)
[23:32] <nacc> so you squash them together, and notice hey, it didn't go empty -- so document what was missed
[23:32] <nacc> in this case, exactly that d/rules still says to compile winbind statically
[23:32] <ahasenack> not just document
[23:32] <ahasenack> fix
[23:33] <nacc> no
[23:33] <nacc> just document
[23:33] <nacc> you don't fix anything in the logical
[23:33] <ahasenack> but then the diff is still there,
[23:33] <nacc> yes
[23:33] <nacc> no
[23:33] <nacc> wait
[23:33] <nacc> what diff?
[23:33] <nacc> the diff *shoudl* be there in logical
[23:33] <ahasenack> the result of applying the fix and incompletely removing it
[23:33] <ahasenack> there is a remainder when you do that
[23:33] <nacc> logical == deconstruct - changelog - metadata
[23:33] <nacc> the remainder is in deconstruct
[23:33] <nacc> but not in your currnt logical
[23:33] <nacc> that's the reason the lint failed
[23:34] <ahasenack> yes, in deconstruct we are applying the fix and not fully removing it
[23:34] <nacc> right
[23:34] <ahasenack> then in logical I dropped (in the take2 branch) both, and that left a remainder that was unexpected
[23:34] <nacc> which emans you must do the same in logical
[23:34] <nacc> logical can't have different net contents than deconstruct
[23:34] <nacc> that violates the above equality we've said a few times
[23:34] <ahasenack> ok, with you so far
[23:35] <ahasenack> so what about this squashing?
[23:35] <nacc> if you had squashed the two commits together rather than dropping them
[23:35] <nacc> then your logical would have been correct
[23:35] <nacc> it would have been described wrong (as it would have a commit message talking about d/p/fix-1584485.patch when in fact the content of the commit was about d/rules
[23:35] <nacc> but it would have been contentfully correct
[23:36] <ahasenack> I shouldn't change the squashed commit message?
[23:36] <nacc> no you should :)
[23:36] <nacc> i was doing one thing at a time
[23:36] <ahasenack> ok, so I change it
[23:36] <ahasenack> do... *? -?
[23:37] <blackboxsw> achiang: I'm playing around w/ ec2 this week (but making dinner right now) will check it tomorrow and see if disabling is possible. we'd had a couple of internal discussions about the viability of disabling it
[23:37] <ahasenack> but the remainder will still be there, the incorrect d/rules lines will be there
[23:37] <nacc> ahasenack: right, which si good, it's part of the delta currently
[23:37] <nacc> ahasenack: you're going to drop it *in* the merge, not before the merge
[23:37] <nacc> ahasenack: basically, the "old" stuff never changes (this is what i was trying to say before)
[23:37] <ahasenack> we just changed the commit message of the old stuff
[23:37] <nacc> contentfully never changes
[23:38] <nacc> metadata (like commit messages) can change
[23:38] <nacc> the order thigns are committed in, can change
[23:38] <nacc> but the endpoints should match (a la the equality we expressed above)
[23:38] <rbasak> The logical is supposed to be exactly the previous delta, re-described.
[23:38] <rbasak> If there was a mistake in the previous delta, the logical will still have the same mistake, but described as one.
[23:38] <nacc> contentfully: reconstruct = deconstruct = logical + changelog + metadata
[23:39] <nacc> what the actual commits look like in each is a separate point, but the above is what the linter is checking for
[23:39] <ahasenack> see, I'm an elecrtrical engineer, when someone says "exactly the same", that has a strong meaning to me :)
[23:39] <nacc> "actual commits look like in each" == `git log old/debian..<each>`
[23:39] <nacc> ahasenack: exactly the same git-tree
[23:39] <nacc> (meaning filesystem  contents)
[23:40] <rbasak> Exactly how you choose to describe the logical (in terms of commits and commit messages) is subjective. But the diff of "git diff old/debian old/ubuntu" must be exactly the same as "git diff old/debian logical/..." except for metadata (update-maintainer etc) and debian/changelog
[23:41] <rbasak> If the diffs aren't the same (except those exceptions), the logical is always incorrect.
[23:41] <nacc> right, that's what the linter was trying to express here, it just didn't spit out the message saying that (fixed in my branch)
[23:41] <ahasenack> well, now I have the diff the same
[23:41] <ahasenack> but the commits are not squashed
[23:41] <nacc> ahasenack: yeah, so i was trying to save you a step in your rebase :)
[23:42] <nacc> ahasenack: it's not strictly necessary, but i think makes it easier to review (given that i'll probably be reviewing, it's even less necessary :)
[23:42] <achiang> blackboxsw: from one developer's opinion, it is really unfriendly -- the service reaches out to the network and takes locks on your system with very little user visibility
[23:42] <nacc> ahasenack: do you want to push your logical as it is now?
[23:42] <ahasenack> I don't know
[23:42] <achiang> blackboxsw: i agree there is some utility there, but it feels more like an opt-in thing, rather than an opt-out
[23:43] <ahasenack> to me squashing the logical as you described "changes" it
[23:43] <achiang> or at the very least, make it possible to disable easily, somehow. the ec2 way would be to pass in a user-data script
[23:43] <ahasenack> but, the normal case where two commits really cancel each other out is a change fit for the logical step
[23:44] <nacc> ahasenack: it can't change it, afaict
[23:44] <nacc> ahasenack: if what "it" is is the diff between old/debian and the tag
[23:47] <ahasenack> ok, trying again
[23:57] <blackboxsw> achiang: yeah I expect we'd minimally be able to pass a runcmd that does the trick


[20:51] <tdaitx> doko, hi! so, openjdk 6b37 source is available on debian, are you planning to sync that to ubuntu any time soon? my interest in this is to decide whether I upload a new package for the security team or just wait for a Xenial one and backport it
[20:54] <doko> tdaitx, now done, and filed https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1518073
[20:55] <doko> hmm, tdaitx, did you check that the generated control file is the same?
[20:57] <tdaitx> doko, only on openjdk 7 it was the same, for openjdk 6 there were a few differences
[20:57] <tdaitx> doko, I mean, between wily and xenial
[20:58] <doko> ?
[20:58] <tdaitx> doko, on openjdk7 the d/control file was the same for xenial and wily IIRC
[20:59] <tdaitx> as for openjdk 6 it was slight different between wily and xenial
[20:59] <tdaitx> (on openjdk 6 dependencies were declared as '>=' on wily and '=' on xenial)
[21:00] <tdaitx> doko, does that answer your questions or did I get your question wrong?
[21:01] <doko> tdaitx, right, so we probably have to unify this, or regenerate the control file before upload
[21:02] <tdaitx> doko, the d/control for the openjdk6 package I pointed you to was for Xenial, did you regenerate it for unstable before the upload?
[21:02] <doko> yes
[21:03] <doko> I'll have a look what we can unify. we can discard the >=/= diffs because we don't need to support lucid anymore
[21:03] <tdaitx> doko, oh, that was from lucid
[21:04] <tdaitx> I didn't know
[21:06] <tdaitx> doko, is it ok to remove those older versions as well? should we do it for this update?
[21:09] <doko> no, has time