Problems building phast against clapack
Hi, I recently have createt a package from clapack to build phast[1]. Unfortunately the build fails for reasons I do not understand. I expect that something might be wrong with either f2c or clapack packaging but I'm not sure. Anybody might be able to make some sense out of: ... ../munge-help.sh consEntropy.help_src > consEntropy.help gcc -O3 -Wall -I/build/phast-1.4/src/util/../../include -DPHAST_VERSION=\"v1.3\" -DPHAST_HOME=\"/build/phast-1.4/src/util/../..\" -I/build/phast-1.4/src/util/../../src/lib/pcre -fno-strict-aliasing -I/usr/lib/INCLUDE -I/usr/lib/F2CLIBS -c indelHistory.c -o indelHistory.o gcc -L/build/phast-1.4/src/util/../../lib -L/usr/lib/F2CLIBS -o /build/phast-1.4/src/util/../../bin/indelHistory indelHistory.o -lphast -lclapack -lctmg -lcblas -lc -lf2c -lm /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libf2c.so: undefined reference to `MAIN__' collect2: error: ld returned 1 exit status Makefile:20: recipe for target '/build/phast-1.4/src/util/../../bin/indelHistory' failed Thanks for any help Andreas. [1] https://anonscm.debian.org/git/debian-med/phast.git -- http://fam-tille.de
Re: Problems building phast against clapack
On Fri, Jun 03, 2016 at 09:59:00AM +0200, Andreas Tille wrote: > ../munge-help.sh consEntropy.help_src > consEntropy.help > gcc -O3 -Wall -I/build/phast-1.4/src/util/../../include > -DPHAST_VERSION=\"v1.3\" -DPHAST_HOME=\"/build/phast-1.4/src/util/../..\" > -I/build/phast-1.4/src/util/../../src/lib/pcre -fno-strict-aliasing > -I/usr/lib/INCLUDE -I/usr/lib/F2CLIBS -c indelHistory.c -o indelHistory.o > gcc -L/build/phast-1.4/src/util/../../lib -L/usr/lib/F2CLIBS -o > /build/phast-1.4/src/util/../../bin/indelHistory indelHistory.o -lphast > -lclapack -lctmg -lcblas -lc -lf2c -lm > /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libf2c.so: > undefined reference to `MAIN__' $ ldd -r /usr/lib/x86_64-linux-gnu/libf2c.so.2.1 linux-vdso.so.1 (0x7fff4efd) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f7df682a000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f7df652c000) /lib64/ld-linux-x86-64.so.2 (0x5572c209f000) undefined symbol: MAIN__(/usr/lib/x86_64-linux-gnu/libf2c.so.2.1) I'd say it's a violation of a "must" policy directive in 10.2, "shared libraries must be linked against all libraries that they use symbols from" -- WBR, wRAR signature.asc Description: PGP signature
Bug#819681: RFS: python-django-gravatar2/1.4.0-1 [ITP]
Le mercredi 20 avril 2016 à 09:07:14+0200, Pierre-Elliott Bécue a écrit :
> Le mercredi 20 avril 2016 à 08:49:27+0200, Nicolas Dandrimont a écrit :
> > Tiago, when replying to a RFS, please use the bug report rather than the
> > mailing list.
> >
> > * Tiago Ilieve [2016-04-12 03:23:50 -0300]:
> >
> > > > When I tried to dput I've been refused it because 1.4.0-1 was already
> > > > on the
> > > > server. That's the only way I found. Maybe I did something wrong.
> > >
> > > Maybe you uploaded again before mentors.d.n processed the first
> > > upload? There's an waiting time ("How long will it take until my
> > > upload is available to sponsors?" from its Q&A[5]) between the upload
> > > and the package actually being available in there. I'm suggesting this
> > > because mentors.d.n even store different versions of the package, even
> > > when you did not bump its version. You can always use the delete
> > > button from its web interface as well.
> >
> > Please don't.
> >
> > Pierre-Elliott, please post full error messages when you have an issue, not
> > your interpretation of the message. You probably got tripped by the fact
> > that
> > dput leaves a .upload file along your .changes to avoid double uploads. You
> > can
> > either remove the .upload file or use dput -f to bypass that check.
> >
> > No need to bump the revision number (which might end you up forgetting to
> > upload the original tarball) or removing the package from mentors.d.n (which
> > will remove history).
> >
> > Bye,
>
> Oh, well, understood, I missed that.
>
> Thanks for the hint, should I reupload the package with -1 version, after
> fixing the changelog? From where I stand that looks awkward but I'm eager to
> follow any suggestion.
Dear mentors,
Apologies for this bump, but I still got no anwser for this package. So I'm
trying again, in hope that somebody who missed this submission will get
interested in. :)
Cheers!
--
PEB
signature.asc
Description: PGP signature
Re: Problems building phast against clapack
On Fri, Jun 03, 2016 at 01:03:28PM +0500, Andrey Rahmatullin wrote: > On Fri, Jun 03, 2016 at 09:59:00AM +0200, Andreas Tille wrote: > > ../munge-help.sh consEntropy.help_src > consEntropy.help > > gcc -O3 -Wall -I/build/phast-1.4/src/util/../../include > > -DPHAST_VERSION=\"v1.3\" -DPHAST_HOME=\"/build/phast-1.4/src/util/../..\" > > -I/build/phast-1.4/src/util/../../src/lib/pcre -fno-strict-aliasing > > -I/usr/lib/INCLUDE -I/usr/lib/F2CLIBS -c indelHistory.c -o indelHistory.o > > gcc -L/build/phast-1.4/src/util/../../lib -L/usr/lib/F2CLIBS -o > > /build/phast-1.4/src/util/../../bin/indelHistory indelHistory.o -lphast > > -lclapack -lctmg -lcblas -lc -lf2c -lm > > /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libf2c.so: > > undefined reference to `MAIN__' > > $ ldd -r /usr/lib/x86_64-linux-gnu/libf2c.so.2.1 > linux-vdso.so.1 (0x7fff4efd) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f7df682a000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f7df652c000) > /lib64/ld-linux-x86-64.so.2 (0x5572c209f000) > undefined symbol: MAIN__(/usr/lib/x86_64-linux-gnu/libf2c.so.2.1) > > I'd say it's a violation of a "must" policy directive in 10.2, "shared > libraries must be linked against all libraries that they use symbols from" In other words you mean this is a bug in libf2c2 package - but how to fix this? Kind regards Andreas. -- http://fam-tille.de
Bug#821270: Review of git version
Hi, after the latest fixes I put the package in deferred/5, to leave Sean enough time to review it and ack the latest changes. thanks for the nice contribution to Debian! G. Il Mercoledì 1 Giugno 2016 12:51, nord-stream ha scritto: Source: firefox-branding-iceweasel This package includes files under: * MPL-2.0 (which is compatible with GPL-2.0+ and LGPL-2.1+) * Triple licensing: MPL-1.1 or GPL-2.1+ or LGPL-2.1+ (compatible with the above) This is largely the same as just 'MPL-2.0' nord-stream On 06/01/2016 03:06 AM, Sean Whitton wrote: > control: tag -1 +moreinfo > > Hello, > > Gianfranco took a look at the package and pointed out to me that the > line > > License: MPL-2.0, and MPL-1.1 or GPL-2.0+ or LGPL-2.1+ > > in d/copyright doesn't really make sense. What are you trying to say? > > I pushed a commit to the team repo to use secure Vcs-* URIs. >
Re: Problems building phast against clapack
On Fri, Jun 03, 2016 at 11:20:09AM +0200, Andreas Tille wrote: > In other words you mean this is a bug in libf2c2 package Yes, an RC one. > - but how to fix this? I have no idea. MAIN__ is used by the library, but not defined in it. -- WBR, wRAR signature.asc Description: PGP signature
Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]
Hi,
I've updated the caffe package in the git repo, one of the major changes is that
`python-caffe-cpu` was changed to `python3-caffe-cpu`.
On 2 June 2016 at 07:00, Ghislain Vaillant wrote:
>
>
> The build time testsuite, autopkgtest and piuparts serve different
> purposes. You might want to spend some time reading a bit more about
> those, as the distinction is quite important from a maintainer's point-
> of-view.
>
> [1] https://wiki.debian.org/piuparts
>
>>> So yes, the Python runtime dependencies should be part of Build-Depends
>>> and the Python testsuite should be called during the build.
>>
>>
>> I'll add them later.
>
>
> Good.
A simple python interface tester was added into packaging repo.
>>> From my experience using caffe at the lab, the Python interface is what
>>> people are mainly using. So IMO, it would be quite a let down if the
>>> caffe were uploaded without Python support.
>>>
>>> IMO, it should be either Python 3 alone or Python 2 + 3. I made this
>>> mistake when packaging OpenGM and regret it now. I'll repeat it here,
>>> Python 2 has an expiration date and we should encourage people to use
>>> Python 3.
>>
>>
>> Let's make python3-caffe-* and let it be python3-only.
>
>
> Good.
Bump python to 3: done.
>>> I did not follow all the recent action on the packaging, but why are we
>>> still using templated install.in files instead of patching the build
>>> system for the great of the rest of the Linux community?
>>
>>
>> I indeed made all suggested changes including using `GNUInstallDirs`
>> to avoid template generation. Currently the *.in files are mostly
>> fake template (nothing to be replaced) but only
>> libcaffe-cpu-dev.install.in is the real one. I need to match
>> a library install directory in this file, which is the only
>> remaining template.
>>
>> Oh yes I should rename those non-template files.
>> :-)
>
>
> Don't forget to forward the patch upstream please.
Rename templates: done.
BTW I have already forwarded some of the patches to upstream:
see
https://github.com/BVLC/caffe/pull/423{6,7,8}
>> BTW, I tested the python3 build and I found that, the python3
>> version can be built without python3-protobuf, and the compilation
>> will not crash. Python3 module will be generated but when trying
>> to import caffe in python3 it will end up with something like:
>>
>> error import google.protobuf
>>
>> That is to say python3-protobuf is not a build-dep but a runtime-dep
>> for the python3 interface.
>
>
> It is explicitly listed in the requirements [2], so no surprise here.
> Since you intend to run the Python testsuite at build time, you will
> probably need all these dependencies translated to Build-Depends.
Now the blocker is mainly python3-protobuf, I plan to look into it recently.
> [2] https://github.com/BVLC/caffe/blob/master/python/requirements.txt
>
> Ghis
Apart from the changes mentioned above, I also
1. remove unnecessary manpages, refresh caffe.1
2. add python module runtime-deps into B-D
3. suggest caffe-doc for package libcaffe-cpu-dev
And this is latest TODO for the caffe-cpu package
1. resolve python3-protobuf
2. [optional] stretch should ship python3-opencv
3. update README.Debian
4. apply similar changes to the repo caffe-contrib.git
--
Best,
Lumin
Bug#826160: RFS: node-getobject/0.1.0-2 -- set and get deep objects easily
Hi, > I am looking for a sponsor for my package "node-getobject" sponsored. G. * Package name: node-getobject Version : 0.1.0-2 Upstream Author : "Cowboy" Ben Alman * URL : https://github.com/cowboy/node-getobject * License : MIT Section : web It builds those binary packages: libjs-getobject - set and get deep objects easily - library for browsers node-getobject - set and get deep objects easily - module for Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-getobject Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-getobject/node-getobject_0.1.0-2.dsc Or clone using this git command: git clone https://anonscm.debian.org/git/pkg-javascript/node-getobject.git The last commit should be signed with the same key as this email. More information about node-getobject can be obtained from https://github.com/cowboy/node-getobject. Changes since the last upload: * Fix Vcs-Git url * Fix autopkgtest command * Remove Testsuite entry from d/control * Updated standards version. No changes needed. * Use secure Vcs-Git url * Adjust priority to match the override of ftp-masters Regards, Jonathan Ulrich Horn
Bug#826219: RFS: localehelper/0.1.4-2 -- locale helper tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "localehelper" * Package name: localehelper Version : 0.1.4-2 Upstream Author : Jakub Wilk * URL : http://jwilk.net/software/localehelper * License : Expat Section : utils It builds those binary packages: localehelper - locale helper tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/localehelper Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/localehelper/localehelper_0.1.4-2.dsc Or clone using this git command: git clone https://anonscm.debian.org/git/users/jonathanh-guest/localehelper.git The last commit should be signed with the same key as this email. More information about localehelper can be obtained from http://jwilk.net/software/localehelper. Changes since the last upload: * Updated watch file as releases now happen on github (Closes: #825565) * Updated standards version. No changes needed * Changed priority to match override from FTP-Masters * Update packaging repository URLs Regards, Jonathan Ulrich Horn signature.asc Description: OpenPGP digital signature
Bug#826155: marked as done (RFS: node-get-stdin/5.0.1-1 [ITP] -- Easier stdin for Node.js)
Your message dated Fri, 3 Jun 2016 12:25:50 + (UTC) with message-id <1292386160.7021599.1464956750171.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#826155: RFS: node-get-stdin/5.0.1-1 [ITP] -- Easier stdin for Node.js has caused the Debian Bug report #826155, regarding RFS: node-get-stdin/5.0.1-1 [ITP] -- Easier stdin for Node.js 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.) -- 826155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826155 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-get-stdin" * Package name: node-get-stdin Version : 5.0.1-1 Upstream Author : Sindre Sorhus * URL : https://github.com/sindresorhus/get-stdin * License : expat Section : web It builds those binary packages: node-get-stdin - Easier stdin for Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-get-stdin Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-get-stdin/node-get-stdin_5.0.1-1.dsc Or clone using this git command: git clone https://anonscm.debian.org/git/pkg-javascript/node-get-stdin.git The last commit should be signed with the same key as this email. More information about get-stdin can be obtained from https://github.com/sindresorhus/get-stdin. Changes since the last upload: * Initial release (Closes: #818786) Regards, Jonathan Ulrich Horn signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- hi, > I am looking for a sponsor for my package "node-get-stdin" looks good, sponsored. * Package name: node-get-stdin Version : 5.0.1-1 Upstream Author : Sindre Sorhus * URL : https://github.com/sindresorhus/get-stdin * License : expat Section : web It builds those binary packages: node-get-stdin - Easier stdin for Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-get-stdin Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-get-stdin/node-get-stdin_5.0.1-1.dsc Or clone using this git command: git clone https://anonscm.debian.org/git/pkg-javascript/node-get-stdin.git The last commit should be signed with the same key as this email. More information about get-stdin can be obtained from https://github.com/sindresorhus/get-stdin. Changes since the last upload: * Initial release (Closes: #818786) Regards, Jonathan Ulrich Horn--- End Message ---
Bug#826219: marked as done (RFS: localehelper/0.1.4-2 -- locale helper tool)
Your message dated Fri, 3 Jun 2016 12:27:15 + (UTC) with message-id <1683778971.7062623.1464956835137.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#826219: RFS: localehelper/0.1.4-2 -- locale helper tool has caused the Debian Bug report #826219, regarding RFS: localehelper/0.1.4-2 -- locale helper tool 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.) -- 826219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "localehelper" * Package name: localehelper Version : 0.1.4-2 Upstream Author : Jakub Wilk * URL : http://jwilk.net/software/localehelper * License : Expat Section : utils It builds those binary packages: localehelper - locale helper tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/localehelper Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/localehelper/localehelper_0.1.4-2.dsc Or clone using this git command: git clone https://anonscm.debian.org/git/users/jonathanh-guest/localehelper.git The last commit should be signed with the same key as this email. More information about localehelper can be obtained from http://jwilk.net/software/localehelper. Changes since the last upload: * Updated watch file as releases now happen on github (Closes: #825565) * Updated standards version. No changes needed * Changed priority to match override from FTP-Masters * Update packaging repository URLs Regards, Jonathan Ulrich Horn signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi, > I am looking for a sponsor for my package "localehelper" signed and uploaded :) G. * Package name: localehelper Version : 0.1.4-2 Upstream Author : Jakub Wilk * URL : http://jwilk.net/software/localehelper * License : Expat Section : utils It builds those binary packages: localehelper - locale helper tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/localehelper Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/localehelper/localehelper_0.1.4-2.dsc Or clone using this git command: git clone https://anonscm.debian.org/git/users/jonathanh-guest/localehelper.git The last commit should be signed with the same key as this email. More information about localehelper can be obtained from http://jwilk.net/software/localehelper. Changes since the last upload: * Updated watch file as releases now happen on github (Closes: #825565) * Updated standards version. No changes needed * Changed priority to match override from FTP-Masters * Update packaging repository URLs Regards, Jonathan Ulrich Horn--- End Message ---
Bug#826234: RFS: xvt/2.1-20.2 [RC] [NMU] -- raise debhelper compatibility
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor of the package "xvt": Package name: xvt Version : 2.1-20.2 Upstream Author : John Bovey, University of Kent at Canterbury. URL : none License : permissive Section : x11 It builds a single binary package: xvt - X terminal-emulator similar to xterm, but smaller For information about the state of this packaging, see https://mentors.debian.net/package/xvt The package is downloaded in a standard manner: dget -x https://mentors.debian.net/debian/pool/main/x/xvt/xvt_2.1-20.2.dsc Observe, that the primary intent of this NMU is to avoid the removal of this software, since debhelper compatibility level 4 will be dis- allowed within very shortly, possibly in a fortnight. Changes since the last upload: * Non-maintainer upload. * Move to compatibility 5, which is the minimally available level in the present release cycle. Closes: #817740. * Disable menu file creation, but include a new desktop file. + debian/rules: Updated. + debian/xvt.desktop: New file. I have offered to assume maintainership of this package, but Sam Hocevar has not responded in any manner whatsoever. Regards, Mats Erik Andersson
Re: Problems building phast against clapack
Hi Barak, not sure whether you follow the discussion on debian-mentors[1] On Fri, Jun 03, 2016 at 03:47:16PM +0500, Andrey Rahmatullin wrote: > On Fri, Jun 03, 2016 at 11:20:09AM +0200, Andreas Tille wrote: > > In other words you mean this is a bug in libf2c2 package > Yes, an RC one. > > > - but how to fix this? > I have no idea. MAIN__ is used by the library, but not defined in it. For me this sounds like a FORTRAN to C problem. The capital letters somehow seem to be originated in the old FORTRAN age. I have no idea how to fix this. Kind regards Andreas. [1] https://lists.debian.org/debian-mentors/2016/06/msg00090.html -- http://fam-tille.de
help2man usage with pybuild / debhelper packaging workflow
Dear all, Are there any successful examples of integration of help2man with a pybuild / debhelper workflow for an arbitrary number of scripts? The only close example I could find was the stdeb package, but I am dealing with many more scripts and I cannot afford to list them all individually by hand. Best regards, Ghis
Re: help2man usage with pybuild / debhelper packaging workflow
On 2016-06-03 16:43 +0100, Ghislain Vaillant wrote: > Dear all, > > Are there any successful examples of integration of help2man with a > pybuild / debhelper workflow for an arbitrary number of scripts? help2man breaks cross-building so is best avoided if you can. Please just write a man page. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: Digital signature
Bug#826234: marked as done (RFS: xvt/2.1-20.2 [RC] [NMU] -- raise debhelper compatibility)
Your message dated Fri, 3 Jun 2016 16:13:13 + (UTC) with message-id <1331235339.7315143.1464970393044.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#826234: RFS: xvt/2.1-20.2 [RC] [NMU] -- raise debhelper compatibility has caused the Debian Bug report #826234, regarding RFS: xvt/2.1-20.2 [RC] [NMU] -- raise debhelper compatibility 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.) -- 826234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor of the package "xvt": Package name: xvt Version : 2.1-20.2 Upstream Author : John Bovey, University of Kent at Canterbury. URL : none License : permissive Section : x11 It builds a single binary package: xvt - X terminal-emulator similar to xterm, but smaller For information about the state of this packaging, see https://mentors.debian.net/package/xvt The package is downloaded in a standard manner: dget -x https://mentors.debian.net/debian/pool/main/x/xvt/xvt_2.1-20.2.dsc Observe, that the primary intent of this NMU is to avoid the removal of this software, since debhelper compatibility level 4 will be dis- allowed within very shortly, possibly in a fortnight. Changes since the last upload: * Non-maintainer upload. * Move to compatibility 5, which is the minimally available level in the present release cycle. Closes: #817740. * Disable menu file creation, but include a new desktop file. + debian/rules: Updated. + debian/xvt.desktop: New file. I have offered to assume maintainership of this package, but Sam Hocevar has not responded in any manner whatsoever. Regards, Mats Erik Andersson --- End Message --- --- Begin Message --- Hi >I am looking for a sponsor of the package "xvt": This isn't an RC right now, so I sponsored, but in deferred/10 and updated the bug report accordingly. thanks for your contribution to Debian! G.--- End Message ---
Re: help2man usage with pybuild / debhelper packaging workflow
Hi, sending what I do on my machine >Il Venerdì 3 Giugno 2016 17:44, Ghislain Vaillant ha >scritto: >Dear all, > >Are there any successful examples of integration of help2man with a >pybuild / debhelper workflow for an arbitrary number of scripts? > >The only close example I could find was the stdeb package, but I am >dealing with many more scripts and I cannot afford to list them all >individually by hand. help2man -N -n "automounter for removable media for Python" udiskie --version-string=1.4.8 > debian/udiskie.1 :) does this help? maybe codesearch.debian.net has some hints? https://codesearch.debian.net/results/help2man%20path%3A%2Frules%24/page_0 G.
Re: help2man usage with pybuild / debhelper packaging workflow
On 03/06/16 17:10, Wookey wrote: On 2016-06-03 16:43 +0100, Ghislain Vaillant wrote: Dear all, Are there any successful examples of integration of help2man with a pybuild / debhelper workflow for an arbitrary number of scripts? help2man breaks cross-building so is best avoided if you can. Please just write a man page. Yes, it is mentioned here [1]. [1] https://wiki.debian.org/ManPage/help2man And I don't mind for a handful of scripts. But what if you have 20 or 30? Ghis
Re: help2man usage with pybuild / debhelper packaging workflow
On 06/03/2016 06:25 PM, Ghislain Vaillant wrote: > On 03/06/16 17:10, Wookey wrote: >> On 2016-06-03 16:43 +0100, Ghislain Vaillant wrote: >>> Dear all, >>> >>> Are there any successful examples of integration of help2man with a >>> pybuild / debhelper workflow for an arbitrary number of scripts? >> >> help2man breaks cross-building so is best avoided if you can. >> Please just write a man page. > > Yes, it is mentioned here [1]. > > [1] https://wiki.debian.org/ManPage/help2man > > And I don't mind for a handful of scripts. But what if you have 20 or > 30? Well, you could add a custom target to debian/rules that calls help2man for all these scripts - so that you as a maintainer can refresh the manpages every now and then. (And store them in debian/ in the packaging.) That way, you don't break cross builds (manpages are pre-generated), but still automate it to a large extent. Regards, Christian
Re: help2man usage with pybuild / debhelper packaging workflow
* Wookey , 2016-06-03, 17:10: Are there any successful examples of integration of help2man with a pybuild / debhelper workflow for an arbitrary number of scripts? help2man breaks cross-building so is best avoided if you can. Please just write a man page. Also, you can write much better manpages than help2man could generate. The quality of stuff help2man spews is often atrocious. Don't forget to forward the manpages upstream. :) -- Jakub Wilk
Re: Problems building phast against clapack
I just noticed that I did not include mentors list in my answer... Il 03/giu/2016 13:53, "Giulio Paci" ha scritto: > > Hi all, > > Il 03/giu/2016 12:47, "Andrey Rahmatullin" ha scritto: > > > > On Fri, Jun 03, 2016 at 11:20:09AM +0200, Andreas Tille wrote: > > > In other words you mean this is a bug in libf2c2 package > > Yes, an RC one. > > > > > - but how to fix this? > > I have no idea. MAIN__ is used by the library, but not defined in it. > > As far as I know this is the intended behavior and is needed so that the library can perform initialisation before main(). Just define main as MAIN__ when compiling your binaries and they should work (have a look at [0]). > > BTW: other fortran compilers implements similar strategies, with different naming; autoconf has a macro detecting the most common setups. > > [0] https://gcc.gnu.org/onlinedocs/gcc-2.95.3/g77_16.html
Re: help2man usage with pybuild / debhelper packaging workflow
On 2016-06-03 18:30 +0200, Christian Seiler wrote: > On 06/03/2016 06:25 PM, Ghislain Vaillant wrote: > > And I don't mind for a handful of scripts. But what if you have 20 or > > 30? > > Well, you could add a custom target to debian/rules that calls > help2man for all these scripts - so that you as a maintainer > can refresh the manpages every now and then. (And store them > in debian/ in the packaging.) That way, you don't break cross > builds (manpages are pre-generated), but still automate it to > a large extent. Yep, that's a reasonable plan. Missing man pages is better than things that gratuitously won't cross-build. Just copying the help into a man page is mostly makework to shut lintian up. They are often very poor manpages. If the help is there already or upstream documentation is some other format (e.g. html), then if you _really_ can't be bothered making man pages, just leave it as upstream supplied. Using help2man is a worse 'solution' than doing nothing. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: Digital signature
Bug#819681: marked as done (RFS: python-django-gravatar2/1.4.0-2 [ITP])
Your message dated Fri, 3 Jun 2016 17:14:55 + (UTC) with message-id <1362133245.7332857.1464974095164.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#819681: RFS: python-django-gravatar2/1.4.0-1 [ITP] has caused the Debian Bug report #819681, regarding RFS: python-django-gravatar2/1.4.0-2 [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.) -- 819681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819681 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 "python-django-gravatar2". * Package name: python-django-gravatar2 Version : 1.4.0-1 Upstream Author : Tristan Waddington * URL : https://github.com/twaddington/django-gravatar * License : MIT Section : python It builds those binary packages: * python-django-gravatar2 - Python2 library that provides essential Gravatar support * python3-django-gravatar2 - Python3 library that provides essential Gravatar support To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-django-gravatar2 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-django-gravatar2/python-django-gravatar2_1.4.0-1.dsc More information about django-gravatar2 can be found on the github's page of the project. I already tried to look for sponsorship on DPMT mailing list, without success so far. Regards, -- Pierre-Elliott Bécue --- End Message --- --- Begin Message --- control: owner -1 ! control: tags -1 moreinfo Hi, >Apologies for this bump, but I still got no anwser for this package. So I'm >trying again, in hope that somebody who missed this submission will get >interested in. :) the packaging was good, I just did some changes: -1 should be the revision (you can upload as many as -1 you want on mentors) until it gets accepted. I really like pybuild, so I did +export PYBUILD_NAME=django-gravatar2 in rules, and removed python3-django-gravatar2.install and python-django-gravatar2.install files. I checked the result, and sponsored on deferred/5 queue. Can you please check and apply this debdiff on top of your package and see if everything works? In that case in 5 days your package will enter the new queue! thanks for your contribution to Debian! G. debdiff Description: Binary data --- End Message ---
Re: Problems building phast against clapack
[ Hmpf, multiple X-Debbugs-Cc don't work the way I expected, hence
attaching my initial email. Sorry for the noise on
debian-med-packaging@, that's the only of the initial X-Debbugs-Cc
that got through. ]
This is now tracked in:
https://bugs.debian.org/826253
Regards,
Christian
--- Begin Message ---
Package: libf2c2
Severity: serious
Version: 20130926-1
Tags: patch
Justification: violation of Debian policy 10.2 (libraries may
not depend on symbols that they don't import)
(cf. discussion on debian-mentors:
https://lists.debian.org/debian-mentors/2016/06/msg00090.html
+ followups)
On 06/03/2016 09:59 AM, Andreas Tille wrote:
> ...
> ../munge-help.sh consEntropy.help_src > consEntropy.help
> gcc -O3 -Wall -I/build/phast-1.4/src/util/../../include
> -DPHAST_VERSION=\"v1.3\" -DPHAST_HOME=\"/build/phast-1.4/src/util/../..\"
> -I/build/phast-1.4/src/util/../../src/lib/pcre -fno-strict-aliasing
> -I/usr/lib/INCLUDE -I/usr/lib/F2CLIBS -c indelHistory.c -o indelHistory.o
> gcc -L/build/phast-1.4/src/util/../../lib -L/usr/lib/F2CLIBS -o
> /build/phast-1.4/src/util/../../bin/indelHistory indelHistory.o -lphast
> -lclapack -lctmg -lcblas -lc -lf2c -lm
> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libf2c.so:
> undefined reference to `MAIN__'
> collect2: error: ld returned 1 exit status
> Makefile:20: recipe for target
> '/build/phast-1.4/src/util/../../bin/indelHistory' failed
So what appears to be the case is the following: libf2c.so has
a function main(), which will be called with fortran programs
converted via f2c, because there needs to be some setup code
to happen before the actual main converted Fortran program can
be run. This main implementation then calls MAIN__, which f2c
generates for converted Fortran programs - but not subroutines.
As far as I can tell, this has the unfortunate consequence that
f2c can't really be used to generate libraries that are used
from anything but other code that is converted via f2c.
Steps to reproduce this issue:
#include
int main() { printf("Hello World!\n"); }
gcc -Wall -o hello hello.c -lf2c
In this trivial example, this is not a huge issue (why would
you want to do so), but you can see the problem it creates in
other software.
Fortunately, there's a way out of this, by adding a weak alias
for MAIN__ in libf2c2's main.c. I've attached a patch that does
this (and also makes the main function in libf2c.so weak, just
in case). I've tested it in a sid chroot and at least my simple
hello example now compiles and runs. (Although linking that
against f2c is rather useless... But other programs will now
hopefully also work.)
Regards,
Christian
Description: Make MAIN__ a weak symbol
Make MAIN__ a weak symbol, to make sure that non-f2c binaries can link
against libraries created by it. Also make main() a weak symbol, just
in case, because we really don't want to override a C program's main
routine.
Author: Christian Seiler
--- a/main.c
+++ b/main.c
@@ -53,6 +53,20 @@ extern int MAIN__(void);
#define Int int
#endif
+/* Make main() a weak symbol. */
+int main(int argc, char **argv) __attribute__((weak));
+
+/* Create dummy MAIN__ function and make MAIN__ a weak alias to it.
+ * If linked against a program that exports MAIN__, i.e. one compiled
+ * by f2c, this MAIN__ will resolve to the program's MAIN__ instead,
+ * whereas normal C programs will still be able to link against this
+ * library. */
+static int weak_MAIN__()
+{
+ return -1;
+}
+extern int MAIN__() __attribute__((weak, alias("weak_MAIN__")));
+
static VOID sigfdie(Sigarg)
{
Use_Sigarg;
signature.asc
Description: OpenPGP digital signature
--- End Message ---
signature.asc
Description: OpenPGP digital signature
Bug#826255: RFS: obdgpslogger/0.16-1.3 [NMU]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "obdgpslogger" * Package name: obdgpslogger Version : 0.16-1.3 Upstream Author : Gary Briggs * URL : https://icculus.org/obdgpslogger/ * License : GPL-2+ Section : science It builds those binary packages: obdgpslogger - suite of tools to log OBDII and GPS data To access further information about this package, please visit the following URL: https://mentors.debian.net/package/obdgpslogger Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/obdgpslogger/obdgpslogger_0.16-1.3.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * Non-maintainer upload * Updated standards version to 3.9.8 - Changed VCS fields to use secure URI - Converted copyright to DEP5 * Updated compat level to 9 * Enabled parallel builds * Dropped versioned build-dep on cmake Many thanks David Jones
Re: help2man usage with pybuild / debhelper packaging workflow
On 03/06/16 17:59, Wookey wrote: On 2016-06-03 18:30 +0200, Christian Seiler wrote: On 06/03/2016 06:25 PM, Ghislain Vaillant wrote: And I don't mind for a handful of scripts. But what if you have 20 or 30? Well, you could add a custom target to debian/rules that calls help2man for all these scripts - so that you as a maintainer can refresh the manpages every now and then. (And store them in debian/ in the packaging.) That way, you don't break cross builds (manpages are pre-generated), but still automate it to a large extent. Yep, that's a reasonable plan. Ack. Missing man pages is better than things that gratuitously won't cross-build. So it is clearly a no-no. I guess the wiki page is here to give a starting point to write manpages, not automate the process of generating them. Just copying the help into a man page is mostly makework to shut lintian up. They are often very poor manpages. If the help is there already or upstream documentation is some other format (e.g. html), then if you _really_ can't be bothered making man pages, just leave it as upstream supplied. Using help2man is a worse 'solution' than doing nothing. In this case, should I leave the lintian warning on, or override it with a comment explaining why? Ghis
Bug#826255: marked as done (RFS: obdgpslogger/0.16-1.3 [NMU])
Your message dated Fri, 3 Jun 2016 17:46:17 + (UTC) with message-id <1385536383.7365355.1464975977113.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#826255: RFS: obdgpslogger/0.16-1.3 [NMU] has caused the Debian Bug report #826255, regarding RFS: obdgpslogger/0.16-1.3 [NMU] 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.) -- 826255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "obdgpslogger" * Package name: obdgpslogger Version : 0.16-1.3 Upstream Author : Gary Briggs * URL : https://icculus.org/obdgpslogger/ * License : GPL-2+ Section : science It builds those binary packages: obdgpslogger - suite of tools to log OBDII and GPS data To access further information about this package, please visit the following URL: https://mentors.debian.net/package/obdgpslogger Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/obdgpslogger/obdgpslogger_0.16-1.3.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * Non-maintainer upload * Updated standards version to 3.9.8 - Changed VCS fields to use secure URI - Converted copyright to DEP5 * Updated compat level to 9 * Enabled parallel builds * Dropped versioned build-dep on cmake Many thanks David Jones --- End Message --- --- Begin Message --- Hi, I sponsored the package on deferred/5 the rationale is: do you want to maintain it? the package is orphaned. Otherwise you might want to put the package under QA team and do a Qa upload instead (look e.g. fet package) thanks in advance for maintaining such useful tool! G. Il Venerdì 3 Giugno 2016 19:30, David Jones ha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "obdgpslogger" * Package name : obdgpslogger Version : 0.16-1.3 Upstream Author : Gary Briggs * URL : https://icculus.org/obdgpslogger/ * License : GPL-2+ Section : science It builds those binary packages: obdgpslogger - suite of tools to log OBDII and GPS data To access further information about this package, please visit the following URL: https://mentors.debian.net/package/obdgpslogger Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/obdgpslogger/obdgpslogger_0.16-1.3.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * Non-maintainer upload * Updated standards version to 3.9.8 - Changed VCS fields to use secure URI - Converted copyright to DEP5 * Updated compat level to 9 * Enabled parallel builds * Dropped versioned build-dep on cmake Many thanks David Jones--- End Message ---
Bug#821236: marked as done (RFS: netsed/1.2-2)
Your message dated Fri, 3 Jun 2016 18:03:36 + (UTC) with message-id <140325644.7333713.1464977016838.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#821236: RFS: netsed/1.2-2 has caused the Debian Bug report #821236, regarding RFS: netsed/1.2-2 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.) -- 821236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor of the package "netsed": Package name: netsed Version : 1.2-2 Upstream Author : Julien Viard de Galbert URL : http://silicone.homelinux.org/release/netsed/ License : GPL-2+ Section : net The source package builds a single binary package: netsed - network packet-altering stream editor Package information is available at http://mentors.debian.net/package/netsed The standard access to the package is via a dget command: dget -x http://mentors.debian.net/debian/pool/main/n/netsed/netsed_1.2-2.dsc Changes since last upload: * Step Standards-Version to 3.9.8, no changes. * Use debhelper in compatibility level 9. * debian/control: Path correction in Vcs-Git. Use HTTPS transport for Vcs-Git as well as for Vcs-Browser. Regards, Mats Erik Andersson --- End Message --- --- Begin Message --- Hi Mats! I sponsored the package a few seconds ago, sorry for the long wait! maybe next time put clearly in the title that this isn't an ITP but a package refresh. As you know, packages already in Debian have an higher priority, because they are already reviewed by a DD. BTW, I see you in the dm list for that package Fingerprint: 20BB3CCECFE50A6139A57E9A1BB375334D750376 Uid: Mats Erik Andersson Allow: netsed (7C0717F9FA2B2B9D788B141BA6DC24D9DA2493D1) who-permits-upload netsed Package: netsed DM: Mats Erik Andersson Sponsor: what did went wrong? thanks for your contribution to Debian! and sorry again for having to wait :) G.--- End Message ---
Bug#826266: RFS: dvtm/0.15-1~bpo8+1 ITP
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "dvtm" * Package name: dvtm Version : 0.15-1~bpo8+1 Upstream Author : Marc Andre Tanner * Url : http://www.brain-dump.org/projects/dvtm * Licenses: MIT/X Section : utils It builds those binary packages: dvtm -- Tiling window management for the console To access futher information about this package, visit the following URL: http://mentors.debian.net/package/dvtm Alternatively, one can download the package with dget using this command: http://mentors.debian.net/debian/pool/main/d/dvtm/dvtm_0.15-1~bpo8+1.dsc Alternatively, you can access package debian/ directory via git from URL: Sorry, git repository is not availiable More information about dvtm can be obtained from http://www.brain-dump.org/projects/dvtm Changes since last upload: * Rebuild for jessie-backports. Regards, Dmitry Bogatov
Bug#826268: RFS: diskscan/0.19-1~bpo8+1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for an updated bpo of "diskscan", and I filed a bpo request for it about two weeks ago. Please upload to delayed/15 to give Joao Eriberto Mota Filho pently of time to review/respond. Package name: diskscan Version: 0.19-1~bpo8+1 Section: utils It builds this binary package: diskscan - scan storage media for bad or near failure sectors To access further information about this package, please visit the following URL: https://mentors.debian.net/package/diskscan Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/diskscan/diskscan_0.19-1~bpo8+1.dsc Changes since the last upload: * Rebuild for jessie-backports. (Closes: #824812) Regards, Nicholas D Steeves
Bug#826266: RFS: dvtm/0.15-1~bpo8+1 ITP
control: owner -1 ! control: tags -1 moreinfo Hi, >http://mentors.debian.net/debian/pool/main/d/dvtm/dvtm_0.15-1~bpo8+1.dsc 404 G.
Bug#826266: RFS: dvtm/0.15-1~bpo8+1 ITP
> >http://mentors.debian.net/debian/pool/main/d/dvtm/dvtm_0.15-1~bpo8+1.dsc > 404 Sorry. Should work now. -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Keep-In-CC: yes X-Web-Site: sinsekvu.github.io
Bug#826135: RFS: lsvpd/1.7.6-1 ITP: lsvpd -- Utility to List Device Vital Product Data (VPD)
* Gianfranco Costamagna , 2016-06-02, 17:07: "License: GPL-2+ with librtas exception" maybe something like License: GPL-2+-with-librtas-exception "FOO with BAR exception" is a valid licence syntax in DEP-5. If it is not appropriate to use it in this case, then you should explain why, because it's not obvious. the difference is just removing the spaces, IIRC lintian was triggering issues on dep-5 format when spaces were used. Spaces are not allowed in license names. But here the license name is just “GPL-2+”. Let me quote the relevant part of the spec: “An exception or clarification to a license is signalled in plain text, by appending ‘with exception’ to the short name.” -- Jakub Wilk
Bug#826135: RFS: lsvpd/1.7.6-1 ITP: lsvpd -- Utility to List Device Vital Product Data (VPD)
Hi >Spaces are not allowed in license names. But here the license name is >just “GPL-2+”. > >Let me quote the relevant part of the spec: >“An exception or clarification to a license is signalled in plain text, >by appending ‘with exception’ to the short name.” probably when I tried a) this wasn't implemented b) I made some typo that triggered lintian warning. Happy to see this works correctly, so to the sponsoree, nevermind this part :) Thanks Jakub! Gianfranco
Bug#826266: marked as done (RFS: dvtm/0.15-1~bpo8+1 ITP)
Your message dated Fri, 3 Jun 2016 20:29:37 + (UTC) with message-id <508358965.7640274.1464985777598.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#826266: RFS: dvtm/0.15-1~bpo8+1 ITP has caused the Debian Bug report #826266, regarding RFS: dvtm/0.15-1~bpo8+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.) -- 826266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826266 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 "dvtm" * Package name: dvtm Version : 0.15-1~bpo8+1 Upstream Author : Marc Andre Tanner * Url : http://www.brain-dump.org/projects/dvtm * Licenses: MIT/X Section : utils It builds those binary packages: dvtm -- Tiling window management for the console To access futher information about this package, visit the following URL: http://mentors.debian.net/package/dvtm Alternatively, one can download the package with dget using this command: http://mentors.debian.net/debian/pool/main/d/dvtm/dvtm_0.15-1~bpo8+1.dsc Alternatively, you can access package debian/ directory via git from URL: Sorry, git repository is not availiable More information about dvtm can be obtained from http://www.brain-dump.org/projects/dvtm Changes since last upload: * Rebuild for jessie-backports. Regards, Dmitry Bogatov --- End Message --- --- Begin Message --- Hi, >Sorry. Should work now. uploaded. BTW I did a debdiff between testing and your package, some differences were found, but they are just different line endings on a couple of files, nothing important, so I sponsored it anyway. Please try to be more careful on the next upload debdiff found attached. G. debdiff Description: Binary data --- End Message ---
Bug#826268: marked as done (RFS: diskscan/0.19-1~bpo8+1)
Your message dated Fri, 3 Jun 2016 20:34:54 + (UTC) with message-id <775950226.7540059.1464986094624.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#826268: RFS: diskscan/0.19-1~bpo8+1 has caused the Debian Bug report #826268, regarding RFS: diskscan/0.19-1~bpo8+1 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.) -- 826268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for an updated bpo of "diskscan", and I filed a bpo request for it about two weeks ago. Please upload to delayed/15 to give Joao Eriberto Mota Filho pently of time to review/respond. Package name: diskscan Version: 0.19-1~bpo8+1 Section: utils It builds this binary package: diskscan - scan storage media for bad or near failure sectors To access further information about this package, please visit the following URL: https://mentors.debian.net/package/diskscan Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/diskscan/diskscan_0.19-1~bpo8+1.dsc Changes since the last upload: * Rebuild for jessie-backports. (Closes: #824812) Regards, Nicholas D Steeves --- End Message --- --- Begin Message --- Hi Nicholas >I am looking for a sponsor for an updated bpo of "diskscan", and I >filed a bpo request for it about two weeks ago. Please upload to >delayed/15 to give Joao Eriberto Mota Filho pently of time to >review/respond. well, this isn't requested by policy, but I guess much appreciated :) I sponsored on deferred/15 as requested :) thanks! Gianfranco--- End Message ---
Bug#826160: marked as done (RFS: node-getobject/0.1.0-2 -- set and get deep objects easily)
Your message dated Fri, 3 Jun 2016 23:01:36 +0200 with message-id <5751f030.60...@debian.org> and subject line RFS: node-getobject/0.1.0-2 -- set and get deep objects easily has caused the Debian Bug report #826160, regarding RFS: node-getobject/0.1.0-2 -- set and get deep objects easily 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.) -- 826160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "node-getobject" * Package name: node-getobject Version : 0.1.0-2 Upstream Author : "Cowboy" Ben Alman * URL : https://github.com/cowboy/node-getobject * License : MIT Section : web It builds those binary packages: libjs-getobject - set and get deep objects easily - library for browsers node-getobject - set and get deep objects easily - module for Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-getobject Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-getobject/node-getobject_0.1.0-2.dsc Or clone using this git command: git clone https://anonscm.debian.org/git/pkg-javascript/node-getobject.git The last commit should be signed with the same key as this email. More information about node-getobject can be obtained from https://github.com/cowboy/node-getobject. Changes since the last upload: * Fix Vcs-Git url * Fix autopkgtest command * Remove Testsuite entry from d/control * Updated standards version. No changes needed. * Use secure Vcs-Git url * Adjust priority to match the override of ftp-masters Regards, Jonathan Ulrich Horn signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- closing G. signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#826182: marked as done (RFS: libretro-beetle-pce-fast [ITP])
Your message dated Fri, 3 Jun 2016 23:05:40 +0200 with message-id <5751f124.8050...@debian.org> and subject line RFS: libretro-beetle-pce-fast [ITP] has caused the Debian Bug report #826182, regarding RFS: libretro-beetle-pce-fast [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.) -- 826182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Hey dear mentors! I'm looking for a sponsor for my package "libretro-beetle-pce-fast" This is the libretro port of Beetle/Mednafen "pce_fast" module, a TurboGrafx-16 / PC Engine emulator, with CD-ROM² support as well. It's a fork of Mednafen to fit better with the libretro API, so it's not possible to use the same source code of Mednafen package. * Package name : libretro-beetle-pce-fast Version : 0.9.36.1+git20160324-1 Upstream Author : Ryphecha / The RetroArch Team (beetle fork) * URL : https://github.com/libretro/beetle-pce-fast-libretro * License : GPL-2+ Programming Lang : C/C++ Description : port of Beetle/Mednafen PCE FAST to libretro API It builds those binary packages: libretro-beetle-pce-fast -- Libretro wrapper for the Beetle PCE FAST core To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libretro-beetle-pce-fast More information about RetroArch and the libretro API can be obtained fromhttp://www.libretro.com/index.php/api/ -- sergio-br2 --- End Message --- --- Begin Message --- closing, G. signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#811426: RFS: golang-github-kennygrant-sanitize/1.0-1 [ITP]
control: tags -1 moreinfo On Sun, 15 May 2016 15:59:09 + Mattia Rizzolo wrote: > On Mon, Jan 18, 2016 at 12:09:14PM -0800, Nathan Osman wrote: > > I am looking for a sponsor for my package > > "golang-github-kennygrant-sanitize" > > > http://mentors.debian.net/package/golang-github-kennygrant-sanitize > > please consider getting in touch with the pkg-go team, maintain the > package within the team and ask sponsorship there. setting moreinfo until the question is answered. G. > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > more about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: OpenPGP digital signature
Bug#816683: RFS: cloudabi-utils/0.8-1 [ITP]
control: tags -1 moreinfo Setting moreinfo until the blocking bug is resolved. G. signature.asc Description: OpenPGP digital signature
Bug#814680: RFS: stp/2.1.2+dfsg-1 [ITP] -- Simple theorem prover
control: tags -1 moreinfo Hi, On Wed, 9 Mar 2016 20:48:46 -0800 Afif Elghraoui wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, Marko, > > On اÙØ£Øد 6 آذار 2016 14:53, Marko DimjaÅ¡eviÄ wrote: > > > > On Fri, 2016-02-26 at 17:42 -0800, Afif Elghraoui wrote: > >> Something like the following: > >> > [...] > > Thank you Afif for this! > > > > No problem. > > > I am not sure what is the cause (maybe incorrect paths in > > debian/rules), but when I try to build with gbp like this: > > > [...] > > > > Any clue what went wrong? > > > > I looked at the tests/query-files/lit.cfg config file/script in > > question, but I don't see why it would fail. > > > > > > The second tarball gets extracted to outputcheck/ (directory name is > based on the name of the subcomponent according to the 3.0 format). It > looks like your code expects it in a subdirectory of utils, so I would > put a symlink there as part of the build process or adjust the script > to find it in outputcheck/ rather than utils/. > > I believe you can also get rid of the code to extract the outputcheck > tarball in the first place. The conventions for the package format > should take care of preparing the source tree. > > regards > Afif > any news on this? Gianfranco signature.asc Description: OpenPGP digital signature
Bug#816652: RFS: compiz/1:0.9.12.2 [ITP:722451]
control: tags -1 moreinfo Setting moreinfo tags, until the first review is fixed. Gianfranco signature.asc Description: OpenPGP digital signature
Re: help2man usage with pybuild / debhelper packaging workflow
Hello, On Fri, Jun 03, 2016 at 06:30:05PM +0200, Christian Seiler wrote: > Well, you could add a custom target to debian/rules that calls > help2man for all these scripts - so that you as a maintainer > can refresh the manpages every now and then. (And store them > in debian/ in the packaging.) That way, you don't break cross > builds (manpages are pre-generated), but still automate it to > a large extent. This is what I do with OCRmyPDF: I do a binary package build, install it, update the manpage, and then prepare a source package for upload to the archive/mentors. I disagree that help2man's manpages are always worse than doing nothing. I frequently make reference to the ocrmypdf manpage myself and don't find it lacking! Each individual help2man manpage should be evaluated on its own merits; you certainly should read everything it generates for your 20--30 scripts. -- Sean Whitton signature.asc Description: PGP signature
Bug#826293: RFS: bit-babbler/0.5~bpo8+1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my trivial backport of "bit-babbler". I have already gotten Ron Lee's blessing to maintain the backport, and to add myself to Uploaders for the backport. We also discussed the Lintian I, P, and W warnings, and I fully support Ron's reasoning for why these do not or should not be fixed. Package name: bit-babbler Version: 0.5~bpo8+1 Section: admin It builds those binary packages: bit-babbler - BitBabbler hardware TRNG and kernel entropy source support bit-babbler-dbg - debugging symbols for BitBabbler tools To access further information about this package, please visit the following URL: https://mentors.debian.net/package/bit-babbler Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/b/bit-babbler/bit-babbler_0.5~bpo8+1.dsc Regards, Nicholas D Steeves
Bug#821270: marked as done (RFS: firefox-branding-iceweasel/0.3.0 [ITP] -- Preserves Iceweasel branding for new Firefox packages)
Your message dated Sat, 4 Jun 2016 12:18:50 +0900 with message-id <20160604031850.ga7...@artemis.silentflame.com> and subject line Re: Bug#821270: Review of git version has caused the Debian Bug report #821270, regarding RFS: firefox-branding-iceweasel/0.3.0 [ITP] -- Preserves Iceweasel branding for new Firefox packages 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.) -- 821270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821270 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 "firefox-branding-iceweasel" * Package name: firefox-branding-iceweasel Version : 0.3.0 Upstream Author : nord-stream * URL : https://notabug.org/desktopd/iceweasel-branding * License : MPL-2.0 Section : web It builds those binary packages: firefox-branding-iceweasel - Preserves Iceweasel branding for new Firefox packages To access further information about this package, please visit the following URL: http://mentors.debian.net/package/firefox-branding-iceweasel Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/f/firefox-branding-iceweasel/firefox-branding-iceweasel_0.3.0.dsc More information about this package can be obtained from https://notabug.org/desktopd/iceweasel-branding. Changelog: * Initial Debian packaging. * Removed support for older Firefox releases (<45.0). Regards, nord-stream signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Fri, Jun 03, 2016 at 10:09:44AM +, Gianfranco Costamagna wrote: > Hi, after the latest fixes I put the package in deferred/5, to leave > Sean enough time to review it and ack the latest changes. Assuming you mean commit 6f2573d50 (since I can't obtain the NEW package from the deferred queue) -- looks good. Let me echo Gianfranco's thanks for your contribution and patience working through the RFS. And thanks for Gianfranco for his input and the sponsorship. -- Sean Whitton signature.asc Description: PGP signature --- End Message ---
Re: help2man usage with pybuild / debhelper packaging workflow
On Sat, Jun 4, 2016 at 12:30 AM, Christian Seiler wrote: > Well, you could add a custom target to debian/rules that calls > help2man for all these scripts - so that you as a maintainer > can refresh the manpages every now and then. (And store them > in debian/ in the packaging.) That way, you don't break cross > builds (manpages are pre-generated), but still automate it to > a large extent. I don't think it is ever appropriate to store pre-generated files in source packages, neither in the upstream tarball nor in the Debian tarball (except for autotools cruft or VCS metadata through autorevision). For Python stuff, it is generally arch all and never needs to be cross-built so help2man is fine. In any case, using something like sphinx and sphinxcontrib-autoprogram or python3-sphinx-argparse plus manual page source in Markdown or reStructuredText format is a better way to go since you get a nice format to write in and automatically sync your --help output with the manual page. -- bye, pabs https://wiki.debian.org/PaulWise
Bug#820644: RFS: libretro-snes9x [ITP]
Ok, they are fixed. Copyright stuff fixed too; libretro folder should be the same license as the core, since libretro.c/cpp is based in the main loop file of the emulators (snes9x.cpp for example). cheers, sergio-br2 On Thu, 2 Jun 2016 17:28:00 +0200 Gianfranco Costamagna wrote: > control: owner -1 ! > control: tags -1 moreinfo > > can you please fix the lintian stuff? > > http://debomatic-amd64.debian.net/distribution#unstable/libretro-snes9x/1.53+git20151206-1/lintian > > specially the copyright stuff. > > G.
