Dear Maintainer,
I guess this issue caused also gegl not transitioning to testing and
therefore another issue within the package gimp e.g. bug #939768
and a few more.
I tried to reproduce it in a qemu VM for mips64el
and hit the same issue.
Running just the mentioned test it returns a timeout
Package: suricata
Version: 1:4.1.4-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other
Control: tag -1 pending
Hello,
Bug #940198 in okasha 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:
Processing control commands:
> tag -1 pending
Bug #940198 [python3-okasha-examples] python3-okasha-examples: missing
Breaks+Replaces: python-okasha-examples
Added tag(s) pending.
--
940198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940198
Debian Bug Tracking System
Contact
Your message dated Sat, 14 Sep 2019 00:50:25 +
with message-id
and subject line Bug#914481: fixed in python-pylxd 2.2.10-1
has caused the Debian Bug report #914481,
regarding [bank] python3-pylxd: Python3-pylxd is not Python3 compatible
to be marked as done.
This means that you claim that
Hi Dominique and Robert,
Could you please verify the {moarvm,nqp,rakudo}-2019.07.1 in
experimental? Shall I proceed and upload it to unstable?
On 2019-09-13 14:44, M. Zhou wrote:
> Hi Dominique,
>
> Will do it later. BTW, the *.moarvm not found error is related to this:
>
Source: printrun
Version: 2.0.0~rc5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other
Processing control commands:
> tag -1 pending
Bug #914481 [python3-pylxd] [bank] python3-pylxd: Python3-pylxd is not Python3
compatible
Added tag(s) pending.
--
914481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #914481 in python-pylxd 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: xfce4-sntray-plugin-common
Version: 0.4.12-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to
Package: ncbi-cn3d
Version: 3.0.20170106+dfsg1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to
Package: python3-zc.buildout
Version: 2.13.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to
Your message dated Fri, 13 Sep 2019 22:19:01 +
with message-id
and subject line Bug#940201: Removed package(s) from unstable
has caused the Debian Bug report #935550,
regarding yubioath-desktop: Qt4 removal from Bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 13 Sep 2019 22:19:24 +
with message-id
and subject line Bug#940202: Removed package(s) from unstable
has caused the Debian Bug report #875140,
regarding [qliss3d] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
On Mon, Sep 02, 2019 at 08:25:55PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Sep 09, 2017 at 11:06:23PM +0200, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > Source: qliss3d
> > Version: 1.4-2
> > Severity: wishlist
> > User: debian-qt-...@lists.debian.org
> > Usertags: qt4-removal
> >
> >
>
Your message dated Fri, 13 Sep 2019 21:36:56 +
with message-id
and subject line Bug#853629: fixed in qtads 2.1.7-0.1
has caused the Debian Bug report #853629,
regarding qtads: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 13 Sep 2019 21:36:56 +
with message-id
and subject line Bug#875157: fixed in qtads 2.1.7-0.1
has caused the Debian Bug report #875157,
regarding [qtads] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt
On Sat, Sep 09, 2017 at 10:13:27PM +0200, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Source: ostinato
> Version: 0.8-1
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
>
>
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as
On Mon, Aug 19, 2019 at 02:12:35AM -0400, Scott Kitterman wrote:
> On Sat, 03 Mar 2018 21:16:22 +0100 Andreas Beckmann wrote:
> > Source: syrthes
> > Version: 4.3.0-dfsg1-2
> > Severity: serious
> > Tags: sid buster
> > Justification: blocks python-qwt5-qt4 removal
> > Control: block 886779 with
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'
> > /usr/bin/ld.gold: contrib/undead/*/__main.o: previous definition here
>
Processing commands for cont...@bugs.debian.org:
> clone 936900 -1
Bug #936900 [src:libpeas] libpeas: Python2 removal in sid/bullseye
Bug 936900 cloned as bug 940199
> reassign -1 src:pluma
Bug #940199 [src:libpeas] libpeas: Python2 removal in sid/bullseye
Bug reassigned from package
Package: python3-okasha-examples
Version: 0.2.4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to
Your message dated Fri, 13 Sep 2019 19:48:50 +
with message-id
and subject line Bug#911171: fixed in epigrass 2.5.0+dfsg-1
has caused the Debian Bug report #911171,
regarding epigrass: Please don't depend on python-visual
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 13 Sep 2019 19:48:50 +
with message-id
and subject line Bug#891994: fixed in epigrass 2.5.0+dfsg-1
has caused the Debian Bug report #891994,
regarding epigrass: Depends on Qt4-only python-qwt5-qt4
to be marked as done.
This means that you claim that the problem has
Source: 3dldf-doc
Version: 2.0.3+ndfsg-3
Severity: serious
3dldf-doc cannot be built in bullseye any longer since the transitional
texlive packages have been removed.
Andreas
Source: gegl
Version: 0.4.12-2
Severity: serious
Justification: ftbfs
Tags: ftbfs
Dear maintainer,
The last build of gegl failed on mips64el and the last binNMU on mipsel
failed with the same error. I noticed because there is currently a glibc
transition going on and glibc can't simply migrate
To clarify, 10.3.18 has been uploaded to Debian unstable. Issue is
still open for Buster and Stretch.
On Wed, 11 Sep 2019 21:01:42 +0200 Christian T. Steigies wrote:
> On Sat, Sep 07, 2019 at 06:48:17PM +0200, Francesco Poli wrote:
> > On Tue, 3 Sep 2019 23:55:22 +0200 Francesco Poli wrote:
> >
> > > On Sun, 1 Sep 2019 23:27:17 +0200 Christian T. Steigies wrote:
> > [...]
> > > > The libgs
Hi.
Today, I made a rebuild of the 0.9.4-2 package on a Debian Stretch.
This is strange because the 0.9.4-2 binary package (amd64) from the
Debian repository works fine here (GUI displayed), but if I make a
rebuild of this very package (without changing anything), the GUI isn't
displayed.
On Friday, September 13, 2019 11:56:30 AM EDT Sebastiaan Couwenberg wrote:
> Hi Scott,
>
> Thanks for finally reviewing pywps.
>
> On 9/13/19 5:23 PM, Scott Kitterman wrote:
> > One of our ftp-trainees reviewed your package and made the following
> > observations.
>
> It seems that the process
notfound 939754 2.10.8-2
thanks
Downgrading to the build currently in buster works around the crash.
Processing commands for cont...@bugs.debian.org:
> notfound 939754 2.10.8-2
Bug #939754 [gimp] gimp: Crashes when I try to open an image or create a new one
No longer marked as found in versions gimp/2.10.8-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Fri, 13 Sep 2019 16:05:13 +
with message-id
and subject line Bug#939492: fixed in nbsphinx 0.4.2+ds-2
has caused the Debian Bug report #939492,
regarding nbsphinx: testsuite failures with new pandoc
to be marked as done.
This means that you claim that the problem has been
Hi Scott,
Thanks for finally reviewing pywps.
On 9/13/19 5:23 PM, Scott Kitterman wrote:
> One of our ftp-trainees reviewed your package and made the following
> observations.
It seems that the process is broken.
This is far from the first time where an anonymous ftp-trainee commented
on a
Processing commands for cont...@bugs.debian.org:
> tags 940185 + moreinfo
Bug #940185 [src:pywps] src:pywps: Debian/copyright needs update
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
940185:
Package: src:pywps
Version: 4.2.1-1
Severity: serious
Justification: Policy 2.3
One of our ftp-trainees reviewed your package and made the following
observations. They exist in the current version of the package, so I'm
not rejecting as a result, but they should be fixed in the next upload:
Your message dated Fri, 13 Sep 2019 15:00:59 +
with message-id
and subject line Bug#940133: Removed package(s) from unstable
has caused the Debian Bug report #874911,
regarding [hamfax] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 13 Sep 2019 15:01:49 +
with message-id
and subject line Bug#940141: Removed package(s) from unstable
has caused the Debian Bug report #875066,
regarding [ofono-phonesim] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 13 Sep 2019 15:01:25 +
with message-id
and subject line Bug#940134: Removed package(s) from unstable
has caused the Debian Bug report #874931,
regarding [karlyriceditor] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 13 Sep 2019 14:55:08 +
with message-id
and subject line Bug#939531: Removed package(s) from unstable
has caused the Debian Bug report #939531,
regarding RM: medit -- RoQA; python2-only; dead upstream; low popcon; no rdeps
to be marked as done.
This means that you
Your message dated Fri, 13 Sep 2019 14:54:27 +
with message-id
and subject line Bug#939529: Removed package(s) from unstable
has caused the Debian Bug report #939529,
regarding RM: gtg -- RoM; python2-only; dead upstream; low popcon; no rdeps
to be marked as done.
This means that you claim
Hi Dominique,
Will do it later. BTW, the *.moarvm not found error is related to this:
https://github.com/rakudo/rakudo/issues/3093
We can temporarily symlink several directories to wordaround this.
On Fri, 13 Sep 2019 at 12:24, Dominique Dumont wrote:
>
> On Thursday, 12 September 2019
Hey.
Just to put some emphasise on this, the fix has now been merged late to
5.3 as urgent.
Also note Filipe's post[0] that the issue can more or less hit anyone.
Cheers,
Chris.
[0]
Am Fr., 13. Sept. 2019 um 15:21 Uhr schrieb Andreas Tille :
>
> Hi Matthias,
>
> since a ling time libbiod does not build and it also does not
> install. Current issue when trying to build it is:
>
> ...
> ldc2 -wi -g -relocation-model=pic -unittest -main -Icontrib/undead -L-lz -O0
> -d-debug
Hi Gregory!
Thanks you for the confirmation and the "workaround".
The issue as just been resolved for Buster (see 939819).
I will check with Otto when the next upload is planned for Stretch.
Regards,
Faustin
signature.asc
Description: PGP signature
Hi Matthias,
since a ling time libbiod does not build and it also does not
install. Current issue when trying to build it is:
...
ldc2 -wi -g -relocation-model=pic -unittest -main -Icontrib/undead -L-lz -O0
-d-debug -link-debuglib contrib/undead/cstream.o contrib/undead/stream.o
Hello,
We confirm this serious bug.
After upgrading from 10.1.38-0+deb9u1 to 10.1.41-0+deb9u1,
replication is completely broken.
For the moment we `apt-mark old` mariadb package with
10.1.38-0+deb9u1 version on all our servers.
Regards,
--
Grégory Colpart - CEO Evolix - Clé OpenPGP :
Your message dated Fri, 13 Sep 2019 12:50:05 +
with message-id
and subject line Bug#874952: fixed in keurocalc 1.3.0-2
has caused the Debian Bug report #874952,
regarding [keurocalc] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 13 Sep 2019 12:48:58 +
with message-id
and subject line Bug#940063: fixed in gnss-sdr 0.0.11-2
has caused the Debian Bug report #940063,
regarding gnss-sdr FTBFS, is gr-iio broken? did gnuradio break ABI?
to be marked as done.
This means that you claim that the
Package: distro-info
Version: 0.21
Severity: serious
Tags: bullseye, sid
pylint has been migrated from python 2 to python 3. This seems to be causing an
autopkgtest failure in your package. Can you fix it so that pylint can migrate
to testing?
On Thursday, 12 September 2019 08:33:00 CEST Niels Thykier wrote:
> Does rakudo build with "Rules-Requires-Root: no"[1]? If it does, then
> you can work around the bug / issue in fakeroot for sid, testing and
> stable for now by using it.
Yes ! I can now build rakudo on my laptop. Thanks for the
Processing commands for cont...@bugs.debian.org:
> severity 938215 serious
Bug #938215 [src:python-testtools] python-testtools: Python2 removal in
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938215:
Package: gimp
Version: 2.10.8-2+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Q) What led up to the situation?
A) open any image file
Q) What exactly did you do (or not do) that was effective (or ineffective)?
A) choose restart
Q) What was the outcome of this
On Fri, Sep 13, 2019 at 05:16:30PM +0800, Drew Parsons wrote:
> Python maintainers, remember, check your reverse dependencies before
> dropping your python2 packages.
> Check each of
>
> build-rdeps python-yourmodule
> apt-rdepends -r python-yourmodule
>
> and confirm the package has rdeps=0
Your message dated Fri, 13 Sep 2019 11:22:22 +
with message-id
and subject line Bug#873992: fixed in libusb-java 0.8+ztex20090101-8
has caused the Debian Bug report #873992,
regarding FTBFS with Java 9 due to -source/-target only
to be marked as done.
This means that you claim that the
Your message dated Fri, 13 Sep 2019 11:24:51 +
with message-id
and subject line Bug#938494: fixed in skimage 0.14.2-3
has caused the Debian Bug report #938494,
regarding skimage: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tag -1 pending
Bug #873992 [src:libusb-java] FTBFS with Java 9 due to -source/-target only
Added tag(s) pending.
--
873992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #873992 in libusb-java 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 Fri, 13 Sep 2019 10:36:59 +
with message-id
and subject line Bug#909416: fixed in gnome-keyring 3.31.91-2
has caused the Debian Bug report #909416,
regarding gnome-keyring: sometimes FTBFS, mostly with single CPU:
test-gkd-ssh-agent-service
Your message dated Fri, 13 Sep 2019 10:21:09 +
with message-id
and subject line Bug#912538: fixed in libjaba-client-java 0+dfsg-2
has caused the Debian Bug report #912538,
regarding libjaba-client-java: FTBFS with Java 11 due to JAXB removal
to be marked as done.
This means that you claim
On Fri, Sep 13, 2019 at 11:09:58AM +0200, Ole Streicher wrote:
> > Sure. But do you want to do team uploads of python-numpy and its > 300
> > rdepends as well? I was considering the amount of packages that are
> > affected by RC bugs which is way lower if we leave skimage RC buggy
> > rather
Control: tag -1 pending
Hello,
Bug #912538 in libjaba-client-java 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:
Processing control commands:
> tag -1 pending
Bug #912538 [src:libjaba-client-java] libjaba-client-java: FTBFS with Java 11
due to JAXB removal
Added tag(s) pending.
--
912538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912538
Debian Bug Tracking System
Contact ow...@bugs.debian.org
On 2019-09-13 15:42, Andreas Tille wrote:
Hi,
as Peter Green found out the cloudpickle source package droped Python2
support which makes bug #938494 serious. I guess it would be even
harder to drop python-skimage right now since this would affect
python-numpy and according to
$ apt-cache
Your message dated Fri, 13 Sep 2019 09:10:00 +
with message-id
and subject line Bug#939402: fixed in sagemath 8.9~beta9-1
has caused the Debian Bug report #939402,
regarding sagemath: depends on cruft Python2 packages
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 13 Sep 2019 09:10:02 +
with message-id
and subject line Bug#929468: fixed in wolfssl 4.1.0+dfsg-1
has caused the Debian Bug report #929468,
regarding wolfssl: CVE-2019-11873
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 13 Sep 2019 09:10:02 +
with message-id
and subject line Bug#918952: fixed in wolfssl 4.1.0+dfsg-1
has caused the Debian Bug report #918952,
regarding wolfssl: CVE-2018-16870
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 13 Sep 2019 09:03:19 +
with message-id
and subject line Bug#917759: fixed in openhft-chronicle-wire 1.1.13-2
has caused the Debian Bug report #917759,
regarding openhft-chronicle-wire: FTBFS: Could not resolve dependencies for
project
Your message dated Fri, 13 Sep 2019 09:00:48 +
with message-id
and subject line Bug#939819: fixed in mariadb-10.3 1:10.3.18-1
has caused the Debian Bug report #939819,
regarding mariadb-10.3: Replication hangs with "preparing" and never starts
to be marked as done.
This means that you claim
Package: python-mlt
Version: 6.16.0-4
Severity: serious
Control: affects -1 flowblade
The upload of mlt 6.16.0-4 converted the package to use Python 3 (thanks
for that). However, it didn't change the name of the binary package to
python3-mlt as required by the Python modules packaging policy.
Processing control commands:
> affects -1 flowblade
Bug #940166 [python-mlt] python-mlt: converted to Python 3 without following
Python modules packaging policy
Added indication that 940166 affects flowblade
--
940166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940166
Debian Bug
Processing commands for cont...@bugs.debian.org:
> affects 924005 release.debian.org
Bug #924005 [jetty9] client certificate verification regression with puppetdb
Added indication that 924005 affects release.debian.org
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing control commands:
> tag -1 pending
Bug #917759 [src:openhft-chronicle-wire] openhft-chronicle-wire: FTBFS: Could
not resolve dependencies for project net.openhft:chronicle-wire:bundle:1.1.13
Added tag(s) pending.
--
917759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917759
Control: tag -1 pending
Hello,
Bug #917759 in openhft-chronicle-wire 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:
Hi,
as Peter Green found out the cloudpickle source package droped Python2
support which makes bug #938494 serious. I guess it would be even
harder to drop python-skimage right now since this would affect
python-numpy and according to
$ apt-cache rdepends python-numpy | sort | uniq | wc -l
75 matches
Mail list logo
