Looking for example package that uses multiple source tarballs

[Qianqian Fang]

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

this toolbox contains a number of built-in utilities that are linked to 
the source repo via submodules


https://github.com/fangq/iso2mesh/tree/master/tools

however, the github release tarball does not contain these submodules 
and I must combine those to build the package.


I previous had used a shell script 
 
to merge the source code trees and create a single .orig.tar.gz, 
however, I was told that using *debian/repack* and *uscan* is the 
preferred way to perform changes like this.


I notice that debian/watch file supports multiple source components, so 
I wrote the below watch file:


|
|

|version=3||
||
||opts="dversionmangle=s/\+dfsg\.\d+$//,filenamemangle=s/\S+\/v?(\S+)\.tar\.gz/iso2mesh-$1\.tar\.gz/" 
\||

||    https://github.com/fangq/iso2mesh/tags .*/v?(\d\S+)\.tar\.gz \||
||    debian debian/repack||
||
||https://github.com/fangq/cork/releases 
.*/v(\d[\d\.]*)\.(?:tar.gz|tar.bz2|tar.xz)||
||https://github.com/fangq/meshfix/releases 
.*/v(\d[\d\.]*)\.(?:tar.gz|tar.bz2|tar.xz)|



but when I ran*uscan --verbose*, it only downloaded/repacked the main 
source file, but refused to download the components


|...||
||uscan info: Matching target for filenamemangle: 
/fangq/iso2mesh/archive/v1.9.5.tar.gz||

||uscan info: Download filename (filenamemangled): iso2mesh-1.9.5.tar.gz||
||...||
||Removing non-DFSG-free files:||
||removed '/tmp/tmp.uNMHl78FqP/octave-iso2mesh-1.9.1.orig/bin/README.txt'||
||Rebuilding DFSG-free upstream source tarball:||
||Moving completed upstream tarball to 
‘../octave-iso2mesh_1.9.1.orig.tar.gz’:||

||...||
||uscan info: Newest upstream tarball version selected for download 
(uversionmangled): 0.9||

||uscan info: Download filename (filenamemangled): v0.9.tar.gz||
||*uscan info: Newest version of octave-iso2mesh on remote site is 0.9, 
local version is 1.9.1*||

||uscan info:    => Only older package available from||
||https://github.com/fangq/cork/archive/v0.9.tar.gz||
||...||
||uscan info: Scan finished|


I am wondering if you know any sample package that uses repack/uscan to 
combine multiple source packages? The uscan manpage mentioned about MUT, 
but I could not find a working example.


thanks, let me know if you have any suggestions.

Qianqian

Re: Looking for example package that uses multiple source tarballs

[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 some repack, I guess you will add some suffix to the
version number (like "+dfsg"), and to do so you should need to provide
the "oversionmangle=..." option for the first tarball. Examples are
shown in uscan's manpage.
I recently packaged libaparapi-java, which is not yet in Debian but
which you can get from its Salsa repository

https://salsa.debian.org/med-team/libaparapi-java

Running "uscan --verbose" will allow you to get three tarballs : a main
one and two components.


thanks Pierre for the comments and sample project, very helpful!

after reading your watch file and uscan's manual page more carefully, I 
was able to download all 3 components using the below watch file


https://salsa.debian.org/pkg-octave-team/octave-iso2mesh/-/blob/master/debian/watch

after running *uscan --verbose*, a bunch of files/folders were created 
in the above directory, see


|drwxrwxr-x  5 fangq fangq 4096 Jun 25 22:03 
octave-iso2mesh-1.9.5+dfsg1||
||-rw-rw-r--  1 fangq fangq  409 Jun 25 22:03 
octave-iso2mesh_1.9.5+dfsg1-0ubuntu1.dsc||
||-rw-rw-r--  1 fangq fangq 5500 Jun 25 22:03 
octave-iso2mesh_1.9.5+dfsg1-0ubuntu1.debian.tar.xz||
||lrwxrwxrwx  1 fangq fangq   20 Jun 25 22:03 
octave-iso2mesh_1.9.5+dfsg1.orig-meshfix.tar.gz -> meshfix-1.2.2.tar.gz||

||-rw-rw-r--  1 fangq fangq  2092675 Jun 25 22:03 meshfix-1.2.2.tar.gz||
||-rw-rw-r--  1 fangq fangq  135 Jun 25 22:03 
octave-iso2mesh_1.9.5+dfsg1.orig.tar.gz||
||-rw-rw-r--  1 fangq fangq 5500 Jun 25 22:03 
octave-iso2mesh_1.9.1-1.debian.tar.xz||
||lrwxrwxrwx  1 fangq fangq   15 Jun 25 22:03 
octave-iso2mesh_1.9.5+dfsg1.orig-cork.tar.gz -> cork-0.9.tar.gz||

||-rw-rw-r--  1 fangq fangq   292728 Jun 25 22:03 cork-0.9.tar.gz||
||-rw-rw-r--  1 fangq fangq   941881 Jun 25 22:03 
octave-iso2mesh_1.9.1.orig.tar.gz||

||-rw-rw-r--  1 fangq fangq 28793215 Jun 25 22:03 iso2mesh-1.9.5.tar.gz|

the final merged source folder, however, only contains the source codes 
of the two components, but not from the main package, see


*|$~/space/git/Temp/pkg$ ls -lt octave-iso2mesh-1.9.5+dfsg1|*|
||total 12||
||drwxrwxr-x 4 fangq fangq 4096 Jun 25 22:03 debian||
||drwxrwxr-x 7 fangq fangq 4096 Jun 20 12:44 meshfix||
||drwxrwxr-x 5 fangq fangq 4096 Oct  1  2019 cork|

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 order to let uscan download 
the new release (1.9.5). however, both .tar.xz files are empty (except 
the debian/ folder)


|octave-iso2mesh_1.9.1-1.debian.tar.xz
octave-iso2mesh_1.9.5+dfsg1-0ubuntu1.debian.tar.xz
|

but the *octave-iso2mesh_1.9.1.orig.tar.gz* file is correctly repacked 
and contains all needed files.


I am wondering if anyone notice something wrong in repack or watch 
script? my repack file was slightly modified from 
https://wiki.debian.org/BenFinney/software/repack


another minor thing is the "|-0ubuntu1|" suffix. I am testing the 
packaging in a Ubuntu 18.04 box, is there a way to remove that?


my packaging files are committed at 
https://salsa.debian.org/pkg-octave-team/octave-iso2mesh/ 
 



much appreciated!

Qianqian

Re: Looking for example package that uses multiple source tarballs

[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 multiple source components, so
> I wrote the below watch file:
> 
> |
> |
> 
> |version=3||
> ||
> ||opts="dversionmangle=s/\+dfsg\.\d+$//,filenamemangle=s/\S+\/v?(\S+)\.tar\.gz/iso2mesh-$1\.tar\.gz/"
> \||
> ||    https://github.com/fangq/iso2mesh/tags .*/v?(\d\S+)\.tar\.gz \||
> ||    debian debian/repack||
> ||
> ||https://github.com/fangq/cork/releases
> .*/v(\d[\d\.]*)\.(?:tar.gz|tar.bz2|tar.xz)||
> ||https://github.com/fangq/meshfix/releases
> .*/v(\d[\d\.]*)\.(?:tar.gz|tar.bz2|tar.xz)|
> 

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 some repack, I guess you will add some suffix to the
version number (like "+dfsg"), and to do so you should need to provide
the "oversionmangle=..." option for the first tarball. Examples are
shown in uscan's manpage.

> 
> but when I ran*uscan --verbose*, it only downloaded/repacked the main
> source file, but refused to download the components
> 
> [...]
> 
> 
> I am wondering if you know any sample package that uses repack/uscan to
> combine multiple source packages? The uscan manpage mentioned about MUT,
> but I could not find a working example.
>

I recently packaged libaparapi-java, which is not yet in Debian but
which you can get from its Salsa repository

https://salsa.debian.org/med-team/libaparapi-java

Running "uscan --verbose" will allow you to get three tarballs : a main
one and two components.

> 
> thanks, let me know if you have any suggestions.
> 
> Qianqian
> 
> 

Regards,
Pierre

Re: lasagne and keras

[Christian Kastner]

On 2020-06-24 19:13, Stephen Sinclair wrote:
> I have submitted an issue upstream but there has been no response, and
> the last real non-trivial commit was in 2018.  I believe this is
> because it depends on Theano, which we know well is already
> end-of-life, so it's possible the authors have lost interest.
> 
> So, although I'd like to fix the strange bug with python mock, I feel
> this may not be worth worrying about if there is no cooperation from
> upstream.

In my own personal experience, I have found that the maintenance burden
of abandoned software is simply not worth the (increasing) effort if the
package has a very low popcon, as it does in this case.

Sure, if I had unlimited time, I would try to salvage it. But my time is
limited, and it is better invested in new projects, or projects that
actually reach users. Even more so when the project in question has a
known EOL, and has reached it.

> If so, this would be the first package I abandon, what is the correct
> procedure? Do I just file as orphaned?
Normally, yes, you would just file as orphaned.

However, in this particular case, with the software (or one of its
dependencies) being EOL'ed, I would consider outright asking for its
removal from the archive.

You might orphan it now, and ask for removal before the next release in
case nobody steps up.