Processing control commands:
> found -1 232-25+deb9u6
Bug #918848 [src:systemd] systemd: CVE-2018-16865
Marked as found in versions systemd/232-25+deb9u6.
> found -1 240-2
Bug #918848 [src:systemd] systemd: CVE-2018-16865
Marked as found in versions systemd/240-2.
--
918848: https://bugs.debian.
Source: systemd
Version: 43-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 232-25+deb9u6
Control: found -1 240-2
Hi,
The following vulnerability was published for systemd, opening
tracking bug.
CVE-2018-16865[0]:
memory corruption
If you fix the vu
On Wed, Jan 09, 2019 at 09:42:43PM +0100, Andreas Tille wrote:
> to find the exact code line[2] where the SIGSEGV is thrown. It turns out
> that the elements of a structure are not accessible:
>
>(gdb) print entry->offset
>Cannot access memory at address 0x7
It's because entry is 0x7.
>
Hi Faidon,
Quoting Faidon Liambotis (2019-01-09 16:16:40)
> > Until it is properly fixed upstream we can just temporarily disable
> > --enable-prof, right?
> We could, yes. This is a useful piece of functionality that I'd like to
> enable, though...
but does it matter if proot disables it in its
On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
wrote:
> Source: systemd
> Version: 204-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Control: found -1 232-25+deb9u6
> Control: found -1 240-2
>
> Hi,
>
> The following vulnerability was published for
Am 09.01.19 um 22:45 schrieb Michael Biebl:
> Should CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866 be handled
> separately, i.e. do you plan to file separate bug reports?
Hm, for some reason I only received #918848 just now.
So that part of my question is moot.
Regards,
Michael
--
Why is it
On Wed, Jan 09, 2019 at 10:49:48PM +0100, Andreas Tille wrote:
> > > to find the exact code line[2] where the SIGSEGV is thrown. It turns out
> > > that the elements of a structure are not accessible:
> > >
> > >(gdb) print entry->offset
> > >Cannot access memory at address 0x7
> > It's b
Your message dated Wed, 09 Jan 2019 21:54:12 +
with message-id
and subject line Bug#918768: fixed in opencolorio 1.1.0~dfsg0-4
has caused the Debian Bug report #918768,
regarding opencolorio FTBFS with yaml-cpp 0.6.2
to be marked as done.
This means that you claim that the problem has been de
Please go on.
I think I finally do full release but I need a little time to start up this
project on Debian's gitlab first.
Cheers,
.''`.Piotr Roszatycki
: :' :mailto:piotr.roszaty...@gmail.com
`. `' mailto:dex...@debian.org
`-
On Wed, Jan 9, 2019 at 11:31 AM Johannes Schauer w
Your message dated Wed, 09 Jan 2019 21:18:50 +
with message-id
and subject line Bug#917660: fixed in pyhamcrest 1.8.0-1.1
has caused the Debian Bug report #917660,
regarding vim-youcompleteme: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 09 Jan 2019 21:18:50 +
with message-id
and subject line Bug#917660: fixed in pyhamcrest 1.8.0-1.1
has caused the Debian Bug report #917660,
regarding vim-youcompleteme: FTBFS (failing tests)
to be marked as done.
This means that you claim that the problem has been deal
Hi,
On Thu, Jan 10, 2019 at 02:14:14AM +0500, Andrey Rahmatullin wrote:
> On Wed, Jan 09, 2019 at 09:42:43PM +0100, Andreas Tille wrote:
> > to find the exact code line[2] where the SIGSEGV is thrown. It turns out
> > that the elements of a structure are not accessible:
> >
> >(gdb) print en
Hi,
as reported in bug #907624 ffindex autopkgtest fails with SIGSEGV in sid
and buster. I've tested in stretch (gcc 6.3) and the code works fine.
I've reported upstream[1] the results of my gdb session where I was able
to find the exact code line[2] where the SIGSEGV is thrown. It turns out
tha
Thanks for reporting this. From looking around, it looks like this was the
consequence of a bug-fix in NumPy 1.16:
```
Arrays based off readonly buffers cannot be set writeable
-
We now disallow setting the writeable flag True on arrays
Your message dated Wed, 09 Jan 2019 21:15:18 +
with message-id
and subject line Bug#918670: fixed in node-duplexer3 0.1.4-3
has caused the Debian Bug report #918670,
regarding node-duplexer3 FTBFS with nodejs 10.15.0
to be marked as done.
This means that you claim that the problem has been de
Hi,
On Wed, Jan 09, 2019 at 10:50:32PM +0100, Michael Biebl wrote:
> Am 09.01.19 um 22:45 schrieb Michael Biebl:
> > Should CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866 be handled
> > separately, i.e. do you plan to file separate bug reports?
>
> Hm, for some reason I only received #918848 j
Processing control commands:
> tag -1 pending
Bug #892388 [src:caffe-contrib] caffe-contrib: build-depends on GCC 6
Added tag(s) pending.
--
892388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Followup-For: Bug #892388
Control: tag -1 pending
Hi,
I just pushed a (build-tested) commit to switch to CUDA 9.2 and GCC 7.
I don't plan to upload it immediately ... so you can update the package
if needed and upload yourself.
Andreas
Your message dated Wed, 9 Jan 2019 22:06:32 +0100
with message-id <20190109210632.ga28...@seneca.home.org>
and subject line Re: morbig: FTBFS: unsatisfiable build-dependencies:
libppx-deriving-yojson-ocaml-dev, libppx-visitors-ocaml-dev
has caused the Debian Bug report #917701,
regarding morbig: F
Processing control commands:
> tags -1 pending
Bug #918090 [src:theano] theano: C-optimized ops fail with "module
'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"
Bug #918217 [src:theano] theano: autopkgtest fails with python-numpy
(1:1.16.0~rc1-3)
Added tag(s) pending.
Added t
Control: tags -1 pending
Control: tags 918771 pending
I intend to upload theano (also containing other changes - see Salsa
repo) either tonight or tomorrow night.
...or by calling numpy 1.16 a transition, are you implying you want this
minimal fix and nothing else?
Your message dated Wed, 09 Jan 2019 22:40:12 +
with message-id
and subject line Bug#916292: fixed in pyfai 0.17.0+dfsg1-2
has caused the Debian Bug report #916292,
regarding pyfai FTBFS on i386: test failures
to be marked as done.
This means that you claim that the problem has been dealt with
Processing commands for cont...@bugs.debian.org:
> severity 918749 serious
Bug #918749 [libtss2-dev] libtss2-dev: missing Depends: libgcrypt20-dev,
pkg-config --libs tss2-esys lists -lgcrypt
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> tags 918823 + moreinfo
Bug #918823 [libc6] libc6: [24945.428485] libvirtd[12553]: segfault at 8 ip
7fb0f515ba63 sp 7fff86e08370 error 4 in ld-2.24.so[7fb0f514b000+23000]
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please co
Processing commands for cont...@bugs.debian.org:
> tags 918823 - d-i
Bug #918823 [libc6] libc6: [24945.428485] libvirtd[12553]: segfault at 8 ip
7fb0f515ba63 sp 7fff86e08370 error 4 in ld-2.24.so[7fb0f514b000+23000]
Removed tag(s) d-i.
> thanks
Stopping processing here.
Please contact me
Hi,
On 2019-01-09 16:25, leopoldotosi wrote:
>
> Package: libc6
> Version: 2.24-11+deb9u3
> Severity: critical
> Tags: d-i
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
> I can not work libvirtd ?-:-(
I am sorry about that.
> Reading symbols from virsh...(no debugging sym
Your message dated Wed, 09 Jan 2019 23:21:36 +
with message-id
and subject line Bug#918833: fixed in node-browserify-lite 0.5.0-3
has caused the Debian Bug report #918833,
regarding node-browserify-lite: autopkgtest regression
to be marked as done.
This means that you claim that the problem h
Your message dated Wed, 09 Jan 2019 23:49:53 +
with message-id
and subject line Bug#834915: fixed in node-temp 0.8.3-2
has caused the Debian Bug report #834915,
regarding node-temp: FTBFS (AssertionError: temp.createWriteStream did not
create a file)
to be marked as done.
This means that you
Package: cargo
Version: 0.31.1-1
Severity: grave
Any time I try to update the crates.io index with the currently packaged
version of cargo, I get a segfault:
$ cargo update
Updating crates.io index
Segmentation fault
I can reproduce this in a brand new project (`cargo new foo`) by adding
any
On 1/9/19 3:45 PM, Andreas Beckmann wrote:
> Package: neutron-fwaas-common
> Version: 1:13.0.1-3
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to remove.
>
>>From the attached log (scroll to the bo
Processing control commands:
> reopen -1
Bug #892403 {Done: Samuel Thibault } [src:starpu-contrib]
starpu-contrib: build-depends on GCC 6
'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 them.
Bug reopened
No l
Followup-For: Bug #892403
Control: reopen -1
Hi,
while trying to rebuild starpu-contrib for CUDA 9.2 it failed with some
errors related to gcc-6.
I successfully built the package with the attached patch that switched
to GCC 7, but since the build system is a bit special, I'm not going to
upload
Andreas Beckmann, le jeu. 10 janv. 2019 01:02:19 +0100, a ecrit:
> I successfully built the package with the attached patch that switched
> to GCC 7, but since the build system is a bit special, I'm not going to
> upload this myself.
I'll handle it once CUDA 9.2 is uploaded, yes. Thanks for checki
Package: debconf
Version: 1.5.69
Severity: serious
Hi.
I'm running a mostly-up-to-date Debian/sid system. I just tried updating
it, and it barf at me when I ask it to update debconf:
root@machine:~# aptitude install debconf
The following NEW packages will be installed:
libau
On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
wrote:
> Source: systemd
> Version: 204-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Control: found -1 232-25+deb9u6
> Control: found -1 240-2
>
> Hi,
>
> The following vulnerability was published for
Your message dated Thu, 10 Jan 2019 01:19:06 +
with message-id
and subject line Bug#912712: fixed in dlang-openssl 2.0.0+1.1.0h-0.1
has caused the Debian Bug report #912712,
regarding vibe.d FTBFS with ldc
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Thu, 10 Jan 2019 01:20:02 +
with message-id
and subject line Bug#918749: fixed in tpm2-tss 2.1.0-3
has caused the Debian Bug report #918749,
regarding libtss2-dev: missing Depends: libgcrypt20-dev, pkg-config --libs
tss2-esys lists -lgcrypt
to be marked as done.
This means
Package:
python-meep-openmpi,python-meep-mpich2,python-meep-mpi-default,python-meep-lam4
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this mak
Control: fixed -1 0.9.15-1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Processing control commands:
> fixed -1 0.9.15-1
Bug #918596 [src:ruby-acts-as-list] ruby-acts-as-list FTBFS with rails 5.2
Marked as fixed in versions ruby-acts-as-list/0.9.15-1.
--
918596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918596
Debian Bug Tracking System
Contact ow...@bugs.de
Your message dated Thu, 10 Jan 2019 10:11:48 +0530
with message-id <37c526ff-638e-43b3-af99-bf23d97ec...@onenetbeyond.org>
and subject line Fixed with new upstream version in unstable
has caused the Debian Bug report #918596,
regarding ruby-acts-as-list FTBFS with rails 5.2
to be marked as done.
T
For anyone looking at this bug (especially folks at bug squashing
parties): I've filed an Intent To Salvage for this package
(https://bugs.debian.org/917937), and assuming I don't hear from the
maintainer by January 21st, will be uploading a version of lsof that
fixes this bug.
Hi Michael,
On Thu, Jan 10, 2019 at 01:41:17AM +0100, Michael Biebl wrote:
> On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
> wrote:
> > Source: systemd
> > Version: 204-1
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > Control: found -1 232-25+d
Your message dated Thu, 10 Jan 2019 06:55:32 +0100
with message-id <20190110055520.gy1...@sym.noone.org>
and subject line Re: Bug#918764: udev: "udevadm control --reload-rules" kills
all processes except init
has caused the Debian Bug report #918764,
regarding udev: "udevadm control --reload-rules
Hi again Tobias,
On Sun, Nov 18, 2018 at 09:53:30AM +0100, Joost van Baal-Ilić wrote:
> On Sat, Nov 17, 2018 at 11:57:03PM +0100, Dr. Tobias Quathamer wrote:
> > Am 17.11.2018 um 09:04 schrieb Joost van Baal-Ilić:
> > > I plan to work on the Debian FAQ at
> > > https://wiki.debian.org/BSP/2019/01/
tags 918326 +patch +pending
tags 918645 +patch +pending
thanks
I just went ahead and uploaded a NMU fixing bugs 918326 (dependency on cruft
package) and 918645 (testsuite failure due to missing build-dependency) to
delayed/5. A debdiff is attatched, please tell me if you have any issues with
t
Processing commands for cont...@bugs.debian.org:
> tags 918326 +patch +pending
Bug #918326 [python3-dfwinreg] python-dfwinreg and python3-dfwinreg depend on
cruft package dtfabric
Added tag(s) patch.
Bug #918326 [python3-dfwinreg] python-dfwinreg and python3-dfwinreg depend on
cruft package dtfa
Your message dated Thu, 10 Jan 2019 06:50:03 +
with message-id
and subject line Bug#918738: fixed in odb-api 0.18.1-4
has caused the Debian Bug report #918738,
regarding libodb-api-dev is not installable due to typo in the dependencies
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 912077 - help
Bug #912077 [src:libbiod] libbiod FTBFS on i386: Error: cannot implicitly
convert expression
Removed tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
912077: https://bugs.debian.org
Your message dated Thu, 10 Jan 2019 09:12:11 +0200
with message-id <20190110071211.GK13260@localhost>
and subject line python-qpid-proton is back in buster
has caused the Debian Bug report #918280,
regarding koji build depends on python-qpid-proton that is currently not in
buster
to be marked as d
Your message dated Thu, 10 Jan 2019 09:10:31 +0200
with message-id <20190110071031.GJ13260@localhost>
and subject line python3-factory-boy is back in buster
has caused the Debian Bug report #918340,
regarding pylint-django build depends on python3-factory-boy that is currently
not in buster
to be
Processing control commands:
> forwarded -1 https://github.com/biod/BioD/issues/50
Bug #917721 [src:libbiod] libbiod: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu
&& LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1
Set Bug forwarded-to-address to 'https://github.com/biod/BioD/is
Control: forwarded -1 https://github.com/biod/BioD/issues/50
Control: tags -1 help upstream
Dear Matthias,
unfortunately there is another issue with libbiod and as usual I need
your help due to my total incompetence in D. :-(
I have reported the issue upstream as well.
Kind regards
Andr
101 - 153 of 153 matches
Mail list logo
