Hi Arturo, it took a long time, but finally I got most of the problems with audio-recorder solved. I'm in contact and also have write access to the source code now. So if there are further problems, it should no be too hard to fix them. The only thing I have no solution for at the moment is the proablem with the watch file. I think this it not too important, but please let me know what you think about it. Here is the link to the new package: https://mentors.debian.net/package/audio-recorder Yours David On 18.08.2016 13:22, David Rabel wrote: > Hi Arturo, > > thank you for your email. I wrote an email to the upstream developer, > asking him to change a few things. :-) > > > On 16.08.2016 09:47, Arturo Borrero Gonzalez wrote: >> On 15 August 2016 at 02:23, David Rabel <David.Rabel@noresoft.com> wrote: >> The Makefile.in.in file seems like a file that should not be included >> in a binary package. >> That file is usually used (wit just one '.in' in the name) to build >> the [upstream] software package. See the newmaint guide [1]. >> >> The final debian binary package should only include the audio-recorder >> tool, and not any other >> stuff used to build the package itself. > > It is not included in the binary package, only in the source package. > Still this leads to a lintian error. I also informed upstream about > this, maybe he will just fix it. If not, it is probably OK to copy the > Makefile.in.in of my intltool installation to the po folder. > > >> Please, talk to GNOME people, since I'm not familiar with their > environment. >> >> The dpkg-shlibdeps is a warning to take into account, but is not a >> blocker for the package to join debian. > > I will have a closer look at it. > > >>> 5) I did not know how to make the watch file work. Because at the >>> moment, the launchpad site [2] is not updated anymore, so I had to pick >>> the tar.gz manually from the ppa. Maybe the easiest is to ask the >>> maintainer to update that site at least when he releases a new version. >> >> Where are the upstream source? Is there any SCM (git). >> >> If launchpad is not updated anymore, where is the code living now? >> >> Perhaps you could suggest upstream to migrate to github or something similar. > > The source is still on launchpad. Only the launchpad project site is not > updated anymore. > So, the source code is here: [1]. > The projects' site is not updated: [2] > And the current tarball I had to pick from the ppa: [3] > > I asked the upstream maintainer to update the projects' site again, at > least to put the tarball of the current version there. > > > Yours > David > > [1] https://code.launchpad.net/~audio-recorder/audio-recorder/trunk > [2] https://launchpad.net/audio-recorder > [3] https://launchpad.net/~audio-recorder/+archive/ubuntu/ppa >
Attachment:
signature.asc
Description: OpenPGP digital signature