/srv/irclogs.ubuntu.com/2009/12/12/#ubuntu-bugs.txt

nano4everCan anyone look at a debdiff I made for the upgrade Bug #206862 ??01:35
ubot4Launchpad bug 206862 in xsensors "New upstream version (0.60) available" [Wishlist,New] https://launchpad.net/bugs/20686201:35
hggdhnano4ever: it is a patch, not a debdiff01:38
dtchennano4ever: is there any other possible value for num?01:39
dtchenusing a switch/case there seems odd if it can only be useful for 101:40
dtchenand, it's missing all the Debian infrastructure01:40
nano4everoh sorry i'll upload it now01:40
dtchen(as hggdh alluded to)01:40
hggdhyeah, an if would be enough. And I, particularly, don't like a return in the middle of a switch01:42
nano4everhggdh: alright it's uploaded01:42
hggdhnano4ever: why are you patching the autoconf files?01:47
hggdhin other words, is 0.61 the new upstream release?01:48
hggdhooooh, we are still at 0.50 in Lucid01:51
nano4everwell the patch is from here https://lists.ubuntu.com/archives/ubuntu-motu/2008-September/004711.html01:51
nano4everthe author posted the patch but with no official change in version number01:51
hggdhthank you01:52
nano4everI contacted him and he said that he would post some updates to xsensors but he hasn't done it yet...01:52
hggdhit would probably be a better idea to propose a new source upstream version, instead of patch 0.50 to 0.60 to 0.6101:53
hggdhthe debdiff is rather big as a result01:53
nano4everah ok01:53
nano4everso what's the process for making such a proposal?01:54
hggdhand -- usually -- running autoconf on package build is not viewed as a good option (I do not really know if it is run, or if the patches for the autoconf are just for completeness)01:54
hggdhnano4ever: you could download the new upstream and add your patches there01:55
hggdhthis would make the debdiff much smaller, and there is no sense in carrying such a large patch if the new upstream code has it all there (except for your patch)01:55
nano4everi just followed the directions here for the update .. https://wiki.ubuntu.com/PackagingGuide/Complete#Updating an Ubuntu Package01:56
nano4everso are you saying that I should make a new package from upstream, then apply the author's patch as an update?01:56
hggdhyes01:57
hggdhyou would have to download the source from upstream (hopefully they have a distribution tarball)01:57
hggdhbecause this would make life much more simpler01:58
hggdhthis is, in fact, what the instructions you pointed try to say01:58
hggdh"Get the new source. Usually you would look up where the old version was downloaded from (check debian/copyright) and use that source. But again, since this is a prepared example:01:58
hggdhso we would upgrade from version 0.50 to 0.6x (whatever it is), plus the additional patch(es)01:59
hggdhbut the *base* version would be 0.6x01:59
hggdhnano4ever: BTW -- thank you for working on this. I understand you may be a bit frustrated now, though02:00
hggdhnano4ever: did I explain it OK?02:00
nano4everi'm just a bit confused. I did start on the link i gave then I skipped to "Creating a debdiff"02:01
nano4everI dled the the newsource02:01
hggdhyou were on the right track, up to diff-ing from 0.50 to 0.60 to 0.61 to you patch02:02
hggdhthis is where you took a, er, misguided turn02:02
nano4everso if I just follow the "Updating an Ubuntu Package" section and upload the dsc file, that should be enough?02:03
hggdhbasically, we are -- right now -- at 0.50 (perhaps plus some patches). The new upstream is at 0.6x. So -- we upgrade the *whole* package to 0.6x02:03
hggdhwhich is to say, we download 0.6x, and base a new package version on it02:03
hggdhyou would need the dsc plus (most probably) a diff02:04
hggdhbecause you will (at least) have to update the ./debian/* files02:04
nano4everwould the diff be from 0.50 to 0.60?02:05
hggdhno. The diff would be from the *current* released upstream02:05
hggdhplustd whatever patches necessary02:05
hggdh0.50 is dead02:05
nano4everok, so what I'm thinking is copy over the .50 debian directory to .60, update those files, then make a .dsc and diff from the new .60 and .60.orig , is that about right?02:06
nano4everand then after .60 is approved, patch to 0.60-0ubuntu2 with the coretemp patch..02:07
hggdhin this case, it is pretty much a *new* version, so there is no debdiff -- you will be uploading a new .orig, plus the debian packaging pieces02:07
nigel_nbhggdh: I'm going to get that ppa wiki done today :)02:08
hggdhfor the last question: this, I am not sure. I personally would try to put it all together in one go, but MOTU may want different02:09
hggdhnano4ever: also, the best channel for packaging Universe is the #ubuntu-motu one02:10
hggdhnigel_nb: cool, thanks02:10
hggdhnano4ever: also, please remember the package should be built for Lucid, not Karmic02:11
nano4everhggdh: alright thanks for the tips! also, I tried #ubuntu-motu,but got no response..02:11
hggdhnano4ever: heh. Ask, and fill yourself of patience ;-)02:12
hggdhthey may delay to answer, but usually they do. Also, this is Friday night/Saturday morning on most places02:12
nano4everah makes sense02:13
hggdhnano4ever: again, thank you for your work on this. We *do* appreciate02:13
nano4everthanks for the thanks :P02:15
nano4everjust trying to give back02:15
hggdhnano4ever: just one more point: we usually try very hard to use the upstream distro tarball without changes *in* it, and addtional patches separate in ./debian/patches02:15
hggdhany patches we carry create a 'delta' from upstream (i.e., a local difference). We try to maintain this delta to a minimum02:15
nano4evergotcha, i'll keep it that in mind02:16
hggdhnano4ever: this is how I started in Ubuntu ;-) giving back what I was taking02:16
hggdhdtchen: welcome back as an official developer :-)02:21
nigel_nbhggdh: how do I know if a bug is part of publically announced testing initiative of an ubuntu team?02:29
hggdhwell, if it was publicly announced...02:31
hggdhbug #?02:31
nigel_nbhggdh: making the wiki edits02:35
nigel_nbor creation02:35
hggdhoh, OK02:35
hggdhthen -- we (as triagers) would have to receive a notice. This is actually a good question... perhaps we need a common place for all officially endorsed test packages as noted in02:37
nigel_nbyea a wiki02:37
nigel_nbI can offer to main a static list, if I'm able to get the announcements02:38
hggdhthis is something to be formalised, I agree02:41
nigel_nbpart of the agenda for the next meeting then02:42
hggdhyes -- and it will have to be discussed with the other groups02:43
hggdhmeanwhile, we might go on, and assume it will be there02:43
nigel_nbyep, including the devs and motu is my best guess02:44
hggdhyes02:45
nigel_nbare there any such programs now?02:45
nigel_nbthat have called for testing?02:45
nigel_nbhggdh: wifi manager in gnome is which package? gnome-net-tools?02:52
nigel_nbgnome-nettools (spelled wrong earlier)02:53
hggdhI do not know (yet). What is the name of the file?02:55
nigel_nbfile?02:55
nigel_nbthe entire bug report consists of "The network manager is unable to connect to hidden wireless network."02:56
nigel_nbI need to change the package and ask for more info02:56
hggdhoh02:56
hggdhnetwork-manager02:56
hggdhand network-manager-gnome02:57
hggdhbut it is probably network-manager that cannot find the AP02:58
nigel_nbokay, thank you :)02:59
=== asac_ is now known as asac
=== asac_ is now known as asac
=== etali1 is now known as etali
=== etali1 is now known as etali
=== mac_v_ is now known as mac_v
=== etali1 is now known as etali
nperry!info pidgin16:05
ubot4nperry: pidgin (source: pidgin): graphical multi-protocol instant messaging client for X. In component main, is optional. Version 1:2.6.2-1ubuntu7 (karmic), package size 562 kB, installed size 1784 kB16:05
nperrypackages.ubuntu.com is down hrrrm16:05
hggdhsometimes it happens. It is, IIRC, a volunteer service16:19
=== yoasif_ is now known as yoasif
=== mac_v_ is now known as mac_v
=== etali1 is now known as etali
YosI just started having this problem for the first time: My computer is booting up into low graphics mode and I cannot change visual effects to normal or extra18:55
YosIs this a bug?  If so, how to report it properly18:55
etaliYos, this channel is for people who are triaging bugs, rather than for support.  You'd probably get a quicker response regarding solving your problem in the #ubuntu channel18:57
etaliIf you want to report it as a bug, you can find help at https://help.ubuntu.com/community/ReportingBugs18:58
YosOk, thanks18:58
etaliI hope you manage to get it sorted!18:59
=== _stink__ is now known as _stink_
awardleCan bugs in evolution be upstreamed?19:53
nigel_nbawardle: yes, it has to be upstreamed *if* it is upstream19:54
awardlewhere to19:54
hggdhand, for Evolution, they should19:54
hggdhhttp://bugzilla.gnome.org19:54
nigel_nbhggdh: upstream gnome down for you?19:55
nigel_nbI've been trying for some time19:55
hggdhwill check19:55
hggdhhum19:55
hggdhnot looking good19:55
awardlebugzilla.gnome.org seems to be down19:56
nigel_nbunfortunately, true :(19:56
hggdhyes. I just asked about it on their bug channel19:57
hggdhnow we wait, Saturday and all of that19:57
nigel_nbyea, plus holiday season19:57
awardleCould someone set bug 495936 to low19:58
ubot4Launchpad bug 495936 in evolution "Feature request: better indication of signed and/or encrypted email" [Undecided,Confirmed] https://launchpad.net/bugs/49593619:58
nperryRight my first request for this evening, time to eat my tea19:58
hggdhawardle: I actually marked it WishList. Thank you20:00
hggdhnperry: you *eat* tea?20:01
nigel_nbnperry: was about to ask, but hggdh already asked20:01
hggdhjust curious. Different people, different mores, etc20:02
nigel_nbprobably eating the tea cup too?20:02
awardletea in England can also mean dinner20:04
nigel_nbawardle: dinner or supper?20:04
hggdhah20:04
nperryhggdh: tea aka dinner20:04
nigel_nbearly dinner then20:05
nperryits 8pm20:05
hggdhwell, my grandmother-in-law used to ask us if we wanted a lemonade of coke, or orange, or whatever20:05
nperryso late really20:05
hggdhindeed. teatime is gone20:06
hggdhbrb. Lunch time at my TZ.20:06
nperryWow that was nice back to my learning to triage :)20:17
hggdhnperry: just ask on any doubt, and we will try to answer20:39
hggdhOK. bugzilla.gnome.org is down for the weekend (I *should* have read the annoucement...)20:41
hggdhfor all, courtesy of the extremely nice bugmeister for gnme: http://permalink.gmane.org/gmane.comp.gnome.devel.announce/6720:46
nigel_nboh great, I was hoping to work on the git.gnome this weekend, so thats gone now20:47
hggdh:-)20:47
nperryhggdh: This evening theres alot of bugs from email, for packages syncs for example 495994 - the right people have been subscribed, do we need to confirm or marked as triaged?21:01
nperrybug 495994 **21:01
ubot4Launchpad bug 495994 in libhamcrest-java "Sync libhamcrest-java 1.1-4 (main) from Debian testing (main)" [Wishlist,New] https://launchpad.net/bugs/49599421:01
hggdhlooking. But usually, workflow request (sync/merge, and others) are outside triaging scope21:02
hggdhin this case, even more due to the OR -- he knows what has to be done21:03
hggdhso, no, do not touch them21:03
nperryOk, just had to double check if New was the right status21:03
nperryThanks :)21:04
hggdhwelcome21:04
nigel_nbhggdh: frustrating to triage today with no upstream :(21:05
=== yofel_ is now known as yofel
hggdhI know. But we can hope it will back earlier (this is their intention)21:06
nigel_nbyea21:08
nigel_nbI'm not triaging today, cant leave tasks undone, I'd rather skip 2 days and go all out from monday21:09
nperryHummm debian bug tracker playing up21:10
nperryAh working now :)21:11
nperryhggdh: fsys state-tarfile returned error exit 2 -- Could this be a bad download?21:18
hggdhnperry: could, but give me a pastebin21:18
nperrybug 49599221:19
ubot4Launchpad bug 495992 in kdebase-runtime "package kde-icons-oxygen 4:4.2.2-0ubuntu1 failed to install/upgrade: subprocess dpkg-deb - fsys state-tarfile returned error exit 2" [Undecided,New] https://launchpad.net/bugs/49599221:19
nperryTerminallog - Never seen the error before, but just to be sure before i convert to question and solve issue21:19
=== markus_ is now known as thekorn
yofelhm, what was 'broken pipe' again?21:21
hggdhnperry: does not sound like bad download21:21
hggdhyofel: a subprocess had a pipe to another subprocess, and this pipe vanished (one of the subp died, in this case)21:22
yofelhggdh: ah yes, thx21:22
hggdhnperry: you can check, nevertheless, by downloading the package to a temp dir, then manually running 'dpkg-deb --fsys-tarfile|tar -tv'21:26
hggdher21:26
hggdhdpkg-deb --fsys-tarfile <package> | tar -tv21:26
nperrymeh packages.ubuntu.com is down :/21:27
hggdhnperry: you can drill down to the specific package from here: https://bugs.edge.launchpad.net/ubuntu/+source/kdebase-runtime21:28
hggdhselect the Overview link at the headers, and then go to the correct distro version21:29
hggdhfor example, I ended up here: https://edge.launchpad.net/~ubuntu-security/+archive/ppa/+build/138810521:30
hggdhoops. Wrong drill down, the OR package is at 0ubuntu1, the one I am showing is at 0ubuntu1-121:31
nperryThats odd, why isnt downloading OR 1-121:33
hggdhno, it is, the bug title is wrong21:35
hggdhlook at the description, and at the end of the log (I also based myself on the title)21:36
hggdhdpkg: erro processando /var/cache/apt/archives/kde-icons-oxygen_4%3a4.2.2-0ubuntu1.1_all.deb (--unpack):21:37
hggdhhum. pt_BR, BTW21:37
nperryIndeed updated that, else i'll forget :)21:39
nperryRight the .deb seems ok21:40
LaibschHi21:52
LaibschHow do I search for bugs that are marked as fixed in the current development release but nominated for hardy or karmic?21:52
hggdhLaibsch: good question, let me try to find out21:53
Laibschhttps://bugs.launchpad.net/ubuntu/hardy/+nominations21:55
hggdhheh, there you go21:55
Laibschcompletely non-obivous, but google helps21:55
Laibschand unfortunately, that includes yet to be fixed bugs21:56
nperryhggdh: I believe bug 495724 is ready to be set as triaged with importance medium21:57
ubot4Launchpad bug 495724 in b43-fwcutter "Broadcom 4306( b43-fwcutter) Wireless can't connect to Access Points WEP/WPA/Unsecure." [Undecided,Incomplete] https://launchpad.net/bugs/49572421:57
nperrynm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed - handsake doesn't seem to be happening21:57
nperrySo I think its a network card/driver related problem - as ndiswrapper driver fixes issue21:58
hggdhLaibsch: trying "advanced search" under +nominations should get there -- then select fix released/committed21:59
LaibschJust did that21:59
LaibschGot a timeout error a couple of times21:59
Laibschbut it seems to be working now21:59
hggdh<sigh/>21:59
hggdhah, OK21:59
Laibschwho can change the status for nominations?22:01
LaibschI think bug 129407 can be rejected as invalid for example22:02
ubot4Launchpad bug 129407 in linux-ubuntu-modules-2.6.22 "r818x.ko missing in linux-ubuntu-modules-2.6.22-8-generic" [Medium,Fix released] https://launchpad.net/bugs/12940722:02
hggdhLaibsch: for nominations, only the maintainers can refuse it22:02
LaibschI see22:02
Laibschbut wait22:03
LaibschUbuntu has no Maintainer per se22:03
hggdhnperry: it would be good to also have the dmesg, and a 'lspci' output22:03
LaibschIt's a team effort22:03
hggdhLaibsch: getting there22:03
hggdhlinux *does* have maintainers22:04
hggdh(I mean the package)22:04
hggdhthe kernel team, specifically22:05
nperryhggdh: Full dmesg?22:06
hggdhnperry: yes, better more than less data22:07
=== Flare183_ is now known as Flare183
Laibschwho would be capable of closing the hardy task for bug 178289?22:15
ubot4Launchpad bug 178289 in ubuntu "Absolutely no keyboard input on fresh hardy alpha 2 installation." [Undecided,Fix released] https://launchpad.net/bugs/17828922:15
LaibschI'm a member of "Ubuntu bugs", yet I don't seem to have the power to do it22:15
nigel_nbLaibsch: I believe only Ubuntu Drivers can close that task22:18
nperryhggdh: Is there an upstream for b43-fwcutter22:18
hggdhLaibsch: first of all, most of the times we see a bug against Ubuntu, this is because the OR did not know which package to set it against22:18
Laibsch?22:19
Laibschhggdh: Were you really talking to me?22:19
hggdhalso, bugsquad/bug-control does not have authority to close nominations22:19
nigel_nbhggdh: I think pedro someone from QA team can.....22:19
nigel_nbpedro, or someone else from the QA team22:20
hggdhLaibsch: yes -- that bug was set to Ubuntu because the OR did not know where to put it (neither do I, for taht matter)22:20
hggdhalso, I reset it to INVALID, since there is no "fix" (apart from a probable bad hardware)22:20
hggdhnigel_nb: probably22:21
nigel_nbanyway, invalid is fine ;)22:21
nperryIf it was just in livecd it would be in ubiquity but if it was there when booted it would be xorg - right?22:21
hggdhLaibsch: nevertheless, you are pointing to a nice issue -- the forgotten nominations. Something should, clearly, be done there22:22
hggdhnperry: it *might* be X, but the OR stated the keyboard was non-functional also during boot22:22
hggdhso this would -- being software -- be more related to the kernel22:23
Laibschhggdh: I thought you were talking about a logical OR (such as the one used in google searches).  My abbreviation for your OR is OP. ;-)22:23
* Laibsch has been using Usenet a lot at dial-up times22:23
hggdhLaibsch: sorry. To be clear -- OR == Original Reporter; for me, OP == Original Poster (which, perhaps wrongly, I tend to use only on mailists)22:24
Laibschyeah, I understood that now22:24
hggdhLaibsch: my fault, nevertheless. I should have been less lazy22:25
Laibschnah, don't worry22:25
LaibschI guess it would make sense to have a "Hardy driver", "$release driver" for past releases22:26
LaibschI'm interested in fixing problems in karmic and hardy22:26
LaibschWhere should I raise this suggestion?22:26
hggdhsomething like that, yes. I am going to raise this on next bugsquad/control meeting22:26
hggdhLaibsch: a good place would be the devel-discuss and bugcontrol mailing lists22:27
dtchenbdmurray: 464612 was a grub bug anyhow.22:27
Laibschhggdh: I don't like to subscribe to yet another mailing list22:27
hggdh:-)22:27
Laibschwhen is that meeting going to be held?22:27
LaibschI suppose it's being done in IRC?22:27
hggdhfirst tuesday of every month, here22:27
hggdhtime... I *think* it is 1600Z22:28
hggdhLaibsch: https://wiki.ubuntu.com/BugSquad/Meeting22:29
hggdhso, yes, 1600Z22:29
hggdh16:00 UTC, actually22:29
Laibschthat's quite some time out22:29
hggdhyes, this is why I suggested the MLs22:30
LaibschAnd I'll likely be without internet for the next one22:30
Laibsch12th, not the 5th?22:30
Laibschthat's probably doable for me22:30
hggdhsend it to the bugsquad ML (or bugcontrol, or devel-discuss)22:30
hggdhoh, I was wrong, it is the second Tuesday, not the first22:31
Laibschplease finishi editing that page ;-)22:34
hggdhanyway, I just added an additional topic for next meeting22:34
hggdhjust did22:34
hggdh:-)22:34
LaibschI would not call it pollution22:35
Laibschthe nominations are a great way to alert the right people that something needs fixing in an older release22:35
Laibsch... if used properly22:35
hggdhI went for the kill, Laibsch. Nominations are good, but if they are not acted on, they just pollute22:35
hggdhI all in favour of them but -- like your bug example -- they must either be accepted or rejected22:36
Laibschwhat's the alternative?22:38
Laibschbugs are marked as fixed when the fix is in release+122:38
Laibschand I think that makes sense22:38
LaibschAs I said, I'd be willing to comb through bugs for hardy and karmic22:39
Laibschand there aren't that many to be overwhelming22:39
hggdhfor those fixed, yes22:41
nperry  hggdh Could i add to the agenda the ammount of Incomplete bugs which havent had a reply for a good couple of months/years - I know they don't count towards any stats but there is alot of them :)22:53
yofelnperry: this is a good start for a statistic: https://bugs.edge.launchpad.net/ubuntu/+expirable-bugs22:55
nperryIs there a magical time for it to be set as invaild? Or has it got to be done manually?22:58
hggdhnperry: you can, but we already discussed it22:58
hggdhcurrently dropping for expiry has been disabled for Ubuntu bugs22:58
hggdhit would be -- by default -- 60 days22:58
nperryIf its already been discussed I wont do :)22:59
hggdhgenrically, anyone can add a topic for the meeting (but should also be present to explain)22:59
yofelnperry: the list I gave you are the bugs that would already be invalid if the feature was turned on22:59
hggdhit was discussed on UDS, IIRC23:00
nperryIs there any remote log of this?23:01
hggdhof waht was noted down, yes, the blueprints23:02
hggdhI do not remember if the session was videotaped, though23:02
* nperry going to look in gobby :)23:03
nperryhggdh: bug 495724 files have now been attached by OR23:07
ubot4Launchpad bug 495724 in b43-fwcutter "Broadcom 4306( b43-fwcutter) Wireless can't connect to Access Points WEP/WPA/Unsecure." [Undecided,Incomplete] https://launchpad.net/bugs/49572423:07
nperrydirect probes are failing.. now thats threw me23:10
hggdhI have been off the BCM world for a while, so I am not sure how things are not. I will mark it triaged23:11
hggdhdone23:15
nperryThankyou hggdh :)23:16
Laibschhggdh: I just received a comment from Steve Langasek that indeed the feature is not used because signal-to-noise is too low.  To improve that I think that making nominations for a release possibly only after a ticket has been closed as fix released would be a good idea.23:39
Laibschwhat do you think about this suggestion?23:39
micahgLaibsch: that's the only time it's possible for anything to be done about it anyways23:40
Laibschexactly23:40
Laibschand it would decrease the noise considerably, I think23:40
micahgbdmurray: can you bump the ff version in the                 firefox-lp-improvements package to 3.6.*?23:46
hggdhLaibsch: good idea, but willrequire lp changes23:54
micahghggdh: you think it should be discussed at the meeting before filing a bug?23:55
hggdhI think it should be discussed by all, yes -- bug-control/squad and devel23:55
hggdhsince I myself do not approve/reject, I am unsure of all possible impacts23:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!