Bug#835559: RFS: python-jsmin/2.2.1-1
control: owner -1 ! control: tags -1 moreinfo Hi, >I'm looking for an sponsor for my updated package python-jsmin pull-debian-source python-jsmin dget -u https://mentors.debian.net/debian/pool/main/p/python-jsmin/python-jsmin_2.2.1-1.dsc debdiff python-jsmin*.dsc > debdiff lets look at the debdiff file: 1) + * Bump standards version. No changes needed. I would also say to which version, otherwise it will become useless after two or three bumps 2) + * Change my name on the control file to match the changelog. not a problem, but I would change both to have the first char as upper-case, instead of using all lowercase for your name 3) you are adding entries to a previous changelog entry + * Add pristine-tar to source VCS. (this appears to be a change in *this* release) 4) and changing one signature date of some old release - -- Gustavo Panizzo Wed, 23 Dec 2015 22:46:59 +0800 + -- Gustavo Panizzo Thu, 14 Jan 2016 23:46:59 +0800 python-all (>= 2.6.6-3~), + dh-python, ^^ there is a instead of spaces (this makes vim sad) I admit, they aren't really blockers, and the problem is in the git repo, where somebody committed something different from the version that has been uploaded in Debian. But I would take the opportunity to fix it once for all, starting from this version. What do you think about? G.
Bug#835368: marked as done (RFS: confinedrv/1.7.7-3 [ITP] -- Hi everyone!)
Your message dated Mon, 29 Aug 2016 07:23:44 + (UTC) with message-id <1725519862.1939818.1472455424...@mail.yahoo.com> and subject line Re: Bug#835368: RFS: confinedrv/1.7.7-3 [ITP] -- Hi everyone! has caused the Debian Bug report #835368, regarding RFS: confinedrv/1.7.7-3 [ITP] -- Hi everyone! 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.) -- 835368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Subject: RFS: confinedrv/1.7.7-3 [ITP] -- Hi everyone! Severity: wishlist Dear mentors, I am looking for a sponsor for my package "confinedrv": * Package name: confinedrv Version : 1.7.7-3 Upstream Author : Elmar Stellnberger * URL : https://www.elstel.org/qemu * License : C-FSL v1.0 Section : utils It is a little script with a man page wrapped into a package: confinedrv - mirror an existing drive but with confined access rights on a per-partition basis (ro/rw/zero/err); there is also a possibilty to use image files for the MBR as well as individual paritions. Every now and then I receive an email of people who like and successfully deploy the program. That is why I think it would be beneficial to promote this little helper script for device mapper into Debian and other distributions. It also shows that the script has proven quite useful in many situations. To access further information about this package, you may also visit the following URL: https://mentors.debian.net/package/confinedrv Alternatively, one can download the package with dget using this command: dget [-x] https://mentors.debian.net/debian/pool/main/c/confinedrv/confinedrv_1.7.7-3.dsc Information about confinedrv can be obtained from the documentation that ships with the package as well as online under https://www.elstel.org/qemu. What will also need to be analysed: The license in use, C-FSL v1.0 will still need to be reviewed. A predecessor license C-FSL v0.8 had already been discussed on debian-legal some time ago. However v1.0 has been reworked basing on the input I had received from there and should now hopefully be without issues. If you decide to review the license do not do it just for confinedrv but for all programs offered by elstel.org: bundsteg (printing with inner margin), xchroot (chroot for X11), debcheckroot (security aware alternative for debsums), dbschemacmd (tool to normalize database schemata), coan for Linux/Qt (coming soon; simulate deterministic / non-deterministic FA, PDA, Turing Machines) pubkey and SHA512SUMS.signed for all programs at elstel.org (DNSSEC/DANE supported) can be found at: https://www.elstel.org/software/SHA512SUMS.signed https://www.elstel.org/auxil/estellnb.pubkey.asc ( also: https://www.elstel.org/auxil/estellnb-offline.pubkey.asc ) Changes since the last upload: none; this package has been uploaded newly. Kind Regards, Elmar Stellnberger --- End Message --- --- Begin Message --- Hi, >Control: tags -1 wontfix > >As the license is non-free, tagging the RFS as wontfix: It cannot be uploaded >to main. >I did not check if if non-free would be possible as target. closing in the meanwhile, please reopen when you have a new package to review or a new license. G.--- End Message ---
Bug#831792: marked as done (RFS: scid/1:4.6.4+dfsg1-1 [ITA] -- chess database with play and training functionality)
Your message dated Mon, 29 Aug 2016 07:21:06 + (UTC) with message-id <589712779.1932427.1472455266...@mail.yahoo.com> and subject line Re: Bug#831792: RFS: scid/1:4.6.4+dfsg1-1 has caused the Debian Bug report #831792, regarding RFS: scid/1:4.6.4+dfsg1-1 [ITA] -- chess database with play and training functionality 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.) -- 831792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831792 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 "scid": * Package name: scid Version : 4.6.2-0.1 Upstream Author : Fulvio Benini * URL : http://scid.sf.net * License : GPL v2 Section : games It builds those binary packages: scid - chess database with play and training functionality scid-data - data files for scid, the chess database application To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scid Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scid/scid_4.6.2-0.1.dsc As advised by Gianfranco I've upload the package to mentors. It closes some other bugs not reproducible by the current version and is lintian clean (hope so :-)). Package development is on the following repo: https://gitlab.com/deb-pkg/scid Changes since the last upload: * Non-maintainer upload. * New upstream version. (Closes: #802196) * UCI engine settings works and doesn't show errors. (Closes: #801607) * Game list can be resized and changes total width of the window (Closes: #692300) * debian/control: - Bump to Standards-Version 3.9.8. No changes required. - Use tcl and tk default version provided by Debian. - Add libsnack2 (enabling sound) and tclsh to Depends on scid-data package. * debian/rules: - Link with '--as-needed' to fix FTBFS. (Closes: #772432) Thanks to Logan Rosen for patch. - Add hardening flags. - Fix executable permissions on some files. * debian/patches: - tcl_syntax: Add to fix syntax for Tcl/Tk script. - 01_datafolder.diff: Add to use a data dir variable. - 01_soundfolder.diff: Change to use share dir variable. - 01_Makefile.conf.diff: Change to use hardening/linking flags. - 01_configure_tclsh.diff: Remove, tcl default version provides tclsh. - 01_spellcorrection.diff: Remove, source file deleted by upstream. * debian/scid.dirs: Remove scidlet dir, it is not used anymore. * debian/scid.install: Remove copying to scidlet dir. * debian/scid-data.dirs: Add tcl dir as upstream installs it by default * debian/scid-data.install: Copy files to tcl dir. Regards, pgpU4_2wSecFo.pgp Description: PGP signature --- End Message --- --- Begin Message --- Hi Jose, >Thanks for advertising scid was orphaned. Added myself as adopter ;-) thanks for stepping in so fast, I sponsored it! G.--- End Message ---
Bug#831792: RFS: scid/1:4.6.4+dfsg1-1
Hi, can you please have a look at the build failures?
thanks
g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
-pthread -Wall -DZLIB -I/usr/include/tk -o src/sortcache.o -c
src/sortcache.cpp
g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
-pthread -Wall -DZLIB -I/usr/include/tk -o src/pgnparse.o -c src/pgnparse.cpp
g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
-pthread -Wall -DZLIB -I/usr/include/tk -o src/engine.o -c src/engine.cpp
src/engine.cpp: In member function 'int Engine::Think(MoveList*)':
src/engine.cpp:1482:51: warning: suggest parentheses around '&&' within '||'
[-Wparentheses]
if (mlist->Size() <= depth || depth >= 5 && IsMatingScore (bestScore)) {
break; }
^
g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
-pthread -Wall -DZLIB -I/usr/include/tk -o src/sc_base.o -c src/sc_base.cpp
In file included from src/gfile.h:26:0,
from src/scidbase.h:25,
from src/sc_base.cpp:21:
src/fastgame.h: In static member function 'static squareT
FastGame::decodeKing(squareT, byte)':
src/fastgame.h:436:63: error: narrowing conversion of '-9' from 'int' to 'char'
inside { } [-Wnarrowing]
static const char sqdiff[] = { 0, -9, -8, -7, -1, 1, 7, 8, 9};
^
src/fastgame.h:436:63: error: narrowing conversion of '-8' from 'int' to 'char'
inside { } [-Wnarrowing]
src/fastgame.h:436:63: error: narrowing conversion of '-7' from 'int' to 'char'
inside { } [-Wnarrowing]
src/fastgame.h:436:63: error: narrowing conversion of '-1' from 'int' to 'char'
inside { } [-Wnarrowing]
src/fastgame.h: In static member function 'static squareT
FastGame::decodeKnight(squareT, byte)':
src/fastgame.h:450:91: error: narrowing conversion of '-17' from 'int' to
'char' inside { } [-Wnarrowing]
static const char sqdiff[] = { 0, -17, -15, -10, -6, 6, 10, 15, 17, 0, 0, 0, 0,
0, 0, 0 };
^
src/fastgame.h:450:91: error: narrowing conversion of '-15' from 'int' to
'char' inside { } [-Wnarrowing]
src/fastgame.h:450:91: error: narrowing conversion of '-10' from 'int' to
'char' inside { } [-Wnarrowing]
src/fastgame.h:450:91: error: narrowing conversion of '-6' from 'int' to 'char'
inside { } [-Wnarrowing]
Makefile:334: recipe for target 'src/sc_base.o' failed
G.
Bug#831792: RFS: scid/1:4.6.4+dfsg1-1
> Hi, can you please have a look at the build failures?
>
> thanks
>
>
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
> -pthread -Wall -DZLIB -I/usr/include/tk -o src/sortcache.o -c
> src/sortcache.cpp
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
> -pthread -Wall -DZLIB -I/usr/include/tk -o src/pgnparse.o -c
> src/pgnparse.cpp
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
> -pthread -Wall -DZLIB -I/usr/include/tk -o src/engine.o -c src/engine.cpp
> src/engine.cpp: In member function 'int Engine::Think(MoveList*)':
> src/engine.cpp:1482:51: warning: suggest parentheses around '&&' within '||'
> [-Wparentheses]
> if (mlist->Size() <= depth || depth >= 5 && IsMatingScore (bestScore)) {
> break; }
> ^
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
> -pthread -Wall -DZLIB -I/usr/include/tk -o src/sc_base.o -c src/sc_base.cpp
> In file included from src/gfile.h:26:0,
> from src/scidbase.h:25,
> from src/sc_base.cpp:21:
> src/fastgame.h: In static member function 'static squareT
> FastGame::decodeKing(squareT, byte)':
> src/fastgame.h:436:63: error: narrowing conversion of '-9' from 'int' to
> 'char' inside { } [-Wnarrowing]
> static const char sqdiff[] = { 0, -9, -8, -7, -1, 1, 7, 8, 9};
> ^
> src/fastgame.h:436:63: error: narrowing conversion of '-8' from 'int' to
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:436:63: error: narrowing conversion of '-7' from 'int' to
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:436:63: error: narrowing conversion of '-1' from 'int' to
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h: In static member function 'static squareT
> FastGame::decodeKnight(squareT, byte)':
> src/fastgame.h:450:91: error: narrowing conversion of '-17' from 'int' to
> 'char' inside { } [-Wnarrowing]
> static const char sqdiff[] = { 0, -17, -15, -10, -6, 6, 10, 15, 17, 0, 0, 0,
> 0, 0, 0, 0 };
> ^
> src/fastgame.h:450:91: error: narrowing conversion of '-15' from 'int' to
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:450:91: error: narrowing conversion of '-10' from 'int' to
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:450:91: error: narrowing conversion of '-6' from 'int' to
> 'char' inside { } [-Wnarrowing]
> Makefile:334: recipe for target 'src/sc_base.o' failed
Hi Gianfranco,
I've uploaded a new revision to mentors[0] that fixes errors on building for
some architectures.
Thanks again!
Regards,
[0]https://mentors.debian.net/package/scid
pgpnFeGmljER2.pgp
Description: PGP signature
Bug#835559: RFS: python-jsmin/2.2.1-1
On Mon, Aug 29, 2016 at 07:17:47 +, Gianfranco Costamagna wrote: > control: owner -1 ! > control: tags -1 moreinfo > > Hi, > > >I'm looking for an sponsor for my updated package python-jsmin > > > pull-debian-source python-jsmin > > dget -u > https://mentors.debian.net/debian/pool/main/p/python-jsmin/python-jsmin_2.2.1-1.dsc > > debdiff python-jsmin*.dsc > debdiff > > lets look at the debdiff file: > > 1) + * Bump standards version. No changes needed. ok > > > I would also say to which version, otherwise it will become useless after two > or three bumps > > > 2) + * Change my name on the control file to match the changelog. > > > not a problem, but I would change both to have the first char as upper-case, > instead of using > all lowercase for your name > > > 3) you are adding entries to a previous changelog entry > + * Add pristine-tar to source VCS. > > > (this appears to be a change in *this* release) > > > 4) and changing one signature date of some old release > > - -- Gustavo Panizzo Wed, 23 Dec 2015 22:46:59 +0800 > + -- Gustavo Panizzo Thu, 14 Jan 2016 23:46:59 +0800 commit b9bd75f323f772460e07da19d875ee8366f93bdf is to blame, I did the change that. I guess the uploader didn't pull after I pushed. good catch, thanks > > python-all (>= 2.6.6-3~), > + dh-python, > > > ^^ there is a > instead of spaces (this makes vim sad) done, i'm surprised wrap-and-sort didn't fix it > > I admit, they aren't really blockers, and the problem is in the git repo, > where somebody > committed something different from the version that has been uploaded in > Debian. > But I would take the opportunity to fix it once for all, starting from this > version. > > What do you think about? I've pushed again to alioth and mentors, thanks for your review > > G. -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa signature.asc Description: PGP signature
Bug#831792: RFS: scid/1:4.6.4+dfsg1-1
hi, done! thanks, G.
Bug#835559: marked as done (RFS: python-jsmin/2.2.1-1)
Your message dated Mon, 29 Aug 2016 15:46:14 + (UTC) with message-id <446805782.2505048.1472485574...@mail.yahoo.com> and subject line Re: Bug#835559: RFS: python-jsmin/2.2.1-1 has caused the Debian Bug report #835559, regarding RFS: python-jsmin/2.2.1-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.) -- 835559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Hello I'm looking for an sponsor for my updated package python-jsmin It builds python-jsmin and python3-jsmin This package contains a new upstream release. python-jsmin (2.2.1-1) unstable; urgency=medium * New upstream release * Bump standards version. No changes needed. * Change my name on the control file to match the changelog. * Update copyright years. * Use https url for Vcs-Git url * Add dh-python to build depends. The package is maintained on collab-main using git Package can be built doing this $ gbp clone https://anonscm.debian.org/cgit/collab-maint/python-jsmin.git $ cd python-jsmin $ gbp buildpackage (--git-pbuilder is optional) Alternatively, it can be downloaded from mentors https://mentors.debian.net/debian/pool/main/p/python-jsmin/python-jsmin_2.2.1-1.dsc I'm a DM, I'd happily accept DM permissions to upload it to the archive thanks! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi Gustavo >done, i'm surprised wrap-and-sort didn't fix it me too :) probably wrap-and-sort -sa would have worked >I've pushed again to alioth and mentors, thanks for your review and I pushed on ftpmaster. I gave you dm, even if this package wasn't perfect, but the changes were probably not completely your fault, but a mix of race conditions about you and your previous sponsor. Please be more careful next time :) (unfortunately when somebody else uploads your stuff this kind of things happens, mentors is outdated, git isn't pushed and so on. When somebody do all the work by himself it is easier to avoid such mistakes, this is why I would prefer you to upload your package :) ) happy hacking, Gianfranco--- End Message ---
Bug#835975: RFS: triops/9.0-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "triops" Package name: triops Version : 9.0-1 Upstream Author : Roberto S. Galende URL : http://github.com/circulosmeos/triops License : GPL 3 Section : utils It builds those binary packages: triops - safely and securely encrypt and decrypt files from cmdline To access further information about this package, please visit the following URL: https://mentors.debian.net/package/triops Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/t/triops/triops_9.0-1.dsc More information about hello can be obtained from https://www.example.com. Regards, Roberto S. Galende
Bug#835975: RFS: triops/9.0-1 [ITP]
Control: tags -1 + moreinfo * Roberto S. Galende , 2016-08-29, 18:58: https://mentors.debian.net/debian/pool/main/t/triops/triops_9.0-1.dsc I had only a quick look at the package, but code like this: // needed by createIV_v3 srand((unsigned) time(NULL)); and iv->rand1=rand()*rand(); makes me think this is very immature and not suitable for Debian at this time. Please: 1) Document the exact algorithm and file format you use. 2) Have the design and the code reviewed by a cryptography expert. 3) Write a comprehensive test suite. 4) Gain a significant user-base. Then you can think about getting your software into Debian. -- Jakub Wilk
[ITA] muse-el, with issues, and questions
Hi, I'm adopting muse-el. Right now it's a work-in-progress. The steps I took to fixup this package can be found here: https://github.com/sten0/muse-el clone: https://github.com/sten0/muse-el.git I've also uploaded a package, with "-sa" full sources for review here: https://mentors.debian.net/package/muse-el https://mentors.debian.net/debian/pool/main/m/muse-el/muse-el_3.20+dfsg-1.dsc I'm not sure what to make of lintian Error "license-problem-gfdl-invariants" against the README. The README says: The Muse manual is available under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, and with the Front-Cover texts and Back-Cover Texts as specified in the manual. Does the README itself also fall under the GFDL or GPL-3? If not, I'll have to add another exclusion to debian/copyright. Additionally, should I break out the documentation into a non-free muse-el-doc package? Finally, is now the time to fix the debian-rules-missing-recommended-target warning? I'm saving homepage and Vcs fields for last. Regards, Nicholas
Re: [ITA] muse-el, with issues, and questions
On 29 August 2016 at 16:49, Nicholas D Steeves wrote: > Hi, > > I'm adopting muse-el. Right now it's a work-in-progress. The steps I > took to fixup this package can be found here: > > https://github.com/sten0/muse-el > clone: https://github.com/sten0/muse-el.git > > I've also uploaded a package, with "-sa" full sources for review here: > https://mentors.debian.net/package/muse-el > https://mentors.debian.net/debian/pool/main/m/muse-el/muse-el_3.20+dfsg-1.dsc > > I'm not sure what to make of lintian Error > "license-problem-gfdl-invariants" against the README. The README > says: > The Muse manual is available under the terms of the GNU Free > Documentation License, Version 1.2 or any later version published by > the Free Software Foundation; with no Invariant Sections, and with the > Front-Cover texts and Back-Cover Texts as specified in the manual. > > Does the README itself also fall under the GFDL or GPL-3? If not, > I'll have to add another exclusion to debian/copyright. Additionally, > should I break out the documentation into a non-free muse-el-doc > package? > > Finally, is now the time to fix the > debian-rules-missing-recommended-target warning? I'm saving homepage > and Vcs fields for last. > > Regards, > Nicholas Also in the queue are: * Add quilt patch to view files with "see" rather than "open". (Closes: #720126) * What about #621697? "byte compile muse-autoloads.el?" Good idea? * What about #663750? "muse info file missing" from texi/muse.info? * What about #720121? "examples/QuickStart.muse png images in package" - /usr/share/doc/muse-el/examples/QuickStart.muse uses two image files muse-made-with.png and emacs-muse.png And also possibly integrating the attached authors into debian/copyright. Muse This is a listing of those who have made contributions of code or documentation to Muse. John Wiegley: Original author Michael Olson: Current maintainer Adrian Aichner: Contributor: - muse-publish.el: 2 lines changes Florian Beck: Contributor: - muse-regexps.el: 1 line changed Karl Berry: Contributor: - muse-latex.el: 5 lines changed Jean Magnan de Bornier: Author of muse-context.el, Contributor (assigned past and future changes) Trent Buck: Contributor: - muse-latex.el: 4 lines changed Sacha Chua: Contributor -- documentation (assigned past and future changes) Brad Collins: Author of: - muse-protocols.el - examples/muse.rnc schema Contributor (assigned past and future changes) Li Daobing: Author of muse-mathml.el, Contributor (assigned past and future changes) Wang Diancheng: Contributor: - muse-publish.el: 1 line changed - muse-regexps.el: 6 lines changed Clinton Ebadi: Contributor: - muse-html.el: 4 lines changed - muse-latex2png: 3 lines changed Bastien Guerry: Contributor (assigned past and future changes) Magnus Henoch: Contributor: - muse.el: 1 line changed Yann Hodique: Author of muse-wiki.el, Contributor (assigned past and future changes) Markus Hoenicka: Contributor (assigned past and future changes) Andrew J. Korty: Author of muse-groff.el (assigned past and future changes) Sasha Kovar: Contributor - muse-blosxom.el: >15 lines changed Bradley M. Kuhn: Contributor -- documentation - muse.texi: 9 lines changed Peter K. Lee: Contributor (assigned past and future changes) Na Li: Contributor: - muse-latex2png.el: 1 line changed Phillip Lord: Author of: - muse-split.el - muse-protocol-iw.el Contributor (assigned past and future changes) Chris Lowis: Contributor: - muse-latex2png.el: 1 line changed Deus Max: Contributor: - muse-publish.el: 2 lines changed Evan Monroig: Contributor: - muse.el: 2 lines changed Alex Ott: Contributor: - muse-html.el: 13 lines changed - muse-publish.el: 2 lines changed Jim Ottaway: Author of muse-backlink.el, Contributor (assigned past and future changes) Elena Pomohaci: Author of: - muse-import-docbook.el - muse-import-xml.el (assigned past and future changes) Andrea Riciputi: Idea taken from code, but re-implemented Stefan Schlee: Contributor - muse-mode: >15 lines changed - muse-protocols.el: 1 line changed - muse.texi: 7 lines changed (assigned past and future changes) Per B. Sederberg: Contributor (assigned past and future changes) René Stadler: Contributor: - muse-journal.el: 1 line cha
Re: [ITA] muse-el, with issues, and questions
On 29/08/16 21:49, Nicholas D Steeves wrote: > Hi, > > I'm adopting muse-el. Right now it's a work-in-progress. The steps I > took to fixup this package can be found here: > > https://github.com/sten0/muse-el > clone: https://github.com/sten0/muse-el.git > > I've also uploaded a package, with "-sa" full sources for review here: > https://mentors.debian.net/package/muse-el > https://mentors.debian.net/debian/pool/main/m/muse-el/muse-el_3.20+dfsg-1.dsc > > I'm not sure what to make of lintian Error > "license-problem-gfdl-invariants" against the README. The README > says: > The Muse manual is available under the terms of the GNU Free > Documentation License, Version 1.2 or any later version published by > the Free Software Foundation; with no Invariant Sections, and with the > Front-Cover texts and Back-Cover Texts as specified in the manual. > > Does the README itself also fall under the GFDL or GPL-3? If not, > I'll have to add another exclusion to debian/copyright. Additionally, > should I break out the documentation into a non-free muse-el-doc > package? This seems to be bug #695783 which was fixed in 3.20+dfsg-0.1 by removing the manual. If you haven't repacked the source, the manual should still be removed so there shouldn't be a problem here. The copyright statement specifically refers to the Muse manual so the README file should be fine. Assuming there aren't any more cases of this in the package, you can probably override the lintian error (with a suitable comment). > Finally, is now the time to fix the > debian-rules-missing-recommended-target warning? I'm saving homepage > and Vcs fields for last. Yes, those targets are required by policy (even though there are masses of packages which don't implement them). Since you're adopting the package, I would rewrite the whole of d/rules using dh. James signature.asc Description: OpenPGP digital signature
Re: [ITA] muse-el, with issues, and questions
Hello, On Mon, Aug 29, 2016 at 10:15:08PM +0100, James Cowgill wrote: > > Finally, is now the time to fix the > > debian-rules-missing-recommended-target warning? I'm saving homepage > > and Vcs fields for last. > > Yes, those targets are required by policy (even though there are masses > of packages which don't implement them). Since you're adopting the > package, I would rewrite the whole of d/rules using dh. And indeed, with dh_elpa. http://pkg-emacsen.alioth.debian.org/elpa-hello/ -- Sean Whitton
Re: [ITA] muse-el, with issues, and questions
Hi Sean, On 29 August 2016 at 17:35, Sean Whitton wrote: > Hello, > > On Mon, Aug 29, 2016 at 10:15:08PM +0100, James Cowgill wrote: >> > Finally, is now the time to fix the >> > debian-rules-missing-recommended-target warning? I'm saving homepage >> > and Vcs fields for last. >> >> Yes, those targets are required by policy (even though there are masses >> of packages which don't implement them). Since you're adopting the >> package, I would rewrite the whole of d/rules using dh. > > And indeed, with dh_elpa. Of course, it would be horribly ungrateful of me to not use that bpo! ;-) That reminds me, the original reason I asked for it was for a magit-2.x bpo. > http://pkg-emacsen.alioth.debian.org/elpa-hello/ Thank you for the guide, it is very much appreciated :-) Cheers, Nicholas
Re: [ITA] muse-el, with issues, and questions
On 29 August 2016 at 17:15, James Cowgill wrote: > On 29/08/16 21:49, Nicholas D Steeves wrote: >> Hi, >> >> I'm adopting muse-el. Right now it's a work-in-progress. The steps I >> took to fixup this package can be found here: >> >> https://github.com/sten0/muse-el >> clone: https://github.com/sten0/muse-el.git >> >> I've also uploaded a package, with "-sa" full sources for review here: >> https://mentors.debian.net/package/muse-el >> https://mentors.debian.net/debian/pool/main/m/muse-el/muse-el_3.20+dfsg-1.dsc >> >> I'm not sure what to make of lintian Error >> "license-problem-gfdl-invariants" against the README. The README >> says: >> The Muse manual is available under the terms of the GNU Free >> Documentation License, Version 1.2 or any later version published by >> the Free Software Foundation; with no Invariant Sections, and with the >> Front-Cover texts and Back-Cover Texts as specified in the manual. >> >> Does the README itself also fall under the GFDL or GPL-3? If not, >> I'll have to add another exclusion to debian/copyright. Additionally, >> should I break out the documentation into a non-free muse-el-doc >> package? > > This seems to be bug #695783 which was fixed in 3.20+dfsg-0.1 by > removing the manual. If you haven't repacked the source, the manual > should still be removed so there shouldn't be a problem here. The > copyright statement specifically refers to the Muse manual so the README > file should be fine. Assuming there aren't any more cases of this in the > package, you can probably override the lintian error (with a suitable > comment). I did repack the source, making use of watch+copyright exclude files automation and also enabling crypto sig verification, because there were a number of comments in the source of the existing package that didn't match the alleged upstream source. My guess is the source was pulled from git, even though a tarball was cited as the source, because the numbers looked like they might be automatic timestamps. Also, it's now xz compressed, which I anticipated is something Gianfranco might hassle me about if I didn't enable haha. Thank you for the review! Nicholas
Re: [ITA] muse-el, with issues, and questions
Hello, On Mon, Aug 29, 2016 at 07:05:59PM -0400, Nicholas D Steeves wrote: > Also, it's now xz compressed, which I anticipated is something > Gianfranco might hassle me about if I didn't enable haha. If you're not uploading a new upstream version you can't change the tarball compression (unless you're changing the source package name, which I don't recommend, per our discussion on IRC). -- Sean Whitton signature.asc Description: PGP signature
Bug#820751: marked as done (RFS: emulationstation/2.0.1a-1 [ITP])
Your message dated Tue, 30 Aug 2016 04:30:39 + with message-id and subject line closing RFS: emulationstation/2.0.1a-1 [ITP] has caused the Debian Bug report #820751, regarding RFS: emulationstation/2.0.1a-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.) -- 820751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820751 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 "emulationstation" EmulationStation is a flexible, graphical front-end designed for keyboardless navigation of your retro game collection, across multiple systems. * Package name : emulationstation Version : 2.0.1a Upstream Author : Alec "Aloshi" Lofquist * URL :http://www.emulationstation.org * License : Expat / MIT Programming Lang : C++ Description : Graphical emulator front-end It builds those binary packages: emulationstation - Graphical emulator front-end To access further information about this package, please visit the following URL: https://mentors.debian.net/package/emulationstation -- Sérgio Benjamim --- End Message --- --- Begin Message --- Package emulationstation has been removed from mentors.--- End Message ---
How to solve "'float log2(float)' conflicts with a previous declaration"
Hi, I tried to fix the issue with the duplicated definition of log2 in clustalo in Git[1] but failed. It probably failed since even if I remove the line that should be excluded by #ifndef HAVE_LOG2 the problem persists and so I assume there is another log2 definition done somewhere. Any ideas? Kind regards Andreas. [1] https://anonscm.debian.org/cgit/debian-med/clustalo.git/tree/debian/patches/log2.patch -- http://fam-tille.de
