Re: same upstream version but different orig.tar.gz

Hi Ferenc Wágner, > > > You can work around this locally by rewriting your .changes files; the > > > changestool utility in the reprepro packages can help with that.  But > > > you won't be able to upload different files with the same name.  The > > > usual solution is adding a numeric part to

Re: same upstream version but different orig.tar.gz

Herbert Fortes writes: >> You can work around this locally by rewriting your .changes files; the >> changestool utility in the reprepro packages can help with that.  But >> you won't be able to upload different files with the same name.  The >> usual solution is adding a numeric

Re: same upstream version but different orig.tar.gz

Hi, > > You can work around this locally by rewriting your .changes files; the > changestool utility in the reprepro packages can help with that.  But > you won't be able to upload different files with the same name.  The > usual solution is adding a numeric part to the version after +dfsg, like

Re: same upstream version but different orig.tar.gz

Herbert Fortes writes: > So I did a new Debian revision after the +dfsg.orig.tar.gz file be > replaced. > > I just did a 'debdiff' to check the differences between the Debian > revisions, and of course, the output is: > > dpkg-source: error: file

Re: same upstream version but different orig.tar.gz

Hello, On Tue, Aug 02, 2016 at 08:47:06PM -0300, Herbert Fortes wrote: > First I removed libAvKys/Plugins/VirtualCamera/ > directory. Generated a new .symbols file and > uploaded to experimental. Then I tested the > software. It did not run. An email to the upstream > was sent. > > Only