Bug#895848: RFS: inotify-tools/3.14-5
control: tag -1 +moreinfo control: owner -1 ! On Mon, Apr 16, 2018 at 10:25:01PM +0300, Dmitry Bogatov wrote: > > I am looking for a sponsor for my package "inotify-tools" FTBFS: dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libinotifytools0/DEBIAN/symbols doesn't match completely debian/libinotifytools0.symbols --- debian/libinotifytools0.symbols (libinotifytools0_3.14-5_amd64) +++ dpkg-gensymbolsU60ncr 2018-04-17 04:48:11.369699111 + @@ -1,7 +1,7 @@ libinotifytools.so.0 libinotifytools0 #MINVER# - __odr_asan.rb_null@Base 3.14-4~ - __odr_asan.tree_filename@Base 3.14-4~ - __odr_asan.tree_wd@Base 3.14-4~ +#MISSING: 3.14-5# __odr_asan.rb_null@Base 3.14-4~ +#MISSING: 3.14-5# __odr_asan.tree_filename@Base 3.14-4~ +#MISSING: 3.14-5# __odr_asan.tree_wd@Base 3.14-4~ _niceassert@Base 3.11 chrtostr@Base 3.11 cleanup_tree@Base 3.12 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:9: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 Looks like you need to update your symbols file. Please be sure to `dch -r`. -- Sean Whitton signature.asc Description: PGP signature
Bug#895870: RFS: deepin-music/3.1.8.1+ds-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "deepin-music" * Package name: deepin-music Version : 3.1.8.1+ds-1 Upstream Author : Deepin Technology Co., Ltd. * URL : https://github.com/linuxdeepin/deepin-music * License : GPL-3+ Section : sound It builds those binary packages: deepin-music - music player with brilliant and tweakful UI To access further information about this package, please visit the following URL: https://mentors.debian.net/package/deepin-music Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/deepin-music/deepin-music_3.1.8.1+ds-1.dsc More information about hello can be obtained from https://salsa.debian.org/pkg-deepin-team/deepin-music -- Yanhao Mo signature.asc Description: PGP signature
Bug#895848: RFS: inotify-tools/3.14-5
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "inotify-tools" * Package name : inotify-tools Version : 3.14-5 Upstream Author : Radu Voicilas * Url : https://github.com/rvoicilas/inotify-tools/wiki/ * Licenses : LGPL-2.1+,GPL-2.1+ Programming Lang : C Section : misc Inotify is a Linux kernel feature enabling user space programs to monitor parts of the filesystem in a efficient way. libinotifytools is a thin layer on top of the kernel interface which makes it easy to set up watches on many files at once, read events without having to deal with low-level I/O, and several utility functions for inotify- related string formatting It builds those binary packages: * libinotifytools0 * libinotifytools0-dev * inotify-tools This package succesfully builds on debomatic machine: http://debomatic-i386.debian.net/distribution#unstable/inotify-tools/3.14-5 To access further information about this package, visit the following URL: https://mentors.debian.net/package/inotify-tools Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/inotify-tools/inotify-tools_3.14-5.dsc Alternatively, you can access package debian/ directory via git from URL: https://salsa.debian.org/iu-guest/inotify-tools.git More information about inotify-tools can be obtained from https://github.com/rvoicilas/inotify-tools/wiki/ Changes since last upload: * Disable sanitize build flags (Closes: #895811) Regards, Dmitry Bogatov
Bug#895812: Fwd: RFS: json-editor.js/0.7.28+ds-1 [ITP]
Ho Joel, thanks for your contribution ! Looking at your work there are a couple of things that can be improved: 1. I see that you set the Maintainer = Debian Javascript Maintainers. In that team normally we use git repos to keep track of the packaging; more precisely we use the git-buildpackage workflow. 2. All new repos nowadays are on salsa (https://salsa.debian.org), you can easily set up a guest account there with the self service webfrontend. 3. If you wish to maintain this package within this team, I'd suggest that you join the team ! Just drop a mail to the mailing list committing to follow the team policies, and indicate your salsa alias. One of the js-team group owners can then add you to the group on salsa. 4. The Debian Javascript Maintainers keeps all repos in the js-team group on salsa (https://salsa.debian.org/js-team); after moving your repo there you can update the Vcs-Browser and Vcs-Git fields in debian/control. 5. I tried to build your package, at the end lintian complains about: - co-maintained-package-with-no-vcs-fields (see previous point) - out-of-date-standards-version 4.1.1 (current is 4.1.4) - insecure-copyright-format-uri http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ - package-uses-old-debhelper-compat-version 10 (current is 11) - json-editor.js source: source-contains-prebuilt-javascript-object dist/jsoneditor.min.js see last point 6. This library comes with examples, so you could install those too. You can patch the examples so that they load the jsoneditor.js file from the default location /javascript/... which should point to /usr/share/javascript/... assuming apache2 alias from the javascript-common package is enabled ... 7. You are repackaging to exclude certain examples because they "link to libraries in external CDNs"; Sctually it should be possible to patch them to use the system installed libraries (I checked examples/select2.html, we do have jquery and libselect2) see: https://salsa.debian.org/js-team/vue.js/blob/master/debian/patches/00-examples.diff (those additional libraries needed to enjoy the examples could be recommended by the package...) 8. It would be super cool if we could enable tests ... but I am not sure how (selenium ?) Tests can be run during package build and in the debian CI infrastructure which helps improve the quality of debian and to avoid mishaps when dependencies are updated; 9. You must repackage for sure: to exclude dist. Else the package will certainly be rejected by the ftp-masters: the dist directory should be re-created from source during the debian build. Unfortunately debhelper does not yet support building with grunt out of the box (https://bugs.debian.org/845043) so you have to manually add that to debian/rules, see: https://codesearch.debian.net/search?q=grunt+build+path%3Adebian%2Frules https://wiki.debian.org/Javascript/Nodejs#Using_build_tools_like_grunt Paolo
Bug#895847: RFS: pqiv/2.10.3-0.1 [NMU] -- Powerful image viewer with minimal UI
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my new revision of the pqiv package. I am the upstream author. * Package name: pqiv Version : 2.10.3-0.1 Upstream Author : Phillip Berndt * URL : https://github.com/phillipberndt/pqiv * License : GPL3 Section : optional The latest version in the Debian archives is 2.6, a bug report [1] with a request to update to the intermediate versions has been open for 14 months now, I have not been able to reach the maintainer since. QA request regarding that is pending. I thought that a NMU might be my best chance of getting a more recent release into the archives. I did my best to update the package to accord to the latest packaging standards while at it. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pqiv Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pqiv/pqiv_2.10.3-0.1.dsc Regards, Phillip Berndt [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856166
Bug#889515: marked as done (RFS: persepolis/3.0.1-1 [ITP])
Your message dated Mon, 16 Apr 2018 16:20:29 + with message-id and subject line closing RFS: persepolis/3.0.1-1 [ITP] has caused the Debian Bug report #889515, regarding RFS: persepolis/3.0.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.) -- 889515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889515 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 the package I created, "persepolis". * Package name: persepolis Version : 3.0.1-1 Upstream Author : Alireza Amirsamimi * URL : https://persepolisdm.github.io/ * License : GPL-3+ Section : net It builds the following package: persepolis - Download Manager with a GUI based on Aria2 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/persepolis Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/persepolis/persepolis_3.0.1-1.dsc More information about persepolis can be obtained from https://persepolisdm.github.io/ . Sincerely yours, Moein Alinaghian --- End Message --- --- Begin Message --- Package persepolis has been removed from mentors.--- End Message ---
Re: Question concerning BTS, my own patch and upstream bugfix
On Mon, 16 Apr 2018 15:02:43 +0500 Andrey Rahmatullin wrote: >On Mon, Apr 16, 2018 at 11:38:25AM +0200, Oliver Meißner wrote: >> How should I deal with this patch? >> >> * Leave it inside my current package (ver 3.5-2), close the bug via >> (Closes: #893812) in d/changelog and remove the patch with the next >> upstream release >> or >> * Remove the patch from my package, don't close the bug and wait for >> the next upstream release? >How is the second option better? maybe the first option confuses someone... OK, I'll to it the first way, thanks. Regards O. Meißner pgpo9PUgNUeZR.pgp Description: Digitale Signatur von OpenPGP
Bug#895814: RFS: swagger-ui/2.2.10+ds-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "swagger-ui" * Package name: swagger-ui Version : 2.2.10+ds-1 Upstream Author : Tony Tam * URL : http://swagger.io * License : Apache-2.0 Section : javascript It builds those binary packages: libjs-swagger-ui - Collection of assets to dynamically generate documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/swagger-ui Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/swagger-ui/swagger- ui_2.2.10+ds-1.dsc More information about Swagger UI can be obtained from https://swagger.io/swagger-ui/. A running example can be found at http://petstore.swagger.io/. Regards, Joel Cross -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#895812: RFS: json-editor.js/0.7.28+ds-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "json-editor.js" * Package name: json-editor.js Version : 0.7.28+ds-1 Upstream Author : Jeremy Dorn (http://jeremydorn.com) * URL : https://github.com/json-editor/json-editor#readme * License : Expat Section : javascript It builds those binary packages: libjs-json-editor - JSON Schema based editor To access further information about this package, please visit the following URL: https://mentors.debian.net/package/json-editor.js Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/j/json-editor.js/json- editor.js_0.7.28+ds-1.dsc More information about json-editor can be obtained from https://github.com/json-editor/json-editor. Regards, Joel Cross -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Re: Question concerning BTS, my own patch and upstream bugfix
On Mon, Apr 16, 2018 at 11:38:25AM +0200, Oliver Meißner wrote: > How should I deal with this patch? > > * Leave it inside my current package (ver 3.5-2), close the bug via > (Closes: #893812) in d/changelog and remove the patch with the next > upstream release > or > * Remove the patch from my package, don't close the bug and wait for the > next upstream release? How is the second option better? -- WBR, wRAR signature.asc Description: PGP signature
Question concerning BTS, my own patch and upstream bugfix
Hi, just a short Question how to handle following situation properly I'm about to adopt the storebackup package and fixed bug #893812 by including a patch into the package. While waiting for a sponsor I got the information from the upstream author, that he'd fixed that bug in his next release, but it's not clear when he will release the next version, because there's still other work to be done. The question is: How should I deal with this patch? * Leave it inside my current package (ver 3.5-2), close the bug via (Closes: #893812) in d/changelog and remove the patch with the next upstream release or * Remove the patch from my package, don't close the bug and wait for the next upstream release? What would you do? Regards, Olly
Bug#895803: RFS: linuxbrew-wrapper/20180209-1 [RC]
Package: sponsorship-requests Severity: important Notes: I have DM permission to this package. However to fix an RC bug this package needs to go through NEW, moving from the main section to the contrib section. See the RC bug for detail. Dear mentors, I am looking for a sponsor for my package "linuxbrew-wrapper" * Package name: linuxbrew-wrapper Version : 20180209-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : utils It builds those binary packages: linuxbrew-wrapper - Homebrew package manager for Linux To access further information about this package, please visit the following URL: https://mentors.debian.net/package/linuxbrew-wrapper Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/contrib/l/linuxbrew-wrapper/linuxbrew-wrapper_20180209-1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: linuxbrew-wrapper (20180209-1) unstable; urgency=medium * Import upstream snapshot. * Move to contrib section. (Closes: #888957) * Add watch file to monitor git HEAD. * Update my name in control and copyright. * Update copyright, and explain why this package goes to contrib. * Use https link in copyright. * Point Vcs-* links to Salsa. * Bump Standards-Version to 4.1.4 . - Remove get-orig-source target. Use watch file instead. - Change Priority to "optional" because "extra" has been deprecated. -- Best,