On Sun, 20 May 2018 00:02:58 +0200 Adam Borowski wrote:
> Source: openhpi
> Version: 3.6.1-3.1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Hi!
> I'm afraid that during a rolling archive rebuild, your package failed.
> Tried on armhf amd
Control: tag -1 pending
Hello,
Bug #875268 in nwchem 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:
https://salsa.debian.org/debichem-team/nwchem/commit/95647d96861343ea8d6617905d2716
Processing control commands:
> tag -1 pending
Bug #875268 [nwchem] nwchem: update BLACS configuration for scalapack 2
Added tag(s) pending.
--
875268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 24 May 2018 04:19:22 +
with message-id
and subject line Bug#893138: fixed in jabref 3.8.2+ds-5
has caused the Debian Bug report #893138,
regarding jabref: Moreover, there is 4.2 now! Still no running jabref anywhere,
since 3.5. No openjdk/-jfx or whatsoever anywhere.
t
Your message dated Thu, 24 May 2018 04:19:22 +
with message-id
and subject line Bug#893138: fixed in jabref 3.8.2+ds-5
has caused the Debian Bug report #893138,
regarding jabref: fails to build and start with openjdk-9
to be marked as done.
This means that you claim that the problem has been
Control: tag -1 pending
Hello,
Bug #893138 in jabref 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:
https://salsa.debian.org/java-team/jabref/commit/922fd3ca13c3a2b5bfcdcd31270d7205e8
Processing control commands:
> tag -1 pending
Bug #893138 [jabref] jabref: fails to build and start with openjdk-9
Bug #898570 [jabref] jabref: Moreover, there is 4.2 now! Still no running
jabref anywhere, since 3.5. No openjdk/-jfx or whatsoever anywhere.
Added tag(s) pending.
Added tag(s) pendi
Good evening,
Here is the nmudiff with a new patch. See
https://salsa.debian.org/owncloud-team/owncloud-client/merge_requests/1 for
a gitted version.
The second patch fixes other errors that may happen, and that were
mentionned in the forwarded bug on github.
The upload will probably occur in th
On Thu, Apr 05, 2018 at 06:26:28PM +0300, Adrian Bunk wrote:
> Uncaught TypeError: nextTick is not a function
> at Cloneable.onData (/usr/lib/nodejs/cloneable-readable/index.js:32:5)
It looks like this is an issue with node-cloneable-readable, though I don't see
why nextTick wouldn't be
On Wed, May 23, 2018 at 02:56:55PM +0200, Gianfranco Costamagna wrote:
> control: reassign -1 src:acpica-unix
> control: found -1 20180508-1
> control: affects -1 virtualbox
>
> On Tue, 22 May 2018 19:12:32 +0200 Emilio Pozuelo Monfort
> wrote:
> > Package: virtualbox
> > Version: 5.2.12-dfsg-1
Processing control commands:
> tag -1 pending
Bug #899332 [zookeeper] CVE-2018-8012: Apache ZooKeeper Quorum Peer mutual
authentication
Added tag(s) pending.
--
899332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Control: tag -1 pending
Hello,
Bug #899332 in zookeeper 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:
https://salsa.debian.org/java-team/zookeeper/commit/525cd00b67d07df6b1f49e25a49a
Your message dated Wed, 23 May 2018 21:04:21 +
with message-id
and subject line Bug#896221: fixed in django-macaddress 1.5.0-1
has caused the Debian Bug report #896221,
regarding python3-django-macaddress: macaddress fails to import
to be marked as done.
This means that you claim that the pro
Your message dated Wed, 23 May 2018 21:04:21 +
with message-id
and subject line Bug#896387: fixed in django-macaddress 1.5.0-1
has caused the Debian Bug report #896387,
regarding python-django-macaddress: macaddress fails to import
to be marked as done.
This means that you claim that the prob
Processing commands for cont...@bugs.debian.org:
> # golang-github-containerd-btrfs now FTBFS
> severity 898874 serious
Bug #898874 [golang-github-containerd-btrfs] golang-github-containerd-btrfs:
Update dependencies for split out libbtrfs-dev
Severity set to 'serious' from 'important'
> user deb
Your message dated Wed, 23 May 2018 20:42:15 +
with message-id
and subject line Bug#897531: fixed in speedcrunch 0.12.0-4
has caused the Debian Bug report #897531,
regarding speedcrunch: FTBFS: make[4]: *** No rule to make target
'doc/manual.qrc', needed by 'CMakeFiles/speedcrunch_arcc_manual
Le 23 mai 2018 20:58:01 GMT+02:00, "Sandro Knauß" a écrit :
>Hey,
>
>> I've prepared an NMU for owncloud-client (versioned as
>2.4.1+dfsg-1.1) and
>> intend to have it uploaded to the archive as soon as you give me your
>> agreement, except if you wish to upload it yourself.
>>
>> Should you not
I uploaded a new backport 0.10.1-1~bpo9+2 with the problematic
commit reverted. HTH.
Hey,
> I've prepared an NMU for owncloud-client (versioned as 2.4.1+dfsg-1.1) and
> intend to have it uploaded to the archive as soon as you give me your
> agreement, except if you wish to upload it yourself.
>
> Should you not answer in the next ten days I'll upload the patch right away.
Thanks
Your message dated Wed, 23 May 2018 18:52:08 +
with message-id
and subject line Bug#899247: fixed in openshot-qt 2.4.1+dfsg1-2
has caused the Debian Bug report #899247,
regarding openshot-qt: missing python3 dependencies
to be marked as done.
This means that you claim that the problem has bee
Control: tag -1 pending
Hello,
Bug #899247 in openshot-qt 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:
https://salsa.debian.org/multimedia-team/openshot-qt/commit/60edae72ab70340c55
Processing control commands:
> tag -1 pending
Bug #899247 [openshot-qt] openshot-qt: missing python3 dependencies
Added tag(s) pending.
--
899247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Probably issues w/ GCC being more strict than last time it was built.
Will investigate when I have time.
On 23/05/18 13:56, Sven Joachim wrote:
> Source: mono
> Version: 4.6.2.7+dfsg-2
> Severity: serious
>
> The new mono version FTBFS on four architectures where it has been built
> before, inclu
Dear maintainer,
I've prepared an NMU for owncloud-client (versioned as 2.4.1+dfsg-1.1) and
intend to have it uploaded to the archive as soon as you give me your
agreement, except if you wish to upload it yourself.
Should you not answer in the next ten days I'll upload the patch right away.
Best
Processing control commands:
> block 899394 by 899395
Bug #899394 [ncurses-base] ncurses-base: Add Breaks on libmono-corlib4.5-cil
(<< 4.6.2.7+dfsg-2)
899394 was not blocked by any bugs.
899394 was not blocking any bugs.
Added blocking bug(s) of 899394: 899395
--
899394: https://bugs.debian.org
Control: block 899394 by 899395
On 2018-05-23 19:27 +0200, Sven Joachim wrote:
> Package: ncurses-base
> Version: 6.1+20180210-4
> Severity: normal
>
> It has been noticed in #899112 and #899222 that Mono's
> System.TermInfoReader is incompatible with the new terminfo format. The
> Debian mono m
Source: mono
Version: 4.6.2.7+dfsg-2
Severity: serious
The new mono version FTBFS on four architectures where it has been built
before, including two release architectures.
On S390x, the error looks like this[1]:
,
| CC mono-mmap.lo
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../..
control: reopen -1
control: retitle -1 Transition script for
xul-ext-ublock-origin->webext-ublock-origin
control: severity -1 normal
Hello Michael,
On Wed, May 23 2018, Debian Bug Tracking System wrote:
> Forgot to close this report with the last upload.
I think it should remain open for the t
Processing control commands:
> reopen -1
Bug #881135 {Done: Michael Meskes } [src:ublock-origin]
xul-ext-ublock-origin: Update ublock-origin to version 1.14.16 by next p-u
Bug #877040 {Done: Michael Meskes } [src:ublock-origin] New
upstream version, including transition to webext
Bug #878072 {Do
Package: darcs
Version: 2.12.5-3
Severity: serious
darcs can't be built anymore on sid:
darcs build-depends on missing:
- libghc-graphviz-dev:amd64 (< 2999.19)
Emilio
Processing control commands:
> severity -1 serious
Bug #899247 [openshot-qt] openshot-qt: fails to start - requires pyhton module
'requests'
Severity set to 'serious' from 'important'
> retitle -1 openshot-qt: missing python3 dependencies
Bug #899247 [openshot-qt] openshot-qt: fails to start - re
Hello Michal,
I have NMU the package with the fix, even `openssl` has also fixed
their side on the same day.
Find NMU diff attached. And of course, I have just noticed 898963
(another NMU) after I have uploaded my changes. :-/
2018-05-18 16:53 GMT+02:00 Michal Čihař :
> Hello
>
> Feel free to
Your message dated Wed, 23 May 2018 14:09:53 +
with message-id
and subject line Re: Bug#894674: kernels 4.15 and 4.16 break xl2tpd
has caused the Debian Bug report #894674,
regarding kernels 4.15 and 4.16 break xl2tpd
to be marked as done.
This means that you claim that the problem has been d
Hi Adrian,
yeah, that didn't work out...
If you have time, would you mind looking at our analysis at
https://github.com/cisco/cjose/issues/70 where we gathered our findings?
Best wishes,
Moritz
On 20.05.2018 15:36, Adrian Bunk wrote:
> Control: reopen -1
>
> On Wed, May 16, 2018 at 08:39:03PM
Your message dated Wed, 23 May 2018 13:04:36 +
with message-id
and subject line Bug#899361: fixed in bcal 1.9-2
has caused the Debian Bug report #899361,
regarding bcal has unsatisfiable (build-) depends
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 23 May 2018 15:01:54 +0200
with message-id <20180523130154.GA8165@feivel>
and subject line Closing
has caused the Debian Bug report #877040,
regarding xul-ext-ublock-origin: Update ublock-origin to version 1.14.16 by
next p-u
to be marked as done.
This means that you claim
Your message dated Wed, 23 May 2018 15:01:54 +0200
with message-id <20180523130154.GA8165@feivel>
and subject line Closing
has caused the Debian Bug report #877040,
regarding Please upgrade to more recent version to be compatible with Firefox 57
to be marked as done.
This means that you claim that
Your message dated Wed, 23 May 2018 15:01:54 +0200
with message-id <20180523130154.GA8165@feivel>
and subject line Closing
has caused the Debian Bug report #877040,
regarding New upstream version, including transition to webext
to be marked as done.
This means that you claim that the problem has b
control: reassign -1 src:acpica-unix
control: found -1 20180508-1
control: affects -1 virtualbox
On Tue, 22 May 2018 19:12:32 +0200 Emilio Pozuelo Monfort
wrote:
> Package: virtualbox
> Version: 5.2.12-dfsg-1
> Severity: serious
>
> virtualbox fails to build on a clean sid chroot here:
>
> In
Processing control commands:
> reassign -1 src:acpica-unix
Bug #899318 [virtualbox] virtualbox: FTBFS: vboxssdt-standard.hex:16:23: error:
expected initializer before '-' token
Bug reassigned from package 'virtualbox' to 'src:acpica-unix'.
No longer marked as found in versions virtualbox/5.2.12-d
Quoting Peter Palfrader :
That entire commit seems highly problematic and not well
through-through for all use-cases.
Yes. It seems, that all three bugs you reported today relate
to the same commit. I will try to fix this today for bpo.
On Wed, 23 May 2018, W. Martin Borgert wrote:
> Seems to be fault of commit d39e1733bcf0d4a8898ab0cf1c31d3950ed8d557
> (https://salsa.debian.org/xmpp-team/prosody/commit/d39e1733bcf0d4a8898ab0cf1c31d3950ed8d557).
> IMHO, just reverting the change of line 28/29 in
> debian/prosody.postinst would h
Seems to be fault of commit d39e1733bcf0d4a8898ab0cf1c31d3950ed8d557
(https://salsa.debian.org/xmpp-team/prosody/commit/d39e1733bcf0d4a8898ab0cf1c31d3950ed8d557).
Strange - I came across the same error when installing 0.10.1-1~bpo9+1
at work, but somehow thought, that I made a mistake and just di
Your message dated Wed, 23 May 2018 11:14:47 +0100
with message-id <20180523101447.ga11...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#899362: preinst: Syntax error: "fi" unexpected
(expecting "done")
has caused the Debian Bug report #899362,
regarding preinst: Syntax error: "fi" unexpec
Processing commands for cont...@bugs.debian.org:
> found 899357 0.10.0-2
Bug #899357 [prosody] fails to configure without snakeoil cert
Marked as found in versions prosody/0.10.0-2.
> found 899359 0.10.0-2
Bug #899359 [prosody] fails to configure without /etc/prosody/certs/localhost.*
Marked as fo
Your message dated Wed, 23 May 2018 09:34:40 +
with message-id
and subject line Bug#897111: fixed in pypandoc 1.4+ds0-1.1
has caused the Debian Bug report #897111,
regarding pypandoc FTBFS with pandoc 2.1.2
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> found 899352 0.10.0-2
Bug #899352 [prosody] removes prosody role from ssl-cert
Marked as found in versions prosody/0.10.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
899352: https://bugs.debian.org/cgi-bin/
Package: bluez
Version: 5.49-2
Severity: serious
Hi,
With last upload, I get the following error when updating:
Préparation du dépaquetage de .../00-bluez_5.49-2_amd64.deb ...
/var/lib/dpkg/tmp.ci/preinst: 28: /var/lib/dpkg/tmp.ci/preinst: Syntax error:
"fi" unexpected (expecting "done")
dpkg:
Package: src:bcal
Version: 1.9-1
Severity: serious
Tags: sid buster
see https://tracker.debian.org/pkg/bcal
looks like package names were copied from a rpm-based system. This is Debian.
Package: prosody
Version: 0.10.1-1~bpo9+1
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
[fixing the snakeoil stuff, we then run into:]
| # dpkg --configure -a
| Setting up prosody (0.10.1-1~bpo9+1) ...
| chown: cannot access '/etc/prosody/certs/localhost.crt':
Package: prosody
Version: 0.10.1-1~bpo9+1
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
| vogler:~# dpkg --configure -a
| Setting up prosody (0.10.1-1~bpo9+1) ...
| install: cannot stat '/etc/ssl/certs/ssl-cert-snakeoil.pem': No such file or
directory
| dpkg:
Your message dated Wed, 23 May 2018 17:57:56 +0900
with message-id
and subject line Re: bluez: Syntax error in bluez preinst script: 28: : "fi"
unexpected (expecting "done")
has caused the Debian Bug report #899340,
regarding bluez: Syntax error in bluez preinst script: 28: : "fi" unexpected
(e
Your message dated Wed, 23 May 2018 17:57:56 +0900
with message-id
and subject line Re: bluez: Syntax error in bluez preinst script: 28: : "fi"
unexpected (expecting "done")
has caused the Debian Bug report #899340,
regarding bluez 5.49-2 preinst is improperly authored and fails during
preinsta
Package: bluez
Version: 5.49-1
Followup-For: Bug #899340
Dear Maintainer,
I tried to upgrade to the 5.49-2 version using the 'aptitude -rf full-upgrade'
and appeared this error.
- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture
Package: prosody
Version: 0.10.1-1~bpo9+1
Severity: serious
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
The prosody package removes the prosody role from ssl-cert at configure
time. If the admin added the prosody user to the ssl-cert group, this
undoes local configuration cha
Processing commands for cont...@bugs.debian.org:
> reassign 899342 src:bluez
Bug #899342 [bluez] bluez 5.49-2 preinst is improperly authored and fails
during preinstall
Bug reassigned from package 'bluez' to 'src:bluez'.
No longer marked as found in versions bluez/5.49-2.
Ignoring request to alte
Your message dated Wed, 23 May 2018 07:19:37 +
with message-id
and subject line Bug#871120: fixed in elixir-lang 1.6.5-1
has caused the Debian Bug report #871120,
regarding elixir-lang: FTBFS: 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 899348 normal
Bug #899348 {Done: Bas Couwenberg } [josm]
java.net.UnknownHostException: api.openstreetmap.org
Severity set to 'normal' from 'grave'
> tags 899348 + upstream wontfix
Bug #899348 {Done: Bas Couwenberg } [josm]
java.net.Unk
Your message dated Wed, 23 May 2018 08:56:34 +0200
with message-id <95da933572c1648b5372468eecbbd...@xs4all.nl>
and subject line Re: Bug#899348: java.net.UnknownHostException:
api.openstreetmap.org
has caused the Debian Bug report #899348,
regarding java.net.UnknownHostException: api.openstreetmap
59 matches
Mail list logo
