[00:25] <Epx998> can the d-i partman handle setting block sizes for the lvm?
[00:26] <sarnold> hehehe_off: just that php makes programming safe tools almost impossible
[06:36] <lordievader> Good morning
[06:36] <cpaelzer> hi lordievader
[06:38] <lordievader> Hey cpaelzer, how are you?
[07:12] <cpaelzer> lordievader: I'm good and feel close to EOW
[07:12] <cpaelzer> lordievader: everything ine for you as well today?
[07:12] <cpaelzer> +f
[07:12] <lordievader> Doing good here, just found out q35 is a lot faster in qemu :D
[07:13] <cpaelzer> more modern = better most of the time
[07:13] <lordievader> True, but newer can also mean less stable.
[07:13] <cpaelzer> lordievader: what was your workload?
[07:14] <lordievader> Oh very low, just some benchmarking. Was checking nfs performance. It was doing 14MB/s while direct to disk was around 130MB/s.
[07:14] <lordievader> In iperf there was a difference of 10 times the bandwith between two similar vms, one had the old stuff the other one q35 turned out.
[07:19] <cpaelzer> I've seen the same when people change from the old default e1000 net to virtio
[07:20] <cpaelzer> Did not expect that much from q35, but maybe it implied some device changes that triggered your improvement
[07:21] <lordievader> I think it is the change pci to pci-e. There is a huge difference between e1000 and virtio.
[08:00] <gheorghe_> hehehe_off you said 755. if the user is www-data, apache can modify the file
[08:49] <adac> on a auto security update of my openvpn package, it seems that the openvpn is not coming up corectly aynmore
[08:50] <adac> only a manual restart solves it /etc/init.d/openvpn restart
[08:57] <adac> This happend on all my machines. is there a bug in upgrading?
[08:57] <cbauer> I've skipped the process of setting up an account when installing ubuntu-server, I suppose there's no default password for root, right?
[08:58] <rbasak> adac: perhaps. Can you try downgrading to see if it starts working again? If so, please report a security regression with details.
[08:58] <rbasak> cbauer: correct
[08:59] <adac> rbasak, how can I downgrade it to previous version?
[08:59] <cbauer> when booting the ubuntu-server livecd, switching tty and trying to chroot to set a password for root of the installed ubuntu-server, but not having much luck even mounting the disk
[08:59] <cbauer> the shell there seems _very_ limited
[09:01] <cbauer> is it normal that I can't name my account "admin"?
[09:01] <cbauer> seems reserved
[09:01] <rbasak> adac: click through the versions on https://launchpad.net/ubuntu/+source/openvpn to find the appropriate debs.
[09:03] <adac> rbasak, ok thanks I'll try
[09:05] <adac> rbasak, yes that worked. tun interface is there and all is up and running
[09:05] <adac> shoudl I try upgrading again?
[09:06] <adac> upgrading also worked
[09:06] <adac> hmm
[09:06] <adac> maybe there is a prblem then wit auto security upgdates?
[09:06] <adac> *updates
[09:42] <cbauer> my livecd doesn't appear to be booting in uefi mode, is this normal?
[09:43] <cbauer> UEFI is of-course enabled on the machine
[09:43] <cbauer> http://imgur.com/l7rmg7L
[09:44] <cbauer> writing error but still, there's no efivars mounted
[09:45] <cbauer> manually mounting it worked though, so not sure if it actually installed in uefi mode
[10:01] <rbasak> adac: hard to say. Thank you for checking. I guess we'll have to see if others report the same problem.
[10:12] <adac> rbasak, ok. You're welcome
[12:14] <frickler> cbauer: check your bios settings, you may need to enable "UEFI CDROM" instead of "CDROM" in your boot device list
[12:15] <cbauer> 'enable'? you mean select?
[12:16] <frickler> cbauer: depends on your bios, but yes. took me some time to find that out when trying to install UEFI via network boot
[12:17] <cbauer> installed it now, as  /sys/firmware/efi/ exist I presume UEFI setup was successfull
[12:18] <cbauer> issue isn't the UEFI at least
[12:18] <cbauer> the livecd/ubuntu is just weird to me, that's all, like missing UEFI tools I'm used to on other distros
[12:20] <cbauer> for some reason lspci doesn't return
[12:21] <cbauer> ^C is ignored as well
[12:57] <frickler> rbasak: adac: we are seeing the same issue now, unattended upgrades updating openvpn and vpn broken after that
[12:57] <adac> frickler, ok thanks for the info!
[12:58] <adac> rbasak, ^^
[13:00] <rbasak> frickler, adac: thanks. To confirm, are you both seeing this server side or desktop side?
[13:01] <rbasak> And could it be that your openvpn clients aren't reconnecting automatically somehow?
[13:01] <rbasak> Or is it something more than that?
[13:02] <adac> rbasak, they actually do but only after ah manual /etc/init.d/openvpn restart
[13:02] <adac> *a manual
[13:06] <frickler> rbasak: I tried manually reconnecting, got no response from the server. restarting fixes it for me like for adac. nothing obvious in the logs though
[13:09] <adac> frickler, ok so we have totally the same issues. And int happened on every single serer of mine
[13:09] <adac> not only one
[13:12] <frickler> adac: right, four servers here, broken after automatic upgrade. cannot reproduce with manual downgrade/upgrade
[13:13] <adac> frickler, exactly not reproducable whith manual downgrade/upgrade here as well
[13:13] <adac> rbasak, ^^
[13:14] <rbasak> mdeslaur: ^
[13:14] <rbasak> I'd like to help but the non-reproducibility of this makes it really difficult :-/
[13:14] <adac> frickler, ubuntu 16.04 right?
[13:14] <adac> rbasak, yes I understand of course
[13:17] <rbasak> adac, frickler: could you try downgrading and then upgrading using the unattended-upgrades command? I'm not sure if that suppresses things if it's run recently though.
[13:18] <rbasak> And it'd be useful if you could file a bug against openvpn to start tracking this please. Tag it "regression-update".
[13:19] <rbasak> I don't see how the unattended-upgrades command would change things, but at least that's closer.
[13:20] <rbasak> http://launchpadlibrarian.net/325110671/openvpn_2.3.10-1ubuntu2_2.3.10-1ubuntu2.1.diff.gz is the diff that was applied as the security update. I don't see anything in there that could be causing this, so perhaps it's a latent bug in the packaging rather than something actually introduced by the security update (rather the security upgrade triggered the latent bug).
[13:34] <frickler> rbasak: adac: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1700079 , unattended-upgrades run manually also does not reproduce this
[13:36] <adac> frickler, ok thanks for the info
[13:39] <adac> frickler, out of curiosity, what did all break for with that? For me of course the communication to the (web) services that are behind the the VPN and can only be access trough the VPN. Second my logging was interrupted, sending everything to to a log server
[13:40] <adac> trough VPN
[13:40] <adac> Im also thinking about turning of auto security updates. Maybe have a monitoring when there are security updates and then run them manually
[13:41] <adac> trough ansible or so
[14:01] <ahasenack> rbasak: hi, question about the git workflow
[14:01] <rbasak> Sure
[14:01] <ahasenack> rbasak: following Deconstruct current Ubuntu delta into logical commits.
[14:01] <ahasenack> rbasak: let's see if I can point you precise where I am at
[14:02] <ahasenack> rbasak: I did the big step "2. Deconstruct current Ubuntu delta into logical commits."
[14:02] <ahasenack> my question is about, at the very end,
[14:02] <ahasenack> "Interactively rebase the deconstructed Ubuntu delta and drop 'changelog' and 'update-metadata' changes, by simply dropping those lines from the rebase todo file."
[14:02] <ahasenack> what I have now, is each change in a single commit, as we wanted
[14:02] <ahasenack> and an out-of-date debian/changelog, because of those drops
[14:03] <ahasenack> and also out-of-date d/control (no maintainer change, it's still debian)
[14:03] <rbasak> That's expected for logical
[14:03] <ahasenack> the next big step is
[14:03] <rbasak> We're reducing it to git commits only - no changelog changes, only commit messages. And no update-maintainer.
[14:03] <ahasenack> 3. Rebase delta onto latest Debian release.
[14:03] <ahasenack> but let's say there was no new debian release
[14:04] <ahasenack> this was just to bring the repo up-to-date with what was uploaded manually, without the git workflow
[14:04] <ahasenack> then we would have to reconstruct the changelog here, right?
[14:04] <ahasenack> and d/control
[14:04] <rbasak> Yes, though I'm a little confused as to why you need that.
[14:05] <ahasenack> I don't think I do, I was just verifying each step
[14:05] <rbasak> But yes, it should be fine to add a commit with the full changelog change, and another commit for the full update-maintainer change.
[14:05] <ahasenack> and understanding where I was
[14:05] <rbasak> Then you should have an identical tree to the non-git upload.
[14:05] <ahasenack> right
[14:05] <ahasenack> rbasak: ok, the other question I have,
[14:05] <rbasak> But I'm not sure what you'd do with that tree/commit when you have it. We don't really have a process/use case for that.
[14:06] <ahasenack> rbasak: when picking each change from debian/changelog, and figuring out the commit that does that,
[14:06] <ahasenack> rbasak: this delta is old
[14:06] <ahasenack> rbasak: the d/changelog usually lists something like "Remaining changes" and then a list
[14:06] <rbasak> You could certainly tag logical (without doing the changelog and update-maintainer commits) and leave that for future merges.
[14:07] <ahasenack> rbasak: my question is, this section doesn't have the original bug numbers anymore for each one of those old delta changes
[14:07] <ahasenack> do we care?
[14:07] <ahasenack> rbasak: http://pastebin.ubuntu.com/24932986/ is what I deconstructed into individual commits
[14:08] <ahasenack> my git log --oneline: http://pastebin.ubuntu.com/24932993/
[14:16] <rbasak> I usually drop the bug numbers, so that matches what I would do. I do this because leaving a full LP references leaves a Launchpad-Bugs-Closed against that version, which would technically be wrong. And the bug numbers can be found in previous changelog entries if needed anyway.
[14:17] <rbasak> ahasenack: on the next merge, feel free to refactor the changelog entry. But you can't change it until then of course.
[14:17] <rbasak> s/the changelog entry/the remaining changes section/
[14:18] <ahasenack> ok
[15:03] <ahasenack> what does this [linux-any] mean in d/control?
[15:03] <ahasenack>                libaio-dev [linux-any],
[15:04] <ahasenack> in a Build-Depends line
[15:08] <powersj> ahasenack: it is an architecture wildcard if I recall.
[15:09] <powersj> kernel-cpu is the format, so you could say any-i386 for only i386, or in your case only linux kernels and any cpu
[15:17] <nacc> ahasenack: https://www.debian.org/doc/debian-policy/ch-relationships.html#s-depsyntax
[17:00] <Epx998> 2
[17:17] <ahasenack> nacc: when you have a moment, we can talk about the samba merge
[17:22] <darinavbt> Hi all. Could I get some assistance setting up a test OpenStack deployment using Ubuntu Autopilot? I seem to be running into an issue.
[17:22] <nacc> ahasenack: give me a few minutes to context switch out of my current stuff
[17:22] <ahasenack> nacc: yep
[17:41] <nacc> ahasenack: want to use a HO?
[17:43] <ahasenack> nacc: yes please
[17:43] <ahasenack> nacc: let's use the standup one
[17:43] <nacc> ahasenack: ok
[18:08] <teward> *beeps*
[18:09] <teward> finally got IPv6 1:1 NAT working... which is... odd...
[18:16] <ahasenack> ipv6 nat?
[18:17] <teward> ahasenack: LXD containers and on-link IPv6 only
[18:17] <teward> ahasenack: the only 'nat' that exists was the snat/dnat >.>
[18:32] <ahasenack> nacc: is there a way to insert those empty commits now after all this? Pick one commit in the middle of the rebase somewhere to edit, commit, and rebase --continue?
[18:33] <ahasenack> I don't mind starting over, btw
[18:34] <nacc> ahasenack: right, so the easiest way is to edit just before you want to insert
[18:34] <ahasenack> ok
[18:34] <nacc> ahasenack: in the rebase -i editor
[18:34] <nacc> ahasenack: that will drop you to the shell just after commiting the entry you edited
[18:35] <nacc> ahasenack: so then you can freely do a `git commit --allow-empty -m 'message...'
[18:35] <ahasenack> great
[18:35] <ahasenack> thx
[18:35] <nacc> ahasenack: what's fun is you can actually do that directly in the rebase -i editor
[18:35] <nacc> with
[18:35] <nacc> x git commit --allow-empty -m 'message..'
[18:35] <ahasenack> but I have no commit hash there
[18:35] <ahasenack> ah, x
[18:35] <nacc> ahasenack: advanced usage :)
[18:35] <ahasenack> I'll get there someday :)
[18:36] <ahasenack> hm, that krb patch isn't upstream yet
[18:37] <ahasenack> I definitely miss a dep3 header
[18:37]  * ahasenack puts on the Indiana Jones hat
[18:38] <ahasenack> heh, found it
[18:38] <ahasenack> https://bugzilla.samba.org/show_bug.cgi?id=10490
[18:38] <ahasenack> from 2014
[18:38] <nacc> ahasenack: :)
[18:39] <nacc> ahasenack: i especially like that last comment from last april
[18:39] <ahasenack> still scrolling down
[18:40] <ahasenack> heh
[18:42] <ahasenack> debian bug is not mentioned in d/changelog or git log
[18:42]  * ahasenack keeps digging
[18:42] <ahasenack> found
[18:42] <ahasenack> https://launchpad.net/bugs/1310919
[18:44] <Epx998> is 17.04 in beta or?
[18:44] <nacc> Epx998: 17.04 ... came out in april 2017
[18:44] <nacc> Epx998: as per the name
[18:44] <Epx998> ah word
[18:44] <Epx998> is not listed as LTS which is why i asked
[18:44] <nacc> Epx998: it's not an LTS.
[18:45] <nacc> Epx998: even year'd april releases are currently LTS
[18:46] <sarnold> someone usually updates this page when releases are released or retired https://wiki.ubuntu.com/Releases
[18:46] <Epx998> thanks - saved the link
[18:47] <Epx998> hmm maybe i should do 16.04.2
[18:48] <sarnold> do you need the newer kernel?
[18:48] <sarnold> oh wait you've got crazy hardware issues. you might benefit frmo the newer kernel. :)
[18:49] <Epx998> no, I am just tinkering with my linux desktop, drive is failing - so giving something new a go
[19:28] <fullstop> Hi all.  I have a 14.04 server with md raid.  one drive failed miserably and won't spin up.  I have replaced the drive and added the new partitions to the arrays, but it adds them as spares and won't promote them to an active drive.
[19:29] <fullstop> is there a way to force the spare to be used?
[19:30] <fullstop> I see a lot of threads online regarding this, but no solutions.
[19:33] <fallentree> fullstop: how did you remove old and add new drive to the array? what mdadm commands did you use?
[19:34] <fullstop> I couldn't remove the old one since it was no longer in the device table -- it won't spin up.
[19:35] <fullstop> so I added a new one with mdadm --manage /dev/md0 --add /dev/sdb3
[19:35] <fullstop> and it resynced
[19:35] <fullstop> but now it shows a degraded array with one drive and one spare.
[19:35] <fallentree> pastebin it?
[19:37] <fullstop> https://pastebin.com/raw/zRFtJAnZ
[19:37] <fullstop> I have all of the data backed up, so rebuilding everything isn't the end of the world
[19:37] <fullstop> but it would have been nice to pop a new drive in and rebuild.
[19:38] <fallentree> fullstop: can you pastebin /proc/mdstat ?
[19:41] <fullstop> https://pastebin.com/raw/czawGj7f
[19:42] <fullstop> I won't know if the larger volume will work or not for a few hours.
[19:45] <fullstop> I think that I'll wait for the resync to finish and start fresh with two new drives.
[19:46] <ahasenack> nacc: hi, one more question
[19:47] <ahasenack> nacc: let me divide up this work in two phases: a) rebase old/debian; b) rebase new/debian
[19:47] <ahasenack> in (a) I split all the changes into individual commits and so on
[19:47] <fullstop> I just found a keysense error in the log, fallentree, and I suspect that the "good" drive isn't so good.
[19:48] <ahasenack> in (b), I apply that to the new debian package, resolving conflicts, dropping patches that are upstream already, etc
[19:48] <ahasenack> nacc: good so far?
[19:48] <ahasenack> nacc: oh, hm. Now that I explained it like that, I don't think I have a question anymore :)
[19:48] <fallentree> fullstop: yeah. --add should've added and activated the drive. see what happens when the sync is done, my guess is it'll promote the drive to active and move to UU status
[19:48] <ahasenack> nacc: but I can humor you with what it was
[19:49] <fallentree> fullstop: well, it's been a few years since I used mdadm last. nowadays it's all ZFS for me
[19:49] <fullstop> yes, we've switched to zfs for new stuff as well.
[19:50] <fullstop> it took me a few minutes to remember how to do the mdadm stuff.
[19:51] <fallentree> fullstop: this cheatsheet always  helped me back then   http://www.ducea.com/2009/03/08/mdadm-cheat-sheet/
[19:52] <fullstop> I have a feeling that it works better if you still have the target disk in place and are able to remove it.
[19:56] <fallentree> perhaps, yeah
[19:57] <sarnold> fallentree: that's handy, thanks
[19:57] <fallentree> I had to replace a drive maybe two or three times and each time they were still visible to the OS so I'd fail it and remove manually, before replacing
[19:57] <fallentree> sarnold: yw
[19:58] <sarnold> fallentree: I haven't tried the root on zfs yet but mdadm is so much less fun I really don't know how to drive the root on mdadm that I've got :)
[20:00] <fallentree> sarnold: grub recognizes it automatically, and you could even reboot into rescue mode / installer USB, recreate partial array (1 disk mirror, with the other "missing" (valid value to mdadm)), rsync files, rinse and repeat on the old drive, sync them up, chroot, update-grub, win
[20:01] <fallentree> did that a few times. in production. over ssh. :)
[20:01] <fallentree> no need to separate out /boot, if it's simple RAID1 mirror, for any other level you need separate /boot
[20:02] <darinavbt> I'm spinning up an OpenStack cloud using Ubuntu Autopilot. I'm setting up MAAS. When I commission machines, should I check "Allow SSH access and prevent machine from powering off"?
[20:02] <darinavbt> I'd think I'd want to be able to SSH into it, but I don't know why that's linked with "prevent powering off".
[20:03] <sarnold> fallentree: ohhhhh my. you mean I can probably live migrate to zfs on root? :)
[20:04] <darinavbt> Or, if that checkbox is unchecked, can I still log in as ubuntu using the SSH key I put into MAAS?
[20:04] <sarnold> darinavbt: if you don't have sccess in here you can also try in #maas
[20:04] <fallentree> sarnold: no, you said mdadm, you and yeah you could live migrate to mdadm RAID 1. As for ZFS, thing is you can't create partial mirrors, so live migration is off
[20:04] <darinavbt> Thanks!
[20:05] <sarnold> fallentree: you can add a new drive to a mirror vdev any time you want :)
[20:05] <fallentree> sarnold: yeah but it doesn't auto-rebalance like btrfs
[20:05] <fallentree> you'd still have to (re)copy data
[20:06] <fallentree> unless that changed recently
[20:06] <sarnold> fallentree: that's adding a new vdev entirely; you can add more disks to a mirror vdev, or turn a single disk vdev into a mirror vdev, any time you want
[20:07] <fallentree> sarnold: I see. in which case it would be possible to live migrate to ZFS root yeah
[20:07] <fallentree> "live"... you would need a short period of downtime when you assemble the chroot with root mounted from the zpool so grub and initramfs pick it up
[20:07] <sarnold> fallentree: the mdadm steps seem more complicated than I expected; I'm surprised about the rsync.. are those instructions for going frmo nothing to mdadm root?
[20:09] <fallentree> sarnold: yeah, I had single drive, plain ext4 partitions, added another, partitioned, created partial mdadm devices (with "missing" in place of original disk), copied data and then from rescue mode assembled the full array and set up grub/initramfs
[20:10] <nacc> ahasenack: sorry, was afk -- i'm here now
[20:10] <fallentree> of course ran one final rsync from rescue mode before cleaning up old single drive and adding to the mirror
[20:11] <ahasenack> nacc: np
[20:12] <ahasenack> nacc: I found out that one of the patches that still applies is wrong now with this new upstream version, and for a moment wondered in which "phase" it should be dropped: (a) or (b). It's (b), of course, since that's when our changes are being applied on top of the new debian version
[20:13] <sarnold> fallentree: that's so cool. :D
[20:14] <fallentree> yeah it was pat-on-the-back-worthy once done :) of course, that was after numerous test attemps with VMs and lotsa failures :)
[20:15] <sarnold> haha
[20:16] <sarnold> yeah I can imagine
[20:35] <SupaYoshi_> anyone experience with pxe / tftp testing?
[20:35] <SupaYoshi_> I am setting up a clonedeploy server and I am having issues with TFTP
[20:36] <SupaYoshi_> I would like to test if my TFTP server on Ubuntu is properply working, but I don't know how too. My router seems to properply handle PXE, based on Wireshark packets, and the server IP
[20:36] <SupaYoshi_> but not sure on the tftp server on the pxe/tftp server.
[20:39] <ahasenack> nacc: I'm getting a traceback now when I run merge finish: http://pastebin.ubuntu.com/24935370/
[20:39] <ahasenack> could it be related to the fact I'm no more in detached head state, since I created that branch to push do LP?
[20:47] <sarnold> SupaYoshi_: can you tftp to the server? :)
[20:54] <nacc> ahasenack: hrm, it *shouldn't* matter
[20:54] <nacc> ahasenack: you ran `git ubuntu merge start` with the same args?
[20:55] <ahasenack> close, I ran with -f
[20:55] <ahasenack> git ubuntu merge start ubuntu/devel -f
[20:55] <nacc> ahasenack: ok, that should be ok still for finish (the -f is mosty for the tag overwriting0
[20:55] <ahasenack> yeah
[20:56] <nacc> ahasenack: bah, it's my recent change -- one sec
[20:56] <ahasenack> :)
[21:01] <nacc> ahasenack: can you push your branch somewhere? i'll see if i can reproduce it locally
[21:01] <nacc> ahasenack: also i think this will fix it: http://paste.ubuntu.com/24935500/
[21:02] <ahasenack> nacc: pushed, it's that samba-merge-4.6.5 one from here: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+ref/samba-merge-4.6.5
[21:03] <ahasenack> nacc: too bad it's a snap and I can't patch it on-the-fly :)
[21:03] <ahasenack> r/o filesystem
[21:04] <nacc> ahasenack: ok, reproduced
[21:07] <nacc> ahasenack: and fixing
[21:13] <nacc> ahasenack: pushing, it should refresh in a few minutes
[21:13] <ahasenack> ok
[21:13] <ahasenack> thx
[21:20] <nacc> ahasenack: should be available now
[21:20] <ahasenack> refreshing
[21:20] <ahasenack> got r65
[21:20] <nacc> ahasenack: yeah that should have the fix
[21:21] <ahasenack> $ git ubuntu merge finish ubuntu/devel
[21:21] <ahasenack> 06/23/2017 18:20:44 - INFO:Using git repository at /home/andreas/git/merges/samba
[21:21] <ahasenack> no crash
[21:21] <ahasenack> and I have a new changelog
[21:21] <ahasenack> I think
[21:21] <nacc> ahasenack: cool :)
[21:22] <ahasenack> some chunks are repeated from previous changelog entries
[21:22] <nacc> ahasenack: can you show me in a paste?
[21:22] <ahasenack> it added the changelog from 4.5.8+dfsg-2ubuntu2
[21:22] <ahasenack> yep
[21:22] <ahasenack> chrome doesn't like big pastes to pastebin :/
[21:23] <nacc> ahasenack: to be clear, the tooling doesn't actually look in d/changelog. What it did was use the git commits you ahve in your branch
[21:23] <nacc> which include the entries (correctly) from 4.5.8+dfsg-2ubuntu2, afaict
[21:23] <ahasenack> nacc: http://paste.ubuntu.com/24935632/
[21:24] <nacc> ahasenack: right, so lines 28-30, e.g., come from 03d512aff0e477b9d2094ac128f1f4b349631231
[21:24] <ahasenack> yes
[21:24] <nacc> ahasenack: it's looking at every git commit since 'debian/sid' and extracting each message into debian/changelog (basically running `git reconstruct-changelog debian/sid`)
[21:25] <nacc> ahasenack: which is correct? I mean it's doing what you told it to do
[21:25] <nacc> ahasenack: you need to push those commit messages in (indentation wise)
[21:25] <nacc> ahasenack: as they are now carried forward delta
[21:25] <ahasenack> I thought I had
[21:25] <ahasenack> no, wait
[21:25] <nacc> ahasenack: at least in my view of your repo, you haven't yet
[21:25] <ahasenack> the dep8 one, for example
[21:25] <ahasenack> that I didn't indent
[21:26] <ahasenack> because it wasn't old delta
[21:26] <ahasenack> but I think I see your point
[21:26] <nacc> it *is* old delta now
[21:26] <ahasenack> it's about being a delta
[21:26] <ahasenack> yeah
[21:26] <nacc> yep
[21:26] <ahasenack> I purposedly skipped those
[21:26] <ahasenack> ok
[21:26] <ahasenack> so it's correct to list all that again, because it's delta from now on
[21:26] <nacc> correct
[21:26] <ahasenack> ok
[21:26] <nacc> and you want to nest it under "remaining chagnes"
[21:26] <nacc> because it is remaining changes that were previously reviewed/uploaded
[21:27] <ahasenack> right
[21:27] <nacc> ahasenack: you can also see the difference between the old changelog and this one, we drop LP: to LP automatically
[21:27] <ahasenack> how do I do this again? I tagged before running merge finish
[21:27] <nacc> ahasenack: git checkout <tag>
[21:27] <nacc> ahasenack: git rebase -i new/debian
[21:27] <nacc> ahasenack: 'r' the ones you want to chagne the commit message for
[21:27] <ahasenack> that's ok
[21:28] <nacc> ahasenack: and then run 'finish' command again
[21:31] <nacc> ahasenack: does that make sense?
[21:31] <ahasenack> nacc: http://pastebin.ubuntu.com/24935676/
[21:32] <ahasenack> nacc: what about   * d/p/krb_zero_cursor.patch: add DEP3 header
[21:32] <nacc> ahasenack: i think lines 35-39 are part of the old delta too?
[21:32] <ahasenack> it's a delta, but a change I made while doing the merge
[21:32] <ahasenack> and when we remove a patch, is that delta?
[21:33] <nacc> ahasenack: i would keep that dep3 change at the top-level, because it's 'new' delta relative to what was uploaded prior
[21:33] <ahasenack> removing the patch removed the delta
[21:33] <nacc> ahasenack: let me look in the branch
[21:33] <ahasenack> I have to push again, after the commit messages changes
[21:33] <ahasenack> but the content is untouched
[21:34] <nacc> ahasenack: that's fine
[21:34] <nacc> ahasenack: ok, so i think this is a case of delta being added and dropped prior
[21:34] <nacc> ahasenack: so it shouldn't even be in the new changelog
[21:35] <ahasenack> which one?
[21:35] <nacc> ahasenack: e.g., 88c04472396882cc60ea81a57ca6902e20cb77cb and e341bb56cbd3d28907e40b4eeb0ec3e550bfe888 negate each other
[21:35] <ahasenack> that guy was added and dropped several times
[21:35] <nacc> ahasenack: or i guess not dropped, but clarified
[21:35] <nacc> ahasenack: as you didn't undo the debian/rules change (afaict)?
[21:36] <ahasenack> oh, I might have forgotten that bit
[21:36] <ahasenack> yep, need to remove it
[21:36] <nacc> ahasenack: do you want to do another HO? might be easier to clarify this case
[21:36] <ahasenack> and have to check artful
[21:36] <SupaYoshi_> hi my tftp gives a timeout
[21:37] <ahasenack> let's forget fix-1584485.patch for a moment
[21:37] <ahasenack> I did indeed forget about the debian/rules associated change for that one
[21:38] <ahasenack> nacc: what about "refresh patches", "add DEP3" and "Remove d/p/winbind_trusted_domains.patch"
[21:38] <ahasenack> last one is me removing a delta
[21:38] <nacc> ahasenack: i think refresh patches can be nested, as you're not contentfully changing the delta
[21:38] <nacc> ahasenack: even the d/p/krb_zero_cursor.patch change, could be nested under the commit corresponding to line 7
[21:39] <nacc> ahasenack: as just a [..] comment
[21:39] <SupaYoshi_> http://prntscr.com/fng069 my tftp server times out
[21:39] <nacc> ahasenack: if you're explicitly dropping delta, it should be in a * Drop: section with a reasoning
[21:40] <ahasenack> ok, will do
[21:41] <nacc> ahasenack: and in git, it should end up being an empty commit (as it can't have any content relative to Debian, as the delta didn't exist in Debian)
[21:41] <ahasenack> hm
[21:42] <ahasenack> I think that goes back to my reasoning before about (a) and (b) phases
[21:42] <ahasenack> the patch can only be dropped when applied to the new samba version
[21:42] <ahasenack> so (b)
[21:42] <ahasenack> I don't understand how that would be an empty commit
[21:42] <nacc> ahasenack: sure, a commit can *become* empty
[21:42] <nacc> ahasenack: ok, so you have some commit X in old/ubuntu
[21:43] <nacc> ahasenack: it added some functionality relative to old/debian
[21:43] <nacc> ahasenack: that change is no longer needed in new/debian
[21:43] <hehehe_off> which channel on freenode is for discussing girls?
[21:43] <ahasenack> nacc: hold a bit
[21:43] <ahasenack> nacc: "so you have some commit X in old/ubuntu"
[21:43] <ahasenack> not really: I have a huge change, not individual commits yet
[21:43] <hehehe_off> its kinda amusing with so many guys here girls are not a topic
[21:43] <nacc> ahasenack: well, that should be logical<version>
[21:44] <nacc> hehehe_off: please stop.
[21:44] <hehehe_off> nacc why
[21:44] <nacc> hehehe_off: you can read the topic, you know you're being offtopic.
[21:44] <hehehe_off> I like girls
[21:44] <hehehe_off> I asked where is such channel
[21:44] <nacc> hehehe_off: and that is a ubuntu server discussion, how?
[21:44] <nacc> !alis | hehehe_off
[21:44] <hehehe_off> I did not find any using alis
[21:44] <hehehe_off> :)
[21:45] <nacc> hehehe_off: i don't care.
[21:45] <hehehe_off> maybe there are none
[21:45] <hehehe_off> nacc then why talk to me?
[21:45] <hehehe_off> so u do care :D
[21:45] <hehehe_off> anyhow I am off :)
[21:45] <nacc> hehehe_off: because you're leading to noise when i'm trying to actually get something done.
[21:45] <hehehe_off> you wont use /ignore why?
[21:46] <hehehe_off> :)))
[21:46] <hehehe_off> if 1 question about girls provokes u so much
[21:46] <nacc> hehehe_off: it's not cute or funny. you are being intentionally disrespectful of a channel's rules.
[21:46] <hehehe_off> :)
[21:46] <fallentree> nacc: ur just feeding trolls. notify the ops and don't waste your time ;)
[21:46] <nacc> fallentree: true
[21:47] <hehehe_off> and coding requires libido :)
[21:47] <hehehe_off> including ubuntu server
[21:51] <gheorghe_> i open #ubuntu-server after hours of doing other stuff and i see hehehe_off saying that coding requires libido. well... sorry for evasdropping on this discussion :D
[21:52] <hehehe_off> :)
[21:52] <hehehe_off> hi gheorghe_
[22:02] <Epx998> is there any weird different for dns from 14 to 16?
[22:03] <ahasenack> thx nacc
[22:03] <ahasenack> have a great weekend, cya
[22:03] <nacc> ahasenack: np, you too!
[22:11] <nergar> hello, I'm checking my seedbox and it is running 2.6 in xenial, why is that? how can I make it boot with kernel 4.8? i already isntalled sudo apt install --install-recommends linux-generic-hwe-16.04
[22:12] <nacc> nergar: what is a seedbox? like a VPS?
[22:12] <qman__> nergar: paste the full output of uname -a
[22:13] <nacc> nergar: ask your hoster, if so, it's probably something you don't get to control
[22:13] <nergar> i hacve root access
[22:13] <nacc> nergar: you might not have 'real' root access
[22:13] <nergar> Linux ss105 2.6.32-042stab120.18 #1 SMP Fri Jan 13 10:32:04 MSK 2017 x86_64 x86_64 x86_64 GNU/Linux
[22:14] <nacc> nergar: yeah that's a VPS something or other -- i've seen it before
[22:14] <gheorghe_> mergar: cat /etc/issue
[22:14] <nacc> nergar: might even just be a container, not a VM
[22:14] <qman__> yeah, you're probably on a container, not an actual VM
[22:14] <nergar> yeah, VPS
[22:14] <nergar> so no chance of changing the kernel? i didn't know this :/
[22:15] <nergar> why would they give me a xenial install with 2.6??
[22:15] <nacc> nergar: because they want to control what is in the kernel
[22:15] <qman__> with containers, the guests use the host kernel
[22:15] <qman__> so they are stuck with whatever the host is running
[22:15] <nergar> oh!
[22:15] <nergar> wow, bummer
[22:16] <gheorghe_> nergar that is why i was curious what is written in /etc/issue ... i didn't even know xenial can run with 2.6
[22:16] <fallentree> what can possibly be running 2.6 kernel still?
[22:16] <nacc> fallentree: plenty of VPS providers, unfortunately
[22:16] <qman__> 2.6.32 is really old at this point, it's probably an old centos
[22:16] <nacc> gheorghe_: /etc/issue is a fileystem file, not reflective of anything beyond what (in this case) was untarred tomake the root fs
[22:16] <nergar> Ubuntu 16.04.2 LTS \n \l
[22:16] <fallentree> 2.6 doesn't even support containers properly if at all
[22:16] <nacc> fallentree: a heavily patched one would
[22:17] <nacc> fallentree: might even be openvz or some such
[22:17] <gheorghe_> nergar, are you using alibaba cloud?
[22:17] <qman__> maybe not lxc, but containers have been around a lot longer than that
[22:17] <Epx998> dang resolv.conf just wont work wth
[22:17] <nergar> Obtrix, the provider is Obtrix
[22:17] <fallentree> nacc: that's bordering criminal negligence :)
[22:17] <nacc> fallentree: it's why they (VPS) are so cheap, on some level :)
[22:18] <qman__> google suggests it's a RHEL 6 OpenVZ kernel
[22:18] <fallentree> uname would solve the mistery
[22:18] <nacc> qman__: sounds about right
[22:18] <fallentree> ah, it was given above
[22:18] <nacc> fallentree: provided above already
[22:18] <nacc> :)
[22:18] <fallentree> stab, yeah openvz
[22:18] <sarnold> fallentree: 2.6.32-042stab120.18
[22:19] <nergar> well, anyhow. i just wanted to try out something, I am dumping them for ByteSized hosting and it runs 4.8
[22:19] <nacc> the frustrating part, to me, is that tooling reports this as "Ubuntu"
[22:19] <nacc> when it's quite clearly not Ubuntu ata ll
[22:19] <nacc> *at all
[22:19] <fallentree> canonical sued OVH for that particular reason (trademark abuse)
[22:20] <sarnold> our legal team sometimes contacts such hosters :)
[22:20] <nacc> fallentree: yeah
[22:20] <nacc> sarnold: yeah, i'm aware :) -- still frustrating, though
[22:20] <nergar> not ubuntu?
[22:20] <nergar> what do you mean?
[22:20] <nacc> nergar: ubuntu has a kernel they ship
[22:20] <nacc> nergar: also, containers are ... just processes, they blur the line of what it means to run a distribution
[22:21] <qman__> it's not really ubuntu, at least not the whole thing - it's a bunch of ubuntu stuff stacked on a RHEL kernel and any hacks they had to do to make that work
[22:21] <nergar> TIL
[22:21] <hehehe_off> canonical sued OVH for that particular reason (trademark abuse) link?
[22:21] <fallentree> google it
[22:21] <hehehe_off> nah ty
[22:21] <hehehe_off> :D
[22:21] <hehehe_off> maybe later
[22:22] <hehehe_off> I was checking something google done
[22:22] <hehehe_off> on blockchain
[22:22] <hehehe_off> apecconnect.org
[22:23] <hehehe_off> seems like bs
[22:23] <hehehe_off> maybe usefull for some
[22:23] <nergar> what about this one?: Linux bermudi 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[22:23] <fallentree> your enter key is stuck.
[22:23] <fallentree> nergar: that sounds like proper xenial kernel
[22:23] <nacc> nergar: yeah that looks better
[22:23] <sarnold> time for a reboot but no terrible :)
[22:24] <nacc> sarnold: does livepatch change the uname? just thinking out loud
[22:24] <sarnold> nacc: probably not
[22:24] <sarnold> a lot of bugs never get livepatched though
[22:24] <nacc> sarnold: yeah i didn't think so ... interesting, another thing to remember to ask about
[22:25] <nacc> sarnold: absolutely, was just curious if you knew
[22:44] <Epx998> figures, network team gave me the wring dns server ip