Nikolaus Rath writes ("Bug#850005: dgit push without dgit build-source"):
> On Jan 04 2017, Nikolaus Rath <[email protected]> wrote:
> > It seems to me that something is wrong with the tree rather than with
> > git-dpm or dgit. I think this may be a consequence of the tree having
> > been imported from SVN. I will try to manually restore the missing files
> > in the master branch (bypassing git-dpm).
> >
> > If this is indeed the problem, then this potentially affects all
> > packages from the debian Python modules team (they've all been batch
> > converted from svn-buildpackage).
>
> The following indeed fixed the problem:
>
> $ git checkout master
> $ git checkout upstream src/llfuse.egg-info/
> $ git commit -m "Restored mysteriously disappeared upstream files."
> [master 29625] Restored mysteriously disappeared upstream files.
> 6 files changed, 192 insertions(+)
> create mode 100644 src/llfuse.egg-info/PKG-INFO
> create mode 100644 src/llfuse.egg-info/SOURCES.txt
> create mode 100644 src/llfuse.egg-info/dependency_links.txt
> create mode 100644 src/llfuse.egg-info/requires.txt
> create mode 100644 src/llfuse.egg-info/top_level.txt
> create mode 100644 src/llfuse.egg-info/zip-safe
Right, OK. I think that means I should close this bug now.
> I'll do some more digging to figure out how these files disappeared and
> then send a heads up to the other dpmt people.
Let me know if you have any other oddities, thanks.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
