[Python-modules-team] Processing of shiboken_1.0.2-2_amd64.changes

2011-05-03 Thread Debian FTP Masters
shiboken_1.0.2-2_amd64.changes uploaded successfully to localhost
along with the files:
  shiboken_1.0.2-2.dsc
  shiboken_1.0.2-2.debian.tar.gz
  shiboken_1.0.2-2_amd64.deb
  libshiboken1.0_1.0.2-2_amd64.deb
  libshiboken-dev_1.0.2-2_amd64.deb
  shiboken-dbg_1.0.2-2_amd64.deb
  shiboken-doc_1.0.2-2_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/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#625125: marked as done (django-countries: FTBFS: ImportError: No module named django.core.management)

2011-05-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 May 2011 13:29:29 +0200
with message-id 20110503112929.ga9...@jwilk.net
and subject line FTBFS: ImportError: No module named django...
has caused the Debian Bug report #625125,
regarding django-countries: FTBFS: ImportError: No module named 
django.core.management
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
625125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: django-countries
Version: 1.0.5-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
 make[1]: Entering directory 
 `/build/user-django-countries_1.0.5-1-amd64-WFy4cZ/django-countries-1.0.5'
 django-admin startproject testproject
 cp debian/settings.py testproject/settings.py
 set -e; \
   for python in python2.7 python2.6; do \
 rm -f testproject/test.db3 ; \
 PYTHONPATH=. $python testproject/manage.py syncdb 
 --settings=testproject.settings --noinput ;\
 PYTHONPATH=. $python testproject/manage.py test 
 --settings=testproject.settings ;\
   done
 Traceback (most recent call last):
   File testproject/manage.py, line 2, in module
 from django.core.management import execute_manager
 ImportError: No module named django.core.management
 make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/django-countries_1.0.5-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---

All these build failures were caused by a transient problem in python-django,
which is fixed now.

--
Jakub Wilk

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

[Python-modules-team] Bug#625129: marked as done (django-markupfield: FTBFS: ImportError: No module named django.core.management)

2011-05-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 May 2011 13:29:29 +0200
with message-id 20110503112929.ga9...@jwilk.net
and subject line FTBFS: ImportError: No module named django...
has caused the Debian Bug report #625129,
regarding django-markupfield: FTBFS: ImportError: No module named 
django.core.management
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
625129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: django-markupfield
Version: 1.0.1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
 make[1]: Entering directory 
 `/build/user-django-markupfield_1.0.1-1-amd64-77ve1L/django-markupfield-1.0.1'
 django-admin startproject testproject
 cp markupfield/tests/*.py testproject/
 set -e; \
   for python in python2.7 python2.6; do \
 $python testproject/manage.py test --settings=testproject.settings 
 --pythonpath=. ; \
   done
 Traceback (most recent call last):
   File testproject/manage.py, line 2, in module
 from django.core.management import execute_manager
 ImportError: No module named django.core.management
 make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/django-markupfield_1.0.1-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---

All these build failures were caused by a transient problem in python-django,
which is fixed now.

--
Jakub Wilk

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

[Python-modules-team] Bug#625138: marked as done (django-openid-auth: FTBFS: ImportError: No module named django.core.management)

2011-05-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 May 2011 13:29:29 +0200
with message-id 20110503112929.ga9...@jwilk.net
and subject line FTBFS: ImportError: No module named django...
has caused the Debian Bug report #625138,
regarding django-openid-auth: FTBFS: ImportError: No module named 
django.core.management
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
625138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: django-openid-auth
Version: 0.3-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
 make[1]: Entering directory 
 `/build/user-django-openid-auth_0.3-2-amd64-w573bL/django-openid-auth-0.3'
 set -e; \
   for python in python2.7 python2.6; do \
 PYTHONPATH=. $python example_consumer/manage.py test 
 --settings=example_consumer.settings django_openid_auth ; \
   done
 Traceback (most recent call last):
   File example_consumer/manage.py, line 2, in module
 from django.core.management import execute_manager
 ImportError: No module named django.core.management
 make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/django-openid-auth_0.3-2_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---

All these build failures were caused by a transient problem in python-django,
which is fixed now.

--
Jakub Wilk

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

[Python-modules-team] Bug#625149: marked as done (django-picklefield: FTBFS: ImportError: No module named django.core.management)

2011-05-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 May 2011 13:29:29 +0200
with message-id 20110503112929.ga9...@jwilk.net
and subject line FTBFS: ImportError: No module named django...
has caused the Debian Bug report #625149,
regarding django-picklefield: FTBFS: ImportError: No module named 
django.core.management
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
625149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: django-picklefield
Version: 0.1.9-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
 make[1]: Entering directory 
 `/build/user-django-picklefield_0.1.9-2-amd64-xrsGDV/django-picklefield-0.1.9'
 django-admin startproject testproject
 echo 'DATABASE_ENGINE = sqlite3'  testproject/settings.py
 echo 'INSTALLED_APPS = [picklefield]'  testproject/settings.py
 set -e; \
   for python in python2.7 python2.6; do \
 PYTHONPATH=.:src $python testproject/manage.py test 
 --settings=testproject.settings; \
   done
 Traceback (most recent call last):
   File testproject/manage.py, line 2, in module
 from django.core.management import execute_manager
 ImportError: No module named django.core.management
 make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/django-picklefield_0.1.9-2_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---

All these build failures were caused by a transient problem in python-django,
which is fixed now.

--
Jakub Wilk

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

[Python-modules-team] Bug#625128: marked as done (python-django-voting: FTBFS: ImportError: No module named django.test.simple)

2011-05-03 Thread Debian Bug Tracking System
Your message dated Tue, 3 May 2011 13:29:29 +0200
with message-id 20110503112929.ga9...@jwilk.net
and subject line FTBFS: ImportError: No module named django...
has caused the Debian Bug report #625128,
regarding python-django-voting: FTBFS: ImportError: No module named 
django.test.simple
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
625128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: python-django-voting
Version: 0+svn73-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
 make[1]: Entering directory 
 `/build/user-python-django-voting_0+svn73-1-amd64-sLdk4Z/python-django-voting-0+svn73'
 set -e; \
   cd voting/tests; \
   for python in python2.7 python2.6; do \
   PYTHONPATH=:../.. $python runtests.py; \
   done
 Traceback (most recent call last):
   File runtests.py, line 4, in module
 from django.test.simple import run_tests
 ImportError: No module named django.test.simple
 make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/python-django-voting_0+svn73-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |


---End Message---
---BeginMessage---

All these build failures were caused by a transient problem in python-django,
which is fixed now.

--
Jakub Wilk

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

[Python-modules-team] Bug#566172: (no subject)

2011-05-03 Thread Cleto Martín Angelina
Hi!

What is going on with this bug? Is it planned to build a package from
svn version to solve this problem?

Thanks for your job.

Cheers,
 Cleto.



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

[Python-modules-team] matplotlib in experimental

2011-05-03 Thread Nikolaus Rath
Hello,

Can you tell me what needs to happen for matplotlib 1.0 from
experimental to enter unstable and (eventually) testing? Are there any
critical showstoppers?

Can I safely download the source package and build it for my testing system?


Thanks for all your great Python packaging work!

Best,

   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C

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

[Python-modules-team] New version of imagemagick will hit experimental

2011-05-03 Thread Bastien ROUCARIES
Hi,

I have just achieved to get imagemagick sponsored. New version will
have a so bump (so experimental). Please take care of this.

Will upload in unstable in two weeks.

Bastien

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


[Python-modules-team] Incomplete upload found in Debian upload queue

2011-05-03 Thread Debian FTP Masters
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
  pyside_1.0.2-1.debian.tar.gz
  pyside_1.0.2-1.dsc
  pyside_1.0.2.orig.tar.bz2
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.

If no .changes file arrives within 23:14:40, the files will be deleted.

If you didn't upload those files, please just ignore this message.

Greetings,

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

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


[Python-modules-team] Processing of pyglet_1.1.4.dfsg-2_amd64.changes

2011-05-03 Thread Debian FTP Masters
pyglet_1.1.4.dfsg-2_amd64.changes uploaded successfully to localhost
along with the files:
  pyglet_1.1.4.dfsg-2.dsc
  pyglet_1.1.4.dfsg-2.debian.tar.gz
  python-pyglet_1.1.4.dfsg-2_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/mailman/listinfo/python-modules-team


[Python-modules-team] Processing of pyside_1.0.2-1_amd64.changes

2011-05-03 Thread Debian FTP Masters
pyside_1.0.2-1_amd64.changes uploaded successfully to ftp-master.debian.org
along with the files:
  pyside_1.0.2-1.dsc
  pyside_1.0.2.orig.tar.bz2
  pyside_1.0.2-1.debian.tar.gz
  python-pyside_1.0.2-1_all.deb
  python-pyside-dbg_1.0.2-1_amd64.deb
  libpyside1.0_1.0.2-1_amd64.deb
  libpyside-dev_1.0.2-1_amd64.deb
  python-pyside.qtcore_1.0.2-1_amd64.deb
  python-pyside.qtdeclarative_1.0.2-1_amd64.deb
  python-pyside.qtgui_1.0.2-1_amd64.deb
  python-pyside.qthelp_1.0.2-1_amd64.deb
  python-pyside.qtnetwork_1.0.2-1_amd64.deb
  python-pyside.qtopengl_1.0.2-1_amd64.deb
  python-pyside.phonon_1.0.2-1_amd64.deb
  python-pyside.qtscript_1.0.2-1_amd64.deb
  python-pyside.qtsql_1.0.2-1_amd64.deb
  python-pyside.qtsvg_1.0.2-1_amd64.deb
  python-pyside.qttest_1.0.2-1_amd64.deb
  python-pyside.qtuitools_1.0.2-1_amd64.deb
  python-pyside.qtwebkit_1.0.2-1_amd64.deb
  python-pyside.qtxml_1.0.2-1_amd64.deb

Greetings,

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

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


[Python-modules-team] Processing of pyside_1.0.2-1_amd64.changes

2011-05-03 Thread Debian FTP Masters
pyside_1.0.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  pyside_1.0.2-1.dsc
  pyside_1.0.2.orig.tar.bz2
  pyside_1.0.2-1.debian.tar.gz
  python-pyside_1.0.2-1_all.deb
  python-pyside-dbg_1.0.2-1_amd64.deb
  libpyside1.0_1.0.2-1_amd64.deb
  libpyside-dev_1.0.2-1_amd64.deb
  python-pyside.qtcore_1.0.2-1_amd64.deb
  python-pyside.qtdeclarative_1.0.2-1_amd64.deb
  python-pyside.qtgui_1.0.2-1_amd64.deb
  python-pyside.qthelp_1.0.2-1_amd64.deb
  python-pyside.qtnetwork_1.0.2-1_amd64.deb
  python-pyside.qtopengl_1.0.2-1_amd64.deb
  python-pyside.phonon_1.0.2-1_amd64.deb
  python-pyside.qtscript_1.0.2-1_amd64.deb
  python-pyside.qtsql_1.0.2-1_amd64.deb
  python-pyside.qtsvg_1.0.2-1_amd64.deb
  python-pyside.qttest_1.0.2-1_amd64.deb
  python-pyside.qtuitools_1.0.2-1_amd64.deb
  python-pyside.qtwebkit_1.0.2-1_amd64.deb
  python-pyside.qtxml_1.0.2-1_amd64.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/mailman/listinfo/python-modules-team


[Python-modules-team] pyglet_1.1.4.dfsg-2_amd64.changes ACCEPTED into unstable

2011-05-03 Thread Debian FTP Masters



Accepted:
pyglet_1.1.4.dfsg-2.debian.tar.gz
  to main/p/pyglet/pyglet_1.1.4.dfsg-2.debian.tar.gz
pyglet_1.1.4.dfsg-2.dsc
  to main/p/pyglet/pyglet_1.1.4.dfsg-2.dsc
python-pyglet_1.1.4.dfsg-2_all.deb
  to main/p/pyglet/python-pyglet_1.1.4.dfsg-2_all.deb


Override entries for your package:
pyglet_1.1.4.dfsg-2.dsc - source python
python-pyglet_1.1.4.dfsg-2_all.deb - optional python

Announcing to debian-devel-chan...@lists.debian.org


Thank you for your contribution to Debian.

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


[Python-modules-team] pyside_1.0.2-1_amd64.changes ACCEPTED into unstable

2011-05-03 Thread Debian FTP Masters



Accepted:
libpyside-dev_1.0.2-1_amd64.deb
  to main/p/pyside/libpyside-dev_1.0.2-1_amd64.deb
libpyside1.0_1.0.2-1_amd64.deb
  to main/p/pyside/libpyside1.0_1.0.2-1_amd64.deb
pyside_1.0.2-1.debian.tar.gz
  to main/p/pyside/pyside_1.0.2-1.debian.tar.gz
pyside_1.0.2-1.dsc
  to main/p/pyside/pyside_1.0.2-1.dsc
pyside_1.0.2.orig.tar.bz2
  to main/p/pyside/pyside_1.0.2.orig.tar.bz2
python-pyside-dbg_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside-dbg_1.0.2-1_amd64.deb
python-pyside.phonon_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.phonon_1.0.2-1_amd64.deb
python-pyside.qtcore_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtcore_1.0.2-1_amd64.deb
python-pyside.qtdeclarative_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtdeclarative_1.0.2-1_amd64.deb
python-pyside.qtgui_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtgui_1.0.2-1_amd64.deb
python-pyside.qthelp_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qthelp_1.0.2-1_amd64.deb
python-pyside.qtnetwork_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtnetwork_1.0.2-1_amd64.deb
python-pyside.qtopengl_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtopengl_1.0.2-1_amd64.deb
python-pyside.qtscript_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtscript_1.0.2-1_amd64.deb
python-pyside.qtsql_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtsql_1.0.2-1_amd64.deb
python-pyside.qtsvg_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtsvg_1.0.2-1_amd64.deb
python-pyside.qttest_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qttest_1.0.2-1_amd64.deb
python-pyside.qtuitools_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtuitools_1.0.2-1_amd64.deb
python-pyside.qtwebkit_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtwebkit_1.0.2-1_amd64.deb
python-pyside.qtxml_1.0.2-1_amd64.deb
  to main/p/pyside/python-pyside.qtxml_1.0.2-1_amd64.deb
python-pyside_1.0.2-1_all.deb
  to main/p/pyside/python-pyside_1.0.2-1_all.deb


Override entries for your package:
libpyside-dev_1.0.2-1_amd64.deb - optional libdevel
libpyside1.0_1.0.2-1_amd64.deb - optional python
pyside_1.0.2-1.dsc - source python
python-pyside-dbg_1.0.2-1_amd64.deb - extra debug
python-pyside.phonon_1.0.2-1_amd64.deb - optional python
python-pyside.qtcore_1.0.2-1_amd64.deb - optional python
python-pyside.qtdeclarative_1.0.2-1_amd64.deb - optional python
python-pyside.qtgui_1.0.2-1_amd64.deb - optional python
python-pyside.qthelp_1.0.2-1_amd64.deb - optional python
python-pyside.qtnetwork_1.0.2-1_amd64.deb - optional python
python-pyside.qtopengl_1.0.2-1_amd64.deb - optional python
python-pyside.qtscript_1.0.2-1_amd64.deb - optional python
python-pyside.qtsql_1.0.2-1_amd64.deb - optional python
python-pyside.qtsvg_1.0.2-1_amd64.deb - optional python
python-pyside.qttest_1.0.2-1_amd64.deb - optional python
python-pyside.qtuitools_1.0.2-1_amd64.deb - optional python
python-pyside.qtwebkit_1.0.2-1_amd64.deb - optional python
python-pyside.qtxml_1.0.2-1_amd64.deb - optional python
python-pyside_1.0.2-1_all.deb - optional python

Announcing to debian-devel-chan...@lists.debian.org


Thank you for your contribution to Debian.

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


[Python-modules-team] Bug#623033: marked as done (1.8.8-1+b2 breaks gnome-devel)

2011-05-03 Thread Debian Bug Tracking System
Your message dated Wed, 4 May 2011 02:25:14 +0200
with message-id 20110504002514.ga2...@jwilk.net
and subject line Re: Bug#623033: 1.8.8-1+b2 breaks gnome-devel
has caused the Debian Bug report #623033,
regarding 1.8.8-1+b2 breaks gnome-devel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
623033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-cairo
Version: 1.8.8-1+b2

Python2.5-cairo is still needed by many things, but the +b2 rebuild no longer
Provides: it.

E.g.
gnome-devel  gnome-core-devel  python-gtk2-dev  python-gtk2  python2.5-cairo


---End Message---
---BeginMessage---

Python2.5-cairo is still needed by many things, but the +b2 rebuild no longer
Provides: it.

E.g.
gnome-devel  gnome-core-devel  python-gtk2-dev  python-gtk2  python2.5-cairo


As far as I can tell, this is now fixed. (gnome-devel is uninstallable 
for the momen, but for unrelated reasons.)


--
Jakub Wilk

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