[08:18] <cpaelzer> pitti: the apparmor fix you asked will be in 3.10 for everyone
[08:18] <cpaelzer> I updated the bug
[08:19] <pitti> cpaelzer: ah nice, thanks!
[08:19] <cpaelzer> I'll update the debian bug as well
[08:19] <cpaelzer> with aping to the upstream commit
[08:21] <cpaelzer> not sure when guido will merge 3.10, but then it will be resolved on Debian as well
[09:30] <cpaelzer> pitti: I see on autopkgtest you have a test against what seems a personal ppa
[09:30] <cpaelzer> pitti: Ppas:	['pitti/systemd-semaphore']
[09:31] <cpaelzer> for the un-enlightened like me is there somewhere a howto to do so?
[09:31] <cpaelzer> I used bileto but that recently lets me down considering everything as "always failed"
[09:31] <cpaelzer> and sometimes testing "on" the infra is just what you need
[09:50] <pitti> cpaelzer: ah, yes! these are upstream tests, set up like https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Integration_with_GitHub_and_GitLab_pull.2Fmerge_requests
[09:50] <pitti> cpaelzer: the underlying mechanics is just adding a ppa= to the test request, like in https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Test_request_format
[09:51] <pitti> cpaelzer: you can use the run-autopkgtest CLI for convenience (https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Re-running_tests)
[09:52] <pitti> actually no, this script is horribly out of date; I don't think it's being used any more
[09:53] <pitti> it's that script actually: https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/tree/run-autopkgtest
[09:53] <pitti> (same name, but using the CGI API instead of ssh to snakefruit)
[09:55] <pitti> argh, it's been too long - so that script isn't useful for you, it's indeed the one that directly talks to AMQP and thus you can't access it
[09:56] <pitti> you can trigger them through request.cgi, but ATM you have to build the URL manually; bileto did that, not sure if there's some CLI for that by now
[10:08] <cpaelzer> thanks pitti
[12:22] <sil2100> Does anyone know if it's possible to run armhf autopkgtests on an amd64 host?
[12:23] <sil2100> I tried using autopkgtest-buildvm-ubuntu-cloud with -a armhf but I guess it's using qemu-system-x86_64 by default, tried switching it to qemu-system-arm but then it fails as the script seems to hard-code some params
[12:23] <sil2100> Is there any guide somewhere for that?
[12:25] <cpaelzer> ahasenack: didn't you try that just days ago - any success?
[12:25] <ahasenack> sil2100: I had to tell it to use a wrapper script for qemu
[12:25] <ahasenack> I had it like this
[12:25] <ahasenack> options=$(echo "$@" | sed "s%-enable-kvm%%")
[12:25] <ahasenack> options="$options -M virt"
[12:25] <ahasenack> echo "options: $options"
[12:26] <ahasenack> that just got me a bit further, but it still didn't work
[12:26] <ahasenack> I don't remember exactly what now, but I think it just didn't boot
[12:26] <ahasenack> autopkgtest-buildvm-ubuntu-cloud -r bionic -m http://br.archive.ubuntu.com/ubuntu/  -p http://<IP_ADDRESS>:3128/ -o ~/adt-qemu-images -a armhf -q /home/andreas/bin/qemu-arm.sh --cloud-image-url http://cloud-images.ubuntu.com
[12:26] <ahasenack> was my command line
[12:27] <ahasenack> the -q bit specified the wrapper
[12:27] <ahasenack> and I used --cloud-image-url so my proxy would cache the image (as opposed to https)
[12:30] <cpaelzer> pitti: you are usually the last resort on autopkgtest magic - ideas for the above?
[12:41] <sil2100> eh, and I can't even create an armhf schroot right now, debootstrap is dying presumably on bash
[12:42] <ogra_> sil2100, you want qemu-debootstrap
[12:43] <sil2100> I'd assume mk-sbuild knows what it should use
[12:44] <persia> Take care with such assumptions.  Code changes, and needs patches.  When code doesn't work, it is worth looking at why, and maybe fixing it.
[12:47] <sil2100> What I wanted to say by that: mk-sbuild uses what it should, it's not the problem here, qemu-debootstrap is just a wrapper and mk-sbuild is made to create different chroots of different architecture
[12:47] <sil2100> It was working fine always and the problem lies somewhere else
[12:48] <sil2100> eh, I'll try creating an artful schroot and just hope I can reproduce the issue I'm chasing in there
[12:51] <ogra_> well, qemu-debootstrap is actually only a "cp" :)
[12:51] <ogra_> but that one cp call is what makes qemu-user-static work :)
[12:51] <ogra_> else you get an exec format error on bash ;)
[12:52] <sil2100> It's a bit more than a cp but anyway, mk-sbuild uses that for non-native archs anyway
[12:52] <ogra_> well, it used to be cp when i wrote it ...
[12:52] <ogra_> not sure how it has grown sicne
[13:10] <pitti> sil2100: autopkgtest-buildvm-ubuntu-cloud uses qemu-system-`uname -m` by default indeed, but you can specify a different one with -q
[13:10] <sil2100> pitti: yeah, tried that, did a wrapper even to get the -machine specified but it then failed further
[13:10] <sil2100> pitti: ahasenack went further with his hacks but still didn't get it working AFAIK
[13:11] <pitti> sil2100: ah, autopkgtest-virt-qemu has an option for specifying additional qemu args, but not buildvm-ubuntu-cloud
[13:44] <coreycb> hello sru team, i just uploaded a new version of neutron to the zesty unapproved queue that has a fix for bug 1731595
[16:02] <sforshee> LocutusOfBorg: we have a 4.14 kernel in bionic-proposed now but the vbox dkms drivers still fail to build with it. When will we have those fixes?
[16:02] <LocutusOfBorg> meh sforshee I can do it then
[16:03] <sforshee> thanks
[16:03] <LocutusOfBorg> I was waiting for test results on excuses page... can you please link them to me?
[16:03] <LocutusOfBorg> got them
[16:04] <LocutusOfBorg> sforshee, the kernel module builds correctly with 4.14
[16:04] <LocutusOfBorg><EMAIL_ADDRESS>[16:04] <LocutusOfBorg> if you mean this error, just ask apw to override it
[16:05] <LocutusOfBorg> it means that the same module is already built so there is no need to dkms it
[16:05] <LocutusOfBorg> autopkgtest for virtualbox/5.2.2-dfsg-2: amd64: Always failed, arm64: Always failed, armhf: Always failed, i386: Always failed, ppc64el: Always failed, s390x: Always failed
[16:05] <LocutusOfBorg> seems already done... so I don't know what is missing
[16:05] <sforshee> huh, my bad. I thought I saw a module build error in the log, maybe I was looking at the wrong one
[16:06] <sforshee> so nm. Thanks LocutusOfBorg!
[16:09] <LocutusOfBorg> :)
[16:09] <LocutusOfBorg> please close the bugs in case
[16:09] <LocutusOfBorg> we have a patch for 4.15, but I don't care to upload it right now
[16:10] <sforshee> that's fine, I'm behind on 4.15 anyhow, still haven't finished the initial rebase
[16:10] <sforshee> too many balls in the air right now :-(
[16:11] <LocutusOfBorg> 5.1.4 will be out before you upload the kernel, but in case... just grab it from vbox-dev mail list if you care
[16:11] <LocutusOfBorg> https://www.virtualbox.org/pipermail/vbox-dev/2017-December/014885.html
[16:13] <LocutusOfBorg> BTW with 4.15 you should really start using the mainline vboxvideo instead of the hacky copy-pasta one
[16:15] <sforshee> LocutusOfBorg: with 4.14 I've already disabled the one from vboxguests in favor of the staging driver
[16:15] <sforshee> we don't even build it
[16:17] <LocutusOfBorg> oh sad news
[16:17] <LocutusOfBorg> please make sure you cherry-picked this commit ce10d7b4e8e3574b9616e54a09d64521b9aeb8b6
[16:17] <LocutusOfBorg> and upload the fix asap in case :p
[16:18] <sforshee> we already got that fix from stable
[16:19] <LocutusOfBorg> <3
[16:19] <LocutusOfBorg> thanks!
[16:20] <LocutusOfBorg> let me know if you do some vm testing then :)
[16:20]  * LocutusOfBorg grabs a bionic from http://cdimage.ubuntu.com/ubuntu/daily-live/20171207/
[17:21] <ahasenack> can someone please click on the retry button in the s390x failed firejail test for iproute2 on http://people.canonical.com/~ubuntu-archive/proposed-migration/artful/update_excuses.html? It's failing because thunderbird is not available in s390x, and the test has been "force-badtested" already so I think it just needs another try
[17:24] <Laney> You don't need a retry for that
[17:27] <ahasenack> I need the failure to be ignored so the package can migrate
[17:28] <ahasenack> or "always failed"
[17:28] <ahasenack> not sure what the state will be after this change
[17:29] <Laney> ok, for artful you need an SRU team member to apply hints, I can't do it
[17:29] <ahasenack> Laney: oh, you did the force-badtest thing for bionic?
[17:29] <Laney> ya
[17:29] <ahasenack> it's wrong there, the test works in bionic
[17:30] <ahasenack> ooop
[17:30] <ahasenack> ps
[17:30] <ahasenack> wait
[17:30] <rbasak> Would someone like to through an MP at me?
[17:30] <ahasenack> it's firejail
[17:30] <rbasak> Uh
[17:30] <rbasak> Throw
[17:30] <ahasenack> Laney: n/m me
[19:33] <ahasenack> is there something going on with setting up ppc64el autopkg tests in excuses? I have 3 different packages failing there with the same error
[19:33] <ahasenack> grub-probe: error: not a directory.
[19:33] <ahasenack> run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
[19:33] <ahasenack> in trusty
[19:33] <ahasenack><EMAIL_ADDRESS>is one of them


[01:31] <Unit193> cyphermox: Actually, here you go: https://sigma.unit193.net/source/plymouth_0.9.0-0ubuntu9_i386.build
[02:12] <Unit193> (All said and done, biggest problem was entering the password twice on an encrypted install.  Everything else worked.)
[04:53] <Logan> Unit193: what did I do
[04:54] <Logan> oh
[04:57] <Unit193> I use that, noticed that problem but requests in vivid is too old anyway.
[06:01] <Logan> Unit193: don't think so?
[06:02] <Logan> it just requires >= 2.2.0
[06:10] <Unit193> Dangit, confusing the two.  That's the dep missing, another one in vivid wasn't new enough.  python-natsort it was.
[06:11] <Unit193> natsort>=3.5.2; Candidate: 3.5.1-1
[06:11] <Unit193> Anywho, moot.
[07:04] <ochosi> good day everyone
[07:06]  * ochosi pokes bluesabre back
[07:06] <ochosi> bluesabre: hey dude, hi, what's up? :)
[07:10] <ochosi> Unit193: since you've been wily for a bit, how's it going so far?
[07:10] <ochosi> any roadblocks or glitches you've seen that we shoudl address?
[07:11] <Unit193> In case you haven't seen it, I seem to be trying to break it with crazy setups.  I'd say all the ones I've hit are != Xubuntu and can be considered fringe events.
[07:15] <ochosi> ok, good
[07:16] <ochosi> well if you notice anything odd, always be sure to mention it here
[07:16] <ochosi> i'm still only doing the occasional test in vbox, so far everything seems good
[07:16] <Unit193> Depends on what you consider odd. ;P
[07:33] <Unit193> Speaking of which, new cores coming soon™
[07:49] <ochosi> Unit193: new cores?
[08:10] <Noskcaj> ochosi, Only issue with wily i've noticed is that parole is near useless
[08:11] <ochosi> oh right, that one
[08:11] <ochosi> yeah, we definitely need to check out what's going on there...
[08:14] <ochosi> it actually seems totally useless, not "near"
[08:14] <ochosi> wonder what that is related to though, since no changes happened in parole
[08:14] <ochosi> guess clutter or gstreamer
[08:15] <ochosi> ok, it's clutter.
[08:15] <ochosi> Noskcaj: easy workaround for you to test: set the property /video/videosink in parole to "xv" instead of clutter
[08:16] <ochosi> then it should launch immediately and smoothly
[08:16] <Unit193> Ah, I don't use parole.
[08:18] <ochosi> bluesabre: so we have a clutter issue in parole in wily (see above)
[08:21] <Unit193> What happens?
[08:21] <Unit193> Crash?  Like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789198?
[08:27] <Noskcaj> ochosi, how do i do that?
[08:27] <ochosi> Unit193: it just freezes up, i would have to compile with debug symbols to know what exactly is going on
[08:27] <ochosi> Noskcaj: open xfce4-settings-editor
[08:28] <Noskcaj> fixed
[08:29] <Noskcaj> i'll install clutter-1.0 and see if that works too
[08:30] <Unit193> ochosi: https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built-in_debug_symbol_packages_.28.2A-dbgsym.29
[08:31] <Unit193> https://launchpad.net/ubuntu/+source/parole/0.8.0-2ubuntu1/+build/7464841/+files/parole-dbgsym_0.8.0-2ubuntu1_amd64.ddeb
[08:35] <ochosi> meh, bidirectional clipboard isn't working in the vbox and that link is definitely too long to type
[08:39] <Unit193> ochosi: http://u193.ga/y/prldbg
[08:39] <ochosi> Unit193: hm, i don't get any additional debug output
[08:40] <ochosi> just the usual gtk3 deprecation warnings
[08:40] <ochosi> which are harmless
[08:40] <Unit193> Oooh, I thought you meant debug symbols. :P
[08:40] <ochosi> yeah, sorry for mis-phrasing that ;)
[08:42] <Unit193> Those should be runtime. :P
[09:01] <ochosi> Unit193: anyway, that bugreport you linked to might well be related
[09:16] <ochosi> Unit193: especially since totem also freezes and then crashes at startup in wily....
[09:21] <Unit193> Try updating the package? :>
[09:33] <Unit193> Except, looks like that's talking about upgrading to the version it is at now, soo.
[09:39] <ochosi> Unit193: you mean upgrading clutter?
[10:30] <Noskcaj> Upgrading clutter-1.0 doesn't seem to do anything
[10:39] <ochosi> Noskcaj: always check whether totem starts and runs ok to be sure
[11:00] <bluesabre> hey all
[11:01] <bluesabre> ochosi: do you want me to package up an artwork update soon?
[11:03] <bluesabre> nice, since clutter seems to be the issue, I could swap us back to xv for the time being
[11:03] <bluesabre> the only issue I have with wily is overlay scrollbars
[11:04] <bluesabre> for some reason, adding this to my bashrc does not work
[11:04] <ochosi> overlay scrollbars because you don't like them?
[11:04] <bluesabre> export GTK_OVERLAY_SCROLLING=0
[11:04] <Unit193> The apport screen looks glitchy as heck with that.
[11:04] <ochosi> and yeah, let's switch back to xv to prevent tons of bugreports
[11:04] <bluesabre> ochosi: I don't like them and they cover up content that I try to use
[11:04] <ochosi> we just have to remember to switch back to clutter ;)
[11:05] <ochosi> bluesabre: don't they fade out again quickly enough? and if not, is that tweakable?
[11:05] <bluesabre> they appear every time you move
[11:05] <Unit193> export QT_STYLE_OVERRIDE=gtk
[11:05] <Unit193> export GTK_OVERLAY_SCROLLING=0
[11:05] <ochosi> right, i guess that makes sense though
[11:05] <bluesabre> so if there is a button under them, good luck
[11:05] <ochosi> hmm
[11:05] <ochosi> i see
[11:05] <ochosi> well i guess then they should only appear when you hover them
[11:05] <ochosi> or the area where they're supposed to appear
[11:05] <ochosi> but i guess we have no influence on that
[11:06] <ochosi> in terms of artwork, yes please! i pushed some more improvements to greybird today and may push one or two more soonish
[11:06] <bluesabre> ok
[11:06] <ochosi> if you want me to do a point release, that'd be fine by me
[11:06] <ochosi> same goes for LO
[11:07] <ochosi> and elementary-xfce
[11:07] <bluesabre> I might upload friday then if you're expecting anything before then
[11:07] <ochosi> not too much tbh
[11:07] <ochosi> maybe more minor improvements
[11:07] <bluesabre> ok
[11:07] <ochosi> but personally  i think it'd be good to have some updated artwork so we can check what's still missing in qiwily more reliably
[11:08] <bluesabre> I also wonder if LO integration will happen before LO 5.0
[11:14] <ochosi> i think we should upload our LO stuff and then we'll see what happens with LO 5.0
[11:15] <ochosi> last i heard it was still planned for wily, but i haven't talked to Sweet5hark in a while
[11:16] <ochosi> the LO icons will likely receive more updates during the wily cycle anyway, so it's ok to do another one after 5.0 lands
[11:17] <bluesabre> alrighty
[11:19] <ochosi> so greybird, elementary-xfce and the LO icons
[11:19] <bluesabre> ok
[11:20] <bluesabre> I might dump lo-icons into xubuntu-artwork for now
[11:20] <bluesabre> maybe
[11:20] <bluesabre> I'll work on that and other things tonight
[11:20] <bluesabre> also
[11:20] <bluesabre> "ooh, you fixed geary in greybird"
[11:21] <ochosi> yeah, i thought i'd do one for your motivation ;)
[11:21] <ochosi> had to add some custom theming though
[11:21] <ochosi> but that was expected
[11:21] <ochosi> and yeah, let's put the LO icons in -artwork for now
[11:23] <ochosi> there's that member of the LO community that wants the icons upstream, so i won't do anything there toin order to not duplicate the effort
[11:24] <bluesabre> yeah, makes sense
[11:24] <bluesabre> and makes it easier
[11:24] <ochosi> for us, anyway ;)
[11:25] <Unit193> xubuntu-artwork or src:xubuntu-artwork?
[11:25] <bluesabre> it will be stuck in -proposed for a few days, I'll have the style create its own package like xubuntu-icon-theme
[11:26] <bluesabre> lp:xubuntu-artwork will create libreoffice-style-elementary or xubuntu-libreoffice-theme or something
[11:27] <ochosi> i'd prefer the prior
[11:27] <bluesabre> same, just not sure if there'd be any complaints
[11:27] <ochosi> the latter obfuscates the project name too much imo
[11:27] <ochosi> well we can always point to that discussion on github if anybody complains that we're not upstreaming
[11:27] <bluesabre> mhm
[11:27] <Unit193> I'd highly prefer the former, considering that follows the package naming of the other themes.
[11:28] <bluesabre> ofc
[11:28] <bluesabre> I'd prefer the former too
[11:28] <bluesabre> :D
[11:28] <bluesabre> but yeah, I'll get the ball rolling on that tonight
[11:28] <Unit193> But then again I want burritos too.
[11:30] <bluesabre> oh yeah
[11:31] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1473952
[11:31] <bluesabre> I'm guessing gtk2 for us for now, right?
[11:33] <ochosi> humm
[11:33] <ochosi> dunno, what's the visual diff?
[11:33] <Unit193> bluesabre: Have to keep an eye on Debian 791441, but yes gtk2.
[11:34] <bluesabre> dunno, don't have anything using pinentry
[11:34] <ochosi> i just wonder whether there are any downsides to using gnome3, even if just for the sake of not having to change the seed
[11:34] <ochosi> me neither
[11:35] <bluesabre> but if the gtk2 version is offered, it would likely be easier on us in the long run
[11:37] <ochosi> i guess
[11:37] <ochosi> hard to say when you've seen neither :)
[11:37] <bluesabre> :D
[12:04] <ochosi> bluesabre: hmm, any idea what the easiest way would be to test evince with headerbar?
[12:04] <ochosi> (in xubuntu, that is)
[12:10] <bluesabre> ochosi: virtualbox, install fedora
[12:10] <bluesabre> :D
[12:10] <bluesabre> no idea
[12:10] <ochosi> hah, meh
[12:10] <bluesabre> gotta run, bbl
[12:10] <ochosi> okeydokey
[12:10] <ochosi> just wanted to fix some small visual nuisances there
[12:11] <ochosi> but i guess that'll have to wait
[12:11] <ochosi> hf bluesabre
[12:12] <Unit193> XDG_CURRENT_DESKTOP=GNOME evince
[12:12] <Unit193> ochosi:
[12:12] <Unit193> o
[12:13] <ochosi> oh right
[12:13] <ochosi> that was easy
[12:13] <ochosi> thanks Uni
[12:13] <Unit193> Sure.
[12:13] <Unit193> Also, http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/evince/wily/view/head:/debian/patches/traditional_menu_bar.patch#L91
[12:15] <ochosi> bluesabre: btw, i fixed my sort issue in the open file dialog with this gsetting: "gsettings set org.gtk.Settings.FileChooser sort-directories-first true"
[12:16] <ochosi> bluesabre: so in case anyone else encounters it, we might want to throw that into x-d-s
[12:17] <Unit193> Just like turning off the GTK animations! :P
[13:30] <cyphermox> Unit193: I see, lots of stuff... though also lots we really really don't care about and don't want to ship
[19:24] <Noskcaj> pinentry-gnome3 just means it's the gtk3 version, there's no gnome specific stuff.
[19:24] <Noskcaj> -gtk2 is apparently missing some features, which is why debian only depends on -gnome3
[19:39] <Noskcaj> bluesabre, If you haven't already seen it, mugshot and menulibre are ftbfs with python3.5
[19:44] <ochosi> Noskcaj: any details as to what features? (and i still don't have a clue because i have no device to use this with)
[19:45] <Noskcaj> quoting debian's gnome team "No, we want pinentry-gnome3 for GNOME, since only that provides a proper UI/replacement for the builtin prompter."
[19:46] <ochosi> hm, still no clue, sorr
[19:46] <ochosi> y
[19:47] <Unit193> Because it is GTK3, thus the only one good enough for GNOME? :P
[19:48] <Noskcaj> Unit193, I think that's most of it
[19:48] <Noskcaj> But if we can use -gnome3 i'd prefer that, it seems to work fine locally
[19:48] <Unit193> cyphermox: Right, I agree.  I used https://bitbucket.org/snippets/unit193/agkpy
[19:49] <Unit193> I personally like gtk2 better, so if there's anything that it's an option on.. :P
[21:31] <ochosi> bluesabre: pushed more artwork updates over the course of today, might push one or two more tomorrow, if time permits. so friday is definitely a good date for up-ing that.
[21:40] <bluesabre> ochosi: nice
[21:40] <bluesabre> Noskcaj: good to know
[21:40] <bluesabre> yay more bugs
[21:40] <bluesabre> :D
[21:47] <ochosi> and evening bluesabre
[21:49] <ochosi> what're you up to?
[21:49] <bluesabre> ochosi: not much, just got home
[21:49] <bluesabre> eating pizza rolls
[21:49] <ochosi> yummy
[21:49] <ochosi> bon appetit
[21:50] <bluesabre> :D
[21:50] <bluesabre> thanks for the geary fix
[21:50] <bluesabre> very nice at work
[21:50] <bluesabre> :D
[21:50] <bluesabre> aaaaand done
[21:51] <ochosi> heh
[21:54] <ochosi> yeah, i went through the issues list for greybird today and tried to cut it in half
[21:54] <bluesabre> nice work
[21:54] <ochosi> i'm sort of hesitant as to whether i should try plain gtk3 without any ubuntu mods
[21:54] <ochosi> i guess that would expose more issues
[21:55] <ochosi> but then again, i really don't want to have to rebase on adwaita
[21:55] <ochosi> so i might do a greybird 1.6 next
[21:55] <ochosi> since it does in fact provide basic gtk3.16 support
[21:55] <bluesabre> yeah
[21:55] <bluesabre> sounds reasonable
[22:00] <ochosi> anyway, if you get around to testing wily more and if you see more glitches there, please let me know
[22:00] <ochosi> would prefer to get in a few more fixes before 1.6, but i also want to release soon
[22:17] <bluesabre> np
[22:17] <bluesabre> I actually run wily as my main now
[22:23] <bluesabre> and that is to say that I don't really have any issues
[22:24] <bluesabre> other than my minor gripes about gtk 3.16 usability


[05:15] <Bashing-om> Gdoc: Ubuntu Core 20 - considering the media attention as a release, do we want to move the article up from the Planet to General Community?
[05:41] <guiverc> yes I'd vote moving up Bashing-om (Ubuntu Core 20)
[05:43] <Bashing-om> Gdoc: Moving Ubuntu Core 20 up :)
[12:28] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: LibreOffice 7.1 Released, This is What’s New @ https://www.omgubuntu.co.uk/2021/02/libreoffice-7-1-release-download (by Joey Sneddon)
[16:32] -SwissBot:#ubuntu-news- ::Planet:: Alan Pope: Let's Go Snapping @ https://popey.com/blog/2021/02/lets-go-snapping/
[17:39] -SwissBot:#ubuntu-news- ::Planet:: Daniel Llewellyn: Getting started with Flutter on Ubuntu @ https://diddledan.com/getting-started-with-flutter-on-ubuntu/


[05:25] <ScottK> Is pending-sru known to be broken?  It's rather empty ATM>
[05:53] <infinity> ScottK: Fun.  I'll clear the cache and see if it fixes itself.
[05:54] <ScottK> Thanks.
[08:30] <NCommander> infinity, cjwatson, ping, can one of you reset or remove the expiration on my membership in ~ubuntu-release
[08:32]  * NCommander isn't even sure why he's set to expire
[08:37] <ogra_> NCommander, thats a default on LP for moderated teams
[08:38] <ogra_> user expiration is pre-set to 1 year iirc
[10:01]  * ogra_ cries
[10:45]  * xnox ponders if "* ogra_ cries" correlates with britney migrating new fuse to saucy-release.
[10:45] <ogra_> xnox, heh, nope, it just correlates with my incompetence :)
[10:46] <ogra_> (forgot to make sure the chroot on the builder has  /etc/resolv.conf before trying to install a package during build)
[11:39] <ScottK> infinity: That didn't do it.
[12:16] <ogra_> ARGH !
[12:16]  * ogra_ stamps his foot
[12:17] <ogra_> Ign http://ftpmaster.internal main Release
[12:17] <ogra_> Err http://ftpmaster.internal main/universe armhf Packages
[12:17] <ogra_>   404  Not Found
[12:17] <ogra_> Ign http://ftpmaster.internal main/universe Translation-en
[12:17] <ogra_> W: Failed to fetch http://ftpmaster.internal/ubuntu/dists/main/universe/binary-armhf/Packages  404  Not Found
[12:18] <ogra_> godamnit ... !
[12:28]  * gema brings ogra_ a coffee to set the mood right again!
[12:29] <ogra_> heh, its fine ... its just that i have to wait for 2h for such a minor typo
[12:29] <ogra_> (and another 2h to check it is fixed)
[12:31] <gema> hence the coffee :D
[12:32] <ogra_> i wish the livefs builders would just pull livecd-rootfs dircetly from proposed
[13:20] <zul>  can an archive admin promote d2t1o (#1183825) and python-pbr (#1183826) please we have a couple of packages that are dep-waited because of them
[14:38] <bdmurray> what has happened to the pending sru report?
[16:01] <NCommander> ogra_, then why am I and skaet the only two with an expiration date?
[16:02] <ogra_> no idea
[16:02] <ogra_> i'm not in that team
[16:21] <stgraber> pending-sru appears to be broken. The cronjob was running twice on lillypilly.
[16:22] <stgraber> I'm disabling the cron entry and running it by hand see if it's just taking a longer time than usual (> 30min) or if there's actually something wrong with it
[16:57] <ogra_> does britney have a hiccup ?
[16:58] <ogra_> livecd-rrotfs sits idling in proposed since over 1h now
[16:58] <infinity> ogra_: Which hiccup would that be?
[16:58] <ogra_> i usually get a migration mail after about 30-45min
[16:58] <infinity> It's more likely that lillypilly's just overloaded or something.
[16:59] <ogra_> ah well
[17:00] <infinity> load average: 56.58, 46.09, 57.73
[17:00] <infinity> Never a good sign.
[17:00] <ogra_> oh sigh
[17:01]  * ogra_ might need one more livecd-rootfs upload today before being done ... would be nice if that actually could happen today :)
[17:01] <infinity> doko: Are you using lillypilly as a lintian lab? :P
[17:01] <ogra_> on the whole archive ?
[17:01] <ogra_> :)
[17:11] <doko> infinity, doing an archive search
[17:11] <infinity> That's more or less what I meant, yes. :/
[17:12] <doko> but the load without my processes goes up to 50 as well
[17:12] <infinity> Except that it was 80 a few minutes ago.
[17:13] <doko> so what?
[17:13] <doko> I did open a ticket in the past, and it was closed
[17:19] <slangasek> is there an iorenice?
[17:20] <slangasek> doko: "so what" --> monopolizing the machine's IO means lots of other things are failing to work because of timeouts
[17:20] <infinity> I think it's called "not unpacking multiple packages in parallel".
[17:20] <doko> slangasek, I'm just using the for-archive tools from the security team
[17:21] <slangasek> doko: well, these tools are clearly doing a number on lillypilly.  I don't know if the security team has somewhere else that they run them?
[17:21] <doko> slangasek, and no, even without this task the machine is overloaded
[17:21] <infinity> Yes, we know it's overloaded even without it, adding to the problem doesn't help.
[17:22] <doko> well, I would like to know which packages are broken in the archive
[17:23] <doko> slangasek, for-archive already does:
[17:23] <doko> # Try to stay out of the way of the rest of the system
[17:23] <doko> ionice -c 2 -n 7 -p $$
[17:24] <slangasek> hmm :/
[17:24] <slangasek> doko: I'm not saying that running the scan isn't worthwhile, I'm saying it's a problem to do this on lillypilly
[17:24] <slangasek> is that the only machine we have a mirror on?
[17:25] <doko> afaik, yes
[17:29] <ogra_> ha !
[17:29] <ogra_> seems at least britney got some cycles
[17:29] <ogra_> my package finally moved out pf proposed after 2h now
[19:31]  * ogra_ curses
[19:32] <ogra_> so why is the groouper kernel behaving completely different from manta, maguro and mako
[19:33] <ogra_>     for subarch in $touchsubarches; do
[19:33] <ogra_>         kpkg="$(Chroot chroot apt-cache depends linux-image-$subarch|grep Depends|sed -e 's/  Depends: //')"
[19:33] <ogra_>         kver=${kpkg#linux-image-}
[19:33] <ogra_>         Chroot chroot "apt-get -y install $kpkg
[19:33] <ogra_> why would:
[19:34] <ogra_> Chroot chroot "env FLASH_KERNEL_SKIP=1 update-initramfs -k $kver -c -v"
[19:34] <ogra_> fail ?
[19:34] <ogra_> it works fine for the other kernels
[19:35] <ogra_> but all i get is ...
[19:35] <ogra_> update-initramfs: Generating /boot/initrd.img-3.1.10-2-grouper
[19:35] <ogra_> df: Warning: cannot read table of mounted file systems: No such file or directory
[19:35] <ogra_> Setting up linux-firmware (1.109) ...
[19:35] <ogra_> Invalid argument for option -k
[19:38]  * ogra_ doesnt get it ... the versioning scheme is the same for all of them
[19:39] <bdmurray> 'Rejected by Brian Murray: A regression potential statement was not provided in the bug being fixed by this upload.'
[19:40] <bdmurray> \o/
[20:09] <infinity> bdmurray: Oh, and I just committed to ubuntu-archive-tools to force rejection comments from the queue tool.  I'll email people about this shortly.
[20:14] <NCommander> infinity, ping, can you reset (or better yet) remove the expiration from me on ~ubuntu-release?
[20:46] <jamespage> ^^ any sru team members that keystone upload fixes a time based FTBFS that happened between upload and accept.
[20:57] <infinity> jamespage: That's disconcerting.
[20:58] <jamespage> infinity, test certificates expired between my original upload and it actually building
[20:58] <jamespage> I'm always amazed at how often this actually happens
[20:58] <jamespage> 2nd time in a year (different projects - the other was tomcat7)
[20:58] <infinity> jamespage: So, is that an ongoing concern?  These test certs surely shouldn't have expiries, or it's a pain for future security updates, etc.
[20:59] <infinity> jamespage: Given that they're snakeoil anyway, can you either get upstream to generate them with insane future expiry dates (like, 2099), or generate them at build-time?
[21:00] <jamespage> infinity, they now all expire in 2023
[21:01] <jamespage> if anyone is still using folsom by then they are insane
[21:01] <infinity> jamespage: Ahh, indeed some of these say 2112 even.  That works.
[21:02] <infinity> jamespage: 2023 isn't actually that far off, in software bitrot terms, but it's certainly past any of our LTS commitments, so good enough for me.
[21:24] <infinity> bdmurray: So, on the one hand, I want to try out your new SRU tool.  On the other hand, I'm afraid I'll hate it and bombard you with feature requests/changes and/or spend hours fixing it myself. :P
[21:31] <bdmurray> infinity: great, now I'm afraid of you trying it out ;-)
[21:32] <infinity> bdmurray: *grin*
[21:32] <infinity> bdmurray: The intro mail scared me a bit.  It doesn't force me to open all bugs in web browsers before I start, does it?
[21:35] <bdmurray> infinity: it does open the bugs in a web browser - it looks like that was suggested by someone " - the ability to open all the bugs (by default)"
[21:36] <infinity> bdmurray: That (by default) may have been misread.
[21:36] <infinity> bdmurray: I'd read it as "Open (all) bugs in browser? [y/n/A]", and y could perhaps give me a list and ask which one(s).
[21:37]  * bdmurray feels bombarded
[21:37] <infinity> bdmurray: Gets increasingly irritating if I'm processing an SRU that's been uploaded for 3 series' and I have to "review" the bugs three times, though the first pass was good enough.
[21:38] <bdmurray> hey, but you don't have to check the box anymore and click accept!
[21:38] <bdmurray> plus you can reject with a message!
[21:38] <stgraber> s/can/have to/
[21:41] <bdmurray> Seriously though, I understand the bugs idea better now
[22:30]  * ogra_` curses
[22:31] <ogra_`> i really dont get that error ... damnit
[22:31] <infinity> ogra_`: Which?
[22:31] <ogra_`> infinity, cadejo.buildd/~buildd/LiveCD/saucy/ubuntu-touch/latest/
[22:31] <ogra_`> have a look at the end
[22:32] <ogra_`> i have a loop that installs the four kernels (and removes them)  and calls update=initramfs and abootimg in each loop to create bootimg's
[22:32] <infinity> Is that you calling update-initramfs, or the linux-firmware postinst?
[22:32] <ogra_`> the first two loops run fine
[22:33] <ogra_`> the third (grouper) fails with "invalid option to -k" from update-initramfs
[22:34] <ogra_`> http://paste.ubuntu.com/5714938/
[22:34] <ogra_`> thats the code
[22:35] <infinity> Oh, that looks obvious to me, but let me confirm my suspicion.
[22:35] <ogra_`> obviously $kver works fine for maguro and mako
[22:35] <ogra_`> the version schema is identical
[22:36] <ogra_`> just different numbers and chars but always the same setup
[22:37] <infinity> What's the fourth?  I get confused with the fish..
[22:37] <ogra_`> touchsubarches="maguro manta grouper mako"
[22:38] <infinity> http://paste.ubuntu.com/5714943/
[22:38] <ogra_`> hmm
[22:38] <infinity> And I'd probably make that awk, just cause I hate the grep|sed pipe.
[22:38] <ogra_`> i cant imagine what the 10 would make different
[22:39] <ogra_`> no no, that part works fine
[22:39] <infinity> for subarch in maguro manta grouper mako; do apt-cache depends linux-image-$subarch| awk '/Depends: linux-image/ {print $2}'; done
[22:39] <ogra_`> kver=${kpkg#linux-image-}
[22:39] <ogra_`> that part doesnt
[22:39] <infinity> Huh?  It's not the 10 that's different, it's the linux-firmware.  You didn't read the paste. :P
[22:40] <ogra_`> or rather Chroot chroot "env FLASH_KERNEL_SKIP=1 update-initramfs -k ${kver} -c -v"
[22:40] <infinity> The first is your code, the second mine.  Notice the two fewer lines in the results.
[22:40] <ogra_`> uh oh !
[22:40] <infinity> Shall I just commit my fix to livecd-rootfs for you? :)
[22:40] <ogra_`> ok
[22:40] <ogra_`> yeah, please
[22:42] <infinity> ogra_`: Have any other fixes you want, or shall I tag and upload?
[22:42] <ogra_`> no, i actually thourgh i was done already, no mre fixes
[22:43] <ogra_`> i just hope my assumption that all this doesnt land inside the tarball is correct :)
[22:43] <ogra_`> but if not, thats something for tomorrow
[22:43] <infinity> Oh, wait.  Escaping hell might make that awk print fail in live-build's Chroot function.
[22:45] <infinity> Ahh, looks like I've used that construct before and it didn't break. :P
[22:45] <ogra_`> i stole a lot from aabove code :)
[22:47] <infinity> ogra_`: Uploaded.
[22:47]  * ogra_` hugs infinity


[00:15] <^arky^> geser: thank you will remember to use update-maintainer in future
[05:14] <ddecator> can someone familiar with 'ar' look at this and let me know why it returns "ar: two different operation options specified"?: http://pastebin.ubuntu.com/398155/
[05:14] <ddecator> (i get this while trying to get sqlite to build for songbird)
[05:17] <persia> ddecator: I think you7re missing an instruction.  I think you need `ar r ${FILES}` or similar.  I may be mistaken.
[05:17] <ddecator> persia: i'll give that a shot. thanks
[05:18] <persia> ddecator: man ar : you man need some modifiers (e.g. "rc" rather than "r")
[05:18] <ddecator> persia: thanks. i'm not very good at figuring out when to use which arguments for what yet, haha
[05:19] <persia> The trick is with older programs like tar or ar where the '-' is optional for passed options.
[05:20] <persia> e.g. `tar xf ...` and `tar -xf ...` are equivalent.  Woe betide the person who tries to deal with xf.tgz unprepared.
[05:23] <ddecator> of course, now i get the fun of what script is causing it to revert back to 'ar' instead of 'ar r'
[05:24] <persia> Really, `ar r` may not be complete.
[05:24] <persia> And I'm not a big ar user, I just read the manual, so I could be completely wrong.
[05:24] <persia> So my recommendation would be to play with ar and make sure you understand which command you want.
[05:24] <persia> Only then does it make sense to fiddle the build scripts.
[05:28] <ddecator> i'll do that once i can figure out where the makefile is being auto configured so that any changes i make are reverted...
[05:30] <persia> Usually in ./configure
[05:31] <ddecator> right, it's just a huge file, haha
[05:32] <ddecator> oh wait..
[05:33] <ddecator> looks like it's supposed to use 'ar cr' but the conditions aren't right or something...heading in the right direction though
[05:35] <persia> cr or rc would make sense, based on the manpage.
[05:37] <ddecator> what the...even the configure file got reconfigured on me
[05:37] <persia> Do you have configure.in or configure.am ?
[05:38] <persia> If so, those are the culprits .am -> .in ->
[05:38] <persia> If not, check debian/rules (or for a new package, INSTALL) for guidance.
[05:39] <ddecator> it's just "configure" there is no "configure.am" or "configure.in", but there are "config.*" files and a "configure.ac"
[05:39] <persia> check configure.ac, but check debian/rules and INSTALL
[05:39] <ddecator> configure.ac is blank...
[05:39] <ddecator> nvm
[05:40] <ddecator> typed the name wrong, haha
[05:40] <ddecator> i'm not used to using terminal for everything...
[05:44] <ddecator> yah, even configure.ac is being autoconfiged
[05:53] <ddecator> even config.cache is resetting...
[05:54] <ddecator> nope, never mind, making progress...
[05:55] <persia> Really, check INSTALL or debian/rules.  It will explain how the build happens.
[05:58] <ddecator> i setup the rules file for this part of the build, not sure where the INSTALL file is located
[07:35] <ddecator> i've identified the problem as $(AR) not being defined correctly, but i can't find where it's defined
[07:36] <persia> might be an implicit define : check the make manual (no, not man make, but the real manual)
[07:42] <ddecator> aha, i think i figured it out. thanks persia
[07:43] <ddecator> yup, that did it =)
[07:43] <persia> Great.
[08:08] <anzenketh> Hello i was wondering where there is more information in regards to the rules file. Or a updated version of https://wiki.ubuntu.com/PackagingGuide/Complete
[08:09] <anzenketh> I am trying to make a package from scratch
[08:10] <hyperair> anzenketh: http://www.debian.org/doc/debian-policy/ch-source.html <-- see section 4.9
[08:11] <hyperair> you're advised to use debhelper though
[08:11] <anzenketh> I plan on using debhelper
[08:12] <hyperair> man dh
[08:12] <anzenketh> basicly so far I have run dhmake edit the changelog edited control and edited copyright
[08:12] <hyperair> dh_make's debian/rules is hopelessly outdated.
[08:12] <anzenketh> ahh
[08:13] <hyperair> just rm it and copy the one from /usr/share/doc/debhelper/examples/rules.tiny
[08:13] <hyperair> you'll have to bump debhelper's version in build-depends to 7.0.50 as well
[08:14] <anzenketh> Do I still want to use dh_make to make the other files
[08:15] <anzenketh> Or is there a new updated way to create all of the debian files
[08:25] <anzenketh> Basicly I am looking for the best place to learn how to create my first ubuntu package from scratch.
[08:57] <persia> hyperair: Don't need 7.0.50 for rules.tiny: only 7.0.0.  7.0.50 is for overrides.
[08:58] <persia> anzenketh: I'll really put this on a wiki page soon, but here's the recipe:
[08:58] <persia> 1) mkdir -p ${package}/debian; cd ${package*
[08:59] <persia> 2) echo 7 > debian/compat; cp /usr/share/doc/debhelper/examples/rules.tiny debian/rules
[08:59] <persia> 3) dch --create to generate debian/changelog
[08:59] <persia> 4) create debian/control based on policy 5.2
[09:00] <persia> 5) create debian/watch based on man uscan
[09:00] <persia> 6) uscan to get the latest sources; unpack; move debian/ in there.
[09:00] <persia> 7) review *all* the files and generate debian/copyright (DEP5 is nice)
[09:01] <persia> 8) build the source and fix bugs as you find them
[09:11] <anzenketh> persia: how up to date is the maint-guide obtained though sudo apt-get install maint-guide
[09:12] <persia> anzenketh: Looks like it hasn't changed in at least a year.
[09:12] <persia> anzenketh: Check the changelog for more.
[09:15] <anzenketh> looks like sep 2008 how much would I be missing on that becosue the wiki is not up to date the maitnance guide is not up to date
[09:15] <persia> Both the maint-guide and the wiki will give you usable instructions.
[09:15] <anzenketh> Basicly would I know enough to sucessfuly create a package
[09:15] <anzenketh> ok
[09:15] <persia> Following my quick guide above may or may not be easier/faster depending on your upstream source.
[09:16] <anzenketh> It is a rather complecated package
[09:16] <persia> why?
[09:17] <anzenketh> It is amahi I am trying to port it over to ubuntu. Complecated due to it includes inits and adds to the bins
[09:17] <anzenketh> but that is about the complexity of it
[09:17] <persia> What do you mean "adds to the bins" ?
[09:18] <ddecator> just for the record, i found the MOTU videos to be helpful, even if they are outdated ;)
[09:18] <anzenketh> Ya I watched those too I understand everything but rules
[09:18] <persia> For includes inits, dh_installinit should do the job, and rules.tiny runs that automatically.
[09:19] <persia> Really, unless you need something special, use rules.tiny.
[09:19] <persia> It works 90% of the time without extra thought.
[09:21] <anzenketh> Basicly this package is a ruby source with some c creates some init.d files and most the files go to /usr/bin and changes some config files and adds some directories
[09:23] <persia> Adding init.d files and putting files in /usr/bin is fine (as long as it doesn't conflict with other files there).
[09:24] <anzenketh> it won't
[09:24] <persia> Changing configuration files is only allowed if those configuration files are specifically related to your package.  Changing conffiles is futher only permitted if the user hasn't changed them manually.
[09:25] <anzenketh> the tiny will create the directories as long as i have them specified right?
[09:26] <persia> rules.tiny will install everything in the places specified by the upstream build system install rule.
[09:27] <persia> You can use debian/amahi.install to add anything that is missing.
[09:27] <sebner> hyperair: grrrrr, 87MB updates and no banshee :\
[09:27] <anzenketh> ahh ok
[09:27] <sebner> huhu persia :)
[09:27] <anzenketh> I think I will give it a wearl
[09:27] <persia> anzenketh: It does assume the upstream build system just works.  If that's not true, it's worth fixing it upstream.
[09:30] <directhex> sebner, i'm not leaning on anyone since 1.5.6 is due within hours-ish
[09:30] <sebner> directhex: wasn't that the same with 1.5.5 ^_^
[09:31] <directhex> sebner, ywah, but there was a freez
[09:32] <directhex> also, b-c-e clearing NEW is good news for us
[09:32] <sebner> directhex: freeze, pffffffffffffffffffffffffffff
[09:32] <sebner> directhex: sure
[09:33] <hyperair> sebner: hmm?
[09:33] <directhex> since it means archive admins can just trust debian & don't need to spend any time on ubuntu NEW
[09:33] <sebner> directhex: well, waiting for next week then :)
[09:33] <sebner> hyperair: ~~~ = 0_o = ~~~~
[09:33] <hyperair> sebner: it's in the PPA =D
[09:34] <sebner> hyperair: we need archive!
[09:34] <directhex> hyperair, is b-c-e in the PPA?
[09:34] <hyperair> directhex: er no it isn't.
[09:34] <hyperair> directhex: should we upload b-c-e to ubuntu?
[09:34] <hyperair> directhex: or do we have something we have to wait for... oh wait, stupid question.
[09:35] <directhex> hyperair, we need to wait for banshee to be synced, but given how imminent 1.5.6 is meant to be, i haven't leaned on anyone to sync 1.5.5
[09:35]  * hyperair sighs.
[09:35] <hyperair> oh well.
[09:35] <hyperair> let's hope 1.5.6 doesn't go the same way as the previous two.
[09:35] <Laney> patience, lads
[09:36] <Laney> i expect syncs will be done at the start of the week
[09:36] <hyperair> o yay.
[09:36] <hyperair> i'll be internetless for the next two days or so
[09:36] <hyperair> make that one and a half days.
[09:37]  * Laney pats hyperair
[09:37] <Laney> it'll be alright in the end, I promise
[09:37] <directhex> download the internets onto your hard disk so you aren't disconnected!
[09:37]  * hyperair weeps
[09:38] <hyperair> to maximize the clicheness of this moment, i suppose i should be burying my face in Laney's chest and bawling my eyes out
[09:39] <directhex> http://www.penny-arcade.com/comic/2002/7/1/
[09:40] <hyperair> ._.
[09:40] <hyperair> sign language?
[10:08] <muelli> hey folks :) I want to package a Python application which brings some public modules. It's called Volatility (from http://code.google.com/p/volatility/) and I have some problems with the packaging: setuptools installs everything as ./lib/python.../site-packages/ but Python in Ubuntu does not have site-packages in their PYTHONPATH. Does anybody know how to make setuptools install stuff in dist-packages?
[10:13] <anzenketh> persia: looks like i need to do it the hardware upstream does not have a build system.
[10:14] <persia> Do you know where things belong?
[10:14] <anzenketh> I can tell from the RPM .spec file
[10:15] <persia> Ugh.  Then you have to do the same hack in packaging.
[10:15] <persia> man dh_install, and put stuff in debian/amahi.install
[10:16] <anzenketh> does the amahi.install allow commands like install -m 755 -p file   directory
[10:17] <persia> anzenketh: No.  It allows commands like "bin usr/bin" which then expands into the right set of install -m ... calls.
[10:18] <persia> So it's much more concise: it's just sources and destinations, and doesn't bother the user with the actual implementation details.
[10:18] <anzenketh> ok good that means most of it was done right previously
[10:19] <anzenketh> how does the amahi.install know what permitions to give file?
[10:20] <persia> It uses the permissions from the source.  Later dh_fixperms goes though and tries to clean up.
[10:20] <anzenketh> ahh ok time for me to learn the CDBS
[10:20] <persia> Why?
[10:20]  * persia currently recommends against CDBS for new packaging : rules.tiny achieves the same goals, and is easier to debug
[10:21] <anzenketh> ok
[10:22] <anzenketh> so how would I compile a c file
[10:22] <anzenketh> it has one c file it needs to compile
[10:22] <persia> And that compilation happens in the .spec file?
[10:23] <anzenketh> yes in %prep it has a %setup -q and a make hdactl-hup
[10:24] <persia> Ugh.
[10:24] <persia> Well, you can do that by adding an override_dh_auto_build: rule to debian/rules
[10:25] <persia> But the *better* way to do it is to make an upstream Makefile that does the right thing.
[10:25] <persia> And then to share that for both types of packaging.
[10:25] <persia> That way if it needs to be adjusted, it only needs to be adjusted in one place.
[10:26] <anzenketh> I agree
[10:26] <anzenketh> now I need to think of a way to define upstream build system.
[10:26] <persia> vi Makefile ?
[10:27] <filip> can I debuild an i386 package on an amd64 system?
[10:27] <kklimonda> yes
[10:27] <persia> Um, no.
[10:27] <filip> ;)
[10:27] <persia> One can use sbuild or pbuilder to generate i386 packages on an amd64 system.
[10:27] <filip> you got me confused a bit :P
[10:27] <persia> One cannot use debuild alone
[10:28] <anzenketh> persia:  so a build something is something like a standard config and makefile
[10:28] <persia> anzenketh: Sure.  Or setup.py or build.xml, or ...
[10:34] <anzenketh> ugh upstream author refuses to make a build system.
[10:37] <anzenketh> Ehh oh well
[10:38] <persia> Then you get to duplicate code :(
[10:39] <anzenketh> Yep
[10:40] <anzenketh> He states it is 20 times more work and it never updates
[10:40] <anzenketh> Which may be true it is a old fedora package
[10:43] <persia> It's precisely the same amount of work, and half as much as duplication, *but* it's a bunch of work to migrate from package hacks to a real Makefile.
[10:43] <persia> So for now, just work around it.
[10:43] <persia> If enough people like amahi on Ubuntu, you will have leverage to share code between .spec and debian/rules in ./Makefile
[10:45] <anzenketh> Well it was already semiported I am just updating the port. And as it is there is duplicates of the same file.
[10:45] <anzenketh> Due to some require specific code in fedora and some specific in ubuntu.
[10:45] <persia> There's no good reason for that.  The code should be able to use lsb_release to figure out which distribution it's using, and do the right thing.
[10:46] <anzenketh> I would agree
[10:47] <persia> Then make your version do that, and submit patches upstream :)
[10:47] <muelli> oh, okay. my bad: setuptools installs correctly in ./dist-packages/ for python2.6 but cdbs
[10:47] <persia> Less maintenance overhead in the future.
[10:47] <muelli> ' install stage moves it to site-packages... ?
[10:50] <persia> muelli: Is this a new package, or are you trying to fix a bug?
[10:50] <muelli> persia: a new package. "Volatility" from http://code.google.com/p/volatility/. I'm not used to package stuff at all btw...
[10:51] <persia> muelli: OK.  So my recommendation is: if CDBS doesn't do what you want, use rules.tiny instead.
[10:52] <muelli> persia: hm. a quick google for that resulted in bug reports only. Do you have some more information or pointers to more information about that?
[10:53] <persia> muelli: cp /usr/share/doc/debhelper/rules.tiny debian/rules and `man dh`.  Ask in #ubuntu-packaging if you get stuck.
[10:53] <muelli> persia: thx. will have a look
[11:00] <muelli> heh. funky rules file -.- And the best thing: It (nearly) does what I want! holy cow!
[11:00] <persia> muelli: Are you using python-support?  There should be a built-in dh_pysupport call if you are.
[11:00] <shadeslayer> so... is there someone here who can update me with the latest 3.0 format?
[11:01] <shadeslayer> like point me to a doc..
[11:02] <muelli> persia: Sorry. I don't know whether I'm using "python-support". I started from scratch calling setup.py myself from the debian/rules, but I thought it was wrong. So I tried cdbs which messed installation up and now I'm using your rules.tiny.
[11:02] <persia> muelli: Add python-support to Build-Depends: in debian/control
[11:05] <muelli> persia: k. right now I put debhelper, cdbs, python-setuptools and python-central. But I will get rid of cdbs and python-central in favour of python-support, I guess.
[11:05] <muelli> persia: btw: shall we move this to #ubuntu-packaging? :)
[11:06] <persia> Even odds.  If you're planning to push this package into the main repos for lucid+1, it's equally on-topic in either place.
[11:07] <muelli> persia: k :)
[11:08] <muelli> oh, and I wouldn't mind pushing that but for now I only want to distribute that program easily using the great PPA system :) But I'm willing to do the right^tm steps so that the package is ready for inclusion. And would keep spending my time caring about it.
[11:12] <persia> For PPA stuff, #ubuntu-packaging is more on-topic : this channel is about working on Ubuntu directly
[11:22] <Anzenketh> persia: Thanks for your help I think i convinced him to change to cmake in the future for a packaging system.
[11:23] <Anzenketh> but right now he wants to do it this way
[11:23] <persia> Anzenketh: That's fine.  In my experience the best way to get someone to change their code is to patch it to do it the way you want, and still work the way they want, and share the patch.
[11:24] <Anzenketh> that is basicly what I will be doing is creating the patch to merge over to cmake and do it the way he wants for now.
[11:24] <Anzenketh> that requires me learning cmake
[11:24] <persia> I think make is easier, and powerful enough for what you're doing, but cmake could work.
[11:25] <Anzenketh> well his comment when i said cmake was that will help with a windows port
[11:25] <Anzenketh> I just rolled my eyes
[11:26] <persia> it's true.  cmake probably has better Windows support than make.
[11:26] <Anzenketh> I noticed somewhere if it is installing to a standard directory I only have to specify the file correct?
[11:26] <Anzenketh> or do I have to specify the path in the package.installer file
[11:27] <persia> I recommend using a variable to define the path, so that the various packaging systems can overrride the variable to whatever they need.
[11:28] <Anzenketh> I like that idea
[11:28] <Anzenketh> also reduces mistakes
[11:28]  * Anzenketh is looking for a example of that
[11:31] <Anzenketh> persia:  do you know of a good source I can look at to learn from on doing this
[11:31] <persia> I know nearly nothing about cmake.  Sorry.
[11:32] <Anzenketh> no not cmake the amahi.installer file
[11:33] <muelli> persia: which patch system do you suggest? I used cdbs' simple-patchsys so far but it doesn't work know anymore after I included simple-patchsys: the clean target is messed up.
[11:35] <persia> muelli: I've been using quilt lately, but I'm increasingly tempted by using Format: 3.0 (quilt) and not having a patch system at all (while still using quilt for local patch management).
[11:37] <muelli> persia: can I easily make quilt work with rules.tiny?
[11:37] <persia> Yeah.
[11:37] <persia> Two ways: 1) use Format: 3.0 (quilt), 2) replace "dh $@" with "dh --with quilt $@".  Pick one.  Don't use both.
[11:41] <Anzenketh> how do I make debuilder stop at creating the build directories in the temp files?
[11:46] <persia> Anzenketh: Why do you want it to stop?
[11:47] <Anzenketh> So I can verify the build directories are created correctly
[11:50] <persia> Anzenketh: Just check the build log.
[11:50] <Anzenketh> That is right that is there.
[11:52] <Anzenketh> persia: How do you compile one file that is in c in the rules file.
[11:56] <persia> Anzenketh: Add an override_dh_auto_build: rule to debian/rules.  Add the compilation instructions from the spec file in that rule.
[11:58] <Anzenketh> so something like this
[11:58] <Anzenketh> override_dh_auto_build:
[11:58] <Anzenketh> make hdactl-hup
[11:59] <Anzenketh> make hdactl-hup is all that was in there before.
[11:59] <Anzenketh> well in the .specs file
[12:02] <persia> Well, try that, and see if it works.
[12:02] <persia> If it doesn't work, then you may have to track down something else fom the .spec file.
[12:02] <Anzenketh> ok
[12:03] <Anzenketh> Thanks a lot for your help persia I am sure what I learn to this I will contribute 10 fold to some other ubuntu package
[12:03] <Anzenketh> And I am learning A ton
[12:16] <Anzenketh> persia: can you do variables in a package.install and if so how to do disclare them.
[12:16] <persia> You can't.
[12:17] <persia> But since you know the location of the source, and you know the destination, you shouldn't need it.
[12:18] <Anzenketh> ok
[12:18] <Anzenketh> I was just wondering to reduce typos
[12:18] <Anzenketh> not that there will be many it is actualy a small package
[12:20]  * abogani waves Anyone could review my merge proposal https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640 Thanks!
[12:20] <Anzenketh> if i call dh_installinit and dh_installcron I should not have to install them in the package.install right?
[12:21] <persia> Anzenketh: dh $@ will call them automatically.
[12:21] <persia> but read the individual dh_* manpages to be sure of behaviour
[12:21] <Anzenketh> ok cool
[12:23] <Anzenketh> it states note Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. but dh $@ should take care of that right?
[12:23] <Anzenketh> that is for dh_installinit
[12:25] <persia> dh $@ should take care of that.  You can always check what it will do with `dh --no-act ${COMMAND}`
[12:41] <Anzenketh> persia: when I run that command I get dh: specify a sequence to run or dh: Unknown sequence dh_installcron (choose from: binary binary-arch binary-indep build clean install)
[12:44] <persia> Right.  You need to use one of binary, binary-arch, binary-indep, build, clean, or install for ${COMMAND}
[12:45] <Anzenketh> oh ok
[12:47] <Anzenketh>  it goes dh_installinfo -a    dh_installinit -a    dh_installmenu -a
[12:48] <Anzenketh> but it is only called once
[12:48] <Anzenketh> and I have 2 init files
[12:48] <muelli> How can I make debuild produce an architecture independent .deb? It's pure python after all.. debin/control has Architecture: any set.
[12:49] <lifeless> set it to all
[12:49] <lifeless> have a look at the packaging guides for the meaning of Architecture - or debian policy, the primary reference for packaging
[13:03] <Anzenketh> persia: I need to so things post install what is the best way to do that?
[13:05] <persia> Anzenketh: What sort of thing do you need to do?
[13:06] <persia> Also, if you ask questions generally, someone else may answer faster :)
[13:08] <Anzenketh> Sorry Looks like the .spec has a post install that changes permitions of files and directories in addition to running a scruot
[13:08] <Anzenketh> script
[13:09] <Anzenketh> So basicly post install I need to run a shell script
[13:10] <persia> OK.  Permissions changes can be added with something like http://paste.ubuntu.com/398306/ in debian/rules
[13:10] <persia> What does the script do?
[13:14] <Anzenketh> Looks like it changes permitions and ownership of files. Then goes though and moves some files for post configuration. Then restarts some services.
[13:15] <Anzenketh> http://pastebin.ubuntu.com/398308/ that is the script
[13:15] <persia> OK.  Permissions/ownership you do with stuff like my paste.
[13:16] <persia> You *cannot* do the stuff that changes the samba configuration.
[13:16] <persia> (you'll have to work with samba differently)
[13:16] <persia> Same for openvpn
[13:17] <persia> and httpd
[13:17] <Anzenketh> Is there a way to tell the installer to run a shall script post install?
[13:17] <persia> and the apache user
[13:17] <persia> Yes, but first I'm going to tell you the bits that need adjustment :)
[13:18] <Anzenketh> Ya I know some permitions are off
[13:18] <persia> the %preun stuff and the hdactl.cache changes can be done in maintainer scripts.
[13:18] <persia> Not permissions.  You can't mess with other packages.
[13:18] <persia> http://women.debian.org/wiki/English/MaintainerScripts is the best document for maintainer scripts I know.
[13:18] <persia> I believe dh_installinit will do the service restart.
[13:18] <persia> The cache stuff may need manual additions.
[13:20] <Anzenketh> ok so for permitions change I can use the pastbin for the cache stuff I can do maintainer scripts
[13:21] <Anzenketh> Just to clarify There is no wat to change config files of other packages
[13:22] <persia> It is in direct contravention of policy.
[13:22] <persia> Many packages provide a programmatic way to adjust configuration under certain circumstances.
[13:22] <persia> I believe both apache and samba fall into this category.
[13:22] <persia> Read the documentation for those packages: you may be able to do something useful.
[13:37] <Anzenketh> So once I find that programic way how would I have the debian install run those commands.
[13:40] <persia> In the maintainer scripts.
[13:40] <Anzenketh> ok
[13:41] <persia> Note that if the packages you need to adjust *don't* already include such a thing, you'll need to work with those packages to enable such a tool.
[13:42] <Anzenketh> And I can not run commands like sed correct?
[13:53] <persia> http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
[14:27]  * abogani waves
[14:27] <abogani> Anyone could review my merge proposal https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640
[14:27] <abogani> Thanks!
[14:34] <nigelb> anyone noticed trouble with submittodebian?
[14:35] <nigelb> I said that patch has been submitted, but I dont see anything in the bug report
[15:25] <lfaraone> I was wondering if anybody had the time to review the merge proposal attached to bug 540934?
[15:28] <DktrKranz> persia: I prepared a preliminary UDD query to display mismatches between sha1sums from Debian and Ubuntu, output is http://merkel.debian.org/~dktrkranz/unmatch_sha1sums
[15:32] <persia> DktrKranz: Thanks.  That's not bad at all.  I'll take a look through them, and see if I can't identify some candidates to get back in sync for lucid+1
[15:33] <DktrKranz> persia: I'll adjust a bit more to be in a better display format and then ask lucas if it can be pushed as UDD cgi
[15:35] <persia> DktrKranz: Don't worry about it.  I think I can hit about 50% of it one-off, and the rest is probably relatively unfixable without deep social engineering.
[15:35] <persia> I actively recognise most of these packages as being special in one way or another.
[15:36] <persia> I may ask you for an update near DIF of lucid+1, but won't need it again until then.
[15:36] <DktrKranz> ok
[15:36] <persia> Adding it to UDD cgi just raises attention to it, and in many cases, we don't want that.
[15:37] <DktrKranz> script is on merkel. so I can run anytime
[15:37] <persia> (because the reason for the variation may reflect badly on Ubuntu<->Debian relationships)
[15:37] <persia> Perfect.  Thanks.
[15:37] <DktrKranz> if you want, I can adapt it to be run on a machine not restricted to DDs
[15:37] <DktrKranz> (alioth, that is)
[15:38] <persia> I certainly don't need that.  If there's another user who wants it, or if you have an interest in doing so yourself... :)
[15:39] <DktrKranz> Not that much, as I use merkel for UDD hacking ;()
[15:40] <persia> Well then :)
[15:40] <persia> But thanks again: as a one-time run, this is hugely useful to me.
[15:41] <nigelb> is submittodebian broken?
[15:42] <lfaraone> nigelb: please elaborate.
[15:42] <nigelb> I followed the instructions but nothing updated on bug
[15:42] <nigelb> and it seems to be diff-ing only the changelog and not the changes made to package
[15:43] <lfaraone> nigelb: it won't modify your bug, it'll submit a new bug to debian.
[15:44] <nigelb> thats strange because it searched debian bugs and asked me which bug this patch corrected
[15:44] <nigelb> I'm not talking about reportbug
[15:44]  * lfaraone will brb, no idea about your problem, it worked for me :)
[15:45]  * nigelb will try again
[15:49] <abogani> Anyone could review my merge proposal https://code.launchpad.net/~abogani/ubuntu/lucid/avrdude/avrdude.fix-529444/+merge/21640 ? Thanks!
[16:22] <nigelb> aha, my submittodebian troubles spring from sendmail I think
[16:26] <nigelb> which I have no clue to fix
[18:00] <ryanakca> Could someone please take a look at bug 538283 ?
[18:12] <crimsun> ryanakca: Uploaded; thanks for your contribution to Ubuntu Lucid!
[18:12] <ryanakca> crimsun: thanks
[20:24] <duanedesign> if or current version is 0.32.4-12ubuntu1  and the new upstream is 0.34.1-1 that would make our new package 0.34.1-1ubuntu2 ?
[20:24] <duanedesign> s/or/our
[20:41] <geser> duanedesign: almost, 0.34.1-1ubuntu1 as it's the 1st change to 0.34.1-1 (but contains all the unmerged colltected Ubuntu deltas)
[20:51] <duanedesign> geser: thank you. I had a feeling I was thinking about that wrong :)


[18:35] <boba_CH> hello - does anyone know where I can download a "beta" version of the 14-04 ubuntu version?
[19:50] <KojiroAK> boba_CH~ http://releases.ubuntu.com/14.04/ Search terms: Ubuntu 14.04 Download


[05:25] <darkxst> jbicha, so just to make sure we don't drop incorrect patches again ;)
[05:25] <darkxst> drop ubuntu_screensaver_fallback.patch
[05:25] <darkxst> (from gnome-shell)
[05:25] <darkxst> and keep ubuntu-lightdm-user-switching.patch
[05:25] <darkxst> ubuntu_lock_on_suspend.patch
[05:25] <darkxst> ^ keep
[05:29] <jbicha> darkxst: ok, I believe I did that https://launchpad.net/ubuntu/+source/gnome-shell/3.6.2-0ubuntu1


[03:05] <Raydiation> is <IP_ADDRESS> > 0.4.2 ?
[03:07] <mwhudson> Raydiation: in debian version numbers? yes
[03:07] <Raydiation> ty
[03:10] <mwhudson> Raydiation: fwiw
[03:10] <mwhudson> dpkg --compare-versions <IP_ADDRESS> '>' 0.4.2 && echo yes || echo no
[03:10] <Raydiation> nice :D
[07:54] <maxb> How *exactly* does the recipe build "build daily *if* branches changed" check work?
[07:54] <maxb> I'm seeing recipe builds seemingly spuriously rebuilding (with consequent upload failure) if the last build attempt was a manual request
[07:55] <maxb> It's as if manually requested builds don't update the last-branch-state metadata
[07:55] <maxb> Which come to think of it, they probably don't
[08:01] <maxb> spm: Thanks! I'm curious... fixing stacking loctions has a "phase 1" ?
[08:01] <spm> heh
[08:02] <spm> basically we run scripts/get-stacked-on-branches.py; get a complete dump; then from that I'll filter more or less based on your list and then apply scripts/update-stacked-on.py
[08:02] <spm> so I make sure I do hit everything; don't miss the odd one or two.
[08:02] <maxb> oh
[08:02] <maxb> I already kinda did that, unless the project has private branches I cannot see
[08:02] <spm> excessively paranoid? probably.
[08:03] <spm> ah
[08:03] <spm> having both won't hurt, just takes a little longer.
[08:03] <maxb> I wrote a launchpadlib / bzrlib script which trawls a project's branches for invalid stacking locations, and then prints a "Dear LOSAs ..." output ready for pasting into a question :-)
[08:03] <spm> haha
[08:04]  * spm adds a "Dear Losas, please ignore all maxb Questions" note to our daily routine >:)
[10:24] <mok0> I am having a problem with bzr builddeb -S ... it seems to not include the tarball in the .changes file, so uploads to my PPA are rejected. I need to manually build the source package using debbuild -S -sa
[10:37] <tumbleweed> mok0: -- -sa ?
[10:38] <mok0> tumbleweed: uhm, it doesn't know that switch
[10:38] <mok0> ah
[10:38] <mok0> :-)
[10:38] <mok0> "--"
[10:38] <mok0> tumbleweed: thank you
[10:40] <tumbleweed> mok0: np :) also very useful for -uc and -us
[10:40] <mok0> tumbleweed: indeed.
[11:19] <dpm> is there anyone from a maintenance squad around? There's no on-call contact listed on the channel's topic and I'm not sure who to ask
[11:19] <dpm> I just wanted to ask if someone could please have a look at bug 715854. It's causing us problems in building the language packs for the 10.04.2 release next week (i.e. broken Firefox translations). We might have a workaround for the languages affected in Lucid, but we'll hit the same problem when building the maverick language packs next, and the Natty ones especially.
[11:27] <bigjools> dpm: let me look
[11:27] <dpm> thanks bigjools
[15:30] <joey> mrevell: ping
[15:44] <joey> jml: ping
[15:44] <joey> since no mrevell
[15:47] <mrevell> Sorry joey, was on a call. Hi.
[15:48] <joey> hi mrevell. Can you please add<EMAIL_ADDRESS>to LP Announce?
[15:48] <mrevell> joey, Yep, no problem.
[15:48] <joey> mrevell: currently linaro is heavily dependent upon LP and they receive no notices of downtime
[15:49] <joey> mrevell: can you send over the announcement again to that address just to test that it works?
[15:51] <mrevell> joey, Done and done.
[15:51] <mrevell> joey<EMAIL_ADDRESS>gave me a bounce-back. I've forward it to you.
[15:55] <joey> mrevell: got it, ok, let's try linaro-dev then... one moment
[15:56] <joey> mrevell: http://lists.linaro.org/mailman/listinfo/linaro-dev
[15:56] <joey> mrevell: I'm not sure how that's going to work though
[15:56]  * joey thinkis
[17:16] <apw> is it possible from the launchpad api to tell the differnece between Incomplete (without responce) and incomplete (with response)
[17:29] <bcurtiswx> bug #561337 has spam, what is the reporting.. questions about launchpad itself?
[17:31] <bcurtiswx> https://answers.launchpad.net/launchpad/+question/144873
[17:31] <bcurtiswx> thanks :)
[18:14] <joey> mrevell: still here?
[18:17] <joey> mrevell: unping, figured it out
[19:56] <bdrung> bug #604548 contains a spam comment. what should i do?
[20:02] <micahg> bdrung: file a request on answers.launchpad.net/launchpad
[20:04] <bdrung> done
[20:15] <achiang> hm, are the armel buildds especially busy today?


[15:08] <kayve> I've just upgraded my Ubuntu and now my Classic Gnome is refusing to send app instances to other workspaces
[15:09] <kayve> Can someone please help me get my Classic Gnome behavior to where I can organize my apps between workspaces?  Thank you in advance.
[15:10] <kayve> I move them, they momentarily flash on the workspace navigator and return to the current worspace
[17:08] <chrisccoulson> pitti, bug 979251
[17:08] <ubot2> Launchpad bug 979251 in linux "Compiz hangs every time when undocking or changing display configuration" [Medium,Confirmed] https://launchpad.net/bugs/979251
[17:09] <seb128> pitti, https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/995435
[17:09] <ubot2> Launchpad bug 995435 in zenity "Zenity --list uses 100%cpu and does nothing" [Critical,Fix released]
[18:54] <rwb> Hi, I just upgraded to 12.04, and panel and desktop switcher is broken.  I was using 11.04 in fallback mode.  Now, my menu is grey (not black) the alt-right click on the panel does nothing.  and my desktop switcher won't remember settings.  Also when I click on a workspace in the switcher, it hides all the panels...  Any advice?


[06:08] <hyper_ch> hi there, I wonder, if baloo kcm / baloo kcm advanced will be added soon as package?
[07:08] <bipul> !info jenkins
[07:40] <aggrey> ishmael, is solr server off, b'se i am getting errors concerned with it
[07:48] <lordievader> Good morning.
[09:24] <Moscherkobold> good morning everyone
[09:25] <Moscherkobold> any suggestions how to sync some folders between my livingroom-pc (win7) and my office pc (kubuntu 14.04)
[09:28] <hateball> Moscherkobold: rsync + robocopy perhaps
[09:35] <Moscherkobold> hateball: how can I acess the files on the windows machine with rsync?
[09:36] <hateball> Moscherkobold: How are you sharing files now?
[09:36] <hateball> Moscherkobold: You'd use rsync on linux, and robocopy on Windows. Or just one of them.
[09:37] <Moscherkobold> they are freed one the windows machine and i can acess them in dolphin with the samba thing
[09:46] <lordievader> Can't rsync do samba?
[09:46] <Moscherkobold> hateball: they are shared one the windows machine and i can acess them in dolphin with the samba thing
[09:47] <Moscherkobold> lordievader: I dont know, I think it is possible but i dont know how at the moment
[09:47] <hateball> I'd mount the SMB share on the linux machine, and treat it like a local folder
[09:47] <lordievader> Moscherkobold: http://rsync.samba.org/examples.html
[09:49] <Moscherkobold> hateball: lordievader thank you I will try this later this day
[12:48] <BluesKaj> Hiyas all
[14:56] <Riddell> ** anyone on trusty? we need testers for kde-workspace 4.11.11 ping me in #kubuntu-devel if you can help
[15:15] <barby> hello
[15:15] <barby> i need to share a disk with rdesktop
[15:15] <barby> does anyone can help me?
[16:51] <Dat> hello, I was using the latest and greated kubuntu and did a recent update a few days ago and it seems I have lost my desktop.  Anyone maybe can help me?
[18:06] <ikonia> if you just explain the problem, people will help if they want to and can
[18:06] <Guest31731> I am a newie and trying to make DOS boot a secondary HDD so later on I can remove it an put it in another PC to use it as primary. If you want me to explain why then it is going to be a long story...
[18:06] <Guest31731> thanks ikonia
[18:06] <ikonia> ok, so what do you mean by dos boot a secondary hdd ?
[18:06] <ikonia> do you mean the grub boot loader ?
[18:07] <Guest31731> DOS or WinXP Operative systems
[18:07] <ikonia> Guest31731: so that's really an ubuntu issue
[18:08] <Guest31731> ??
[18:08] <ikonia> Guest31731: configuring windows XP isn't really something that's part of ubuntu
[18:08] <Guest31731> I know
[18:08] <ikonia> ok ? so you're in #kubuntu
[18:08] <Guest31731> I don't want help to configure WInXP
[18:08] <ikonia> ok, what do you actually want
[18:08] <Guest31731> I am running kubuntu on this pc
[18:09] <Guest31731> OK, it is going to be a little long jajja
[18:09] <ikonia> doesn't need to be long
[18:09] <Guest31731> I have 2 PCs, almost the same
[18:09] <ikonia> "what do you want to happen"
[18:09] <ikonia> what is the answer to that question
[18:09] <Guest31731> One is this one running ubuntu
[18:09] <Guest31731> the other one needs to run WinXP as there is a soft I can only use in WinXP and I don't have the hardware requirements to run a virtual PC
[18:09] <Guest31731> But....
[18:10] <ikonia> "what do you want to happen"
[18:10] <ikonia> just answer that question
[18:10] <Guest31731> both PCs are old so there is no USB boot option
[18:10] <Guest31731> the other PC at the moment cannot even boot from a CD or DVD
[18:10] <ikonia> ok, I've lost interest
[18:11] <Guest31731> Ok thanks anyway
[18:11] <Guest31731> anyone else who can help please?
[18:12] <lordievader> Guest31731: Try to explain clearly what you are trying to do.
[18:12] <Guest31731> sorry I was concentrated in my explanation and I missed your questions
[18:12] <Guest31731> I NEED to make the other PC work with WINXP and I only have this PC with kubuntu to help me doing that
[18:13] <lordievader> Guest31731: Burn an iso.
[18:13] <Guest31731> and then what? I can't use USB or DVD on the other PC
[18:14] <lordievader> Ah, is it capable of reading a CD?
[18:14] <Guest31731> no
[18:14] <Guest31731> only using an external CD via USB but that does work only once in WINXP or Kubuntu, etc
[18:14] <lordievader> Guest31731: And you want to install Windows on it?
[18:15] <Guest31731> I need to install winxp on it, yes
[18:15] <BluesKaj> buy a cdrom drive for 25bucks
[18:15] <Guest31731> no, it is a notebook, military type,
[18:15] <lordievader> Guest31731: Good luck, Windows doesn't like to be transfered from hardware to hardware.
[18:15] <Guest31731> the PCs are almost the same specs, manufacturer, etc
[18:16] <ikonia> the host id's are different
[18:16] <lordievader> Guest31731: Put the hdd in the other pc and install from there. But don't come crying when Windows blue screens when you put the drive back into the original pc.
[18:17] <Guest31731> that is more or less what I am trying to do
[18:17] <Guest31731> but there are catchs
[18:17] <ikonia> this really isn't an ubuntu issue
[18:17] <ikonia> (kubuntu)
[18:17] <Guest31731> but Kubuntu can help as it is what I am running
[18:17] <ikonia> kubuntu has nothing to do with it
[18:18] <lordievader> Guest31731: Kubuntu cannot help with installing Windows ;)
[18:18] <Guest31731> I don't need help to install windows, just to make that HD boot on DOS or WINXP
[18:18] <ikonia> that's nothing to do with kubuntu
[18:18] <ikonia> and therefore nothing to do with this channel
[18:18] <Guest31731> I just need to write that info on the MBR using kubuntu
[18:19] <ikonia> no you don't
[18:19] <ikonia> the mbr will not install windows
[18:19] <Guest31731> but If I am able to write into that and install a FreeDOS or something with support for USB then I am fine
[18:19] <ikonia> no, you're not
[18:20] <ikonia> free dos has nothing to do with it
[18:20] <Guest31731> actually I've found a couple of tools which can do the job
[18:20] <ikonia> great
[18:20] <Guest31731> it is just me that I am not very good to understand the instructions
[18:20] <ikonia> which tools ?
[18:20] <Guest31731> as I am quite new with Kubuntu
[18:21] <Guest31731> plopKexec
[18:21] <Guest31731> plopKexec
[18:22] <ikonia> thats nothing to do with kubuntu
[18:22] <Guest31731> it looks like it runs on kubuntu
[18:22] <Guest31731> you think it doesn't?
[18:22] <ikonia> it doesn't run on anything
[18:22] <ikonia> it's a boot manager
[18:22] <ikonia> it lives on the masterboot record of a disk
[18:22] <lordievader> Guest31731: Have you read their page: Its based on a Linux Kernel and can load only other Linux kernels!
[18:22] <lordievader> Won't boot Windows.
[18:23] <Guest31731> but it will give me access to USB
[18:23] <ikonia> no it won't
[18:23] <lordievader> Guest31731: Like BluesKaj suggested, your best bet is to simply go out and buy a cd/dvd drive.
[18:24] <Guest31731> no I can't as my new solid state hard disk occupies the space where the CD player goes
[18:24] <Guest31731> It says on the website: You can boot Linux from USB even if there is no Bios USB support.
[18:24] <ikonia> Guest31731: right, you can do that
[18:24] <ikonia> Guest31731: however you want to boot windows
[18:24] <ikonia> you can't do that
[18:25] <lordievader> Guest31731: Why would you put an ssd into an old XP machine?
[18:25] <Guest31731> This tool is by the same guy who made Plop and I used plop to boot DOS from USB, that is my confusion then, sorry
[18:25] <lordievader> Forgive me, but my logic fails me here.
[18:25] <ikonia> Guest31731: listen very carefully
[18:25] <ikonia> Guest31731: "what you want to do is not practical, nor is it anything to do with kubuntu - this is not the channel you need"
[18:26] <Guest31731> because the old HD needs an adapter that it is broken and it happened that I have a SSD disk and its adapter
[18:26] <lordievader> Guest31731: ##windows is a more suited channel.
[18:27] <Guest31731> It won't because I am running Kubuntu and I don't have access to any other PC
[18:27] <Guest31731> My option is probably Plop
[18:27] <ikonia> it is not
[18:27] <Guest31731> I just need opinions about it
[18:27] <ikonia> but if you think it is, talk to the plop support resources to find out how to do it
[18:28] <Guest31731> Ok if you don't want to help you don't have to
[18:28] <Guest31731> I can't be sending emails and waiting for answers, it will take me months
[18:28] <ikonia> then talk to the plop resources
[18:28] <ikonia> this channel is not what you need
[18:28] <ikonia> please drop the topic
[18:29] <Guest31731> are you the administrator of the channel?
[18:29] <ikonia> that has nothing to do with it
[18:29] <ikonia> the topic of this channel is for kubuntu support
[18:29] <Guest31731> or maybe you were busy with some other topic?
[18:29] <ikonia> not 3rd party applications that are nothing to do with kubuntu being configured to do things that are outside of kubuntu
[18:29] <Guest31731> It looks like you don't want people to become insterested in using Kubuntu
[18:30] <ikonia> Guest31731: ok
[18:30] <ikonia> Guest31731: either way, it's a dead topic
[18:31] <Guest31731> so it is forbidden by you to talk about it?
[18:31] <ikonia> Guest31731: correct
[18:31] <Guest31731> are you the admin?
[18:31] <ikonia> Guest31731: not that it matters
[18:31] <ikonia> but yes
[18:32] <Guest31731> have good luck, because with that attitude you are going to need it...
[18:32] <ikonia> ok, thanks
[19:33] <ShalokShalom> hi there, what is the path to costumize the kdm themes please ?
[19:40] <BluesKaj> ShalokShalom, system settings>login screen, but why are you using kdm ?
[19:41] <ShalokShalom> BluesKaj: Its for a friend of mine. I mean: Where is the path in the filestructure, where the kdm themes are saved ?
[19:41] <ShalokShalom> He want to edit a theme from kde look
[19:42] <ShalokShalom> you recommend lightdm or sddm ? or another one ?
[19:44] <BluesKaj> ShalokShalom, the theme installer for the login screen has the option to install from a file. lightdm is default on 14.04 that uses plasma4 which is also default
[19:45] <ShalokShalom> He want to edit a downloaded theme
[19:46] <ShalokShalom> change the wallpaper of a complete kdm theme
[19:50] <BluesKaj> yes tell him to use the login page installer in system settings and choose the file after he edits
[19:50] <ShalokShalom> how to edit it ?
[19:50] <ShalokShalom> somebody explain me the path in #suse, i am on openmandriva
[19:51] <ShalokShalom> i mean, somebody in #kde explain me the path in openSUSE
[19:51] <BluesKaj> how does he want to edit the image or just use the image at the login page
[19:53] <lordievader> ShalokShalom: You are not on Kubuntu? Paths to such things are often disto specific.
[19:54] <ShalokShalom> lordievader: yep, thats the question, why i ask here ;)
[19:56] <lordievader> ShalokShalom: Lightdm themes are in "/usr/share/kde4/apps/lightdm-kde-greeter/themes".
[19:56] <ShalokShalom> kdm ?
[19:56] <lordievader> ShalokShalom: Kubuntu used lightdm by default.
[19:57] <lordievader> Uses*
[19:57] <ShalokShalom> he use KDM
[19:57] <BluesKaj> there's no other theme available unless he downloads from kde-look or some such, then he gas to install it from the downloads folder by clicking on the background image in the login page to find the load from file option
[19:57] <ShalokShalom> yes
[19:58] <ShalokShalom> he already do that
[19:58] <ShalokShalom> and want to change the wallpaper in this theme
[19:58] <lordievader> ShalokShalom: Does he use Kubuntu? If so, why does he use KDM?
[19:58] <BluesKaj> there is no theme just a wallpaper image
[19:58] <ShalokShalom> he use 14.04 and use kdm, because he want to use this theme
[19:58] <ShalokShalom> ok
[19:58] <ShalokShalom> no positions ?
[19:58] <ShalokShalom> no icons ?
[19:59] <BluesKaj> not for the login page
[20:00] <BluesKaj> unledd he finds an image at kde-look that contains them
[20:00] <BluesKaj> unless
[21:08] <nell> so kubuntu come with kde5?
[21:09] <lordievader> nell: Not yet, but you can add a ppa.
[21:09] <nell> oh
[21:09] <nell> october is release
[21:09] <nell> I like KDE + ubuntu for my AV media workstation
[21:09] <nell> I'm doing stuff with VR and its nice to work in
[21:10] <nell> if I wanna get ubuntu studio packages
[21:10] <nell> should i get ubuntu studio w/ kde or kubuntu w/ ubuntu studio sources
[21:13] <lordievader> nell: By the by, Plasma5 is not really what I call usable yet. Best to stick with Plasma4 for production machines.
[21:15] <nell> Thanks, I think im satisfied with that
[21:15] <nell> peace
[22:06] <laaaa> hello


[10:53] <teddy-dbear> Morning peoples, critters and everything else
[12:00] <erstazi> morning teddy-dbear
[13:16] <icey> ahoy


[21:31] <k1l_> [^FuL|an0^]<EMAIL_ADDRESS>  antisemitic guy again
[21:31] <k1l_> "This is why we need to keep the jews out."
[21:33] <dax> depressingly enough, that doesn't look like the usual antisemitic spammer either
[21:34] <dax> (they got k-lined regardless)


 Hello everyone, I hope you are enjoying the release of the new version of Ubuntu. I know this is only a testing channel, but I would like to let you know that the Ubuntu Weekly Newsletter is now also on Telegram and has a channel to keep every Ubuntu member and the community informed about everything that happens and what everyone is doing to make Ubuntu better for everyone.
 The link to the UWN channel is this:
 t.me/ubuntunewsletter
 We'll be building an RPi version of it soon :) (re @Zachariah: Does this include the Raspberry Pi version? I'm itching to put this on my 400!)
 Cool
 It turned out for me for UCR our arm64 seed mentions packages that doesn’t exist for arm64
 Oops 😬 (re @ItzSwirlz: It turned out for me for UCR our arm64 seed mentions packages that doesn’t exist for arm64)


[07:32] <njin> bug 1010782
[07:32] <ubot2> Launchpad bug 1010782 in ubuntu "service(8) output inconsistent to stdout/stderr" [Undecided,New] https://launchpad.net/bugs/1010782
[07:32] <njin> can someone help assigning package ?
[08:36] <jibel> njin, dpkg -S usr/sbin/service
[08:36] <jibel> sysvinit-utils: /usr/sbin/service
[08:36] <jibel> njin, source package is sysvinit
[08:50] <njin> jibel, thanks
[09:14] <luc4_mac> Hi! I've been asked to perform kernel bisection for bug 997767, but it seems that kernel 2.6.38 is affected by the bug, which I don't think is possible since I've never had any issues until 12.04. Does it make sense to test older kernels?
[09:14] <ubot2> Launchpad bug 997767 in linux "10ec:8139 Network connection rtl8139 lost after some hours of inactivity and comes up again on user interaction" [Medium,Incomplete] https://launchpad.net/bugs/997767
[12:17] <Abhijit> hi
[12:17] <Abhijit> Someone please triage this bug https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1010866
[12:17] <ubot2> Launchpad bug 1010866 in gnome-screensaver "No Keyboard Layout option in lock screen" [Undecided,New]
[12:24] <luc4_mac> Hi! I've been asked to perform kernel bisection for bug 997767, but it seems that kernel 2.6.38 is affected by the bug, which I don't think is possible since I've never had any issues until 12.04. Does it make sense to test older kernels?
[12:24] <ubot2> Launchpad bug 997767 in linux "10ec:8139 Network connection rtl8139 lost after some hours of inactivity and comes up again on user interaction" [Medium,Incomplete] https://launchpad.net/bugs/997767
[13:05] <penguin42> luc4_mac: It's possible that older kernels are affected by something that's newer in userland but didn't cause a problem with previous user lands, however if it still affects 2.6.38 I'm not sure it makes sense going any further back
[13:06] <luc4_mac> penguin42: I understand… so I can do nothing else but wait for an answer in the bugreport right?
[13:07] <luc4_mac> penguin42: and thanks for your help also :-)
[13:07] <penguin42> luc4_mac: It's very difficult to help when stuff only happens on a few peoples machines; it's difficult to track down
[13:08] <penguin42> luc4_mac: The only thing I can think to do is to see if you can find something that if run during that time keeps the network up; I mean if you leave a ping running in the background does the network stay up? If you script something to take the network down and bring it back up every 5 minutes does that stop it failing altogether?
[13:08] <luc4_mac> penguin42: I understand this. That is why I wanted to help. By the way, recovery mode is not solving the issue, only reducing.
[13:09] <penguin42> hmm interesting
[13:09] <luc4_mac> penguin42: I just discovered this :-) I tried 4 times to clone the kernel git, I'm unable to finish because network shuts down :-)
[13:10] <penguin42> luc4_mac: Even if you stay logged in?
[13:10] <luc4_mac> penguin42: yes, via ssh and locally.
[13:10] <penguin42> luc4_mac: So that's a bit different from you're original report
[13:11] <luc4_mac> penguin42: what is different? Only the information about recovery mode. But I just found that out.
[13:11] <penguin42> luc4_mac: No, because you originally said it lost connection when it was idle/you were away from it
[13:12] <luc4_mac> penguin42: yes, that remains. I'm logged in, but I'm not pressing any button on the local keyboard.
[13:12] <penguin42> luc4_mac: Right, so I mean can you manage that git clone if you stay at the keyboard ?
[13:13] <luc4_mac> penguin42: I suppose yes, but I should test that better. When network shuts down anyway it is sufficient to press any button to wake net up.
[13:13] <luc4_mac> penguin42: or plugging any mouse in.
[13:14] <luc4_mac> penguin42: also, I noticed keeping a mouse plugged in reduces the frequency of faults. But that doesn't solve completely.
[13:16] <luc4_mac> penguin42: I'll try again with the live CD, I supposed it worked, but I'll test again cause that might have only reduced the faults as well.
[13:18] <penguin42> luc4_mac: It really sounds like some power saving thing
[13:19] <luc4_mac> penguin42: yes, but consider that pressing any button on the keyboard makes the network wake up immediately. Maybe less than a second. Quite fast...
[13:20] <luc4_mac> penguin42: pressing the button or pluggin the mouse in results in some noise like access to hard disk, and network is up. Really strange...
[13:21] <penguin42> luc4_mac: Very odd; you could try something like a (as root) lspci -vvv   in a repeating loop and see whether the output changes while it's network failed or not
[13:21] <luc4_mac> penguin42: ok, I can do that. Do you also know if recovery mode starts some services?
[13:22] <penguin42> not sure
[13:22] <luc4_mac> penguin42: strangely I see proftpd up...
[17:53] <dlentz> could someone mark bug 1001609 as Triaged/Medium? (No changelogs is a usability issue, but does not limit functionality of core packages)
[17:54] <ubot2> Launchpad bug 1001609 in ubuntu "Changelogs not being uploaded to changelog server" [Undecided,Confirmed] https://launchpad.net/bugs/1001609
[17:54] <dlentz> and if anyone has ideas of where or what group/package  to assign it to so that it gets more attention, that would be helpful
[17:55] <dlentz> thanks
[17:58] <penguin42> dlentz: I won't mark something as triaged without it being in the right or reasonable package
[17:58] <dlentz> penguin42, i see, any suggestions?
[17:58] <penguin42> hmm I was going to suggest launchpad but I see it's already been passed back from that. hmm
[18:03] <dlentz> penguin42, i changed it to changelog extract tool, it is the closest match i could find and mentions the server changelogs.ubuntu.com
[18:06] <penguin42> dlentz: I'm not sure that's a good idea either - the launchpad content for that is almost empty
[18:06] <penguin42> the bugs page says it's not configured to forward bugs to their devs
[18:07] <dlentz> yeah, i just saw that :\
[18:08] <penguin42> dlentz: And it won't let me change the importance in that because I'm only in ubuntu-bugcontrol - and that's not actually tied to ubuntu
[18:09] <dlentz> ok, i switched it back. i'll keep hunting to see who's responsible for http://changelogs.ubuntu.com/
[18:09] <penguin42> dlentz: You could ask in #ubuntu-packaging
[18:09] <dlentz> ok, i'll query there, thanks
[21:17] <dudeman1996> caann I get some help?
[21:26] <hggdh> dudeman1996: just ask your question. If someone can help, they will
[21:26] <dudeman1996> basically, I upgraded from 11.10 to 12.04 today, and suspending doesn't work. I hit suspend, the screen goes black for about 20 seconds and then it takes me back to the lockscreen
[21:37] <lifeless> dudeman1996: https://wiki.ubuntu.com/DebuggingKernelSuspend is probably what you need to read
[21:37] <lifeless> dudeman1996: there are  anumber of links from there, and it may require significant reading to get a grip on it; I'm sure thats now what you wanted to hear - sorry!
[21:58] <dudeman1996> lifeless: thanks for that link, but that's about resuming from suspend. I'm having problems with suspending, so I'm guessing something is wrong with the ACPI subsystem. The link "Detailed analysis of ACPI kernel code for debugging a suspend problem" is blocked for me, even after registering on the forums