Package: python3-astroquery
Version: 0.3.10+dfsg-1
Severity: serious
Tags: patch
Dear maintainers,
The new astropy 4.0 is in Debian unstable now. However, astroquery now
fails the CI tests and is therefore preventing astropy from migration.
As stated in [1], this is probably only a testing
Processing commands for cont...@bugs.debian.org:
> block 944227 by 948397
Bug #944227 [release.debian.org] transition: prompt-toolkit
944227 was blocked by: 944542
944227 was blocking: 887101 942660
Added blocking bug(s) of 944227: 948397
>
End of message, stopping processing here.
Please
Source: python-softlayer
Severity: serious
Justification: Policy 7.4
Control: blocks 944227 -1
Dear Maintainer,
prompt-toolkit has been updated to the 2.x series. The current version
of python-softlayer requires prompt-toolkit 1, and was added to the
Breaks: list for prompt-toolkit 2.0.10.
This
Your message dated Wed, 08 Jan 2020 06:35:32 +
with message-id
and subject line Bug#947730: fixed in rdflib 4.2.2-3
has caused the Debian Bug report #947730,
regarding rdflib: Build-Depends on python-rdflib-jsonld
to be marked as done.
This means that you claim that the problem has been
Hi !
this is blocking migration of libglvnd from 1.1.0-1 to 1.3.0-5, which in turn
is blocking migration of qtbase-opensource-src from 5.12.5+dfsg-2 to
5.12.5+dfsg-5, which in turn is blocking doxygen (that's where this hits me !).
I have verified that libgl-dev 1.3.0-5 indeed breaks the 3depict
I am Miss Joy Williams .My father was a wealth Merchant and He died the
year 2018 after a brief Illness. He has left 2.2 Million US Dollars ,
which I am ready to move through you. I am 23 years old . I am very
interested with you and I want us to do business together. If you can work
with me and
On Fri, 4 Mar 2016 12:51:53 -0400 David =?iso-8859-1?Q?Pr=E9vot?=
wrote:
> I packaged php-pimle as used by owncloud, but owncloud is going away,
> see #816376. There is a priori little point to ship php-pimple in a
> stable Debian release.
>
> I intend to follow up with an RM request in a few
Your message dated Tue, 7 Jan 2020 17:54:34 -0800
with message-id <20200108015434.ga26...@ofb.net>
and subject line Re: gromacs: FTBFS on several architectures
has caused the Debian Bug report #943650,
regarding gromacs: FTBFS on several architectures
to be marked as done.
This means that you
Processing control commands:
> forwarded -1
> https://lore.kernel.org/lkml/d05aba2742ae42783788c954e2a380e7fcb10830.ca...@scientia.net/
Bug #945055 [linux] linux: CPU runs at considerably higher temperatures
Set Bug forwarded-to-address to
Control: forwarded -1
https://lore.kernel.org/lkml/d05aba2742ae42783788c954e2a380e7fcb10830.ca...@scientia.net/
Hey.
I've forwarded this to lkml.
My most recent post in that thread[0] contains an pretty elaborate test
series comparing kernel 5.2 vs. 5.4 (each with intel_pstate=disable and
Source: pykaraoke
Severity: grave
Tags: patch
Justification: renders package unusable
If I run pykaraoke_mini to play .kar file, it return:
>>>pykaraoke_mini
pygame 1.9.4.post1
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
File
Your message dated Wed, 08 Jan 2020 01:04:58 +
with message-id
and subject line Bug#948215: fixed in jekyll 3.8.3+dfsg-7
has caused the Debian Bug report #948215,
regarding FTBFS after ruby-i18n has been updated to version 1.x
to be marked as done.
This means that you claim that the problem
Hi all,
since python2.7 is back in boost-python and my shlibs patch is in, too,
I've requested a "transition" to get the binNMUs done to tighten the
boost-python dependencies: https://bugs.debian.org/948378
Andreas
Hi,
Today I have finally been working on this. The result is that I at least
have a new (WIP) version for buster. I'm running it on a dom0 right now
and did smoke testing, live migrate, restarting domUs etc. It just works
(tm).
This was the easy part, most of the work was assembling the
> I'm in a hurry right now, I will try to file it tomorrow, but please go ahead
> if you have time, no need to wait and thanks for pushing this!
I've reassigned this bug to ftp.d.o -- thanks!
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian:
Processing commands for cont...@bugs.debian.org:
> reassign 948162 ftp.debian.org
Bug #948162 [src:python-peak.util] python-peak.util: should this package be
removed?
Bug reassigned from package 'src:python-peak.util' to 'ftp.debian.org'.
No longer marked as found in versions
Your message dated Tue, 7 Jan 2020 22:02:52 +
with message-id
and subject line re: freedv ftbfs with libcodec2-0.9
has caused the Debian Bug report #947620,
regarding freedv ftbfs with libcodec2-0.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> found 947998 0.6.1~ds1-4
Bug #947998 [src:notary] notary FTBFS in testing/unstable
Ignoring request to alter found versions of bug #947998 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need
On Tue, 7 Jan 2020 13:43:29 +0100 =?UTF-8?Q?Christian_G=C3=B6ttsche?=
wrote:
> Unpacking fonts-noto-core (20200103-1) over (20181227-1) ...^M
> ^[[1mdpkg:^[[0m error processing archive
> /tmp/apt-dpkg-install-jG8reX/16-fonts-noto-core_20200103-1_all.deb
> (--unpack):^M
> trying to overwrite
>
Your message dated Tue, 07 Jan 2020 21:50:05 +
with message-id
and subject line Bug#936729: fixed in imgsizer 2.10-0.1
has caused the Debian Bug report #936729,
regarding imgsizer: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Package: python3-nibabel
Version: 2.5.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy
Source: ruby2.7
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hello!
ruby2.7 fails to build from source on multiple architectures due to
mismatched symbols files:
- armel
- armhf
- i386
- mips64el
- mipsel
- s390x
- m68k
- ppc64
- sparc64
Architectures not listed
Hi Maintainer,
At this moment, I built chromium packages from chromium-79.0.3945.93-
lite.tar.xz in https://gsdview.appspot.com/chromium-browser-official
according to Eloston's method, but WITHOUT APPLYING HIS PATCH, just for
testing. The chromium-79.0.3945.93 is the latest version of chromium
Hello Sandro,
On Sat, Jan 04, 2020 at 03:03:59PM -0500, Sandro Tosi wrote:
> Source: python-peak.util
> Severity: serious
>
> Hello,
> this package recently became a leaf pkg and it's currently python2-only;
> looking
> at how it's made of, it appears it's a combination of modules:
>
>
>
Package: fw4spl
Version: 17.2.0-2
Severity: serious
Tags: bullseye sid
fw4spl seems to be replaced by sight,
should this package get removed?
Source: sight
Version: 19.0.0-3
Severity: serious
Tags: ftbfs
sight build depends on the renamed libvtk7.1-qt,
the build dependency on libvtk7-qt-dev alone
should be sufficient.
Your message dated Tue, 07 Jan 2020 20:49:31 +
with message-id
and subject line Bug#947969: fixed in ceph 14.2.5-3
has caused the Debian Bug report #947969,
regarding ceph-mgr: indefinite queue growth causing commands to hang
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 07 Jan 2020 15:38:15 -0500
with message-id <8f5ae32a7a131d834b3ad8a7a44005ef25393dd0.ca...@debian.org>
and subject line Bug#915151: No longer affect gnulib >= 20180305
has caused the Debian Bug report #915151,
regarding gnulib does not work with glibc/2.28
to be marked as
Your message dated Tue, 07 Jan 2020 15:38:15 -0500
with message-id <8f5ae32a7a131d834b3ad8a7a44005ef25393dd0.ca...@debian.org>
and subject line Bug#915151: No longer affect gnulib >= 20180305
has caused the Debian Bug report #915151,
regarding lbzip2 FTBFS with glibc 2.28
to be marked as done.
Package: audacity
Version: 2.3.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
On my system, audacity seems to be leaking memory during playback. To reproduce,
record anything, then play it repeatedly, or in a loop (Maj+play). The memory
usage of audacity in top
Your message dated Tue, 07 Jan 2020 20:00:16 +
with message-id
and subject line Bug#946951: fixed in wine 5.0~rc1-2
has caused the Debian Bug report #946951,
regarding can't start wine: chdir to /run/user/1000/wine/server-805-14c0be6 :
No such file or directory
to be marked as done.
This
Your message dated Tue, 07 Jan 2020 20:00:16 +
with message-id
and subject line Bug#946939: fixed in wine 5.0~rc1-2
has caused the Debian Bug report #946939,
regarding wine: no longer builds wine-binfmt and fonts-wine packages
to be marked as done.
This means that you claim that the problem
Control: severity -1 important
Hi Andreas,
On 07-01-2020 08:38, Andreas Tille wrote:
> I've uploaded 2.5.1+dfsg-2 with more debug infor in the autopkgtest. Since
> this
> the tests are passing again as you can check from
>
>
Processing control commands:
> severity -1 important
Bug #948093 [src:hyphy] hyphy: autopkgtest regression: Duplicate analysis
keyword
Severity set to 'important' from 'serious'
--
948093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948093
Debian Bug Tracking System
Contact
Hi,
On 07.01.20 08:56, Martin Pitt wrote:
Ken and Andreas, this would mean we set Debian8 (and the equivalent
Ubuntu release) as the minimum required for Makepkgs builds. Would
that be a problem for anyone? It turns out that was the first Debian that
used systemd as the init system, so
Your message dated Tue, 07 Jan 2020 19:19:14 +
with message-id
and subject line Bug#944742: fixed in assimp 5.0.0~ds2-4.1
has caused the Debian Bug report #944742,
regarding assimp: testsuite regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 07 Jan 2020 19:19:48 +
with message-id
and subject line Bug#937936: fixed in python-mysqldb 1.4.4-2
has caused the Debian Bug report #937936,
regarding python-mysqldb: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 8 Jan 2020 03:06:09 +0800
with message-id
and subject line Closing old bugs when docker.io depends extra containerd
package
has caused the Debian Bug report #863248,
regarding containerd 0.2.3+git20170126.85.aa8187d~ds1-1: container not started
(docker.io 1.13.0~ds1-3)
Your message dated Wed, 8 Jan 2020 03:06:09 +0800
with message-id
and subject line Closing old bugs when docker.io depends extra containerd
package
has caused the Debian Bug report #855922,
regarding containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start
containerd
to be marked as done.
Processing control commands:
> tag -1 pending
Bug #944742 [src:assimp] assimp: testsuite regression
Added tag(s) pending.
--
944742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #944742 in assimp 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 Tue, 07 Jan 2020 19:00:15 +
with message-id
and subject line Bug#948167: fixed in plplot 5.15.0+dfsg-10+gnat8+1
has caused the Debian Bug report #948167,
regarding plplot: autopkgtest regression on arm64:
/usr/lib/x86_64-linux-gnu/libm.so: No such file or directory
to be
Processing control commands:
> tag -1 pending
Bug #937936 [src:python-mysqldb] python-mysqldb: Python2 removal in sid/bullseye
Added tag(s) pending.
--
937936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #937936 in python-mysqldb 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 commands for cont...@bugs.debian.org:
> forwarded 936632 https://gitlab.gnome.org/GNOME/gnumeric/issues/419
Bug #936632 [src:gnumeric] gnumeric: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/gnumeric/issues/419'.
> # upstream won't fix
Your message dated Wed, 8 Jan 2020 02:38:59 +0800
with message-id
and subject line New containerd version is uploaded
has caused the Debian Bug report #857819,
regarding FTBS: Missing b-d on golang-golang-x-sys-dev &&
golang-github-docker-go-connections-dev
to be marked as done.
This means
Your message dated Wed, 8 Jan 2020 02:38:59 +0800
with message-id
and subject line New containerd version is uploaded
has caused the Debian Bug report #943652,
regarding containerd: FTBFS in experimental - some tests fail
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 8 Jan 2020 02:38:59 +0800
with message-id
and subject line New containerd version is uploaded
has caused the Debian Bug report #923431,
regarding containerd: unsatisfiable build dependencies
to be marked as done.
This means that you claim that the problem has been dealt
On Tue, 7 Jan 2020 18:34:06 +0100 Gianfranco Costamagna
wrote:
> Source: numpy
> Version: 1:1.17.4-5
> Severity: serious
> tags: patch
>
> Hello, looks like there still is a python2 call in rules file, making the
> package FTBFS where python2 is not installed anymore
>
> possible patch:
>
>
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Source: numpy
Version: 1:1.17.4-5
Severity: serious
tags: patch
Hello, looks like there still is a python2 call in rules file, making the
package FTBFS where python2 is not installed anymore
possible patch:
diff -Nru numpy-1.17.4/debian/changelog numpy-1.17.4/debian/changelog
---
Hi Maintainer,
A few days ago, I built chromium according to the way of Eloston's,
too. But I also needed to slightly modify Eloston's patch to finish to
compile whole chromium source. I attached my version of the patch to
this report.
Until now, I'm testing this version of chromium by usual
Processing control commands:
> severity -1 important
Bug #855908 [src:hiro] hiro: FTBFS: test_segment_not_complete_error [...]
AssertionError: False is not true
Severity set to 'important' from 'serious'
--
855908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855908
Debian Bug Tracking
Control: severity -1 important
On Wed, Apr 25, 2018 at 03:31:58AM +0200, Nicolas Dandrimont wrote:
> Control: reopen -1
> Control: found -1 0.5-1
>
> Seems that hiro still FTBFS in the reproducible-builds test environment. Ugh
> timezones.
>...
It buildds on the buildd, which is what matters
Processing commands for cont...@bugs.debian.org:
> severity 936541 serious
Bug #936541 [src:fonts-rit-sundar] fonts-rit-sundar: Python2 removal in
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936541:
Control: tags 947514 + patch
Control: tags 947514 + pending
Dear maintainer,
I've prepared an NMU for midori (versioned as 7.0-2.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Since midori v0.5.6, it has migrated away from libunique. As a result, this
Processing control commands:
> tags 947514 + patch
Bug #947514 [src:midori] midori: build-depends on obsolete libunique-dev
Added tag(s) patch.
> tags 947514 + pending
Bug #947514 [src:midori] midori: build-depends on obsolete libunique-dev
Added tag(s) pending.
--
947514:
Your message dated Tue, 07 Jan 2020 16:19:20 +
with message-id
and subject line Bug#947822: fixed in geeqie 1:1.5.1-6
has caused the Debian Bug report #947822,
regarding geeqie: file conflict with older geeqie-common
to be marked as done.
This means that you claim that the problem has been
Hello,
Andreas Tille, le lun. 18 févr. 2019 10:45:59 +0100, a ecrit:
> On Mon, Feb 18, 2019 at 06:45:55AM +, Mo Zhou wrote:
> > pkg-config file has been marked deprecated by upstream.
>
> I admit I have no idea what to do now. Any hint?
Apparently there is a opencv4.pc file?
Samuel
Processing control commands:
> tags -1 + patch
Bug #947822 [geeqie] geeqie: file conflict with older geeqie-common
Added tag(s) patch.
--
947822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
On 2020-01-07 20:03 +0800, Paul Wise wrote:
> Control: reopen -1
> Control: found -1 1:1.5.1-5
> Control: notfixed -1 1:1.5.1-4
> Control: usertags -1 + bittenby
>
> On Tue, 7 Jan 2020 10:51:14 + Tomas Janousek wrote:
>
>> I don't think this is fixed, I got the same
On Tue, Jan 7, 2020 at 9:22 AM Peter Green wrote:
> have either of you tested 0.7.0 on a Pi running Debian arm64
Yes, v0.7.0 (from pypi.org) works fine here on Debian arm64.
Cheers,
Andre'
Your message dated Tue, 07 Jan 2020 13:18:20 +
with message-id
and subject line Bug#933459: fixed in pgadmin3 1.22.2-6
has caused the Debian Bug report #933459,
regarding pgadmin3: Please rebuild against wxWidgets GTK 3 package
to be marked as done.
This means that you claim that the problem
On 07/01/2020 08.56, jim_p wrote:
> First of all, thank you for fixing the issue. It is really nice to have a
> working nvidia driver again.
Thanks for confirming that this was the issue.
> Given the fact that nvidia itself did not actually support 340.x from kernels
> 5.0 to 5.4, all released
Hi,
I can also reproduce the crashes (segfaults) on two different machines.
The version is 79.0.3945.79-1
This makes chromium essentially unusable.
Regards,
--
Antoine Amarilli
signature.asc
Description: PGP signature
Package: fonts-noto-core
Version: 20200103-1
Severity: serious
On package upgrade dpkg complained:
Unpacking fonts-noto-core (20200103-1) over (20181227-1) ...^M
^[[1mdpkg:^[[0m error processing archive
/tmp/apt-dpkg-install-jG8reX/16-fonts-noto-core_20200103-1_all.deb
(--unpack):^M
trying to
Processing commands for cont...@bugs.debian.org:
> found 933459 1.22.2-5
Bug #933459 [pgadmin3] pgadmin3: Please rebuild against wxWidgets GTK 3 package
Marked as found in versions pgadmin3/1.22.2-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933459:
Control: reopen -1
Control: found -1 1:1.5.1-5
Control: notfixed -1 1:1.5.1-4
Control: usertags -1 + bittenby
On Tue, 7 Jan 2020 10:51:14 + Tomas Janousek wrote:
> I don't think this is fixed, I got the same error as Sven when updating from
> 1:1.5.1-2 to 1:1.5.1-5:
>
> ...
>
Your message dated Tue, 07 Jan 2020 12:04:26 +
with message-id
and subject line Bug#947371: fixed in dpdk 19.11-2
has caused the Debian Bug report #947371,
regarding dpdk: FTBFS during indep-only build
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> reopen -1
Bug #947822 {Done: Andreas Rönnquist } [geeqie] geeqie: file
conflict with older geeqie-common
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No
Control: tag -1 pending
Hello,
Bug #947371 in dpdk 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/debian/dpdk/commit/20fb7c12a234d4f76aa38632c8f96aed98023c99
Processing control commands:
> tag -1 pending
Bug #947371 [src:dpdk] dpdk: FTBFS during indep-only build
Ignoring request to alter tags of bug #947371 to the same tags previously set
--
947371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947371
Debian Bug Tracking System
Contact
Package: bioperl-run
Version: 1.7.3-2
Severity: serious
bioperl-run: Depends: libbio-tools-run-alignment-clustalw but it is not
installable
Was the dependency intended on libbio-tools-run-alignment-clustalw-perl?
Hi Andreas,
On Tue, Dec 31, 2019 at 05:03:10PM +, Debian Bug Tracking System wrote:
> [...]
> We believe that the bug you reported is fixed in the latest version of
> geeqie, which is due to be installed in the Debian FTP archive.
> [...]
I don't think this is fixed, I got the same error as
Your message dated Tue, 07 Jan 2020 10:44:14 +
with message-id <871rsbfsw1@zephyr.silentflame.com>
and subject line Fixed in latest upload
has caused the Debian Bug report #912092,
regarding impass FTBFS: FAIL decrypt db
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 07 Jan 2020 10:34:18 +
with message-id
and subject line Bug#947828: fixed in freedv 1.4-1.1
has caused the Debian Bug report #947828,
regarding freedv FTBFS on most architectures, unconditionally uses x86 asm for
avx detection.
to be marked as done.
This means that
Package: dh-python
Version: 4.20191017
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8
pybuild reads:
if arch_data['DEB_BUILD_ARCH'] != arch_data['DEB_HOST_ARCH']:
# support cross compiling Python 3.X extensions, see #892931
After consulting with upstream (who approved my patch and said they intend to
apply it upstream) I have gone ahead with the NMU. Final debdiff is attached.
diff -Nru freedv-1.4/debian/changelog freedv-1.4/debian/changelog
--- freedv-1.4/debian/changelog 2019-11-18 03:32:07.0 +
+++
Your message dated Tue, 07 Jan 2020 10:19:21 +
with message-id
and subject line Bug#933775: fixed in dnsviz 0.8.0-1.1
has caused the Debian Bug report #933775,
regarding dnsviz: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 07 Jan 2020 10:19:21 +
with message-id
and subject line Bug#933775: fixed in dnsviz 0.8.0-1.1
has caused the Debian Bug report #933775,
regarding dnsviz: Switch to Python 3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: dh-python
Version: 4.20191017
Severity: serious
Tags: sid bullseye patch
Fix setting _PYTHON_HOST_PLATFORM, amd64 is not what Python expects. It's
x86_64. Causes python-packaging's tests to fail.
Processing commands for cont...@bugs.debian.org:
> severity 945456 normal
Bug #945456 [xul-ext-torbirdy] xul-ext-torbirdy: Torbirdy is incompatible with
Thunderbird > 60
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> forwarded 947004 https://github.com/Bioconductor/S4Vectors/issues/57
Bug #947004 [r-bioc-s4vectors] Tests segfaults (since the r-base-core update?)
Changed Bug forwarded-to-address to
'https://github.com/Bioconductor/S4Vectors/issues/57' from
Package: openssh-server
Version: 1:8.1p1-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrading openssh-server from version 8.1p1-1 to version 8.1p1-2, using
the apt command line tool, the sshd service failed on restart. Please see below
the corresponding
It seems it is necessary to cherry pick change 129:03be41933c1b from
upstream.
While that would certainly be a possible route, i'm not sure it makes much
sense, at least for testing/unstable.
I don't have a Pi running Debian bullseye/sid arm64 handy, have either of you
tested 0.7.0 on a Pi
Your message dated Tue, 07 Jan 2020 08:50:57 +
with message-id
and subject line Bug#945697: fixed in mariadb-10.3 1:10.3.21-2
has caused the Debian Bug report #945697,
regarding mariadb-10.3: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> close 944653 1.31-1
Bug #944653 [src:ofono] ofono: FTBFS on arm64, armel, armhf, ppc64el, s390x
Marked as fixed in versions ofono/1.31-1.
Bug #944653 [src:ofono] ofono: FTBFS on arm64, armel, armhf, ppc64el, s390x
Marked Bug as done
> thanks
close 944653 1.31-1
thanks
Hey,
This seems fixed in 1.31-1
Closing
Hello Nathan,
Nathan Scott [2020-01-07 11:18 +1100]:
> Thanks for looking into this issue while we were all off, Martin and Sunil!
>
> To summarise where I understand things are at now: Martin's uploaded
> a pcp package for rebuild which drops the python2 build steps. I think
> this is fine and
Package: nvidia-legacy-340xx-driver
Followup-For: Bug #948195
First of all, thank you for fixing the issue. It is really nice to have a
working nvidia driver again.
Second, I read this in the news file
The 340.xx legacy driver series has been declared as End-of-Life by
NVIDIA. No further
90 matches
Mail list logo
