Processing commands for cont...@bugs.debian.org:
> tags 940634 + upstream
Bug #940634 [src:ibus] ibus: FTBFS: emojier.vala:915.48-915.53: error:
Assignment: Cannot convert from `GLib.SList' to `GLib.SList?'
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> block 940605 with 940632
Bug #940605 [libjbig2dec0] libjbig2dec0: breaks mupdf with message "undefined
symbol: jbig2_ctx_new"
940605 was not blocked by any bugs.
940605 was not blocking any bugs.
Added blocking bug(s) of 940605: 940632
> block
Control: tags -1 upstream
Control: forwarded -1 https://github.com/lbcb-sci/racon/issues/6
Processing control commands:
> tags -1 upstream
Bug #940564 [src:racon] racon: FTBFS against libspoa3
Added tag(s) upstream.
> forwarded -1 https://github.com/lbcb-sci/racon/issues/6
Bug #940564 [src:racon] racon: FTBFS against libspoa3
Set Bug forwarded-to-address to
Control: forcemerge 939754 939768 939876 939977 939985 940008 940011 940042
940044 940088 940174 940177 940285 940472 940525 940561 940610
Hello,
I hope it is ok to merge all such bugs.
All of them show gimp_gegl_mask_is_empty at an
instruction address ending in 411.
Now that gegl 0.4.14-2
Processing commands for cont...@bugs.debian.org:
> tags 939754 - upstream
Bug #939754 [gimp] gimp: Crashes when I try to open an image or create a new one
Bug #939768 [gimp] gimp: After the last upgrade, GIMP crashes when creating a
new image or opening an existing one.
Bug #939876 [gimp] gimp:
Hi,
pyface was lagging extremely behind upstream. To cope with Qt5 and
Python3 migration I simply pushed the latest upstream version to
the packaging Git[1]
==
ERROR: pyface.action.tests.test_action_item
Your message dated Wed, 18 Sep 2019 08:51:30 +
with message-id
and subject line Bug#933526: fixed in python-os-faults 0.2.1-2
has caused the Debian Bug report #933526,
regarding python3-os-faults: fails to install: update-alternatives: error:
alternative path /usr/bin/python3-os-inject-fault
Source: diffoscope
Version: 124
Severity: serious
Hello, thanks for fixing the previous bug! it worked!
However, due to another change, there is now a new failure:
=== FAILURES ===
___
Your message dated Wed, 18 Sep 2019 09:42:33 +
with message-id <20190918094233.GP1621@debian>
and subject line Re: [DRE-maint] Bug#939630: schleuder: breaks testbed?
has caused the Debian Bug report #939630,
regarding schleuder: breaks testbed?
to be marked as done.
This means that you claim
Source: ibus
Version: 1.5.19-4
Severity: serious
Justification: FTBFS
Hi
ibus currently FTBFS in unstable. Attached the build log when trying
to build 1.5.19-4 in a pbuilder chroot.
Regards,
Salvatore
ibus_1.5.19-4_amd64.build.xz
Description: application/xz
Processing control commands:
> tags -1 + fixed-upstream
Bug #940634 [src:ibus] ibus: FTBFS: emojier.vala:915.48-915.53: error:
Assignment: Cannot convert from `GLib.SList' to `GLib.SList?'
Added tag(s) fixed-upstream.
--
940634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940634
Debian
Control: tags -1 + fixed-upstream
It's been fixed in upstream 1.5.20 or later.
Maybe we can just upload 1.5.21-1~exp2 in experimental to unstable.
On 12/09/2019 15:42, Anton Ivanov wrote:
On 12/09/2019 13:14, Ritesh Raj Sarraf wrote:
Hi,
I am not sure if this has been reported upstream but with libpcap 1.9,
user mode linux fails to build. The build failure happens with both,
5.2 and 4.19 LTS kernels.
A much detailed report is
Processing control commands:
> forcemerge 939754 939768 939876 939977 939985 940008 940011 940042 940044
> 940088 940174 940177 940285 940472 940525 940561 940610
Bug #939754 [gimp] gimp: Crashes when I try to open an image or create a new one
Bug #940285 [gimp] segmentation fault at start
Control: tag -1 pending
Hello,
Bug #940645 in diffoscope 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:
Your message dated Wed, 18 Sep 2019 09:48:54 +
with message-id
and subject line Bug#940645: fixed in diffoscope 125
has caused the Debian Bug report #940645,
regarding diffoscope: testsuite failure due to new binutils?
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tag -1 pending
Bug #940645 [src:diffoscope] diffoscope: testsuite failure due to new binutils?
Added tag(s) pending.
--
940645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> found 939735 0.6~dfsg0-3
Bug #939735 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:libmysofa] libmysofa: CVE-2019-16091 CVE-2019-16092 CVE-2019-16093
CVE-2019-16094 CVE-2019-16095
Marked as found in versions libmysofa/0.6~dfsg0-3.
> thanks
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: fails to open file
to be marked as done.
This means that you claim that
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: crashes on opening exsisting or creating new image
to be marked as done.
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding Gimp 2.8 crashes
to be marked as done.
This means that you claim that the
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: segmentation fault on open
to be marked as done.
This means that you claim
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: GIMP crashed with a fatal error: fatal error: Segmentation fault
to be
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: GIMP crashed with a fatal error: fatal error: Segmentation fault
to be
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: Crashes when I try to open an image or create a new one
to be marked as
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: After the last upgrade, GIMP crashes when creating a new image
or opening
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: Crashes on Create with segmentation fault
to be marked as done.
This means
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding Gimp: crashes when I try open or create an image
to be marked as done.
This
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: GIMP crashes when opening an image
to be marked as done.
This means that
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: GIMP crashed with a fatal error: fatal error:
Speicherzugriffsfehler when
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: segfault on start
to be marked as done.
This means that you claim that the
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding segmentation fault at start
to be marked as done.
This means that you claim that
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: GIMP crashed with a fatal error: fatal error:
Speicherzugriffsfehler
to be
Processing commands for cont...@bugs.debian.org:
> fixed 939630 3.4.0-4
Bug #939630 {Done: Georg Faerber } [src:schleuder] schleuder:
breaks testbed?
Marked as fixed in versions schleuder/3.4.0-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
939630:
Processing control commands:
> severity 940605 serious
Bug #940605 [libjbig2dec0] libjbig2dec0: breaks mupdf with message "undefined
symbol: jbig2_ctx_new"
Severity set to 'serious' from 'normal'
> retitle 940605 jbig2dec: ABI breakage without SONAME and package name change
Bug #940605
On Mon, 05 Aug 2019 01:31:12 -0400 Scott Kitterman
wrote:
> Package: src:lavacli
> Version: 0.9.7-1
> Severity: grave
> Tags: security
> Justification: user security hole
>
> The new version of pyyaml no longer allows use of yaml.load() without a
> loader being specifed. This raises a
--
Can I discuss this Financial BUSINESS/PROJECT INVESTMENT with you?
Let me have your Tell, Fax and mobile Numbers and also contact address
in response.
Let me hear from you.
Kind regards
Hussein Khalid.
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: Gimp crashed with SIGSEGV
to be marked as done.
This means that you claim
Your message dated Wed, 18 Sep 2019 07:07:51 -0400
with message-id
and subject line Re: Bug#939754: gimp: Crashes when I try to open an image or
create a new one
has caused the Debian Bug report #939754,
regarding gimp: segmentation fault
to be marked as done.
This means that you claim that
Package: cycle
Version: 0.3.1-15
Severity: serious
Upgrading cycle to the latest version in unstable leads to the following
error during configuration:
Sorry: TabError: inconsistent use of tabs and spaces in indentation (cycle.py,
line 29)
This is due to the mix of 4 spaces for one level of
Am Fr., 13. Sept. 2019 um 22:51 Uhr schrieb Andreas Tille :
>
> On Fri, Sep 13, 2019 at 03:37:32PM +0200, Matthias Klumpp wrote:
> > Am Fr., 13. Sept. 2019 um 15:21 Uhr schrieb Andreas Tille
> > :
> > > /usr/bin/ld.gold: error: bin/biod_tests.o: multiple definition of
> > > '_d_execBssBegAddr'
>
Your message dated Thu, 19 Sep 2019 00:06:02 +0900
with message-id
and subject line Re: Bug#940634: ibus: FTBFS: emojier.vala:915.48-915.53:
error: Assignment: Cannot convert from `GLib.SList' to `GLib.SList?'
has caused the Debian Bug report #940634,
regarding ibus: FTBFS:
Your message dated Wed, 18 Sep 2019 15:34:08 +
with message-id
and subject line Bug#940651: fixed in cycle 0.3.1-16
has caused the Debian Bug report #940651,
regarding cycle: package installation fails at configuration stage due to
TabError
to be marked as done.
This means that you claim
Fresh installation is fine. /usr/share/perl6 should be a
symlink pointing to /usr/lib/perl6 in the latest version.
When directly upgrading rakudo to the expeirmental version,
this is not handled by dpkg.
I've fixed the upgrade issue in rakduo 2019.07.1-2 (experimental).
Later when the binary is
Your message dated Wed, 18 Sep 2019 15:19:37 +
with message-id
and subject line Bug#940267: fixed in ibus 1.5.21-1
has caused the Debian Bug report #940267,
regarding ibus: CVE-2019-14822
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Control: tags -1 + patch
Dear maintainers,
porting stretchplayer to Qt5 was straightforward.
You can find a merge request on salsa [0].
Kind regards,
Reiner
[0] https://salsa.debian.org/multimedia-team/stretchplayer/merge_requests/1
signature.asc
Description: PGP signature
Your message dated Wed, 18 Sep 2019 17:49:25 +
with message-id
and subject line Bug#934021: fixed in libsidplayfp 2.0.1-1
has caused the Debian Bug report #934021,
regarding libsidplayfp5: missing Breaks+Replaces: libsidplayfp4
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tags -1 + patch
Bug #875195 [src:stretchplayer] [stretchplayer] Future Qt4 removal from Buster
Added tag(s) patch.
--
875195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi!
El mié., 18 sep. 2019 13:18, Reiner Herrmann escribió:
> Control: tags -1 + patch
>
> Dear maintainers,
>
> porting stretchplayer to Qt5 was straightforward.
> You can find a merge request on salsa [0].
>
The patch looks great. I'll happy NMU it if you (the maintainer) agree.
I'll also NMU
Processing control commands:
> tag -1 pending
Bug #875195 [src:stretchplayer] [stretchplayer] Future Qt4 removal from Buster
Added tag(s) pending.
--
875195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #875195 in stretchplayer 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:
Package: zfsutils-linux
Version: 0.7.12-2+deb10u1
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
after upgrading from Stretch, the zfs filesystems fail to mount at boot time
due to the zfs-import-cache
service unit fails, with the following log:
systemd[1]:
Source: pandas
Version: 0.23.3+dfsg-6
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=pandas=amd64=0.23.3%2Bdfsg-6=1568839095=0
Was your local build on a different architecture, or must this be
something random / hardware-or-environment-dependent / a very recent
change in a
Processing commands for cont...@bugs.debian.org:
> severity 937632 normal
Bug #937632 [ftp.debian.org] RM: pythoncard -- RoQA; orphaned; Python 2 only;
dead upstream; low popcon
Severity set to 'normal' from 'serious'
> reassign 836500 wnpp
Bug #836500 [ftp.debian.org] ITA: flask-principal --
Processing commands for cont...@bugs.debian.org:
> severity 940220 serious
Bug #940220 [postgresql-common] postgresql-common: pg_ctlcluster segfault
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
940220:
Hi,
[Pjotr as upstream in CC]
On Wed, Sep 18, 2019 at 04:54:16PM +0200, Matthias Klumpp wrote:
> Am Fr., 13. Sept. 2019 um 22:51 Uhr schrieb Andreas Tille :
> >
> > On Fri, Sep 13, 2019 at 03:37:32PM +0200, Matthias Klumpp wrote:
> > > Am Fr., 13. Sept. 2019 um 15:21 Uhr schrieb Andreas Tille
>
On Wed, Sep 18, 2019 at 02:44:49PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Hi!
>
> El mié., 18 sep. 2019 13:18, Reiner Herrmann escribió:
>
> > Control: tags -1 + patch
> >
> > Dear maintainers,
> >
> > porting stretchplayer to Qt5 was straightforward.
> > You can find a merge
Your message dated Wed, 18 Sep 2019 20:37:07 +
with message-id
and subject line Bug#923759: fixed in netlib-java 0.9.3-7
has caused the Debian Bug report #923759,
regarding mtj: FTBFS: [javac]
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmBandMatrix.java:25:
error: package
Your message dated Wed, 18 Sep 2019 20:37:07 +
with message-id
and subject line Bug#923759: fixed in netlib-java 0.9.3-7
has caused the Debian Bug report #923759,
regarding mtj: FTBFS in buster/sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 18 Sep 2019 20:37:07 +
with message-id
and subject line Bug#924804: fixed in netlib-java 0.9.3-7
has caused the Debian Bug report #924804,
regarding mtj: FTBFS: [javac]
/<>/mtj-0.9.14+dfsg/src/no/uib/cipr/matrix/AbstractSymmBandMatrix.java:25:
error: package
Your message dated Wed, 18 Sep 2019 20:37:07 +
with message-id
and subject line Bug#924804: fixed in netlib-java 0.9.3-7
has caused the Debian Bug report #924804,
regarding mtj: FTBFS in buster/sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Hi all,
Libundead was removed as dependency for biod, but it may be there are
some other issues now because the D ecosystem keeps moving.
My main interest is sambamba and we are working on a fix for one of
the main outstanding bugs building against the latest D compilers.
I suggest to drop the
Package: lava-server
Version: 2019.01-5
Severity: serious
Tags: bullseye, sid
lava depends on gunicorn3 which is no longer built by the gunicorn source package.
I belive you need to change your dependency to gunicorn, possiblly with a version
constraint of >= 19.9.0-4
Your message dated Wed, 18 Sep 2019 23:48:59 +
with message-id
and subject line Bug#939044: fixed in ocrmypdf 9.0.3+dfsg-1
has caused the Debian Bug report #939044,
regarding ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript
and/or pytest
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> severity 938816 serious
Bug #938816 [src:webtest] webtest: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938816:
Your message dated Thu, 19 Sep 2019 00:19:16 +
with message-id
and subject line Bug#940015: fixed in minder 1.5.0-1
has caused the Debian Bug report #940015,
regarding minder: Incomplete debian/copyright?
to be marked as done.
This means that you claim that the problem has been dealt with.
On 19/09/17 10:17, Andreas Tille wrote:
> On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> >
> > Is the embedded stuff all in extlibs/? or is there some other 3rdparty code?
>
> A lot is excluded in advance from the packaging Git:
>
> Files-Excluded:
Am Mi., 18. Sept. 2019 um 20:39 Uhr schrieb Andreas Tille :
> [...]
> > This is definitely an error in BioD itself, caused by a deprecation
> > that turned into an error in recent LDC versions.
> > So, libbiod will need to be upgraded for sure to fix this.
>
> @Pjotr: Can you comment on this?
>
>
Package: breezy
Severity: serious
Version: 3.0.1-2
Breezy (both versions 3.0.1-2 and 3.0.1-4) build-depends on python-subunit
which is no longer built by the subunit source package.
Your message dated Thu, 19 Sep 2019 04:19:10 +
with message-id
and subject line Bug#935290: fixed in rakudo 2019.07.1-3
has caused the Debian Bug report #935290,
regarding rakudo: FTBFS on amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 19 Sep 2019 04:04:39 +
with message-id
and subject line Bug#940492: fixed in nordugrid-arc 6.2.0-2
has caused the Debian Bug report #940492,
regarding nordugrid-arc-arex: missing Breaks+Replaces: nordugrid-arc-aris
to be marked as done.
This means that you claim that
Source: ucblogo
Version: 6.0+dfsg-2
Severity: serious
Tags: upstream
Justification: Policy 2.1.2
I noticed this comment in debian/rules:
# don't autoreconf, as configure is newer than configure.in
# -> configure.in doesn't contain wxwidgets related checks
dh $@ --without
73 matches
Mail list logo
