Bug#837167: RFS: aiscm/0.6.2-2
On Mon, 2 Jan 2017, Andrey Rahmatullin wrote: Uploaded, thanks! -- WBR, wRAR Thanks for reviewing the aiscm package. Your comments have helped improve the package a lot. Regards Jan
Bug#837167: RFS: aiscm/0.6.2-2
Uploaded, thanks! -- WBR, wRAR signature.asc Description: PGP signature
Bug#837167: RFS: aiscm/0.6.2-2
On Sun, 1 Jan 2017, Andrey Rahmatullin wrote: You have override_dh_makeshlibs: # NOOP to prevent debuild from invoking ldconfig Debuild doesn't invoke ldconfig. If it's done to avoid adding an ldconfig trigger you should explain that and explain why it is added because it's not clear why do you need manual actions here. -- WBR, wRAR Ok, I have changed the documentation as follows: override_dh_makeshlibs: # NOOP to prevent debuild from adding an ldconfig trigger. # aiscm does not install shared libraries in the library path, # it merely installs native extensions to be loaded by the Guile interpreter. The extension builds shared libraries but does not install them in the library path.
Bug#837167: RFS: aiscm/0.6.2-2
You have override_dh_makeshlibs: # NOOP to prevent debuild from invoking ldconfig Debuild doesn't invoke ldconfig. If it's done to avoid adding an ldconfig trigger you should explain that and explain why it is added because it's not clear why do you need manual actions here. -- WBR, wRAR signature.asc Description: PGP signature
Bug#837167: RFS: aiscm/0.6.2-2
On Thu, 22 Dec 2016, Andrey Rahmatullin wrote: On Thu, Dec 22, 2016 at 12:32:20PM +, Jan Wedekind wrote: There is one final unresolved issue: "hardening-no-fortify-functions" (certainty: wild-guess) even though GCC is now run with hardening options. Can I leave it as it is, do I need to override the lintian warning, or do I need to file a bug report for the lintian warning? You should use blhc to check if the flags are passed correctly for all cases. This tag is sometimes a false positive. Ok, blhc aiscm*.build does not output anything. I verified that blhc works by running it on an edited build file, too.
Bug#837167: RFS: aiscm/0.6.2-2
On Thu, Dec 22, 2016 at 12:32:20PM +, Jan Wedekind wrote: > There is one final unresolved issue: "hardening-no-fortify-functions" > (certainty: wild-guess) even though GCC is now run with hardening options. > Can I leave it as it is, do I need to override the lintian warning, or do I > need to file a bug report for the lintian warning? You should use blhc to check if the flags are passed correctly for all cases. This tag is sometimes a false positive. -- WBR, wRAR signature.asc Description: PGP signature
Bug#837167: RFS: aiscm/0.6.2-2
On Sat, 17 Dec 2016, Andrey Rahmatullin wrote: You shouldn't put upstream changes into d/changelog. I have removed those by the way. Your package has quite a lot of lintian problems, some of them are even listed on the mentors, page. There is one final unresolved issue: "hardening-no-fortify-functions" (certainty: wild-guess) even though GCC is now run with hardening options. Can I leave it as it is, do I need to override the lintian warning, or do I need to file a bug report for the lintian warning? Regards Jan
Bug#837167: RFS: aiscm/0.6.2-2
On Sat, 17 Dec 2016, Andrey Rahmatullin wrote: You shouldn't put upstream changes into d/changelog. Your package has quite a lot of lintian problems, some of them are even listed on the mentors, page. Did you see them? Here is the full list: W: aiscm source: diff-contains-substvars debian/substvars I: aiscm source: debian-watch-file-is-missing I: aiscm: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-v4l2.so.0.0.0 I: aiscm: hardening-no-bindnow usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-ffmpeg.so.0.0.0 I: aiscm: hardening-no-bindnow usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-image.so.0.0.0 I: aiscm: hardening-no-bindnow usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-jit.so.0.0.0 I: aiscm: hardening-no-bindnow ... use --no-tag-display-limit to see all (or pipe to a file/program) I: aiscm: extended-description-is-probably-too-short X: aiscm: privacy-breach-generic usr/share/doc/aiscm/index.html (https://img.shields.io/github/license/wedesoft/aiscm.png) X: aiscm: privacy-breach-generic usr/share/doc/aiscm/index.html (https://travis-ci.org/wedesoft/aiscm.png?branch=master) X: aiscm: privacy-breach-generic usr/share/doc/aiscm/index.html (https://img.shields.io/github/release/wedesoft/aiscm.png) X: aiscm: privacy-breach-generic ... use --no-tag-display-limit to see all (or pipe to a file/program) I: aiscm: arch-dep-package-has-big-usr-share 3285kB 79% I: aiscm: possible-documentation-but-no-doc-base-registration W: aiscm: package-has-unnecessary-activation-of-ldconfig-trigger Yes, I noticed the lintian issues on the mentors page. Sorry for not looking into it earlier. You have an autopkgtest file with "make check" in it. How is that supposed to check the installed package? Ok, I misunderstood how autopkgtest works. I have removed the autopkgtest use for the moment. The current recommended debhelper compat level is 10. Ok, I have updated the debhelper level to 10. The updated package is here: https://mentors.debian.net/package/aiscm Regards Jan
Bug#837167: RFS: aiscm/0.6.2-2
You shouldn't put upstream changes into d/changelog. Your package has quite a lot of lintian problems, some of them are even listed on the mentors, page. Did you see them? Here is the full list: W: aiscm source: diff-contains-substvars debian/substvars I: aiscm source: debian-watch-file-is-missing I: aiscm: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-v4l2.so.0.0.0 I: aiscm: hardening-no-bindnow usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-ffmpeg.so.0.0.0 I: aiscm: hardening-no-bindnow usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-image.so.0.0.0 I: aiscm: hardening-no-bindnow usr/lib/x86_64-linux-gnu/guile/2.0/extensions/libguile-aiscm-jit.so.0.0.0 I: aiscm: hardening-no-bindnow ... use --no-tag-display-limit to see all (or pipe to a file/program) I: aiscm: extended-description-is-probably-too-short X: aiscm: privacy-breach-generic usr/share/doc/aiscm/index.html (https://img.shields.io/github/license/wedesoft/aiscm.png) X: aiscm: privacy-breach-generic usr/share/doc/aiscm/index.html (https://travis-ci.org/wedesoft/aiscm.png?branch=master) X: aiscm: privacy-breach-generic usr/share/doc/aiscm/index.html (https://img.shields.io/github/release/wedesoft/aiscm.png) X: aiscm: privacy-breach-generic ... use --no-tag-display-limit to see all (or pipe to a file/program) I: aiscm: arch-dep-package-has-big-usr-share 3285kB 79% I: aiscm: possible-documentation-but-no-doc-base-registration W: aiscm: package-has-unnecessary-activation-of-ldconfig-trigger You have an autopkgtest file with "make check" in it. How is that supposed to check the installed package? The current recommended debhelper compat level is 10. -- WBR, wRAR signature.asc Description: PGP signature
Bug#837167: RFS: aiscm/0.6.2-2
On Wed, 14 Dec 2016, Andrey Rahmatullin wrote: On Tue, Dec 13, 2016 at 10:48:32PM +, Jan Wedekind wrote: Other problems: - the package doesn't build in a clean sid chroot: not ok 19 - Check a pixel in the first video frame of the video (ERROR: In procedure #f: Wrong type (expecting ffmpeg): #) FAIL: test_ffmpeg.scm 19 - Check a pixel in the first video frame of the video (ERROR: In procedure #f: Wrong type (expecting ffmpeg): #) I have not managed to reproduce the failing test (even using pbuilder). Can you let me know how you created the chroot environment with the failing test? It's an usual sbuild sid-amd64 chroot. Ok, thanks. I managed to reproduce the failing test. There seems to be a new side effect in ffmpeg. The test passes when the pixel is read immediately after the image is decoded. I have uploaded the modified package here: https://mentors.debian.net/package/aiscm Regards Jan
Bug#837167: RFS: aiscm/0.6.2-2
On Tue, Dec 13, 2016 at 10:48:32PM +, Jan Wedekind wrote: > > Other problems: > > - the package doesn't build in a clean sid chroot: > > not ok 19 - Check a pixel in the first video frame of the video (ERROR: In > > procedure #f: Wrong type (expecting ffmpeg): #) > > FAIL: test_ffmpeg.scm 19 - Check a pixel in the first video frame of the > > video (ERROR: In procedure #f: Wrong type (expecting ffmpeg): # > smob 55c544fd8520>) > > I have not managed to reproduce the failing test (even using pbuilder). Can > you let me know how you created the chroot environment with the failing > test? It's an usual sbuild sid-amd64 chroot. -- WBR, wRAR signature.asc Description: PGP signature
Bug#837167: RFS: aiscm/0.6.2-2
On Tue, 13 Dec 2016, Andrey Rahmatullin wrote: On Mon, Dec 12, 2016 at 09:51:36PM +, Jan Wedekind wrote: There is no such package in the archive. Is this a new package? If yes, please follow the procedures outlined at https://mentors.debian.net/intro-maintainers Hi Andrey, Thanks for your email. The version 0.6.2-2 is three months old. Here is the most recent version: http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1-1.dsc http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1.orig.tar.gz http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1-1.debian.tar.xz It has the same problem, you need to open the ITP bug and close it in the first and the only changelog entry, see https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#newpackage if you've missed that part in the mentors link I gave you. Ok, thanks. I filed an ITP here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848078 Other problems: - the package doesn't build in a clean sid chroot: not ok 19 - Check a pixel in the first video frame of the video (ERROR: In procedure #f: Wrong type (expecting ffmpeg): #) FAIL: test_ffmpeg.scm 19 - Check a pixel in the first video frame of the video (ERROR: In procedure #f: Wrong type (expecting ffmpeg): #) I have not managed to reproduce the failing test (even using pbuilder). Can you let me know how you created the chroot environment with the failing test? - you shouldn't list shared lib dependencies explicitly, they should be found automatically Ok, thanks for letting me know. I removed the explicit shared lib dependencies. - current standards version is 3.9.8. Ok, I updated the version number. I tried to upload it to mentors.debian.net but I didn't manage to figure out how to create a "changes" file as required by "dput". By building the package. Let me know if it is necessary to upload it to mentors.debian.net in which case I'll have another look at it. No, it is not necessary, as you already have a dget-able link. I managed to upload the updated version aiscm-0.9.2 to mentors.debian.net (not sure why I didn't notice the "changes" file before): https://mentors.debian.net/package/aiscm Regards Jan
Bug#837167: RFS: aiscm/0.6.2-2
On Mon, Dec 12, 2016 at 09:51:36PM +, Jan Wedekind wrote: > > There is no such package in the archive. Is this a new package? If yes, > > please follow the procedures outlined at > > https://mentors.debian.net/intro-maintainers > > > > Hi Andrey, > Thanks for your email. The version 0.6.2-2 is three months old. Here is the > most recent version: > >http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1-1.dsc > > http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1.orig.tar.gz > > http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1-1.debian.tar.xz It has the same problem, you need to open the ITP bug and close it in the first and the only changelog entry, see https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#newpackage if you've missed that part in the mentors link I gave you. Other problems: - the package doesn't build in a clean sid chroot: not ok 19 - Check a pixel in the first video frame of the video (ERROR: In procedure #f: Wrong type (expecting ffmpeg): #) FAIL: test_ffmpeg.scm 19 - Check a pixel in the first video frame of the video (ERROR: In procedure #f: Wrong type (expecting ffmpeg): #) - you shouldn't list shared lib dependencies explicitly, they should be found automatically - current standards version is 3.9.8. > I tried to upload it to mentors.debian.net but I didn't manage to figure out > how to create a "changes" file as required by "dput". By building the package. > Let me know if it is > necessary to upload it to mentors.debian.net in which case I'll have another > look at it. No, it is not necessary, as you already have a dget-able link. -- WBR, wRAR signature.asc Description: PGP signature
Bug#837167: RFS: aiscm/0.6.2-2
Lyn/Carly On Mon, 12 Dec 2016, Andrey Rahmatullin wrote: Control: tags -1 + moreinfo On Fri, Sep 09, 2016 at 05:29:24PM +0100, Jan Wedekind wrote: Dear mentors, I am looking for a sponsor for my package "aiscm": * Package name: aiscm Version : 0.6.2-2 Upstream Author : Jan Wedekind * URL : http://wedesoft.github.io/aiscm/ * License : GPL-3+ Section : lisp There is no such package in the archive. Is this a new package? If yes, please follow the procedures outlined at https://mentors.debian.net/intro-maintainers Hi Andrey, Thanks for your email. The version 0.6.2-2 is three months old. Here is the most recent version: http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1-1.dsc http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1.orig.tar.gz http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1-1.debian.tar.xz I tried to upload it to mentors.debian.net but I didn't manage to figure out how to create a "changes" file as required by "dput". Let me know if it is necessary to upload it to mentors.debian.net in which case I'll have another look at it. Alternatively, one can download the package with dget using this command: dget -x http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.6.2-2.dsc There is no such file, btw. The updated URL is. dget -x http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.9.1-1.dsc -- WBR, wRAR
Bug#837167: RFS: aiscm/0.6.2-2
Control: tags -1 + moreinfo On Fri, Sep 09, 2016 at 05:29:24PM +0100, Jan Wedekind wrote: > Dear mentors, > > I am looking for a sponsor for my package "aiscm": > > * Package name: aiscm > Version : 0.6.2-2 > Upstream Author : Jan Wedekind > * URL : http://wedesoft.github.io/aiscm/ > * License : GPL-3+ > Section : lisp There is no such package in the archive. Is this a new package? If yes, please follow the procedures outlined at https://mentors.debian.net/intro-maintainers >Alternatively, one can download the package with dget using this command: > >dget -x > http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.6.2-2.dsc There is no such file, btw. -- WBR, wRAR signature.asc Description: PGP signature
Bug#837167: RFS: aiscm/0.6.2-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "aiscm": * Package name: aiscm Version : 0.6.2-2 Upstream Author : Jan Wedekind * URL : http://wedesoft.github.io/aiscm/ * License : GPL-3+ Section : lisp It builds those binary packages: aiscm - Guile computer vision extension aiscm is a real-time computer vision extension for the Guile programming language. Performance in Scheme is achieved by means of an AMD64 JIT compiler. To access further information about this package, please visit the following URL: https://github.com/wedesoft/aiscm/tree/RFS Alternatively, one can download the package with dget using this command: dget -x http://wedesoft.github.io/aiscm/apt/pool/main/a/aiscm/aiscm_0.6.2-2.dsc More information about aiscm can be obtained from http://wedesoft.github.io/aiscm/. Changes since the last upload: - Make releases for different distros - fix package dependencies (do not use aliases) - Pulse audio input and output using asynchronous API - ring buffer for first-in first-out (FIFO) buffering of data - improved documentation Regards, Jan Wedekind
