Bug#856652: RFS: xpdf/3.0.4.real-4
On Sun, 2017-03-05 at 17:36 -0700, Sean Whitton wrote: > control: noowner -1 > > > OK, got it. Are you still interested to sponsor this package, now when > > you know about status quo? If so, I'll create an account at > > alioth.debian.org and we'll continue from there. > > I was hoping that you could provide a counter-argument to allay my > concerns about security. Since you don't seem to have a response to the > issues I've raised, I wouldn't be comfortable uploading xpdf. I don't see where your concerns regarding security are, please explain. Reading more about the bugs in xpdf, the problems are mainly created by the use of poppler as a backend, not when using the _real_ upstream sources. So, if I remove the offending hello.pdf from the upstream source, can you (or somebody else) be the sponsor for this package? Please. I have also contacted the upstream author about the hello.pdf file as well as other issues. Hopefully, he will reply with an updated upstream tarball. Thanks!
Bug#856910: RFS: inotify-tools/3.14-3
On Mon, Mar 06, 2017 at 09:05:19AM +0300, Dmitry Bogatov wrote: > I am looking for a sponsor for my package "inotify-tools" - you could install NEWS as the upstream changelog - you could add a doc-base registration This would bring you down to a single lintian tag! -- Sean Whitton signature.asc Description: PGP signature
Bug#855439: RFS: cvm/0.97
control: tag -1 +moreinfo Dear Dmitry, On Sat, Feb 18, 2017 at 10:23:46AM +0300, Dmitry Bogatov wrote: > Note, that this is not full-scale modernization of package. It is just > a NMU, required for libbg1 -> libbg2 transition. Could you explain the background, please? Stretch is frozen. Have the release team authorized this transition? It's rarely appropriate for an NMU to update to a new upstream version. If you are just performing the transition in experimental, there is no justification for it. > Please note, that package is maintained with dgit(1) tool using > dgit-maint-merge(7) workflow. In particular, it means that quilt patches > are squashed in source package and are not intended for review. For more > information about how to sponsor this package, see dgit-sponsorship(7). This is not appropriate for an NMU. Indeed, I see that you've changed the source format to 3.0 (quilt) -- also not appropriate for an NMU. -- Sean Whitton signature.asc Description: PGP signature
Bug#856910: RFS: inotify-tools/3.14-3
control: tag -1 +moreinfo control: owner -1 ! Dear Dmitry, On Mon, Mar 06, 2017 at 09:05:19AM +0300, Dmitry Bogatov wrote: > I am looking for a sponsor for my package "inotify-tools" Thank you for your interest in adopting this package. And great choice for the git workflow ;) A review of dca4111: - Your conversion of d/copyright has lost some information, by merging the stanzas for McGovern and McCutchan. If you use two separate stanzas the conversion would not be lossy. - In your changelog you wrote that you bumped the std-ver. It's conventional to say what version you bumped it to. - The Lintian override could use a wildcard so that it only matches the doxygen file, not any other javascript that might appear in a new upstream release (unlikely though that is) - You've modified debian/*.install but this isn't in the changelog. - The dgit-maint-merge patch header has been updated to a better text. Please consider using it: https://manpages.debian.org/dgit-maint-merge - Changes to d/rules not in changelog. - Just fyi: https://manpages.debian.org/git-deborig Don't forget `dch -r` once you've addressed these. -- Sean Whitton signature.asc Description: PGP signature
Bug#857005: RFS: sigrok/0.3-1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "sigrok" * Package name: sigrok Version : 0.3-1 Upstream Author : none (metapackage) * URL : none (metapackage) * License : none (metapackage) Section : electronics It builds those binary packages: sigrok - Logic analyzer and protocol decoder software suite (metapackage) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sigrok Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sigrok/sigrok_0.3-1.dsc Changes since the last upload: * Bump dependency to sigrok-cli >= 0.6.0. * Bump dependency on pulseview >= 0.3.0. * Bump dependency on sigrok-firmware-fx2lafw >= 0.1.4. * Standards-Version: 3.9.8 (no changes required). * Bump debhelper compat and dependency to 10 * New maintainer (Closes: #852828) The package was recently RFA'd by the current maintainer Uwe, see #852834, and i would like to take over the maintenance of this package and the related packages in the sigrok suite (see at http://sigrok.org/wiki/Downloads). RFSs for the other packages are already sent. Unfortunately Uwe doesn't have time for sponsoring the package, so i would like to ask the community to guide me with the first steps. To ease this i uploaded my version to mentors.debian.net, see above. The packaging work is version controlled here: https://git.zgyarmati.de/debian-packaging/sigrok-debian which repository i plan to migrate to collab-maint eventually once i'm more set in the Debian infrastructure. Please feel free to contact with any comments or questions, best regards -- Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature
Bug#857004: RFS: sigrok-cli/0.6.0-1 [ ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "sigrok-cli" * Package name: sigrok-cli Version : 0.6.0-1 Upstream Author : http://sigrok.org * URL :http://sigrok.org/wiki/Sigrok-cli * License : GPL Section : electronics It builds those binary packages: sigrok-cli - command-line frontend for the sigrok software To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sigrok-cli Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sigrok-cli/sigrok-cli_0.6.0-1.dsc Changes since the last upload: * New upstream release. * Standards-Version: 3.9.8 (no changes required). * New maintainer (Closes: #852834). * Bump debhelper compat and dependency to 10 * Update sigrok dependencies' version The package was recently RFA'd by the current maintainer Uwe, see #852834, and i would like to take over the maintenance of this package and the related packages in the sigrok suite (see at http://sigrok.org/wiki/Downloads). RFSs for the other packages coming soon. Unfortunately Uwe doesn't have time for sponsoring the package, so i would like to ask the community to guide me with the first steps. To ease this i uploaded my version to mentors.debian.net, see above. The packaging work is version controlled here: https://git.zgyarmati.de/debian-packaging/sigrok-cli-debian which repository i plan to migrate to collab-maint eventually once i'm more set in the Debian infrastructure. Please feel free to contact with any comments or questions, best regards -- Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature
Bug#857002: RFS: pulseview/0.3.0-1 [ ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pulseview" * Package name: pulseview Version : 0.3.0-1 Upstream Author : http://sigrok.org * URL : http://sigrok.org/wiki/PulseView * License : GPL Section : electronics It builds those binary packages: pulseview - sigrok logic analyzer, oscilloscope, and MSO GUI To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pulseview Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pulseview/pulseview_0.3.0-1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: Changes since the last upload: * New upstream release * New maintainer (Closes: #852833) * Standards-Version: 3.9.8 (no changes required) * Update sigrok dependencies' version * Remove obsolete patches * Add patches to fix build errors * Build with Qt5, set build dependencies accordingly The package was recently RFA'd by the current maintainer Uwe, see # 852833, and i would like to take over the maintenance of this package and the related packages in the sigrok suite (see at http://sigrok.org/wiki/Downloads). RFSs for the other packages coming soon. Unfortunately Uwe doesn't have time for sponsoring the package, so i would like to ask the community to guide me with the first steps. To ease this i uploaded my version to mentors.debian.net, see above. The packaging work is version controlled here: https://git.zgyarmati.de/debian-packaging/pulseview-debian which repository i plan to migrate to collab-maint eventually once i'm more set in the Debian infrastructure. Please feel free to contact with any comments or questions, best regards -- Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature
Bug#856989: RFS: sigrok-firmware-fx2lafw/0.1.4-1 [ITA]
Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "sigrok-firmware-fx2lafw" * Package name: sigrok-firmware-fx2lafw Version : 0.1.4-1 Upstream Author : http://sigrok.org * URL : http://sigrok.org/wiki/Fx2lafw * License : GPL Section : electronics It builds those binary packages: sigrok-firmware-fx2lafw - Firmware for Cypress FX2(LP) based logic analyzers To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sigrok-firmware-fx2lafw Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sigrok-firmware-fx2lafw/sigrok-firmware-fx2lafw_0.1.4-1.dsc Changes since the last upload: * New upstream release. * Standards-Version: 3.9.8 (no changes required). * New maintainer (Closes: #852835). * Bump debhelper compat and dependency to 10 The package was recently RFA'd by the current maintainer Uwe, see #852835, and i would like to take over the maintenance of this package and the related packages in the sigrok suite (see at http://sigrok.org/wiki/Downloads). RFSs for the other packages coming soon. Unfortunately Uwe doesn't have time for sponsoring the package, so i would like to ask the community to guide me with the first steps. To ease this i uploaded my version to mentors.debian.net, see above. The packaging work is version controlled here: https://git.zgyarmati.de/debian-packaging/sigrok-firmware-fx2lafw-debian which repository i plan to migrate to collab-maint eventually once i'm more set in the Debian infrastructure. Please feel free to contact with any comments or questions, best regards -- Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature
Bug#856987: RFS: libsigrokdecode/0.4.1-1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libsigrokdecode" * Package name: libsigrokdecode Version : 0.4.1-1 Upstream Author : http://sigrok.org/ * URL : http://sigrok.org/wiki/Libsigrokdecode * License : GPL Section : libs It builds those binary packages: libsigrokdecode-dev - sigrok protocol decoding library - development files libsigrokdecode2 - sigrok protocol decoding library - shared library libsigrokdecode3 - sigrok protocol decoding library - shared library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libsigrokdecode Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libs/libsigrokdecode/libsigrokdecode_0.4.1-1.dsc More information about the sigrok can be obtained from http://sigrok.org/. Changes since the last upload: * New upstream release 0.4.1 * New maintainer (Closes: #852831) * Increment package name suffix as upstream soname has changed * Add transitional package for libsigrokdecode2 * Standards-Version: 3.9.8 (no changes required) * Bump debhelper compat and dependency to 10 The package was recently RFA'd by the current maintainer Uwe, see #852831, and i would like to take over the maintenance of this package and the related packages in the sigrok suite (see at http://sigrok.org/wiki/Downloads). RFSs for the other packagescoming soon. Unfortunately Uwe doesn't have time for sponsoring the package, so i would like to ask the community to guide me with the first steps. To ease this i uploaded my version to mentors.debian.net, see above. The packaging work is version controlled here: https://git.zgyarmati.de/debian-packaging/libsigrokdecode-debian which repository i plan to migrate to collab-maint eventually once i'm more set in the Debian infrastructure. Please feel free to contact with any comments or questions, best regards -- Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature
Bug#856981: RFS: libsigrok/0.4.0-1 [ ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libsigrok" * Package name: libsigrok Version : 0.4.0-1 Upstream Author : http://sigrok.org/ * URL : http://sigrok.org/wiki/Libsigrok * License : GPL Section : libs It builds those binary packages: libsigrok-dev - sigrok hardware driver library - development files libsigrok2 - sigrok hardware driver library (transitional dummy package) libsigrok3 - sigrok hardware driver library - shared library libsigrokcxx3 - sigrok hardware driver library - shared library libsigrokcxx3-dev - sigrok C++ bindings - development files python-libsigrok3 - Python bindings for the libsigrok library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libsigrok Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libs/libsigrok/libsigrok_0.4.0-1.dsc More information about the sigrok can be obtained from http://sigrok.org/. Changes since the last upload: * New upstream release 0.4.0 * New maintainer (Closes: #852830) * Increase package name suffix as soname changed, add correspondig dummy package * Remove obsolote transitional dummy package libsigrok0-dev * Add binary and dev packages for C++ bindings * Add binary package for Python bindings * Patch Makefile.am to avoid build quiteness and install Python module under dist-packages * Add build-deps needed for C++/Python bindings The package was recently RFA'd by the current maintainer Uwe, see #852830, and i would like to take over the maintenance of this package and the related packages in the sigrok suite (see at http://sigrok.org/wiki/Downloads). RFSs for the other packagescoming soon. Unfortunately Uwe doesn't have time for sponsoring the package, so i would like to ask the community to guide me with the first steps. To ease this i uploaded my version to mentors.debian.net, see above. The packaging work is version controlled here: https://git.zgyarmati.de/debian-packaging/libsigrok-debian which repository i plan to migrate to collab-maint eventually once i'm more set in the Debian infrastructure. Please feel free to contact with any comments or questions, best regards -- Zoltan Gyarmati https://zgyarmati.de -- Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature
Bug#856974: RFS: libserialport/0.1.1-2 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libserialport" * Package name: libserialport Version : 0.1.1-2 Upstream Author : http://sigrok.org/ * URL : http://sigrok.org/wiki/Libserialport * License : LGPL Section : libs It builds those binary packages: libserialport-dev - Crossplatform serial port handling library - development files libserialport0 - Crossplatform serial port handling library - shared library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libserialport Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libs/libserialport/libserialport_0.1.1-2.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * New maintainer (Closes: #852832) * Add patch to fix build on kfreebsd (Closes: #816334) * Standards-Version: 3.9.8 (no changes required) * Increase debhelper compat to 10 * Added libserialport0.symbols file The package was recently RFA'd by the current maintainer Uwe, see #852832, and i would like to take over the maintenance of this package and the related packages in the sigrok suite (see at http://sigrok.org/wiki/Downloads). RFSs for the other packages coming soon. Unfortunately Uwe doesn't have time for sponsoring the package, so i would like to ask the community to guide me with the first steps. To ease this i uploaded my version to mentors.debian.net, see above. The packaging work is version controlled here: https://git.zgyarmati.de/debian-packaging/libserialport-debian which repository i plan to migrate to collab-maint eventually once i'm more set in the Debian infrastructure. Please feel free to contact with any comments or questions, best regards -- Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature
Bug#856603: RFS: arc-theme/20170302-1
On 03/03/17 06:20, Adam Borowski wrote: > 3.22.9-1 is a whole new upstream release, with changes that actively break > unrelated packages. As you just mentioned, it does at least require themes > to be updated, and, as usual for GTK 3 new releases, probably a bunch of > gtk-3 using programs as well. That's not usual for point releases, in this case a bad change slipped through. That has been fixed in 3.22.9-3. > Then there's 3.22.9-2 which is a targetted RC bug fix... atop of bad > 3.22.9-1 rather than testing's 3.22.8-1. Ie, exactly the reason why > uploading random changes to unstable during freeze is a bad idea. > > I see that gtk+3.0's maintainers will need to make a separate upload to > testing-proposed-updates with a 3.22.8-2. That bug was introduced in 3.22.9, it doesn't affect 3.22.8. So no, nothing needs to go through tpu. BTW thanks for the notice about this regression. Cheers, Emilio
