date:20160512

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

2016-05-12 Thread Dmitry Shachnev

Hi Helmut,

On Thu, May 12, 2016 at 08:40:00PM +0200, Helmut Grohne wrote:
>> 161 is many packages, though in my opinion splitting the documentation into
>> arch:all packages is something that should be done independently of this bug.
>> Maybe we can have some kind of DD list whose packages are affected by this?
>> (Or a Lintian warning, see below.)
>
> Computing this list in an automated way is difficult, because
> build-rdeps has no way of ignoring Build-Depends-Indep (even though the
> underlying dose can do that, though not in unstable as Johannes just
> told me).

reverse-depends -b src:sphinx [1] returns multiple lists for B-D and B-D-I,
but a *huge* part of the B-D group is packages that don't have arch-dep
stuff at all (i.e. pure Python packages).

[1] where reverse-depends is from ubuntu-dev-tools

> This is not as clear cut. Sometimes documentation is small. We tend to
> not split out every single bit of documentation into arch:all packages.
> To the contrary, manual pages tend to be included with the main package.
> I do not see consensus for this increase in the number of binary
> packages.

Right, but we were talking about the solutions to cross issues...

> If the dh addon is not to be used, you should deprecate it. I actually
> find the addon useful, because it removes complexity (unless you do
> [1]). In an ideal world, we would maybe say "dh $@ --with-indep sphinx"?

I won't deprecate it because Sphinx was developed for Python and most
Python packages don't have any arch-specific stuff at all, so for them
--with sphinxdoc works fine.

A --with-indep option would be nice indeed :)

> > Alternatively, as you suggest, such packages may build-depend on 
> > sphinx-common
> > and I may mark sphinx-common as Muili-Arch: foreign. If it helps then I will
> > do that.
>
> It's the simplest workaround that I see. Of course, people need to
> remember to Build-Depend on sphinx-common to use the addon, which is
> complexity of its own. If we pursue that road, we should document it
> precisely (e.g. README.Debian?).

So should I go ahead and add M-A: foreign attribute to sphinx-common?

I can also document it in README.Debian but I am not sure I will find
proper wording to describe the problem. Maybe you can help me with that?
If you could do that, then I'll be able to describe the solution myself.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] python-scruffy_0.3.3-1_amd64.changes ACCEPTED into unstable, unstable

2016-05-12 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 May 2016 22:46:42 +0800
Source: python-scruffy
Binary: python-scruffy python3-scruffy
Architecture: source all
Version: 0.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 python-scruffy - framework for taking care of a bunch of boilerplate in 
Python2 ap
 python3-scruffy - framework for taking care of a bunch of boilerplate in 
Python3 ap
Closes: 823992
Changes:
 python-scruffy (0.3.3-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #823992)
Checksums-Sha1:
 dd6944d96b4dddbd065dee621881daa0949bd7a6 2197 python-scruffy_0.3.3-1.dsc
 4f42d803a3e1b76cd2dc35599315d155499eaac7 8767 python-scruffy_0.3.3.orig.tar.gz
 bb94bb2b391bb8c827023ff3ce5f1ceff8fc19a3 2352 
python-scruffy_0.3.3-1.debian.tar.xz
 602785e914ce74126e2cf89e519d93493d7fd76f 10630 python-scruffy_0.3.3-1_all.deb
 f66c4b3d1fcc6036260f0c177d12a0835106396d 10716 python3-scruffy_0.3.3-1_all.deb
Checksums-Sha256:
 47de13fa2ce34b677bedf93233d27cc86449aae4aaf63527d47cd68c771bbe71 2197 
python-scruffy_0.3.3-1.dsc
 54b17f550628167d16b1c651d8dff1213d8eb61b728e949ef63aa201c08d4ba2 8767 
python-scruffy_0.3.3.orig.tar.gz
 17d3d48498b60c2bdb8e3ddc93cfe478a2a8626e5e5c14c45da44546e0204629 2352 
python-scruffy_0.3.3-1.debian.tar.xz
 b8218c6102cfcce3e5fb408c2d96308b09fff59950ef293270319d2ad3dd1125 10630 
python-scruffy_0.3.3-1_all.deb
 cad5ff7c488f7a11197de7dbbde34e534755d8b0a38263a9a42a504da60f6d21 10716 
python3-scruffy_0.3.3-1_all.deb
Files:
 4e3b01ba00a6cef6085164da6d912853 2197 python optional 
python-scruffy_0.3.3-1.dsc
 7c482fabe5e6aaba1c18ed065533ba6c 8767 python optional 
python-scruffy_0.3.3.orig.tar.gz
 91e76a7215863fc11f908fd2814570bf 2352 python optional 
python-scruffy_0.3.3-1.debian.tar.xz
 45e55b147a52076bb6b424d2a6326431 10630 python optional 
python-scruffy_0.3.3-1_all.deb
 b01dba6dc404c3d6714f443df7038ab4 10716 python optional 
python3-scruffy_0.3.3-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXM0cGAAoJELTYlw90nD9qO9oQAJlozDj+YsNxsoyzIO6b6Y2U
Jy9h3y3IW3noaCl+dcM9sXEmKapIl+s5E9wT0yJkTYV30WOjk5JNzJ+dAxlER3+8
tevuMtwD47l7sqG7eeIeFdNWp3eaJbt4KJq5uzg09u4m23awX7Z1pbC6v1W+XTso
l6Sl4GCRzlokK138nRVMal3zH5ms7ROrWBu8BFRoRFIgwLsZtl8yaulwtqK6TriC
CyuxsD95f5YkqOaHBn4BV+LSntx/wIdZwvVPOOJUXqLKKS0rcavOg0AaQxqwaZ87
tafQUcPDuBP+xEYtWLgkMZpGZGFS/8J+7a2k07pcBdYZ7F5BE0byIijgDNtWc50s
CB3ne1NzCXUwl9l70LJ/p6UwzTBGkN4zE3sr6EZDX8pWcqcmwDuyRUkQB1WrDF8q
uHLHgRgBVqsYNqMtTPd1m5bksyuc9neSEWVmYMTnU9XKieB/JYhIrQXkOnVq/k7h
Di4UJcZ4Xd2zCEWjZqvr3khSgTPVRe7kG9dn3FOrdORel7GsVoPV5xa4Bseqnlfy
KKr44d0UJREd4/ov61G066e/xa+BEWj9OXsJ/KdYc9G9Bwq943HS5U9Wqfse5jJb
Kxs8qrYDLeT1RtrTQz8mx9VB5H+XW0SJuPu73B3g3QMAKsQeBqfA8OnHru/E0K66
oCIW2xy8w8tEKpkhvd0/
=ka3g
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

2016-05-12 Thread Helmut Grohne

Hi Dmitry,

On Thu, May 12, 2016 at 01:34:04PM +0300, Dmitry Shachnev wrote:
> As you can see, I don't always reply quickly. Sorry for the delay this time.

Things go slowly in cross-land anyway. Thanks for your continued
interest. :)

> > Cross building only applied to arch-dep packages. So in jansson's case,
> > it is not about libjansson-doc, but about the other packages. The only
> > part of sphinx that is actually used during a cross build of jansson
> > actually is the debhelper addon, which actually lives in sphinx-common
> > and is exposed by python-sphinx. In a very similar case, Tomasz Buchert
> > was able to move python-sphinx from Build-Depends to Build-Depends-Indep
> > in nghttp2[1]. So looking at this closer again, a potential solution for
> > sphinx could be:
> >
> >  * Mark sphinx-common Multi-Arch: foreign.
> >  * Move python-sphinx from jansson's Build-Depends to
> >Build-Depends-Indep.
> >  * Add sphinx-common to jansson's Build-Depends.
> >
> > I didn't verify whether these changes are correct. We can try this to
> > put urgency out of the loop.
> 
> I like the plan, though the third point can be avoided if dh_sphinxdoc is
> called only during arch-indep build.

Correct. In jansson's case, the dh addon is used. In the mean time, we
fixed jansson with a wicked patch[1] that only enables the addon for
arch-indep builds. While it works, it looks fragile to me.

So whenever the dh addon is used, adding sphinx-common to Build-Depends
is the easy way.

> 161 is many packages, though in my opinion splitting the documentation into
> arch:all packages is something that should be done independently of this bug.
> Maybe we can have some kind of DD list whose packages are affected by this?
> (Or a Lintian warning, see below.)

Computing this list in an automated way is difficult, because
build-rdeps has no way of ignoring Build-Depends-Indep (even though the
underlying dose can do that, though not in unstable as Johannes just
told me).

> > Do you have any preferences on the approaches sketched above keeping in
> > mind that we will apply it to hundreds of packages?
> 
> In an ideal world, the solution looks this way:
> 
> 1) Packages shipping Sphinx documentation in arch:any packages should
> split it into arch:all packages.
> 
> 2) All packages using Sphinx should make sure dh_sphinxdoc is only called
> during arch-indep build.
> 
> For 1), maybe we can have a Lintian warning for that?
> (i.e. sphinx-documentation-in-architecture-dependent-package)

This is not as clear cut. Sometimes documentation is small. We tend to
not split out every single bit of documentation into arch:all packages.
To the contrary, manual pages tend to be included with the main package.
I do not see consensus for this increase in the number of binary
packages.

> For 2), this means packages having both arch-dep and arch-indep packages won't
> be able to use --with sphinxdoc because sphinxdoc.pm sequence won't be present
> during arch:indep build. We can recommend packages to insert it manually then,
> like:
> 
> override_dh_installdocs-indep:
> dh_installdocs -i
> dh_sphinxdoc -i

If the dh addon is not to be used, you should deprecate it. I actually
find the addon useful, because it removes complexity (unless you do
[1]). In an ideal world, we would maybe say "dh $@ --with-indep sphinx"?

> Alternatively, as you suggest, such packages may build-depend on sphinx-common
> and I may mark sphinx-common as Muili-Arch: foreign. If it helps then I will
> do that.

It's the simplest workaround that I see. Of course, people need to
remember to Build-Depend on sphinx-common to use the addon, which is
complexity of its own. If we pursue that road, we should document it
precisely (e.g. README.Debian?).

Helmut

[1] 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=807848;filename=jansson_2.7-3.1.debdiff;msg=29

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] django-polymorphic_0.9.2-1_amd64.changes ACCEPTED into unstable

2016-05-12 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 12 May 2016 15:05:00 +0200
Source: django-polymorphic
Binary: python-django-polymorphic python3-django-polymorphic 
python-django-polymorphic-doc
Architecture: source all
Version: 0.9.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-polymorphic - Seamless Polymorphic Inheritance for Django Models
 python-django-polymorphic-doc - Seamless Polymorphic Inheritance for Django 
Models (Documentation
 python3-django-polymorphic - Seamless Polymorphic Inheritance for Django 
Models (Python3 versi
Changes:
 django-polymorphic (0.9.2-1) unstable; urgency=low
 .
   [ Ondřej Nový ]
   * Fixed VCS URL
 .
   [ Michael Fladischer ]
   * New upstream release.
   * Bump Standards-Version to 3.9.8.
   * Remove version from python-django for Depends and Build-Depends.
   * Switch to python3-sphinx and drop versioned Build-Depends.
Checksums-Sha1:
 e5b2eee8e34247a72f1849ec8cc5f125b93fe72d 2372 django-polymorphic_0.9.2-1.dsc
 7ec1267dedc7e560889d93ac304dffc5001dd3a2 69159 
django-polymorphic_0.9.2.orig.tar.gz
 6f17fb2f0f3f2b736c7bb3e6e6b054a7d2b62f8b 3744 
django-polymorphic_0.9.2-1.debian.tar.xz
 f85d062eea15619c2459e67deb923ecd9967de10 55964 
python-django-polymorphic-doc_0.9.2-1_all.deb
 79bdeae5d5a2a0b4fb24f06718e531b3c42467cb 39508 
python-django-polymorphic_0.9.2-1_all.deb
 078f22f7ec4f187664846c80ba8bfba3a284460b 39388 
python3-django-polymorphic_0.9.2-1_all.deb
Checksums-Sha256:
 cb103f911693c0588cd63505d1b3401d91b4502d41fc6ce2a33c5a24b1e9f558 2372 
django-polymorphic_0.9.2-1.dsc
 069c38da2450850d5cf68dea4f520b18373dc607a97939ea2cdef357c62365b8 69159 
django-polymorphic_0.9.2.orig.tar.gz
 a02f351b519d237ca6009a8ae45788145f330a911b8af2e8669cb6b92c0e8e06 3744 
django-polymorphic_0.9.2-1.debian.tar.xz
 e837f75cb6825f99858e8f0de5101c59404cc79b87d59fa7ec8122aee2330edb 55964 
python-django-polymorphic-doc_0.9.2-1_all.deb
 fa8747232a496dffbd3aa66fd0a2d042899a0edeec682b966e36e7664f99dc32 39508 
python-django-polymorphic_0.9.2-1_all.deb
 49650564c7436ea09dc51587efb250675124594fdcf31330554accbc69947bc2 39388 
python3-django-polymorphic_0.9.2-1_all.deb
Files:
 9dd3151fc09f04118b96b67831c0ec99 2372 python optional 
django-polymorphic_0.9.2-1.dsc
 e2d08b6ed7b13d657a62677ad3e8aba8 69159 python optional 
django-polymorphic_0.9.2.orig.tar.gz
 1082b310f23e25aa1df2f023bc250615 3744 python optional 
django-polymorphic_0.9.2-1.debian.tar.xz
 6afdd11ee6df23271b7ad443a1d74e2e 55964 doc optional 
python-django-polymorphic-doc_0.9.2-1_all.deb
 d34e210748e9d0f9c1624536ee4dfe46 39508 python optional 
python-django-polymorphic_0.9.2-1_all.deb
 66d4b7f5fa4840c0f6c3778e91ab740b 39388 python optional 
python3-django-polymorphic_0.9.2-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXNLOfAAoJEGlMre9Rx7W24oMP/0MGymTTe645SR7da69GF44E
L+xwQ+45FBWh5hj3XgiDAbJXxWvoQzHTPv3K07USeSxYwaroiWYKjBYZ2dMZQEBB
K3O0Upy4P3VYSO6VytUe0md/4F/BrNyme5ifYglTbhL6jNA50UkDAJDodK3acfQp
F6sFlKchdS+n4hIWNrbhJ6u4e/79RyCWEa7+QxR+CuGPmC5jnmkBfZvC+/Zuwlu+
0FCFi1b2nS5ftcEMPyfJbBKs/2Zury1yoYoULp3kniN6cogVnxgRrRrGg7bYPsz7
O6rIsYXTcRJGZltYZfq+3e9iy03ylFqHEREq25RA9ntUpk5LS90pLP3k4OSxwYwi
6reBCHkoWV2gy1+YWgy5h4Ojv9ojqpyUrm4tJwoRaeeCBdB/6Vn+Vyjtfaa3Aht6
HRcJHpTuLAXsonVJ4O8ctVk00IN1Z+dB6mSou30a+bUPLO7u9omE63ADJ5utj32W
ZqJU9woGLyue9OaDXNTRL8mCkxXlCPqttppuuHzMgxpvsXi/0AyD18B3Qv7OS4g9
Wwbhvq/cptVekOVzM8pM/XEcaTwHDu4NIlvKIAjyRjbt7N7wKzWpTlVeILpjnprJ
qJp2rTzrv8X8yOwQkwOqK+KlUmQtCTcZT9ZXDyU4qo69IudPIrmmqymO9cqoy8dN
cVZf3+PHYHgqlWoa+PHM
=OBPG
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processing of django-polymorphic_0.9.2-1_amd64.changes

2016-05-12 Thread Debian FTP Masters

django-polymorphic_0.9.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  django-polymorphic_0.9.2-1.dsc
  django-polymorphic_0.9.2.orig.tar.gz
  django-polymorphic_0.9.2-1.debian.tar.xz
  python-django-polymorphic-doc_0.9.2-1_all.deb
  python-django-polymorphic_0.9.2-1_all.deb
  python3-django-polymorphic_0.9.2-1_all.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] python-django 1.9.6-1 MIGRATED to testing

2016-05-12 Thread Debian testing watch

FYI: The status of the python-django source package
in Debian's testing distribution has changed.

  Previous version: 1.9.5-2
  Current version:  1.9.6-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Детский развивающий конструктор Funny Bricks

2016-05-12 Thread Karina

конструктор Funny Bricks (Gears)

Если вам нужна стоящая и полезная игрушка для ребенка, обратите внимание на 
конструктор Funny Bricks (Gears), для детей от 3 до 10 лет.
Он развивает творческие навыки, воображение, логику, моторику и 
пространственное 3D мышление. Конструктор Фани Брикс - уникальный!
Он состоит из 81 детали: строительных блоков-пазлов, которые нужно правильно 
сложить между собой и шестеренок, которые также нужно сложить правильно, чтобы 
весь механизм "заработал".
Из конструктора можно собрать настолько много различных вариантов - на сколько 
фантазии хватит у малыша и или родителей, воспитателей, бабушек и дедушек ;)
Рекомендуем - лучший конструктор для разностороннего развития ребенка.

Подробнее >>>

http://3ghk.ru/bricks.html

АКЦИЯ - СКИДКА 32% - СЕГОДНЯ
ВСЕГО - 295 грн.
Уверены - вам и деткам - понравится :)
Подробная информация: 38 097 140 63 67 (Киев)
пс. доставка по Киеву и Украине – БЕСПЛАТНО
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#824108: python-django: Insufficient build-dependency on python-sphinx

2016-05-12 Thread Micha Lenk


Source: python-django
Source-Version: 1.9.6-1

Hi,

for internal purposes I just tried to create a backported Debian package 
of python-django by building the package in a jessie environment. This 
failed with the following error:


make[2]: Entering directory '/home/mlenk/python-django-1.9.6/docs'
sphinx-build -b djangohtml -n -d _build/doctrees -D language=   . 
_build/html

Making output directory...
Running Sphinx v1.2.3

Sphinx version error:
This project needs at least Sphinx v1.3 and therefore cannot be built 
with this version.

Makefile:49: recipe for target 'html' failed
make[2]: *** [html] Error 1
make[2]: Leaving directory '/home/mlenk/python-django-1.9.6/docs'
debian/rules:17: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/home/mlenk/python-django-1.9.6'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

So, apparently the version requirements on python-sphinx defined in 
Build-Depends are not strict enough.


Best regards,
Micha

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

2016-05-12 Thread Dmitry Shachnev

Hi Helmut,

On Mon, Mar 14, 2016 at 07:05:11AM +0100, Helmut Grohne wrote:
> Hi Dmitry,
>
> Thank you for your quick and insightful reply.

As you can see, I don't always reply quickly. Sorry for the delay this time.

> Cross building only applied to arch-dep packages. So in jansson's case,
> it is not about libjansson-doc, but about the other packages. The only
> part of sphinx that is actually used during a cross build of jansson
> actually is the debhelper addon, which actually lives in sphinx-common
> and is exposed by python-sphinx. In a very similar case, Tomasz Buchert
> was able to move python-sphinx from Build-Depends to Build-Depends-Indep
> in nghttp2[1]. So looking at this closer again, a potential solution for
> sphinx could be:
>
>  * Mark sphinx-common Multi-Arch: foreign.
>  * Move python-sphinx from jansson's Build-Depends to
>Build-Depends-Indep.
>  * Add sphinx-common to jansson's Build-Depends.
>
> I didn't verify whether these changes are correct. We can try this to
> put urgency out of the loop.

I like the plan, though the third point can be avoided if dh_sphinxdoc is
called only during arch-indep build.

> If it were just jansson, I would certainly have spent more time on a
> workaround there. But we are talking about 161 source packages[2]. It
> seems highly likely that a significant fraction of them do not split
> their sphinx generated documentation into Arch:all packages.

161 is many packages, though in my opinion splitting the documentation into
arch:all packages is something that should be done independently of this bug.
Maybe we can have some kind of DD list whose packages are affected by this?
(Or a Lintian warning, see below.)

> I do not like the proposed solution at all. That is why I hesitated more
> than two years after recognizing that it would indeed fix things before
> actually sending a bug. I would certainly love to see a different
> solution.

I do not like it too... But I will try to do as much as possible from my side
to resolve this problem.

> Do you have any preferences on the approaches sketched above keeping in
> mind that we will apply it to hundreds of packages?

In an ideal world, the solution looks this way:

1) Packages shipping Sphinx documentation in arch:any packages should
split it into arch:all packages.

2) All packages using Sphinx should make sure dh_sphinxdoc is only called
during arch-indep build.

For 1), maybe we can have a Lintian warning for that?
(i.e. sphinx-documentation-in-architecture-dependent-package)

For 2), this means packages having both arch-dep and arch-indep packages won't
be able to use --with sphinxdoc because sphinxdoc.pm sequence won't be present
during arch:indep build. We can recommend packages to insert it manually then,
like:

override_dh_installdocs-indep:
dh_installdocs -i
dh_sphinxdoc -i

Alternatively, as you suggest, such packages may build-depend on sphinx-common
and I may mark sphinx-common as Muili-Arch: foreign. If it helps then I will
do that.

--
Dmitry Shachnev

signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

[Python-modules-team] python-scruffy_0.3.3-1_amd64.changes ACCEPTED into unstable, unstable

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

[Python-modules-team] django-polymorphic_0.9.2-1_amd64.changes ACCEPTED into unstable

[Python-modules-team] Processing of django-polymorphic_0.9.2-1_amd64.changes

[Python-modules-team] python-django 1.9.6-1 MIGRATED to testing

[Python-modules-team] Детский развивающий конструктор Funny Bricks

[Python-modules-team] Bug#824108: python-django: Insufficient build-dependency on python-sphinx

[Python-modules-team] Bug#818115: turn python-sphinx into an arch:any package

9 matches

Site Navigation

Mail list logo

Footer information