[Bug 1078012] [NEW] Sync picard-tools 1.79-1 (universe) from Debian unstable (main)
Launchpad Bug Tracker
1078012 at bugs.launchpad.net
Mon Nov 12 16:36:01 UTC 2012
You have been subscribed to a public bug by Logan Rosen (logan):
Please sync picard-tools 1.79-1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Transition package to use default java implementation:
- d/control: BD on default-jdk, switch runtime dependency to
default-jre | java6-runtime.
- d/rules: Specify source/target = 1.5 to ensure that backwards
compatible bytecode is built.
All of the Ubuntu changes were made in Debian as well, so a sync is fine for this package.
Changelog entries since current raring version 1.46-1ubuntu1:
picard-tools (1.79-1) unstable; urgency=low
* New upstream release 1.79
-- Olivier Sallou <osallou at debian.org> Mon, 29 Oct 2012 08:58:44 +0100
picard-tools (1.78-1) unstable; urgency=low
* New upstream release
-- Olivier Sallou <osallou at debian.org> Sat, 13 Oct 2012 11:20:49 +0200
picard-tools (1.77-1) unstable; urgency=low
* New upstream release
-- Olivier Sallou <osallou at debian.org> Fri, 21 Sep 2012 16:41:23 +0200
picard-tools (1.76-1) unstable; urgency=low
* New upstream release
-- Olivier Sallou <osallou at debian.org> Fri, 07 Sep 2012 11:44:03 +0200
picard-tools (1.75-1) unstable; urgency=low
[Olivier Sallou]
* New upstream releases.
* Build-depend on libsnappy1.0.3-java (debian/control).
[Charles Plessy]
* Refreshed debian/patches/01-build.xml.
* Use default java implementation.
- debian/control: BD on default-jdk, switch runtime dependency to
default-jre | java6-runtime.
- debian/rules: Specify source/target = 1.5 to ensure that backwards
compatible bytecode is built.
- Closes: #684172, thanks to J. Page and Ubuntu.
-- Olivier Sallou <osallou at debian.org> Thu, 06 Sep 2012 09:10:11 +0900
** Affects: picard-tools (Ubuntu)
Importance: Undecided
Status: New
--
Sync picard-tools 1.79-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1078012
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list