/srv/irclogs.ubuntu.com/2014/02/09/#launchpad.txt

ekristenmaxb: can I use saucy or taunty to build packages for precise?00:06
ekristenmaxb: 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
maxbYes - that's one of the principle benefits of using chroots00:07
maxbIf 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 available00:08
ekristenyeah, just never had to do that before, maybe something changed within that source code00:12
cjwatsonor perhaps one of your other build-dependencies previously depended on it00:30
cjwatsonregardless, it's always correct to directly declare build-dependencies on things you use directly (and usually only on those things)00:30
cjwatsonI used trusty (and previously saucy) to build packages for just about everything under the sun, using sbuild00:31
cjwatsonit's possible that I didn't convert to sbuild until after I stopped using precise for my development system00:32
cjwatsons/used trusty/use trusty/00:32
=== Mission-Critical is now known as MissionCritical
ekristencjwatson: 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:38
tewardekristen: https://wiki.ubuntu.com/SimpleSbuild#Temporarily_adding_PPAs maybe?01:50
ekristenteward: can’t believe i missed that, thanks01:51
tewardyou're welcome01:51
ekristenteward: 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 section01:55
ekristenany suggestions?01:55
ekristenoh nm02:00
tewardekristen: sorry, my head's in the command line, i'm rebuilding my chroots after catastrophic evil coming from them02:00
ekristenteward: 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
ekristenI’m getting used to sbuild, new to it02:01
tewardi find it easier to use than pbuilder, but yeah, i'm not an sbuild veteran either.02:02
ekristendo you usually run debuild -S outside a chroot environment to create your dsc and source files and then use sbuild to build them?02:03
tewardekristen: 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
tewards/Launchapd/Launchpad/02:05
=== zz_zz_mwhudson is now known as mwhudson
=== mwhudson is now known as zz_mwhudson
=== zz_mwhudson is now known as mwhudson
=== mwhudson is now known as zz_mwhudson
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?4152415:54
cjwatsonTJ-: I think it may need to be in the form "http://savannah.gnu.org/bugs/?41524", as per the other items on16:12
cjwatsonhttps://bugs.launchpad.net/bugs/bugtrackers/savannah16:12
=== DarkPlayer_ is now known as DarkPlayer
TJ-cjwatson: aha! would be useful to have launchpad display the acceptable URL template when an error occurs16:59
cjwatsonYeah16:59
gasullHi. How does one know if a PPA is trustworthy and doesn't contain malware? What's a user to do?18:11
tewardgasull, you don't.18:14
tewardgasull, that's the risk you take.18:14
tewardgasull, 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
tewardgasull, ultimately trusting a PPA is up to you18:15
tewardmy PPAs, for instance, don't contain malware, and the nginx team's PPAs don't contain malware either18:15
tewardgasull, but ultimately, there's no reason to trust them18:16
tewardgasull, 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
tewardthe warning there is there for a reason18:16
gasullteward:  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
tewardgasull, actually, it's maintained by me, but its packages are direct from Debian, which IS maintained by people who help maintain nginx :P18:19
tewardgasull, that's the thing, though, trust in a PPA is purely based on your opinion18:20
gasullteward: I see. How does the karma work? I'm trying to figure out how much of a good indicator it is.18:20
tewardgood indicator of what?18:22
tewardkarma's just an indication of how active an individual is18:22
tewardat least, AFAIK18:22
tewardhttps://help.launchpad.net/YourAccount/Karma18:22
tewardand only in a specific recent period of time (since Karma decays)18:23
gasullteward: I see.18:23
gasullteward: Thank you so much.18:23
tewardgasull, 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:23
tewardbut again, the point is, for PPAs, trust is your call.18:24
tewardif you DO find a PPA with malware, though, you can report it to the LP admins, and then evil befalls the person18:24
saiarcot895or closed-source software, I suppose18:24
tewardtrue18:24
tewardor incompatible-license software18:25
tewardexcept i think malware gets you as a user doomed, whereas the PPAs just get sniped if it's closed-source or an incompatible license18:25
teward(don't quote me on that, i'm not an LP admin)18:25
=== zz_mwhudson is now known as mwhudson
=== Nafallo_ is now known as Nafallo
=== mwhudson is now known as zz_mwhudson
=== zz_mwhudson is now known as mwhudson
=== nickoe is now known as argo
=== argo is now known as nickoe
=== nickoe is now known as argo
=== argo is now known as nickoe
=== nickoe is now known as faps
=== faps is now known as nickoe
=== nickoe is now known as faps
=== faps is now known as nickoe

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