[14:58] <paulduf> heno, I believe that we won't fix upgrade issues in Edgy now, but I believe it is not uncommon for old bugs to still apply to current version, except maybe packaging bugs that make the update stop, but then again, it is unclear what is the correct thing to do in this case (I have no authority at all, just a normal bug squasher)
[15:06] <ubotu> New bug: #162656 in gnome-volume-manager (main) "microphone auto unmutes after serveral minutes" [Undecided,New] https://launchpad.net/bugs/162656
[15:06] <ubotu> New bug: #162657 in xaos (main) "XaoS -fullscreen doesn't work" [Undecided,New] https://launchpad.net/bugs/162657
[15:09] <mvo_> paulduf: it is overwriten
[15:10] <mvo_> heno_: its sort-of-useful, I want to have a good understanding what went wrong in between dapper-hardy so that the upgrader tries to get those cases right
[15:10] <mvo_> heno_: but if the report has no logs, its useless
[15:10] <ubotu> New bug: #162661 in ubuntu "/var/lib/defoma/fontconfig.d/J: failed to write cache" [Undecided,New] https://launchpad.net/bugs/162661
[15:11] <heno_> mvo_: ok, thanks
[15:11] <ubotu> New bug: #162658 in ubuntu "svn unknown error" [Undecided,New] https://launchpad.net/bugs/162658
[15:11] <ubotu> New bug: #162659 in ubuntu "/var/lib/defoma/fontconfig.d/J: failed to write cache" [Undecided,New] https://launchpad.net/bugs/162659
[15:15] <bddebian> Boo
[15:16] <ubotu> New bug: #162662 in evolution (main) "Error while Expunging folder." [Undecided,New] https://launchpad.net/bugs/162662
[15:20] <ogra> bee
[15:25] <ubotu> New bug: #162664 in vlc (universe) "none of VLCs output modules play nice with Compiz" [Undecided,New] https://launchpad.net/bugs/162664
[15:27] <paulduf> mvo: thanks, (for info that old logs are overwritten)
[15:36] <ubotu> New bug: #162665 in compiz (main) "Compiz should allow exceptions for window transparency" [Undecided,New] https://launchpad.net/bugs/162665
[15:39] <paulduf> pedro (Villavicienco): You should update the web page after each bug you deal with
[15:40] <ubotu> New bug: #162666 in update-manager (main) "Open links with middle click" [Undecided,New] https://launchpad.net/bugs/162666
[15:40] <ubotu> New bug: #162667 in koffice2 (universe) "missing kdefx prevents koffice2 to start" [Undecided,New] https://launchpad.net/bugs/162667
[15:45] <paulduf> Wow, effective my message (but now I must wait pedro to finish editing :-))
[15:46] <pedro_> paulduf: sure, thanks for the reminder
[15:46] <pedro_> done
[15:48] <paulduf> pedro: ok, thanks!
[15:56] <ubotu> New bug: #162668 in svn-workbench (universe) "[gutsy] svn workbench fails when using umlaut in comment" [Undecided,New] https://launchpad.net/bugs/162668
[15:56] <ubotu> New bug: #162669 in kdebase (main) "kwin-dev package needed (kdebase-dev split)" [Undecided,New] https://launchpad.net/bugs/162669
[16:00] <ubotu> New bug: #162671 in ubuntu "VT6656 wireless chipset is unsupported" [Undecided,New] https://launchpad.net/bugs/162671
[16:05] <sourcercito> paulduf, sorry about 50499
[16:15] <ubotu> New bug: #162672 in ubuntu "Apps that use D-Bus don't work over SSH" [Undecided,New] https://launchpad.net/bugs/162672
[16:20] <ubotu> New bug: #162673 in epiphany (universe) "after ctrl+enter, down does not move the focus" [Undecided,New] https://launchpad.net/bugs/162673
[16:26] <ubotu> New bug: #162676 in ubuntu "Network manager (nm-applet) asks for keyring password after login or resume" [Undecided,New] https://launchpad.net/bugs/162676
[16:26] <ubotu> New bug: #162674 in bug-buddy (main) "[Merge] bug-buddy 2.20.1+dfsg-1ubuntu1" [Undecided,New] https://launchpad.net/bugs/162674
[16:31] <ubotu> New bug: #162677 in linux-meta (main) "restricted nvidia driver fails after gutsy upgrade" [Undecided,New] https://launchpad.net/bugs/162677
[16:31] <ubotu> New bug: #162678 in gdm (main) "Ipv6 enabled gdm can't get host correctly in ipv4" [Undecided,New] https://launchpad.net/bugs/162678
[16:38] <paulduf> sourcecito: really thinks that bug #50499 should stay invalid? Looks to me it could have usefull info even if we don't know if it still apply to feisty
[16:38] <ubotu> Launchpad bug 50499 in update-manager "upgrade to dapper removes xchat" [Medium,Invalid] https://launchpad.net/bugs/50499
[16:38] <ubotu> New bug: #162679 in nautilus (main) "php files get classified as html" [Undecided,New] https://launchpad.net/bugs/162679
[16:38] <ubotu> New bug: #162680 in torrentflux (universe) "Downloading all files fails if some files have already been downloaded" [Undecided,New] https://launchpad.net/bugs/162680
[16:46] <ubotu> New bug: #162681 in glibc (main) "libc6-i386 dependency not met in gutsy x86_64 after upgrade of libc6" [Undecided,New] https://launchpad.net/bugs/162681
[16:52] <paulduf> I have reopened #50499
[16:52] <sourcercito> paulduf, ok, as i said, i'll leave to your discretion
[16:54] <sourcercito> i was just pointing out that, the submitter doesn't give feedback on the last question for almost 9 months
[16:55] <ubotu> New bug: #162683 in linux-source-2.6.15 (main) "DVD-RAM writing error" [Undecided,New] https://launchpad.net/bugs/162683
[16:58] <paulduf> Was not really realizing this was that long. Still believe however that it is up to mvo to decide if he want to close bug #50499
[16:58] <ubotu> Launchpad bug 50499 in update-manager "upgrade to dapper removes xchat" [Medium,Confirmed] https://launchpad.net/bugs/50499
[17:00] <ubotu> New bug: #162684 in ubuntu "[Gutsy] Sony Vaio VGN-FZ* Fn Keys Not Working" [Undecided,New] https://launchpad.net/bugs/162684
[17:00] <ubotu> New bug: #162685 in ubiquity (main) "installer crashed" [Undecided,New] https://launchpad.net/bugs/162685
[17:00] <sourcercito> paulduf, don't worry about it, as long you're working on it, won't harm anyone, i think, leave it open ;)
[17:06] <ubotu> New bug: #162686 in ubuntu "1267 - Illegal mix of collations (latin1_swedish_ci,COERCIBLE) and (utf8_general_ci,IMPLICIT) for operation 'find_in_set'  this on mysql-server-4.1.15, this bug is repair on 4.1.16     OOPS-683B1042" [Undecided,New] https://launchpad.net/bugs/162686
[17:11] <ubotu> New bug: #162687 in gv (universe) "gv (gs) gobbles gigabyte of virtual memory with empty font" [Undecided,New] https://launchpad.net/bugs/162687
[17:12] <paulduf> Just as a remember, it is usefull to keep https://wiki.ubuntu.com/Bugs/Responses near while triaging (I say it for me as much as for others)
[17:28] <ubotu> New bug: #162689 in update-manager (main) "apt versionupgrade crashes when upgrade" [Undecided,New] https://launchpad.net/bugs/162689
[17:36] <ubotu> New bug: #162691 in openoffice.org2 (main) "Insert Picture causes Writer to crash" [Undecided,New] https://launchpad.net/bugs/162691
[17:40] <calc> i'm almost back down to the number of new bugs i had in august :)
[17:41]  * calc hopes to be down to ~ 0 by next week
[17:41] <calc> i've processed 100 NEW bugs since yesterday :)
[17:45] <ubotu> New bug: #162693 in oolite (multiverse) "Please sync oolite 1.65-6 from Debian unstable" [Undecided,In progress] https://launchpad.net/bugs/162693
[17:45] <ubotu> New bug: #162695 in rhythmbox (main) "will not play audio from library after changing location to new network folder" [Undecided,New] https://launchpad.net/bugs/162695
[17:46] <ubotu> New bug: #162692 in eel2 (main) "[Merge] eel2 2.20.0-2ubuntu1" [Undecided,New] https://launchpad.net/bugs/162692
[17:50] <ubotu> New bug: #162696 in openoffice.org2 (main) "Presentation will not open" [Undecided,New] https://launchpad.net/bugs/162696
[18:02] <bdmurray> ogasawara: can you add me to 45507 and set it to green?
[18:02] <bdmurray> or let me know when you are done
[18:02] <ogasawara> bdmurray: yup
[18:03] <bdmurray> ogasawara: are you using editmoin?  I find it much faster for stuff like this
[18:04] <ogasawara> bdmurray: yes, but it sort of annoying having to update the wiki after triaging each bug
[18:05] <bdmurray> ogasawara: yeah, it would be neat if you could script editmoin somehow
[18:09] <ubotu> New bug: #162698 in gnome-network (universe) "Network Manager very erratic, not saving changes, etc." [Undecided,New] https://launchpad.net/bugs/162698
[18:10] <ogasawara> bdmurray:  https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/99451
[18:10] <ubotu> Launchpad bug 99451 in update-manager "update manager fails to complete update (kubuntu, edgy->feisty): missing packages" [Undecided,New]
[18:11] <ogasawara> bdmurray: seems like an old report, in that case do we just want to ask if it's still an issue?
[18:12] <bdmurray> ogasawara: yeah, I could plop in a stock reply if you want to see what it looks like
[18:12] <ogasawara> bdmurray: that'd be great, go ahead
[18:12] <bdmurray> ogasawara: done
[18:13] <ogasawara> bdmurray: I'll update the wiki for you
[18:14] <ogasawara> damn, you're quick
[18:14] <bdmurray> indeed
[18:16] <bdmurray> ogasawara: have I mentioned that sending attachments via e-mail to a bug report doesn't work?
[18:16] <ogasawara> bdmurray: nope
[18:17] <bdmurray> okay, well that is probably what happened with bug 150358
[18:17] <ubotu> Launchpad bug 150358 in update-manager "Preparing upgrade to gutys freeze fetching files at 77 of 78" [Undecided,Incomplete] https://launchpad.net/bugs/150358
[18:20] <ubotu> New bug: #162700 in eclipse-pydev (universe) "package eclipse-pydev-gcj 1.2.5-2 failed to install/upgrade: le sous-processus post-removal script a retourn? une erreur de sortie d'?tat 3" [Undecided,New] https://launchpad.net/bugs/162700
[18:23] <ubotu> New bug: #162701 in pidgin (main) "pidgin freezes while typing a message" [Undecided,New] https://launchpad.net/bugs/162701
[18:23] <ubotu> New bug: #162704 in flac (main) "[Feisty] update of xmms-flac disables plugin" [Undecided,New] https://launchpad.net/bugs/162704
[18:23] <ubotu> New bug: #162705 in nautilus (main) "different wallpapers on each desktop" [Undecided,New] https://launchpad.net/bugs/162705
[18:23] <ubotu> New bug: #162706 in samba (main) "smb.conf resolve order messes up Nautilus" [Undecided,New] https://launchpad.net/bugs/162706
[18:24] <bdmurray> bug 71028 is interesting
[18:24] <ubotu> Launchpad bug 71028 in update-manager "Malformed Apt Source Causes Segfault in Synaptic" [Undecided,Confirmed] https://launchpad.net/bugs/71028
[18:25] <bdmurray> paulduf: you confirmed that one right?
[18:26] <bdmurray> I'm not able to reproduce it on Gutsy if I understand the bug correctly
[18:26] <ogasawara> bdmurray: what team do we assign update-manager bugs to?
[18:26] <bdmurray> ogasawara: when they are confirmed or triaged?
[18:26] <ogasawara> bdmurray: triaged
[18:27] <bdmurray> ogasawara: assignment isn't necessary - the kernel team is just special that way
[18:27] <ogasawara> bdmurray: ah
[18:32] <ace_suares> hi all... is this hug day ?
[18:33] <bdmurray> ace_suares: A mini hug day - we are specifically focusing on update-manager bug reports
[18:34] <ace_suares> cool - how's it going ?
[18:35] <bdmurray> ace_suares: pretty well you can see the list at https://wiki.ubuntu.com/UbuntuBugDay/20071114
[18:35] <bdmurray> and also look at pretty pictures at http://people.ubuntu.com/~brian/complete-graphs/update-manager/plots/
[18:36] <bdmurray> the 1day graphs are quite impressive
[18:36] <ace_suares> Search for duplicates (and mark if found) or (missing text ?)
[18:38] <ace_suares> wow impressive list....
[18:39] <bdmurray> yeah, we are trying to do some clean up and also get some traction with new tags for update-manager
[18:40] <ace_suares> unfortunately i don't have the time today, and I am also quite new as mmbr of bugsquad, but i'd like to do such a minihugday on kdepim/kmail
[18:40] <ace_suares> someday...
[18:45] <ubotu> New bug: #162708 in ubuntu "Ubuntu working with Google Android" [Undecided,New] https://launchpad.net/bugs/162708
[18:50] <ubotu> New bug: #162709 in yum (universe) "yum can't load cElementTree module" [Undecided,New] https://launchpad.net/bugs/162709
[18:52] <pedro_> yum? do we have yum?!
[18:53] <andrea-bs> apt-cache search yum
[18:53] <andrea-bs> yum - Advanced front-end for rpm
[18:53] <pedro_> just saw it, oh gosh
[18:56] <ubotu> New bug: #162710 in gnome-keyring-manager (main) "Cannot access wireless networks keys when user change is session password." [Undecided,New] https://launchpad.net/bugs/162710
[18:56] <ubotu> New bug: #162712 in evolution-data-server (main) "Changing "Show" Catagory in Contacts causes Memo, Calendar & Address Book to crash" [Undecided,New] https://launchpad.net/bugs/162712
[19:02] <bdmurray> pedro_: are you updating the wiki?
[19:02] <pedro_> not now, why?
[19:03] <bdmurray> I've looked at a couple of bugs only to find they have already been worked on
[19:03] <pedro_> oh yeah that.. that's probably because i'm not looking to the list in the wiki page..
[19:04] <pedro_> i'm going trough the whole list of bugs in u-m
[19:04] <bdmurray> Oh, well that's good.
[19:05] <pedro_> I'll review my list now and update the wiki
[19:07] <ubotu> New bug: #162714 in compiz (main) "Use opaque resize instead of rectangle resize" [Undecided,New] https://launchpad.net/bugs/162714
[19:11] <paulduf> Well, I am stopping for now. Good bug day squashing every one!
[19:11] <bdmurray> paulduf: thanks for all of your help!
[19:12] <ogasawara> bdmurray, pedro:  https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/125796
[19:12] <ubotu> Launchpad bug 125796 in update-manager "Update Manger did not update correctly" [Undecided,New]
[19:12] <pedro_> paulduf: bye thanks !
[19:13] <ogasawara> what do we do again with reports needing translations?
[19:15] <pedro_> ogasawara: 4 months old, I'd mark it as invalid and ask for a new report in english if the bug is still present
[19:16] <pedro_> probably isn't
[19:16] <ogasawara> pedro_: cool thanks.  I just stock replied asking if it's still an issue
[19:16] <bdmurray> blah blah "English is the common language of Ubuntu developers could you please post your error message in English?"
[19:16] <pedro_> cool!
[19:20] <bdmurray> bug 149078 is kind of interesting
[19:20] <ubotu> Launchpad bug 149078 in update-manager "upgrade tool crashed" [Undecided,New] https://launchpad.net/bugs/149078
[19:20] <bdmurray> you'll notice that in the head of mainlog it indicates the version of release-upgrade 0.77
[19:21] <bdmurray> which is a bit old so it'd be worthwhile to see if it is still an issue for the reporter
[19:21] <bdmurray> I think I neglected to document where to find the version of release-upgrader
[19:22] <bdmurray> Is that information helpful?
[19:24] <bdmurray> keescook: can you comment on bug 161888?
[19:24] <ubotu> Launchpad bug 161888 in update-manager "upgrade to gutsy requires user to make poor security choice" [Undecided,New] https://launchpad.net/bugs/161888
[19:26] <keescook> bdmurray: checking...
[19:27] <keescook> bdmurray: sure, confirm, wishlist, assign mvo?  I think that falls into the "don't teach bad habits" goal I have.
[19:28] <bdmurray> keescook: what would a solution be?
[19:28] <keescook> bdmurray: had update-manager not store its downloaded self in a weird location.  :)
[19:28] <keescook> s/had/have/
[19:32] <bdmurray> writing a clue file for 'dpkg --reconfigure -a' might be interesting
[19:32]  * bdmurray does it
[19:51] <ubotu> New bug: #162716 in ubuntu "FIREFOX" [Undecided,New] https://launchpad.net/bugs/162716
[19:51] <bdmurray> ubotu makes me sad
[19:51] <ubotu> Sorry, I don't know anything about makes me sad - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[19:57] <bdmurray> or better would be 'dpkg --configure -a' for the clue file
[19:58] <bdmurray> silly me
[20:01] <ubotu> New bug: #162717 in ubuntu "desktop multiplier restarts computer over and over and doesn't detect settings right, causes crash" [Undecided,New] https://launchpad.net/bugs/162717
[20:02] <bdmurray> okay, I'm out for lunch - bbiab
[20:15] <lifeless> viao
[20:22] <ubotu> New bug: #162718 in ktorrent (main) "ktorrent crashes for no aparent reason" [Undecided,New] https://launchpad.net/bugs/162718
[20:26] <ubotu> New bug: #162719 in ubuntu "In GUTSY, unchecking Enable System Beep not completely working" [Undecided,New] https://launchpad.net/bugs/162719
[20:26] <ubotu> New bug: #162720 in gtranslator (universe) "Cannot save if there is a space in directory name" [Undecided,New] https://launchpad.net/bugs/162720
[20:27] <bdmurray> anybody else seen "WARNING no activity on terminal" messages?
[20:28] <bdmurray> for the update-manager bugs
[20:31] <bdmurray> heh
[20:31] <bdmurray> "I know you
[20:31] <bdmurray> probably have this inherent sense of things but your operating system kicks
[20:31] <bdmurray> serious ass."
[20:31] <bdmurray> from a reply from a bug today
[20:31] <IntuitiveNipple> I wish it'd kick a few more bugs into touch, too :p
[20:41] <ubotu> New bug: #162722 in ubuntu "gutsy - system sounds don't work at all" [Undecided,New] https://launchpad.net/bugs/162722
[20:41] <ubotu> New bug: #162723 in xulrunner-1.9 (universe) "xulrunner-1.9 build leaves orphaned find processes, hangs buildds" [High,New] https://launchpad.net/bugs/162723
[20:41] <ubotu> New bug: #162724 in ccid (universe) "builtin O2 Micro CCID SC reader not supported" [Undecided,New] https://launchpad.net/bugs/162724
[20:47] <ubotu> New bug: #162725 in hal (main) "Brightness only works at certain levels with g-p-m due to invalid levels" [Undecided,New] https://launchpad.net/bugs/162725
[20:59] <ubotu> New bug: #162726 in xorg (main) "Xorg Crash when closing screen on clone desktop setup" [Undecided,New] https://launchpad.net/bugs/162726
[21:05] <ubotu> New bug: #162729 in rhythmbox (main) "rhythmbox stores file wrong to ipod" [Undecided,New] https://launchpad.net/bugs/162729
[21:06] <ubotu> New bug: #162694 in ubuntu "cant install updates or package" [Undecided,New] https://launchpad.net/bugs/162694
[21:06] <ubotu> New bug: #162728 in compiz (main) "[patch] Metacity-like window raise/lower" [Undecided,New] https://launchpad.net/bugs/162728
[21:10] <ubotu> New bug: #162730 in compiz (main) "Ugly black border around xterms with compiz" [Undecided,New] https://launchpad.net/bugs/162730
[21:10] <ubotu> New bug: #162731 in hybserv (universe) "hybserv initscript not working" [Undecided,New] https://launchpad.net/bugs/162731
[21:20] <ubotu> New bug: #162735 in compiz (main) "Smart window placement not so smart" [Undecided,New] https://launchpad.net/bugs/162735
[21:21] <ubotu> New bug: #162734 in ubuntu "Titles very big" [Undecided,New] https://launchpad.net/bugs/162734
[21:25] <ubotu> New bug: #162736 in dvd+rw-tools (main) "growisofs buffer size does not respect bufsize option" [Undecided,New] https://launchpad.net/bugs/162736
[21:31] <ubotu> New bug: #162737 in sound-juicer (main) "no sound" [Undecided,New] https://launchpad.net/bugs/162737
[21:31] <ubotu> New bug: #162738 in smokeping (universe) "Please sync smokeping 2.2.6-1  (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/162738
[21:39] <calc> what is a country that uses arabic?
[21:40]  * calc is checking on bug 126119
[21:40] <ubotu> Launchpad bug 126119 in openoffice.org "I can not change OpenOffice interface to Arabic" [Undecided,New] https://launchpad.net/bugs/126119
[21:40] <calc> i think one of the openoffice.org-l10n-* packages provides it but i don't know which he needs
[21:41] <ubotu> New bug: #162739 in mysql-query-browser (universe) "mysql-query-browser crashed with SIGSEGV in gtk_source_view_new()" [Undecided,New] https://launchpad.net/bugs/162739
[21:45] <calc> nm, found the answer from rene
[22:05] <ubotu> New bug: #162744 in gnome-keyring (main) "Changing the user password should also change password for the "login" keyring." [Undecided,New] https://launchpad.net/bugs/162744
[22:17] <ubotu> New bug: #162727 in baltix (main) "feature-request: splash screen could show random quotes while loading" [Undecided,New] https://launchpad.net/bugs/162727
[22:21] <ubotu> New bug: #162745 in linux-meta (main) "(gutsy) ATI driver shows movie outside window and overrides other videos" [Undecided,New] https://launchpad.net/bugs/162745
[22:21] <ubotu> New bug: #162746 in tmw (universe) "Please sync tmw 0.0.23-3  (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/162746
[22:35] <ubotu> New bug: #162747 in openoffice.org-amd64 (main) "OpenOffice's calc cannot overwrite files residing on CIFS share" [Undecided,New] https://launchpad.net/bugs/162747
[22:35] <ubotu> New bug: #162748 in cryptsetup (main) "(gutsy) encrypted linux filesystem issues" [Undecided,New] https://launchpad.net/bugs/162748
[22:45] <ubotu> New bug: #162749 in gst-pulse (universe) "Please sync gst-pulse (main) 0.9.4-2 from debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/162749
[22:45] <ubotu> New bug: #162750 in displayconfig-gtk (main) "(Gutsy) screens and graphics setup with(out) restricted drivers" [Undecided,New] https://launchpad.net/bugs/162750
[22:50] <ubotu> New bug: #162751 in trayer (universe) "Please sync trayer 1.0-1  (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/162751
[22:55] <ubotu> New bug: #162752 in ubuntu "internal error" [Undecided,New] https://launchpad.net/bugs/162752
[23:02] <ubotu> New bug: #162753 in gnump3d (universe) "gnump3d does not list lame as a required or recommended package" [Undecided,New] https://launchpad.net/bugs/162753
[23:26] <ubotu> New bug: #162756 in gtk+2.0 (main) "Cannot login as user after hard crash" [Undecided,New] https://launchpad.net/bugs/162756
[23:26] <ubotu> New bug: #162757 in linux-source-2.6.22 (main) "Screen blanks permanently on Toshiba Satellite 1800 during 7.10 Live CD bootup or full installation" [Undecided,New] https://launchpad.net/bugs/162757
[23:35] <ubotu> New bug: #162758 in gnome-launch-box (universe) "Please sync gnome-launch-box (universe) 0.2-1 from debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/162758
[23:45] <ubotu> New bug: #162761 in ubuntu "NVIDIA GeForce Go 7300 is hanging up whn using restricted driver " [Undecided,New] https://launchpad.net/bugs/162761
[23:45] <ubotu> New bug: #162762 in compiz (main) "widget layer is below full-screen windows" [Undecided,New] https://launchpad.net/bugs/162762
[23:56] <ubotu> New bug: #162742 in exaile "[gutsy-backport-request] Please backport exaile 0.2.11" [Undecided,New] https://launchpad.net/bugs/162742


[01:01] <lifeless> wgrant: StevenK: one of you may wish to tag or tag n dup bug 982539
[01:01] <_mup_> Bug #982539: Losing access to private bugs recently <Launchpad itself:New> < https://launchpad.net/bugs/982539 >
[04:08] <lifeless> wgrant: I believe 163 TypeError: <DBItem InformationType.PUBLIC, (1) Public> is not JSON serializable is yours ?
[04:11] <wgrant> lifeless: StevenK's and harmless.
[04:12] <lifeless> wgrant: its in the report, if its expected it shouldn't, otherwise it should be fixed.
[04:12] <lifeless> s2n fail otherwise
[04:12] <lifeless> StevenK: ^
[04:12] <wgrant> Of course.
[04:13] <wgrant> But it's harmless so it's not being fixed as utmost priority.
[04:53] <StevenK> lifeless: Not working today.
[04:53] <lifeless> kk
[04:54] <StevenK> lifeless: The bug has been marked as disclosure, so it's on our roadmap. I expect Curtis will get me to fix it after I finish the bug transistion to information type.
[07:20] <huwshimi> Something is broken with mp comments
[07:21] <huwshimi> The first time I submitted some comments it updated the page with my comments, but lost them on page refresh
[07:22] <huwshimi> When I returned and rewrote my comments and submitted it updated the page correctly again, but this time on refresh it had double submitted my comments (I only pressed Save Comment once)
[07:23] <huwshimi> oh and the text was different between the two submissions so the double paste wasn't just my old text appearing
[07:23] <huwshimi> oh wait, I'm lying
[07:23] <huwshimi> ignore me :)
[07:24] <huwshimi> something weird is going on with caching or something
[07:24] <huwshimi> I'll get me coat
[08:14] <czajkowski> aloha
[09:03] <adeuring> good morning
[10:41] <rick_h> morning
[12:18] <mpt> lifeless, hey, remember I told you last week that there was a really obscure difference in behavior between Invalid and Won't Fix, but I couldn't remember what it was? I just found it -- it's described in bug 196500.
[12:18] <_mup_> Bug #196500: Unexplained that only "Won't Fix" series status makes main bug status changeable <confusing-ui> <docs> <lp-bugs> <ui> <Launchpad itself:Triaged> < https://launchpad.net/bugs/196500 >
[12:37] <wgrant> mpt: Interesting that even you forget that one!
[12:53] <mpt> wgrant, you mock me
[12:59] <gary_poster> jml, do you have any predictions for when your recent testtools MPs will land?  We are working from them for our own changes and relying on them.  Having them merged would be ideal; failing that, having you maintain a fully merged and up-to-date version of those three branches would be nice; failing that we will plan to do it. https://code.launchpad.net/~jml/testtools/tagger/+merge/101904 , https://code.launchpad.ne
[12:59] <gary_poster> t/~jml/testtools/wrap-result-in-concurrent-suite/+merge/101902 , https://code.launchpad.net/~jml/testtools/tsfr-fixup/+merge/101898
[13:23] <rick_h> abentley: is there a way to get a nice list of files changed with bzr diff?
[13:23] <StevenK> rick_h: bzr st
[13:25] <rick_h> StevenK: ah cool, bzr diff --help only shows --stat-dir
[13:25] <abentley> rick_h: as StevenK says, you want "bzr stat" for that.  I prefer the --short output, which is also more scriptable.
[13:25] <abentley> rick_h: Actually, it says "see also: status"
[13:26] <rick_h> abentley: ah true. but bzr diff --stat --old=... works but isn't in the list
[13:26] <rick_h> but yea, gotcha
[13:26] <abentley> rick_h: which list?  the see also list?
[13:27] <abentley> rick_h: bzr diff --stat does not work for me.
[13:27] <rick_h> abentley: the Option: in --help
[13:27] <rick_h> bzr diff --stat --old=../devel just got me some info
[13:28] <rick_h> looks like a lot more than I changed though so looking at what it's grabbing
[13:28] <abentley> rick_h: which version of bzr are you using?
[13:28] <rick_h> abentley: 2.5.0 it looks like
[13:29] <rick_h> abentley: 2.5.0 it looks like
[13:32] <abentley> rick_h: bzr status -r ancestor:../launchpad-trunk
[13:42] <wgrant> bzr st -rsubmit: :)
[13:48] <rick_h> nice, thanks guys, exactly what I was looking for
[13:48] <rick_h> time to add an alias
[14:38] <czajkowski> sinzui: hello :D
[14:38] <czajkowski> I swear one of these days I won't come looking for you over privacy bugs
[14:38] <sinzui> hey, IRC really works. I think my ISP is disabling DNS when U1 sync on enabled
[14:39] <rick_h> sinzui: at the packet level?
[14:39] <sinzui> not sure
[14:39] <rick_h> sinzui: or just your isp dns servers don't like to respond to you?
[14:39] <rick_h> as in just set your own dns to <IP_ADDRESS> or whatever to get around?
[14:39] <sinzui> The who house was affected. I yesterday and today was fixed by me disabling u1 on all the computers
[14:40] <rick_h> strange
[14:40] <jml> gary_poster: they are blocked on lifeless
[14:40] <jml> ish
[14:40] <czajkowski> sinzui: know the feeling when in ireland i disbale U1 sync as it kills my connect :/
[14:40] <jml> gary_poster: but I can land them tomorrow, I guess.
[14:41] <czajkowski> roll on when I go back to uk it'll all be up to date again
[14:41] <sinzui> czajkowski, did you try limiting the upload to 50kb/s
[14:42] <czajkowski> yup doesnt really help not a great connection but does the job just not for U1 syning without killings things badly
[14:42] <czajkowski> sinzui: one for you https://bugs.launchpad.net/launchpad/+bug/982539
[14:42] <_mup_> Bug #982539: Losing access to private bugs recently <Launchpad itself:New> < https://launchpad.net/bugs/982539 >
[14:45] <sinzui> czajkowski, this must be related to the regression where th proper people are not subscribed
[14:46] <sinzui> czajkowski, you will need to follow up with the reporter to as an admin to subscribe the bug supervisor to the bugs. I will add this issue to the purple squad's queue
[14:46] <czajkowski> okie dokie thanks sinzui
[14:47] <czajkowski> sinzui: next monday I promise no privacy bug issues :)
[14:47] <sinzui> czajkowski, I am updating the bug to ask if this has happened in the last 8 hours...we released a change to address the previous regression
[14:47] <sinzui> maybe this bug is aa dupe
[14:48] <czajkowski> k
[14:48] <sinzui> czajkowski, oh, I see jcsackett has not landed the fix
[14:49] <sinzui> jcsackett, what is blocking Bug #967115
[14:49] <_mup_> Bug #967115: Cannot set a bug private is the bug supervisor is not set <bugs> <disclosure> <privacy> <regression> <Launchpad itself:In Progress by jcsackett> < https://launchpad.net/bugs/967115 >
[14:49] <jcsackett> sinzui: a host of tests that i missed that i need to read through to update/delete.
[14:49] <jcsackett> in the process of that now.
[14:50] <sinzui> thank you.
[14:50] <czajkowski> sinzui: jcsackett thanks folks
[15:02] <gary_poster> jml, tomorrow would be great, thanks
[15:13] <jml> gary_poster: if lifeless reviews the branches during his working day, that would be the ideal for me.
[15:13] <jml> gary_poster: but I'll land either way
[15:13] <gary_poster> jml, cool thanks
[15:38] <cjwatson> jtv: if you have a minute, review of my fix for my screw-up in https://code.launchpad.net/~cjwatson/launchpad/remove-query-distro-pending-suites/+merge/102129 would be great
[15:39] <jtv> cjwatson: you realize it's close to 23:00 on a public holiday?  :)
[15:39] <cjwatson> No :-)
[15:39] <cjwatson> Feel free to say no then ;-)
[15:40] <cjwatson> I find timezones are a disease I frequently develop immunity to, and so often forget the exact ways in which other people are afflicted.  Doubly so for holidays.
[15:41] <jtv> Are inoculations available?
[15:41] <jtv> Anyway, the new code looks to my eye suspiciously like what I suggested, but the old code looks suspiciously like what it said _before_ the branch I reviewed.  What gives?
[15:41] <cjwatson> http://www.whittard.co.uk/coffee
[15:42] <jtv> Ah, the distroarchseriesID column on the model class.
[15:43] <cjwatson> 'distroarchseries_id' => 'distroarchseriesID' was more or less the change from your review to my first merge; then in the second merge, add the missing [] and add the ID to the interface
[15:43] <cjwatson> http://bazaar.launchpad.net/~cjwatson/launchpad/remove-query-distro-pending-suites/revision/15104 is the difference
[15:44] <jtv> ahh
[15:45] <cjwatson> (I couldn't find any documentation of these magic ID attributes, and had to zen it from the surroundings.)
[15:47] <jtv> Yeah, it's pure cargo cult I'm afraid.
[15:47] <jtv> Anyway, I've filed my review.
[15:49] <cjwatson> mkay, thanks
[15:49]  * cjwatson fixes and goes to land
[15:49] <cjwatson> (Can I set it to Approved myself once it has an Approve review and I'm ready to land it?)
[16:01] <cjwatson> Oh, there we go, my logs say I asked about that a few months back
[16:01] <cjwatson> 2011-12-20.log:14:02 <benji> cjwatson: generally the MP initiator sets it to approved, sometimes they might be getting a DB review too or a UI approval
[16:02] <cjwatson> 14:07 <cjwatson> benji: ah, and I can't set the MP to Approved because I'm not in ~launchpad
[16:02] <cjwatson> So could somebody set https://code.launchpad.net/~cjwatson/launchpad/remove-query-distro-pending-suites/+merge/102129 to Approved for me so that I can land it, please?
[16:02] <jtv> cjwatson: OK, I'll do it
[16:02] <cjwatson> Thanks - I do have landing access now, but not ~launchpad
[17:30] <SpamapS> webops ping  Hi I want to make launchpad.net/charms series 'precise' the dev focus now, I need a LOSA to do that. Thanks!
[17:36] <thedac> SpamapS: so you want /charms/precise set to "Active development" correct?
[17:37] <SpamapS> thedac: right, I was told this is the process for that: https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/BranchUbuntu
[17:37] <thedac> SpamapS: ah, ok
[17:38] <SpamapS> thedac: one thing I'm a little nervous about...
[17:38] <SpamapS> thedac: it won't overwrite branches that already exist for the target series, will it?
[17:39] <thedac> SpamapS: I would not think so but that may be a question for another LP dev
[17:39] <SpamapS> thedac: I'll read the script.. please standby
[17:39] <thedac> sounds good
[17:41] <SpamapS>             except BranchExists:
[17:41] <SpamapS>                 pass
[17:41] <SpamapS> on the surface, looks good
[17:48] <olli> hiho
[17:48] <olli> is it possible to have a private distribution in LP
[18:06] <SpamapS> thedac: ok, looks good
[18:06] <SpamapS> thedac: so I think it would be smoething like './branch-distro.py -v charms oneiric precise
[18:06] <thedac> SpamapS: ok, one moment
[18:10] <lifeless> olli: not at the moment
[18:10] <lifeless> olli: you can have private PPAs which may be enough
[18:12] <thedac> SpamapS: I am getting a connection error: https://pastebin.canonical.com/64350/
[18:12] <thedac> checking now
[18:16] <SpamapS> thedac: reading
[18:18] <thedac> SpamapS: connectivity to the dbs looks good. I am not sure why that is failing
[18:22] <SpamapS> thedac: haven't seen the error yet, had to go get my phone for 2factor auth ;)
[18:23] <thedac> ok
[18:24] <SpamapS> thedac: whoa, does that have to be run on the db master directly?
[18:24] <SpamapS> oh wait thats pgpool right?
[18:25] <thedac> port 5432 is postgres 5433 would be pgbouncer
[18:25] <SpamapS>         connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
[18:25] <SpamapS> wouldn't that be.. a local server?
[18:25] <thedac> so it must not be picking up the correct config
[18:26] <thedac> we probably need an LPCONFIG=... before the command
[18:29] <thedac> SpamapS: that was it is running now
[18:29] <SpamapS> thedac: sweeeet
[18:31] <thedac> SpamapS: completed: https://pastebin.canonical.com/64352/
[18:33] <SpamapS> thedac: thanks. There must be some other process to make precise the active (not Experimental) series
[18:34] <thedac> Yes, I can set that in the UI. That was my first question
[18:36] <SpamapS> is it just that a LP admin needs to change it?
[18:36] <thedac> SpamapS: ok, the precise series is now active
[18:36] <SpamapS> perfect
[18:40] <SpamapS> thedac: so.. some last step is missing. lp:charms/* is still oneiric
[18:40] <SpamapS> anybody know?
[18:41] <SpamapS> hm maybe not
[18:42] <thedac> SpamapS: yeah, I am not sure what needs doing at this point
[18:42] <SpamapS> thedac: never mind that seems to be good, lp:charms/* is in fact precise now
[18:42] <thedac> ah, cool
[18:42] <SpamapS> The only weird thing now is that under "Active series and mielstones" only 11.10 shows
[18:43] <thedac> SpamapS: I suspect this is a timing problem. Let's give it 15 minutes and check back
[18:43] <SpamapS> thedac: sounds good :)
[18:45] <rick_h> deryck: ping
[18:45] <deryck> rick_h, hey hey
[18:46] <rick_h> deryck: ok, stuck again, but this should be the last one
[18:46] <rick_h> deryck: http://paste.mitechie.com/show/620/ chasing down the oauth bits and how they work
[18:46] <deryck> rick_h, don't worry about it.  looking....
[18:46] <rick_h> deryck: let me know if it would be easier to hop on a call
[18:46] <rick_h> basically trying to find when new oauth tokens take flight, and having issues tracing where the person bit comes into play
[18:47] <rick_h> it *appears* that not until it's been reviewed/ok'd by the user, but that doesn't make sense else how does the user see their list of unapproved tokens
[18:47] <deryck> rick_h, ok, let me look at this paste and code....
[18:48] <rick_h> deryck: rgr
[18:55] <deryck> rick_h, have you seen lib/lp/services/oauth/stories/authorize-token.txt ?
[18:57] <rick_h> deryck: no was working my way from code -> test
[18:57] <rick_h> deryck: but this seems nice and step by step'd so will go through it
[18:57] <rick_h> thanks
[18:57] <deryck> rick_h, np.  you can also grep zcml for +authorize-token to find the view.
[18:58] <rick_h> yea, I went from teh view into the model bits
[20:53] <czajkowski> salgado: ping
[20:53] <salgado> hi czajkowski
[20:54] <czajkowski> salgado: are you still working on bllueprints?
[20:54] <czajkowski> salgado: not sure if you are https://bugs.launchpad.net/launchpad/+bug/983309
[20:54] <_mup_> Bug #983309: Cannot read blueprints'  titles when the dependecy tree is  large <Launchpad itself:New> < https://launchpad.net/bugs/983309 >
[20:55] <beuno> czajkowski, u1 has captured salgado and has no plans of releasing him again
[20:55] <czajkowski> beuno: ello and good evening to you
[20:55] <salgado> czajkowski, not anymore, no
[20:55] <czajkowski> salgado: grand job
[20:56] <salgado> czajkowski, the Linaro infrastructure team is still on the hook for any issues related to work-items in LP, but I don't think this would qualify
[20:57] <czajkowski> nods
[20:57] <salgado> czajkowski, however, that bug was filed by someone from Linaro so they might end up fixing it too
[20:58] <salgado> czajkowski, jamestunnicliffe has taken over the work-items stuff, btw
[20:59] <czajkowski> salgado: good to know
[21:00] <mwhudson> i'm pretty sure that bug is a duplicate fwiw
[21:01] <mwhudson> https://bugs.launchpad.net/launchpad/+bug/576807
[21:02] <_mup_> Bug #576807: blueprint dependency graph is too small and unreadable <lp-blueprints> <Launchpad itself:Triaged> <NULL Project:Invalid> < https://launchpad.net/bugs/576807 >
[21:55] <m_3> thedac: hi, I'm working with SpamapS to promote our charms up to precise
[21:55] <m_3> thedac: we've still got some problems with the branch names after what you/clint did a couple of hours ago
[21:55] <m_3> thedac: do you have a sec to help with that?
[21:55] <thedac> m_3: sure
[21:56] <m_3> so the lp aliases are lp:charms/<charm-name> which now points to lp:~charmers/charms/precise/<charm-name>/precise
[21:57] <m_3> they should be pointing instead to lp:~charmers/charms/precise/<charm-name>/trunk
[21:57] <m_3> I can push them to .../trunk and then promulgate which updates the alias to point to the correct branch
[21:58] <thedac> ok, let me see if I can do anything in the UI
[21:58] <m_3> however, that results in the alias pointing to .../trunk which is stacked on top of .../precise
[21:58] <m_3> then it won't let me remove the .../precise branches
[21:59] <m_3> thedac: I'm not sure what to do with it... I would guess that we could fix the aliases if we just had a mass rename of the aliased branches to .../trunk
[22:01] <m_3> lp:charms/sbuild is an example of one I tried to fix manually
[22:01] <thedac> m_3: I am not seeing a way for me to change that. I would guess the update script did this.
[22:01] <thedac> Anyone else have an idea what we can do? ^^^^
[22:01]  * m_3 really clueless about that... lp newb
[22:01] <maxb> It sounds likely that branch-distro would have set things up this way
[22:02] <maxb> Give me a charm name that hasn't had manual fixing attempts to look at?
[22:02] <m_3> lp:charms/mongodb
[22:03] <m_3> it used to point to lp:~charmers/charms/oneiric/mongodb/trunk for the oneiric versions
[22:03] <m_3> clint ran some branch-distro script and now it points to lp:~charmers/charms/precise/mongodb/precise
[22:03] <maxb> Right, that'd be branch-distro at work
[22:04] <m_3> gotcha
[22:04] <maxb> Does it matter that the branch name is <series-name> rather than "trunk" ?
[22:04] <m_3> gustavo's charm store looks exclusively for .../trunk branches though
[22:04] <maxb> ah
[22:04] <maxb> Well, fixing it all up ought to be fairly easy with a launchpadlib script
[22:05] <maxb> And you'd need to get a fix into branch-distro for the q-series opening
[22:06] <m_3> oh, ok...  I'll go read up on launchpadlib.  The manual changes created .../trunk stacked on .../precise which left dangling branches around that I couldn't clean up.  I assumed that launchpadlib would just do the same basic thing
[22:07] <maxb> m_3: Presumably after you pushed the sbuild/trunk you did something to make it the official branch for precise?
[22:08] <maxb> Well, you don't want to use launchpadlib to create new branches, you want to use it to rename the existing ones
[22:09] <m_3> maxb: yes... our promulgate script (have to look to see what it does)... essentially creates the lp:charms/sbuild alias for the branch
[22:10] <m_3> maxb: ok, looking for rename
[22:10]  * m_3 and hoping clint returns from lunch soon :)
[22:10] <m_3> maxb thedac: thanks!
[22:10] <thedac> m_3: no problem
[22:12] <maxb> m_3: can you "re-promulgate" the ~charmers/charms/precise/sbuild/precise branch and delete the current .../trunk one?
[22:13] <m_3> maxb: sure... one sec
[22:15] <m_3> maxb: done
[22:16] <m_3> lp:charms/sbuild points to lp:~charmers/charms/precise/sbuild/precise again
[22:16] <maxb> If you have a "Change branch details" link in the right-hand portlet of https://code.launchpad.net/~charmers/charms/precise/sbuild/precise you can use that to change the name to trunk
[22:17] <SpamapS> Oh
[22:17] <SpamapS> there's a rename?!
[22:17] <maxb> yes :-)
[22:17] <m_3> maxb: ok, did that... poking around now
[22:17] <SpamapS> fantastic
[22:18] <SpamapS> can we map that to launchpadlib calls?
[22:18] <maxb> Give me 5 minutes, I'll whip up a launchpadlib script to do the rest in bulk
[22:18]  * SpamapS has just noted that maxb is his hero
[22:18] <m_3> SpamapS: can you try out sbuild from the store for precise now?
[22:18]  * m_3 no free envs atm
[22:19] <m_3> SpamapS: actually, nevermind... that worked!
[22:20] <SpamapS> m_3: woot
[22:22] <maxb> Give http://paste.ubuntu.com/933212/ a try .... a little difficult for me to test without a fake Launchpad, but I think it should work
[22:25] <maxb> it successfully complains about me not having access to edit the charms branches, anyway :-)
[22:27] <wgrant> SpamapS, m_3: Why do you have the custom naming scheme?
[22:27] <wgrant> branch-distro is not designed to do that.
[22:27] <wgrant> Why doesn't juju use the alias?
[22:27] <m_3> maxb: Yikes... it did a couple, then I got an IntegrityError
[22:28] <wgrant> m_3: There's probably already one with that name.
[22:28] <m_3> wgrant: right... excepting that case
[22:28] <SpamapS> wgrant: I don't know why the custom name is needed
[22:29] <m_3> wgrant: no idea on the name
[22:29] <SpamapS> m_3: probably statusnet
[22:29] <SpamapS> wgrant: Something about using get_branch_tips, which I don't believe shows the aliases
[22:31] <maxb> m_3: ok, my script is only acting on branches matching ~charmers/charms/precise/*/precise, so just manually resolve the duplication issue for that particular charm, then re-run; it won't go back over ones it has already renamed
[22:31] <SpamapS> wgrant: also we do actually use the name to specify charms to deploy via the store or not for non-official charms.
[22:31] <maxb> I agree with wgrant that using the aliases would make far more sense, but this way we can work with the existing hardcoded assumptions for now
[22:31] <SpamapS> wgrant: so lp:~clint-fewbar/charms/precise/puppet/trunk is a signal to the charm store to pick that charm up, but lp:~clint-fewbar/charms/precise/puppet/in-progress would not be published
[22:31] <wgrant> wtf
[22:32] <wgrant> That is, um, intriguing.
[22:32] <maxb> SpamapS: That seems a bit.... wrong. LP already has a concept of official-ness, which is what drives the aliases. Why not use that, rather than some odd naming convention?
[22:32] <SpamapS> I would prefer that we use the branch metadata, and only ship 'Mature' branches
[22:32] <SpamapS> maxb: we want users to be able to say something is official without access to the whole distro
[22:33] <SpamapS> maxb: its only official in their personal namespace.
[22:33] <SpamapS> so it becomse cs:~clint-fewbar/precise/puppet
[22:33] <SpamapS> (cs is the charmstore)
[22:33]  * maxb has trouble grappling with the idea of "official in a personal namespace"
[22:33] <SpamapS> maxb: think PPA
[22:33] <wgrant> I suspect it means "stable"
[22:33] <wgrant> Which is what Mature means
[22:33] <SpamapS> its as official as a package pushed to a PPA
[22:33] <SpamapS> which means, not very :)
[22:34] <SpamapS> I think we should move it to using the Mature status instead
[22:34] <m_3> ok, script ran... only a couple of pre-existing branches
[22:34] <maxb> Surely "trunk" is exactly the wrong name to use to mean "Mature" ? :-)
[22:34] <SpamapS> and drop the trunk thing altogether
[22:34] <SpamapS> maxb: depends on whether you are dev or ops ;)
[22:34] <maxb> I'm devops :-)
[22:34] <SpamapS> then you ship trunk, after it passes tests
[22:35] <lifeless> s/trunk/ripe/ perhaps
[22:35] <m_3> thedac maxb wgrant: thanks!
[22:37] <maxb> m_3 / SpamapS: Well, I guess you'll figure something out... just remember that branch-distro is going to copy whatever is marked as official to a branch named <whatever-q-series-turns-out-to-be> next cycle
[22:37] <StevenK> sinzui: http://pastebin.ubuntu.com/933230/
[22:39] <SpamapS> maxb: I'm opening a bug that we should ship all "Mature" branches, not just those named 'trunk'
[22:40] <SpamapS> bug #983530 to be exact
[22:40] <_mup_> Bug #983530: charm store should publish all 'Mature' branches. <juju:New> < https://launchpad.net/bugs/983530 >
[22:42] <maxb> There appear to still be 5 branches named ~charmers/charms/precise/*/precise, btw
[22:43] <maxb> Also, branch-distro has its own ideas of how it should manipulate branch lifecycle status, so you'll want to watch out for that
[22:45] <[reed]> who is an appropriate contact for launchpad's bugzilla integration nowadays?
[22:53] <sinzui> StevenK, wgrant, wallyworld, jcsackett: http://blog.launchpad.net/general/a-tale-of-two-travesties
[23:03] <SpamapS> maxb: Right, I noticed they all are set to 'Development', which makes sense.. we really want them to be Mature if the one they copied from was Mature.
[23:04] <SpamapS> maxb: we might need some alternative behavior flags for our use case... but I bet it takes us a year before we have a patch for LP ;)
[23:13] <maxb> SpamapS: Fortunately all the code you care about here is localized in one file, eliminating much of the usual scaryness of chasing around the LP codebase
[23:13] <maxb> lib/lp/codehosting/branchdistro.py ftr
[23:13] <SpamapS> maxb: its more about the scariness of chasing down our time to get 'er done
[23:14] <maxb> Aww. It's really just a fairly simple Python script once you learn to look past the "Eek! Launchpad!" factor :-)
[23:14] <SpamapS> so I think this is a bug in branch-distro
[23:15] <SpamapS> if I push to lp:charms/somethingnew
[23:15] <SpamapS> I get lp:~myuser/charms/precise/somethingnew/trunk
[23:15] <SpamapS> I should reasonably expect that branch-distro would duplicate that behavior, and not call a copy of that by the series name, but 'trunk' again.
[23:15] <maxb> hm
[23:16] <maxb> You do rather have a point there, that the two components of Launchpad ought to at least be consistent
[23:16] <SpamapS> this is causing enormous pain now because the official branches for things like rabbitmq-server were forked, and already existing as lp:~something/charms/precise/foo/trunk
[23:16] <SpamapS> which were not seen as BranchExisting errors. :-P
[23:17] <maxb> why is this causing enormous pain? A mild discomfort akin to a stone in your shoe, I would have thought :-)
[23:17] <wgrant> SpamapS: Ubuntu doesn't use the push-to-alias code, so it doesn't work well for distros.
[23:17] <wgrant> SpamapS: That's designed for projects.
[23:18] <wgrant> s/push-to-alias/push-to-new-alias/
[23:18] <SpamapS> indeed, I think we are breaking new ground.. and have happily found an inconsistency :)
[23:19] <SpamapS> wgrant: I assume the package importer does the new branch creation manually then.
[23:20] <wgrant> SpamapS: Right.
[23:21] <SpamapS> so either push to new alias code should use series name in distros, and we should fix the charm store (seems the low impact way) or branch-distro should have a new option --branch-name to override the default of $series
[23:22] <StevenK> I do *not* like the idea of hacking branch-distro. It is utterly the wrong place.
[23:22] <SpamapS> Even better would be that a new flag would be added to the distro object to note that it has charms in it, and change the behavior.
[23:22] <SpamapS> Because there are other things that look weird in launchpad.net/charms because we're not storing packages there
[23:22] <SpamapS> like, it would be cool to be able to say +charm instead of +source ..
[23:23] <SpamapS> and to drop the warnings about a package that has never been published
[23:23] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/forbid-proprietary-api/+merge/102201 since we're off the call.
[23:25] <wgrant> SpamapS: I objected pretty strongly to using distros in the first place :)
[23:25] <wgrant> StevenK: Won't that break like a million tests?
[23:25] <StevenK> Hm. Maybe a few.
[23:26] <SpamapS> wgrant: you'd prefer we have each charm as a project? Or a giant single bzr branch of all the charms?
[23:26] <cjwatson> When I've done QA for r15103 (which will be tomorrow) and everything up to there is deployable, should I remove that deployment exception entry from LaunchpadProductionStatus on the grounds that any future deployment will be >=15103, or is there some other protocol for letting people know that that deployment exception can go away?
[23:26] <SpamapS> wgrant: we've already used the cross-charm capability to track bugs that affect multiple charms. And each charm in a branch gives us the ability to delegate permissions very effectively.
[23:27] <wgrant> cjwatson: Leave it there, just in case.
[23:27] <maxb> Other than the fact we have vast precedent, why does it make sense to use the series name as the branch name for default distro branches?
[23:27] <wgrant> cjwatson: Although I'll likely be deploying 15103 before you wake up.
[23:27] <cjwatson> Oh, there's a Comments column
[23:27] <cjwatson> wgrant: ah, well, if you want to do the obvious QA on it then fine by me
[23:28] <wgrant> maxb: I like to think that one day we will make project and distribution branch models not gratuitously divergent.
[23:28] <wgrant> maxb: Probably by removing the distroseries from the URL
[23:28] <maxb> um?
[23:28] <wgrant> This would make that easier, although it's probably not the reason.
[23:29] <wgrant> maxb: The distro branch namespace is divided up by series. Project branch namespaces aren't.
[23:30] <wgrant> If we ever want to make these consistent, it's possibly handy to keep the branch names fairly unique like that.
[23:30] <maxb> Oh, I see what you mean now
[23:30] <jelmer> wgrant: +1
[23:30] <wgrant> (of course I basically completely disagree with how distro branches work, but it's probably a bit late to make big changes)
[23:31] <wgrant> But this change is reasonably inoffensive and sensible, so might happen in a few years.
[23:31] <maxb> It would be the incompatible change from hell, but it has a certain sense to it
[23:31] <jelmer> wgrant: what's your fundamental problem with them, just that they're so different from project branches?
[23:32] <SpamapS> for the record, as an ubuntu developer and charm developer, I really like the way distro branches work :)
[23:32] <SpamapS> though I would prefer to have automatic population of -updates and -proposed for ubuntu so merge proposals for SRU's works properly
[23:34] <maxb> I'm not sure I'd want -updates and -proposed to pop into existence for every package with identical content to the release pocket, for *every package*
[23:35] <cjwatson> we sort of want them to autovivify when pushed to.  which is not exactly trivial.
[23:35] <maxb> On the other hand, if you don't do that, you kind of need the ability to file a merge proposal onto a target branch which doesn't exist yet
[23:35] <SpamapS> I'd be happy if they were just seen as aliases to the main package, until they were actually published/pushed to
[23:35] <cjwatson> pushed to> or otherwise referenced as an lvalue
[23:35] <cjwatson> if I may shamelessly borrow terms
[23:35] <maxb> It's a good term :-)
[23:38] <wgrant> jelmer: They make collaboration between distros hard -- in reality they will eventually just be minor branches of the upstream code, but they're all completely segregated and invisible to the upstream project.
[23:38] <wgrant> jelmer: Most packages would do fine without a separate namespace in the distro.
[23:38] <wgrant> They could just be specially linked branches in the project.
[23:39] <jelmer> wgrant: that doesn't seem like a fundamental problem though, mostly a presentation issue
[23:39] <maxb> The hard split between debian and ubuntu isn't great
[23:40] <maxb> On the other hand, yes, it's really just a presentation problem
[23:41] <wgrant> Perhaps.
[23:41] <jelmer> .. and an issue with the importer, which doesn't take upstream links into account when it generates file ids or ancestry
[23:41]  * SpamapS wonders if we'll ever get all these worms back in the can
[23:43] <jelmer> with sensible heuristics, and perhaps some support for handling parallel imports there is a lot we can do
[23:43] <jelmer> that's a nontrivial amount of work though
[23:44] <StevenK> wgrant: I think you're right that it will break a few tests. But I'd like it to break for users. :-(
[23:44] <wgrant> StevenK: Also, that error message is entirely useless.
[23:44] <wgrant> I can't transition to proprietary because I can't transition to proprietary :(
[23:49]  * StevenK isn't sure how to check if it's from the API.
[23:49] <StevenK> In fact, I'm not certain if you can.
[23:49] <wgrant> You can't directly.
[23:50] <StevenK> Hm, can't think of a way to solve this then. That's disappointing.
[23:50] <wgrant> You could add a from_api argument or something
[23:52] <timrc> lol @ <wgrant> But this change is reasonably inoffensive and sensible, so might happen in a few years.
[23:52] <StevenK> wgrant: Or I could fix it differently and allow it only if the pillar has private_bugs.
[23:52] <jelmer> timrc: you've not met wgrant before?
[23:52] <wgrant> StevenK: But that's wrong.
[23:52] <jelmer> timrc: :P
[23:53] <StevenK> wgrant: I thought that was the plan?
[23:53] <timrc> jelmer, No, I hope he takes his comedy act on the road though :) jk
[23:53] <wgrant> StevenK: "plan" being the important word here
[23:53] <wgrant> StevenK: Future.
[23:53] <StevenK> Keeping in the mind the plan is somewhat elastic. :-)
[23:53] <wgrant> The plan is fairly well defined in only slightly conflicting ways in the minds of sinzui and myself.;


[00:09] <silverarrow> anyone awake?
[00:09] <silverarrow> */join radeon
[00:09] <silverarrow> I'm attempting a install now
[00:22] <phillw> silverarrow: I am awake
[00:22] <silverarrow> good
[00:22] <phillw> silverarrow: which set of instructions are you follwong?
[00:22] <silverarrow> are you handy with driver packages and unusual solutions?
[00:23] <silverarrow> I think wxl made it
[00:23] <phillw> silverarrow: I do not have a PPC
[00:23] <silverarrow> the live radeonfb.....something
[00:23] <silverarrow> but you do have a head
[00:23] <silverarrow> hopefully
[00:23] <wxl> i didn't find it
[00:23] <wxl> greg did
[00:23] <silverarrow> and are clever with this stuff
[00:23] <wxl> i found the nouveau alternative
[00:23] <silverarrow> nouveua?
[00:24] <silverarrow> which one was that?
[00:24] <phillw> silverarrow: wxl can you please test https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058641
[00:24] <silverarrow> I am installing now, 12.04 is deleted
[00:24] <phillw> it is real easy patch.
[00:24] <silverarrow> I will
[00:24] <silverarrow> i am slighly worried about wireless drivers
[00:24] <wxl> nouveau = nvidia
[00:24] <wxl> if you have radeon it's irrelevant
[00:25] <wxl> the radeon machine i'm borrowing i can't instlal to
[00:25] <wxl> if i can test live we're good
[00:25] <silverarrow> I have access to routuer, but not here
[00:25] <silverarrow> aha
[00:25] <wxl> so i can't help with that one phillw sorry
[00:25] <silverarrow> i have radeon
[00:25] <wxl> altho wait
[00:25] <wxl> maybe i can
[00:26] <silverarrow> are yoiu familiar with "install alongside LTR 12l.04" option ?
[00:26] <phillw> wxl: my CAPS in my email are really intended, ppc people either stop mentioning their individual successes an get a solution that works accross the board, or there will not be a 12.10 PPC release. Can you go and bang some heads together, please?
[00:28] <phillw> I have a Nvid one via kernel, and a proposed radeon via x-term.
[00:28] <phillw> time is running out.
[00:29] <silverarrow> I am at home , with my iBook, I can work with you
[00:29] <silverarrow> i am installing now,
[00:29] <silverarrow> and it seems to work !!
[00:29] <wxl> that solution greg proposed will work for all radeon chips
[00:29] <wxl> it's likely this will too
[00:30] <wxl> i think that people are mentioning individual success but with multiple people reporting the same thing it is pretty across the board
[00:30] <phillw> wxl: i NEED  proposal to take to the ubuntu-x team... and I need it about last week :(
[00:30] <silverarrow> it will be implemented in the live CD boot stage ?
[00:31] <silverarrow> phillw: so right away?
[00:31] <silverarrow> I am not clever enough to work out solutions
[00:31] <phillw> wxl: when the improvements knocked out both chip sets, it was a nightmare. So many bugs were being reported.
[00:32] <silverarrow> I can test, and do all suggestions
[00:32] <silverarrow> and I am here all day for days now
[00:32] <balloons> phillw, pong
[00:32] <phillw> We lost two staging cycles over it
[00:32] <silverarrow> i can take time to work with pcc every day
[00:33] <phillw> we really do need to nail this down now. I honestly believe we have enough information to do so.
[00:33] <phillw> hiyas balloons
[00:34] <silverarrow> can I painlessly install Ubuntu alongside Lubuntu, and test all fine?
[00:34] <phillw> silverarrow: as a tester, you may fail to realise just how important you are :)
[00:35] <silverarrow> maybe
[00:35] <wxl> anyone know a pastebinit type program for images?
[00:35] <balloons> hiya
[00:35] <phillw> silverarrow: indeed you can, but dependant on the spec of your PPC you may find Ubuntu is too hungry for resources
[00:35] <silverarrow> i have an iBook that are still some use, I see several posts on my model on the forum
[00:36] <phillw> wxl: http://imagebin.org/
[00:36] <wxl> NOT A COMMAND LINE PROGRAM
[00:36] <silverarrow> now for fist bootup after install
[00:37] <phillw> wxl: in that case, Im sorry.. no... balloons do you know of such a site?
[00:37] <wxl> NOT A SITE
[00:37]  * phillw runs off for a ciggie :)
[00:37] <phillw> wxl: I know... a command!
[00:38] <silverarrow> so how do I activate wireless without wired web connection? b43 drivers
[00:38] <balloons> imgur
[00:38] <silverarrow> serisouly, I have been on that subject all day and half of yesterday
[00:39] <wxl> silverarrow: no can do
[00:39] <wxl> i thought i explained that to the mailing list in elaborate detail?
[00:39] <silverarrow> i see
[00:39] <balloons> imageshack used to be big back in the day
[00:40] <silverarrow> there has to be a way to get the b43 package on a usb stick?
[00:40] <silverarrow> from a windows computer
[00:40] <wxl> sure
[00:41] <silverarrow> and it would hopefully install in lubuntu
[00:41] <wxl> well you don't install "it"
[00:41] <wxl> per se
[00:41] <wxl> you use b43-fwcutter to cut it out and install it
[00:41] <wxl> once you have the files
[00:41] <silverarrow> hmm
[00:42] <silverarrow> ...
[00:42] <wxl> btw i've never actually done this but i know enough about it to have a vague idea of how it owrks
[00:42] <wxl> balloons: any ideas that don't require javascript?
[00:42] <balloons> for image hosting/
[00:42] <balloons> what are you trying to do?
[00:43] <balloons> imageshack.us might not
[00:43] <wxl> do this in terminal
[00:45] <silverarrow> what?
[00:46] <wxl> HOW WEIRD
[00:46] <wxl> the screenshot looks decent
[00:48] <silverarrow> we should get all the ppc guys on irc
[00:48] <silverarrow> which might get things rolling
[00:49] <phillw> balloons: you free for an a quick PM while the PPC team take over -testing?
[00:49] <silverarrow> draft them to irc
[00:50] <phillw> silverarrow: I really do wish we could arrange a session on IRC meeting to get things chatted about and plot a way to the final release.
[00:50] <silverarrow> trouble with the fwcutter for powerpc
[00:50] <silverarrow> it just isn't anywhere
[00:50] <wxl> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/50
[00:50] <wxl> there
[00:50] <wxl> tons of info for you, phillw
[00:50] <wxl> run with it
[00:50] <wxl> also i note there are others complaining it doesn't work
[00:51] <phillw> wxl: that bug is dead.. Why do I have keep saying so?
[00:51] <wxl> um
[00:51] <wxl> it's not dead
[00:51] <wxl> thats my point
[00:51] <wxl> the supposed fix doesn't work for me
[00:51] <wxl> nor others who have left comments
[00:51] <silverarrow> this channel are all right, people should appear whithout worry about anything?
[00:52] <silverarrow> is*
[00:53] <phillw> wxl: look at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/48 and then https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518/comments/50
[00:53] <phillw> the fix was for #48.
[00:53] <wxl> 48 says it works
[00:53] <wxl> 49,50 say otherwise
[00:54] <phillw> your bug is nothing to do with anything but nVid, which is a small %age of PPC graphic chip sets. the other is an 'X' bug.
[00:55] <wxl> dude
[00:55] <wxl> look at the bug:
[00:55] <wxl> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518
[00:55] <wxl> see "linux" ?
[00:55] <wxl> not x
[00:55] <wxl> linux
[00:55] <wxl> and yes, this is isolated to nvidia, which is well established in the comments
[00:55] <phillw> wxl: ::SIGH:: the fix is for nVidia.
[00:55] <wxl> IT DOESN"T FIX IT
[00:56] <phillw> the bug that looks the same, is for a totally different GPU.
[00:56] <phillw> wxl: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058641
[00:56] <wxl> i get the feeling either you don't know what i'm talking about or vice versa or both
[00:56] <wxl> i'm not worried about that one
[00:56] <wxl> i don't have an nvidia chip
[00:57] <wxl> i mean i don't have a radeon chip
[00:57] <wxl> you're making me crazy phillw
[00:57] <phillw> wxl: in which case... ignore https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518
[00:57] <wxl> also i refute your assertion. most of the ppcs out there are aluminum g4s, all of which could optionally come with radeon or nvidia
[00:57] <phillw> as it has exactly ZERO to do with your issue?
[00:57] <wxl> right, and that bug is nvidia only it seems
[00:57] <wxl> AND IT DOESN"T WORK
[00:57] <wxl> the LINUX bug is related
[00:58] <wxl> the whole comments, everything, talks about nvidia and nouveau and is a bug against the kernels and the fix attempts to solve the driver issue
[00:58] <wxl> so it's everything to do with my issue
[00:58] <phillw> wxl: yes, it is.. changes have been made... I do follow the chat, but for Radeon, it is 'X' who need to fix it. It will not be fixed via kernel.
[00:59] <wxl> the x bug does not
[00:59] <wxl> maybe i'll write this up to the mailing list and maybe then this will make sene to you
[01:00] <phillw> wxl: do so... i see not one mention of Nvidia on https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058641
[01:00] <wxl> nor do i because i'm not talking about that bug
[01:00] <wxl> you're obsessed with it, apparently, but i haven't mentioned it this entire time
[01:01] <phillw> wxl: which radeon bug is your favourite? Only rule is.... no mention of nVid bugs, as that was kernel, and Radeon is 'X'.
[01:02] <silverarrow_> I am online
[01:02] <wxl> ok here we go phillw
[01:03] <wxl> run this:
[01:03] <wxl> w3m -dump https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518 | grep -ci nvidia
[01:03] <phillw> wxl: I don't have a ppc machine
[01:03] <wxl> (tells you how many times the word nvidia turns up on that page)
[01:03] <wxl> you don't need a ppc machine
[01:03] <wxl> just a linux machine
[01:03] <wxl> give it a shot
[01:03] <phillw> so there is little point me trying.
[01:03] <wxl> or i could spoil the punchline if you prefer
[01:04] <wxl> FIFTEEN
[01:04] <wxl> how can the bug not be about nvidia when it's mentioned fifteen times?
[01:04] <wxl> change the nvidia to radeon and you get 1
[01:04] <wxl> it's not a bug about radeon
[01:04] <wxl> the x bug is
[01:04] <wxl> not the linux bug
[01:05] <wxl> the bug relevant to my symptoms is the linux bug
[01:07] <silverarrow> is server down or slow for downloading packages?
[01:08] <silverarrow> 70 minutes to dowload b43 stuff
[01:08] <silverarrow> !
[01:14] <silverarrow> should I post an email suggestion a irc meeting, just to see what the respons is+
[02:02] <silverarrow> how do you load or reset a new driver for wifi?
[11:39] <silverarrow> there is no ppc package for b43 firmware?
[11:39] <silverarrow> !!!!!!!!!!!!!!!!!!!
[14:39] <wxl> anyone have a clue what the default user/pw would be for the lubuntu alternate cd?
[14:40] <smartboyhw> Dunno
[14:40] <wxl> for ubuntu maybe? :)
[14:40] <smartboyhw> wxl, no alternate for vanilla Ubuntu:P
[14:41] <wxl> oh well
[14:42] <smartboyhw> phillw, you know?
[14:42] <phillw> nope, there should be no password.
[14:43] <smartboyhw> phillw, how about user then? wxl also needs that
[14:44] <phillw> there should be no user / password to install the alternate. You set them up as part of the install.
[14:46] <phillw> wxl: did the self check on the md5sum come up as okay?
[15:07] <wxl> phillw, smartboyhw: nevermind question. pebkac.
[15:26] <silverarrow> where is the x but we are to test?
[15:26] <smartboyhw> silverarrow, er....I don't understand what are you asking:P
[15:27] <silverarrow> phillw linked to a bug, and I thought I bookmarked it
[15:27] <silverarrow> but apparently not
[15:27] <smartboyhw> silverarrow, what bug is it?
[15:27] <phillw> silverarrow: give me a moment
[15:27] <smartboyhw> silverarrow, find the irclogs then in irclogs.ubuntu.com :P
[15:28] <silverarrow> normally I could do that, but xchat and 12-04 is all gone
[15:31] <phillw> silverarrow: you got radeon or nvidia chip set?
[15:31] <silverarrow> radeon
[15:33] <phillw> silverarrow: head over to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058641
[15:36] <silverarrow> thanks
[17:43] <silverarrow> hi
[17:44] <silverarrow> I am in pidgin from quantal
[17:44] <silverarrow> finally !!
[17:44] <silverarrow> pidgin seems to work better this time
[17:49] <silverarrow> hi
[17:50] <GridCube> hi
[17:51] <silverarrow> how are ou GridCube
[17:51] <silverarrow> I am finally getting somwhere with quantal
[17:52] <GridCube> :) thats nice, but this is not a channel for random chatter :)
[17:52] <silverarrow> ture
[17:52] <silverarrow> true
[17:53] <silverarrow> I am onto a bug
[17:53] <GridCube> fire then :D
[17:53] <silverarrow> it seems to be fine on my hardware though
[17:53] <GridCube> someone might help you
[17:53] <silverarrow> bug #1058641
[17:54] <silverarrow> I booted and installed yesterdays download, and have not noticed anything
[18:00] <njin> hallo phillw, when i launch Abiword in Lubuntu it start focused (with blinking cursor) but won't type, I've to click on the sheet to have it working. is this a bug in Lubuntu or abiword ?
[18:01] <silverarrow> I can type all fine in abi
[18:01] <silverarrow> not yet installed libre
[18:02] <silverarrow> njin: did you launch in terminal?
[18:03] <silverarrow> I got this error message WARNING: gnome-keyring:: couldn't connect to: /home/taoseeker/.cache/keyring-IobUNG/pkcs11: No such file or directory
[18:03] <silverarrow> but it launched fine
[18:04] <silverarrow> not sure what that is about
[18:06] <silverarrow> we seem to call on phillw
[18:07] <phillw> silverarrow: I'd report the issue you see against lubuntu, at least that way Julien will get to see it.
[18:07] <wxl> wuz the deal?
[18:08] <wxl> i get those gnome-keyring errors occassionally too but they seem to affect nothing
[18:08] <silverarrow> not sure yet
[18:09] <silverarrow> I got it when I launched abiword in terminal
[18:09] <wxl> i know better and should report it but i don't sweat it
[18:09] <wxl> bigger fish to fry
[18:09] <silverarrow> just to check with njin
[18:09] <silverarrow> I could post my xorg.0 log though
[18:10] <silverarrow> if it is any help on the 1058641 bug
[18:10] <wxl> bug 1058641
[18:11] <wxl> what symptoms do you get? can you boot, with no special parameters, to the desktop?
[18:11] <silverarrow> after install I seem to be fine
[18:11] <silverarrow> I used the suggested fix for radon
[18:12] <silverarrow> live video=radoenfb...somthing
[18:12] <wxl> which one? the video=radeonfb:1024x768-32@60?
[18:12] <wxl> right, what if you don't use it?
[18:12] <silverarrow> yes
[18:12] <silverarrow> I don`t use it after install
[18:12] <silverarrow> and all seems fine
[18:12] <silverarrow> I have the 1 of october daily
[18:13] <wxl> hm
[18:13] <wxl> if you still have the disc, could you try booting to the live session with no parameters?
[18:13] <silverarrow> and this is the first time I have managed to boot live and install at all
[18:13] <silverarrow> I could
[18:13] <wxl> if you can boot to the desktop with no special parameters, even if the screen is a little funky, you don't have the symptoms of that bug
[18:13] <silverarrow> right now?
[18:14] <wxl> but it might be useful to say as such and make sure to be clear what chip you have (lspci | grep VGA)
[18:14] <wxl> do it when you like; it's your time XD
[18:15] <silverarrow> I have tried before, with or with out all the suggest fixes
[18:16] <wxl> ok so the important thing is to post your results
[18:16] <njin> phillw, is already know that the checkmark in ubiquity -preparing to install is not working, it only change colour but the checkmark don't appear
[18:16] <wxl> aas the bug report is written it should affect all radeon chips. so you could reply and say "i have such-and-such chip and i can boot to livecd and to desktop without needing to do anything, not even using special boot parameters"
[18:16] <njin> silverarrow, same error for me if launched in terminal
[18:17] <wxl> which AT LEAST makes it so they can narrow down which chips are affected and which are not
[18:17] <wxl> which is where the nvidia bug seems to be heading
[18:21] <silverarrow> i have no idea about the nvida driver
[18:21] <silverarrow> or xorg hickup
[18:23] <wxl> don't worry about nvidia; you dont have one
[18:24] <silverarrow> graphics seem to be difficult all over
[18:26] <silverarrow> I started a download, will boot cd as soon as it finishes
[18:28] <silverarrow> I want to do the testing right
[18:28] <silverarrow> not sure what phillw can make use of
[18:28] <silverarrow> and julian
[18:29] <phillw> silverarrow: when you have an iso, if you use zsync you will find it downloads faster as zsync will only download the stuff that has changed.
[18:30] <silverarrow> I like the wireless signal indicator
[18:30] <silverarrow> it works this time
[18:30] <silverarrow> in 12.04 it was always greyed out
[18:30] <silverarrow> now signal strength shows
[18:31] <silverarrow> pidgin doesn't crash, which probably never was a ppc issue
[18:33] <silverarrow> swas is excessive on this install
[18:33] <silverarrow> swap
[18:39] <silverarrow> wxl, coars pixeled desktop, the odd orange font, and nonworking installer
[18:40] <silverarrow> in other words, the same
[18:42] <wxl> so sounds like what i got
[18:42] <wxl> and the video=radeonfb: should fix it
[18:43] <njin> can someone confirm bug 1060396
[18:44] <wxl> njin: what checkbox? any? give me an example
[18:44] <njin> wxl, any
[18:45] <wxl> lxterminal → preferences → allow bold font looks fine
[18:45] <wxl> so, no, anti-confirm
[18:45] <wxl> ;)
[18:45] <njin> then it is expected working so, without checkmark inside ?
[18:46] <wxl> there's a checkmark inside that example i gave you
[18:47] <njin> ok, then is a bug in ubiquity
[18:47] <wxl> find another dialog with the same prob
[18:49] <njin> wxl, screenshot attached
[18:50] <wxl> njin: let me try this a different way. i am on an install right now. it's the most up to date 12.10 can be. i can check a bunch of dialogs if you like, but checking ubiquity isn't as easy.
[18:51] <wxl> ah, yes, that seems to be the new thing
[18:51] <wxl> i'm trying to think about what other dialogs i've seen it in but i have seen it
[18:51] <wxl> not sure if it's a bug or intended
[19:01]  * phillw goes and finds some superglue to keep silverarrow in the room :)
[19:01] <silverarrow> why are there no alsamixer?
[19:01] <wxl> no alsamixer?
[19:01] <silverarrow> yeah, glue might help
[19:01] <silverarrow> no
[19:01] <wxl> i got one here
[19:02] <silverarrow> can I have it?
[19:02]  * wxl hands it to silverarrow
[19:02] <silverarrow> thanks
[19:02] <wxl> wei8rd tho
[19:02] <wxl> alsamixer loads but apt-cache policy alsamixer doesn't work
[19:03] <silverarrow> I have " no such..."
[19:03] <silverarrow> ppc needs loads of small fixes
[19:03] <silverarrow> !!!!!!!!
[19:04] <wxl> duh
[19:04] <wxl> alsamixer is in package alsa-utils
[19:04] <silverarrow> I see
[19:04] <silverarrow> isn`t utils only the gui
[19:05] <phillw> is it missing from the seed?
[19:05] <silverarrow> for launch in menu I mean
[19:05] <silverarrow> phillw: it isn`t even planted you mean?
[19:05] <silverarrow> ...and it will not sprout until spring now
[19:06] <phillw> silverarrow: pretty much. if not planted, it will not appear on your install ISO, thus cannot grow on your system.
[19:06] <wxl> there is never a gui
[19:06] <wxl> the gui is yucky and no one likes it
[19:06] <silverarrow> this is what I get in terminal "cannot open mixer: No such file or directory"
[19:06] <wxl> alsamixer not mixer
[19:07] <silverarrow> no, I wrote in alsamixer
[19:07] <silverarrow> !!
[19:07] <silverarrow> that is the reply
[19:07] <wxl> dunno, that's strange
[19:07] <wxl> you think you got it bad. i gotta figure out how to make an xorg.conf file. :/
[19:10] <silverarrow> come to think of it, I  had the same trouble in 12.04
[19:11] <phillw> wxl: it should be detailed on the PPC-FAQ area.
[19:11] <wxl> phillw: it is
[19:12] <wxl> i'm trying to approach it with the "can do" attitude suggested XD
[19:12]  * wxl puts the bag he's hyperventilating into down.
[19:13] <phillw> he he :)
[19:13] <silverarrow> I have to reinstall the alsa packages
[19:16] <silverarrow> !"#¤%&?)
[19:19] <silverarrow> brb, restart
[19:23] <silverarrow> more weirdness, "this sound device does not have any controls"
[19:23] <silverarrow> ??
[19:23] <silverarrow> however, I have a sort of alsamixer in terminal now
[19:25] <phillw> wxl: there is one final release of kernel tomorrow evening (UTC). Please get as much info in for the nVidia one as possible as soon as possible. There will only then be a new kernel released for serious problems, we may end up with a release note and a fix for as soon as kernel freeze is removed.
[19:25] <silverarrow> oh why!!
[19:26] <phillw> silverarrow: we are on various freezes now. No 'new' stuff to be added. Only bug fixes.
[19:28] <phillw> there is FFe (Feature Freeze execption) request in for pcmanfm 1.1 to be added. So, things do not completely stop; you just need a darn good reason to back up an exception request.
[19:33] <wxl> phillw: i will have a report on nosplash asap but i can't promise i can both learn about xorg.confs and produce one all in one night
[19:33] <wxl> yikes :(
[19:35] <phillw> wxl: it's no big deal, just means we are unlikely to get a kernel fix for nvid via kernel. we also really do need something put together for the x-org people as a matter of urgency.
[19:36] <phillw> if there is a genuine bug, and a fix. then it will go in as a bug fix.
[19:36] <wxl> oops wrong channel OBVIOUSLY :)
[19:36] <wxl> oh jeez
[19:36] <wxl> nevermind that comment
[19:36] <phillw> bug fix <> feature freeze.
[19:36] <wxl> well, i've done what i can to encourage others to post on that bug. i myself reported my own experiences. i have a sneaking suspicion the ppc radeon cards may not be affected
[19:36] <wxl> (that bug=radeon/x bug)
[19:37] <phillw> I have read your emails with interest. As we discussed, it really does need someone with a PPC to take the lead here.
[19:38] <wxl> i'm trying, i'm trying!
[19:38] <phillw> Adam will give assistance, but does not have time to be POC for this.
[19:38] <phillw> wxl: you're doing great :)
[19:38] <wxl> ok good :)
[19:39] <phillw> he used to email me privately about stuff, so do make sure you and he keep in touch.
[19:39] <wxl> i guess for the final testing we could always tell teh nvidia folks to stop testing (i think that's johnathan and i) and that may help keep ppc released
[19:39] <phillw> I'd appreciate being cc'd so I have some idea of what is going on :D
[19:39] <wxl> adam = ojordan?
[19:40] <phillw> yes
[19:40] <wxl> k
[19:40] <wxl> he's the one pushing me to do the xorg.conf XD
[19:40] <phillw> indeed!
[19:40] <phillw> that is fixable, he reckons, provided we can give a good case to the x-org team.
[19:41] <wxl> well an xorg.conf should be an easy fix
[19:41] <phillw> It is why I was pulling my hair out at people emailing up their own 'unique' solutions. PPC needs a generic one that will work :)
[19:41] <wxl> meaning if we have it and we know it works, implementing it is super trivial
[19:42] <phillw> indeed :)
[19:43] <wxl> so pray for me
[19:43] <wxl> and johnathan
[19:43] <wxl> he has the EXACT SAME CARD
[19:45] <phillw> jonathan is the only person testing server. This needs to change at the RC stage. IIRC, I have one edit only to make to the test case. I have clearance to get it edited, so I'll get it done before the RC testing takes place.
[19:50] <wxl> x is part of userinterface freeze (long past)?
[19:52] <wxl> phillw: ↑
[19:53] <phillw> wxl: yup, but bug-fix <> Feature Freeze :)
[19:53] <wxl> which is also long overdue
[19:56] <phillw> If PPC can give an over-ridingly simple bug fix to a regression, then I do have a chance of getting it done. For this, PPC need to concentrate all issues of X to the proposed solution. If it gets thumbs up from the testers it can be presented as a fix to a regression.
[19:56] <phillw> the Nvidia seems a bit of a red herring, as some have it & others do not. That is one for further investigation.
[19:57] <wxl> well greg's comment is on an amd64 machine too
[19:57] <silverarrow> what is regression exactly ?
[19:57] <wxl> silverarrow: bug that was fixed, now showing symptoms again
[19:58] <silverarrow> @aha
[19:58] <meetingology> silverarrow: Error: "aha" is not a valid command.
[19:58] <silverarrow> ?@
[19:58] <phillw> silverarrow: it is when a change is to fix a bug that then goes and breaks breaks something else
[19:58] <phillw> -breaks
[19:58] <silverarrow> hmm, interesting
[19:58] <silverarrow> lubuntu avalanche
[19:59] <silverarrow> swooooooooooooosh
[19:59] <phillw> we had it after A3 for PPC :/
[19:59] <silverarrow> horror
[19:59] <phillw> things were going horribly well :D
[20:00] <silverarrow> lol
[20:00] <silverarrow> why would I have no sound ?
[20:00] <silverarrow> I need a different fix than the ones listed in faq
[20:00] <silverarrow> what worked in 12.04 do not anymore
[20:01] <wxl> silverarrow: i suggest powerpcfaq
[20:01] <silverarrow> which is where I am reading
[20:01] <wxl> https://wiki.ubuntu.com/PowerPCFAQ#Why_do_I_have_no_sound.3F
[20:03] <balloons> you guys look like your having fun with ppc!
[20:04] <wxl> hahahah
[20:04]  * wxl picks up bag to hyperventilate into again
[20:04] <wxl> we're pushing hard tho
[20:05] <silverarrow> however it is probably the G4 sound card issue
[20:05] <phillw> hi balloons, sorry to kidnap -testing (again).. It seemed quiet at the time and it is testing topic :D
[20:05] <balloons> no, it's good
[20:05] <balloons> I like see it
[20:05] <balloons> no one like an empty channel
[20:05] <silverarrow> I don`t  understand the blacklisting !"#¤%&)?#
[20:06] <silverarrow> I used this command last time sudo rm /etc/modprobe.d/blacklist.local.conf
[20:07] <silverarrow> 12.04 I mean
[20:07] <silverarrow> now I get rm: cannot remove `/etc/modprobe.d/blacklist.local.conf': No such file or directory
[20:07] <wxl> suggestion: if you don't know what a command does, don't do it
[20:07] <silverarrow> hey, I would not do many commands then
[20:08] <silverarrow> I copy and paste a lot
[20:08] <wxl> no you would learn about them :)
[20:08] <wxl> also did you try to locate the file elsewhere? or search around in the directories above?
[20:08] <silverarrow> yeah, preferably
[20:08] <silverarrow> no
[20:09] <wxl> well there ya go
[20:09] <wxl> although i don't think you'll find anything
[20:11] <njin> phillw, I haven't got nouveau bug with Lubuntu, but I have it with Ubuntu ;-P
[20:12] <phillw> njin: can you pop a comment onto the bug report, please?
[20:12] <njin> phillw, wich ine ?
[20:13] <phillw> njin: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518
[20:13] <njin> one?
[20:14] <wxl> i'd also look through the other conf files there too silverarrow
[20:14] <silverarrow> ohhhh,
[20:14] <phillw> I think it is needed that people let the kernel team know which graphics cards they are using. I must say that if you are having a problem with Ubuntu and not Lubuntu, then what you are seeing is NOT kernel related.
[20:14] <silverarrow> horror
[20:14] <wxl> on that subject, to let them know about your card, provide the results of "lspci | grep VGA," njin
[20:18] <silverarrow> wxl, do you know what the ppc faq fix is about for the G4 audio card?
[20:19] <wxl> silverarrow: haven't tried it, no
[20:19] <silverarrow> I am in modprobe.d but cannot figure out how to add what they list
[20:19] <silverarrow> maybe I can ask someone on the mailing list or forum
[20:19] <silverarrow> there are a few with G4s
[20:20] <wxl> maybe just file a bug report and someone will point you in the right direction
[20:22] <njin> wlx, phillw, sorry it is too late for me, i've opened a bug report, bug 1054689 that doesn't sound similar, my card is geforce 6100
[20:22] <silverarrow> yeah, bugreports can be really cumbersome
[20:22] <njin> today i haven't seen the bug in Lub untu.
[20:22] <njin> tomorrow i try in ubuntu
[20:22] <wxl> silverarrow: that attitude keeps development from happening
[20:22] <njin> se you tomorrow
[20:23] <phillw> njin: check to see if it is related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518 if so, just mark it as duplicate and transfer information onto that bug.
[20:24] <silverarrow> ey
[20:24] <njin> ok, but tomorow, i've to verify the Ubuntu build
[20:25] <njin> nope, mine is affextong the installed system too
[20:25] <njin> affecting
[20:25] <njin> goodnight
[20:26] <silverarrow> bug launcher does not recogize pacakge name
[20:27] <silverarrow> shouldn`t alsa-utils be enought ?
[20:29] <silverarrow> oh just a "-" too much
[20:30] <phillw> he he
[20:52] <phillw> wxl: you views on the latest email would be appreciated :)
[21:01] <wxl> done
[21:01] <wxl> too bad adam has no time. he's clearly got a lot of knowledge
[21:01] <wxl> i wish i was at the level
[21:20] <wxl> anyone know a general place i can find info about graphics in general? like it doesn't make sense to me that radeonfb uses fbdev and not the radeon xorg driver. i hate to bug adaam with my stupidity :)
[22:23] <Noskcaj> is test 11 on http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/24728/testcases/1451/results a typo or just copy/paste?
[23:12] <phillw> Noskcaj: as in an error on http://iso.qa.ubuntu.com/qatracker/testcases/1451/info
[23:12] <Noskcaj> yes phillw
[23:13] <phillw> Noskcaj: I've not read the test case (was busy) where do you see the typo / error? I can then go through the logic of the test case (I do not hold them all in my little brain :) )
[23:14] <Noskcaj> i quote "11. If there is only one hard disk, skip to step 10 (On the 'Where are you?' screen...). Otherwise, on the 'Installation type' screen verify that the drive selected on the Select drive list corresponds to the drive on the chart (e.g /dev/sda) Selected drive is displayed on the chart
[23:15] <Noskcaj> as this is after the test referenced it is an error the test it should reference is test 14
[23:15] <phillw> Noskcaj: do you have a correct phrase?
[23:15] <Noskcaj> just change 10 to 14
[23:15] <Noskcaj> i think
[23:16] <phillw> what's with "I think"?
[23:16] <phillw> we have tried to get the old test cases moved, a lot of these errors have been there for years!
[23:17] <phillw> Noskcaj: please have a read through it, and let me or balloons know of any gremlins in the instructions. Thanks.
[23:18] <Noskcaj> ok
[23:19] <Noskcaj> the i think was because i cant see that part of the testcase because i only have one hard drive
[23:21] <phillw> Noskcaj: ha ha! now I do see it, and you are 100% correct.
[23:22] <phillw> forgive us, we were doing mass conversions to the new system. Typos / errors in the actual test cases we rely on good people such as you to alert us to.
[23:22] <Noskcaj> is that the dd dt or just the added testcases?
[23:25] <phillw> Noskcaj: can you refresh your test case to ensure the change has gone through?
[23:26] <phillw> Noskcaj: we pulled in the test cases that were on the wiki based system, several coversions to CSS have been done, but we did inherit any errors from the legacy test cases. I've found a few, others have also.
[23:27] <Noskcaj> phillw: it has changed
[23:27] <phillw> bottom line... if you see a gremlin, please do let myself or balloons know. We will jump on them really quickly!
[23:28] <phillw> Noskcaj: is it now correct for your order of testing?
[23:28] <Noskcaj> yes
[23:29] <phillw> Noskcaj: great, thank you for taking the time to point it out. It means that others following it will not have "WHAT?!!" moments (you know what I mean) :)
[23:30] <Noskcaj> yep
[23:57] <balloons> phillw, Noskcajd did we fix the typo
[23:57] <balloons> ?
[23:59] <phillw> balloons: immediatly,