[10:44] <vir17> hi, anyone know how to install wireless in ubuntu snappy xenial?#
[11:40] <ogra_`> vir17, everything you need should be there, just create a wlan0 (or however your device is called) file in /etc/network/interfaces,.d
[12:13] <vir17> thank you ogra_`
[12:14] <vir17> i suppose within classic shell?
[12:14] <ogra_`> nope, directrly in snappy
[12:14] <ogra_`> here is an example of the syntax http://people.canonical.com/~ogra/snappy/dragonboard/README
[12:16] <vir17> perfect, I will try it
[12:16] <vir17> :)
[12:22] <vir17> and another stupid question
[12:22] <vir17> i use touch to add wlan0 file
[12:23] <vir17> but I dont know how to add data inside this file
[12:23] <ogra_`> use vi :)
[12:23] <vir17> i have nano instal
[12:23] <vir17> but i get permission denied
[12:23] <ogra_`> sudo vi /etc/network/interfaces.d/wlan0
[12:24] <vir17> sorry nano is for classic
[15:36] <anpok_> i now get signature verification failed when trying a install a snap.. even when using --allow-unauthenticated
[15:36] <anpok_> s/a/to
[15:50] <renat> Hi all! It's Renat from Screenly.
[15:50] <renat> I need a help with snapcraft.
[15:51] <renat> For the some reason, when it ask it to build for armhf acrh, - it builds for x86_64 arch.
[15:51] <renat> It generates armhf snap, but inside there are x86 executables.
[15:51] <renat> And I cannot execute them on the RaspberryPI=(
[16:09] <anpok_> i guess I should rather ask .. how does snapcraft sign snaps?..
[16:10] <anpok_> renat: hm i tinkered with cross compiling snaps.. but couldnt manage to solve the problem you describe..
[16:11] <anpok_> maybe time for a bug report...
[16:11] <renat> anpok_I don't need to cross-compile. It used to work as I rememeber. I just need to run a python script.
[16:11] <anpok_> I am now building on one of my boards in a chroot env on a decent sata drive
[16:12] <renat> anpok_ : Sign - you mean - install without --allow-unauthenticated ?
[16:14] <anpok_> hm yeah that used to work
[16:14] <anpok_> i updated to newest snapcraft and updated the system image today
[16:15] <anpok_> now i get verification failed with exit status 14
[17:26] <ogra_`> anpok_, snapcraft doesnt sign them at all, only the store does, if you have locally build snaps you always need (and needed) --allow-unauthenticated
[17:27] <ogra_`> could it be that you used the snappy-remote script in the past (that sets the option by default when installing) ?
[17:33] <anpok_> hm no only found out about snappy-remote today..
[17:33] <anpok_> could it be that the snappy update failed
[17:35] <ogra_`> snappy list would tell you
[17:36] <anpok_> hm still the old one
[17:36] <anpok_> i guess i need something newer than september 2015 to work with current snaps
[17:36] <ogra_`> snapcraft 2.0 needs xenial/rolling
[17:37] <ogra_`> only 1.0 works with 15.04
[17:37] <renat> ogra_: hi! It's Renat from Screenly.
[17:37] <renat> I have a question=)
[17:37] <ogra_`> i see it above :)
[17:37] <ogra_`> i dont think you can build armhf snaps on non armhf systems yet
[17:37] <renat> Is it possible to build armhf snap on the amd64 ubuntu?
[17:37] <anpok_> ogra_`: something like: release: ubuntu-core/15.04/edge
[17:38] <ogra_`> anpok_, thats the non QAed build of 15.04 ... before it goes to the stable channel
[17:38] <ogra_`> (and can only use snapcraft 1.0 binaries)
[17:39] <renat> ogra_: understood. Thanks. So I need an other ubuntu. For example Trusty for Rpi.
[17:39] <ogra_`> if you target xenial (16.04) then you can build on your snappy system
[17:40] <ogra_`> the 16.04 images have the "classic dimension" ... i.e. a container thats shipped by default to enable you to use apt
[17:40] <ogra_`> sudo snappy enable-classic
[17:40] <ogra_`> snappy shell classic
[17:40] <ogra_`> ...
[17:40] <ogra_`> and you anc atp-get install what you need
[17:40] <ogra_`> (i.e. snapcraft to do native armhf builds)
[17:41] <ogra_`> note though that this obnly works in 16.04 images
[17:41] <anpok_> ogra_`: is there an easy way to get to get to xenial?
[17:41] <ogra_`> no
[17:42] <ogra_`> well, as easy as re-flashing :)
[17:42] <anpok_> hehe
[17:42] <ogra_`> there is no update path
[17:42] <anpok_> ok .. guess it is time to learn that
[17:42] <ogra_`> just use ubuntu-device-flash to roll an up to date image :)
[17:47] <anpok_> i guess I could reuse the device part from lemaker ..


[19:36] <tsimonq2> Any idea regarding s390x builder sadness?
[19:36] <tsimonq2> Quite a few builders seem to be cleaning for a couple of days.
[19:59] <arraybolt3> tsimonq2: Did you see ahasenack and paride's emails on DEP8 timeouts?
[20:00] <arraybolt3> tl;dr: a couple of datacenters are somehow downloading data at about 100 kB/s.


[05:01] -lugito:#lubuntu-devel- [rCALAPACKAGING9c0fb84fdf67: No-change rebuild against libkpmcore11] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rCALAPACKAGING9c0fb84fdf67
[05:01] -lugito:#lubuntu-devel- [rCALAPACKAGING32e7a538598f: Merge branch 'ci/stable' into ci/unstable] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rCALAPACKAGING32e7a538598f
[05:02] -lugito:#lubuntu-devel- [rMANUAL361b2ea4368f: Remove paragraph and screenshot for boot screen removed in installer] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL361b2ea4368f
[05:03] -lugito:#lubuntu-devel- [rMANUALc3cd6add2c85: Remove uneeded space] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALc3cd6add2c85
[05:03] -lugito:#lubuntu-devel- [rMANUALdae0cab3bfc1: Remove paragraph and screenshot for boot screen removed in installer] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALdae0cab3bfc1
[05:04] -lugito:#lubuntu-devel- [rCALAPACKAGING7ddedf462b8a: build with arch any] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rCALAPACKAGING7ddedf462b8a
[05:04] -lugito:#lubuntu-devel- [rCALAPACKAGINGdef22da757bc: Merge branch 'ci/stable' into ci/unstable] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rCALAPACKAGINGdef22da757bc
[05:05] -lugito:#lubuntu-devel- [rMANUAL0f8e9da1784d: Add snap back into alignment sentence to monitor settings] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0f8e9da1784d
[05:27] -lugito:#lubuntu-devel- [Lubuntu CI] merger_sddm FAILURE: https://ci.lubuntu.me/job/merger_sddm/321/
[05:27] -lugito:#lubuntu-devel- [Lubuntu CI] merger_calamares just succeeded after failing: https://ci.lubuntu.me/job/merger_calamares/813/
[05:58] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/450/
[05:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/172/
[05:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/529/
[05:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/529/
[05:58] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/655/
[05:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/308/
[05:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/671/
[05:59] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/451/
[06:23] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/656/
[06:23] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/173/
[06:23] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/309/
[06:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/672/
[06:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/672/
[06:25] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/753/
[06:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/608/
[06:25] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/272/
[06:45] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/752/
[06:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/754/
[06:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_libfm-qt/754/
[06:48] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/608/
[06:49] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt just failed after being unstable: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/273/
[06:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/753/
[07:10] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/380/
[07:10] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/163/
[07:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/601/
[07:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/602/
[07:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/602/
[07:15] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_lximage-qt/753/
[07:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-config/441/
[07:24] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/164/
[07:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/768/
[07:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/768/
[07:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/768/
[07:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-config/441/
[07:39] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/380/
 Congrats and thanks to everyone who helped with hirsute. Is it just me or hirsute hippo cycle felt a lot longer than earlier ones? Also, whee! Impish is here.  I suspect for me kgiii testing live extensively meant I felt less need to (opening all apps etc isn't fun..) but it's probably a lot more than that
 Every new release should be a challenge and of course an improvement.. (re @The_LoudSpeaker: Congrats and thanks to everyone who helped with hirsute. Is it just me or hirsute hippo cycle felt a lot longer than earlier ones? Also, whee! Impish is here. Hit me up if any help is required anywhere.)
[13:15] <kgiii> @guiverc is correct. Opening all the apps isn't a whole lot of fun. But, at least it means I learn new things. So, it has that going for it!
 Idk. I just felt like it was a lot of time. Tho i know it was essentially same as every other release.
 Things have been waay slow or waay fast lately. Sometimes days just don't seem to end. And sometimes they end up so fast.
 Wierd times.
 Was a weird one for me, as for almost half the time the Kubuntu installer was broken
 Also FYI there is something weird going on in the impish archive. packages that are 'Architecture: linux any' don't seem to be building for riscv64, whereas they did before.
 so they get blocked in excuses
 Since this is the start of a new cycle, maybe  I should set the target of being involved by the time its released. Where's the best place to get started as a noob?
 Not sure lubuntu has many of those, but FYI in case you hit one
[15:54] <kgiii> @acor_uk, testing is a good spot to start. You just look for things that don't work like they should and file reports when you find something broken. It can be a bit meticulous and repetitive, but it's a service that needs doing and is easy enough for me to do it.
[15:55] <The_LoudSpeaker> @acor_uk if you can write some small programs then https://phab.lubuntu.me/w/lubuntu-dev/new-code/ is also a good place. But should be familliar with https://phab.lubuntu.me/w/packaging/ first.
[15:56] <The_LoudSpeaker> also, teward bhaiya phab doesn't allow people without @ubuntu.com email addresses to sign up?
[15:59] <The_LoudSpeaker> A debian maintainer was trying to sign up.
[15:59] <The_LoudSpeaker> ManasKashyap.
 @The_LoudSpeaker @kgiii Thanks, I can probably eventually turn my hands to small programmes or debgging, but my languages are php, js, python so probably will need to learn something c-based first?Happy to find bugs first though.
[16:08] <The_LoudSpeaker> some of those things which are noted as c++ in the new code required section can be done in python too. no restrictions as long as it is cpp or python. feel free to try anything that interests you. Don't hold back because cpp is written there.
[16:10] <kgiii> Yeah, just put it out there that you're willing to learn and willing to help. They'll find a way to make your hours useful. It needn't be testing. Someone will find something useful for you to do. Bug hunting is pretty boring and tedious work.
 I'm a meticulous type of person so bug hunting can sometimes be therapeutic I think ha ha
 @lynorian I forgot to mention that we need to add in the GNU Grub 2.04 menu - (re @lynorian: @Leokolb thanks)
[16:58] <teward> @The_LoudSpeaker: registration on phab was shut for now from random addresses due to insane registration volume of spammers.  Council decision.  We can individually register users by hand but they need to request it from the Council right now
[16:59] <teward> so we restricted to ubuntu.com and lubuntu.me addresses for now i believe.  have to double check the settings
[17:02] <teward> i may be able to add debian addresses to permitted but it requires council vote.
[17:02] <teward> wxl: kc2bez[m]: ^^ to start with
[17:05] <kc2bez[m]> I replied in the council chat @teward001
[18:39] <The_LoudSpeaker> yeah. debian addresses should be considered. Let me know if they are approved. else I will ask him to send a request to council.


[01:03] <pochu> good night folks!
[02:16] <nhandler> While reviewing packages on REVU, I came accross one that follows http://wiki.debian.org/Proposals/CopyrightFormat?action=recall&rev=196 for debian/copyright. Is this ok? Or should I have them switch to the more traditional style?
[02:17] <ScottK-laptop> nhandler: Those are fine.
[02:18] <nhandler> ScottK-laptop: Ok, I just wanted to make sure since I hadn't seen a copyright like that before
[02:18] <ScottK-laptop> Some people are a real fan of it.
[02:59] <nhandler> If a program is distributable but not modifiable, can it enter multiverse?
[03:06] <ScottK> nhandler: Yes.
[03:07] <nhandler> Thanks ScottK
[04:52] <AnAnt> Hello, can someone look at this merge request: bug 305124
[05:23]  * invaleed is away (Please give me hug)
[05:25] <jdong> Hobbsee: ^^
[05:25] <jdong> I think it's removal time...
[05:25] <wgrant> Yes.
[05:25] <wgrant> A very nice hug it will be.
[05:26] <wgrant> jdong: Can we backport python3.0?
[05:26] <jdong> wgrant: what does doko think?
[05:26] <wgrant> jdong: No idea. But it has no rdepends...
[05:26] <jdong> if it installs side by side correctly, I think that would be pretty cool to backport
[05:26] <wgrant> We already have rc3 in Intrepid.
[05:26] <jdong> but since I know /dev/null about python packaging, I'd like to have someone who knows what they're doing weigh in :)
[05:27] <jdong> I know we have rc3 in Intrepid but I want to make sure nothing changed significantly in jaunty
[05:27] <wgrant> Right.
[05:27]  * jdong has a feeling that he needs to have a firefox-3.1 talk of similar nature in the near future :)
[05:27] <wgrant> Firefox 3.1 breaks subpixel rendering :(
[05:27] <ScottK-laptop> wgrant: doko already said no.
[05:27] <wgrant> ScottK-laptop: Aw, why?
[05:28] <ScottK-laptop> We'll have it in intrepid-updates.
[05:28] <wgrant> Ah.
[05:28] <wgrant> Good enough reason.
[05:28] <jdong> ScottK-laptop: ah, even cooler :)
[05:28] <ScottK-laptop> Hardy, we aren't supporting.
 what irony...
[05:28] <jdong> the day I do a lengthy blogpost raving about the benefits of AppArmor...
[05:28] <ScottK-laptop> It's not like Python 3.0 will be good for anything but experimental use for quite some time.
[05:29] <jdong> KDE4.2 installed a restrictive apparmor profile that I spent 20 mintues tweaking :)
[05:29] <ScottK-laptop> jdong: For which package?
[05:29] <jdong> the mysqld config backend thingie
[05:29] <ScottK-laptop> Right.
[05:29] <ScottK-laptop> Akonadi.
[05:30] <ScottK-laptop> It's actually a mysql profile.
[05:30] <jdong> for my encrypted-private-directory setup apparmor chokes on it
[05:30] <ScottK-laptop> Interesting.
[05:30] <ScottK-laptop> I'd imagine jdstrand would be interested in that one.
[05:30]  * wgrant decides he should pack at some point.
[05:31] <jdong> I needed rwk for not just ${HOME}.local/share/akonadi/**, but ${HOME}/Private and ${HOME}/.Private/local/share......
[05:31] <jdong> which makes sense due to the way ecryptfs has an upper and lower layer
[05:31] <jdong> and IMO Ubuntu needs to port over Suse's AppArmor troubleshooter
[05:32] <jdong> it took me a while to realize that AppArmor was causing the problem
[05:33] <ScottK-laptop> jdong: Would you please file a bug against akonadi with your information?
[05:33] <ScottK-laptop> Please susbcribe me to it.
[05:33] <jdong> will do.
[05:34] <ScottK-laptop> Thanks
[05:37] <jdong> ScottK-laptop: done (bug 305669); subscribed
[05:38] <ScottK-laptop> jdong: Thanks.
[05:38] <jdong> sure thing
[08:26] <AnAnt> Hello, can someone help me with a bug fix ? I am trying to fix debian bug 507340
[08:27] <AnAnt> to fix the problem for those upgrading sl-modem, I did 'usermod --home /var/log/slmodemd Slmodemd' in postinst
[08:27] <AnAnt> now , when I install the package (even for the first time), this usermod gives a Seg fault
[08:27] <AnAnt> yet dpkg does continue installing it
[09:11] <jonnymind> Hello
[09:33] <keymone> hi
[09:34] <keymone> i tried apt-build with O3 but still some packages are being built with O2 - why would that happen?
[11:25] <cliffbreaker_> hi everyone. Try to build a package from source and it gives an error (when using debuild -S -sa) -  make: *** No rule to make target `clean'. Stop. How can I fix it?
[11:25] <azeem> you need to add a clean target
[11:26] <azeem> it's required
[11:26] <azeem> cliffbreaker_: how did you create your debian/rules?
[11:26] <cliffbreaker_> azeem: well, I understand that. How do I do that - I'm a newbie, sorry, just trying to build my first package
[11:27] <cliffbreaker_> I used dh_make and it was generated
[11:27] <azeem> dh_make generates a clean rule, why did you remove it?
[11:28] <cliffbreaker_> well i didn't. I didn't change anything there. It's present and the section containing a clean rule is there
[11:29] <azeem> cliffbreaker_: post your rules file on a pastebin then
[11:29] <cliffbreaker_> ok
[11:39] <cliffbreaker> azeem: http://paste.org/index.php?id=4411
[11:42] <azeem> cliffbreaker: can you also pastebin the whole output of debuild -S -sa?
[11:42] <azeem> cliffbreaker: otherwise, the only thing I can think of is tab/space mangling in rules maybe, so that make gets confused
[11:43] <cliffbreaker> azeem: ok, but it is half russian)
[11:44] <azeem> cliffbreaker: run it with LANG=C in front
[11:45] <cliffbreaker> azeem http://paste.org/index.php?id=4413
[11:45] <cliffbreaker> oh, just a minute
[11:45] <RainCT> sebner: you haven't reviewed anything yet :(
[11:46] <sebner> RainCT: is it still friday somewhere?
[11:46] <cliffbreaker> azeem: http://paste.org/index.php?id=4414  - here it is
[11:46] <RainCT> sebner: yep, iirc it's still REVU Day for 2 hours or so
[11:47] <sebner> RainCT: well, I have to go off now *but* today I'll review something ;)
[11:47] <azeem> cliffbreaker: ohhhh
[11:47] <azeem> cliffbreaker: sorry
[11:48] <cliffbreaker> azeem: for what?)
[11:48] <azeem> cliffbreaker: the problem is that the clean rules exists, but runs "make clean", but either there is no Makefile in the upstream source, or it does not contain a clean rule
[11:48] <azeem> so this is not about debian/rules but Makefile
[11:48] <azeem> cliffbreaker: is there a Makefile.in?
[11:49] <cliffbreaker> i'll have a look
[11:50] <cliffbreaker> azeem: well there is none
[11:51] <azeem> cliffbreaker: what kind of project is it?
[11:52] <cliffbreaker> it is deluge-torrent. It has no makefile - just setup.py . Seems to use python
[11:52] <azeem> cliffbreaker: this is a prime example why you should not just use the dh_make debian/rules per se, it usually needs to be adopted to the project you're packaging
[11:52] <azeem> cliffbreaker: ok, so you need to rewrite debian/rules
[11:53] <cliffbreaker> azeem: well. It seems quite a task for me) could you please give me any hints?
[11:53] <azeem> look at other python packages
[11:54] <cliffbreaker> azeem: well I don't seem to understand what to do, sorry(( just used the instructions provided by MOTU
[11:59] <DktrKranz> Does anybody notice a "connection refused" error while uploading to PPAs?
[12:00] <DktrKranz> now it's working, probably it was just me
[12:00] <Hobbsee> DktrKranz: no, it was broken
[12:01] <DktrKranz> cool
[12:01] <Hobbsee> (and was fixed)
[12:32] <gnomefreak> we should either remove iceweasel-linky from archives or add firefox and friends to the depends. does anyone have an idea on what is better? ill be glad to fix it if needed
[12:34] <Hobbsee> gnomefreak: s/firefox/abrowser/
[12:34] <Hobbsee> (if you go that route)
[12:34] <gnomefreak> Hobbsee: yeah i was gonna add all that we use with extensions just not sure if removing it or adding deps would be best
[12:40]  * gnomefreak will work on it monday.
[12:41] <directhex> does it need firefoxish, or xulrunner? :p
[12:46] <iulian> directhex: Hey, I see that a lot of CLI apps are not yet uploaded to experimental. Is meebey lazy? ;-)
[12:47] <directhex> iulian, no comment!
[12:47] <iulian> I agree with you.
[12:47] <directhex> iulian, was giver successfully transitioned? it's still in red - if it's waiting on meebey it should go yellow
[12:47] <iulian> directhex: Oh really? Didn't know that.
[12:47]  * iulian wonders how to change the colour.
[12:48] <iulian> Lemme have a look at the wiki.
[12:48] <iulian> And yes, it's done already.
[12:48] <directhex> iulian, as for laziness, i've been bugging him for something which IMHO is higher priority: a new mono version for lenny to fix an RC bug
[12:49] <directhex> which is done now. 1.9.1+dfsg-5
[12:49] <directhex> it might be worth a SRU for the same bugfixes for intrepid, but i'm not gonna open that can of worms myself
[12:49] <iulian> Aha
[12:49] <iulian> directhex: How do you change the colour?
[12:50]  * iulian was using the GUI mode.
[12:50] <directhex> iulian, i'll do it then. i assume gui modes break things ;)
[12:51] <iulian> directhex: OK then, but I still want to know how to change the colour :)
[12:51] <iulian> Ah, got it.
[12:52] <iulian> You cannot change the colour when using the GUI.

[12:52] <directhex> yeah. apprently the gui sucks then :)
[12:52] <iulian> Indeed
[12:57] <iulian> Hey mok0.
[13:05] <gnomefreak> directhex: it only needs to be dependant on browsers because the browsers will bring in xulrunner-*
[13:05] <gnomefreak> sorry for late reply im working on something
[13:06] <directhex> gnomefreak, right..... but if it works in all the browsers, you could depend on xulrunner-1.9. that way on debian or ubuntu it'd work in FF, iceweasel, abrowser, etc etc etc
[13:07] <gnomefreak> iirc xulrunner doesnt bring in browsers
[13:08] <gnomefreak> it doesnt depend on browsers but the other way around
[13:09] <gnomefreak> i see icedtea was renamed
[13:20] <directhex> gnomefreak, exactly. unless you want the | from hell in your depends, the way to offer an extension to all browsers is via depending on xulrunner
[13:20] <directhex> gnomefreak, if it CAN'T be used by all browsers, then, well, welcome to | city
[13:27] <gnomefreak> i wont know anything until i get around to looking at the *.rdf to find out what browsers it supports
[14:41] <mok0> (two hours later) Oh, hi iulian :-)
[15:45] <StevenHarperUK> Hi, I am looking for a member of the SRU Team please
[15:47] <Elbrus> Can anybody imagine a reason why you want to have the clean target depend on the configure and/or patch target
[15:47] <nixternal> superm1: hey dude, are you in the same hotel as everyone else? I get in tomorrow at about 5pm there, so I will look you up if you are around
[15:47] <azeem> Elbrus: maybe so you can run make distclean, for a autotools package
[15:48] <azeem> though I don't think that makes a lot of sense
[15:49] <Elbrus> it does have "make XXX_distclean" lines
[15:54] <hefe_bia> Hi! Anybody care to review http://revu.ubuntuwire.com/details.py?package=tomboy-blogposter ? Had one advocate and all the outstanding issues should be fixed now. I'd be happy ;)
[15:56] <AnAnt> when's the UDS ?
[15:59] <pochu> AnAnt: from Monday to Friday
[15:59] <StevenHarperUK> OK, looks like no SRU's about : if any read this (from logs) can you have a look at https://bugs.edge.launchpad.net/ubuntu/+source/easycrypt/+bug/293903 it needs processing : thanks a lot
[15:59] <AnAnt> I see
[15:59] <AnAnt> pochu: thanks
[16:55]  * invaleed is away (Please give me hug)
[17:34] <jdong> sigh I am a total idiot :)
[17:34] <jdong> did you know that drag-drop Nautilus doesn't work well with iTunes?
[17:35] <jdong> I guess the joke's on me for having a full GNOME stack on OS X then accidentally using gnome-open when I should've used open.
[18:55] <Skiessi> aika hiljasta
[19:51] <jdong> yikes that's my 2nd time being an idiot today.
[19:51] <jdong> this time almost dpkg -i'ed something onto my Mac
[19:54] <mok0> jdong: fink uses dpkg
[19:55] <jdong> mok0: yeah to some degree it does, though I just happen to have dpkg installed from macports
[19:55] <jdong> along with yum and rpm (don't ask; lots of fun)
[19:56] <mok0> Oh, I see
[19:56] <mok0> I use fink on my mac
[19:56] <jdong> I use macports; somehow I've found packages in there to be better maintained.
[19:56] <jdong> could just be the specific packages i use at specific moments in history that gave me that impression though
[19:57] <jdong> ordinarily I would bias towards fink just because it uses dpkg/apt, but I was disappointied to find that only true for the binary packages.
[19:57] <rww> i tried using fink a few times, but it somehow always seemed to mess up and break things :(
[19:57] <mok0> jdong, Hm, my impression is there are alway update
[19:57] <jdong> the source building system is *still* a ports-like build script backend
[19:57] <jdong> not debhelper/debuild
[19:57] <mok0> rww, just rm -rf /sw and start over :-)
[19:57] <jdong> rww: glad I'm not the only one that experiences that!
[19:57] <jdong> mok0: my macports tree has lasted me since 10.4.10
[19:58] <jdong> minor rebuilding here and there to keep ABIs from breaking
[19:58] <jdong> and I have all of GNOME, KDE4, and mono installed from macports too
[19:58] <jdong> I've been told that I don't use my Mac correctly...
[19:58] <mok0> What annoys me is that you always have to build the packages
[19:59] <jdong> yeah IMO it wouldn't KILL them to build fairly up to date packages.
[19:59] <jdong> macports and fink.
[19:59] <mok0> which means you need to install all the build-deps in addition to the actual deps
[19:59] <jdong> these systems don't differentiate between -dev and -bin
[19:59] <mok0> jdong: exactly
[19:59] <jdong> it is somewhat of a waste of space.
[19:59] <jdong> I've not heard ANY good arguments why this is better
[20:00] <jdong> other than it promotes lazy packaging and makes it easier to "install the stupid -dev packages" (not my words)
[20:00] <mok0> The Gentoo people claims that it's faster; I don't believe that
[20:00] <mok0> jdong: actually, in fink there _are_ dev packagees
[20:01] <jdong> it might possibly be faster.
[20:01] <jdong> but in reality IMO only a handful of packages benefit from such optimization.
[20:01] <jdong> not the entire system blindly
[20:02] <jdong> and neither fink nor macports ships with any kind of optimizing CFLAGS by default
[20:02] <mok0> jdong, of course you can optimize for your Athlon or K8 or whatever
[20:02] <jdong> not to mention you *KNOW* all Mac hardware are Core Duos with SSE2,SSE3,MMX anyway.
[20:02] <jdong> the greatest common denominator is already large enough that additional CFLAGs wouldn't matter much on top of that
[20:03] <mok0> jdong: except, just the time it takes to compile gcc easily makes up for any speed-gains in the next 100 years
[20:05] <rww> mok0: hence me not using gentoo
[20:12] <mok0> rww: yeah binary packages... woot
[20:17] <retour> How to format/erase DVD-RAM under ubuntu
[20:17] <jdong> (1) this is not a support channel
[20:17] <jdong> (2) DVD-RAM should show up as a regular block device at /dev/dvd
[20:18] <jdong> you can use mkfs just as if it were a hard drive.
[20:19] <rww> retour: you probably want #ubuntu ;)
[20:22] <retour> Sorry but I tried Ubuntu/Xubuntu chanels - no answers. I'm ignored. I've got DVD-RAM disks that were used in portable DVD player/recorder and 50% of the capacity is used by something nonvisible to me. Additionaly every DVD when automunts gives me errors because of a bug with access rights. I can aonly watch/access DVD's as root
[20:23] <jdong> well being ignored in #ubuntu is not really an excuse to take t he topic into a channel that is not meant for support issues
[20:23] <jdong> speaking of support, the issue at hand is Ubuntu really does not support DVD-RAM and DVD+RW writeable optical media
[20:24] <jdong> the system mounts optical media read-only and not owned by the user in its default rules anyway
[20:26] <retour> OK sorry. Just read what Masters chanell really is. Bye!
[20:42] <jdong>       printf ("%g %f %f MB\n", f, f, f/1024000);
[20:42] <jdong> *blinks*
[20:42] <jdong> what the hell kind of byte is that?
[20:42] <jdong> a MixiByte?
[20:43] <jdong> the last time I've seen that definition was with 1.44MB floppies
[21:25] <hefe_bia> Hi! Anybody interested in reviewing tomboy-blogposter, a small utility to blog about Ubuntu (and other topics) from Tomboy? ;) It's been advocated by mok0 and I think I have corrected all issues mentioned by dktrkranz. See http://revu.ubuntuwire.com/details.py?package=tomboy-blogposter
[21:25] <hefe_bia> I'll be here for feedback...
[23:31] <goshawk> hi
[23:32] <goshawk> if someone has free time, can please review http://revu.ubuntuwire.com/details.py?package=dsss ?


[02:52] <Sp0tter> does ubuntu support the Archos 32 hardware?
[02:54] <tmzt> what is the archos 32 hardware?
[02:54] <rcn-ee> ubuntu supports the cortex a8 'architecture' of the archoes 32, you'll have to either find someone who did the kernel, or do it yourself..
[02:54] <ScottK-droid> ogra_ac: Qt finally built so FTBFS should start improving.
[02:56] <tmzt> Neko: you should be able to add a dapm without a pcm then if it's just routing
[02:56] <tmzt> nice if linux had a framework for this
[03:03] <prpplague> ogra_ac: greetings
[03:17] <rsalveti> GrueMaster: found the nm fix
[03:17] <rsalveti> ScottK-droid: cool, nice to know
[03:18] <GrueMaster> rsalveti: What was it?
[03:19] <rsalveti> GrueMaster: lack of a proper variable type: http://paste.ubuntu.com/540509/
[03:19] <rsalveti> fix is already upstream, will now open the bug following the debdiff with the fix
[03:19] <rsalveti> will also post a new deb, so you can also test
[03:20] <rsalveti> the backtrace was really really weird
[03:20] <rsalveti> inside glib, then a segv in strchr
[03:20] <GrueMaster> Wheee.
[03:20] <rsalveti> all of that because on arm the time type is 32
[03:20] <GrueMaster> heh
[03:21] <GrueMaster> Gotta love non-portable typesets
[03:21] <rsalveti> yeah
[04:08] <rsalveti> argh, takes quite a while to install everything I need to build and then build
[04:26] <rsalveti> GrueMaster: http://people.canonical.com/~rsalveti/686320/
[04:31] <rsalveti> GrueMaster: please confirm the bug and test the fix later, then I can ask people to push the fix tomorrow
[04:53] <GrueMaster> rsalveti: I'm shut down for the moment.  Will test first thing in the morning.
[05:00] <rsalveti> GrueMaster: sure, np, also going off now
[05:00] <rsalveti> see ya
[09:29] <armin76> http://www.linuxfordevices.com/c/a/News/ZT-Systems-R1801e-/
[10:32] <ogra_ac> dmart, hey
[10:32] <ogra_ac> dmart, did my comment on the bug make the issue a bit clearer ?
[11:03] <dmart> ogra_ac: hi - has that bug definitely been isolated to busybox, and do we know where/what it is ... or is that still unknown?
[11:14] <ogra_ac> dmart, NCommander traced the issue down to exec so its definitely busybox, also the fact that dropping -marm fixes it while neither klibc nor initamfs-tools changed between maverick and natty (not even a rebuild) somehow points to busysbox
[11:14] <ogra_ac> or rather the toolchain
[11:16] <dmart> ogra_ac: do you know what is being exec'd and from where?
[11:19] <ogra_ac> dmart, run-init is from /init
[11:20] <ogra_ac> run-init exposes the same error with a random error # if you dont run it from pid 1 btw
[11:21] <dmart> ogra_ac: You mean, the shell barfs on the "exec run-init" line in /init?
[11:21] <ogra_ac> either run-init does because the environment changed
[11:21] <ogra_ac> i.e. it might be that the PID doesnt get carried over properly
[11:24] <ogra_ac> its massively hard to debug, it would be better to compare exec from busybox-initramfs with and without -marm outside of an initrd
[11:25] <ogra_ac> s/either/rather/
[11:29] <dmart> ogra_ac: ok ... bit of a mystery.  I don't see any asm in busybox, so to me that suggests a compiler bug or a bug in run-init
[11:30] <ogra_ac> cant be in run-init
[11:30] <dmart> Oh yeah, you don't rebuild that
[11:30] <ogra_ac> natty and maverick initrd's are the same apart from busybox and the toolchain
[11:30] <ogra_ac> everything else involved is 100% identical
[11:31] <dmart> right...
[11:31] <ogra_ac> thats why the bug is open for gcc
[11:31] <ogra_ac> but as i said above, its very very hard to debug
[11:31] <ogra_ac> since the only debugging you could do would be to change /init
[11:32] <ogra_ac> but with every binary you inject in the exec call the PID will change from 1
[11:32] <ogra_ac> which will expose the error in any case
[11:43] <dmart> ogra_ac: gdb --attach ?
[11:46] <NCommander> dmart: bit of a problem because the debugging tools stop spitting output when the kernel panic(0s
[11:47] <NCommander> and my understanding is that since all processes are interconnected, when pid 1 goes, EVERYTHING goes
[11:48] <ogra_ac> ah, NCommander is here, I'll hand that over then and do other vacation stuff ;)
[11:48]  * NCommander goes poof
[11:48]  * ogra_ac isnt offifically here until end of year
[11:48]  * NCommander just saw the hilight since I was talking to a friend on another channel
[11:48]  * NCommander isn't here either
[11:49] <ogra_ac> NCommander, but you will at least be in a few hours ;)
[11:49] <dmart> NCommander: the kernel panics if PID 1 dies ... possibly we could hack the kernel not to do this
[11:49] <dmart> Though there might be odd knock-on effects.
[11:49]  * ogra_ac just tries to find out when we switched to i686 by default
[11:50] <NCommander> dmart: I don't think you can, everything is a child process of PID 1
[11:50] <dmart> parent process death isn't generally fatal
[11:50] <NCommander> you might be able to debug from the kernel debugger, but then you run into nasty VM issues
[11:50] <dmart> but you will need to suppress or ignore the SIGHUPs that the child processes would get
[11:51] <dmart> None of this is easy though :/
[11:51] <NCommander> dmart: according to ogra, run-init is dependent on being PID 1
[11:51] <NCommander> ideally, the easiest way to debug is to remove that requirement
[11:52] <dmart> Might not work though ... being PID 1 is genuinely different in some ways from being any other PID, mostly to do with signal behaviour IIUC
[11:52] <ogra_ac> NCommander, not *being* only *being run by*
[11:52] <NCommander> Maybe use Userspace Linux, or something like that?
[11:53] <NCommander> ther ehas to be way to have a pseudo-PID 1, else Keybuk would have probably gone mad trying to debug upstart
[11:53] <dmart> run-init is exec'd, so it will be PID 1 also...  and run-init execs upstart, so that will be PID 1 too
[11:53] <ogra_ac> right
[11:53] <dmart> Yeah, I guess he may have some good ideas...
[12:43] <dmart> ogra_ac, NCommander: here's an approach which seems to work for debugging init:
[12:43] <dmart> ogra_ac, NCommander: http://pastebin.ubuntu.com/540609/
[12:44] <dmart> I don't have the right filesystem in front of me though
[14:23] <ScottK> NCommander: You assume he didn't.
[14:30] <ScottK> NCommander: Anything you changed for Alpha 1 due to Qt being dead you ought to be able to put back now.
[15:37] <dmart> ogra_ac: ^ did you spot that link?  Should I post it somewhere else?
[15:37] <ogra_ac> probably dump it in the bug
[15:37] <dmart> ogra_ac: oh, much scrolling ... well, here it is again, just in case:
[15:37] <dmart> ogra_ac:  http://pastebin.ubuntu.com/540609/
[15:38] <dmart> ok
[15:38] <ogra_ac> i mean the url :)
[15:38] <ogra_ac> dont expect me to work on it, i'm on vacation ;)
[15:39] <ogra_ac> NCommander, janimo or rsalveti have to help out, though in the end its likely to be a toolchain issue so i bet it will have to move over to linaro in the end
[15:39] <rsalveti> afaik NCommander is still looking at this bug
[15:40] <ogra_ac> right, but i suspect it to boild down to toolchain anyway
[15:40] <ogra_ac> which puts it into linaros realm
[15:40] <rsalveti> yeah
[15:41] <dmart> I'm curious to find out what the actual bug is ...
[15:41] <ogra_ac> gcc 4.5 :P
[15:41] <dmart> but I don't want to deprive other people of the fun of tracking it down :P
[15:41] <GrueMaster> Guys, NCommander is on vacation as well.    Since he lives with me, I would know.
[15:44] <GrueMaster> about both.
[15:44] <rsalveti> hehe
[16:57] <rsalveti> GrueMaster: any chance to test the nm fix?
[16:57] <GrueMaster> on the phone brb.
[17:02] <rsalveti> k
[17:02] <hrw> have a nice rest of day
[17:04] <Sp0tter> does anyone know of ubuntu supports the hardware on the Archos 32 tablet?
[17:43] <GrueMaster> rsalveti: Finally able to work again.  I downloaded, installed, and rebooted with your network manager.  system works again.  Good find.
[17:44] <rsalveti> GrueMaster: nice, please post your results at the bug and let's try to find someone to sponsor the fix :-)
[17:44] <GrueMaster> Yep.
[17:48] <GrueMaster> You should see a flood of emails from LP.  I changed status to "In Progress, High priority, Natty-Alpha-2".
[17:49] <rsalveti> GrueMaster: ouch hehe :-) but thanks
[17:50] <GrueMaster> Just filling out the info for the release team.  Making the bug more complete.
[17:50] <rsalveti> yeah, nice
[17:52] <GrueMaster> Back to working on paperwork.
[18:22] <rsalveti> I'm impressed by the time it takes to get a kernel fix released into main
[18:22] <rsalveti> just got two notifications for testing the kernel released at proposed, and the bug was opened almost 1 month ago, with the fix included at the same day
[18:23] <GrueMaster> And it is already in proposed and tested by me two weeks ago.
[18:23] <rsalveti> yeah
[18:23] <GrueMaster> I've already raised the question on #u-kernel.
[19:10] <apachelogger> aloha
[19:10] <apachelogger> any clues where one would get powervr graphics drivers for omap3?
[19:12] <rsalveti> apachelogger: https://wiki.ubuntu.com/ARM/OMAP/Graphics
[19:12] <rsalveti> not the best one, and without a proper x11 driver, but it's there already
[19:13] <rsalveti> for omap4 the pvr stack is better, and also available from a ppa
[19:16] <apachelogger> uh
[19:16] <apachelogger> rsalveti: thanks :)
[19:54] <rbelem> fala rsalveti
[19:54] <rsalveti> rbelem: hey
[19:54] <rbelem> rsalveti, is qt compiled with gl es support?
[19:55] <rsalveti> rbelem: not yet :-)
[19:55] <rbelem> for arm?
[19:55] <rbelem> apachelogger, ^
[19:55] <rsalveti> it'll be soon
[19:55] <rsalveti> now that we got qt building fine again
[19:56]  * apachelogger has a change for that in pipeline
[19:56] <apachelogger> rbelem: http://people.ubuntu.com/~apachelogger/mobile/qt.tar.gz
[19:56] <apachelogger> binaries for testing
[19:56] <rbelem> rsalveti, what is going on about the qt neon discussion?
[19:57] <rsalveti> rbelem: still missing someone to sit and do the final work :-)
[19:57] <rsalveti> for maverick it'll be a little bit harder, as need proper backport
[19:57] <rbelem> :-)
[19:57] <rsalveti> problem is that qt takes too much time to build
[19:57] <rsalveti> any simple test turns out in days
[19:58] <rbelem> rsalveti,  and that gcc patch?
[19:58] <rbelem> rsalveti, does the arm toolchain works fine with icecc?
[19:58] <rbelem> that could speed up the builds
[19:59] <rbelem> apachelogger, hum... with gles and neon?
[19:59] <rsalveti> rbelem: https://launchpad.net/ubuntu/+source/qt4-x11/4:4.7.1-0ubuntu4/+build/2052893
[19:59] <apachelogger> rbelem: if maverick did not yet get changed to build without neon...
[20:00] <apachelogger> it is based on the most recent maverick package
[20:00] <rsalveti> rbelem: did finish fine this time
[20:00] <rbelem> cool :-)
[20:00] <rsalveti> rbelem: yeah, but I don't have lots of boards around to let them just building qt atm
[20:00] <apachelogger> rbelem: see my blog post on icecc & arm :P
[20:00] <apachelogger> qt builds in about 12 hours
[20:01] <rsalveti> yeah, half the time
[20:01] <apachelogger> if you did nt screw up and the build fails 3 times ^^
[20:01] <rbelem> apachelogger, wow :-(
[20:01]  * apachelogger notes that even on his laptop it took quite a while with -j10
[20:02] <rbelem> at work i usually use -j20 :-)
[20:02] <rsalveti> and the webkit linking part needs a lot of memory
[20:02] <rsalveti> and also takes quite a while
[20:02] <rbelem> rsalveti, xdeb works to build qt?
[20:03] <rsalveti> didn't try, but saw someone posting a but while cross building qt days ago
[20:03] <rsalveti> *bug
[20:03] <rbelem> :-/
[20:04]  * rsalveti brb, need to eat something
[20:04] <rbelem> :-)
[20:07] <apachelogger> rsalveti: well, 4.8 doesnt have webkit anymore
[20:07] <apachelogger> also I think we only need to do that stupid linking because Qt's help browser implicitly depends on its rendering in 4.7
[22:59] <Sp0tter> anyone have an Archos 32?
[23:00] <Sp0tter> been trying to find if Ubuntu will run on it
[23:00] <Sp0tter> it's omap


[19:44] <smoser> powersj: did you test console output ?
[19:45] <smoser> in your ec2
[19:45] <powersj> I added the call to grab it, however as you will note about my comment it isn't always ready to get pulled
[19:45] <smoser> seems like it should return a base64 encoded string
[19:45] <smoser> http://boto3.readthedocs.io/en/latest/reference/services/ec2.html#EC2.Instance.console_output
[19:45] <powersj> the latest commit got it from: https://git.launchpad.net/~powersj/cloud-init/commit/?id=677c60738d026a9bc1272c3b6e2366ce4bdc98f8
[19:45] <smoser> ie, if you *did* get something i think it will be base64
[19:46] <powersj> also the base64 encoding doesn't apply since "If using a command line tool, the tool decodes the output for you."
[19:46] <powersj> when using the aws-cli == command line tool
[19:47] <smoser> right
[19:47] <smoser> you're *not* using it
[19:47] <smoser> so you need to decode
[19:47] <powersj> or using the python library seems to cover that as well
[19:47] <smoser> that seems wrong
[19:47] <powersj> same for user-data... we don't encode it
[19:47] <smoser> https://eucalyptus.atlassian.net/browse/TOOLS-407
[19:48] <smoser> err.. the redux
[19:48] <smoser>  https://eucalyptus.atlassian.net/browse/TOOLS-675?attachmentViewMode=gallery
[19:49] <smoser> basically, though, i'd expect that the content that went to the console of the device is not necessarily anything that be represented losslessly as a string
[19:49] <smoser> it is bytes
[19:49] <smoser> so if ec2 did an encode to utf8, that'd be lossy
[19:51] <powersj> smoser: your comments stem from my use of .encode() on the output?
[19:52] <smoser> have you tested this?
[19:52] <powersj> yes ran it through all the tests, only one fails and we need to fix that test
[19:52] <powersj> let me try again in case I just never got any output at all
[19:52] <smoser> because i think what you will be '.encode()'ing is b'aGVsbG8gd29ybGQK'
[19:53] <smoser> so sure, it will work, buit the console log will be base64 encoded string
[19:53] <smoser> er,...bytes.
[19:54] <smoser> i have to run, i'll take a further look later.
[19:59] <powersj> smoser: it produces a string
[19:59] <powersj> https://paste.ubuntu.com/26321229/
[20:00] <powersj> here is also an example of no output: https://paste.ubuntu.com/26321219/
[20:03] <powersj> here is part of the raw string: https://paste.ubuntu.com/26321243/
[20:07] <blackboxsw> powersj minor comments on my last pass of your ec2 branch posted
[20:07] <blackboxsw> approved on my end once those nits are reviewed and handled or rejected by you
[20:09] <powersj> blackboxsw: thank you, I'm +1 on all of those
[20:12] <dojordan_> hey smoser, I'm working on using url_helper instead of raw requests, but I need infinite retry support so I was planning on using max_wait==None. I wanted to make sure that is okay, as well as wanted to point out that right now, using the default parameter of None will trigger a somewhat unexpected exception
[20:13] <dojordan_> def timeup(max_wait, start_time): return ((max_wait <= 0 or max_wait is None) or (time.time() - start_time > max_wait))
[20:13] <dojordan_> the problem is the short circuit check for a None parameter should happen before the none to int comparison. (this is in url_helper)
[20:15] <powersj> smoser: in addition to the above, take a look at: https://paste.ubuntu.com/26321285/
[20:39] <powersj> blackboxsw: changes pushed
[20:39] <powersj> spelling fix, docstring format, try/except change, and more details in debug messages
[20:42] <blackboxsw> powersj: looks good, just saw another highlighted in your latest changest.   'deleting secuirty' in tests/cloud_tests/platforms/ec2/platform.py
[20:42] <blackboxsw> all good otherwise.
[20:44] <powersj> blackboxsw: thx are you using a spell checker of some sort?
[20:45] <blackboxsw> I have two of them, and no prescription glasses ;)
[20:45] <powersj> lol
[20:45] <powersj> mine don't work very well
[20:45] <blackboxsw> nope just reading through things generally. that's why I missed the typos first time around (I should use a spell checker) ispell or something
[21:01] <powersj> blackboxsw: https://paste.ubuntu.com/26321529/ may have some test escapes again
[21:01] <powersj> that was on my local branch, let me see if the nightly run shows the same
[21:02] <powersj> actually ignore me... I am looking at the decimal wrong doh
[21:02] <powersj> coffee time
[21:02] <blackboxsw> powersj: hrm, yeah that is taking a bit long..... I thought when we saw bad escapes we'd see > 1 second (but that was probably with retries etc)
[21:02] <powersj> yeah I saw that and went 5 seconds?!
[21:02] <powersj> but it isn't 5 seconds :P
[21:04] <blackboxsw> powersj: yeah I went on a date to zquila over break and had a decimal place issue. we almost ordered 2 margs that were $75 each. thank goodness the waitress asked us to double check
[21:04] <powersj> hahaha
[21:05] <blackboxsw> I can't believe enough people would actually order a $75 marg to warrant putting something like that on the menu
[21:06] <blackboxsw> #wrongchannel
[21:06] <blackboxsw> :)
[21:09] <blkadder> LOL
[21:58] <smoser> powersj: then the bug is in boto3 :-(
[21:58] <powersj> bug?
[21:58] <smoser> i'll file it upstream.
[21:59] <powersj> you believe it should return bytes over a string?
[21:59] <smoser> it is taking a base64 encoded blob and decoding it into a string
[21:59] <smoser> and losing data along the way
[22:01] <powersj> https://github.com/boto/botocore/blob/develop/botocore/handlers.py#L142
[22:01] <smoser> yeah, thats the bug :)
[22:08] <smoser> https://github.com/boto/botocore/issues/1351
[22:08] <smoser> thanks for digging, powersj
[22:09] <powersj> smoser: heh thanks for calling it out :)
[22:09] <powersj> I am always amazed by your ability to pull out pugs from years ago heh :P
[22:09] <smoser> firefox history
[22:10] <smoser> i think euca must not use boto3
[22:10] <smoser> otherwise it would never have seen the bug that i reported (twice)
[22:10] <smoser> i  know it didn't origintally use boto3, but i figured it might have moved by now. but the project is kind of dead now.
[22:13] <smoser> dojordan_: yes, that seems sane. 0 might also make sense.
[22:14] <smoser> powersj: fwiw i'm not just making this stuff up. the data that systemd writes to /dev/console is almost all the time *not* utf-8 during a boot cycle on ubuntu at least.
[22:14] <smoser> i only know this because of tools that assumed it was not working :)
[22:15] <powersj> ok good to know, my quick look at the data made me go looks like normal output and move on
[22:27] <smoser> powersj: i hit 'submit' on review
[22:27] <smoser> i think i might be missing something though... i just went through my last round of comments, and it didn't look like you addressed many of them.
[22:29] <powersj> smoser: hmm thought I did
[22:29] <powersj> I'll look
[22:40] <powersj> smoser: looks like I misunderstood your comment about snapshots, otherwise hit all your previous requests
[22:40] <powersj> I'll get these fixes done
[23:40] <powersj> smoser: pushed updates, with a question on the review


[04:29] <pitti> Good morning
[05:45] <didrocks> good morning
[05:52] <thumper> o/ didrocks and pitti
[05:53]  * thumper is finishing for the day now
[05:53] <thumper> have a good friday and weekend folks
[07:00] <willcooke> morning all.  Look busy, there are shareholders watching
[07:03] <didrocks> hey willcooke
[07:11] <seb128> hey willcooke
[07:22] <pitti> ah, what a nice morning for running
[07:22] <pitti> hey willcooke, hey seb128
[07:23] <willcooke> o/
[07:23] <pitti> willcooke: ah, Instant Porsche Owner soon? :-)
[07:23] <seb128> hey pitti, wie gehts?
[07:23] <seb128> pitti is sport addict
[07:23] <pitti> seb128: prima, danke! und selbst?
[07:23] <seb128> auch gut, danke!
[07:23] <pitti> willcooke: I assume you refer to http://www.zdnet.com/article/mark-shuttleworth-considering-canonical-ipo/ :)
[07:23] <willcooke> yeah
[07:24] <willcooke> wrong button
[07:26] <didrocks> good morning pitti!
[07:27] <mpt> Huh, I’ve found a reliable way to crash Nautilus
[07:27] <seb128> mpt, oh, which one?
[07:27] <mpt> Unfortunately, the error reporter came up only the first time
[07:27] <mpt> seb128, :-P
[07:28] <mpt> seb128, navigate to the “Screenshots” folder on the phone, then drag one of the screenshots over the “Places” area of Nautilus’s sidebar
[07:28] <mpt> (That’s probably needlessly specific, I haven’t investigated much yet)
[07:29] <mpt> Yeah, same happens with any image, doesn’t need to be on the phone
[07:29] <seb128> works for me
[07:29] <mpt> …Same happens with any file, doesn’t need to be an image
[07:29] <mpt> …Same happens with a folder, doesn’t need to be a file
[07:29] <seb128> mpt, that seems similar to bug #1447848
[07:30] <seb128> mpt, having an error report would be useful
[07:30] <seb128> or a backtrace
[07:32] <mpt> seb128, https://errors.ubuntu.com/oops/1abf28e6-0053-11e5-8191-fa163e22e467
[07:33] <mpt> Ah, it’s bug 1293168
[07:33] <mpt> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1293168
[07:33] <mpt> At least according to the bucketer
[07:34] <seb128> mpt, seems so
[07:37] <seb128> mpt, you are on the LTS I guess?
[07:37] <mpt> yes
[07:37] <seb128> k, seems like it's fixed in newer versions from the e.u.c table
[07:59] <seb128> mpt, k, I can't get it to bug ... do you have anything that looks special/weird in ~/.config/gtk-3.0/bookmarks? I tried to add duplicates or buggy entries without luck
[08:00] <seb128> mpt, do you use desktop as home?
[08:04] <Laney> hullo
[08:05] <larsu> morning Laney!
[08:06] <Laney> hey larsu
[08:06] <Laney> happy friday!
[08:08] <seb128> hey Laney
[08:08] <seb128> hey robert_ancell
[08:08] <seb128> mpt, ok, I found a way to reproduce by editing .config/user-dirs.dirs
[08:09] <didrocks> hey Laney
[08:09] <Laney> hello french friends
[08:10] <Laney> I am going to a friend's house tonight to have tartiflette
[08:10] <Laney> scared
[08:10] <seb128> yummmy
[08:10] <seb128> lucky you
[08:10]  * seb128 wants that
[08:10] <Laney> I had reblochon once before and ...
[08:10] <Laney> didn't eat very much :)
[08:11] <didrocks> you will just fallback on potatoes :)
[08:12] <Laney> maybe it's different with all the other stuff
[08:16] <seb128> mpt, I can reproduce that nautilus bug now, looking for a fix, thanks for pointing it out ;-)
[08:39] <mpt> \o/
[09:41] <Laney> seb128: what happens with systemd and your whoopsie writable fix?
[09:42] <seb128> Laney, you mean?
[09:42] <Laney> doesn't that path rely on renaming files too?
[09:43] <Laney> (iirc)
[09:43] <seb128> oh
[09:43] <seb128> https://launchpadlibrarian.net/201618635/lac.debdiff you mean?
[09:44] <seb128> ogra_ was looking at it I think
[09:44] <seb128> but verification failed because the whoopsie side was missing
[09:44] <Laney> that's upstart
[09:44] <Laney> didrocks made it use update-rc.d disable for systemd
[09:44] <seb128> right, need to look at that
[09:44] <Laney> I wonder if this is going to work or not
[09:44] <seb128> I'm going to do it after lunch
[09:44] <Laney> okay
[09:44] <didrocks> it will create symlinks in /etc/systemd/
[09:44] <seb128> thanks for the reminder
[09:44] <didrocks> seb128: ^
[09:45] <didrocks> you should look at that part :)
[09:45] <didrocks> (it's only one file to set as writable)
[09:45] <didrocks> seb128: /etc/systemd/system/multi-user.target.wants/whoopsie.service
[09:45] <didrocks> it's creating/deleting that symlink
[09:46] <seb128> didrocks, under systemd pid1 right?
[09:46] <didrocks> yep
[09:46] <seb128> not under upstart
[09:46] <seb128> which the phone currently still use
[09:46] <seb128> but yeah, we should make both work
[09:46] <Laney> future proofing
[09:46] <didrocks> well, the phone will use soon systemd
[09:46] <didrocks> so, I guess it worthes it
[09:46] <Laney> I'm going a bit cross eyed at this code
[09:46] <seb128> not sure, maybe /etc/systemd/system should be writable as a dir
[09:46] <Laney> I can't find where it makes the upstart override
[09:47] <didrocks> Laney: whoopsie-preferences?
[09:47] <Laney> ye
[09:47] <seb128> need to go for lunch, bbl
[09:47] <didrocks> it's using update-rc.d
[09:47] <Laney> does update-rc.d make an override?
[09:47] <didrocks> good week-end seb128 :)
[09:47] <didrocks> IIRC, yeah, let me check, one sec
[09:47] <seb128> didrocks, oh right, thanks, you too
[09:47] <didrocks> enjoy the "north"
[09:47] <didrocks> :)
[09:47] <Laney> yes, it does
[09:48] <seb128> hehe, and you enjoy Paris ;-)
[09:48] <didrocks> well, it's far enough from Paris, thanks god!
[09:48] <Laney> do we need to pre-create this file?
[09:48] <Laney> like we do for ssh.override it seems
[09:48] <didrocks> Laney: yeah, so update-rc.d does this
[09:48] <didrocks> Laney: I'm afraid you do
[09:49] <didrocks> for the bindmount
[09:49] <Laney> fair enough
[09:49]  * didrocks imagines how pitti enjoys that conversation :)
[09:49] <pitti> didrocks: what, what?
[09:50] <didrocks> pitti: speaking about mounting hacks needed for whoopsie on touch
[09:50] <Laney> oh, just doing some butchery
[09:50] <didrocks> "sorry for the blood"
[09:51] <pitti> didrocks: ah, you mean https://launchpadlibrarian.net/201618635/lac.debdiff ?
[09:52] <didrocks> pitti: yeah, and now, adding the systemd part
[09:52] <pitti> yeah, every time we add another bind mount, a little kitten dies somewhere :(
[09:52] <Laney> I think they are open to doing something different for snappy
[09:52] <didrocks> pitti: you mean http://ikonal.com/wp-content/uploads/2011/06/100-chats-1662099.jpg is next?
[09:53] <didrocks> Laney: depends on who you talk to
[09:53] <didrocks> Laney: there is a very long email thread about it a couple of months ago
[09:53] <pitti> didrocks: right, and now imagine that with a blunt fork in its belly!
[09:53] <Laney> I started a new one a couple of days ago
[09:53] <didrocks> yeah, I saw it
[09:53] <Laney> I think asac recognises the problem so ...
[09:53] <Laney> there is hope
[09:53] <didrocks> let's cross fingers
[09:55] <didrocks> Laney: I was referencing this email: https://lists.ubuntu.com/archives/snappy-devel/2015-February/000285.html
[09:56] <didrocks> especially:
[09:56] <didrocks> "using read-only bind-mounts and
[09:56] <didrocks> tmpfs mounts instead (possibly hundreds/thousands of them)"
[10:07] <Laney> is ubuntu-rtm still relevant?
[10:08] <didrocks> yes, AFAIK
[10:09] <asac> Laney: which problem?
[10:09] <asac> :)
[10:09] <asac> me? :P
[10:09] <Laney> renaming thing
[10:09] <Laney> ogra_: confirm/deny ubuntu-rtm please
[10:09] <asac> so far i didnt get it :(
[10:09] <asac> but i didnt have time to even ask anyone to explain it to me
[10:10] <Laney> ok
[10:20] <ogra_> Laney, not relevant anymore
[10:21] <ogra_> vivid+overlay is the relevant one now ...
[10:21] <ogra_> (wily is not supposed to have a phone release at all (might change indeed, but not planned atm))
[10:25] <Laney> thx
[10:25] <Laney> I think for whoopsie vivid=wily so fix is the same
[11:05]  * didrocks is going to catch a train and work offline. Have a good week-end everyone!
[11:05] <willcooke> see ya didrocks
[11:05] <Laney> bye didrocks!
[11:05] <didrocks> see you on Tuesday, enjoy the long week-end willcooke, Laney :)
[11:06] <Laney> and to you
[11:06] <Laney> GOD
[11:06] <Laney> speedquitting
[11:06] <willcooke> :D
[11:08]  * Laney keeps forgetting that it is a long weekend
[11:08] <willcooke> only if we survive the earth quake apocalypse
[11:09] <Laney> maybe the south will slide into the sea
[11:10] <willcooke> It's the collective will of the Tories in Kent trying to distance themselves from Scotland
[11:24] <larsu> Laney: what are we updating totem to this cycle?
[11:24]  * larsu wonders if he should backport patches
[11:25] <Laney> 16 probably
[11:25] <larsu> k
[11:25] <Laney> has that code changed?
[11:25] <larsu> well, let's see what hadess says first
[11:25] <Laney> because ... we'd probably want to SRU the fix
[11:25] <larsu> not by much I don't think
[11:25] <larsu> I think I'd like to SRU the gsettings-on-startup one
[11:25] <Laney> peas?
[11:26] <larsu> no. gregier wasn't impressed
[11:26] <larsu> I filed a bug though, let's see
[11:26] <larsu> put a workaround in totem at gnome bug #749722
[11:26] <mitya57> attente, seb128: Qt 5.4.2 is not released yet, but we'll update when it is
[11:26] <Laney> i see
[11:26] <mitya57> (that might take a while though)
[11:27] <Laney> well, we'll want it on 3.14 for the SRU either way
[11:29] <larsu> indeed
[11:30] <Laney> thanks for fixing it!
[11:30] <Laney> sorry for the yaks
[11:31] <seb128> mitya57, thanks
[11:36] <seb128> back
[11:37] <seb128> Laney, for systemd, any reason we just don't make the whole /etc/system.d/system writable? that should work for any enabling/disabling of systemd jobs then?
[11:37] <Laney> I don't know - we could have done that for /etc/init too
[11:38] <larsu> Laney: I also found a bug in the dbus action group exporter in the process :)
[11:38] <Laney> heh
[11:39] <larsu> don't think I've ever had that many yaks while working on a "I just need to drop this menubar xml here"
[11:40] <seb128> Laney, yeah, I'm fine doing it for /etc/init as well
[11:40] <seb128> ogra_, ^ do you know why we didn't do that?
[11:40] <Laney> it's probably a principled th ing
[11:40] <Laney> man this pear is really messy
[11:40] <ogra_> seb128, security ... then you could as well make all of /etc writable which we dont want
[11:44] <seb128> ogra_, if you can adb and use sudo on the device security is out anyway
[11:44] <ogra_> well, it is the concept ...
[11:44] <seb128> you can as well set the image to rw
[11:44] <seb128> and change the password
[11:44] <seb128> what concept?
[11:45] <seb128> even mdeslaur gave a +1 on the phone list to pitti's suggestion to have /etc rw with some bits ro symlinked somewhere
[11:45] <ogra_> that only a minimal set of files are made writable ... only in cases where something needs a cache dir or some such dirs are allowed writable
[11:45] <ogra_> the idea was to have complete control over each file ...
[11:45] <seb128> well experience show it doesn't work
[11:46] <seb128> we keep piling hacks to make things writable
[11:46] <ogra_> that is why snappy will make that better ;)
[11:46] <seb128> how?
[11:46] <ogra_> if you want to change the security concept of the whole system some days before an OTA, feel free to discuss that with the new phone team
[11:47] <seb128> no, I don't
[11:47] <ogra_> snappy will most likely use overlayfs with a whitelist
[11:47] <seb128> but I don't want snappy to have the same limitations
[11:47] <seb128> ah, cool
[11:47] <ogra_> depends on how hard the backporting of it to the android kernels will be
[11:47] <seb128> so we are making overlayfs work? ;-)
[11:47] <seb128> great
[11:47] <ogra_> not decided yet ... we need to look into the kernel work
[11:48] <ogra_> but i thnk thats the long term goal in any case
[11:48] <seb128> k
[11:48] <seb128> that's good to know
[11:48] <seb128> thanks
[11:48] <seb128> ogra_, meanwhile can we land https://launchpadlibrarian.net/201618635/lac.debdiff? you or rsalveti were looking at it I think?
[11:49] <ogra_> (if it is as easy as patching apparmor (drop the upstream apparmor dir, unpack ours in there) we will surely do it)
[11:49] <ogra_> seb128, well, is whoopsie ready for that now ?
[11:49] <seb128> ogra_, yes, https://code.launchpad.net/~seb128/whoopsie-preferences/touch-writable-image/+merge/259531 got merged today
[11:50] <ogra_> iirc there was the systemd-like patch needed
[11:50] <ogra_> ah, perfect
[11:51] <seb128> seems like  lxc-android-config  has already some landing up in the system
[11:51] <ogra_> yeah
[11:51] <ogra_> kenvandine was handling the last one ... i think  once his is in we can try landing the whoopsie one
[11:51] <seb128> great, thanks
[11:52] <ogra_> the others should all only be test silos or leftover ones (ken merged most of them in one landing)
[12:05] <Laney> seb128: I uploaded whoopsie-preferences
[12:05] <seb128> Laney, thanks!
[12:05] <Laney> commented on what's left
[12:06] <seb128> thanks
[12:08] <ChrisTownsend> seb128: Hi!  dkessel was asking yesterday about the login credentials of Ubuntu Desktop Next Live session.  dkessel wants to switch to a VT to do some debugging, but it's requiring a username and password.  1) I thought VT's were automatically logged in on a Live session 2) he tried ubuntu/<blank> and ubuntu/ubuntu with no success.  Do you have any ideas?
[12:09] <seb128> ChrisTownsend, hey, replied on #ubuntu-unity
[12:09] <Laney> what happened to the work to turn that into a preinstalled image btw?
[12:10] <seb128> preinstalled? you mean the container thing? or snappy personal?
[12:11] <Laney> didrocks was preparing the bits to make it a snappy image
[12:11] <Laney> the live desktop-next was going to go away
[12:11] <didrocks> ok, staying connected as long as we are not at 300kms/h!
[12:11] <Laney> oh hello!
[12:11] <didrocks> no promise though :p
[12:11] <didrocks> but EMISSCONTEXT with ping
[12:11]  * pitti waves to didrocks while he zips through the landscape
[12:11] <Laney> I was asking about the 'new' desktop-next that you were working on at the sprint
[12:12] <pitti> didrocks: btw, good news! fsckd works fairly well with the /run/systemd/fsck.progress in systemd 220
[12:12] <pitti> didrocks: I just had to drop the fsck modifications and clean up the patch a bit
[12:13] <seb128> Laney, right, but didrocks did rage quit that project, I'm looking at it with robert_ancell next, we just aren't there yet
[12:13] <Laney> haha
[12:13] <Laney> ok, I was just asking :)
[12:13] <seb128> :-)
[12:19] <seb128> Laney, though I'm unsure what the changes didrocks did in London were about exactly, he changed the livecd scripts to prepare some of the work I think, but not sure how that fit with the snappy image build
[12:20] <didrocks> seb128: well, if it's another name, you "just" need to do the same with another name
[12:20] <didrocks> there are livecd changes and at least another component to change
[12:20] <didrocks> +the seed creation of course if it's a new name
[12:20] <Laney> no new name, just finishing up what you did i think
[12:20] <seb128> didrocks, well, snappy images are built like livecd?
[12:20] <Laney> they are driven from the same scripts
[12:20]  * seb128 still doesn't have a good picture of how those pieces fit
[12:20] <didrocks> seb128: yeah, with special propertie
[12:21] <didrocks> properties*
[12:21] <Laney> but they produce a different type of image at the end
[12:21] <didrocks> that's why I did the changes there
[12:21] <seb128> k
[12:21] <didrocks> Laney: it's normally "done", just need to be in production
[12:21] <didrocks> and fix ;)
[12:21] <Laney> does it use the seeds still?
[12:21] <didrocks> yep
[12:22] <seb128> did you upload your changes at the end?
[12:22] <didrocks> it's just the output elements that are differents
[12:22] <Laney> ya
[12:22] <seb128> do we have some wiki/documentation about building a snappy image from a seed?
[12:22] <Laney> I don't know what unknown surprises there will be, surely some
[12:22] <didrocks> seb128: no, we were stuck in willy to open, and then, I retargeted myself
[12:22] <Laney> unlikely
[12:22] <seb128> didrocks, did you stack your wip work somewhere?
[12:23] <didrocks> seb128: nothing AFAIK, just needed to dive into the code
[12:23] <seb128> k
[12:23]  * Laney senses some lag
[12:23] <seb128> didrocks, thanks
[12:25] <Laney> there were some branches pushed
[12:25] <Laney> I saw cjwatson doing some reviews
[12:25] <didrocks> seb128: it's in ~ubuntu-desktop
[12:25] <didrocks> just check for recent branches, I guess I don't have enough bandwith
[12:25] <didrocks> seb128: there are MPs as well (approved)
[12:25] <pitti> seb128: if you find some documentation, I'd be interested in that as well
[12:26] <seb128> didrocks, great, thanks
[12:26] <seb128> pitti, ok, if I do I let you know ;-)
[12:26] <pitti> it seems to me that building a snappy image shouldn't be much more than calling vmdebootstrap with a 30-liner shell script to install additional things?
[12:26] <seb128> Laney, thanks for catching that absolute/relative symlink thing
[12:27] <Laney> np!
[12:28] <Laney> lunch time
[12:28] <Laney> aka courgette time
[12:28] <Laney> yum yum
[12:29] <seb128> Laney, enjoy! better to eat light, keep some space for the cheese tonight
[12:41] <ogra_> oh, poetry !
[13:31]  * willcooke -> kids school
[13:31] <willcooke> bbl
[14:58] <Laney> seb128: do you remember a bug about the font preview thing in gedit?
[14:58] <Laney> I thought that was fixed but still seems to be happening here
[14:58] <seb128> Laney, no, what's wrong with it?
[14:58] <Laney> no sample text
[14:59] <seb128> oh, that
[15:02] <seb128> Laney, https://git.gnome.org/browse/gedit/commit/?id=af6d3204ec4a71efff8521f2df7ffb69960279f4
[15:02] <seb128> need to backport that
[15:03] <Laney> ya, can do
[15:03] <Laney> just got forgotten?
[15:03] <seb128> well, I think it was "fixed with new gedit" and larsu was looking at updating gedit
[15:03] <seb128> so we didn't bother doing backporting
[15:03] <Laney> 'kay
[15:04] <seb128> you can maybe just commit that to the vcs to batch for the next upload
[15:04] <seb128> that doesn't seem important enough to bother uploading
[15:11] <Laney> bah
[15:11] <Laney> 9 and 10 aren't in bzr
[15:11] <Laney> just 10
[15:11]  * Laney can't read
[16:02] <qengho> Hey hey. I'm testing a new chromium, and I want a few others to test, especially if you're using a non-default input method.  https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage
[16:03] <qengho> I see some weird problem with typing at a new tab, and I don't know if it's fcitx or Cr or my machine.
[16:03] <seb128> qengho, I can test but I'm not using an im for input
[16:04] <qengho> seb128: well, that is data too. Please give it a try.
[16:04] <seb128> qengho, installing
[16:11] <seb128> qengho, seems to work fine here, no input issue in tabs
[16:12] <seb128> the tab UI is weird
[16:12] <seb128> if you select the entry in the middle of the page an start typing the input/focus goes to the top bar
[16:12] <seb128> is that expected?
[16:12] <seb128> it works, just looks weird
[16:12] <qengho> seb128: so, C-n new tab, "foo"+enter, sends text to location bar and searches for "foo"?
[16:13] <seb128> yes
[16:13] <seb128> I can ctrl-t and type, enter and get google result
[16:13] <seb128> same for new instances
[16:14] <seb128> https://www.google.nl/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8&client=ubuntu#q=ubuntu
[16:14] <seb128> is what I get typing "ubuntu"
[16:14] <seb128> is that sourceid correct?
[16:15] <qengho> seb128: you mean beneath the new-tab "Google   [     ]    eight frequent sites" page?  Clicking in that search box and typing "should" (or has gone for a while in Cr and G-C) to what you and I call the location bar. That part is normal.
[16:15] <nessita> seb128, hi! remmber I had some issues with the desktop where all the characters in the browser (firefox) and terminal completely messed up? it happened again, and not sure hot to go back to a sane state without rebooting. What I see is https://drive.google.com/a/canonical.com/file/d/0B-cmfDncRJmYbEROaFhPRGJCTlk/view?usp=sharing
[16:16] <seb128> qengho, I mean I type in the box on the middle of the page and the focus/text goes to the url bar at the top
[16:16] <qengho> seb128: right. Normal.
[16:16] <seb128> k
[16:16] <seb128> weird experience
[16:17] <seb128> nessita, yeah, seems to be an intel driver bug...
[16:17] <seb128> nessita, https://bugs.freedesktop.org/show_bug.cgi?id=88584
[16:17] <qengho> seb128: I think it's training users to just search already, instead of searching for "google" and then searching.
[16:17] <seb128> qengho, I see :-)
[16:18] <seb128> qengho, which tag is our client is? client=ubuntu?
[16:18] <seb128> qengho, not sourceid?
[16:18] <qengho> seb128: the source id is not used by us. Only "client" matters.
[16:18] <seb128> k
[16:18] <seb128> good
[16:18] <seb128> I was unsure so checking ;-)
[16:18] <seb128> nessita, usually when I get that changing fonts or zoom fixes it
[16:19] <seb128> that can be a workaround you can try
[16:19] <seb128> if you don't want to reboot
[16:19] <seb128> nessita, "gsettings get org.gnome.desktop.interface font-name"
[16:19] <seb128> then try to set that to a with a small difference to the size for example
[16:20] <nessita> seb128, thanks (had to re-open the chat in the text terminal because I couldn't read what you were saying :-))
[16:20] <seb128> nessita, sometime selecting works as well
[16:21] <seb128> qengho, confirmed that I've no input issue here, sorry ...
[16:21] <nessita> seb128, you are right! and then pasting on a gmail draft ;-)
[16:22] <seb128> hehe
[16:22] <qengho> seb128: Thanks!
[16:23] <seb128> yw!
[16:23] <nessita> hum, changing fonts does not fix it (tried Arial, Verdana)
[16:23] <nessita> will reboot :-)
[16:25] <seb128> k
[16:25] <seb128> sorry, I don't have a better suggestion...
[17:07] <Laney> bye, happy one day holiday!
[17:07] <Laney> of^


[11:04] <Jonopoly> Anyone got a nice terminal based google calander that can recommend ?
[11:06] <lotuspsychje> !info gcalcli
[11:07] <lotuspsychje> !info khal
[11:08] <Jonopoly> Thanks, really helpful will try them bothg
[11:08] <Jonopoly> Thanks, really helpful will try them both
[11:08] <lotuspsychje> !info calcurse
[12:25] <Jonopoly> I don't think Khal can sync with google calendar
[21:39] <arraybolt3[m]> Over the weeks since Jammy was released, I have seen so many people annoyed, alarmed by, or confused by, the "Pending update of firefox" warning that Snap throws out every so often. It's made worse by the fact that the auto-update doesn't seem to happen immediately after closing the app. Fix ideas?
[21:40] <sarnold> arraybolt3[m]: I think that's the topic of discussion on https://github.com/snapcore/snapd/pull/11912
[21:42] <arraybolt3[m]> Nice! Hopefully that will get an SRU soon.
[21:44] <sarnold> tying updates to the running / not running status of executables in the snaps feels like it was a mistake. granted, firefox and libreoffice were already not reliable if you kept them running after updating their debs
[21:44] <sarnold> but when someone can prevent security updates from installing by leaving a program running -- or, likewise, when the security update kills their running processes -- both those are pretty frustrating situations
[21:45] <arraybolt3[m]> It seems like since Snaps are squashfs-based and sandboxed, this should be easy enough to make work. It's not the notification that's the problem, half so much as the fact that closing the app doesn't auto update.
[21:45] <arraybolt3[m]> If the update would apply in the background, let you know when it was finished, and then tell you to restart the app, that would be great. And while I'm not a big fan of forcing the app to restart after a while if the user is stubborn, it's better than the alternative.


[00:02] <evand> 17:41:47 < cjwatson> evand: something like http://paste.ubuntu.com/60697/ maybe?
[00:02] <evand> kirkland: ^ apply that to /lib/partman/fstab.d/hostboot
[00:02] <evand> and see if it still hangs
[00:03] <evand> before you hit partman in d-i, that is
[00:03] <evand> gotta run out again, unfortunately.  Back in a little bit.
[00:41] <kirkland> evand: that pastebin patch didn't work as is
[00:41] <kirkland> evand: i'm looking at it a bit more
[00:46] <kirkland> cjwatson: ^
[00:47] <cjwatson> how did it fail?
[00:47] <cjwatson> it certainly shouldn't have been in the same way
[00:47] <cjwatson> although I can believe that it is busted somehow, it was totally untested
[00:47] <kirkland> cjwatson: i'm reading the patch, and I don't quite get it...
[00:48] <kirkland> cjwatson: so this "loop" file shows up
[00:49] <cjwatson> yes, that indicates that the device is a loop-mount
[00:49] <cjwatson> it's set by autopartition-loop
[00:50] <kirkland> cjwatson: hmm, okay, so the situation i'm hitting is: /boot on a raid1 of 2 disks, and / on a raid5 of 3 disks
[00:51] <kirkland> cjwatson: that's sort of my setup on a few servers, seems reasonable
[00:51] <cjwatson> are you actually using wubi?
[00:51] <kirkland> cjwatson: when doing so, installer "hangs", with several instances of 07root_on_raid
[00:52] <kirkland> cjwatson: looking at 07root_on_raid's code, running "ext3" seems to hang
[00:52] <kirkland> cjwatson: i've never run wubi in my life
[00:52] <kirkland> i'm wonder if we've gotten our bugs crossed........
[00:53] <kirkland> cjwatson: i got the impression from evand and yourself that hostboot farkage might be at the root of this problem
[00:55] <cjwatson> if you get a hang on open_infifo, it's because something fucked up the parted_server communication
[00:55] <cjwatson> it could be basically anything that ran just before it
[00:56] <cjwatson> it's like a malloc failure, manifesting after the actual cause
[00:56] <cjwatson> we need to see the partman log again from after you applied that patch
[00:56] <cjwatson> syslog wouldn't hurt either, just in case some shell script died in the middle
[00:57] <kirkland> cjwatson: http://pastebin.com/f7500f9d6
[00:57] <kirkland> cjwatson: http://pastebin.com/f70d3af56
[00:58] <kirkland> cjwatson: i inadvertentantly left off DEBCONF_DEBUG=developer
[00:58] <kirkland> :-/
[01:01] <cjwatson> http://pastebin.com/f70d3af56 breaks. try paste.ubuntu.com please?
[01:01] <cjwatson> "Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 1154191 bytes) in /home/pastebin/lib/geshi/geshi.php on line 2474"
[01:02] <kirkland> cjwatson: shite, okay
[01:03] <kirkland> cjwatson: http://pastebin.ubuntu.com/60747/
[01:03] <kirkland> cjwatson: http://pastebin.ubuntu.com/60748/
[01:16] <cjwatson> kirkland: hmm, still hostboot - you sure you applied that patch?
[01:17] <cjwatson> kirkland: and can you see what's happening in ps output?
[01:17] <NCommander> Have there been any recent installation reports with grub failing to install ?
[01:18] <NCommander> (alternate i386)
[01:18] <cjwatson> kirkland: I'm fading fast, going to have to come back to this in the morning
[01:45] <kirkland> cjwatson: sorry, family obligations here on my end
[01:45] <kirkland> cjwatson: let's revisit tomorrow
[01:47] <kirkland> cjwatson: the hostboot: http://pastebin.ubuntu.com/60765/
[01:47] <kirkland> cjwatson: ps -ef > http://pastebin.ubuntu.com/60766/
[05:24] <StevenK> It appears I can't run partman under Ubiquity with --automatic and debugging, since it dies with an AssertionError
[05:25] <evand> StevenK: it should work fine as that's the debug-ubiquity kernel command line argument.  What's the assertion error?
[05:26] <StevenK> assert self.extra_choice is not None
[05:26] <StevenK> ubiquity/components/partman.py:422
[05:26]  * evand raises an eyebrow
[05:27] <evand> and this only happens with both --debug and --automatic enabled?
[05:28] <evand> if that's the case I suspect there is some very bad interaction in debconf land.
[05:28] <StevenK> So it seems. I can copy the debug log out of the way and then try with just --automatic if you wish
[05:28] <evand> you shouldn't need to move the debug log, but give it a try with just automatic (on a fresh debconf db)
[05:29]  * StevenK has forgotten how to wipe debconf's database
[05:30] <persia> StevenK, You don't want to wipe completely, or you lose the preseeding.  Maybe reboot?
[05:31] <StevenK> Then I lose the debug log
[05:31] <evand> indeed, I don't know of any way to revert to the intial state short of keeping a copy of /var/cache/debconf/config.dat handy.
[05:32]  * StevenK scp's off the log
[05:33] <persia> StevenK, You probably want /var/log/partman and /var/log/syslog to go with that.
[05:51] <StevenK> evand: Right, it doesn't break with 'ubiquity --automatic' but it does ask the question
[05:53] <persia> StevenK, Same initial setup, partman breaks with -d and --automatic isn't skipping a question (but you can't get to that question with debug)?
[05:53] <StevenK> persia: Suprisingly, it did skip the username question
[05:54] <persia> Which question is it asking when you say "it does ask the question"?
[05:54]  * StevenK reboots, and tries it from the icon
[05:54] <StevenK> persia: How to partition the hard disk
[05:54] <evand> hrm, perhaps it's a red herring.  Do the logs show anything interesting?  Perhaps partman bailed out?
[05:54] <StevenK> evand: I doubt it bailed, it says it ready to install
[05:55] <evand> hrm
[05:55] <StevenK> sda1 -> ext3, sda5 -> swap
[05:55] <StevenK> Looks like guided to me
[05:57] <persia> StevenK, Did it perhaps bail the time it didn't work?
[05:57] <StevenK> evand: Shall I quit, capture logs, and then try with --debug --automatic again?
[05:59] <evand> sure, can I see the logs? syslog, debug and partman, that is.
[06:01] <StevenK> I have the earlier debug ones, too
[06:06] <evand> ok
[06:09] <StevenK> evand: http://people.ubuntu.com/~stevenk/ubi/
[06:09]  * StevenK stares at his laptop.
[06:15] <evand> nothing is jumping out at me, but I'm still looking over the logs
[06:16] <persia> There's a *big* difference in the partman logs there, although the initial conditions look similar.  Did partman give you a useful error of any sort with --debug --automatic?
[06:17] <StevenK> An assertion error, which is in the logs
[06:17] <StevenK> evand: In the --debug --automatic logs, I hit the "I don't care, do it again" button, so the error is probably duplicated
[06:18] <evand> ah, ok
[06:18] <evand> can you pastebin your preseed file?
[06:20] <StevenK> evand: http://paste.ubuntu.com/60852/
[06:21] <evand> Oct 22 04:13:31 debconf (filter): <-- INPUT critical partman-auto/init_automatically_partition
[06:21] <evand> debconf (developer): <-- METAGET partman-auto/init_automatically_partition Type
[06:21] <evand> debconf (developer): --> 1 select
[06:21] <evand> debconf (developer): <-- FGET partman-auto/init_automatically_partition seen
[06:21] <evand> debconf (developer): --> 0 true
[06:21] <evand> Oct 22 04:13:31 debconf (filter): --> 30 question skipped
[06:21] <evand> I wonder why that's happening again, given that Colin fixed this (bug 182004)
[06:22] <evand> might also be a red herring
[06:22]  * evand digs further
[06:34] <evand> and curiously I cannot reproduce it here, given your preseed file
[06:34] <evand> hrm
[07:24] <evand> I'll pick back up with this in the morning.
[10:33] <davmor2> guys you know on encrypted lvm install where the system boots and asks you for a password for the drive... Is there anyway to make that font clearer?  It's quite fuzzy especially on the s's
[10:57] <xivulon> superm1 I cannot replicate the crash on vista, will try tonight using xp in vm
[10:58] <xivulon> davmor2 do you happen to have xp?
[10:59] <davmor2> testing across the board at the moment xivulon although I will be doing some wubi testing in about an hour
[11:01] <xivulon> cool, the issue reported by superm1 is that when you use wubi in xp attached to a network but without internet connection, then it crashes at the reboot screen
[11:04] <davmor2> xivulon: on what cd version
[11:04] <xivulon> I guess using latest ubuntu desktop daily
[11:05] <davmor2> okay np's I'll have a look shortly :)
[11:05] <xivulon> but in theory it should not matter, since the issue is in windows, and wubi is still rev 513
[11:16] <cjwatson> davmor2: font> looks like it's example-theme/helvB10.bdf in the usplash package
[11:17] <cjwatson> (or possibly bogl/helvB10.bdf, but they're the same)
[11:18] <davmor2> cjwatson: if you get chance have a look if you can.  The s's are worse hit
[11:18] <cjwatson> not for intrepid I think
[11:18] <cjwatson> but do file a bug
[11:19] <cjwatson> kirkland: 227848 has a release-notes task, but ISTR you were working on fixing this?
[11:19] <davmor2> I thought it wouldn't be in for intrepid.  I'll bug it after
[11:19] <cjwatson> (for intrepid)
[12:14] <davmor2> xivulon: seems okay here on kubuntu. I'll try with ubuntu in a bit though incase it is specific
[12:17] <davmor2> xivulon: is his copy of xp up-to-date?
[12:21] <xivulon> davmor2: not sure, superm1 ^
[12:22] <xivulon> you have to be connected to the router but the router must not be connected to the web (or at least so I understood)
[12:27] <davmor2> xivulon: ah hangon then I was connected to my switch but not router
[12:30] <davmor2> I'll try it like that on the next one shouldn't be too long
[12:37] <holst> is there some way to check the syntax of a debian preseed file?
[12:37] <holst> it just says "no!" withtout any hints
[12:37] <cjwatson> debconf-set-selections -c
[12:38] <cjwatson> but you may not actually have a syntactic problem
[12:40] <soren> cjwatson: Thanks for you pointer about /var/{run,lock} yesterday. http://bazaar.launchpad.net/~ubuntu-virt/vmbuilder/trunk/revision/258 is clearly the better solution.
[12:49] <cjwatson> soren: looks good
[13:13] <davmor2> xivulon: happens on xp and vista it hangs on reboot not of xp/vista but of ubutnu
[13:13] <davmor2> ubuntu even
[14:07] <xivulon> davmor2 that is then a different issue
[14:08] <xivulon> it usually depends on /etc/init.d/sendsigs or /etc/init.d/umountfs
[14:10] <xivulon> you have no hangs within windows though, correct?
[14:15] <xivulon> hmm sendsigs and umountfs look good to me
[14:16] <davmor2> xivulon: no hang in windows no
[14:26] <xivulon> davmor2, it should be possible to narrow down the issue by going to a terminal and running the scripts in /etc/rc6.d
[14:27] <davmor2> xivulon: we're bhind with testing but I might be able to tomorrow
[14:28] <xivulon> ok, will have a go myself tonight, do you see anything on script? I/O errors?
[14:28] <xivulon> s/script/screen
[14:34] <davmor2> xivulon: nothing just a flashing underscore
[14:35] <xivulon> was this in vm or real hardware?
[14:36] <davmor2> real
[14:37] <xivulon> thx will have a look
[15:27] <superm1> davmor2, xivulon this is xp sp3 that i did it on
[15:39] <xivulon> superm1 as mentioned on vista worked will, will give it another go in xp/vm, did you use a vm by the way?
[15:39] <superm1> xivulon, yeah that's the only way i have to test it is vm
[15:41] <holst> cjwatson: well, if it just stops, how can I know what is the problem?
[15:41] <holst> if its a missing package, something syntax error, or something else
[15:56] <cjwatson> holst: you need to look in the syslog
[15:56] <cjwatson> holst: put it on a pastebin and I'll be happy to have a look at it
[15:58] <kirkland> cjwatson: hey, i'm working on a writeup on encrypted private for james_w ...  I've not installed from a desktop intrepid iso in a long time ...  did setting up an encrypted private directory ever make it into the desktop installer?
[15:59] <cjwatson> kirkland: I swear I've answered this once a day for the last week :)
[15:59] <cjwatson> kirkland: no, it didn't
[15:59] <kirkland> cjwatson: :-)  not from me!
[16:11] <holst> cjwatson: ah, syslog. I will try that
[18:32] <davmor2> cjwatson: we're getting a hang at 5% on installing ubuntu dvd via ubiquity
[18:33] <evand> IIRC, that's formatting.  If you run top and sort by CPU, do you see mkfs chugging along?
[18:33] <evand> How long has it been hanging for?
[18:34] <davmor2> long enough for the screensaver to kick in so minimum of 10minutes
[18:35] <evand> can you pastebin `ps auxf`?
[18:36] <davmor2> evand: I'll re run in a second I was running cd check to make sure it was alright
[18:36] <evand> ok
[18:37] <davmor2> evand: re-running now no errors found
[18:43] <davmor2> evand: heno has just said that his vm install just started up again after 15-20 minutes or so
[18:44] <evand> started up again?  Can you elaborate on what you mean by that
[18:44] <davmor2> install continued
[18:45] <evand> ah
[18:45] <davmor2> evand: right I'm at 5% again and my hd is going like mad at the minute so I'll give it till the hd stops and and then paste the info is that okay?
[18:47] <evand> sure thing
[18:49] <davmor2> evand: http://paste.ubuntu.com/61106/
[18:53] <evand> hrm
[18:54] <davmor2> it's just sat there no hd light going no dvd light going
[18:55] <davmor2> evand: I'm off for my lugmeeting soon but I'll leave it to run and see if it has installed when I get back
[18:55] <evand> ok
[18:55] <evand> davmor2: when you're about to go can you run strace -p 14115 -o ubiquity.log , let it run for a bit and then pastebin
[18:56] <evand> might be a bit large for pastebin
[18:57] <davmor2> I'll tag it to http://www.davmor2.co.uk/......     Will 4 minutes be enough?
[18:58] <davmor2> oh apparently operation is no permited
[19:00] <davmor2> got it
[19:00] <evand> need to sudo it
[19:00] <davmor2> sudo strace
[19:00] <evand> less than a minute will be fine
[19:00] <evand> indeed
[19:01] <evand> err about a minute, that is
[19:02] <davmor2> hrm it seems to be empty should that be the case?
[19:03] <evand> no
[19:04] <evand> is this still the same install as when you pastebin'ed?
[19:04] <davmor2> yeap at the same place still too
[19:05] <evand> double check that 14115 is the process ID of python /usr/share/ubiquity/install.py
[19:05] <davmor2> 14115 /usr/bin/python /usr/share/ubiquity/install.py
[19:06] <davmor2> re-running strace but I really need to go in a minute
[19:06] <evand> indeed
[19:06] <evand> don't let me keep you
[19:06] <evand> we can continue this at some other time
[19:07] <davmor2> oh it just shot up to 15%
[19:09] <davmor2> evand: http://www.davmor2.co.uk/ubiquity.log
[19:09] <davmor2> got to go now bye
[19:10] <evand> cheers
[19:10] <davmor2> 32% and still going
[21:23] <ClaesBas> Why does "do-release-upgrade -d" want  88.1M free space on /boot ?
[21:23] <ClaesBas> I only have 12M on my /boot now (8.04)!
[21:23] <cjwatson> you want mvo for that, who isn't here; try #ubuntu-devel
[21:24] <ClaesBas> OK...
[21:24] <cjwatson> either clean up some old kernels or have a less inconveniently small /boot, though :-)
[21:25] <ClaesBas> Do you think 100M /boot is to small!?
[21:25] <cjwatson> if you only have 12M left, you need the first option (clean up some old kernels)
[21:25] <cjwatson> kernels consume about 12M apiece
[21:25] <cjwatson> (when you count initrd etc.)
[21:27] <ClaesBas> I meant that my files on /boot (8.04) take 12M
[21:27] <cjwatson> oh, I see
[21:27] <cjwatson> its calculation does sound wrong then
[21:28] <ClaesBas> Is mvo a user or does it mean anything else?
[21:33] <cjwatson> ClaesBas: mvo is Michael Vogt, the author of do-release-upgrade
[21:33] <cjwatson> ClaesBas: alternatively, just file a bug: https://bugs.launchpad.net/ubuntu/+source/update-manager/+filebug
[21:34] <evand> The hanging DVD situation appears to be the fault of generate_blacklist(), which makes sense as that's one area where we'd see a difference between the CDs and DVDs.
[21:34] <cjwatson> oh, so it's just slow? that would figure
[21:34] <cjwatson> is it at the dependency calculation stage, or the stage where it does dpkg -L everything?
[21:34] <evand> indeed, it seems we set out to reduce installation time and created a monster in the process :)
[21:35] <evand> not sure, I'll probe further
[21:35] <cjwatson> what we have done at least is reduce the required disk space
[21:35] <evand> ah, very true
[21:35] <cjwatson> we could back it all out; I'm insanely cautious about any optimisation on that code right now since we've already created a release notes entry requirement ...
[21:36] <cjwatson> has anyone been paying attention to ensure that it isn't removing anything it shouldn't remove any more?
[21:37] <evand> I haven't seen any new complaints, but I haven't run a test to make sure that two installs with and without the blacklist generates the same files.
[21:37] <evand> I can do that tonight though
[21:39] <cjwatson> you could also check the logged files
[21:41] <evand> actually, indeed
[21:41] <evand> watching that now
[21:42] <cjwatson> kirkland: can you confirm whether bug 227848 should be release-noted or fixed for intrepid? In the former case, could you provide some sample text?
[21:43] <kirkland> cjwatson: release noted;  we don't have time/resources for a proper fix for intrepid
[21:43] <kirkland> cjwatson: how long is such release note text, generally?
[21:44] <kirkland> cjwatson: 1 paragraph?  5 sentences or so?
[21:44] <cjwatson> kirkland: http://wiki.ubuntu.com/IntrepidReleaseNotes
[21:44] <kirkland> cjwatson: thx
[21:44] <cjwatson> usually a paragraph or two is fine
[21:48] <kirkland> cjwatson: actually, I stand corrected ....
[21:49] <kirkland> cjwatson: i don't think we really have anything to release-note
[21:49] <kirkland> cjwatson: we don't really have a viable workaround for intrepid
[21:49] <cjwatson> "it's broken"? :-)
[21:49] <kirkland> cjwatson: i think the priority should be lowered from Critical to High
[21:49] <cjwatson> please do that
[21:49] <kirkland> cjwatson: oh, just a release not to note the bug?
[21:49] <cjwatson> sometimes that is worthwhile
[21:50] <kirkland> cjwatson: okay
[21:50] <cjwatson> not currently supported, even though it looks like it should be, or whatever
[21:54] <kirkland> cjwatson: i'm working with EtienneG on it....
[22:22] <CIA-1> debian-installer: cjwatson * r982 ubuntu/ (build/Makefile debian/changelog):
[22:22] <CIA-1> debian-installer: Take /usr/share/localechooser/languagelist.data.gz into account when
[22:22] <CIA-1> debian-installer: building reduced font (LP: #287668).
[22:26] <ClaesBas> cjwatson: About the /boot size problem, it looks like do-release-upgrade dowloads the file intrepid.tar.gz which does some checks in DistUpgradeController.py ... That checks calculate from what it thinks is installed, NOT what is physically on the partition!
[22:26] <cjwatson> seriously, I'm not the expert here, it's probably best not to talk to me about it :)
[22:26] <ClaesBas> I had to "remove" all old kernels from apt....
[22:26] <cjwatson> err. you removed old kernels using rm rather than by removing the package?
[22:27] <cjwatson> be sure to say that in your bug report; that's unusual practice
[22:27] <cjwatson> I agree that it ought to cope with that
[22:29] <ClaesBas> I'm going to try fill in some bug report about now...
[22:51] <superm1> evand, given a DVD was finally functional today, i grabbed it and dropped it onto a recovery partition.  has a bunch of stuff changed with partman preseeding since  the last dvd? http://paste.ubuntu.com/61230/
[22:52] <persia> Oddly, in the current -mid image, I am shown step 5 iff I don't run in debug mode.  How could I best troubleshoot this?
[22:53] <superm1> along with this preseed: http://paste.ubuntu.com/61231/
[22:54] <cjwatson> superm1: could do with syslog and partman too
[22:55] <evand> I think I know what it is
[22:55]  * evand digs
[22:56] <evand> https://lists.ubuntu.com/archives/intrepid-changes/2008-October/008520.html
[22:56] <evand> superm1: preseed partman/filter_mounted to false
[22:56]  * evand steps out for a few
[22:56] <superm1> evand, okay i'll try
[22:57] <evand> sorry about that.  I had intended to send a notice of new preseed options the ubuntu-installer ML
[22:57] <evand> I'm going to try to get in the habit of doing so with each new ubiquity release
[22:58] <superm1> so this is supplemental to the existing ubiquity/partman-skip-unmount boolean true  then?
[23:04] <superm1> well that at least got it further, but it's just hanging at "1%: Creating ext3 file system for / in partition #3 of SCSI1 (0,0,0) (sda) ..." now, the python process with install.py as an argument is pegging the CPU too. hum
[23:06] <evand> superm1: read up a bit, we're on it :)
[23:07] <superm1> evand, ah okay.  need any other data points for  that too then?
[23:07] <evand> oh half that conversation is in #ubuntu-release
[23:07] <evand> back in a bit
[23:08] <kirkland> cjwatson: iscsi text sent your way via email
[23:08] <cjwatson> kirkland: can you put it in the bug, please?
[23:09] <kirkland> cjwatson: yup
[23:10] <kirkland> cjwatson: done: https://bugs.edge.launchpad.net/ubuntu/+source/open-iscsi/+bug/227848
[23:10] <cjwatson> thanks