Your message dated Fri, 10 Mar 2017 21:26:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#671102: python-enable: FTBFS if built twice in a row:
aborting due to unexpected upstream changes
has caused the Debian Bug report #671102,
regarding python-enable: FTBFS if built twice in a row: aborting due to
unexpected upstream changes
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 [email protected]
immediately.)
--
671102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671102
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-enable
Version: 4.1.0-1
Severity: important
User: [email protected]
Usertags: qa-doublebuild
python-enable FTBFS if built twice in a row:
| dpkg-source -b python-enable-4.1.0
| dpkg-source: info: using source format `3.0 (quilt)'
| dpkg-source: info: building python-enable using existing
./python-enable_4.1.0.orig.tar.gz
| dpkg-source: warning: file python-enable-4.1.0/enable.egg-info/requires.txt
has no final newline (either original or modified version)
| dpkg-source: warning: file python-enable-4.1.0/enable.egg-info/SOURCES.txt
has no final newline (either original or modified version)
| dpkg-source: info: local changes detected, the modified files are:
| python-enable-4.1.0/enable.egg-info/PKG-INFO
| python-enable-4.1.0/enable.egg-info/SOURCES.txt
| python-enable-4.1.0/enable.egg-info/dependency_links.txt
| python-enable-4.1.0/enable.egg-info/not-zip-safe
| python-enable-4.1.0/enable.egg-info/requires.txt
| python-enable-4.1.0/enable.egg-info/top_level.txt
| dpkg-source: error: aborting due to unexpected upstream changes, see
/tmp/python-enable_4.1.0-1.diff.0PyIK0
| dpkg-source: info: you can integrate the local changes with dpkg-source
--commit
| dpkg-buildpackage: error: dpkg-source -b python-enable-4.1.0 gave error exit
status 2
--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Version: 4.5.1-1
On Tue, May 01, 2012 at 10:49:04PM +0200, Jakub Wilk wrote:
> python-enable FTBFS if built twice in a row:
> | dpkg-source -b python-enable-4.1.0
> | dpkg-source: info: using source format `3.0 (quilt)'
> | dpkg-source: info: building python-enable using existing
> ./python-enable_4.1.0.orig.tar.gz
> | dpkg-source: warning: file python-enable-4.1.0/enable.egg-info/requires.txt
> has no final newline (either original or modified version)
> | dpkg-source: warning: file python-enable-4.1.0/enable.egg-info/SOURCES.txt
> has no final newline (either original or modified version)
> | dpkg-source: info: local changes detected, the modified files are:
> | python-enable-4.1.0/enable.egg-info/PKG-INFO
> | python-enable-4.1.0/enable.egg-info/SOURCES.txt
> | python-enable-4.1.0/enable.egg-info/dependency_links.txt
> | python-enable-4.1.0/enable.egg-info/not-zip-safe
> | python-enable-4.1.0/enable.egg-info/requires.txt
> | python-enable-4.1.0/enable.egg-info/top_level.txt
> | dpkg-source: error: aborting due to unexpected upstream changes, see
> /tmp/python-enable_4.1.0-1.diff.0PyIK0
> | dpkg-source: info: you can integrate the local changes with dpkg-source
> --commit
> | dpkg-buildpackage: error: dpkg-source -b python-enable-4.1.0 gave error
> exit status 2
since 4.5.1-1 a d/s/options ignores those files.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
