Bug#788418: New upload in mentors
Alright, I have uploaded a new candidate package on mentors. However, the lintian on mentors shows an error that I cannot reproduce locally on my gbp build. The error is the following: postinst-must-call-ldconfig and makes no-sense to me, as I am not doing anything much differently from the previous upload. Besides, my local lintian does not show it. Thoughts? Ghis
Bug#801711: marked as done (RFS: osmo-trx/0~20150325gitf147b17+dfsg-1 [ITP])
Your message dated Wed, 14 Oct 2015 14:18:14 +0200 with message-id <20151014121814.GA14684@macbookair> and subject line Re: RFS: osmo-trx/0~20150325gitf147b17+dfsg-1 [ITP] has caused the Debian Bug report #801711, regarding RFS: osmo-trx/0~20150325gitf147b17+dfsg-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 801711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "osmo-trx" * Package name: osmo-trx Version : 0~20150325gitf147b17+dfsg-1 Upstream Author : Osmocom * URL : http://openbsc.osmocom.org/trac/wiki/OsmoTRX * License : AGPL-3+ Section : utils It builds those binary packages: osmo-trx - SDR transceiver that implements Layer 1 of a GSM BTS To access further information about this package, please visit the following URL: http://mentors.debian.net/package/osmo-trx Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/osmo-trx/osmo-trx_0~20150325gitf147b17+dfsg-1.dsc More information about osmo-trx can be obtained from http://openbsc.osmocom.org/trac/wiki/OsmoTRX Changes since the last upload: Initial release (Closes: #777303) Regards, Ruben Undheim --- End Message --- --- Begin Message --- Cool! > Ok, good job, I have uploaded your package. Thank you very much for quick help, and thanks for getting me to look into (and learn) autopkgtest. > Please pay attention that I repacked your tarball > and dropped sqlite-files from there. I assume that you had to remove the line "sqlite3/Makefile \" from configure.ac somehow (either via patch or before packing) to make it build? I would be useful to get the .orig.tar.gz you uploaded so that I can put it into the git repo with pristine-tar tags etc. I'm not sure if it can be found online while it is in the NEW queue. Thanks again! Cheers, Rubem > 2015-10-13 22:22 GMT+02:00 Ruben Undheim : > > Thanks for a very quick response! > > > > > > I've fixed things for each of the 4 comments you added and re-uploaded > > to mentors. > > Please allow a few minutes for the changes to appear. > > > > I've not been able to test if the autopkgtest test works in the proper > > environment. I just > > added a simple test which checks if the executable can run with return > > code 0. (osmo-trx -h) > > > > Ruben > > > > > > 2015-10-13 20:37 GMT+02:00 Anton Gladky : > >> Hi Ruben, > >> > >> your package looks very good. A couple of minor notice. > >> > >> 1) Please add Files-excluded option in d/copyright to drop > >> embedded sqlite and files, listed in d/README.sources. > >> So uscan --repack will create a clean tarball without those > >> files. > >> > >> 2) Please also add autotest during build time and autopkgstest > >> in d/tests (see DEP-8). > >> > >> 3) Add --parallel option to dh. > >> > >> 4) Please double-check whether all files are covered by d/copyright. > >> > >> Please fix it and I will then sponsor your package. > >> > >> Best regards > >> > >> [1] https://wiki.debian.org/UscanEnhancements > >> > >> > >> Anton > >> > >> 2015-10-13 19:50 GMT+02:00 Ruben Undheim : > >>> > >>> Package: sponsorship-requests > >>> Severity: wishlist > >>> > >>> Dear mentors, > >>> > >>> I am looking for a sponsor for my package "osmo-trx" > >>> > >>> * Package name: osmo-trx > >>> Version : 0~20150325gitf147b17+dfsg-1 > >>> Upstream Author : Osmocom > >>> * URL : http://openbsc.osmocom.org/trac/wiki/OsmoTRX > >>> * License : AGPL-3+ > >>> Section : utils > >>> > >>> It builds those binary packages: > >>> > >>> osmo-trx - SDR transceiver that implements Layer 1 of a GSM BTS > >>> > >>> To access further information about this package, please visit the > >>> following URL: > >>> > >>> http://mentors.debian.net/package/osmo-trx > >>> > >>> > >>> Alternatively, one can download the package with dget using this command: > >>> > >>> dget -x > >>> http://mentors.debian.net/debian/pool/main/o/osmo-trx/osmo-trx_0~20150325gitf147b17+dfsg-1.dsc > >>> > >>> More information about osmo-trx can be obtained from > >>> http://openbsc.osmocom.org/trac/wiki/OsmoTRX > >>> > >>> Changes since the last upload: > >>> > >>> Initial release (Closes: #777303) > >>> > >>> > >>> Regards, > >>> Ruben Undheim > >>> > >> signature.asc Description: PGP signature --- End Message ---
Bug#801774: RFS: libosmocore/0.8.3-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libosmocore" * Package name: libosmocore Version : 0.8.3-1 Upstream Author : Osmocom * URL : http://bb.osmocom.org/trac/wiki/libosmocore * License : GPL-2+ Section : libs It builds those binary packages: libosmocodec-doc - Documentation for the osmo codec library libosmocodec0 - Osmo codec library libosmocore - Metapackage for all libraries from libosmocore libosmocore-dbg - Debug symbols for Open Source MObile COMmunications CORE library libosmocore-dev - Development headers for Open Source MObile COMmunications CORE li libosmocore-doc - Documentation for the Osmo Core library libosmocore-utils - Utilities for gsm libosmocore6 - Osmo Core library libosmoctrl0 - Osmo control library libosmogb4 - Osmo GPRS GB library libosmogsm-doc - Documentation for the Osmo GSM utility library libosmogsm5 - Osmo GSM utility library libosmosim0 - Osmo SIM library libosmovty-doc - Documentation for the Osmo VTY library libosmovty2 - Osmo VTY library To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libosmocore Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libo/libosmocore/libosmocore_0.8.3-1.dsc More information about libosmocore can be obtained from http://bb.osmocom.org/trac/wiki/libosmocore. Changes since the last upload: * Initial release (Closes: 646276) Regards, Ruben Undheim signature.asc Description: PGP signature
Bug#788418: New upload in mentors
Hi Ghislain, > Alright, I have uploaded a new candidate package on mentors. > > However, the lintian on mentors shows an error that I cannot reproduce > locally on my gbp build. The error is the following: > > postinst-must-call-ldconfig > > and makes no-sense to me, as I am not doing anything much differently > from the previous upload. Besides, my local lintian does not show it. > > Thoughts? Your local lintian is 'sid' ? If so, it is a different version of mentors, I believe. I asked the same question days ago. And debhelper on sid should take care of it. regards, -- Herbert Parentes Fortes Neto (hpfn)
Re: Bug#788418: New upload in mentors
El Dimecres, 14 d'octubre de 2015, a les 09:55:02, Herbert Parentes Fortes Neto va escriure: > Hi Ghislain, > > > Alright, I have uploaded a new candidate package on mentors. > > > > However, the lintian on mentors shows an error that I cannot reproduce > > locally on my gbp build. The error is the following: > > > > postinst-must-call-ldconfig > > > > and makes no-sense to me, as I am not doing anything much differently > > from the previous upload. Besides, my local lintian does not show it. > > > > Thoughts? > > Your local lintian is 'sid' ? If so, it is a different > version of mentors, I believe. > > I asked the same question days ago. And debhelper on > sid should take care of it. I have found the same odd behavior. In one of my boxes, with wheezy and lintian 2.5.30+deb8u2~bpo70+1 I have that message. However, in another box with jessie and lintian 2.5.38~bpo8+1 it doesn't appears. Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Bug#801444: marked as done (RFS: node-bootstrap-tour/0.10.2+dfsg-1 [ITP bug #801443])
Your message dated Wed, 14 Oct 2015 14:18:05 + (UTC) with message-id <1277885608.463854.1444832285082.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#801444: RFS: node-bootstrap-tour/0.10.2+dfsg-1 [ITP bug #801443] has caused the Debian Bug report #801444, regarding RFS: node-bootstrap-tour/0.10.2+dfsg-1 [ITP bug #801443] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 801444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-bootstrap-tour" * Package name: node-bootstrap-tour Version : 0.10.2+dfsg-1 Upstream Author : Ulrich Sossou * URL : https://github.com/sorich87/bootstrap-tour * License : Apache-2.0 Section : web It builds those binary packages: libjs-bootstrap-tour - Build product tours (JavaScript library) node-bootstrap-tour - Build product tours (Node.js module) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-bootstrap-tour Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-bootstrap-tour/node-bootstrap-tour_0.10.2+dfsg-1.dsc It's also here: Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-bootstrap-tour.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-bootstrap-tour.git Thanks, Snark on #debian-js --- End Message --- --- Begin Message --- Hi Julien, Built&Signed&Uploaded :) thanks for your contribution to Debian! cheers, G. Il Sabato 10 Ottobre 2015 12:42, Julien Puydt ha scritto: Le samedi 10 oct. 2015 à 09:37:46 (+), Gianfranco Costamagna a écrit : > Control: owner -1 ! > Control: tags -1 moreinfo > > grep MIT . -R > returns some files, please update the copyright accordingly > (if needed of course, but I leave checks to you :) ) > > the files were originally MIT licensed it seems, so please check if > this still applies. > In fact, that's the reverse : it's Apache-2.0 but they want to move to MIT, so need to ask all contributors. I'll re-package it better. Snark on #debian-js--- End Message ---
Bug#801782: RFS: node-private/0.1.6+20141112-1 [ITP, bug #789794]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-private" * Package name: node-private Version : 0.1.6+20141112-1 Upstream Author : Ben Newman * URL : https://github.com/benjamn/private * License : Expat Section : web It builds those binary packages: node-private - Utility for associating truly private state with any JavaScript o To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-private Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-private/node-private_0.1.6+20141112-1.dsc It is also visible here: Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-private.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-private.git Cheers, Snark on #debian-js
Bug#797888: RFS: panda3d/1.9.0-1 [ITP] -- Panda3D free 3D engine SDK
Hi, >What exactly? I mean dh_build, dh_clean, dh_install and so on :) >I would like to avoid that, mainly because the work would be obsolete soon, >as upstream wants to switch to CMake in the (more or less) near future. ack then >You realized that these files aren't symlinks but libraries? So really >don't think this would be correct. One example: So I guess you should create the library and symlink the so file? (I mean, a library and a library-dev with the so symlinked) dynamic shared libraries without soname are so painful (unless they are kept private, and I don't remember the package right now) I still don't understand, even after looking at the package sed 's/@DEB_HOST_MULTIARCH@/$(DEB_HOST_MULTIARCH)/g' debian/libpanda3d$(P3DVER).links.in > debian/panda3d$(P3DVER).links why a libpanda3d*.links.in becomes a panda3d*.links? at the end the result is somewhat correct, but I presume there are some packaging issues, e.g. the libpanda3d1.9.0 package contains .so files, but they are just links. cheers, G.
Bug#801782: RFS: node-private/0.1.6+20141112-1 [ITP, bug #789794]
Control: owner -1 ! Control: tags -1 moreinfo Hi, as said on irc: control: 1) priority: optional changelog 2) 0.1.6+20141112-1 --> 0.1.6+git20141112-1 3) README.source. Instead of wget -c https://github.com/benjamn/private/archive/.tar.gz maybe something like https://github.com/benjamn/private/tarball/master BTW I would appreciate asking upstream to push tags, I see they pushed a 0.1.2 on releases https://github.com/benjamn/private/releases cheers, G. Il Mercoledì 14 Ottobre 2015 16:24, Julien Puydt ha scritto: Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-private" * Package name: node-private Version : 0.1.6+20141112-1 Upstream Author : Ben Newman * URL : https://github.com/benjamn/private * License : Expat Section : web It builds those binary packages: node-private - Utility for associating truly private state with any JavaScript o To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-private Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-private/node-private_0.1.6+20141112-1.dsc It is also visible here: Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-private.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-private.git Cheers, Snark on #debian-js
Bug#787861: review: polyml
Hi James, >Thank you for continuing to look at this. I have just uploaded the newest >version (5.5.2-1~rc1) to https://mentors.debian.net/package/polyml. thanks to you for caring! >1) I have sent a request to join debian-science. Presumably I should wait >until the package is ready to be uploaded before requesting an upload? nope, I'm member of debian-science, I can sponsor it because I'm part of the team already. (maybe we can cc debian-science too, I'm doing it right now) and this is a package that has only *one* maintainer upload dated 2009 and an NMU dated 2012, if somebody complains they should start maintain the package instead of making them outdated :) >2) By this do you mean change it from an NMU to a team upload in the >changelog? If so, I have done that. correct, but you need to start with a "* Team Upload" dch --team does this for you >6) It had it before (https://packages.debian.org/sid/amd64/polyml/filelist). >It is in fact required by the new “polyc” compiler executable (a shell script; >the output binary is linked against libpolymain) which is currently part of >the “polyml” binary package. well, and then you are forcing people to link against a static library? I would expect the package polyml to depend on the -dev package, and allowing people to choose their favourite library version (or moving the polyc inside the -dev package, since it is useful for developing stuff) 7) I know it fails to build on hurd-i386 (due to a lack of PATH_MAX), which I plan to fix and submit upstream. However, I imagine it probably does build on a lot of the other architectures that aren’t listed. yes, there is no need to restrict where not necessary. specially for ppc64* and arm64 archs I guess it should build cleanly 9) The entirety of libffi/ is licensed under the MIT license, and is a copy of the source for https://sourceware.org/libffi/, apart from some unlicensed files in its test suite, and a few other files: >> debian:polyml-5.5.2 james% licensecheck * -r | grep -v 'GENERATED FILE$' | >> grep -v 'LGPL (v2.1 or later)$' | grep -v '^libffi/.* MIT/X11 (BSD like)$' | >> grep -v '^libffi/testsuite/libffi\.call.*\*No copyright\* UNKNOWN$' > >I have added an entry to debian/copyright listing libffi as MIT; is this >sufficient? I guess you should add also them (at least) libffi/msvcc.sh: MPL (v1.1) GPL (unversioned/unknown version) libffi/texinfo.tex: GPL (v3) libffi/ltmain.sh: GPL (v2 or later) ltmain.sh: GPL (v2 or later) 11) Changed nitpick: instead of "debian/tmp/usr/share/man/man1/poly.1" it should work also a "usr/share/man/man1/poly.1" version. new points: mentors shows something: I unused-file-paragraph-in-dep5-copyright paragraph at line 10 paragraph at line 5 I vcs-field-not-canonical http://git.debian.org/?p=debian-science/packages/polyml.git https://anonscm.debian.org/cgit/debian-science/packages/polyml.git git://git.debian.org/git/debian-science/packages/polyml.git git://anonscm.debian.org/debian-science/packages/polyml.git W shlib-with-executable-stack usr/lib/x86_64-linux-gnu/libpolyml.so.6.0.0 the last specially is something I never encountered, but seems bad cheers, Gianfranco
Bug#784898: RFS: duperemove/0.10-1 [ITP]
Control: owner -1 ! Control: tags -1 moreinfo Hi Felix, let's review. 1) the first patch should be upstreamed 2) the second one should be: -PREFIX = /usr/local +PREFIX ?= /usr this way you can upstream it too. (please forward and add link inside the patches) 3) copyright is outdated. xxhash.c: BSD (2 clause) xxhash.h: BSD (2 clause) also many copyrights are missing grep copyright . -Ri lists a lot of stuff the other stuff might look good. the package seems to be working. cheers, G.
Bug#801650: RFS: edgar/1.21-1 [ITP]
Hi again "fonts/DejaVuSans.ttf" I would appreciate using the system font (apt-file search can give you an hint about where it is located, and hedgewars package can show you some code to link it, or to make the code find it) "make clean" I would appreciate fixing distclean and use $(MAKE) instead of make BTW "make foo" crashes, as well as any other make command cheers, G.
Bug#784898: RFS: duperemove/0.10-1 [ITP]
Another issue: http://debomatic-amd64.debian.net/distribution#unstable/duperemove/0.10-1/blhc cheers, G.
Bug#801782: RFS: node-private/0.1.6+20141112-1 [ITP, bug #789794]
Hi, Le 14/10/2015 17:28, Gianfranco Costamagna a écrit : Control: owner -1 ! Control: tags -1 moreinfo Hi, as said on irc: control: 1) priority: optional Ok. changelog 2) 0.1.6+20141112-1 --> 0.1.6+git20141112-1 Not according to a discussion with jonas on irc. 3) README.source. Instead of wget -c https://github.com/benjamn/private/archive/.tar.gz maybe something like https://github.com/benjamn/private/tarball/master As I don't package "master", but a specific commit, I prefer giving a link to the right source of my upstream tarball, with the specific commit's SHA. Let's keep in mind that tomorrow morning, upstream might have committed something and master will have moved on. BTW I would appreciate asking upstream to push tags, I see they pushed a 0.1.2 on releases https://github.com/benjamn/private/releases I finally push that package forward after a discussion with jonas, and after upstream has sit on the issue of tagging for almost three months despite my report: https://github.com/benjamn/private/issues/10 Snark on #debian-js
Bug#784898: RFS: duperemove/0.10-1 [ITP]
On Wed, Oct 14, 2015 at 04:14:16PM +, Gianfranco Costamagna wrote: > 1) the first patch should be upstreamed > 2) the second one should be: > -PREFIX = /usr/local > +PREFIX ?= /usr > > this way you can upstream it too. > (please forward and add link inside the patches) well, to upstream that you need to do -PREFIX = /usr/local +PREFIX ?= /usr/local then you can set PREFIX in d/rules -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#784898: RFS: duperemove/0.10-1 [ITP]
true story :) bad copy/paste, sorry! thanks for the fix, (please finish your NM process! we need you :p ) G. Sent from Yahoo Mail on Android From:"Mattia Rizzolo" Date:Wed, 14 Oct, 2015 at 19:21 Subject:Bug#784898: RFS: duperemove/0.10-1 [ITP] On Wed, Oct 14, 2015 at 04:14:16PM +, Gianfranco Costamagna wrote: > 1) the first patch should be upstreamed > 2) the second one should be: > -PREFIX = /usr/local > +PREFIX ?= /usr > > this way you can upstream it too. > (please forward and add link inside the patches) well, to upstream that you need to do -PREFIX = /usr/local +PREFIX ?= /usr/local then you can set PREFIX in d/rules -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Bug#801650: RFS: edgar/1.21-1 [ITP]
The edgar-data package takes the font and compresses it in the edgar.pak archive. Should I make fonts-dejavu-core a build dependency and link it before it builds? On 10/14/15, Gianfranco Costamagna wrote: > Hi again > > > "fonts/DejaVuSans.ttf" > > I would appreciate using the system font > > (apt-file search can give you an hint about where it is located, and > hedgewars package can show you some code to link it, or > to make the code find it) > > > "make clean" > > > I would appreciate fixing distclean and use $(MAKE) instead of make > > > BTW "make foo" > crashes, as well as any other make command > > > cheers, > > G. >
Bug#784898: RFS: duperemove/0.10-1 [ITP]
Am Mittwoch, den 14.10.2015, 18:41 +0100 schrieb Gianfranco Costamagna: > thanks for the fix, Thanks very much to both of you. I created now a github fork for it: https://github.com/fezie/duperemove Though I didn't do much yet. > > (please finish your NM process! we need you :p ) Thanks again very much. You can't imagine how good that feels to me :-) Regards Felix
Bug#787861: review: polyml
Hi Gianfranco,
I have uploaded 5.5.2-1~rc2 to mentors.
1) Do I need to send a separate email to this then? I also filed #801793 for a
transition, but that has already been closed as unnecessary since there are no
rdeps.
2) Added
6) The compiler is indeed forcing your code to be linked against a static
library. I would argue that the compiler *should* be included in the polyml
package along with the interpreter. The libpolyml-dev package provides access
to the internal library used by polyml, whereas the static libpolymain.a
library provides an entry point stub for your compiled code. It contains the
single libpolymain/polystub.c file, defining main (or WinMain if you happen to
compile on Windows…) which calls through to polymain, contained in the *shared*
libpolyml.so.6 library, like so:
> int main(int argc, char *argv[])
> {
> return polymain(argc, argv, &poly_exports);
> }
These are the symbols in libpolymain.a:
> debian:polytest james% nm /usr/lib/x86_64-linux-gnu/libpolymain.a
>
> polystub.o:
> T main
> U poly_exports
> U polymain
I hardly think linking against this static library is an issue.
7) I have added arm64, ppc64el and ppc64
9) Added (libffi/msvcc.sh is MPL-1.1, GPL-2.0+ or LGPL-2.1+)
11) It doesn’t seem to work without the debian/tmp/ prefix. The manpage for
dh_install specifically mentions falling back to debian/tmp/, but there is no
such statement in dh_installman, so I believe you have to specify that manually.
New Points:
12) I unused-file-paragraph-in-dep5-copyright: Fixed by reordering entries
13) I vcs-field-not-canonical: Changed to Vcs-Browser:
https://anonscm.debian.org/cgit/debian-science/packages/polyml.git/ and
Vcs-Git: git://anonscm.debian.org/debian-science/packages/polyml.git
14) W shlib-with-executable-stack: This is because libpolyml has one assembly
file[1] for x86 (other architectures don’t have any assembly). I have added a
patch under debian/patches which I have also submitted upstream to fix this.
[1] GNU as defaults to having an executable stack, unlike with GCC etc, and you
have to explicitly tell it to not do so. You can either do this by adding the
magic '.section .note.GNU-stack, "", @progbits' statement, or by passing it a
command-line argument. The former is apparently generally preferred (and is
what libffi does in its assembly files).
Thanks,
James
> On 14 Oct 2015, at 16:46, Gianfranco Costamagna
> wrote:
>
> Hi James,
>
>
>
>> Thank you for continuing to look at this. I have just uploaded the newest
>> version (5.5.2-1~rc1) to https://mentors.debian.net/package/polyml.
>
>
> thanks to you for caring!
>> 1) I have sent a request to join debian-science. Presumably I should wait
>> until the package is ready to be uploaded before requesting an upload?
>
>
> nope, I'm member of debian-science, I can sponsor it because I'm part of the
> team already.
> (maybe we can cc debian-science too, I'm doing it right now)
>
>
> and this is a package that has only *one* maintainer upload dated 2009 and an
> NMU dated 2012,
> if somebody complains they should start maintain the package instead of
> making them outdated :)
>
>
>> 2) By this do you mean change it from an NMU to a team upload in the
>> changelog? If so, I have done that.
>
> correct, but you need to start with a "* Team Upload"
> dch --team does this for you
>
>> 6) It had it before (https://packages.debian.org/sid/amd64/polyml/filelist).
>> It is in fact required by the new “polyc” compiler executable (a shell
>> script; the output binary is linked against libpolymain) which is currently
>> part of the “polyml” binary package.
>
> well, and then you are forcing people to link against a static library? I
> would expect the package polyml to depend on the -dev package, and allowing
> people to choose their favourite library version
> (or moving the polyc inside the -dev package, since it is useful for
> developing stuff)
>
> 7) I know it fails to build on hurd-i386 (due to a lack of PATH_MAX), which I
> plan to fix and submit upstream. However, I imagine it probably does build on
> a lot of the other architectures that aren’t listed.
>
> yes, there is no need to restrict where not necessary.
> specially for ppc64* and arm64 archs I guess it should build cleanly
>
> 9) The entirety of libffi/ is licensed under the MIT license, and is a copy
> of the source for https://sourceware.org/libffi/, apart from some unlicensed
> files in its test suite, and a few other files:
>
>>> debian:polyml-5.5.2 james% licensecheck * -r | grep -v 'GENERATED FILE$' |
>>> grep -v 'LGPL (v2.1 or later)$' | grep -v '^libffi/.* MIT/X11 (BSD like)$'
>>> | grep -v '^libffi/testsuite/libffi\.call.*\*No copyright\* UNKNOWN$'
>>
>> I have added an entry to debian/copyright listing libffi as MIT; is this
>> sufficient?
>
>
> I guess you should add also them (at least)
>
> libffi/msvcc.sh: MPL (v1.1) GPL (unvers
Bug#801838: RFS: node-es5-shim/4.1.14+dfsg-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-es5-shim" * Package name: node-es5-shim Version : 4.1.14+dfsg-1 Upstream Author : Kristopher Michael Kowal and contributors * URL : http://github.com/es-shims/es5-shim/ * License : Expat Section : web It builds those binary packages: libjs-es5-shim - ECMAScript 5 compat. shims for old JavaScript engines (library) node-es5-shim - ECMAScript 5 compat. shims for old JavaScript engines (Node.js) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-es5-shim Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-es5-shim/node-es5-shim_4.1.14+dfsg-1.dsc It is also available here: Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-es5-shim.git Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-es5-shim.git Thanks, Snark on #debian-js
Bug#788418: New upload in mentors
On 14/10/15 13:55, Herbert Parentes Fortes Neto (hpfn) wrote: Hi Ghislain, Alright, I have uploaded a new candidate package on mentors. However, the lintian on mentors shows an error that I cannot reproduce locally on my gbp build. The error is the following: postinst-must-call-ldconfig and makes no-sense to me, as I am not doing anything much differently from the previous upload. Besides, my local lintian does not show it. Thoughts? Your local lintian is 'sid' ? If so, it is a different version of mentors, I believe. I asked the same question days ago. And debhelper on sid should take care of it. regards, So these errors should probably be disregarded. The package in mentors is ready for review then. Awaiting Gianfranco's comments. Many thanks, Ghis
