[FFE] Sync new package numad 0.5+20150602-2 (universe) from Debian unstable (main)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Ubuntu |
Wishlist
|
Chris J Arges | ||
Bug Description
Please sync numad 0.5+20150602-2 (universe) from Debian unstable (main)
All changelog entries:
numad (0.5+20150602-2) unstable; urgency=medium
* fix build for platforms with no __NR_migrate_pages syscall
-- Kamal Mostafa <email address hidden> Tue, 01 Sep 2015 13:17:01 -0700
numad (0.5+20150602-1) unstable; urgency=low
* Initial release (Closes: #776826)
* Package git snapshot.
-- Jeremías Casteglione <email address hidden> Thu, 12 Feb 2015 20:54:12 +0000
| Changed in ubuntu: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| summary: |
- Sync numad 0.5+20150602-2 (universe) from Debian unstable (main) + [FFE] Sync new package numad 0.5+20150602-2 (universe) from Debian + unstable (main) |
| Chris J Arges (arges) wrote : | #1 |
| Chris J Arges (arges) wrote : | #3 |
09:50:34 infinity | arges: It's a new package, doesn't need an FFe unless you intend to also
| get it installed by default.
| Changed in ubuntu: | |
| assignee: | nobody → Chris J Arges (arges) |
| Chris J Arges (arges) wrote : | #4 |
$ syncpackage -v numad
syncpackage: Source numad -> wily/Proposed: not in Ubuntu, new version 0.5+20150602-2
syncpackage: New changes:
numad (0.5+20150602-2) unstable; urgency=medium
* fix build for platforms with no __NR_migrate_pages syscall
-- Kamal Mostafa <email address hidden> Tue, 01 Sep 2015 13:17:01 -0700
numad (0.5+20150602-1) unstable; urgency=low
* Initial release (Closes: #776826)
* Package git snapshot.
-- Jeremías Casteglione <email address hidden> Thu, 12 Feb 2015 20:54:12 +0000
Sync this package [y|N]? y
syncpackage: Request succeeded; you should get an e-mail once it is processed.
| Changed in ubuntu: | |
| status: | Confirmed → Fix Released |


I've built this package in a wily amd64/i386 schroot without issue; I can syncpackage if/when necessary. Can I have release-team ACK on this exception?