gcc-4.1 4.1.2-17 MIGRATED to testing

FYI: The status of the gcc-4.1 source package in Debian's testing distribution has changed. Previous version: 4.1.2-16 Current version: 4.1.2-17 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information.

[bts-link] source package gcc-4.0

# # bts-link upstream status pull for source package gcc-4.0 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #161432 # * http://gcc.gnu.org/PR8603 # * remote status changed: NEW -> ASSIGNED usertags 161432 - status-NE

[bts-link] source package gcc-snapshot

# # bts-link upstream status pull for source package gcc-snapshot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #448217 # * http://gcc.gnu.org/PR33923 # * remote status changed: ASSIGNED -> RESOLVED # * remote reso

Processed: [bts-link] source package gcc-snapshot

Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-snapshot > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status rep

Bug#170352: GNAT 4.1 issues a warning

fixed 170352 4.1.2-17 close 170352 thanks GNAT 4.1 properly issues the warning.

Processed: GNAT 4.1 issues a warning

Processing commands for [EMAIL PROTECTED]: > fixed 170352 4.1.2-17 Bug#170352: gnat: No warning when uninitialised variables used in record aggregates Bug marked as fixed in version 4.1.2-17. > close 170352 Bug#170352: gnat: No warning when uninitialised variables used in record aggregates 'clo