[00:03] dobey: still downloading the tar.gz [00:03] :S [00:04] oh [00:32] RoAkSoAx: i need to get dinner, but let me know if you find anything; thanks [00:33] dobey: will sure do... though, is the dsc in launchpad somewhere as this seems will take for ever [00:36] RoAkSoAx: no; i am trying to set up daily builds of rhythmbox to test with for precise development, while trying to preserve the ubuntu patches to it; the error happens when building the source package in the recipe builder, but doesn't happen locally. so i'm not even sure a dsc will help really [00:36] RoAkSoAx: you can bzr branch lp:rhythmbox, then inside the rhythmbox dir "bzr branch lp:~ubuntuone-control-tower/rhythmbox/packaging-dailies debian" and debuild -S to get one [00:37] the only difference between that and the dsc i built, is the version number in debian/changelog. [00:42] maybe it's a launchpad issue, but it doesn't immediately strike me as one. [00:42] anyway, need to get some food [00:53] dobey: cool, will take a look as soon as I get back [00:55] bdmurray: kerneloops is up for adoption in Debian if you have an interest in it [00:56] or anyone else so inclined :) [01:00] dobey: You're aware that you can do the recipie build locally, right? Install bzr-builder and you get a ‘bzr dailydeb $RECIPIE’ command, which does the same thing as launchpad does. [01:17] @pilot out === udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/or6CHJ | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: [01:17] ...for lunch. [01:17] :) === Ursinha-lunch is now known as Ursinha [02:05] are there any d-i tricks to redirect syslog to serial console? [02:11] RoAkSoAx: oh, hrmm; i see something else in the log now, that might be why; it appears that maybe quilt is crashing when applying the patch for some reason? [02:11] and so when it tries to un-apply, it fails because it's not actually applied [02:12] Now at patch 05_hide_on_quit.patch [02:12] (2.2881429999999998, 0.56403499999999995, 0, 0, 0, 0, 62025, 30, 0, 8280, 68960, 0, 0, 0, 5806, 174) [02:12] i don't know what all those numbers mean, but surely not good [02:17] slangasek: http://lintian.ubuntuwire.org/tags/data.tar.xz-member-without-dpkg-pre-depends.html [02:17] "This tag has not been emitted in any package tested by Lintian" [02:25] adam_g: what seems to be the problem [02:25] dobey: just got back gonna look at it now [02:25] broder: hmm, that's the one we have an archive accept-time check for; did we get signals crossed somewhere? The one we're missing info on is use of dpkg-maintscript-helper in preinst without pre-depends [02:26] ok, i see [02:27] yeah, lintian isn't checking for that currently [02:29] that'll take writing a new check. i'll look into it [02:31] RoAkSoAx: i refreshed some more of the patches again, and am trying another build now. [02:31] broder: cool, thanks :) [02:34] dobey: ok, i;m building here too [02:34] RoAkSoAx: ok, thanks [02:38] dobey: its building just fine in a PPA for oneiric [02:38] s/PPA/pbuilder [02:39] dobey: didn't even refreshed the patches [02:42] RoAkSoAx: right; the problem isn't that. the problem is that building the source package is failing, and refreshing the patches didn't seem to help me either :( [02:43] dobey: in my case the source package builds on my pbuilder [02:43] dobey: i didn't have to refresh the patches [02:43] for it to build [02:45] RoAkSoAx: yes, here too. i don't mean build in that sense though. i mean dpkg -S is what's failing in the recipe builder on the server [02:47] dobey: I'll upload to my PPA [02:48] i guess those numbers are meaningless, and are actually coming from bzr-builder plug-in [02:49] but why oh why is quilt applying-but-not-applying the patch :( [03:07] dobey: ok, so in my cause, it seems to be building https://launchpad.net/~andreserl/+archive/ppa/+build/2976892 [03:08] dobey: though, since I did everything manually, that might be it. Maybe there's something wrong in your recipe for the daily builds [03:09] dobey:there are the steps I followed: http://pastebin.ubuntu.com/756702/ [03:09] no, it's not the recipe. it's quilt [03:10] yes, debuild -S -sa works fine here [03:10] s/cause/case [03:15] anyways, I gotta go sorry I could not be of further sassitance [03:15] maybe tomorrow that I'm fresh I could help more [03:15] cheers [03:15] thanks anyway [03:15] cheers === bladernr_ is now known as bladernr_afk [04:11] if debian/rules has override_dh_install with a line 'dh_install -pXYZ', and debian/control lists XYZ as only for i386. Will that line be ignored on an arm build? [04:12] apw: linux fails the same way, BTW. kernel-wedge dies. [04:12] SpamapS: Around? [04:12] SpamapS: It looks like language-pack-kde-en got copied to oneiric-updates, but language-pack-kde-en-base didn't, so language-pack-kde-en is now uninstallable. [04:13] I don't know if any other languages are affected. [04:13] (or any other ubuntu-sru person) [04:14] OK, we'll do it this way ... [04:14] !regression-alert [04:14] cjwatson, jdong, pitti, skaet, ScottK, kees, Daviey, pgraner: reporting regression in a stable release update; investigate severity, start an incident report, perhaps have the package blacklisted from the archive [04:15] Regression is above the alert .... [04:15] Nothing needs to be blacklisted, just need to copy over language-pack-kde-en-base to oneiric-updates. [04:17] It would also be good if someone could check if other languages are affected (I'm on an airplane that's 20 minutes from landing, so I'll have to shut down shortly) [04:21] StevenK: ^ do you have the perms ? [04:23] slangasek: around? can you fix the langpack issue above? [04:23] I can look. pitti probably can too. [04:31] ScottK, lifeless: Copied. [04:50] Good morning [04:51] lool: ah, probably just copy&paste error from a previous merge [04:54] ScottK, StevenK: uh, we didn't mean to do a -base refresh; I'll check the other ones, thanks for pointing out [04:54] aah, this was still from the previous round [04:55] pitti: So I've copied the wrong thing, or it's okay? [04:55] StevenK: no, it's fine [04:55] StevenK: it just explains why -base was needed [04:55] in the previous update round we did do a -base refresh, but not in this one [05:19] Daviey: thanks for moving over the milestone bugs [05:31] jamespage, wendar: FYI, fixed current software-center/ubuntu-desktop uninstallability and CD build failure, needed a binNEW [05:32] jamespage, wendar: now looking at edubuntu uninstallability due to nautilus-python [05:33] pitti: I had one merge proposal and one archive admin task from my work today (dropped you an email) [05:35] wendar: saw it, thank you! will get to it [05:35] but I'll work on the uninstallability first, as this is our first "red alert" priority [05:36] pitti: very much so [05:36] wendar: how did your first day go? [05:36] on our TODO list for tools improvements: http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html [05:36] "pretty please say WHY the package isn't installable" [05:37] pitti: good, it was great to focus [05:37] wendar: yeah, I find that as well; there's so many things I always wanted to get around to, like component-mismatches etc. [05:37] hah, yes that would be useful :) [05:37] and now there's theh time [05:38] the more information the better [05:38] gr_vmcircbuf_createfilemapping: createfilemapping is not available [05:38] hmm [05:39] wendar: our buildds run the lucid kernel, so maybe it's relying on some kernel features that only newer versions provide [05:39] wendar: other differences are: no network, building with DEB_BUILD_OPTIONS=parallel=4 [05:39] wendar: you could try tossing the package in a PPA and see whether it makes a difference [05:40] wendar: as a next step I'd try to upload a no-change rebuild to see whether the failure reproduces [05:41] wendar: we have two FTBFS in main on armel, do you want to look into these, too? [05:42] pitti: ruby and telepathy? sure I can break out the pandaboard tomorrow [05:42] wendar: we have porter boxes [05:42] pitti: I can try those too [05:42] wendar: but yeah, it might be an opportunity to set them up and get them running; yay for new toys :) [05:43] pitti: actually, I'll try logging in now, in case I need UK support before my day tomorrow [05:44] infinity: oh, look! http://ddebs.ubuntu.com/dists/precise/main/binary-armhf/Packages [05:44] wendar: did you join the +1 team? [05:44] pitti: Oooo. [05:44] * +1 maintenance [05:44] infinity: now, if we actually had a retracer running on arm :) [05:45] pitti: They're still valuable for local debugging. [05:45] pitti: I get "Permission denied (publickey)." so I must not be set up for the porter boxes [05:45] infinity: it's actually rather easy to set it up, just waiting for that RT ticket to give me a real psql db for duplicates [05:45] pitti: (Which was our original use-case before the magical retracer happened) [05:45] micahg: yah, I'm a December +1-er [05:45] infinity: right, if you install apport-retrace, the crash notifications will grow an "examine locally" button [05:46] which will give you a fancy stack trace or toss you into a gdb session with full symbols [05:46] wendar: ah, that sounds worth an RT; you can CC: me so that I can send my +1 (also for powerpc) [05:46] wendar: awesome, is there a list somewhere of the current members? [05:46] micahg: jamespage, wendar, me [05:47] micahg: https://wiki.ubuntu.com/PlusOneMaintenanceTeam [05:47] has the roster [05:48] pitti: cool, thanks for the info, is that channel worth idling in? [05:49] micahg: TBH, I'm not planning to use it much; I can't follow another channel, so rely on getting pinged there; and most issues should be fine to discuss here or in /msg [05:50] but let's see how much it actually gets used [05:59] pitti: I'm kinda hoping the channel can die. [05:59] pitti: Given that -devel is +1-centric, almost by definition, I hate having conversations about problems/solutions split over channels. [06:00] pitti: (And I really hate duplicating work because I didn't see the conversation about someone else working on it) [06:00] infinity: that's my feeling [06:00] * infinity realises the irony of the above statement, where most of his armhf conversations have been happening in linaro-armhf and debian-arm, but... [06:00] wendar, jamespage: opinions? ^ shall we try using #u-devel until people complain? [06:01] pitti: works for me [06:18] StevenK: Thanks. All better now. [06:46] wendar: hm, just followed up to your RT. Your user account exists, and you are in porting_team [06:46] wendar: so maybe ssh after all? not sure [06:47] wendar: but I guess IS will figure it out [06:48] pitti: yup, not sure. It could be that they don't have all the right ssh keys propagated over === TeTeT_ is now known as TeTeT === tkamppeter_ is now known as tkamppeter [07:36] pitti, hi [07:36] infinity: out of curiosity are there any new tricks for armhf porting vs armel porting for FTBFS fixes? [07:37] micahg: Not really. There's the general "watch out for upstream thinking they know better than us about default compiler flags", but that's true for every arch. [07:38] micahg: Mostly, it's business as usual. [07:38] sounds good [07:40] micahg: Care to figure out why libicudata appears to not be a valid shared object on armhf? :P [07:41] infinity: nah, I've got my own build failures to figure out over the weekend :) [07:41] I got 2 so far [07:46] Hrm. icu is build with -O0 on armel for entirely unrelated reasons. I wonder if that also makes the library not broken. :P [07:46] * infinity settles in for some testing. [08:07] good morning === jibel_ is now known as jibel [08:31] jibel: we got a bunch of server failures this morning, like https://jenkins.qa.ubuntu.com/view/Precise/job/precise-server-amd64_dns-server/lastBuild/ [08:31] jibel: the previous ones were marked as "pass", but I can't see an obvious difference in the log files [08:32] jibel: for example, the four DNS resolution tests at https://jenkins.qa.ubuntu.com/view/Precise/job/precise-server-amd64_dns-server/lastSuccessfulBuild/artifact/2/test-results/dns-server.stderr already failed before [08:35] jibel: oh, perhaps they have just been yellow yesterday? [08:35] so far I interpreted yellow as "last build succeeded, but some previous ones didn't" [08:36] oh, https://jenkins.qa.ubuntu.com/view/Precise/job/precise-server-amd64_lvm/lastBuild/console says "No test report files were found. Configuration error? [08:36] is that the reason for the failure? [08:37] pitti, yellow is 'tests partly failed' [08:37] pitti, no the reason is that the installation didn't finish [08:37] some package failed to install and the installation hanged at some point. I'm on it [08:38] jibel: ah, red == installation failed, yellow == install succeeded, but post-install tests failed? [08:38] jibel: where do you see that a package failed to install? [08:38] pitti, right [08:38] pitti, from syslog, the installation didn't reach the end [08:38] I really hate to ping you about all these, I'd like to learn where to get that info from myself [08:39] pitti, we are working on this doc https://wiki.ubuntu.com/QATeam/AutomatedTesting/UnderstandingJenkins [08:39] Nov 29 08:06:39 grub-installer: Installation finished. No error reported. [08:40] and then a bunch of more debconf === gema_afk is now known as gema [08:43] pitti, I'll rerun a server job, there's nothing obvious in the log it just stops at "Dec 2 07:00:58 debootstrap: Setting up libc6 (2.13-20ubuntu8) ..." [08:45] jibel: which syslog are you looking at in particular? [08:45] pitti, https://jenkins.qa.ubuntu.com/view/Precise/job/precise-server-amd64_default/lastFailedBuild/ [08:46] jibel: ah, I was looking at the lvm/dns ones [08:46] attachment d-i-syslog.log [08:47] jibel: ah, thanks [08:47] pitti, same error for all, you were looking at the log from Nov 29 [08:48] ok [08:48] pitti, jenkins' UI is confusing because when you click on a job it shows the artefacts of the last successful build, not the last build [08:48] jibel: another question (sorry), there are no desktop/alternate tests for today's dailies in the "planned builds" queue [08:49] jibel: right, I guess that tricked me a couple of times [08:50] pitti, they are running, I'll see with patrickmw how we can keep the list of running jobs between the private and public instance of jenkins in sync. [08:50] jibel: ah, good to know, thanks! === jodh is now known as jodh_ [08:51] rickspencer3: ^ FYI [08:56] infinity: what went wrong with qt4-x11? [09:00] pitti, the VMs don't reboot after install, that sounds bad. [09:05] jibel: that's the desktop ones? [09:06] pitti, nope, server. desktop are still queued [09:06] ah, ok [09:13] doko: I killed it to move it to a Panda. 11 hour build time versus a day and a half. [09:18] pitti, jamespage that's interesting, the VM reboots in the middle of the installation. That's why the logs are truncated and hard to understand. [09:19] jibel: that was my guess [09:19] doko: Did you give-back pyicu? [09:19] doko: It's just going to fail again. As will several other icu-related failures. Trying to figure out why everything hates libicudata.so.48 so much. [09:20] jibel: urgh; invalidly triggered reboot by our test code, or happening "by itself"? [09:20] pitti, by itself [09:20] just after setting up libc6 [09:21] I'll mount the image and try to find more information. [09:21] kern.log might have some bits [09:21] hopefully [09:28] doko: Also, is that lsb-release change the beginning of a python3 transition? [09:32] pitti, jibel am I surmising correctly that the problems seem to be with the test rig, and not the ISOs themselves, or have you not determined that yet? [09:32] infinity, pyicu, yes. lsb-release: as in oneiric, to get it on the CD first [09:33] rickspencer3, the problem seems to be with the ISO. [09:33] doko: Yeah, ICU is being misbuilt somehow. Nothing can link/load the libraries. [09:34] doko: I'm going to look more in the morning. [09:34] aha [09:34] ah, that explains why today's images are still oversized [09:34] so, "daily quality" kick in :) [09:34] thanks jibe [09:34] libicu44 was removed (-7.1 MB), but python3.2 was added (+5.9 MB) [09:34] thanks jibel [09:39] cjwatson: what generates http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html ? [09:40] jamespage, nothing in the log. on the console is displays 'setting up debconf' and reboots [09:41] pitti: britney. [09:47] infinity: ah, thanks; I was getting confused because bin/run-britney just outputs to www/precise_outdate_all.txt [09:48] I now see the testing/www output dir [09:49] lots of uncommitted changes in testing/ bzr, hmm [09:49] cjwatson: is that something we can hack on, or do we need to keep it in sync with Debian somehow? [09:50] cjwatson: I'd love to integrate (1) links to pending builds (which explain most of the current problems) and (2) the reason _why_ the package is uninstallable [09:50] cjwatson: We're not even remotely in sync with Debian. Our britney is an 8-year-old fork. [09:50] Err. [09:50] ah, ok [09:50] s/cjwatson/pitti/ [09:50] so that at least resolves that question [09:51] cjwatson: Disregard my poor tab-completion. :P [09:51] I refuse getting cjwatson replaced with me [09:51] we so much need him! [09:53] jibel: I just re-produced as well - rebooted during install of base system [09:54] jamespage: that's with today's server ISO? [09:54] pitti: yep - thats the symptom see in the automated testing as well [09:54] jamespage, ack. I'm filing a bug [09:54] jamespage: I'm now downloading the desktop alternate to see whether it happens there as well [09:55] seems jenkins didn't get to alternate/desktop testing yet [09:56] jibel, pitti; I'm going to manually terminate the precise-server tests currently running - they are just spinning and holding up the desktop and alternate tests. [09:57] jamespage, bug 899049, could you please confirm it ? [09:57] Launchpad bug 899049 in debian-installer (Ubuntu Precise) "Ubuntu Server reboots during installation" [Critical,New] https://launchpad.net/bugs/899049 [09:58] jibel: confirmed [09:59] @pilot in === udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/or6CHJ | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: jamespage [09:59] jamespage, pitti there is this error during install [09:59] Dec 2 07:00:46 base-installer: chroot: can't execute 'debconf-set-selections': No such file or directory [09:59] Dec 2 07:00:46 base-installer: warning: /usr/lib/base-installer.d/20console-setup returned error code 127 [10:00] infinity, so just linux-libc-dev is missing for the buildd variant? [10:00] jibel: it looks like a requested reboot; normal Sending SIGTERM message stuff [10:02] jamespage, could it be that it doesn't set the debconf values and after the base install it reboots because there's nothing left to do ? [10:02] doko: Should be just that. I think. [10:03] pitti: it's in ~ubuntu-archive/testing/ on lillypilly [10:03] pitti: also ~ubuntu-archive/testing-ports/ (sorry, code kept in sync rather than common) [10:03] pitti: there might be a few outstanding uncommitted changes, mainly from the cocoplum->lillypilly move [10:04] jibel: those server jobs have now cleared through [10:04] pitti: if you can figure out how to add that kind of information to its output, be my guest :-) [10:04] pitti: the alternate automated test is currently running [10:04] cjwatson: ok, so ok for hacking on it [10:04] pitti: how about I go through and sort out uncommitted stuff first [10:05] cjwatson: there's also changes to update_out/dpkg.c, the rest of bzr diff is just config diff; it doesn't get in my way, I'd like to touch different files [10:05] cjwatson: thanks! [10:06] jibel, pitti: think alternate is doing the same [10:07] 6 minutes to go for downloading [10:07] jamespage: do you want to look into this? I'm also looking at bug 897680, so maybe better if we don't overlap there [10:07] Launchpad bug 897680 in ubiquity (Ubuntu Precise) "Precise Desktop 64Bit: libc6 fails to install if "install 3rd party software" is selected" [High,In progress] https://launchpad.net/bugs/897680 [10:07] jamespage, yes, you can cancel the jobs [10:07] pitti: sure [10:08] jibel,jamespage: so this is reproducible outside jenkins? [10:09] cjwatson: yes [10:09] jamespage: OK, I'll look at it then [10:09] cjwatson: thanks [10:09] . o O { yay for daily automatic tests! } [10:15] cjwatson, jibel; I'm struggling to see an specific step causing this looking at the d-i logs in jenkins [10:15] jamespage: I have a guess based on prior experience but I'd rather see it for myself first [10:19] pitti: all merged up now [10:21] cjwatson: thanks! [10:31] * cjwatson videos the installer to try to track this down [10:33] jibel, pitti, cjwatson: all of the alternate installs failed with the same issue [10:36] jamespage: yeah, they would have done [10:36] there's no room for anything flavour-specific here [10:58] jibel,jamespage: fix uploaded [10:59] I would suggest a rebuild of all d-i images after libselinux has built everywhere [10:59] thanks cjwatson [11:00] I need to catch a train this afternoon, but I should have enough bandwidth to trigger new builds; unless someone else can do that [11:00] I probably can [11:00] I'll be online at 1300 UTC (in 2 hours), I'll check IRC/nusakan then [11:01] cjwatson: ah, upstart is now working too well in a chroot? [11:04] pitti: not a new class of problem; see my reference to the eglibc change, which was in natty [11:05] sysvinit telinit u sends SIGHUP to pid 1, upstart telinit u sends SIGTERM to pid 1 [11:05] the latter causes busybox init to reboot [11:05] it's a semantic difference we need to account for [11:06] I knew I'd seen this kind of thing before :) === _salem is now known as salem_ [11:09] dholbach: sorry, missed my patch pilot shift today; I'll do that on Monday instead [11:09] pitti, no worries [11:10] whatever suits you better - you should also be able to just move the events in the google cal [11:10] * dholbach hugs pitti [11:12] dholbach: nevermind, I just can't read my mobile; it already _is_ on Monday :) [11:12] haha [11:12] great [11:46] diwic, hello. I just upgraded to 12.04 - so far so good, the only problem I get is http://paste.ubuntu.com/756958/ - did you see anything similar somewhere else already? [11:46] dholbach, your production machine ? [11:46] ogra_, yep [11:46] wow, brave [11:50] dholbach, hmm, not recognising [11:50] dholbach, does it happen every time you plug it in? [11:50] diwic, it looks like it - I tried twice, but I can try again if you like [11:51] diwic, yes, just tried again [11:51] dholbach, my gut feeling is that this is a generic USB problem rather than a sound card problem, does it happen to other usb devices as well? === funkyHat2 is now known as funkyHat [11:52] dholbach, given that the first sign of trouble is "usb 1-1.2: string descriptor 0 malformed (err = -61), defaulting to 0x0409" from the USB driver rather than the sound card driver [11:52] diwic, usb-storage seems to work [11:52] ok [11:53] let me see how it works with the scanner [11:54] diwic, uvcvideo: Failed to submit URB 0 (-28). - that's for the webcam, but it's not USB - just thought I'd test it as well [11:55] "URB 0" sounds very much like USB [11:55] webcams are often connected with USB internally [11:55] ah ok [11:56] * ogra_ always thought uvd even means Usb Video Connector [11:56] *uvc [11:57] diwic, the scanner seems to be happy AFAICS [11:59] dholbach, so, my gut feeling says "USB driver failure" rather than "sound driver failure", so see if you can find an USB expert, if (s)he tells you that it's a sound driver problem, I guess I'll have to take a deeper look. Makes sense? :-) === dendro-afk is now known as dendrobates [11:59] diwic, I think I can try the oneiric kernel to see if that makes it work again and then file a bug on linux? [12:00] ok [12:00] cool [12:00] you can also try oneiric kernel + alsa dkms packages to further try to rule out (or in) ALSA === MacSlow is now known as MacSlow|lunch [12:04] dholbach, you can also try oneiric kernel + alsa dkms packages to further try to rule out (or in) ALSA [12:05] or rather [12:05] alsa backports [12:05] dkms is for snd-hda-intel only [12:05] diwic, just going back to the oneiric kernel worked: http://paste.ubuntu.com/756964/ [12:05] hmm ok [12:06] Once upon a time, there would be a popup when my mouse was running out of battery. /me misses that thing [12:07] #define ENOSPC 28 /* No space left on device */ [12:10] diwic, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899099 [12:10] Launchpad bug 899099 in linux (Ubuntu) "snd-usb-caiaq fails to load" [Undecided,New] [12:12] diwic, who could be close to being the "USB expert" you mentioned? :) [12:14] dholbach, guess why I wrote "USB expert" instead of a specific name? :-) [12:14] at least I've found the line where your error message comes from [12:17] diwic, I know this is going to sound vague - mostly because I have little idea of the internals, but if the string descriptor is malformed, is the device still being brought up? (can anything be read at all?) [12:19] dholbach, I think you should try to talk to Daniel Mack, (zonque on freenode) he wrote that caiaq driver and seems to know quite a bit about USB audio drivers [12:20] ok, will do [12:21] cjwatson: do you plan to sync reiser4progs (you're TIL for it) for precise? see also bug #889991 [12:21] Launchpad bug 889991 in reiser4progs (Ubuntu) "reiser4progs (main) should be synced from Debian testing (main)" [Undecided,New] https://launchpad.net/bugs/889991 [12:22] * Daviey wonders why NEW sync's from Debian require AA approval. [12:22] do they? that's new to me [12:23] geser: source NEW. [12:24] I know that AA have to accept them, but not that AA need to approve before it can be synced (uploaded) [12:24] Daviey, license review etc [12:24] tumbleweed, thank you! [12:24] geser: yes, although it requires a fakesync [12:25] ogra_: right, but if it got into Debian, the licence is probably good :) [12:25] Daviey: because in some cases we blacklist classes of packages from Ubuntu (e.g. all xul extensions) [12:25] or freebsd packages, or ... [12:25] zyga_: ping [12:25] although that's a post-hoc justification; the real reason is that the condition on NEW is simply "haven't seen this before" [12:25] cjwatson: Ah, makes sense [12:25] int_ua, pong [12:26] how can I help you [12:26] talking of AA syncs, can we have the sync request bugs processed, please [12:26] zyga_: I'm from https://bugs.launchpad.net/command-not-found/+bug/880616 :) [12:26] Launchpad bug 880616 in command-not-found "Add an option to install the package right away ( + draft patch )" [Undecided,Confirmed] [12:26] quadrispro: np [12:27] int_ua, hi, welcome :) [12:27] int_ua, so how can I help you with c-n-f work? :-) [12:27] zyga_: I did't have experience with merges yet, so I wanted to ask you some questions. I need to create a new branch, yes? [12:28] int_ua, ok, I'll walk you through this [12:28] int_ua, I assume you branched lp:command-not-found, did your patch there [12:28] int_ua, did you commit your change yet? [12:29] zyga_: yes, commited [12:29] zyga_: locally [12:29] int_ua, excellent, since you have a launchpad account that part is also done, do you have any ssh keys registered on launchpad? You will need that to put your branch up in the system [12:29] zyga_: (I'd like to do some additional work, but it's tested now) [12:30] zyga_: yes, I have two 8-) [12:30] excellent [12:30] then just do something like that [12:30] bzr push lp:~yourlaunchpadusername/command-not-found/add-install-support [12:31] where the last part is anything you like obviously, it does not matter that much for a short lived branch [12:31] Don't i need to create a new branch in the web interface? [12:32] int_ua, nope [12:32] ok, doing it :) [12:34] zyga_: Done. https://code.launchpad.net/~xintx-ua/command-not-found/add-install-support [12:35] but I want to add root installation too before submitting [12:35] int_ua, ok, from the same directory do this: bzr lp-propose-merge [12:35] int_ua, that's okay, you can commit more changes [12:35] int_ua, and just push them again [12:35] int_ua, the branch and the merge request will automatically update [12:37] zyga_: Ok, what should I write to the log file that has just opened? What is it for? [12:38] int_ua, it's the description of the merge request, you don't need to write anything but I usually write a short description of what the branch is about, if the branch is very small (few patches) I just ask people to look at the patches instead [12:38] <`-`> #ubuntu ops are nazi fags. please remember to use your brain not that other bit of the anatomy the #ubuntu team appears to think is best. [12:39] zyga_: and should I change bug status to "In Progress" if I'm working on it? [12:39] int_ua, if you want, go for it :-) [12:39] int_ua, much of the tools are defined by how we use them, if you like a particular way of working just work like that [12:40] ok, looks like submitted from here :) https://code.launchpad.net/~xintx-ua/command-not-found/add-install-support/+merge/84257 [12:41] int_ua, the good thing about this is that anyone can easily see the diff as both your branch and trunk change and anyone can easily take your branch without having to fiddle with the patch [12:41] zyga_: great :) [12:41] diwic, ignore my question about the malformed string descriptor - I got the same message with oneiric and it didn't matter :) [12:42] zyga_: And now I have to link this branch to bug, am I? [12:42] int_ua, there's a button for that in the sidebar [12:42] (of the bug actually [12:42] zyga_: yeah, got it [12:43] But "Loading suggestions..." is all that it does [12:43] int_ua, you need to give the name of your branch [12:43] just paste lp:~xintx-ua/command-not-found/add-install-support [12:44] done [12:44] I added some comments there [12:44] ~xintx-ua/command-not-found/add-install-support worked too :) [12:44] int_ua, you are using some cyrlic-based locale, correct? [12:45] yes, uk_UA [12:45] int_ua, I've seen a ton of bugs about c-n-f crashing on various non-ansi characters. I'm pretty sure that is not happening when you are using .UTF-8 encoding (LC_MESSAGES and LC_CTYPE end in .UTF-8) [12:45] int_ua, have you seen any of those crashes yourself? [12:46] no, but mine is .UTF-8 [12:46] right [12:46] also, the regexp doesn't work as expected in uk [12:46] I suspect that's CJK [12:46]