Processed: Move to the package where it was fixed

Processing commands for cont...@bugs.debian.org: > reassign 889936 libproj13 Bug #889936 {Done: Sebastiaan Couwenberg } [src:survex] survex: FTBFS with proj 5.0.0 Bug reassigned from package 'src:survex' to 'libproj13'. Ignoring request to alter found versions of bug #889936

Bug#892488: pcre2: FTBFS on mips* - test failures

Hi, Matthew Vernon wrote: > On 09/03/18 15:20, James Cowgill wrote: >> Source: pcre2 >> Version: 10.31-1 >> Severity: serious [...] >> pcre2 FTBFS on mips* with lots of testsuite failures. It looks to me >> like the JIT is bust. >> >> I forwarded the log upstream to the above address. I'll try

Bug#892499: Non-ascii characters broken in d-i (text-based installer)

Control: reassign -1 installation-locale Control: done -1 1.7+b1 As mentioned on the list, this gets fixed by rebuilding installation-locale (against the latest glibc) Samuel

Processed (with 1 error): Re: Bug#892499: Non-ascii characters broken in d-i (text-based installer)

Processing control commands: > reassign -1 installation-locale Bug #892499 [debian-installer] Non-ascii characters broken in d-i (text-based installer) Bug reassigned from package 'debian-installer' to 'installation-locale'. Ignoring request to alter found versions of bug #892499 to the same

Bug#892499: Non-ascii characters broken in d-i (text-based installer)

> It seems there is something generic broken in the installer. > A screenshot of the languagechooser screen is attached, where several broken > characters can be seen (in Arabic, Belarusian, Bulgarian, Chinese, Czech and > Greek, for example). Please also note the broken alignment of the right

Bug#887323: dewalls i386 test failure

Wow, we were using long doubles before. I don't think we need that much precision for cave survey. In catch there is Approx() that should take care of floating point comparison correctly. On Fri, Mar 9, 2018 at 11:30 AM Wookey wrote: > A bit of research tells that using

Bug#891275: marked as done (stress-ng: FTBFS with glibc 2.27: error: 'ret' undeclared (first use in this function); did you mean 'recv'?)

Your message dated Fri, 9 Mar 2018 21:25:44 +0200 with message-id <20180309192544.GN20833@localhost> and subject line Already fixed in 0.09.18-1 has caused the Debian Bug report #891275, regarding stress-ng: FTBFS with glibc 2.27: error: 'ret' undeclared (first use in this function); did you mean

Bug#892511: ruby-grape-route-helpers: FTBFS and Debci failure with ruby-grape 0.19.2-3

Source: ruby-grape-route-helpers Version: 2.1.0-1 Severity: serious https://ci.debian.net/packages/r/ruby-grape-route-helpers/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-grape-route-helpers.html ... Failures: 1)

Bug#892500: mitmproxy: Doesn't start with dependency versions currently available in Debian

Package: mitmproxy Version: 2.0.2-3 Severity: grave Justification: renders package unusable The package has unversioned dependencies like "python3-ruamel.yaml", and versioned like python3-pyperclip (>= 1.5.22). However, mitmproxy-2.0.2.egg-info/requires.txt has stricter versioning requirements,

Bug#888855: marked as done (squid3: ftbfs with GCC-7)

Your message dated Fri, 9 Mar 2018 23:50:30 +0200 with message-id <20180309215030.GP20833@localhost> and subject line Already workarounded in 3.5.27-1 has caused the Debian Bug report #55, regarding squid3: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has

Bug#892507: ruby-sequel FTBFS with Ruby 2.5

Source: ruby-sequel Version: 4.37.0-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-sequel.html ... 1) Failure: Sequel::Database dump methods#test_0036_should handle converting common defaults

Bug#892508: ruby-psych FTBFS with Ruby 2.5

Source: ruby-psych Version: 2.2.4-6 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-psych.html ... dh_auto_configure -O--buildsystem=ruby dh_ruby --configure debian/rules override_dh_auto_build-indep make[1]: Entering directory

Processed: found 889936 in 5.0.0-1

Processing commands for cont...@bugs.debian.org: > found 889936 5.0.0-1 Bug #889936 {Done: Sebastiaan Couwenberg } [libproj13] survex: FTBFS with proj 5.0.0 Marked as found in versions proj/5.0.0-1. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#892373: [INFO] Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1

On 09.03.2018 16:28, Francesco P. Lovergine wrote: Hi, > Here the fix is trivial as suggested. Even in this case it is better > upgrading to current upstream version. > Where did you get a later version from? According to http://www.castaglia.org/proftpd/ the 0.2 is the latest version. H. --

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

On 09/03/18 14:50, Yves-Alexis Perez wrote: control: tag -1 unreproducible moreinfo On Wed, 2018-03-07 at 22:37 +0100, Stuart Pook wrote: Dear Maintainer, Light-locker crashes when I unlock my session. This means that my session is not locked the next time it should be, hi Yves-Alexis

Bug#892488: pcre2: FTBFS on mips* - test failures

On 9 March 2018 18:47:25 GMT+00:00, Jonathan Nieder wrote: >Hi, > >Matthew Vernon wrote: >> On 09/03/18 15:20, James Cowgill wrote: > >>> Source: pcre2 >>> Version: 10.31-1 >>> Severity: serious >[...] >>> pcre2 FTBFS on mips* with lots of testsuite failures. It looks to me

Bug#892510: python-distutils-extra FTBFS: FAIL: test_apport_hook

Source: python-distutils-extra Version: 2.40 Severity: serious Tags: buster sid Some recent change in unstable makes python-distutils-extra FTBFS: https://tests.reproducible-builds.org/debian/history/python-distutils-extra.html

Processed: Re: Bug#889936: survex: FTBFS with proj 5.0.0

Processing commands for cont...@bugs.debian.org: > notfound 889936 survex/1.2.32-1 Bug #889936 [src:survex] survex: FTBFS with proj 5.0.0 No longer marked as found in versions survex/1.2.32-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 889936:

Bug#892499: closing 892499

close 892499 1.7+b1 thanks -- Samuel bah, j'aime bien les feux d'artifices, mais j'ai peur de me prendre un boeing sur le coin de la gueule si je vais sur le pont de brooklyn -+- #ens-mim - 11 septembre forever -+-

Processed: closing 892499

Processing commands for cont...@bugs.debian.org: > close 892499 1.7+b1 Bug #892499 [installation-locale] Non-ascii characters broken in d-i (text-based installer) Marked as fixed in versions installation-locale/1.7. Bug #892499 [installation-locale] Non-ascii characters broken in d-i

Bug#541538: duplicates and age of this bug

Hello, it seems that there are several older bugs about this configuration: #674935 and #674936 (duplicate submission) #697119 These go back to *early 2012* Can we maybe get this default configuration value adjusted? We're not talking about a code patch, here. Thanks.

Processed: Re: pcre2: FTBFS on mips* - test failures

Processing commands for cont...@bugs.debian.org: > severity 892488 serious Bug #892488 [src:pcre2] pcre2: FTBFS on mips* - test failures Severity set to 'serious' from 'important' > tags 892488 + upstream pending Bug #892488 [src:pcre2] pcre2: FTBFS on mips* - test failures Added tag(s) upstream

Processed: bug update #891956

Processing commands for cont...@bugs.debian.org: > found 891956 3.8.1-10 Bug #891956 [eclipse] eclipse no starting -ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter Marked as found in versions eclipse/3.8.1-10. > End of message, stopping processing here. Please contact me

Bug#887323: dewalls i386 test failure

On 2018-03-09 19:24 +, Philip Schuchardt wrote: > Wow, we were using long doubles before. I don't think we need that much > precision for cave survey. In catch there is Approx() that should take care of > floating point comparison correctly. Yes. Catch has approx and margin and epsilon which

Bug#887323: dewalls i386 test failure

So we need to fixed the comparisons on the dewalls library. On Fri, Mar 9, 2018 at 2:24 PM Philip Schuchardt wrote: > Wow, we were using long doubles before. I don't think we need that much > precision for cave survey. In catch there is Approx() that should take care > of

Bug#892488: pcre2: FTBFS on mips* - test failures

Hi, This is blocking git updates from migrating to testing (https://qa.debian.org/excuses.php?package=git), so my preference would be removing "mips mipsel mips64el" from the list of JIT arches for now as a stopgap. Done and uploaded, so I've downgraded this bug to important. Regards,

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 892488 important Bug #892488 [src:pcre2] pcre2: FTBFS on mips* - test failures Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 892488:

Bug#891956: Your mail

On Fri, 9 Mar 2018 20:07:32 -0500 "William L. DeRieux IV" wrote: > after editing /etc/eclipse.ini > and adding -debug to it > > I get the following output (when running eclipse): > - > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; >

Bug#892360: Bug #892360 in systemd marked as pending

Control: tag -1 pending Hello, Bug #892360 in systemd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #892360 in systemd marked as pending

Processing control commands: > tag -1 pending Bug #892360 [systemd] systemd pid 1 freezes at startup on x86 systems Added tag(s) pending. -- 892360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#892520: libpodofo: CVE-2018-8000 CVE-2018-8001 CVE-2018-8002

Package: libpodofo X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, the following vulnerabilities were published for libpodofo. CVE-2018-8000[0]: | In PoDoFo 0.9.5, there exists a heap-based buffer overflow | vulnerability in PoDoFo::PdfTokenizer::GetNextToken() in |

Processed: Bug #890043 in wcc marked as pending

Processing control commands: > tag -1 pending Bug #890043 [src:wcc] wcc's test dependencies cannot be fulfilled anymore Ignoring request to alter tags of bug #890043 to the same tags previously set -- 890043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890043 Debian Bug Tracking System

Bug#890043: wcc: diff for NMU version 0.0.2+dfsg-2.1

On Fri, 09 Mar 2018, Adrian Bunk wrote: > I've prepared an NMU for wcc (versioned as 0.0.2+dfsg-2.1) and uploaded > it to DELAYED/3. Please feel free to tell me if I should cancel it. Thanks for this, but I just uploaded a new version with this change and other cleanups too. Cheers, -- Raphaël

Bug#890043: Bug #890043 in wcc marked as pending

Control: tag -1 pending Hello, Bug #890043 in wcc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#890043: marked as done (wcc's test dependencies cannot be fulfilled anymore)

Your message dated Sat, 10 Mar 2018 00:05:12 + with message-id and subject line Bug#890043: fixed in wcc 0.0.2+dfsg-3 has caused the Debian Bug report #890043, regarding wcc's test dependencies cannot be fulfilled anymore to be marked as done. This means

Bug#873321: wrk FTBFS with luajit 2.1

Hi. I believe patch below should fix the build. Here is why changes are made. First, is luaL_reg. It was a macro for compatibility with Lua 5.0. It was defined in LuaJIT 2.0 headers, but removed in LuaJIT 2.1. The solution is to use luaL_Reg (note capital R), or to define the macro again. Next

Bug#891956: updating found version

found 891956 3.8.1-10

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 890954 serious Bug #890954 [chromium] With this version all extensions crash Bug #891656 [chromium] Adblockers fail to start Severity set to 'serious' from 'normal' Severity set to 'serious' from 'normal' > forcemerge 890954 892509 Bug

Bug#891956: (no subject)

after editing /etc/eclipse.ini and adding -debug to it I get the following output (when running eclipse): - OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Install location:     file:/usr/lib/eclipse/

Processed: severity of 889936 is important

Processing commands for cont...@bugs.debian.org: > severity 889936 important Bug #889936 {Done: Sebastiaan Couwenberg } [libproj13] survex: FTBFS with proj 5.0.0 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need

Bug#892468: proftp: Prevent migration to testing

Package: proftpd-basic Version: 1.3.6-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, for now we want to prevent the package from migrating to testing until we are sure all bugs are fixed. For now already three bugs were reported telling that some modules do not

Bug#853527: lmms: ftbfs with GCC-7

Hi lmms maintainers, Several months have passed and I found this bug still not fixed. Are you going to fix the problem soon? If not, is it okay if someone prepares an NMU and upload the fix? -- Regards, Boyuan Yang

Bug#887323: dewalls i386 test failure

On 2018-03-09 05:06 +, Wookey wrote: > > Changing the tests to this: > CHECK_THROWS( WallsSurveyParser("360.1").azimuth(Angle::Degrees) > ); > CHECK_THROWS( WallsSurveyParser("-0.1").azimuth(Angle::Degrees) ); > CHECK_THROWS( >

Processed: Re: Bug#803713: Elasticsearch should not be part of a Debian release

Processing control commands: > clone -1 -2 Bug #803713 [src:elasticsearch] Elasticsearch should not be part of a Debian release Bug 803713 cloned as bug 892466 > retitle -2 RM: elasticsearch -- ROM; NPOASR; unmaintained since ~2 years; > security issues Bug #892466 [src:elasticsearch]

Bug#803713: Elasticsearch should not be part of a Debian release

Control: clone -1 -2 Control: retitle -2 RM: elasticsearch -- ROM; NPOASR; unmaintained since ~2 years; security issues Control: severity -2 normal Control: reassign -2 ftp.debian.org On Thu, Mar 08, 2018 at 11:17:20PM +0100, Emmanuel Bourg wrote: > Le 08/03/2018 à 22:50, Nicolas Braud-Santoni a

Bug#892393: dewalls: build-depends on GCC 6

On 2018-03-09 10:23 +0100, Emilio Pozuelo Monfort wrote: > > Why do you even build-depend on libstdc++ ? That's installed through g++. > g++-6 > installs libstdc++-6-dev, while g++-7 installs libstdc++-7-dev. g++ is > build-essential, so you can just let g++ do the work here and drop the >

Bug#892467: spfquery (libspf2-2?) and spf-milter-python falsely report "Void lookup limit exceeded"

Package: spfquery Version: 1.2.10-7+b2 Severity: grave Tags: ipv6 Justification: causes non-serious data loss Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I got notified that another organization was unable

Bug#892393: dewalls: build-depends on GCC 6

On 09/03/18 12:29, Wookey wrote: > On 2018-03-09 10:23 +0100, Emilio Pozuelo Monfort wrote: >> >> Why do you even build-depend on libstdc++ ? That's installed through g++. >> g++-6 >> installs libstdc++-6-dev, while g++-7 installs libstdc++-7-dev. g++ is >> build-essential, so you can just let

Bug#892458: Security: please consider upgrade to 3.43(0)

Control: retitle -1 cfitsio: vulnerabilities Control: found -1 3.370-2 On Fri, Mar 09, 2018 at 09:56:39AM +0100, Ole Streicher wrote: > Package: cfitsio > Version: 3.420-3 > Severity: grave > Tags: security > > Hi, > > a new version of cfitsio just came out, accompanied with the following >

Processed: Re: Bug#892458: Security: please consider upgrade to 3.43(0)

Processing control commands: > retitle -1 cfitsio: vulnerabilities Bug #892458 [cfitsio] Security: please consider upgrade to 3.43(0) Changed Bug title to 'cfitsio: vulnerabilities' from 'Security: please consider upgrade to 3.43(0)'. > found -1 3.370-2 Bug #892458 [cfitsio] cfitsio:

Bug#892396: marked as done (gmp-ecm: build-depends on GCC 6)

Your message dated Fri, 09 Mar 2018 11:19:29 + with message-id and subject line Bug#892396: fixed in gmp-ecm 7.0.4+ds-2 has caused the Debian Bug report #892396, regarding gmp-ecm: build-depends on GCC 6 to be marked as done. This means that you claim

Bug#892360: systemd: No problem on my amd64 systems

On Thu, 08 Mar 2018 20:29:49 +0100 Diederik de Haas wrote: CONFIG_CGROUP_CPUACCT=y As the bug is triggered if this config is not set, no surprise. --eric

Bug#892458: Security: please consider upgrade to 3.43(0)

Package: cfitsio Version: 3.420-3 Severity: grave Tags: security Hi, a new version of cfitsio just came out, accompanied with the following notice from upstream: The NASA security team requires the following warning to all users of CFITSIO: = The CFITSIO open source software project

Bug#892460: ruby-parslet: FTBFS and Debci failure with Ruby 2.5

Source: ruby-parslet Version: 1.8.2-1 Severity: serious https://ci.debian.net/packages/r/ruby-parslet/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-parslet.html ... Failures: 1) Regression on example/mathn.rb runs successfully Failure/Error:

Bug#892311: marked as done (ncl: FTBFS on various architectures)

Your message dated Fri, 09 Mar 2018 09:36:52 + with message-id and subject line Bug#892311: fixed in ncl 6.4.0-9 has caused the Debian Bug report #892311, regarding ncl: FTBFS on various architectures to be marked as done. This means that you claim that

Bug#892360: systemd: No problem on my amd64 systems

On donderdag 8 maart 2018 20:49:54 CET Elimar Riesebieter wrote: > Well, I reported the initial reportfor x86 only, though. Correct. apt-listbug did show it for my amd64 system though and later on there were messages indicating that amd64 could also be affected. > > CONFIG_CGROUP_CPUACCT=y > As

Bug#888121: ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined method `yaml_as'

Hello, The issue below is caused by `ruby-delayed-job`. Find patch attached which fixes the problem. Regards On Tue, Jan 23, 2018 at 03:09:02PM +, Chris West (Faux) wrote: > Source: ruby-delayed-job-active-record > Version: 4.0.3-2 > Severity: important > User:

Bug#892462: python-mpop FTBFS and Debci failure: FAIL: test_boundaries_to_extent (mpop.tests.test_satin_helpers.TestSatinHelpers)

Source: python-mpop Version: 1.5.0-2 Severity: serious https://ci.debian.net/packages/p/python-mpop/unstable/amd64/ https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-mpop.html ... == FAIL:

Bug#889556: monotone: (Build-)Depends on obsolete libbotan1.10-dev

On 03/09/2018 10:32 AM, Jack Lloyd wrote: > 2.4.0 was just (in last week or so) packaged for buster - > https://packages.debian.org/buster/libbotan-2-4 oh, very nice. Looks like I searched only "stable". Thank you for the hint. Kind Regards Markus signature.asc Description: OpenPGP digital

Processed: affects 890751

Processing commands for cont...@bugs.debian.org: > affects 890751 src:ruby-minitest-shared-description Bug #890751 [src:rake] rake FTBFS with Ruby 2.5: cannot load such file -- ubygems (LoadError) Added indication that 890751 affects src:ruby-minitest-shared-description > thanks Stopping

Bug#889556: monotone: (Build-)Depends on obsolete libbotan1.10-dev

Hello Ondřej, On 02/04/2018 03:14 PM, Christian Hofstaedtler wrote: > your package monotone (build-)depends on botan1.10, which itself is > obsolete. Upstream will end security support at the end of 2018, so it > must not be part of buster. any plans on packaging Botan 2 for Debian? Otherwise I

Processed: affects 888121

Processing commands for cont...@bugs.debian.org: > affects 888121 src:ruby-delayed-job-active-record Bug #888121 [ruby-delayed-job] ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined method `yaml_as' Added indication that 888121 affects

Bug#883501: fixed in ktikz 0.12~kf5~git20180101-1

Hi, On Tue, 02 Jan 2018 09:05:14 + Stuart Prescott wrote: > ktikz (0.12~kf5~git20180101-1) experimental; urgency=medium > . >* New upstream git snapshot of the 'frameworks' branch for KF5 support > (Closes: #874996, #883501). >* Add qstring-ctor.patch to

Bug#892418: marked as done (lyx-common: Invalid python2 syntax)

Your message dated Fri, 09 Mar 2018 10:07:46 + with message-id and subject line Bug#892418: fixed in lyx 2.3.0-2 has caused the Debian Bug report #892418, regarding lyx-common: Invalid python2 syntax to be marked as done. This means that you claim that

Bug#892457: ruby-jquery-ui-rails FTBFS with Ruby 2.5

Source: ruby-jquery-ui-rails Version: 6.0.1+dfsg-2 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-jquery-ui-rails.html ... dh_ruby --build ln -s /usr/lib/nodejs/jquery-ui . rake rake aborted! SyntaxError:

Bug#892393: dewalls: build-depends on GCC 6

On 08/03/18 19:20, Wookey wrote: > On 2018-03-08 18:48 +0100, po...@debian.org wrote: >> Source: dewalls >> Severity: serious >> Tags: sid buster >> User: debian-...@lists.debian.org >> Usertags: gcc-6-rm >> >> Hi, >> >> dewalls build-depends on GCC 6. We now have GCC 7 (default) and GCC 8 >> in

Processed: reassign 888121 to ruby-delayed-job

Processing commands for cont...@bugs.debian.org: > reassign 888121 ruby-delayed-job Bug #888121 [src:ruby-delayed-job-active-record] ruby-delayed-job-active-record: FTBFS on ruby2.5: `method_missing': undefined method `yaml_as' Bug reassigned from package 'src:ruby-delayed-job-active-record' to

Bug#892382: devscripts: FTBFS in mipsel/mips64el: uscan_ftp test timeouts

On Sat, Mar 10, 2018 at 01:30:20AM +0900, Osamu Aoki wrote: > I don't see my patchies applied on salsa git repo. Yes they are. > I guess you are testing my old commit to alioth. I'm not _testing_ anything, this is with commit 77ecff2e9b18c74e8391aa0c8dccdd86a50544d5 that contains your changes

Bug#853527: lmms: ftbfs with GCC-7

X-Debbugs-CC: 073p...@gmail.com El dv 09 de 03 de 2018 a les 19:10 +0800, Boyuan Yang va escriure: > Are > you going to fix the problem soon? I cannot promise anything. > If not, is it okay if someone prepares an NMU and upload the fix? If master version still works, do not wait for me either.

Bug#853527: lmms: ftbfs with GCC-7

[Boyuan Yang] > Hi lmms maintainers, > > Several months have passed and I found this bug still not fixed. Are > you going to fix the problem soon? > > If not, is it okay if someone prepares an NMU and upload the fix? I'm on https://wiki.debian.org/LowThresholdNmu >, but am not the most active

Bug#892477: spf-milter-python: If connection is IPv6, milter says "Void lookup limit of 2 exceeded"

Package: spf-milter-python Version: 0.8.18-2 Severity: grave Tags: ipv6 Justification: causes non-serious data loss Dear Maintainer, I noted that when someone at mdh.se tries to send e-mail to us, and the connection is from an IPv6-address (almost all connections are these days),

Bug#892477: Acknowledgement (spf-milter-python: If connection is IPv6, milter says "Void lookup limit of 2 exceeded")

Please close this bug. It turned out that the domain mhd.se must have -records for the included 'a:' hostnames in DNS, which they didn't. And by using cloud-based e-mail they are using IPv6 without actually knowing it. $ host f-medby.ita.mdh.se f-medby.ita.mdh.se has address

Bug#892467: Acknowledgement (spfquery (libspf2-2?) and spf-milter-python falsely report "Void lookup limit exceeded")

Please close this bug. It turned out that the domain mhd.se must have -records for the included 'a:' hostnames in DNS, which they didn't. And by using cloud-based e-mail they are using IPv6 without actually knowing it. $ host f-medby.ita.mdh.se f-medby.ita.mdh.se has address

Bug#853527: lmms: ftbfs with GCC-7

[Boyuan Yang] > Hi lmms maintainers, > > Several months have passed and I found this bug still not fixed. Are > you going to fix the problem soon? > > If not, is it okay if someone prepares an NMU and upload the fix? I'm on https://wiki.debian.org/LowThresholdNmu >, but am not the most active

Processed: Re: Bug#892360: core: do not free stack-allocated strings

Processing control commands: > tags -1 patch Bug #892360 [systemd] systemd pid 1 freezes at startup on x86 systems Added tag(s) patch. -- 892360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#892360: core: do not free stack-allocated strings

Control: tags -1 patch Hi all, * Jindřich Makovička [2018-03-08 19:46 +]: > There is a fix in upstream master. > > https://github.com/systemd/systemd/pull/8391 I managed to build Debian's 238-1 with the attached patch included. I hereby confirm that those packages fix

Bug#892458: Security: please consider upgrade to 3.43(0)

On 2018-03-09 12:47, Adrian Bunk wrote: > Control: retitle -1 cfitsio: vulnerabilities > Control: found -1 3.370-2 > > On Fri, Mar 09, 2018 at 09:56:39AM +0100, Ole Streicher wrote: > > Package: cfitsio > > Version: 3.420-3 > > Severity: grave > > Tags: security > > > > Hi, > > > > a new

Processed: wcc: diff for NMU version 0.0.2+dfsg-2.1

Processing control commands: > tags 890043 + pending Bug #890043 [src:wcc] wcc's test dependencies cannot be fulfilled anymore Added tag(s) pending. -- 890043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#890043: wcc: diff for NMU version 0.0.2+dfsg-2.1

Control: tags 890043 + pending Dear maintainer, I've prepared an NMU for wcc (versioned as 0.0.2+dfsg-2.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should cancel it. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the

Processed: Re: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

Processing control commands: > tag -1 unreproducible moreinfo Bug #892290 [light-locker] light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect Added tag(s) moreinfo and unreproducible. -- 892290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892290

Bug#892290: [Pkg-xfce-devel] Bug#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

control: tag -1 unreproducible moreinfo On Wed, 2018-03-07 at 22:37 +0100, Stuart Pook wrote: > Dear Maintainer, > > Light-locker crashes when I unlock my session. This means that my session > is not locked the next time it should be, Hi, there was no recent update to light-locker. What did

Bug#892477: marked as done (spf-milter-python: If connection is IPv6, milter says "Void lookup limit of 2 exceeded")

Your message dated Fri, 09 Mar 2018 09:22:42 -0500 with message-id <12673837.a0SURGFqhx@kitterma-e6430> and subject line Re: Bug#892477: Acknowledgement (spf-milter-python: If connection is IPv6, milter says "Void lookup limit of 2 exceeded") has caused the Debian Bug report #892477, regarding

Bug#892484: ruby-pgplot: missing ruby2.5 build

Source: ruby-pgplot Version: 0.1.9-3 Severity: serious Justification: ruby2.5 will be the default ruby in buster Tags: buster sid Since ruby-pgplot depends on a package from non-free, it won't be rebuilt on the buildds. So ruby-pgplot needs to be manually rebuilt and uploaded by someone who cares

Bug#892371: [INFO] Bug#892371: proftpd-mod-vroot FTBFS with proftpd 1.3.6-1

On Thu, Mar 08, 2018 at 05:25:20PM +0200, Adrian Bunk wrote: Source: proftpd-mod-vroot Version: 0.9.4-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-vroot.html ... mod_vroot.c:1518:19: error: void value not ignored as it

Bug#892393: marked as done (dewalls: build-depends on GCC 6)

Your message dated Fri, 09 Mar 2018 15:05:39 + with message-id and subject line Bug#892393: fixed in dewalls 1.0.0+ds1-5 has caused the Debian Bug report #892393, regarding dewalls: build-depends on GCC 6 to be marked as done. This means that you claim

Bug#887323: marked as done (dewalls FTBFS on i386: test failures)

Your message dated Fri, 09 Mar 2018 15:05:39 + with message-id and subject line Bug#887323: fixed in dewalls 1.0.0+ds1-5 has caused the Debian Bug report #887323, regarding dewalls FTBFS on i386: test failures to be marked as done. This means that you

Bug#892488: pcre2: FTBFS on mips* - test failures

Source: pcre2 Version: 10.31-1 Severity: serious Tags: sid buster Forwarded: https://bugs.exim.org/show_bug.cgi?id=2254 Hi, pcre2 FTBFS on mips* with lots of testsuite failures. It looks to me like the JIT is bust. I forwarded the log upstream to the above address. I'll try to take a look at

Processed: The generated dependency should be fine when the FTBFS is fixed

Processing commands for cont...@bugs.debian.org: > reassign 883641 src:php-phpdocumentor-reflection Bug #883641 [php-phpdocumentor-reflection] php-phpdocumentor-reflection: uninstallable in sid: Depends: php-parser (< 2~~) but 3.1.2-2 is to be installed Bug reassigned from package

Bug#892373: [INFO] Bug#892373: proftpd-mod-fsync FTBFS with proftpd 1.3.6-1

On Thu, Mar 08, 2018 at 05:28:49PM +0200, Adrian Bunk wrote: Source: proftpd-mod-fsync Version: 0.2-1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-fsync.html ... mod_fsync.c:184:10: error: implicit declaration of function

Bug#892488: pcre2: FTBFS on mips* - test failures

Hi, On 09/03/18 15:20, James Cowgill wrote: Source: pcre2 Version: 10.31-1 Severity: serious Tags: sid buster Forwarded: https://bugs.exim.org/show_bug.cgi?id=2254 Hi, pcre2 FTBFS on mips* with lots of testsuite failures. It looks to me like the JIT is bust. I forwarded the log upstream to

Bug#892494: diceware: "diceware" name violates trademark

Source: diceware Severity: serious Tags: upstream Justification: Policy 2.1 As stated in the footer of http://world.std.com/%7Ereinhold/diceware.html the original creator of diceware claims a trademark on the name. I've filed a bug with upstream here: https://github.com/ulif/diceware/issues/48

Processed: Move to the package where it was fixed

Processing commands for cont...@bugs.debian.org: > reassign 889100 libpixelif-common 0.8.4-2 Bug #889100 {Done: Christoph Ender } [fizmo-sdl2] fizmo-sdl2: Segfaults on start-up Bug reassigned from package 'fizmo-sdl2' to 'libpixelif-common'. No longer marked as

Bug#892382: devscripts: FTBFS in mipsel/mips64el: uscan_ftp test timeouts

Hi, On Thu, Mar 08, 2018 at 05:22:40PM +0100, Mattia Rizzolo wrote: > Source: devscripts > Version: 2.18.1 > Severity: serious > X-Debbugs-Cc: Osamu Aoki > > Hi Osamu-san :) > > the new uscan_ftp tests seems to misbehave on mipsel/mips64el. > Just to mention one: > >

Bug#892372: [INFO] Bug#892372: proftpd-mod-msg FTBFS with proftpd 1.3.6-1

On Thu, Mar 08, 2018 at 05:27:10PM +0200, Adrian Bunk wrote: Source: proftpd-mod-msg Version: 0.4.1-1.1 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-msg.html ... mod_msg.c:56:3: error: #error "mod_msg requires Controls

Bug#892468: proftp: Prevent migration to testing

On Fri, Mar 09, 2018 at 12:13:55PM +0100, Hilmar Preuße wrote: Package: proftpd-basic Version: 1.3.6-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, for now we want to prevent the package from migrating to testing until we are sure all bugs are fixed. For now

Bug#887323: dewalls i386 test failure

A bit of research tells that using 'long double' causes 80-bit fp on x86 (i386 and amd64), as opposed to the 64-bit IEE 754 fp representation used on other platforms, which is what you get if you specify double. So I tried changing the angle.{cpp.h} code to use double instead of long double.