Bug#889140: Bug#901800: python-gevent: diff for NMU version 1.3.4-0.1

Le mercredi 11 juillet 2018 à 07:31:55+0200, László Böszörményi (GCS) a écrit : > This is my bad, should sleep more. You know, recently I learnt people > import my package to Salsa, make changes, upload it _under my name_. > When its build broke, he pointed fingers on me that I'm the maintainer >

Processed: tagging 856948

Processing commands for cont...@bugs.debian.org: > tags 856948 = pending Bug #856948 [kmldonkey] kmldonkey: Segfault starting Added tag(s) pending; removed tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 856948:

Bug#889140: Bug#901800: python-gevent: diff for NMU version 1.3.4-0.1

On Wed, Jul 11, 2018 at 12:10 AM Pierre-Elliott Bécue wrote: > Le 10 juillet 2018 23:54:31 GMT+02:00, "László Böszörményi (GCS)" > a écrit : > > I do not get your point, what's funny in that you committed even more > >to the repository without asking. But read on. > This is my repository in my

Bug#903492: Runtime error "PMIX-XFER-VALUE: UNSUPPORTED TYPE 28016"

On Tue, 10 Jul 2018 19:57:57 +0200 Anton Gladky > > it looks like the version 3.1.1.real-1 introduces the regression in autopkgtest. > Not just the autopkgtest, it's fouling up petsc and dolfin too ;(

Processed: Re: Bug#903530: pyresample FTBFS with Python 3.7 as supported version

Processing commands for cont...@bugs.debian.org: > notfound 903530 pyresample/1.9.3-2 Bug #903530 [src:pyresample] pyresample FTBFS with Python 3.7 as supported version No longer marked as found in versions pyresample/1.9.3-2. > severity 903530 important Bug #903530 [src:pyresample] pyresample

Bug#860064: This problem starts to get serios

I have both. Currently I have problems only on Jessie On 10.07.18 16:45, Christoph Martin wrote: Are your servers Jessie or Stretch ? Am 10. Juli 2018 15:42:00 MESZ schrieb Anton Avramov : My servers stops working all around the country because of this problem, since they autoupdate

Bug#901731: marked as done (ipmiutil: Attempts to enable/start services named like ipmiutil.ipmiutil*.service without shipping them)

Your message dated Wed, 11 Jul 2018 00:48:56 + with message-id and subject line Bug#901731: fixed in ipmiutil 3.1.1-1 has caused the Debian Bug report #901731, regarding ipmiutil: Attempts to enable/start services named like ipmiutil.ipmiutil*.service without shipping them to be marked as

Bug#901562: invesalius is marked for autoremoval from testing

Hi Andreas, I think the easiest way to fix this bug is to package the git version. Also, the git version is already working with Python3. What do you think? Best regards. On Tue, Jul 10, 2018 at 3:27 AM Andreas Tille wrote: > > Hi Thiago, > > any news about this? Note that bug #901377 is fixed

Bug#902788: python3-minimal needs Breaks for software/modules broken by 3.7

Hello, I see that this issue block a lot of package installation. Do you think that we should update the python3-defaults [1]? Actually is 3.6.* version. If not, what is the possible solution? [1] https://tracker.debian.org/pkg/python3-defaults Thanks! Regards! -- Arias Emmanuel

Bug#903493: marked as done (hobbit-plugins: libfile-slurp-perl only in Suggests, but used by the libs check which is enabled by default)

Your message dated Wed, 11 Jul 2018 00:18:55 + with message-id and subject line Bug#903493: fixed in hobbit-plugins 20180711 has caused the Debian Bug report #903493, regarding hobbit-plugins: libfile-slurp-perl only in Suggests, but used by the libs check which is enabled by default to be

Bug#903520: marked as done (libext2fs-dev: ext2fs/ext2fs.h includes nonexisting hashmap.h)

Your message dated Tue, 10 Jul 2018 19:07:32 -0400 with message-id <20180710230732.gc9...@thunk.org> and subject line Re: Bug#903520: libext2fs-dev: ext2fs/ext2fs.h includes nonexisting hashmap.h has caused the Debian Bug report #903520, regarding libext2fs-dev: ext2fs/ext2fs.h includes

Processed: tagging 903533

Processing commands for cont...@bugs.debian.org: > tags 903533 + ftbfs Bug #903533 [src:yapf] yapf FTBFS with Python 3.7 as supported version Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 903533:

Bug#903533: yapf FTBFS with Python 3.7 as supported version

Source: yapf Version: 0.22.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/yapf.html ... I: pybuild base:217: cd /build/1st/yapf-0.22.0/.pybuild/cpython3_3.7_yapf/build; python3.7 -m nose

Bug#888423: firefox: FF 58.0 segfaults each 1-2 minute

On Thu, 25 Jan 2018 15:25:32 +0300 "Dmitry E. Oboukhov" wrote: > gdb /usr/bin/firefox core Hi, I'm also seeing frequent crashes in firefox (62), and I just want to ask - how do you make core files/backtraces from firefox crashes? I always get the option to report to mozilla, restore tabs etc.

Processed: tagging 903493

Processing commands for cont...@bugs.debian.org: > tags 903493 + pending Bug #903493 [hobbit-plugins] hobbit-plugins: libfile-slurp-perl only in Suggests, but used by the libs check which is enabled by default Added tag(s) pending. > thanks Stopping processing here. Please contact me if you

Bug#881765: marked as done (yapf3: uninstallable in jessie-backports)

Your message dated Wed, 11 Jul 2018 02:28:36 +0300 with message-id <20180710232836.GE32281@localhost> and subject line Fixed in 0.15.1-1~bpo8+1.1 has caused the Debian Bug report #881765, regarding yapf3: uninstallable in jessie-backports to be marked as done. This means that you claim that the

Bug#903531: python-ruffus FTBFS with Python 3.7 as supported version

Source: python-ruffus Version: 2.6.3+dfsg-5 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-ruffus.html ... I: pybuild base:217: python3.7 setup.py clean Traceback (most recent call last): File "setup.py", line 12, in import

Bug#903530: pyresample FTBFS with Python 3.7 as supported version

Source: pyresample Version: 1.9.3-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyresample.html ... creating build/temp.linux-amd64-3.7 creating build/temp.linux-amd64-3.7/pyresample creating build/temp.linux-amd64-3.7/pyresample/ewa

Bug#901800: marked as done (python-gevent: (Build-)Depends on cruft packages python-greenlet-dbg python3-greenlet-dbg)

Your message dated Tue, 10 Jul 2018 22:35:52 + with message-id and subject line Bug#901800: fixed in python-gevent 1.3.4-1 has caused the Debian Bug report #901800, regarding python-gevent: (Build-)Depends on cruft packages python-greenlet-dbg python3-greenlet-dbg to be marked as done. This

Bug#903145: marked as done (python3-gevent: Package fails to install in a Python3.7 environment)

Your message dated Tue, 10 Jul 2018 22:35:52 + with message-id and subject line Bug#903145: fixed in python-gevent 1.3.4-1 has caused the Debian Bug report #903145, regarding python3-gevent: Package fails to install in a Python3.7 environment to be marked as done. This means that you claim

Processed: python3-ws4py fails to install with Python 3.7 as supported version

Processing control commands: > block 902788 by -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903526 903527 902757 903030 902761 903528 902989 903423 902631 903522 902650 903388 902646 903457 902900 903016 902766 903525 903145

Bug#903529: python3-ws4py fails to install with Python 3.7 as supported version

Package: python3-ws4py Version: 0.4.2+dfsg1-2 Severity: grave Control: block 902788 by -1 Setting up python3-ws4py (0.4.2+dfsg1-2) ... File "/usr/lib/python3/dist-packages/ws4py/async_websocket.py", line 87 asyncio.async(closeit()) ^ SyntaxError: invalid syntax File

Bug#903457: marked as done (python3-gevent: Package fails to install in a Python3.7 environment)

Your message dated Tue, 10 Jul 2018 22:35:52 + with message-id and subject line Bug#903145: fixed in python-gevent 1.3.4-1 has caused the Debian Bug report #903145, regarding python3-gevent: Package fails to install in a Python3.7 environment to be marked as done. This means that you claim

Bug#889140: marked as done (python-gevent: FTBFS with Sphinx 1.6.6: maximum recursion depth exceeded while calling a Python object)

Your message dated Tue, 10 Jul 2018 22:35:52 + with message-id and subject line Bug#889140: fixed in python-gevent 1.3.4-1 has caused the Debian Bug report #889140, regarding python-gevent: FTBFS with Sphinx 1.6.6: maximum recursion depth exceeded while calling a Python object to be marked

Bug#903520: marked as done (libext2fs-dev: ext2fs/ext2fs.h includes nonexisting hashmap.h)

Your message dated Wed, 11 Jul 2018 01:32:07 +0300 with message-id <20180710223207.GD32281@localhost> and subject line Fixed in 1.44.3-1 has caused the Debian Bug report #903520, regarding libext2fs-dev: ext2fs/ext2fs.h includes nonexisting hashmap.h to be marked as done. This means that you

Bug#903528: python3-seqdiag fails to install with Python 3.7 as supported version

Package: python3-seqdiag Version: 0.9.5+dfsg-1 Severity: grave Control: block 902788 by -1 Setting up python3-seqdiag (0.9.5+dfsg-1) ... File "/usr/lib/python3/dist-packages/seqdiag/drawer.py", line 106 if edge.async: ^ SyntaxError: invalid syntax File

Processed: python3-seqdiag fails to install with Python 3.7 as supported version

Processing control commands: > block 902788 by -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903388 903525 903030 903031 902715 903457 903016 902650 902766 903527 902900 902757 902989 903145 903526 902761 902631 903218 903522

Processed: python3-motor fails to install with Python 3.7 as suported version

Processing control commands: > block 902788 by -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903218 902761 902766 903145 902989 903457 902715 903526 902757 902650 903522 902646 903423 902794 902631 903016 902900 903525 903030

Bug#903527: python3-motor fails to install with Python 3.7 as suported version

Package: python3-motor Version: 1.2.3-1 Severity: grave Control: block 902788 by -1 Setting up python3-motor (1.2.3-1) ... File "/usr/lib/python3/dist-packages/motor/frameworks/asyncio/__init__.py", line 32 from asyncio import async as ensure_future ^

Processed: python3-jira fails to install with Python 3.7 as supported version

Processing control commands: > block 902788 by -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902989 902900 902794 902631 903457 902650 902761 903525 903145 903423 903522 902757 903388 902646 903030 903218 903031 902715 903016

Bug#903526: python3-jira fails to install with Python 3.7 as supported version

Package: python3-jira Version: 1.0.10-1 Severity: grave Control: block 902788 by -1 Setting up python3-jira (1.0.10-1) ... File "/usr/lib/python3/dist-packages/jira/client.py", line 199 validate=False, get_server_info=True, async=False, logging=True, max_retries=3, proxies=None,

Bug#903525: python3-dropbox fails to install with Python 3.7 as supported version

Package: python3-dropbox Version: 8.7.1-1 Severity: grave Control: block 902788 by -1 Setting up python3-dropbox (8.7.1-1) ... File "/usr/lib/python3/dist-packages/dropbox/base.py", line 10 async, ^ SyntaxError: invalid syntax File

Processed: python3-dropbox fails to install with Python 3.7 as supported version

Processing control commands: > block 902788 by -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902715 902761 903031 903457 903218 902989 902900 903423 903522 903030 902766 902794 902757 903016 903145 902650 902631 902646 903388

Bug#901800: Bug#889140: Bug#901800: python-gevent: diff for NMU version 1.3.4-0.1

Le 10 juillet 2018 23:54:31 GMT+02:00, "László Böszörményi (GCS)" a écrit : >Hi, > >On Mon, Jul 9, 2018 at 2:12 PM Pierre-Elliott Bécue >wrote: >> Le dimanche 08 juillet 2018 à 19:35:13+0200, László Böszörményi (GCS) >a écrit : >> > On Sun, Jul 8, 2018 at 5:51 PM Pierre-Elliott Bécue > wrote:

Bug#889140: Bug#901800: python-gevent: diff for NMU version 1.3.4-0.1

Hi, On Mon, Jul 9, 2018 at 2:12 PM Pierre-Elliott Bécue wrote: > Le dimanche 08 juillet 2018 à 19:35:13+0200, László Böszörményi (GCS) a écrit > : > > On Sun, Jul 8, 2018 at 5:51 PM Pierre-Elliott Bécue wrote: > > > I've prepared an NMU for python-gevent (versioned as 1.3.4-0.1), to fix > > >

Bug#903524: manuel FTBFS with Python 3.7 as supported version

Source: manuel Version: 1.8.0-5 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/manuel.html ... I: pybuild base:217: python3.7 setup.py test ... == FAIL:

Bug#903523: jaraco.itertools FTBFS with Python 3.7 as supported version

Source: jaraco.itertools Version: 2.0.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jaraco.itertools.html ... I: pybuild base:217: cd /build/1st/jaraco.itertools-2.0.1/.pybuild/cpython3_3.7_jaraco.itertools/build; python3.7 -m pytest

Processed: block 902788 with 903031 903030

Processing commands for cont...@bugs.debian.org: > block 902788 with 903031 903030 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902794 903388 903218 903457 902900 902766 903016 903522 902989 902761 902757 902650 902715 902646

Bug#903522: python3-django-q fails to install with Python 3.7 as supported version

Package: python3-django-q Version: 0.9.4-1 Severity: grave Control: block 902788 by -1 Setting up python3-django-q (0.9.4-1) ... File "/usr/lib/python3/dist-packages/django_q/__init__.py", line 15 from .tasks import async, schedule, result, result_group, fetch, fetch_group, count_group,

Processed: python3-django-q fails to install with Python 3.7 as supported version

Processing control commands: > block 902788 by -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902715 902900 903423 903016 902757 902794 903457 903145 902631 902989 902646 903218 903388 902650 902766 902761 902788 was blocking:

Bug#903520: libext2fs-dev: ext2fs/ext2fs.h includes nonexisting hashmap.h

Package: libext2fs-dev Version: 1.44.3~rc2-1 Severity: grave Dear Maintainer, In the latest packaged version of libext2fs-dev, the file /usr/include/ext2fs/ext2fs.h contains a line , | #include "hashmap.h" ` This file does not exist, leading build failures of software that wants to

Bug#903514: gimp: completely broken

On Tue, 2018-07-10 at 17:20 -0400, Jeremy Bicha wrote: > I don't know. It works fine here. Could you try to be more specific > about *when* things stopped working? I'm afraid I have no idea... I noticed it a week ago, which doesn't mean though, that it wasn't introduced earlier. Wasn't there

Bug#903118: marked as done (rustc: FTBFS in stretch (no cargo executable found))

Your message dated Tue, 10 Jul 2018 21:32:11 + with message-id and subject line Bug#903118: fixed in rustc 1.24.1+dfsg1-1~deb9u2 has caused the Debian Bug report #903118, regarding rustc: FTBFS in stretch (no cargo executable found) to be marked as done. This means that you claim that the

Bug#903519: backblaze-b2 FTBFS with Python 3.7 as supported version

Source: backblaze-b2 Version: 1.1.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/backblaze-b2.html ... I: pybuild base:217: python3.7 setup.py nosetests ... == ERROR:

Bug#903514: gimp: completely broken

On Tue, Jul 10, 2018 at 4:59 PM, Christoph Anton Mitterer wrote: > Since some time the GIMP is completely broken. I don't know. It works fine here. Could you try to be more specific about *when* things stopped working? > GIMP-Error: Unable to run plug-in "plugin-uncrop.py" >

Bug#903514: gimp: completely broken

Package: gimp Version: 2.10.2-1 Severity: grave Justification: renders package unusable Hi. Since some time the GIMP is completely broken. In most cases it does not even start (e.g. when invoking it from another program) or when: $ gimp or $ gimp 0.jpg (with 0.jpg not existing) it simply hangs

Processed: FTBFS are RC

Processing commands for cont...@bugs.debian.org: > severity 889649 serious Bug #889649 [src:iptables] FTBFS with debhelper 10 Bug #903365 [src:iptables] iptables: FTBFS in buster/sid (dh_installman: Cannot find "debian/nfnl_osf.8") Severity set to 'serious' from 'normal' Severity set to

Bug#860064: This problem starts to get serios

Are your servers Jessie or Stretch ? Am 10. Juli 2018 15:42:00 MESZ schrieb Anton Avramov : >My servers stops working all around the country because of this >problem, >since they autoupdate themselves > >Can the LTS team fix this? > >-- >Антон Аврамов /Anton Avramov/ > >Луканет ООД /Lukanet

Bug#903160: marked as done (thunderbird: Thunderbird 52.9.0-1 can cause non-critical data loss)

Your message dated Tue, 10 Jul 2018 20:42:39 + with message-id and subject line Bug#903160: fixed in thunderbird 1:52.9.1-1 has caused the Debian Bug report #903160, regarding thunderbird: Thunderbird 52.9.0-1 can cause non-critical data loss to be marked as done. This means that you claim

Processed: tagging 903448

Processing commands for cont...@bugs.debian.org: > tags 903448 + buster sid Bug #903448 [ruby-websocket-parser,ruby-websocket] ruby-websocket-parser,ruby-websocket: error when trying to install together Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you

Bug#902199: marked as done (python-numpy FTBFS on s390x: numpy.core.tests.test_umath.TestComplexFunctions.test_against_cmath ... Segmentation fault)

Your message dated Tue, 10 Jul 2018 23:18:09 +0300 with message-id <20180710201809.GB32281@localhost> and subject line python-numpy did now build on s390x has caused the Debian Bug report #902199, regarding python-numpy FTBFS on s390x:

Processed: tagging 903381

Processing commands for cont...@bugs.debian.org: > tags 903381 + buster Bug #903381 {Done: Graham Inggs } [src:utf8proc] utf8proc: FTBFS with unicode-data 11 Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 903381:

Processed: tagging 903379

Processing commands for cont...@bugs.debian.org: > tags 903379 + buster Bug #903379 {Done: Jeremy Bicha } [src:gucharmap] gucharmap: FTBFS with unicode-data 11 Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 903379:

Bug#902117:

Here's what I've learned: Adding this logging subsystem to corosync.conf allows the output to the terminal, which is what I originally expected. logger_subsys { subsys: QDEVICE debug: on to_stderr: yes } However, I was still

Processed: Re: Bug#903457:

Processing commands for cont...@bugs.debian.org: > forcemerge 903145 903457 Bug #903145 [python3-gevent] python3-gevent: Package fails to install in a Python3.7 environment Bug #903457 [python3-gevent] python3-gevent: Package fails to install in a Python3.7 environment 902788 was blocked by:

Bug#903457:

forcemerge 903145 903457 thanks On Tue, 2018-07-10 at 10:57 +0200, Michal Arbet wrote: > When package is installing , these errors appears below .. : [...] > These is caused because of python 3.7 where async is reserved > python3.7 keyword. > Please , could you fix and upload new revision ?

Processed (with 1 error): Re: Bug#903457:

Processing control commands: > retitle -1 python3-gevent: Package fails to install in a Python3.7 environment Bug #903457 [python3-gevent] (no subject) Set Bug title to 'python3-gevent: Package fails to install in a Python3.7 environment'. > severity -1 grave Bug #903457 [python3-gevent]

Bug#903498: libjulia0.6: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/julia/libccalltest.so

Package: libjulia0.6 Version: 0.6.3-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other

Bug#903493: [Xymon] Debian buster: Task libs terminated, status 2

Package: hobbit-plugins Version: 20180610 Severity: serious Control: submitter -1 Jaap Winius Control: retitle -1 hobbit-plugins: libfile-slurp-perl only in Suggests, but used by the libs check which is enabled by default Justification: Maintainer's opinion Hi Jaap, On Tue, Jul 10, 2018 at

Processed: Re: [Xymon] Debian buster: Task libs terminated, status 2

Processing control commands: > submitter -1 Jaap Winius Bug #903493 [hobbit-plugins] [Xymon] Debian buster: Task libs terminated, status 2 Changed Bug submitter to 'Jaap Winius ' from 'Axel Beckert '. > retitle -1 hobbit-plugins: libfile-slurp-perl only in Suggests, but used by > the libs

Bug#903492: Runtime error "PMIX-XFER-VALUE: UNSUPPORTED TYPE 28016"

Source: openmpi Version: 3.1.1.real-1 Severity: serious Dear maintainer, it looks like the version 3.1.1.real-1 introduces the regression in autopkgtest. We are preparing some set of autopkgtests for the boost libraries (not in the package yet) [1]. And the MPI-autopkgtests are failing, when

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

Alexis Murzeau writes: > Hi, > > Le 27/06/2018 à 00:21, Alexis Murzeau a écrit : >> Le 26/06/2018 à 04:13, vasudev-debian a écrit : >>> I'll have a look. if possible clone from team repo and raise a pr on it. >>> >> >> I've created 3 PR at [0], one for each branch (in this order: upstream, >>

Bug#903456: marked as done (libbio-tools-phylo-paml-perl: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/man/man3/Bio::Tools::Phylo::PAML.3pm.gz)

Your message dated Tue, 10 Jul 2018 15:04:28 + with message-id and subject line Bug#903456: fixed in libbio-tools-phylo-paml-perl 1.7.3-2 has caused the Debian Bug report #903456, regarding libbio-tools-phylo-paml-perl: fails to upgrade from 'stable' to 'sid' - trying to overwrite

Bug#903077: marked as done (r10k FTBFS: update Build-Depends: ruby-ronn -> ronn)

Your message dated Tue, 10 Jul 2018 14:45:05 + with message-id and subject line Bug#903077: fixed in r10k 2.6.3-1 has caused the Debian Bug report #903077, regarding r10k FTBFS: update Build-Depends: ruby-ronn -> ronn to be marked as done. This means that you claim that the problem has been

Bug#903195: marked as done (libsass-python FTBFS with new libsass)

Your message dated Tue, 10 Jul 2018 14:42:00 + with message-id and subject line Bug#903195: fixed in libsass-python 0.14.5-1 has caused the Debian Bug report #903195, regarding libsass-python FTBFS with new libsass to be marked as done. This means that you claim that the problem has been

Processed: found 888555 in 1:6.0-41, notfound 903448 in ruby-1.2.5-1, found 903448 in 1.2.5-1

Processing commands for cont...@bugs.debian.org: > found 888555 1:6.0-41 Bug #888555 [clang-tools] clang-tools: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/clang-apply-replacements.1.gz Marked as found in versions llvm-defaults/0.41. > notfound 903448 ruby-1.2.5-1 Bug

Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)

Can verify,  this bug is kernel independent. On Tue, 10 Jul 2018 12:15:51 +0200 Vincent Gatignol wrote: > hi there, > > running  4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 > GNU/Linux and having this issue too > > not specifically related to the 4.16 versions > > >

Bug#862884: Please upload

As a result of this patch not being applied, I couldn't connect my laptop to my employer's VPN (because I run testing, and this package isn't available in testing). Applying the patch and building it locally worked fine.

Bug#860064: This problem starts to get serios

My servers stops working all around the country because of this problem, since they autoupdate themselves Can the LTS team fix this? -- Антон Аврамов /Anton Avramov/ Луканет ООД /Lukanet Ltd/ София, България /Sofia, Bulgaria/ ул. Никола Габровски 108 /108 Nikola Gabrovski str./ tel. +359 2

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 889649 src:iptables Bug #889649 [iptables] FTBFS with debhelper 10 Bug reassigned from package 'iptables' to 'src:iptables'. No longer marked as found in versions iptables/1.6.2-1. Ignoring request to alter fixed versions of bug #889649

Processed: tagging 891901

Processing commands for cont...@bugs.debian.org: > tags 891901 - a11y Bug #891901 [arduino] arduino: Doesn't open. Removed tag(s) a11y. > thanks Stopping processing here. Please contact me if you need assistance. -- 891901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891901 Debian Bug

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 903365 889649 Bug #903365 [src:iptables] iptables: FTBFS in buster/sid (dh_installman: Cannot find "debian/nfnl_osf.8") Unable to merge bugs because: package of #889649 is 'iptables' not 'src:iptables' Failed to forcibly merge 903365:

Bug#899506: marked as done (fcitx-sunpinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

Your message dated Tue, 10 Jul 2018 13:04:13 + with message-id and subject line Bug#899506: fixed in fcitx-sunpinyin 0.4.2-2 has caused the Debian Bug report #899506, regarding fcitx-sunpinyin: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org to be marked as done. This means

Processed (with 1 error): merge bugs #889649 and #903365

Processing commands for cont...@bugs.debian.org: > merge 903365 889649 Bug #903365 [src:iptables] iptables: FTBFS in buster/sid (dh_installman: Cannot find "debian/nfnl_osf.8") Unable to merge bugs because: severity of #889649 is 'normal' not 'serious' package of #889649 is 'iptables' not

Bug#902658: apache2: apachectl graceful/restart results in segfault

I have the same problem with the same Debian and Apache2 version (upgrade testing/buster 2018/07/07): /var/log/kern.log: Jul 9 18:25:28 eussa kernel: [12436.633037] /usr/sbin/apach[12386]: segfault at 7f5c82d98660 ip 7f5c82d98660 sp 7ffcfaf711f8 error 14 in

Bug#900623: marked as done (missing dependency on cl-unicode)

Your message dated Tue, 10 Jul 2018 12:34:09 + with message-id and subject line Bug#900623: fixed in cl-interpol 20171227-2 has caused the Debian Bug report #900623, regarding missing dependency on cl-unicode to be marked as done. This means that you claim that the problem has been dealt

Bug#900300: nvidia-cuda-toolkit: depends on openjdk-8

anti-AUTORM-ping while we have 9.2 in experimental, testing it is blocked by the required drivers still sitting in NEW Andreas

Bug#902961: marked as done (mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests)

Your message dated Tue, 10 Jul 2018 12:21:58 + with message-id and subject line Bug#902961: fixed in mozjs52 52.3.1-9 has caused the Debian Bug report #902961, regarding mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests to be marked as done. This means

Bug#902197: marked as done (mozjs52 FTBFS with icu 60.2)

Your message dated Tue, 10 Jul 2018 12:21:58 + with message-id and subject line Bug#902197: fixed in mozjs52 52.3.1-9 has caused the Debian Bug report #902197, regarding mozjs52 FTBFS with icu 60.2 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#903195: libsass-python FTBFS with new libsass

Thanks Peter for letting know about that! I prepared an upload to fix this with a libsass-python in sync with libsass 3.5.4 . F. On Sat, 7 Jul 2018 12:49:41 +0100, peter green wrote: > Package: libsass-python > Severity: serious > Version: 0.13.4-1 > > A new version of libsass was recently

Bug#901556: marked as done (enigmail contains unbuildable artifacts)

Your message dated Tue, 10 Jul 2018 11:49:15 + with message-id and subject line Bug#901556: fixed in enigmail 2:2.0.7+ds1-1 has caused the Debian Bug report #901556, regarding enigmail contains unbuildable artifacts to be marked as done. This means that you claim that the problem has been

Processed: closing 903245

Processing commands for cont...@bugs.debian.org: > close 903245 2.04-2 Bug #903245 [pgbackrest] pgbackrest: FTBFS everywhere: keys at index 8 do not match Marked as fixed in versions pgbackrest/2.04-2. Bug #903245 [pgbackrest] pgbackrest: FTBFS everywhere: keys at index 8 do not match Marked

Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)

hi there, running  4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux and having this issue too not specifically related to the 4.16 versions Regards

Processed: affects 903414

Processing commands for cont...@bugs.debian.org: > affects 903414 src:libdazzle Bug #903414 [meson] libdazzle: FTBFS in buster/sid (dh_install: Cannot find "usr/share/gtk-doc" (tried in ., debian/tmp)) Added indication that 903414 affects src:libdazzle > thanks Stopping processing here. Please

Processed: Bug #902961 in mozjs52 marked as pending

Processing control commands: > tag -1 pending Bug #902961 [src:mozjs52] mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests Ignoring request to alter tags of bug #902961 to the same tags previously set -- 902961:

Bug#902961: mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests

Control: tags -1 = ftbfs patch pending On Wed, 04 Jul 2018 at 00:51:05 +0100, Simon McVittie wrote: > Running it under gdb reveals that this is because > ReserveProcessExecutableMemory() in js/src/jit/ProcessExecutableMemory.cpp > fails during startup, causing JS_Init() to fail. On closer

Processed: Re: Bug#902961: mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests

Processing control commands: > tags -1 = ftbfs patch pending Bug #902961 [src:mozjs52] mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests Added tag(s) patch and pending; removed tag(s) help. -- 902961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902961

Bug#902961: Bug #902961 in mozjs52 marked as pending

Control: tag -1 pending Hello, Bug #902961 in mozjs52 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#883615: Who is this

What did I buy

Bug#903456: libbio-tools-phylo-paml-perl: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/man/man3/Bio::Tools::Phylo::PAML.3pm.gz

Package: libbio-tools-phylo-paml-perl Version: 1.7.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to

Bug#902897: virtualbox: #metoo

Package: virtualbox Version: 5.2.14-dfsg-1 Followup-For: Bug #902897 I hit this but after upgrading the kernel from 4.9 to 4.16. Before that, I think vbox 5.2.14 worked for me OK. -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500,

Bug#903455: menhir-doc: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/share/doc/menhir/examples/Makefile

Package: menhir-doc Version: 20180530-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other

Bug#902463: marked as done (flask-script: FTBFS in buster/sid (failing tests))

Your message dated Tue, 10 Jul 2018 08:49:17 + with message-id and subject line Bug#902463: fixed in flask-script 2.0.6-1 has caused the Debian Bug report #902463, regarding flask-script: FTBFS in buster/sid (failing tests) to be marked as done. This means that you claim that the problem has

Bug#903454: fcitx-bin: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/fcitx4-config

Package: fcitx-bin Version: 1:4.2.9.6-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails because it tries to overwrite

Bug#903423: marked as done (python-autobahn: Fails to install with python 3.7)

Your message dated Tue, 10 Jul 2018 08:38:16 + with message-id and subject line Bug#903423: fixed in python-autobahn 17.10.1+dfsg1-3 has caused the Debian Bug report #903423, regarding python-autobahn: Fails to install with python 3.7 to be marked as done. This means that you claim that the

Bug#903453: atheme-services-contrib: fails to upgrade from 'stretch' - trying to overwrite /usr/share/atheme/help/contrib/access

Package: atheme-services-contrib Version: 7.2.9-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails because it tries to

Processed: Bug #902463 in flask-script marked as pending

Processing control commands: > tag -1 pending Bug #902463 [src:flask-script] flask-script: FTBFS in buster/sid (failing tests) Added tag(s) pending. -- 902463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#903414: libdazzle: FTBFS in buster/sid (dh_install: Cannot find "usr/share/gtk-doc" (tried in ., debian/tmp))

Control: reassign 903414 meson 0.47.0-1 Control: forwarded 903414 https://github.com/mesonbuild/meson/issues/3829 Control: tags 903414 + fixed-upstream patch On Mon, 09 Jul 2018 at 17:25:46 +, Santiago Vila wrote: > dh_install: Cannot find (any matches for) "usr/share/gtk-doc" (tried in ., >

Processed: Re: Bug#903414: libdazzle: FTBFS in buster/sid (dh_install: Cannot find "usr/share/gtk-doc" (tried in ., debian/tmp))

Processing control commands: > reassign 903414 meson 0.47.0-1 Bug #903414 [src:libdazzle] libdazzle: FTBFS in buster/sid (dh_install: Cannot find "usr/share/gtk-doc" (tried in ., debian/tmp)) Bug reassigned from package 'src:libdazzle' to 'meson'. No longer marked as found in versions

Bug#902463: Bug #902463 in flask-script marked as pending

Control: tag -1 pending Hello, Bug #902463 in flask-script 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:

  1   2   >