Bug#972473: RFS: ipcalc-ng/1.0.0-1 -- parameter calculator for IPv4 and IPv6 addresses
Control: tags -1 moreinfo On Sun, Oct 18, 2020 at 08:25:11PM -0300, Fabio Augusto De Muzio Tobich wrote: >... > Changes since the last upload: > > ipcalc-ng (1.0.0-1) unstable; urgency=medium >... >* debian/manpage/ipcalc-ng.1: added to provide a manpage generated from the > upstream markdown file with a bug free ronn. >... >- 030_do-not-use-upstream-manpage.patch: created to not generate the > manpage from the upstream markdown file. >... It would be better to get ronn in Debian fixed. Is the problem #964322 or a different issue? > Regards, cu Adrian
Bug#972472: marked as done (RFS: sudoku-solver/1.0.1-1 -- sudoku puzzles solver)
Your message dated Fri, 6 Nov 2020 09:26:39 +0200 with message-id <20201106072639.GA20201@localhost> and subject line Re: Bug#972472: RFS: sudoku-solver/1.0.1-1 -- sudoku puzzles solver has caused the Debian Bug report #972472, regarding RFS: sudoku-solver/1.0.1-1 -- sudoku puzzles solver 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.) -- 972472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972472 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 "sudoku-solver": * Package name: sudoku-solver Version : 1.0.1-1 Upstream Author : https://bitbucket.org/admsasha/sudoku-solver/issues/new * URL : https://bitbucket.org/admsasha/sudoku-solver * License : GPL-3+, MIT * Vcs : https://salsa.debian.org/debian/sudoku-solver Section : games It builds those binary packages: sudoku-solver - sudoku puzzles solver To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sudoku-solver/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sudoku-solver/sudoku-solver_1.0.1-1.dsc The vcs repo on salsa is up to date and can also be used: https://salsa.debian.org/debian/sudoku-solver Changes since the last upload: sudoku-solver (1.0.1-1) unstable; urgency=medium . * New upstream release. * Upload to unstable. * debian/control: added 'qt5-qmake:native' in Build-Depends field to prevent FTCBFS. * debian/copyright: - Removed 'create-man.sh' file block, it was removed from package. - Removed the BSD-3-Clause license block, not used anymore. * debian/manpage/: removed, manpage provided upstream now. * debian/manpages: updated manpage path. * debian/source/lintian-overrides: removed, not needed anymore. * debian/tests/control: changed last test to run a script instead a Test-Command and marked as superficial. * debian/tests/run: added to run a simple test. Regards, -- ⢀⣴⠾⠻⢶⣦⠀ Fabio A. De Muzio Tobich ⣾⠁⢰⠒⠀⣿⡁ 9730 4066 E5AE FAC2 2683 ⢿⡄⠘⠷⠚⠋⠀ D03D 4FB3 B4D3 7EF6 3B2E ⠈⠳⣄ GPG:rsa4096/7EF63B2E signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Sun, Oct 18, 2020 at 07:24:10PM -0300, Fabio Augusto De Muzio Tobich wrote: >... > sudoku-solver (1.0.1-1) unstable; urgency=medium >... Thanks, uploaded. > Regards, cu Adrian--- End Message ---
Bug#972383: marked as done (RFS: simple-scan/3.38.1-1 -- Simple Scanning Utility)
Your message dated Fri, 6 Nov 2020 08:54:04 +0200 with message-id <20201106065404.GA18016@localhost> and subject line Re: Bug#972383: RFS: simple-scan/3.38.1-1 -- Simple Scanning Utility has caused the Debian Bug report #972383, regarding RFS: simple-scan/3.38.1-1 -- Simple Scanning Utility 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.) -- 972383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972383 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 "simple-scan": Package name: simple-scan Version : 3.38.1-1 Upstream Author : Robert Ancell URL : https://gitlab.gnome.org/GNOME/simple-scan License : GPL-3+ Vcs : https://jff.email/cgit/simple-scan.git Section : gnome It builds those binary packages: simple-scan - Simple Scanning Utility To access further information about this package, please visit the following URL: https://mentors.debian.net/package/simple-scan/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/simple-scan/simple-scan_3.38.1-1.dsc or from git https://jff.email/cgit/simple-scan.git?h=release%2Fdebian%2F3.38.1-1 Changes since the last upload: simple-scan (3.38.1-1) unstable; urgency=medium . * New upstream release. 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. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- On Sat, Oct 17, 2020 at 01:20:16PM +0200, Jörg Frings-Fürst wrote: >... > Changes since the last upload: > > simple-scan (3.38.1-1) unstable; urgency=medium > . >* New upstream release. Thanks, uploaded. > CU > Jörg cu Adrian--- End Message ---
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
Em qui., 5 de nov. de 2020 às 20:25, Carlos Henrique Lima Melara escreveu: > > Hi, > > On Thu, Nov 05, 2020 at 09:55:31PM +0500, Andrey Rahmatullin wrote: > > On Thu, Nov 05, 2020 at 10:58:16AM -0500, Tong Sun wrote: > > > So I just ignore it, without trying to fix blhc? > > It's not a blhc problem, nothing to fix there. > > It cannot know which of the compilation commands in your build process are > > important. > > So I've been very interested in this problem (really don't know why ) > but it may have a solution. This bug #725484 is similar to your problem. > Also in the last release 0.12 this a debian/NEWS was created, take a look: > > blhc (0.12-1) unstable; urgency=medium > > Since 0.12 version, blhc is able to ignore false positives spotted by > line(s) "injected" inside .build file via debian/rules. It is useful > for Salsa automated tests and to skip wrong lines shown in local blhc > report. See more details in blhc(1) manpage. There are examples in > /usr/share/doc/blhc/README.Debian. > > -- Joao Eriberto Mota Filho Wed, 29 Jul 2020 20:41:39 > -0300 > > This might solve the problem. If it does, let us know. > > Cheers, > Charles A good catch Charles, but it is more appropriate to false positives, e.g. an echo command from upstream saying that you can change the options to use 'gcc -g -O2' only. So, when blhc will see 'gcc -c -O2' in the build log, it will tell about a hardening issue. You can see this case in ngetty[1]: echo "CC = diet -Os gcc -W"; [1] https://buildd.debian.org/status/fetch.php?pkg=ngetty=amd64=1.1-9=1596428459=0 shc has an upstream problem because the tests do not consider CPPFLAGS (via Makefile). Consequently, dpkg is not able to send CPPFLAGS content to the test commands. The upstream should fix it. A workaround in Debian is to send -D_FORTIFY_SOURCE=2 via CFLAGS. To make it, the following line must be placed in debian/rules: export DEB_CFLAGS_MAINT_APPEND = -D_FORTIFY_SOURCE=2 Cheers, Eriberto
Bug#973849: RFS: pppconfig/2.3.25 [QA] [RC] -- Text menu based utility for configuring ppp
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "pppconfig": * Package name: pppconfig Version : 2.3.25 Section : admin It builds those binary packages: pppconfig - Text menu based utility for configuring ppp To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pppconfig/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pppconfig/pppconfig_2.3.25.dsc Changes since the last upload: pppconfig (2.3.25) unstable; urgency=medium . * QA upload. * Remove dh-systemd Build-Depends, move to debhelper 10. (Closes: #958607) * Remove pppconfig.lintian-overrides, contained removed override init.d-script-missing-dependency-on-remote_fs throwing lintian E. Regards, Ryan Finnie signature.asc Description: OpenPGP digital signature
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
Hi, On Thu, Nov 05, 2020 at 09:55:31PM +0500, Andrey Rahmatullin wrote: > On Thu, Nov 05, 2020 at 10:58:16AM -0500, Tong Sun wrote: > > So I just ignore it, without trying to fix blhc? > It's not a blhc problem, nothing to fix there. > It cannot know which of the compilation commands in your build process are > important. So I've been very interested in this problem (really don't know why ) but it may have a solution. This bug #725484 is similar to your problem. Also in the last release 0.12 this a debian/NEWS was created, take a look: blhc (0.12-1) unstable; urgency=medium Since 0.12 version, blhc is able to ignore false positives spotted by line(s) "injected" inside .build file via debian/rules. It is useful for Salsa automated tests and to skip wrong lines shown in local blhc report. See more details in blhc(1) manpage. There are examples in /usr/share/doc/blhc/README.Debian. -- Joao Eriberto Mota Filho Wed, 29 Jul 2020 20:41:39 -0300 This might solve the problem. If it does, let us know. Cheers, Charles
salsa: new repo tinydyndns
Hi, I intend to do some QA work on tinydyndns. Could someone please create that repository under the debian namespace and add me (lyknode) as Maintainer? Thanks, https://tracker.debian.org/pkg/tinydyndns -- Baptiste Beauplat - lyknode OpenPGP_0x1EDBAA3C6926AF92.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
Bug#961996: marked as done (RFS: uriparser/0.9.4+dfsg-1 -- URI parsing library compliant with RFC 3986)
Your message dated Thu, 5 Nov 2020 22:37:54 +0200 with message-id <20201105203754.GI6151@localhost> and subject line Re: Bug#961996: RFS: uriparser/0.9.4+dfsg-1 -- URI parsing library compliant with RFC 3986 has caused the Debian Bug report #961996, regarding RFS: uriparser/0.9.4+dfsg-1 -- URI parsing library compliant with RFC 3986 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.) -- 961996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961996 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 "uriparser" Package name: uriparser Version : 0.9.4+dfsg-1 Upstream Author : Sebastian Pipping URL : http://uriparser.sourceforge.net License : BSD-3-clause Vcs : https://jff.email/cgit/uriparser.git Section : libs It builds those binary packages: liburiparser1 - URI parsing library compliant with RFC 3986 liburiparser-dev - development files for uriparser liburiparser-doc - documentation files for uriparser To access further information about this package, please visit the following URL: https://mentors.debian.net/package/uriparser Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.4+dfsg-1.dsc or from git: https://jff.email/cgit/uriparser.git/?h=release%2Fdebian%2F0.9.4%2Bdfsg-1 Changes since the last upload: * New upstream release. - Refresh patch. - Refresh symbols file. * Declare compliance with Debian Policy 4.5.0 (No changes needed). * Migrate to debhelper-compat 13: - Remove debian/compat. - Bump minimum debhelper-compat version in debian/control to = 13. - New debian/not-installed: + Add all files of dh_missing errors. * Add suffix +dfsg to changelog version number to make lintian happy. * debian/watch: - Add +dsfg staff. * debian/control: - Add Rules-Requires-Root: no. * debian/copyright: - Add year 2020 to myself. CU Jörg Frings-Fürst -- 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. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- On Sat, Oct 17, 2020 at 07:46:20PM +0200, Jörg Frings-Fürst wrote: >... > Typo corrected. > > > The package is uploaded to mentors > https://mentors.debian.net/package/uriparser/ > > > and can downloaded > > https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.4+dfsg-1.dsc >... Thanks, uploaded. > CU > Jörg cu Adrian--- End Message ---
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Thu, Nov 05, 2020 at 10:58:16AM -0500, Tong Sun wrote: > So I just ignore it, without trying to fix blhc? It's not a blhc problem, nothing to fix there. It cannot know which of the compilation commands in your build process are important. -- WBR, wRAR signature.asc Description: PGP signature
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Thu, Nov 05, 2020 at 01:32:49PM -0300, Carlos Henrique Lima Melara wrote: > I think you can ignore for now but would be really nice if you could report > it to the upstream or fill a bug in the blhc package. It's not a bug in blhc. -- WBR, wRAR signature.asc Description: PGP signature
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
Hi, On Thu, Nov 05, 2020 at 10:58:16AM -0500, Tong Sun wrote: > > On Thu, Nov 5, 2020 at 10:52 AM Carlos Henrique Lima Melara wrote: > > > > On Thu, Nov 05, 2020 at 08:49:33AM -0500, Tong Sun wrote: > > > > > So, looking at the build log after you removed the export from d/rules [1] > > seens to build with -D_FORTIFY_SOURCE=2 (look at line 1223). > > > > [1] https://salsa.debian.org/debian/shc/-/jobs/1138271 > > > > > On Thu, Nov 5, 2020 at 8:21 AM Andrey Rahmatullin wrote: > > > > On Thu, Nov 05, 2020 at 08:08:17AM -0500, Tong Sun wrote: > > > > > > > > > > Anything else I can do? > > > > > > > > If blhc complains even without this line, I suspect it captures the > > > > comnpilation lines from the tests, in which case you can either ignore > > > > that or change the test commands. Always read the build log manually > > > > before trying to fix blhc output. > > > > This may be what's happening. > > So I just ignore it, without trying to fix blhc? I think you can ignore for now but would be really nice if you could report it to the upstream or fill a bug in the blhc package. Maybe someone else could opinion on this matter too. Cheers, Charles
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Thu, Nov 5, 2020 at 10:52 AM Carlos Henrique Lima Melara wrote: > > Hi, > > On Thu, Nov 05, 2020 at 08:49:33AM -0500, Tong Sun wrote: > > On Thu, Nov 5, 2020 at 8:21 AM Andrey Rahmatullin wrote: > > > > > > On Thu, Nov 05, 2020 at 08:08:17AM -0500, Tong Sun wrote: > > > > > > I used > > > > > > > > > > > > export DEB_BUILD_MAINT_OPTIONS = hardening=+all > > > > > > > > > > > > to fix the hardening issue, but it yields the following error from > > > > > > blhc: > > > > > > > > > > > > CPPFLAGS missing (-D_FORTIFY_SOURCE=2) > > > > > > > > > > > > See https://salsa.debian.org/debian/shc/-/jobs/1126952 > > > > > > > > > > > > I've tried some "solutions" that I found from the internet but > > > > > > nothing worked. > > > > > > > > > > > > Anyone know how to fix this please? > > > > > Remove "export CPPFLAGS = " from debian/rules. > > > > > > > > That was actually my "fix" -- There wasn't such a line and I got > > > > `CPPFLAGS missing (-D_FORTIFY_SOURCE=2)` in the first place. > > > And this "fix" removed -D_FORTIFY_SOURCE=2 from the main compilation > > > command as you can see if you compare the build logs, so removing it fixes > > > the actual problem. > > > > removing it yields > > https://salsa.debian.org/debian/shc/-/jobs/1138279 > > the same as where it all begins -- > > https://salsa.debian.org/debian/shc/-/jobs/1126858 > > So, looking at the build log after you removed the export from d/rules [1] > seens to build with -D_FORTIFY_SOURCE=2 (look at line 1223). > > [1] https://salsa.debian.org/debian/shc/-/jobs/1138271 > > > > > Anything else I can do? > > > If blhc complains even without this line, I suspect it captures the > > > comnpilation lines from the tests, in which case you can either ignore > > > that or change the test commands. Always read the build log manually > > > before trying to fix blhc output. > > This may be what's happening. So I just ignore it, without trying to fix blhc?
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
Hi, On Thu, Nov 05, 2020 at 08:49:33AM -0500, Tong Sun wrote: > On Thu, Nov 5, 2020 at 8:21 AM Andrey Rahmatullin wrote: > > > > On Thu, Nov 05, 2020 at 08:08:17AM -0500, Tong Sun wrote: > > > > > I used > > > > > > > > > > export DEB_BUILD_MAINT_OPTIONS = hardening=+all > > > > > > > > > > to fix the hardening issue, but it yields the following error from > > > > > blhc: > > > > > > > > > > CPPFLAGS missing (-D_FORTIFY_SOURCE=2) > > > > > > > > > > See https://salsa.debian.org/debian/shc/-/jobs/1126952 > > > > > > > > > > I've tried some "solutions" that I found from the internet but > > > > > nothing worked. > > > > > > > > > > Anyone know how to fix this please? > > > > Remove "export CPPFLAGS = " from debian/rules. > > > > > > That was actually my "fix" -- There wasn't such a line and I got > > > `CPPFLAGS missing (-D_FORTIFY_SOURCE=2)` in the first place. > > And this "fix" removed -D_FORTIFY_SOURCE=2 from the main compilation > > command as you can see if you compare the build logs, so removing it fixes > > the actual problem. > > removing it yields > https://salsa.debian.org/debian/shc/-/jobs/1138279 > the same as where it all begins -- > https://salsa.debian.org/debian/shc/-/jobs/1126858 So, looking at the build log after you removed the export from d/rules [1] seens to build with -D_FORTIFY_SOURCE=2 (look at line 1223). [1] https://salsa.debian.org/debian/shc/-/jobs/1138271 > > > Anything else I can do? > > If blhc complains even without this line, I suspect it captures the > > comnpilation lines from the tests, in which case you can either ignore > > that or change the test commands. Always read the build log manually > > before trying to fix blhc output. This may be what's happening. Cheers, Charles
Bug#973750: RFS: pekwm/0.1.17-4 [QA] [RC] -- very light window manager
Control: tags -1 moreinfo On Wed, Nov 04, 2020 at 10:37:14AM -0300, Carlos Henrique Lima Melara wrote: >... > Changes since the last upload: Looks good to me, except: > pekwm (0.1.17-4) unstable; urgency=medium >... >- 50_fix-FTBFS-with-gcc-10.patch: created to fix a FTBFS bug. > (Closes: #957672) >... Please use the upstream fix instead of fixing it differently: https://github.com/pekdon/pekwm/commit/e2e7456ce3d12c9c9330e615d2c90b3c41a90a67 > Regards, > Carlos Melara (charles) cu Adrian
Bug#973320: marked as done (RFS: lilo/1:24.2-5.1 [NMU] [RC] -- LInux LOader - the classic OS boot loader)
Your message dated Thu, 5 Nov 2020 17:02:41 +0200 with message-id <20201105150241.GA11426@localhost> and subject line Re: Bug#973320: RFS: lilo/1:24.2-5.1 [NMU] [RC] -- LInux LOader - the classic OS boot loader has caused the Debian Bug report #973320, regarding RFS: lilo/1:24.2-5.1 [NMU] [RC] -- LInux LOader - the classic OS boot loader 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.) -- 973320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, [RFS: This NMU fixes a GCC-10 ftbfs (#957490) which has kept lilo out of testing since August.] I am looking for a sponsor for my package "lilo": * Package name: lilo Version : 1:24.2-5.1 Upstream Author : Joachim Wiedorn * URL : http://lilo.joonet.de/ * License : BSD-3-clause, GPL-2+ * Vcs : https://salsa.debian.org/joowie-guest/maintain_lilo.git Section : admin It builds those binary packages: lilo-doc - LInux LOader - Documentation for the classic OS boot loader lilo - LInux LOader - the classic OS boot loader To access further information about this package, please visit the following URL: https://mentors.debian.net/package/lilo/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/lilo/lilo_24.2-5.1.dsc Changes since the last upload: lilo (1:24.2-5.1) unstable; urgency=medium . * Non-maintainer upload. * Fix ftbfs with GCC-10. (Closes: #957490) Regards, -- Ryan Finnie signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Wed, Oct 28, 2020 at 12:22:47PM -0700, Ryan Finnie wrote: >... > lilo (1:24.2-5.1) unstable; urgency=medium > . >* Non-maintainer upload. >* Fix ftbfs with GCC-10. (Closes: #957490) Thanks, uploaded. > Regards, cu Adrian--- End Message ---
Bug#972075: RFS: klystrack/0.20171212-5 [RC] -- Chiptune tracker
Control: tags -1 moreinfo On Mon, Oct 12, 2020 at 10:36:29AM +0200, Gürkan Myczko wrote: >... > Changes since the last upload: > > klystrack (0.20171212-5) unstable; urgency=medium > . >* Add -fcommon to upstream CFLAGS. (Closes: #957407) >... Please use the proper upstream fix instead: https://github.com/kometbomb/klystron/commit/989fafc4fffb1bb881ab677fe52eb34527e08129 > Regards, Thanks Adrian
Bug#973818: RFS: scikit-build/0.11.1-1 [ITP] -- skbuild (documentation)
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "scikit-build": * Package name: scikit-build Version : 0.11.1-1 Upstream Author : The scikit-build team * URL : https://scikit-build.org * License : BSD-3-Clause, Apache-2.0, CC0-1.0, MIT * Vcs : https://salsa.debian.org/debian/scikit-build Section : python It builds those binary packages: python-skbuild-doc - skbuild (documentation) python3-skbuild - improved build system generator for Python C/C++/Fortran/Cython extensions To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scikit-build/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scikit-build/scikit-build_0.11.1-1.dsc Changes for the initial release: scikit-build (0.11.1-1) unstable; urgency=medium . * Initial release. Closes: #947097 Regards, -- Emmanuel Arias
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Thu, Nov 05, 2020 at 08:49:33AM -0500, Tong Sun wrote: > removing it yields > https://salsa.debian.org/debian/shc/-/jobs/1138279 > the same as where it all begins -- > https://salsa.debian.org/debian/shc/-/jobs/1126858 So it even shows the commands that it thinks are incorrect, and you can see that those are test commands and the main build command is not listed. -- WBR, wRAR signature.asc Description: PGP signature
Re: how to declare unsupported architecture in autopkgtest
On Wed, Nov 4, 2020 at 2:29 PM Lorenzo wrote: > Reading [1] it looks like you can list unsupported arch for autopkgtest in a > new field of the control file, > but i don't understand: how to do that? According to the documentation linked from the announcement, the Architecture field in debian/tests/control is the same as in debian/control: https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst#L178-187 https://www.debian.org/doc/debian-policy/ch-controlfields.html#architecture https://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-arch-spec https://www.debian.org/doc/debian-policy/ch-customized-programs.html#s-arch-wildcard-spec > I need to exclude arm architectures for one of my tests. What causes the test failures on ARM? Sounds like you need to list the arches it works on. -- bye, pabs https://wiki.debian.org/PaulWise
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Thu, Nov 5, 2020 at 8:21 AM Andrey Rahmatullin wrote: > > On Thu, Nov 05, 2020 at 08:08:17AM -0500, Tong Sun wrote: > > > > I used > > > > > > > > export DEB_BUILD_MAINT_OPTIONS = hardening=+all > > > > > > > > to fix the hardening issue, but it yields the following error from blhc: > > > > > > > > CPPFLAGS missing (-D_FORTIFY_SOURCE=2) > > > > > > > > See https://salsa.debian.org/debian/shc/-/jobs/1126952 > > > > > > > > I've tried some "solutions" that I found from the internet but nothing > > > > worked. > > > > > > > > Anyone know how to fix this please? > > > Remove "export CPPFLAGS = " from debian/rules. > > > > That was actually my "fix" -- There wasn't such a line and I got > > `CPPFLAGS missing (-D_FORTIFY_SOURCE=2)` in the first place. > And this "fix" removed -D_FORTIFY_SOURCE=2 from the main compilation > command as you can see if you compare the build logs, so removing it fixes > the actual problem. removing it yields https://salsa.debian.org/debian/shc/-/jobs/1138279 the same as where it all begins -- https://salsa.debian.org/debian/shc/-/jobs/1126858 > > Anything else I can do? > If blhc complains even without this line, I suspect it captures the > comnpilation lines from the tests, in which case you can either ignore > that or change the test commands. Always read the build log manually > before trying to fix blhc output. Yeah for sure, I tried, but the blhc output is just beyond me. My "fix" was my guess out of blhc output how to fix it.
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Thu, Nov 05, 2020 at 08:08:17AM -0500, Tong Sun wrote: > > > I used > > > > > > export DEB_BUILD_MAINT_OPTIONS = hardening=+all > > > > > > to fix the hardening issue, but it yields the following error from blhc: > > > > > > CPPFLAGS missing (-D_FORTIFY_SOURCE=2) > > > > > > See https://salsa.debian.org/debian/shc/-/jobs/1126952 > > > > > > I've tried some "solutions" that I found from the internet but nothing > > > worked. > > > > > > Anyone know how to fix this please? > > Remove "export CPPFLAGS = " from debian/rules. > > That was actually my "fix" -- There wasn't such a line and I got > `CPPFLAGS missing (-D_FORTIFY_SOURCE=2)` in the first place. And this "fix" removed -D_FORTIFY_SOURCE=2 from the main compilation command as you can see if you compare the build logs, so removing it fixes the actual problem. > Anything else I can do? If blhc complains even without this line, I suspect it captures the comnpilation lines from the tests, in which case you can either ignore that or change the test commands. Always read the build log manually before trying to fix blhc output. -- WBR, wRAR signature.asc Description: PGP signature
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Thu, Nov 5, 2020 at 4:38 AM Andrey Rahmatullin - w...@debian.org wrote: > > On Wed, Nov 04, 2020 at 10:28:04PM -0500, Tong Sun wrote: > > Hi, > > > > I used > > > > export DEB_BUILD_MAINT_OPTIONS = hardening=+all > > > > to fix the hardening issue, but it yields the following error from blhc: > > > > CPPFLAGS missing (-D_FORTIFY_SOURCE=2) > > > > See https://salsa.debian.org/debian/shc/-/jobs/1126952 > > > > I've tried some "solutions" that I found from the internet but nothing > > worked. > > > > Anyone know how to fix this please? > Remove "export CPPFLAGS = " from debian/rules. That was actually my "fix" -- There wasn't such a line and I got `CPPFLAGS missing (-D_FORTIFY_SOURCE=2)` in the first place. Anything else I can do?
Bug#973813: RFS: fonts-spleen/1.8.2-1 -- monospaced font for consoles and terminals
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "fonts-spleen": * Package name: fonts-spleen Version : 1.8.2-1 Upstream Author : Frederic Cambus * URL : https://github.com/fcambus/spleen * License : BSD-2-clause * Vcs : https://salsa.debian.org/fonts-team/fonts-spleen Section : fonts It builds those binary packages: fonts-spleen - monospaced font for consoles and terminals To access further information about this package, please visit the following URL: https://mentors.debian.net/package/fonts-spleen/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/fonts-spleen/fonts-spleen_1.8.2-1.dsc Changes since the last upload: fonts-spleen (1.8.2-1) unstable; urgency=medium . * New upstream version. * Bump debhelper version to 13, drop d/compat. * d/upstream/metadata: added. * d/control: - added Rules-Requires-Root. - improved long description. * d/copyright: - update copyright years. - added Upstream-Contact. * d/watch: drop template part. * d/patches/add-vector-font-of-dunkelstern-fork: set forwarded url. Regards, -- Gürkan Myczko
Bug#972276: RFS: olive-editor/20200620-1 -- Professional open-source NLE video editor
Hi G. Many thanks, I've prepared a new update with the patch applied you hinted to, it should appear on mentors.debian.net shortly. Best, On 05/11/2020 11:02, Gianfranco Costamagna wrote: > On Thu, 5 Nov 2020 10:43:40 +0100 Gianfranco Costamagna > wrote: >> Hello, thanks! >> >> I was just looking to have the qt fixes uploaded and found your RFS >> >> > > unfortunately it turned out to be not sufficient for qt 5.15.1, this > additional patch is required > https://github.com/olive-editor/olive/commit/22c5b61898f75654bf889f55c447f4d1c400b8fd > > Please prepare a new upload when possible, thanks > > https://launchpad.net/ubuntu/+source/olive-editor/20200620-1ubuntu1 > > G. > > G. >> >> On Thu, 15 Oct 2020 19:36:19 +0200 =?UTF-8?Q?G=C3=BCrkan_Myczko?= >> wrote: >>> Package: sponsorship-requests >>> Severity: normal >>> >>> Dear mentors, >>> >>> I am looking for a sponsor for my package "olive-editor": >>> >>> * Package name: olive-editor >>> Version : 20200620-1 >>> Upstream Author : Olive Team >>> * URL : https://www.olivevideoeditor.org/ >>> * License : GPL-3+, MIT >>> * Vcs : >>> https://salsa.debian.org/multimedia-team/olive-editor >>> Section : video >>> >>> It builds those binary packages: >>> >>>olive-editor - Professional open-source NLE video editor >>> >>> To access further information about this package, please visit the >>> following URL: >>> >>>https://mentors.debian.net/package/olive-editor/ >>> >>> Alternatively, one can download the package with dget using this >>> command: >>> >>>dget -x >>> https://mentors.debian.net/debian/pool/main/o/olive-editor/olive-editor_20200620-1.dsc >>> >>> Changes since the last upload: >>> >>> olive-editor (20200620-1) unstable; urgency=medium >>> . >>> * New upstream version. >>> >>> Regards, >>> -- >>>Gürkan Myczko >>> >>> >> >>
Bug#972276: RFS: olive-editor/20200620-1 -- Professional open-source NLE video editor
On Thu, 5 Nov 2020 10:43:40 +0100 Gianfranco Costamagna wrote: > Hello, thanks! > > I was just looking to have the qt fixes uploaded and found your RFS > > unfortunately it turned out to be not sufficient for qt 5.15.1, this additional patch is required https://github.com/olive-editor/olive/commit/22c5b61898f75654bf889f55c447f4d1c400b8fd Please prepare a new upload when possible, thanks https://launchpad.net/ubuntu/+source/olive-editor/20200620-1ubuntu1 G. G. > > On Thu, 15 Oct 2020 19:36:19 +0200 =?UTF-8?Q?G=C3=BCrkan_Myczko?= > wrote: > > Package: sponsorship-requests > > Severity: normal > > > > Dear mentors, > > > > I am looking for a sponsor for my package "olive-editor": > > > > * Package name: olive-editor > > Version : 20200620-1 > > Upstream Author : Olive Team > > * URL : https://www.olivevideoeditor.org/ > > * License : GPL-3+, MIT > > * Vcs : > > https://salsa.debian.org/multimedia-team/olive-editor > > Section : video > > > > It builds those binary packages: > > > >olive-editor - Professional open-source NLE video editor > > > > To access further information about this package, please visit the > > following URL: > > > >https://mentors.debian.net/package/olive-editor/ > > > > Alternatively, one can download the package with dget using this > > command: > > > >dget -x > > https://mentors.debian.net/debian/pool/main/o/olive-editor/olive-editor_20200620-1.dsc > > > > Changes since the last upload: > > > > olive-editor (20200620-1) unstable; urgency=medium > > . > > * New upstream version. > > > > Regards, > > -- > >Gürkan Myczko > > > > > >
Bug#972276: marked as done (RFS: olive-editor/20200620-1 -- Professional open-source NLE video editor)
Your message dated Thu, 5 Nov 2020 10:43:40 +0100 with message-id and subject line Re: RFS: olive-editor/20200620-1 -- Professional open-source NLE video editor has caused the Debian Bug report #972276, regarding RFS: olive-editor/20200620-1 -- Professional open-source NLE video editor 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.) -- 972276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972276 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 "olive-editor": * Package name: olive-editor Version : 20200620-1 Upstream Author : Olive Team * URL : https://www.olivevideoeditor.org/ * License : GPL-3+, MIT * Vcs : https://salsa.debian.org/multimedia-team/olive-editor Section : video It builds those binary packages: olive-editor - Professional open-source NLE video editor To access further information about this package, please visit the following URL: https://mentors.debian.net/package/olive-editor/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/o/olive-editor/olive-editor_20200620-1.dsc Changes since the last upload: olive-editor (20200620-1) unstable; urgency=medium . * New upstream version. Regards, -- Gürkan Myczko --- End Message --- --- Begin Message --- Hello, thanks! I was just looking to have the qt fixes uploaded and found your RFS G. On Thu, 15 Oct 2020 19:36:19 +0200 =?UTF-8?Q?G=C3=BCrkan_Myczko?= wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "olive-editor": > > * Package name: olive-editor > Version : 20200620-1 > Upstream Author : Olive Team > * URL : https://www.olivevideoeditor.org/ > * License : GPL-3+, MIT > * Vcs : > https://salsa.debian.org/multimedia-team/olive-editor > Section : video > > It builds those binary packages: > >olive-editor - Professional open-source NLE video editor > > To access further information about this package, please visit the > following URL: > >https://mentors.debian.net/package/olive-editor/ > > Alternatively, one can download the package with dget using this > command: > >dget -x > https://mentors.debian.net/debian/pool/main/o/olive-editor/olive-editor_20200620-1.dsc > > Changes since the last upload: > > olive-editor (20200620-1) unstable; urgency=medium > . > * New upstream version. > > Regards, > -- >Gürkan Myczko > > --- End Message ---
Re: hardening=+all caused CPPFLAGS missing (-D_FORTIFY_SOURCE=2)
On Wed, Nov 04, 2020 at 10:28:04PM -0500, Tong Sun wrote: > Hi, > > I used > > export DEB_BUILD_MAINT_OPTIONS = hardening=+all > > to fix the hardening issue, but it yields the following error from blhc: > > CPPFLAGS missing (-D_FORTIFY_SOURCE=2) > > See https://salsa.debian.org/debian/shc/-/jobs/1126952 > > I've tried some "solutions" that I found from the internet but nothing worked. > > Anyone know how to fix this please? Remove "export CPPFLAGS = " from debian/rules. -- WBR, wRAR signature.asc Description: PGP signature
