=== Ursinha-afk is now known as Ursinha [02:15] has anyone looked into why 13.04 isnt sleeping correctly? === Guest49957 is now known as jrib === blkperl_ is now known as blkperl [07:06] which pkg says 'The program '*' is currently not installed. You can install it by typing:' ? === julius is now known as Guest731 [12:22] hi i recently joined bussquad but ofc im not able to set bugs from eol versions to wont fix. what am i supposed to do? [12:27] Guest731: only bug control member can set bugs to wont fix (and I'm only a bug squad member) [12:31] so shall i ccontactfor example https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/946742 [12:31] Launchpad bug 946742 in intel-vaapi-driver (Ubuntu) "Shotwell crashes on start with gstreamer0.10-vaapi" [Undecided,Confirmed] [12:32] shall i try to contacct the assignee? or a specific person of bug-contol? [12:34] Guest731: did you add a comment to that? [12:34] yes [12:34] the last one? [12:35] y and several before [12:36] Guest731: OK, I think you're wrong to say that 12.04.1 is out of support [12:40] Guest731: If you can point me to somewhere that does say that I'd be interested [12:40] well on https://wiki.ubuntu.com/Releases its just empty. only 12.04.2 has an offical end of life, while 12.04.0/1 dont [12:40] but 12.04.1 is not in the EoL section [12:41] my understanding is that 12.04 is supported for the whole period [12:43] also, I generally wouldn't want to change a bug to won't fix/invalid if it's assigned [12:48] even something like that https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/303404 five years old and filed agianst 8.10? and the upstream bug linked says Status: RESOLVED Resolution: OBSOLETE [12:48] Launchpad bug 303404 in rhythmbox (Ubuntu) "last.fm: selecting multiple songs produces a download error" [Low,Triaged] [12:51] hmm, that I might be tempted by; it's not had any activity for a long time and it's assigned to a group rather than one person; I'd probably set it to incomplete and ask if anyone can still reporduce [12:56] why dont you set it to wont fix and ask wheter it stil reproducable. so it will vanish from the default bug list view an not distract from important bugs anymore. the bu submitter and all subcribed will get an email and if they wish to ropen it again they can comment or sent a mail. otherwise you have to visit the bug again after some time. although chances are 0.000001 percent that someone will respond [12:57] for which, the 1st or the 2nd one? [12:59] the second one. the old filed against 8.10 [13:00] because 'incomplete' times out and expires after a few weeks automatically; which is really what you're after - you want to ask a question 'does anyone still see this?' and if no one replies positively then it'll expire [13:01] it's incomplete if no one answers your question [13:03] Guest731: It's not too rare to end up with people filing bugs against one release, it never getting fixed, it expiring as EoL but it never being fixed, so they submit another bug and the same thing happens - 5 years later it's still not fixed [13:04] ok you mean incomplete because theres no up to date descripton. well my perception was that incomplete means wheter was at least once a proper description. [13:04] no, incomplete can be because you need some more information - whether that's description or the answer to a question [13:04] i think that solves my problems [19:13] Supervisors: I'd like to nominate bug 1179281 for a raring SRU [19:13] Launchpad bug 1179281 in s3ql (Ubuntu) "Data corruption with eglibc 2.17" [Undecided,New] https://launchpad.net/bugs/1179281 [19:17] done === Jikan is now known as Jikai [19:20] Nikratio: it would be good if s3ql gets autopkgtest so that this type of issue can be caught without rebuild [19:20] ubuntu runs the tests on each first level dependency change: https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/ [19:25] jtaylor_: will look into it, thanks for the link === Jikai is now known as Jikan === jtaylor_ is now known as jtaylor === thomi_ is now known as thomi