Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).
Hi Hilmar, > Did you get the updated debian.tar.xz I sent you? Consider to use that one. Yes, I did. Thank you! It arrived moments after I sent my last post. > Don't install a program into /usr/local. The package won't be accepted. My makefile has prefix defined for vguitar exe destination. ./Makefile:prefix = /usr/local ./Makefile:$(DESTDIR)$(prefix)/bin/vguitar What should this be? Nick Strauss https://www.nick-strauss.com
Bug#966253: RFS: devtodo/0.1.20-8 [QA] -- hierarchical, prioritised todo list manager
Hi. On Tue, 1 Sep 2020 08:27:34 +0300 Adrian Bunk wrote: > please always Cc people in the BTS, except for the maintainer noone gets > automatically subscribed. Will do. > > On Thu, 27 Aug 2020 11:41:48 +0300 Adrian Bunk wrote: > > > >* debian/rules: replaced override_dh_auto_install with > > > > dh_bash-completion > > > > for the installation of bash-completion code. > > > > > > This is not the correct name for the installed file: > > > /usr/share/bash-completion/completions/devtodo.bash-completion > > > > I think that the phrase just looks a bit confusing (my bad). What > > I meant is replaced override_dh_auto_install with dh_bash-completion > > addon. > > But it isn't doing the same. > > What I meant is that debdiff says when comparing 0.1.20-7 with 0.1.20-8: > > Files in first .deb but not in second > - > -rw-r--r-- root/root /usr/share/bash-completion/completioins/devtodo > > Files in second .deb but not in first > - > -rw-r--r-- root/root > /usr/share/bash-completion/completions/devtodo.bash-completion > > Your change fixes the typo in the directory name (good), > but it installs the file with the wrong name (bad). Yes, I really missed that filename on the debdiff. It's fixed now, thanks. Regards, Charles
Bug#969782: RFS: jag/0.3.8-1 -- arcade and puzzle 2D game
Hi Reiner, > I think the test is not yet working. > > jag is a graphical application, but you are not instructing autopkgtest > to start a (virtual) X server. > And even if this was working, what would this actually be testing? > > I think the autopkgtest is only passing because of the & which starts it > in the background (where it fails to start) and then the shell process exits > successfully? > > I would recommend to remove the test as it's currently not testing > anything (not even "superficially"). Writing a proper test for a game > is probablby quite difficult, though maybe someone else has a better > idea how this could be tested. I see, I removed the autopkgtest from the package. But in future updates I will see if I can deploy correctly. Whoever sponsors this package, I will be very grateful. Thanks! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
Bug#970047: RFS: xsd/4.0.0-9 [RC] -- XML Data Binding for C++
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "xsd": Package name: xsd Version : 4.0.0-9 Upstream Author : xsd-user Maillist URL : http://codesynthesis.com License : public-domain, GFDL-1.2, GPL-2+ and FLOSS Vcs : https://jff.email/cgit/xsd.git/ Section : devel It builds those binary packages: xsdcxx - XML Data Binding for C++ To access further information about this package, please visit the following URL: https://mentors.debian.net/package/xsd/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/x/xsd/xsd_4.0.0-9.dsc or from git https://jff.email/cgit/xsd.git/?h=release%2Fdebian%2F4.0.0-9 Changes since the last upload: xsd (4.0.0-9) unstable; urgency=medium . * Fix FTBFS with gcc-10 (Closes: #957999): - New debian/patches/0120-g++10.patch. * Migrate to debhelper 13: - Bump minimum debhelper-compat version in debian/control to = 13. * Fix FTCBFS: Use dpkg's buildtools.mk to export tools for make install. (Closes: #955728). Thanks to Helmut Grohne . * Declare compliance with Debian Policy 4.5.0 (No changes needed). * Use jdupes to change duplicate files into symlinks: - debian/rules: Add override_dh_link. - debian/control: Add Build-Depend jdupes. - debian/xsdcxx.lintian-overrides: Remove duplicate-files. * Switch to debhelper-compat: - debian/control: Replace debhelper with debhelper-compat. - Remove debian/compat. * debian/control: - Switch Vcs-* to new location. - Add Rules-Requires-Root: no. * debian/copyright: - Add year 2020 to debian/*. - Use secure URI. - Change Source to directory listing. - Add paragraph for FLOSS. - Fix lintian *-globbing-patterns errors. * debian/changelog: - Remove EOL before EOF. CU Jörg - -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9ajH0ACgkQCfifPIyh 0l39RQ//a9gYhyduaGa2YBuApNPlIdmhgCueFRF9+aSc0oa8hR4Ac+49kwB2taJx TJ0e/GJESnW1arhW9UzcxFGSTFmSojLAF4aDCIItzjtLoNdhmTRg6c6Imf6sQ6rE eZRAzWrEU6iQ8+I7Snx/DH06EL5SIGK3vSq5zG9TuHG5+vTDX4Nelp/7wrXyN2u+ X6nbxVjdXg082s7YPAPxhSs9soz9IpcwnejNhURL8uBktE99xvoR6mzeWpr2JYVb E4EEv02nbLkZnNXfX0axdtYs8XzEHfXwN1nHBD6qQdxCjtB2f4B6BBZzUKwjGZcQ 20Kv3CKZweUC8wD/zgJaEpfYFdgS0m7Vkp6t3Z/ydWi8mwTuo+kDbg0+XEwP4m7g oiVNqIUtL1T2ln/lfLYdMGGwm993MLsK/rDo0SEESAEAcCnIDUsKw30O+bdbwR9g pyCN4jI9QJmEmChRZpunjTNBYEVDimiwXcG4f/NH+ZMd5InWPtnci2Y7jknQf50/ k3F7CrdQ5HraIvuoGjRbHplp4sB2p5pkvcFh284hlH+oj2NiNUgzLvnxdpL3a2Om Zf/ASFd8QwR0iUY5errUsSw7WddcWxxdHPdf0eX/DpOVSaBtMJhWq6kgzbXUhs6D 6pcqtu/RryNJL/XFLTg2zEkuCAKtIhbHYUYituNsGKdfMi74hNk= =jxF7 -END PGP SIGNATURE-
Bug#969291: marked as done (RFS: sane-backends/1.0.31-1~experimental1 [RC] -- API library for scanners [transitional package])
Your message dated Thu, 10 Sep 2020 18:02:30 +0200 with message-id <51ac3ec0-e355-a6a3-4ad0-9239c974b...@debian.org> and subject line Re: Bug#969291: RFS: sane-backends/1.0.31-1~experimental1 [RC] -- API library for scanners [transitional package] has caused the Debian Bug report #969291, regarding RFS: sane-backends/1.0.31-1~experimental1 [RC] -- API library for scanners [transitional package] 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.) -- 969291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "sane-backends": Package name: sane-backends Version : 1.0.31-1~experimental1 Upstream Author : [fill in name and email of upstream] URL : http://www.sane-project.org License : GPL-3+, GPL-2+ with sane exception, Artistic, GFDL-1.1, GPL-2+, LGPL-2.1+, GPL-2 Vcs : https://jff.email/cgit/sane-backends.git Section : graphics It builds those binary packages: libsane - API library for scanners [transitional package] libsane-dev - API development library for scanners [development files] libsane1 - API library for scanners libsane-common - API library for scanners -- documentation and support files sane-utils - API library for scanners -- utilities To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sane-backends/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.0.31-1~experimental1.dsc or from git https://jff.email/cgit/sane-backends.git?h=release%2Fdebian%2F1.0.31-1_experimental1 Changes since the last upload: sane-backends (1.0.31-1~experimental1) experimental; urgency=medium . * New upstream release (Closes: #968949, #962539). * Add back libsane transitional package, to ease upgrades (Closes: #962936): - debian/control: Add package libsane as oldlibs. Thanks to Gianfranco Costamagna . * debian/copyright: - Fix lintian *-globbing-patterns errors. - Refresh to the new upstream release. * Convert debian/po/de.po to utf-8. * New patches: - debian/patches/0045-disable_lock_test_at_build_time.patch - debian/patches/0050-Use-python3-shebang.patch - debian/patches/0055-Fix_build_error.patch * debian/rules: - Use --enable-locking instead --disable-locking. * debian/control: - Add libpoppler-glib-dev to Build-Depends. - Add ipp-usb to libsane1 Recommends (Closes: #968953). * debian/libsane1.symbols: - Remove 7 not longer available symbols. * debian/saned@.service: - Switch Standard[Output|Error] from syslog to append:/var/log/saned.log. - New debian/sane-utils.logrotate to pack and remove old logs. * debian/libsane-common.lintian-overrides: - Rename tags. * debian/patches/0125-multiarch_dll_search_path.patch: - Add $(prefix)/lib64/sane to lib search path (Closes: #931297). * Fix FTCBFS: (Closes: #948711) - 0060-cross.patch: Make gphoto2 detection use the host architecture pkg-config. - Build tools/sane-desc for the build architecture. - Thanks to Helmut Grohne . * Remove files no longer needed: - debian/saned.socket - debian/saned@.service CU Jörg - -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9MCZIACgkQCfifPIyh 0l2ZMg/9GQNQFsi7V4CoHKFLd35lpht7VaMIYWDQh5VJKjttM4XsPbsGu7ojnW7H jb+v+qZaEKMfTPKZooedE9LOJZxU0mABLDP03XIye6qTy4/clM/xg6jNeDKqdiN7 2wHOIamEHKx0vEsT43TA/k0vaVHchrVBQjO53Oi9gAuib9QbgR1Qb9FXkPAih/tc QQH2TMd5W9LeGmUc2D2xsTAwUQ6Z1dKNWuYIOY+3AMg8u3hsSM+m3Z6sMY1z9wV7 WsBEngNbdy0dkmU5Kn+RDOf9HwElJr6uCzPUidMQiZ6yiF3vOh4nj9m5oeUsePH+ zy8g+yu4QzTWnipDNvRLTgFI+xIEs1yYQ1NZYu0LN6Cmu8SHmbbHWHPdAsyxokV7
Bug#964862: RFS: git-revise/0.6.0-1 -- handy git tool for doing efficient in-memory commit rebases & fixups
Hei, På fr. 28. aug. 2020 kl. 22.54 + skrev Nicolas Schier: > On Fri, Aug 28, 2020 at 01:28:00PM +0300, Adrian Bunk wrote: > > Control: tags -1 moreinfo > > > > On Sat, Jul 11, 2020 at 02:02:43PM +0200, Nicolas Schier wrote: > > >... > > > Changes since the last upload: > > >... > > >* Enable autopkgtest by using upstream tests (Closes: #944957) > > > > This likely worked when you posted the sponsorship request, > > but new pylint makes it fail: > > > > ... > > lint run-test: commands[0] | pylint gitrevise > > * Module gitrevise.merge > > gitrevise/merge.py:207:12: W0707: Consider explicitly re-raising using the > > 'from' keyword (raise-missing-from) > > gitrevise/merge.py:225:12: W0707: Consider explicitly re-raising using the > > 'from' keyword (raise-missing-from) > > * Module gitrevise.utils > > gitrevise/utils.py:73:8: W0707: Consider explicitly re-raising using the > > 'from' keyword (raise-missing-from) > > gitrevise/utils.py:89:12: W0707: Consider explicitly re-raising using the > > 'from' keyword (raise-missing-from) > > > > -- > > Your code has been rated at 9.96/10 (previous run: 9.96/10, +0.00) > > > > ERROR: InvocationError for command > > /tmp/autopkgtest.SDfHIM/tree/.tox/lint/bin/pylint gitrevise (exited with > > code 4) > > ... > finally, I uploaded a new version. Since I did not get any feedback from upstream, yet, I am going open an issue for upstream. Adrian, can you please have a look at the freshly uploaded version? Thanks and kind regards, Nicolas -- epost: nico...@fjasle.eu irc://oftc.net/nsc ↳ gpg: 18ed 52db e34f 860e e9fb c82b 7d97 0932 55a0 ce7f -- frykten for herren er opphav til kunnskap -- signature.asc Description: PGP signature
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
On Thu, Sep 10, 2020 at 12:12:29PM +0200, Alec Leamas wrote: > On Thu, 10 Sep 2020 05:12:34 -0400 The Wanderer > wrote: > > On 2020-09-10 at 01:45, Tobias Frost wrote: > > > > > On Wed, Sep 09, 2020 at 10:53:37PM +0200, Alec Leamas wrote: > > > > > > > Well, actually, all those lines probably should be removed: > > > debian/changelog is intended to record changes to the packaging part > > > only, it is not to record changes made upstream; more generally: Only > > > stuff that changes files in the debian directory should be mentioned > > > in d/changelog. (See > > > https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog > > > for some better/more accurate wording in the Policy) > > > > I'm not sure I read that section as meaning that. Could you point more > > specifically to the exact wording there which you understand as > > reflecting this rule? > > > > Regardless, I'm fairly sure there are exceptions to this in practice. > > For example, if a new upstream release includes a change which closes an > > open Debian bug report or fixes a particular CVE, a notation in the > > changelog recording that fact seems to be de rigueur, and in fact as I > > understand matters the tooling recognizes and parses notes such as > > "Closes: #123456" or "CVE-1000-123-1234" to auto-close the given bug > > report or to mark a newly-packaged version as unaffected by the given > > CVE. > > > > For that matter, look at the Linux kernel packages > > (linux-image-VERSION-ARCH, among others). They don't seem to ship a > > changelog.Debian.gz, but the changelog.gz which they do ship seems to be > > > > This seems to be a Deep Philosophical Discussion between Debian > Developers. I should thus basically stay quiet, but I feel the > discussion is a little bit off in this case. (Sorry that this RFS has been hijacked. I try keep on topic now; I'm not sure whether The Wanderer is DD or package maintainer, but its not relevant anyway) > I'm working tight with upstream, so the upstream/downstream boundaries > are a little obscured. >The references was a result (all cases) of a > workflow like > > - Packaging, I find a bug and make a patch in d/patches > - The bug is filed upstream. > - The patch is converted to an upstream PR. > - The PR is merged on upstream master branch, to be included in next > release. > - The patch in d/patches is updated with DEP-5 info (yes, did that). > - The line in the changelog is (was) updated with the upstream bug #. > > So, these references stem from my downstream work. They do (did) *not* > reference anything in the release tag, only changes after that. Srry, EPARSE, can you expand? Oh wait, I guess I see the misunderstanding now… Oops, totally sorry, I misread the changelog entries all the time and missing the word "patch"… Actually those changes _are_ changes to the debian package, so of course they need to be in d/changelog. However, May I propose a better structuring like: * New patches: - udev rule installation patch. - metadata installation patch. - Remove bogus svg file patch. (**) - Patch to fix cmake parallel execution. - Add two plugin compatiblity patches (#1997). (in my packages I usually write "New patch $patch-filename.", because details would be the dep3 headers of the patch. This allow sometime better to understand which patch is what change. But thats personal taste) While having the changelog open: * Handle some lintian informational warnings. is not a good changelog entry, because it does have enough information what has been changed (and why)) * Remove bogus svg file patch. Its unclear to me why are you removing it? (If it doesn't cause problems I would leave it…) I will continue later, I need some food first ;-) But I'm glad this knot in my brain has been sliced ;-) > Having these lines, with or without upstream references is no big thing, > at least not for me. Just trying to clarify > Cheers! > --alec >
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
On Thu, Sep 10, 2020 at 05:12:34AM -0400, The Wanderer wrote: > > https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog > > for some better/more accurate wording in the Policy) > > I'm not sure I read that section as meaning that. Could you point more > specifically to the exact wording there which you understand as > reflecting this rule? Policy says: "Changes _in_ the Debian version of the package should be briefly explained in this file." (emphasis mine) (I'm positive that project at large interprets that as like I do. People told me it too, when I was learning packaging. The manpage for debian/changelog seems to support this futher.) Though note that is a "should" requirement only, so this would a "normal bug", not "RC." > Regardless, I'm fairly sure there are exceptions to this in practice. > For example, if a new upstream release includes a change which closes an > open Debian bug report A "New upstream version" packaging is a change to the Debian packaging (regardless if it closes a bug or not) If it happens to close a Debian bug, it is recorded like all other bugs. > or fixes a particular CVE, a notation in the > changelog recording that fact seems to be de rigueur, and in fact as I > understand matters the tooling recognizes and parses notes such as > "Closes: #123456" or "CVE-1000-123-1234" to auto-close the given bug > report or to mark a newly-packaged version as unaffected by the given > CVE. CVEs are a special expection anyway, as it is basically the only instance where even rewriting history* is permitted in d/changelog. (* changeing old changelog entries) > For that matter, look at the Linux kernel packages > (linux-image-VERSION-ARCH, among others). They don't seem to ship a > changelog.Debian.gz, but the changelog.gz which they do ship seems to be > in Debian changelog form and list Debian package versions, and is > reported by apt-listchanges at upgrade time; in that file, each new > Debian version tends to contain a "New upstream stable update" entry, > which is then followed by a kernel changelog URL and a lengthy, detailed > listing of changes (apparently nearly commit-level) taken from that > upstream changelog. > > I'm not sure this is best practice, or that it would be a good thing for > other packages to be doing en masse - but it's a large-scale example of > including upstream changes in debian/changelog, and it certainly doesn't > seem to be an unacceptable violation if something as core as the kernel > packages have been doing it for so long and are still going that way. You should discuss that with the kernel package maintainers. Policy says that "Every _source_ package must include the Debian changelog file, debian/changelog.", and they do: https://tracker.debian.org/media/packages/l/linux/changelog-5.8.7-1 For _binary_ package the relveant policy section is §12.7 and the filename is /usr/share/doc/package/changelog.Debian.gz, so technically you are seeing the upstream changelog. (I guess this is discussion becoming off topic for this RFS, so I leave it here…;) -- tobi
Bug#962714: marked as done (RFS: ddupdate/0.6.5-1 -- Tool updating DNS data for dynamic IP addresses)
Your message dated Thu, 10 Sep 2020 14:38:23 +0200 with message-id and subject line Re: RFS: ddupdate/0.6.5-1 -- Tool updating DNS data for dynamic IP addresses has caused the Debian Bug report #962714, regarding RFS: ddupdate/0.6.5-1 -- Tool updating DNS data for dynamic IP addresses 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.) -- 962714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962714 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 "ddupdate" * Package name: ddupdate Version : 0.6.5-1 Upstream Author : https://github.com/leamas/ddupdate/issues * URL : https://github.com/leamas/ddupdate * License : Expat * Vcs : https://github.com/leamas/ddupdate/tree/debian Section : net It builds the single, standard python package: ddupdate - Tool updating DNS data for dynamic IP addresses This is a bugfix upstream release. More info is available at https://mentors.debian.net/package/ddupdate Alternatively, one can download the package with dget using: dget -x https://mentors.debian.net/debian/pool/main/d/ddupdate/ddupdate_0.6.5-1.dsc Changes since the last upload: * New upstream release. * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set field Upstream-Contact in debian/copyright. * Set upstream metadata fields: Bug-Submit, Repository. * Remove obsolete fields Contact, Name from debian/upstream/metadata (already present in machine-readable debian/copyright). * Update standards version to 4.5.0, no changes needed. * Fix error running ddupdate-config (#41) * New plugin domains.google.com * Multiple python 3.9 fixes. Regards, -- Alec Leamas --- End Message --- --- Begin Message --- ack G. On Fri, 12 Jun 2020 16:01:30 +0200 Alec Leamas wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "ddupdate" > > * Package name: ddupdate >Version : 0.6.5-1 >Upstream Author : https://github.com/leamas/ddupdate/issues > * URL : https://github.com/leamas/ddupdate > * License : Expat > * Vcs : https://github.com/leamas/ddupdate/tree/debian >Section : net > > It builds the single, standard python package: > > ddupdate - Tool updating DNS data for dynamic IP addresses > > This is a bugfix upstream release. More info is available at > > https://mentors.debian.net/package/ddupdate > > Alternatively, one can download the package with dget using: > > dget -x > https://mentors.debian.net/debian/pool/main/d/ddupdate/ddupdate_0.6.5-1.dsc > > Changes since the last upload: > >* New upstream release. >* Bump debhelper from old 11 to 12. >* Set debhelper-compat version in Build-Depends. >* Set field Upstream-Contact in debian/copyright. >* Set upstream metadata fields: Bug-Submit, Repository. >* Remove obsolete fields Contact, Name from debian/upstream/metadata > (already present in machine-readable debian/copyright). >* Update standards version to 4.5.0, no changes needed. >* Fix error running ddupdate-config (#41) >* New plugin domains.google.com >* Multiple python 3.9 fixes. > > Regards, > > -- > Alec Leamas > > --- End Message ---
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
On Thu, 10 Sep 2020 05:12:34 -0400 The Wanderer wrote: > On 2020-09-10 at 01:45, Tobias Frost wrote: > > > On Wed, Sep 09, 2020 at 10:53:37PM +0200, Alec Leamas wrote: > > > > Well, actually, all those lines probably should be removed: > > debian/changelog is intended to record changes to the packaging part > > only, it is not to record changes made upstream; more generally: Only > > stuff that changes files in the debian directory should be mentioned > > in d/changelog. (See > > https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog > > for some better/more accurate wording in the Policy) > > I'm not sure I read that section as meaning that. Could you point more > specifically to the exact wording there which you understand as > reflecting this rule? > > Regardless, I'm fairly sure there are exceptions to this in practice. > For example, if a new upstream release includes a change which closes an > open Debian bug report or fixes a particular CVE, a notation in the > changelog recording that fact seems to be de rigueur, and in fact as I > understand matters the tooling recognizes and parses notes such as > "Closes: #123456" or "CVE-1000-123-1234" to auto-close the given bug > report or to mark a newly-packaged version as unaffected by the given > CVE. > > For that matter, look at the Linux kernel packages > (linux-image-VERSION-ARCH, among others). They don't seem to ship a > changelog.Debian.gz, but the changelog.gz which they do ship seems to be > This seems to be a Deep Philosophical Discussion between Debian Developers. I should thus basically stay quiet, but I feel the discussion is a little bit off in this case. I'm working tight with upstream, so the upstream/downstream boundaries are a little obscured. The references was a result (all cases) of a workflow like - Packaging, I find a bug and make a patch in d/patches - The bug is filed upstream. - The patch is converted to an upstream PR. - The PR is merged on upstream master branch, to be included in next release. - The patch in d/patches is updated with DEP-5 info (yes, did that). - The line in the changelog is (was) updated with the upstream bug #. So, these references stem from my downstream work. They do (did) *not* reference anything in the release tag, only changes after that. Having these lines, with or without upstream references is no big thing, at least not for me. Just trying to clarify Cheers! --alec
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
On 2020-09-10 at 01:45, Tobias Frost wrote: > On Wed, Sep 09, 2020 at 10:53:37PM +0200, Alec Leamas wrote: >> Hi, >> >> A new version is uploaded to mentors. Time to reset the history. Changes >> since last round: >> >> - New warning dialog for downloading binary plugin content (patch). >> - Spelling error fixed >> - Removed references to upstream bugs. I think it's a pity, the >> references linked patches in d/patches to upstream bugs. > > Well, actually, all those lines probably should be removed: > debian/changelog is intended to record changes to the packaging part > only, it is not to record changes made upstream; more generally: Only > stuff that changes files in the debian directory should be mentioned > in d/changelog. (See > https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog > for some better/more accurate wording in the Policy) I'm not sure I read that section as meaning that. Could you point more specifically to the exact wording there which you understand as reflecting this rule? Regardless, I'm fairly sure there are exceptions to this in practice. For example, if a new upstream release includes a change which closes an open Debian bug report or fixes a particular CVE, a notation in the changelog recording that fact seems to be de rigueur, and in fact as I understand matters the tooling recognizes and parses notes such as "Closes: #123456" or "CVE-1000-123-1234" to auto-close the given bug report or to mark a newly-packaged version as unaffected by the given CVE. For that matter, look at the Linux kernel packages (linux-image-VERSION-ARCH, among others). They don't seem to ship a changelog.Debian.gz, but the changelog.gz which they do ship seems to be in Debian changelog form and list Debian package versions, and is reported by apt-listchanges at upgrade time; in that file, each new Debian version tends to contain a "New upstream stable update" entry, which is then followed by a kernel changelog URL and a lengthy, detailed listing of changes (apparently nearly commit-level) taken from that upstream changelog. I'm not sure this is best practice, or that it would be a good thing for other packages to be doing en masse - but it's a large-scale example of including upstream changes in debian/changelog, and it certainly doesn't seem to be an unacceptable violation if something as core as the kernel packages have been doing it for so long and are still going that way. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Bug#969291: RFS: sane-backends/1.0.31-1~experimental1 [RC] -- API library for scanners [transitional package]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, Am Freitag, den 04.09.2020, 15:21 +0200 schrieb Raphael Hertzog: > Hello, > > I'd like to see this new upstream release in sid so I'm taking a look > but I'm quite surprised by many things. And actually I want this fix > in the package too: > https://gitlab.com/sane-project/backends/-/merge_requests/502 > I have add this merge request as d/p/0165-respect_local_only_parameter.patch [...] > On Sun, 30 Aug 2020, Jörg Frings-Fürst wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Package: sponsorship-requests > > Severity: important > > > > Dear mentors, > > > > I am looking for a sponsor for my package "sane-backends": > > > >Package name: sane-backends > >Version : 1.0.31-1~experimental1 > >Upstream Author : [fill in name and email of upstream] > >URL : http://www.sane-project.org > >License : GPL-3+, GPL-2+ with sane exception, Artistic, GFDL-1.1, > > GPL-2+, LGPL-2.1+, GPL-2 > >Vcs : https://jff.email/cgit/sane-backends.git > >Section : graphics > > > > It builds those binary packages: > > > > libsane - API library for scanners [transitional package] > > libsane-dev - API development library for scanners [development files] > > libsane1 - API library for scanners > > libsane-common - API library for scanners -- documentation and support > > files > > sane-utils - API library for scanners -- utilities > > > > To access further information about this package, please visit the following > > URL: > > > > https://mentors.debian.net/package/sane-backends/ > > > > Alternatively, one can download the package with dget using this command: > > > > dget -x > > https://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.0.31-1~experimental1.dsc > > > > or from > > > > git > > https://jff.email/cgit/sane-backends.git?h=release%2Fdebian%2F1.0.31-1_experimental1 > > > > Changes since the last upload: > > > > sane-backends (1.0.31-1~experimental1) experimental; urgency=medium > > . > >* New upstream release (Closes: #968949, #962539). > >* Add back libsane transitional package, to ease upgrades (Closes: > > #962936): > > - debian/control: Add package libsane as oldlibs. > >Thanks to Gianfranco Costamagna . > >* debian/copyright: > > - Fix lintian *-globbing-patterns errors. > > - Refresh to the new upstream release. > >* Convert debian/po/de.po to utf-8. > >* New patches: > > - debian/patches/0045-disable_lock_test_at_build_time.patch > > - debian/patches/0050-Use-python3-shebang.patch > > - debian/patches/0055-Fix_build_error.patch > >* debian/rules: > > - Use --enable-locking instead --disable-locking. > >* debian/control: > > - Add libpoppler-glib-dev to Build-Depends. > > - Add ipp-usb to libsane1 Recommends (Closes: #968953). > >* debian/libsane1.symbols: > > - Remove 7 not longer available symbols. > >* debian/saned@.service: > > - Switch Standard[Output|Error] from syslog to > > append:/var/log/saned.log. > > - New debian/sane-utils.logrotate to pack and remove old logs. > >* debian/libsane-common.lintian-overrides: > > - Rename tags. > >* debian/patches/0125-multiarch_dll_search_path.patch: > > - Add $(prefix)/lib64/sane to lib search path (Closes: #931297). > >* Fix FTCBFS: (Closes: #948711) > > - 0060-cross.patch: Make gphoto2 detection use the host architecture > >pkg-config. > > - Build tools/sane-desc for the build architecture. > > - Thanks to Helmut Grohne . > >* Remove files no longer needed: > > - debian/saned.socket > > - debian/saned@.service > > [...] Please can someone review my changes? Many thanks. CU Jörg - -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl9Z7RIACgkQCfifPIyh 0l0fAxAAvCQbITRZdM938lFiGS254OX7BfRamcbBnQ27swG9OBxwDZg/M7zPOzfg GVCNLVdI0jcRLURUU2CH+M8Rq6b76a5VP0SjoMfb5uyWqHEAplqynmA+OXW7mQri KrO9sQGkf7Z89pa2H5ocqy5gJAgk5Fbf9jP6RqGhzZdBy2RIGcP+iCHpvFPK1WUC JugZg8+GK9+nhlG2susbsYnXPlBiHTQYCRERKlb8Y+WXwUf1mX0VQi/HNUTkxlcA wB5zsU901n4EU7ErclIXnAty/gvjvaJ74jdNoxVffHh88IifD9xhs55T8UNrAm8y ei3M3rx0fYADI4i9SoeoxqxemeKOX8VTqi9yie6lUlnhlIPvOkPq0wmSFqz76RSC MPlk0Sfv7FAfDc0rm6PfJFTU0vgGvtmlv3X6jn65+o3UX4Ygyj3wKoQ1wgSIPIjP Rzg15i0auz8re3SipVfWIZggUTi2/VWwhgn9cIPgs3TFJy/lXhEiGxklv+6ZRzDN
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
Hi Tobias, On Thu, 10 Sep 2020 08:06:10 +0200 Tobias Frost wrote: > On Wed, Sep 09, 2020 at 11:08:53PM +0200, Alec Leamas wrote: > > On Wed, 9 Sep 2020 22:53:37 +0200 Alec Leamas wrote: > > Dammit. There's still one copyright for src/gshhs.cpp to fix. I'm on it, > > but holding next upload until I hear from you. > > PS: Hints to make your life easier: > - there are tools that might help https://wiki.debian.org/CopyrightReviewTools > (probably you know already, as some lines look tool-generated ;-) Yes, as Fedora packager I've been using licensecheck since too many years. And once you have been able to set up cme it's a great tool. However, current fixes is basically wrapping up after some cme wrongdoing. To maintain a copyright file like this manually would be , well, interesting... [snip] > Hope that helps a bit. It does (thanks!), taking it with me to next release. However, keeping delta small at this point. Cheers! --alec
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
On Thu, 10 Sep 2020 07:46:32 +0200 Tobias Frost wrote: > On Wed, Sep 09, 2020 at 11:08:53PM +0200, Alec Leamas wrote: > > On Wed, 9 Sep 2020 22:53:37 +0200 Alec Leamas wrote: > just go ahead and update the package on mentors. Done. --alec
Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).
Hi Hilmar, > - debian/control: you need to declare a BD on at least libasound2-dev, > did not test further. > > Build the package fails nevertheless b/c vguitar binary is installed > into usr/local/. Did you even try to build a binary package from your > source package? I am unfamiliar. I updated Debian files to reflect your mentoring advice. Thank you. apt-key adv --keyserver keyserver.ubuntu.com --recv-keys AB406C34 deb-src http://apt.nick-strauss.com/apt/debian jessie main apt-get source vguitar Now, updated files are: vguitar_2.6-2.debian.tar.xz vguitar_2.6-2.dsc I added build dependencies (BD): Build-Depends: debhelper (>=9), libncurses5-dev, libasound2-dev, libc6-dev I built with "debuild -v -uc -us" debian/vguitar/usr/local/bin/vguitar --help works. Please provide progressive. Thanks. Nick Strauss
Bug#965363: RFS: opencpn/5.2.0+dfsg-1 [RC] -- Open Source Chartplotter and Marine GPS Navigation Software
On Wed, Sep 09, 2020 at 11:08:53PM +0200, Alec Leamas wrote: > On Wed, 9 Sep 2020 22:53:37 +0200 Alec Leamas wrote: > > Hi, > > > > A new version is uploaded to mentors. Time to reset the history. Changes > > since last round: > > ... > > Dammit. There's still one copyright for src/gshhs.cpp to fix. I'm on it, > but holding next upload until I hear from you. PS: Hints to make your life easier: - there are tools that might help https://wiki.debian.org/CopyrightReviewTools (probably you know already, as some lines look tool-generated ;-) ) - you can combine entries, we don't need per-file accurary. For example (just picking 3 _short_ paragraphs from your d/copyright) ; it also applies to the other paragraphs Files: include/GL/* Copyright: 1999-2007, Brian Paul License: Expat Files: include/GL/glext.h Copyright: 2007-2012, The Khronos Group Inc. License: Expat (..) Files: libs/SQLiteCpp/* Copyright: 2012-2018, Sebastien Rombauts (sebastien.romba...@gmail.com) License: Expat Can be shortened to: Files: include/GL/* libs/SQLiteCpp/* Copyright: 1999-2007, Brian Paul 2007-2012, The Khronos Group Inc. 2012-2018, Sebastien Rombauts (sebastien.romba...@gmail.com) License: Expat IOW: As long as the license is the same, you can combine the sections and just add the respective copyright holders to the list Also, if you have something like (making this example up) You can also combine copyright years, so no need to have two lines if only the years differ. Just extend the span if needed… Hope that helps a bit. > > "Annoyed" > > --alec >
Bug#969446: RFS: vguitar-2.6 [ITP] -- Play Guitar in any term window. Use with a MIDI synthesizer (qsynth).
Am 10.09.2020 um 05:44 teilte Nick Strauss mit: Hi, Did you get the updated debian.tar.xz I sent you? Consider to use that one. > I added build dependencies (BD):> > Build-Depends: > debhelper (>=9),> > libncurses5-dev,> libasound2-dev,> libc6-dev> libc6-dev is pulled in by build-essential. No need to declare a BD on it. > I built with "debuild -v -uc -us" > > debian/vguitar/usr/local/bin/vguitar --help > > works. > Don't install a program into /usr/local. The package won't be accepted. H. -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
