[00:06] <ekristen> maxb: can I use saucy or taunty to build packages for precise?
[00:07] <ekristen> maxb: https://launchpadlibrarian.net/165421447/buildlog_ubuntu-precise-i386.sleuthkit_4.1.3.01-1ubuntu2_FAILEDTOBUILD.txt.gz this package never seem to fail before for this reason, now it says command ant not found? so do I just need to add ant to the build depends?
[00:07] <maxb> Yes - that's one of the principle benefits of using chroots
[00:08] <maxb> If the package requires ant to build, you certainly do need to declare that, or the builder has no way to know it should make it available
[00:12] <ekristen> yeah, just never had to do that before, maybe something changed within that source code
[00:30] <cjwatson> or perhaps one of your other build-dependencies previously depended on it
[00:30] <cjwatson> regardless, it's always correct to directly declare build-dependencies on things you use directly (and usually only on those things)
[00:31] <cjwatson> I used trusty (and previously saucy) to build packages for just about everything under the sun, using sbuild
[00:32] <cjwatson> it's possible that I didn't convert to sbuild until after I stopped using precise for my development system
[00:32] <cjwatson> s/used trusty/use trusty/
[01:38] <ekristen> cjwatson: how do I add a ppa to an sbuild chroot so that it can use those dependencies to build? do I just enter the chroot an add the repo?
[01:50] <teward> ekristen: https://wiki.ubuntu.com/SimpleSbuild#Temporarily_adding_PPAs maybe?
[01:51] <ekristen> teward: can’t believe i missed that, thanks
[01:51] <teward> you're welcome
[01:55] <ekristen> teward: so I have a package that continues to say “make[3]: ant: Command not found” but ant is clearly in the debian/control Build Depends section
[01:55] <ekristen> any suggestions?
[02:00] <ekristen> oh nm
[02:00] <teward> ekristen: sorry, my head's in the command line, i'm rebuilding my chroots after catastrophic evil coming from them
[02:01] <ekristen> teward: no worries, I figured out that I forgot to rebuild my dsc, guess I have to update my local build environment with all the dependencies so I can do a debuild -S so that I can do an sbuild :
[02:01] <ekristen> I’m getting used to sbuild, new to it
[02:02] <teward> i find it easier to use than pbuilder, but yeah, i'm not an sbuild veteran either.
[02:03] <ekristen> do you usually run debuild -S outside a chroot environment to create your dsc and source files and then use sbuild to build them?
[02:05] <teward> ekristen: we can discuss these things in privmsg if you'd like, I'd prefer not to clutter the Launchapd channel with our discussion :)
[02:05] <teward> s/Launchapd/Launchpad/
[15:54] <TJ-> There appears to be a bug when adding an upstream bug tracker link to grub2 from /ubuntu/+source/grub2/+bug/1278114/+choose-affected-product which reports "Launchpad does not recognize the bug tracker at this URL." for http://savannah.gnu.org/bugs/index.php?41524
[16:12] <cjwatson> TJ-: I think it may need to be in the form "http://savannah.gnu.org/bugs/?41524", as per the other items on
[16:12] <cjwatson> https://bugs.launchpad.net/bugs/bugtrackers/savannah
[16:59] <TJ-> cjwatson: aha! would be useful to have launchpad display the acceptable URL template when an error occurs
[16:59] <cjwatson> Yeah
[18:11] <gasull> Hi. How does one know if a PPA is trustworthy and doesn't contain malware? What's a user to do?
[18:14] <teward> gasull, you don't.
[18:14] <teward> gasull, that's the risk you take.
[18:15] <teward> gasull, since all PPAs are third-party there's no reason to trust them.  That's why support for them isn't done on the Ubuntu IRC channels.
[18:15] <teward> gasull, ultimately trusting a PPA is up to you
[18:15] <teward> my PPAs, for instance, don't contain malware, and the nginx team's PPAs don't contain malware either
[18:16] <teward> gasull, but ultimately, there's no reason to trust them
[18:16] <teward> gasull, to quote Ubottu and the factoid they have for PPAs:  [2014/02/09 13:16:13] <ubottu> A Personal Package Archive (PPA) can provide alternate software not normally available in the offical Ubuntu repositories - Looking for a PPA? See https://launchpad.net/ubuntu/+ppas - WARNING: PPAs are unsupported third-party packages, and you use them at your own risk.
[18:16] <teward> the warning there is there for a reason
[18:19] <gasull> teward:  Thanks.  I guess you can only trust PPAs maintained by the people involved on the software project itself.  I guess the nginx PPA you mention is official in the sense that is maintained by the same people who maintain ngnix itself.
[18:19] <teward> gasull, actually, it's maintained by me, but its packages are direct from Debian, which IS maintained by people who help maintain nginx :P
[18:20] <teward> gasull, that's the thing, though, trust in a PPA is purely based on your opinion
[18:20] <gasull> teward: I see. How does the karma work? I'm trying to figure out how much of a good indicator it is.
[18:22] <teward> good indicator of what?
[18:22] <teward> karma's just an indication of how active an individual is
[18:22] <teward> at least, AFAIK
[18:22] <teward> https://help.launchpad.net/YourAccount/Karma
[18:23] <teward> and only in a specific recent period of time (since Karma decays)
[18:23] <gasull> teward: I see.
[18:23] <gasull> teward: Thank you so much.
[18:23] <teward> gasull, karma isn't going to help you determine if someone is trustworthy or not.  Having said this, someone who's listed as an Ubuntu Member, and has signed the Ubuntu CoC, is probably less likely to put malware in a PPA than some random user.
[18:24] <teward> but again, the point is, for PPAs, trust is your call.
[18:24] <teward> if you DO find a PPA with malware, though, you can report it to the LP admins, and then evil befalls the person
[18:24] <saiarcot895> or closed-source software, I suppose
[18:24] <teward> true
[18:25] <teward> or incompatible-license software
[18:25] <teward> except i think malware gets you as a user doomed, whereas the PPAs just get sniped if it's closed-source or an incompatible license
[18:25] <teward> (don't quote me on that, i'm not an LP admin)