Processing of graphite2_1.3.13-3_amd64.changes

2019-01-06 Thread Debian FTP Masters
graphite2_1.3.13-3_amd64.changes uploaded successfully to localhost along with the files: graphite2_1.3.13-3.dsc graphite2_1.3.13-3.debian.tar.xz graphite2_1.3.13-3_amd64.buildinfo libgraphite2-3-dbgsym_1.3.13-3_amd64.deb libgraphite2-3_1.3.13-3_amd64.deb

graphite2_1.3.13-3_amd64.changes ACCEPTED into experimental

2019-01-06 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 04 Jan 2019 17:04:27 + Source: graphite2 Binary: libgraphite2-3 libgraphite2-dev libgraphite2-doc libgraphite2-utils python3-graphite2 Architecture: source amd64 all Version: 1.3.13-3 Distribution:

Bug#918499: libreoffice: fails with 'ERROR 4 forking process'

2019-01-06 Thread David Zelinsky
Package: libreoffice Version: 1:6.1.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, I'm running "testing", and recently did a dist-upgrade. Previously libreoffice worked fine, but now fails to start. From the menu, nothing happens. From command line, it fails with

Bug#918499: libreoffice: fails with 'ERROR 4 forking process'

2019-01-06 Thread Rene Engelhard
tag 918499 + moreinfo tag 918499 + unreproducible severity 918499 important thanks Hi, On Sun, Jan 06, 2019 at 01:46:09PM -0500, David Zelinsky wrote: > Package: libreoffice > Version: 1:6.1.3-2 > Severity: grave > Justification: renders package unusable Sorry, but not every problem one person

Bug#918499: libreoffice: fails with 'ERROR 4 forking process'

2019-01-06 Thread David Zelinsky
First, I apologize for any way in which I might be misusing the bug-reporting system. Really I thought I was doing a service by reporting this. As an aside, if, as I hope, you want to encourage people to use Debian and to report bugs, I would suggest you might want to adopt a more more civil

Bug#918499: libreoffice: fails with 'ERROR 4 forking process'

2019-01-06 Thread Rene Engelhard
On Sun, Jan 06, 2019 at 08:21:36PM -0500, David Zelinsky wrote: > > No, you didn't. > > Yes, I did. If you think something may have gone wrong with it, then > you might tell me that. But if you think I'm lying, you're wrong. I just said you didn't do a upgrade _recently_ because, see below -