[00:06] <drab> anybody familiar with bonding/lacp and iperf testing?
[00:06] <drab> I think my setup is correct, but the numbers disagree
[04:34] <vexati0n> does anyone have any idea how (or whether it's possible) to move an intact Snap app from one server to another one, including its data?
[07:04] <cpaelzer> good morning
[07:06] <lordievader> Good morning
[09:00] <jamespage> zul: when you start can you read me comments on https://bugs.launchpad.net/cloud-archive/+bug/1675088 please
[10:43] <Giane> Hi all I have a problem to configure my apache2 for redirect to 3 different webapps someone can help me?
[10:52] <zul> jamespage: doh i didnt see your comment
[10:52] <jamespage> zul: no worries
[12:26] <cpaelzer> jamespage - could you verify the rbd issue in bug 1672367 against yakkety proposed?
[12:27] <cpaelzer> jamespage: due to a stall in SRUs I merged this with the follow on, so it got no auto-update to the bug
[12:27] <cpaelzer> Last time you checked for your issue and ran a Tempest on it IIRC - repeating that on y-p would be great
[12:27] <cpaelzer> I'll do generic regressions tests on my side as well
[12:43] <hateball> Giane: did you try #httpd ?
[12:48] <Filystyn> is xinetd question ok here?
[13:01] <cpaelzer> Filystyn: just ask, there might be the chance that nobody knows but other than that feel free
[13:03] <Filystyn> ok i have xinetd service
[13:03] <Filystyn> but the bianry iopen server on same port udp and tcp
[13:03] <Filystyn> what protocol i pass in xinetd config
[13:03] <Filystyn> hm?
[13:03] <Filystyn> the bianry runs server udp and tcp on same port
[13:03] <Filystyn> so what service?
[13:23] <cpaelzer> Filystyn: there can be equally named service config statements in its config - in your case one for tcp and one for udp
[13:23] <cpaelzer> Filystyn: so copy&paste and change the prorocol
[13:45] <jamespage> cpaelzer: kicked the yakkety proposed tests off am today
[13:45] <jamespage> need to review
[13:48] <ronator> hi, I have an issue with ubuntu16 after release-upgrade and system-networking: the second network card always fails when trying to bring it up. the first one has no problems. "failed to bring up ens192" - how can I fix this? Do I have to use /etc/udev/rules.d/70-persistent-net.rules (it is emtpy but works for eth0/ens160)
[13:51] <ronator> feels verys much like this issue: http://askubuntu.com/questions/795592/failed-to-start-raise-network-interfaces
[13:52] <Filystyn> cpaelzer ok thx
[13:52] <ronator> Yes, I do have ens192 (confirmed)
[13:56] <jamespage> zul:  amd64 build of python-oslo.cache 1.19.0-0ubuntu1 in ubuntu zesty RELEASE
[13:56] <jamespage> is that you?
[13:58] <cpaelzer> jamespage: thanks, let me know once you had time to look at their results
[14:00] <zul> jamespage: yeah wrong ppa
[14:01] <zul> jamespage: ermm....yeah i created a pike-staging ppa so i can build deps going under openstack-ubuntu-testing group
[14:02] <jamespage> zul: good - we can stage everything in that and then sync out to the real pike-staging ppa and the pike ppa when things look good
[14:03] <zul> jamespage: yeah im building for zesty right now though
[14:03] <jamespage> zul: yeah I was just thinking about that
[14:03] <jamespage> zul: oh right yes I remember - this is the 'fake zesty' thing we chatted about yesterday right?
[14:03] <zul> jamespage: ill use backportpackage when im done is what im thinking
[14:04] <zul> jamespage: yeah i prefer 'in-between zesty'
[14:04] <ronator> systemd-networking drop-in replacement seems broken for more than one NIC - is this a known issue for ubuntu 16.04.2?
[14:25] <Giane> hateball, yes ty solved
[14:28] <hateball> :)
[14:35] <ronator> systemd-networking fixed
[15:06] <Filystyn> one more question
[16:11] <muser> So I am thinking about building a home file server using an older desktop. Does this sound like a waste of time? I plan to use a 1TB internal drive. My other laptops and desktops in the house will backup designated folders to this machine (just user files not system files).  We will also have Samba shares so we can transfer music and other things between our win/linux machines.  This server will then use an external usb drive to b
[16:11] <muser> ackup the internal drive weekly or so.
[16:16] <compdoc> sounds great, but 1TB isnt much space
[16:16] <nacc> muser: and what are you going to do to backup the file server?
[16:17] <nacc> muser: ah nm, i see the trailing line now
[16:20] <muser> It may be a 2 TB drive I Don't remember. I bought it about 6 months to a year ago. I just never could decide how I wanted to do it.
[16:20] <muser> I originally thought to RAID1 the share drive but read more about it and it was suggested to just to a straight scheduled backup instead.
[16:23] <muser> I have ubuntu server on the hardware already. Runs great no real power consumption. I haven't really looked into what it takes to schedule my backups on the other machines. They are a mix of Win8.1, Win7, and Mint of various versions.
[16:57] <blackrabbit> hello
[16:57] <blackrabbit> can you help me with step 6 on ubuntu server? I don't know what I should do http://doc.otrs.com/doc/manual/admin/5.0/en/html/manual-installation-of-otrs.html
[16:59] <rbasak> blackrabbit: you're more likely to get help on an OTRS support channel. Ubuntu doesn't ship OTRS and didn't write those instructions, so we don't know much about it here.
[17:01] <blackrabbit> rbasak, more ubuntu relate thing is that according to the manual, there should be folder "/etc/apache2/conf.d" but it seems that on ubuntu it's "etc/apache2/conf-enabled"
[17:01] <rbasak> Sounds like their instructions were written against a really old version of Ubuntu.
[19:39] <faekjarz> Hey there! I have one of those fancy i350-T4 NICs, out of China (not the power consumption optimized V2 though). It's got a plastic heat sink, yes plastic. Although there is thermally conductive plastic, of which heat sinks are made, I don't trust it. Until a proper metal heat sink is delivered next week, i'd like to keep an eye on the temperatures. Please give me a gentle nudge in the right direction, to monitoring i350 temps on 16.04. T
[19:44] <jge> hey all, trying to disable IPv6 on ubuntu (following directions here: https://paste.ee/p/Y8apy) but where do I put this "long-life config file?"
[19:48] <faekjarz> jge: you don't need to manually put it somewhere. The "...| sudo tee..." already does it.
[19:49] <sarnold> faekjarz: you were cut off at "temps on 16.04. T"
[19:50] <sarnold> faekjarz: plastic heat sink eh? sounds crazy
[19:50] <jge> faekjarz: oh wow, failed to see those commands are enclosed within the echo command.. thought they were separate :P
[19:50] <faekjarz> jge: tee works like a plumbers T-coupling, it writes to stdout, and to the specified file
[19:50] <jge> thanks
[19:51] <faekjarz> my cut-off remnants: Tools? Links? Maybe even howto guides? Anyone?
[19:51] <sarnold> faekjarz: in the past I've used lmsensors; I suspect these days there may be easier mechanisms, but I don't know any off-hand
[19:52] <sarnold> faekjarz: before going with lmsensors I'd probably try to find the relevant directory in /sys/devices/ for the NIC and see if there's any files that look useful.
[19:52] <sarnold> faekjarz: and it's wild speculation but maybe NRPE or collectd or similar has stats for your nic?
[19:52] <faekjarz> sarnold: i haven't installed my new puppy yet. Ah, yes, the mighty sysfs :)
[19:52] <sarnold> (which might be useful to steal from, if not use)
[19:53] <sarnold> faekjarz: hehe, that makes sense.
[19:54] <faekjarz> haha, AYE! But i want to play with it, so so bad. xD
[19:58] <faekjarz> well, i mean, i don't intend to load it to its max. capability (32, i.e. 4x8 VFs <3) → shouldn't become too hot. The >1k pages controller IC datasheet states Tcase Max. of >100°C. I doubt that i'll reach that high.
[19:59] <sarnold> maybe plastic is fine then? :) heh
[20:03] <faekjarz> *sigh* almost every other i350 on ebay seems to have a ~proper* metal heat sink …i chose the cheapest from China :\ That's why i'm concerned
[20:03] <sarnold> how about the rest of the thing? may be a "fourth shift" or similar knock off entirely :/
[20:16] <faekjarz> oh, it's got a "China Export" symbol, i.e. a CE (Conformite Europeanne, don't quote my spelling) - the C is supposed to be half a circle, of which the invisible half overlays the E up to the origin of the Es' center line
[20:18] <faekjarz> this is how the CE sign works https://upload.wikimedia.org/wikipedia/de/f/fd/CE-Norm.svg …the one on my NIC is way to narrow, hence it's a "China Export" sign :\
[20:21] <faekjarz> …however, thanks sarnold, i'll look into what you mentioned
[21:29] <DirtyCajun> Does anyone have any experience with the TACACS package?
[21:30] <DirtyCajun> tac_plus
[21:30] <bekks> !ask | DirtyCajun
[21:31] <DirtyCajun> Fine haha. I manage a large environment using TACACs and would like to break the tac_plus.conf file down in to sub sections similar to how Apache does. It does not like source /folderlocation. Has anyone tried or been successful in this endeavor and how?
[21:43] <sarnold> DirtyCajun: you could always generate it yourself, like cat /etc/cajun/tacos/*.conf > /etc/tacacswhatever.conf  in a systemd pre-exec line or init script or something similar


[04:22] <vibhav> hello
[04:30] <JoseeAntonioR> hello, vibhav.
[04:30] <vibhav> hey JoseeAntonioR
[05:28] <vibhav> j #ubuntu-devel
[12:19] <sevkooo> hii


[02:04] <vorlon> bdmurray: well, extras.ubuntu.com was designed to be a repo under Ubuntu governance for things that didn't fit the archive policy (e.g. things that wouldn't fit the SRU policy) and would be maintained by third-parties.  http://extras.ubuntu.com/ubuntu/dists/ has no releases past utopic and has effectively been superseded by the snap store
[02:27] -queuebot:#ubuntu-release- Unapproved: freeipmi (hirsute-proposed/main) [1.6.4-3ubuntu2 => 1.6.6-3] (ubuntu-desktop) (sync)
[06:04] -queuebot:#ubuntu-release- Unapproved: openldap (focal-proposed/main) [2.4.49+dfsg-2ubuntu1.7 => 2.4.49+dfsg-2ubuntu1.8] (i386-whitelist, ubuntu-server)
[06:17] -queuebot:#ubuntu-release- Unapproved: rabbitmq-server (focal-proposed/main) [3.8.2-0ubuntu1.1 => 3.8.2-0ubuntu1.2] (ubuntu-server)
[06:18] -queuebot:#ubuntu-release- Unapproved: rabbitmq-server (groovy-proposed/main) [3.8.5-1 => 3.8.5-1ubuntu0.1] (ubuntu-server)
[07:28] -queuebot:#ubuntu-release- Unapproved: qtwebkit-opensource-src (hirsute-proposed/universe) [5.212.0~alpha4-11 => 5.212.0~alpha4-12] (i386-whitelist, kubuntu, qt5) (sync)
[07:29] -queuebot:#ubuntu-release- Unapproved: qtwebengine-opensource-src (hirsute-proposed/universe) [5.15.3+dfsg-3ubuntu1 => 5.15.3+dfsg-5] (kubuntu) (sync)
[07:53] -queuebot:#ubuntu-release- Unapproved: manila (hirsute-proposed/universe) [1:12.0.0~rc1-0ubuntu1 => 1:12.0.0~rc1-0ubuntu2] (openstack)
[07:59] -queuebot:#ubuntu-release- Unapproved: openjdk-17 (hirsute-proposed/universe) [17~15-1 => 17~17-1] (i386-whitelist)
[08:01] <RikMills> si
[08:01] <RikMills> oops
[08:02] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-17 [source] (hirsute-proposed) [17~17-1]
[08:03] -queuebot:#ubuntu-release- Unapproved: mame (hirsute-proposed/universe) [0.230+dfsg.1-1ubuntu1 => 0.230+dfsg.1-1ubuntu2] (no packageset)
[08:05] -queuebot:#ubuntu-release- Unapproved: accepted mame [source] (hirsute-proposed) [0.230+dfsg.1-1ubuntu2]
[08:07] -queuebot:#ubuntu-release- Unapproved: accepted freeipmi [sync] (hirsute-proposed) [1.6.6-3]
[08:07] -queuebot:#ubuntu-release- Unapproved: accepted mesa [sync] (hirsute-proposed) [21.0.1-2]
[08:07] -queuebot:#ubuntu-release- Unapproved: accepted manila [source] (hirsute-proposed) [1:12.0.0~rc1-0ubuntu2]
[08:07] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (hirsute-proposed) [1:78.9.0+build2-0ubuntu3]
[08:27] -queuebot:#ubuntu-release- Unapproved: ukui-control-center (hirsute-proposed/universe) [3.0.2-2 => 3.0.2-2ubuntu1] (ubuntukylin)
[08:29] -queuebot:#ubuntu-release- Unapproved: accepted ukui-control-center [source] (hirsute-proposed) [3.0.2-2ubuntu1]
[08:47] <sil2100> xnox: hey! So I'm looking at releasing the grub2 SRUs and I started thinking: won't it actually cause trouble for us in the future if we don't release it for both -updates and -security?
[08:48] <sil2100> xnox: I mean, any security update of grub2 would then need the whole 'stack' pushed
[08:52] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (hirsute-proposed) [247.3-3ubuntu3]
[08:54] -queuebot:#ubuntu-release- Unapproved: accepted deja-dup-caja [source] (hirsute-proposed) [0.0.9-0ubuntu1]
[08:54] -queuebot:#ubuntu-release- Unapproved: accepted libubootenv [sync] (hirsute-proposed) [0.3-2]
[08:54] -queuebot:#ubuntu-release- Unapproved: accepted xubuntu-artwork [source] (hirsute-proposed) [21.04.1]
[09:01] -queuebot:#ubuntu-release- Unapproved: bluedevil (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: breeze-gtk (hirsute-proposed/universe) [5.21.3-0ubuntu1 => 5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: breeze-grub (hirsute-proposed/universe) [5.21.3-0ubuntu1 => 5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: breeze (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: breeze-plymouth (hirsute-proposed/universe) [5.21.3-0ubuntu1 => 5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kactivitymanagerd (hirsute-proposed/universe) [5.21.3-0ubuntu1 => 5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kde-gtk-config (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kdeplasma-addons (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: khotkeys (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kmenuedit (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: drkonqi (hirsute-proposed/universe) [5.21.3-0ubuntu1 => 5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kdecoration (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kinfocenter (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kde-cli-tools (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:01] -queuebot:#ubuntu-release- Unapproved: kgamma5 (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: kscreen (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: ksshaskpass (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: kwallet-pam (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: kwayland-server (hirsute-proposed/universe) [5.21.3-0ubuntu1 => 5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: kwrited (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: libksysguard (hirsute-proposed/universe) [4:<IP_ADDRESS>-0ubuntu2 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: oxygen (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: kscreenlocker (hirsute-proposed/universe) [5.21.3-0ubuntu2 => 5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: kwayland-integration (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: libkscreen (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: ksysguard (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: milou (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:02] -queuebot:#ubuntu-release- Unapproved: kwin (hirsute-proposed/universe) [4:5.21.3-0ubuntu1 => 4:5.21.4-0ubuntu1] (kubuntu) (sync)
[09:03] <slyon> hey sil2100! Should we restore the previous netplan SRU (0.101-0ubuntu3~20.04.2) to focal-updates for the time being, as noted by IBM (https://bugs.launchpad.net/netplan/+bug/1922898/comments/11)?  I'm not sure if the 0.101 focal binaries are still available somewhere.. I've re-deployed them to a PPA if you need it: https://launchpad.net/~slyon/+archive/ubuntu/lp1922898/+packages
[09:08] <sil2100> They are, no worries
[09:08] <sil2100> LP is really slow and I didn't notice the copy failures
[09:10] <sil2100> slyon: ok, sorry about that! Should be good in a few minutes
[09:11] <slyon> sil2100: thanks!
[09:11] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [sync] (focal-updates) [0.101-0ubuntu3~20.04.2]
[09:16] -queuebot:#ubuntu-release- Unapproved: rejected glibc [sync] (focal-proposed) [2.31-0ubuntu9.3]
[09:21] -queuebot:#ubuntu-release- Unapproved: gtk+3.0 (hirsute-proposed/main) [3.24.25-1ubuntu3 => 3.24.25-1ubuntu4] (i386-whitelist, ubuntu-desktop)
[09:29] -queuebot:#ubuntu-release- Unapproved: accepted glibc [sync] (groovy-proposed) [2.32-0ubuntu3.2]
[09:48] -queuebot:#ubuntu-release- Unapproved: accepted glibc [sync] (focal-proposed) [2.31-0ubuntu9.3]
[09:51] <doko> starting to remove pocl/pyopencl binaries for riscv64, as done in debian ...
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [source] (groovy-proposed) [1.4.7-0~20.10.1]
[10:09] -queuebot:#ubuntu-release- Unapproved: accepted fwupd-signed [source] (groovy-proposed) [1.30.1]
[10:16] -queuebot:#ubuntu-release- New binary: icingaweb2-module-incubator [amd64] (hirsute-proposed/universe) [0.6.0-1] (no packageset)
[10:18] -queuebot:#ubuntu-release- New: accepted icingaweb2-module-incubator [amd64] (hirsute-proposed) [0.6.0-1]
[10:21] -queuebot:#ubuntu-release- Unapproved: fwupd (groovy-proposed/main) [1.4.7-0~20.10.1 => 1.4.7-0~20.10.1] (core)
[10:22] -queuebot:#ubuntu-release- Unapproved: fwupd (groovy-proposed/main) [1.4.7-0~20.10.1 => 1.4.7-0~20.10.1] (core)
[10:22] -queuebot:#ubuntu-release- Unapproved: fwupd (groovy-proposed/main) [1.4.7-0~20.10.1 => 1.4.7-0~20.10.1] (core)
[10:28] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (groovy-proposed) [1.4.7-0~20.10.1]
[10:28] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (groovy-proposed) [1.4.7-0~20.10.1]
[10:28] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (groovy-proposed) [1.4.7-0~20.10.1]
[10:42] -queuebot:#ubuntu-release- Unapproved: nettle (hirsute-proposed/main) [3.7-2.1 => 3.7-2.1ubuntu1] (core, i386-whitelist)
[10:57] <ricotz> sil2100, hi :), regarding libreoffice, feel free to ask if you have questions, note that there are two libreoffice packages waiting, focal and groovy
[11:51] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (hirsute-proposed/main) [1:0.8.8 => 1:0.8.9] (desktop-core)
[11:56] <sil2100> ricotz: sure! I'm on it right now ;)
[12:08] <rbasak> sil2100: o/ I'm going to look at libpod and golang-github-containers-buildah in groovy unapproved as they're fixes for the container stack SRUs.
[12:08] <sil2100> rbasak: ACK o/
[12:08] <sil2100> Thanks for the heads up o/
[12:11] <sil2100> ricotz: hey, to get everything SRU compliant - could you provide the SRU information for bugs LP: #1897784 and LP: #1916786 ? I mean things like a possible test-case and regression potential ('Where problems could occur')
[12:15] -queuebot:#ubuntu-release- Unapproved: texlive-extra (hirsute-proposed/universe) [2020.20210202-1 => 2020.20210202-3] (i386-whitelist, kubuntu) (sync)
[12:16] -queuebot:#ubuntu-release- Unapproved: accepted golang-github-containers-buildah [source] (groovy-proposed) [1.15.2-1ubuntu2.2]
[12:18] -queuebot:#ubuntu-release- Unapproved: accepted libpod [source] (groovy-proposed) [2.0.6+dfsg1-1ubuntu1.2]
[12:21] -queuebot:#ubuntu-release- Unapproved: texlive-bin (hirsute-proposed/main) [2020.20200327.54578-6 => 2020.20200327.54578-7] (i386-whitelist, ubuntu-desktop) (sync)
[12:21] -queuebot:#ubuntu-release- Unapproved: tipa (hirsute-proposed/universe) [2:1.3-20.1 => 2:1.3-21] (i386-whitelist, kubuntu) (sync)
[12:25] <ricotz> sil2100, the proposed fix for #1897784 is a simple null-check, so no regression potential -- #1916786 is a move from Suggests to Recommends which was confirmed as a fix
[12:26] -queuebot:#ubuntu-release- Unapproved: alqalam (hirsute-proposed/universe) [0.2-8.1 => 0.2-9] (no packageset) (sync)
[12:26] <ricotz> sil2100, the dedicated SRU bug report provide all the information needed, as autopkgtest runs and installation testing
[12:26] -queuebot:#ubuntu-release- Unapproved: accepted alqalam [sync] (hirsute-proposed) [0.2-9]
[12:27] <sil2100> Ok, let's link those together then. Since basically per SRU policy if a bug is mentioned in the changelog, it requires an explicit test case and regression analysis
[12:28] <sil2100> But let's conditionally accept it by linking the main SRU bug in both, let me do that
[12:28] <ricotz> I see, thank you
[12:49] <sil2100> Ok, groovy looks good, approved!
[12:50] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [sync] (groovy-proposed) [1:7.0.5-0ubuntu<IP_ADDRESS>]
[12:54] -queuebot:#ubuntu-release- Unapproved: accepted texlive-bin [sync] (hirsute-proposed) [2020.20200327.54578-7]
[12:54] -queuebot:#ubuntu-release- Unapproved: accepted tipa [sync] (hirsute-proposed) [2:1.3-21]
[12:54] -queuebot:#ubuntu-release- Unapproved: accepted texlive-extra [sync] (hirsute-proposed) [2020.20210202-3]
[12:54] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-drivers-common [source] (hirsute-proposed) [1:0.8.9]
[13:09] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [sync] (focal-proposed) [1:6.4.7-0ubuntu<IP_ADDRESS>]
[13:33] -queuebot:#ubuntu-release- Unapproved: greenbone-security-assistant (hirsute-proposed/universe) [7.0.3+dfsg.1-1 => 20.8.0-2ubuntu1] (no packageset)
[13:33] -queuebot:#ubuntu-release- Unapproved: accepted greenbone-security-assistant [source] (hirsute-proposed) [20.8.0-2ubuntu1]
[13:40] -queuebot:#ubuntu-release- New: rejected bootgen-xlnx [sync] (hirsute-proposed) [2020.2-0ubuntu1]
[13:42] -queuebot:#ubuntu-release- Unapproved: avahi (hirsute-proposed/main) [0.8-5ubuntu2 => 0.8-5ubuntu3] (core, i386-whitelist)
[13:53] -queuebot:#ubuntu-release- New sync: bootgen-xlnx (hirsute-proposed/primary) [2020.2-0ubuntu3]
[14:35] -queuebot:#ubuntu-release- Unapproved: interimap (hirsute-proposed/universe) [0.5.6-1 => 0.5.6-1ubuntu1] (no packageset)
[14:36] -queuebot:#ubuntu-release- Unapproved: accepted interimap [source] (hirsute-proposed) [0.5.6-1ubuntu1]
[14:54] <bdmurray> xnox: We'd previously talked about the hirsute riscv64 image not booting with qemu-system-riscv64. What was the outcome of that?
[14:55] <bdmurray> plars also indicated they are not booting on unleashed
[14:58] -queuebot:#ubuntu-release- Unapproved: xorg-server (hirsute-proposed/main) [2:1.20.10-3ubuntu5 => 2:1.20.10-3ubuntu6] (desktop-core, i386-whitelist, xorg)
[15:03] <xnox> bdmurray: yeah, i am debugging this.
[15:04] <bdmurray> xnox: Should we have a bug for that?
[15:04] <xnox> sil2100:  grub2 was built in security; grub2-(un)signed are bootloaders only freestanding code without any runtime deps.
[15:04] <xnox> bdmurray:  yes.
[15:04] <sil2100> Ah, ok! Looked at the wrong package then! duh
[15:13] -queuebot:#ubuntu-release- Unapproved: cinder (groovy-proposed/main) [2:17.0.1-0ubuntu2 => 2:17.1.0-0ubuntu1] (openstack)
[15:13] -queuebot:#ubuntu-release- Unapproved: neutron (groovy-proposed/main) [2:17.1.0-0ubuntu3 => 2:17.1.1-0ubuntu1] (openstack)
[15:16] -queuebot:#ubuntu-release- Unapproved: nova (groovy-proposed/main) [2:22.1.0-0ubuntu1 => 2:22.2.0-0ubuntu1] (openstack)
[15:16] -queuebot:#ubuntu-release- Unapproved: octavia (groovy-proposed/universe) [7.1.0-0ubuntu1 => 7.1.1-0ubuntu1] (openstack)
[15:19] -queuebot:#ubuntu-release- Unapproved: horizon (groovy-proposed/main) [4:18.6.1-0ubuntu1.1 => 4:18.6.2-0ubuntu1] (openstack)
[15:59] <xnox> sil2100:  https://code.launchpad.net/~xnox/ubuntu-archive-tools/slow-grub-shim/+merge/400814
[15:59] <xnox> for slow phasing
[16:00] <sil2100> o/
[16:16] <sil2100> xnox: ok, +1, but I guess we'd want to revert at least the grub2 bits once we land the current SRU, right?
[16:16] <sil2100> Since I'm not sure if we want to slow phase grub2 always
[16:17] <vorlon> honestly I'm not sure it matters to slow it now either as the current SRU is just about dropping binary packages
[16:18] <vorlon> also, are there specific upgrade interactions if someone has grub2 ready to phase but grub2-signed not?  Remembering that the phasing for each source package is independent
[16:18] <vorlon> (hopefully we've done all the versioned dependencies correctly such that things will just be held back)
[16:18] <sil2100> vorlon: ok, wanted to play it safe, but if you think it's not risky, I guess let's just release as-is
[16:19] <sil2100> Maybe at least releasing one series at a time?
[16:19] <sil2100> I'd start with groovy today and with focal on Monday, see how it goes
[16:19] <vorlon> mm?  I'm only speaking about the phasing
[16:19] -queuebot:#ubuntu-release- New sync: icingaweb2-module-reporting (hirsute-proposed/primary) [0.9.2+20200529-1]
[16:20] -queuebot:#ubuntu-release- New sync: icingaweb2-module-generictts (hirsute-proposed/primary) [2.0.0+20201009-1]
[16:20] -queuebot:#ubuntu-release- New sync: icingaweb2-module-toplevelview (hirsute-proposed/primary) [0.3.1-1]
[16:21] <sil2100> Yeah, I mean instead of slow phasing, maybe it's enough if we just release one-series at a time with regular phasing - to play it safe
[16:21] -queuebot:#ubuntu-release- New: accepted icingaweb2-module-generictts [sync] (hirsute-proposed) [2.0.0+20201009-1]
[16:21] -queuebot:#ubuntu-release- New: accepted icingaweb2-module-toplevelview [sync] (hirsute-proposed) [0.3.1-1]
[16:21] -queuebot:#ubuntu-release- New: accepted icingaweb2-module-reporting [sync] (hirsute-proposed) [0.9.2+20200529-1]
[16:22] <vorlon> sil2100: I was only referring to the grub2 source package not needing phasing.  But we don't want to release grub2 alone, we want it released together with grub2-signed + grub2-unsigned
[16:22] <vorlon> so I am NOT arguing against xnox's branch
[16:23] <vorlon> and I do think we should do this in parallel across releases, not serially
[16:25] -queuebot:#ubuntu-release- New binary: icingaweb2-module-generictts [amd64] (hirsute-proposed/none) [2.0.0+20201009-1] (no packageset)
[16:26] -queuebot:#ubuntu-release- Unapproved: makedumpfile (hirsute-proposed/main) [1:1.6.8-3 => 1:1.6.8-4] (core) (sync)
[16:26] -queuebot:#ubuntu-release- New: accepted icingaweb2-module-generictts [amd64] (hirsute-proposed) [2.0.0+20201009-1]
[16:27] -queuebot:#ubuntu-release- New binary: icingaweb2-module-toplevelview [amd64] (hirsute-proposed/none) [0.3.1-1] (no packageset)
[16:28] -queuebot:#ubuntu-release- New: accepted icingaweb2-module-toplevelview [amd64] (hirsute-proposed) [0.3.1-1]
[16:28] -queuebot:#ubuntu-release- New binary: icingaweb2-module-reporting [amd64] (hirsute-proposed/none) [0.9.2+20200529-1] (no packageset)
[16:34] <rbalint> vorlon, why not later releases first? people or older releases likely have stronger preference to avoid regressions
[16:34] <xnox> vorlon:  it's not possible to release grub2 alsone.
[16:34] <LocutusOfBorg> doko, its always a sad day when gcc segfaults due to new lto changes...
[16:34] <LocutusOfBorg> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/21369216
[16:34] -queuebot:#ubuntu-release- New: accepted icingaweb2-module-reporting [amd64] (hirsute-proposed) [0.9.2+20200529-1]
[16:34] <rbalint> vorlon, i think delayed SRU releases across series from newer to older should be the default process
[16:35] <LocutusOfBorg> gcc: fatal error: Killed signal terminated program lto1
[16:35] <LocutusOfBorg> compilation terminated.
[16:35] <LocutusOfBorg> lto-wrapper: fatal error: gcc returned 1 exit status
[16:35] <LocutusOfBorg> so now libguestfs doesn't build anymore due to new golang and new lto...
[16:35] <xnox> vorlon: current grub2 + grub2-signed have strict deps. so all three needs releasing together.
[16:38] <doko> LocutusOfBorg: well, the lto issue was hidden behind the golang issue
[16:39] <LocutusOfBorg> yes doko! I found it after fixing the golang sadness...
[16:39] <LocutusOfBorg> I tried the -fnolto in DEB_MAINT_OPTIONS as we did on llvm-12
[16:39] <LocutusOfBorg> let me see
[16:40] <LocutusOfBorg> +export DEB_BUILD_MAINT_OPTIONS=optimize=-lto
[16:40] <LocutusOfBorg> .this one
[16:40] <doko> is it s390x only?
[16:40] <LocutusOfBorg> nack, its *all*
[16:40] <doko> ok, I'll have a look later
[16:40] <LocutusOfBorg> I'll upload on archive if the build is fine
[16:41] <LocutusOfBorg> if you want to reproduce just use the patch for golang and remove the line on rules I think
[16:53] -queuebot:#ubuntu-release- Unapproved: gcc-10 (hirsute-proposed/main) [10.2.1-24ubuntu1 => 10.3.0-1ubuntu1] (core, i386-whitelist)
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted gcc-10 [source] (hirsute-proposed) [10.3.0-1ubuntu1]
[17:20] -queuebot:#ubuntu-release- Unapproved: flatpak (hirsute-proposed/universe) [1.10.2-1 => 1.10.2-1ubuntu1] (ubuntu-budgie, xubuntu)
[17:20] -queuebot:#ubuntu-release- Unapproved: accepted avahi [source] (hirsute-proposed) [0.8-5ubuntu3]
[17:20] -queuebot:#ubuntu-release- Unapproved: accepted nettle [source] (hirsute-proposed) [3.7-2.1ubuntu1]
[17:20] -queuebot:#ubuntu-release- Unapproved: accepted gtk+3.0 [source] (hirsute-proposed) [3.24.25-1ubuntu4]
[17:20] -queuebot:#ubuntu-release- Unapproved: accepted xorg-server [source] (hirsute-proposed) [2:1.20.10-3ubuntu6]
[17:31] -queuebot:#ubuntu-release- Unapproved: zaqar-ui (hirsute-proposed/universe) [9.0.0+git2021012814.bbf2703-0ubuntu1 => 10.0.0~rc1-0ubuntu1] (openstack)
[17:34] -queuebot:#ubuntu-release- Unapproved: libguestfs (hirsute-proposed/universe) [1:1.44.1-1ubuntu1 => 1:1.44.1-1ubuntu2] (no packageset)
[17:34] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (hirsute-proposed/multiverse) [6.1.18-dfsg-3ubuntu<IP_ADDRESS> => 6.1.18-dfsg-4ubuntu<IP_ADDRESS>] (kernel-dkms)
[17:35] -queuebot:#ubuntu-release- Unapproved: accepted libguestfs [source] (hirsute-proposed) [1:1.44.1-1ubuntu2]
[17:44] -queuebot:#ubuntu-release- Unapproved: vitrage (hirsute-proposed/universe) [7.3.0+git2021012713.fd833604-0ubuntu1 => 7.4.0-0ubuntu1] (openstack)
[17:44] -queuebot:#ubuntu-release- Unapproved: zaqar (hirsute-proposed/universe) [11.0.0+git2021012713.656b9373-0ubuntu1 => 12.0.0~rc1-0ubuntu1] (no packageset)
[17:44] -queuebot:#ubuntu-release- Unapproved: accepted zaqar [source] (hirsute-proposed) [12.0.0~rc1-0ubuntu1]
[17:45] <LocutusOfBorg> please accept virtualbox-hwe finally fixing vboxvideo
[17:48] -queuebot:#ubuntu-release- Unapproved: vmware-nsx (hirsute-proposed/universe) [17.0.0+git2021012713.2f49527e3-0ubuntu1 => 17.0.0+git2021040813.116ac637a-0ubuntu1] (openstack)
[18:35] <vorlon> xnox: yes, that's what I said, we don't want to release grub2 alone.
[18:48] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (hirsute-proposed/multiverse) [6.1.18-dfsg-3ubuntu<IP_ADDRESS> => 6.1.18-dfsg-5ubuntu<IP_ADDRESS>] (kernel-dkms)
[18:56] <xnox> oh ok
[20:08] <rbalint> vorlon, please merget this last round for glibc https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/400835
[20:14] <vorlon> rbalint: is there a baseline retest for ipset showing it's not triggered by the new glibc?
[20:18] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (hirsute-proposed/main) [1:21.04.6 => 1:21.04.7] (core)
[20:49] <vorlon> rbalint: (now there is)
[21:05] -queuebot:#ubuntu-release- Unapproved: python-django (hirsute-proposed/main) [2:2.2.19-1ubuntu1 => 2:2.2.20-1] (no packageset) (sync)
[21:08] -queuebot:#ubuntu-release- Unapproved: mumps (hirsute-proposed/universe) [5.3.5-1build1 => 5.3.5-2] (no packageset) (sync)
[21:09] -queuebot:#ubuntu-release- Unapproved: accepted mumps [sync] (hirsute-proposed) [5.3.5-2]
[21:09] -queuebot:#ubuntu-release- Unapproved: petsc (hirsute-proposed/universe) [3.14.4+dfsg1-2 => 3.14.5+dfsg1-2] (no packageset) (sync)
[21:09] -queuebot:#ubuntu-release- Unapproved: accepted petsc [sync] (hirsute-proposed) [3.14.5+dfsg1-2]
[21:21] <bdmurray> vorlon: I'm releasing ubuntu-release-upgrader to focal as that was sil2100's intent but the copy package failed
[21:40] <vorlon> bdmurray: failed how?
[22:48] -queuebot:#ubuntu-release- Unapproved: plocate (hirsute-proposed/universe) [1.1.5-1 => 1.1.7-1] (ubuntu-budgie, xubuntu) (sync)
[22:50] <bdmurray> vorlon: probably a Launchpad timeout - I got some on Tuesday
[22:51] <vorlon> bdmurray: hmm, I didn't see any emails about this copy failure, which is supposed to be what happens now
[22:52] <bdmurray> vorlon: Oh yeah, I did get one on Tuesday
[22:52] <vorlon> bdmurray: and u-r-u shows up now as ready to be removed from -proposed according to https://people.canonical.com/~ubuntu-archive/pending-sru.html#cleanup
[22:53] <bdmurray> vorlon: right because I released it for real
[22:53] <vorlon> ok
[22:53] <vorlon> oh I see, it was sil2100's copy that failed, not yours?
[22:53] <bdmurray> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152 see comment #17
[22:53] <bdmurray> yes
[22:53] <bdmurray> I was cleaning up my cards and noticed it wasn't Fix Released although that's what he intended
[23:22] <vorlon> what the heck, why did mobile-tweaks' binaries get synced as Priority: important?
[23:24] <vorlon> xnox: are we resolving perl+perl-modules being pulled into required, prior to release?


[00:00] <bdmurray> xteejx: roughly right is kind of vague.  Let's say you have a bug with someone's upgrade and you suspect it might be hardware.  I'd recommend setting the package to update-manager anyway as there are some knowledgable update-manager triagers who could help.  Does that clarify things?
[00:01] <xteejx> Definately, and it might just encourage more users to want to do it, for the _fun_ of it, and might even bring more people to Ubuntu, M$ has this office type look and directed at them users, Ubuntu doesn't have to be "geeks" anymore, its a laugh....if you get what I mean
[00:02] <xteejx> bdmurray: It does :) I meant...say if its I dunno...someones laptop screen flashes a lot, do I put it as kernel (linux) for possible acpi problems, etc...that kind of vagueness I meant :)
[00:02] <bdmurray> xteejx: In that case I'd leave it alone until you have more information
[00:04] <xteejx> bdmurray: Cool, just wanted to make sure. Also, I've applied to bug control any idea how long it takes for them to review the application, and do they look at my poor attempts at bug solving? lol
[00:04] <angusthefuzz> xteejx: see bug #295141 for example.  I just started working on it, and from the initial comments its impossible to tell what package it belongs to, even though i have a guess.
[00:05] <bdmurray> xteejx: The turn around time is 1 week.  Additionally, I don't see any specific example bugs in your application.
[00:06] <persia> Having the example bugs in the application is key to getting good comments from peers.
[00:06] <xteejx> bdmurray: Oh is it you who does it? Didn't realise, and also I didn't put any on there as I haven't done that many, I've just tried picking at bits of old ones, see if they're still valid and if so try pushing them through, you're perfectly welcome to look at my launchpad xteejx if you need to
[00:06] <xteejx> angusthefuzz: I'd be _thinking_ maybe xkb? How many points do I get? lol
[00:07] <persia> xteejx, Anyone in bug control can comment on the application, for or against.  If you add good bugs, it not only shows that you can triage, but that you can recognise good triage, which is helpful to show you're ready.
[00:07] <xteejx> Or the kernel possibly, I'd get more info I guess
[00:07] <angusthefuzz> xteejx: often hotkeys that dont turn off are kernel bugs, from what i have seen
[00:08] <bdmurray> xteejx: Additionally, we really want to know what Importance you'd give the bugs since that is something you'd be able to do as a part of the team.
[00:08] <persia> I remember one candidate who picked a poor set of bugs, and was rejected, and then reapplied a couple days later with a different set of bugs (all from before the first application), and was approved.
[00:08] <angusthefuzz> xteejx: but you are right, we need more information
[00:08] <xteejx> Damn, so I'm going to be denied straight away then on that basis that I haven't listed any.
[00:11] <persia> Well, you might get lucky that enough people know you and your work well enough to say enough good things in a week, but you might want to send a follow-up with a list of 5-7 bugs where you did an especially good job to improve your chances.
[00:11] <xteejx> It's no big deal anyway, I just thought it would help all of you out. I know you got shed loads to do as it is, and I'm online at least 8 hours a day :) But I really do want to help out, I love Ubuntu, I diss windows to my mates all the time but I guess I would :)
[00:12] <xteejx> persia: I haven't done enough really, I've just been clearing out old crunf to be honest
[00:13] <xteejx> I'm not sure if I had bug control a few years ago to be honest on my old account mcisbackuk, can anyone check that at all?
[00:13] <persia> You're mcisbackuk?  I remember you.  Just check launchpad.net/~mcisbackuk
[00:14] <xteejx> Yeah than
[00:14] <xteejx> *Yeah thats me persia :) Thought I remembered your name as well hehe
[00:14] <xteejx> persia: I must have deleted the account it's gone
[01:29] <zombuntu> anyone have suspend problems?
[01:29] <angusthefuzz> zombuntu: there are many bugs about suspend, did you have a particular question?
[01:31] <zombuntu> i used to use the proprietary driver but in 8.10 its not available cause of xorg 7.3 compatability. i was able to fix supend with that driver but not this new one
[01:31] <persia> Which proprietary driver?
[01:31] <maco> ati's or nvidia's?
[01:31] <zombuntu> nvidia
[01:32] <zombuntu> im thinking of going back to 8.04 lts
[01:33] <zombuntu> the new driver doesnt hand acceleration very good either
[01:35] <persia> Not much the Ubuntu devs can do about the nVidia driver.  If it's not working as well for you, 8.04 might be a good option for the short term.  I'd recommend subscribing to some of the outstanding bugs against the driver, just so you'll be notified when they close.
[01:36] <persia> nVidia provides some support in their forums, and being willing to test candidates there might be a faster route towards getting support working though.
[01:36] <zombuntu> suspend is an old issue. seems like they could've fixed it by now
[01:37] <zombuntu> i check launchpad: bugs
[01:37] <maco> it's not a bug ubuntu can fix
[01:38] <maco> because the bug is in nvidia's proprietary driver, meaning we have no access to the code to fix anything at all
[01:38] <persia> Yeah, well.  My nVidia card still overheats for no good reason, the drivers are still not -rt safe, and sometimes some people still get the screen-frozen-mouse-moves crash.  There's a lot of bits need chasing, and only a few people doing it (and I think they spend most of their time on getting new cards to work).
[01:38] <persia> If you're feeling particularly interested, you could try to convince nVidia that if they open the source, you'll help fix the bugs, but you'll have to mean it.
[01:39] <maco> persia: screen-frozen-but-mouse-moves....what's crashing in that case? i get that one with intel on occasion. though more often lately it's screen-frozen-and-mouse-too-but-caps-not-blink-so-maybe-not-panic
[01:39] <zombuntu> nvidia- get your stuff together
[01:39] <maco> yeah, thats about it
[01:39] <maco> we were all hoping ati's opening of their driver would force nvidia's hand a bit
[01:40] <zombuntu> hopefully it will sometime
[01:41] <persia> macd, I've stopped following that bug.  Was it bug #13977 ?  Anyway, from when I was following it, there were about 5 different reasons, but it was a hard kernel freeze and yet the video card was still operative and running the hardware mouse pointer.
[01:41] <persia> Nope.  I didn't remember correctly :)  13xxx anyway.
[01:41] <angusthefuzz> now there is a descriptive title
[01:41] <persia> The devs were chasing them, and hit most of them, so it's rare now.  These days when the kernel locks, the driver mostly shuts down the screen.
[01:42] <persia> angusthefuzz, well, it was enough to fix it :)
[01:42] <angusthefuzz> clearly persia
[01:43] <maco> hm, still need to figure out how to make the kernel stop locking then
[01:45] <persia> Ah, bug #13530.
[01:45] <persia> maco, kernel locks because it's in a code path inside the binary blob.
[01:46] <persia> That's a different issue.  If you want to chase it, install the debug version of the driver, and report the cryptic information from Xorg.0.log in the support forum.
[01:48] <persia> the Xids and Nids are sometimes enough that the developers can reproduce it, at which point it gets tracked internallly (and invisibly to us mortals) and a fixd might land sometime.
[04:13] <ScottK> bdmurray: When your around I've got a topic I'd like to discuss  with you.
[05:24]  * cllaudyu am revenit!
[11:39] <user1> hello
[11:39] <user1> I upgraded 8.04 -> 8.10   and it failed epically  when  by hand mounting iso image to a directory instead using a real cd...
[11:40] <user1> upgradecd program couldn't even unpack the installer because he had trouble deducing the cdname (using `pwd` helped)
[11:51] <BUGabundo> does any one know a dupe for https://bugs.edge.launchpad.net/ubuntu/+source/vlc/+bug/295519 ?
[13:31] <ToHellWithGA> morning
[13:32] <ToHellWithGA> is a lack of options in "systemsettings", the package which controls system settings for kde (sound, mouse, keyboard, i18n, etc.) a good enough reason to find a bug?
[13:32] <ToHellWithGA> when the package "kcontrol" was installed for adjusting kde3 settings under gnome i was able to configure keyboard and mouse
[13:32] <ToHellWithGA> with "systemsettings" (with or without "kdebase") there is no option to adjust mouse settings
[13:33] <ToHellWithGA> .me leaves for a 5k charity walk/run (more walk than run for me) and returns later to check decision from bug-ubunteros
[13:33] <ToHellWithGA> cheers
[13:53] <xteejx> Hey guys, I've noticed a BIG inconsistency in the Wiki pages, a few pages say change bugs to Confirmed ifother users are having the same problem OR if there's enough logs and information that could help devs, some other pages say only when there's more than 1 user with the problem...which is right, as I've been using the 1st...I'm kinda stumped now as to which is correct??
[13:55] <arno_b> xteejx: I agree. I usually confirm when there is several guys that have the same problem (and if there is enough information)
[13:56] <xteejx> arno_b: Cool, it's just weird some wiki pages saying one thing, and others saying another
[13:58] <xteejx> Don't know if anyone is able to look into it at some point, as it might be confusing for new triagers? :) Just a thought
[14:00] <xteejx> Question: What is the reason bugs like bug 40306 is still set as "New"? I'm a little confused, as it's set as Wishlist, and its an oldie?
[14:04] <joumetal> xteejx: hmm seems that gnome-accessibility package exists now.
[14:06] <xteejx> That's what I thought, isn't most of this old stuff just old crunf that's been fixed since? I'm going to go through the really old needs-packaging stuff, check if its in Ubuntu now and Invalidate it if so :)
[14:12] <joumetal> Good idea. For that particular bug fix released seems to be good status.
[14:17] <xteejx> Cool.
[14:23] <joumetal> Tags confuses me. Let's take tag edgyeft. It has 2 bugs invalid and fix released. Tag is showing one and it is unsupported release.
[14:26] <angusthefuzz> xteejx: I asked about that discrepancy about a week ago, I was told if debugging procedures for that package are met, it can be marked confirmed
[14:28] <angusthefuzz> xteejx: that is also one of the major differences between confirmed and triaged, two users who have a problem = confirmed, all the necessary information present = triaged.  Think of triaged as an advanced state of confirmation.  If a bug could be marked triaged, it could definitely be confirmed.
[14:29] <angusthefuzz> xteejx: anyway, not all bugs may have multiple users, for example, obscure hardware problems.
[15:13] <angusthefuzz> hey, does anyone know how to collapse the Tags column on launchpad (or maybe remove it altogether as it is way too long)
[15:26] <ScottK> angusthefuzz: You can't.
[15:27] <angusthefuzz> ScottK: yeah, i couldnt find I way, I just figured it annoyed someone else enough for a greasemonkey script
[16:45] <angusthefuzz> is it appropriate to invalidate needs-packaging bugs that have not been maintained in over a year and a half? or even never released an official package
[16:46] <angusthefuzz> *not the bug being maintained but the package the bug is about
[16:46] <ddd> does recording sound work in 8.10?
[16:46] <ScottK> angusthefuzz: Not really.  I'd only invalidate it if the license precluded it going in the archive or upstream was entirely gone.
[16:46] <ddd> two 8.10 boxes, in both arecord gives io error
[16:47] <angusthefuzz> okay ScottK, thanks
[16:49] <awsoonn> hi all
[16:50] <awsoonn> Problem time. nm-applet is crashing on start and I need to reconfigure networking on 8.10
[16:51] <ScottK> awsoonn: You probably want #ubuntu for support then.
[18:15] <yuriy> ToHellWithGA: most likely you just don't have the packages for those things installed. the systemsettings packge is mostly just the shell.
[19:15] <lfaraone> Hey, would it be a good/bad idea to attach a video to a bugreport that documents the bug? (4.5MiB OGG Theora)
[19:17] <angusthefuzz> lfaraone: that would be a fine idea, screencasts are important sometimes and very useful for recreation of the bug
[19:20] <lfaraone> angusthefuzz: kk, just trying to make sure I wouldn't use up too much disk space or anything :P
[19:22] <lfaraone> angusthefuzz: done. ( bug 147419 )
[19:31] <ToHellWithGA> yuriy: that's a shame, man
[19:32] <ToHellWithGA> in the past, and know that my kde under gnome experience is quite limited, installing "kcontrol" and "k3b" was sufficient to be able to adjust the sound/keyboard/mouse
[19:38] <yuriy> ToHellWithGA: installing kcontrol didn't help? what version of ubuntu?
[19:39] <ToHellWithGA> kcontrol is no longer available
[19:39] <ToHellWithGA> !info kcontrol
[19:39] <yuriy> no, not in intrepid
[19:39] <yuriy> no more kde3 stuff
[19:39] <ToHellWithGA> is there an actual replacement?
[19:39] <yuriy> systemsettings
[19:39] <ToHellWithGA> systemsettings configures exactly nothing useful
[19:40] <ToHellWithGA> *from a running kde applications under gnome standpoint
[19:40] <yuriy> because the actual control modules are in other package
[19:40] <yuriy> I don't know which one the mouse is in
[19:40] <yuriy> probably kdebase
[19:40] <ToHellWithGA> not kdebase
[19:40] <yuriy> i mean, kdebase-workspace
[19:40] <ToHellWithGA> i had no change between systemsettings w/ and w/out kdebase
[19:40] <ToHellWithGA> i'll look into that
[19:41] <ToHellWithGA> if that package isn't in the "recommended" set for kcontrol it might be a good idea to make it so
[19:41] <yuriy> you mean, for systemsettings?
[19:41] <ToHellWithGA> right
[19:42] <ToHellWithGA> yuriy: it seems a little excessive that the entire kde workspace must be installed to tweak mouse settings
[19:43] <ToHellWithGA> kde window manager and all that
[19:52] <ToHellWithGA> yuriy: installing kdebase-workspace had no effect
[19:55] <ScottK> It seems a bit odd to be wanting to use kcontrol to tweak mouse setting if you aren't actually running in KDE.
[19:55] <nuggan> hi
[19:56] <nuggan> i got quite a situation with the new intrepid ibex
[19:56] <ToHellWithGA> ScottK: i want to click adn drag
[19:57] <ToHellWithGA> s/adn/and/
[19:57] <nuggan> desktop-effects are not supported anymore
[19:58] <nuggan> i checked a number of threads but found no solutions for intel graphic cards
[19:58] <ToHellWithGA> clicking and dragging in a kde application running under gnome is impossible now
[19:58] <ToHellWithGA> nuggan: it works fine for me on two machines
[19:58] <ToHellWithGA> what's wrong?
[19:58] <ToHellWithGA> which chipset are you running?
[19:59] <ToHellWithGA> if this is not the proper channel, we can chat elsewhere
[20:00] <nuggan> it was ok with v. 8.04 - i could choose the drivers for the chipsets then (i used i810 or so - the controller is a 945 g or gm)
[20:00] <ToHellWithGA> you shouldn't need to do that now
[20:00] <ToHellWithGA> when you run "glxinfo" what kind of output do you get?
[20:00] <nuggan> that, i suspect is the problem
[20:00] <nuggan> ok one moment
[20:01] <ToHellWithGA> i had something go wacky on my 915 chipset and perfectly normal behavior on my 945 chipset
[20:02] <nuggan> many, many lines - what kind of info would you need?
[20:02] <ToHellWithGA> try running glxgears
[20:02] <ToHellWithGA> see what kind of framerate you get
[20:03] <nuggan> ok
[20:03] <ToHellWithGA> i'm thinking something was up where "DRI" was not enabled for some mysterious reason
[20:04] <ToHellWithGA> without "DRI" enabled on the x display compositing window managers don't work
[20:04] <ToHellWithGA> *on intel
[20:04] <nuggan> around 220.000 fps - well, how is that to enable - DRI?
[20:07] <ToHellWithGA> nuggan: for what it's worth, i get 500-600 fps on a 2GHz pentium 4 on a 915 chipset
[20:07] <ToHellWithGA> 200 seems a little low unless you're on seriously old and slow hardware
[20:07] <ToHellWithGA> i'd guess that means DRI isn't running
[20:08] <ToHellWithGA> nuggan: try "gksudo displayconfig-gtk &"
[20:08] <ToHellWithGA> that should let you choose/force a driver
[20:10] <xteejx> Evening guys, can someone clear something up for me with bug 294424, I seemed to have helped the guys upgrade problem but there's still a problem with the upgrade when a user has postgresql-plperl installed.
[20:10] <xteejx> Oh, sorry what do I do with it? (Triager with no bug control right)
[20:12] <xteejx> Do I just leave it as confirmed, or fix released, as its still a problem for Hardy users?
[20:13] <nuggan> ToHellWithGA - doing so i get "[1] 10274" - as an answer - no options - but i believe - something that worked with ubuntu 8.04 should also work with 8.10 - i dont even want some special effects or cubes, but only the normal visual effects, which should even work with older/weak chipsets
[20:14] <ToHellWithGA> nuggan: nothing comes up?
[20:14] <ToHellWithGA> when you try to run displayconfig-gtk
[20:16] <nuggan> very odd - but in the end it say 'command not found' - i know that command from hardy, when i had fthis package installed - but intrepid won't suppurt it - does it?
[20:17] <krychek> hi, on my friends computer update-manager does not work.. it says segmentation error whatever he tries to do, hes using hardy, any idea?
[20:18] <ToHellWithGA> nuggan: "sudo aptitude install displayconfig-gtk"
[20:18] <xteejx> krychek: You will need to get it filed as a bug and work on it from there, might just be a trivial problem.
[20:19] <ToHellWithGA> krychek: how about apt-get or aptitude?
[20:20] <xteejx> krycheck: You might be able to try "dpkg --configure -a" it could just be a broken package somewhere that command _should_ fix it
[20:20] <krychek> apt-get says segmentation error, if he start the graphical update manager it just quits after 1-2 secs without any messages
[20:20] <ToHellWithGA> krychek: that sounds pretty hosed, man
[20:20] <ToHellWithGA> will he lose data if he reinstalls
[20:21] <krychek> xteejx: we have tried that.. but it didnt fix it
[20:21] <xteejx> krycheck: Worst case scenario your mate might have removed an essential package or files by mistake
[20:21] <krychek> he says he made a normal upgrade (not dist upgrade) and it just quit during the upgrade
[20:22] <ToHellWithGA> krychek: have y'all tried "sudo aptitude install -f"?
[20:22] <xteejx> krychek: Ok, it might be a really stupid idea but its worth a try - probably wont work, but "sudo apt-get reinstall update-manager" ?
[20:23] <ToHellWithGA> nuggan: marco
[20:23] <xteejx> Can someone look at bug 294424 please, shall I leave it confirmed or fix released, I thought leave as Confirmed?
[20:24] <krychek> we will try those.. but i guess there will be just a segfault message..
[20:26] <Flare183> xteejx: I'll look at it
[20:27] <krychek> i have another problem.. bug 157215
[20:28] <krychek> has anyone tried if time synching works in Hardy?
[20:29] <Flare183> krychek: I haven't
[20:29] <Flare183> Let me take a look at it
[20:33] <Flare183> I see
[20:33] <Flare183> umm
[20:41] <krychek> also there is an issue with java applets, they just freeze firefox, see bug 288642 and bug 285729
[20:42] <krychek> i cant access my netbank since i upgraded to intrepid
[20:43] <xteejx> Flare183: Thanks :)
[20:43] <Flare183> xteejx: np
[20:47] <krychek> Flare183: "Do you have the daylight savings time feature turned on? This might be the cause."    the system time is totally wrong, not just 1-2 hours difference
[20:48] <Flare183> oh ok
[20:49] <afflux> krychek: as far as I know this time-server thing does not sync the time if there is more than X minutes difference
[20:50] <krychek> hmm thats not good..
[20:50] <krychek> this is an old comp, it forgets the time when its turned off
[20:51] <nick_> My hybrid pro DVB usb stick does not work under the new ubuntu. \dev\DVB\ does not appear when it's plugged in
[20:52] <afflux> krychek: maybe try to add an "ntpdate ntp.ubuntu.com" call to /etc/init.d/ntp right before the ntpd gets startet
[20:52] <afflux> *started
[20:56] <krychek> afflux: before this line: start-stop-daemon --start --quiet --oknodo --pidfile $PIDFILE --startas $DAEMON -- -p $PIDFILE -u $UGID $NTPD_OPTS ?
[20:56] <afflux> yes
[20:56] <krychek> is there inet connection at that point during the boot?
[20:58] <afflux> uh
[20:59] <afflux> krychek: you're right, NetworkManager get's started after ntpd. Maybe you should change the links from /etc/rc*.d/S23ntp to S39ntp.
[21:00] <afflux> krychek: note that this whole ntpdate approach is quite hackish
[21:00] <krychek> yeah :)
[21:01] <krychek> why doesnt the time get synced when the difference is too big? :/
[21:02] <krychek> i should just buy a new battery instead..
[21:09] <krychek> i closed a warty bug a few days ago.. bug 29
[21:13] <nuggan> Bug #279835 - any workaround?
[21:17] <nuggan> does this mean i should trash my laptop due to depricated on-board graphics-chipsets? (it's only 3 years old!!!)
[21:23]  * ScottK hands nuggan https://wiki.ubuntu.com/X/Troubleshooting/
[21:44] <Mads-hk> Goodevening people...
[21:45] <Mads-hk> Just wanted to hear what needs to be done before changing the status of a bug from Confirmed to Triaged?
[21:46] <angusthefuzz> Mads-hk: all the relevant log files necessary for debugging that package need to be attached
[21:47] <Mads-hk> Eeehm... okay
[21:47] <angusthefuzz> Mads-hk: please see the following link for proceedures of various packages: https://wiki.ubuntu.com/DebuggingProcedures
[21:48] <afflux> triaged means it has enough information for a developer to start working on it. This means: problem is localised and / or the bug has some kind of an approach to fix it
[21:49] <Mads-hk> ah okay... i have attached all the log files, described in the debugging wiki
[21:49] <angusthefuzz> Mads-hk: so now a decision needs to be made about having a developer look at the problem
[21:50] <angusthefuzz> Mads-hk: what is the bug number?
[21:50] <Mads-hk> okay... the number is #295679
[21:50] <afflux> "dpkg-divert: error checking `/usr/lib32/libGL.so.1': No such file or directory" -- what does this mean, by what is this caused?
[21:50] <angusthefuzz> bug #295679
[21:51] <Mads-hk> exactly :)
[21:52] <angusthefuzz> Mads-hk: part of the problem is that audio bugs are assigned to the linux package unless alsa is built from source
[21:53] <angusthefuzz> Mads-hk: additionally, confirmed audio bugs need to have the ubuntu-audio team subscribed to them
[21:53] <angusthefuzz> Mads-hk: I have made these changes for you
[21:53] <Mads-hk> oh, thank you! :)
[21:53] <angusthefuzz> (just giving you some info for the future ;-)
[21:54] <Mads-hk> and i appreciate it :)
[21:57] <angusthefuzz> Mads-hk: now all we need is someone from bug control to come by and change the importance
[21:58] <Mads-hk> okaay :)
[22:00] <jibel> afflux: this is likely bug 36625
[22:02] <afflux> jibel: indeed it is, thanks!
[23:36] <xteejx> Hi guys can someone have a look at bug 221402 please? Do I need to provide any logs/info?


[00:31] <komputes> Sarvatt: awesome, thanks
[00:32] <komputes> Sarvatt: ATI will show 'drm'?
[00:32] <Sarvatt> ati/intel have drmfb's nouveau only has KMS
[00:32] <komputes> ah yes - [drm] radeon defaulting to kernel modesetting.
[00:32] <Sarvatt> its looking for nouveaufb or drmfb
[00:33] <komputes> Sarvatt: sorry, confused. again from the beginning.
[00:34] <komputes> /proc/fb contains a list of frame buffer devices, with the frame buffer device number and the driver that controls it
[00:34] <Sarvatt> yeah if nouveaufb or any of the drmfb's are in there it's using KMS
[00:35] <komputes> Sarvatt: and just to be clear those drmfb's are inteldrmfb, nouveaufb, radeonfb
[00:35] <Sarvatt> nouveaufb radeondrmfb or inteldrmfb
[00:35] <komputes> cool, thanks Sarvatt
[00:40] <Sarvatt> no problem, also I forgot but vmwgfx is svgadrmfb as well
[00:47] <komputes> Sarvatt: which are?
[01:45] <ripps> Can someone please mentor me with l-b-m? I want to add an updated wacom module fix problems with new wacom bamboo tablets. I've already discussed this and submitted a proposal on the mailing list, but nobody has responded. See bugs #568064 and #606278
[01:45] <ubot2> Launchpad bug 568064 in linux (Ubuntu) "Wacom new bamboo models are not recognized in Lucid (affects: 19) (heat: 101)" [Undecided,Confirmed] https://launchpad.net/bugs/568064
[01:45] <ubot2> Launchpad bug 606278 in linux-backports-modules-2.6.35 (Ubuntu) "Add linux-backports-modules-input (affects: 6) (dups: 1) (heat: 42)" [Undecided,New] https://launchpad.net/bugs/606278
[01:46] <ripps> Since I can see any sign of anybody working on this, I wanted to know if somebody can help me write a patch instead. I've taken a look at the l-b-m source, but it's so complicated I can't really make much sense of it.
[01:46] <ripps> *don't see any sign
[01:49] <ion> It might be nice to have CONFIG_COMPACTION on.
[01:51] <ripps> I'm not some noob with packaging, I was just hoping somebody give me some hints or guidance on how to start adding a new component to l-b-m
[02:41] <Sarvatt> ripps: does l-b-m make sense for something thats not a backport? what's wrong with your dkms package?
[02:42] <ripps> Sarvatt: nobody would accept it. MOTU's said to try and get it into Debian, and Debian said that it was just working around a problem with the kernel. Problem is, the linuxwacom project isn't updating their wacom kernel source because apparently their refactoring it or something.
[02:44] <ripps> After discussing it here, I was advised to propose an addition to linux-backport-modules. But apparently, nobody wants to help me get in there, either.
[07:21] <tjaalton> any known regressions in the current lucid kernel? I
[07:21] <tjaalton> hrm
[07:22] <tjaalton> I'm unable to do a full install (~2500 packages) anymore, since dpkg sees some packages are corrupt (same size, different md5sum as on the archive)
[07:23] <tjaalton> or when unpacking some config stubs in /tmp are missing etc
[07:23] <tjaalton> maybe I should try with ext3 to rule it out
[07:30] <tjaalton> ah, actually.. the installer image is the release one :)
[07:30] <tjaalton> the one that worked was from March
[07:34] <tjaalton> though the corruptness happens on an installed system as well, and that has the latest kernel
[08:47] <apw> /usr/share/doc/debian-policy/upgrading-checklist.txt.gz
[08:59] <era> hi ogasawara, is anything being done to implement this? https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/590090/comments/7
[08:59] <ubot2> Ubuntu bug 590090 in ndiswrapper (Ubuntu) (and 1 other project) "package ndiswrapper-dkms 1.56-1 failed to install/upgrade: ndiswrapper kernel module failed to build (affects: 40) (dups: 3) (heat: 206)" [Medium,Confirmed]
[10:32] <apw> if ! git remote | grep FOO >/dev/null; then echo NO; fi
[12:33] <tumbleweed> can anyone suggest things to try and get useful debug information? Got a user who's USB controller seems to hang ~once a day (leaving him without working keyboard and mouse). Nothing interesting in kernel/X logs, and lsusb hangs on open("/dev/bus/usb/002/005")
[12:34] <tumbleweed> nm that, after a while, starteg tetting task blocked messages in kernel logs
[13:29] <Ejdesgaard_> hi, is there any chance that https://bugzilla.kernel.org/show_bug.cgi?id=16315 will be backported to 10.04 LTS?
[13:29] <ubot2> bugzilla.kernel.org bug 16315 in i386 "icebp (opcode 0xf1) no longer causing a SIGTRAP, breaks Wine" [Normal,New]
[13:30] <smb> Ejdesgaard_, If the patch goes upstream as a stable patch it will come back as soon as upstream stable picks it up
[15:07] <JFo> lag, the picture is up on my Facebook
[15:09] <JFo> sent to you in e-mail
[15:30] <lag> JFo: That's awesome!
[15:30] <JFo> :)
[15:40] <lag> JFo: http://people.canonical.com/~ljones/lastsupper/
[15:47] <JFo> nice!
[15:48] <JFo> not a bad approximation
[15:55] <lag> It's there or there abouts
[15:55] <lag> Someone is facing completely the wrong way and I'm a few degrees off
[15:55] <lag> Overall I think we did okay :)
[15:56] <vanhoof> lol!
[15:57] <vanhoof> you guys werent kidding around :D
[15:57] <Ejdesgaard_> smb, it was included in .35-rc4
[15:58] <bjf> ##
[15:58] <bjf> ## Kernel team meeting in two hours
[15:58] <bjf> ##
[16:14] <ogasawara> era: it seems that bug was recently resolved in the last few hours by the package maintainer
[16:18] <ogasawara> era: I'm not opposed to going with their plan B in the future and completely dropping ndiswrapper from the kernel but that's a discussion that needs to probably take place on the kernel-team mailing list
[16:31] <Riddell> jcrigby: has the binary package names in the linux-linaro upload been OKed by the kernel team?
[16:32] <tgardner> Riddell, its been uploaded, but is awaiting acceptance by an archive admin
[16:32] <jcrigby> Riddell: I don't know.  What constitutes approval.
[16:32] <Riddell> tgardner: why do you think I'm asking :)
[16:33] <Riddell> jcrigby: tgardner's blessing? :)
[16:33] <tgardner> Riddell, random curiosity?
[16:33] <tgardner> Riddell, slangasek said he had some concerns, but he's at debconf
[16:34] <Riddell> why do some of the binary packages have "linaro" in the name and some go for the -1000 suffix?
[16:34] <tgardner> Riddell, um, not supposed to. I guess I'd better look closer. I only looked at the control file
[16:35] <jcrigby> I tried to follow the abstracted debian model.  May have messed up.
[16:35] <Riddell> well it looks deliberate I presume there's a reason why that's the best way to do it
[16:35] <jcrigby> tgardner:  I removed a bunch of entries from the control file yesterday.  It now looks like the ti-omap4 control file.
[16:35] <Riddell> e.g. linux-headers-2.6.35-1000
[16:35] <tgardner> Riddell, whats the URL for looking at the generated packagesd?
[16:36] <Riddell> tgardner: there are no generated packages, I'm reviewing the source
[16:38] <jcrigby> I think you will see the same convention in the ubuntu kernel
[16:38] <jcrigby> without the 1000
[16:38] <tgardner> Riddell, according to debian/control I think the package names are correct. it follows the same model as other kernel topic branches
[16:38] <Riddell> yeah that's the ABI number
[16:39] <Riddell> but it seems curious to namespace some packages with "linaro" and some with <mega big ABI number>
[16:39] <smb> Ejdesgaard_, Is that definitely needed for 2.6.32 (10.04 LTS) as the patch seems to have been sent for 2.6.33.y specifically
[16:40] <tgardner> Riddell, oh, you mean the 'linaro' part? I guess he's using it to distinguish these kernel binaries from the omap4 packages that are already in the archive.
[16:41] <Riddell> tgardner: yeah that makes sense.  bumping the ABI to 1000 is what seems strange to me
[16:42] <tgardner> jcrigby, so, do you want to respin with new binary package names?
[16:42] <tgardner> Riddell, we use the ABI number to distinguish between kernel topic branches
[16:42] <tgardner> otherwise we'd have binary package name collision
[16:42] <jcrigby> tgardner:would be glad to if someone tells me what to change them to
[16:42] <Riddell> I'd have thought e.g. linux-linaro-headers-2.6.35-1 would make more sense
[16:43] <tgardner> Riddell, its a restriction of the installer, which insists on the linux-header* pattern
[16:43] <jcrigby> ahh
[16:43] <tgardner> similarly for linux-image*
[16:43] <Riddell> tgardner: ah, I knew there'd be a perfectly rational explanation
[16:43] <tgardner> well, rational is a stretch :)
[16:45] <jcrigby> on a different matter, I changed the control yesterday and removed some stuff and made Architecture: armel for everything
[16:45] <jcrigby> so the build system only tries to build on armel
[16:46] <Riddell> jcrigby: in that case should I reject the current upload and save the non-arm buildds the hassle of building something they don't want?
[16:46] <tgardner> jcrigby, I'm not sure you can do that. Some of the packages have to be constructed on the default arch (i386), e.g., the headers _all.deb
[16:47] <jcrigby> tgardner:I made it look like the ti-omap4 control
[16:47] <jcrigby> is that known good?
[16:47] <tgardner> Riddell, why don't you go ahead and reject this upload. I
[16:47] <tgardner> I'll work with jcrigby to fix the control file issues
[16:49] <jcrigby> tgardner:thanks
[16:49] <Riddell> ok rejected, ping me when you reupload if you want a quick review
[16:50] <tgardner> Riddell, later today I think. Thanks for your help.
[16:51] <jcrigby> tgardner:what is best for you.  Do you want to just send me a patch?
[16:52] <tgardner> jcrigby, send a pull request with your current bits
[16:52] <jcrigby> with the ti-omap4 changes?
[16:52] <jcrigby> style changes that is
[16:52] <tgardner> jcrigby, yep
[16:53] <jcrigby> ok, I notice one thing that your comment above sheds some light on:
[16:53] <jcrigby> Package: linux-headers-2.6.35-1000
[16:53] <jcrigby> Architecture: armel
[16:53] <jcrigby> Section: devel
[16:53] <jcrigby> Priority: optional
[16:53] <jcrigby> Depends: ${misc:Depends}, coreutils | fileutils (>= 4.0)
[16:53] <jcrigby> #Provides: linux-linaro-headers, linux-linaro-headers-2.6
[16:53] <jcrigby> Description: Header files related to Linux kernel version 2.6.35
[16:53] <jcrigby>  This package provides kernel header files for version 2.6.35, for sites
[16:53] <jcrigby>  that want the latest kernel headers. Please read
[16:53] <jcrigby>  /usr/share/doc/linux-linaro-headers-2.6.35-1000/debian.README.gz for details
[16:54] <jcrigby> explains the commented out Provides:
[16:55] <tgardner> jcrigby, correct
[17:07] <apw> bjf, is there a meeting today?
[17:07] <bjf> apw, yes
[17:07] <apw> ahh i see your 2 hour warning now
[17:14] <smb> sconklin, bjf Seems there is no need to start a new release on Lucid, that was already done
[17:15] <sconklin> smb: yes, I'm just applying the patches. I'll start with the things we wanted on the short list
[17:15] <smb> sconklin, ok
[17:17] <smb> sconklin, We should sync on the writeback patches. I got the feeling there is a patchset you got and one I have done
[17:18] <sconklin> smb let me check what I have and see if they're in my public repo
[17:18] <smb> bug 643617
[17:18] <ubot2> smb: Error: Bug #643617 not found.
[17:18] <smb> hm
[17:18] <smb> bug 543617
[17:18] <ubot2> Launchpad bug 543617 in linux (Fedora) (and 3 other projects) "Unmount of an fs with dirty cache buffers causes pathological slowdown (affects: 11) (dups: 2) (heat: 101)" [Unknown,Unknown] https://launchpad.net/bugs/543617
[17:19] <smb> same as bug 585092
[17:19] <ubot2> Launchpad bug 585092 in linux (Ubuntu) "giant IO delays (affects: 1) (heat: 22)" [Medium,In progress] https://launchpad.net/bugs/585092
[17:20] <sconklin> smb: yes, there's already a branch "bug bug543617" in my public repo that I used to build the test kernel for that bug
[17:21] <sconklin> oops, branch name is simply bug543617
[17:21] <smb> sconklin, Let me check what is there. Cause I have been working on that and probably got a different set
[17:25] <smb> sconklin, My set is there (http://kernel.ubuntu.com/git?p=smb/linux-2.6.32.y.git;a=shortlog;h=refs/heads/writeback) and looks like being a superset of yours. I am currently trying to get Jens Axboe look at those to get them backported to stable upstream. There is a set for 2.6.34.y as well
[17:25] <smb> sconklin, Have you sent your patches for review already. I cannot remember having seen that
[17:26] <sconklin> as I recall, they were sent for review weeks ago, and I just picked them up. Let me check
[17:27] <sconklin> smb: [1/2] writeback: fix WB_SYNC_NONE writeback from umount
[17:27] <smb> I was holding back because I at least wanted to have some feedback on them before. These series has been taking a lot of time to mature upstream
[17:28] <sconklin> [2/2] writeback: ensure that WB_SYNC_NONE writeback with sb pinned is sync
[17:28] <smb> Ok, maybe my bad not deleting those
[17:28] <sconklin> smb: OK, I just grabbed them and built a test while you were out sick because rtg asked about them
[17:28] <smb> sconklin, Please don't pick them for applying now
[17:29] <sconklin> smb: they were still active in patchwork also
[17:29] <sconklin> ok, I won't pick them
[17:29] <smb> Right, I should have marked them as superseeded
[17:30] <smb> Thanks. Unfortunately there was a time in between when I knew the ones we had were not good but upstream was not fixed yet. And not to forget I did not set them as rejected
[17:31] <bjf> ##
[17:31] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[17:31] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting
[17:31] <bjf> ##
[17:32] <smb> sconklin, The set now seems to be ok, but as you can see in that tree its a huge set.
[17:33] <smb> sconklin, The only thing we need to remember is to revert the workaround when we apply the writeback set
[17:33] <sconklin> smb: I'll apply the graphics fixes for the two issues we have patches for, then the writeback patches, then the stable update, OK?
[17:35] <smb> sconklin, Leave out the writeback patches completely. I want to get feedback on the backport first and then do another round of sending those to the kt-mailing list
[17:35] <sconklin> smb: ok
[17:36] <vanhoof> sconklin: i assume you need that sru sooner than later for the x201 display bug?
[17:36] <sconklin> vanhoof: yes, I'd hate for it to end up being the gating factor
[17:36] <vanhoof> manjo: ^^ :D
[17:37] <manjo> yes building kernel with patch now
[17:37] <manjo> I will send it to SRU as soon as I am done
[17:37] <vanhoof> manjo: ok, i can re-test if you'd like
[17:38] <manjo> yep that will be great!
[17:38] <sconklin> vanhoof, manjo: also, people have been ignoring the SRU requests or not completing them properly. We've been fixing them up without complaining, but I'm going to start bouncing them until they are correct.
[17:39] <smb> sconklin, I removed the writeback parts from patchwork for now so there won't be confusion on that part
[17:40] <sconklin> smb: ok, but I think I acked them on the mailing list, so you'll want to follow up on that
[17:41] <smb> sconklin, There is another one to disable CONFIG_LGUEST for hardy lpia which went in as part of the security update to fix the build failure
[17:41] <smb> sconklin, I probably should post a message there, too
[18:29] <manjo> Is there an issue with tangerine ?
[18:29] <manjo> manjo@tangerine:~$ dchroot -c lucid-amd64
[18:29] <manjo> W: Group ‘sbuild’ not found
[18:29] <manjo> E: Access not authorised
[18:29] <manjo> I: You do not have permission to access the schroot service.
[18:29] <manjo> I: This failure will be reported.
[18:29] <manjo> manjo@tangerine:~$
[18:29] <manjo> I was able to dchroot just couple of hrs ago
[18:29] <JFo> <-starving... headed to lunch
[18:31] <manjo> tgardner, ^^ any idea ?
[18:31] <tgardner> manjo, I guess you're not special.
[18:31] <manjo> ?
[18:32] <bjf> tgardner, i think it's because he *is* "special"
[18:32] <tgardner> manjo, just kidding. lemme check
[18:32] <manjo> bjf, thanks
[18:33] <tgardner> apw, smbgot some oops on tangerine.
[18:34]  * manjo brb
[18:34] <tgardner> smb, ^^ need to reboot.
[18:34] <smb> Hm, just for compiling six kernels in paralell
[18:34] <smb> ok
[18:34] <apw> tgardner, stuck in writeback ... smb could that be your writeback issue you had patches for ?
[18:34] <tgardner> shall we try the 2.6.35 kernel?
[18:34] <bjf> ogasawara, you want me to leave "delta-review" on the agenda?
[18:34] <smb> tgardner, apw Let me have a quick look
[18:35] <ogasawara> bjf: I'd say take it off
[18:36] <ogasawara> bjf: the last big item is to review if any of our ubuntu drivers need updating (which I suspect they won't)
[18:36] <bjf> ogasawara, it's gone
[18:36] <sconklin> smb: do we put the buglink for the stable update bug in every patch that's part of a stable pile?
[18:37] <smb> sconklin, yes. maint-modify-patch
[18:37] <sconklin> ok, doing that now
[18:37] <smb> tgardner, apw Seems the process that was stuck first was returning later. So it might well be the slow writeback problem
[18:38] <bjf> apw, you still have two agenda items do you want to keep them?
[18:38] <tgardner> smb, lets try the LTS backport kernel for awhile.
[18:38] <simar> I want to triage bugs for kernel at first. So I'm going to read documents of Ubuntu Kernel Bug triaging ..
[18:39] <apw> bjf, the misc one is likely redundant
[18:39] <smb> tgardner, as long as we can switch back to the lts kernel later, ok. Cause that machine is good for running stress io tests
[18:40] <smb> tgardner, I am off it again, so you can reboot if you like
[18:43]  * smb is gone
[18:45] <manjo> tgardner, please let me know when tangerine is back
[18:50] <apw> simar, sounds great for us ...
[18:51] <manjo> simar, talk to JFo he should be able to help you as well
[18:52] <manjo> simar, he leads the bug triaging effort
[18:56] <manjo> tgardner, looks like tangerine is back... can I use it ?
[18:57] <manjo> ah same issue cannot dchroot ...
[18:57]  * manjo getting lunch will be back soon
[18:58] <tgardner> manjo, should be OK now. you'll need to logout first.
[20:33]  * ogasawara lunch
[20:33]  * jjohansen lunch too
[22:06] <sconklin> manjo, vanhoof: The graphics patches you wanted are now in the lucid repo
[22:06]  * manjo sconklin beer++
[22:15] <bjf> ogasawara, sconklin just pushed some patches to the lucid repo is there anything that will automatically build that (some kind of pre-proposed / stable crack of the day)?
[22:15] <ogasawara> bjf: hrm, I can't remember if smb's pre-proposed in the kernel-ppa builds automatically
[22:16] <tgardner> ogasawara, bjfAFAIK it does
[22:16] <ogasawara> bjf: it certainly should be easy enough to make it do so automatically as apw does the same for the latest maverick tip
[22:16] <bjf> ogasawara, that's what i thought, was just wondering if we already did it
[22:17] <bjf> tgardner, i guess we'll know in a bit then
[22:19] <manjo> latest maverick iso i386 from cdimage current does not seem to boot ...
[22:19] <manjo> I recall apw posted something in this regard wrt to usb keys .. anyone recall ?
[22:21] <ogasawara> manjo: bug 608382 ?
[22:21] <vanhoof> sconklin: awesome!
[22:21] <ubot2> Launchpad bug 608382 in usb-creator (Ubuntu) (and 1 other project) "USB images of Maverick CDs fail to boot with -- Error: Unkown keyword in configuration file (affects: 13) (dups: 1) (heat: 70)" [High,New] https://launchpad.net/bugs/608382
[22:21] <manjo> looking
[22:23] <manjo> ogasawara, thanks a ton
[22:24] <tgardner> bjf, kernel-ppa@zinc:~$ crontab -l
[22:24] <tgardner> # m h  dom mon dow   command
[22:24] <tgardner> 0 *    *   *   *   $HOME/buildscripts/mainline-build/kernel-version-map >$HOME/public_html/info/kernel-version-map.html.new && mv $HOME/public_html/info/kernel-version-map.html.new $HOME/public_html/info/kernel-version-map.html
[22:24] <tgardner> 0 09    *   *   *   USER=kernel-ppa $HOME/kteam-tools/mainline-build/mainline-trigger >>$HOME/logs/mainline-trigger 2>&1
[22:24] <tgardner> 5  *    *   *   *   USER=kernel-ppa $HOME/kteam-tools/mainline-build/cod-execute >>$HOME/logs/cod-execute 2>&1
[22:24] <tgardner> @hourly /srv/kernel.ubuntu.com/www/scripts/gitfind > /dev/null 2>&1
[22:25] <manjo> ogasawara, if you are channel operator can you add "10.10 USB boot issues see https://launchpad.net/bugs/608382 for workaround" ?
[22:25] <ubot2> Ubuntu bug 608382 in usb-creator (Ubuntu) (and 1 other project) "USB images of Maverick CDs fail to boot with -- Error: Unkown keyword in configuration file (affects: 13) (dups: 1) (heat: 70)" [High,New]
[23:23] <apw> ogasawara, bjf, sconklin-gone, the pre-proposed engine builds all of the releases, assuming they have non-ignored commits following a release
[23:24] <bjf> apw, yes, i was looking at the scripts and sort of decided that
[23:24] <bjf> apw, if i understand it, they should kick off 0900 UTC
[23:25] <apw> bjf yes indeedy
[23:25] <apw> bjf with the new queuing ability we could reschedule the pre-proposed to a better time independantly if needed
[23:26] <apw> night
[23:26] <bjf> g'night


[00:45] <balloons> Right, we still have a bunch of trusty no worries
[00:45] <balloons> Ty for review
[01:03] <axw> hml: for things to do after the sprint: Australia Zoo is pretty close to the sprint location. I didn't think it was that great of a zoo, but if you want to see kangaroos and koalas, there's that
[01:04] <axw> there's a bus that goes there, or you could drive pretty easily if you feel like driving on the wrong side of the road
[01:04] <hml> axw: I saw a koalas santuary near Brisbane?
[01:04] <axw> hml: oh yeah, I think it's near wallyworld's house actually :)
[01:04] <hml> axw: i’ve driven in Ireland, hopefully the roads are wider.  :-)
[01:04] <axw> probably
[01:05] <axw> haven't been to ireland
[01:05] <wallyworld> hml: the koala place is 3 minutes away from me
[01:05] <axw> but given the rest of europe...
[01:05] <wallyworld> there's another place closer to the venue; the steve irwin place
[01:05] <hml> axw: the roads are scarey small in the country side - and easy to find ones with grass down the middle
[01:05] <wallyworld> crocodile hunter and all that
[01:05] <axw> (that's Australia Zoo)
[01:06] <hml> wallyworld: :-)
[01:06] <wallyworld> we can organise an excursion there if people are interested; a group booking
[01:07] <axw> wallyworld: if we can have the team dinner at https://www.tripadvisor.com.au/Restaurant_Review-g261638-d1745794-Reviews-Spice_Bar-Mooloolaba_Sunshine_Coast_Queensland.html I wouldn't be unhappy ;)  not sure if it's within budget
[01:09] <wallyworld> axw: we'll sort something out :-) I was also thinking of Spirit House as a possibility
[01:09] <axw> wallyworld: in Yandina?
[01:09] <wallyworld> yeah
[01:09] <axw> wallyworld: looks nice
[01:10] <axw> might be nice to get off the strip
[01:10] <wallyworld> it is - have been there. very good food. but your place looks nice also. degausation too
[01:11] <wallyworld> we can take inpt from the group to decide :-)
[01:11] <wallyworld> easy enough to organise a minibus if needed
[01:11] <wallyworld> i'll organise stuff next week once things are locked in
[01:12] <axw> yup
[01:22] <wallyworld> babbageclunk: https://github.com/juju/juju/pull/7336 is updated. there are 2 commits - the 2nd one is the changes due to the rebase. whenever you get a chance is fine
[01:28]  * thumper takes dog for a walk
[01:44] <babbageclunk> wallyworld: ok, will look once I get to the bottom of this subordinate thing - I feel like I've nearly got it.
[01:44] <wallyworld> \o/
[01:44] <wallyworld> no rush
[02:18] <wgrant> babbageclunk: Thanks for looking at the subordinate bug.
[02:18] <babbageclunk> wgrant: :) I haven't fixed it yet!
[02:21] <wgrant> babbageclunk: I have a suspicion that this it might be related to a couple of the remove-application issues as well, since they mostly involve subordinates.
[02:22] <wgrant> https://bugs.launchpad.net/juju/+bug/1655486 is one
[02:22] <mup> Bug #1655486: removal of principal ceph-osd charm stuck in 'executing' state <sts> <OpenStack ceph-osd charm:Incomplete> <juju:Triaged> <ceph-osd (Juju Charms Collection):Invalid> <https://launchpad.net/bugs/1655486>
[02:25] <babbageclunk> wgrant: ok, I'll keep that in mind, thanks
[02:26] <wallyworld> babbageclunk: you may get to fix 2 or 3 bugs in one go - legend
[02:35]  * babbageclunk isn't counting chickens
[03:00] <wallyworld> axw: babbageclunk: just off for a bit to take son to get stitches out, bbiab
[03:00] <axw> ok, later
[03:31] <axw> wallyworld: when you're back, please take a look at https://github.com/juju/juju/pull/7355
[04:05] <babbageclunk> axw: free for a moment? I think I understand the subordinate problem but not sure how to fix it.
[04:15] <babbageclunk> wallyworld: back from the hospital yet?
[04:19]  * babbageclunk is lonely
[04:34] <menn0> jam: I can't make the standup, or the start at least. it's chaos here and I need to do a kid pickup.
[04:34] <menn0> babbageclunk: quick call?
[04:35] <jam> k
[04:39] <jam> menn0: I take it the CAAS call has already ended?
[04:40] <menn0> jam: yes
[05:23] <axw> babbageclunk: sorry went out, do you still need me?
[05:24] <babbageclunk> axw: No, I talked about it with thumper, I think it makes sense.
[05:24] <axw> babbageclunk: ok, cool
[05:25] <babbageclunk> axw: thanks though! I added it to the bug here: https://bugs.launchpad.net/juju/+bug/1686696
[05:25] <mup> Bug #1686696: Subordinate units won't die until all principal relations are gone <juju:Triaged by 2-xtian> <https://launchpad.net/bugs/1686696>
[05:27] <axw> babbageclunk: sounds logical to me. maybe call it WatchUnitRelations though
[05:28] <babbageclunk> axw: yeah, I am - forgot to update the comment.
[05:28] <babbageclunk> axw: Cheers!
[07:27] <wallyworld> axw: sorry, totally missed the ping, looking now
[07:45] <axw> wallyworld: thanks
[07:45] <wallyworld> np
[08:48] <rogpeppe> axw, wallyworld: any chance of a review of some of this API client refactoring? https://github.com/juju/juju/pull/7338
[08:51] <axw> rogpeppe: will look shortly
[08:51] <rogpeppe> axw: tyvm
[09:30] <axw> rogpeppe: just one trivial. good stuff, thank you
[09:30] <rogpeppe> axw: thanks!
[09:46] <wpk> wallyworld: re: landscape tests failing, I have a fix, I'm writing a test and will have a PR in a few minutes
[10:29] <wpk> wallyworld: jam: https://github.com/juju/juju/pull/7357 short one, simple one
[10:30] <jam> wpk: saw it before you advertised, lgtm
[10:30] <jam> wpk: did you respond to my review of SSH? 7348
[10:31] <wpk> jam: the first one? yes
[10:33] <wpk> I see that all your comments are outdated
[10:38] <jam> ah, I just had to reload the page
[10:39] <wpk> web 2.0...
[10:56] <wpk> When is RC1 scheduled to be released?
[11:14] <wallyworld> wpk: sorry, i was at soccer, bck now. thanks for the fix!
[11:41] <wpk> wallyworld: always reminds me of https://www.youtube.com/watch?v=2sD_8prYOxo ;)
[11:51] <wallyworld> wpk: yeah, i like john cleese
[11:58] <wpk> and it's merged.
[12:06] <jam> wpk: I responded to your update
[12:10] <wpk> k, thanks
[13:55] <gsamfira> Hi! Any volunteers for a 2 line PR? :P
[15:07] <mup> Bug #1662272 opened: Agents stop running hooks and are hung <canonical-is> <juju-core:New> <https://launchpad.net/bugs/1662272>
[15:19] <mup> Bug #1662272 changed: Agents stop running hooks and are hung <canonical-is> <juju-core:New> <https://launchpad.net/bugs/1662272>
[15:22] <mup> Bug #1662272 opened: Agents stop running hooks and are hung <canonical-is> <juju-core:New> <https://launchpad.net/bugs/1662272>
[21:17] <thumper> morning
[21:32] <wpk> night
[22:11] <balloons> thumper, wallyworld, I believe https://github.com/juju/juju/commit/fbe29cb10097aa301fba795f449cb617c88420c8 broke backup/restore. Just confirming now, it'll be a bit
[22:14] <thumper> balloons: ta
[22:17] <babbageclunk> wallyworld, thumper: anyone remember the trick for creating subordinate units in tests?
[22:17] <thumper> babbageclunk: can the factory do it?
[22:18] <babbageclunk> thumper: not directly
[22:18] <wallyworld> otp, sorry, give me a sec
[22:18] <wpk> can someone take a look at https://github.com/juju/juju/pull/7353 ? I made some changes after jam approved it and I'd like to merge it before RC1 if possible
[22:19] <wpk> (and if you think it's ok then $$merge$$ it)
[22:20] <babbageclunk> thumper: ooh, I remember where I had to do it now - ensuring principal units get migrated before subordinates.
[22:24] <babbageclunk> wpk: Looks good to me. Merged!
[22:38] <thumper> wallyworld: https://github.com/juju/juju/pull/7363/files
[22:42] <wallyworld> looking
[22:45] <wallyworld> thumper: gret, ty
[22:45] <wallyworld> great
[22:59] <thumper> well poo
[22:59] <thumper> my theory around logs not being queries across models is wrong
[22:59] <babbageclunk> thumper: you and Ada would definitely get on.
[23:03] <thumper> wallyworld: here is another datapoint
[23:03] <thumper> in http://juju-ci.vapour.ws/job/github-check-merge-juju/1087/artifact/artifacts/grant.log
[23:03] <thumper> 22:53:35 ERROR juju.cmd.juju.commands bootstrap.go:492 unable to contact api server after 1 attempts: unable to connect to API: x509: certificate signed by unknown authority
[23:03] <wallyworld> hmmm, joy
[23:22] <thumper> wallyworld: also I can't make the standup today, taking daughter to the Drs
[23:22] <wallyworld> ok
[23:25] <axw> wallyworld: how'd the demo go?
[23:26] <wallyworld> axw: aborted - screen sharing failed
[23:26] <wallyworld> going to retry next week
[23:26] <axw> wallyworld: :(  I thought that was a solved problem
[23:27] <wallyworld> it  worked when i shared the console with conjure-up but sharing a browser window failed. wtf
[23:30] <axw> thumper: that cert error is nothing to do with ssh though. that's about the TLS cert used to connect to the API
[23:30] <axw> I can believe that my changes might have broken backup/restore, but I don't think that particular error is related
[23:31] <thumper> axw: I was raising the point with wallyworld because we talked earlier about cert changes that rogpeppe had been doing recently
[23:31] <axw> thumper: ah ok
[23:32] <thumper> but perhaps the strict host checking is breaking backup / restore
[23:35] <axw> wallyworld: no online travel tool yet?
[23:35] <axw> just got the email, but says to use provider
[23:35] <axw> I can email sarah, just wondering ify ou know
[23:38] <axw> thumper: yes, I think I did break restore. in state/backup/restore.go, the ssh command is running without having any host keys set
[23:39] <axw> thumper: so we should poke them in, they'll be in the state DB


[02:59] <elky> oh hey, so ubottu just disappeared
[02:59] <elky> AlanBell, ping
[02:59] <elky> jussi, ping
[06:47] <gnomefreak> ikonia: is there an issue with "borked"? in -ot
[06:48] <io> nah
[06:48] <io> ikonia is handling it
[06:48] <gnomefreak> k thanks
[06:49] <io> plus Flannel is also awake
[06:49] <Flannel> What?
[06:49] <io> gnomefreak: no more coffee after 7PM for you
[06:50] <io> Flannel: you are awake, or maybe sleep typing?
[06:50] <Flannel> io: Flannel's not here right now, but if you'd like to leave a message, please do so at the beep.
[06:50] <gnomefreak> i had coffee at ~3am yesterday today no coffee at all