Bug#901134: marked as done (RFS: anbox-modules/0.0~git20180608-1 [ITP])
Your message dated Wed, 4 Jul 2018 13:28:25 +0800 with message-id and subject line Android modules are built as in-tree modules since kernel 4.17.3 has caused the Debian Bug report #901134, regarding RFS: anbox-modules/0.0~git20180608-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.) -- 901134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: Chris Lamb Dear mentors, I am looking for a sponsor for my package "anbox-modules" * Package name: anbox-modules Version : 0.0~git20180608-1 Upstream Author : Simon Fels * URL : https://github.com/anbox/anbox-modules/ * License : GPL-2 Section : kernel It builds those binary packages: anbox-modules-dkms - Android kernel driver (binder, ashmem) in DKMS format To access further information about this package, please visit the following URL: https://mentors.debian.net/package/anbox-modules Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/anbox-modules/anbox-modules_0.0~git20180608-1.dsc Regards, Shengjing Zhu signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Android modules are built as in-tree modules since kernel 4.17.3 Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901492 Hence, I'm closing these two bugs. -- Best regards, Shengjing Zhu--- End Message ---
Bug#902967: RFS: ddnet/11.2.1-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ddnet" * Package name: ddnet Version : 11.2.1-1 Upstream Author : Dennis Felsing * URL : http://ddnet.tw/ * License : zlib (code), CC-BY-SA 3.0 (data) Section : games It builds those binary packages: ddnet - Teeworlds modification with a unique cooperative gameplay ddnet-data - Data for DDNet ddnet-server - Server for DDNet ddnet-tools - Tools for DDNet To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ddnet Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/ddnet/ddnet_11.2.1-2.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * New upstream release Regards, Yangfl
Bug#902494: marked as done (RFS: libplist/2.0.0-4 [QA])
Your message dated Wed, 4 Jul 2018 01:33:02 +0200 with message-id <20180703233302.dcjuh4hlzlcmh...@angband.pl> and subject line Re: Bug#902494: RFS: libplist/2.0.0-4 [QA] has caused the Debian Bug report #902494, regarding RFS: libplist/2.0.0-4 [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.) -- 902494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal X-Debbugs-CC: sunwea...@debian.org Dear Mike and mentors, I am looking for a sponsor for package "libplist" as a QA upload. Besides, I am looking for a DD to help creating a git repository under Salsa's Debian group and grant me (hosiet-guest) a Master role so that I could push the changes onto the git repo. * Package name: libplist Version : 2.0.0-4 Upstream Author : Nikias Bassen and others * URL : https://github.com/libimobiledevice/libplist/ * License : LGPL-2.1+ Section : libs It builds those binary packages: libplist++-dev - Library for handling Apple binary and XML property lists libplist++3v5 - Library for handling Apple binary and XML property lists libplist-dev - Library for handling Apple binary and XML property lists libplist-doc - Library for handling Apple binary and XML property lists - docs libplist-utils - Apple property list converter libplist3 - Library for handling Apple binary and XML property lists python-plist - Library for handling Apple binary and XML property lists To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libplist Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libp/libplist/libplist_2.0.0-4.dsc Git packaging repository (proposed, not exist yet): https://salsa.debian.org/debian/libplist.git Git packaging repository (temporary, will be removed after upload): https://salsa.debian.org/hosiet-guest/libplist.git Changes since the last upload: libplist (2.0.0-4) unstable; urgency=medium . * QA upload. * Apply "wrap-and-sort -abst". * Bump Standards-Version to 4.1.4. * Bump debhelper compat to v11. * debian/control: - Drop unnecessary build dependency dh-autoreconf. - Drop -dbg package to achieve -dbgsym migration. + Mark Multi-Arch information according to M-A Hints: + libplist-doc: M-A: foreign + libplist++-dev: M-A: same + libplist-dev: M-A: same + python-plist: M-A: same + Update Vcs fields with git repo under Salsa Debian group. + Use Breaks + Replaces instead of Conflicts + Replaces for package replacement. * debian/compat: Update accordingly. * debian/copyright: Update information accordingly. * debian/patches: Refresh patches. * debian/pycompat: Removed. (lintian tag "debian-pycompat-is-obsolete") * debian/rules: + Enable full hardening. + Use "dh_missing --fail-missing". + Update dh_strip invocation for dbgsym migration. + Force non-parallel build to circumvent failure in tests. * d/p/0003-bplist-Prevent-store-to-misaligned-address-when-writ.patch: Backport upstream patch. Side note: I'm not sure why I often encounter with random test failures caused by parallel build (parallel tests) while others basically cannot reproduce. Might be a problem on my side or some flaws in upstream build system. Anyway, forcing --no-parallel solves FTBFS. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- On Wed, Jun 27, 2018 at 06:03:03PM +0800, Boyuan Yang wrote: > Besides, I am looking for a DD to help creating a git repository under Salsa's > Debian group and grant me (hosiet-guest) a Master role so that I could push > the changes onto the git repo. Done. I even copied in your repo this time, for a change. > * Package name: libplist >Version : 2.0.0-4 > libplist (2.0.0-4) unstable; urgency=medium > . >* QA upload. >* Apply "wrap-and-sort -abst". >* Bump Standards-Version to 4.1.4. >* Bump debhelper compat to v11. >* debian/control: > - Drop unnecessary build dependency dh-autoreconf. > - Drop -dbg package to achieve -dbgsym migration. > + Mark Multi-Arch information according to M-A Hints: >+ libplist-doc: M-A: foreign >+ libplist++-dev: M-A: same >+ libplist-dev: M-A: same >
Bug#902486: marked as done (RFS: node-macaddress/0.2.9-1)
Your message dated Wed, 4 Jul 2018 00:57:15 +0200 with message-id <20180703225715.6percm7wn45za...@angband.pl> and subject line Re: Bug#902486: RFS: node-macaddress/0.2.9-1 has caused the Debian Bug report #902486, regarding RFS: node-macaddress/0.2.9-1 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.) -- 902486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal X-Debbugs-CC: sunwea...@debian.org pkg-javascript-de...@lists.alioth.debian.org Hi Mike, Debian JavaScript Team and mentors, I am looking for a sponsor for team-maintained package "node-macaddress". * Package name: node-macaddress Version : 0.2.9-1 Upstream Author : Julian Fleischer * URL : https://github.com/scravy/node-macaddress * License : Expat Section : javascript It builds those binary packages: node-macaddress - Get MAC addresses of host network interfaces in Node.js To access further information about this package, please visit the following URL: https://mentors.debian.net/package/node-macaddress Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/n/node-macaddress/node-macaddress_0.2.9-1.dsc Git packaging repository: https://salsa.debian.org/js-team/node-macaddress.git Changes since the last upload: node-macaddress (0.2.9-1) unstable; urgency=medium . * New upstream release. + Fix a vulnerability to arbitrary code execution attack. * Bump Standards-Version to 4.1.4 (no changes needed). * d/rules: Use "dh_missing --fail-missing". * d/copyright: Refresh copyright information. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- On Wed, Jun 27, 2018 at 01:38:54PM +0800, Boyuan Yang wrote: > * Package name: node-macaddress > Version : 0.2.9-1 > node-macaddress (0.2.9-1) unstable; urgency=medium > . >* New upstream release. > + Fix a vulnerability to arbitrary code execution attack. >* Bump Standards-Version to 4.1.4 (no changes needed). >* d/rules: Use "dh_missing --fail-missing". >* d/copyright: Refresh copyright information. ✓ -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices.--- End Message ---
Bug#902894: marked as done (RFS: fcitx-qt5/1.2.3-1)
Your message dated Wed, 4 Jul 2018 00:39:37 +0200 with message-id <20180703223937.idmmcz7dtkly2...@angband.pl> and subject line Re: Bug#902894: RFS: fcitx-qt5/1.2.3-1 has caused the Debian Bug report #902894, regarding RFS: fcitx-qt5/1.2.3-1 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.) -- 902894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian-input-met...@lists.debian.org a...@debian.org sunwea...@debian.org s...@debian.org Dear Aron, Mike, debian-input-method members and mentors, As part of bug fixes and package rebuild in Input Method Team, I prepared a team upload for package "fcitx-qt5" and am currently looking for a sponsor for this package. Levels of rebuild (and bugfix): Level 1: * libmarisa0 (done), libopencc2 (done) Level 2: * libbkc2 (done), libkkc-data (done), librime1 (done) Level 3: * brise (done), fcitx (done) Level 4: * fcitx-qt5, goldendict, ibus-libzhuyin, fcitx-kkc, ibus-kkc, ibus-rime ^ we are here Level 5: * fcitx-rime * Package name: fcitx-qt5 Version : 1.2.3-1 Upstream Author : Weng Xuetian * URL : https://github.com/fcitx/fcitx-qt5 * License : GPL-2+ Section : libs It builds those binary packages: fcitx-frontend-qt5 - Free Chinese Input Toy of X - Qt5 IM Module frontend fcitx5-module-quickphrase-editor - Flexible Input Method Framework - Quick Phrase editor module libfcitx-qt5-1 - Free Chinese Input Toy of X - D-Bus client libraries for Qt5 libfcitx-qt5-data - Free Chinese Input Toy of X - data files for Qt5 integration libfcitx-qt5-dev - Free Chinese Input Toy of X - Devel files for libfcitx-qt5 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fcitx-qt5 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fcitx-qt5/fcitx-qt5_1.2.3-1.dsc Git packaging repository: https://salsa.debian.org/debian/fcitx-qt5 Changes since the last rebuild: fcitx-qt5 (1.2.3-1) unstable; urgency=medium . * Team upload. * New upstream release. + Fix FTBFS with Qt 5.11. * Apply "wrap-and-sort -abst". * debian/control: Update YunQiang Su's email address with @debian.org one. * Drop backported patches. -- Regards, Boyuan Yang --- End Message --- --- Begin Message --- On Tue, Jul 03, 2018 at 12:12:25PM +0800, Boyuan Yang wrote: > * Package name: fcitx-qt5 >Version : 1.2.3-1 > fcitx-qt5 (1.2.3-1) unstable; urgency=medium > . >* Team upload. >* New upstream release. > + Fix FTBFS with Qt 5.11. >* Apply "wrap-and-sort -abst". >* debian/control: Update YunQiang Su's email address with @debian.org one. >* Drop backported patches. ✓ -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices.--- End Message ---
Bug#902737: marked as done (RFS: sunpinyin/3.0.0~rc1+ds1-1 [RC])
Your message dated Wed, 4 Jul 2018 00:23:38 +0200 with message-id <20180703222336.buc5ibvmgs54j...@angband.pl> and subject line Re: Bug#902737: RFS: sunpinyin/3.0.0~rc1+ds1-1 [RC] has caused the Debian Bug report #902737, regarding RFS: sunpinyin/3.0.0~rc1+ds1-1 [RC] 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.) -- 902737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important X-Debbugs-CC: guoli...@debian.org debian-input-met...@lists.debian.org sunwea...@debian.org Dear Mike, Liang, debian-input-method members and mentors, As part of bug fixes and package rebuild in Debian Input Method Team, I prepared a team upload for package "sunpinyin" and I'm currently looking for a sponsor for this package. Besides, I am looking for a DD to help to create a git repository under Debian group on Salsa platform and grant me (hosiet-guest) write access so that I could push and maintain changes there. Levels of rebuild (and bugfix): Level 1: * sunpinyin (libsunpinyin), fcitx (separate RFS #902675) ^ we are here Level 2: * xsunpinyin, fcitx-sunpinyin, ibus-sunpinyin, ucimf-sunpinyin * Package name: sunpinyin Version : 3.0.0~rc1+ds1-1 Upstream Author : Sun Microsystems, Inc and other Sunpinyin Developers * URL : https://github.com/sunpinyin/sunpinyin/ * License : LGPL-2.1 or CDDL Section : libs It builds those binary packages: libsunpinyin-dev - Simplified Chinese Input Method from SUN (development) libsunpinyin3v5 - Simplified Chinese Input Method from SUN (runtime) python-sunpinyin - Simplified Chinese Input Method from SUN (Python binding) sunpinyin-utils - Simplified Chinese Input Method from SUN (utilities) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sunpinyin Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sunpinyin/sunpinyin_3.0.0~rc1+ds1-1.dsc Git packaging repository (proposed, not exist yet): https://salsa.debian.org/debian/sunpinyin Git packaging repository (temporary, will be removed after upload): https://salsa.debian.org/hosiet-guest/sunpinyin Changes since the last upload: sunpinyin (3.0.0~rc1+ds1-1) unstable; urgency=medium . * Team upload. * New upstream snapshot 20180629. + Added support for riscv64 architecture. (Closes: #898019) + Made the build reproducible. (Closes: #860201) + Various fixes. * debian: Apply "wrap-and-sort -abst". * debian/control: + Update Maintainer field with debian-input-method mailing list address. (Closes: #899693) + Bump debhelper compat to v11. + Bump Standards-Version to 4.1.4. + Update homepage information. (Closes: #860202) + Drop unnecessary build dependency quilt. + Drop old -dbg package in favor of automatic -dbgsym package. + Migrate git packaging repo onto Salsa platform. + Update Uploaders list and use @debian.org mail address. * debian/copyright: + Explicitly write wrapper files in Files-Excluded field. + Refresh information. * debian/changelog: + Remove trailing spaces. * debian/patches/backport: Backport all latter commits from trunk. * debian/rules: + Use "dh_missing --fail-missing". + Add full hardening. + Update dh_strip for automatic debug package migration. * debian/watch: Refine and reintroduce watch file. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- On Sat, Jun 30, 2018 at 09:42:29AM +0800, Boyuan Yang wrote: > Besides, I am looking for a DD to help to create a git repository under Debian > group on Salsa platform and grant me (hosiet-guest) write access so that I > could push and maintain changes there. Done, temp repository not pushed. > * Package name: sunpinyin >Version : 3.0.0~rc1+ds1-1 > sunpinyin (3.0.0~rc1+ds1-1) unstable; urgency=medium > . >* Team upload. >* New upstream snapshot 20180629. > + Added support for riscv64 architecture. (Closes: #898019) > + Made the build reproducible. (Closes: #860201) > + Various fixes. >* debian: Apply "wrap-and-sort -abst". >* debian/control: > + Update Maintainer field with debian-input-method mailing list address. >(Closes: #899693) > + Bump
Bug#900368: RFS: pygithub/1.40a3-1 [ITP]
On Tue, Jul 03, 2018 at 06:00:34PM -0300, eamanu15 wrote: > Hello Dimitry, > > Thanks for you email. I Will make the changes that you recommend. > > I have a cuestion for you. When I update to the version 1.40, Do I merge > all the changelog entries, including 1.35-1 upload, isn't? Yes, it is better to merge these entries and keep one entry per actual upload to archive. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#900368: RFS: pygithub/1.40a3-1 [ITP]
Hello Dimitry, Thanks for you email. I Will make the changes that you recommend. I have a cuestion for you. When I update to the version 1.40, Do I merge all the changelog entries, including 1.35-1 upload, isn't? Thanks Regards Arias Emmanuel eamanu.com El mar., 3 de jul. de 2018 17:17, Dmitry Shachnev escribió: > Control: merge 898416 898811 900368 > > Hi Emmanuel! > > On Tue, May 29, 2018 at 12:35:25PM -0300, eamanu15 wrote: > > Package: sponsorship-requests > > Severity: normal > > > > Dear mentors, > > > > I am looking for a sponsor for my package "pygithub" > > Note that I am merging your three RFS bugs. If you want to ping, just reply > to the existing bug, not file a new one. > > Here are my comments about your changes. > > - It would be nice if you based the repository on the existing Git > repository [1], rather than starting from scratch. > > Also for new team repositories as this one, it is better to use Gbp-Pq > workflow as described in the team wiki [2]. > > - Please merge the last three changelog entries, as 1.35-1 upload did not > happen. > > - When building in the current sid, I get Lintian warnings about three > files > shipped in /usr/lib/python3.7/dist-packages/. > > That probably happens because of output of 2to3 is slightly different in > Python 3.6 and 3.7 (e.g. files.items() vs. iter(files.items())), and > dh_python3 does not remove the file if it does not match. > > I would recommend removing debian/python3-github/usr/lib/python3.* > manually > in debian/rules. Keeping debian-python@ in Cc in case someone has a > better > idea. > > - A new stable 1.40 release has been released on June 26th [3]. > Can you update from alpha to the stable version? > > Also please add uversionmangle to debian/watch (like here [4]), to make > it > treat 1.40 as a higher version than 1.40aN. > > [1]: > https://alioth-archive.debian.org/git/users/kaction-guest/pygithub.git.tar.xz > [2]: https://wiki.debian.org/Python/GitPackagingPQ > [3]: https://pypi.org/project/PyGithub/1.40/ > [4]: https://pypi.debian.net/PyGithub/watch > > -- > Dmitry Shachnev >
Bug#900368: RFS: pygithub/1.40a3-1 [ITP]
Control: merge 898416 898811 900368 Hi Emmanuel! On Tue, May 29, 2018 at 12:35:25PM -0300, eamanu15 wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "pygithub" Note that I am merging your three RFS bugs. If you want to ping, just reply to the existing bug, not file a new one. Here are my comments about your changes. - It would be nice if you based the repository on the existing Git repository [1], rather than starting from scratch. Also for new team repositories as this one, it is better to use Gbp-Pq workflow as described in the team wiki [2]. - Please merge the last three changelog entries, as 1.35-1 upload did not happen. - When building in the current sid, I get Lintian warnings about three files shipped in /usr/lib/python3.7/dist-packages/. That probably happens because of output of 2to3 is slightly different in Python 3.6 and 3.7 (e.g. files.items() vs. iter(files.items())), and dh_python3 does not remove the file if it does not match. I would recommend removing debian/python3-github/usr/lib/python3.* manually in debian/rules. Keeping debian-python@ in Cc in case someone has a better idea. - A new stable 1.40 release has been released on June 26th [3]. Can you update from alpha to the stable version? Also please add uversionmangle to debian/watch (like here [4]), to make it treat 1.40 as a higher version than 1.40aN. [1]: https://alioth-archive.debian.org/git/users/kaction-guest/pygithub.git.tar.xz [2]: https://wiki.debian.org/Python/GitPackagingPQ [3]: https://pypi.org/project/PyGithub/1.40/ [4]: https://pypi.debian.net/PyGithub/watch -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#902949: RFS: elpy/1.22.0-1
Package: sponsorship-requests Severity: normal Dear Chris, I have CCed you because you've sponsored past releases of Elpy. To add to the changelog, I realised that it would ease long-term maintenance to make 0001-Disable-failing-tests.patch more granular—at a minimum, a patch for a test known to always fail on buildd, and a patch that tests interoperation with a package that Debian does not provide. Dear mentors, I am looking for a sponsor for my package "elpy" Package name: elpy Version : 1.22.0-1 Upstream Author : Jorgen Schaefer URL : https://github.com/jorgenschaefer/elpy License : GPL-3+ Section : devel It builds this binary package: elpa-elpy - Emacs Python Development Environment To access further information about this package, please visit the following URL: https://mentors.debian.net/package/elpy Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/e/elpy/elpy_1.22.0-1.dsc Or clone with git: git clone https://salsa.debian.org/emacsen-team/elpy.git More information about elpy can be obtained from https://github.com/jorgenschaefer/elpy Changes since the last upload: elpy (1.22.0-1) unstable; urgency=medium [ Nicholas D Steeves ] * New upstream version. * Add 0002-Disable-tests-for-black-code-formatter.patch - Debian does not yet provide a package for Black, "the uncompromising Python code formatter" (https://github.com/ambv/black). - Disable these tests until there is something to test. * Rename 0001-Disable-failing-tests.patch to -> 0001-Disable-test-shell-send-region-or-buffer.patch -- Nicholas D Steeves Tue, 03 Jul 2018 14:39:24 -0400 elpy (1.21.0-1) unstable; urgency=medium Regards, Nicholas D Steeves
Re: Explicit Autoconf disables
On Tue, 03 Jul 2018, Ferenc Wágner wrote: > When building packages in clean chroots many configure checks are > expected to fail not finding their dependencies. This is fine. Until > somebody tries to build the package in a not so clean chroot, where the > additional packages present satisfy some of these checks enabling extra > features. Or even breaking the build by exposing bugs (see #874600 for > an example). > > Is adding all possible --disable-whatever options to the configure call > a good practice? It clutters debian/rules, isn't easy to do > exhaustively in an obviously correct way, but protects against some > changes in the build environment. I'm interested in hearing your takes > on the issue. You could disable them in configure, yes. But often this is addressed as build-conflicts, instead. Especially when you're not going to *really* test if the end result with the undesired dependencies installed but the feature disabled in configure. Which one is best depends really on how easy you want to make for people to selectively enable these features on local rebuilds. -- Henrique Holschuh
Explicit Autoconf disables
Dear Mentors, When building packages in clean chroots many configure checks are expected to fail not finding their dependencies. This is fine. Until somebody tries to build the package in a not so clean chroot, where the additional packages present satisfy some of these checks enabling extra features. Or even breaking the build by exposing bugs (see #874600 for an example). Is adding all possible --disable-whatever options to the configure call a good practice? It clutters debian/rules, isn't easy to do exhaustively in an obviously correct way, but protects against some changes in the build environment. I'm interested in hearing your takes on the issue. -- Thanks, Feri
Bug#902425: marked as done (RFS: gammaray/2.9.0-2.1 [NMU])
Your message dated Tue, 3 Jul 2018 10:19:43 +0200 with message-id <0dd8f79b-4113-2e85-9555-14f7e3728...@debian.org> and subject line Re: RFS: gammaray/2.9.0-2.1 [NMU] has caused the Debian Bug report #902425, regarding RFS: gammaray/2.9.0-2.1 [NMU] 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.) -- 902425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902425 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 "gammaray" * Package name: gammaray Version : 2.9.0-2.1 Upstream Author : Klarälvdalens Datakonsult AB, a KDAB Group company * URL : http://www.kdab.com/gammaray * License : GPL-2+ Section : devel It builds those binary packages: gammaray - Tool for examining the internals of Qt application gammaray-dev - GammaRay plugin development files gammaray-plugin-bluetooth - QtBluetooth type support for GammaRay gammaray-plugin-kjobtracker - KJob tracker plugin for GammaRay gammaray-plugin-positioning - Qt5Positioning type support for GammaRay gammaray-plugin-quickinspector - GammaRay plugin for inspecting QtQuick2 applications gammaray-plugin-waylandinspector - Wayland compositor inspector plugin for GammaRay To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gammaray Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gammaray/gammaray_2.9.0-2.1.dsc Changes since the last upload: gammaray (2.9.0-2.1) unstable; urgency=medium * Non-maintainer upload. - Rebuild with Qt 5.10 (Closes: #902098). * d/gammaray.install: Remove the 2nd line about *gammaray_3dinspector* because they don't get compiled. -- Yanhao Mo signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Tue, 26 Jun 2018 13:35:17 + Yanhao Mo wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "gammaray" > > * Package name: gammaray >Version : 2.9.0-2.1 >Upstream Author : Klarälvdalens Datakonsult AB, a KDAB Group company > * URL : http://www.kdab.com/gammaray > * License : GPL-2+ >Section : devel > > It builds those binary packages: > > gammaray - Tool for examining the internals of Qt application > gammaray-dev - GammaRay plugin development files > gammaray-plugin-bluetooth - QtBluetooth type support for GammaRay > gammaray-plugin-kjobtracker - KJob tracker plugin for GammaRay > gammaray-plugin-positioning - Qt5Positioning type support for GammaRay > gammaray-plugin-quickinspector - GammaRay plugin for inspecting QtQuick2 > applications > gammaray-plugin-waylandinspector - Wayland compositor inspector plugin for > GammaRay > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/gammaray > > > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/g/gammaray/gammaray_2.9.0-2.1.dsc > > Changes since the last upload: > > gammaray (2.9.0-2.1) unstable; urgency=medium > > * Non-maintainer upload. > - Rebuild with Qt 5.10 (Closes: #902098). > * d/gammaray.install: Remove the 2nd line about *gammaray_3dinspector* > because they don't get compiled. > on my way, thanks! G. > -- > Yanhao Mo--- End Message ---
