Bug#861772: marked as done (RFS: writeroom-mode/3.6.1-1 [ITP])
Your message dated Fri, 29 Sep 2017 04:20:15 + with message-id and subject line closing RFS: writeroom-mode/3.6.1-1 [ITP] has caused the Debian Bug report #861772, regarding RFS: writeroom-mode/3.6.1-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.) -- 861772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Control: block -1 by 861705 Dear mentors, I am looking for a sponsor for my package "writeroom-mode" * Package name: writeroom-mode Version : 3.6.1-1 Upstream Author : Joost Kremers * URL : https://github.com/joostkremers/writeroom-mode * License : BSD-3-clause Section : lisp It will be maintained in the pkg-emacsen project: ssh://git.debian.org/git/pkg-emacsen/pkg/writeroom-mode.git It builds this binary package: elpa-writeroom-mode - Minor mode for distraction-free writing To access further information about this package, please visit the following URL: https://mentors.debian.net/package/writeroom-mode Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/writeroom-mode/writeroom-mode_3.6.1-1.dsc And here is changelog: writeroom-mode (3.6.1-1) unstable; urgency=medium * Initial release. (Closes: #861124) * Add 0001-Use-Texinfo-format-for-directory-declaration-for-inf.patch and 0002-Fix-menu-entry-in-texi-before-body.patch and 0003-Increase-header-levels-of-customisation-options-in-R.patch - These are needed to fix a variety of issues with the info file, including the lintian error "info-document-missing-dir-entry". -- Nicholas D Steeves Wed, 03 May 2017 15:52:36 -0400 Do the headers for the patches I cherry-picked (one manual 3-way merge) from upstream look ok? Specifically I'm wondering if I should use the "Applied-Upstream: commit hash" or "Applied-Upstream: commit: hash". I chose the former. Cheers, Nicholas signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Package writeroom-mode has been removed from mentors.--- End Message ---
Bug#877047: marked as done (RFS: sane-backends-extras/1.0.22.5 [QA])
Your message dated Thu, 28 Sep 2017 22:20:10 + with message-id and subject line closing RFS: sane-backends-extras/1.0.22.5 [QA] has caused the Debian Bug report #877047, regarding RFS: sane-backends-extras/1.0.22.5 [QA] 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.) -- 877047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877047 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 "sane-backends-extras". * Package name: sane-backends-extras Version: 1.0.22.5 Upstream Author: SANE * URL: http://www.sane-project.org/ * License: GPL v2 Section: graphics It builds the following binary packages: * libsane-extras - API library for scanners -- extra backends * libsane-extras-common - API library for scanners -- documentation and support files * libsane-extras-dev - API development library for scanners [development files] To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sane-backends-extras Alternatively, you may download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sane-backends-extras/sane-backends-extras_1.0.22.5.dsc Changes since the last upload: * QA upload. * debhelper update: - Update package compatibility to level 10 * debian/control: - Bump debhelper build-dep to >= 10~. - Remove autotools-dev from the Build-Depends list, as debhelper enables the 'autoreconf' sequence by default. - Bump Standards-Version from 3.9.8 to 4.1.0 (no changes needed). - Convert libsane-extras-common to Architecture: all. - Mark libsane-extras-dev Multi-Arch: same (Closes: #862263). * debian/extras-backends/geniusvp2: - Fix a spelling error in the BUGS file (lintian). * debian/rules: - Remove '--with=autotools_dev' (now handled by debhelper level 10). * doc/sane-geniusvp2.man: - Fix spelling errors (lintian). * Rename configure.in to configure.ac (lintian). Regards, Hugh McMaster--- End Message --- --- Begin Message --- Package sane-backends-extras version 1.0.22.5 is in unstable now. https://packages.qa.debian.org/sane-backends-extras--- End Message ---
Bug#867727: marked as done (RFS: parlatype/1.5.2-1 [ITP])
Your message dated Thu, 28 Sep 2017 22:04:40 +0200 with message-id <6bc3b267-1a78-a581-5b48-0117daa81...@the-gammons.net> and subject line Re: Bug#867727: RFS: parlatype/1.5.2-1 [ITP] has caused the Debian Bug report #867727, regarding RFS: parlatype/1.5.2-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.) -- 867727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "parlatype" * Package name: parlatype Version : 1.5.1-1 Upstream Author : Gabor Karsay * URL : http://gkarsay.github.io/parlatype/ * License : GPL-3 Section : gnome It builds those binary packages: gir1.2-parlatype-1.0 - Library for Parlatype - gir bindings libparlatype-dev - Library for Parlatype - development version libparlatype-doc - Documentation files for the Parlatype library libparlatype1 - Library for Parlatype - runtime version parlatype - Minimal audio player for manual speech transcription parlatype-libreoffice-helpers - Set of macros for LibreOffice To access further information about this package, please visit the following URL: https://mentors.debian.net/package/parlatype Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/parlatype/parlatype_1.5.1-1.dsc More information about parlatype can be obtained from http://gkarsay.github.io/parlatype/. I am also the upstream author. The first public release was in January 2016, the program is in a good state, is already translated in a few languages and fills a gap for an easy to use transcription utility (manual transcription). I'm not aware of another program in Debian for GNOME, targeting transcriptions and also offering a waveform. I was packaging it already for a time for Ubuntu. The package was built with pbuilder in a sid chroot. There is one lintian warning that I don't know what to do with: hardening-no-fortify-functions. I think the compiler flags are set right, but I don't know if I should override it. There's also one thing unclear to me about the procedure: Is this sponsorship request enough or should I file a WNPP bug, too? Thank you Gabor Karsay --- End Message --- --- Begin Message --- Uploaded! Thanks for adding parlatype to Debian. On 09/28/2017 02:09 PM, Gabor Karsay wrote: > >> Would you like to maintain this within the Debian Multimedia Team? If so: >> https://wiki.debian.org/DebianMultimedia/Join >> and then follow the stuff in the Develop Packaging link there (to create >> the git repository etc). >> We can always do this before the next upload if you prefer. Just let me >> know. > > I'm not sure. I guess it would be better but at the moment I don't have > much time to learn a new workflow. Besides I probably wouldn't do much > work for other packages in the Multimedia Team. I'd prefer not to join > at the moment if that is possible. No problems, we can learn the new workflow next time. I would prefer the whole package was in git version control. It makes it easier for a sponsor to see what has changed in the packaging, and for other developers to help out as required. Well - the teamwork goes both ways. There might be times you need advice from developers experienced in packaging multimedia type packages. And then maybe one day you see a way to help out with another package :-) Anyway, there is always collab-maint to store the git repository instead, for packages that don't fit into a team: https://wiki.debian.org/CollaborativeMaintenance Regards, Ross signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#877047: RFS: sane-backends-extras/1.0.22.5 [QA]
Hi Hugh McMaster, > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "sane-backends-extras". > > * Package name: sane-backends-extras >Version: 1.0.22.5 >Upstream Author: SANE > * URL: http://www.sane-project.org/ > * License: GPL v2 >Section: graphics > > It builds the following binary packages: > * libsane-extras - API library for scanners -- extra backends > * libsane-extras-common - API library for scanners -- documentation and > support files > * > lihttp://deb.debian.org/debian/pool/main/b/bogofilter/bogofilter_1.2.4+dfsg1-10.dscbsane-extras-dev > - API development library for scanners [development files] > > To access further information about this package, please visit the following > URL: > https://mentors.debian.net/package/sane-backends-extras > > Alternatively, you may download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/s/sane-backends-extras/sane-backends-extras_1.0.22.5.dsc > > Changes since the last upload: > * QA upload. > * debhelper update: > - Update package compatibility to level 10 > * debian/control: > - Bump debhelper build-dep to >= 10~. > - Remove autotools-dev from the Build-Depends list, as debhelper > enables the 'autoreconf' sequence by default. > - Bump Standards-Version from 3.9.8 to 4.1.0 (no changes needed). > - Convert libsane-extras-common to Architecture: all. > - Mark libsane-extras-dev Multi-Arch: same (Closes: #862263). > * debian/extras-backends/geniusvp2: > - Fix a spelling error in the BUGS file (lintian). > * debian/rules: > - Remove '--with=autotools_dev' (now handled by debhelper level 10). > * doc/sane-geniusvp2.man: > - Fix spelling errors (lintian). > * Rename configure.in to configure.ac (lintian). > > Regards, > > Hugh McMaster > Uploaded. Thanks for you time. Regards, Herbert
Bug#861772: RFS: writeroom-mode/3.6.1-1 [ITP]
On Thu, Sep 28, 2017 at 08:54:46AM -0400, Antoine Beaupre wrote: > On Wed, May 17, 2017 at 10:47:00AM -0400, Nicholas D Steeves wrote: > > Control: tag -1 +moreinfo > > > > Tagging as moreinfo while investigating a potential trademark > > infringement issue. I will untag when this has been resolved. > > Any update here? > > Can you clarify the trademark issue and what's possibly at stake here? > Has there been any public communication outside of the BTS about this we > can refer to? Did you talk to upstream? > > Thanks! Hi Antoine, Yes, I asked a fairly generic question somewhere on OFTC, then privately contacted upstream, and got in contact with debian-legal with upstream's consent. IIRC they recommended upstream rename as the easiest course of action (I forget if that was public or private), and provided an alternative that requires a bit of work (and less certainty). What's at stake? As I understand it, potential (American) lawyer fees, and/or headaches of needing to pull things offline in a hurry. Upstream recently send me an email, and is busy with IRL stuff. I remain optimistic this will be resolved this fall. Cheers, Nicholas P.S. Elpy is currently waiting for find-file-in-project to make it through the NEW queue. I'm working on getting the (recommended but not required) test suite working in the meantime. See your ITP for more info. 140-something files failing 300-something tests...it's a challenge haha. signature.asc Description: PGP signature
Doubt about using a forked version for a new package release
Hi! I would like to have some opinions and suggestions about the best action when updating a package that has a forked version. The forked version is better updated, maintained and has improvements over the original version. Debian has pngnq at version 1.0 with the latest upstream version at 1.1 The fork https://sf.net/projects/pngnqs9 is at version 2.0.2 The best option seems, indeed, to offer the forked version (as https://bugs.debian.org/862077 also says) Options that I see are: 1) ask for removal of pngnq and upload the new pngnqs9 But then users will lose the "pngnq" binary, affecting scripts, etc. I could create a symlink or use alternatives to have "pngnq" available to the user (pointing it to the new pngnq-s9 binary). A possible problem here is if one day pngnq gets back to life. 2) pack pngnqs9 as pngnq Just ship pngnqs9 as pngnq. Problem here is if pngnq's upstream releases a new version too, like on 1 (possible problem with version numbers, with incompatible features, diverging the program and making it completely different, etc) or if somebody else packs and uploads pngnqs9 (then we will have pngnq = pngnqs9 in the archive) 3) update pngnq to the latest version + some patches backported from pngnqs9 Simple option, but we won't have a version with all improvements 4) implement option 3 and also upload the new pngnqs9 package But then I am unsure if we need the 2 versions as they are right now (since pngnqs9 can replace pngnq for now) Most probably this is the right option to do. Does anybody have a good idea on how to provide the forked version and still keep a "pngnq" available for the user, if possible, please? Thank you! Best regards, Nelson
Re: Bug#877047: RFS: sane-backends-extras/1.0.22.5 [QA]
Hi Hugh McMaster, > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "sane-backends-extras". I can review this RFS. I did the last QA upload. Regards, Herbert > > * Package name: sane-backends-extras >Version: 1.0.22.5 >Upstream Author: SANE > * URL: http://www.sane-project.org/ > * License: GPL v2 >Section: graphics > > It builds the following binary packages: > * libsane-extras - API library for scanners -- extra backends > * libsane-extras-common - API library for scanners -- documentation and > support files > * libsane-extras-dev - API development library for scanners [development > files] > > To access further information about this package, please visit the following > URL: > https://mentors.debian.net/package/sane-backends-extras > > Alternatively, you may download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/s/sane-backends-extras/sane-backends-extras_1.0.22.5.dsc > > Changes since the last upload: > * QA upload. > * debhelper update: > - Update package compatibility to level 10 > * debian/control: > - Bump debhelper build-dep to >= 10~. > - Remove autotools-dev from the Build-Depends list, as debhelper > enables the 'autoreconf' sequence by default. > - Bump Standards-Version from 3.9.8 to 4.1.0 (no changes needed). > - Convert libsane-extras-common to Architecture: all. > - Mark libsane-extras-dev Multi-Arch: same (Closes: #862263). > * debian/extras-backends/geniusvp2: > - Fix a spelling error in the BUGS file (lintian). > * debian/rules: > - Remove '--with=autotools_dev' (now handled by debhelper level 10). > * doc/sane-geniusvp2.man: > - Fix spelling errors (lintian). > * Rename configure.in to configure.ac (lintian). > > Regards, > > Hugh McMaster >
Bug#861772: RFS: writeroom-mode/3.6.1-1 [ITP]
On Wed, May 17, 2017 at 10:47:00AM -0400, Nicholas D Steeves wrote: > Control: tag -1 +moreinfo > > Tagging as moreinfo while investigating a potential trademark > infringement issue. I will untag when this has been resolved. Any update here? Can you clarify the trademark issue and what's possibly at stake here? Has there been any public communication outside of the BTS about this we can refer to? Did you talk to upstream? Thanks! A. -- There has been only one Christian. They caught him and crucified him -- early. - Mark Twain
Bug#867727: RFS: parlatype/1.5.2-1 [ITP]
Ross Gammon schrieb am 2017-09-24 um 21:03: The only thing I spotted, was the lack of a docbase file to help people fire up the docs locally: https://www.debian.org/doc/manuals/maint-guide/dother.en.html#doc-base Done. Added the doc-base file and put a symlink from /usr/share/gtk-doc/html/parlatype to /usr/share/doc/libparlatype-doc/html. I looked how other packages are doing this and I found both install locations: e.g. gtk installs docs in /usr/share/doc and symlinks to /usr/share/gtk-doc but clutter for example does it the other way round, installing in /usr/share/gtk-doc and symlinking to /usr/share/doc as I did. Would you like to maintain this within the Debian Multimedia Team? If so: https://wiki.debian.org/DebianMultimedia/Join and then follow the stuff in the Develop Packaging link there (to create the git repository etc). We can always do this before the next upload if you prefer. Just let me know. I'm not sure. I guess it would be better but at the moment I don't have much time to learn a new workflow. Besides I probably wouldn't do much work for other packages in the Multimedia Team. I'd prefer not to join at the moment if that is possible. Some minor things we can work on for next time: 1. Lintian complains about there being no upstream changelog. As you are upstream, maybe you can fix this? It is a nice service to our users to see what changed in each version without going online. The Debian changelog only contains changes in the packaging. Yes, I can release an upstream changelog next time. There are already release notes for every release. 2. It would be nice to add some autopkgtests. For parlatype, that might just be to run the binary command without a file to check that it installs & doesn't crash. For the library & gir library you can compile a simple app against the libraries to check they compile & run OK. If you search on Debian Codesearch you will find examples. I plan that for the next minor release (which might or might not be this year). Regards, Gabor
Bug#877057: RFS: python-bayespy/0.5.11-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: python-bayespy Version : 0.5.11-1 Upstream Author : Jaakko Luttinen * URL : https://www.bayespy.org * License : Expat Section : python Please check out the package by visiting the following URL: https://anonscm.debian.org/git/debian-science/packages/python-bayespy.git Changes since the last upload: * New upstream version 0.5.11 * Update copyright dates * Revert exclusion of plot tests * Use DEB_BUILD_OPTIONS for nocheck * Replace occurrences of findstring with filter * Fixup whitespacing in rules file * Move extend-diff-ignore to d/s/options * Add an autopkgtest suite * Fixup the Vcs-Browser URI * Drop install dependency on python3-tk * Bump the standards version to 4.1.0 Regards, Ghis
Bug#861490: update
quick update: I package it already, I'd only need a sponsor. The package is on mentors: https://mentors.debian.net/package/xf86-input-tslib I maintain the tslib package aswell. It gains popularity now: https://qa.debian.org/popcon-graph.php?packages=libts0+libts-bin&show_installed=on&want_legend=on&want_ticks=on&from_date=2017-01-01&to_date=now&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 Maintaining xf86-input-tslib wouldn't be a problem. And it's quite useful as long as people are still using X11.
