/srv/irclogs.ubuntu.com/2017/07/03/#launchpad.txt

mwhudsoncjwatson, wgrant: if the primary archive and the ppa have packages of the same version, packages in the ppa seem to get preferred00:40
mwhudsoncjwatson, wgrant: is this done via apt preferences or, to state my real question, how do i reproduce this in a local schroot?00:40
cjwatsonmwhudson: apt breaks ties by sources.list order00:48
cjwatsonmwhudson: so just put the PPA first in sources.list00:48
mwhudsoncjwatson: oh heh ok00:53
tjaaltonhi, some bugs get spam from a few users. what to do with those?07:07
tjaaltonid's j-a150678, pin8-h, giuse-obino07:10
cpaelzerhi LP build recipes try to puzzle me, maybe someone here can help07:27
cpaelzerrecipe as in https://code.launchpad.net/~ubuntu-virt/+recipe/qemu-daily07:27
cpaelzerbut I can perfectly recreate locally with rm -rf qemu-workdir/*; git-build-recipe --allow-fallback-to-native qemu-daily/qemu.recipe qemu-workdir07:27
cpaelzerwhat happens is this07:27
cpaelzerthe "packaging" repo has fixes e.g. in d/control now libseccomp-dev (>= 2.2.0)07:28
cpaelzerthat was 2.3 before07:28
cpaelzeralso if I clone the packaging repo into a new dir I see that it fetches master with the "libseccomp-dev (>= 2.2.0)"07:28
cpaelzerbut if running through git-build-recipe or on LP it always picks up old content from the packaging branch07:29
cpaelzerwhich leads to dependency killing the build as in https://launchpadlibrarian.net/326205008/buildlog_ubuntu-xenial-amd64.qemu_2%3A0~daily-201706300837-c5eb584~ubuntu16.04.1_BUILDING.txt.gz07:29
cpaelzerdoes anybody have an idea why/how the "old" content of debian/control could slip in here?07:30
cpaelzerI see git-build-recipe calling git -C qemu-workdir/qemu merge --commit -m Merge master ...08:12
cpaelzerand it is the right hash with the fixed content08:12
cpaelzerbut the result eventually is still having the old one08:12
geserlooks like something triggers the "debian/control" target in debian/rules to regenerate debian/control from debian/control-in and the later file still has the old dependency08:18
geser"echo '# autogenerated file, please edit debian/control-in' > debian/control.tmp" (from the buildlog for the source package)08:21
=== chihchun_afk is now known as chihchun
gesercpaelzer: ^^08:31
cpaelzerI fount it09:06
cpaelzerthanks geser09:06
cpaelzerthe worst is I know that it is generated, but I happen to forget once every 3 months :-/09:07
cpaelzerhmm it seems currently all LP build recipies on artful fail for me with09:17
cpaelzerE: The repository 'file:/home/buildd/work/apt ./ Release' is not signed.09:17
cpaelzerReading package lists...09:17
cpaelzerE: You must put some 'source' URIs in your sources.list09:17
cpaelzeris that any sort of known current issue in artful?09:17
cpaelzerwhile the issue is at the recipe building, not the follow on build of the binary package - I'll ask in ubuntu-devel to get a wider audience if one has seen the issue in general09:21
muktupavelscpaelzer: https://bugs.launchpad.net/launchpad-buildd/+bug/170182609:23
ubot5Ubuntu bug 1701826 in launchpad-buildd "APT 1.5: E: The repository 'file:/home/buildd/work/apt ./ Release' is not signed. " [Critical,In progress]09:23
cpaelzerthanks muktupavels - in ubunut-devel there is also some chat backlog to be found about it09:23
cjwatsonwgrant: ^- could you review my MP for that, please?09:49
wgrantugh what10:09
wgrantcjwatson: Remember that precise is still in ESM, though hopefully nobody's using git-buildrecipe with it.10:10
cjwatsonwgrant: precise supports [trusted=yes]10:17
cjwatsonI said that in my MP :)10:17
wgrantcjwatson: ... indeed.10:18
wgrantI misread that line as "trusty", I guess because it started with "trusted".10:18
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== pbek_ is now known as pbek

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