Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
The current upstream code claims to support Python 3.
Popcon is 14.
Reverse deps checked with dak rm -Rnb python-translitcodec
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: src:thumbor
Version: 6.7.0-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertag: py2removal py2leaf py3noport py2rm
As we are trying to remove Python 2 from unstable, and this package is a leaf
package with popcon of 1 and many Python 2 deps/build-deps, it will be removed
Package: src:thumbor
Version: 6.7.0-1
Severity: serious
python-celery was recently removed and so this package cannot be built anymore.
I don't see why that B-D is needed though.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: src:python-raven
Version: 6.3.0-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertag: py2removal py2leaf py3available
python-celery was recently removed so python-raven can't be installed and the
package can't be built.
-- System Information:
Debian Release: bullseye/sid
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
The package is Python 2 only and depends on celery which is Python 3 only.
It also depends on libjs-twitter-bootstrap which will be removed too
(#908424). The upstream code supports Python 3.
Package: src:chaussette
Version: 1.3.0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertag: py2removal py2leaf py2rm
According to #855671 this package doesn't seem to be working for the last 2.5
years, has popcon of 3, doesn't have Python 3 support and depends on a lot of
Python 2
Package: src:pyramid-jinja2
Version: 2.7+dfsg-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertag: py2removal py2leaf py3available
As a part of removing Python 2 from unstable we would like to remove python-
pyramid, and python-pyramid-jinja2 blocks that. Please drop the Python 2
Package: src:python-pyramid-multiauth
Version: 0.8.0-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertag: py2removal py2leaf py3available
As a part of removing Python 2 from unstable we would like to remove python-
pyramid, and python-pyramid-multiauth blocks that. Please drop the
Control: user -1 debian-pyt...@lists.debian.org
Control: usertag -1 + py2removal py2leaf py3available
Control: retitle -1 Please replace with a python3 module or remove the package
Control: severity -1 important
As a part of removing Python 2 from unstable we would like to remove
python-pyramid,
Package: src:monkeysign
Version: 2.2.4
Severity: serious
As Python 2 versions of zbar and zbarpygtk were removed, this package should be
updated to use Python 3 or removed.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'),
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
I couldn't find if the upstream source supports Python 3.
Reverse deps checked with dak rm -Rnb python-libavg
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Andrey Rahmatullin
* Package name: pytest-twisted
Version : 1.11
Upstream Author : Kyle Altendorf et al.
* URL : https://github.com/pytest-dev/pytest-twisted
* License : BSD-3
Programming Lang: Python
Description
Control: tags -1 + pending
On Fri, Sep 14, 2018 at 02:30:11PM +0200, Enrico Zini wrote:
> The current version in Debian seems to be two major releases behind
> upstream. Could you please package a newer version?
I've done the update, it waits for when sybil passes NEW.
--
WBR, wRAR
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
No upstream releases since the last packaged one in 2012.
python3-xcffib description says "This package is intended to be a (mostly)
drop-in replacement for xpyb. xpyb has an inactive upstream,
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
Looks like it doesn't work at all in the current state.
Reverse deps checked with dak rm -Rn python-uniconvertor
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
The latest upstream code at https://github.com/pearu/pyvtk seems to
support Python 3, but the Debian package contains code from 2007.
Reverse deps checked with dak rm -Rnb python-pyvtk
--
WBR,
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
Last release in 2009.
Reverse deps checked with dak rm -Rnb python-excelerator
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
Upstream Python 3 bugreport:
https://bitbucket.org/blais/optcomplete/issues/2/python3-compatibility
Reverse deps checked with dak rm -Rnb python-optcomplete
--
WBR, wRAR
signature.asc
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
There is some Py3 fork at https://github.com/tynn/PyAO
Reverse deps checked with dak rm -Rn pyao
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
Last upstream commit in 2012.
Reverse deps checked with dak rm -Rnb python-m2ext
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
Last release in 2003.
Reverse deps checked with dak rm -Rnb python-jabber
--
WBR, wRAR
signature.asc
Description: PGP signature
Control: reassign -1 src:redis-py-cluster/1.3.3-1
Control: severity -1 grave
Control: forwarded -1 https://github.com/Grokzen/redis-py-cluster/issues/295
Control: affects -1 src:python-limits
On Sat, Feb 09, 2019 at 06:57:54PM +0100, Slavko wrote:
> while this of course affects the python-limits
Package: ftp.debian.org
Severity: normal
User: debian-pyt...@lists.debian.org
Usertag: py2removal
No upstream releases since 2009.
Reverse deps checked with dak rm -Rnb python-gpiv
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
Last upstream release in 2011, http://www.wallix.org/pylibssh2-project/ doesn't
work.
Reverse deps checked with dak rm -Rnb python-libssh2
Package: ftp.debian.org
Severity: normal
Latest upstream source supports Python 3.
Reverse deps checked by dak rm -Rnb python-django-shorturls
Control: tags -1 - moreinfo
On Sun, Aug 11, 2019 at 02:08:11AM -0400, Scott Kitterman wrote:
> > Reverse deps checked by dak rm -Rnb python-elixir
>
> I guess that doesn't catch build-depends:
It does, but...
> Checking reverse dependencies...
> # Broken Build-Depends:
> rabbitmq-server: elixir
Package: ftp.debian.org
Severity: normal
Development stopped 5 years ago.
Reverse deps checked by dak rm -Rnb python-ricky
Package: ftp.debian.org
Severity: normal
The code is from 2007.
Reverse deps checked by dak rm -Rnb python-protocols
Package: ftp.debian.org
Severity: normal
Project is old and dead.
Reverse deps checked by dak rm -Rnb python-pyflot
Package: ftp.debian.org
Severity: normal
There is only one release of this software, in 2006.
Reverse deps checked by dak rm -Rnb python-captcha
Package: ftp.debian.org
Severity: normal
The upstream code is old but seems to support Python 3.
Reverse deps checked by dak rm -Rnb python-chef
Package: ftp.debian.org
Severity: normal
Reverse deps checked by dak rm -Rnb python-pmock
Package: ftp.debian.org
Severity: normal
Related to the obsolete Pylons stack.
Reverse deps checked by dak rm -Rnb python-pastewebkit
Package: ftp.debian.org
Severity: normal
Related to the obsolete Pylons stack.
Reverse deps checked by dak rm -Rnb python-myghtyutils
Package: ftp.debian.org
Severity: normal
No upstream releases after the Debian upload. https://11craft.github.io/louie/
is 404
Reverse deps checked by dak rm -Rnb python-louie
Package: ftp.debian.org
Severity: normal
Reverse deps checked by dak rm -Rnb python-loofah
Package: ftp.debian.org
Severity: normal
The latest upstream code at https://github.com/Didacti/elixir seems to support
Python 3.
Reverse deps checked by dak rm -Rnb python-elixir
Package: ftp.debian.org
Severity: normal
The Debian package is old, the current upstream code at
https://cfpython.bitbucket.io seems to support Python 3.
Reverse deps checked by dak rm -Rn cf-python
Package: ftp.debian.org
Severity: normal
There is some support for Python 3 but the upstream code is 8 years old.
Reverse deps checked by dak rm -Rnb python-bunch
Package: ftp.debian.org
Severity: normal
https://creoleparser.googlepages.com/ is dead. Current upstream release was
uploaded in 2012.
Reverse deps checked by dak rm -Rnb python-creoleparser
Package: ftp.debian.org
Severity: normal
"I'm not even sure if this code is currently Python 3 compatible.":
https://github.com/bookieio/breadability/issues/36
Reverse deps checked by dak rm -Rnb python-breadability
Package: ftp.debian.org
Severity: normal
The latest upstream code, 4 years old, claims to support Python 3.
Reverse deps checked by dak rm -Rnb python-bjsonrpc
Package: ftp.debian.org
Severity: normal
The code seems to support Python 3 but there is no subpackage.
Reverse deps checked by dak rm -Rnb python-beanstalkc
Package: ftp.debian.org
Severity: normal
http://code.sp-its.at/projects/argvalidate is dead, PyPI has the same 10 year
old release as we have.
Reverse deps checked by dak rm -Rnb python-argvalidate
Package: ftp.debian.org
Severity: normal
The source supports Python 3 but there is no subpackage. The upstream
development stopped in 2015.
There is one reverse dep, python-remotecv, its RM bug is #934391
Reverse deps checked by dak rm -Rn remotecv pyres
Package: ftp.debian.org
Severity: normal
Unclear if the source supports Python 3 but there is no Python 3 subpackage.
Reverse deps checked with dak rm -Rnb python-remotecv
Package: ftp.debian.org
Severity: normal
The code claims to support Python 3 but there is no subpackage.
Reverse deps checked by dak rm -Rnb python-trollius-redis
Package: ftp.debian.org
Severity: normal
The upstream has only one commit after 2011 and obviously no Python 3 support.
Reverse deps checked by dak rm -Rn pyxmpp
Package: ftp.debian.org
Severity: normal
The latest upstream release supports py3, I didn't check the version in Debian
which is very old.
Reverse deps checked by dak rm -Rnb python-pywbem
Package: ftp.debian.org
Severity: normal
The package description says
* This package is Python2 as was gnukhata-core-engine. Upstream has no plan
to make a Python3 version, but we intend to raise the question and we hope
a Python3 release will appear before the end of life of Python2
On Fri, Aug 09, 2019 at 08:37:48AM -0700, Felix Lechner wrote:
> > It's the same with lintian from sid (2.16.0) on xhtml2pdf 0.2.2-2 and
> > 0.2.2-3.
> I do not see any issues terminating locally. I used both Lintian
> master and 2.16.0 on the xhtml2pdf source packages, per below. I also
> tried,
It's the same with lintian from sid (2.16.0) on xhtml2pdf 0.2.2-2 and 0.2.2-3.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: src:turbogears2
Version: 2.3.12+really2.3.7-1
Severity: important
While we are working on dropping Python 2, and there is already #880154 that
asks about providing Python 3 support, dropping Pylons is a separate task and
it will help with dropping a bunch of obsolete Python 2-only
Package: ftp.debian.org
Severity: normal
This package is the only package in the archive using the Pylons library which
is Py2-only and will be removed. It is orphaned and no upstream development
happened since 2015.
Package: ftp.debian.org
Severity: normal
No upstream activity at https://launchpad.net/pyrrd since the last package
upload. No Python 3 support. RFH #876679.
Reverse deps checked by dak rm -Rnb python-pyrrd
Package: ftp.debian.org
Severity: normal
http://www.wallix.org/pylogsparser-project/ is dead.
https://pypi.org/project/pylogsparser/ has a newer version than in the package
but still 7 years old.
Reverse deps checked by dak rm -Rnb python-logsparser
Package: ftp.debian.org
Severity: normal
The package is 5 years old, the new version at
https://github.com/dcantrell/pykickstart supports Python 3.
Reverse deps checked by dak rm -Rnb python-pykickstart
Package: ftp.debian.org
Severity: normal
No Python 3 support even in the new upstream at
https://github.com/twisted/epsilon
The only reverse dep is python-axiom, whose RM bug is #934176.
Reverse deps checked by dak rm -Rnb python-epsilon
Package: ftp.debian.org
Severity: normal
Source seems to support Python 3 in some form but this is not used in the
package, some related packaging parts exist but are commented out. The version
in Debian is 5 years old, the upstream is active. It also depends on shogun
which is currently orphaned
Package: ftp.debian.org
Severity: normal
Source claims to support Python 3.4 but there is no Python 3 subpackage.
https://github.com/aodag/jsonrpc2 has no updates since the packaged version (5
years ago).
Reverse deps checked by dak rm -Rnb python-jsonrpc2
Package: ftp.debian.org
Severity: normal
Upstream Python 3 support is only proposed:
https://github.com/twisted/axiom/issues/106
Reverse deps checked by dak rm -Rnb python-axiom
Package: ftp.debian.org
Severity: normal
The source doesn't support Python 2, http://mokshaproject.net/ redirects to
https://reactdom.com/graphql and I couldn't find a new upstream location.
Reverse deps checked with dak rm -Rnb python-moksha.hub
On Mon, Aug 05, 2019 at 07:39:54PM +0100, Adam D. Barratt wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: rm
> >
> > Orphaned, doesn't support Python 2, doesn't have revdeps (checked
> > with `dak rm
> > -Rn storm`).
> >
Removal from unstable.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
No Python 3 support. No revdeps (checked with dak rm -Rn pyramid-beaker).
Newer upstream versions declare Python 3.2 compatibility. Last release in 2013.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Orphaned, doesn't support Python 2, doesn't have revdeps (checked with `dak rm
-Rn storm`).
No Py3 support upstream either: https://bugs.launchpad.net/storm/+bug/1530734
On Mon, Aug 05, 2019 at 11:22:50AM +0200, Johannes Schauer wrote:
> Control: tag -1 + newcomer
>
> Hi,
>
> Quoting Andrey Rahmatullin (2019-08-02 15:14:23)
> > Currently sbuild sets APT::Keep-Downloaded-Packages to false and it doesn't
> > look configurable. If sbuil
Control: owner -1 !
As agreed on IRC, I'll work on this ITP. I'm almost finished already.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: sbuild
Version: 0.78.1-2
Severity: wishlist
Currently sbuild sets APT::Keep-Downloaded-Packages to false and it doesn't
look configurable. If sbuild is used with a persistent package cache (e.g.
bind-mounting the host one) this setting should be set to true to skip
downloading the same
On Wed, Jul 31, 2019 at 12:35:56PM +, Holger Levsen wrote:
> > > > > src:librsync is currently still to be removed from bullseye on August
> > > > > 9th, because #776246 was only fixed in experimental...
> > > > In experimental and unstable.
> > >
> > > not according to the bts which only
On Wed, Jul 31, 2019 at 11:28:46AM +, Holger Levsen wrote:
> > > src:librsync is currently still to be removed from bullseye on August
> > > 9th, because #776246 was only fixed in experimental...
> > In experimental and unstable.
>
> not according to the bts which only knows 1.0.0-1~exp1 as
On Wed, Jul 31, 2019 at 02:06:50AM +, Holger Levsen wrote:
> > Turns out I had some extra time for this flying back from DebConf and it
> > needed changes to only one file for this, so new rdiff-backup with
> > librsync2 was uploaded yesterday...
>
> src:librsync is currently still to be
librsync2 is available in unstable, please binNMU burp, csync2 and
duplicity.
From https://lists.debian.org/debian-python/2019/07/msg00093.html I guess
Otto (Cced) is interested in keeping rdiff-backup? In that case, Otto,
please prepare an upload with a fix.
--
WBR, wRAR
signature.asc
On Mon, Jul 29, 2019 at 10:36:57AM +0200, Otto Kekäläinen wrote:
> > librsync2 is available in unstable, please binNMU burp, csync2 and
> > duplicity.
> >
> > From https://lists.debian.org/debian-python/2019/07/msg00093.html I guess
> > Otto (Cced) is interested in keeping rdiff-backup? In that
On Tue, Jul 23, 2019 at 01:54:10PM +0200, Santiago Vila wrote:
> * Because this is a violation of a Policy "must" directive, I consider
> the downgrade to be a tricky way to modify Debian Policy without
> following the usual Policy decision-making procedure.
Please also note that
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
The librsync library changed the ABI and also some parts of API, the API change
impacts only rdiff-backup, for which #928885 is filed with no reaction so far.
I've tested all revdeps,
Control: severity -1 serious
Control: block 776246 by -1
As the buster is released I'm bumping the severity.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Jul 10, 2019 at 11:45:53AM +0200, Laurent Bigonville wrote:
> Now that buster has been released, do you think we could move forward with
> uploading the last version of librsync in unstable?
Yes, I plan to proceed with this soon.
> I tried to rebuild duplicity and it's building fine.
I
On Tue, Jul 02, 2019 at 11:50:00PM +0200, Andreas von Heydwolff wrote:
> On 02.07.19 07:20, Andrey Rahmatullin wrote:
> > Doing anything with libimobiledevice4 packages won't touch your locally
> > installed bad library. You should remove it, and any other locally
> >
Doing anything with libimobiledevice4 packages won't touch your locally
installed bad library. You should remove it, and any other locally
installed libraries, and never do such installs again, at least while you
don't fully understand the consequences.
--
WBR, wRAR
signature.asc
Description:
On Fri, Jun 14, 2019 at 10:16:50PM +0200, A. Heydwolff wrote:
> Jun 14 21:10:58 karfiol upowerd[15367]: /usr/lib/upower/upowerd: error while
> loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No
> such file or directory
Note that /usr/lib/upower/upowerd isn't linked to
Package: src:rdiff-backup
Version: 1.2.8-7
Severity: normal
Tags: upstream
We plan upgrading librsync to 2.0.2 after the buster release, see #776246. This
version is not API-compatible with 0.9.7 but it seems the only package that
breaks is rdiff-backup:
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g
On Mon, May 06, 2019 at 12:00:22PM -0400, Sam Hartman wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Hi. As discussed in
> https://cointelegraph.com/news/phishing-attack-on-electrum-wallet-nets-hacker-almost-1-million-in-hours-report
> the version of electrum in sid is vulnerable to
On Mon, Apr 15, 2019 at 06:40:41AM +, Mishra, Gaurav wrote:
> FOSSology currently supports Debian Jessie and Stretch both. And Jessie still
> have a year left to meet its end of life that is the reason we still support
> it. And that is the reason php5-cli is still there.
Please keep in the
On Thu, Apr 11, 2019 at 08:16:06AM +, Mishra, Gaurav wrote:
>
> Changes since the last upload:
>
> * First release as a Debian package.
> * Closes: bug#924659
If it's a first release it shouldn't have 2 as the Debian version.
--
WBR, wRAR
signature.asc
Description: PGP signature
libwolfssl was removed from testing due to #918952.
The shared lib was removed but this package was not, because it doesn't
depend on the lib. Maybe the B-D can be safely removed.
--
WBR, wRAR
signature.asc
Description: PGP signature
Control: tags -1 + upstream
Please forward it to https://github.com/tibirna/qgit/issues, ideally with
instructions how to create such repo.
--
WBR, wRAR
signature.asc
Description: PGP signature
-05 22:07:29.0 +0500
+++ pygnuplot-0.11.16/debian/changelog 2019-03-17 14:00:05.0 +0500
@@ -1,3 +1,10 @@
+pygnuplot (0.11.16-2) unstable; urgency=medium
+
+ * Team upload.
+ * Fix the build dependency on debhelper (Closes: #924341).
+
+ -- Andrey Rahmatullin Sun, 17 Mar 2019 14
On Mon, Mar 11, 2019 at 05:09:58PM +, Santiago Vila wrote:
> In file included from /usr/include/GraphicsMagick/magick/analyze.h:18,
> from /usr/include/GraphicsMagick/magick/api.h:55,
> from map_geo.c:137:
> /usr/include/GraphicsMagick/magick/image.h:1108:10:
On Tue, Mar 12, 2019 at 09:43:22AM +, Santiago Vila wrote:
> TZ=UTC ronn --roff debian/coveralls.mkd
> roff: debian/coveralls.mkd.1
[...]
> dh_installman: Cannot find (any matches for) "debian/coveralls.1" (tried in
> ., debian/tmp)
So a change in ronn, I guess. The
On Mon, Mar 04, 2019 at 11:16:02AM +, Santiago Vila wrote:
> Searching for billiard<3.6.0,>=3.5.0.2
It's 3.6.0.0 in sid (was 3.5.0.4 when this package was uploaded).
--
WBR, wRAR
signature.asc
Description: PGP signature
The code giving the errors is actually from juce-modules-source. The
version used for building the current sid giada package is 5.3.2~repack-1,
while the version in sid (which causes FTBFS) is
5.4.1+really5.4.1~repack-2. This seems to be related to #913915, I have no
idea how can the current sid
The problem here is the API compatibility break in glslang, described in
https://github.com/KhronosGroup/glslang/issues/1538#issuecomment-431643795
Changes related to the new glslang version seem to be bundled in
https://github.com/baldurk/renderdoc/commit/2ea6174c83c3c55f504c107303991d9bb2aa9af3
The actual error message is
"""
CMake Error at CMakeLists.txt:298 (message):
MPIIO package needs LAMMPS to be build with MPI
Call Stack (most recent call first):
CMakeLists.txt:304 (pkg_depends)
"""
It seems to mean MPI is not found. After removing QUIET from
find_package(MPI):
-- Found
Package: libradare2-dev
Version: 3.2.1+dfsg-4
Severity: serious
Control: block 923321 by -1
At least libuv and liblz4 are listed in Requires.private of the .pc files yet
the -dev package doesn't depend on their -dev packages. This leads to
pkg-config --cflags r_core failing.
-- System
On Tue, Feb 26, 2019 at 11:18:18AM +, Santiago Vila wrote:
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
> -DSYSCONFDIR='"/etc"' -I./../libdynaloginclient -Wdate-time
> -D_FORTIFY_SOURCE=2 -pthread -DLINUX -D_REENTRANT -D_GNU_SOURCE
>
On Tue, Feb 26, 2019 at 05:23:13PM +0800, Yanhao Mo wrote:
> Control: tags -1 + pending
>
> Andrey Rahmatullin writes:
>
> > Control: tags -1 + upstream fixed-upstream
> >
> > On Wed, Feb 13, 2019 at 09:21:17PM +0800, Yanhao Mo wrote:
> >> Control:
Control: tags -1 + upstream fixed-upstream
On Wed, Feb 13, 2019 at 09:21:17PM +0800, Yanhao Mo wrote:
> Control: tags -1 + confirmed help
This seems to be fixed upstream:
https://github.com/teejee2008/timeshift/issues/375
--
WBR, wRAR
signature.asc
Description: PGP signature
On Fri, Feb 22, 2019 at 10:53:47PM +, Santiago Vila wrote:
> In file included from src/com/redhat/nuxwdog/wdpwd.cpp:37:
> /usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private'
> extern long keyctl_dh_compute_kdf(key_serial_t private, key_serial_t prime,
>
Package: python-turbogears2
Version: 2.3.12-1
Severity: important
Control: block 922263 by -1
/usr/lib/python2.7/dist-packages/tg/controllers/decoratedcontroller.py in
()
12 from tg.predicates import NotAuthorizedError, not_anonymous
13
---> 14 from crank.util import
201 - 300 of 1360 matches
Mail list logo
