Conversation started Feb 10, 2013 at 2:37.
Feb 10, 2013 02:37
Does anyone have the permissions to change a bug status?
Incorrectly marked as "fix released".
@jrg It's just the impression I got when Novel started migrating towards Windows Apps and away from a Linux App Server.
@Mechanicalsnail You want to mark it what?
jrg
jrg
Open a new one
@Abraham might be valid, I wasn't aware of them doing that.
"""Setting intrepid as invalid as it's already EOL.

As this bug is marked as fix released, the better is that somebody that still experiences it in a supported Ubuntu version creates a new bug for it. Then, he/she can link there to this bug report for extra completeness. Thanks."""
@smartboyhw Confirmed
@jrg Someone already did that, I think, and it got marked as a duplicate.
Feb 10, 2013 02:45
OHHHHH, then yes, absolutely...and add a comment about that. Just what I would do
@AbrahamVanHelpsing You mean on the original bug?
@Mechanicalsnail yes. so if someone reads to the end of the thread, they see that piece of data. it may not be possible to comment on a closed bug, i haven't tried. if that's the case, it should be filed as a bug against launchpad itself citing this as an example
that way, you probably fix or get in the fix queue two bugs at once
@AbrahamVanHelpsing It's definitely possible to comment on a closed bug.
But it's closed: nobody will notice.
It would have nicked us telling you to open a new bug...
@AbrahamVanHelpsing "nicked"?
Feb 10, 2013 02:57
kept us from telling you. like "nicked it in the bud" ... i stand corrected "nip in the bud" is the expression. gosh i'm a redneck
jrg
jrg
@mechanical snail kill two birds with one stone I think is what he means.
Oh, I'm wrong. OK.jpg
i'm fetching the source to try a build and see if it just works. it may be that the current deb-src works and it just needs a build trigger. would explain the bug closure
Man. KDE is such an ornery little bugger. The 4.10 upgrade stomped all over my xfce and lightdm configs like a Vandal sacking Rome. :-/
5
How's the AU world today?
@maggot you'll have that rep to push you over 2k soon. and i've heard that about KDE. it is well afaik
@AbrahamVanHelpsing Awesome. That answer got quite a boost once the bounty was put on the Q.
Feb 10, 2013 03:12
@Mechanicalsnail yep that's the problem. it builds properly. someone just needs to trigger a build or shovel in a junk commit to get a build to happen
The strange thing is, I was aware of KDE doing that, but I didn't have a problem installing 4.9. My other WMs were kept intact. Guess I was lulled into a false sense of complacency. This install was mildly brutal.
@AbrahamVanHelpsing So it just copies the old package if the source didn't changed, without checking that it still works?
@maggotbrain Is this from the updates PPA?
i just did an apt-get build-dep. apt-get install photoprint(to confirm the bug). apt-get remove photoprint. apt-get source. debuild -us -uc. dpkg -i photoprint.
@Mechanicalsnail ^^
@Mechanicalsnail Yep, from ppa.launchpad.net/kubuntu-ppa/backports/ubuntu. I'm only so much of a masochist these days. :-/ I'll compile apps. But, kernels and WMs, no thanks.
everyone should compile their own kernel at least once.
not for daily use. just to have done it
Feb 10, 2013 03:20
@AbrahamVanHelpsing Isn't visiting the jslinux webpage enough to have done that?
Oh, I have. Believe me. I don't miss the days of building an install off of 24 floppies of Slackware. I might do a Linux from Scratch build this year to refresh my pain.
@Mechanicalsnail that's like saying installing from binary packages and waiting for a freebsd ports build is the same thing
Am happy I never caught the Gentoo bug.
gentoo is interesting, but for the same target i would go archlinux
Feb 10, 2013 03:23
@AbrahamVanHelpsing Sure. It has it's place. It's just not a viable lifestyle choice for me. ;-)
Just curious, if anyone can tell me. What is going on with the AU troubleshooting tool. I've been seeing folks talking about it, in chat here, and was wondering if I could help with any testing. This is George Edison's baby, no?
@GeorgeEdison pingedipingping
Feb 10, 2013 03:26
@FEichinger ninjamicated
Oh, the AU Troubleshooter.
@AbrahamVanHelpsing Damn you!
It's not quite ready for testing yet.
oh. Hi, George. Didn't realize you were here.
Feb 10, 2013 03:33
Was looking for burrito, found a dune worm reference instead. winning: static.fjcdn.com/pictures/Burrito_675859_649847.jpg
@AbrahamVanHelpsing Redirects to funnyjunk
user image
5
sorry...
@Mechanicalsnail and you saw where i commented on that bug. i referenced the room here with the screenshot. should get the bug resolved "easily" but not necessarily the underlying issue.
This is probably the best Ubuntu Forums post of my life
while(!this.isRested()) {
    this.sleep(100);
}
@FEichinger good code
Feb 10, 2013 03:46
Awful code, but suffices for my purposes.
removed
how does dunecat get more star weight than troubleshooting an issue on launchpad?!? w.t.?.
lol > srs
@AbrahamVanHelpsing Because looking at a dunecat is more fun than triaging bugs (srsly) (LOL)
that's fair. i was going on pure usefulness since the bug in question points out a problem with auto-build as opposed to a non-core package
@FEichinger You won't get much rest sleeping 100 ms at a time.
Feb 10, 2013 04:00
@Mechanicalsnail That's why it loops and the Thread handles the check. :P
@AbrahamVanHelpsing That said kill all the bugs.
@AbrahamVanHelpsing Should we report the auto-build issue?
@FEichinger Obese grasshoppers are not scary enough.
@Mechanicalsnail I think so. I don't know where to report it though.
I think it would be launchpad or libtool with a cursory glance. To be fair I don't have a thorough understanding of either at the source level. This is just based on symptoms and things I notice during build process.
@Mechanicalsnail Then I'd go with this fancy bug.
@FEichinger It is a big one.
@AbrahamVanHelpsing It also spits fire.
Feb 10, 2013 04:05
You should have cited: youtube.com/watch?v=Y4BU0SS-8x0
@FEichinger That doesn't even look like a bug. This is a real fancy bug.
Splat
No, this is a non-bug-looking bug.
@FEichinger it looks like a horrible bug. it's diabolical nature just isn't addressed in a cursory glance
This bug is so severe it's not worth addressing directly initially. It affects so much that it's worth working around for a while
@jrg I use google analytics
@JorgeCastro - you might want to send this up the chain bugs.launchpad.net/ubuntu/+source/photoprint/+bug/260849 it's not a bug in photoprint directly, it just evidences there
seems like a dependency tracking and libtool issue to me.
Feb 10, 2013 04:18
@AbrahamVanHelpsing you need to flip the bug to "Confirmed" if it exists
I don't have that level of privilege on LP
@JorgeCastro The problem is that Launchpad doesn't let us.
afaik anyway...confirmed, i get a dialog that lists bug states but doesn't let me change bug state
I tried changing it to Confirmed using Firebug, but it wouldn't accept that.
huh weird, like 5 people see it and no one has rights to flip it?
ok no worries, I've set it to Confirmed
(you can't change a status on a bug unless you're in the bugsquad)
Feb 10, 2013 04:21
cool beans. it's just something we were talking about here and i went the extra mile to confirm the if and why
or reopening a new bug works too
I left a comment on the bug
<--- goes out drinking
@JorgeCastro Well it lets me change most Ubuntu bugs to anything other than triaged or wontfix.
It's just this bug that we can't change the status of.
Maybe the Intrepid sub-bug is the cause.
 
Conversation ended Feb 10, 2013 at 4:23.