On Fri, Sep 01, 2017 at 10:56:39PM +0200, Sandro Mani wrote: > Hi > > I've got another weird situation: I wanted to get pjproject building > again, rebased and added necessary patches, did the scratch build, > and all looked good [1]. So I went ahead and committed the result, > fired off the build, but to my surprise that build failed while > applying the patches [2]. I thought maybe upstream did a respin of > the source tarball and that I was using another one that what was > uploaded with fedpkg new-source, so I did a fedpkg sources, and for > some reason that also downloaded obsolete version of some of the > patches: > > $ fedpkg sources > Downloading pjproject-2.6.tar.bz2 > ######################################################################## > 100.0% [...] > I suspect that this is why the build are failing, because it is > still using the obsolete patches, and not what I committed [3]. > > Any idea what's going on here? I think you've basically analyzed it correctly. The patches have been added to the ‘sources’ file (and so are pulled from the lookaside cache). This is of course wrong. The new patches are in git, but these are overwritten by the lookaside cache. The easiest thing is to simply edit the ‘sources’ file and remove all the lines from it which mention a patch -- in the currently checked in ‘sources’ file basically all the lines except the very first one. It should work after you commit that change. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
