Adam D. Barratt wrote:

> If the change were made today and it was purely the text change, we 
> might just squeeze it in. NEWS.Debian will only be displayed to
> people upgrading from earlier versions, so of those two options the
> description would probably be more useful.

Ok, I'm currently building a package with the following description
change.
A couple of questions for the RT:
* gcc-msp430 is at the same version on sid and testing, can I target this -4 to
  unstable and let it migrate from there? Or should I build a -3+wheezy1 in a
  wheezy chroot and target t-p-u?
* Should I also provide a small paragraph for the release notes remarking the 
  issue and saying that it will be fixed really soon?

Debdiff inline below, please ACK:

diff -Nru gcc-msp430-4.6.3~mspgcc-20120406/debian/changelog 
gcc-msp430-4.6.3~mspgcc-20120406/debian/changelog
--- gcc-msp430-4.6.3~mspgcc-20120406/debian/changelog   2012-05-20 
13:53:45.000000000 +0200
+++ gcc-msp430-4.6.3~mspgcc-20120406/debian/changelog   2013-05-02 
10:13:41.000000000 +0200
@@ -1,3 +1,12 @@
+gcc-msp430 (4.6.3~mspgcc-20120406-4) unstable; urgency=high
+
+  * Change package description to mention the incompatibility
+    with MSP430FR5xxx chips (eg. Fraunchpad board).
+    This package DOES NOT work on that chips series, and will
+    brick it.
+
+ -- Luca Bruno <lu...@debian.org>  Thu, 02 May 2013 10:10:38 +0200
+
 gcc-msp430 (4.6.3~mspgcc-20120406-3) unstable; urgency=low
 
   * Disable features not relevant to msp430
diff -Nru gcc-msp430-4.6.3~mspgcc-20120406/debian/control 
gcc-msp430-4.6.3~mspgcc-20120406/debian/control
--- gcc-msp430-4.6.3~mspgcc-20120406/debian/control     2012-05-17 
09:06:33.000000000 +0200
+++ gcc-msp430-4.6.3~mspgcc-20120406/debian/control     2013-05-02 
10:10:13.000000000 +0200
@@ -20,3 +20,8 @@
  This is the GNU C compiler, a fairly portable optimizing compiler for C
  for TI's MSP430 architecture.  This package is primarily for MSP430 
  developers and cross-compilers and is not needed by normal users.
+ .
+ BEWARE: due to a bug in the memory layout reference of FRAM-based chips, 
+ this package DOES NOT WORK with MSP430FR5xxx chips (eg. FraunchPad devkit).
+ DO NOT use gcc-msp430 on that chip series, as you will lose access to
+ JTAG and BSL, and permanently BRICK your chip!

Cheers, Luca

-- 
  .''`.  |               ~<[ Luca BRUNO ~ (kaeso) ]>~
 : :'  : | Email: lucab (AT) debian.org ~ Debian Developer
 `. `'`  | GPG Key ID: 0x3BFB9FB3       ~ Free Software supporter
   `-    | HAM-radio callsign: IZ1WGT   ~ Networking sorcerer

Attachment: signature.asc
Description: PGP signature

Reply via email to