[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#681825: marked as done (django-notification: fails to build twice in a row)

Your message dated Sat, 02 Jul 2016 17:23:35 +0000
with message-id <E1bJOdj-0004st-JI@franck.debian.org>
and subject line Bug#681825: fixed in django-notification 0.1.5-4
has caused the Debian Bug report #681825,
regarding django-notification: fails to build twice in a row
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 owner@bugs.debian.org
immediately.)


-- 
681825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681825
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: django-notification
Version: 0.1.5-1
Severity: important

Log tail:

dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building django-notification using existing ./django-notification_0.1.5.orig.tar.gz
dpkg-source: info: local changes detected, the modified files are:
 django-notification-0.1.5/django_notification.egg-info/PKG-INFO
 django-notification-0.1.5/django_notification.egg-info/SOURCES.txt
dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/django-notification_0.1.5-1.diff.qSPDBb
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-buildpackage: error: dpkg-source -b django-notification-0.1.5 gave error exit status 2



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
Source: django-notification
Source-Version: 0.1.5-4

We believe that the bug you reported is fixed in the latest version of
django-notification, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 681825@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto <hpfn@debian.org> (supplier of updated django-notification package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 01 Jul 2016 12:23:55 -0300
Source: django-notification
Binary: python-django-notification
Architecture: source all
Version: 0.1.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Herbert Parentes Fortes Neto <hpfn@debian.org>
Description:
 python-django-notification - user notification management for Django
Closes: 681825
Changes:
 django-notification (0.1.5-4) unstable; urgency=medium
 .
   * QA upload.
   * DH_LEVEL: 9
   * egg-info SOURCES.txt file is not being packaged by the packaging
     system. http://setuptools.readthedocs.io says that the file is not so
     important, so I am doing nothing about it.
   * debian/copyright:
       - format 1.0
       - updated
   * debian/control:
       - Build-Depends-Indep field removed.
       - python-all added to Build-Depends.
       - dh-python added to Build-Depends.
       - using X-Python-Version: >= 2.5
       - bump Standards-Version from 3.9.3 to 3.9.8
       - Vcs-* updated and using https.
   * debian/rules:
       - override_dh_clean added. (Closes: #681825)
   * debian/watch:
       - the project has a new name now. There is no need to create an
         operational debian/watch file. Just putting an information that
         the project has a new name.
Checksums-Sha1:
 54566ffa604102e377141c7bb0fba9964da3f104 2023 django-notification_0.1.5-4.dsc
 ea1092fa2269d11962be78efc0c9a9099fa7a66a 3044 django-notification_0.1.5-4.debian.tar.xz
 f1e552373447915388748045e8f71469691e03c9 20842 python-django-notification_0.1.5-4_all.deb
Checksums-Sha256:
 11c3565beeeae1f1882ef7f4127bc39dd15e4a0a30cf3f81774347a88941b0d8 2023 django-notification_0.1.5-4.dsc
 c0deecf2012a98724f0ef45660f9ec23ea4250515ae7d36b45e088fd94d88033 3044 django-notification_0.1.5-4.debian.tar.xz
 93fcc6700e297f4af6a6748eeaec2302630dd7d76d0c99988066df6855f0b2b9 20842 python-django-notification_0.1.5-4_all.deb
Files:
 068616aa36d64d136961702b98629895 2023 python optional django-notification_0.1.5-4.dsc
 3c393305a35598e819212c185afec035 3044 python optional django-notification_0.1.5-4.debian.tar.xz
 d1ce1900363189cbc020b9c32d01ee8e 20842 python optional python-django-notification_0.1.5-4_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJXdqSaAAoJEFUlbyisYGEaqZgQAJwcR8Cb8FCRCkN5sKD7zdq8
+4pgoBqunmuCzhIbE8SlSgui9JuPieOmkLhKEIruhpYm+AUqTAkBJSTCL/mLwY+R
y9HaOlt7jpWSUFWfVYs4Ul9aurES8TQRi6VCJJDoyztuNg0XP0hRK2kF0VqaSpGj
ckcAxmiUsV7gjo8LEdHqAxbXCmkSxnusQQBIBA+eaQtLnzDSuJZGx7Ab+U3yjwWd
jQV4cOkPw/FDydkoyahsTwVQ9IwxsiFYCbPhFC8rJUerGJ/v/eNBCMao6RTF9uuu
ikPwTVO5SCjavYkH8E7MHejSuQ+g3XnaQoUbOce6YeBQW7SMKHX80horAkWeUL2V
tBWWb6P0/FUYYmCBHXxgldwdGQncvn3TMAMqEiu6y6Cztk8AdrOR3HPp9siblA5+
ygVhUGmK1PbLrMbugJ9wwiN4uQvHxSGAzZmh9AHrZs0nIhjKDLQt2NWMToduuusn
TPN6JuomT6cGqJXaco54+6aOPbMaMsrqyzDtMWNk2X5zd/FfrpZSQbu5FujxQuWu
UZTREF38bBUKxElDdMbwrVt9LiTc5WdxYn9meTg0hrSvUyohDT4+J8cqdMNjzkKa
N5VsWSB97V4D5ZLiJAGZmsrFelSH7ruV7k2ptdUJIsGYczEfyPsuK1466pqGyAln
cJiRZUZiwmjOxXM/4Ytz
=Hqhw
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: