On 19/01/17 19:36, Ian Jackson wrote:
I think such a tool would be very useful in general, if it could be
used for individual users.
I see no reason why it couldn't be used by an individual user.
I have posted the current code at .
https://github.com/plugwash/dscdirtogit (import tool)
First let me introduce myself, I am Peter Michael Green, cofounder of the
Raspbian project. I have quite a bit of experiance with Debian
Some time ago I put together what I call the "autoforwardporter". The aim of
this is to take downstream changes and apply them on top of new debian uploads.
I haven't run dgit's dsc importer on a whole historical archive but
Peter Green of Raspian has been running it and filing bugs. I haven't
seen such a bug recently so I hope it has been working for all the
packages he's seen.
I haven't really been doing large scale importing, I have just
I have recently started pushing source for packages where we carry
modifications for in raspbian to github. The packages are imported into git
using dgit.
However I have discovered that this is not possible for all packages. In
particular github rejects files over 100 megabytes and the
I recently discovered some unusual behaviour in a source package I was working
on.
I was using some scripts I put together myself to generate patch series for a
debian package.
dgit claimed I was creating a new symlink and that creation of a new symlink could not be
represented by 3.0
.
Secondly AIUI git-lfs stores every version of the file seperately. If so then
one would very quickly blow through the default storage and bandwidth
limitations for githubs lfs offering.
On March 9, 2017 7:42:20 AM PST, peter green <plugw...@p10link.net> wrote:
I have recently started p
As part of my dgit based autoforwardporter I want to add a script that will
de-fuzz patches with fuzz and remove patches that cannot be applied.
To do this I need the "upstream" source tree. However the process of extracting
the upstream source is quite fiddly, there may be multiple tarballs
On 27/12/17 23:42, Paul Wise wrote:
On Thu, Dec 28, 2017 at 5:41 AM, peter green wrote:
Unfortunately there doesn't seem to be a good way to securely retrive a dsc
from snapshot.debian.org given a package name and version number.
At this time there isn't any good way to do that securely