Re: Looking for example package that uses multiple source tarballs

2020-06-27 Thread Qianqian Fang
On 6/26/20 12:00 PM, Pierre Gruet wrote: As you guessed, the fact that you got the old version number 1.9.1 in the name of the orig tarball is because "debian" is provided as the third argument concerning the first tarball, as the above link explains: it forces the use of the version number

Re: Looking for example package that uses multiple source tarballs

2020-06-26 Thread Pierre Gruet
Hi Qianqian, Le 26/06/2020 à 04:20, Qianqian Fang a écrit : > > [...] > > thanks Pierre for the comments and sample project, very helpful! > You are welcome! > > [...] > > I am not sure if it is related, but i have to change my debian/changelog > version to a lower version number (1.9.1) in

Re: Looking for example package that uses multiple source tarballs

2020-06-25 Thread Qianqian Fang
On 6/25/20 4:09 PM, Pierre Gruet wrote: I think you should provide some options ("opts=..."): for instance, a component name should be provided for the two last parts. You can look at the manpage of uscan, it provides some examples of watch files for multiple upstream tarballs. As you are doing

Re: Looking for example package that uses multiple source tarballs

2020-06-25 Thread Pierre Gruet
Hi Qianqian, Le 25/06/2020 à 21:02, Qianqian Fang a écrit : > hi everyone, > > I am working on packaging a matlab/octave toolbox that involves multiple > source tarballs > > https://salsa.debian.org/pkg-octave-team/octave-iso2mesh > > [...] > > I notice that debian/watch file supports