meanwhile, feel free to clone my repo and build
the patched version yourself.
Glad I could help,
Ondrej Behal
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.22-amd64 (SMP w/2 CPU thread
"ALWAYS_SET_PATH no" >> /etc/default/runuser
# runuser -u gitlab -- sh -c 'echo $PATH'
/usr/share/gitlab/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/.local/bin
--
Ondrej Zary
Hello,
Indeed if you just change the evdi version to 1.14.6 in
https://salsa.debian.org/debian/evdi and then build the deb (e.g. via
`dpkg-buildpackage -uc -us`) and install it, then the module gets built
for the latest kernels OK.
Best Regards,
Ondrej P.
Hello,
Can this be finally fixed please? It's going on for almost a month now
and it should be as simple as bumping `evdi` to 1.14.5 (see
https://github.com/DisplayLink/evdi/issues/469 ) - as celel...@gmail.com
already mentioned.
Best Regards,
Ondrej P.
Package: gitlab
Version: 16.11.6-3~bpo12+1
Severity: important
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
upgrading failed because cssbundling-rails tries to run 'yarn" which is not in
PATH.
Workaround: ln -s /usr/share/nodejs/yarn/bin/yarn /usr/bin/yarn
rake aborted!
cssbundling-rails: Comm
Package: gitlab
Version: 16.11.6-3~bpo12+1
Severity: important
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
upgrading failed because of missing g++. Maybe it should be included in
dependencies?
warning Error running install script for optional dependency:
"/var/lib/gitlab/node_modules/tree-si
Package: dovecot-fts-xapian
Version: 1.5.5-1+b2
Severity: important
Tags: upstream
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
dovecot-fts-xapian crashes with "Memory too low (text) 'std::bad_alloc'" error
when indexing large mailboxes.
I've compiled and tested 1.7.8 and 1.7.9 but it's not ge
Package: gitlab
Version: 16.4.4+ds2-3~fto12+1
Severity: normal
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
since upgrading from 16.2.8+ds1-6~fto12+1 to 16.4.4+ds2-3~fto12+1, sidekiq
check of "gitlab-rake gitlab:check" always fails becacuse it finds two cluster
processes instead of just one. It'
Package: gitlab
Version: 16.4.4+ds2-2~fto12+4
Severity: important
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
upgrading gitlab from 16.2.8+ds1-6~fto12+1 to 16.4.4+ds2-2~fto12+4 failed
during gitlab:check phase. There were about 60 sidekiq processes running,
eating all the memory and causing OOM
Package: php-horde-imp
Version: 6.2.27-3
Severity: grave
Tags: upstream
Justification: renders package unusable
Followup-For: Bug #1038441
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
the bug severity should be grave as Horde IMP web UI does not work at all.
Quick fix below, but there are more
Package: php-net-dns2
Version: 1.5.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
after upgrading to Debian 12, Horde stopped working. It logs messages like:
PHP Fatal error: Uncaught ValueError: fread(): Argument #2 ($len
Source: cyrus-sasl2
Severity: normal
X-Debbugs-Cc: on...@mistotebe.net
Dear Maintainer,
now that MD5 support is being phased out from all crypto libraries (and
more generally), DIGEST-MD5 is going to disappear from cyrus-sasl. Its
replacement the SCRAM family of SASL mechanisms is however not bein
to determine what might be wrong.
Thanks,
Best Regards,
Ondrej Pirko
-- Package-specific info:
** Version:
Linux version 6.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06
Package: apcupsd
Version: 3.14.14-3.1+b1
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: li...@rainbow-software.org
Dear Maintainer,
there are old bugs in apcupsd preventing it from getting almost any data from
SmartUPS v/s 650:
# apcaccess
APC : 001,018,0451
DATE : 2023-07-02 19:43:
I'm using another workaround - /etc/rsyslog.d/filter-gitlab.conf file
containing:
:programname, isequal, "gitlab-sidekiq" stop
--
Ondrej Zary
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: normal
X-Debbugs-Cc: z...@gsystem.sk
Dear Maintainer,
after upgrading gitlab to 15.4.2, gitlab-sidekiq is spamming logs like this:
gitlab-sidekiq[311326]: Passing the timeout as a positional argument is
deprecated, it should be passed as a
Hi Julien,
after security update of rsync rpm package on our mirror server, ftpsync was
unable to talk to our upstream repo. We downgraded the package and will check
the situation. Ftpsync works for now.
--
Bc. Ondrej Filip
IT4Innovations
Vysoká škola báňská - Technical University Ostrava
Package: firefox-esr
Version: 91.4.1esr-1~deb11u1
Severity: important
File: /usr/bin/firefox
X-Debbugs-Cc: t...@security.debian.org
Dear Maintainer,
after upgrading firefox-esr from 78.15.0esr-1 to 91.4.1esr-1, it can't open
any web page. The tab crashes immediately, with errors like this in dmesg
On Friday 22 October 2021, Yves-Alexis Perez wrote:
> On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote:
> > MDEV-15912: Remove traces of insert_undo
> >
> > Let us simply refuse an upgrade from earlier versions if the
> > upgrade procedure was not fo
dff451f0a7a6d6246334aace697b230b4174f2c1 M mysql-test
:04 04 4a0352d498b9487cae46c6363d86603de0ccb361
3e6aa2377e89f28192e987f2f8655e3d866ab4be M storage
--
Ondrej Zary
Tested upstream mariadb packages. 10.3.30 works, 10.3.31 fails.
--
Ondrej Zary
OR] Unknown/unsupported storage engine: InnoDB
> 2021-10-14 9:38:49 0 [ERROR] Aborting
>
> So maybe I do have a corrupted database or something but I'm unsure what to do
> next (I don't think I have an older backups of the database). Also it still
> works just fine with 10.3.25.
I still get the error too. That patch was meant to fix a problem specific to
BSD.
--
Ondrej Zary
e1), then shutdown ended
immediately. Seems that the file structure is corrupted somehow - probably
because of a previous bug. One table is also affected by the "ERROR 1118
(42000): Row size too large (> 8126)" bug.
When complete SQL dump is restored with a new ibdata1, everything works
(upgrade to 10.3.31 and also clean shutdown).
--
Ondrej Zary
t mariadb-10.3.30 but dpkg-buildpackage failed with:
dh_install: mariadb-plugin-cassandra missing files:
etc/mysql/conf.d/cassandra.cnf
--
Ondrej Zary
gt;
> Thanks for reporting. Could you please check if this has been reported
> upstream at jira.mariadb.org?
>
> There isn't much we can do about InnoDB internals in Debian packaging.
--
Ondrej Zary
Package: mariadb-server
Version: 1:10.3.31-0+deb10u1
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
upgrading mariadb-server from 1:10.3.29-0+deb10u1 to 1:10.3.31-0+deb10u1 failed
because mariadb failed to start. /var/log/mysql/error.log:
2021-10-10 15:12:49 0 [ERROR
ules/@vue/component-compiler-utils/dist/parse.js:15:23)
at Object.module.exports
(/var/lib/gitlab/node_modules/vue-loader/lib/index.js:67:22)
@ ./pages/projects/new/index.js 5:0-57 28:29-50 32:15-36
@ multi ./main ./pages/projects/index.js ./pages/projects/new/index.js
--
Ondrej Zary
Package: gitlab
Version: 13.12.9+ds1-1~fto10+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
installing gitlab 13.12.9+ds1-1~fto10+1 on buster amd64 fails with:
Installing node modules...
Resolving 2.4.2 to a url...
error An unexpected error occurred: "Release not found
On Tuesday 21 September 2021, Thorsten Glaser wrote:
> Ondrej Zary dixit:
>
> >Hello, why tomcat9 still does not have an init script despite it has
> >been posted here?
> >
> >I'm upgrading a Stretch server without systemd to Buster. Tomcat 9 is
> >instal
Hello,
why tomcat9 still does not have an init script despite it has been posted here?
I'm upgrading a Stretch server without systemd to Buster. Tomcat 9 is installed
but cannot be started without an init script.
--
Ondrej Zary
On Tuesday 21 September 2021, Bastien ROUCARIES wrote:
> Le mar. 21 sept. 2021 à 07:55, Ondrej Zary a écrit :
> >
> > On Monday 20 September 2021, Bastien Roucariès wrote:
> > > Le lundi 20 septembre 2021, 19:32:52 UTC Bastien ROUCARIES a écrit :
> > > Could
-inl.h:27,
from ../src/async_wrap.cc:22:
../src/util.h:210:11: error: ‘Persistent’ does not name a type; did you mean
‘gethostent’?
const Persistent& persistent);
^~~~~~
--
Ondrej Zary
On Tuesday 21 September 2021, Jérémy Lal wrote:
> Le lun. 20 sept. 2021 à 22:30, Ondrej Zary a écrit :
>
> > On Monday 20 September 2021 21:32:52 Bastien ROUCARIES wrote:
> > > Could you try first to apply
> > https://github.com/nodejs/node/commit/c60780ff52
> >
est_fixture.h.rej
patching file test/cctest/test_base_object_ptr.cc
patching file test/cctest/test_node_postmortem_metadata.cc
Hunk #1 succeeded at 91 (offset -2 lines).
--
Ondrej Zary
On Monday 20 September 2021 19:31:56 Bastien ROUCARIES wrote:
> Le lun. 20 sept. 2021 à 17:28, Jérémy Lal a écrit :
> >
> >
> >
> > Le lun. 20 sept. 2021 à 19:15, Ondrej Zary a écrit :
> > >
> > > On Monday 20 September 2021 16:56:18 Bastien ROUCAR
On Monday 20 September 2021 16:56:18 Bastien ROUCARIES wrote:
> Le lun. 20 sept. 2021 à 14:24, Ondrej Zary a écrit :
> >
> > On Monday 20 September 2021, Bastien ROUCARIES wrote:
> > > Could you try to apply
> > >
> >
ObjectPtr definition.
--
Ondrej Zary
n fault
# dpkg -l | grep dbgsym
ii libnode64-dbgsym:i38610.24.0~dfsg-1~deb10u1
i386 debug symbols for libnode64
ii libuv1-dbgsym:i386 1.24.1-1+deb10u1
i386 debug symbols for libuv1
ii nodejs-dbgsym10.24.0~dfsg-1~deb10u1
i386 debug symbols for nodejs
--
Ondrej Zary
> And try to rebuild the whole libuv and nodejs with -fstack-protector-all
Does not print anything other than Segmentation fault.
--
Ondrej Zary
1 blocks
==6122== suppressed: 0 bytes in 0 blocks
==6122== Rerun with --leak-check=full to see details of leaked memory
==6122==
==6122== For counts of detected and suppressed errors, rerun with: -v
==6122== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
Segmentation fault
--
Ondrej Zary
On Monday 20 September 2021, Bastien ROUCARIES wrote:
> Could you try to build both libuv and node with -fsanitize=null it is
> likely a null dereference so catch it
It does not seem to work correctly:
runuser -u gitlab -- sh -c 'yarnpkg install'
../deps/v8/src/date.cc:44:20: runtime error: member
suppressed: 0 bytes in 0 blocks
==3163== Rerun with --leak-check=full to see details of leaked memory
==3163==
==3163== For counts of detected and suppressed errors, rerun with: -v
==3163== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
Segmentation fault
--
Ondrej Zary
can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/lib/i386-linux-gnu/libnode.so.64+0x50bb5a) in
node::fs::FSReqWrap::~FSReqWrap()
==26662==ABORTING
--
Ondrej Zary
I'm unable to compile node with -fsanitize=address,undefined. Seems that
compiler hits 32-bit memory space limit:
cc1plus: out of memory allocating 65536 bytes after a total of 3356393472 bytes
--
Ondrej Zary
Rebuilt Debian libuv1 1.24.1 with -fno-stack-protector - still segfaults.
Rebuilt Debian libuv1 1.42.0 (from unstable) in Buster - still segfaults.
--
Ondrej Zary
). Or cflags?
--
Ondrej Zary
Added back --shared-zlib: works.
Added back also --shared-cares: works.
So you're right: --shared-libuv is the problem.
Upstream seems to include libuv 1.34.2.
Buster has 1.24.1-1.
--
Ondrej Zary
fto10+2 to work.
Then I can upgrade gitlab further to 12 and 13 and only then I can upgrade
Debian to bullseye.
I've rebuilt Debian nodejs without --shared-zlib, --shared-cares and
--shared-libuv (remove them from debian/rules). It works now!
Going to narrow it down.
--
Ondrej Zary
There's no such patch in 10.24.0~dfsg-1~deb10u1
--
Ondrej Zary
Upstream node rebuilt in Debian works. So it's not a compiler or libc problem.
The Debian (buster) i386 version 10.24.0~dfsg-1~deb10u1 already contains SSE2
instructions - it does not work on Pentium 3:
$ node
Illegal instruction
So I doubt that changing -march would help.
--
Ondrej Zary
8.3.0-6) 8.3.0
libc6 2.28-10
I'll try to build the upstream version in Debian.
--
Ondrej Zary
/nodejs and
/usr/share/nodejs:
/node_modules -> /usr/share/nodejs
/var/lib/gitlab/.node_libraries -> /usr/lib/nodejs
yarnpkg completed without segfault!
--
Ondrej Zary
It works from amd64 chroot on the same machine. The i386 nodejs is broken.
--
Ondrej Zary
135>: add$0x10,%esp
0xf6fdfb9a <+138>: lea-0x8(%ebp),%esp
0xf6fdfb9d <+141>: pop%ebx
0xf6fdfb9e <+142>: pop%esi
0xf6fdfb9f <+143>: pop%ebp
0xf6fdfba0 <+144>: ret
0xf6fdfba1 <+145>: lea0x0(%esi,%eiz,1),%esi
0xf6fdfba8 <+152>: sub$0xc,%esp
0xf6fdfbab <+155>: pushl 0x16978(%ebx)
0xf6fdfbb1 <+161>: call 0xf6f1fcb0 <_ZN4node6AssertEPA4_KPKc@plt>
This is on a 64-bit CPU (P4) running i386 userspace. This does not look like a
CPU problem.
It simply crashed in a C++ code.
nodejs 10.24.0~dfsg-1~deb10u1
yarnpkg 1.22.4-5~bpo10+1
--
Ondrej Zary
Package: src:linux
Version: 5.10.40-1
Severity: normal
Driver ds2490 For Dallas 1-wire bus driver DS9490R seems broken.
No devices on 1-wire bus are detected and reading most files from
/sys/bus/w1/drivers/w1_master_driver/w1_bus_master1 causes process
to hang in uninterruptible wait.
The same ha
directory)
Where comes the weird CHANNELID 0x0103F8 from? Maybe 0x3f8 as I/O address of PC
COM1 port?
The working /etc/reader.conf.d/libtowitoko2 file is:
FRIENDLYNAME "Towitoko Chipdrive Reader"
LIBPATH /usr/lib/libtowitoko.so.2.0.0
CHANNELID 1
However, it should probably be commented-out by default (as in
/etc/reader.conf.d/libccidtwin)
--
Ondrej Zary
On Sat, 2 Jan 2021 14:20:57 +0100 Bill Allombert wrote:
> What Sean meant is that, at this stage, this proposal needs to be
> seconded by people impacted by this virtual package before being
> accepted.
as maintainer of todotxt-cli I second this.
--
Best regards
Ondřej Nový
signature.asc
De
Hi,
if you want to proceed with the transition, maybe it's a good idea to
upload libgit2 to unstable first :)
python-pygit2 is ready for transition since 12 Jun 2020 (in experimental).
--
Best regards
Ondřej Nový
Hi,
check-manifest have in setup.py:
install_requires=[
'build>=0.1',
and doesn't have python3-build (which is not in archive) in B-D. Thus
reassigning to check-manifest.
--
Best regards
Ondřej Nový
Hi,
check-manifest have in setup.py:install_requires=['build>=0.1',
and doesn't have python3-build (which is not in archive) in B-D. Thus
reassigning to check-manifest.
--
Best regards Ondřej Nový
signature.asc
Description: This is a digitally signed message part
Hi,
Antonio Terceiro píše v St 04. 11. 2020 v 14:01 -0300:
> Could you ellaborate? Maybe we should have a discussion in the Pythonteam so
> that we implement consistent practices. For example, `gunicorn`and `pip` now
> point to their python3 versions, but you are saying thatpytest will not do
> th
Hi,
pá 16. 10. 2020 v 17:32 odesílatel Andrius Merkys
napsal:
> Hello,
>
> Recently cherrytree [1] has been rewritten from Python to C++, thus it
> no longer belongs in DPT. Could someone with adequate permissions
> transfer it from DPT to generic Debian group on salsa.d.o?
>
done: https://sals
correct link, sorry:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/searx/6271353/log.gz
--
Best regards
Ondřej Nový
Hi,
út 21. 4. 2020 v 23:24 odesílatel Thomas Goirand napsal:
> > But that still leaves the question of what to do about the dependency of
> > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and
> > it's reverse-dependencies in the same way that regular python2 modules
> > we
Hi,
čt 30. 1. 2020 v 22:05 odesílatel Ondrej Novy napsal:
> Python 2 package is needed for many other packages:
>
same is valid for PyPy version:
onovy@sid:~$ reverse-depends -b pypy-setuptools-scm
Reverse-Build-Depends
* backports.functools-lru-cache
* pytest
* python-importlib-me
Hi Dmitry,
čt 30. 1. 2020 v 22:38 odesílatel Dmitry Shachnev
napsal:
> However upstream python-keyring has dropped Python 2 support, and I want
> to upgrade to a newer release, so Python 2 support will be dropped sooner
> or later.
>
upstream drop of Python 2 support doesn't mean you need to dr
Hi,
čt 30. 1. 2020 v 10:10 odesílatel Dmitry Shachnev
napsal:
> setuptools-scm has removed Python 2 support (see #938470), so
> python-keyring
> build-dependencies are no longer satisfiable.
>
> Thus I am going to remove Python 2 support from python-keyring
please don't, because #938470 should
Hi,
Python 2 package is needed for many other packages:
onovy@sid:~$ reverse-depends -b python-setuptools-scm
Reverse-Build-Depends
* apipkg
* automat
* backports.functools-lru-cache
* cherrypy3
* execnet
* keyrings.alt
* monkeysign
* pytest
* pytest-forked
* pytest-runner
* pytest-xdist
* python
Hi,
čt 28. 11. 2019 v 17:11 odesílatel Andreas Tille napsal:
> Hmmm, what are the chances to get this applied? I've added
>
tbh dunno :)
> in Git - but this will not reall fix the test. The only solution I'd see
> otherwise is to deactivate the test.
>
you have two options:
1. deactivate t
On Tue, 26 Mar 2019 10:42:29 +0100 Ondrej Kozina wrote:
On Thu, 14 Mar 2019 19:43:26 +0100 Guilhem Moulin
wrote:
> Hi Milan,
>
> On Thu, 14 Mar 2019 at 19:22:42 +0100, Milan Broz wrote:
> > (...)
> > FYI we know about that parallel unlocking problem already and we a
Hi,
út 12. 11. 2019 v 16:37 odesílatel Osamu Aoki napsal:
> Upstream is active and prides to keep python 2.5 compatibility code in
> it ... (Not just 2.7). I (Osamu Aoki ) and dkg even
> made some effort to support both 2 and 3 but the idea was rejected by
> upstream in 2018.
that's odd :/
Hi,
twisted needs Python 2 version (see #943582), reuploading and reopening bug.
--
Best regards
Ondřej Nový
Hi,
ne 27. 10. 2019 v 12:33 odesílatel Rebecca N. Palmer <
rebecca_pal...@zoho.com> napsal:
> Hence, our options are:
> (a) Remove python-pandas and upgrade pandas to 0.25
> (b) Split pandas into two source packages (like matplotlib) so we can
> have python-pandas 0.23 and python3-pandas 0.25
> (
Hi,
so 21. 9. 2019 v 8:32 odesílatel Geert Stappers
napsal:
> i'm not sure if the 3 should/must goto into package name.
>
src: python-foo
binary-python3: python3-foo
binary-doc: python-foo-doc
Thanks. :)
--
Best regards
Ondřej Nový
from CLI
--
Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
signature.asc
Description: PGP signature
Hello,
thanks, freerdp2-x11 works fine.
It's also in stretch-backports so I can use it on my Stretch machines.
On Saturday 31 August 2019 17:08:24 Bernhard Übelacker wrote:
> Hello Ondrej Zary,
> while looking through bug reports for some random
> packages I got to your report.
Package: icedtea-netx
Version: 1.7.2-2
Severity: important
Dear Maintainer,
when trying to launch (at least) iDRAC9 virtual console, javaws eats up all
the memory, machine starts thrashing to the point it requires hard reset in
a couple of seconds. Downgrading icedtea-netx to 1.6.2-3.1+deb9u1 (kee
Package: freerdp-x11
Version: 1.1.0~git20140921.1.440916e+dfsg1-13+deb9u3
Severity: important
Dear Maintainer,
freerdp is not usable on i386 machines without SSE2 - crashes immediately:
$ freerdp 1.2.3.4
WARNING: Using deprecated command-line interface!
1.2.3.4 -> /v:1.2.3.4
connected to 1.2.3.4:
reassign 934959 src:sunpy 0.9.6-2
thx
This is bug in sunpy, using StopIteration in newer Python 3.
Thanks.
--
Best regards
Ondřej Nový
Package: rdesktop
Version: 1.8.6-2~deb9u1
Severity: important
Dear Maintainer,
since upgrading rdesktop to 1.8.6, it does not work properly when connecting to
a Windows XP system.
Windows login screen appears but rdesktop crashes immediately after entering
correct username and password:
$ rdeskt
Hi,
first of all I would like to say thanks to Andrey. He is hard working to
remove Python 2 from Debian. It's not easy job.
ne 11. 8. 2019 v 9:24 odesílatel Apollon Oikonomopoulos
napsal:
> While I understand the urge to get Python 2 out of bullseye as early as
> possible, I don't feel happy a
Hi,
yes, stupid me :) Sorry.
--
Best regards
Ondřej Nový
Hi,
python3-m2crypto is ready in git:
https://salsa.debian.org/python-team/modules/m2crypto
--
Best regards
Ondřej Nový
Hi,
pá 9. 8. 2019 v 23:36 odesílatel Simon Josefsson
napsal:
> Package: python-monotonic
>
> The 'oz' package uses python 2.x because m2crypto in debian does not
> support python 3.x yet. Would you consider re-adding the python 2.x
> python-monotonic binary package, so that oz can build in sid?
Hi,
Drew Parsons píše v Út 06. 08. 2019 v 17:25 +0800:
> e.g what to do about..."/usr/lib/python3/dist-
> packages/flaky/flaky_pytest_plugin.py", line 272, in
> call_runtest_hookINTERNALERROR> when=when,INTERNALERROR>
> TypeError: __init__() missing 3 required positional arguments:
> 'excinfo'
Hi,
ne 4. 8. 2019 v 22:45 odesílatel Jonathan Wiltshire napsal:
> Please go ahead in unstable.
>
uploaded.
Thanks.
--
Best regards
Ondřej Nový
Package: ftp.debian.org
Severity: normal
Hello,
Please remove old binary package python-stopit (1.1.1-1).
Reason:
New release (1.1.2-1) drops Python 2 module, which closes bug #896297.
However, https://qa.debian.org/excuses.php?package=python-stopit
says Updating python-stopit introduces new bugs
Hi,
yes, sorry for noise. After talk over IRC, current plan is:
* remove almost all pypy modules, keep only pypy interpreter (and maybe
setuptools, etc.)
* migrate to pypy3 (not possible now, waiting for tooling)
Thanks.
--
Best regards
Ondřej Nový
Hi,
st 24. 7. 2019 v 11:00 odesílatel Iain Learmonth napsal:
> We are using PyPy because Python 3 was not really fast enough. The
> migration path here is that we move to pypy3. We are blocked by the lack
> of packages for pypy3-setuptools and pypy3-stem.
>
there will be no pypy3-* packages. py
Package: wnpp
Severity: wishlist
Owner: Ondrej Koblizek
* Package name: python-b2-sdk
Version : 1.0.0
Upstream Author : Backblaze, Inc.
* URL : https://github.com/Backblaze/b2-sdk-python
* License : MIT
Programming Lang: Python
Description : Python
Package: wnpp
Severity: wishlist
Owner: Ondrej Koblizek
* Package name: python-json-logger
Version : 0.1.11
Upstream Author : Zakaria Zajac
* URL : https://github.com/madzak/python-json-logger
* License : BSD-2-Clause
Programming Lang: Python
Description
Hi,
uploaded to DELAYED/10-day
Thanks.
--
Best regards
Ondřej Nový
On Mon, May 20, 2019 at 04:19:32PM +0200, Marco d'Itri wrote:
> Do you want me to submit an unblock request for 1.6.6-1 on your behalf?
> I would hate to ship a broken package in the next stable.
Hi
Yes, if you could submit it, it would be glad.
--
Elen sila lumenn' om
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-molotov
Version 1.6-3 currently in testing FTBFS randomly, see #927810. Version
1.6-4 fixies this.
Debdiff attached. Thanks.
unblock python-molotov/1.6-4
--
ssentially a bugfix release, this is one bug that was
fixed. It would be good if it could get into testing.
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
fixes.
python-fakeredis is leaf-package, so the risk is minimal.
Kindly asking to pre-approve this migration.
Thanks
Ondrej Koblizek
debdiff follows:
diff -Nru python-fakeredis-1.0~rc1/debian/changelog
python-fakeredis-1.0.3/debian/changelog
--- python-fakeredis-1.0~rc1/debian/changelog 2019-
On Thu, 14 Mar 2019 19:43:26 +0100 Guilhem Moulin
wrote:
Hi Milan,
On Thu, 14 Mar 2019 at 19:22:42 +0100, Milan Broz wrote:
> (...)
> FYI we know about that parallel unlocking problem already and we are trying
> to find (with systemd people) some solution (perhaps based on cgroups memory
limit
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-molotov
Version in sid fixies FTBFS (#924805).
Debdiff attached.
Thanks.
unblock python-molotov/1.6-3
-- System Information:
Debian Release: buster/sid
A
MR: https://salsa.debian.org/lintian/lintian/merge_requests/116
--
Best regards
Ondřej Nový
Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Hi,
I can't reproduce it and I can build this package locally without any
problem.
--
Best regards
Ondřej Nový
Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
1 - 100 of 830 matches
Mail list logo
