Bug#873459: RFS: python-singa/1.1.1-1 [ITP]
On Mon, Aug 28, 2017 at 09:12:17AM +0800, Moaz Reyad wrote: > > I am looking for a sponsor for my package "python-singa" > > dget -x > https://mentors.debian.net/debian/pool/main/p/python-singa/python-singa_1.1.1-1.dsc Hi Moaz, your orig.tar.gz seems to contain the complete git history from upstream, which doesn't seem to useful. I suggest redoing the orig without the .git subdirectory. Kind Regards Andreas -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 signature.asc Description: PGP signature
Re: git problem with upstream branch
On Sat, Sep 16, 2017 at 11:08:41AM +0200, Felix Natter wrote: > I have pushed all branches here: > https://anonscm.debian.org/cgit/pkg-java/knopflerfish-osgi.git > > I think I am safe, did I miss anything? Looks fine to me. -- WBR, wRAR signature.asc Description: PGP signature
Bug#875973: RFS: glogic/2.6-3
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "glogic" * Package name: glogic Version : 2.6-3 Upstream Author : Koichi Akabe* URL : https://launchpad.net/glogic * License : GPL-3 Section : electronics It builds those binary packages: glogic - graphical logic circuit simulator To access further information about this package, please visit the following URL: https://mentors.debian.net/package/glogic Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/glogic/glogic_2.6-3.dsc The package is also on git https://anonscm.debian.org/git/collab-maint/glogic.git Changes since the last upload: * New maintainer (Closes: #864582). + Changed Maintainer field in debian/control file. + Add copyright information for debian files in debian/copyright file. * Add Vcs-Browser and Vcs-Git on debian/control file. * Standards version 4.1.0. + Bumped compat level and debhelper to 10. * Aplied patch write by Jakob Haufe (Closes: #782557 LP: #1422501 LP: #1459027). * Aplied patch for add Keywords field to data/glogic.desktop.in file. * Aplied two patch to erase external HTML link. Regards, Innocent De Marchi
Bug#875804: RFS: robocut/1.0.11-1-- Control program for Graphtec cutting plotters
On Thu, Sep 14, 2017 at 12:10:01PM -0400, Markus Schulz wrote: > > I am looking for a sponsor for my package "robocut": Hello Markus, I'm not a DD so can't sponsor your package, but here's a review: - Please consider using a dep5-style copyright file (https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/) - Please check if your package complies to the current version of the Debian Policy, which is version 4.1.0 (https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt) - There's an empty debian/robocut.menu file, it should be removed Cheers, Andreas -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 signature.asc Description: PGP signature
Bug#875949: RFS: libsml/0.1.1+git20170608-2
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libsml" * Package name: libsml Version : 0.1.1+git20170608-2 Upstream Author : Juri Glass, Mathias Runge, Nadim El Sayed,DAI-Labor (TU-Berlin) * URL : https://github.com/dailab/libsml/ * License : GPL Section : libs It builds those binary packages: libsml-dev - Header files for libSML libsml1- Library for the Smart Messaging Language (SML) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libsml Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libs/libsml/libsml_0.1.1+git20170608-2.dsc Here's the changelog: libsml (0.1.1+git20170608-2) unstable; urgency=medium * Add patch to allow building on non-Linux. (Closes: #873895) * Use O_NONBLOCK where available (Closes: #873894) * Declare compatibility with Policy 4.1.0 I look forward to any comments and reviews! Thanks! Regards, Andreas Moog -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 signature.asc Description: PGP signature
Re: Bug#875764: RFS: pybind11/2.2.1-1 [experimental]
Hi Ghislain Vaillant, > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for the following package: > > * Package name : pybind11 > Version : 2.2.1-1 > Upstream Author : Wenzel Jakob> * URL : https://github.com/pybind/pybind11 > * License : BSD > Section : libs > > Please check out the package by visiting the following URL: > > https://anonscm.debian.org/git/debian-science/packages/pybind11.git > > Changes since last upload: > > * New upstream version 2.2.1 > * Drop the patch queue, no longer required > * Prevent multiple install of headers > * Add new test dependency on Boost > * Test query of includes via pybind11 > * Add recommended get-orig-source target > * Fixup the nocheck and nodoc guards > - Replace occurrences of findstring with filter > - Use DEB_BUILD_OPTIONS instead of DEB_BUILD_PROFILES > * Fixup whitespacing in rules file > * Drop superfluous dependency on python-pytest > * Filter egg-info directory with extend-diff-ignore > * Fixup the Vcs-Browser URI > * Bump the standards version to 4.1.0 > There are some files that have headers with - Copyright (c) 2017. But debian/copyright file was not refreshed. Please update debian/copyright file. Regards, Herbert
Re: Bug#875876: RFS: python-dtcwt/0.12.0-1
The copyright you quoted applies to the code from the original implementation in MATLAB. This code is a complete rewrite in Python, so the original copyright should not apply. Not sure why this file is provided since the two code bases are different. Anyway I am open to hear from a second opinion from d-legal. Ghis Le 16 sept. 2017 11:20, "Herbert Fortes"a écrit : > Hi Ghislain Vaillant, > > > Package: sponsorship-requests > > Severity: normal > > > > Dear mentors, > > > > I am looking for a sponsor for my package "python-dtcwt" > > > > * Package name: python-dtcwt > > Version : 0.12.0-1 > > Upstream Author : Rich Wareham > > * URL : https://github.com/rjw57/dtcwt > > * License : BSD > > Section : science > > > > Cc: debian-legal > > > python-dtcwt is in Debian since 2015, but ORIGINAL_README.txt[0] > file is a bit problematic. I need someone to do a second check on > copyright. > > [0] - https://anonscm.debian.org/git/debian-science/packages/ > python-dtcwt.git/tree/ORIGINAL_README.txt > > It is said: > > "This code is copyright and is supplied free of charge for research > purposes only. In return for supplying the code, all I ask is that, if > you use the algorithms, you give due reference to this work in any > papers that you write and that you let me know if you find any good > applications for the DT CWT. If the applications are good, I would be > very interested in collaboration. I accept no liability arising from use > of these algorithms." > > - ... free of charge for research only ... > - ... all I ask is ... let me know if you find any good ... > > The package is BSD, but COPYING.txt file says: > > "This licence applies to any parts of this library which are novel in > comparison > to the original DTCWT MATLAB toolbox written by Nick Kingsbury and Cian > Shaffrey. See the ORIGINAL_README.txt file for details on any further > restrictions of use." > > It does not look to be in "main" to me. > > > > Regards, > Herbert > >
Re: Bug#875876: RFS: python-dtcwt/0.12.0-1
Hi Ghislain Vaillant, > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "python-dtcwt" > > * Package name : python-dtcwt > Version : 0.12.0-1 > Upstream Author : Rich Wareham> * URL : https://github.com/rjw57/dtcwt > * License : BSD > Section : science > Cc: debian-legal python-dtcwt is in Debian since 2015, but ORIGINAL_README.txt[0] file is a bit problematic. I need someone to do a second check on copyright. [0] - https://anonscm.debian.org/git/debian-science/packages/python-dtcwt.git/tree/ORIGINAL_README.txt It is said: "This code is copyright and is supplied free of charge for research purposes only. In return for supplying the code, all I ask is that, if you use the algorithms, you give due reference to this work in any papers that you write and that you let me know if you find any good applications for the DT CWT. If the applications are good, I would be very interested in collaboration. I accept no liability arising from use of these algorithms." - ... free of charge for research only ... - ... all I ask is ... let me know if you find any good ... The package is BSD, but COPYING.txt file says: "This licence applies to any parts of this library which are novel in comparison to the original DTCWT MATLAB toolbox written by Nick Kingsbury and Cian Shaffrey. See the ORIGINAL_README.txt file for details on any further restrictions of use." It does not look to be in "main" to me. Regards, Herbert
Bug#875938: RFS: minetest-mod-infinite-chest/1.0.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "minetest-mod-infinite-chest" * Package name: minetest-mod-infinite-chest Version : 1.0.0-1 Upstream Author : Brett O'Donnell * URL : https://github.com/cornernote/minetest-infinite_chest * License : Expat Section : games It builds those binary packages: minetest-mod-infinite-chest - Minetest module to get chests with an infinite number of slots To access further information about this package, please visit the following URL: https://mentors.debian.net/package/minetest-mod-infinite-chest Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/minetest-mod-infinite-chest/minetest-mod-infinite-chest_1.0.0-1.dsc It is packaged within the Debian Games Team: Vcs-Git: https://anonscm.debian.org/git/pkg-games/minetest-mod-infinite-chest.git Vcs-Browser: https://anonscm.debian.org/git/pkg-games/minetest-mod-infinite-chest.git Thanks, Snark on #debian-games
Bug#875937: RFS: minetest-mod-quartz/1.0.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "minetest-mod-quartz" * Package name: minetest-mod-quartz Version : 1.0.0-1 Upstream Author : EvergreenTree * URL : https://github.com/minetest-mods/quartz * License : Expat Section : games It builds those binary packages: minetest-mod-quartz - Minetest module to add quartz To access further information about this package, please visit the following URL: https://mentors.debian.net/package/minetest-mod-quartz Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/minetest-mod-quartz/minetest-mod-quartz_1.0.0-1.dsc It is packaged within the Debian Games Team: Vcs-Git: https://anonscm.debian.org/git/pkg-games/minetest-mod-quartz.git Vcs-Browser: https://anonscm.debian.org/git/pkg-games/minetest-mod-quartz.git Cheers, Snark on #debian-games
git problem with upstream branch
hello mentors, in the process of updating knopflerfish-osgi, I pulled the latest changes from master branch branch before adding my changes, but not from the upstream and pristine-tar branches (which contained upstream/5.2.0). So when I tried to push the new upstream/6.1.1, I had to pull, and of course got merge conflicts (while pulling): $ git push Enter passphrase for key '/home/felix/.ssh/id_rsa': To git+ssh://git.debian.org/git/pkg-java/knopflerfish-osgi.git ! [rejected]upstream -> upstream (non-fast-forward) error: failed to push some refs to 'git+ssh://fnatter-gu...@git.debian.org/git/pkg-java/knopflerfish-osgi.git' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g. hint: 'git pull ...') before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details. I aborted the merge, and ran: $ git pull --strategy=ours Merge made by the 'ours' strategy. (in order to keep the upstream/6.1.1 changes and discard the upstream/5.2.0 changes) which seems to work. The history is: $ git log -3 commit 8710f8e5d2b81805b82dc4a0f11d5dd20032a5a7 (HEAD -> upstream) Merge: b2511e0 0872330 Author: Felix NatterDate: Sat Sep 16 10:40:09 2017 +0200 Merge branch 'upstream' of git+ssh://git.debian.org/git/pkg-java/knopflerfish-osgi into upstream commit b2511e0431fdc9acbd2895bac3702f863de0944e (tag: upstream/6.1.1) Author: Felix Natter Date: Sat Sep 16 10:05:50 2017 +0200 New upstream version 6.1.1 commit 08723308d93f5675b1092003bc512b492aa5abe2 (tag: upstream/5.2.0, origin/upstream) Author: Emmanuel Bourg Date: Mon Oct 3 15:37:31 2016 +0200 New upstream version 5.2.0 $ git diff upstream/6.1.1..HEAD The package builds, and I see: [...] gbp:info: Creating knopflerfish-osgi_6.1.1.orig.tar.xz from 'upstream/6.1.1' [...] Regarding the pristine-tar branch, I just merged it without conflicts, of course. I have pushed all branches here: https://anonscm.debian.org/cgit/pkg-java/knopflerfish-osgi.git I think I am safe, did I miss anything? Thanks and Best Regards, -- Felix Natter debian/rules!
Re: debuild finds no secret key after dist-upgrade
On Fri, Sep 15, 2017 at 11:44:02PM +0200, Thomas Schmitt wrote: > > > - How to bring the original tarball's .sig file into the packaging ? > > > Convert it to .asc > > I could try to squeeze something out of > https://lists.gnupg.org/pipermail/gnupg-users/2011-November/043252.html > or > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832267 The bug report contains a recipe, using gpg --enarmor > but will probably generate such an .asc file from original data as soon > as i found out how it relates to the .asc payload wrapper which i generate > by gpg --clearsign. The only difference between .sig and .asc is that .asc is ASCII-armored. > > and read dpkg-source(1). > > I try hard. But what does it mean when it says > "tarball can be accompanied by a detached upstream signature" > ? I think I've already answered that. You need to put it in the same directory. > > > Can it [my key] be too old for the new gpg binary ? > > > Have you read https://www.gnupg.org/faq/whats-new-in-2.1.html#nosecring > > Yes. But it does not explain how the dist-upgrade of last year left > gpg in the state which after another dist-upgrade makes it inoperational. Most likely because the old dist-upgrade doesn't have anything to do with that. And the recent dist-upgrade changed your /usr/bin/gpg to v.2. > Something must have confused apt-get (or a layer underneath). Of course not. apt doesn't touch user files. > > Check /usr/bin/gpg2 or whatever it was called in the old gnupg2 package? > There is one and it does not see keys. You asked where did you get a v.2 GnuPG. Here is the answer. I didn't expect it to see the keys. > > please fix your workflow ASAP. > > I am thankful for your advise. But your instructions are far too short. Use sbuild or pbuilder. > It is not easy to navigate between contradicting DD styles and tool chains. > And then there is https://www.debian.org/doc/manuals/maint-guide/ ... https://www.debian.org/doc/manuals/maint-guide/build.en.html#pbuilder > I don't strive for becoming a Debian Maintainer. That doesn't matter. You are making packages for Debian. You ned to do that correctly. > Isn't any tool in the box which can make a Debian package out of a vanilla > autotools based tarball ? ./configure && make && make install Yes, but the result is not suitable for inclusion in Debian. > GUIX can, Arch can, Fedora can. I guess it's the same here. -- WBR, wRAR signature.asc Description: PGP signature