[17:18] -queuebot:#ubuntu-release- New binary: bmusb [ppc64el] (zesty-proposed/universe) [0.5.3-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: bmusb [s390x] (zesty-proposed/universe) [0.5.3-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: khard [ppc64el] (zesty-proposed/universe) [0.11.3-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: khard [s390x] (zesty-proposed/universe) [0.11.3-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: libzorpll [ppc64el] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: ndpi [ppc64el] (zesty-proposed/universe) [1.8-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: ruby-defaults [amd64] (zesty-proposed/main) [1:2.3.3] (kubuntu, ubuntu-desktop)
[17:21] -queuebot:#ubuntu-release- New binary: bmusb [i386] (zesty-proposed/universe) [0.5.3-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: ndpi [s390x] (zesty-proposed/universe) [1.8-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: libzorpll [s390x] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: bmusb [amd64] (zesty-proposed/universe) [0.5.3-1] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: bmusb [armhf] (zesty-proposed/universe) [0.5.3-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: bmusb [arm64] (zesty-proposed/universe) [0.5.3-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: cylc [ppc64el] (zesty-proposed/universe) [6.11.2-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: bmusb [powerpc] (zesty-proposed/universe) [0.5.3-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: ndpi [amd64] (zesty-proposed/universe) [1.8-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: libzorpll [armhf] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: cylc [s390x] (zesty-proposed/universe) [6.11.2-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: ndpi [i386] (zesty-proposed/universe) [1.8-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: libzorpll [arm64] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: ndpi [arm64] (zesty-proposed/universe) [1.8-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: libzorpll [amd64] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: libzorpll [powerpc] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: libzorpll [i386] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: ndpi [armhf] (zesty-proposed/universe) [1.8-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: khard [armhf] (zesty-proposed/universe) [0.11.3-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: ndpi [powerpc] (zesty-proposed/universe) [1.8-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: khard [amd64] (zesty-proposed/universe) [0.11.3-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: node-after [amd64] (zesty-proposed/universe) [0.8.2-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: khard [arm64] (zesty-proposed/universe) [0.11.3-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: node-shelljs [amd64] (zesty-proposed/universe) [0.7.5-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: vtgamma [amd64] (zesty-proposed/universe) [0.2-1] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: node-hook-std [amd64] (zesty-proposed/universe) [0.2.0-1] (no packageset)
[17:30] -queuebot:#ubuntu-release- New binary: cylc [amd64] (zesty-proposed/universe) [6.11.2-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: khard [powerpc] (zesty-proposed/universe) [0.11.3-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: cylc [arm64] (zesty-proposed/universe) [6.11.2-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: svxlink [amd64] (zesty-proposed/universe) [15.11-2] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: khard [i386] (zesty-proposed/universe) [0.11.3-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: cylc [armhf] (zesty-proposed/universe) [6.11.2-1] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: cylc [powerpc] (zesty-proposed/universe) [6.11.2-1] (no packageset)
[17:49] <bdmurray> elopio: He pinged, on Friday and we don't release SRUs to -updates b/c of the weekend.  We can do it on Monday.
[19:12] -queuebot:#ubuntu-release- New binary: kicad [amd64] (zesty-proposed/universe) [4.0.4+dfsg2-1] (no packageset)
[21:46] -queuebot:#ubuntu-release- New: accepted bmusb [amd64] (zesty-proposed) [0.5.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted bmusb [armhf] (zesty-proposed) [0.5.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted bmusb [powerpc] (zesty-proposed) [0.5.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted bmusb [s390x] (zesty-proposed) [0.5.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted cylc [arm64] (zesty-proposed) [6.11.2-1]
[21:46] -queuebot:#ubuntu-release- New: accepted cylc [powerpc] (zesty-proposed) [6.11.2-1]
[21:46] -queuebot:#ubuntu-release- New: accepted cylc [s390x] (zesty-proposed) [6.11.2-1]
[21:46] -queuebot:#ubuntu-release- New: accepted khard [arm64] (zesty-proposed) [0.11.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted khard [i386] (zesty-proposed) [0.11.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted khard [ppc64el] (zesty-proposed) [0.11.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted bmusb [arm64] (zesty-proposed) [0.5.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted bmusb [ppc64el] (zesty-proposed) [0.5.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted cylc [armhf] (zesty-proposed) [6.11.2-1]
[21:46] -queuebot:#ubuntu-release- New: accepted khard [amd64] (zesty-proposed) [0.11.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted khard [powerpc] (zesty-proposed) [0.11.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted bmusb [i386] (zesty-proposed) [0.5.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted cylc [ppc64el] (zesty-proposed) [6.11.2-1]
[21:46] -queuebot:#ubuntu-release- New: accepted khard [s390x] (zesty-proposed) [0.11.3-1]
[21:46] -queuebot:#ubuntu-release- New: accepted cylc [amd64] (zesty-proposed) [6.11.2-1]
[21:47] -queuebot:#ubuntu-release- New: accepted khard [armhf] (zesty-proposed) [0.11.3-1]
[21:47] -queuebot:#ubuntu-release- New: accepted kicad [amd64] (zesty-proposed) [4.0.4+dfsg2-1]
[21:47] -queuebot:#ubuntu-release- New: accepted libzorpll [arm64] (zesty-proposed) [<IP_ADDRESS>-1]
[21:47] -queuebot:#ubuntu-release- New: accepted libzorpll [i386] (zesty-proposed) [<IP_ADDRESS>-1]
[21:47] -queuebot:#ubuntu-release- New: accepted libzorpll [ppc64el] (zesty-proposed) [<IP_ADDRESS>-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ndpi [amd64] (zesty-proposed) [1.8-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ndpi [armhf] (zesty-proposed) [1.8-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ndpi [powerpc] (zesty-proposed) [1.8-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ndpi [s390x] (zesty-proposed) [1.8-1]
[21:47] -queuebot:#ubuntu-release- New: accepted libzorpll [amd64] (zesty-proposed) [<IP_ADDRESS>-1]
[21:47] -queuebot:#ubuntu-release- New: accepted libzorpll [powerpc] (zesty-proposed) [<IP_ADDRESS>-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ndpi [arm64] (zesty-proposed) [1.8-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ndpi [ppc64el] (zesty-proposed) [1.8-1]
[21:47] -queuebot:#ubuntu-release- New: accepted libzorpll [armhf] (zesty-proposed) [<IP_ADDRESS>-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ndpi [i386] (zesty-proposed) [1.8-1]
[21:47] -queuebot:#ubuntu-release- New: accepted libzorpll [s390x] (zesty-proposed) [<IP_ADDRESS>-1]
[21:47] -queuebot:#ubuntu-release- New: accepted node-after [amd64] (zesty-proposed) [0.8.2-1]
[21:47] -queuebot:#ubuntu-release- New: accepted node-hook-std [amd64] (zesty-proposed) [0.2.0-1]
[21:47] -queuebot:#ubuntu-release- New: accepted ruby-defaults [amd64] (zesty-proposed) [1:2.3.3]
[21:47] -queuebot:#ubuntu-release- New: accepted vtgamma [amd64] (zesty-proposed) [0.2-1]
[21:47] -queuebot:#ubuntu-release- New: accepted node-shelljs [amd64] (zesty-proposed) [0.7.5-1]
[21:47] -queuebot:#ubuntu-release- New: accepted svxlink [amd64] (zesty-proposed) [15.11-2]
[21:56] -queuebot:#ubuntu-release- New binary: node-debug-fabulous [amd64] (zesty-proposed/universe) [0.0.4-1] (no packageset)
[21:56] -queuebot:#ubuntu-release- New binary: node-unique-stream [amd64] (zesty-proposed/universe) [2.2.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: fxlinuxprint [ppc64el] (zesty-proposed/none) [1.1.0+ds-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: nixstatsagent [ppc64el] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: rng-tools5 [ppc64el] (zesty-proposed/none) [5-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: jid [ppc64el] (zesty-proposed/none) [0.6.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: python-xattr [ppc64el] (zesty-proposed/main) [0.9.1-1] (ubuntu-server)
[23:19] -queuebot:#ubuntu-release- New binary: d3-tip.js [amd64] (zesty-proposed/none) [0.7.1-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: fxlinuxprint [i386] (zesty-proposed/none) [1.1.0+ds-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-disconnect-wifi [amd64] (zesty-proposed/none) [3.22.14-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-system-monitor [amd64] (zesty-proposed/none) [31-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: emacs-anzu [amd64] (zesty-proposed/none) [0.62-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-multi-monitors [amd64] (zesty-proposed/none) [0.00~git20160725.1.7390a66-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-better-volume [amd64] (zesty-proposed/none) [0.0-git20161106.ff67408-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: jqueryui [amd64] (zesty-proposed/universe) [1.12.1+dfsg-3] (ubuntustudio)
[23:20] -queuebot:#ubuntu-release- New binary: dhcpcanon [amd64] (zesty-proposed/none) [<IP_ADDRESS>-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: jid [i386] (zesty-proposed/none) [0.6.1-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: python-xattr [amd64] (zesty-proposed/main) [0.9.1-1] (ubuntu-server)
[23:20] -queuebot:#ubuntu-release- New binary: python-xattr [i386] (zesty-proposed/main) [0.9.1-1] (ubuntu-server)
[23:20] -queuebot:#ubuntu-release- New binary: fxlinuxprint [amd64] (zesty-proposed/none) [1.1.0+ds-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: python-xattr [arm64] (zesty-proposed/main) [0.9.1-1] (ubuntu-server)
[23:20] -queuebot:#ubuntu-release- New binary: node-package [amd64] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: jid [amd64] (zesty-proposed/none) [0.6.1-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: rng-tools5 [s390x] (zesty-proposed/none) [5-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: fxlinuxprint [arm64] (zesty-proposed/none) [1.1.0+ds-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: jid [s390x] (zesty-proposed/none) [0.6.1-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: fxlinuxprint [s390x] (zesty-proposed/none) [1.1.0+ds-1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: python-xattr [armhf] (zesty-proposed/main) [0.9.1-1] (ubuntu-server)
[23:22] -queuebot:#ubuntu-release- New binary: android-platform-tools-apksig [amd64] (zesty-proposed/none) [0.3+git154~gfdc6e98-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: jid [armhf] (zesty-proposed/none) [0.6.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: libnet-whois-ip-perl [amd64] (zesty-proposed/none) [1.19-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: nixstatsagent [arm64] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: nixstatsagent [s390x] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: rng-tools5 [armhf] (zesty-proposed/none) [5-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: tendermint-ed25519 [amd64] (zesty-proposed/none) [0.0~git20160723.0.1f52c6f-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: tendermint-go-process [amd64] (zesty-proposed/none) [0.0~git20161130.0.226eb65-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: jid [arm64] (zesty-proposed/none) [0.6.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: libpod-pom-view-restructured-perl [amd64] (zesty-proposed/none) [0.02-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: rng-tools5 [arm64] (zesty-proposed/none) [5-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: tendermint-go-event-meter [amd64] (zesty-proposed/none) [0.0~git20160420.0.c9240a5-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: libnet-ldap-sid-perl [amd64] (zesty-proposed/none) [0.001-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: ruby-neovim [amd64] (zesty-proposed/none) [0.3.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: nixstatsagent [armhf] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: zfs-auto-snapshot [amd64] (zesty-proposed/none) [1.2.1-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: fxlinuxprint [armhf] (zesty-proposed/none) [1.1.0+ds-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: python-xattr [s390x] (zesty-proposed/main) [0.9.1-1] (ubuntu-server)
[23:22] -queuebot:#ubuntu-release- New binary: rng-tools5 [i386] (zesty-proposed/none) [5-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: nixstatsagent [amd64] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rng-tools5 [amd64] (zesty-proposed/none) [5-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: fxlinuxprint [powerpc] (zesty-proposed/none) [1.1.0+ds-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: python-xattr [powerpc] (zesty-proposed/main) [0.9.1-1] (ubuntu-server)
[23:23] -queuebot:#ubuntu-release- New binary: nixstatsagent [i386] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rambo-k [amd64] (zesty-proposed/none) [1.21+dfsg-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: android-platform-tools-analytics-library [amd64] (zesty-proposed/none) [2.2.2-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: nixstatsagent [powerpc] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: jid [powerpc] (zesty-proposed/none) [0.6.1-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: rng-tools5 [powerpc] (zesty-proposed/none) [5-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: python-intervaltree-bio [amd64] (zesty-proposed/none) [1.0.1-1] (no packageset)
[23:50] -queuebot:#ubuntu-release- New: accepted android-platform-tools-analytics-library [amd64] (zesty-proposed) [2.2.2-1]
[23:50] -queuebot:#ubuntu-release- New: accepted d3-tip.js [amd64] (zesty-proposed) [0.7.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted emacs-anzu [amd64] (zesty-proposed) [0.62-1]
[23:50] -queuebot:#ubuntu-release- New: accepted android-platform-tools-apksig [amd64] (zesty-proposed) [0.3+git154~gfdc6e98-1]
[23:50] -queuebot:#ubuntu-release- New: accepted dhcpcanon [amd64] (zesty-proposed) [<IP_ADDRESS>-1]
[23:50] -queuebot:#ubuntu-release- New: accepted fxlinuxprint [amd64] (zesty-proposed) [1.1.0+ds-1]
[23:50] -queuebot:#ubuntu-release- New: accepted fxlinuxprint [armhf] (zesty-proposed) [1.1.0+ds-1]
[23:50] -queuebot:#ubuntu-release- New: accepted fxlinuxprint [powerpc] (zesty-proposed) [1.1.0+ds-1]
[23:50] -queuebot:#ubuntu-release- New: accepted fxlinuxprint [s390x] (zesty-proposed) [1.1.0+ds-1]
[23:50] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-disconnect-wifi [amd64] (zesty-proposed) [3.22.14-1]
[23:50] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-system-monitor [amd64] (zesty-proposed) [31-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jid [arm64] (zesty-proposed) [0.6.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jid [i386] (zesty-proposed) [0.6.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jid [ppc64el] (zesty-proposed) [0.6.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jqueryui [amd64] (zesty-proposed) [1.12.1+dfsg-3]
[23:50] -queuebot:#ubuntu-release- New: accepted fxlinuxprint [arm64] (zesty-proposed) [1.1.0+ds-1]
[23:50] -queuebot:#ubuntu-release- New: accepted fxlinuxprint [ppc64el] (zesty-proposed) [1.1.0+ds-1]
[23:50] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-multi-monitors [amd64] (zesty-proposed) [0.00~git20160725.1.7390a66-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jid [armhf] (zesty-proposed) [0.6.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jid [s390x] (zesty-proposed) [0.6.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted libnet-whois-ip-perl [amd64] (zesty-proposed) [1.19-1]
[23:50] -queuebot:#ubuntu-release- New: accepted nixstatsagent [amd64] (zesty-proposed) [1.0.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted nixstatsagent [armhf] (zesty-proposed) [1.0.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted nixstatsagent [powerpc] (zesty-proposed) [1.0.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted nixstatsagent [s390x] (zesty-proposed) [1.0.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted fxlinuxprint [i386] (zesty-proposed) [1.1.0+ds-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jid [amd64] (zesty-proposed) [0.6.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted libnet-ldap-sid-perl [amd64] (zesty-proposed) [0.001-1]
[23:50] -queuebot:#ubuntu-release- New: accepted nixstatsagent [arm64] (zesty-proposed) [1.0.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted nixstatsagent [ppc64el] (zesty-proposed) [1.0.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-better-volume [amd64] (zesty-proposed) [0.0-git20161106.ff67408-1]
[23:50] -queuebot:#ubuntu-release- New: accepted libpod-pom-view-restructured-perl [amd64] (zesty-proposed) [0.02-1]
[23:50] -queuebot:#ubuntu-release- New: accepted jid [powerpc] (zesty-proposed) [0.6.1-1]
[23:50] -queuebot:#ubuntu-release- New: accepted nixstatsagent [i386] (zesty-proposed) [1.0.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted node-debug-fabulous [amd64] (zesty-proposed) [0.0.4-1]
[23:51] -queuebot:#ubuntu-release- New: accepted node-unique-stream [amd64] (zesty-proposed) [2.2.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-xattr [amd64] (zesty-proposed) [0.9.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-xattr [armhf] (zesty-proposed) [0.9.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-xattr [powerpc] (zesty-proposed) [0.9.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-xattr [s390x] (zesty-proposed) [0.9.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rng-tools5 [amd64] (zesty-proposed) [5-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rng-tools5 [armhf] (zesty-proposed) [5-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rng-tools5 [powerpc] (zesty-proposed) [5-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rng-tools5 [s390x] (zesty-proposed) [5-1]
[23:51] -queuebot:#ubuntu-release- New: accepted node-package [amd64] (zesty-proposed) [1.0.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-xattr [arm64] (zesty-proposed) [0.9.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-xattr [ppc64el] (zesty-proposed) [0.9.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rng-tools5 [arm64] (zesty-proposed) [5-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rng-tools5 [ppc64el] (zesty-proposed) [5-1]
[23:51] -queuebot:#ubuntu-release- New: accepted tendermint-ed25519 [amd64] (zesty-proposed) [0.0~git20160723.0.1f52c6f-1]
[23:51] -queuebot:#ubuntu-release- New: accepted tendermint-go-process [amd64] (zesty-proposed) [0.0~git20161130.0.226eb65-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-intervaltree-bio [amd64] (zesty-proposed) [1.0.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rambo-k [amd64] (zesty-proposed) [1.21+dfsg-1]
[23:51] -queuebot:#ubuntu-release- New: accepted ruby-neovim [amd64] (zesty-proposed) [0.3.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted zfs-auto-snapshot [amd64] (zesty-proposed) [1.2.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted python-xattr [i386] (zesty-proposed) [0.9.1-1]
[23:51] -queuebot:#ubuntu-release- New: accepted tendermint-go-event-meter [amd64] (zesty-proposed) [0.0~git20160420.0.c9240a5-1]
[23:51] -queuebot:#ubuntu-release- New: accepted rng-tools5 [i386] (zesty-proposed) [5-1]


[23:35] <donofrio_>  If anyone has some time and feel like helping here is my new install of 17.04 and I get this (mouse moves aross both screens and I can even bring up terminal on left side - any thoughts of how to fix? https://1drv.ms/i/s!AsBlZbBf72iNm4Z_w3Cbr3OW7rNKHw  hwinfo@ https://apaste.info/naDx
[23:45] <mingdao> think that's called tearing
[23:45] <mingdao> not sure; never eXPerienced it
[23:46] <donofrio_> mingdao, yes that is what is is doiing exactly
[23:46] <mingdao> that's an Apple computer?
[23:46] <donofrio_> yes
[23:46] <mingdao> never eXPerienced one of those, either
[23:46] <donofrio_> imac5,5 I believe
[23:46] <mingdao> I can't tell much from that output
[23:47] <mingdao> can you post the output of: lspci -k|nc termbin.com 9999
[23:47] <mingdao> if you have netcat
[23:48] <mingdao> AMD/ATI ... wonder if that's the amdgpu
[23:48] <donofrio_> mingdao, the #ubuntu camp wanted 17.04 and not 17.10 so I'm rebuilding In 40 min I'll be back to 17.10
[23:48] <donofrio_> fwiw dmesg is https://apaste.info/X1vH
[23:49] <mingdao> donofrio_: I'm not going to be much help atm ... must take daughter to the store; just saw you went 10m w/no response
[23:50] <mingdao> hopefully someone w/Mac eXPerience will show up
[23:50] <mingdao> check the forums, also, as this channel seems pretty low traffic
[23:50] <donofrio_> k I'll be here (I've been on iirc for over two decades and I know things take time.....) back to lurking for me ;)


[00:00] <codepal> hrm, won't I have to get it to crash first?
[00:01] <codepal> or does it pull in logs of progs already crashed?
[00:03] <penguin42> codepal: Yes you need to get it to crash first
[00:04] <penguin42> codepal: SO boot the installer and go to Try Ubuntu rather than install, then double click on the install and go through the installer; then when it dies hopefully you can still open a terminal
[00:04] <penguin42> (although I thought there was an easier way - hmm)
[00:06] <codepal> right, thank you!
[00:07] <codepal> is it normal for the installer to take > 1min from "For Best results," > Continue?
[00:14] <penguin42> I can't remember when For Best Results come sup
[00:14] <codepal> First screen after --- What do you want to do? Install / Live
[00:15] <penguin42> hmm I don't think it should take long
[00:16] <codepal> what are the min spec details for precise?
[00:19] <penguin42> not sure - what have you got?
[00:19] <codepal> man, submitting a bug report could be hard if it's gonna take over 20mins to crash :P
[00:19] <codepal> Celeron D341
[00:21] <codepal> Intel® Celeron(R) CPU 2.93GHz  in sysinfo
[00:21] <penguin42> that should be fine - how much ram?
[00:21] <codepal> Mem: 3.9 GiB & running off a DVD
[00:22] <penguin42> oh yeh, no problem
[00:22] <codepal> 32-bit
[00:22] <penguin42> are you sure your DVD burn is good?
[00:22] <codepal> I'll just check checksum
[00:23] <penguin42> I was thinking more about the burn rather than the download
[00:23] <penguin42> it's a lot easier these days to install from thumb drive
[00:24] <infid> have people found 'precise pangolin' alpha to be stable enough for software development or home desktop use?
[00:24] <infid> i really need a distro of ubuntu that has newer packages, even 11.10 has outdated packages
[00:24] <CyberDawg> Is v12 using Unity?
[00:24] <penguin42> infid: it's not too bad, some stuff breaks now and again during development
[00:25] <penguin42> CyberDawg: The default with Ubuntu is Unity, you can install GNome3 packaes if you like, or KDE etc
[00:25] <infid> penguin42: enough to where it's probably not a good idea to install it on my work station at work for php development?
[00:26] <codepal> perfect match on md5 checksums
[00:26] <infid>  i just don't want it crashing on my everyday or not allowing me to install packages
[00:26] <penguin42> infid: I wouldn't
[00:26] <infid> penguin42: but i can't install LTS either because those packages are waaaay too out of date
[00:26] <penguin42> infid: But there again I keep Lucid at work and use PP on my home machines
[00:26] <infid> it's like i'm caught betwen a rock and a hard place
[00:27] <codepal> penguin42: are you trying to say that DVD installs are more notorious?
[00:27] <CyberDawg> penguin42, thanks for the info
[00:27] <penguin42> codepal: Well you just get bad burns and things and it takes a while to burn the DVD etc - and whats the point, it's just so much easier with a thumb drive
[00:27] <codepal> lol, I'm thinking I'll run this baby as a live-hdd
[00:28] <codepal> that way I won't ever have to worry about installing it :P
[00:28] <penguin42> best to install ; although I do use the CD images in VMs for things like banking - means I always run with a fresh image
[00:29] <codepal> I let you know when this thing decides to crash
[00:29] <CyberDawg> instead of running from USB and it be run fron an SD card?
[00:29] <codepal> I mean, it's like taking forever!
[00:30] <penguin42> codepal: If you have a terminal then do a dmesg and see if there are any errors
[00:30] <jtaylor> installing?
[00:30] <yofel> wtf. - I upgraded my eeePC and in precise the touchpad moves my mouse as soon as I touch it even if I'm not moving @_@
[00:31] <penguin42> CyberDawg: Not sure; I suspect it depends how the SD is connected, some SD readers look exactly like a USB thumb drive to the host
[00:31] <penguin42> yofel: Is it in absolute mode ?
[00:31] <yofel> penguin42: where do I see that?
[00:31] <CyberDawg> penguin42, think I will give that a try after dindin
[00:31] <codepal> penguin42:  can't see anything
[00:32] <penguin42> yofel: Dunno, I was fairly sure some of the pads could do it
[00:40] <codepal> so what the recommended fs format for precise?
[00:42] <yofel> ext4 I would say
[00:44] <codepal> glad to see xkill still works -  he
[00:45] <yofel> ls
[00:45] <yofel> ...
[00:50] <codepal> bbs
[01:57] <lucas-arg> wow kde 4.8 impresive
[02:01] <snadge> how do you get dpkg-buildpackage to do parallel builds?
[02:01] <snadge> this is annoying
[02:01] <snadge> DEB_BUILD_OPTIONS=parallel=9
[02:01] <snadge> thats not working.. passing -j9 isnt working
[02:05] <snadge> maybe i should use pbuild ? i dont know
[02:08] <infid> how do you install updates after installing precise? are there any?
[02:08] <infid> i'm used to lucid so this unity interface or whatever is weird
[02:11] <snadge> apt-get update ; apt-get upgrade
[02:11] <snadge> theres also update-manage
[02:11] <snadge> +r
[02:11] <infid> there's no way to do it from the gui?
[02:11] <snadge> sure.. run update-manager
[02:12] <infid> how do you click to it
[02:12] <snadge> win (meta) - type up
[02:12] <infid> thx
[02:12] <infid> i tried alt+f2 then typing up before but that didnt work but your way does thanks
[02:12] <snadge> to do it purely with the mouse
[02:13] <snadge> click the icon in the top right corner.. theres an updates available thing
[02:13] <snadge> if thats not there.. you can go
[02:14] <snadge> click on the dash icon.. click on "more apps", scroll down till you find "update manager"
[02:14] <snadge> thats kinda painfully slow though ;)
[02:15] <snadge> now im trying to figure out, why this stupid fucking package is only building with one thread
[02:15] <snadge> despite my repeated attempts to override that
[04:33] <codepal> thoroughly impressed with Unity
[04:33] <codepal> good job folks
[04:37] <snadge> i am for the most part
[04:37] <snadge> it has an irritating input focus bug that almost shits me to tears every time it happens
[04:39] <codepal> hrm? I think I might have noticed that... a small delay before it allows you to type?
[04:41] <snadge> no
[04:42] <snadge> this is annoyingirfox on it (in particular) when typing in the address bar, the autocomplete feature does not work
[04:42] <snadge> if you right click and bring up context menu, when you move the mouse over it, it disappears
[04:42] <snadge> unless you click on the window title bar, to manually focus it
[04:44] <codepal> uck
[04:44] <codepal> I made a small oopsy before I installed, somehow fudged my old LTS - :'(
[04:44] <codepal> more fixing to do
[04:45] <codepal> I've been using 10.04 for ages because of the wacom support it had
[04:45] <codepal> (until I upgraded xorg)
[04:45] <codepal> I see a wacom control panel in settings, gonna plug in the old serial wacom and see what kind of support I get.
[04:46] <snadge> 12.04 has allegedly merged some new input code
[04:46] <codepal> yeah, they'll be wanting to compete with Windows 'Kinect' 8
[04:47] <codepal> I for one, will never, ever use a wand or speak to my computer to get it to do things
[04:47] <codepal> mouse and keyboard for me, it's tradition
[05:09] <codepal> well that was exciting.... anybody round here tried loggin into a debian machine via SSH x forwarding ?
[05:09] <codepal> unfortunately apport complained about a few missing things libpam stuff, and I coundn't finish the bug submit
[06:07] <codepal> Anybody got some idea how I might find out whether / how I can install a serial wacom Intous in ubuntu 12.10?
[06:07] <codepal> hrm, I might try a restart with it plugged in first...
[06:07] <codepal> bbs
[08:22] <sbarcteam> hi.
[08:22] <sbarcteam> I've just installed precise inside a virtualbox on mac.
[08:22] <sbarcteam> And it works :)
[08:22] <sbarcteam> which is kinda nice.
[08:49] <lotuspsychje> u like precise changes?
[11:14] <codepal> yole! - What's cotendo.com got to do with ubuntu?
[11:14] <codepal> lsof shows many, many connections....
[13:01] <Hoyt> hi , anyone using Precise here ?
[13:01] <Hoyt> could you help me run a command:   find /usr/lib/indicator* -name libappmenu.so , and i want the result path , thanks
[13:02] <snadge>  usr/lib/indicators3/7/libappmenu.so
[13:02] <Hoyt> thanks
[13:03] <Hoyt> i shall get that launchpad bug fixed
[13:07] <BluesKaj> Howdy all
[13:10] <penguin42> is anyone seeing scrolling problems? I'm seeing in chrome a lot of jumping back to the top of the page for no apparent reasons
[13:12] <BluesKaj> penguin42,  that's chrome , it's slow to load everything , so if you scroll down to find something before the page is fully loaded , jumps back up when it's done , it's pita for sure
[13:12] <penguin42> BluesKaj: I hadn't had that problem before
[13:12] <BluesKaj> I've seen it on chromium for a while
[13:32] <Daekdroom> That's started to happen to me on Firefox too.
[14:34] <penguin42> hmm I'm seeing this in pidgin as well
[14:40] <penguin42> ok, can some one try this - just gently keep scrolling down with a mouse roller - does it ever jump up?  OK - if not try moving the mouse very slightly while scrolling
[15:31] <FernandoMiguel> guud afternoon
[15:32] <penguin42> Hey FM
[16:17] <coz_> any issues with this mornings updates, before I restart?
[16:17] <pangolin> none that i have seen mentioned
[16:18] <coz_> pangolin,  ok thanks, I will reboot,, and if I have to reinstall I will come back crabby :)
[16:18]  * pangolin sets the ban now :P
[16:22] <FernandoMiguel> lol
[17:07] <penguin42> anyone in Kubuntu+1 at the moment? Can they try starting a gnome-terminal - it shrunk back to a single line
[17:50] <alkisg> I have my laptop connected to an external monitor. After login I get a cloned view. Then I type:
[17:50] <alkisg> xrandr --output LVDS1 --off
[17:50] <alkisg> Then compiz crashes, and I get a prompt to report the bug
[17:51] <alkisg> And when I click yes, it tells me that it's a bug report against a package that is not installed!
[17:51] <alkisg> ....should I manually file 2 bugs?!
[17:51] <penguin42> sounds like it
[17:51] <alkisg> Thank you
[17:51] <penguin42> when you say it's against one you haven't got installed, is it the source package for one you have installed?
[17:52] <alkisg> /usr/bin/python /usr/share/apport/apport-gtk
[17:52] <alkisg> I guess that's the program that shows the dialog
[17:52] <alkisg> I have a Greek interface so I don't know the exact wording
[17:53] <penguin42> yeh apport is the one that does error reporting
[17:53] <alkisg> compiz gets respawned of course and it works afterwards
[17:53] <alkisg> It's just that it crashes with the xrandr command (intel graphics), and I don't know why apport thinks that I don't have compiz installed
[17:53] <penguin42> alkisg: do you know the exact Greek wording?
[17:54] <alkisg> Yes I have the dialog open still
[17:54] <alkisg> Η αναφορά ανήκει σε ένα πακέτο το οποίο δεν είναι εγκατεστημένο.
[17:54] <alkisg> "The report belongs to a package that is not installed"
[17:54] <alkisg> And a [Close] button
[17:54] <penguin42> hmm ok; then best to report both of them
[17:55] <alkisg> Thank you penguin42
[17:58] <aguitel> is anyone using nvidia-173 drivers in 12.04 ?
[18:48] <BluesKaj> aguitel,  GPUs ranging from GeForce series 5 to GeForce series 9 are supported according to synaptic
[19:38] <aguitel> BluesKaj, it is not working in precise
[19:39] <iceroot> aguitel: bug is opened?
[19:39] <aguitel> iceroot, i am in oneric
[19:40] <iceroot> aguitel: bug is opened?
[19:40] <aguitel> iceroot, not
[19:40] <iceroot> aguitel: then please open the bug
[19:40] <iceroot> aguitel: i told you 5 times to open the bug
[19:40] <aguitel> iceroot, but need to install again precise
[19:40] <iceroot> aguitel: i also told you how to open the bug when you are on 11.10
[19:41] <aguitel> iceroot, yes i know
[19:41] <aguitel> but i decide to install oneric
[19:41] <iceroot> aguitel: then what is the problem? you have a problem on 12.04, you dont want to open a bug and now you are on 11.10
[19:41] <BluesKaj> good luck iceroot :P
[19:42] <aguitel> iceroot, when you talk to me to open a bug for the first time i decide to reinstall oneric
[19:42] <iceroot> aguitel: what is the current problem now?
[19:43] <aguitel> iceroot, in oneric all is ok
[19:43] <iceroot> aguitel: fine
[19:44] <iceroot> [20:38]   aguitel | BluesKaj, it is not working in precise
[19:44] <iceroot> open a bug for that, nothing less or more
[19:45] <iceroot> 12.04 is alpha and normally only for people how wants to do some testing, bugreporting, bug fixing, nothing else is 12.04 at the moment
[19:46] <iceroot> so if you dont want to work with Launchpad at the moment i thing 12.04 is not what you are looking for at the moment, wait for the stable release and hope your bug is fixed by someone else (or even detected)
[19:46] <bjsnider> if you're using the 173 driver you might be better off using nouveau instead at this point
[19:46] <bjsnider> nvidia doesn't put much effort into the 173 blob
[19:47] <bjsnider> i'm assuming the hardware is old junk
[19:48] <bjsnider> or end-of-life hardware, to put it another way
[19:49] <iceroot> wasnt there a driver for old hardware too?
[19:49] <iceroot> nvidia-legancy or something like that
[19:58] <bjsnider> the nvidia-96 and 173 drivers are for old hardware
[20:05] <aguitel> but this is linux ,don't need the last device
[21:00] <varikonniemi> hello, could somebody tell me what is recommended to get a program to support the system titlebar under unity, ie hide all window decoration and titlebar from the window? Is it trivial or must it be designed to use it
[21:01] <varikonniemi> and is it possible some future ubuntu version does it os-side so the program does not have to be specifically coded for ubuntu ?=
[21:02] <trism> varikonniemi: oh, you are writing a program and you want it to have the behavior? there isn't anything special you need to, the window manager takes care of that
[21:02] <varikonniemi> no i am running a program
[21:02] <varikonniemi> and it refuses to hide the titlebar
[21:03] <trism> varikonniemi: might help to specify the exact program, and again sorry for misunderstanding
[21:03] <varikonniemi> https://imgur.com/Nb5hz
[21:04] <varikonniemi> no need to say sorry :D my english is not the best
[21:04] <varikonniemi> in that screenshot spring thinks it is maximized
[21:12] <varikonniemi> wait a second, i clicked maximized again and again and again, and finally it seemed to have worked, it rendered without titlebar, but immediately crashed :(
[21:16] <varikonniemi> i guess my question is: is there anything that should be done/could be done to ensure it should work, or is this just a random bug?
[21:24] <bjsnider> varikonniemi, this channel is probably not the best one to ask this question
[21:29] <trism> varikonniemi: I just installed to test and I see it here though, might be worth a bug report, either unity not picking up the window correctly or spring doing something weird. I did notice though that the decoration does hide in gnome shell with the modified theme I linked in #ubuntu earlier
[21:31] <varikonniemi> ok so it is probably a unity bug then. bjsnider why is this not the correct channel? is'n this about ubuntu development, and this is an issue with ubuntu / or spring
[21:31] <varikonniemi> and what trism said suggests its ubuntu?
[21:32] <bjsnider> it's not the correct channel because the unity/ayatana programming crowd isn't here
[21:33] <varikonniemi> so where are they? :P
[21:33] <Daekdroom> #ubuntu-unity
[21:34] <varikonniemi> thank you :)
[21:35] <bjsnider> but sunday is not the best day to get in touch with them because they have weekends off and whatnot
[23:34] <oconnore> how do you change the layout of windows in raw X11? the update to 12.04 killed unity, so now I am in raw X and can't see the update manager.
[23:34] <jtaylor> use a terminal?
[23:35] <Ben64> oconnore: try starting metacity
[23:35] <jtaylor> if getting to updates is your problem :/
[23:36] <oconnore> Ben64: thanks
[23:41] <oconnore> This is interesting. I am upgrading to 12.04 to try to fix a keyboard input problem, where, for example, I would type "terminal" in the finder and the last 4 letters would be dropped. It also happened in firefox, gedit, and terminal. As soon as unity crashed, my problem went away.
[23:41] <oconnore> My keyboard is now perfectly responsive.
[23:44] <oconnore> Perhaps if this update doesn't work, my next step should be to install xfce or maybe kde.
[23:44] <mw1coe> Anyone help with a PowerPC Install please.
[23:58] <codepal> Q: Why does Ubuntu 12.04 setup 3 partitions, when installing in side-by-side mode?
[23:59] <codepal> I had a ext4 partition all ready for it on my SSD, then it went ahead and repartitioned it into 3. 1 x data - 1 x base - 1 x swap...
[23:59] <codepal> I already had a swap, which somehow it didn't see


[05:38] <jam> vila: no issues building the installers, I just haven't tried yet
[05:43] <vila> jam: do you plan to try soon or should I announce 2.4.0 without them ?
[06:32] <vila> hi all !
[06:34] <vila> poolie: regarding HTTPErrors on jubany, here is an interesting one: http://paste.ubuntu.com/677730
[06:34] <poolie> hi vila, jam
[06:35] <poolie> hi vila
[06:35] <jam> hi poolie
[06:36] <jam> so... interesting news about fdatasync
[06:36] <vila> poolie: hey
[06:36] <poolie> i think i know what's happening there, which is that it's getting None for one of the branches so lp rejects the attempt to file an mp
[06:36] <jam> test suite w/fdatasync 3h35min, hacking it out, 1h35min
[06:36] <jam> still not as fast as bzr-2.3's 45min
[06:36] <poolie> locally? or on pqm?
[06:36] <jam> poolie: on pqm
[06:36] <jam> so there is more going on than just fdatasync
[06:36] <poolie> that's about what i would expect
[06:36] <poolie> right
[06:36] <jam> but it is clearly part of it
[06:36] <poolie> i wonder if it's failing to load some extensions?
[06:37] <jam> poolie: doesn't that issue warnings, and we use -Werror ?
[06:38] <poolie> it's just kind of a shot in the dark about what could cause such a large slowdown
[06:38] <poolie> do we know anything about the relative timing of particular tests?
[06:38] <jam> poolie: yeah, the difference w/ 2.3 was where I was going to focus
[06:38] <jam> poolie: we could do a failing pqm run that doesn't filter out successes, and we would get back a subunit stream containing all the timings
[06:42] <jam> 2.4 has a few more tests, 26.3k vs 24.7k than 2.3
[06:42] <jam> I doubt that accounts for doubling the time, though
[06:44] <jam> poolie: I'll try to find another quiescent time for PQM and put another couple of test runs through
[06:44] <poolie> you can also just ask the sysadmins to run something on that box
[06:45] <poolie> i saw Sidnei wrote about having a tarmac-on-openstack set up for tarmac so i might try to convert that some time
[06:45] <poolie> vila, that bug you mentioned with httperror i was going to keep tracking under the same number
[06:45] <poolie> i fixed some of them but that's still a problem
[06:46] <poolie> it's related to the Branch.getByURL call (that might not be the exact name)
[06:48] <vila> poolie: not a bug, just something I caught while monitoring jubany after deploying bzr-builddeb yesterday
[06:48] <poolie> it is a bug
[06:48] <vila> right
[06:49] <vila> what I mean is that I've seen different outputs usually, this one was mentioning something different (the missing branch)
[06:51] <vila> ... and I didn't file a new bug before mentioning it to you, should I ?
[06:52] <vila> so s/not a bug/not *yet* a bug/
[06:59] <vila> jam: do you plan to try building the windows installers soon or should I announce 2.4.0 without them ?
[06:59] <jam> vila: I'm working on them as we chat
[07:00] <vila> jam: great, waiting for your feedback to do the announcement
[07:00] <jam> anyone know if qbzr-0.21 is still the right version to build with?
[07:02] <jam> there seems to be an 0.21.1, I'll go with that
[07:02] <jam> though I think there was supposed to be a 0.21.2 coming soon
[07:25] <vila> maxb: do you plan to upload bzr-svn-1.1.0 to the stable ppa ?
[07:49] <poolie> are you ready to mumble?
[07:50] <fullermd> Speaking of qbzr, is it just me or does it still completely hork the test suite on .dev?
[07:51] <fullermd> ...  and of course, it figures I say that right before firing off a pull that gets the rev that fixes it...
[07:51] <jam> poolie: I believe that has to be spelled "muuuummmbbbbbbbbllllllee" ?
[07:51]  * fullermd sighs.
[07:53] <jam> poolie: http://www.youtube.com/watch?v=WvufFwdqMzg&feature=player_detailpage#t=53s
[07:53] <jam> but yes, I'm logged in
[07:54] <poolie> yep
[07:54] <jam> Or maybe "LETS GET READY TO *mumble*"
[07:59] <jam> vila: it says it will be 20min for it to copy down to me, and then 5-10 min for me to upload them to launchpad
[07:59] <jam> but -1 is built
[08:42] <jam> vila: windows installers have been uploaded and announced
[08:43] <vila> jam: thanks
[08:45] <poolie> Riddell, so can people actually get into translating bzr now?
[08:46] <poolie> i thought perhaps you should send an update on the state of i18n - perhaps it's better to wait until it's live though
[08:54] <Riddell> you go to https://translations.launchpad.net/bzr and do the translation
[08:55] <Riddell> it's set to restricted so you have to be an approved translator
[08:55] <Riddell> I can e-mail the translators list and bazaar list to announce that
[08:56] <jam> poolie: https://code.launchpad.net/~hid-iwata/bzr/fix-827721/+merge/73125 I don't know if you saw that I already made the fix, but accidentally submitted it to trunk instead of 2.4
[08:56] <jam> I'm guessing you did the same fix?
[08:56] <poolie> i saw a comment about that
[08:56] <poolie> i sent just a correction of his patch to 2.4
[08:56] <poolie> did you fix it in a substantially different way?
[09:06] <jam> poolie: I just indented by 1 space
[09:07] <poolie> that's what i did too
[09:07] <poolie> it's running on jubany now
[09:07] <poolie> *bellany
[09:13] <jam> poolie: well, jubany does have better hardware, maybe we could install PQM and.... :)
[09:17] <jelmer> jam: I'm looking at my bzr/move-hashcache branch; is it correct that just WT2 and WT3 use the hashcache?
[09:18] <jam> yes
[09:18] <jam> the cache is in the Dirstate for WT4+
[09:28] <poolie> ok i'm going to sign off
[09:29] <poolie> vila, if you commit that fix to trunk it should automatically get onto docs.b.c.c
[09:29] <vila> poolie: yup, I know, submitting to pqm
[09:30] <vila> poolie: grepping 2\.4 I found some references to python-2.4 that we don't support anymore, I'll file a bug for that as several docs needs a deeper fix
[09:30] <jam> jelmer: rather than resubmit, I think just marking your submission back to NeedsReview
[09:30] <jam> at least for me, it means that email threads get put on the right submission, etc.
[09:30] <jam> like I *just* commented on the last one
[09:30] <jelmer> ah, hmm
[09:30] <jelmer> with some projects I find that reviewers ignore MPs that already have votes on them
[09:31] <jam> jelmer: well, I just ignore everything you submit regardless :)
[09:32] <fullermd> jam: Ignore who?  ;p
[09:32] <jam> jelmer: I supposed it is project dependent. I do a lot of processing merge requests via email vs the web ui
[09:32] <jam> and often keep "unread" things that are in queue to reviewe
[09:32] <jam> unfortunately, LP does *not* link emails across resubmissions
[09:33] <jam> so it starts a new email thread
[09:33] <jam> and doesn't have a "this proposal has been superseded" email
[09:33] <jam> in this particular case, it looks like we raced
[09:33] <jam> where I was in the web app commenting, and you were resubmitting.
[09:34] <jelmer> jam: Clearly the workflow isn't optimal yet :) I'm happy to just change the MP status for bzr though
[09:35] <jam> for bzr, I would probably resubmit if there has been a long discussion that is now only partly relevant due to large changes
[09:36] <vila> jam: additionally when you review via mail CC'ing the submitter, the submitter gets two mails, one of them without the lp links and headers which also break threading
[09:36] <jelmer> jam: also, we don't always change the MP status when we vote so there's no way to indicate a MP is ready for another review
[09:37] <jelmer> e.g. https://code.launchpad.net/~jelmer/bzr/move-hashcache/+merge/73299
[09:37] <jam> sure, but you can also just *say* "ready for re-review"
[09:37] <vila> jelmer: you can request an additional review from the web ui, which should send emails
[09:38] <vila> jelmer: I did that yesterday for https://code.launchpad.net/~jelmer/bzr/metadir-goes-colo/+merge/72451 and got an email with the updated diff AFAICS
[09:38] <jam> vila: yeah, but then jelmer resubmitted it as well :)
[09:38] <jelmer> jam, vila: neither of those makes it easy to see what needs another review on the +activereviews page
[09:39] <vila> jelmer: true :-/
[09:39] <jelmer> anyway, I wasn't trying to be a pedant..
[09:39] <jam> jelmer: *everything* needs review if it is still on that page
[09:39] <jam> that page should always be pushed to 0
[09:39] <jam> IMO
[09:39] <jam> though yes, some with more or less priority
[09:39] <jam> which isn't particularly easy to see
[09:39] <jam> though, even when used "correctly" it isn't very easy to see
[09:39] <vila> jelmer: I don't think you were
[10:14] <jelmer> vila: several of the recent problems building against 2.4 seem fail because of the safety net
[10:14] <jelmer> grmbl
[10:14] <jelmer> vila: several of the recent problems building against 2.4 seem be because of the safety net
[10:14] <jelmer> vila: e.g. https://launchpadlibrarian.net/78535248/buildlog_ubuntu-oneiric-i386.trac-bzr_0.4.2%2Bbzr117~ppa34~oneiric1_FAILEDTOBUILD.txt.gz
[10:15] <jelmer> do you have any idea what might be causing that? It seems to be some weird interaction with fakeroot (which LD_PRELOADs and pretends the currents uid is 0)
[10:16] <vila> jelmer: failing to call setUp for the parent class ?
[10:16] <jelmer> it succeeds when not run under nosetests
[10:17] <jelmer> argh, when not run under fakeroot
[10:17] <jelmer> and as far as I can tell setUp() gets called where necessary
[10:18] <vila> hmm, doesn't explain the attributeerror...
[10:18] <vila> _SAFETY_NET_PRISTINE_DIRSTATE was introduced recently, let me check
[10:19] <vila> created in _check_safety_net, called by _make_test_root
[10:20] <vila> there is a comment there about tricky test dir on OSX,
[10:20] <vila> the issue there was that /tmp is redirected to /private/tmp
[10:21] <vila> jelmer: could it be that fakeroot is doing some trick too about /tmp ?
[10:21] <vila> not that it would explain the AttributeError either...
[10:21] <jelmer> vila: well, it pretends the owner of all files is root.root, for /tmp too.
[10:22] <vila> brain dumping,
[10:23] <vila> we had issues related to tests run as root, we had issues related to a very early failure with the test root not being properly created or something
[10:24] <jelmer> fwiw the debian packages have always been using fakeroot, but this issue has only come up recently
[10:25] <vila> jelmer: recently << 2011-07-11 ?
[10:25] <jelmer> vila: I'm also surprised it's trying to access /root/.bazaar/locations.conf
[10:26] <vila> jelmer: $HOME == /root ?
[10:26] <jelmer> vila: nope, HOME=/home/jelmer
[10:26] <vila> wow, test isolation
[10:26] <jelmer> although getpwuid(0).pwd_home is /root
[10:27] <vila> HOME is not set I presume, fallback to python whatever
[10:27] <jelmer> in fact, it seems that if I change the home directory of root in /etc/passwd the tests all pass..
[10:27] <vila> yup, python is getting there to get the home if nothing else is available
[10:28] <jelmer> so the _SAFETY_NET_PRISTINE_DIRSTATE issue is a red herring
[10:28] <vila> known issue
[10:28] <vila> not sure they are related
[10:30] <jelmer> vila: it looks like it's now reading the config because it wants to know if it should fdatasync, perhaps it wasn't doing that previously
[10:30] <jelmer> vila: is the safety net perhaps created before BZR_HOME is overridden?
[10:30] <vila> for the config stuff, yes, it wasn't and it's related to finding HOME from /etc/passwd and is a test isolation issue
[10:30] <jelmer> because creating the safety net involves creating a tree, and that involves reading the config
[10:30] <vila> yup
[10:31] <vila> oh, and some exception is lost ?
[10:31] <vila> so we miss the safety net not being created ?
[10:33] <jelmer> vila: if creating the safety net fails then the exception is masked by the fact that the teardown fails, because we haven't set _SAFETY_NET_PRISTINE_DIRSTATE yet at that point
[10:33] <vila> urgh, http://paste.ubuntu.com/677867 , indeed the safety net is created before overriding the env for tests
[10:37] <vila> jelmer: in the short term, can you try a way to run selftest in a context where bzr *can* read its config files ?
[10:38] <vila> s/try/find/
[10:38] <vila> jelmer: like... BZR_HOME=<valid home> may be ?
[10:39] <vila> jelmer: valid here doesn't imply there is a .bazaar dir, just that we get File not found instead of permission denied
[10:41] <vila> alternatively we should catch permission denied and handle it as meaning we can't read the config files
[10:42] <jelmer> vila: overriding the environment variables doesn't seem to work :(
[10:43] <vila> may be fakeroot filters it ?
[10:44] <jelmer> vila: nope
[10:45] <vila> jelmer: hmm, does os.path.isfile(infile) raises permission denied ?
[10:45] <vila> s/s//
[10:46] <jelmer> it returns False
[10:46] <jelmer> vila: still, that seems like the wrong thing to do. We shouldn't be reading the users' config
[10:46] <vila> jelmer: configobj uses this to decide if the file exists
[10:46] <vila> jelmer: why ?
[10:47] <vila> jelmer: we're not *in* the test at this point, we are still in the user context setting up the test environment
[10:47] <jelmer> vila: this is for the test setup, we shouldn't be using the users preferences for the repository we're going to use for testing
[10:47] <vila> jelmer: we obey TMP
[10:48] <vila> which is part of the user env
[10:48] <jelmer> vila: sure, but this means you could get varying test results based on what the user has in ~/.bazaar/bazaar.conf
[10:48] <vila> no, because we take care of that just after
[10:48] <vila> but I think I've found the hole
[10:48] <vila> TestCase.setUp has been called and there we clear BZR_HOME
[10:50] <vila> jelmer: try moving _make_test_root *before* the upcall to setUp() ? (May not be enough)
[10:51] <jelmer> AttributeError: 'TestRepository' object has no attribute '_bzr_selftest_roots'
[10:52] <jelmer> vila: where do we reset the standalone working tree so it isn't affected by the users settings?
[10:52] <vila> I don't follow
[10:53] <vila> the safety net is supposed to be created... above the test dirs
[10:54] <vila> the tests have no idea it exists
[10:54] <jelmer> vila: ah, nevermind.. I see we just use bzrdir.BzrDir.create_standalone_workingtree() to get at the dirstate bytes
[10:54] <vila> jelmer: try commenting out the calls to _create_safety_net and _check_safety_net
[10:54] <jelmer> vila: that does mean we try to read ~/.bazaar/bazaar.conf for every test though, doesn't it?
[10:55] <vila> yes, that's the main issue related to config in the fdatasync patch
[10:56] <jam> vila, jelmer: We only create the safety net once per test suite run, right?
[10:56] <jelmer> does remembering the raw bytes of the dirstate file really gain us all that much speed?
[10:56] <jam> we just check it on every test
[10:56] <jam> jelmer: spiv commented it was about 15% of the run speed for the whole test suite
[10:56] <jam> so... yes
[10:57] <jelmer> jam: yeah, I guess I'm just seeing it being executed multiple times because its setup fails
[10:57] <jam> jelmer: the point of that code was we *used* to have a real problem with a test case not isolating itself from the environment
[10:57] <jam> hence you can do "bzr log -r revid:A"
[10:57] <jam> in bzr.dev
[10:58] <jam> It honestly hasn't been a problem for a while, but perhaps that is because it gets caught easily. I would venture it is because TestCaseInTempDir/MemoryTransport et al make it easy to just inherit a base that is env safe
[10:58] <jam> I think vila already submitted a bug that if _create_safety_net fails, it should just abort the test suite
[10:58] <jam> rather than fail 20k times
[10:59] <vila> https://bugs.launchpad.net/bzr/+bug/825027
[10:59] <jam> vila, jelmer, Riddell: I'd like to do some more PQM timing runs, but I want to make sure not to block anything. Is there a reasonable time for me to do it?
[10:59] <vila> jam: thanks !
[11:00] <vila> jelmer: doh, but you *did* comment on this one !
[11:00] <spiv> jam, jelmer: IIRC by reading the raw bytes we skipped open_workingtree and that in turn skipped reading all bazaar.conf and locations.conf
[11:01] <vila> spiv: right, but the issue here is when *creating* the wt
[11:01] <jelmer> jam: as long as you don't approve any MPs you should be good ;)
[11:01] <jam> jelmer: k, I'll make sure to reject all patches. :)
[11:01] <jam> jelmer: it is more "is there stuff you want to see land soon that hasn't been approved so I'll wait"
[11:01] <vila> jam: fine with me, I'm finishing the announcement for 2.4
[11:01] <spiv> (Because it is the safety net, not some wt inside it, that means reading the users real ~/.bazaar/locations.conf, etc)
[11:01] <jam> we already have a Q depth of 4
[11:02] <jelmer> jam: I figured :) Nothing from me.
[11:02] <jam> hi spiv! good to see you around, btw
[11:03] <jam> jelmer: is it "_create_safety_net" or "_check_safety_net" that is cousing problems for bzr-cia?
[11:03] <vila> jam: i.e. nothing urgent from me, the one waiting can even be canceled (but let me know as it was a pqm-submit one)
[11:04] <spiv> jam: thanks :)
[11:04] <jam> vila: I have a strong suspicion that our current Q is going to overflow for at least today.
[11:04] <vila> jam, jelmer: I suspect it's create_safety_net and the exception is caught
[11:04] <jam> 4*2.5 is already 10 hours
[11:04] <spiv> jam: If the Q overflows, I guess that makes it an R
[11:04] <jam> spiv: I'm pretty sure it becomes QQ
[11:05] <vila> jam: yeah, debugging a live pqm is not fun
[11:05] <vila> jam: which is why I postponed it :)
[11:05] <jam> spiv: from: http://www.urbandictionary.com/define.php?term=less%20qq%20more%20pew%20pew
[11:05] <spiv> jam: two Qs?  Too cute :P
[11:05] <jelmer> vila,jam: it's _create_safety_net (but that gets called by _check_safety_net)
[11:05] <jam> spiv: It symbolizes tears coming out of eyes
[11:06] <vila> jelmer: I don't think we reach that call
[11:06] <jam> vila: we do if it is failing
[11:06] <vila> jam: we get an AttributeError on _SAFETY_NET_PRISTINE_DIRSTATE so we don't reach it
[11:07] <jam> ah
[11:07] <jelmer> yeah, that's true
[11:07] <jelmer> because _create_safety_net raised an exception
[11:07]  * jelmer 's head spins
[11:07] <vila> jelmer: try commenting out create/check safety_net
[11:07] <vila> calls
[11:09] <vila> safety net and permit_url kind of overlap in both their implementations and intents, in your case, if you don't get failures with safety net outside of fakeroot, then it's probably safe to disable it
[11:09] <jelmer> yeah, that's fine (apart from a test isolation error because BzrDir browses up too far in the fs)
[11:09] <spiv> jam: QQ makes me think of pearl tea (http://en.wikipedia.org/wiki/Bubble_tea), there's a tea place I used to go to that lists the tapioca balls on the menu as QQ.
[11:09] <vila> "browses up too far in the fs" is a hard one
[11:10] <jelmer> vila: could we just temporarily monkey patch config_dir in _create_safety_net ?
[11:10] <jam> jelmer: http://paste.ubuntu.com/677891/
[11:10] <vila> pfew, to which value ?
[11:11] <vila> jam: that would make the test suite fails for jelmer, he is trying to get a successful run (or it could just not run it all otherwise)
[11:11] <vila> s/it could/he could/
[11:11] <jam> vila: well fix #1, if we can't set up, stop running the rest of the tests
[11:11] <jam> fix #2, make it so we can run
[11:12] <jelmer> jam: thanks, that would at least make it fail sensibly
[11:12] <vila> jam: right, that's what bug #825027 is about
[11:12] <jam> jelmer: I think there should be a better way, integrating it with our test suite runner, etc.
[11:12] <jelmer> vila: set BZR_HOME to e.g. TestCaseWithMemoryTransport.TEST_ROOT while we run create_standalone_workingtree
[11:13] <jelmer> vila: we don't care if that location doesn't exist
[11:13] <vila> jelmer: yup, should work
[11:13] <jam> jelmer: can you paste the actual traceback somewhere?
[11:16] <jelmer> jam: http://pastebin.ubuntu.com/677896/
[11:16] <jelmer> that's with a slight change to _check_safety_net to use getattr to get at _SAFETY_NET_PRISTINE_DIRSTATE
[11:16] <jam> jelmer: well, I would say that if config gets PermissionDenied, it should just accept it and treat it as though the file doesn't exist
[11:17] <jam> jelmer: by the time we get to _check* we should always have _SAFETY_NET set
[11:17]  * jelmer looks at vila
 alternatively we should catch permission denied and handle it as meaning we can't read the config files
[11:17] <jelmer> jam: Perhaps we should just warn ?
[11:17] <jam> jelmer: looking at the traceback you posted, it is clearly during "_make_test_root" not during "_check_safety_net"
[11:17] <jelmer> that works for me I guess
[11:18] <jam> jelmer: I could consider warning.
[11:18] <jelmer> jam: If I don't make that slight change to _check_safety_net then I get an attributeerror from _check_safety_net.
[11:18] <jam> jelmer: I'm thinking you're getting that after the previous failure, during tear-down time
[11:18] <jelmer> jam: yes, I am
[11:18] <jam> so setUp() fails, then we always run tearDown() and *it* fails
[11:19] <jelmer> jam: that attributeerror is a red herring, but that's why I mentioned _check_safety_net in that bug report
[11:19] <jam> sure
[11:19] <jelmer> cool
[11:34] <jam> jelmer: is bug #835183 actually fixeD?
[11:34] <jelmer> jam: not yet - the right packages are available from the daily PPA but not from the regular PPA
[11:34] <jam> jelmer: the bug at least claims to be the daily
[11:35] <jam> "bzr-svn from bzr-daily repo doesn't install with bzr  from the same repo"
[11:35] <jelmer> jam: in that case it might be a different one than I was thinking about
[11:35] <jam> which is why I'm confused that you saying "use the daily repo" and he claimed it was fixed
[11:36] <jelmer> jam: marked fixed, thanks for the pointer
[11:41] <jelmer> vila: https://code.launchpad.net/~jelmer/bzr/config-file-permdenied/+merge/73361
[11:57] <vila> jelmer: cough, configobj based configs doesn't have the issue and TransportConfig is not involved either in your case
[12:01] <vila> jelmer: the bug is that configobj uses os.path.isfile and doesn't see the permission denied while config.IniFileStore traps only NoSuchFile and should also catch permission denied
[12:08] <jelmer> vila: updated
[12:08] <jelmer> (and confirmed working against tracbzr)
[12:09] <grumbel> I have here a bzr repository (based on a svn repo) with some user created changes, I (the one with write access to the SVN) want to merge those changes back into the main svn repository. How would I do that?
[12:09] <jelmer> grumbel: if you have a checkout, it should just be a matter of running "bzr commit"
[12:10] <jelmer> grumbel: if you have a standalone branch that's derived from the svn branch, commit and push back
[12:19] <grumbel> jelmer: confusing part for me right now is that the bzr repository (not mine) is against anon-svn, while I would need to commit to the non-anon svn, which has a different URL
[12:20] <jelmer> grumbel: if the bzr branch is standalone it should just be a matter of pushing
[12:20] <jelmer> and specifying the non-anon URL to "bzr push"
[12:44] <vila> jelmer: BB:tweak, can you check that my tweak still works for tracbzr ?
[12:45] <vila> jelmer: finally, don't we want that for 2.4 ?
[12:55] <jelmer> vila: either works for me; I'll have to ship it as a Debian patch anyway. I'm not sure if it's big enough of an issue for other users.
[12:56] <vila> jelmer: wfm
[12:57] <vila> jelmer: and sorry for the trouble, I should have thought about bug #825027 earlier :-/
[12:58] <jelmer> vila: thanks for the review, I'll submit to PQM after John is done
[13:04] <jelmer> vila: no worries, it's pretty hard to recognize what it breaks without knowing the exact cause
[13:05] <vila> jelmer: where is fakeroot used in the whole bzr ecosystem ?
[13:06] <jelmer> vila: it's used by pretty much all debian packages when building
[13:06] <vila> jelmer: including ubuntu packages you mean ?
[13:06] <jelmer> vila: yep
[13:07] <vila> weird that we didn't encountered sooner...
[13:08] <jelmer> vila: it only happens if there actually is a /root directory - on most build hosts there isn't
[13:08] <vila> oh my...
[13:08] <vila> jelmer: and 'fakeroot -u' is not applicable ?
[13:09] <jelmer> nope
[13:09] <jelmer> vila: the idea is that when installing binaries they don't end up being owned by some random uid
[13:09] <vila> ok
[13:12] <vila> it's still weird to pretend to be root while not allowing to read config files though, but well, I can't see how to fix that anyway
[13:15] <vila> jelmer: ha, no, you mentioned the right fix earlier I think: force BZR_HOME to an existing place while creating the safety net, I'll add that to the brittle safety net bug
[13:25] <jelmer> vila: thanks!
[13:33] <jelmer> Speaking of weird FTBFS errors..
[13:33] <jelmer>   File "/usr/lib/python2.7/dist-packages/bzrlib/osutils.py", line 822, in compact_date
[13:33] <jelmer>     return time.strftime('%Y%m%d%H%M%S', time.gmtime(when))
[13:33] <jelmer> ValueError: timestamp out of range for platform time_t
[13:34] <vila> 8-(
[13:34] <jelmer> my thoughts exactly
[13:34] <jam> jelmer: clearly 'when' is negative?
[13:34] <jam> or a BIGINT
[13:34] <jam> I wonder if you need (time.gmtime(int(when))) or something
[13:35] <jelmer> jam: yeah, it's probably something like that
[13:35] <jam> the fact that it says out-of-range seems very strange
[13:36] <jelmer> it's also something that only occurs on the buildds
[13:36] <jelmer> anyway, I'll dig deeper
[13:37] <jelmer> it just seems like *somebody* forgot to tell me that today is weird FTBFS day.
[13:37] <jam> jelmer: didn't they just do an oneiric "rebuild" which causes everything to break?
[13:38] <jelmer> jam: yeah, but usually that just results in one or two plugin packages that happen to still call a method that has been removed from bzrlib
[13:38] <jam> jelmer: https://code.launchpad.net/~jelmer/bzr/move-hashcache/+merge/73299
[13:39] <jam> appears to be duplicating _write_hashcache_if_dirty
[13:39] <vila> jelmer: today is weird FTBFS day.
[13:39] <jam> anyway, not to distract you from what you're up to
[13:40] <jelmer> jam: it is - rather than using hashcache in the base class it makes WT2 and WT3 use it explicitly
[13:40] <jelmer> I could've made that clearer in the comments.
[13:41]  * jelmer adds a comment
[13:45] <jam> jelmer: is it possible to unify them, such as by just having a non-class attribute, or an extra base class. It is a real pain to track down and fix a bug in duplicated code.
[13:46] <jam> like NonDirstateWorkingTree or something
[13:46] <jelmer> jam: yeah, it's always a tradeoff I guess. I'd be happy to add a base class
[13:47] <jam> jelmer: I know it is old code that doesn't get touched much, but that's also why I'd like to not make it harder to support
[13:50] <vila> jam: that's what I was trying to convey when I asked you that follow-up about get_parent_map :)
[13:50] <jam> vila: except in my case there isn't code duplication, which is what I told you
[13:50] <jam> it isn't copy and paste code, it is take data from a different format and extract it for the api
[13:51] <vila> doesn't make the maintenance easier
[13:51] <jam> It is a "give me data" interface, but there isn't a simple corresponding "insert data" interface
[13:52] <vila> that's true
[13:53] <vila> but that can be addressed for the tests
[13:55] <vila> jelmer: do you have an easy way to test the build failure (without your patch for permission denied) ?
[13:55] <jelmer> vila: yeah
[13:56] <vila> jelmer: http://paste.ubuntu.com/677992/
[14:00] <vila> jelmer: bah, waitasec
[14:00] <jelmer> NoSuchFile: No such file: u'/tmp/testbzr-BmUC0T.tmp/.bzr/checkout/dirstate': [Errno 2] No such file or directory: u'/tmp/testbzr-BmUC0T.tmp/.bzr/checkout/dirstate'
[14:01] <vila> jelmer: http://paste.ubuntu.com/677995/ the previous one was blatently bogus
[14:01] <vila> or did you fix it yourself ?
[14:02] <jelmer> vila: "1". Really?
[14:02] <vila> for os.exit ? you prefer -1 ?
[14:03] <jelmer> vila: see that pastebin :)
[14:03] <vila> LOL
[14:03] <vila> pastebinit epic failure :)
[14:03] <vila> jelmer: http://paste.ubuntu.com/677998
[14:06] <jelmer> vila: that works
[14:07] <vila> ha, gooood, now, can I add tests for that...
[14:08] <vila> jelmer: just checking by "works" you mean the test pass not that we abort at the first one right ?
[14:15] <jelmer> vila: yep
[15:04] <vila> jelmer: speaking of weird cases, something happens in a try: tree.lock_write() /finally: tree.unlock() that leaves a broken lock, what can 'something' be ?
[15:09] <vila> jelmer: some failed imports can't be requeued without breaking these locks manually which is.. disruptive ;)
[15:09] <jelmer> vila: hmm, not sure either :/
[15:10] <vila> an unmatched lock/unlock ?
[15:10] <vila> unlikely
[15:11] <jelmer> could be, I guess
[15:11] <vila> and we get a traceback... so the finally clause should be obeyed...
[16:30] <lamalex> hi, so bzr status only showed 2 unknown files, so i can bzr add. and it added a fucking ton of other files. is there a sane way to remove them without losing all of the changes i had in my tree?
[16:34] <LeoNerd> bzr rm --keep path/to/file   will forget an 'add'
[16:45] <jelmer> lamalex: what kind of files did it add that "bzr status" didn't show?
[16:46] <lamalex> jelmer, build files
[16:46] <lamalex> can i bzr ignore build/ and have it disregard the add?
[16:47] <lamalex> ha oh LeoNerd bzr rm --keep worked great
[16:47] <jelmer> lamalex: yes, "bzr add" (without arguments) will ignore files that are in .bzrignore
[16:47] <jelmer> lamalex: if you explicitly specify files it will add them regardless of whether they are in .bzrignore
[16:48] <lamalex> yah
[16:48] <lamalex> thanks
[17:11] <lamalex> does anyone know of a good tutorial on bzr pipelines and bzr colo
[17:11] <lamalex> i keep finding myself in space where i think i would really benefit from the workflow
[17:11] <lamalex> but i can't find good docs about really how people use it
[17:12] <lamalex> thumper, ^ don't you use these things?
[19:16] <AuroraBorealis> is launchpadlibrarian slow as hell to anyone?
[19:16] <AuroraBorealis> im downloading at 2 kb/s
[19:24] <Quintasan> jelmer: http://paste.kde.org/116311 <-- any idea about that? recipe file: http://paste.kde.org/116317
[20:26] <thumper> lamalex: yes, I use pipelines
[21:54] <jelmer> Quintasan: sorry, was out. I'll have a look now
[22:17] <Quintasan> jelmer: Thanks
[22:21] <jelmer> Quintasan: can you run this: python -c 'from bzrlib.plugins.builder.cmds import get_maintainer; print get_maintainer()'
[22:21] <Quintasan> ('Micha\xc5\x82 Zaj\xc4\x85c'<EMAIL_ADDRESS>[22:22] <jelmer> Quintasan: bzr-builder needs to be calling .decode on that since python-debian (now?) uses unicode for changelogs
[22:22] <jelmer> Quintasan: can you file a bug?
[22:24] <Quintasan> jelmer: against bzr?
[22:24] <jelmer> Quintasan: against bzr-builder
[22:28] <Quintasan> jelmer: https://bugs.launchpad.net/bzr-builder/+bug/837741
[22:28] <jelmer> Quintasan: thanks
[22:28]  * jelmer wished he could triage bugs from IRC
[22:29] <jelmer> Quintasan: setting DEBFULLNAME to something that only includes ascii characters should work around it for hte moment
[23:53] <poolie> hi all


[00:24] <Ubulette> asac, i've tried to port the lcd subpixel patch for the cairo lib bundled in ff3 (for bug 164640). i've merged a part manually but it needs some work in the build system, mostly freetype2 stuff.
[00:24] <ubotu> Launchpad bug 164640 in firefox-3.0 "Apply subpixel rendering patch to cairo" [Undecided,New] https://launchpad.net/bugs/164640
[00:26] <Ubulette> that's a lot of changes in the code. I don't think it's wise to do that now.
[00:28] <asac> well ... that patch should be send upstream. If upstream doesn't do anything we won't be able to run system-cairo
[00:28] <asac> (upstreawm as in cairo upstream)
[00:29] <asac> so ... if its needed for mozilla we better get it in ;)
[00:29] <asac> or get something else that mozilla can use
[00:29] <asac> Ubulette: b1 doesn't yet contain the gnome depends, right?
[00:29] <Ubulette> the new icons ? no
[00:30] <Ubulette> it's a b2pre stuff
[00:30] <Ubulette> asac, should I close both changelogs ?
[00:31] <Ubulette> I wanted to push the cairo patch in as the user insisted it's trivial. it isn't so let's close with what we have and move on
[00:32] <asac> do we know a cairo bug id?
[00:40] <Ubulette> asac, no. Scott James Remnant (do you know him?) did the integration into ubuntu's cairo. seems it's based on David Turner's patches
[00:41] <asac> Ubulette: yes i know scott
[00:43] <asac> Ubulette:
[00:43] <asac> +
[00:43] <asac> +debian/debsearch.gif usr/share/firefox-addons/searchplugins
[00:43] <asac> +debian/debsearch.src usr/share/firefox-addons/searchplugins
[00:43] <asac> +
[00:43] <asac> +debian/wikipedia.gif usr/share/firefox-addons/searchplugins
[00:43] <asac> +debian/wikipedia.src usr/share/firefox-addons/searchplugins
[00:44] <asac> we don't have five-home anymore?
[00:44] <Ubulette> seems it's not useful
[00:45] <Ubulette> the default is fine
[00:45] <Ubulette> far better than using an empty one ;)
[00:45] <Ubulette> or a broken one
[00:46] <asac> yeah
[00:46] <asac> anyway the searchplugin thing above looks wrong
[00:47] <Ubulette> why ?
[00:48] <Ubulette> oh damn, the link is wrong
[00:48] <asac> he?
[00:48] <asac> i mean you still use share there
[00:48] <asac> not lib
[00:49] <Ubulette> that's expected. that's the shared -addons like xul
[00:49] <asac> why do we need LIBDIR in firefox.sh
[00:49] <Ubulette> last line
[00:49] <asac> shared?
[00:50] <asac> what do you mean?
[00:50] <Ubulette> well, not shared but stable
[00:50] <Ubulette> if any package wants to add a search plugin for ff, it uses that
[00:50] <Ubulette> no ?
[00:50] <asac> and the usr/lib/firefox-addons/searchplugins dir contains what compared to the shared one?
[00:51] <Ubulette> i've made a mistake
[00:51] <Ubulette> fixing it
[00:51] <asac> yeah :)
[00:51] <asac> they go to usr/lib/firefox-addons, right?
[00:52] <Ubulette> yeah
[00:52] <asac> feel free to add a link from there to share ;)
[00:52] <asac> but i thought this change was about eliminating that ;)
[00:53] <asac> i just wonder why you do things like introducing DEBIAN_NAME in the same commit as all the versioned dir things
[00:55] <Ubulette> i should have done that long ago. I had to dig to see what was the package name and what was the hard path
[00:55] <Ubulette> now it's clear
[00:57] <asac> looks good from just looking at last commit
[00:57] <asac> but its intrusive enough for me to try :)
[01:00] <Ubulette> yep, sure
[01:00] <Ubulette> http://paste.ubuntu.com/2228/
[01:01] <asac> right
[01:01] <asac> does ffox with system xul install anything in /etc/gre.d?
[01:01] <asac> (i don't think nor hope so) :)
[01:02] <Ubulette> no
[01:03] <Ubulette> hmm, looks like xul is leaking a file though. http://paste.ubuntu.com/2229/
[01:04] <Ubulette> strange dpkg does not complain about it
[01:05] <asac> Ubulette: purging doesn't remove it?
[01:29] <Ubulette> how ? i don't want to remove xul
[04:17]  * Hobbsee wonders if bugzilla accounts for the mozilla  bugtracker expire.
[04:21] <Hobbsee> nope, it appears they don't.  good.
[04:27] <[reed]> they don't :)
[04:28] <[reed]> they exist forever :)
[04:32] <Hobbsee> neat
[04:32] <Hobbsee> oh goody, bug is here, and i've been able to narrow it down
[04:34] <Hobbsee> https://bugzilla.mozilla.org/show_bug.cgi?id=315416
[04:34] <ubotu> Mozilla bug 315416 in Password Manager "Passwords reappear after being deleted, some can never be deleted" [Normal,Resolved: incomplete]
[04:35] <Hobbsee> now...how do i reopen it?
[09:28] <salty-horse> hi. I installed the adobe flash plugin + nspluginwrapper through the plugin finder. it prompted for the root password 3 times. can it be reduced to 1?
[09:35] <asac> salty-horse: for me its only one time
[09:35] <salty-horse> did you uninstall both first?
[09:36] <asac> yes
[09:36] <asac> well ... not today ... but i certainly did it before ;)
[09:36] <salty-horse> on amd64?
[09:37] <asac> yes
[09:37] <salty-horse> let me try again
[09:42] <salty-horse> it asks once for the "add/remove" app, and twice for synaptic
[09:42] <salty-horse> I recorded a video
[09:50] <asac> salty-horse: gnome session?
[09:50] <salty-horse> yes
[09:53] <[reed]> asac: think you can get around to reviewing mozilla bug 319965 soon?
[09:54] <asac> no idea ... gksudo shouldn't ask you twice
[09:54] <ubotu> Mozilla bug 319965 in X-remote "Dual-monitors, FF opens in one or the other, not both." [Major,New] http://bugzilla.mozilla.org/show_bug.cgi?id=319965
[09:55] <salty-horse> maybe it's because gksudo is launched multiple times?
[10:06] <asac> [reed]: yes ... I just returned from holidays :) and a security update is waiting for me :) ...
[10:06] <[reed]> asac: ah, k
[10:07] <[reed]> yes, <IP_ADDRESS> is coming out today
[10:07] <[reed]> I think
[10:07] <[reed]> today or tomorrow
[10:07] <[reed]> who knows
[10:07] <asac> [reed]: the patch makes sense to me ... would like to look into the code surrounding this though.
[10:07] <[reed]> cool
[10:09] <asac> salty-horse: usually not ... I can run gksudo echo hello multiple times ... only the first time i get ask for password
[10:09] <salty-horse> hmm.. trying another app
[10:10] <salty-horse> oh. I think I got it. I changed the sudo timeout to 0
[10:10] <asac> salty-horse: yeah :)
[10:10] <salty-horse> still, is it possible to have the plugin finder call gksudo just once?
[10:10] <asac> the plugin finder calls it just once
[10:11] <asac> its the synaptic thing apparently that does this
[10:11] <salty-horse> so add/remove calls synaptic twice
[10:11] <asac> file a bug against apturl
[10:11] <asac> ?
[10:11] <asac> why add/remove? i thought you are installing using the plugin finder wizard
[10:12] <salty-horse> this is what I get in the password prompts:
[10:13] <salty-horse> 1) "Add/Remove..." 2+3) "Synaptic Package Manager"
[10:15] <asac> salty-horse: how do you instlal the plugins?
[10:16] <salty-horse> via the plugin wizard.
[10:16] <asac> and how is add/remove ... involved? afaik there is just "install" in the plugin finder wizard
[10:20] <salty-horse> the plugin wizard lists the available gnash and adobe plugin. after choosing the adobe one and clicking "next", I get a new dialog asking if I want to install the package 'flashplugin-nonfree'. answering yes prompts for a password (requested by the "add/remove" app). after typing it in, I get two more password prompts requested by synaptic
[10:21] <asac> ah ok ... yes, then file a bug against apturl
[10:21] <asac> the maintainer should reassign it appropriately
[10:21] <salty-horse> ok
[10:21] <asac> no idea if its easy to fix though. i think its easiest to use a timeout of > 0
[10:21] <asac> :)
[10:22] <salty-horse> it's insecure, IMO. even with just me by the computer, I want to be asked when doing potentially damaging things :)
[10:23] <asac> salty-horse: yeah ... i think its a valid concern ... post a bug :)
[10:23] <asac> and keep me updated ;)
[10:31] <salty-horse> https://bugs.launchpad.net/ubuntu/+source/apturl/+bug/165147
[10:31] <ubotu> Launchpad bug 165147 in apturl "numerous password prompts when using plugin finder" [Undecided,New]
[10:43] <asac> salty-horse: commented
[10:53] <salty-horse> thanks
[11:58] <armin76> asac: Ubulette: https://bugzilla.mozilla.org/show_bug.cgi?id=405424
[11:58] <ubotu> Mozilla bug 405424 in XPCOM "Updates for Linux/ia64" [Normal,Unconfirmed]
[12:07] <asac> armin76: ok i will confirm
[12:10] <asac> [reed]: who to ask for ia64 review? (mozilla bug 405424)
[12:10] <ubotu> Mozilla bug 405424 in XPCOM "Updates for Linux/ia64" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=405424
[12:18]  * asac lunch
[12:55] <asac> shaky freenode today :/
[16:08] <armin76> [reed]: why did you assign me the bug?
[17:18] <armin76> asac: Ubulette: is the ppc/powerppc in md/unix/Makefile a known issue?
[17:20] <armin76> i mean, is there a bug upstream?
[17:31] <asac> armin76: is it the same for gentoo?
[17:31] <armin76> yup
[17:31] <armin76> target_cpu is from the toolchain, and the toolchain in ppc is powerpc, not ppc
[17:32] <armin76> i think it's a regression of bug 372428
[17:32] <armin76> mozilla bug 372428
[17:32] <ubotu> Mozilla bug 372428 in Build Config "firefox configure.in does not work currently with a 64 bit kernel and a full 32 bit userland" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=372428
[17:44] <bluekuja> asac, heya alex
[17:45] <bluekuja> asac, had a chance to build the package?
[17:45] <bluekuja> asac, just finished to study....I can call them 11 hours
[17:45] <bluekuja> today :/
[17:48] <asac> armin76: yes ... but will it reregress?
[17:48] <asac> bluekuja: i think i built it yesterday ... but didn't come to anything else afaik
[17:49] <asac> completely forgot since it was late
[17:49] <bluekuja> asac, that means it did *not* FTBFS?
[17:49] <asac> no idea either
[17:49] <asac> never looked at that terminal
[17:49] <bluekuja> ah damn
[17:49] <bluekuja> :/
[17:50] <bluekuja> are you able to retry?
[17:51] <asac> bluekuja: 0.2.3-3~ppa1 builds in sid
[17:51] <bluekuja> asac, mmm...
[17:51] <bluekuja> crazy then
[17:51] <bluekuja> WTH it fails on Debian build machines then=
[17:52] <asac> bluekuja: missing depends?
[17:52] <asac> i don't use pbuilder so i wont catch those
[17:52] <bluekuja> asac, impossible...it fails on using gconf
[17:53] <bluekuja> and works in some archs
[17:53] <bluekuja> but fails on amd64
[17:53] <bluekuja> and one-two more
[17:53] <asac> build machine broken then i guess
[17:53] <bluekuja> yep
[17:53] <bluekuja> is give-back possible in Debian?
[17:56] <bluekuja> asac: http://buildd.debian.org/fetch.cgi?&pkg=diff-ext&ver=0.2.3-2&arch=amd64&stamp=1195237138&file=log
[17:58] <bluekuja> this is the FTBFS on adm64
[17:59] <asac> GCONF_CONFIG_SOURCE=xml:readwrite:/home/buildd/.gconf /usr/bin/gconftool-2 --makefile-install-rule diff-ext.schemas
[17:59] <asac> (gconftool-2:19515): GConf-WARNING **: Failed to load source "xml:readwrite:/home/buildd/.gconf": Failed: Could not make directory `/home/buildd/.gconf': No such file or directory
[17:59] <asac> GConf-ERROR **: file gconftool.c: line 918 (main): assertion failed: (err == NULL)
[17:59] <bluekuja> yes
[17:59] <asac> aborting...
[17:59] <asac> the buildd has not writable home apparently
[17:59] <asac> the build shouldn't rely on that
[17:59] <asac> fix that :)
[18:00] <bluekuja> actually there is a work-around for this
[18:00] <bluekuja> I can just move schemas installation
[18:00] <bluekuja> after make-install
[18:00] <bluekuja> and not before
[18:00] <bluekuja> maybe in a postinst file
[18:00] <bluekuja> that will fix this issue actually
[18:01] <bluekuja> because schemas will be installed not during build
[18:01] <bluekuja> but after
[18:01] <bluekuja> that's suggested from gconf itself
[18:02] <bluekuja> too
[18:02] <bluekuja> cool :)
[18:02] <asac> look how other software deals with schema and fix the build system i would say
[18:02] <bluekuja> actually I have to follow gconf policy
[18:02] <bluekuja> that suggests to install schemas *after* the build
[18:02] <bluekuja> and not during make install
[18:02] <bluekuja> (which is our case)
[18:03] <asac> so you patch the Makefile.am ?
[18:03] <bluekuja> asac, yep
[18:03] <asac> anyway, do whatever is necessary to fix this and let me know :)
[18:03] <asac> i will be out for a while
[18:03] <asac> will come back later
[18:04] <bluekuja> asac, perfect mate :)
[18:05] <bluekuja> asac, having no testing machines to test this sux!
[18:05] <bluekuja> :)
[18:05] <asac> bluekuja: he?
[18:06] <asac> just make your home not-writable
[18:06] <bluekuja> mm...is it possible on pbuilder too?
[18:06] <bluekuja> *without* logging in
[18:06] <asac> its nothing amd specific
[18:07] <bluekuja> I'll have to work on logging inside a pbuilder
[18:07] <bluekuja> I think it's not possible to make my home not-writable
[18:07] <bluekuja> in the tarball
[18:07] <bluekuja> itself
[18:14] <asac> bluekuja: build without pbuilder
[18:14] <bluekuja> asac, yep
[18:14] <bluekuja> or I can log inside it as well
[18:14] <bluekuja> so I have a clean chroot
[18:16] <bluekuja> ok, home dir not-writable now
[18:16] <bluekuja> test-building
[18:19] <bluekuja> ok, it fails
[18:20] <bluekuja> now let's make the fix
[19:00] <bluekuja> asac, fix ready to go
[19:03] <bluekuja> asac, patching makefiles wasnt necessary
[19:03] <bluekuja> I used a configure rule to disable schemas installation ;)
[19:03] <Ubulette> hi
[19:04] <bluekuja> Ubulette, heya
[19:05] <armin76> asac: re: reregression, no, it won't, actually it's broken
[19:06] <bluekuja> Ubulette, are you good wirh schemas? (gconf)
[19:06] <bluekuja> *with
[19:06] <Ubulette> depends
[19:06] <Ubulette> fixing or writing ?
[19:07] <bluekuja> just for an hint
[19:07] <asac> bluekuja: ok if thats common practice go ahead
[19:07] <bluekuja> Ubulette, does gconf-schemas works fine for installing schemas?
[19:07] <bluekuja> instead of using gconftool-2
[19:07] <asac> bluekuja: why don't you test
[19:07] <asac> ?
[19:08] <asac> the installed schemas should be visible in gconf-editor
[19:08] <bluekuja> right
[19:08] <bluekuja> let me see
[19:09] <asac> Ubulette: i fixed the url classifier thingy
[19:09] <asac> Ubulette: now i see more issues :/
[19:09] <asac> what issues have you been talking about?
[19:09] <asac> (you talked about some issues with b2pre, didn't you)?
[19:10] <Ubulette> give me half an hour. we'll discuss that
[19:10] <asac> Ubulette: ok
[19:10] <bluekuja> asac, plus lintian complains about using gconftool-2
[19:10] <bluekuja> in a maintainer script
[19:11] <bluekuja> and it suggests gconf-schemas instead
[19:11] <bluekuja> ^^
[19:11] <asac> bluekuja: there should be a policy document in debian somewhere
[19:11] <asac> don't ask me where
[19:12] <bluekuja> asac, anyway yes, using gconftool-2
[19:12] <bluekuja> and gconf-schemas is the same
[19:12] <bluekuja> schemas gets installed correctly
[19:12] <bluekuja> so it should be fine to disable the installation of schemas via a rule
[19:12] <bluekuja> and it will fix the FTBFS
[19:13] <bluekuja> asac, updating the branch
[19:13] <bluekuja> asac, are you able to check/upload that today?
[19:13] <bluekuja> gonna give you branch links when done in a while
[19:13] <asac> to debian? i would like to try ;)
[19:14] <bluekuja> yes, to Debian :)
[19:14] <bluekuja> perfect
[19:14] <bluekuja> give me some minutes
[19:14] <bluekuja> updating
[19:34] <Ubulette> back
[19:34] <[reed]> armin76: we assign bugs to the person who writes the patch
[19:34] <[reed]> you wrote the patch
[19:34] <[reed]> so, the bug is assigned to you
[19:38] <Ubulette> asac, so what did you do with url classifier ?
[19:38] <armin76> [reed]: oh, sorry then
[19:48] <bluekuja> asac, done
[19:49] <bluekuja> asac, back
[19:49] <bluekuja> asac, branch is ready
[19:49] <bluekuja> asac, let me upload you the tarball
[19:50] <bluekuja> asac, or you prefer the upstream branch?
[19:50] <Ubulette> bluekuja, seems most package install those schemas manually
[19:50] <bluekuja> Ubulette, yep
[19:50] <bluekuja> postinst handle that
[19:50] <bluekuja> with gconf-schemas
[19:51] <Ubulette> http://paste.ubuntu.com/2261/  here is file-roller
[19:51] <bluekuja> Ubulette, yes, they stop installing schemas on build
[19:51] <bluekuja> that's right
[19:51] <bluekuja> I've used --disable-schemas-install configure variable
[19:51] <bluekuja> for that
[19:52] <bluekuja> so I don't have to hack makefiles using autotools
[19:52] <asac> bluekuja: why do i need a new tarball? i already have one ;)
[19:52] <bluekuja> ah fine :)
[19:52] <bluekuja> asac: bzr branch http://bazaar.launchpad.net/~bluekuja/diff-ext/debian.source
[20:08] <asac> bluekuja: i won't verify that it really works ... just upload
[20:08] <bluekuja> asac, actually I just deleted the FTBFS cause
[20:08] <bluekuja> and schemas are still registered
[20:08] <bluekuja> with postinst
[20:08] <bluekuja> but not on build run
[20:08] <bluekuja> ;)
[20:09] <asac> bluekuja: the orig is already in debian?
[20:09] <bluekuja> asac, yes, let me grab you the link
[20:10] <bluekuja> asac, http://ftp.de.debian.org/debian/pool/main/d/diff-ext/diff-ext_0.2.3.orig.tar.gz
[20:10] <asac> bluekuja: tell me md5sum please
[20:10] <bluekuja> yes, just a sec
[20:11] <asac> 8a82a8c76f1bd30cb3ee7dd8c270aab7 ?
[20:11] <bluekuja> asac, 8a82a8c76f1bd30cb3ee7dd8c270aab7
[20:11] <asac> yes
[20:11] <bluekuja> yep, that's it
[20:11] <asac> so lets see ;)
[20:11] <asac> uploaded
[20:11] <asac> i will look in an hour ;)
[20:11] <asac> lets hope
[20:11] <bluekuja> gonna ping you
[20:12] <bluekuja> when I see accepted
[20:12] <bluekuja> (hopefully=
[20:12] <bluekuja> *)
[20:12] <bluekuja> I really hope your key problem is fixed
[20:12] <bluekuja> :)
[20:13] <[reed]> ams is so stupid
[20:13] <[reed]> if any of you all know him
[20:13] <bluekuja> mmm...nope, never heard
[20:14] <[reed]> ah, then you're lucky
[20:14] <bluekuja> who is he?
[20:14] <bluekuja> and which channel?
[20:14] <[reed]> he's a GNU Hurd developer
[20:14] <[reed]> that should explain it all
[20:14] <[reed]> :p
[20:14] <bluekuja> lol
[20:15] <bluekuja> [reed], have you ever tried to browse live spaces?
[20:16] <bluekuja> for msn
[20:16] <[reed]> no, I don't patronize Microsoft sites
[20:16] <[reed]> :P
[20:16] <[reed]> but I remember a bug on that
[20:16] <bluekuja> same here
[20:16] <bluekuja> but I'm just watching some cool photos
[20:16] <bluekuja> of a friend
[20:16] <bluekuja> (female)
[20:16] <bluekuja> :P
[20:16] <bluekuja> and I'm getting crazy
[20:17] <bluekuja> 1-2 minutes to download a damn image
[20:17] <bluekuja> too slow website
[20:17] <bluekuja> damn it
[20:18] <[reed]> mozilla bug 403481 has a reviewed patch, at least
[20:18] <[reed]> it should get committed today
[20:18] <ubotu> Mozilla bug 403481 in GFX: Thebes "minefield memory usage keeps growing as png images are dynamically loaded (maps.google.com)" [Major,Assigned] http://bugzilla.mozilla.org/show_bug.cgi?id=403481
[20:19] <bluekuja> it simply doesn't load the page
[20:19] <bluekuja> : /
[20:40] <bluekuja> asac, no mails yet
[20:40] <bluekuja> bad sign
[20:41] <bluekuja> asac, we should receive a REJECTED mail anyway, I guess
[20:42] <Ubulette> i'm fighting with prism
[20:42] <bluekuja> gonna win?
[20:43] <Ubulette> persia wants my get-orig-source to look less shellish, more makefileish ;)
[20:43] <bluekuja> ^^
[20:45] <Ubulette> sure i'll win but if we ask him to review any of our moz package, we'd better trash our rules file and start from scratch
[20:45] <bluekuja> lol
[20:46] <bluekuja> is it NEW?
[20:46] <Ubulette> it will
[20:46] <bluekuja> yes, but is it a new package?
[20:46] <bluekuja> e.g not the in the archive yet?
[20:46] <Ubulette> yes
[20:46] <bluekuja> ah ok
[20:46] <bluekuja> so on REVU
[20:46] <Ubulette> yes
[20:59] <bluekuja> asac, still nothing... :/
[20:59] <bluekuja> I think dak won't send a rejected mail
[20:59] <bluekuja> don't know why
[20:59] <bluekuja> but that's strange
[21:07] <asac> well its not a bug ... its a security feature i guess
[21:38] <Ubulette> asac, with http://paste.ubuntu.com/2267/  persia seems happier :)
[21:39] <bluekuja> asac, found duplicate status token ('KEYEXPIRED').
[21:39] <bluekuja> Rejected: internal error while performing signature check on diff-ext_0.2.3-3_amd64.changes.
[23:31] <Ubulette> asac, if we don't ship xul soon, i'll have to ship dom inspector with prism instead of just a link
[23:36] <asac> Ubulette: yes ... will happen tomorrow .. tuning the patch one more time ... will commmit in 30 minutes or so ... then you can take a look
[23:36] <asac> and close et al
[23:36] <Ubulette> ok
[23:39] <asac> why did we switch to slow diff.gz approach for xulrunner again? :) ?
[23:39] <Ubulette> eh?
[23:39] <asac> nm
[23:39] <asac> i should get some speedy disks i guess
[23:40] <Ubulette> yes
[23:40] <Ubulette> you do that :)
[23:43] <Ubulette> I can't do more than that http://paste.ubuntu.com/2276/
[23:47] <asac> Ubulette: do you still install all prism apps in Internet menu?
[23:48] <Ubulette> yes
[23:48] <Ubulette> only this default set
[23:48] <asac> i think it would be better to put the applications in the proper menu
[23:48] <asac> e.g. office => office et al
[23:49] <Ubulette> it is supposed to be integrated to the desktop, not split
[23:49] <asac> yes
[23:49] <asac> but that would mean to put google calendar in office
[23:49] <asac> not internet
[23:57] <Ubulette> that would mean adding more logic to the rules
[23:57] <Ubulette> not difficult but i'd like to get this one in
[23:58] <asac> y