Control: reassign -1 nodejs
This fails too:
yarnpkg add electron-spellchecker@1.1.2
Are you all doing this on qemu or on real hardware ?
On i686 ?
I'm asking because buster does not support i586, nor does nodejs,
and it seems qemu defaults to something < i686 (to be verified).
Jérémy
Control: tags -1 confirmed moreinfo
Hi,
On Thu, Mar 21, 2019 at 07:03:08PM +0100, Mathieu Parent wrote:
> I'm waiting your ack to upload those to unstable:
>
> unblock ldb/2:1.5.1+really1.4.6-3
> unblock samba/2:4.9.5+dfsg-2
Please go ahead with the upload to unstable and remove the moreinfo ta
Source: open-vm-tools
Version: 2:9.4.6-1770165-1
Severity: critical
Tags: security upstream
Upstream released 10.3.10, which contains a fix for a long standing
security issue:
commit e88f91b00a715b79255de6576506d80ecfdb064c
Author: Oliver Kurth
Date: Tue Jan 29 14:03:19 2019 -0800
Fix po
Le vendredi 29 mars 2019 à 01:23 -0400, Borden Rhodes a écrit :
> On Sun, 24 Mar 2019 17:47:38 +0100 =?ISO-8859-1?Q?S=E9bastien?=
> Villemot wrote:
> > The main reason is lack of manpower (a lot of work in the
> > Javascript
> > packages need to happen first).
>
> Thank you for the explanation. I
Package: python-scipy
Followup-For: Bug #723722
Apologies, I was trying to cancel my previous message but it slipped
through by accident, so please ignore it.
What I found was that the warning is emitted in
all cases, whether
np.nanmean([np.nan, np.nan])
np.nanmean([[np.nan, np.nan]])
or
Package: onesixtyone
Severity: important
Hello Jose,
The version of onesixtyone in Debian is very old (latest upload
was in 2008) and there is a new git repository as mentionned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909298
Since you did not reply to the bug above, I'm wondering if
Package: python-scipy
Followup-For: Bug #723722
nanmean is now removed from scipy.stats (1.1.0-4)
np.nanmean will process the array (without a warning) if given as a
numpy array (numpy 1:1.16.2-1):
>>> np.nanmean(np.array([np.nan, np.nan]))
nan
Hi Andreas
On 2019/03/29 09:45, Andreas Tille wrote:
with the current state in Git. Are you sure you have exactly the status
from Git (now head at 86cc4e0eafcc1cd2e2916ecf7c476495f5c16f1f - but I
simply added myself to Uploaders - no change to test).
I ran debdiff on what I uploaded to Ubuntu
Package: fstransform
Version: 0.9.3-2
Severity: critical
Tags: upstream
Justification: causes serious data loss
Dear Maintainer,
approximately 1.5 years ago I have discovered a reproducible case
of filesystem corruption by fstransform, and reported it upstream:
https://github.com/cosmos72/fstran
Package: sponsorship-requests
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear mentors,
I am looking for a sponsor for my package "wordplay"
Package name: wordplay
Version : 7.22-20
Upstream Author : Evans A Criswell (unresponsive)
URL :
http://hs
Package: simple-cdd
Version: 0.6.5
Severity: important
User: de...@kali.org
Usertags: origin-kali
Using a very basic configuration for simple-cdd, I can't build a stretch
image:
# cat > cdd.conf
debian_mirror=http://deb.debian.org/debian
security_mirror=http://security.debian.org/
dist=st
Subject: uwsgi-emperor: duplicate
Package: uwsgi-emperor
Version: 2.0.18-1
Severity: important
Dear Maintainer,
here is the problem:
# systemctl status logrotate.service
● logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor
preset: enab
Package: simple-cdd
Version: 0.6.5
Severity: normal
User: de...@kali.org
Usertags: origin-kali
When working within a long path, gpg-agent can't start and fails with an
explicity error message like the following:
gpg-agent: socket name
'/path/to/super/long/and/deeply/buried/directory/.../S.gpg-
Le 28/03/2019 à 21:50, Thorsten Glaser a écrit :
> 11. Apparently, the option is not available in the Zero VM,
> only in Hotspot (didn’t check DCE, JamVM, etc).
Indeed, but running Tomcat on Zero is not a good idea anyway.
G1 isn't available for DCEVM, but at least the error message is clear:
Same here, I have just one machine running jessie, FWIW it seems that
what triggers the problem is an rsync connection from another host.
Unfortunately nothing gets logged (the last message in syslog is the
rsync connection) and nothing on the console.
The (virtual) machine is totally unresponsiv
Package: libkf5libkleo5
Version: 4:18.08.3-2
Severity: normal
Dear Maintainer,
Kleopatra used a slightly wrong syntax for calling tar when archiving
a folder. This is no longer accepted by tar and leads to errors.
This was fixed upstream by:
https://cgit.kde.org/libkleo.git/commit/?
id=8a94ac083
Hi Steve,
> Could you describe your system a little more please? Has efibootmgr
> worked OK previously?
I'm on a generic HP "ProDesk" desktop. I don't know if efibootmgr
worked previously, as it has been recently pulled by another
dependency.
What could help you to know ?
Hi Graham,
On Thu, Mar 28, 2019 at 04:58:38PM +0200, Graham Inggs wrote:
> Hi Olivier
>
> On 2019/03/09 17:56, olivier sallou wrote:
> > I have pushed a fix to get autopkgtests done in python-intervaltree-bio
> > I have not uploaded package, as we are in freeze transition, so patch is in
> > git
Forwarded: https://github.com/Ultimaker/CuraEngine/issues/984
The Fedora maintainer already reported the issue upstream and applied a patch:
https://src.fedoraproject.org/rpms/CuraEngine/blob/master/f/CuraEngine-gcc9.patch
However, this patch makes the package unbuildable on GCC 8, so it will nee
101 - 119 of 119 matches
Mail list logo
