Hello Andreas!
I'm sorry to tell you that I did a mistake: I filed again the
bug #940204 by accident!
--
Yours sincerely
Joerg Schiermeier
Package: bed
Version: 3.0.0
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
1.) The desktop file for Linux (/usr/share/applications/xx.desktop) is missing
the additional category 'ConsoleOnly'. Please see for futher informations the
documentation about desktop files
Hello Nordert, thanks for the report. I will fix it next week-end. Cheers,
Jerome.
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B
signature.asc
Description: OpenPGP digital
Your message dated Mon, 16 Sep 2019 02:34:13 +
with message-id
and subject line Bug#940190: fixed in gegl 0.4.14-2
has caused the Debian Bug report #940190,
regarding gegl: FTBFS on mips64el and mipsel while it did built before
to be marked as done.
This means that you claim that the problem
Control: tag -1 pending
Hello,
Bug #940190 in gegl 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 #940190 [src:gegl] gegl: FTBFS on mips64el and mipsel while it did built
before
Added tag(s) pending.
--
940190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Great -- given that this bug is at least a week old, several people have
found fixes, and a fix hasn't yet made it into the 'testing' updates, what
is necessary to get a fix pushed to the world?
I can apt-pin like many of the correspondents in this report, and many
other reports for the same
Control: fixed -1 435.21-1
the nonglvnd libraries were removed upstream in the 435 driver series
Andreas
Processing control commands:
> fixed -1 435.21-1
Bug #939401 [nvidia-driver-libs-nonglvnd] nvidia-driver-libs-nonglvnd: Xorg
crashing when running with nonglvnd libraries
Bug #939489 [nvidia-driver-libs-nonglvnd] nvidia-driver-libs-nonglvnd: Xorg
crashing when running with nonglvnd libraries
Package: falkon
Version: 3.0.0-3
Severity: critical
Tags: upstream
Justification: breaks the whole system
Dear Maintainer,
After a fresh install, I tried to run Falkon with no success. It crashes on
start. Sometimes it actually starts but when it does, If I click the default
bookmark, titled
Your message dated Sun, 15 Sep 2019 22:23:19 +
with message-id
and subject line Bug#939598: fixed in libubootenv 0.1-2
has caused the Debian Bug report #939598,
regarding libubootenv-tool: trying to overwrite '/usr/bin/fw_printenv', which
is also in package u-boot-tools 2019.01+dfsg-7
to be
On 9/15/19 2:26 PM, Mattia Rizzolo wrote:
> Considering that this is bzr we are talking about, a package that is
> already entering the graveyard, I think it would be easiest to just
> disable the test suite and move on.
>
> But I would be happier it Thomas at least checked the rdeps before
>
Processing commands for cont...@bugs.debian.org:
> severity #936189 serious
Bug #936189 [src:bcfg2] bcfg2: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> severity #937165 serious
Bug #937165 [src:nss-pam-ldapd] nss-pam-ldapd: Python2 removal in sid/bullseye
Severity set
On Thu, Aug 29, 2019 at 08:31:00PM +0200, Moritz Mühlenhoff wrote:
> On Thu, Sep 21, 2017 at 03:36:38PM +0200, Yves-Alexis Perez wrote:
> > On Thu, 2017-09-21 at 00:09 +0800, Boyuan Yang wrote:
> > > I noticed that you are planning to remove Qt components of lightdm from
> > > Debian's lightdm.
On Sat, Sep 09, 2017 at 11:55:14PM +0200, Andreas Tille wrote:
> control: forwarded -1 https://github.com/SCIInstitute/ImageVis3D/issues/8
> control: tags -1 upstream
>
> Hi,
>
> I have opened an issue on Github (#8) that a Qt5 port would be helpful
> to keep the imagevis3d package inside
Processing commands for cont...@bugs.debian.org:
> tags 939937 + security upstream
Bug #939937 {Done: se...@debian.org (Steinar H. Gunderson)} [libapreq2-3]
Remotely exploitable null pointer dereference bug
Added tag(s) upstream and security.
> thanks
Stopping processing here.
Please contact me
Package: gnumed-client
Version: 1.7.7+dfsg-1
Followup-For: Bug #936630
Upstream (me) has py3 support available but it needs to be
polished and released.
Karsten
-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable-debug'), (500,
Your message dated Sun, 15 Sep 2019 19:34:08 +
with message-id
and subject line Bug#875168: fixed in radium-compressor 0.5.1+git20190909-1
has caused the Debian Bug report #875168,
regarding [radium-compressor] Future Qt4 removal from Buster
to be marked as done.
This means that you claim
Package: sdaps
Version: 1.9.7-0.1
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for sdaps (versioned as 1.9.7-0.2) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru sdaps-1.9.7/debian/changelog
Processing commands for cont...@bugs.debian.org:
> forwarded 940190 https://gitlab.gnome.org/GNOME/gegl/issues/206
Bug #940190 [src:gegl] gegl: FTBFS on mips64el and mipsel while it did built
before
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/gegl/issues/206'.
> thanks
Hi!
El dom., 15 sep. 2019 09:49, Jonas Smedegaard escribió:
> Quoting Lisandro Damián Nicanor Pérez Meyer (2019-09-12 23:54:32)
> > On Thu, 12 Sep 2019 at 17:37, Lisandro Damián Nicanor Pérez Meyer
> > wrote:
> > >
> > > On Mon, 30 Jul 2018 19:01:50 +0200 Reiner Herrmann
> wrote:
> > > >
Hello,
I have created a new upstream issue:
https://gitlab.gnome.org/GNOME/gegl/issues/206
Kind regards,
Bernhard
Yeah.. i am looking for a sponsor for my awesome package that us gathering dust at mentors.devian.net...
;)
https://mentors.debian.net/package/dmagnetic
Who else?
Jason Turner hat am 15. September 2019 um 15:35
Your message dated Sun, 15 Sep 2019 17:19:00 +
with message-id
and subject line Bug#855671: fixed in chaussette 1.3.0+git20170419+82ac44a-0.1
has caused the Debian Bug report #855671,
regarding FTBFS: chaussette incompatible with waitress 1.0, tests fail
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> severity 895520 serious
Bug #895520 [libunique-1.0-0] libunique-1.0-0: deprecated and unmaintained
upstream
Severity set to 'serious' from 'important'
> tags 895520 + bullseye sid
Bug #895520 [libunique-1.0-0] libunique-1.0-0: deprecated and
Your message dated Sun, 15 Sep 2019 17:04:36 +
with message-id
and subject line Bug#939937: fixed in libapreq2 2.13-6
has caused the Debian Bug report #939937,
regarding Remotely exploitable null pointer dereference bug
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 885135 serious
Bug #885135 [src:pygtk] pygtk: Unmaintained, use GObject Introspection instead
Bug #885752 [src:pygtk] pygtk: Unmaintained, should not be released with Debian
Severity set to 'serious' from 'important'
Severity set to
Processing commands for cont...@bugs.debian.org:
> severity 911166 serious
Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Bullseye
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
911166:
Hi,
So, I've uploaded python-fixtures with Python 2 support removed.
Now, it looks like python-fastimport is part of a dependency chain for
BZR. Since, as I wrote, BZR is probably going to be removed from Debian,
I'm not sure if we should fix python-fastimport or just get it removed
from Debian
Your message dated Sun, 15 Sep 2019 17:11:30 +0200
with message-id <87216c23-3f01-9085-9e34-eeb5c537e...@debian.org>
and subject line ACK, but let's go forward anyway
has caused the Debian Bug report #940283,
regarding Removing python-testtools breaks many packages
to be marked as done.
This
Package: matplotlib2
Version: 2.2.4-1
Severity: serious
matplotlib2 build-depends on python-cxx-dev, this package is no longer built by
the pycxx source package. It is still present in unstable as a cruft package,
but is completely gone from testing.
Le 14/09/2019 à 09:51, Gianfranco Costamagna a écrit :
> Hello, looks like the new zed made the package FTBFS
> [...]
> can you please have a look?
There is a new upstream release of lambda-term presumably fixing that.
Unfortunately, the new lambda-term depends on lwt >= 4 which depends on
ocaml
Hi,
Moritz Mühlenhoff a écrit le 13/09/2019 à 23:18 :
> 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:
Hello,
Jason here from Source Global Media - We are a reputed Digital Marketing
Agency working with variety of clients from UK, USA, France, Greece,
Finland, Germany and Spain
We are interested in developing partnerships with companies / webmaster
such as yourself to check if you can publish
Package: zope.testing
Version: 4.6.2-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/z/zope.testing/2966135/log.gz
autopkgtest [06:13:32]: test all: [---
Traceback (most recent call last):
File "/usr/bin/zope-testrunner", line 9, in
Package: zope.testrunner
Version: 4.4.9-3
Severity: serious
autopkgtest [06:13:47]: test all-2: [---
bash: /tmp/autopkgtest-lxc.v65a_j_9/downtmp/build.cMu/src/debian/tests/all-2:
/usr/bin/python: bad interpreter: No such file or directory
autopkgtest [06:13:47]: test all-2:
Package: neo
Version: 0.7.2-1
Severity: serious
The release team have decreed that non-buildd binaries can no longer migrate to
testing. Please make a source-only upload so your package can migrate.
Your message dated Sun, 15 Sep 2019 14:19:23 +0100
with message-id <8126cfaa-b7cc-5c94-363f-9705e8138...@p10link.net>
and subject line re: neo FTBFS: ValueError: ufunc %r not supported by quantities
has caused the Debian Bug report #877152,
regarding neo FTBFS: ValueError: ufunc %r not supported
[sent again, avoiding UTF-8 mail header upsetting Debian mailhost]
Quoting Lisandro Damián Nicanor Pérez Meyer (2019-09-12 23:54:32)
> On Thu, 12 Sep 2019 at 17:37, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> >
> > On Mon, 30 Jul 2018 19:01:50 +0200 Reiner Herrmann
> > wrote:
> > > Control:
Package: python3-osprofiler
Version: 2.6.0-1
Severity: grave
python3-osprofiler fails to install, I first noticed this in an autopkgtest,
but I was able to reproduce it in a local sid chroot too.
Setting up python3-osprofiler (2.6.0-1) ...
update-alternatives: error: alternative path
Processing commands for cont...@bugs.debian.org:
> severity 938804 serious
Bug #938804 [src:vtk6] vtk6: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938804:
Your message dated Sun, 15 Sep 2019 12:00:13 +
with message-id
and subject line Bug#934814: fixed in dballe 8.3-1
has caused the Debian Bug report #934814,
regarding libdballe7: built with libmariadbclient18, which doesn't exist any
longer
to be marked as done.
This means that you claim
Your message dated Sun, 15 Sep 2019 12:00:13 +
with message-id
and subject line Bug#853367: fixed in dballe 8.3-1
has caused the Debian Bug report #853367,
regarding dballe: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sun, 15 Sep 2019 12:00:13 +
with message-id
and subject line Bug#871272: fixed in dballe 8.3-1
has caused the Debian Bug report #871272,
regarding libdballe7: requires rebuild against GCC 7 and symbols/shlibs bump
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> # Do not depends on python-qt4
> close 935354 3.0.0-1
Bug #935354 [src:vitables] vitables: Qt4 removal from Bullseye
Marked as fixed in versions vitables/3.0.0-1.
Bug #935354 [src:vitables] vitables: Qt4 removal from Bullseye
Marked Bug as done
>
Processing commands for cont...@bugs.debian.org:
> fixed 940031 3.7-2
Bug #940031 {Done: Dmitry Smirnov } [src:gnucash-docs]
gnucash-docs_3.7-1_all.changes REJECTED
Marked as fixed in versions gnucash-docs/3.7-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Control: tags -1 + moreinfo
On Sat, Sep 14, 2019 at 11:54:53AM +0200, Julien Cristau wrote:
> Package: ircd-hybrid
> Version: 1:8.2.24+dfsg.1-1
> Severity: grave
>
> Hi,
>
> I just upgraded to buster and ircd keeps crashing.
> One case with a segfault in strcmp, other times with glibc aborts.
Processing commands for cont...@bugs.debian.org:
> reassign 940031 src:gnucash-docs 3.7-1
Bug #940031 {Done: Dmitry Smirnov } [src:gnucash]
gnucash-docs_3.7-1_all.changes REJECTED
Bug reassigned from package 'src:gnucash' to 'src:gnucash-docs'.
No longer marked as found in versions
Processing control commands:
> tags -1 + moreinfo
Bug #940230 [ircd-hybrid] ircd-hybrid: use after free and crash
Added tag(s) moreinfo.
--
940230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> reopen 925835
Bug #925835 {Done: Andreas Tille } [src:spoa] spoa: ftbfs
with GCC-9
Bug reopened
Ignoring request to alter fixed versions of bug #925835 to the same values
previously set
> merge 925835 940280
Bug #925835 [src:spoa] spoa: ftbfs
Processing commands for cont...@bugs.debian.org:
> tags 939899 + ftbfs
Bug #939899 [apitrace-tracers]
apitrace_7.1+git20170623.d38a69d6+repack-3+b4_mipsel.changes REJECTED
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
939899:
Package: src:python-testtools
Version: 2.3.0-6
Severity: serious
The current upload drops the python 2 packages, which are still used by e.g.
bzr and python-subunit, python-fixtures, python-testscenarios, python-daemon,
python-fastimport.
Processing control commands:
> severity -1 important
Bug #884516 [src:python-bayespy] python-bayespy: FTBFS and Debci failure on
several architectures
Severity set to 'important' from 'serious'
--
884516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884516
Debian Bug Tracking System
Control: severity -1 important
Arch:all packages are only required to build on amd64.
There are still autopkgtest failures on several architectures, which
are reproducible on the porterboxes, so downgrading the severity, but
leaving the bug open.
Source: spoa
Version: 3.0.0-1
Severity: serious
Tags: bullseye sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9
Hi Maintainer
As can be seen on reproducible builds [1], spoa FTBFS with GCC 9.
Common build failures are new warnings resulting in build failures
with -Werror turned on,
Sorry, copy/paste error and ended sending the mail unfinished.
On Sun, 15 Sep 2019 at 09:25, Graham Inggs wrote:
> As can be seen on reproducible builds [1], wham-align FTBFS with GCC 9.
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped
Source: wham-align
Version: 0.1.5-1
Severity: serious
Tags: bullseye sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9
Hi Maintainer
As can be seen on reproducible builds [1], wham-align FTBFS with GCC 9.
Regards
Graham
[1]
g++ -lpthread -o wham sequence.o hash.o embedhash.o
Your message dated Sun, 15 Sep 2019 07:05:01 +
with message-id
and subject line Bug#886779: Removed package(s) from unstable
has caused the Debian Bug report #914307,
regarding src:pyqwt5: Should not ship with buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 15 Sep 2019 07:05:01 +
with message-id
and subject line Bug#886779: Removed package(s) from unstable
has caused the Debian Bug report #787300,
regarding [pyqwt5] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 15 Sep 2019 07:05:01 +
with message-id
and subject line Bug#886779: Removed package(s) from unstable
has caused the Debian Bug report #787300,
regarding [pyqwt5] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> severity 782952 serious
Bug #782952 [python-pyramid-zcml] Please replace with a python3 module or
remove the package
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
61 matches
Mail list logo
