[00:27] <penguin42> bug 296538 is funny
[00:27] <ubot2> Launchpad bug 296538 in ubuntu-wallpapers (Ubuntu) "warty-final-ubuntu.png is actually a jpeg (affects: 17) (dups: 3) (heat: 72)" [Low,Triaged] https://launchpad.net/bugs/296538
[00:28] <yofel> I think by now that's expected behaviour :P
[00:29] <penguin42> well, the unanswered question seems to be the one between Ken Wilmer and David Lowe at the end of 2008/start 2009
[00:30] <penguin42> Ken is saying the update process should be able to cope as of Jaunty
[01:03] <alucardni> Hello, I'm in process of triaging LP 618562, would somebody review this bug report and mark it as Triaged?? Thanks on advance
[01:03] <ubot2> Launchpad bug 618562 in debian (and 1 other project) "new package cgit (affects: 1) (heat: 6)" [Unknown,Unknown] https://launchpad.net/bugs/618562
[01:04] <micahg> alucardni: have you read this? https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs
[01:04] <micahg> oh...I thought the instructions said to add to description...
[01:04] <micahg> alucardni: nm
[01:08] <alucardni> micahg: ok
[01:10] <micahg> alucardni: done, in general though, needs-packaging bugs can stay new
[01:11] <micahg> alucardni: but linking to the Debian ITP or RFP is always helpful, few packages actually end up being introduced in Ubuntu due to resource limitations
[01:12] <alucardni> micahg: ok, I'll keep that in mind. Thanks a lot.
[10:36] <grold> https://bugs.edge.launchpad.net/ubuntu/+source/bash-completion/+bug/590829
[10:36] <ubot2> Ubuntu bug 590829 in bash-completion (Ubuntu) "bash-completion fails to complete filenames with single quote (affects: 3) (heat: 14)" [Undecided,New]
[10:36] <grold> bug was filed against lucid and not reproduced in maverick
[10:36] <grold> shall we marked it fixed?
[10:42] <yofel> grold: yes, works fine in maverick here, please close as fix released
[10:43] <grold> and am I right for nominating it fo lucid?
[10:45] <yofel> yeah, but that will require someone to do a SRU https://wiki.ubuntu.com/StableReleaseUpdates
[10:50] <grold> now, when I close this bug as fix released it not appears in list like: https://bugs.edge.launchpad.net/ubuntu/+source/bash-completion . how anyone will find this bug later?
[10:55] <grold> where it listed now? may be there are special pages like http://qa.ubuntu.com/reports/sponsoring/ where nominated (but not yet confirmed as SRU) bugs are collected?
[10:57] <yofel> actually I'm not sure myself where such bugs go
[13:28] <abhijit> hello :)
[13:33] <penguin42> hi
[13:38] <hggdh> hi penguin42
[16:02] <njin> pedro_: around?
[16:04] <pedro_> njin, hello, yes
[16:12] <charlie-tca> njin: I did confirm the 2 hdd bug last nite
[16:12] <njin> charlie-tca-good work, thanks
[16:18] <JFo> charlie-tca, you rock
[16:18] <JFo> just wanted to share that
[16:20] <charlie-tca> Thanks, JFo
[16:20] <charlie-tca> I just try to do help where I can
[16:21] <JFo> well, fwiw, I appreciate it :)
[16:22] <charlie-tca> That is what makes it worth it to me.
[16:54] <penguin42> does anyone understand bug 619135 ? I'm getting it on some packages but not others - is it a packaging mistake or a dpkg/apt problem?
[16:54] <ubot2> Launchpad bug 619135 in banshee (Ubuntu) "Warnings in '/var/lib/dpkg/updates/***' while installing banshee (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/619135
[16:54] <penguin42> (as of the last few days(
[16:59] <sinurge> !topic
[16:59] <ubot2> Please read the channel topic whenever you enter, as it contains important information. To view it at any time after joining, simply type /topic
[17:06] <bilalakhtar> I've noticed that there are a few bugs that have both Lucid and Maverick statuses for a single package, like this one #595265 . How do I get it for my bug? as I need to track statuses for both lucid and maverick
[17:06] <micahg> bilalakhtar: nominate for release
[17:07] <bilalakhtar> micahg: that doesn't do it
[17:07] <bilalakhtar> micahg: let me give you an example
[17:07] <micahg> bilalakhtar: YOU can't do it :)
[17:07] <bilalakhtar> micahg: then who can?
[17:07] <micahg> bilalakhtar: a MOTU or core-dev needs to accept the nomination
[17:07] <bilalakhtar> micahg: ah, I got it. an ubuntu driver
[17:07]  * bilalakhtar wishes he was MOTU
[17:08] <bilalakhtar> thanks micahg
[17:08] <micahg> bilalakhtar: np
[17:13] <yofel> penguin42: I see that too, possibly caused by dpkg if I understand it correctly
[17:13] <yofel>   * Always print a massage on warning when parsing control files.
[17:13] <yofel>   * On database parsing only warn on bogus versions previously accepted,
[17:13] <yofel>     the other instances will keep producing errors, to avoid newly
[17:13] <yofel>     introduced bogosity. Closes: #590885, #590896, #591692, #591885
[17:16] <penguin42> yofel: So is that saying the warnings are valid because some packages are missing maintainer data?
[17:17] <yofel> I'm not sure, I only know it started recently
[17:17] <penguin42> yeh last few days
[17:17] <yofel> got this today: http://paste.ubuntu.com/479993/
[17:18] <penguin42> yeh I got it on a few today
[17:19] <penguin42> yofel: So my question is really is that bug 619135 valid and actually needs a similar one for every broken package (probably a bad idea?) ?
[17:19] <ubot2> Launchpad bug 619135 in banshee (Ubuntu) "Warnings in '/var/lib/dpkg/updates/***' while installing banshee (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/619135
[17:19] <yofel> not sure, jibel: do you know anything about this?
[17:28] <jibel> yofel, hello, corrupted device probably ? Asking for dmesg may help.
[17:37] <yofel> jibel: I just got http://paste.ubuntu.com/479999/ while installing updates, and no I don't have any ata or ext4 errors during that time
[17:38] <jibel> yofel,  hm, let me try that
[17:38] <penguin42> jibel: I'm also seeing it, as is one other on #ubuntu+1 and there's bug 619135
[17:38] <yofel> that's maverick btw.
[17:38] <ubot2> Launchpad bug 619135 in banshee (Ubuntu) "Warnings in '/var/lib/dpkg/updates/***' while installing banshee (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/619135
[17:38] <jibel> yofel, what's your version of dpkg ?
[17:39] <yofel>   Installed: 1.15.8.4ubuntu1
[17:39] <penguin42> same here
[17:43] <jibel> I can't reproduce with libcanberra-dev, trying banshee.
[17:44] <penguin42> saw it earlier with mc and a few others
[17:49] <jibel> yofel, from dpkg (1.15.8.4)  "  * Always print a massage on warning when parsing control files.", published 2 days ago.
[17:50] <yofel> that's what I suspect too, but I don't really understand what that means, as the control files seem fine from what I see
[17:52] <jibel> 1mn, let me try something (if not back in 2 minutes, I broke my system)
[17:57] <penguin42> guess it's broke then :-)
[17:57] <jibel> Nope, I'm back.
[17:58] <jibel> Here is the content of /var/lib/dpkg/updates/0025 : http://paste.ubuntu.com/480010/
[18:01] <penguin42> where does that come from?
[18:03] <jibel> dpkg unpacks the control files to /var/lib/dpkg/updates when processing a package, a delete the files once it's done.
[18:03] <jibel> That's the mechanism that helps to manage transactions and keep the system consistent even when the upgrade is interrupted.
[18:04] <jibel> when you see 'please run dpkg --configure -a' then this directory is probably not empty.
[18:04] <penguin42> how did you extract that file - did you get dpkg not to remove it or something?
[18:05] <ashams> simar: I'm here! :)
[18:06] <jibel> penguin42, pkill -9 -f dpkg while it's running
[18:07] <penguin42> haha ok
[18:07] <jibel> penguin42, yofel, unless there's really a problem with the packaging of banshee, dpkg is probably a bit verbose here.
[18:07] <penguin42> jibel: That's what we're trying to figure out, it's lots of packages doing it - is it dpkg being verbose suddenly or is it actually something dumb in lots of packages
[18:08] <yofel> well, according to dpkg-deb -f the control files of the packages it warnes about look fine :/
[18:09] <yofel> just got 'warning, in file '/var/lib/dpkg/updates/0025' near line 6 package 'banshee': missing maintainer' while installing banshee
[18:09] <yofel> dpkg-deb -f /var/cache/apt/archives/banshee_1.7.3-2ubuntu2_amd64.deb -> http://paste.ubuntu.com/480016/
[18:10] <penguin42> jibel: Are those files in updates directly from the package? They don't look like the control file itself
[18:10] <penguin42> jibel: It looks like they're temporary files generated as it's awaiting other packages to do something
[18:10] <yofel> I would guess it's the template for the /var/lib/dpkg/status section
[18:12] <yofel> but the banshee section there looks fine too, or does dpkg try to unpack the control file, messes up and retries until it gets a working one o.O?
[18:13] <penguin42> yofel: Well the ones that are complaining for me don't have a maintainer entry - the original control file does, but those aren't the control file
[18:14] <jibel> penguin42, yes, those files tracks the transaction, I think that the warning is wrong but that's the limit of my knowledge of dpkg, I asked cjwatson if he knows what that warning is.
[18:16] <penguin42> jibel: My guess is something is checking control files; but applying the same check to these temporary files that have almost the same format - but I don't know anything about the internals of dpkg
[18:16] <jibel> however, as a triager, you should add a task for dpkg, paste the output of pastebin (file 0025) add an information to explain it started with the latest version and set it to triage.
[18:19] <jibel> penguin42, yeah, understanding the internals of dpkg takes some time. And it's very frustrating when you ask a guru about and he has the answer in a few seconds. So, triage it, and let see what his opinion.
[18:21] <penguin42> jibel: Yeh my problem was trying to understand whether dpkg was validly complaining and hence it really was a banshee bug or whether it was a dpkg bug, but it is sounding like a dpkg one from those intermediaries
[18:22] <penguin42> jibel: So you think the right thing is to move that one to dpkg from banshee and comment?
[18:24] <jibel> penguin42, until we are sure it's a dpkg issue, I would keep the banshee task opened (in case there's really something with banshee's control file) and open a new task for dpkg.
[18:24] <penguin42> jibel: Can you explain what you mean by opening a new task - do you mean a separate launchpad bug ?
[18:25] <jibel> penguin42, upstream may have strengthen the policy in dpkg which may need a fix in the control file, and it's complaining about it.
[18:25] <jibel> penguin42, to open a task, click on 'Also affects distribution'
[18:26] <penguin42> jibel: Ah ok, and then just still ubuntu and package dpkg ?
[18:26] <jibel> penguin42, leave 'Ubuntu' as distribution and set package to 'dpkg'
[18:26] <penguin42> ok
[18:27] <jibel> If that's really dpkg becoming suddenly overly verbose, we'll probably receive many reports of that kind in the next few days.
[18:28] <penguin42> jibel: Indeed
[18:28] <penguin42> jibel: OK, added dpkg task and added comment with an example of one of the temporary files
[18:28] <jibel> penguin42, so choose one as master and set the new reports as duplicates and that will confirm that it is a dpkg issue.
[18:29] <jibel> penguin42, many thanks for your help.
[18:29] <penguin42> jibel: And yours - so if I find any others I'll just dupe them to 619135 - does it need tagging in any way?
[18:31] <jibel> penguin42, no specific tagging for that case. .
[18:31] <penguin42> ok
[18:48] <ashams> simar: I'll be waiting till 18:00 UTC....
[18:50] <yofel> ashams: any questions we could help with?
[18:50] <ashams> yofel: no thank you yofel, I'm just waiting for my mentor.
[20:05] <MichealH> Do 100 Papercuts Bugs need traging?
[20:05] <MichealH> *triaging?
[20:09] <MichealH> Anyone?
[20:10] <charlie-tca> We don't touch them
[20:10] <charlie-tca> vish will look at them, usually
[20:11] <vish> MichealH: hey , wassup?
[20:11] <micahg> MichealH: that's a separate project, vish can fill you in
[20:12] <MichealH> vish, Is it okay for me to go throught the process of traiging 100 papercut bugs or helping triage them?
[20:12] <vish> hmm , just a couple of weeks ago, i had brought down the number of new bugs to 10.. now its back to 40 :s
[20:12] <MichealH> vish I can help you if you wnat
[20:12] <vish> MichealH: yeah, sure feel free to triage..
[20:13] <MichealH> vish: I dont have them privelages
[20:13] <MichealH> Can I look around and give you bug numbers
[20:13] <vish> sure.
[20:14] <vish> MichealH: do note that not all bugs are papercuts, some of the bugs need design and thought, so some i just wait for a clear mind :)
[20:14] <MichealH> Okay
[20:15] <vish> MichealH: for starters have a quick read of the wiki page : https://wiki.ubuntu.com/PaperCut
[20:17] <vish> MichealH: if you can fix any of the bugs, feel free to do so too.. :D
[20:17] <MichealH> Yeah
[20:19] <MichealH> vish: Could https://bugs.edge.launchpad.net/hundredpapercuts/+bug/597464 be classed as a bug to triage in this case?
[20:19] <ubot2> Ubuntu bug 597464 in notify-osd (Ubuntu) (and 2 other projects) "NetworkManager "connected" message is "masked" by other notifications (affects: 2) (heat: 69)" [Undecided,New]
[20:20] <vish> MichealH: yeah, i'v not able to reproduce that one..  iirc we fixed that last cycle
[20:20] <MichealH> Okay
[20:20] <vish> i mean in Lucid.
[20:20] <MichealH> So It cant be triaged
[20:20] <MichealH> Becuase it is fixed
[20:21] <MichealH> Should I put "Fix Released" on them?
[20:21] <vish> MichealH: we assigned priorities for those notifications and they are supposed to be fixed..
[20:21] <vish> MichealH: but i actually havent tested it yet..  my system connects before other notifications..
[20:21] <MichealH> Okay
[20:22] <MichealH> Mine too :P
[20:22] <vish> MichealH: so i dont have a test case to say it is fixed.. would be great if someone had an idea for that :)
[20:22] <MichealH> What about https://bugs.edge.launchpad.net/hundredpapercuts/+bug/596717
[20:22] <ubot2> Ubuntu bug 596717 in xcursor-themes (Ubuntu) (and 1 other project) "Whiteglass "busy" cursor is not aligned properly (affects: 2) (heat: 66)" [Undecided,Confirmed]
[20:23] <MichealH> I havent confirmed in 100Papercuts yet
[20:23] <MichealH> But is that what we are looking for?
[20:24] <vish> MichealH: heh , yeah.. such is our dilemma often .. :D
[20:24] <MichealH> So should I get it ready for Triaging?
[20:25] <vish> MichealH: we can leave it as confirmed for now.. we dont yet know if it is trivially fixable
[20:25] <vish> but it should be..
[20:25] <MichealH> So its a no for that one
[20:27] <MichealH> What about https://bugs.edge.launchpad.net/hundredpapercuts/+bug/618723
[20:27] <ubot2> Ubuntu bug 618723 in update-manager (Ubuntu) (and 1 other project) "Rename Update Manager to Software Updater (affects: 1) (heat: 6)" [Wishlist,New]
[20:27] <MichealH> That can be fixed easily
[20:27] <vish> MichealH: i filed that one :D , devildante is working on it..
[20:27] <MichealH> :/
[20:28] <MichealH> He isnt assigned
[20:29] <MichealH> vish: I know this one is a good one https://bugs.edge.launchpad.net/hundredpapercuts/+bug/619532
[20:29] <ubot2> Ubuntu bug 619532 in hundredpapercuts "Password discountinuity (affects: 1) (heat: 6)" [Undecided,New]
[20:30] <MichealH> Shall We get to triage this?
[20:30]  * vish looks , oh a new one!
[20:31] <MichealH> Me has dont he Confirmation
[20:31] <MichealH> *done
[20:31] <MichealH> *the
[20:32] <MichealH> Now, Its ready to triage! :)
[20:34] <vish> MichealH: cool! , now we open an Ubuntu task for the bug, and forward it upstream too.
[20:35] <MichealH> How do we do that?
[20:35] <vish> MichealH: select the "Also affects distribution"
[21:27] <vish> kamusin: no! it hasnt been applied ;)
[21:28]  * vish hopes kamusin is confused :D
[21:28] <kamusin> virtuald, heh I think so
[21:28] <kamusin> vish,
[21:29] <vish> kamusin: banshee .. ;)
[21:29] <vish> kamusin: they still havent merged that browser branch
[21:32] <kamusin> vish, heh.. I did a quickly search in banshee source included in Maverick and I can't found nothing too .. so that confirm my suspicion :)
[21:34] <vish> kamusin:  ... btw, use your @ubuntu id in bgo ;)
[21:35] <MichealH> vish: Found a bug tracker yet?
[21:35] <kamusin> right! I always forgot it :$ heh
[21:36] <vish> MichealH: you are the triager.. not me :)
[21:46]  * vish sleeps.. 2am here
[21:46] <MichealH> vish: I found http://debbugs.gnu.org/
[21:46] <MichealH> vish: Please look before sleeping
[21:47] <MichealH> Please
[21:47] <vish> MichealH: i dont think thats the one.. its somewhere in here http://alioth.debian.org/projects/adduser/  ..
[21:48] <micahg> vish: what are you looking for a tracker for?
[21:48] <vish> micahg: adduser
[21:51] <micahg> vish: Debian BTS
[21:52] <vish> micahg: ah cool!
[21:52] <vish> MichealH: ^^ just send a mail to the debian BTS , its easy no registration required
[21:52] <MichealH> vish: So we can file a report there and get this over and done with
[21:52] <vish> MichealH: yup
[21:53] <micahg> MichealH: reportbug -Bdebian is good for reporting to the BTS
[21:53] <MichealH> Shall I just copy and paste from Launchpad
[21:53] <MichealH> micahg: If I was on Ubuntu :/
[21:53] <MichealH> I am on Windows
[21:53] <vish> micahg: we dont have reportbug by default ;)
[21:53] <MichealH> vish: Shall I just copy and paste from Launchpad
[21:53] <micahg> vish: that's easy enough to install for triagers
[21:54] <vish> micahg: +1 , though MichealH seems to be in a hurry
[21:55] <MichealH> Whats the Version of adduser currently?
[21:56] <vish> MichealH: hmm , how did you test the bug, if you are in Windows?
[21:57] <MichealH> I had encounted it before a few days ago
[21:57] <vish> :/
[21:58] <vish> anyways..
[21:58]  * vish sleeps
[21:58] <MichealH> vish: Wait!
[21:58] <MichealH> Im done reporting the bug!
[21:59] <MichealH> micahg: Can you help?
[21:59] <micahg> MichealH: with?
[22:00] <MichealH> Triaging this bug
[22:00] <MichealH> I just need to upload upstream as vish said then Im done
[22:00] <micahg> MichealH: what bug?
[22:00] <MichealH> https://bugs.edge.launchpad.net/adduser/+bug/619532
[22:00] <ubot2> Ubuntu bug 619532 in adduser (Ubuntu) (and 2 other projects) "Allow user to set preferred password (affects: 2) (heat: 10)" [Undecided,Confirmed]
[22:01] <MichealH> How do I upload upstream
[22:01] <micahg> MichealH: where's the upstream bug
[22:01] <MichealH> It is getting uploaded
[22:01] <micahg> MichealH: also affects distribution
[22:01] <vish> MichealH: i would really consider this very bad triaging, what if i had not checked the bug and just gone by your "confirmed"?
[22:02] <MichealH> vish: Sorry.
[22:02] <vish> MichealH: always really confirm the bug when you are triaging, not from past memory
[22:02] <MichealH> Okay
[22:02]  * micahg has a feeling it'll be closed Won't Fix
[22:03] <vish> micahg: probably..
[22:03] <MichealH> vish: Its not letting me add a url to the reported bug elsewhere :/
[22:03] <micahg> MichealH: I told you how to add it, the upstream project in LP is not correct
[22:04] <vish> MichealH: use "also affect distribution"
[22:04] <micahg> also, why is this bug in adduser?
[22:04] <micahg> you change a password with passwd
[22:04] <MichealH> me and vish decided upon it
[22:04] <micahg> vish: :P
[22:04] <vish> micahg: thats the closet i could get and hence asked seb-128 as well
[22:05] <micahg> vish: seb said to put it in adduser?
[22:05] <vish> micahg: he didnt know either
[22:05] <micahg> vish: well, one question missing is how is the user changing the password?
[22:06] <vish> micahg: there is password : "change..."
[22:06] <micahg> vish: is it through passwd on the console or through the GUI...
[22:07] <vish> micahg: gui
[22:07] <micahg> vish: how do you know?
[22:07] <vish> micahg: thats when the prompt occurs :)
[22:08] <MichealH> I cant access the url of the bug I sent D:
[22:08] <micahg> vish: it occurs on teh console as well...
[22:08] <vish> doh! my bad
[22:09] <vish> micahg: so its a bug in passwd?
[22:10] <micahg> vish: yes, the bug should be in shadow source
[22:10] <micahg> and the bug in the BTS should be moved
[22:10] <vish> MichealH: ^^
[22:10]  * vish really sleeps now! 02:45!
[22:10] <MichealH> How do I do that?
[22:11]  * hggdh thinks this is related to pam
[22:11] <hggdh> :-)
[22:12] <micahg> hggdh: could be, but passwd is definitely better than adduser :)
[22:12] <vish> ah! hggdh !
[22:13] <MichealH> pam?
[22:13] <vish> hggdh: do note: MichealH tried to triage the bug without actually testing it now.. ;)
[22:14] <MichealH> Okay I have the link to the bug report
[22:14]  * micahg agrees with hggdh
[22:15] <micahg> move to pam, probably will be marked won't fix
[22:16] <MichealH> "
[22:16] <MichealH> Oops
[22:16] <MichealH> "Bug watches can not be added for Ubuntu, as it uses Launchpad as its official bug tracker. Alternatives are to add a watch for another project, or a comment containing a URL to the related bug report."
[22:16] <MichealH> I get that error
[22:16] <micahg> MichealH: you're doing something wrong then :0o
[22:16] <micahg> :)
[22:16] <hggdh> vish: dully noted
[22:16] <MichealH> It goes to Debian BTS for the bug URL
[22:16] <MichealH> I set the url to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593513
[22:16] <ubot2> Debian bug 593513 in adduser "Allow user to set preferred password" [Normal,Open]
[22:17] <micahg> MichealH: you need to set the distro to Debian :)
[22:17] <MichealH> Ahhhh
[22:17] <hggdh> I do remember seeing this some time ago, I just do not remember who is responsible
[22:18] <MichealH> Okay Now i think it needs the adduser changed (I dont know how) and then it can be triaged
[22:18] <MichealH> Can someone change the PackageName for me?
[22:18] <MichealH> *The Project name
[22:19]  * MichealH needs to sleep
[22:19] <MichealH> micahg: ^^
[22:19] <MichealH> Bye
[22:25] <hggdh> pam_login, it seems
[22:26] <micahg> hggdh: I moved it to libpam-runtime since that manages the default password options
[22:29] <MichealH> Has that been done yet?
[22:29] <MichealH> Micahg ^^
[22:29] <micahg> MichealH: yeah, you should've been notified
[22:29] <MichealH> Okay So it's triaged?
[22:30] <micahg> MichealH: yeah
[22:30] <MichealH> Thanks
[22:30]  * micahg would love to mark won't fix
[22:30] <MichealH> :D
[22:30] <MichealH> Why?
[22:30] <micahg> but will let Debian do it first :)
[22:30] <MichealH> Why Won't fix?
[22:31] <micahg> MichealH: someone can change it themself if they insist on being insecure
[22:31] <micahg> it might not be won't fix for Ubuntu but I can pretty much guess it will be for debian
[22:31] <MichealH> micahg ^^
[22:32] <MichealH> Okay
[22:33] <vish> oh!
[22:34] <micahg> vish: huh?
[22:34] <vish> micahg: it doesnt allow from GUI, it just says "User passwords must be longer than 6 characters and preferably formed by numbers, letters and special characters" and takes you back.. how are you being allowed to change?
[22:34] <micahg> vish: you can't it's the pam rules
[22:34] <micahg> vish: I said the console gives the same warning
[22:35] <yofel> yeah, but console gives the option to run 'sudo passwd' gui doesn't
[22:35] <vish> ah.. never tried the console
[22:35] <micahg> yofel: what's the difference
[22:35] <yofel> micahg: root user can set any password I think
[22:35] <vish> micahg: well , from a GUI there needs to be something similar as well..
[22:36] <micahg> yofel: yeah, you're correct root overrides PAM rules...
[22:36] <micahg> yofel: maybe that's a bug ;)
[22:37] <yofel> not sure, IIRC it's like that everywhere I tried, meaning ubuntu, debian and gentoo (can't remember suse)
[22:39] <micahg> well, that's also why console vs gui makes a difference
[22:40] <micahg> also can the users and groups  GUI change to anything like sudo passwd on the console?
[22:41] <yofel> not sure about gnome, in KDE it can't
[22:43] <micahg> right so it could be the bug was aimed at the wrong component still...
[22:43]  * micahg gives up on this
[22:50] <micahg> vish: bug 619532 still needs more information when you get up (main question is where is the user running into the issue since there are at least 3 places in the default install to do it that won't work and another that will)
[22:50] <ubot2> Launchpad bug 619532 in pam (Debian) (and 3 other projects) "Allow user to set preferred password (affects: 2) (heat: 12)" [Unknown,Unknown] https://launchpad.net/bugs/619532
[22:51] <hggdh> I would like to point out that what I think is needed is consistency. I would rather have such consistency on blocking *any* over-weak password, though
[22:52] <micahg> hggdh: well, my main issue is if root can override, than maybe the Users and Groups GUI which is run as sudo should have that option
[22:53] <micahg> in which case, there's no bug for Debian, but rather upstream gnoem
[22:53] <micahg> *gnoem
[22:53] <micahg> whatever...
[22:53] <vish> micahg: hehe , i never even knew there were 3 different ways.. pretty sure the user is trying from GUI.. papercut bugs are usually about the gui
[22:53]  * vish asks now!
[22:55] <micahg> vish: I might be wrong about the 3rd (I thought there's some type of change my password GUI), but there's Users and Groups and passwd from the console
[22:56] <vish> micahg: bug 619532 marked it incomplete :)
[22:57] <ubot2> Launchpad bug 619532 in pam (Debian) (and 3 other projects) "Allow user to set preferred password (affects: 2) (heat: 12)" [Unknown,Unknown] https://launchpad.net/bugs/619532
[22:57]  * micahg marked Ubuntu task incomplete as well
[22:58]  * vish would have done that, but dint wanna change micahg's triaged :)
[22:58] <micahg> vish: also good to remind people when upstreaming to link to the LP bug
[22:59] <vish> micahg: hmm? didnt understand..
[22:59] <micahg> vish: add a link in the upstream bug (or use the appropriate bugzilla field if it exists) for the LP bug
[23:00] <vish> micahg: yeah thats exactly what i told MichealH, he was in a hurry to set the bug triaged..
[23:01] <vish> micahg: kept pinging me[PM] and he wouldnt even wait for me to ask someone what the right package was.. :/
[23:01] <micahg> vish: I think we're better off telling people to come back when they have more time in cases like this...the rushing caused everyone else to rush and now we upstreamed an incomplete bug
[23:01]  * micahg is at fault as well
[23:02] <vish> micahg: +1 , he probably wants to apply as soon as he has 5bugs set as triaged.. hence i pinged hggdh to note that he is doing a lot of wrong
[23:03] <vish> micahg: even the earlier bug the ubiquity bug he wanted to mark as triaged without testing
[23:03] <hggdh> vish: heh dully noted. I had already cleaned up some 10 bugs he was (mis)worked on...
[23:04] <hggdh> thanks to micahg, BTW, who pointed me to the bugs
[23:04] <vish> hggdh: oh neat! so people know :)
[23:05] <micahg> part of Bug Triage just like in medicine is keeping a cool head so mistakes aren't made
[23:06] <hggdh> :-) and remembering that, sometimes, it is better to Do Nothing
[23:07] <vish> :)
[23:08] <vish> i even had to explain to him that i have only set the papercut as triaged and that the ubuntu bug is not triaged, which is what is necessary for a BC application
[23:08] <vish> and that the ppc triaged does not count..
[23:08] <hggdh> although, frankly, I do not understand how one can triage bugs in Linux running under Windows (or any other O.S.)
[23:09] <vish> that totally pissed me off.. :/
[23:09] <micahg> VirtualBox
[23:09] <vish> i dont think he was using VB
[23:09] <penguin42> hggdh: Depends on the bug
[23:10] <micahg> vish: I know
[23:10] <hggdh> well. I do hope he RTFM... right now, if he applies... I will have no option but to decline
[23:10] <penguin42> hggdh: Obviously nothing timing or hardware related; but hey if it's application level it shouldn't make much odds
[23:10] <hggdh> penguin42: it may well be: if I have a stracktrace, all I (most probably) need is the code
[23:11] <hggdh> this was not the case this time, though
[23:11] <penguin42> hggdh: Well, that depends on the problem
[23:11] <penguin42> hggdh: A stack trace tells you what state it wound up in when it broke not how it got there
[23:11] <hggdh> penguin42: indeed, and this is why I qualified my response: "most probably"
[23:16] <vish> micahg: just saw the scrollback on the channel as well.. i have asked him here itself to open an upstream bug first :)
[23:16] <micahg> vish: yeah, not good
[23:40] <hggdh> well, OK, here he comes. I just approved his email to the bug-control ML
[23:42] <micahg> oh boy