On Thu, 15 Feb 2018 23:20:08 +0200, Luca Falavigna wrote: > 2018-01-24 18:14 GMT+01:00 Yavor Doganov <ya...@gnu.org>: > > The pubring as specified in the repository section in the > > configuration file is also not copied to the chroot's > > /etc/apt/trusted.gpg.d as it should be. > > Odd, pubring should be copied in if the relevant configuration option > is defined in the configuration file and the file itself is found: > https://sources.debian.org/src/debomatic/0.22-1/Debomatic/build.py/#L464-L468
I'm not sure, but I think this code is never reached (or more likely, the condition is false). Perhaps the same applies for the other condition at line 460. > > The commands file I use is: > > builddep viewpdf.app_1:0.2dfsg1-6 experimental libgnustep-gui-dev (>= 0.26) > > > > I also tried copying the .debs and creating a local repository myself, > > as I do with semi-automatically with pbuilder. This repository is > > also ignored if I add it to extramirrors under the experimental > > distribution. > > I think this is due to how experimental pinning is handled by apt. If > you upload a new package revision (let's say 0.26.2-2+dom) in > debomatic, and then you change the builddep command to request > libgnustep-gui-dev (>= 0.26-2+dom), it should work. I don't think I understand. These commands result in successful builds: builddep gnustep-base_1.25.1-2 experimental libicu-dev (>= 60.2) builddep lynkeos.app_2.10+dfsg1-3 experimental libavcodec-dev (>= 7:4.0) However, if I build/upload (in debomatic) gnustep-make/2.7.0-4+dom both for experimental/unstable these commands fail: builddep mknfonts.tool_0.5-12 experimental gnustep-make (>= 2.7.0-4+dom) builddep mknfonts.tool_0.5-12 unstable gnustep-make (>= 2.7.0-4+dom) That's because these versions of icu/ffmpeg are available in the official archive while the local debomatic repository is not taken into account. I don't believe it has anything to do with pinning.
