[Pkg-electronics-devel] Latest KLayout

Thomas Dorch thomaspdorch at gmail.com
Tue Aug 30 21:50:41 BST 2022


Hi,

I re-patched #977415 using the patch queue, but still wasn't able to get
#977416 set up as a patch. I think this has to do with it modifying the
debian/rules file and it's somehow getting unapplied during gbp's patching
process.
Instead, I added a git commit and set the author and date the same way as
the other patch, but on master rather than on the patch queue. Is this
sufficient? If not, do you have any idea how I can get the patch working on
patch queue?

-Thomas


On Sun, Aug 28, 2022, 12:41 AM Carsten Schoenert <c.schoenert at t-online.de>
wrote:

> Hello,
>
> Am 28.08.22 um 02:31 schrieb Thomas Dorch:
> > I have incorporated one of the patches
> > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977415), but am
> > having trouble applying the other
> > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977416 ). gbp
> > buildpackage fails when trying to apply this patch with the error: "the
> > patch has fuzz which is not allowed, or is malformed". I'll keep trying
> > to get this working but is there a way to add these patches via to the
> > git history rather than as files in the debian/patches folder?
>
> well gbp does nothing here, it's plain git workflow needed to get things
> together.
>
> The patch is rather trivial so I'd do simply applying the modifications
> manually and and use git commit (--amend) together with --author and
> --date to set the authorship of origin while working on the patch queue.
>
> --
> Regards
> Carsten
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-electronics-devel/attachments/20220830/754770a9/attachment.htm>


More information about the Pkg-electronics-devel mailing list