Bug#637079: Bug #637079 ITP: python-visvis -- Python/OpenGL based 1D to 4D object oriented plotting software
On 14/08/11 17:18, Aron Xu wrote: No, I don't mean running lintian within pbuilder, but just build the package in pbuilder. By simply running debuild on your system, there are many things can influence the build result, for instance the packages you have installed but not declared in Build-Depends, and the environment variables you have set but not declared in debian/rules. While with pbuilder, it makes a clean chroot, which means a minimal amount of packages installed and a clean/default environment variables, thus pbuilder can help you test if everything behaves correctly. After building your package in pbuilder, you can check the built packages outside the chroot, lintian does not have the problem to perform checks. Thanks, I have now learned more about how pdebuild works. With my earlier method, I hadn't really checked the pdebuild package. I was actually just fooling myself, and was rechecking the 'debuild' package. The pdebuild package actually ends up in /var/cache/pbuilder/result, which I didn't know... Thanks for your work, but you forgot to add a minimum version requirement to Build-Depends, that is "python (>= 2.6.6-3~)". This is documented on the wiki page, please double check. Done. Thanks. OK, great. And please be aware that no upstream changelog isn't a critical issue to get your package into Debian. So you don't need to wait for a new release before uploading the first version of your package. Ok. Upstream seems to have a nice HTML changelog. I know there is Debian documentation about how to treat this case, so I'll get that done even though it is not a strict requirement. Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e4816c3.1080...@gmail.com
Bug#637079: Bug #637079 ITP: python-visvis -- Python/OpenGL based 1D to 4D object oriented plotting software
On 14/08/11 15:46, Aron Xu wrote: On Sun, Aug 14, 2011 at 21:25, Torquil Macdonald Sørensen wrote: Thanks for checking the package! Would it be possible to see your build log? Attached. I can successfully build it on both my amd64 and i386 computers. On the amd64 I've also built it successfully using pbuilder. I haven't yet been able to do the pbuilder test on the i386 due to a pbuilder bug regarding the proc filesystem. When I run lintian I only get: $ lintian -IE --pedantic --show-overrides python-visvis_1.5-1_amd64.changes P: python-visvis: no-upstream-changelog and the same thing on my i386 computer. Here is the procedure I used on both computers: $ dget http://mentors.debian.net/debian/pool/main/p/python-visvis/python-visvis_1.5-1.dsc $ dpkg-source -x python-visvis_1.5-1.dsc $ cd python-visvis-1.5 $ debuild $ cd .. $ lintian -IE --pedantic --show-overrides python-visvis_1.5-1_amd64.changes Can you run check for a pbuilder build, instead of a local debuild? Because your own environment may influence the build result. Thanks for the dh_python2 info. I'm on it! :-) Let me know when you have finished it, :-) Finished! Ok, I think your build problem appeared because "python" was not included as a Build-Depends. Your build log indicated an error message where the program "pyversions" was not found. I actually got the same error message in my pbuilder build log without noticing it before. After including python as a Build-Depends, I no longer have this problem. You suggested that I should run the lintian command within the chroot. I have not yet figured out how to do this, but will investigate some man pages. Even so, I am sufficiently confident that I have fixed the problem to upload this once more to mentors.debian.net. My apologies if the problem is still present. So now I have included python as a Build-Depends, and I think I have followed the instructions for converting to dh_python2. In this case it seems to be as simple as to just obey the recommendations for the Build-Depends and Depends, as well as to include the option --with python2 for the dh commands that are run in the rules script. I have uploaded a new version (with the same version number). Due to the new "expo" system on mentors.debian.net I had to first delete the old package, but the URL should be the same to the *.dsc. At least I get the updated package when I download it using dget http://mentors.debian.net/debian/pool/main/p/python-visvis/python-visvis_1.5-1.dsc Regarding the "P: python-visvis: no-upstream-changelog" lintian message, I have inquired upstream about how to obtain a suitable changelog. Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e47e1aa.80...@gmail.com
Bug#637079: Bug #637079 ITP: python-visvis -- Python/OpenGL based 1D to 4D object oriented plotting software
On 14/08/11 08:14, Aron Xu wrote: Hi, I've done a quick check about your package on mentors.debian.net, something seems to be wrong: * $ lintian -E -I --show-overrides python-visvis_1.5-1_i386.changes W: python-visvis: empty-binary-package This means the package installs wrongly and does not contains the needed content. Please try to extract the .deb generated to see what happens. * I see the package is still using python-support, can you use dh_python2 instead? Reference: http://wiki.debian.org/Python/TransitionToDHPython2 Thanks for checking the package! Would it be possible to see your build log? I can successfully build it on both my amd64 and i386 computers. On the amd64 I've also built it successfully using pbuilder. I haven't yet been able to do the pbuilder test on the i386 due to a pbuilder bug regarding the proc filesystem. When I run lintian I only get: $ lintian -IE --pedantic --show-overrides python-visvis_1.5-1_amd64.changes P: python-visvis: no-upstream-changelog and the same thing on my i386 computer. Here is the procedure I used on both computers: $ dget http://mentors.debian.net/debian/pool/main/p/python-visvis/python-visvis_1.5-1.dsc $ dpkg-source -x python-visvis_1.5-1.dsc $ cd python-visvis-1.5 $ debuild $ cd .. $ lintian -IE --pedantic --show-overrides python-visvis_1.5-1_amd64.changes Thanks for the dh_python2 info. I'm on it! :-) Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e47ccb2.4010...@gmail.com
Bug#637079: ITP: python-visvis -- Python/OpenGL based 1D to 4D object oriented plotting software
Package: wnpp Severity: wishlist Owner: "Torquil Macdonald Sørensen" * Package name: python-visvis Version : 1.5 Upstream Author : Almar Klein * URL : http://code.google.com/p/visvis * License : BSD Programming Lang: Python Description : Python/OpenGL based 1D to 4D object oriented plotting software Visvis is a pure Python library for visualization of 1D to 4D data in an object oriented way. Essentially, visvis is an object oriented layer of Python on top of OpenGl, thereby combining the power of OpenGl with the usability of Python. A Matlab-like interface in the form of a set of functions allows easy creation of objects (e.g. plot(), imshow(), volshow(), surf()). -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110808110959.5045.899.reportbug@localhost
Bug#579924: Good!
Looking forward to this. Bug #590526 is really annoying! :-) I've actually made an iptraf-ng package myself that I've just started to use. Seems to work fine. Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dd53f75.2030...@gmail.com
Bug#626087: ITP: tinarng -- Tina's (pseudo-) Random Number Generator Library
Anyone reading here might also be interested in the discussion at a previous ITP report (#624764) for the same software under a different name (trng): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624764 Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc72ca1.6020...@gmail.com
Bug#624764: ITP: trng -- Tina's Random Number Generator Library
On 09/05/11 00:32, Henrique de Moraes Holschuh wrote: I must ask something else: we usually do not package libraries unless we will also have binary packages that depend on them, or they have a _large_ userbase outside of the distro. Do any of those conditions apply? Most likely none of those apply. However, I believe there are still good reasons to include it. A high-quality parallel RNG library will be very useful for researchers like myself that develop special purpose applications that don't have any use for wide audiences, e.g. Monte Carlo simulations within physics, math/statistics, biology and finance (++). General purpose binary applications as may be included in Debian that use random numbers usually don't required a very high quality of RNG, unless they are some kind of mathematical application. Therefore there won't be a lot of general purpose applications that depend on such a library. In that way I think this kind of library should be considered excempt from such "dependency considerations" :-) My motivation for including it is to improve Debian as a platform for numerical research work. I don't know how large the user base is for this library. Also, nowadays the number of multi-core computers is rising dramatically. More and more mathematical software that includes random number generation will need to include proper parallel RNG algorithms. Anyway, if I change the package name, would I need to report a second ITP with a different package name, or can an upload of a renamed package close this particular ITP? No need to file a second ITP or retitle the ITP bug. Well, I already did it and reported an ITP for 'tinarng' (#626087), so this is really closed... :-) I don't mind communicating here, though. Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc72b94.3060...@gmail.com
Bug#626087: ITP: tinarng -- Tina's (pseudo-) Random Number Generator Library
Package: wnpp Severity: wishlist Owner: "Torquil Macdonald Sørensen" * Package name: tinarng Version : 4.12 Upstream Author : Heiko Bauke * URL : http://trng.berlios.de * License : BSD Programming Lang: C++ Description : Tina's (pseudo-) Random Number Generator Library Tina's Random Number Generator Library (TRNG) is a state of the art C++ pseudo-random number generator library for sequential and parallel Monte Carlo simulations. Its design principles are based on a proposal for an extensible random number generator facility, that will be part of the random number generator facility of the forthcoming revision of the C++ standard. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110508173135.19512.42072.report...@asus.home.org
Bug#624764: ITP: trng -- Tina's Random Number Generator Library
On 08/05/11 17:16, Henrique de Moraes Holschuh wrote: On Sun, 08 May 2011, Torquil Macdonald Sørensen wrote: Might you consider using tinarng as the package name, please? TRNG is commonly used as the abbreviation of True Random Number Generator (and variations, such as thruly random number generator). It could cause some confusion. Really, upstream should have known better... At the very least, change the short description to add "pseudo". Hi Henrique! Thanks for the feedback! I've consulted with upstream and we both agree that renaming the library would be a bit unfortunate due to incompatibility. Upstream and I agree that your suggestion of including "pseudo" in the short description is a very good idea, so I've done that. I am not suggesting a rename of the library itself (although THAT would be the best option in the long term). I am asking for a rename of the *Debian package*, only. Users would still easily find it, provided that you add "libtrng" and "trng" in the full description somewhere to ease searching. Besides, it is a library: maintainers will find it easily enough to add as a dependency, and our automated find-the-library-package scripts (such as auto-apt and friends) do NOT rely upon the package name or descriptions at all, instead they look for lib in the *filesystem contents* of the packages. So, please consider renaming the *PACKAGE* to tinarng. Ok, that makes sense. I was (most likely incorrectly) under the impression that the names (package and library file) had to be the same, since I previously got a lintian warning about this (before I included the 4-0 in libtrng4-0). However, I'll read up here regarding package names: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html Anyway, if I change the package name, would I need to report a second ITP with a different package name, or can an upload of a renamed package close this particular ITP? - Torquil -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc6b6c9.7010...@gmail.com
Bug#624764: ITP: trng -- Tina's Random Number Generator Library
On 01/05/11 15:47, Henrique de Moraes Holschuh wrote: On Sun, 01 May 2011, Torquil Macdonald Sørensen wrote: Package: wnpp Severity: wishlist Owner: "Torquil Macdonald Sørensen" * Package name: trng Version : 4.11 Upstream Author : Heiko Bauke * URL : http://trng.berlios.de/ * License : BSD Programming Lang: C++ Description : Tina's Random Number Generator Library Tina's Random Number Generator Library (TRNG) is a state of the art C++ pseudo-random number generator library for sequential and parallel Monte Carlo simulations. Its design principles are based on a proposal for an extensible random number generator facility, that will be part of the random number generator facility of the forthcoming revision of the C++ standard. Might you consider using tinarng as the package name, please? TRNG is commonly used as the abbreviation of True Random Number Generator (and variations, such as thruly random number generator). It could cause some confusion. Really, upstream should have known better... At the very least, change the short description to add "pseudo". Hi Henrique! Thanks for the feedback! I've consulted with upstream and we both agree that renaming the library would be a bit unfortunate due to incompatibility. Upstream and I agree that your suggestion of including "pseudo" in the short description is a very good idea, so I've done that. At this point I have uploaded to mentors and requested sponsorship on the mentors list, so the wheels are in motion! :-) Thanks again Best regards Torquil Sørensen -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc6abfb.9090...@gmail.com
Bug#624764: ITP: trng -- Tina's Random Number Generator Library
Package: wnpp Severity: wishlist Owner: "Torquil Macdonald Sørensen" * Package name: trng Version : 4.11 Upstream Author : Heiko Bauke * URL : http://trng.berlios.de/ * License : BSD Programming Lang: C++ Description : Tina's Random Number Generator Library Tina's Random Number Generator Library (TRNG) is a state of the art C++ pseudo-random number generator library for sequential and parallel Monte Carlo simulations. Its design principles are based on a proposal for an extensible random number generator facility, that will be part of the random number generator facility of the forthcoming revision of the C++ standard. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110501124836.6669.86969.report...@asus.home.org
Bug#543923: Guitarix
Yeah, it would be really nice to have this in Debian. I have packaged version 0.09 myself and it works fine without much trouble. Torquil -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c40715e.3050...@gmail.com
