Package: mariadb-client-10.3
Version: 1:10.3.25-0+deb10u1
Severity: grave
Hello,
on start mytop a get:
[quote]
> mytop
/usr/bin/env: „perl -w“: Datei oder Verzeichnis nicht gefunden
/usr/bin/env: use -[v]S to pass options in shebang lines
[/quote]
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F
Control: reassign -1 googletest
Control: forcemerge 972618 -1
Control: reassign 972775 googletest
Control: forcemerge 972618 972775
Control: affects -1 src:ros-ros src:ros-rospack
Hi Doko,
* Matthias Klose [2020-10-23 12:07]:
ros-ros ftbfs with python3.9 (python3-defaults from experimental), n
On Fri, Oct 23, 2020 at 11:33:41AM +0200, Julien Cristau wrote:
> https://github.com/axboe/liburing/commit/25bbcbef3e0a8bfba8044be55d08d5116c51dccd
> seems to have bumped SONAME upstream.
That would fix it, yes, but it seems to have missed the kflags change
(the commit says all added padding is at
Package: src:zeroc-ice
Version: 3.7.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
zeroc-ice ftbfs with python3.9 (python3-defaults from experimental):
https://people.debian.org/~ginggs/python3.9-default/zeroc-ice_3.7.4-1build1_amd64-2020-10-23T0
Package: src:zbar
Version: 0.23.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
this looks like cython3 is not run during the build (python3-defaults from
experimental).
https://people.debian.org/~ginggs/python3.9-default/zbar_0.23.1-1build1_amd64
Package: src:vim
Version: 8.2.0716-3
Severity: important
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9
vim ftbfs with python3.9 (test failure), python3-defaults from experimental
Not sure if that's really related to 3.9:
https://people.debian.org/~ginggs/python
Package: src:talloc
Version: 2.3.1-1
Severity: serious
Tags: sid bullseye ftbfs
talloc ftbfs with python3.9 (python3-defaults from experimental). Looks like
hard-coding a specific python version.
https://people.debian.org/~ginggs/python3.9-default/talloc_2.3.1-1build1_amd64-2020-10-22T15:04:42Z.b
Package: needrestart
Version: 3.5-1
Followup-For: Bug #972685
On 10/22/20 8:16 PM, Thomas Liske wrote:
> Hi,
>
> thanks for the patch. Would it possible that you provide a updated patch
> compatible with upstream's git HEAD?
>
Hi,
You should be able to git am the patch attached to this mess
Control: tags -1 confirmed
Quoting Iustin Pop (2020-10-23 00:02:11)
> On 2020-10-10 13:34:16, Bernhard Übelacker wrote:
> > Dear Maintainer,
> > tried to have a look at this one, found the segfault [1],
> > and can point to the place where the pointer gets overwritten [2].
> > Unfortunately Valgri
Package: src:ros-rospack
Version: 2.6.2-1
Severity: serious
Tags: sid bullseye ftbfs
ros-rospack ftbfs with python3.9 (python3-defaults from experimental), not yet
convinced if that's related to python3.9, looks more like a googletest issue.
https://people.debian.org/~ginggs/python3.9-default/ros
Package: src:ros-ros
Version: 1.15.7-1
Severity: serious
Tags: sid bullseye ftbfs
ros-ros ftbfs with python3.9 (python3-defaults from experimental), not yet
convinced if that's related to python3.9, looks more like a googletest issue.
https://people.debian.org/~ginggs/python3.9-default/ros-ros_1.
Package: src:python-ciso8601
Version: 2.1.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
https://people.debian.org/~ginggs/python3.9-default/python-ciso8601_2.1.3-2build1_amd64-2020-10-22T13:38:30Z.build
packaging error, you are mixing b-d's pyt
Package: src:pybdsf
Version: 1.9.2-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
pybdsf ftbfs with python3.9 (python3-defaults from experimenal):
https://people.debian.org/~ginggs/python3.9-default/pybdsf_1.9.2-2build1_amd64-2020-10-22T13:21:38Z.b
Package: src:openstructure
Version: 2.1.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
openstructure ftbfs with python3.9 (python3-defaults from experimental), looks
like it still looks for 3.8
https://people.debian.org/~ginggs/python3.9-default/
Subject: libnss-nis: dist-upgrade buster to sid error
Package: libnss-nis
Version: 3.1-4
Severity: normal
Dear Maintainer,
When I try to upgrade from buster to sid, errors show that libc6 could not
be configured :
/usr/bin/apt-get dist-upgrade -y
...
... (no errors above)
...
Running hooks in /e
Package: src:libsigrokdecode
Version: 0.5.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
libsigrokdecode ftbfs with python3.9 (python3-defaults from experimental):
https://people.debian.org/~ginggs/python3.9-default/libsigrokdecode_0.5.3-1build1_
Package: src:kissplice
Version: 2.5.3-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
Not sure if that's python 3.9 specific (python3-defaults from experimental was
used). this ends up with a link error:
https://people.debian.org/~ginggs/python3.9-d
On Fri, Oct 23, 2020 at 10:47:57AM +0200, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 09:55:36AM +0200, Steinar H. Gunderson wrote:
> > If this were somehow only about newer functionality or critical fixes, it
> > could
> > be fixed by bumping the versioned dependency, but rhis goes both
Package: src:frr
Version: 7.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
frr ftbfs with python3.9 (python3-defaults from experimental)
https://people.debian.org/~ginggs/python3.9-default/frr_7.4-1build1_amd64-2020-10-21T08:19:46Z.build
[...]
Package: src:fontforge
Version: 1:20190801~dfsg-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
fontforge ftbfs with python3.9 (python3-defaults from experimental). There seem
to be two issues, 3.8 is used instead of 3.9, and d-shlibs isn't aware of
Package: d-shlibs
Version: 0.94
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
fontforge ftbfs with python3.9 (python3-defaults from experimental). There seem
to be two issues, 3.8 is used instead of 3.9, and d-shlibs isn't aware of 3.9.
https://pe
Package: src:cantor
Version: 20.04.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
cantor ftbfs with python3.9 (python3-defaults from experimental):
https://people.debian.org/~ginggs/python3.9-default/cantor_20.04.3-1build1_amd64-2020-10-22T21:44:
Control: severity -1 serious
Control: retitle -1 python-mpd: autopkgtest fails when two python3 versions are
supported
Control: tags -1 + patch pending
On Fri, 23 Oct 2020 at 15:31:24 +1300, Michael Hudson-Doyle wrote:
> I got confused and thought this package was maintained by the Python
> team
Package: src:bornagain
Version: 1.16.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
bornagain ftbfs with python3-defaults from experimental, ending up with a mix of
3.8 and 3.9.
https://people.debian.org/~ginggs/python3.9-default/bornagain_1.16.0
Package: src:bup
Version: 0.31-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
https://people.debian.org/~ginggs/python3.9-default/bup_0.31-1build1_amd64-2020-10-21T07:33:31Z.build
bup ftbfs with python3.9 (python3-defaults from experimental):
[...
On Fri, Oct 23, 2020 at 09:55:36AM +0200, Steinar H. Gunderson wrote:
> If this were somehow only about newer functionality or critical fixes, it
> could
> be fixed by bumping the versioned dependency, but rhis goes both ways; if you
> build plocate against liburing 0.6-3, and then upgrade liburin
Package: liferea
Version: 1.13.3-1
Severity: important
liferea in "copy link location" and "open link in external browser" link
conversion broke links.
On machine with UTF-8 locales link with latin2 (ISO-8859-2) encoded chars is
converted
from?szukaj=%AF%F3%B3ty%20dom
to ?szukaj=\Uf
Package: wnpp
Severity: wishlist
Owner: Nilesh Patra
X-Debbugs-CC: debian-de...@lists.debian.org
* Package name: golang-github-iafan-cwalk
Version : 0.0~git20191125.dd7f505-1
Upstream Author : Igor Afanasyev
* URL : https://github.com/iafan/cwalk
* License : Ex
Package: liburing1
Version: 0.7-1
Severity: grave
Tags: upstream
Hi,
I've had a number of reports from people who are having problems with plocate,
that can be traced to differing versions of liburing1. Specifically, plocate
is built in sid against liburing1 0.7-1 (which gets a versioned dependen
Package: wnpp
Severity: wishlist
Owner: Nilesh Patra
X-Debbugs-CC: debian-de...@lists.debian.org
* Package name: golang-github-smallfish-simpleyaml
Version : 0.0~git20170911.a320310-1
Upstream Author : 陈小玉
* URL : https://github.com/smallfish/simpleyaml
* License
Hi Paul,
Paul Wise wrote:
> On Fri, 2020-10-23 at 08:05 +0200, Axel Beckert wrote:
> > Ack. Just have to think how I make that separation properly. Either by
> > listing all supported previous release names (or maybe just those not
> > yet archived) and defaulting to the new scheme to be comaptibl
Package: gitlab
Version: 13.2.10-1+fto10+1
Severity: normal
Dear Maintainer,
After upgrading to version 13.2.10-1+fto10+1 I could no longer upload
images to issues in the issue tracker. A quick [search on the
internet][1] pointed me to a missing dependency on
`libimage-exiftool-perl`. Installing
Package: mousepad
Version: 0.4.2-1
Severity: wishlist
Tags: upstream
X-Debbugs-Cc: colomar.6@gmail.com
Dear Maintainer,
"find and replace" only allows replacing all of the appearances at once.
gedit has two buttons, one of them to replace all at once,
and the other to more carefully replace o
Control: found -1 3.20.5+dfsg0-3
Control: tags -1 +bullseye +upstream
Le vendredi, 16 octobre 2020, 14.23:59 h CEST Didier 'OdyX' Raboud a écrit :
> According to the 3.20.9-3 armhf auutopkgtest run for migration testing;
> https://ci.debian.net/data/autopkgtest/testing/armhf/h/hplip/7460676/log.gz
On 15/10 09:30, Baptiste Beauplat wrote:
> From what I can see on the package tracker, testinfra hasn't been very
> active packaging wise. No source upload have been done and the package
> hasn't migrated to testing, since 2019.
>
> I do believe that having testinfra in a Debian stable release wou
On Fri, 2020-10-23 at 08:05 +0200, Axel Beckert wrote:
> Ack. Just have to think how I make that separation properly. Either by
> listing all supported previous release names (or maybe just those not
> yet archived) and defaulting to the new scheme to be comaptible with
> all future releases.
Tha
101 - 136 of 136 matches
Mail list logo
