[01:19] jtaylor: to the package [01:20] * hggdh goes AFK again === JackyAlcine is now known as JackyAlcine2 === JackyAlcine2 is now known as JackyAlcine_ === JackyAlcine_ is now known as EvilJackyAlcine === EvilJackyAlcine is now known as JackyAlcine === lenios__ is now known as lenios_ === seb128_ is now known as seb128 [14:00] for packages from multiverse "sponsors" are responsable for fixes/reviews?? [14:00] https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/851725 [14:01] Launchpad bug 851725 in flashplugin-nonfree (Ubuntu) "flashplugin-downloader is suggesting msttcorefonts but the package is called ttf-mscorefonts-installer (affects: 1) (heat: 8)" [Undecided,New] [14:03] and because of that i guess they want a debdiff instead of my normal patch [14:03] ah there is a patch-pilot on devel [14:14] what to do when i THINK a bug is an upstream-bug? https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/887442 [14:14] Launchpad bug 887442 in evolution (Ubuntu) "evolution is using the wrong color to mark missspelled words. yellow instead of red (affects: 1) (heat: 6)" [Undecided,New] [14:15] iceroot - what reason do you have to think it's *not* an upstream bug? [14:15] brendand: because maybe ubuntu patched something [14:16] iceroot: for the evo bug: open upstream, and chat with the evo developers on #evolution on irc.gimp.net [14:16] hggdh: thank you, i will do so [14:16] iceroot: you can always check, looking at the bzr branch of the package [14:17] iceroot - 95% chance that unless you can think of a reason why it might be an ubuntu specific problem then it is in fact upstream [14:17] hggdh: brendand u just was not sure what is the correct way to report such bugs because its affecting ubuntu and maybe vanilla-evolution [14:18] s/u/i/ [14:20] of course a great way to make sure if to have e.g. debian on a vm and install the vanilla packages there to check. [14:21] brendand: but maybe debian patched something too :) [14:21] iceroot: you will usually need to look at the source package. There are (basically) two types of "Ubuntu" bugs: packaging issues, and patching issues [14:22] for patching, just look at the ./debian/patches directory of the source package [14:23] hggdh: not always easy for a normal user to see what has been patched, even when looking at the patch-file [14:23] hggdh: i will create a upstream-bug, link the launchpad-bug against it and will see what is happening then [14:24] it's a duplicate of bug #829351 [14:24] Launchpad bug 829351 in evolution (Ubuntu Oneiric) (and 1 other project) "Misspelled words are highlighted in yellow instead of red (affects: 4) (dups: 1) (heat: 19)" [Low,Confirmed] https://launchpad.net/bugs/829351 [14:24] iceroot: well, I did not suggest it would be easy ;-). But, then, a so-called "normal user" would not even know of upstreams :-) [14:25] seb128: thank you, dear sir [14:34] hggdh: ok its upstream and there is already a patch. http://git.gnome.org/browse/evolution/commit/?id=d4571114e8b8949922213ac23825075880e59231 so what are the next steps? [14:36] iceroot - link it upstream and the LP bug will get updated as the upstream one progresses [14:36] brendand: done [14:38] thanks for the help === yofel_ is now known as yofel [15:21] what is the correct tag if something is fixed upstream? [15:43] iceroot: no chances on our bug -- if you linked the LP bug to upstream, Launchpad will automatically update the status of the upstream bug [15:47] hggdh: ok [16:03] mvo: available? [16:07] mvo: when you get a chance, have a look at bug 878719. Not sure what the culprit is. Even a clean install of the update-manager and its config files didnt help the issue. [16:07] Launchpad bug 878719 in update-manager (Ubuntu) "Update manager comes to a contineous "processing" status (with the rotating cursor pointer) when the "Install updates" button is pressed (affects: 2) (heat: 14)" [Undecided,Incomplete] https://launchpad.net/bugs/878719 [16:41] RedSingularity: ohhh, so the bug in comment #4 is a bug in u-m that happend during the porting. should only affect people who do not have aptdaemon installed [17:13] what is happening to bugs which are only affecting a EOL-version of ubuntu? are they closed as "invalid"? https://bugs.launchpad.net/ubuntu/+source/lxde-common/+bug/309983 [17:13] Launchpad bug 309983 in lxde-common (Ubuntu) "icon at LXDE panel not appearing fine (affects: 2) (heat: 8)" [Undecided,New] [17:13] no they should be tested in the latest release of Ubuntu if the package is still available [17:14] bdmurray: firefox-3.0 is no longer available and the bug does not affect higher version of lubuntu and firefox [17:14] then won't fix sounds like the correct status [17:15] bdmurray: ok [17:15] bdmurray: seems i can not change the state to "wont fix" [17:15] if you can not set that status, add a comment saying why it should be won't fix and let me know and I'll set the right status [17:16] bdmurray: ok [17:18] bdmurray: done https://bugs.launchpad.net/ubuntu/+source/lxde-common/+bug/309983 [17:18] Launchpad bug 309983 in lxde-common (Ubuntu) "icon at LXDE panel not appearing fine (affects: 2) (heat: 8)" [Undecided,New] [17:19] iceroot: more information about what supported ubuntu version you tested this with would be helpful for people in the future [17:19] iceroot: rather than having to try and think about what releases were supported in 2011-11 ... [17:20] bdmurray: done [17:21] iceroot: wow, thanks for testing with all of those releases! I've set the task to Won't Fix. [17:21] bdmurray: yes, i made some vms in the last month for better support on creating bugs (especially to see what versions are affected from bugs i created) [17:22] "bugs I created"? [17:23] bdmurray: opened :) [17:23] got it === bdmurray changed the topic of #ubuntu-bugs to: Ubuntu Bug Squad - next meeting 12/08/11 | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu === JackyAlcine is now known as graviti2011 === graviti2011 is now known as JackyAlcine [17:26] https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/851725 is the patch from me the correct way of fixing this issue? do i have to put someone on cc on that bug? for universe i know i have to use debdiff and ubuntu-sponsors. what about multiverse? [17:26] Launchpad bug 851725 in flashplugin-nonfree (Ubuntu) "flashplugin-downloader is suggesting msttcorefonts but the package is called ttf-mscorefonts-installer (affects: 1) (heat: 8)" [Undecided,New] [17:27] iceroot: the bug bot that commented on that bug has put it in the right queue [17:28] bdmurray: ok i was just wondering because its 2 month old (i know its not an important issue) [17:29] so i was not sure about "ubuntu-sponsors" "debdiff" and "multiverse" [17:33] iceroot: having a patch instead of a debdiff creates slightly more work for a developer to upload the package so if it were a debdiff it'd go to a different queue and may get fixed faster [17:34] bdmurray: ah i though a debdiff would be more work because a patch can placed in debian/patches and works on every new version and a debdiff is only working against the latest source-package [17:38] iceroot: because its a change to the control file it wouldn't go into debian/patches [17:38] iceroot: and this does not qualify for an SRU so it would only be fixed in the development release (precise) [17:39] bdmurray: why should it be a SRU? [17:40] if i understand SRU correctly its bringing new versions of a package in an existing release (like a major update) [17:40] iceroot: I was saying it shouldn't be released in an update for a stable release of Ubuntu [18:42] iceroot: no, new versions in stable releases is generically known as a backport [18:43] SRUs are usually much more contained, and maintain the same version [18:52] hehe so as long as we're talking SRUs, are string changes SRUable? I have an updated string in trunk and would like that change to make it into 11.10, will it be accepted? [19:04] if it is important enough, yes [19:04] if it is just a cosmetic fix, no new and important information being conveyed, chances are it will be refused [19:05] hggdh: we refer to "sound preferences" when it should be "sound settings" [19:06] roadmr: it might be enough, since we would then be directing the user to an incorrect place [19:06] worth to bite the bullet, and try [19:07] hggdh: ok, sounds reasonable, I'll try that then, thanks :) [19:07] It's all in the motivation [19:08] ersi: it's just to fix confusing strings (two of them) - I guess it'll be up to the SRU reviewer to decide whether it's worthwhile [19:09] It's still all in the motivation :-) [21:37] Hi yofel..... apparently Gstreamer's phonon backend is broken [21:37] should I report this or do we have a open bug ? [21:38] Hai [21:38] hi [21:49] bkerensa: I don't know of one offhand - phonon-backend-gstreamer works fine for me [21:49] yofel: Well one of the devs from #tomahawk said you were aware that phonon-backend-gstreamer is bugging [21:49] * bkerensa cant get it to work with Tomahawk but the VLC phonon works fine [21:50] let's move there actually [21:50] ok will do