Your message dated Mon, 16 Oct 2006 08:16:32 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357684: fixed in singularity 0.25-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: singularity
Version: 0.22-1
Severity: minor
This package is "arch: any" but it doesn't (afaik) include any
architecture specific code, so it should be "arch: all".
> Automatic build of singularity_0.22-1 on bigsur by sbuild/mips 1.106
...
> patches: debian/patches/01_saveload.patch debian/patches/02_launcher.patch
> Not reversing not applied patches.
> if [ "reverse-patches" = "debian/stamp-patched" ] ; then touch
> debian/stamp-patched ; \
> elif [ "reverse-patches" = "reverse-patches" ] ; then rm -f
> debian/stamp-patch* ; \
> fi
> if [ "reverse-patches" != "reverse-patches" ] ; then \
> /usr/bin/make -f debian/rules update-config ; \
> fi
> for dir in debian/patches ; do \
> rm -f $dir/*.log ; \
> done
> rm -f singularity.6
> debian/rules build
> test -x debian/rules
> if [ -n "" ]; then \
> mkdir -p ""; \
> fi
> if [ ! -d "." ]; then \
> mkdir -p "."; \
> fi
> if [ -z "" ]; then \
> if ! test -f debian/compat; then echo 4 > debian/compat; fi; \
> fi
> /usr/bin/make -f debian/rules reverse-config
> make[1]: Entering directory `/build/tbm/singularity-0.22'
> make[1]: Nothing to be done for `reverse-config'.
> make[1]: Leaving directory `/build/tbm/singularity-0.22'
> patches: debian/patches/01_saveload.patch debian/patches/02_launcher.patch
> Trying patch debian/patches/01_saveload.patch at level 0...1...success.
> Trying patch debian/patches/02_launcher.patch at level 0...1...success.
> if [ "debian/stamp-patched" = "debian/stamp-patched" ] ; then touch
> debian/stamp-patched ; \
> elif [ "debian/stamp-patched" = "reverse-patches" ] ; then rm -f
> debian/stamp-patch* ; \
> fi
> if [ "debian/stamp-patched" != "reverse-patches" ] ; then \
> /usr/bin/make -f debian/rules update-config ; \
> fi
> make[1]: Entering directory `/build/tbm/singularity-0.22'
> make[1]: Nothing to be done for `update-config'.
> make[1]: Leaving directory `/build/tbm/singularity-0.22'
> /usr/bin/fakeroot debian/rules binary-arch
> test -x debian/rules
> test "`id -u`" = 0
> dh_clean -k
> dh_installdirs -A
> if [ -n "" ]; then \
> mkdir -p ""; \
> fi
> if [ ! -d "." ]; then \
> mkdir -p "."; \
> fi
> if [ -z "" ]; then \
> if ! test -f debian/compat; then echo 4 > debian/compat; fi; \
> fi
> dh_installdirs -psingularity
> dh_installdocs -psingularity ./AUTHORS
> dh_installexamples -psingularity
...
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Source: singularity
Source-Version: 0.25-1
We believe that the bug you reported is fixed in the latest version of
singularity, which is due to be installed in the Debian FTP archive:
singularity_0.25-1.diff.gz
to pool/contrib/s/singularity/singularity_0.25-1.diff.gz
singularity_0.25-1.dsc
to pool/contrib/s/singularity/singularity_0.25-1.dsc
singularity_0.25-1_all.deb
to pool/contrib/s/singularity/singularity_0.25-1_all.deb
singularity_0.25.orig.tar.gz
to pool/contrib/s/singularity/singularity_0.25.orig.tar.gz
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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Kari Pahula <[EMAIL PROTECTED]> (supplier of updated singularity 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 [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 2 Oct 2006 23:09:59 +0300
Source: singularity
Binary: singularity
Architecture: source all
Version: 0.25-1
Distribution: unstable
Urgency: low
Maintainer: Kari Pahula <[EMAIL PROTECTED]>
Changed-By: Kari Pahula <[EMAIL PROTECTED]>
Description:
singularity - game where one becomes the singularity
Closes: 353750 353886 355216 357684 380950 386187 390413
Changes:
singularity (0.25-1) unstable; urgency=low
.
* New maintainters
* New upstream release (Closes: #353750, #353886, #386187)
.
[Ana Beatriz Guerrero Lopez]
* Updated package to the last Python Policy (Closes: #380950).
* Bumped compat to 5.
* Bumped Standards-Version to 3.7.2, no changes required.
* Changed to "Architecture: all" since the package does not include
any architecture specific code (Closes: #357684).
* Fixed minor errors in the description and man page (Closes: #355216).
Thanks to Drake Wilson for the corrections.
* Added Homepage in debian/control
* Updated watch file
.
[Kari Pahula]
* Switched over to use quilt for patches
* Moved game data from /usr/share/singularity to
/usr/share/games/singularity
* Updated the debian/copyright file
* Repackaged orig.tar.gz to split non-free game data to singularity-data
package. Resectioned singularity to contrib/games (Closes: #390413).
* Removed bitstream-vera-ttf font from the repackaged orig.tar.gz too.
* Added icon entry in menu file
Files:
bd965c237c63e96fb6cf3d8424029898 693 contrib/games optional
singularity_0.25-1.dsc
00d63f7acaf415b5dcef0570c6f30446 364596 contrib/games optional
singularity_0.25.orig.tar.gz
beade96a0dbc68ee50285124a43144fa 5012 contrib/games optional
singularity_0.25-1.diff.gz
358ab12d3cf89794b24ecc3995b3af8a 311322 contrib/games optional
singularity_0.25-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFIXI+eYl9593Atw0RArQfAJ4yHwfG6dbuyVpo4mfYsVPUNPyIcwCgqQ45
HbnHbmqdI6xM07/XL2wZKXw=
=ca6O
-----END PGP SIGNATURE-----
--- End Message ---
