[ubuntu/oneiric] massxpert 2.5.2-1 (Accepted)

[Fabrice Coutadeur]

massxpert (2.5.2-1) unstable; urgency=low

  * New upstream release:
  
    - Fix regression causing a crash when fragmenting oligomers in any
    kind of situation. This fix is critical.
  

massxpert (2.5.1-1) unstable; urgency=low

  * Modified the email address of the uploader to my debian address
    lopippo at debian.org.
  * Removed the DM-Upload-Allowed bit.
  
  * New upstream release:
  
    - Fix serious bug that crashed the program upon recleaving a polymer
    within the same CleavageDlg window. That bug appeared related to the
    upgrade of the Qt libraries as it crept without modifications of the
    massXpert source code. The cleavage oligomers are now displayed in a
    QTableView widget instead of a QTreeView widget which simplified a lot
    both the code and the graphics display of the data.
  
    - Fix problems with the reliability of the cleavage details that were
    provided as feedback when an oligomer from the tree/table view was
    selected.

massxpert (2.5.0-1) unstable; urgency=low

  * New upstream release:
  
    - Implement feature allowing one to apply formulas commonly found
    during fragmentation, like loss of water or loss of ammonia, to each
    fragment oligomer computed for any given fragmentation pattern.

massxpert (2.4.4-1) unstable; urgency=low

  * New upstream release:
  
    - Fix FTBFS with gcc-4.6 -Werror (this package builds with -Werror,
    and GCC 4.6 triggers new warnings) reported by Matthias Klose
    <doko at debian.org> (Closes: #625382).

massxpert (2.4.3-1) unstable; urgency=low

  * Upstream release. 
    
    - Rewrote the Formula's elementalComposition() so that the order of
    the atoms is in the CHNO->alphabetic conventional order;
    
    - Added ion charge proton to the formula of the z fragmentation
    specification;
    
    - Added feature: when running the mz calculations dialog from the
    sequence editor window, the masses are automatically set in the dialog
    window
    

massxpert (2.4.2-1) unstable; urgency=low

  * New upstream release:
  
    - Fix bug (Closes: #611142) due to insufficient checking of the array
    boundary upon clicking on the sequence editor outside of the vignettes.
  
    - debian/control : Standards-Version: 3.9.1.

massxpert (2.4.1-1) unstable; urgency=low

  * Fix bug due to returning false when should return a string. Thanks to
    Mathias Klose <doko at ubuntu.com> for reporting the bug, and to Stéphane
    Téletchéa <steletch at free.fr> for reporting the same in private
    (Closes: #607723).

Date: Thu,  09 Jun 2011 12:00:24 +0000
Changed-By: Fabrice Coutadeur <coutadeurf at gmail.com>
Maintainer: The Debichem Group <debichem-devel at lists.alioth.debian.org>
Origin: Debian/unstable
https://launchpad.net/ubuntu/oneiric/+source/massxpert/2.5.2-1
-------------- next part --------------
Origin: Debian/unstable
Format: 1.7
Date: Thu,  09 Jun 2011 12:00:24 +0000
Source: massxpert
Binary: massxpert, massxpert-data, massxpert-doc
Architecture: source
Version: 2.5.2-1
Distribution: oneiric
Urgency: low
Maintainer: The Debichem Group <debichem-devel at lists.alioth.debian.org>
Changed-By: Fabrice Coutadeur <coutadeurf at gmail.com>
Description:
 massxpert  - linear polymer mass spectrometry software
Closes: 607723 611142 625382
Files:
 cd59a3c23501e35c58708ee40b49f554 12317 science optional massxpert_2.5.2-1.debian.tar.gz
 5129e3307146f915af17be90a360cf7b 1370 science optional massxpert_2.5.2-1.dsc
 ed453e61e5d292ea4aed4067f89228c8 14224803 science optional massxpert_2.5.2.orig.tar.gz
Changes:
 massxpert (2.5.2-1) unstable; urgency=low
 .
   * New upstream release:
   
     - Fix regression causing a crash when fragmenting oligomers in any
     kind of situation. This fix is critical.
   
 .
 massxpert (2.5.1-1) unstable; urgency=low
 .
   * Modified the email address of the uploader to my debian address
     lopippo at debian.org.
   * Removed the DM-Upload-Allowed bit.
   
   * New upstream release:
   
     - Fix serious bug that crashed the program upon recleaving a polymer
     within the same CleavageDlg window. That bug appeared related to the
     upgrade of the Qt libraries as it crept without modifications of the
     massXpert source code. The cleavage oligomers are now displayed in a
     QTableView widget instead of a QTreeView widget which simplified a lot
     both the code and the graphics display of the data.
   
     - Fix problems with the reliability of the cleavage details that were
     provided as feedback when an oligomer from the tree/table view was
     selected.
 .
 massxpert (2.5.0-1) unstable; urgency=low
 .
   * New upstream release:
   
     - Implement feature allowing one to apply formulas commonly found
     during fragmentation, like loss of water or loss of ammonia, to each
     fragment oligomer computed for any given fragmentation pattern.
 .
 massxpert (2.4.4-1) unstable; urgency=low
 .
   * New upstream release:
   
     - Fix FTBFS with gcc-4.6 -Werror (this package builds with -Werror,
     and GCC 4.6 triggers new warnings) reported by Matthias Klose
     <doko at debian.org> (Closes: #625382).
 .
 massxpert (2.4.3-1) unstable; urgency=low
 .
   * Upstream release. 
     
     - Rewrote the Formula's elementalComposition() so that the order of
     the atoms is in the CHNO->alphabetic conventional order;
     
     - Added ion charge proton to the formula of the z fragmentation
     specification;
     
     - Added feature: when running the mz calculations dialog from the
     sequence editor window, the masses are automatically set in the dialog
     window
     
 .
 massxpert (2.4.2-1) unstable; urgency=low
 .
   * New upstream release:
   
     - Fix bug (Closes: #611142) due to insufficient checking of the array
     boundary upon clicking on the sequence editor outside of the vignettes.
   
     - debian/control : Standards-Version: 3.9.1.
 .
 massxpert (2.4.1-1) unstable; urgency=low
 .
   * Fix bug due to returning false when should return a string. Thanks to
     Mathias Klose <doko at ubuntu.com> for reporting the bug, and to Stéphane
     Téletchéa <steletch at free.fr> for reporting the same in private
     (Closes: #607723).