[00:00] <infinity> rbasak: Anyhow, I'm not a huge stickler about it.  The "correct" (whether you believe correct is the upload history or source history) version is obtainable out of band either way.
[00:00] <infinity> rbasak: But it's also way less work for a pure backport to do it my way. ;)
[00:01] <infinity> (Since doing it the other way implies a lot more changelog futzing)
[00:15] <infinity> rbasak: Of course, with the wonderful events in 2016 in the UK and the US, I imagine we'll be doing uploads via signal fires and semaphore soon, so maybe arguing over changelog formats isn't that dire.
[00:17] <sarnold> we're just building a wall to keep the foreign packets from taking the jobs of hardworking native packets. we're going to get the foreign packets to pay for it.
[00:20] <valorie> lol
[00:31] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (trusty-proposed) [1:2014.1.5-0ubuntu7]
[01:50] -queuebot:#ubuntu-release- Unapproved: snapcraft (yakkety-proposed/universe) [2.21+16.10 => 2.22+16.10] (no packageset)
[02:16] <sergiusens> rbasak or slangasek mind letting snapcraft into yakkety-proposed and xenial-proposed?
[02:17] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.21 => 2.22] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: goopg [amd64] (zesty-proposed/universe) [0.3.1-3] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: patat [amd64] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: patat [i386] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: yuma123 [amd64] (zesty-proposed/universe) [2.9-1] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: yuma123 [ppc64el] (zesty-proposed/universe) [2.9-1] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: yuma123 [i386] (zesty-proposed/universe) [2.9-1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: yuma123 [s390x] (zesty-proposed/universe) [2.9-1] (no packageset)
[05:27] -queuebot:#ubuntu-release- New binary: patat [armhf] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[05:27] -queuebot:#ubuntu-release- New binary: patat [powerpc] (zesty-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: yuma123 [arm64] (zesty-proposed/universe) [2.9-1] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: yuma123 [powerpc] (zesty-proposed/universe) [2.9-1] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: yuma123 [armhf] (zesty-proposed/universe) [2.9-1] (no packageset)
[08:49] <josvaz> bdmurray, could you take a look at this xenial change waiting to be approved into purposed?
[08:49] <josvaz> bdmurray: http://launchpadlibrarian.net/292538218/walinuxagent_2.1.5-0ubuntu4~16.04.0_source.changes
[08:50] <josvaz> I pinged rbasak yesterday and he requested a more detailed test plan, which we wrote down here: https://wiki.ubuntu.com/walinuxagentUpdates
[08:50] <josvaz> bdmurray: and this is the bug https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1603581
[08:50] <ubot5`> Ubuntu bug 1603581 in walinuxagent (Ubuntu Xenial) "Azure Linux Agent (WALA) 2.1.5 Released" [Wishlist,In progress]
[09:09] <rbasak> josvaz: sorry I ran out of time to finish looking at that yesterday. I'll take a look this morning.
[09:17] <rbasak> josvaz: on the wiki page, shouldn't the "QA Process" bullets be part of the SRU Test Cases section?
[09:17] <rbasak> But if you're planning to do both sections, then that's perfect, thanks.
[09:19] <josvaz> The SRU Test cases section is the minimal tests we do before the the SRU process and automated tests
[09:20] <rbasak> OK
[09:20] <rbasak> Would you mind making it clear which part is followed for SRU verification purposes please?
[09:21] <rbasak> Maybe replace "QA Process" with "SRU Verification Process"?
[09:21] <josvaz> ok
[09:21] <rbasak> And "SRU Test Cases" with "SRU Test Cases Prior to Upload" or something? Otherwise "SRU Test Cases" sounds like they're the ones you will follow for SRU verification.
[09:23] -queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (xenial-proposed) [2.1.5-0ubuntu4~16.04.0]
[09:25] <josvaz> on it
[09:27] <josvaz> re-reading the SRU Test Cases text (prepared by Dan) mention using -purposed packages, which needs to happen AFTER we get to purposed, but we already kind of this this testing BEFORE getting tu purposed
[09:27] <josvaz> as mentioned in the first bullet of SRU Verification process
[09:27] <josvaz> needs some clarification, will have it shortly
[09:27] <rbasak> SRU Test Cases as you wrote them seemed to be a copy of what you did before.
[09:28] <rbasak> So maybe they need modifying?
[09:29] <rbasak> I appreciate you do some testing beforehand, but my concern here is the testing you do specifically for SRU verification from -proposed. I'd like it to be clear which section that is, and for that to include the testing we talked about yesterday and that you documented in "QA Process". As the page was written a few minutes ago, I felt there was some confusion as to which section that is.
[09:30] <rbasak> The "QA Process" is exactly what I was looking for - thank you. I just want to make it clearly documented that this section is what will be followed for SRU verification purposes - for example if a new person joins your team and is pointed to the page generally, that person will know what to do.
[09:30] <rbasak> (or at least, which steps need carrying out)
[09:33] <rbasak> josvaz: fyi, I've already accepted the package into -proposed.
[09:34] <josvaz> thanks rbasak, understood
[09:41] <josvaz> rbasak: I am working now on making the wiki more clear
[10:01] <josvaz> rbasak: I updated https://wiki.ubuntu.com/walinuxagentUpdates I believe now is more clear
[10:17] <rbasak> josvaz: that's great. Thanks!
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (yakkety-proposed) [2.22+16.10]
[10:40] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (xenial-proposed) [2.22]
[10:41] -queuebot:#ubuntu-release- Unapproved: accepted samba [source] (xenial-proposed) [2:4.3.11+dfsg-0ubuntu<IP_ADDRESS>]
[10:42] <pitti> I've emptied the yakkety queue and am now attacking xenial; but can someone else please review nplan? (that's my upload)
[10:42] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (xenial-proposed) [1:16.04.18]
[10:44] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (xenial-proposed) [2:8.3.0-0ubuntu1.1]
[10:45] -queuebot:#ubuntu-release- Unapproved: rejected python-os-brick [source] (xenial-proposed) [1.2.0-3]
[10:46] -queuebot:#ubuntu-release- Unapproved: accepted multipath-tools [source] (xenial-proposed) [0.5.0+git1.656f8865-5ubuntu2.3]
[10:46] -queuebot:#ubuntu-release- Unapproved: rejected dovecot [source] (xenial-proposed) [1:2.2.22-1ubuntu2.2]
[10:47] -queuebot:#ubuntu-release- Unapproved: accepted python-os-brick [source] (xenial-proposed) [1.2.0-2ubuntu0.1]
[10:48] -queuebot:#ubuntu-release- Unapproved: accepted cups-filters [source] (xenial-proposed) [1.8.3-2ubuntu3.2]
[10:49] <pitti> apw: ^ maybe you have a minute (nplan)
[10:49] -queuebot:#ubuntu-release- Unapproved: accepted playonlinux [source] (xenial-proposed) [4.2.10-2ubuntu0.1]
[10:50] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (xenial-proposed) [0.90ubuntu0.2]
[10:52] -queuebot:#ubuntu-release- Unapproved: accepted python-pip [source] (xenial-proposed) [8.1.1-2ubuntu0.4]
[10:53] -queuebot:#ubuntu-release- Unapproved: accepted maas [source] (xenial-proposed) [2.1.1+bzr5544-0ubuntu1~16.04.1]
[10:54] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (xenial-proposed) [0.9+1474479173.6c180c6-0ubuntu1]
[10:55] -queuebot:#ubuntu-release- Unapproved: accepted ido [sync] (xenial-proposed) [13.10.0+16.04.20161028-0ubuntu1]
[10:55] <pitti> ok, the remainder of the queue is blocked by previous SRUs in -proposed, except nplan
[10:57] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (trusty-proposed) [0.9+1474479173.6c180c6-0ubuntu1]
[11:03] -queuebot:#ubuntu-release- Unapproved: accepted samba [source] (trusty-proposed) [2:4.3.11+dfsg-0ubuntu<IP_ADDRESS>]
[11:03] -queuebot:#ubuntu-release- Unapproved: rejected unscd [source] (trusty-updates) [0.51-1ubuntu1]
[11:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (trusty-proposed) [2.02~beta2-9ubuntu1.13]
[11:05] <pitti> trusty is now in the same boat; empty except shim-signed which is blocked by previous SRU
[11:05] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (trusty-proposed) [1.34.15]
[11:06] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (precise-proposed) [0.9+1474479173.6c180c6-0ubuntu1]
[11:06] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (precise-proposed) [1.19~12.04.1]
[11:06] -queuebot:#ubuntu-release- Unapproved: xserver-xorg-video-intel (xenial-proposed/main) [2:2.99.917+git20160325-1ubuntu1.1 => 2:2.99.917+git20160325-1ubuntu1.2] (desktop-core, xorg)
[11:09] -queuebot:#ubuntu-release- Unapproved: unscd (trusty-proposed/universe) [0.51-1build2 => 0.51-1ubuntu1] (no packageset)
[11:16] <marcustomlinson> xnox: ping
[11:16] <xnox> marcustomlinson, hello
[11:16] <marcustomlinson> xnox: hi! So I see libboost-python1.62 update fixed my build failures.
[11:16] <marcustomlinson> xnox: but I'm seeing more symbol issues not in autopkg tests
[11:16] <marcustomlinson> xnox: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-2110-excuses/2016-11-10_09:35:01/2110.1_zesty_excuses.html
[11:17] <marcustomlinson> /s/not/now
[11:18] <xnox> marcustomlinson, thank you for pointing this out, indeed looks b0rked still.
[11:19] <marcustomlinson> xnox: thanks for the help :)
[11:31] -queuebot:#ubuntu-release- Unapproved: grub2 (trusty-proposed/main) [2.02~beta2-9ubuntu1.13 => 2.02~beta2-9ubuntu1.13] (core)
[12:29] -queuebot:#ubuntu-release- New: accepted django-html-sanitizer [amd64] (zesty-proposed) [0.1.5-1]
[12:29] -queuebot:#ubuntu-release- New: accepted gnuastro [arm64] (zesty-proposed) [0.2.33-1]
[12:29] -queuebot:#ubuntu-release- New: accepted gnuastro [i386] (zesty-proposed) [0.2.33-1]
[12:29] -queuebot:#ubuntu-release- New: accepted gnuastro [s390x] (zesty-proposed) [0.2.33-1]
[12:29] -queuebot:#ubuntu-release- New: accepted goopg [amd64] (zesty-proposed) [0.3.1-3]
[12:29] -queuebot:#ubuntu-release- New: accepted patat [i386] (zesty-proposed) [<IP_ADDRESS>-1]
[12:29] -queuebot:#ubuntu-release- New: accepted gnuastro [amd64] (zesty-proposed) [0.2.33-1]
[12:29] -queuebot:#ubuntu-release- New: accepted gnuastro [powerpc] (zesty-proposed) [0.2.33-1]
[12:29] -queuebot:#ubuntu-release- New: accepted patat [armhf] (zesty-proposed) [<IP_ADDRESS>-1]
[12:29] -queuebot:#ubuntu-release- New: accepted gnuastro [armhf] (zesty-proposed) [0.2.33-1]
[12:29] -queuebot:#ubuntu-release- New: accepted patat [powerpc] (zesty-proposed) [<IP_ADDRESS>-1]
[12:29] -queuebot:#ubuntu-release- New: accepted goopg [amd64] (zesty-proposed) [0.3.1-2]
[12:29] -queuebot:#ubuntu-release- New: accepted patat [amd64] (zesty-proposed) [<IP_ADDRESS>-1]
[12:29] -queuebot:#ubuntu-release- New: accepted tipp10 [arm64] (zesty-proposed) [2.1.0-2]
[12:29] -queuebot:#ubuntu-release- New: accepted tipp10 [i386] (zesty-proposed) [2.1.0-2]
[12:29] -queuebot:#ubuntu-release- New: accepted tipp10 [ppc64el] (zesty-proposed) [2.1.0-2]
[12:29] -queuebot:#ubuntu-release- New: accepted yuma123 [amd64] (zesty-proposed) [2.9-1]
[12:29] -queuebot:#ubuntu-release- New: accepted yuma123 [armhf] (zesty-proposed) [2.9-1]
[12:29] -queuebot:#ubuntu-release- New: accepted yuma123 [powerpc] (zesty-proposed) [2.9-1]
[12:29] -queuebot:#ubuntu-release- New: accepted yuma123 [s390x] (zesty-proposed) [2.9-1]
[12:29] -queuebot:#ubuntu-release- New: accepted tipp10 [amd64] (zesty-proposed) [2.1.0-2]
[12:29] -queuebot:#ubuntu-release- New: accepted tipp10 [powerpc] (zesty-proposed) [2.1.0-2]
[12:29] -queuebot:#ubuntu-release- New: accepted yuma123 [arm64] (zesty-proposed) [2.9-1]
[12:29] -queuebot:#ubuntu-release- New: accepted yuma123 [ppc64el] (zesty-proposed) [2.9-1]
[12:29] -queuebot:#ubuntu-release- New: accepted tipp10 [armhf] (zesty-proposed) [2.1.0-2]
[12:29] -queuebot:#ubuntu-release- New: accepted yuma123 [i386] (zesty-proposed) [2.9-1]
[12:29] -queuebot:#ubuntu-release- New: accepted tipp10 [s390x] (zesty-proposed) [2.1.0-2]
[12:33] -queuebot:#ubuntu-release- New binary: gnuastro [ppc64el] (zesty-proposed/universe) [0.2.33-1] (no packageset)
[12:54] -queuebot:#ubuntu-release- Unapproved: linux-meta-snapdragon (yakkety-proposed/universe) [<IP_ADDRESS>3.25 => <IP_ADDRESS>5.27] (kernel) (sync)
[12:54] -queuebot:#ubuntu-release- Unapproved: linux-snapdragon (yakkety-proposed/universe) [4.4.0-1033.37 => 4.4.0-1035.39] (kernel) (sync)
[13:18] -queuebot:#ubuntu-release- Unapproved: linux-meta-snapdragon (yakkety-proposed/universe) [<IP_ADDRESS>3.25 => <IP_ADDRESS>5.27] (kernel) (sync)
[13:18] -queuebot:#ubuntu-release- Unapproved: linux-snapdragon (yakkety-proposed/universe) [4.4.0-1033.37 => 4.4.0-1035.39] (kernel) (sync)
[13:23] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-snapdragon [sync] (yakkety-proposed) [<IP_ADDRESS>5.27]
[13:23] -queuebot:#ubuntu-release- Unapproved: accepted linux-snapdragon [sync] (yakkety-proposed) [4.4.0-1035.39]
[13:23] -queuebot:#ubuntu-release- Unapproved: rejected linux-meta-snapdragon [sync] (yakkety-proposed) [<IP_ADDRESS>5.27]
[13:23] -queuebot:#ubuntu-release- Unapproved: rejected linux-snapdragon [sync] (yakkety-proposed) [4.4.0-1035.39]
[14:06] -queuebot:#ubuntu-release- Unapproved: init-system-helpers (trusty-proposed/main) [1.14 => 1.14ubuntu1] (core)
[14:17] -queuebot:#ubuntu-release- Unapproved: systemd (trusty-proposed/main) [204-5ubuntu20.19 => 204-5ubuntu20.20] (core)
[14:18] <pitti> slangasek: I spoke to tvoss again today, and finally uploaded these two ^ for bug 1616422; do you have some time to review these?
[14:18] <ubot5`> bug 1616422 in systemd (Ubuntu Trusty) "[trusty SRU/FFE] Add systemd binary package for snapd" [High,In progress] https://launchpad.net/bugs/1616422
[14:18] <pitti> it's certainly not "your average SRU", so please let me know if you want to discuss this with the TB first
[14:23] <xnox> if it's not used / pulled in by default (yet) it cannot regress =)
[14:24] <pitti> xnox: right, but it's still a new feature
[15:52] <slangasek> pitti: why make deb-systemd-invoke a /bin/true "script" instead of a symlink, OOI?
[15:53] <pitti> slangasek: bikeshedding matter; I mostly wanted a place to add a comment, but I'm happy to make it a symlink too
[15:53] -queuebot:#ubuntu-release- Unapproved: accepted init-system-helpers [source] (trusty-proposed) [1.14ubuntu1]
[15:53] <slangasek> pitti: it's a whole extra two syscalls, oh noes efficiency ;)
[15:54] <pitti> right, the remainder of dpkg and postinst will pale against that extra exec! :-)
[16:52] -queuebot:#ubuntu-release- New source: python-vmware-nsxlib (zesty-proposed/primary) [0.2.0-0ubuntu1]
[16:57] -queuebot:#ubuntu-release- New source: monasca-statsd (zesty-proposed/primary) [1.3.0-0ubuntu1]
[17:00] <doko> zul: did you update the copyright? ^^^
[17:00] <zul> doko: yes
[17:25] -queuebot:#ubuntu-release- New binary: freeradius [ppc64el] (zesty-proposed/main) [3.0.12+dfsg-3] (ubuntu-server)
[17:30] -queuebot:#ubuntu-release- New binary: freeradius [arm64] (zesty-proposed/main) [3.0.12+dfsg-3] (ubuntu-server)
[17:31] -queuebot:#ubuntu-release- New binary: freeradius [amd64] (zesty-proposed/main) [3.0.12+dfsg-3] (ubuntu-server)
[17:31] -queuebot:#ubuntu-release- New binary: freeradius [armhf] (zesty-proposed/main) [3.0.12+dfsg-3] (ubuntu-server)
[17:36] -queuebot:#ubuntu-release- New binary: freeradius [i386] (zesty-proposed/main) [3.0.12+dfsg-3] (ubuntu-server)
[17:37] -queuebot:#ubuntu-release- New: accepted gnuastro [ppc64el] (zesty-proposed) [0.2.33-1]
[17:37] -queuebot:#ubuntu-release- New binary: freeradius [powerpc] (zesty-proposed/main) [3.0.12+dfsg-3] (ubuntu-server)
[17:37] -queuebot:#ubuntu-release- New binary: freeradius [s390x] (zesty-proposed/main) [3.0.12+dfsg-3] (ubuntu-server)
[17:39] <doko> zul: no Python3 support?
[17:39] -queuebot:#ubuntu-release- New: accepted freeradius [amd64] (zesty-proposed) [3.0.12+dfsg-3]
[17:39] -queuebot:#ubuntu-release- New: accepted freeradius [armhf] (zesty-proposed) [3.0.12+dfsg-3]
[17:39] -queuebot:#ubuntu-release- New: accepted freeradius [powerpc] (zesty-proposed) [3.0.12+dfsg-3]
[17:39] -queuebot:#ubuntu-release- New: accepted freeradius [s390x] (zesty-proposed) [3.0.12+dfsg-3]
[17:39] -queuebot:#ubuntu-release- New: accepted freeradius [arm64] (zesty-proposed) [3.0.12+dfsg-3]
[17:39] -queuebot:#ubuntu-release- New: accepted freeradius [ppc64el] (zesty-proposed) [3.0.12+dfsg-3]
[17:39] -queuebot:#ubuntu-release- New: accepted freeradius [i386] (zesty-proposed) [3.0.12+dfsg-3]
[17:39] -queuebot:#ubuntu-release- New: accepted monasca-statsd [source] (zesty-proposed) [1.3.0-0ubuntu1]
[17:39] <zul> doko: there is work upstream to add that
[17:42] -queuebot:#ubuntu-release- New binary: openssl [ppc64el] (zesty-proposed/main) [1.0.2g-1ubuntu10] (core)
[17:42] -queuebot:#ubuntu-release- New binary: openssl [s390x] (zesty-proposed/main) [1.0.2g-1ubuntu10] (core)
[17:44] -queuebot:#ubuntu-release- New binary: monasca-statsd [amd64] (zesty-proposed/none) [1.3.0-0ubuntu1] (no packageset)
[17:44] -queuebot:#ubuntu-release- New binary: openssl [amd64] (zesty-proposed/main) [1.0.2g-1ubuntu10] (core)
[17:44] -queuebot:#ubuntu-release- New binary: openssl [i386] (zesty-proposed/main) [1.0.2g-1ubuntu10] (core)
[17:44] -queuebot:#ubuntu-release- New binary: openssl [powerpc] (zesty-proposed/main) [1.0.2g-1ubuntu10] (core)
[17:48] -queuebot:#ubuntu-release- New binary: openssl [arm64] (zesty-proposed/main) [1.0.2g-1ubuntu10] (core)
[17:51] -queuebot:#ubuntu-release- New binary: openssl [armhf] (zesty-proposed/main) [1.0.2g-1ubuntu10] (core)
[18:12] <xnox> doko, libssl1.0-dev is in binary new
[18:23] -queuebot:#ubuntu-release- New: accepted monasca-statsd [amd64] (zesty-proposed) [1.3.0-0ubuntu1]
[18:23] -queuebot:#ubuntu-release- New: accepted openssl [arm64] (zesty-proposed) [1.0.2g-1ubuntu10]
[18:23] -queuebot:#ubuntu-release- New: accepted openssl [i386] (zesty-proposed) [1.0.2g-1ubuntu10]
[18:23] -queuebot:#ubuntu-release- New: accepted openssl [ppc64el] (zesty-proposed) [1.0.2g-1ubuntu10]
[18:23] -queuebot:#ubuntu-release- New: accepted openssl [amd64] (zesty-proposed) [1.0.2g-1ubuntu10]
[18:23] -queuebot:#ubuntu-release- New: accepted openssl [powerpc] (zesty-proposed) [1.0.2g-1ubuntu10]
[18:23] -queuebot:#ubuntu-release- New: accepted openssl [armhf] (zesty-proposed) [1.0.2g-1ubuntu10]
[18:23] -queuebot:#ubuntu-release- New: accepted openssl [s390x] (zesty-proposed) [1.0.2g-1ubuntu10]
[18:29] <bdmurray> pitti: Thanks for working on the SRU queues!
[18:35] -queuebot:#ubuntu-release- Unapproved: accepted nplan [source] (xenial-proposed) [0.14~16.04]
[18:40] -queuebot:#ubuntu-release- Unapproved: accepted xserver-xorg-video-intel [source] (xenial-proposed) [2:2.99.917+git20160325-1ubuntu1.2]
[18:43] <slangasek> pitti: systemd conflicts: systemd-shim; in trusty systemd-shim is Priority: standard; how do we expect this transition to look?
[18:48] <infinity> slangasek: Err, it does?
[18:48] <slangasek> +  * systemd: Add Conflicts: to systemd-shim
[18:49] <slangasek> that's in the changelog of the SRU
[18:49] <infinity> Oh, in an SRU.
[18:49] <infinity> I was looking in the archive, silly me. ;)
[18:49] <slangasek> pff who looks there
[18:50] <infinity> slangasek: That seems reasonable in trusty, no?  We don't want people installing both.
[18:50] <infinity> slangasek: In xenial, systemd doesn't have the conflict, but rather a versioned Breaks.
[18:51] <infinity> (Though, I'm also not sure what problem it's solving years after trusty was released)
[18:51] <infinity> Oh.
[18:51] <slangasek> infinity: sure, but we want people to actually install it, and systemd-shim is in standard, so ick
[18:51] <infinity> Now I'm looking at the whole SRU.
[18:51] <infinity> Yeah, that doesn't work at all.
[18:52] <infinity> If the goal is to have a new systemd binary package that people install. :P
[18:52] <slangasek> that is the goal
[18:52] <slangasek> mostly interesting for the cloud image case, however
[18:52] <slangasek> and perhaps we don't have standard included there
[18:52] <slangasek> or can wiggle around it at image build time
[18:55] <infinity> Conflicting with standard is wrong regardless, IMO.
[18:56] <infinity> What's this new systemd solving?  snapd in trusty?
[18:56] <pitti> slangasek: apt has no problem with it; you mean that you don't want to lose the metapackage?
[18:56] <pitti> back for real in an hour, then we can discuss longer
[18:56] <infinity> pitti: Why the conflict at all, when we don't have it in later releases?
[18:56] <infinity> (later releases just have a versioned breaks, and the two coexist theoretically fine)
[18:56] <pitti> infinity: they'd fight for the same D-Bus API
[18:56] -queuebot:#ubuntu-release- Unapproved: accepted unscd [source] (trusty-proposed) [0.51-1ubuntu1]
[18:57] <pitti> no, they can't coexist under upstart really
[18:57] <pitti> with systemd as pid 1 that can claim that d-bus interface first
[18:57] <pitti> well, we could maybe rename the dbus service file, but you can't order a d-bus service against an upstart unit
[18:58] <pitti> anyway, back in ~ 1 h
[19:04] <slangasek> pitti: I mean that I don't expect systemd+snapd install in trusty to remove the metapackages, yes
[19:05] <slangasek> pitti: maybe we need to also change libpam-systemd to accommodate this?  (currently Depends: systemd-shim | systemd-sysv)
[19:06] <ogra_> just switch trusty from upstart to systemd via SRUs :P
[19:09] <slangasek> n/m, I was looking at yakkety deps there instead of trusty
[19:10] <slangasek> the deps seem ok on trusty; so we're only removing one package with Task: standard
[19:32] <infinity> slangasek: If a swap from systemd-shim to systemd is meant to DTRT in all cases, we can refresh ubuntu-meta to swap them in ubuntu-standard too.
[19:32] <infinity> slangasek: But this all sounds a bit "whee".
[19:33] <slangasek> nonsense
[19:33] <slangasek> it's perfectly safe
[19:33] <infinity> MY IRONY DETECTOR JUST WENT OFF, HOLD ON, NEED TO POKE IT WITH A BROOM.
[19:39] <davmor2> infinity: that's not Irony it's Sarcasm you need a different detector for that ;)
[19:39] <infinity> davmor2: Look up the defition of sarcasm. :P
[19:40] <infinity> definition, too.
[19:40] <davmor2> infinity: Ironically it seems to be missing from the Dictionary
[19:43] <infinity> davmor2: http://lmgtfy.com/?q=definition+of+sarcasm
[19:44] <davmor2> infinity: sometimes I worry that you don't have enough sarcasm detectors ;)
[19:46] <davmor2> infinity: next you'll be double checking if gullible has been removed too
[19:47] <infinity> davmor2: I got my mother with that classic, not once but TWICE.
[19:47] <davmor2> infinity: D'oh
[19:47] <infinity> davmor2: (several years apart, but still...)
[19:56] <slangasek> pitti: and should this trusty systemd package include the udev rules?
[20:01] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (trusty-proposed) [204-5ubuntu20.20]
[20:07] <pitti> infinity, slangasek: so switching from systemd-shim to systemd is likely to break suspend on some desktops (as that also won't use pm-utils any more) -- this was meant to be server/cloud mostly
[20:07] <pitti> but indeed this can't ever be perfect -- this is an utter hack which has never ever been done in the field before
[20:09] <pitti> slangasek: udev rules> we do need /lib/udev/rules.d/99-systemd.rules from systemd, this tells systemd which devices to track as .device units (snappy might need that)
[20:09] <slangasek> pitti: ok, got it
[20:09] <pitti> and the others are in s-services for logind, and shouldn't have changed
[20:10] <pitti> slangasek: so about the shim thing, I need to stare at this more closely
[20:10] <pitti> slangasek: so perhaps keep it in the pipe for now (or reject, I can easily reupload -- but I figure we do want to get rid of the breaks: then)
[20:10] <slangasek> pitti: oops I accepted
[20:10] <pitti> slangasek: ... or, we do a followup SRU to avoid it :)
[20:11] <slangasek> pitti: not sure that there is anything to avoid; I think the systemd-shim conflicts is reasonably correct within trusty
[20:11] <pitti> slangasek: it logically conflicts eiter way, yes; the only thing we could do is to make s-shim a no-op by some other means while systemd is installed
[20:12] <slangasek> yeah, that doesn't seem necessary to me
[20:12] -queuebot:#ubuntu-release- New binary: systemd [ppc64el] (trusty-proposed/main) [204-5ubuntu20.20] (core)
[20:12] <pitti> slangasek: util-linux is still in the pipeline, FYI
[20:13] <slangasek> right
[20:13] -queuebot:#ubuntu-release- New binary: systemd [i386] (trusty-proposed/main) [204-5ubuntu20.20] (core)
[20:19] -queuebot:#ubuntu-release- New binary: systemd [powerpc] (trusty-proposed/main) [204-5ubuntu20.20] (core)
[20:20] -queuebot:#ubuntu-release- New binary: systemd [amd64] (trusty-proposed/main) [204-5ubuntu20.20] (core)
[20:20] <pitti> slangasek: so now let's backport util-linux, then networkd too, then netplan
[20:20] <pitti> we might just have done ln -s xenial trusty on archive.u.c. to cut it short :)
[20:20] <slangasek> pitti: oh? I didn't understand that networkd+nplan were needed for this
[20:21] <slangasek> or was that a joke
[20:21] <pitti> slangasek: well, I hope it is a joke :)
[20:21] -queuebot:#ubuntu-release- New binary: systemd [arm64] (trusty-proposed/main) [204-5ubuntu20.20] (core)
[20:21] <slangasek> ok ;)
[20:21] <pitti> slangasek: but actually it did come up last week
[20:21] <slangasek> hmmm
[20:21] -queuebot:#ubuntu-release- New binary: systemd [armhf] (trusty-proposed/main) [204-5ubuntu20.20] (core)
[20:22] <pitti> slangasek: in the context of "we need an ifupdown backend written in netplan to be able to use it on trusty"
[20:22] <slangasek> who is saying that using netplan on trusty is a requirement?
[20:22] <pitti> slangasek: not a requirement so far; I think rharper mentioned it, but it was more like a discussion point than a roadmap
[20:23] <slangasek> I thought there was agreement ( rharper ?) that we would use v2 yaml for later OSes, v1 yaml for earlier
[20:23] <slangasek> like, this was specifically discussed for why we don't need to support v1 and v2 in the same yaml
[20:23] <slangasek> and supporting v2 yaml on trusty doesn't remove the flag day, just changes it
[20:51] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (trusty-proposed) [2.02~beta2-9ubuntu1.13]
[21:01] -queuebot:#ubuntu-release- New binary: syslog-ng [amd64] (zesty-proposed/universe) [3.8.1-5] (no packageset)
[21:01] -queuebot:#ubuntu-release- New binary: syslog-ng [i386] (zesty-proposed/universe) [3.8.1-5] (no packageset)
[21:01] -queuebot:#ubuntu-release- New binary: syslog-ng [s390x] (zesty-proposed/universe) [3.8.1-5] (no packageset)
[21:04] -queuebot:#ubuntu-release- New binary: syslog-ng [armhf] (zesty-proposed/universe) [3.8.1-5] (no packageset)
[21:04] -queuebot:#ubuntu-release- New binary: syslog-ng [powerpc] (zesty-proposed/universe) [3.8.1-5] (no packageset)
[21:04] -queuebot:#ubuntu-release- New binary: syslog-ng [arm64] (zesty-proposed/universe) [3.8.1-5] (no packageset)
[21:15] -queuebot:#ubuntu-release- New: accepted systemd [i386] (trusty-proposed) [204-5ubuntu20.20]
[21:15] -queuebot:#ubuntu-release- New: accepted systemd [ppc64el] (trusty-proposed) [204-5ubuntu20.20]
[21:15] -queuebot:#ubuntu-release- New: accepted systemd [amd64] (trusty-proposed) [204-5ubuntu20.20]
[21:15] -queuebot:#ubuntu-release- New: accepted systemd [armhf] (trusty-proposed) [204-5ubuntu20.20]
[21:15] -queuebot:#ubuntu-release- New: accepted systemd [arm64] (trusty-proposed) [204-5ubuntu20.20]
[21:15] -queuebot:#ubuntu-release- New: accepted systemd [powerpc] (trusty-proposed) [204-5ubuntu20.20]
[21:17] -queuebot:#ubuntu-release- Unapproved: neutron (yakkety-proposed/main) [2:9.0.0-0ubuntu<IP_ADDRESS> => 2:9.0.0-0ubuntu<IP_ADDRESS>] (openstack, ubuntu-server)
[21:18] -queuebot:#ubuntu-release- Unapproved: neutron (xenial-proposed/main) [2:8.3.0-0ubuntu1.1 => 2:8.3.0-0ubuntu1.2] (openstack, ubuntu-server)
[21:53] <slangasek> pitti: did you reject cyphermox's shim syncs out of the queue?
[21:54] <cyphermox> I'm more curious as to why I can't see the emails for it, but I suppose it's because it's a sync?
[21:54] <slangasek> mayhaps
[21:54] <infinity> Yeah, syncs don't behave entirely correctly.
[21:54] <infinity> See the Soyuz Redesign that William, Colin and I could never get enough buyin to actually allocate resources/time to.
[21:55] <infinity> (A big part of that was making syncs first class queue citizens that actually contain stuff and act like any other queue object, rather than being weird pointers to nowhere that behave unintuitively in almost every way)
[22:11] -queuebot:#ubuntu-release- Unapproved: shim (precise-proposed/main) [0.8-0ubuntu2 => 0.9+1474479173.6c180c6-0ubuntu1] (no packageset) (sync)
[22:12] -queuebot:#ubuntu-release- Unapproved: shim (trusty-proposed/main) [0.8-0ubuntu2 => 0.9+1474479173.6c180c6-0ubuntu1] (core) (sync)
[22:26] -queuebot:#ubuntu-release- Unapproved: shim (xenial-proposed/main) [0.8-0ubuntu2 => 0.9+1474479173.6c180c6-0ubuntu1] (core) (sync)
[22:27] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (trusty-proposed) [0.9+1474479173.6c180c6-0ubuntu1]
[22:31] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (trusty-proposed) [1.21.4~14.04.1]
[22:38] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (xenial-proposed) [0.9+1474479173.6c180c6-0ubuntu1]
[22:43] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (xenial-proposed) [1.21.4~16.04.1]
[22:47] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (xenial-proposed) [2.02~beta2-36ubuntu3.5]
[22:49] -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (xenial-proposed) [1.66.5]
[22:50] -queuebot:#ubuntu-release- New: accepted python-glance-store [amd64] (xenial-proposed) [0.13.0-3ubuntu<IP_ADDRESS>]
[22:56] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.4 => 2.02~beta2-36ubuntu3.5] (core)
[23:19] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.5 => 2.02~beta2-36ubuntu3.5] (core)
[23:19] -queuebot:#ubuntu-release- New binary: golang-gopkg-alexcesaro-statsd.v1 [amd64] (zesty-proposed/universe) [0.0~git20160306.0.c289775-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: golang-github-ctdk-go-trie [amd64] (zesty-proposed/universe) [0.0~git20161027.0.6443fbc-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: golang-github-mreiferson-go-httpclient [amd64] (zesty-proposed/universe) [0.0~git20160630.0.31f0106-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: golang-github-tideland-golib [amd64] (zesty-proposed/universe) [4.12.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: golang-github-ctdk-chefcrypto [amd64] (zesty-proposed/universe) [0.0~git20161109.0.dea96d7-1] (no packageset)


[09:38] <niluje> hey, any help would be appreciated.. how is merge working with bzr?
[09:38] <niluje> my coworker, ed, has a branch. He wants to merge my work on it. bzr merge <my branch> doesn't merge the commits but only the changes
[09:39] <niluje> is it possible to merge the commits and their messages?
[09:40] <niluje> or does he have to merge & commit for each of my commit?
[09:41] <fullermd> merge _does_ merge the commits.
[09:44] <niluje> fullermd: http://pastie.org/10513117
[09:46] <fullermd> Thus the pending merge tip  :)
[09:46] <jelmer> niluje: "bzr merge" just stages the merge; you need to run "bzr commit" to commit it.
[09:46] <niluje> oh
[09:47] <niluje> yeah
[09:47] <niluje> but if I run "bzr commit -m 'whatever'"
[09:47] <jelmer> niluje: "bzr merge" just stages the merge; you need to run "bzr commit" to commit it.
[09:47] <niluje> there only one commit with "whatever" as message
[09:48] <fullermd> Merged revs are hidden away by default.  Use -n0 to expand them out.
[09:48] <niluje> on which command should I use -n0?
[09:48] <fullermd> log
[09:48] <niluje> oh, indeed
[09:49] <niluje> is there a great GUI tool on osx?
[09:49] <niluje> thanks a lot :) as a git user, I'm a bit confused with bzr :p
[09:49] <niluje> -n0 answers my questions
[09:51] <fullermd> How well/deeply do you know git?
[09:53] <niluje> well :p
[09:54] <fullermd> 'k.  So in gittish terms, 'bzr log' by default only follows the first parents.  Revs with more parents do get marked [merge], but you need -n[something] to expand those branches.
[09:54] <niluje> yep
[09:54] <niluje> so there no equivalent to fast forward merges, right?
[09:55] <fullermd> The operative theory is...   well, OK, the _proximate_ operative theory behind the change that made that happen, is that it's faster/not as painfully slow to do that.
[09:56] <fullermd> But the _other_ operative theory is that generally, you don't care about the details of something merged.  Merges tend to be stuff like "merge trunk [into this feature branch I'm still working on, to keep caught up]", or "land feature X [into trunk]".  In either case, most of the time, just the fact of what happened is all you really care about.
[09:56] <fullermd> It's only when you need to look at some detail along the way that you care about the individual revs inside it, so collapsing them away makes it easier to look at the history and find the bits you _do_ care about.
[09:57] <fullermd> 'bzr pull' does fast forwards [only].
[09:57] <fullermd> There's also a 'merge --pull' that does fast forwards if it can.
[09:58] <fullermd> It's a bit confusing using it IMO, though, since that means that sometimes it'll FF and you don't have to commit anything, but sometimes it can't and so you do have to commit the merge.
[09:58] <niluje> ok
[09:58] <niluje> what about rebasing?
[09:58] <niluje> if I'm on my feature branch and I want to rebase on the master branch, should I merge?
[09:59] <fullermd> There's a 'rewrite' plugin that does [some subset of] that.  I'm not sure how well it works.
[09:59] <fullermd> In bzr world, people generally just merge stuff.
[09:59] <niluje> ok :)
[10:00] <niluje> thanks a lot for the explainations fullermd
[10:00] <niluje> what about a GUI on OSX? do you know a good one?
[10:01] <fullermd> I don't think there's an integrated one.  I imagine the bits of qbzr work there, which gives GUI's for certain commands.
[10:01] <fullermd> There is/what a bzr-gtk too, that was similar.
[10:02] <niluje> let's stick with cli then :p
[10:02] <fullermd> (is/was; at one point it fell into near-total disrepair, I don't recall if it was resurrected or not)
[10:02] <niluje> kk, thanks!
[10:17]  * fullermd pulls vila's plug a few more times, just for kicks.
[10:19] <vila> fullermd: hehe, try again, I switched from desktop to laptop for an upgrade ;)
[10:20] <fullermd> Upgrade?  You mean you switched out that "Lunix" thing for a _real_ OS?   ;>
[10:22] <vila> hehe, real ? What's real and what's virtual... Do I still know...
[10:22] <fullermd> Real is stuff you can eat.  Virtual is just little bytes.
[10:23] <vila> ha right, I should stop that diet then ;)


[00:37] <Bashing-om> UWN-prep; Gdoc. Mary Frances Hull made a suggestion that I declined to accept. See Gdoc that my refusal notice is acceptable, please.
[04:11] <guiverc> sorry went to range to make noise (thus delayed...) your response seemed nice/appropriate to me Bashing-om (adding name to contributor I love too!)
[04:18] <Bashing-om> guiverc: Good deal - I just considered might be a better means to make the response as public than in Gdoc - :(
[04:21] <guiverc> I would possibly add your response to the "suggestion" (comment) to the right of the gdoc.. ie. a reply, as I believe this will go to her email (I tend to see response to comments via email) where as the answer in the doc itself maybe missed... my only thought.
[04:21] <guiverc> maybe add "Thank you..." as well
[04:22]  * guiverc is thinking of how i mechnically reply to bug responses... stopped myself at 'thank you' ^
[04:23] <Bashing-om> guiverc: Great thought and advise - yeah "might" go to her Email :)
[04:27] <Bashing-om> guiverc: See too if youu find the redo of the Community Office Hours article acceptable.
[04:40]  * guiverc responded my thoughts via gdoc ;  I'll be away awhile walking pup
[06:12] <Bashing-om> guiverc: Me thibnks we are now good to go - so I am up and went - laters :D
[06:13] <guiverc> :)  Night Bashing-om
[06:13] <Bashing-om> toodles :D
[08:29] -SwissBot:#ubuntu-news- ::Planet:: Julian Andres Klode: Migrating away from apt-key @ https://blog.jak-linux.org/2021/06/20/migrating-away-apt-key/
[20:16] <Bashing-om> UWN: Issue 588 up for review and final edits: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue688 :D


[03:09] <Peet> Hello. Can I ask an install question here please?
[03:10] <Peet> I just installed Unbuntu 12.04 from the live CD. The install said it was successful. After the first reboot though, it tries to start from the HD but I just see a flashing cursor in the upper left corner. No GRUB
[03:11] <Peet> No nothing.  Any ideas on where I can start?
[03:12] <holstein> Peet: try booting the live CD
[03:12] <Peet> Yep, that works fine. Then what?
[03:13] <Peet> If it helps any, I installed ubunut onto a clean, brand new HDD
[03:13] <holstein> Peet: test the hard drive.. maybe its bad
[03:16] <Unit193> It's not an EFI system is it?  And the Grub menu doesn't normally pull up on a single boot system.
[03:17] <Peet> Unit193: Sorry, what do you mean by EFI?    It's a Toshiba Satellite laptop from 2006.
[03:17] <Unit193> Then not EFI.
[03:17] <Peet> That helps me as far as Grub, thanks
[03:17] <Peet> Ok, I see
[03:18] <Peet> If the install went all the way through, is there still a chance the CD I installed from is bad?
[03:18] <Peet> I was thinking of maybe creating another CD-R
[03:23] <holstein> Peet: you can test the CD
[03:24] <Peet> Good point. I did run it as the Live part on a nother PC here and that works fine. Connect to the net from there, etc...
[03:24] <Peet> You mentioned testing the HDD. Is there a tool for that or did you just mean connect it to another PC and read its contents?
[03:25] <holstein> i use the ultimate boot cd...
[03:30] <Peet> holstein: thanks. reading about it now ...
[04:58] <vastkahuna> I have compiz installed on my system, how do I get it to work?
[04:59] <holstein> vastkahuna: what system?
[04:59] <vastkahuna> Ubuntu 12.10
[04:59] <holstein> vastkahuna: ubuntu just ships it... so its just working, or should be.. are you on xubuntu?
[05:00] <vastkahuna> I'm on just regular ubuntu, but I don't see it doing anything fancy like I was expecting
[05:01] <holstein> vastkahuna: its not like that anymore..
[05:01] <vastkahuna> Do I have to go into it and enable certain things?
[05:02] <holstein> vastkahuna: you dont have to, but you can.. just nail down what certain things you want
[05:02] <vastkahuna> Where do I go and how do I do it?
[05:02] <holstein> vastkahuna: do what?
[05:03] <vastkahuna> Open the settings and change them
[05:03] <holstein> vastkahuna: unity is not all that customizable.. what are you wanting to change?
[05:04] <vastkahuna> I just want to see the different effects like it does when you open your browser or a new window
[05:08] <krytarik> Just install CompizConfig Settings Manger, fire it up, and go to "Effects -> Animations".
[05:11] <vastkahuna> Can I do that in the terminal or where?
[05:13] <krytarik> Either run "sudo apt-get install compizconfig-settings-manager", or use the Software Center to install CCSM.
[05:14] <krytarik> After that, run it from the Dash, or from the menu, depending on what session you are using.
[05:17] <vastkahuna> http://pastebin.com/xCBFYnck
[05:18] <vastkahuna> I just tried it in the terminal but I'm not sure if it's telling me it's ready or what
[05:19] <krytarik> Alright, go for the Dash/menu now.
[05:20] <vastkahuna> And what do I put in to open it?
[05:20] <krytarik> "CCSM", for example.
[05:21] <krytarik> Now what session are you using actually?
[05:22] <krytarik> ^^ That was for the Dash in Unity or under Gnome Shell, alternatively just start typing "Compiz...".
[05:23] <vastkahuna> I'm not sure what you mean by session, I'm in ubuntu 12.10 and I'm using Firefox if that's what you mean
[05:24] <vastkahuna> I have the menu open for CCSM but I'm not sure how to enable the different effects
[05:25] <krytarik> Like I said, what you mentioned is under "Effects -> Animations".
[05:26] <krytarik> Also, you may want to install the package "compiz-plugins" to get even more options.
[05:27] <vastkahuna> So sudo apt-get compiz-plugins in the terminal?
[05:28] <krytarik> Plus "install" after "apt-get", yes.
[05:30] <vastkahuna> Now do I have to close and re-open CCSM for these to take efffect or reboot or anything like that?
[05:31] <krytarik> You should better just relogin, yes.
[05:36] <krytarik> vastkahuna, can you please run this command and tell me the output? It would show the name of the session you are using. -> "echo $DESKTOP_SESSION"
[05:38] <krytarik> Not that you are using a session where Compiz isn't actually used, like Gnome Shell or Gnome Classic w/o Effects. :P
[05:41] <vastkahuna> It didn't seem to do anything
[05:41] <krytarik> Run in the Terminal?
[05:41] <vastkahuna> http://pastebin.com/
[05:42] <krytarik> Wrong URL. :P
[05:45] <vastkahuna> So re-enter echo $DESKTOP_SESSION  in the terminal?
[05:45] <krytarik> Yes.
[05:45] <krytarik> Make sure you don't misspell it.
[05:49] <krytarik> What happened, vastkahuna?
[05:50] <krytarik> ^^ vastkahuna_
[05:52] <vastkahuna_> It didn't seem to do anything
[05:53] <krytarik> Now I actually meant why you needed to relogin to IRC. :)
[05:53] <krytarik> Doesn't the command output a session name? It should.
[05:53] <vastkahuna_> My browser seemed to freeze
[05:54] <krytarik> Aha, already thought something like that.
[05:56] <vastkahuna_> I was trying to send you the link from pastebin but that page seems to be messedup, I can't find the link at the top of that pge
[05:56] <krytarik> You aren't possibly using something like Cinnamon, are you?
[05:57] <vastkahuna_> No just standard ubuntu 12.10 and whatever that uses
[05:57] <krytarik> The pure default then, yes?
[05:58] <vastkahuna_> Yes
[05:58] <krytarik> That would be Unity then, and the output should be "ubuntu" - isn't it?
[05:58] <vastkahuna> Yes
[05:59] <krytarik> Oki doki. :)
[05:59] <krytarik> Compiz is used then.
[06:00] <krytarik> Have fun with playing with its settings then, but don't break it! :P
[06:01] <vastkahuna_> Something weird just happened, my search bars are missing from the top of my browser page
[06:03] <vastkahuna_> OK it's back now
[06:03] <krytarik> Ok, was going to say: right-click somewhere besides the tabs and re-enable "Navigation Toolbar". :)
[06:04] <krytarik> Btw, you may want to use something like XChat when chatting that often on IRC. :)
[06:05] <krytarik> I.e. the webchat interface is rather ugly and misses a lot of features.
[06:05] <vastkahuna_> Yeah, now in CCSM I have the effects and animations open, so just check the boxes under random effects?
[06:06]  * krytarik looks
[06:07] <vastkahuna_> OK thanks
[06:07] <krytarik> No, that's really only for if you set "Random" as the effect for something on the list above that.
[06:09] <krytarik> For example, I have the first on the list under "Open Animation" set to "Glide 2".
[06:10] <krytarik> Click on the entry you want to edit, then below the list, click on "Edit".
[06:11] <vastkahuna_> That seems to be the standard setting because mine is like that too but I don't see any special effects when I open my browser or a new window
[06:12] <krytarik> Yeah, might be, but I think I have lowered the duration - to what is it set there? I have mine on 80.
[06:13] <vastkahuna_> Glide 2 on mine is at 120
[06:14] <vastkahuna_> Fade is at 80
[06:15] <krytarik> Now that you mention it, it doesn't work here either (Lucid 10.04), and I remember there is a bug report about that somewhere.
[06:17] <krytarik> So sorry, I guess you can forget about that for now. :|
[06:17] <vastkahuna_> I was reading on it somewhere before I logged in here and they think it has to do with unity, maybe disabling something there first?
[06:18] <krytarik> Most other animations should work tough, just not the "Open Animation".
[06:19] <krytarik> As I mentioned, I'm using Lucid 10.04, way before Unity as it is now started to exist. :P
[06:19] <vastkahuna_> I don't know but it doesn't seem to do anything, it's just regular
[06:19] <krytarik> Yep, just pops up.
[06:20] <vastkahuna_> I have a question about something else
[06:20] <krytarik> Then shoot! :)
[06:21]  * krytarik searches for that bug report
[06:22] <vastkahuna_> I installed ubuntu restricted extras to fix flash and my dvd movie player, it fixed flash but the codecs must be missing for the dvd
[06:23] <krytarik> !dvd
[06:23] <krytarik> Check out that ^^ too then.
[06:25] <vastkahuna_> Yeah  I was looking at that but it didn't seem to help, why do they make it so hard?
[06:26] <krytarik> I'm not playing DVDs myself, so I can't really help with that, sorry.
[06:27] <vastkahuna_> OK thanks
[06:27] <vastkahuna_> Bye
[06:27] <krytarik> Bye.
[07:53] <r4y> I am having trouble with my mp3 player. I am not sure if I did safe removeable or not, but it will not mount. It's an RCA mp3 player model number th1814wm-a
[07:53] <r4y> http://paste.ubuntu.com/5575630/
[07:53] <r4y> http://imagebin.org/248545
[07:53] <r4y> http://imagebin.org/248546
[07:53] <r4y> http://imagebin.org/248547
[07:56] <r4y> It still plays the music that is on it. And Windows XP says it is in mtp mode and if I remember right it is supposed to be in msc mode, but I don't know how to change it's mode. I tried formatting it but it can't be formatted and there is no mount point and I tried flashing the firmware with an exe file rca supplied. I should say I 2 different ones that they supplied, one of which I have...
[07:56] <r4y> ...used before to fix this mp3 player before.
[07:57] <r4y> It's cheap, but we are pinching our pennies right now
[08:01] <r4y> To get the photos and info from the terminal I had to connect this mp3 player over and over and over each time removing the battery to turn it off, because it stops being under /dev/bus/usb/001
[08:21] <r4y> I found this:
[08:21] <r4y> http://ubuntuforums.org/archive/index.php/t-1551985.html
[08:21] <r4y> How can I use what they said to do at the bottom of that thread?, and should I try it?
[08:23] <r4y> Am I supposed to create this file /etc/usb_modeswitch.conf?, because I don't see it there, or is that a file that has to downloaded from the link given at the bottom of that thread?
[08:26] <r4y> I guess the downloadable file was only of the logging that person did
[08:28] <krytarik> A quick web search indicates that you can just create that file there and enter that setting.
[08:30] <r4y> ah, I will try then
[08:34] <r4y> O well, it was worth a shot. TY for trying
[08:35] <krytarik> I barely just googled for you :P - didn't work then apparently?
[08:36] <r4y> I don't think so
[08:37] <krytarik> Did you reboot after putting that file in place? If not, I think you should do so.
[08:37] <r4y> I also tried changing it and adding EnableLogging=1, but I don't know where the info for logging would be put into
[08:38] <r4y> OK, I change it and do so just in case
[08:38] <r4y> I will be back
[08:44] <r4y> I didn't work. I is it supposed to be DisableSwitching=1
[08:45] <r4y> I would guess not assuming 1=true and 0=false
[08:46] <krytarik> Too bad. Reg. the log file, it should pop up directly under "/var/log", according to this page - there is way more info there too: http://www.draisberghof.de/usb_modeswitch/#trouble
[08:49] <r4y> I should read this, so I bookmarked it and I will change DisableSwitching=1 to DisableSwitching=0and enable debugging as well then I will have to reboot then get the info from the log file
[08:49] <r4y> I will be back
[08:50] <krytarik> Ok.
[08:50] <r4y> Are those the only 2 lines needed? because I am a newbie sort of
[08:51] <r4y> I mean I am not a dev of coarse and I haven't messed with scripting and so forth
[08:52] <r4y> Just plain, right?
[08:52] <krytarik> Yeah, I've seen an example file in a forums post, the rest was all outcommented stuff.
[08:52] <r4y> DisableSwitching=0 enter next line EnableLogging=1
[08:52] <krytarik> Yes, just plain text.
[08:52] <r4y> OK
[08:52] <r4y> I will be back
[08:57] <r4y> There is no log
[08:57] <r4y> was this what this line should read DisableSwitching=0
[08:59] <krytarik> What version of Ubuntu are you using then?
[08:59] <r4y> 10.04
[08:59] <r4y> Am I supposed to run a command for this?
[09:00] <r4y> Ah, I haven't read that link yet
[09:01] <krytarik> No, I just have checked whether that config should be there by default in your version of Ubuntu - in Lucid 10.04 not.
[09:03] <r4y> Automatic serial driver assignment will work with the 3G-optimized driver only for kernels from 2.6.27 and up
[09:05] <krytarik> Btw, the example file content I was referring to is here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=5815&sid=d6747e6f86292dc1e0e1ea436633e561#p5815
[09:07] <r4y> So then it should work for this kernel I think after checking synaptic package manager
[09:08] <r4y> Header files related to Linux kernel version 2.6.32 and that is what I remember to be a lower number
[09:08] <krytarik> You know, you should try with the Live CD of a current version of Ubuntu if 1.) your original issue exists, and 2.) that workaround works.
[09:09] <r4y> Would I need to install extra packages?
[09:09] <r4y> updates
[09:09] <krytarik> Since the version of that tool provided via the Lucid 10.04 is considerably older too.
[09:10] <r4y> Well couldn't I try Ubuntu 12.04 virtaully for this?
[09:10] <krytarik> Also, Lucid's End of Life is in April this year anyway.
[09:10] <r4y> I know
[09:10] <r4y> But I am not switching
[09:11] <r4y> in a calm tone
[09:12] <krytarik> Well, I will upgrade to Precise 12.04 any time soon - I'm currently still on Lucid too. :)
[09:13] <r4y> I tried it but to each their own
[09:14] <krytarik> Reg. the Virtual Machine thing, I don't think that it would go that deep, hardware control-wise, but I don't really know.
[09:14] <r4y> I still haven't tried the OSes Unit193 suggested to try out which I have downloaded, but I am going
[09:14] <r4y> to
[09:14] <krytarik> It's not that you have to live with the default "Ubuntu" setup, you know. :)
[09:14] <r4y> kubuntu, lubuntu and xubuntu
[09:15] <r4y> I know
[09:15] <r4y> I want to myself out there and try debian but I am afraid
[09:15] <krytarik> You should definitely have a look at Xubuntu, I was quite impressed when I played with it thoroughly just recently. :)
[09:16] <krytarik> You can simply run any Ubuntu ISO through Grub2, you know?
[09:17] <r4y> I still haven't tried other linux oses on this motherboard because I had tried some other gnome off shoots of Ubuntu for pleasing gnome fans whichI didn't like
[09:17] <r4y> grub2, what?, I mean Idon't like installing and messing up another install
[09:18] <r4y> I still to one install per hard drive just in case
[09:18] <krytarik> Grub2 is the boot loader.
[09:18] <r4y> I told you I am sort of a newbie
[09:19] <r4y> I've been using Ubuntu since gutsy
[09:19] <r4y> but I lack a lot
[09:19] <krytarik> I.e. you put the ISO somewhere on your HDD, add an entry for it to the Grub2 menu, and then you can boot directly into it.
[09:20] <krytarik> Sec., grabbing for a link.
[09:20] <r4y> What, that's cool
[09:21] <krytarik> There: http://ubuntuforums.org/showthread.php?t=1549847
[09:22] <krytarik> Yeah, indeed, that way I'm running any sorts of current Ubuntu ISO without ever having to burn a CD/DVD. :)
[09:22] <r4y> I like not having to install a program but that is great as well
[09:24] <krytarik> Grub2 is the default boot loader of Lucid 10.04 as well.
[09:26] <r4y> So the path should be under the filesystem?, not home
[09:27] <r4y> O
[09:27] <r4y> I mean I was wrong I guess
[09:28] <krytarik> You mean for the config file? Yes.
[09:28] <krytarik> As well as the log file.
[09:28] <r4y> I like to use this command gksudo nautilus when messing with the filesystem. It just makes things easier for me
[09:30] <krytarik> Yeah, but not always necessary, sometimes it's easier to just use "sudo nano <file>" for just editing files, for example.
[09:31] <r4y> I am a little lost and I need to use the bathroom and get water, sorry, I need to read this some more as well
[09:31] <krytarik> Yeah, I should go to bed as well, so... :)
[09:31] <r4y> Sorry for speaking so soon hear
[09:32] <r4y> TY for this info but it will take me a little to put it together. I haven't messed with the grub menu I don't think
[09:32] <krytarik> It's 10:32 AM here already, so.. - I'm just a little weird in that.  There is also this, if you want to know more: https://help.ubuntu.com/community/Grub2
[09:34] <r4y> TY, that should help me
[09:34] <krytarik> You are welcome. :)
[09:34] <r4y> TY for trying to help me
[09:35] <krytarik> And good luck with your original issue.
[09:35] <r4y> This mp3 player is driving me nuts, but I know I need to get a better one
[09:35] <r4y> and I've been to the channel rockbox
[09:36] <r4y> I Just don't have the money yet for it
[09:36] <r4y> Things are some what tight here, but I am happy
[09:36] <r4y> TY again
[09:36] <krytarik> Yup. :)
[09:36] <r4y> Ya, I may never get it fixed, but what ever
[09:37] <Guest41676> Hi
[09:37] <r4y> Hi
[09:37] <Guest41676> I am new to Ubuntu and have a problem
[09:37] <Guest41676> I installed 12.10 inside VirtualBox running on Windows 7
[09:38] <r4y> There is also the ubuntu channel as well as this channel just in case
[09:38] <Guest41676> It wend well until the first real boot. The system booted but I did not get any prompt/loging window
[09:38] <Guest41676> Nothing
[09:38] <Guest41676> Can anybody help?
[09:39] <r4y> I can't, I am sorry, but maybe someone else here can help, I am just a visitor
[09:39] <r4y> There is this channel as well #ubuntu
[15:15] <r4y> Hello, can someone help me add an entry to the grub 2 menu?
[15:15] <r4y> http://paste.ubuntu.com/5576527/
[15:17] <r4y> Disk Utility says /dev/sda, is it still supposed to be the way I posted it in pastebin if it is sda?
[15:17] <r4y> Someone gave me this link:
[15:17] <r4y> http://ubuntuforums.org/showthread.php?t=1549847
[15:18] <r4y> I think that person's nick started with a k, anyways
[15:20] <r4y> I think the answer is yes
[15:21] <r4y> does hd0,1 remain as hd0,1 or should it be changed
[15:34] <r4y> http://paste.ubuntu.com/5576579/
[15:35] <r4y> I want to understand better what is sda1 and sda2 and sda5 for?, is one for home and one for the filesystem, please make this clear to me
[15:35] <r4y> Anyone?
[15:36] <r4y> Give me my daily Linux bread, lol
[15:36] <r4y> Don't over feed me though
[15:37] <r4y> I forgot got to say pretty please
[15:39] <r4y> I should say that the help I've been given here has been very nice and I want to thank all the people here for the help you give us
[15:44] <r4y> I need to sleep, so I will keep this open in hopes that someone will answer what I have asked.
[15:54] <r4y> I didn't have chatzilla logging, so now I can go to sleep. Any help with my simple questions would really help me in strides. Sorry for any past trouble. TY all for the help over the years
[16:05] <r4y> I wasn't referring to the questions I had regarding my mp3 player, just the questions regarding adding an iso file to the grub 2 menu entrie and what sda1, sda2 and sda5 stand for. I forgot home is under the filesystem, duh, so then never mind that question
[16:07] <r4y> Is this right?, http://paste.ubuntu.com/5576527/ or hd0,1 is supposed to be different http://paste.ubuntu.com/5576579/
[16:12] <r4y> Sorry, in part it is too much coffee and lack of sleep. I am not a social person, so I lack thinking before I speak and ramble. What's great about the Ubuntu forums for instance is that we can edit what we have written to take out spelling errors and ramblings. Anyways, sorry again
[16:13] <r4y> I will be logging this so I can sleep
[21:57] <alexitc_> is anyone here knowledgable?
[21:59] <alexitc_> is anyone here alive?
[22:00] <alexitc_> shadeslayer r u here?
[22:28] <alexitc_> anyone here?
[22:29] <Unit193> !ask | alexitc_
[22:30] <alexitc_> i cant find the mount point for my external dvd drive. how can i find that out?
[22:32] <Unit193> /dev/sr0 is a standard one.
[22:32] <Unit193> !mount
[22:34] <alexitc_> cant find /dev/sr0 in /etc/fstab or /etc/mtab
[22:43] <alexitc_> am i never gonna be able to mount a cd or dvd drive?
[23:29] <cerebrate> Peace yall.  may i have guidance into making a practical script to keep my touchpad i dont need or want from activating through the software
[23:32] <krytarik> How about this?: https://help.ubuntu.com/community/SynapticsTouchpad#Completely_disabling_Touchpad
[23:35] <cerebrate> it varies with the necessary change of login devices attached to my computer krytarik
[23:35] <cerebrate> plus i want it automated
[23:35] <cerebrate> i guess i should read the friendly manpage or something
[23:35] <cerebrate> oh yeah you proved satisfactory :D
[23:35] <krytarik> :)
[23:37] <cerebrate> dissatisfactory implimenting due to use of lubuntu instead of less modified ubuntu variants :/
[23:38] <cerebrate> atareao not found in commands
[23:38] <cerebrate> atareao not found in accessories list
[23:40] <krytarik> You'd have to install it from its PPA first, with the commands provided there.
[23:41] <cerebrate> apparently touchpad functionality disabled :D
[23:41] <cerebrate> tyvm ^3^
[23:41] <krytarik> You are welcome. :)
[23:55] <r4y> krytarik 	Is this right?, http://paste.ubuntu.com/5576527/ or hd0,1 is supposed to be different http://paste.ubuntu.com/5576579/
[23:57]  * krytarik looks
[23:58] <krytarik> Looks fine to me.


[03:02] <kelms> hi there
[03:05] <Guest48720> Hey all=) Newbie member here!
[03:07] <kelms> hi there
[03:08] <eddies92> im new to irc. this is the NM LUG correct?
[03:08] <eddies92> not a very big outcome.
[03:08] <kelms> nope
[03:09] <eddies92> i hope you mean no to the outcome piece. maybe more will come later?
[03:09] <eddies92> I have a question: I have two dvd drives on my computer and linux mint only sees one. Is there a way I can enable the second one.
[03:12] <eddies92> Lubotu1 here?