Your message dated Sat, 31 Dec 2016 19:21:20 +0000
with message-id <[email protected]>
and subject line Bug#849815: fixed in julia 0.4.7-3
has caused the Debian Bug report #849815,
regarding julia: Please set TAGGED_RELEASE_BANNER to identify Debian package 
builds
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.)


-- 
849815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849815
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: julia
Version: 0.4.7-2
Severity: wishlist

Dear Maintainer,

In order to more clearly identify when an issue gets reported upstream
by someone who may be using the debian package build of julia, I'd like
to request that the debian build process set the TAGGED_RELEASE_BANNER
makefile flag when compiling julia. The identifier string from that flag
will be shown between the version number and the platform triple in the
julia startup banner. Something that identifies the copy of julia as
built in a debian packaging configuration will help us determine whether
reported bugs are due to the debian packaging in particular, if we have
trouble reproducing. I would prefer to have it set in a way that can be
easily (automatically?) overridden by debian derivatives as well.


-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-43-Microsoft
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
Source: julia
Source-Version: 0.4.7-3

We believe that the bug you reported is fixed in the latest version of
julia, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Colberg <[email protected]> (supplier of updated julia 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: SHA512

Format: 1.8
Date: Sat, 31 Dec 2016 13:43:20 -0500
Source: julia
Binary: julia julia-common julia-doc
Architecture: source
Version: 0.4.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Julia Team <[email protected]>
Changed-By: Peter Colberg <[email protected]>
Description:
 julia      - high-performance programming language for technical computing
 julia-common - high-performance programming language for technical computing 
(co
 julia-doc  - high-performance programming language for technical computing (do
Closes: 849815
Changes:
 julia (0.4.7-3) unstable; urgency=medium
 .
   * Set TAGGED_RELEASE_BANNER to distribution and source package version
     (Closes: #849815)
Checksums-Sha1:
 c1d0516c2918733ed4531d3eba585539f6a45a8e 2595 julia_0.4.7-3.dsc
 2c9723bbfd49a682ebb1911e7d6b31007ef0d54d 24044 julia_0.4.7-3.debian.tar.xz
Checksums-Sha256:
 e88f7e616e08d89099f63388186c39fe2453c883c604342c6ffde8da1c19acc6 2595 
julia_0.4.7-3.dsc
 a6988baa8e474c9d80a937e99e5de645d7ae6e739b30f370fced99da242dd98b 24044 
julia_0.4.7-3.debian.tar.xz
Files:
 f3501e9af198099787d0da3fd5f49997 2595 science extra julia_0.4.7-3.dsc
 213a35b1e76cd6770071ae76601fd5f6 24044 science extra 
julia_0.4.7-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEmDv50PAqYBQM7FKfdn4SqMkqMcsFAlhn/TQSHHBldGVyQGNv
bGJlcmcub3JnAAoJEHZ+EqjJKjHLdkYP/1dPJ7GDW01yovolZc166g+60z9nh+ES
cOQw+WMuSqrDm16z4/p9Lp4nfCoOMaL4Af0fOMySL822Qe48UNcSE1vIAS+OLMUm
GneSbdixSL/GbnvigeDG2LRNJcAqqDWJgVduEielN2L+5xeM8BjymTuH0V8BGo+/
+fBMd053bBpPpwWMkcDgHJtS7xqX1P5fuh9m7Ssz+9qErF71ieUdfFb8faWGJpzY
gGjp23vnbXev0ShzRDGmd7whbiLdmvUC9cB/BJ5wjrEHx7qjWdeyYkeZ68AVhf9w
00L1amS2c/bXRvotD+aRRfI3QjeYXediiLm8IYZprAkOrzj4wNSQ4Xjv+O0Z5P2W
rOwsbWiXv2qt+PlRyeDZ0TTQlXz5DQavumik8yew84wYqo+aLYBv+eq9wQyQzvYJ
G0keSUzlRS2INRY4NSc6cicCYrJ3VlkBV60AAHbGr2wyi95YGGltgByFDhztTtYA
Ydoy+c/5jISWc13kRJ5K7mZeqMUbWiMnR+MECHJxsX5hnGxS83LAToOaWbgGdaH5
AuHT6/Tk0L+iSsDJbzv7mVoPXwcI6h/u2uPzRyA2ENrnTaGNtVF+LX6/kmJDmd4Y
UoJneqCDEpLDh0MO+6/ilaA6QK+jSVGFxzTOpX/1HiUSpAkTtGhYoaknIfOzbHts
vHld2AHrzHMp
=phrq
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to