[09:09] <CIA-33> ubiquity: evand * r3430 ubiquity/ (50 files in 8 dirs):
[09:09] <CIA-33> ubiquity: Merged Michael Terry's plugins branch (LP: #419989). See
[09:09] <CIA-33> ubiquity: http://wiki.ubuntu.com/Ubiquity/Plugins for instructions on writing
[09:09] <CIA-33> ubiquity: new plugins.
[09:13] <evand> cjwatson: may I request permission to use one of your previous rejection notices as a template for further rejections?
[09:13] <evand> "Membership of this team confers commit access to parts of the installer, so it's only granted to people with a track record of sending good patches. Feel free to reapply after you've had a reasonable number of patches accepted."
[09:14] <ogra> evand, hey
[09:15] <ogra> evand, is there a way to make usb-creator only use it's dd functionallity ? we have the prob that it wont be usable on armel because syslinux isnt available, so i thought i'd ask if there is a way to use it without the syslinux parts before i unseed it ;)
[09:16] <cjwatson> evand: yes
[09:26] <evand> ogra: as in just dd an image to the disk, or mount the vfat filesystem, copy the files, but don't install the bootloader?
[09:26] <evand> cjwatson: thanks
[09:26] <ogra> evand, just as in dd an image to the disk
[09:27] <evand> ogra: that option is slightly broken in the devicekit backend (but works just fine in the windows backend), I'm fixing it today.
[09:27] <ogra> i'm aware it work be able to do all the stuff it does on i386, but if there is any use for it on armel i'd like to keep it
[09:28] <evand> You can either add a disk image via the Other... button or by passing the path to it on the command line using the -i option
[09:28] <ogra> hmm, you are not understanding what i mean :)
[09:28] <evand> ah, apologies
[09:28] <ogra> on armel we ship ubuntu-desktop
[09:28] <ogra> in ubuntu-desktop we seed usb-creator
[09:29] <ogra> usb-creator cant do its normal function (create a usb key from iso) because on armel syslinux isnt available
[09:29] <ogra> but usb-creator can act as dd frontend
[09:30] <ogra> if there is a way to make it act *only* as dd frontend on armel desktops we can still use it there
[09:30] <evand> hrm
[09:30] <ogra> if there is not, i need to unseed it on armel because it is uninstallable without syslinux
[09:31] <ogra> its not the end of the world to unseed it, but i wanted your opinion
[09:31]  * evand thinks of the best way to accomplish that
[09:31] <ogra> and if there would be some kind of switch we'd happily leave it in as dd frontend
[09:32] <ogra> dpkg-architecture could tell you you are on armel and switch off the iso writing behavior ... but its some work to add such a check i guess
[09:35] <evand> I wonder what the best way to replicate preprocessor ifdefs in a pygtk application is.
[09:35] <evand> ogra: I'll see what I can come up with
[09:36] <ogra> evand, ok, tell me what you decide, the deps need arch specific adjustment as well if you really do it
[09:36] <evand> my current thought is to have another desktop file that gets installed instead of the normal one in usb-creator-gtk when the build system is armel
[09:37] <evand> this desktop file would provide another parameter that enabled some sort of dd-only mode
[09:37] <ogra> sounds good
[09:38] <ogra> would help on ia64 powerpc and sparc too btw :)
[09:39] <evand> ah, indeed :)
[09:43] <CIA-33> ubiquity: evand * r3431 ubiquity/ (d-i/manifest debian/changelog):
[09:43] <CIA-33> ubiquity: Automatic update of included source packages: clock-setup
[09:43] <CIA-33> ubiquity: 0.98ubuntu2.
[10:02] <CIA-33> ubiquity: evand * r3432 ubiquity/debian/changelog: releasing version 1.99.17
[10:54] <CIA-33> ubiquity-slideshow-ubuntu: evand * r137 html/debian/changelog: releasing version 4
[13:06] <CIA-33> casper: cjwatson * r678 trunk/ (debian/changelog scripts/casper): merge lp:~tormodvolden/casper/empty-dev
[13:09] <CIA-33> casper: cjwatson * r679 trunk/ (debian/changelog scripts/casper): merge lp:~tormodvolden/casper/guard-dev-nodes
[13:10] <CIA-33> casper: cjwatson * r680 trunk/scripts/casper: move check_dev existence test up a bit to avoid problems with LIVEMEDIA_OFFSET
[13:12] <CIA-33> casper: cjwatson * r681 trunk/debian/changelog: releasing version 1.190
[13:15] <lool> evand1: Hey, around?
[13:15] <evand1> lool: yarp
[13:15] <lool> evand1: I created an USB stick with usb-creator tip
[13:15] <lool> but cant boot it on two different computers
[13:15] <lool> I used an i386 UNR ISO from an amd64 install
[13:15] <lool> I had to manually umount /media/gibberish at the end of the USB creation and issued a "sync" before removing the USB key
[13:16] <lool> Not sure whether any of this is relevant
[13:16] <lool> What happens on boot is that I see a blinking cursor, and then nothing happens
[13:16] <lool> The USB key is only blinking for a couple of seconds and then stops
[13:16] <evand1> is partition 1 marked as active/boot?
[13:16] <lool> No
[13:16] <evand1> ah, set that and see if that makes a difference
[13:16] <evand1> I just realized that I forgot to carry that over from the old branch
[13:17] <lool> Ok thanks
[13:17]  * ogra olways thought thats only relevant for dos
[13:18] <cjwatson> no, some BIOSes care
[13:18] <ogra> ah
[13:18] <lool> evand1: no difference on both computers
[13:18] <AnAnt> cjwatson: when can I ping you ?
[13:18] <evand1> hrm
[13:18] <ogra> AnAnt, you just did :P
[13:19] <AnAnt> hehe
[13:20] <AnAnt> cjwatson: last week you said you'll look at LP 416949
[13:20] <lool> evand1: I actually had the same thing last week with two USB micro SD readers and wanted to try again with a real USB stick to take that out of the equation; it seems it was truly the contents of the USB image at some level
[13:20] <AnAnt> cjwatson: I don't want to be annoying, but I know that sometimes ppl forget
[13:20] <evand1> rather than the bootloader, you mean?
[13:21] <cjwatson> AnAnt: I said I'd look when I had a moment, and I haven't yet
[13:21] <AnAnt> ok
[13:21] <cjwatson> I have not forgotten and you do not need to keep reminding me
[13:21] <lool> I was fearing the BIOS might be sensible to various types of USB devices as I want sure the micro SD adapters were mass storage or not
[13:22] <evand1> ah, I understand
[13:23] <lool> sudo syslinux /dev/sdb1
[13:23] <lool> file is read only, overwrite anyway (y/n) ?
[13:23] <lool> odd
[13:23] <lool> and ^C releases a storm in my terminal
[13:23] <evand1> oh yeah, don't do that
[13:24] <evand1> I have a bug in debian on mtools relating to that
[13:24] <lool> evand1: Dont ^C or dont run syslinux at all?
[13:24] <lool> Is it safe to run on sdb1?
[13:24] <evand1> don't ^C
[13:25] <lool> I was wondering if the bug could be that syslinux was run while the vfat was mounted
[13:25] <evand1> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542635
[13:25] <lool> Running syslinux again didn't bring it any further
[13:26] <evand1> I have another suggestion, just give me a minute to dig it up
[13:27] <ogra> lool, make sure btw that the drive is actually unmounted, i noticed that nautilus doesnt seem to properly unmount stuff if you click the eject icon nowadays
[13:27] <lool> ogra: I unmounted and sync-ed manually
[13:27] <ogra> ah, k
[13:27] <evand1> dd if=/usr/lib/syslinux/mbr.bin of=/dev/whatever bs=446 count=1 conv=sync
[13:27] <evand1> I'm wondering if it's getting confused by whatever is in the boot sector.
[13:28] <lool> Oh that could be
[13:28] <lool> I didn't have ay
[13:28] <lool> any
[13:28] <evand1> (another small bit of code I forgot to carry over)
[13:28] <lool> that's almost certainly the issue
[13:29] <lool> yup
[13:29] <evand1> hooray
[13:29] <lool> evand1: thanks
[13:29] <evand1> (and a big fail to me)
[13:29] <evand1> sure thing, I'll fix that in trunk
[13:29] <lool> thanks for that too; do you want a bug?
[13:29] <evand1> please
[13:30] <lool> Strictly speaking I guess one could argue that I was at fault for using an USB key without a MBR in the first place
[13:31] <lool> (It's odd that I know perfectly about MBR and bootable flags but didn't check these myself; I suck!)
[13:32] <lool> 425680
[13:33] <evand1> thanks!
[13:46] <CIA-33> partman-partitioning: cjwatson * r713 ubuntu/ (90 files in 10 dirs): merge from Debian 71
[14:02] <davmor2> evand1, cjwatson: guys I'm just doing a wubi install off of todays iso.  Also I'll do a install along side to try and sort out that grub2 issue showing vista up
[14:12] <davmor2> evand1: wubi is caught up in a cycle at ubuntu boot time again
[14:12] <evand1> davmor2: can you pastebin the exact error message?
[14:14] <davmor2> evand1: I can pastebin the wubilog you don't get to see an error it just restarts the machine as soon as you hit ubuntu from the windows grub menu
[14:14] <evand1> hrm
[14:15] <davmor2> evand1: I thought you said rev 150 should be pulled in?
[14:15] <davmor2> the wubi log says rev 142
[14:16] <evand1> it should
[14:16]  * evand1 investigates
[14:20] <evand1> weird, the wubi builds weren't producing new executables
[14:21] <davmor2> evand1: I'll leave that one with you then and try again tomorrow :)
[15:13] <davmor2> cjwatson: afternoon.  Right vista on, ubuntu on, vista still not showing up in the grub menu.  However grub still pauses for 4 secs or whatever to allow you to select the os to use, even though it still only displays the ubuntu options
[15:14] <CIA-33> usb-creator: evand * r158 trunk/ (debian/changelog usbcreator/backends/devicekit/backend.py):
[15:14] <CIA-33> usb-creator: * Unmount partitions before writing a disk image.
[15:14] <CIA-33> usb-creator: * Clear the boot sector code area and set the boot flag on the partition
[15:14] <CIA-33> usb-creator:  (LP: #425680).
[15:19] <tormod> cjwatson, thanks for merging those casper branches so fast!
[15:20] <tormod> it so more encouraging to fix things when it get acted upon timely
[15:21] <tormod> now, there is also bug #385305, I am unsure what is the best fix out of several options. if you have an opinion, I can prepare a branch
[15:48] <shtylman> evand1: I worked on the kubuntu-slideshow and have a branch I proposed for merging into trunk... I didn't merge myself cause I wanted one of yall to review it and make sure I did everything right as I moved quite a bit around
[15:48] <evand1> shtylman: wonderful!  I'll take a look at it now
[15:49] <shtylman> evand1: thanks
[15:53] <cjwatson> tormod: I think it would be OK to require .disk/casper-uuid-$blah nowadays
[15:54] <cjwatson> tormod: I'm a bit reluctant to remove it altogether since it's (AFAIK) the only thing that lets image-written-to-unpartitioned-USB-stick work
[15:55] <cjwatson> tormod: to tell you the truth I'm not exactly sure I know all the RAID paths though, so if you have the relevant systems to hand you're probably better-placed than me to make a judgement call ...
[16:07] <evand1> shtylman: You should get some text in the Konqueror page before we upload.
[16:08] <evand1> shtylman: Also, may I ask that you update debian/copyright for the new icons before I merge
[16:08] <shtylman> evand1: indeed :) ... I will poke the kubuntu people to think of something...I am not best suited for that
[16:08] <evand1> sure :)
[16:08] <shtylman> evand1: gotcha...now...the icons...I got some from wikipedia and others from the oxygen icon set...
[16:08] <shtylman> evand1: are there problems of use there?
[16:08] <shtylman> evand1: I unfortunately don't know the intricate details there...
[16:09] <evand1> we're fine so long as they're under and acceptable open source license
[16:09] <evand1> but you'll need to note the license for each in debian/copyright, as we've done for the other icons
[16:10] <evand1> and if it's a license that isn't already included, add it to the copyright file.
[16:11] <shtylman> evand1: gotcha..ok..I will do that and also update the konq page once I get more eyes on it :) thanks for reviewing
[16:11] <evand1> sure thing
[16:11] <evand1> let me know when you're ready for a merge
[16:11] <shtylman> will do
[16:12] <tormod> cjwatson: what is the use-case for image-written-to-unpartitioned-USB-stick? can you boot from something like this in the first place?
[16:12] <tormod> one problem with the "ugly hack" path is that is stops looking elsewhere. maybe we can fix that.
[16:18] <cjwatson> I think you can, yes, and indeed the installation guide used to recommend it in some cases
[16:18] <cjwatson> it saves having to bother with partitioning
[16:25] <tormod> so the CD iso file is written to e.g. /dev/sdc? or only the squashfs file? and what are the "ext[234]" cases for? I don't understand all of the code yet, like the softlinking of this device.
[16:28] <cjwatson> you ask as if I wrote all this ... :-)
[16:28] <cjwatson> you certainly couldn't just write the squashfs on its own and expect it to work, but there'd probably be nothing much stopping you dding the iso9660 filesystem over
[16:29] <tormod> but you wouldn't be able to boot from it...
[16:29] <CIA-33> usb-creator: evand * r159 trunk/usbcreator/ (3 files in 3 dirs): Use proper exceptions. Use a threading.Event object rather than a boolean flag to manage shutting down.
[16:30] <cjwatson> err. I forget then. bzr blame and see if you can find an audit trail? :)
[16:31] <tormod> all this * came from a debian merge so bzr won't reveal the guilty
[16:32] <tormod> if I knew which setups we want to support, I could make sure I understand those, and ditch the rest...
[16:33] <tormod> btw, is the plan to stick to casper for a while? otherwise I wouldn't invest too much in it.
[16:34] <tormod> only make a workaround the mentioned bug is fixed
[16:35] <cjwatson> I see no reason not to stick to casper
[16:36] <cjwatson> moving to live-initramfs would be a huge amount of work at this point and we'd have to make all the current stuff work again ...
[16:36] <CIA-33> usb-creator: evand * r160 usb-creator/usbcreator/backends/devicekit/backend.py: Do not add CD drives to the targets list.
[16:52] <davmor2> cjwatson: Is there anything you would like me to try to get vista showing up on grub2?
[16:53] <davmor2> evand1: did you get to the bottom of the wubi build issue?
[16:53] <cjwatson> I can't look now :-( I'm beating my head against totally reorganising developer permissions in LP
[16:54] <evand1> davmor2: indeed, the latest daily-live should fix the issue
[16:55] <davmor2> cjwatson: Fun :D Not  well I need to redo vista tomorrow to retest wubi :)
[16:55] <cjwatson> sorry, I know I need to find some time when you're free to debug it
[16:56] <davmor2> cjwatson: your the one that needs to be free you gotta fix it :)
[16:56] <davmor2> you're even
[16:57]  * cjwatson tries to figure out how to synthesise a test upload for LP
[19:06] <lool> Did anybody test casper-rw persistence recently?
[19:11] <lool> I think it OOPSes
[19:12] <lool> with aufs that is


[02:46] <bluesabre> :)
[03:06] <Unit193> https://gitlab.xfce.org/panel-plugins/xfce4-pulseaudio-plugin/-/merge_requests anything good here?  Cut a new release soon maybe? :D
[10:25] <bluesabre> Definitely some nice sounding patches. Will try to take a look in the next couple days.


  Not sure why that would fail.  Let me look
[08:43] <robitaille> oh...you mean the server, not the mailing list.  I'm just an admin on the ML
[08:45] <robitaille> do you want me to reset your password? it seems I can do it
[08:45] <Burgundavia> thanks
[09:04] <Burgundavia> robitaille: fridge is pure html, correct?
[09:05] <robitaille> when writing stories?  you have the choice...one of which is pure html
[09:07] <Burgundavia> saw that
[05:38] <nixternal> FREE GEEK article posted and awaiting moderation
[05:49] <nixternal> FREE GEEK article posted and awaiting moderation
[05:49] <nixternal> just in case that didn't get through
[06:18] <nixternal> hrmm..mdke made changes to the fridge article about free geek that isn't correct
[06:18] <nixternal> they only install ubuntu on some machines..not all
[06:18] <nixternal> most of the time is is SuSE or Fedora Core, but the Free Geek Chicago guys love Xubuntu


[19:00] <superm1> evand, oh well.  just figured it'd be easiest to hand carry it rather than fedexing.  good on the flash drive at least


[13:38] <cmaloney> morning
[14:09] <jrwren> morning
[14:09] <jrwren> yakkety is less than a month away. so much excite
[14:10] <cmaloney> What's exciting in it?
[14:20] <jrwren> i've no idea. I should probably go look ;]
[14:31] <cmaloney> Please do.


[00:17] <harlowja_at_home> smoser, woot, i'm an openstack PTL now :-P
[00:17] <harlowja_at_home> take that bossman
[00:17] <harlowja_at_home> lol
[00:17] <harlowja_at_home> crap i never wrote that parser
[00:17] <harlowja_at_home> lol
[00:18] <smoser> oh my.
[00:19] <smoser> yeah, crap to you
[00:19] <smoser> but congrats too
[08:55] <Odd_Bloke> All hail harlowja_at_home
[15:28] <harlowja_at_home> lol
[15:35] <smoser> harlowja_at_home, because i'm too lazy to google
[15:35] <smoser> what PTL ?
[15:36] <harlowja_at_home> project technical lead smoser
[15:36] <harlowja_at_home> whatever that means, ha
[15:36] <harlowja_at_home> :-P
[15:44] <smoser> harlowja_at_home, i know what it meant.
[15:44] <smoser> which ptl are you
[15:44] <harlowja_at_home> oh
[15:44] <harlowja_at_home> lol
[15:45] <smoser> 'what PTL', not whats ptl ?
[15:45] <harlowja_at_home> oslo, the common library stuff/glue
[15:45] <smoser> wow. you actually are important.
[15:45] <harlowja_at_home> ha
[15:45] <harlowja_at_home> idk
[15:46] <harlowja_at_home> i'm just a poor boy from a poor family
[15:46] <harlowja_at_home> easy come easy go
[15:46] <harlowja_at_home> lol
[21:07] <magicalChicken> smoser: Hey, I've been working on finishing up merging ip= configuration into net config and I think everything is working correctly,
[21:07] <magicalChicken> but I'm not sure if some of the values I'm writing out should be omitted or not
[21:07] <magicalChicken> here's a demo run: http://paste.ubuntu.com/15418034/
[21:24] <suro-patz> hello folks !
[21:25] <suro-patz> Is there a way to re-run network config by cloud init, after the node got booted up
[21:26] <suro-patz> I think one alternative is removing /var/lib/cloud/instances/* and then reboot
[21:26] <suro-patz> I am trying to save the reboot each time
[21:26] <suro-patz> harlowja_at_home:^^
[22:26] <smoser> magicalChicken, ok. great. i have some other stuff for you...
[22:27] <smoser> suro-patz, you can probably re-run cloud-init local (or cloud-init) which ever wrote the data for you.
[22:29] <smoser> magicalChicken, ok. so it looks there like 'gateway' is missing from eth0, right ?
[22:29] <smoser> oh. i see the comment.
[22:30] <smoser> so you're saying it only added the new interface
[22:30] <smoser> i think that is fine.
[22:52] <smoser> suro-patz, rm -Rf /var/lib/cloud /var/log/cloud-init*; cloud-init init --local'
[22:52] <smoser> magicalChicken, http://paste.ubuntu.com/15419211/
[22:52] <smoser> rharper, ^
[22:52] <smoser> thoughts on that if you see it. i hope to put some more work into that.
[22:53] <smoser> i actually think its fairly well throught through and solid at this point.
[23:32] <suro-patz> smoser: will try the same, thanks!


[09:54] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2954 UNAPPROVED queue
[14:10] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2995 Preparing packages
[14:10] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2995 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[16:36] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2995 Diff missing
[17:59] -queuebot:#ubuntu-ci-eng- jamespage cpaelzer, https://bileto.ubuntu.com/#/ticket/2979 Ready to build (artful/dpdk). Successfully built (artful/openvswitch)


[02:14] <hardbop200> hi! what's the recommended (or, better yet, most stable) version of ubuntu studio?  hardy, jaunty, karmic, lucid or maverick? I don't want to run anything *really* old, but I don't mind stepping back a version or two if I need to. thoughts?
[02:15] <holstein> hey hardbop200 :)
[02:16] <holstein> i use lucid
[02:16] <holstein> i would say dont use natty yet
[02:16] <holstein> other than that, your good to go :)
[02:18] <holstein> i use lucid with falktx's PPA added
[02:18] <holstein> anyways...


[14:58] <Volkard> Hello
[14:58] <Volkard> Where is everyone from
[15:05] <Malinux> Volkard: Norway I assume
[15:05] <Volkard> safe assumption
[15:06] <Malinux> it is


[18:16] <Umeaboy> Hi! I've logged into Launchpad with my old emailadress, but I want to change that to the one I created instead. Can'
[18:16] <Umeaboy> t seem to find the setting to change that.
[18:17] <Umeaboy> I have added two emailadresses to be contacted by and I want to login with<EMAIL_ADDRESS>[18:39] <caraka> Umeaboy: Try logging in directly at ubuntuone.com, and update your settings there.
[18:42] <Umeaboy> caraka: Thanks! That solved it!
[18:42] <Umeaboy> Gotta go.
[18:42] <Umeaboy> Take care!
[21:00] <olzhas> Trying to support C++14 project with gcc 4.9 on Ubuntu 14.04 via launchpad. Is it possible?


[00:08] <mdeslaur> valorie: wait a day and I should appear by itself when we do monday triage
[00:09] <mdeslaur> it*
[00:13] <valorie> ok
[00:19] <tsimonq2> valorie: also I saw that Debian applied these fixes, that might help too
[00:19] <tsimonq2> s/applied/released/
[00:21] <valorie> excellent
[00:26] <tsimonq2> valorie: You might want to point them towards bug 1745635 as it seems to be the tracking bug for this.
[00:28] <valorie> tsimonq2: thanks for that -- passed along
[05:41] <cpaelzer> bdrung: hi
[05:41] <cpaelzer> bdrung: I think smb will do the next iproute2 merge somewhere along kernel 4.15
[07:00] <cpaelzer> I'm wondering which way to install a file to use
[07:00] <cpaelzer> dh_install doe sonly want to move, but not rename
[07:00] <cpaelzer> suggestions are made to dh-exec
[07:00] <cpaelzer> but I need mv + rename + chmod afterwards
[07:01] <cpaelzer> should I just go for a few lines in d/rules instead?
[07:30] <alkisg> Hi, some package in the Ubuntu archive has some security issue (details deliberately omitted) that ends up in all /home/*/.config folders being world-readable. Is it possible to reset that directory to its proper permissions for all users with a package upgrade, or is that prohibited by the Debian policy?
[07:31] <cpaelzer> alkisg: if it can be safely detected that the reason access is open is the bug in said package an update can fix it up I think
[07:31] <cpaelzer> alkisg: but otherwise I think it is bad to mess with access controls kind of unconditionally
[07:31] <cpaelzer> after all people might have set up the same intentionally
[07:31] <cpaelzer> therfore the "is it safe to detect" question
[07:32] <cpaelzer> in general LP bugs can be opened private + security which allos discussions on non disclosed security issues
[07:32] <alkisg> cpaelzer: very nice, where would you put the detect/restore login, in postinst or in an /etc/xdg/autostart script?
[07:32] <cpaelzer> alkisg: depends too much on the actual issue that caused it to answer, I'd expect a postinst actually
[07:33] <cpaelzer> as packages could be used on non graphical environments - so xdg/autostart would never trigger
[07:33] <alkisg> Hmm indeed, although they may also be installed when /home is unmounted :/
[07:34] <alkisg> Thanks, I think a private+security bug report might be the best place to discuss this
[07:48] <alkisg> I filed LP: #1745929.
[07:54] <valorie> alkisg: none of use will be able to look at it unless we're part of the security team
[07:54] <valorie> thanks for doing that
[07:54] <alkisg> valorie: the package maintainer (I assigned the bug to him) will still be able to see it, right?
[07:55] <valorie> that I don't know
[07:55] <Unit193> "Should"
[07:55] <alkisg> I think I've seen some security issues that were assigned to my packages in the past, so I believe so...
[07:55] <alkisg> (wrongly assigned to my packages :P :D)
[07:55] <valorie> I would assume that the maintainer will see the proposed patch at least
[07:56] <Unit193> My favorite are errors.ubuntu.com bugs, contain no info and just link to a place you can't view details (though to be fair, a quick poke and people usually are very willing to help by pasting stuff into the report.)
[08:10] <juliank> ugh, systemd-journal uses 100% CPU again.
[08:10] <juliank> ah / remounted r/o again
[08:10] <juliank> yay
[08:10] <Unit193> Why'd you do that?
[08:10] <Unit193> You're silly.
[08:11] <juliank> btrfs remounted itself r/o because it was "full"
[08:16] <juliank> And I'm back.
[08:16] <juliank> Rebooted, deleted a few snapshots of / and added another 100 MB to the LV it's on
[08:17] <juliank> now my vg has no free space left :(
[08:17] <juliank> I'm not sure I like btrfs remounting r/o when it's out of space
[08:19] <juliank> or journald going insane on CPU usage
[08:26] <alkisg> Remount-ro on errors sounds sane, 100% cpu, not so much
[08:34] <juliank> alkisg: well at least it helps you notice the problem!
[08:34] <alkisg> Haha, an effective way :D
[09:45] <juliank> jibel: I think I figured u-r-u / bug 1744722 out  https://code.launchpad.net/~juliank/ubuntu-release-upgrader/valid-release/+merge/336761
[09:46] <juliank> The goal was to check if the entry we are creating is valid. Checking that the dist is a valid toDist seems to be the right thing
[09:47] <juliank> Rather than just checking if the old entry was a valid old distribution
[09:48] <jibel> juliank, ok, but actually wouldn't the right fix to change the current entries to old-releases.u.c if it's a valid mirror?
[09:49] <jibel> then recheck if there is a basemetapackage and proceed with the upgrade
[09:49] <jibel> nowhere we tell the user that its release is EOL afaik
[09:51] <juliank> huh
[09:52] <juliank> Doesn't it look at the meta package for the target release?
[09:52]  * juliank not sure what it does
[09:52] <jibel> juliank, let me check again but I don't think so. I does the veirfication before rewriting sources.list
[09:52] <juliank> In any case this fix seems like a fixed variant of your fix
[09:53] <jibel> juliank, indeed, sounds good to me
[10:15] <juliank> jibel: So I'd merge and upload this then. Unfortunately, I don't see how we could SRU that to artful - we need a proper test case for it.
[10:16] <juliank> If only we had the sources.list
[10:17] <juliank> jibel: Ah, got a test case
[10:18] <jibel> juliank, we have the sources.list from the reporter. I'm testing your fix with his list
[10:19] <juliank> jibel: I added "deb https://dl.bintray.com/aluxian/deb/ stable main" to the test data which causes the problem to occur
[10:20] <juliank> It then generates deb http://archive.ubuntu.com/ubuntu stable main # auto generated by ubuntu-release-upgrader
[10:21] <juliank> It's not even that code generating that entry
[10:23] <juliank> Maybe I just ran the test wrong :D
[10:24] <juliank> Yeah, it works
[10:28] <juliank> or not
[10:28] <juliank> well it also worked before
[10:33] <jibel> juliank, for the test you need a valid mirror with an obsolete release and an entry with a third part repo eg a ppa
[10:33] <jibel> third party*
[10:37] <juliank> jibel: I'm trying to write a test case for it, but I have not found anything that breaks yet
[10:39] <juliank> It breaks and fixes when I run tests/test_sources_list.py manually, but if I run via nose-tests it works in both cases.
[10:39] <juliank> the test suite is of course, somewhat broken, as usual.
[10:40] <juliank> (if you run tests with python-apt, you basically have to run apt_pkg init at least in a setupClass or something)
[10:40] <juliank> otherwise some state might stick around from other tests
[10:45] <juliank> Oh, my test case is broken.
[10:45] <juliank> # deb https://dl.bintray.com/aluxian/deb/ stable main # disabled on upgrade to gutsy
[10:45] <juliank> is there all the time
[10:45] <juliank> but before, there also is
[10:45] <juliank> deb http://archive.ubuntu.com/ubuntu stable main # auto generated by ubuntu-release-upgrader
[10:54] <juliank> there are a ton of bugs in the test suite because we only check that the expected sources are there, not any unexpected
[11:02] <juliank> jibel: I added/modified a test case now in https://code.launchpad.net/~juliank/ubuntu-release-upgrader/valid-release/+merge/336761 and verified that it was broken before and passes now
[12:27] <jbicha> xnox: please open a new bug for your comment at LP: #400573
[12:33] <xnox> jbicha, the comment was on purpose, such that people who are subscribed to that bug get the notification. As I was trying to reach them. If there is no responses there for a while, I will be opening a brand new bug to "demote" wvdial.
[12:34] <jbicha> could you go ahead and open that bug now? :)
[12:35] <jbicha> I am a fan of demoting/removing stuff earlier in the release cycle if possible so there's more time to notice problems :)
[12:40] <tsimonq2> xnox: I'll pull the OpenSSL 1.1 patch in during the Qt 5.9.4 transition I'm currently prepping in Bileto if that's OK?
[12:43] <xnox> tsimonq2, if that does dual-build, where the qt builds with either openssls, then yes, please.
[12:43] <xnox> tsimonq2, if it does "require openssl1.1.0 only" then that would obviously will ftbfs.
[12:44] <xnox> tsimonq2, still discussing when and how to introduce openssl1.1.0
[12:45] <tsimonq2> xnox: ok, I'll take a closer look later and let you know
[12:45] <xnox> tsimonq2, tah!
[13:04] <sforshee> doko: this is from your test rebuild - https://launchpadlibrarian.net/353098637/buildlog_ubuntu-bionic-arm64.linux_4.13.0-17.20_BUILDING.txt.gz
[13:58] <doko> sforshee: ohh, it's in superseded section :-/  does 4.15 build?
[14:03] <sforshee> doko: I don't think I've tried 4.15 yet with that binutils, will test
[14:04] <doko> sforshee: maybe wait for the final 2.30, once it's built
[14:04] <sforshee> ack
[14:07] <juliank> doko: ld from proposed segfaults on armhf trying to build systemd: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3114/+build/14286752
[14:07] <juliank> it also does not build on i386 or arm64
[14:08] <juliank> i386: /usr/bin/ld: /tmp/ccp5bmno.ltrans0.ltrans.o(.text+0x3362): unresolvable R_386_PLT32 relocation against symbol `__udivdi3'
[14:08] <juliank> arm64: ld: /usr/lib/crt0-efi-aarch64.o: relocation R_AARCH64_ABS16 against `EFI_SUBSYSTEM' can not be used when making a shared object
[14:12] <jibel> could someone re-run the failed autopkgtest for network-manager on ppc64el https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#network-manager
[14:17] <seb128> jibel, done
[14:17] <jibel> seb128, thanks
[14:17] <seb128> yw!
[15:32] <ginggs> How can I figure out why the build-dependencies of hwloc-contrib and eztrace-contrib are not installable?
[15:44] <seb128> xnox, slangasek, is systemd/persistant log something you are (still?) looking at for the LTS?
[15:44] <seb128> there was an ubuntu-devel@ list discussion but it didn't get any real traction
[15:44] <xnox> seb128, it's enabled, not sure if it has migrated yet.
[15:45] <seb128> xnox, oh ok, might be good to follow up on that list discussion to say that then :)
[15:45] <seb128> good news
[15:45] <xnox> ack
[15:45] <seb128> yeah, looks like it migrated
[15:51] <LocutusOfBorg> juliank, https://sourceware.org/bugzilla/show_bug.cgi?id=22751 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888478 :)
[16:25] <juliank> cpaelzer: Oh, you updated sanlock. Now we just need to get it into main
[16:25] <juliank> lvm2 wants it :(
[16:32] <cpaelzer> juliank: well I didn't want ti MIR it
[16:33] <cpaelzer> juliank: I just wanted to make it somewhat usable
[16:33] <cpaelzer> like able to install :-)
[16:33] <juliank> cpaelzer: :)
[16:33] <cpaelzer> juliank: it didn't seem MIR-worth to me when I looked at the code this afternoon
[16:33] <cpaelzer> juliank: could you go without in lvm2 ?
[16:34] <juliank> cpaelzer: Well lvm2-lockd needs it. some people want lvm2-lockd.
[16:35] <GunnarHj> doko: Did you see my ping at #ubuntu-desktop?
[16:35] <GunnarHj> https://irclogs.ubuntu.com/2018/01/29/%23ubuntu-desktop.html#t12:31
[16:35] <juliank> cpaelzer: nacc knows more about that https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986
[16:36] <juliank> cpaelzer: But I'm sure we'll figure something out eventually
[16:36] <juliank> We could also demote lvm2-lockd to universe
[16:36] <juliank> but I don't want to decide that :D
[16:44] <TJ-> juliank: Yes, we very much would like lvm2 with proper lock support, several users of it
[16:44] <TJ-> juliank: nacc took it on when we dealt with it recently
[16:50] <juliank> TJ-: Right. It will go to universe it seems, unless a team MIRs it.
[16:52] <TJ-> juliank: that'll be good; saves having to maintain a custom build :)
[16:55] <slangasek> xnox: you've enabled persistent log in systemd?  What steps have you taken to avoid double-logging to syslog?
[16:55]  * juliank thinks double logging sounds like a good idea for now
[16:57] <juliank> Well, at least you don't lose logs that way :)
[17:24] <bbear> you can still double lose them.
[17:57] <tsimonq2> kor
[17:57] <tsimonq2> (mistype)
[18:02] <xnox> slangasek, given that one has full timestamps, and the other one does not, i choose to keep data.
[18:03] <xnox> slangasek, let's talk about enabling nano-timestamps in syslog by default, and thus breaking everyone's syslog parsing regexp-es? aka all the logwatch / graylisting things.
[18:03] <xnox> slangasek, and enable journald module of syslog by default
[18:09] <slangasek> xnox: the full timestamps are in the journal, yes?  I'm not saying we shouldn't do the persistent journal, I'm asking how we get rid of the duplication of data that is syslog
[18:13] <xnox> slangasek, well, imho we currently have dataloss since `systemclt status` and `journalctl` do not read syslog files and the user gets the "no logs available" messages and/or incomplete output.
[18:13] <xnox> slangasek, imho syslog should be pulling data from journal using the journald module that it has.
[18:14] <slangasek> xnox: I think you're misunderstanding my objection
[18:14] <xnox> slangasek, I think you are misunderstanding our users =)
[18:14] <slangasek> enabling persistent journal - yes, +1
[18:14] <xnox> slangasek, all of our users want more logs, not less.
[18:14] <slangasek> still having data logged to syslog, causing redundant disk usage - -1
[18:14] <xnox> well.
[18:15] <xnox> slangasek, our users expect to have both plain text logs; and useful `systemctl status` output.
[18:15] <xnox> i have as many people shouting at me that we shall not remove plain text logs; and that we should have complete journals across reboots.
[18:15] <xnox> slangasek, note that xenial's journalctl fails to read bionic's .journal files =/
[18:16] <slangasek> xnox: so I'll gather a bunch of people on my side to also shout about the wasted disk space ;-)
[18:16] <xnox> and everything can read plain text syslog.
[18:16] <slangasek> and then it'll be well-balanced
[18:16] <xnox> slangasek, disk space is not wasted, as logs are rotated.....
[18:17] <xnox> slangasek, oh, i totally do have roughly equal amount of people shouting at me about all the logs and disk space =)
[18:17] <xnox> at the moment, keep everything prevents dataloss.
[18:17]  * xnox .... log-loss?
[18:19] <xnox> slangasek, do you know of a way to support 1) plain text logging 2) remote syslog logging 3) full journals -> without duplication?
[18:20] <alkisg> Plain text logging isn't very important if there's a command that can display plain text output...
[18:20] <slangasek> xnox: nope :)
[18:20] <xnox> slangasek, cause to have full remote logging journal should be pushed to syslog, and to not have duplicate disk space somehow plain text syslog and journal should be picked for some/all/split logs.
[18:22] <slangasek> xnox: right - so rsyslog has all kinds of clever filtering, and I think it would be appropriate for us to configure rsyslog by default to not write to disk logs that systemd is also writing to the journal
[18:22] <slangasek> while having systemd continue to /send/ them to syslog, for remote logging etc
[18:23] <xnox> slangasek, interesting.
[19:03] <jbicha> !dmb-ping