Your message dated Thu, 16 Apr 2020 05:48:46 +
with message-id
and subject line Bug#956527: fixed in numpy 1:1.18.2-1
has caused the Debian Bug report #956527,
regarding numpy: hardcodes python2 call into rules file
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Thu, 16 Apr 2020 05:48:46 +
with message-id
and subject line Bug#948354: fixed in numpy 1:1.18.2-1
has caused the Debian Bug report #948354,
regarding numpy: hardcodes python2 call into rules file
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Thu, 16 Apr 2020 05:48:46 +
with message-id
and subject line Bug#948354: fixed in numpy 1:1.18.2-1
has caused the Debian Bug report #948354,
regarding FTBFS: debian/rules still uses python(2) without havind an explicit
dependency
to be marked as done.
This means that you c
Your message dated Thu, 16 Apr 2020 05:48:46 +
with message-id
and subject line Bug#956527: fixed in numpy 1:1.18.2-1
has caused the Debian Bug report #956527,
regarding FTBFS: debian/rules still uses python(2) without havind an explicit
dependency
to be marked as done.
This means that you c
Your message dated Thu, 16 Apr 2020 01:35:07 -0400
with message-id
and subject line Re: Bug#952008: numpy: FTBFS: ./_configtest.c:6: undefined
reference to `exp'
has caused the Debian Bug report #952008,
regarding numpy: FTBFS: ./_configtest.c:6: undefined reference to `exp'
to be marked as done
Processing commands for cont...@bugs.debian.org:
> tags 952008 - patch
Bug #952008 [src:numpy] numpy: FTBFS: ./_configtest.c:6: undefined reference to
`exp'
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952008: https://bugs.debian.org/cgi-
Processing commands for cont...@bugs.debian.org:
> unmerge 952008
Bug #952008 [src:numpy] numpy: FTBFS: ./_configtest.c:6: undefined reference to
`exp'
Bug #948354 [src:numpy] numpy: hardcodes python2 call into rules file
Bug #956527 [src:numpy] FTBFS: debian/rules still uses python(2) without ha
Package: python3-adios
Version: 1.13.1-21+b2
Severity: serious
Justification: prevents package configuration
binNMU 1.13.1-21+b2 removed python3.7 builds, and seems to have broken
python3-adios:
Errors were encountered while processing:
python3-adios
E: Sub-process /usr/bin/dpkg returned an err
Source: ho22bus
Version: 0.9.1-2
Severity: serious
X-Debbugs-CC: cheny...@gmail.com
Dear Debian ho22bus maintainer,
After reviewing the ho22bus package [1] in Debian, I found that this package
saw no upload in the past 8 years. Currently its upstream project is also
defunct (previously hosted on
Your message dated Thu, 16 Apr 2020 01:03:39 +
with message-id
and subject line Bug#956790: fixed in gnome-screensaver 3.6.1-13
has caused the Debian Bug report #956790,
regarding gnome-screensaver: FTBFS with gnome-desktop3 (>= 3.36)
to be marked as done.
This means that you claim that the p
Your message dated Wed, 15 Apr 2020 23:35:59 +
with message-id
and subject line Bug#948789: fixed in racket 7.6+dfsg1-2
has caused the Debian Bug report #948789,
regarding racket ftbfs at least on armhf, and doesn't migrate
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 956829 serious
Bug #956829 [tumiki-fighters] tumiki-fighters: Crash with undefined symbol
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
956829: https://bugs.de
Your message dated Wed, 15 Apr 2020 22:04:15 +
with message-id
and subject line Bug#947532: fixed in gwaei 3.6.2-9
has caused the Debian Bug report #947532,
regarding gwaei: build-depends on deprecated gnome-doc-utils
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 15 Apr 2020 20:49:25 +
with message-id
and subject line Bug#956749: fixed in odil 0.12.0-2
has caused the Debian Bug report #956749,
regarding odil: FTBFS on mips64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not t
Your message dated Wed, 15 Apr 2020 20:50:01 +
with message-id
and subject line Bug#956587: fixed in texlive-bin 2020.20200327.54578-3
has caused the Debian Bug report #956587,
regarding texlive-binaries: needs Breaks/Replaces on older texlive-extra-utils
to be marked as done.
This means that
Your message dated Wed, 15 Apr 2020 22:35:11 +0200
with message-id <93dabcb8-684a-8297-210a-1b71ddcf0...@debian.org>
and subject line Re: Bug#956204: pdftk-java: pdftk Unsupported major.minor
version 52.0
has caused the Debian Bug report #956204,
regarding pdftk-java: pdftk Unsupported major.minor
Processing commands for cont...@bugs.debian.org:
> fixed 956204 pdftk-java/3.0.9-1
Bug #956204 [pdftk-java] pdftk-java: pdftk Unsupported major.minor version 52.0
Marked as fixed in versions pdftk-java/3.0.9-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
95620
On Tue, Apr 14, 2020 at 08:25:53PM +0300, Adrian Bunk wrote:
> On Sun, Mar 29, 2020 at 10:18:05PM +0200, Andrea Bolognani wrote:
> >...
> > Adrian, I see you tagged the bug as fixed-upstream: can you please
> > share any additional information you might have and that convinced
> > you the bug is no
A workaround is to start it with
python3 -m pympress file.pdf
It seems there is a conflict between python3.7 (used by default by pympress)
and python3.8 (used by most other programs).
Le 15/04/2020 à 11:15, Andreas Tille a écrit :
> Hi Julien,
>
> On Wed, Apr 15, 2020 at 10:19:11AM +0200, Julien Lamy wrote:
>> Following the build failures of Odil on mips64el (which never really
>> built correctly, due to timeouts), I'd like to remove the support for
>> mips64el. From what I've
Source: printrun
Version: 2.0.0~rc5-1
Severity: grave
Justification: FTBFS
X-Debbugs-CC: rockst...@gmx.com
Tags: patch
Dear Debian printrun maintainers,
The current printrun package FTBFS with python 3.8. As a result, it is
blocking the transition from python3.7 to python3.8.
Please consider fix
Package: pympress
Version: 1.5.1+dfsg-3
Severity: critical
Dear Maintainer,
After installing pympress, I try to run it and get the trace below. This makes
the package unusable.
Best,
C.
Traceback (most recent call last):
File "/usr/bin/pympress", line 11, in
load_entry_point('pympress
On Tue, Mar 31, 2020 at 03:55:42PM +0200, Andreas Tille wrote:
> On Tue, Mar 31, 2020 at 03:48:02PM +0200, Michael Crusoe wrote:
> >
> > I don't think dropping the 32bit archs is urgent right now.
>
> I'm happy if you have a better solution, Andreas.
I'm not sure what qualifies for "urgent" but
On 15 April 2020 at 20:44, Sebastian Ramacher wrote:
| Source: quantlib-swig
| Version: 1.18-1
| Severity: serious
| Tags: ftbfs sid bullseye
| Justification: fails to build from source (but built successfully in the past)
Yes ... but it also failed before. See e.g. #909725 (per a quick scan in
On Wed, 15 Apr 2020 at 19:06:59 +, Mike Gabriel wrote:
> On Mi 15 Apr 2020 10:49:03 CEST, Simon McVittie wrote:
> > I've done that for you.
>
> Thanks for that. What is the exact BTS query to list those bugs?
Sorry, I don't know the CLI for it, but I made them block 895037/895038
as appropri
Source: mysql-5.7
Version: 5.7.26-1
Severity: grave
Tags: security upstream
Justification: user security hole
Hi
See
https://www.oracle.com/security-alerts/cpuapr2020.html#AppendixMSQL
for a list of CVEs affecting src:mysql-5.7.
Regards,
Salvatore
Your message dated Wed, 15 Apr 2020 19:09:52 +
with message-id
and subject line Bug#956741: Removed package(s) from unstable
has caused the Debian Bug report #950343,
regarding golang-github-aanand-compose-file: build-depends on
golang-github-docker-engine-api-dev which has been requested to
Your message dated Wed, 15 Apr 2020 19:10:14 +
with message-id
and subject line Bug#902180: Removed package(s) from unstable
has caused the Debian Bug report #950348,
regarding golang-github-docker-engine-api: obsolete, incompatible with current
docker version
to be marked as done.
This mean
Your message dated Wed, 15 Apr 2020 19:06:11 +
with message-id
and subject line Bug#956743: Removed package(s) from unstable
has caused the Debian Bug report #950345,
regarding docker-swarm: build-depends on golang-github-docker-engine-api-dev
which has been requested to be removed
to be mark
Your message dated Wed, 15 Apr 2020 19:07:03 +
with message-id
and subject line Bug#956744: Removed package(s) from unstable
has caused the Debian Bug report #952349,
regarding golang-github-rsc-letsencrypt: FTBFS: dh_auto_build: error: cd
obj-x86_64-linux-gnu && go install -trimpath -v -p 1
Your message dated Wed, 15 Apr 2020 19:08:02 +
with message-id
and subject line Bug#956823: Removed package(s) from unstable
has caused the Debian Bug report #936760,
regarding jaxml: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dea
Hi Simon, hi Ivo,
I am currently drowned in customer requests. Sorry for the late reply.
On Mi 15 Apr 2020 10:49:03 CEST, Simon McVittie wrote:
> > To help the overview of what's still missing, it might be good to add
> > blocking
> > bugs for every package to this one.
It seems this wasn't
Your message dated Wed, 15 Apr 2020 19:06:11 +
with message-id
and subject line Bug#956743: Removed package(s) from unstable
has caused the Debian Bug report #861550,
regarding docker-swarm: FTBFS with latest golang-go.crypto
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 15 Apr 2020 19:05:51 +
with message-id
and subject line Bug#956742: Removed package(s) from unstable
has caused the Debian Bug report #907151,
regarding skydns: FTBFS in buster/sid (too many arguments in call to
activation.PacketConns)
to be marked as done.
This means
Source: insighttoolkit4
Version: 4.13.2-dfsg1-8
Severity: serious
https://salsa.debian.org/med-team/insighttoolkit/-/blob/master/debian/rules#L138
This line installs the Python extension always for Python 3.7. This
means the rebuilt for Python 3.8 installed the extensions incorrectly
and produced
close 956204 pdftk-java/3.0.9-1
thanks
This bug should be fixed by 3.0.9:
pdftk-java (3.0.9-1) unstable; urgency=medium
* New upstream version.
* Update Standards-Version to 4.5.0.
* debian/watch: Download .tar.gz file instead of .tar file.
-- Johann Felix Soden Wed, 15 Apr 2020 15:13:
Source: quantlib-swig
Version: 1.18-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
The last upload of quantlib-swig failed to build on mipsel:
https://buildd.debian.org/status/fetch.php?pkg=quantlib-swig&arch=mipsel&ver=1
Processing control commands:
> notfound -1 hedgewars/1.0.0-4
Bug #955416 {Done: Simon McVittie } [src:hedgewars] hedgewars:
FTBFS with newer SDL
No longer marked as found in versions hedgewars/1.0.0-4.
--
955416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955416
Debian Bug Tracking Syste
control: notfound -1 hedgewars/1.0.0-4
On Tue, 31 Mar 2020 14:48:06 +0200 Tobias Frost wrote:
> Source: hedgewars
> Severity: serious
> Justification: FTBFS
>
> Dear Maintainer,
>
> hedgewars is also affected by #951087, but it seems that no bug has been
> filed.
>
> The quoted bugs above has
Control: tags -1 upstream
Control: forwarded -1 https://github.com/igraph/igraph/issues/1370
Processing control commands:
> tags -1 upstream
Bug #956821 [src:igraph] igraph: FTBFS on arm64, armel, armhf, i386, mipsel,
ppc64el, s390x
Added tag(s) upstream.
> forwarded -1 https://github.com/igraph/igraph/issues/1370
Bug #956821 [src:igraph] igraph: FTBFS on arm64, armel, armhf, i386, mipse
Source: bedtools
Version: 2.27.1+dfsg-4
Severity: serious
Control: close -1 2.29.2+dfsg-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 955403
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
a
Processing control commands:
> close -1 2.29.2+dfsg-3
Bug #956828 [src:bedtools] src:bedtools: fails to migrate to testing for too
long: FTBFS on several archs
Marked as fixed in versions bedtools/2.29.2+dfsg-3.
Bug #956828 [src:bedtools] src:bedtools: fails to migrate to testing for too
long: F
Source: xpra
Version: 3.0.8+dfsg1-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
xpra failed to build on armel and armhf. See
https://buildd.debian.org/status/fetch.php?pkg=xpra&arch=armel&ver=3.0.8%2Bdfsg1-1&stamp=158687
Processing commands for cont...@bugs.debian.org:
> tags 956335 + sid
Bug #956335 [fretsonfire-game] depends on python-pil which is being removed in
bullseye (testing)
Added tag(s) sid.
> tags 956336 + sid
Bug #956336 [bkchem] depends on python-pil which is being removed in bullseye
(testing)
Add
Source: igraph
Version: 0.8.0-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
igraph failed to build almost everywhere. See
https://buildd.debian.org/status/package.php?p=igraph&suite=sid
Cheers
--
Sebastian Ramacher
s
Control: severity -1 important
Control: retitle -1 glom: ensure build with ocmpatible libpython and
libboost-python
On 2020-04-14 16:27:13 +0200, Giacomo Mulas wrote:
> Package: libglom-1.30-0
> Version: 1.30.4-6
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
Processing control commands:
> severity -1 important
Bug #956709 [libglom-1.30-0] libglom-1.30-0: upgrade of boost packages makes
libglom-1.30-0 uninstallable
Severity set to 'important' from 'grave'
> retitle -1 glom: ensure build with ocmpatible libpython and libboost-python
Bug #956709 [libglo
Your message dated Wed, 15 Apr 2020 17:53:52 +0100
with message-id <653e45a0-266e-a799-20f0-5b47b2058...@debian.org>
and subject line Fixed in 0.15.1-1
has caused the Debian Bug report #955079,
regarding python-xarray: FTBFS with Sphinx 2.4: ImportError: cannot import name
'main' from 'sphinx' (/u
Your message dated Wed, 15 Apr 2020 18:50:13 +0200
with message-id <58a6a61e-e72c-b977-ddb3-1a27213c3...@debian.org>
and subject line fixed
has caused the Debian Bug report #953711,
regarding src:autofdo: fails to migrate to testing for too long
to be marked as done.
This means that you claim that
Your message dated Wed, 15 Apr 2020 15:23:40 +
with message-id
and subject line Bug#956814: fixed in sprai 0.9.9.23+dfsg1-1
has caused the Debian Bug report #956814,
regarding sprai FTBFS:
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Wed, 15 Apr 2020 15:23:19 +
with message-id
and subject line Bug#950840: fixed in lxc-templates 3.0.4-2
has caused the Debian Bug report #950840,
regarding English India selected during installation breaks locale in lxc
to be marked as done.
This means that you claim that t
close 955668
thanks
Processing commands for cont...@bugs.debian.org:
> fixed 955668 0.15.1-10
Bug #955668 {Done: Pierre-Elliott Bécue } [src:libgaminggear]
libgaminggear: FTBFS: pango-coverage.h:28:10: fatal error: hb.h: No such file
or directory
Marked as fixed in versions libgaminggear/0.15.1-10.
> thanks
Stoppin
Processing commands for cont...@bugs.debian.org:
> close 955668
Bug #955668 [src:libgaminggear] libgaminggear: FTBFS: pango-coverage.h:28:10:
fatal error: hb.h: No such file or directory
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
955668: h
Processing commands for cont...@bugs.debian.org:
> reassign 952046 libsdl2-dev
Bug #952046 {Done: Simon McVittie } [src:mrboom] mrboom:
FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory
Bug reassigned from package 'src:mrboom' to 'libsdl2-dev'.
No longer marked as fou
Source: sprai
Version: 0.9.9.23+dfsg-3
Severity: serious
Tags: ftbfs patch
https://buildd.debian.org/status/package.php?p=sprai&suite=sid
...
make[1]: Entering directory '/<>'
chmod 766 bfmt72s nss2v_v3 myrealigner m52bfmt7 ca_ikki_v5.pl
ezez4makefile_v4.pl ezez4qsub_vx1.pl ezez_vx1.pl dumbbell_
Hi Sandro,
On Wed, Apr 15, 2020 at 09:41:27AM -0400, Sandro Tosi wrote:
> wait a second: i dont like this idea that DPMT/PAPT are a dumping
> ground you can throw away your packages you dont care about that much
> so that someone will take care of then.
I'm willing to care for team uploads for th
Source: snort
Version: 2.9.15.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=snort&suite=sid
...
checking for luajit... yes
checking openssl/x509.h usability... no
checking openssl/x509.h presence... no
checking for openssl/x509.h... no
ERROR! openssl/x509.h
wait a second: i dont like this idea that DPMT/PAPT are a dumping
ground you can throw away your packages you dont care about that much
so that someone will take care of then. we still require a human
maintainer behind the team name (either they be in Maintainer or
Uploaders, with the different mea
Your message dated Wed, 15 Apr 2020 15:24:12 +0200
with message-id
and subject line
has caused the Debian Bug report #955561,
regarding src:r-cran-rmarkdown: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hi Salsa admins,
please be so kind to transfer
https://salsa.debian.org/debian/logbook
to
https://salsa.debian.org/python-team/modules/logbook
Thanks a lot
Andreas.
On Wed, Apr 15, 2020 at 11:33:21AM +0200, Agustin Henze wrote:
> Hi Andreas, please go ahead and thank you :).
>
Your message dated Wed, 15 Apr 2020 11:49:56 +
with message-id
and subject line Bug#945729: fixed in zomg 0.8.1-2
has caused the Debian Bug report #945729,
regarding zomg: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Wed, Apr 15, 2020 at 06:29:18AM -0400, Jeremy Bicha wrote:
> python3-mutagen now contains mutagen-inspect.
Wonderful.
On Thu, 28 Nov 2019 00:26:15 + Clint Adams wrote:
> zomg has a weak dependency on /usr/bin/mutagen-inspect, which
> is expressed as a Recommends on python-mutagen. If
> mutagen-inspect is moved to python3-mutagen or another package,
> the Recommends can be adjusted accordingly.
python3-mutag
Processing commands for cont...@bugs.debian.org:
> # Sphinx 2.4 is now in unstable
> severity 955053 serious
Bug #955053 [src:scoop] scoop: FTBFS with Sphinx 2.4: Theme error: An error
happened in rendering the page index.
Severity set to 'serious' from 'important'
> severity 955054 serious
Bug #
Processing control commands:
> block 954422 by -1
Bug #954422 [release.debian.org] transition: GNOME 3.36
954422 was blocked by: 954659 956163 956166 956171 956162 956169 956170 956164
956168 954774 956147 956165 956167 956172
954422 was not blocking any bugs.
Added blocking bug(s) of 954422: 956
Source: gnome-screensaver
Version: 3.6.1-11
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: block 954422 by -1
Control: fixed -1 3.6.1-12
gnome-screensaver failed to build when binNMU'd against gnome-desktop3
3.36. This ap
Hi Andreas, please go ahead and thank you :).
Cheers,
On 4/14/20 11:16 AM, Inaki Malerba wrote:
> El 14/4/20 a las 10:43, Andreas Tille escribió:
>> Hi Agustin and Iñaki,
>>
>> I wonder whether you would like to maintain the logbook package in
>> Debian Python Modules team (by setting the mailing
Hi Julien,
On Wed, Apr 15, 2020 at 10:19:11AM +0200, Julien Lamy wrote:
> Following the build failures of Odil on mips64el (which never really
> built correctly, due to timeouts), I'd like to remove the support for
> mips64el. From what I've understood, I'll need to change the
> Architectures entr
Your message dated Wed, 15 Apr 2020 08:49:13 +
with message-id
and subject line Bug#956692: fixed in fparser 0.0.10-3
has caused the Debian Bug report #956692,
regarding fparser: depends on python3.7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
On Thu, 02 Apr 2020 at 14:11:42 +0200, Ivo De Decker wrote:
> On Mon, Oct 22, 2018 at 10:13:32AM +, Mike Gabriel wrote:
> > > # Broken Depends:
>
> [...]
>
> > The above list is irrelevant, what counts are the build-deps.
>
> Well, this was the output of dak rm. These dependencies need to be
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956778 956777 956771 956764 956765 956769 956770 956776
956772 921339 9060
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956771 956772 956770 956776 956778 956769 956767 956775
956764 906026 9567
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956776 956767 956770 956771 956769 956777 956766 956761
956772 956775 9567
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956777 906026 956762 956774 956766 956764 956776 956773
956772 956767 9567
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956771 956773 956761 906026 956764 956768 956774 956778
956772 956762 9567
Processing commands for cont...@bugs.debian.org:
> block 895037 with 921339
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956773 956775 956777 956774 956772 956766 956769
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956769 906026 956771 956761 956767 956766 956772 956770
956776 956762 9567
Hi,
> python-pbr (5.4.5-2) unstable; urgency=medium
> .
> * Uploading to experimental, fixing "cannot install" (Closes: #956736).
Just an FYI that the changelog entry claims "Uploading to
experimental" yet it appears to be actually targetting unstable.
Regards,
--
,''`.
: :' :
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956770 956768 956762 956766 956771 956774 956761 956764
956772 956773 9060
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956769 956773 956768 956770 956762 956767 956766 906026
956765 956771 9567
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956769 956765 956772 906026 956775 956762 956766 956761
956771 956767 9567
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956764 956769 906026 956770 956767 956761 956771 956766
956765 956768 9567
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956764 956769 956765 956762 956767 906026 956761 956766
956768
895037 was
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956770 956765 956771 956767 956768 906026 956761 956762
956766 956764 9567
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956767 956768 956766 956764 906026 956765 956770 956769
956762 956761
8950
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956765 956766 956762 906026 956761 956764
895037 was blocking: 895038
Added
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 906026 956767 956762 956766 956761 956765 956764
895037 was blocking: 89503
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956762 956766 956765 956764 956761 956767 956768 906026
895037 was blocking
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956762 906026 956761 956764
895037 was blocking: 895038
Added blocking bug(
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956764 956761 906026 956762 956765
895037 was blocking: 895038
Added blocki
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956762 906026 956761
895037 was blocking: 895038
Added blocking bug(s) of 8
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 906026 956761
895037 was blocking: 895038
Added blocking bug(s) of 895037:
Processing control commands:
> block 895037 by -1
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 906026
895037 was blocking: 895038
Added blocking bug(s) of 895037: 956761
Processing control commands:
> block 895038 by -1
Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to
libayatana-indicator instead
895038 was blocked by: 895037 956759
895038 was not blocking any bugs.
Added blocking bug(s) of 895038: 956760
--
895038: https://bugs.debi
Processing commands for cont...@bugs.debian.org:
> block 895038 with 906026
Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to
libayatana-indicator instead
895038 was blocked by: 956759 895037 956760
895038 was not blocking any bugs.
Added blocking bug(s) of 895038: 9060
Processing control commands:
> block 895038 by -1
Bug #895038 [src:libindicator] libindicator: deprecated in Debian, switch to
libayatana-indicator instead
895038 was blocked by: 895037
895038 was not blocking any bugs.
Added blocking bug(s) of 895038: 956759
--
895038: https://bugs.debian.org/
Processing commands for cont...@bugs.debian.org:
> block 895037 with 906026
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian;
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was not blocked by any bugs.
895037 was blocking: 895038
Added bl
Your message dated Wed, 15 Apr 2020 07:49:38 +
with message-id
and subject line Bug#956736: fixed in python-pbr 5.4.5-2
has caused the Debian Bug report #956736,
regarding python3-pbr: Uninstallable because of broken alternative
to be marked as done.
This means that you claim that the problem
1 - 100 of 105 matches
Mail list logo
