[04:46] -queuebot:#ubuntu-release- New: accepted r-cran-gfonts [sync] (mantic-proposed) [0.2.0-2]
[04:48] -queuebot:#ubuntu-release- New binary: r-cran-gfonts [amd64] (mantic-proposed/none) [0.2.0-2] (no packageset)
[05:39] -queuebot:#ubuntu-release- New: accepted r-cran-gfonts [amd64] (mantic-proposed) [0.2.0-2]
[07:48] -queuebot:#ubuntu-release- New sync: unison-2.53 (mantic-proposed/primary) [2.53.3-2]
[07:52] <LocutusOfBorg> I'm doing some ocaml syncs, they are bugfixes only, they deprecate ocaml-nox, some cleanup of build system with new dh-ocaml build facilities
[07:52] <LocutusOfBorg> should be easy stuff, all leaf packages
[07:52] <LocutusOfBorg> this unison-2.53 is a new leaf package, but upstream moved to gtk-3 and they "urged people to upgrade" :)
[07:53] <LocutusOfBorg> we can keep both 2.52 and 2.53 in the archive, not sure why every release they add a new source package
[08:07] -queuebot:#ubuntu-release- New sync: unison-2.53 (mantic-proposed/primary) [2.53.3-2]
[08:15] -queuebot:#ubuntu-release- New sync: ocaml-merlin (mantic-proposed/primary) [4.7-413-3]
[08:18] -queuebot:#ubuntu-release- New sync: pplacer (mantic-proposed/primary) [1.1~alpha19-6]
[08:24] <LocutusOfBorg> pplacer should be rejected ^^ also the duplicate unison-2.53, my bad
[09:00] <ricotz> hello ubuntu-archive, please unblock libreoffice in mantic-proposed which is held back by missing i386 build
[09:20] <doko> no, i386 is not in the Architecure fields, it's deliberate, not missing
[09:35] -queuebot:#ubuntu-release- New: accepted ocaml-merlin [sync] (mantic-proposed) [4.7-413-3]
[09:35] -queuebot:#ubuntu-release- New: rejected unison-2.53 [sync] (mantic-proposed) [2.53.3-2]
[09:35] -queuebot:#ubuntu-release- New: rejected pplacer [sync] (mantic-proposed) [1.1~alpha19-6]
[09:38] -queuebot:#ubuntu-release- Unapproved: openssh (jammy-proposed/main) [1:8.9p1-3ubuntu0.3 => 1:8.9p1-3ubuntu0.4] (core, i386-whitelist)
[09:38] -queuebot:#ubuntu-release- Unapproved: openssh (lunar-proposed/main) [1:9.0p1-1ubuntu8.4 => 1:9.0p1-1ubuntu8.5] (core, i386-whitelist)
[09:46] -queuebot:#ubuntu-release- New binary: ocaml-merlin [amd64] (mantic-proposed/none) [4.7-413-3] (no packageset)
[09:46] -queuebot:#ubuntu-release- New binary: ocaml-merlin [ppc64el] (mantic-proposed/none) [4.7-413-3] (no packageset)
[09:46] -queuebot:#ubuntu-release- New binary: ocaml-merlin [arm64] (mantic-proposed/none) [4.7-413-3] (no packageset)
[09:46] -queuebot:#ubuntu-release- New binary: ocaml-merlin [s390x] (mantic-proposed/none) [4.7-413-3] (no packageset)
[09:50] -queuebot:#ubuntu-release- New binary: ocaml-merlin [armhf] (mantic-proposed/none) [4.7-413-3] (no packageset)
[09:59] <ricotz> doko, https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#libreoffice
[09:59] <ricotz> doko, I meant the autopkgtests excuses
[10:01] <doko> that would be a bug report for britney, trying to run tests for non-existing binaries
[10:10] -queuebot:#ubuntu-release- New binary: ocaml-merlin [riscv64] (mantic-proposed/none) [4.7-413-3] (no packageset)
[10:14] -queuebot:#ubuntu-release- New: accepted ocaml-merlin [amd64] (mantic-proposed) [4.7-413-3]
[10:14] -queuebot:#ubuntu-release- New: accepted ocaml-merlin [armhf] (mantic-proposed) [4.7-413-3]
[10:14] -queuebot:#ubuntu-release- New: accepted ocaml-merlin [riscv64] (mantic-proposed) [4.7-413-3]
[10:14] -queuebot:#ubuntu-release- New: accepted ocaml-merlin [arm64] (mantic-proposed) [4.7-413-3]
[10:14] -queuebot:#ubuntu-release- New: accepted ocaml-merlin [s390x] (mantic-proposed) [4.7-413-3]
[10:14] -queuebot:#ubuntu-release- New: accepted ocaml-merlin [ppc64el] (mantic-proposed) [4.7-413-3]
[13:31] <rs2009> would be great if someone could rebuild ubuntu-unity-desktop (had updated the seed a week ago to include `xserver-xorg-input-libinput`)
[13:32] <rs2009> s/ubuntu-unity-desktop/ubuntu-unity-meta
[18:32] -queuebot:#ubuntu-release- Packageset: Removed libffi7 from i386-whitelist in jammy
[18:32] -queuebot:#ubuntu-release- Packageset: Added llvm-toolchain-17 to i386-whitelist in jammy
[18:32] -queuebot:#ubuntu-release- Packageset: Added python3.12 to i386-whitelist in jammy
[18:35] -queuebot:#ubuntu-release- Unapproved: valgrind-if-available (jammy-proposed/universe) [3.18.1 => 3.18.1] (i386-whitelist) (sync)
[18:40] <ginggs> ricotz: you want ubuntu-release to bump that libreoffice hint, already done for 4:7.5.6~rc2-0ubuntu1, but for next time...
[18:51] <seb128> ginggs, why do we need that hint? why is the infra waiting for results on an infrastructure where the package isn't built?
[18:58] <ginggs> seb128: libreoffice/i386 was put in never_run, but britney keeps expecting a result
[18:58] <ginggs> https://autopkgtest.ubuntu.com/packages/libreoffice/mantic/i386
[18:59] <seb128> can we get britney fixed?
[18:59] <ginggs> i've only seen this problem with this particular package
[19:00] <seb128> still a bug?
[19:02] <ginggs> libreoffice builds arc:all binaries, so it is expected that the autopkgtest will be attempted on i386
[19:02] -queuebot:#ubuntu-release- Packageset: Added valgrind-if-available to i386-whitelist in jammy
[19:03] <seb128> ginggs, for sure libreoffice isn't our only package building arch all binaries and not building on i386...
[19:03] <seb128> that seems like a pretty obvious bug in britney to block on such cases
[19:04] <ginggs> if the libreoffice autopkgtest just failed normally on i386, it wouldn't be a problem
[19:04] <seb128> ginggs, also hinting the test as bad would make britney not wait for result to allow migration no?
[19:05] <ginggs> instead the last times it attempted to run it failed with 'exit code 14' see results from May 4 through May 17
[19:06] <ginggs> seb128: unfortunately not, britney still expects a result
[19:06] <ginggs> so in theis case, the i386 autopkgtest just shows 'Test in progress' until someone hints it
[19:08] <seb128> :-(
[19:08] <seb128> but hints updates are reserved to release members right?
[19:10] <ginggs> seb128: that's correct
[19:11] <seb128> :-(
[19:56] <jbicha> rs2009: done https://launchpad.net/ubuntu/+source/ubuntu-unity-meta/0.14


 Meeting rest of the day, then another at 9am
[09:35] <duflu> So I guess I should say good night
[09:42] <didrocks> seb128: I’m good, and you?
[09:42] <seb128> I'm alright thanks!
[09:57] <duflu> waveform, my Pi 400 is blanking the screen correctly, for now. But I'm reminded of a general problem you can encounter whereby some monitors will soft disconnect when blanking. So that counts as a wakeup event
[09:57] <waveform> duflu, intriguing -- I've only checked it on a cheapo BenQ monitor so far -- I'll see what happens on something a bit fancier!
[12:54] <jbicha> good morning
[12:56] <jbicha> seb128: could you push your gnome-initial-setup upload to the ubuntu/master git? Otherwise, I can run gbp import-dsc for it
[13:00] <seb128> jbicha, do you want me to force push overwrite what is in the vcs?
[13:02] <jbicha> I don't think that should be necessary since you were the last to commit to the ubuntu/master branch
[13:03] <seb128> oh, indeed, I had another checkout
[13:03] <KGB-0> gnome-initial-setup ubuntu/master d0e9180 Sebastien Bacher * pushed 103 commits (first 5 follow) * https://deb.li/FH3F
[13:03] <KGB-0> gnome-initial-setup ubuntu/master 874ade5 Will Thompson NEWS * NEWS for 41.rc * https://deb.li/3OVah
[13:03] <seb128> pushed
[13:03] <KGB-0> gnome-initial-setup ubuntu/master ffc51ff Will Thompson meson.build * Bump version to 40.0 * https://deb.li/zcJ2
[13:04] <KGB-0> gnome-initial-setup ubuntu/master 69045e8 Goran Vidović po/hr.po * Update Croatian translation * https://deb.li/3vXpC
[13:04] <KGB-0> gnome-initial-setup ubuntu/master 8c1711d Emin Tufan Çetin po/tr.po * Update Turkish translation * https://deb.li/3d9J1
[13:04] <KGB-0> gnome-initial-setup ubuntu/master ae25270 Alan Mortensen po/da.po * Updated Danish translation * https://deb.li/ufKd
[14:24] <jbicha> seb128: what do you think about bug 1960954 ?
[14:25] <kenvandine> jbicha: will we not even have libsoup3 in the archive for jammy?
[14:26] <kenvandine> I'm not asking in the context of gvfs, but thinking about the gnome-42 platform snap
[14:27] <jbicha> We often try to avoid having an extra library version in the release, but we could
[14:27] <kenvandine> not the end of the world, i could build libsoup3 as a part in gnome-42-2204-sdk
[14:27] <jbicha> I had WIP packaging of libsoup3. I just need to rebase it on the latest libsoup2 packaging changes
[14:28] <kenvandine> but if packagers not using the gnome platform need it, it could be handy if it was at least in universe
[14:29] <kenvandine> actually, doesn't gnome-software need it?
[14:29] <jbicha> see https://gitlab.gnome.org/GNOME/libsoup/-/issues/218
[14:29] <kenvandine> oh, gnome-software has an option for soup2
[14:29] <kenvandine> they must have added that
[14:30] <kenvandine> i had to build soup3 as a part when i was testing the snap-store-42 branch I was working on
[14:30] <seb129> jbicha, there are little changes in gvfs so either way, update to new serie and revert the libsoup change or stay on old and cherry pick fixes is equivalent
[14:30] <jbicha> it's going to be an awkward transition. I think we'll try to push through a lot of the transition later this year in time for next Debian Stable. Also GNOME 43 might want to push it more.
[17:42] <KGB-2> system-config-printer signed tags 58302dc Jeremy Bicha ubuntu/1.5.15-2ubuntu1 * system-config-printer Debian release 1.5.15-2ubuntu1 * https://deb.li/i4iDl
[17:42] <KGB-2> system-config-printer ubuntu/master 284819e Jeremy Bicha debian/patches/ series Support-GNOME-42-dark-style-preference.patch * Add patch to support GNOME 42 dark theme preference * https://deb.li/3ASjj
[17:42] <KGB-2> system-config-printer ubuntu/master e6b175b Jeremy Bicha debian/ control control.in * debian/control.in: Depend on gir1.2-handy-1 for that change * https://deb.li/FSJN
[17:42] <KGB-2> system-config-printer ubuntu/master 0fdf9b2 Jeremy Bicha debian/changelog * releasing package system-config-printer version 1.5.15-2 * https://deb.li/3ds4x
[17:42] <KGB-2> system-config-printer ubuntu/master e46e53e Jeremy Bicha debian/ (5 files in 2 dirs) * Merge tag 'debian/1.5.15-2' into ubuntu/master * https://deb.li/WYns
[17:42] <KGB-2> system-config-printer ubuntu/master eab997d Jeremy Bicha debian/changelog * releasing package system-config-printer version 1.5.15-2ubuntu1 * https://deb.li/3FifU
[18:42] <KGB-0> rhythmbox signed tags 1127694 Jeremy Bicha ubuntu/3.4.4-5ubuntu1 * rhythmbox Debian release 3.4.4-5ubuntu1 * https://deb.li/SMII
[18:42] <KGB-0> rhythmbox ubuntu/master 759bae4 Jeremy Bicha * pushed 10 commits (first 5 follow) * https://deb.li/3zZiA
[18:42] <KGB-0> rhythmbox ubuntu/master 9b343cc Jeremy Bicha debian/patches/ series mmkeys-Remove-gnome-settings-daemon-MediaKeys-plugin.patch * Cherry-pick patch to remove obsolete GNOME MediaKeys plugin * https://deb.li/3egJc
[18:42] <KGB-0> rhythmbox ubuntu/master 74d821e Jeremy Bicha debian/patches/ series mpris-Make-the-plugin-builtin.patch * Cherry-pick patch to make the replacement MPRIS plugin built-in * https://deb.li/34yKC
[18:42] <KGB-0> rhythmbox ubuntu/master 795373a Jeremy Bicha debian/rhythmbox-plugins.install * debian/rhythmbox-plugins.install: Don't try to install the MediaKeys plugin * https://deb.li/iWjaG
[18:43] <KGB-0> rhythmbox ubuntu/master 477af96 Jeremy Bicha debian/ control control.in rules * Build-Depend on dh-sequence-gir, dh-sequence-gnome, dh-sequence-python3 * https://deb.li/pguM
[18:43] <KGB-0> rhythmbox ubuntu/master a3cca78 Jeremy Bicha debian/ control control.in rules * Bump debhelper-compat to 13 * https://deb.li/3QPRj


[00:00] <nixternal> the rest seemed to have nuked fine
[00:00]  * sistpoty looks
[00:02] <sistpoty> nixternal: no idea actually, but I removed it manually from the db
[00:07] <nixternal> thanks
[00:19] <TomJaeger> .orig.tar.gz is supposed to be the original tarball from upstream, right?
[00:19] <sistpoty> TomJaeger: yes
[00:19] <TomJaeger> why is this not the case for wacom-tools?
[00:20]  * sistpoty looks
[00:22] <sistpoty> TomJaeger: not too sure, I guess for convencience (debian/README.Debian makes me think that). Generally, this should be avoided w.o. a very good reason
[00:24] <TomJaeger> okay, I guess I'll fix that too, while I'm at it
[00:25] <james_w> TomJaeger: at what?
[00:25] <sistpoty> TomJaeger: oh, are you considering to update wacom-tools?
[00:25] <TomJaeger> nobody else is doing it, are they?
[00:26] <sistpoty> TomJaeger: the please head the rule of thumg: do minimal changes to the current package (unless you maintain it)
[00:26] <sistpoty> then
[00:26] <sistpoty> and rule of thumb... bah, I'm no typing expert today
[00:27] <james_w> it's in main isn't it?
[00:28] <TomJaeger> bug #195953
[00:28] <ubotu> Launchpad bug 195953 in wacom-tools "Tablet input resolution tied to display resolution" [Medium,Triaged] https://launchpad.net/bugs/195953
[00:28] <TomJaeger> this is the reason
[00:29] <james_w> TomJaeger: go for it
[00:30] <james_w> TomJaeger: so your update is a new upstream version?
[00:30] <TomJaeger> yeah, but it needs some fixes to even compile
[00:30] <aquo> i am trying to create my own meta-packages ...
[00:30] <sistpoty> TomJaeger: still, try to do minimal changes in packaging, I gues the release team will appreciate this
[00:30] <aquo> with debuild i get the message
[00:30] <aquo> bad-distribution-in-changes-file gutsy
[00:31] <aquo> i have gutsy in my changelog, is this wrong?
[00:31] <james_w> aquo: do you have "ubuntu" in the version number?
[00:31] <sistpoty> aquo: last entry in debian/changelog: change "gutsy" to "hardy"
[00:31] <TomJaeger> sistpoty, I'm still moving that autoconf-garbage out of the diff
[00:31] <james_w> aquo: are you compiling for gutsy?
[00:31] <aquo> james_w: no, i think i will put ppa in
[00:31] <aquo> james_w: yes
[00:32] <aquo> james_w: i dont have ubuntu in the version number
[00:33] <aquo> sistpoty: but i don't want to make the metapackage for hardy, i want i to be for gutsy.
[00:33] <sistpoty> aquo: are you sure? (once hardy gets out, I doubt that too many gutsy systems will remain)... but if so, ignore the warning ;)
[00:34] <aquo> sistpoty: it is not a warning, is is marked E:
[00:34] <james_w> I think this is just for personal use isn't it?
[00:34] <sistpoty> aquo: by what?
[00:34] <aquo> by debuild
[00:34] <aquo> E: aquo-packaging_0.1_i386.changes: bad-distribution-in-changes-file gutsy
[00:34] <sistpoty> aquo: are you using a debuild from before gutsy?
[00:34] <james_w> aquo: instead of 0.1-1 have 0.1-0ubuntu1
[00:35] <aquo> no
[00:35] <sistpoty> hm...
[00:35] <sistpoty> aquo: from debian?
[00:35] <aquo> no, just from scratch.
[00:35] <james_w> I think there's a safety catch added in Ubuntu to stop you uploading packages to Ubuntu with "Debian" version numbers.
[00:35] <aquo> it is just an README with some created debian/ directory ...
[00:35] <james_w> as it -1 etc.
[00:35] <sistpoty> aquo: hm... do you have some triggers in debuild that require a clean lintian run?
[00:36] <aquo> no, but i want to do it the right way ...
[00:36] <aquo> if i create a metapackage from scratch, which version number do i need to give?
[00:36] <james_w> aquo: i suggest 1
[00:36] <aquo> should it be 0.1-1?
[00:36] <aquo> or is 0.1 ok?
[00:37] <james_w> or maybe it has to be 1ubuntu1
[00:37] <james_w> or 0.1-0ubuntu1
[00:37] <james_w> or 0.1ubuntu1
[00:37] <sistpoty> james_w: right, now I recall some completely and utter stupid changes back then, which derive the distribution from the version number
[00:37] <Flannel> It only gets the ubuntuX wart if its modified from virgin source
[00:38] <sistpoty> so it would be 1ubuntu1 (for a metapackage, which I guess should be native)
[00:38] <aquo> james_w: i don't want to have it ubuntu in the version, i am just going for ppa
[00:38] <aquo> so 1ppa1 ...
[00:38] <Flannel> sistpoty: -1ubuntu1  implies theres been one debian modification, and then one ubuntu modification ontop of that
[00:38] <Flannel> aquo: The metapackage is for the 0.1 version of the software, right?
[00:39] <james_w> aquo: I'm trying to tell you that I think it's the fact that you don't have ubuntu in the version number that is giving you the error
[00:39] <Flannel> james_w: I think thats wrong
[00:39] <sistpoty> Flannel: it doesn't really matter for a metapackage... either 0ubuntu1 or 1ubuntu1 (as debian probably won't sync that one)
[00:39] <aquo> Flannel: i just created a metapackage (just a README-file) f
[00:39] <Flannel> Not that I'm an expert, but I would've given it the 0.1 version, and been done with it.
[00:39] <aquo> for the dependencys ...
[00:39] <aquo> there is no real source ...
[00:39] <sistpoty> (oh, and sorry for my wording about the changes... of course I should have written "not so prudent" or s.th. like that)
[00:40] <sistpoty> Flannel: to be correct, 0.1 would (iirc) be a nmu of a debian native package in debian
[00:40] <aquo> it is a native package, but it is native to ubuntu
[00:41] <Flannel> sistpoty: No, it's the 0.1 version from upstream, 0.1-1 would be one debian change
[00:41] <sistpoty> Flannel: not for a *native* package
[00:41] <Flannel> aquo: http://packages.ubuntu.com/gutsy/ocaml-libs is an example of a metapacakge with no warts, so it's definately not a requirement
[00:42] <sistpoty> Flannel: rule of thumb: no dash in the version number -> native package
[00:42] <Flannel> sistpoty: Have an example?
[00:42] <Flannel> sistpoty: the one I just gave, actually, has no dash
[00:42] <sistpoty> Flannel: exactly ;)
[00:43] <Flannel> sistpoty: http://packages.debian.org/search?keywords=ocaml-libs&searchon=names&suite=testing&section=all
[00:43] <Flannel> sistpoty: Its not native
[00:43] <Flannel> er, ok, so its the etch version, but still, not native
[00:43] <sistpoty> Flannel: why would it be not native?
[00:44] <Flannel> sistpoty: What are you defining native as?
[00:44] <sistpoty> Flannel: native == "no orig.tar.gz"
[00:44] <Flannel> So, all metapackages are native then, by definition?
[00:44] <aquo> ubuntu-meta has "ubuntu-meta (1.79) gutsy; urgency=low"
[00:44] <sistpoty> Flannel: yes
[00:46] <Flannel> sistpoty: I took native to be Ubuntu created.  If a metapackage has a change from debian's, is it -0ubuntu1?
[00:47] <aquo> -Xubuntu1
[00:47] <TomJaeger> sistpoty, so I think the reason they repacked it is because the debian/ubuntu package is called wacom-tools and upstream calls it linuxwacom
[00:47] <sistpoty> Flannel: there is no real policy... the right thing imho would be to create a non-native package from it, but that also has its problems. So I usually go for Xubuntu1 (being X the debian version)
[00:48] <aquo> sistpoty: ubuntu-meta is also a "native"-package in my eyes.
[00:48] <sistpoty> aquo: yes, it is
[00:48] <aquo> so, how do i get rid of the E: aquo-packaging_0.1_i386.changes: bad-distribution-in-changes-file gutsy message?
[00:49] <TomJaeger> sistpoty, so I'll do the same thing
[00:49] <sistpoty> aquo: have you tried adding "ubuntu1" to the (last) version in debian/changelog?
[00:50] <sistpoty> TomJaeger: have you checked, if there was actually just a rename of the original version, or if it has been otherwise fiddled with as well?
[00:51] <sistpoty> brb
[00:51] <aquo> sistpoty: i tried ppa1
[00:51] <aquo> E: aquo-packaging_0.1ppa1_i386.changes: bad-distribution-in-changes-file gutsy
[00:52] <TomJaeger> sistpoty, everything has been moved to a linuxwacom and there's a strange doc dir
[00:52] <TomJaeger> *linuxwacom subdir*
[00:53] <james_w> aquo: I doubt ppa will make any difference if the issue is what I think it is, as ppas weren't around then.
[00:53] <TomJaeger> how are renames usually handled?
[00:54] <james_w> just in the packaging usually
[00:54] <aquo> james_w: ok, with ubuntu1 the Error-Message is gone
[00:54] <james_w> it doesn't really matter what's going on in the source package as long as the binary packages come out ok
[01:02] <sistpoty> james_w: *cough*.. https://wiki.ubuntu.com/PackagingGuide/Basic#ChangingOrigTarball (though if it's screwed once, you'll have a hard time for a new upstream version)
[01:02] <sistpoty> (that was actually written by me, in case you wonder)
[01:04] <james_w> heh, preaching to the choir :-)
[01:04] <sistpoty> :)
[01:09] <sistpoty> soren: can you attach the usual information for bug #208161 please? thanks!
[01:09] <ubotu> Launchpad bug 208161 in ubuntu-vm-builder "FFe: Update ubuntu-vm-builder" [Undecided,Incomplete] https://launchpad.net/bugs/208161
[01:11] <TomJaeger> is there a way to make dpkg-buildpackage show the current directory?
[01:12] <james_w> what do you mean?
[01:26] <james_w> sistpoty: thanks for the ack on the bzr* FFe
[01:27] <sistpoty> james_w: you'll still need to get the ack from main (until mine gets valid)
[01:27] <sistpoty> james_w: as I understand it, there is a tight correlation between bzr and bzr-tools, right?
[01:28] <james_w> yeah, they all need to go in together
[01:28] <aquo> so, the basic for my metapackage seems to work ...
[01:28] <james_w> I realise it's not complete yet, but it's good to have that but done
[01:28] <aquo> it is nice to have those metapackages for software installation ;)
[01:28] <sistpoty> james_w: yes, that's what I thought... so basically my opinion is: if one goes into main, the others should follow ;)
[01:29] <aquo> but: if i change anything inside my metapackage: do i change the native version or the ubuntu one?
[01:29] <aquo> if i use dch -i ubuntu counts up ....
[01:29] <aquo> hmmm
[01:30] <sistpoty> aquo: for native packages, the complete version is the version of the package
[01:30] <aquo> sistpoty: grmpf
[01:30] <Laney> james_w: I started a wiki page about the packaging jam: https://wiki.ubuntu.com/UKTeam/PackagingJamJune2008 - feel free to edit :)
[01:30] <james_w> thanks Laney
[01:30] <sistpoty> aquo: because there's no .orig.tar.gz, every new version is put in a (native) .tar.gz again
[01:31] <aquo> sistpoty: but i had to introduce the ubuntu1 to get the error message away ...
[01:31] <sistpoty> aquo: hence changing either the version number, or the X after ubuntuX will result in the same thing packaging wise
[01:31] <james_w> Laney: looks good, do you want to email the list to tell everyone about it.
[01:32] <james_w> Laney: also, there's no mention of the possible Bug Jam.
[01:32] <Laney> james_w: I'll add that. You can email the list if you'd like or I'll try and get round to it tomorrow
[01:32] <sistpoty> aquo: the usual thing for debian imported native packages is to increase X though (as in <version>ubuntuX becomes <version>ubuntuX+1)
[01:33] <sistpoty> (X+1 as expression *g*)
[01:33] <aquo> ok, but i didn't import anything from debian
[01:33] <james_w> Laney: we're in to the time where I won't let myself send email for fear of saying something stupid due to tiredness, so it would be tomorrow anyway
[01:33] <aquo> i created a native metapackage for ubuntu
[01:33] <james_w> Laney: so if you don't do it tomorrow I can
[01:33] <sistpoty> aquo: but since you have an ubuntu version number, just increase X ;()
[01:33] <Laney> james_w: That's fine
[01:33] <sistpoty> -(
[01:34] <aquo> if i  mv aquo-packaging-0.1/ aquo-packaging-0.2 and run dch -i inside it, it prompts me with 0.1ubuntu2 ...
[01:35] <sistpoty> aquo: yes, that's correct... for native packages, the source package == upstream package
[01:35] <sistpoty> aquo: so usually you don't move the debian dir around, but just add to the existing package
[01:35] <sistpoty> (s/usually/always)
[01:36] <aquo> sistpoty: there is no debian-dir, i just created this for myself from scratch, understand?
[01:36] <aquo> it is a native metapackage for ubuntu.
[01:37] <sistpoty> aquo: w.o. debian dir, you cannot build a package?
[01:37] <sistpoty> aquo: I guess we're misunderstaning here
[01:39] <aquo> sistpoty: ok, i have a ubuntu native metapackage directory named aquo-packaging-0.1 with some debian-directory inside it with all the control stuff ...
[01:40] <aquo> because of some freaky error-message i had to intruduce the ubuntu1 version in changelog.
[01:40] <aquo> if i run dch -i inside the directory ubuntuX counts up ...
[01:40] <sistpoty> aquo: yes, that's correct
[01:40] <aquo> but this is a native package, so i want the native version number to count up ...
[01:41] <aquo> a can hand-edit this, but why use dch -i if i need to hand-edit stuff?
[01:42] <james_w> aquo: try dch -U
[01:42] <sistpoty> aquo: the native version == what is in debian/changelog
[01:42] <james_w> that should get rid of this "ubuntu" check
[01:42] <james_w> (I think)
[01:42] <sistpoty> aquo: if you put 1.2ubuntu3 there, the native version is exactly this
[01:43] <aquo> no it isn't
[01:43] <sistpoty> aquo: if you want to increase 1.2ubuntu3 to 1.3ubuntu1, you'll need to hand edit the file
[01:43] <aquo> i am the "upstream"-maintainer and the packager in one person.
[01:43] <sistpoty> aquo: yes, that's what "native package" is all about ;)
[01:45] <aquo> ok, it seems that nobody seems to understand my question.
[01:46] <sistpoty> aquo: at least, I don't... maybe you could rephrase it again=
[01:47] <sistpoty> ?
[01:47] <james_w> aquo: dch -v will allow you to specify the version that you want
[02:25] <bddebian> Heya gang
[02:25] <protonchris> hey bddebian
[02:25] <mneptok> bddebian: heya
[02:25] <bddebian> Hi protonchris, mneptok
[02:28] <sistpoty> hi bddebian
[02:29] <bddebian> Heya sistpoty
[02:37] <TomJaeger> alright, I've updated the wacom-tools package now, who do we get this uploaded?
[02:38] <james_w> TomJaeger: you need a core-dev sponsor
[02:39] <TomJaeger> how would I find a core-dev sponsor?
[02:41] <Fujitsu> Hmmm. Something has caused several duplicates of a rather old soundconverter bug to be filed in the past few days. There were no duplicates for 30k bugs, then 7 in just a couple of thousand.
[02:41] <james_w> you should subscribe ubuntu-main-sponsors, but I'm afraid that I don't know the format that they wnat new upstream versions in
[02:41] <james_w> TomJaeger: also have you applied for a Freeze exception?
[02:41] <TomJaeger> no
[02:42] <james_w> I think you'll need to do that. I'm not very familiar with main, sorry
[02:42] <james_w> you can see if anyone is around on #ubuntu-devel
[02:42] <TomJaeger> so I'm wrong here?
[02:43] <james_w> no, not exactly, but motu only look after universe
[02:43] <james_w> there's more likely to be core-dev on that channel than this
[02:44] <TomJaeger> alright, thanks
[02:46]  * sistpoty is off to bed now.. gn8
[02:47] <james_w> night sistpoty
[02:47] <sistpoty> gn8 james_w
[02:47] <james_w> TomJaeger: you should probably explain that you are trying to make an upload and you want details on whether you need a freeze exception, and how to get sponsorship of a new upstream version.
[03:17] <cody-somerville> Fujitsu, Can we get the logbot back in #xubuntu-devel? I dunno why it disappeared.
[03:18] <ScottK2> cody-somerville: You gotta do 5 u-u-s uploads in the next day now that you're MOTU. Congratulations.
[03:18] <Fujitsu> cody-somerville: I've no idea.
[03:18] <Fujitsu> cody-somerville: Nothing to do with me.
 Thanks ScottK2 :)
[03:18] <cody-somerville> Fujitsu, I thought you were the one that maintained it. My mistake.
[03:19]  * Fujitsu feels like he's doing 5-(non-)FFes-a-day
[03:19] <Fujitsu> cody-somerville: fabbione, perhaps.
[03:19] <cody-somerville> Right right
[03:19] <cody-somerville> :)
[03:19]  * ScottK2 feels like he's d0ko's release assistant chasing after python-xml removal and python-central build-dep fixes.
[03:23] <Fujitsu> ScottK2: And then there's LDFLAGS...
[03:24] <ScottK2> Was that his too?
[03:24] <Fujitsu> Of course.
[03:24] <Fujitsu> And there was something else too.
[03:24] <Fujitsu> I forget.
[03:25] <Fujitsu> Ah, yes, starting the gfortran transition.
[03:25] <ScottK2> Ah.  Well the last act for python-xml is assigned to him, so I'm done on that one.
[03:26] <Fujitsu> Very good.
[03:26] <ScottK2> It's milestoned against the release too.
[03:27] <ScottK2> ;-)
[03:30] <protonchris> Anybody up for looking at a FFE (Bug 204039)?
[03:30] <ubotu> Launchpad bug 204039 in glom "Hardy: Please update to glom 1.6.10" [Undecided,New] https://launchpad.net/bugs/204039
[03:32] <ScottK2> protonchris: Looking
[03:33] <slangasek> heh, glom still isn't done?  any time we could clear libgdamm off of http://people.ubuntu.com/~ubuntu-archive/NBS/ would be just peachy :)
[03:34] <protonchris> slangasek: Hopefully glom will be done with the next release.  Sorry.
[03:35] <ScottK2> protonchris: The current version is FTBFS or dep wait on several archs.  Will this one be any better?
[03:38] <ScottK2> protonchris: I don't see any features in that release.  It looks like just bugfixes to me, so no FFe needed.
[03:40] <protonchris> ScottK2: Looks like hppa is hung up on python-gnome2-extras and python-gtk2
[03:40] <protonchris> ScottK2: sparc stuck on python-gnome2-extras
[03:40] <ScottK2> hppa is often stuck on stuff.  Would a giveback on sparc work at this point?
[03:44] <protonchris> ScottK2: not sure.  I am new to this.  What does a giveback mean?
[03:45] <ScottK2> Try to build it again.
[03:45] <ScottK2> Is the python-gnome2-extras problem sorted out already?
[03:48] <protonchris> It is not clear to me why it didn't work on sparc before since it looks like sparc has python-gnome2-extras
[03:48] <ScottK2> protonchris: Maybe it didn't then
[03:48] <ScottK2> Or it's not in sufficient version
[03:48] <protonchris> slangasek: what causes a package show up on that webpage?
[03:50] <slangasek> protonchris: it's no longer built from any current source package, but still in the archive
[03:51] <protonchris> ScottK2: yeah, strange.  Lets try a giveback on sparc if it isn't too much trouble.
[03:51]  * cody-somerville just made his first upload :)
[03:51] <ScottK2> cody-somerville: Congratulations again.
[03:51] <cody-somerville> :)
[03:52] <ScottK2> protonchris: Since we're contemplating a new upload, that'd take care of it.
[03:52] <ScottK2> protonchris: What about the dep wait on ia64?
[03:54] <ScottK2> protonchris: What do we have to do for libgda3-dev 3.0.2 or better to be available on that arch?
[03:56] <protonchris> ScottK2: it is waiting on libgda3-dev which segfaults during building.  segfault problem also exists in debian.
[03:57] <PMantis> Hello! I setup my own repo (dpkg-scanpackages, apt-ftparchive) and with a proper sources.list file. However, if I create a Release.gpg, apt-get complains on the clients: Failed to fetch http://<path>/Release  What did I do wrong?
[03:57] <PMantis> Guess I didn't finish my first thought....
[03:58] <ScottK2> protonchris: So I'd try and look into that one.
[03:58] <protonchris> ScottK2: ok, I'll ask the debian maintainer about it.
[03:58] <ScottK2> OK.
[03:58] <slangasek> libgda-3.0-scan.c:18: warning: implicit declaration of function 'gda_blob_op_get_type'
[03:58] <slangasek> protonchris, ScottK2: how about setting a proper prototype? :)
[03:59] <ScottK2> Fair enough.
[03:59] <slangasek> I bet that returns a pointer and ia64 goes waaaaa
[03:59] <PMantis> Better stated: Without the Release.gpg all is ok, except the security warning when Installing packages. With the Release.gpg file in my repository, 'apt-get update' chokes. Yes, I've imported the gpg key using apt-key.
[04:00]  * ScottK2 is trying to help point protonchris is a useful direction without getting his hand's to sticky with the goo from this one.
[04:00] <slangasek> heh
[04:00] <protonchris> slangasek: :)
[04:01] <protonchris> Actually that was meant for ScottK2
[04:02] <slangasek> ./libgda/gda-blob-op.h:GType    gda_blob_op_get_type  (void);
[04:02] <slangasek> I win
[04:03] <slangasek> unfortunately, I also lose, because I can never remember where the source for those scanners is supposed to come from. :P
[04:05] <protonchris> ScottK2: thanks for looking at the glom bug
[04:06] <ScottK2> protonchris: You're welcome.  I think you've got enough of a hint that you can go to the Debian maintainer and he can figure a patch if you aren't up to it yourself.
[04:06] <joejaxx> what is an FFe?
[04:06] <ScottK2> Feature Freeze Exception (replace UVFe since we don't have UVF anymore).
[04:07] <joejaxx> oh ok
[04:07] <ScottK2> Hello joejaxx
[04:07] <joejaxx> hi
[04:07] <ScottK2> joejaxx: It was suggested to me that I hunt you down to help out with unforking our SE Linux stuff.
[04:08] <joejaxx> oh ok
[04:08] <ScottK2> joejaxx: I'm expecting Manoj to upload a new setools to Debian in the next ~36 hours.
[04:09] <joejaxx> ok
[04:09] <ScottK2> Personally I'd rather break SE Linux than fork, so it'd be good to have someone involved that actually cares how well it works.
[04:09] <joejaxx> :)
[04:10] <ScottK2> joejaxx: See Bug 204428 for my perspective.
[04:10] <ubotu> Launchpad bug 204428 in setools "Package contains gratuitous divergence from Debian" [Undecided,In progress] https://launchpad.net/bugs/204428
[04:11]  * joejaxx looks
[04:13] <joejaxx> ScottK2: is this for hardy?
[04:13] <joejaxx> i am guessing
[04:13] <ScottK2> Yes
[04:14] <ScottK2> joejaxx: If we release with our renamed packages we'll have to carry transitional packages all the way to the next LTS release.  It'd be good not to have to maintain that diff.
[04:15] <joejaxx> yeah
[04:15] <joejaxx> hmm
[04:18] <joejaxx> ok
[04:18] <joejaxx> i will try and take a look at the diff when Manoj uploads
[04:18] <joejaxx> as well :)
[04:19]  * joejaxx wish he was not having bzr problems still :\
[04:20] <joejaxx> well i am going to retire for the evening
[04:20] <joejaxx> Goodnight All :)
[04:23] <slangasek> protonchris: http://people.ubuntu.com/~vorlon/libgda3-ia64-segv.diff is the fix for libgda3's build failure on ia64
[04:24] <protonchris> slangasek: should I submit a new package or pass that along to the debian maintainers.
[04:24] <ScottK> protonchris: Make us a debdiff and send it to Debian.
[04:25] <protonchris> ScottK: ok.  I'll tackle this tomorrow.  Thanks.
[04:27] <protonchris> slangasek: I hope to get libgdamm of your bad list soon.  :)
[04:27] <protonchris> of -> off
[04:28] <slangasek> appreciated :-)
[04:32] <Fujitsu> Thanks ScottK.
[04:36] <protonchris> I am going to go to bed.  Thanks for your help.
[04:40] <cody-somerville> StevenK, Can you add me to u-u-s?
[04:50]  * persia comes late to the party, and notes that an NMU of debian-native 0.1 is 0.1-0.1
[04:50] <persia> cody-somerville: I'll do that.  Thanks for helping.
[04:50] <cody-somerville> persia, Thanks.
[04:50] <cody-somerville> So, whats the command to sign the .changes file correctly?
[04:50] <persia> debuild -S
[04:51] <cody-somerville> Right but if I'm sponsoring someone else's upload
[04:51] <cody-somerville> Don't I have to do something extra since I can't actually sign as them?
[04:52] <Fujitsu> -k<yourkeyid>
[04:52] <persia> Ah.  If you're sponsoring someone else's upload, use `debuild -S -k<keyid>`.  That gives them Changed-By: credit, with your signature.
[04:52] <persia> cody-somerville: https://launchpad.net/%7Ecody-somerville/+participation
[04:53] <cody-somerville> :)
[05:12]  * Fujitsu takes a deep breath, and tries a Dapper->Hardy upgrade.
[05:12] <ScottK2> Three cheers for Fujitsu
[05:13] <Fujitsu> Anybody else who's tried it? Anything I need to know?
[05:13]  * ScottK2 tried Dapper -> Gutsy once.
[05:13] <ScottK2> It didn't end well.
[05:13] <persia> My memory is that upstart can bite, but that may have been fixed.
[05:14] <Fujitsu> I presume it works a bit by this point in the cycle.
[05:14] <ScottK2> Actually it turns out it was largely OK (eventually), but by the time I realized I was having problems unrelated to the upgrade I'd alread nuked it.
[05:14] <jdong> Fujitsu: I've heard someone else here with 3 of 3 failures
[05:14] <jdong> Fujitsu: though from what I've heard, none of the failures were irrecoverable.
[05:15] <jdong> more like they weren't spotless out of the box....
[05:15] <jdong> which admittedly sounds like doublespeak for failure ;-)
[05:15] <Fujitsu> I've done a few stupid multi-release upgrades, but have always managed to recover from the breakage.
[05:16] <jdong> I don't think it's anything we can't recover from
[05:17]  * jdong wonders how many hours is 600,000 centisecs....
[05:18] <jdong> 1.67
[05:18] <jdong> I wonder if that's too greedy a pdflush writeback time :D
[06:38] <warp10> Good morning
[09:34] <\sh> moins
[09:38] <\sh> mah I does not like people who are touching my bugs which I'm assigned to
[09:39] <geser> Hi \sh
[09:39] <persia> touching?  How?  While I tend to agree, I never complain if someone milestones it, or someone leaves a comment with insight.
[09:42] <\sh> persia: I mean changing status to something else....I'm assigned to the bug becasue I'm working on it. Problem is...this bug can't be confirmed, because it's just an good will of upstream to inform us that they compiled a patch list where at least 10 crashers (two of them were reported from ubuntu)..anyways...there is nothing to be confirmed to...because it deals with known bugs...and I don't like people who are just passing by to deal with those bugs
[09:42] <\sh> bah,.../me needs coffee and some roles from the bakery
[09:42] <\sh> brb
[09:42] <persia> \sh: Yeah.  I tend to agree with that.  When you wake up, might say something in #ubuntu-bugs...
[09:51] <\sh> re
[09:57] <\sh> hah..-.breakfast is doing good to my system
[10:29] <DRebellion> When can I start uploading packages for hardy+1?
[10:33] <jpatrick> DRebellion: when the toolchain is uploaded
[10:33] <harrisony> iirc as soon as hardy gets into final freeze
[10:33] <harrisony> im wrong :P
[10:34] <DRebellion> jpatrick, any rough date set for that?
[10:34] <jpatrick> DRebellion: https://wiki.kubuntu.org/IntrepidReleaseSchedule
[10:34] <Fujitsu> Perhaps mid-May.
[10:34] <jpatrick> DRebellion: May 1st
[10:35] <DRebellion> jpatrick, thanks
[10:36] <Iulian> G'morning
[10:37] <jpatrick> moin Iulian
[10:37] <Iulian> Hey jpatrick
[10:38] <jpatrick> brb - TZ update
[10:40] <\sh> well, you can test already your packages with a hardy package of the toolchain stuff from ubuntu-toolchain team...
[10:58] <\sh> phew claws-mail fixed and uploaded
[11:05] <Fujitsu> Is there any reason we have kfreebsd-5 in the archive, other than automatically importing it from Debian?
[11:06] <Fujitsu> It's probably pretty useless, and appears to have some open security issues.
[11:06] <\sh> hmm...
[11:06] <\sh> UbuntuBSD ... that would rock ,->
[11:07] <\sh> pushing upstart and friends to bsd...merging ports system to .deb oh man...our bsd friends will love us ;)
[11:29] <RainCT> Hi
[11:29] <\sh> moins RainCT
[11:31] <jeromeg> could someone of motu-sru have a look at bug 156432 ?
[11:31] <ubotu> Launchpad bug 156432 in zim "Zim freeze when create a link" [Undecided,Triaged] https://launchpad.net/bugs/156432
[11:31] <jeromeg> please :)
[11:35] <\sh> jeromeg: can you follow https://wiki.ubuntu.com/StableReleaseUpdates and prepare some more infos?
[11:36] <jeromeg> \sh: what is missing ?
[11:37] <jeromeg> impact: crash
[11:37] <jeromeg> how it has been adressed: with a new version
[11:37] <jeromeg> patch: attached
[11:39] <jeromeg> sorry got to go to have lunch
[11:39] <jeromeg> will come back later
[11:40] <\sh> jeromeg: so you just need someone who is uploading it to gutsy-proposed...
[11:40] <jeromeg> \sh: ok
[11:40] <jeromeg> thank you for your help
[11:40] <jeromeg> see you
[11:51] <bobbo> RainCT; i jumped in and did a fix for bug #184084 in diggler, is that ok?
[11:51] <ubotu> Launchpad bug 184084 in tabextensions "Extension description mentions Iceweasel/Icedove/Iceape" [Low,Confirmed] https://launchpad.net/bugs/184084
[11:52] <RainCT> bobbo: sure, thx for working on it :)
[11:53] <RainCT> bobbo: the short description says " utilities for Seamonkey and Firefox's location bar
[11:53] <RainCT>  utilities for Seamonkey and Firefox's location bar
[11:53] <RainCT> (oops)
[11:54] <RainCT> * bobbo: the short description says " utilities for Seamonkey  and Firefox's location bar
[11:54] <RainCT> argh damn irssi xDD
[11:54] <bobbo> ah crap i left in an extra space?
[11:54] <RainCT> bobbo: the short description mentions both Seamonkey and Firefox, but it has no alternative dependency on seamonkey
[11:54] <zorglu_> q. before i found a channel with the ubuntu people which take care about all the server/mirror to store the .deb of ubuntu. i dont remember the name tho... anybody got suggestion?
[11:55] <\sh> zorglu_: ?? you have a mirror or want to setup one?
[11:56] <zorglu_> \sh: i want to talk to the people who handle this. i got no mirror to propose. i just want information
[11:56] <bobbo> RainCT; ah, i just search & replaced it and Iceweasel and Iceape must have both been mentioned
[11:56] <zorglu_> \sh: i talked to somebody sometime ago on this channel i dont remember the name :)
[11:57] <\sh> zorglu_: hmm...depends on the question it could be #ubuntu-devel (most likely you'll have a better chance on monday) or #canonical-sysadmin (also more likely on monday)
[11:58] <\sh> but you can ask here too...eventually we know the answer
[11:58] <zorglu_> \sh: ok i remember the personn was from canonical. but not on those channel. i will retry on monday then
[11:58] <RainCT> bobbo: well, just add seamonkey as an alternative dependency and it should be ok
[11:58] <bobbo> RainCT, ok, thanks
[11:58] <\sh> zorglu_: what's your problem anyways?
[11:58] <RainCT> * seamonkey-browser rather
[11:59] <zorglu_> \sh: well this is a long discussion :) not a yes/no question, so i think i will not trouble people here with irrelevant talks :)
[11:59] <\sh> zorglu_: ok then :)=
[11:59] <jpatrick> zorglu_: https://help.ubuntu.com/community/InternetRelayChat - has a list of ubuntu channels
[11:59] <jpatrick> zorglu_: porbably #ubuntu-mirrors
[11:59] <zorglu_> jpatrick: ahhhh that's the one :)
[12:00]  * \sh steps out for a while....
[12:00] <zorglu_> jpatrick: \sh: thanks for your help
[12:02] <bobbo> RainCT; if im adding seamonkey to the diggler depends, do we still need mozilla-browser?
[12:03] <RainCT> bobbo: ahh right, mozilla-browser = seahorse-browser
[12:03] <RainCT> bobbo: no, delete mozilla-browser then (replacing it for seahorse-browser)
[12:04] <RainCT> *seamonkey-browser
[12:04]  * RainCT thinks he should go sleep some longer lol
[12:04] <bobbo> RainCT; seahorse is the gnome GPG frontend :/
[12:04] <bobbo> hehe :)
[12:12] <bobbo> RainCT; i stuck a new debdiff up, if your not asleep
[12:15] <RainCT> bobbo: diggler (0.9-14ubuntu2) feisty; urgency=low
[12:16] <bobbo> RainCT; http://bobbo.mooo.com/~bobbo/diggler_0.9-14ubuntu2.debdiff
[12:19] <RainCT> asac: could you have a fast look at the debdiff above to be sure that I'm not overlooking anyting please? :P
[12:25] <asac> RainCT: if it works then its fine :)
[12:25] <asac> the debdiff looks rather trivial
[12:25] <asac> is that an extension?
[12:26] <RainCT> asac: yes
[12:26]  * RainCT is just doing stupid stuff today so I better ask before uploading anything :)
[12:26] <asac> hehe
[12:30] <RainCT> bobbo: *gettingsourcechecking&uploading* :)
[12:30] <bobbo> thanks :)
[12:35] <RainCT> bobbo: Uploaded. Thanks for contributing to Ubuntu
[14:03] <protonchris> Can anyone point me to a package with an arch specific patch?
[14:05] <james_w> protonchris: does the package you are working on use a patch system?
[14:05] <james_w> also, why does it need to be arch specific?
[14:07] <protonchris> Well, it is a FTBFS on ia64.
[14:08] <james_w> yes, but it's rare that a patch needs to be arch specific
[14:08] <james_w> for instance it would never be accepted upstream, and so Ubuntu would have to carry it until upstream fixed it properly
[14:09] <james_w> it should be possible to write a patch that only has an effect on ia64
[14:09] <james_w> can you describe the issue? or just point to the build log?
[14:10] <protonchris> sure.  one second
[14:11] <protonchris> http://launchpadlibrarian.net/12660577/buildlog_ubuntu-hardy-ia64.libgda3_3.0.2-2_FAILEDTOBUILD.txt.gz
[14:11] <protonchris> I'll try applying the patch to all arches and see what happens.
[14:12] <james_w> protonchris: so what does the patch do
[14:12] <james_w> ?
[14:13] <james_w> was this the package that slangasek said would probably be fixed by defining function prototypes?
[14:13] <civija> guys sorry for offtopic but maybe someone here would know or point me in right direction. who do I need to contact to get my LoCo team web page included here http://www.ubuntu.com/support/community/locallanguage? tnx
[14:14] <protonchris> james_w: yeah, I think so.
[14:14] <james_w> civija: is you LoCo approved?
[14:14] <james_w> protonchris: can you pastebin the patch please?
[14:14] <civija> james_w: yes, we exist over 2 years
[14:15] <civija> james_w: we also provide local support on forum, irc, ...
[14:15] <james_w> civija: #ubuntu-locoteams might be a better place
[14:15] <civija> james_w: ok, tnx!
[14:15] <protonchris> james_w: looking at the patch I don't see why it would work on all arches.
[14:16] <protonchris> james_w: http://people.ubuntu.com/~vorlon/libgda3-ia64-segv.diff
[14:17] <james_w> protonchris: you don't see why it would work on all arches, or you don't see why it wouldn't?
[14:17] <james_w> I would hate to think what is in that header if including it causes failures on other arches.
[14:17] <protonchris> james_w: wouldn't :)
[14:18] <james_w> I agree, so I think add it and then check it still builds on your machine
[14:18] <james_w> I assume you don't have an ia64?
[14:18] <protonchris> james_w: no I don't
[14:18] <protonchris> james_w: you don't happen to have one, do you?
[14:18] <james_w> nope
[14:19] <james_w> I think you should be pretty safe throwing this one at the buildds if it still builds on your machine
[14:20] <protonchris> james_w: general question:  The patch is only requred for ia64.  So we are essentially fixing something that isn't broke on all the other arches by applying it.  I figured packages changes should be kept to a minimum.
[14:20] <protonchris> james_w: hence my arch specific question earlier.
[14:21] <james_w> yes, but it's actually something bad on all arches, but it just happens to only cause trouble on ia64 due to the sizes of different types
[14:21] <protonchris> Ah.  Good point.  Thanks.
[14:21] <james_w> and I think that the minimal change is actually to apply it on all arches
[14:22] <james_w> it's more work to make it only apply on one, and is just confusing
[14:22] <james_w> protonchris: was this reported to Debian as well?
[14:23] <james_w> it's not reported
[14:23] <protonchris> yeah, I am going to make a debdiff for us and pass the patch on to the debian maintainer.
[14:23] <protonchris> I will be reported to debian.
[14:23] <protonchris> I -> it
[14:23] <protonchris> Once I am sure that the patch fixes the problem.
[14:24] <james_w> ah, http://buildd.debian.org/fetch.cgi?&pkg=libgda3&ver=3.0.2-2&arch=ia64&stamp=1204633860&file=log
[14:24] <james_w> yeah, that's the right approach
[14:24] <james_w> you can point them to that. It does fail on Debian, it just hasn't been processed and a bug filed yet
[14:25] <protonchris> Yeah, I noticed the debian problem a little while ago and thought they might fix it.  Then we could sync again, but I think we are running out of time.
[14:27] <protonchris> james_w: thanks for your help.
[14:28] <james_w> yeah, the best thing to do at this point is to patch it and send it upstream. It can be synced after release with only a little more effort
[14:28] <james_w> no problem
[14:44] <protonchris> When changing a debian package should the following control file fields be removed: Uploaders, DM-Upload-Allowed, Vcs-Browser, and Vcs-Svn ?
[14:53] <Exfil> i need some help setting up virtual hosts on apache can anyone help?
[15:05] <james_w> protonchris: no, maybe, yes, yes
[15:06] <james_w> Exfil: #ubuntu is for support
[15:06] <james_w> protonchris: the second has no meaning here, so it wouldn't hurt to keep it, the last two would giving bad information though, so they should be removed or modified
[15:21] <ScottK2> Exfil: You can get server specifiy support on #ubuntu-server.
[15:22] <ScottK2> protonchris: The patch that slangesek gave you is good for all archs.  ia64 is more picky, which is why it only FTBFS, but it's a good change all the way around.
[15:23] <ScottK2> protonchris: It's also the kind of change that you can safely make based on code inspection and I trust him to have got it right.
[15:23] <ScottK2> protonchris: Let me know if you need help packaging the patch or when you're ready to have it sponsored.
[15:28] <protonchris> ScottK2: thanks.
[15:36] <protonchris> ScottK2: If you are bored, you could take a look at Bug 204039 and sponsor an upload if the package is good. :)
[15:36] <ubotu> Launchpad bug 204039 in glom "Hardy: Please update to glom 1.6.10" [Undecided,Confirmed] https://launchpad.net/bugs/204039
[15:43] <ScottK2> protonchris: I'm not bored, but I'll have a look anyway.
[15:45] <protonchris> ScottK2: Thanks.
[15:46] <ScottK2> protonchris: You were going to give me the ia64 fix for the library.  I'd like to upload that first.
[15:46] <ScottK2> protonchris: How's that coming?
[15:47] <protonchris> ScottK2: building on my machine now.
[15:48] <ScottK2> protonchris: Great.
[15:48] <ScottK2> protonchris: I should be here for several hours, so ping me when that one's ready and I'll do it first.
[15:50] <marnanel> I was told to come here on #ubuntu-bugs; I am making a debdiff to add a patch (that I wrote for upstream) to a package; I've not used debuild before. james_w was talking me through doing it yesterday.  My patch adds a file which needs compiling, and adds it to Makefile.am; it gets linked in if I use ./configure;make but not debuild -uc -s.  Where should I start looking for a solution?
[15:52] <marnanel> I assume I have a problem with debian/rules but I can't see what.
[15:52] <pochu> marnanel: shouldn't you 'automake' it so that your change gets to Makefile.in?
[15:53] <marnanel> pochu: debuild does not do that for me?  I know little about the internal workings of debuild
[15:54] <pochu> I don't think so, debuild is just a wrapper around dpkg-buildpackage AFAIK
[15:54] <ScottK2> protonchris: Why do you "Rebuild against updated libgdamm3.0 soname." on both your last upload and this one according to debian/changelog?
[15:54]  * marnanel figured I shouldn't touch derived files because the tools would deal with them
[15:54] <marnanel> Okay then...
[15:54] <crimsun> marnanel: no, autotools are not automatically invoked
[15:54] <marnanel> pochu, crimsun: thanks
[15:54] <crimsun> (where I'm being loose with the term "autotools")
[15:55] <ScottK2> protonchris: This is glom still ....  pycompat is no longer needed and should be removed.  It was only useful when dh_python was being used.
[15:56] <ScottK2> protonchris: I haven't built it yet, but from a quick look at the glom debdiff, those are my comments.
[16:00] <bobbo> is anyone in here bored / willing to check a debdiff for me?
[16:00] <ScottK2> Just 6 packages left in Bug #204895 and they're going fast.  This may be your last chance to participate in this special offer.  Excellent bug for people new to packaging that want to learn a bit more to work on.
[16:00] <ubotu> Launchpad bug 204895 in harvestman "Packages failed archive rebuild test possibly due to python-central transition" [Medium,Fix released] https://launchpad.net/bugs/204895
[16:00] <ScottK2> bobbo: What bug?
[16:01] <bobbo> ScottK2; bug #184063
[16:01] <ubotu> Launchpad bug 184063 in apt-mirror "apt-mirror should mirror .bz2 files" [Undecided,In progress] https://launchpad.net/bugs/184063
[16:02] <protonchris> ScottK2: libgdamm3.0 soname has changed twice recently.
[16:03] <ScottK2> protonchris: Fair enough.  Thanks.
[16:03] <ScottK2> bobbo: It's not clear to me from reading the bug what this actually helps.
[16:03] <ScottK2> bobbo: What does mirror, but not use mean?
[16:04] <ScottK2> bobbo: How have you tested this patch?
[16:04] <bobbo> ScottK2; it was in dholbachs really fix it list so i had assumed it had been tested
[16:05] <ScottK2> bobbo: OK.  That's a script that just picks up anything that's marked patch in Launchpad.
[16:06] <bobbo> ScottK2; ah, sorry, i thought they were manually added :/
[16:06] <ScottK2> bobbo: Looking at it, it looks sane, but I'm not familiar enough with the package to be comfortable uploading it this late in the cycle without some sort of testing.
[16:06] <ScottK2> bobbo: Maybe you could get in touch with the original reporter and have him test it?
[16:07] <bobbo> ScottK2; ok, will do that
[16:26] <protonchris> ScottK2: Here is the debdiff for libgda3 ... Bug 208833
[16:26] <ubotu> Launchpad bug 208833 in libgda3 "FTBFS: libgda3_3.0.2-2 on hardy/ia64" [Undecided,New] https://launchpad.net/bugs/208833
[16:26] <\sh> damn..i need to start to code more on my own
[16:27] <james_w> hi marnanel
[16:28] <ScottK2> protonchris: Looking
[16:29] <marnanel> james_w: hey there :)
[16:29] <james_w> how's it going today?
[16:29] <james_w> got any more stories for me?
[16:29] <james_w> or a pot of tea I could share?
[16:30] <protonchris> I got some tea to share :)
[16:30] <marnanel> I have actually drunk all the tea :( There are always plenty of stories, though
[16:31] <james_w> ah, we should all take a little break for some tea and stories then.
[16:31]  * marnanel agrees
[16:31] <james_w> I've got a load of cake that needs eating as well
[16:32]  * marnanel has happy memories of Pembroke College Winnie-the-Pooh Society where everyone sits around eating cake and drinking tea and reading Winnie the Pooh stories to one another.  I think it should start branches outside Cambridge
[16:34] <marnanel> So I am having this problem.  I think something in the packaging tools is not picking up that I intend to add two new files to the src directory.  It fails to link because of this, although a couple of people pointed out that if I run automake before debuild this will be fixed, and that's true.  However, debdiff says there are no changes in the file list.  What am I doing wrong here?
[16:35] <ScottK2> protonchris: debdiff looks good.  If it builds I'll upload it.
[16:35] <protonchris> ScottK2: great
[16:36] <ScottK2> protonchris: If you upload a revised glom debdiff that removes pycompat, I'll do that one after.
[16:37] <protonchris> ScottK2: ok
[16:37] <protonchris> ScottK2: It is almost ready.  I am building now (just to make sure) :)
[16:40] <AnAnt> man-di: hello
[16:41] <james_w> marnanel: are you debdiffing the resulting .debs?
[16:41] <AnAnt> man-di: I notice that gcc,g++ & gcj on Debian are all 4.3, do you think icedtea (or openjdk, as I heard it got renamed) would build ?
[16:42] <james_w> marnanel: debdiff has two modes, one compares binary packages, one source packages, we want to use the source package mode. I assume that your changes don't add any more files to the binary packages, which is what suggests you may be using binary mode
[16:42] <marnanel> james_w: I am, yes.  debdiff orig/gnome-alsamixer_0.9.7~cvs.20060916.ds.1-1_i386.deb new/gnome-alsamixer_0.9.7~cvs.20060916.ds.1-1_i386.deb  -->  File lists identical (after any substitutions)
[16:42] <marnanel> ahh, okay
[16:42] <james_w> marnanel: ok, so pass it the .dsc files instead
[16:42] <james_w> marnanel: you must run debuild -S after all your changes to build the .dsc for the your new version
[16:44] <ScottK2> protonchris: I got distracted and just now kicked off my libgada build.
[16:44] <marnanel> what is .dsc?
[16:45] <protonchris> ScottK2: no problem
[16:45] <ScottK2> marnanel: .deb is the binary file you install.  .dsc is the source control file that describes what is in the source package.
[16:45] <marnanel> ohhh, okay
[16:46]  * marnanel tries this
[16:47] <AnAnt> ping man-di
[16:48] <james_w> marnanel: the .dsc is a text file, so you can read it to see a little what it is about.
[16:49] <james_w> it just lists some info about the package, and then the files that make up the rest of the source package, along with md5sums and sizes for integrity purposes
[16:50] <protonchris> ScottK2: when you get a chance -> Bug 204039
[16:50] <ubotu> Launchpad bug 204039 in glom "Hardy: Please update to glom 1.6.10" [Undecided,Confirmed] https://launchpad.net/bugs/204039
[16:50] <ScottK2> OK.  After libgada is done.
[16:51] <protonchris> ScottK2: thanks
[16:52] <marnanel> well, now it thinks it can't find my secret key.  *goes to find out how to tell it how to find my secret key*
[16:54] <james_w> marnanel: -kkeyid
[16:54] <marnanel> james_w: aha.  thanks.
[16:54] <james_w> marnanel: however, you don't really need to sign it, as you are not going to be passing the actual source package to anyone else, just using it as a source for the diff, so the other option is "-uc -us" again
[16:56] <ScottK2> protonchris: There's a .11 out for glom now.  Do we want that?
[16:57] <marnanel> oh, neat
[16:58] <protonchris> ScottK2: dang.  Yeah, looks like a bug fix.  One of these days I will be done with glom.
[16:58] <ScottK2> protonchris: libgada uploaded.  Thank you for your contribution to Ubuntu.  Please send the patch to Debian in a bug.
[16:58] <ScottK2> protonchris: Let me know when you're ready for me to look at that one.
[16:59] <protonchris> ScottK2: 6 new versions since the 1st of the year.
[16:59] <ScottK2> :-)
[17:01] <marnanel> what is the difference between .dsc and .dsc.asc ?
[17:02] <ScottK2> marnanel: The .asc file gets left over if you try to sign it and it fails.  It can be removed.
[17:04] <marnanel> ScottK2: thank you
[17:04] <ScottK2> marnanel: You're welcome.
[17:09] <marnanel> Oookkay!! I have a debdiff.  It contains everything I want, plus mysteriously some additions to the gettext template.
[17:09] <marnanel> Any reason I shouldn't strip that by hand?
[17:13] <marnanel> also: I find a lot of this sort of work needs doing on packages I maintain upstream: is there a conflict of interest if upstream maintainers get involved in downstream maintenance?
[17:13] <pochu> no, you're welcome to work downstream instead :)
[17:14] <pochu> marnanel: and yes, I think you should remove the gettext changes from the debdiff
[17:14] <marnanel> if I work downstream instead the packages go almost completely unmaintained, which would not make anyone happy :)
[17:15] <marnanel> okay, great
[17:19] <ScottK2> marnanel: Do both.  There are packages I work on upstream, in Debian, and Ubuntu.
[17:21] <marnanel> ScottK2: okay, great-- that's helpful to know.  I'll ask the downstream maintainers how I can be of use to them.
[17:21] <marnanel> Okay, so now I have this debdiff, I just make it an attachment to the bug report?
[17:21] <marnanel> Or is there more to it than that?
[17:22] <protonchris> ScottK2: looks like it built on ia64 just fine.  Thanks.
[17:22] <ScottK2> protonchris: Great.
[17:22] <protonchris> murrayc_: ping
[17:22] <ScottK2> protonchris: If something FTBFS on IA64 and no where else, then thing it failed on is virtually always a missing include.
[17:23] <protonchris> ScottK2: good to know.  I haven't played with a ia64 at all.
[17:23] <ScottK2> marnanel: Attach it to a bug report and subscribe ubuntu-universe-sponsors.
[17:23] <ScottK2> marnanel: Assuming it's a Universe package.  If it's in Main, it's ubuntu-main-sponsors.
[17:25] <ScottK2> protonchris: Don't forget the send the patch to Debian step of the process.
[17:26] <protonchris> ScottK2: will do.
[17:28] <murrayc_> protonchris: pong
[17:30] <AnAnt> what is a Ubuntero ?
[17:31] <protonchris> murrayc_: any plans to do another glom release in the next month?
[17:31] <murrayc_> Not unless I hear of another bug that needs fixing. Sorry for the frequent releases, but I am trying to push bugfixes out as soon as possible because I don't know when my last chance for Hardy really i
[17:31] <murrayc_> s
[17:31] <pochu> AnAnt: someone who has signed the CoC
[17:31] <ScottK2> !ubuntero
[17:31] <ubotu> To become an Ubuntero on Launchpad you need to sign the Code of Conduct.  See https://help.ubuntu.com/community/GnuPrivacyGuardHowto
[17:31] <protonchris> murrayc_: ok.  I'll work on getting .11 into hardy.
[17:33] <AnAnt> pochu: ok
[17:33] <murrayc_> protonchris: Many thanks.
[17:33] <\sh> nixternal: so i'm not alone with this problem :)
[17:33] <marnanel> "This attachment is a patch" -- is a debdiff a patch within the meaning of this statement?
[17:33] <\sh> marnanel: yes..it's a patch :)
[17:34] <marnanel> thanks
[17:34] <AnAnt> thanks
[17:34]  * marnanel is used to hunting down people who tick that box elsewhere and then upload things which aren't strictly unified diff format :)
[17:37] <marnanel> Okay!  All done!  Do I just sit back and wait for someone to deal with it now?
[17:43] <pochu> marnanel: yes. which bug # ?
[17:45] <marnanel> bug 106903
[17:45] <ubotu> Launchpad bug 106903 in gnome-alsamixer "error message when gnome-alsamixer is launching" [Undecided,Confirmed] https://launchpad.net/bugs/106903
[17:45] <protonchris> ScottK2: if you have time (new 1.6.11 package) -> Bug 204039
[17:45] <ubotu> Launchpad bug 204039 in glom "Hardy: Please update to glom 1.6.10" [Undecided,Confirmed] https://launchpad.net/bugs/204039
[17:47] <ScottK2> protonchris: Looking
[17:50] <ScottK2> protonchris: You change the version requirements in the build-depends without documenting that in debian/changelog.
[17:51] <ScottK2> protonchris: Same thing with depends.
[17:51] <ScottK2> protonchris: Please update debian/changelog and let me know when it's ready.
[17:59] <protonchris> ScottK2: mind if I query?
[18:01] <ScottK2> Not at all
[18:39] <slangasek> protonchris: that patch is fixing something that isn't *obviously* broken on other architectures.  It's broken on amd64 as well, but amd64 happens at present to normally map everything at addresses below the 31-bit mark, so a pointer truncated to 32-bits (which is what happens without this patch) will happen to Just Work right now, but it's still a latent bug
[18:43] <ScottK2> protonchris: glom built, so ping me when you're done with your functional testing.
[18:52] <protonchris> ScottK2: glom worked just fine.  I was able to open an example database as well as create a brand new one.
[18:53] <protonchris> slangasek: thanks for the info.
[18:57] <ScottK2> protonchris: Uploaded.  Thank you for your contribution to Ubuntu.
[18:57] <protonchris> ScottK2: thanks for all of your help today.
[18:58] <ScottK2> protonchris: You could show appreciation by knocking out a couple of debdiffs or sync requests for Bug #204895
[18:58] <ubotu> Launchpad bug 204895 in python-pmw "Packages failed archive rebuild test possibly due to python-central transition" [Undecided,In progress] https://launchpad.net/bugs/204895
[18:58] <ScottK2> I'll sponsor those too (after I get back).
[19:00] <eddyMul> can cdbs simple-patchsys handle svn diffs?
[19:08] <pochu> eddyMul: I think so
[19:09] <eddyMul> pochu: thanx.
[19:09] <protonchris> slangasek, ScottK2: looks like glom can be built on sparc due to a python problem:
[19:09] <protonchris> can -> can't
[19:09] <protonchris> python-gnome2-extras-dev: Depends: python-gnome2-extras (>= 2.19.1-0ubuntu7) but it is not going to be installed
[19:10] <eddyMul> am looking at LP#128761, but patch from upstream applies to svn trunk, instead of current Ubuntu version. Oh well..  :(
[19:12] <mbt> Can a REVU admin sync the uploaders keyring, please?
[19:15] <RainCT> mbt: sure
[19:15] <mbt> RainCT: Thanks!
[19:15] <RainCT> mbt: what's you LP account?
[19:15] <mbt> mtrausch
[19:16] <RainCT> has the logo in the MOTD changed? :P
[19:17] <mbt> ?
[19:18] <RainCT> mbt: done
[19:18] <mbt> Thanks!  :)  Appreciate it.  Got an upload coming, then.
[19:19] <RainCT> (that about the MOTD was a general comment, not to you ;))
[19:19] <mbt> Ahh, alright.  Was confused for a second lol
[19:25] <spacepluk> Hi, I'm trying to make my first package from emesene sources
[19:27] <spacepluk> this is a python program, but I'm not sure if I've to compile it someway or just let the .py files.
[19:27] <spacepluk> There's no makefile provided with the sources
[19:28] <slangasek> protonchris: yes, the python-gnome2-extras uninstallability is Somebody Else's Problem :)
[19:28] <mbt> spacepluk: You might want to check out some other python application source packages to see how other people package them.  spe (an editor in Python) might be a good package to look at.
[19:29] <protonchris> slangasek: I'll keep an eye for that being fixed and then do a glom giveback.
[19:29] <POX_> spacepluk: http://svn.debian.org/wsvn/python-apps/packages/?rev=0&sc=0
[19:29] <protonchris> slangasek: unfortunately that problem will keep libgdamm on your bad list :(
[19:30] <spacepluk> mbt: POX_: thanks :)
[19:35] <slangasek> protonchris: except I'm going to fix that problem right now ;)
[19:36] <slangasek> or at least, I'll soon know /why/ it fails
[19:36] <spacepluk> mbt: spe is a perfect sample, thank you very much
[19:40] <mbt> spacepluk: You're welcome.
[19:46] <slangasek> protonchris: buildd admins pinged, build failure may be sorted out soon
[19:46] <protonchris> slangasek: thanks.
[19:48] <bobbo> RainCT; ping
[20:03] <RainCT> bobbo: pong
[20:24] <norsetto> howdy dowdy all
[20:24] <pochu> hi norsetto
[20:25] <norsetto> Hola pochu
[20:26] <protonchris> norsetto: hey.
[20:27] <norsetto> protonchris: hi Chris!
[20:28] <protonchris> norsetto: I think the glom and libgdamm stuff for hardy is finally finished. :)
[20:29] <norsetto> protonchris: yes, I even remember somebody telling me "this should be pretty easy" ;-)
[20:30] <bobbo> RainCT; sorry, was away, are there any packages in Bug #184084 that you havent made a patch for and i could do tonight?
[20:30] <ubotu> Launchpad bug 184084 in venkman "Extension description mentions Iceweasel/Icedove/Iceape" [Low,Fix released] https://launchpad.net/bugs/184084
[20:30] <norsetto> Amaranth: are you here?
[20:30] <RainCT> bobbo: all those which are marked as "new"
[20:31] <bobbo> RainCT; ah thanks, didnt want to duplicate any work
[20:38] <protonchris> ScottK2: I'll take a look at one of your python-central bugs tomorrow.  Thanks again.
[21:53] <Fujitsu> ScottK2: Around?
[22:25] <jdong> grumble
[22:25] <jdong> 80% of the open bugs in my subscribed page seems to be because of Baltix holding a ticket open.
[22:25] <Fujitsu> jdong: That seems to be the sole purpose of Baltix.
[22:26] <slangasek> heh
[22:26] <slangasek> jdong: I habitually unsubscribe ubuntu-archive from those backports bugs after the backports task is closed, if I see Baltix on there
[22:26] <jdong> slangasek: yeah that's a smart idea.  moments
[22:28]  * jdong grumbles at https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/185634/comments/39
[22:29] <ubotu> Launchpad bug 185634 in linux-ubuntu-modules-2.6.24 "uvcvideo: iSight firmware loading does not work" [Medium,Confirmed]
[22:29] <jdong> that's a real helpful tone....
[22:30] <ScottK2> Fujitsu: Here now.
[22:30] <Fujitsu> ScottK2: /query
[22:31] <sistpoty> hi folks
[22:31] <ScottK2> Fujitsu: Sure
[22:33] <pochu> hey sistpoty
[22:33] <sistpoty> hi pochu
[22:34] <sebner> hoi sistpoty
[22:34] <sistpoty> hi sebner
[22:34] <sebner> sistpoty: I already mailed cesare. I the package is in sid soon I would do the FFe sync stuff :)
[22:34] <sebner> *If
[22:35] <sistpoty> sebner: which one actually?
[22:35] <sebner> sistpoty: ah sry. conky
[22:35] <sistpoty> sebner: ah, excellent. Thanks a lot!
[22:36] <emgent> heya
[22:36] <sistpoty> hi emgent
[22:37] <sebner> sistpoty: ah not a big thing. I also did the last sync :) but I also told cesare that for packaging from scratch (if it doesn't hit sid soon) I'm not the right one ...
[22:38] <sistpoty> heh
[22:40] <sistpoty> RainCT: I'd like to reboot sparky for kernel upgrade. ok for you, or should I wait a little bit?
[22:40] <sistpoty> (as you're logged in)
[22:41] <RainCT> sistpoty: I'm not.. it's probably some screen which I left on
[22:41] <sistpoty> RainCT: hm... ok... then I'll reboot now
[22:41] <ScottK2> sistpoty: Would you please ack Bug #209006?  I'm interested enough to do a sync, but not so much that I'll fill out all the FFe paperwork.  At worst it'll be going from totally broken to less broken.
[22:42] <ubotu> Launchpad bug 209006 in quantlib-swig "Please sync quantlib-swig 0.9.0-1 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/209006
[22:42] <marnanel> Does launchpad have a way to view the current debian/patches of an Ubuntu project?
[22:43] <ScottK2> marnanel: Download the source and look is the easiest way.  apt-get source packagename.
[22:44] <sistpoty> ScottK2: acked
[22:44] <marnanel> Thanks.  I wanted something I could link to from the metacity page (I was making a list of distro-specific changes), though
[22:44] <ScottK2> sistpoty: Thanks.
[22:44] <sebner> Is anyone willing to merge monodevelop 1.0 final?
[22:44] <sebner> No?
[22:44] <ScottK2> marnanel: I don't think so.
[22:45] <sebner> Ok, I'll do it :P
[22:45] <sistpoty> wohoo... sparky survived the reboot as well as spooky :)
[22:46] <sebner> lol
[22:46] <geser> sistpoty: you sound like you didn't expect it
[22:47] <sistpoty> geser: well, I did expect it to work, but I'm always feeling better if it in fact does *g*
[22:49] <marnanel> ScottK2: Okay... thanks for your help!
[22:49] <ScottK2> marnanel: You might ask in #launchpad.
[22:55] <RainCT> good night
[22:56] <sebner> RainCT: gn8 :)
[22:56] <jpatrick> RainCT: night
[22:56] <bobbo> night RainCT
[22:57] <pochu> marnanel: http://patches.ubuntu.com/m/metacity/extracted/
[23:01] <ScottK2> albert23: willowng uploaded.  Thank you for your contribution to Ubuntu.
[23:02] <albert23> ScottK2: Thanks!
[23:04] <ScottK2> albert23: I'm test building sqlrelay now.  Feel free to grab some more from that bug.
[23:12] <ScottK2> albert23: sqlrelay uploaded too.  Thank you again for your contribution and please keep them coming.
[23:16] <albert23> ScottK2: Should -nspkg.pth files still be removed as described in http://python-modules.alioth.debian.org/python-central_howto.txt?
[23:17]  * ScottK2 looks
[23:18] <albert23> ScottK2: Doing that needs some additional work to make the package installable, but Debian doesn't do it anymore
[23:18] <ScottK2> albert23: Python-central handles that now for you (I'm pretty sure).
[23:18] <ScottK2> No.  wait
[23:19] <ScottK2> I was looking at the line about about egg naming
[23:19] <albert23> Scottk2: http://packages.debian.org/sid/i386/python-enthought-traits/filelist lists these files
[23:19] <ScottK2> Let's ask a real expert.
[23:19] <ScottK2> POX_: Are you around?  ^^^^
[23:19] <ScottK2> I'm not sure.
[23:21] <norsetto> g'night folks
[23:22] <albert23> Scottk2: Is it bad if we remove them? The fix to make the package installable is easy, just remove the files before dh_pycentral is called, instead of after that call.
[23:23] <ScottK2> albert23: Then I'd do it that way.  No, I don't think it's bad, just not sure if it's necessary.
[23:24] <albert23> Scottk2: will do that
[23:31] <marnanel> pochu: a winner is you, totally
[23:31] <marnanel> pochu: thanks
[23:39] <sebner> Can somebody help me? I'm currently merging monodevelop 1.0. It build-dep on xulrunner-1.9-dev but pbuilder is not willing to install it but to keep xulrunner [<IP_ADDRESS>+nobinonly-0ubuntu1 (hardy)]
[23:39] <pochu> sebner: can you paste a log somewhere?
[23:40] <pochu> sebner: and can you pastebin debian/control too?
[23:40] <sebner> pochu: http://pastebin.com/m6bdbec7a
[23:41] <sebner> pochu: http://pastebin.com/m7defc072
[23:42] <pochu> any reason you're not using pbuilder-satisfydepends-gdebi? :)
[23:42] <sebner> pochu: yes. I never used it before ^^
[23:42] <pochu> sebner: in debian/control, you have both libxul-dev and xulrunner-1.9-dev, but the latter conflicts with the former
[23:43] <pochu> sebner: so remove libxul-dev
[23:43] <pochu> since we have ported it to Xulrunner 1.9 (right?)
[23:43] <sebner> pochu: cool. thx :D
[23:43] <sebner> pochu: so remove it? Because debian replaced (something with geko) with it
[23:44] <sistpoty> sebner: maybe asac has some clues about xulrunner? ;)
[23:44] <pochu> sebner: sorry, didn't get you. debian did what?
[23:45] <sebner> sistpoty: Yeah I would ask him if he were online
[23:45] <pochu> he's online, but probably not in front of the computer ;)
[23:45] <sistpoty> sebner: and slomo_ about mono? (just to highlight yet another person :P)
[23:46] <sebner> pochu: Replaced libgecko2.0-cil build dependency with libxul-dev, as it's used
[23:46] <sebner> +      directly.
[23:46] <sebner> sistpoty: mono isn't the problem? or do you want mono 1.9 in hardy? ^^
[23:46] <pochu> sebner: see this changelog entry: monodevelop (0.18.1+dfsg-1ubuntu2) hardy; urgency=low
[23:46] <sistpoty> sebner: no, but monodevelop sounds mono related, doesn't it? :P
[23:47] <pochu> we are using xulrunner-1.9-dev, so you just need to remove libxul-dev
[23:47] <sebner> pochu: ah great. I'm a dunce :D MD can rock now
[23:47] <sebner> sistpoty: xD xD xD
[23:48] <sebner> pochu: and I suppose the depency on libxul0d isn't also need anymore?
[23:48] <pochu> right
[23:48] <pochu> we depend on xulrunner-1.9
[23:48] <pochu> instead
[23:49] <sebner> :D :D :D
[23:49] <pochu> sebner: for pbuilder-satisfydepends-gdebi, just use it in /etc/pbuilderrc instead of your current pbuilder-satisfydepends, it's much faster
[23:50] <sebner> pochu: nice to hear :) thx for the tip
[23:50] <pochu> np
[23:55] <sebner> pochu: wow. it's pretty fast :) Is there something similar for LP? :P ^^
[23:57] <sistpoty> well, for me speed is not really the problem, but rather that it should behave exactly like soyuz (quite some while ago, pbuilder resolved or'd build-dependencies exactly the other way as soyuz, not too sure if it's still the case though)
[23:57] <pochu> sebner: heh, ssh to the database server and query it, but I don't think that's possible for people like us ;)
[23:58] <sebner> hrhr


[14:32] <micahg> chrisccoulson: if you get a chance, can you please push up your lightning-extension.head branch so I can merge in the powerpc build fix


[03:55] <lifeless> yay
[03:55] <lifeless>     10000  OOPS-4f236f15bf506c5061124374b4816633  Unknown
[19:49] <cjohnston> When someone gets a chance, could I please get some opinons on the wording changes in https://code.launchpad.net/~chrisjohnston/launchpad/part-essential/+merge/124559  - the reasoning why the change is being made is listed in the MP
[20:17] <czajkowski> cjohnston: please mail to the -dev list
[20:18] <czajkowski> cjohnston: irc really at the weekend isn't a good idea for getting feedback.
[20:21] <cjohnston> I know.. just posting it for if someone happens to be around and bored
[20:55] <cjohnston> lifeless: I'm not against it being removed.. I am just not sure that I'm up to snuff with the LP code to be the one to remove it.. there is a 'middle' registration level between attending and required that participation essential is getting.. if you want to remove participation essential from LP, I'm good with it.. I would just rather it happen much sooner than later
[20:55] <lifeless> the meetings system exists solely as a/the backend for summit
[20:55] <lifeless> if there is a mismatch, I think you should fix it
[20:56] <lifeless> I mean, you could have made participation essential a restricted field in LP
[20:56] <lifeless> so that only drivers could set it.
[20:56] <cjohnston> that would work for me as well... again, I am not sure how much success *I* would have with it.. :-)
[20:57] <lifeless> LP is straight forward to develop on
[20:57] <lifeless> there are occasional gotchyas, but that happens everywhere. The buggest hurdle I've seen folk have is just not trying at all.
[22:54] <cjohnston>         or user is owner:
[22:54] <cjohnston>         essential = BoolCol(notNull=True, default=False)
[22:55] <cjohnston> err
[23:00] <lifeless> cjohnston: moving the attribute from the Edit to Admin interfaces probably
[23:01] <lifeless> cjohnston: and dealing with any manual forms that show it specifically and should instead not
[23:01] <lifeless> cjohnston: probably a few hundred lines of diff once you track all the bits down.
[23:01] <lifeless> cjohnston: if you're talking about changing who can set it
[23:01] <lifeless> cjohnston: if you're talking about removing it, thats a little more complex, needs three patches:
[23:01] <lifeless>  - one patch to make it a nullable column
[23:02] <lifeless>  - one patch to drop all code references to it
[23:02] <lifeless>  - one patch to drop the column
[23:02] <cjohnston> by edit admin you mean https://blueprints.launchpad.net/summit/+spec/uds-q/+edit  ?
[23:11] <lifeless> no, configure.zcml / interfaces, within blueprints
[23:11] <lifeless>   <!-- SpecificationSubscription -->
[23:11] <lifeless>   <class class="lp.blueprints.model.specificationsubscription.SpecificationSubscription">
[23:11] <lifeless>     <allow
[23:11] <lifeless>         interface="lp.blueprints.interfaces.specificationsubscription.ISpecificationSubscription"/>
[23:11] <lifeless>     <require
[23:11] <lifeless>         permission="launchpad.Edit"
[23:11] <lifeless>         set_attributes="essential"/>
[23:11] <lifeless> currently only requires Edit on the subscription to set it as essential
[23:12] <lifeless> so you'd mov that to Admin, and write an adapter to grant launchpad.Admin to someone relevant to the spec (e.g. ubuntu driver, or spec owner, or whatevers).
[23:19] <cjohnston> is there an example adapter I could look at?
[23:19] <lifeless> dozens
[23:20] <lifeless> IIRC they are in 'security.py' somewhere in the tree.
[23:30] <cjohnston> so something like http://paste.ubuntu.com/1207923/ lifeless ?
[23:31] <lifeless> something like
[23:31] <lifeless> yes
[23:31] <lifeless> there is zcml to register them to
[23:34] <cjohnston> is that the ISpecificationSubscription?
[23:35] <lifeless> no, grep for the name of one of the example security adapters


[07:22] <knome> pleia2, ping me when you are home and have something around 30-60 minutes to debug the flyer printing process so we can finally get that done and over with
[07:26] <knome> Unit193, where's the MP to update the docs debian/ dir?
[07:46] <Unit193> I don't know?
[08:01] <knome> can you do one?
[09:25] <Unit193> knome: For what exactly?
[09:26] <knome> the dependency updates
[09:26] <Unit193> To?
[09:26] <knome> docs
[09:26] <knome> fop
[09:26] <Unit193> I see...
[09:26] <knome> you pasted me that pastebin
[09:26] <knome> so please make it a MP..
[09:27] <Unit193> I don't remember any such thing, last paste I had was for livecd-rootfs.
[09:27] <knome> maybe it was krytarik then
[09:35] <ochosi> bluesabre: what potential issue with the patched panel? and good to hear you could successfully drop it in -staging!
[09:49] <knome> ochosi, http://tracker.xubuntu.org/ppa-uploads.html
[09:55] <bluesabre> ochosi: I followed up with a "ignore me"
[09:55] <bluesabre> :p
[09:56] <bluesabre> I thought that staging had the split panel package for vivid, which required a few plugin rebuilds, but that was in staging so it was not a problem
[09:57] <knome> bbl
[10:45] <ochosi> bluesabre: oh ok, perfect. ignoring you now :)
[10:45] <bluesabre> :p
[10:45] <ochosi> knome: sweet
[10:47] <ochosi> bluesabre: so i guess this is working and we can ping flocculant about it?
[10:47] <bluesabre> ochosi: yep, it's in -staging and ready to go
[10:48] <ochosi> cool, so flocculant you can ahead and check xfce4-panel and xfpanel-switch from the staging ppa and give it a go. you can then launch xfpanel-switch from the panel preferences after the update as the new "backup and restore" button
[10:51] <bluesabre> ochosi: made the sidebar a bit nicer on catfish last night, working on making the sidebar work more nicely https://code.launchpad.net/~catfish-search/catfish-search/gtk316-csd
[10:52] <ochosi> what widgets are you using in the sidebar btw?
[10:52] <Unit193> Toggle to turn off CSD, by chance?
[10:52] <ochosi> buttons?
[10:52] <bluesabre> ochosi: ListBox
[10:52] <ochosi> oh interestig
[10:52] <bluesabre> Unit193: maybe
[10:52] <Unit193> Oooh, wasn't expecting that.
[10:52] <bluesabre> xfce handles them sanely now, so not enitrely necessary
[10:53] <ochosi> is it listbox that is not properly themed in greybird or is it catfish being a bit funky there?
[10:53] <bluesabre> well, it seems to be gtk being dumb
[10:53] <bluesabre> listboxrows for some reason are adapting the button class
[10:53] <ochosi> ooookay :)
[10:53] <bluesabre> I force remove the css class now
[10:54] <ochosi> hm, well we can throw together some css to include in catfish if you want
[10:54] <bluesabre> I fixed that last night
[10:54] <ochosi> to make it look sane in adwaita and greybird by default
[10:54] <ochosi> cool
[10:54] <bluesabre> http://i.imgur.com/gZ6YfWF.png
[10:55] <ochosi> nice, looks sane now
[10:55] <ochosi> i just pulled ;)
[10:55] <ochosi> the menuitems in the settings menu look a bit off still, but other than that it's nice now!
[10:56] <bluesabre> yeah, going to fiddle with that for a while tonight
[10:56] <ochosi> anyway, nice work!
[10:56] <ochosi> looks like the release isn't terribly far away though
[10:56] <bluesabre> this week for sure
[10:56] <bluesabre> hoping to drop a mugshot release this weekend as well
[10:56] <ochosi> the search-entry is a bit short
[10:57] <ochosi> but well
[10:57] <bluesabre> need to reach out to libreoffice packaging team today, or blacklist the human theme on the iso
[10:57] <ochosi> i think file managers work around that by showing the search in a separate row below the headerbar
[10:57] <bluesabre> yeah
[10:57] <ochosi> oh right, in that case get in touch with Sweet5hark
[10:57] <ochosi> he might not always be around, but you're looking for him
[10:57] <bluesabre> cool
[10:58] <bluesabre> ochosi: will you be around today?
[10:59] <bluesabre> it'd be cool if somebody could start prodding ubuntu-dev about an ubiquity release https://code.launchpad.net/~ubuntu-installer/ubiquity/trunk
[10:59] <ochosi> oh humm, i prolly won't be around during the day..
[10:59] <ochosi> would be back in about 4hrs or so
[10:59] <bluesabre> ok, there might still be a few folks around at that time
[10:59] <ochosi> maybe it's enough to poke someone once now
[11:00] <ochosi> and i can follow up on it later
[11:00] <ochosi> i can get in touch with Sweet5hark then
[11:00] <bluesabre> I'm out from soonish to +10 hours
[11:00] <ochosi> what do we want from him again?
[11:00] <ochosi> wrt the human theme i mean
[11:01] <bluesabre> alternate depends/recommends for libreoffice-gtk on libreoffice-style-human|libreoffice-style-elementary
[11:01] <bluesabre> I might be able to put together a patch before heading out
[11:05] <ochosi> ok cool
[11:05] <ochosi> gotta run now
[11:05] <ochosi> bbl
[11:06] <bluesabre> seeya
[11:21] <bluesabre> ochosi: this is the diff, basically we want libreoffice-style-elementary as an alternate Recommends for libreoffice-gtk and libreoffice-gtk3 http://paste.ubuntu.com/12054927/
[11:22] <bluesabre> not sure when lo-5 is due to be packaged, but we can probably blacklist the human theme in our seed for the meantime
[11:22] <bluesabre> gotta run, bbl
[11:29] <flocculant> bluesabre: did that lightdm upload go in - in time for live build at 09:50? if so then I guess it wasn't that
[11:29] <flocculant> still got password in livesession
[11:29] <flocculant> ochosi: ok :)
[11:40] <bluesabre> flocculant: yeah, it should be in there
[11:40] <flocculant> mmm - ok - issue elsewhere then perhaps
[11:41] <bluesabre> for reference http://changelogs.ubuntu.com/changelogs/pool/universe/x/xubuntu-default-settings/xubuntu-default-settings_15.10.2/changelog
[11:41] <bluesabre> in case somebody wants to help in the investigation
[11:42] <flocculant> ok - well that's in the livesession ok
[11:43] <flocculant> I guess I'll try in -release later see if I can get some interest in it
[11:43] <bluesabre> :)
[12:54] <krytarik> knome: Yes, it was me - I've noticed 'debian/copyright' in the work items too though - so how about you combine it with that? :P - http://paste.openstack.org/show/MqvUKza6T5IN3p2iZsyU/
[12:55] <knome> krytarik, please, do a MP...
[13:06] <knome> oh no, not again...
[14:21] <knome> dpm, hello!
[14:21] <dpm> o/
[14:22] <knome> so if you haven't got the information yet, we've moved the tracker to http://tracker.xubuntu.org/
[14:23] <dpm> knome, so ochosi and I had a conversation about the tracker, and when he showed it to me I thought it was something really cool to showcase. I was just going to mention it on a G+ post, but I asked him whether the server/url were already stable enough to point to, and he'd said he'd check with you
[14:23] <dpm> so here we are :)
[14:25] <dpm> essentially, it pulls data from LP blueprints as a nicer/xubuntuier frontend to replace status.u.com, correct?
[14:51] <knome> yep
[14:52] <knome> we've also been planning more stuff, like building a list of the latest uploads to our testing PPAs as well as the main repositories for packages that we are interested in
[14:52] <knome> this would especially help our testers see what has changed lately and focus on making sure new stuff that is landing is working and not regressing
[14:54] <knome> another new feature i've been preparing is pulling stuff from the QA trackers to get some information on the amount of tests ran etc
[18:29] <flocculant> ochosi: the digging at why live starts at password is ongoing
[20:07] <flocculant> Unit193: it is apparently lightdm "lightdm now expects an actual meaningful value instead of what we're handing it for autologin-session="
[20:19] <krytarik> # user-session = Session to load for users
[20:19] <krytarik> # autologin-session = Session to load for automatic login (overrides user-session)
[20:19] <krytarik> So?
[20:20] <krytarik> → http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/xubuntu-default-settings/wily/view/head:/debian/60-xubuntu.conf
[20:27] <flocculant> yea I know
[20:36] <krytarik> Obviously, we'd want to check what happens when we set "autologin-session=xubuntu", alone and alongside the current one.
[21:06] <flocculant> krytarik: we could, personally I'm going to let it get dealt with "I'll "fix" that in a second" :)
[21:06] <flocculant> it's at least Ubuntu also
[21:06] <flocculant> I'll catch up tomorrow
[21:29] <ochosi> late evening all
[21:29] <ochosi> bluesabre: did only make it back now, so no progress on the LO stuff
[22:00] <genii> Hehe, yep
[22:04] <bluesabre> ochosi: darn
[22:06] <ochosi> and now Sweet5hark isn't around
[22:07] <bluesabre> double-darn
[22:07] <bluesabre> :D
[22:07] <ochosi> although judging from the logs, he wasn't all day :)
[22:08] <ochosi> what if we just file a bugreport or better yet a merge-request?
[22:08] <bluesabre> ochosi: yeah, that's what I need to do
[22:08] <bluesabre> nothing to merge into
[22:08] <bluesabre> so need to create a debdiff
[22:08] <ochosi> then it'd be easier to ping people about
[22:08] <ochosi> oh
[22:08] <bluesabre> yup
[22:09] <ochosi> hmm, right, it's only a packaging change
[22:09] <bluesabre> was just in a hurry this morning
[22:09] <ochosi> oh, doko would be another candidate
[22:10] <ochosi> you could try to ping him in #u-devel
[22:15] <bluesabre> yeah
[22:15] <bluesabre> creating a bug report now so we have tracking
[22:17] <ochosi> cool
[22:24] <bluesabre> ochosi: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1483914
[22:26] <ochosi> nice
[22:26] <ochosi> i'd say let's either link it to the bugs blueprint or to the dev one
[22:26] <bluesabre> I'll link it to dev
[22:27] <ochosi> sounds good
[22:27] <ochosi> wanna ping doko straight away?
[22:27] <bluesabre> done linking
[22:27] <bluesabre> sure
[22:30] <bluesabre> ochosi: feel free to add any other comments ;)
[22:30] <ochosi> k :)
[22:30] <ochosi> well doko is in the LO packaging team
[22:30] <ochosi> so i would presume he will take care of it
[22:30] <bluesabre> sensible request then
[22:31] <bluesabre> :)
[22:34] <ochosi> added a line
[22:35] <bluesabre> ochosi: cool
[22:38] <ochosi> ok, i guess i gotta get some sleep
[22:38] <ochosi> bluesabre: anything left for me to do before i take off?
[22:39] <bluesabre> nah, I'll try to get some stuff together for you to do tomorrow
[22:39] <bluesabre> ;)
[22:39] <ochosi> heh
[22:39] <ochosi> alrighty
[22:40] <ochosi> bluesabre: humm, just one more thing..
[22:40] <ochosi> the clutter bug
[22:40] <ochosi> that affects parole
[22:40] <ochosi> has that been fixed meanwhile?
[22:40] <bluesabre> ochosi: probably not
[22:40] <bluesabre> but don't know
[22:41] <ochosi> upstream claims so, but i think ebassi merged two bugs that are not the same
[22:41] <bluesabre> cool
[22:41] <bluesabre> suppose I'll have to check that out then
[22:42] <ochosi> i'll quickly fire up my wily vbox to check
[22:44] <ochosi> hmm, also, what was the outcome of your talk with Unit193 about xfpanel-switch packaging? can we add a workitem for him or what? :)
[22:45] <bluesabre> :)
[22:45] <bluesabre> one of us will write a bug report tonight for packaging in ubuntu
[22:46] <bluesabre> maybe I can convince him to tidy up the package if I write the request
[22:46] <bluesabre> :D
[22:48] <ochosi> yeah hmpf, still not fixed
[22:48] <ochosi> so clutter still has that bug
[22:50] <ochosi> oh crap
[22:50] <ochosi> totem works now
[22:50] <ochosi> so i guess we're on our own
[22:50] <ochosi> we can either skim totem's changelog for mentions of clutter-gdk or ... humm, well i dunno what else to do
[22:51] <bluesabre> fun
[22:51] <bluesabre> sounds like something that can be fixed after FF
[22:51] <bluesabre> unless somebody wants to look into it
[22:53] <krytarik> flocculant, Unit193: So, there we go :P - https://launchpad.net/ubuntu/+source/casper/1.364 , http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/casper/wily/revision/1187
[22:53] <bluesabre> krytarik: nice!
[22:54] <krytarik> Indeed!
[22:54] <krytarik> Took me a while to find where this file is coming from. :P
[22:57] <ochosi> bluesabre: found no relevant change in totem when quickly skimming upstreams git
[22:58] <bluesabre> fun fun
[22:58] <bluesabre> gstreamer changes that we can't keep up with
[22:58] <bluesabre> like mugshot's camera
[22:58] <bluesabre> *cry*
[22:59] <ochosi> yeah
[22:59] <ochosi> also no relevant changes i could find in ubuntu's package
[23:00] <ochosi> and no patches that point in our direction
[23:00] <bluesabre> we'll figure it out
[23:00] <bluesabre> probably just need to sit down with wily and crash it a bunch to figure it out
[23:01] <ochosi> okeydokey
[23:01]  * ochosi tries to remain optimistic
[23:01] <ochosi> so let's fix mugshot's and parole's bugs post-FF
[23:01] <bluesabre> yup
[23:02] <ochosi> so that we can get the feature stuff done now
[23:02] <bluesabre> try to get new features done this week, bugs after
[23:02] <ochosi> alrighty, sounds like a plan i can fall asleep to
[23:02] <bluesabre> so new catfish/menulibre this week/early next week
[23:02] <bluesabre> and packaging
[23:03] <ochosi> sweet
[23:03] <ochosi> that should get a lot of our workitems done
[23:03] <bluesabre> mhm
[23:04] <ochosi> lol https://github.com/gmc-holle/xfdashboard/commit/965b6f01210c3c97fe5c02f3e77b7d45e481e75d
[23:05] <bluesabre> :3
[23:05] <ochosi> fwiw, adding the CLUTTER_BACKEND=x11 fixes parole
[23:05] <bluesabre> that probably won't work for very long
[23:05] <ochosi> if you want yet another hacky workaround
[23:05] <bluesabre> but good to know
[23:05] <ochosi> also, parole still segfaults when closing
[23:06] <bluesabre> yeah
[23:06] <bluesabre> bugs bugs bugs
[23:06] <ochosi> which is another, probably unreported bug
[23:06] <bluesabre> bugs
[23:06] <bluesabre> :D
[23:06] <ochosi> developers developers developers!
[23:07] <ochosi> anyhoo, time to get some sleep finally
[23:07] <ochosi> night everyone
[23:08] <bluesabre> night ochsoi
[23:08] <bluesabre> internet slowing down... uh oh
[23:08] <bluesabre> bbabl
[23:15] <ochosi> bluesabre: ok, final note: according to this bugreport https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785538 this might be a clue https://git.gnome.org/browse/totem/commit/?id=8c15325bc12740e94000d7b42a76c2a9b5896560
[23:15] <ochosi> however, we don't have that call to set the connection-speed in parole
[23:15] <ochosi> maybe we should add it though
[23:36] <Unit193> So, Aug 20th is FF, and GCC5 hasn't fully landed yet. :D


[06:22] <dholbach> good morning
[08:54] <Jinesh> hello
[08:54] <Jinesh> any one there
[14:06] <mhall119> https://wiki.ubuntu.com/UbuntuGlobalJam
[21:08] <LedM> hellow aliens!  OH!  HAHAHA!  (IMPOSSIBLE) BUT I DON'T SUBESTIME! GOOD BYE! DAMNED TRASHES!     ENEMYS NOW ARE FREEZED!   STAY BLOCKING! IDIOTS! SOMEDAY THESE 2 BEASTS GOGLE AND FACEBOK, WILL LOCKS YOU TO IDOLATRE THEM OR YOU WILL BE KILLED! BYE BYE SUCKER ZOMBIE!
[22:24] <d_ed> what was all that about ^
[22:25] <k1l> never mind the trolls
[22:27] <d_ed> but that was fantastic...
[22:27] <d_ed> I assume someone set noexec on external media ?
[22:27] <d_ed> I like watching shouty people (when thye're not shouting at me)


 Not sure if this is the right place to report; please let me know if I should report this elsewhere. Running Xubuntu 22.10 beta, updated. After setting the default browser to chromium and then trying to start it, I get an error that the default browser can not be found. : https://matterbridge.thomas-ward.net/4e1f4742/file_207.jpg
[19:56]  * chromebittin is doing a test install of the 22.10 beta now