Your message dated Sat, 24 Jun 2017 03:49:35 +
with message-id
and subject line Bug#865706: fixed in haskell-http-link-header 1.0.3-2
has caused the Debian Bug report #865706,
regarding haskell-http-link-header: FTBFS everywhere (except all)
to be marked as done.
This means that you claim tha
Source: ocaml
Version: 4.04.0-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://caml.inria.fr/mantis/view.php?id=7557
Hi,
the following vulnerability was published for ocaml.
CVE-2017-9772[0]:
| Insufficient sanitisation in the OCaml compiler versions
Source: haskell-yaml
Version: 0.8.23-2
Severity: serious
Hi,
haskell-yaml FTBFS on every architecture (except all) due to testsuite
failures:
> Failures:
>
> test/Data/YamlSpec.hs:440:
> 1) Data.Yaml.Data.Yaml encode invalid numbers
>expected: ".\n"
> but got: ".\n...\n"
>
>
Control: tag -1 + unreproducible
Control: severity -1 important
On Fri, Jun 23, 2017 at 06:36:37PM +0300, Adrian Bunk wrote:
> Source: ruby-prof
> Version: 0.16.2+dfsg-2
> Severity: serious
> Tags: buster sid
>
> Some recent change in unstable makes ruby-prof FTBFS:
>
> https://tests.reproducibl
Processing control commands:
> tag -1 + unreproducible
Bug #865667 [src:ruby-prof] ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.
Added tag(s) unreproducible.
> severity -1 important
Bug #865667 [src:ruby-prof] ruby-prof FTBFS: ERROR: Test "ruby2.3" failed.
Severity set to 'important' from 'seriou
Processing control commands:
> severity -1 important
Bug #865675 [src:libyaml] yaml: breaks reverse-dependencies testsuites, and
please move to github maintained repo.
Severity set to 'important' from 'serious'
--
865675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865675
Debian Bug Tracki
control: severity -1 important
>I understand it's inconvenient, but it's not RC. As long as you file another
>bug, it won't get lost.
done :)
>Not so fast.
>
>Apparently all you looked at were autopkgtests. Pyyaml runs the test suite
>during build (although failures are non-fatal - I should p
On Sun, 05 Feb 2017 10:24:24 +0800, Tommy Wu wrote:
> After upgrade to 1.05-1, sendxmpp program can't send message to googole
> hangouts.
>
> XML::Stream: SetCallBacks: tag(node) func(CODE(0x5567d6c2aa20))
> XMPP::Conn: xmppCallbackInit: start
> XMPP::Conn: SetCallBacks: tag(message) func(CODE(0
Source: haskell-http-link-header
Version: 1.0.3-1
Severity: serious
Hi,
haskell-http-link-header FTBFS on every architecture (other than all):
> Network.HTTP.Link
> writeLinkHeader tests: : commitBuffer: invalid argument (invalid
> character)
> Test suite tests: FAIL
Regards,
James
Your message dated Fri, 23 Jun 2017 23:29:16 +
with message-id
and subject line Bug#865207: fixed in texlive-extra 2017.20170623-1
has caused the Debian Bug report #865207,
regarding texlive-latex-extra: File conflict due to missing Breaks/Replaces:
trying to overwrite
'/usr/share/texlive/te
Your message dated Fri, 23 Jun 2017 23:22:45 +
with message-id
and subject line Bug#864750: fixed in texlive-base 2017.20170623-1
has caused the Debian Bug report #864750,
regarding texlive-base: dvipdfmx.def is broken
to be marked as done.
This means that you claim that the problem has been
Package: quiterss
Version: 0.18.4+dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
quiterss has stopped working today with segfault. This is the backtrace:
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
[...]
Reading symbols from quiterss...Reading symbols
from
/usr/
Processing control commands:
> severity 854210 serious
Bug #854210 [libnet-xmpp-perl] libnet-xmpp-perl: sendxmpp can't send message to
hangouts (work fine for 1.02-5)
Severity set to 'serious' from 'important'
--
854210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854210
Debian Bug Trackin
Processing commands for cont...@bugs.debian.org:
> forcemerge 850033 865702
Bug #850033 [libepoxy0] libepoxy0: Segmentation fault, fixed upstream
Bug #865702 [libepoxy0] libepoxy: Patch causing serious issues on amdgpu-pro
Severity set to 'important' from 'critical'
Marked as found in versions lib
Package: libepoxy0
Version: 1.3.1-2
Severity: critical
File: libepoxy
Justification: breaks the whole system
2017-06-23 23:54 GMT+02:00 Gianfranco Costamagna :
Hello, just FYI, a patch you included in the Debian packaging is causing some
serious issues on amdgpu-pro
devices
https://github.com/anh
On 23 June 2017 at 22:37, Helmut Grohne wrote:
| Source: sprng
| Version: 2.0a-2
| Severity: serious
| Justification: policy 4.6
| User: helm...@debian.org
| Usertags: rebootstrap
|
| sprng's build system hides build failures. It's Makefile uses
| constructs such as:
|
| (cd $somewhere; $(MA
On Friday, June 23, 2017 08:18:44 PM Gianfranco Costamagna wrote:
> Hello Scott!
>
> >I'm not the maintainer, just an interest maintainer of a reverse
> >dependency.
> thanks for your caring (help and feedbacks are appreciated a lot!) :)
>
> >First, all the home page changes are inappropriate for
Processing commands for cont...@bugs.debian.org:
> affects 865563 src:libcatmandu-sru-perl
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Added indication that 865563 affects src:libcatmandu-sru-perl
> thanks
Stopping processing here.
Please contact me if you need as
Control: reassign -1 libmodule-build-perl 0.422400-1
Control: forwarded -1
https://github.com/Perl-Toolchain-Gang/Module-Build/issues/77
Control: affects src:libcatmandu-sru-perl
On Fri, 23 Jun 2017 21:19:43 +0100, Dominic Hargreaves wrote:
> On Fri, Jun 23, 2017 at 07:43:52PM +0200, gregor herr
Processing control commands:
> reassign -1 libmodule-build-perl 0.422400-1
Bug #865563 [src:libcatmandu-sru-perl] libcatmandu-sru-perl FTBFS: test failures
Bug reassigned from package 'src:libcatmandu-sru-perl' to
'libmodule-build-perl'.
No longer marked as found in versions libcatmandu-sru-perl/
Source: sprng
Version: 2.0a-2
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap
sprng's build system hides build failures. It's Makefile uses
constructs such as:
(cd $somewhere; $(MAKE); cd ..)
If there is a failure in the submake, it is not propagate
Hello Scott!
>I'm not the maintainer, just an interest maintainer of a reverse dependency.
thanks for your caring (help and feedbacks are appreciated a lot!) :)
>First, all the home page changes are inappropriate for an NMU. I would
>recommend you file a separate, normal priority, bug about t
On Fri, Jun 23, 2017 at 07:43:52PM +0200, gregor herrmann wrote:
> On Fri, 23 Jun 2017 17:22:52 +0200, gregor herrmann wrote:
>
> > > So what is not there anymore is PERL_USE_UNSAFE_INC=1.
> >
> > Dom, I think you're our expert on dot-in-inc; do you think my hunch
> > is correct that we need to a
Hi Julien,
On Fri, Jun 23, 2017 at 09:02:30PM +0200, Julien Yann Dutheil wrote:
> This is most strange indeed. The errors are all "time out" errors on unit
> tests which take the longest time (several min or so). Looks like some
> issues with the default value for the timeout setting in CTest... I
Dear Andreas, Adrian,
This is most strange indeed. The errors are all "time out" errors on unit
tests which take the longest time (several min or so). Looks like some
issues with the default value for the timeout setting in CTest... I would
suggest to simply skip the unit tests by running "cmake
-
I forwarded the bug to upstream. I think they will work on this very soon.
S
Le 23/06/2017 à 20:58, Marcio Bezerra a écrit :
> Looks like this bug was introduced in the latest kernel libraries
> update. Scilab was working just fine less than 24 hours ago.
> Scilab-cli is working but is very limi
Looks like this bug was introduced in the latest kernel libraries update.
Scilab was working just fine less than 24 hours ago. Scilab-cli is working
but is very limited. Does anyone know of a workaround for this kind of
problem? How long does it usually take for them to release a patch?
I have dow
Your message dated Fri, 23 Jun 2017 18:35:18 +
with message-id
and subject line Bug#865317: fixed in miller 5.2.1-3
has caused the Debian Bug report #865317,
regarding miller FTBFS on mips: FAIL run (exit status: 1)
to be marked as done.
This means that you claim that the problem has been dea
Hi,
u:
> I'm opening this RC bug in order to prevent tails-installer from
> migrating to testing.
Let's close this bug once there's a new upstream release that fixes
https://labs.riseup.net/code/issues/12696, so Tails Installer migrates
to testing (and then Ulrike can upload it to stretch-backpor
Source: josm-plugins
Version: 0.0.svn33112+ds-1
Severity: serious
Tags: upstream
Justification: makes the package unsuitable for release
josm-plugins will be removed from Debian because it doesn't play well
with user installed plugins. See:
https://josm.openstreetmap.de/ticket/7483
RM bugs have
I have the same bug on Debian 9 with KDE Plasma.
I had the same problem on Arch, maybe this is related to the kernel ? (
https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1699892 )
Best regards,
Piotr
On Friday, June 23, 2017 06:42:46 PM Gianfranco Costamagna wrote:
> control: tags -1 patch
> control: severity -1 serious
>
> > debdiff will follow once the bug is opened
>
> and here we are!
>
> I have uploaded in Ubuntu a few seconds ago
I'm not the maintainer, just an interest maintainer of
On Fri, 23 Jun 2017 17:22:52 +0200, gregor herrmann wrote:
> > So what is not there anymore is PERL_USE_UNSAFE_INC=1.
>
> Dom, I think you're our expert on dot-in-inc; do you think my hunch
> is correct that we need to add PERL_USE_UNSAFE_INC back?
> (And if yes, where would be the best place - i
Processing commands for cont...@bugs.debian.org:
> severity 855829 normal
Bug #855829 [python-django-tables2] python-django-tables2 FTBFS with Django 1.11
Severity set to 'normal' from 'serious'
> retitle 855829 New upstream release needed in experimental for testing with
> django 1.11
Bug #85582
severity 855829 normal
retitle 855829 New upstream release needed in experimental for testing with
django 1.11
tag 855829 - buster
tag 855829 - sid
thanks
Adrian - where is the FTBFS build log to justify increasing the
severity of 855829 to RC?
I reported a different bug, nothing at all to do wi
Processing control commands:
> found -1 2.5.1-1
Bug #865678 [src:knot] knot: Improper TSIG validity period check can allow TSIG
forgery
Marked as found in versions knot/2.5.1-1.
--
865678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865678
Debian Bug Tracking System
Contact ow...@bugs.debi
Source: knot
Version: 2.4.3-1
Severity: grave
Tags: security upstream patch
Control: found -1 2.5.1-1
Hi
See
https://lists.nic.cz/pipermail/knot-dns-users/2017-June/001144.html
and
http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
and filling a bug in BTS to have a referen
Processing commands for cont...@bugs.debian.org:
> forcemerge 865522 865659
Bug #865522 [scilab] scilab: Segmentation fault at lauch
Bug #865659 [scilab] scilab: Segmentation fault at launch. It was working
before an upgrade performed on 21 June.
Severity set to 'grave' from 'important'
Marked as
Processing control commands:
> tags -1 patch
Bug #865675 [src:libyaml] yaml: breaks reverse-dependencies testsuites, and
please move to github maintained repo.
Added tag(s) patch.
> severity -1 serious
Bug #865675 [src:libyaml] yaml: breaks reverse-dependencies testsuites, and
please move to git
Source: scotch
Version: 5.1.12b.dfsg-2
Severity: serious
Justification: policy 4.6
Tags: jessie stretch buster sid
User: helm...@debian.org
Usertags: rebootstrap
When some part of scotch's build fails (e.g. mpicc), the build continues
and may produce a broken package. This violates Debian Policy s
Your message dated Fri, 23 Jun 2017 15:53:17 +
with message-id
and subject line Bug#865650: fixed in firefox-esr 52.2.0esr-2
has caused the Debian Bug report #865650,
regarding firefox-esr FTBFS: tries to use system nspr but has no build
dependency
to be marked as done.
This means that you c
Source: ruby-prof
Version: 0.16.2+dfsg-2
Severity: serious
Tags: buster sid
Some recent change in unstable makes ruby-prof FTBFS:
https://tests.reproducible-builds.org/debian/history/ruby-prof.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-prof.html
...
┌───
On Thu, 22 Jun 2017 21:33:27 +0200, gregor herrmann wrote:
> Basically the diff between 0.422000-1 (with our changes) and 0.422400-1
> (with a different fix and without our patch) is:
>
>
> @@ -1824,6 +1824,11 @@ sub print_build_script {
>my $shebang = $self->_startperl;
>my $magic_numbe
Source: golang-github-microcosm-cc-bluemonday
Version: 0.0~git20161012.0.f77f16f-1
Severity: serious
Tags: buster sid
Some recent change in unstable makes golang-github-microcosm-cc-bluemonday
FTBFS:
https://tests.reproducible-builds.org/debian/history/golang-github-microcosm-cc-bluemonday.html
Source: flask-restful
Version: 0.3.5-1
Severity: serious
Tags: buster sid
Some recent change in unstable makes flask-restful FTBFS:
https://tests.reproducible-builds.org/debian/history/flask-restful.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flask-restful.html
...
Processing commands for cont...@bugs.debian.org:
> tags 865662 buster sid
Bug #865662 [src:libcatmandu-perl] libcatmandu-perl FTBFS:
Catmandu-Fix-perlcode.t failed
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
865662: http://bugs.de
Source: libcatmandu-perl
Version: 1.0304-2
Severity: serious
Some recent change in unstable makes libcatmandu-perl FTBFS:
https://tests.reproducible-builds.org/debian/history/libcatmandu-perl.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcatmandu-perl.html
...
t/Catm
Your message dated Fri, 23 Jun 2017 15:09:50 +
with message-id
and subject line Bug#865606: fixed in orthanc 1.2.0+dfsg-2
has caused the Debian Bug report #865606,
regarding orthanc FTBFS with libdcmtk-dev 3.6.1~20170228-2
to be marked as done.
This means that you claim that the problem has b
On Fri, Jun 23, 2017 at 11:56:45PM +0900, Mike Hommey wrote:
> On Fri, Jun 23, 2017 at 04:53:19PM +0300, Adrian Bunk wrote:
> > Source: firefox-esr
> > Version: 52.2.0esr-1
> > Severity: serious
> >
> > https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid
> >
> > ...
> > checking
On Fri, Jun 23, 2017 at 11:56:45PM +0900, Mike Hommey wrote:
> On Fri, Jun 23, 2017 at 04:53:19PM +0300, Adrian Bunk wrote:
> > Source: firefox-esr
> > Version: 52.2.0esr-1
> > Severity: serious
> >
> > https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid
> >
> > ...
> > checking
Source: django-compat
Version: 1.0.13-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/django-compat.html
...
Normal module existence can be tested ... ok
test_json_response_custom_encoder (compat.tests.test_compat.JsonResponseTests)
... ok
On Fri, Jun 23, 2017 at 04:53:19PM +0300, Adrian Bunk wrote:
> Source: firefox-esr
> Version: 52.2.0esr-1
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid
>
> ...
> checking for valloc in malloc.h... yes
> checking for valloc in unistd.h... no
> checkin
Now I upgraded xrdp and xorgxrdp to experimental, and the problem
still persists:
# dpkg -l | grep xrdp
ii xorgxrdp0.9.2~20170325-1~exp1
amd64Remote Desktop Protocol (RDP) modules for X.org
ii xrdp0.9.2~20170325-1~exp1
amd64Remo
9.0 machine, by installing xrdp and
creating a user. I'm using the Windows 8.1 RDP client.
After logging in, the screen is blank blue background for 10 seconds, and then a
window with "Connection problem, giving up" appears. The following is the
content of
/var/log/xrdp-sesman.log
Your message dated Fri, 23 Jun 2017 22:58:02 +0900
with message-id <20170623135802.sxkoq2nd5psc5...@bulldog.preining.info>
and subject line closing bug
has caused the Debian Bug report #864750,
regarding texlive-base: dvipdfmx.def is broken
to be marked as done.
This means that you claim that the
Source: firefox-esr
Version: 52.2.0esr-1
Severity: serious
https://buildd.debian.org/status/package.php?p=firefox-esr&suite=sid
...
checking for valloc in malloc.h... yes
checking for valloc in unistd.h... no
checking NSPR selection... system
checking for nspr-config... no
checking for NSPR - ver
Package: openstack-debian-images
Version: 1.19
Severity: serious
Tags: patch
The code is currently *only* adding security sources into
apt/sources.list when building for wheezy or jessie. This is clearly
wrong. I've just had to rebuild our stretch images again (9.0.1 to
9.0.2) to get expected upda
Your message dated Fri, 23 Jun 2017 13:20:35 +
with message-id
and subject line Bug#865589: fixed in openvpn 2.4.3-2
has caused the Debian Bug report #865589,
regarding Ships a tmpfile in /usr and /etc, one overriding the other
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 23 Jun 2017 13:35:19 +
with message-id
and subject line Bug#865511: fixed in haskell-tls 1.3.10-2
has caused the Debian Bug report #865511,
regarding haskell-tls: FTBFS, missing quickcheck dependency?
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 863659 serious
Bug #863659 [libgpg-error0] debian/copyright puts LGPL-2.1+ text in GPL-2.1+
license block
Severity set to 'serious' from 'minor'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863659: ht
Your message dated Fri, 23 Jun 2017 12:36:11 +
with message-id
and subject line Bug#827665: fixed in live-config 5.20170623
has caused the Debian Bug report #827665,
regarding systemd goes into timeout while waiting for local-fs.target
to be marked as done.
This means that you claim that the
ok, I have stretch installed, looking how to boot it (configure grub
manually)
SH0x@OFTC #debian-boot
On 06/22/2017 10:31 PM, jared.doming...@dell.com wrote:
*Dell Customer Communication
*
I’m saying you can manually add a boot entry if the installer doing it
fails. That way you’ll be ab
Your message dated Fri, 23 Jun 2017 12:20:45 +
with message-id
and subject line Bug#865494: fixed in logidee-tools 1.2.17
has caused the Debian Bug report #865494,
regarding logidee-tools: Don't depend on NBS pgf
to be marked as done.
This means that you claim that the problem has been dealt
On Fri, Jun 23, 2017 at 01:20:02PM +0200, Daniel Pocock wrote:
> Package: virt-viewer
> Version: 5.0-1
> Severity: serious
>
>
> I recently updated a Debian system, here are the new and old versions of
> each package from dpkg.log
>
> upgrade virt-viewer:amd64 1.0-1 5.0-1
> upgrade virt-manager:
On 23/06/17 13:45, Guido Günther wrote:
> On Fri, Jun 23, 2017 at 01:20:02PM +0200, Daniel Pocock wrote:
>> Package: virt-viewer
>> Version: 5.0-1
>> Severity: serious
>>
>>
>> I recently updated a Debian system, here are the new and old versions of
>> each package from dpkg.log
>>
>> upgrade vir
Hi Adrian,
thanks a lot for your continuous QA effort (I have the feeling that 90%
of the Debian Med bugs were issued by you ;-) ).
Julien, do you have some explanation for the issue? I made sure that
cmake files were found also on i386 so the issue now concerns
Version: 2.3.1-3
but bpp-phyl
On Wed, May 31, 2017 at 01:42:34PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
>
> >From the attached log (scroll to the bottom...):
>
> Setting up gru
Package: virt-viewer
Version: 5.0-1
Severity: serious
I recently updated a Debian system, here are the new and old versions of
each package from dpkg.log
upgrade virt-viewer:amd64 1.0-1 5.0-1
upgrade virt-manager:all 1:1.0.1-5 1:1.4.0-5
upgrade spice-client-gtk:amd64 0.25-1+b1 0.33-3.3
upgrade l
Processing commands for cont...@bugs.debian.org:
> severity 865511 serious
Bug #865511 [src:haskell-tls] haskell-tls: FTBFS, missing quickcheck dependency?
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
865511: http://bugs.
Your message dated Fri, 23 Jun 2017 10:51:08 +
with message-id
and subject line Bug#865575: fixed in miaviewit 1.0.5-1
has caused the Debian Bug report #865575,
regarding miaviewit FTBFS with mia 2.4.4-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> severity 856951 grave
Bug #856951 [runc] runc: does not work with systemd hybrid cgroup hierarchy
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
856951: http://bugs.debian.or
Your message dated Fri, 23 Jun 2017 09:38:15 +
with message-id
and subject line Bug#865465: fixed in openmpi 2.1.1-6
has caused the Debian Bug report #865465,
regarding openmpi FTBFS on s390x: undefined reference to opal_atomic_*
to be marked as done.
This means that you claim that the proble
Processing commands for cont...@bugs.debian.org:
> reopen 865317
Bug #865317 {Done: Stephen Kitt } [src:miller] miller FTBFS
on mips: FAIL run (exit status: 1)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add t
Your message dated Fri, 23 Jun 2017 09:24:08 +
with message-id
and subject line Bug#865615: fixed in mia 2.4.4-2
has caused the Debian Bug report #865615,
regarding mia: Reduce build-time memory usage on mips/mipsel to fix FTBFS
to be marked as done.
This means that you claim that the problem
On 23.06.2017 10:26, Raphael Hertzog wrote:
> Hello Felix,
>
> On Thu, 22 Jun 2017, Felix Geyer wrote:
>> I've prepared a backported patch of the relevant changes from 5.5.5 for
>> jessie and stretch.
> How did you identify the relevant changes from 5.5.5 given that we
> don't have any git reposit
Your message dated Fri, 23 Jun 2017 08:50:36 +
with message-id
and subject line Bug#865233: fixed in auto-multiple-choice 1.3.0-3
has caused the Debian Bug report #865233,
regarding auto-multiple-choice-common: depends on non-existing package
latex-xcolor
to be marked as done.
This means tha
Hello Felix,
On Thu, 22 Jun 2017, Felix Geyer wrote:
> I've prepared a backported patch of the relevant changes from 5.5.5 for
> jessie and stretch.
How did you identify the relevant changes from 5.5.5 given that we
don't have any git repository and that we don't have access to the
previous rele
Hi,
Fyi, the original patch also breaks openjdk (SEGV from JNI_CreateJavaVM)
when the VM is launched on the main thread (which is not the case for
the normal java launcher, but embedded uses - e.g. browser plugin <
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772>,
commons-daemon, ...)
Processing commands for cont...@bugs.debian.org:
> retitle 865590 django-sekizai FTBFS with Django 1.11: TypeError: context must
> be a dict rather than SekizaiContext
Bug #865590 [src:django-sekizai] django-sekizai FTBFS with Django 1.11
Changed Bug title to 'django-sekizai FTBFS with Django 1.1
Processing commands for cont...@bugs.debian.org:
> reassign 865416 src:linux
Bug #865416 [cargo] cargo: segfaults some of the time on ppc64el, can't
reproduce in gdb
Bug reassigned from package 'cargo' to 'src:linux'.
No longer marked as found in versions cargo/0.17.0-2.
Ignoring request to alter
Processing commands for cont...@bugs.debian.org:
> found 865571 mingw-w64/5.0.2-1
Bug #865571 {Done: Stephen Kitt } [mingw-w64-tools] alliance
and mingw-w64-tools: error when trying to install together
Marked as found in versions mingw-w64/5.0.2-1.
> notfound 865571 mingw-w64-tools/5.0.2-1
Bug #8
Your message dated Fri, 23 Jun 2017 07:20:39 +
with message-id
and subject line Bug#865317: fixed in miller 5.2.1-2
has caused the Debian Bug report #865317,
regarding miller FTBFS on mips: FAIL run (exit status: 1)
to be marked as done.
This means that you claim that the problem has been dea
Processing commands for cont...@bugs.debian.org:
> found 865571 mingw-w64-tools/5.0.2-1
Bug #865571 {Done: Stephen Kitt } [mingw-w64-tools] alliance
and mingw-w64-tools: error when trying to install together
The source mingw-w64-tools and version 5.0.2-1 do not appear to match any
binary package
Processing control commands:
> forcemerge -1 865416
Bug #865549 [src:linux] linux: stack-guard fix for CVE-2017-1000364 incorrect
Unable to merge bugs because:
package of #865416 is 'cargo' not 'src:linux'
Failed to forcibly merge 865549: Did not alter merged bugs.
--
865416: http://bugs.debian
Control: forcemerge -1 865416
It's fixed by the kernel you linked:
$ uname -a
Linux page 3.16.0-4-powerpc64le #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-21)
ppc64le GNU/Linux
$ for i in {1..10}; do cargo/bin/cargo -V; done
cargo 0.19.0 (28d1d60d4 2017-05-16)
cargo 0.19.0 (28d1d60d4 2017-05-16)
carg
Source: mia
Version: 2.4.4-1
Severity: serious
Tags: patch
https://buildd.debian.org/status/package.php?p=mia&suite=sid
...
virtual memory exhausted: Cannot allocate memory
mia/2d/maskedcost/CMakeFiles/2dimage-maskedcost-ncc-common.dir/build.make:65:
recipe for target
'mia/2d/maskedcost/CMakeFi
86 matches
Mail list logo
