Bug#833259: ITP: cassbeam -- Cassegrain antenna modelling

[Ole Streicher]

Package: wnpp
Severity: wishlist
Owner: Ole Streicher 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-as...@lists.debian.org

* Package name: cassbeam
  Version : 1.0.1
  Upstream Author : Walter Brisken, NRAO
  URL : https://github.com/ratt-ru/cassbeam
* License : GPL-2.0+
  Programming Lang: C
  Description : Cassegrain antenna modelling
 Cassbeam is a Cassegrain antenna ray tracer. A Cassegrain antenna is
 a double reflector system which works on the principle of cassegrain
 optical telescope. A high gain cassegrain reflector antenna in
 Ku-band has been successfully developed for command transmit
 application for the missile programme. It can also be used for
 monopulse radar, satellite communication.

This package already has been in Debian until 2011, when it was removed due
to the lack of maintenance. The current package is rewritten from scratch by
Gijs Molenaar for his Kernsuite, and will be co-maintainer with him under
the Debian Astro umbrella.

A git repository is available under

https://anonscm.debian.org/cgit/debian-astro/packages/cassbeam.git

Best regards

Ole

Re: [MBF] Obsoleting Source-Version substvar

[Guillem Jover]

Hi!

On Sun, 2016-07-10 at 02:16:21 +0200, Guillem Jover wrote:
> I'd like to obsolete the ${Source-Version} substvar, which has very
> misleading semantics, and has been deprecated since dpkg 1.13.19 in
> 2006-05-04. This currently emits warnings from various dpkg-dev
> scripts and from lintian.
> 
> 
> 
> I'm attaching the prospective dd-list, and the template bug report. I'd
> like do the MBF in 1 or 2 weeks, and turn the warnings into errors in
> the first dpkg release after 1 or 2 months from now. I'm easy if people
> would like more or less time?

Thanks to the maintainers that already fixed their packages! I handled
most of the QA team packages, except for libsigc++-1.2 which we should
probably try to remove instead as it only has one remaining rdep.

I've done the MBF [M], and I'm planning on turning the substvar usage
warning into an error in the first dpkg release happening after two weeks
from now, at which point I'll upgrade the remaining bugs to serious.

  [M] 


Thanks,
Guillem

Re: [MBF] Obsoleting bzip2 compression in .deb packages

[Guillem Jover]

Hi!

On Wed, 2016-07-06 at 03:19:40 +0200, Guillem Jover wrote:
> I'd like to obsolete bzip2 (and lzma) as .deb compressors when building
> binary packages. dpkg-deb currently emits warnings, this would turn them
> into errors. For lzma it's fine in Debian as the archive has never
> accepted them. For bzip2 there are currently 31 source packages that
> produce some binary packages using that compressor:
> 
> 
> 
> Unpacking *will* keep being supported for the forseeable future so that
> we can examine old binaries, in the same way dpkg-deb still supports
> format 0.939000.
> 
> I'm attaching the prospective dd-list, and the template bug report. I'd
> like do the MBF in 1 or 2 weeks, and turn the warnings into errors in
> the first dpkg release after 1 or 2 months from now. I'm easy if people
> would like more or less time?

Thanks to Adam Borowski who handled the QA team packages!

I've done the MBF [M], and I'm planning on turning the compressor
deprecation warnings into errors in the first dpkg release happening
after two weeks from now, at which point I'll upgrade the remaining bugs
to serious.

  [M] 


Thanks,
Guillem

Re: New default -fdebug-prefix-map build flag for dpkg

[Guillem Jover]

Hi!

On Thu, 2016-07-21 at 11:06:32 +, Mattia Rizzolo wrote:
> On Mon, Jul 18, 2016 at 08:57:01AM +, Mattia Rizzolo wrote:
> > As part of the Reproducible Builds effort [0], we would like to enable
> > a new default build flag from the reproducible/fixdebugpath feature
> > area in order to prevent issues with build paths.

> > Thus, following the dpkg team's policy [5] about adding a new default
> > build flag, I'm seeking a wider discussion to see whether somebody has
> > any concern we haven't already taken care of.
> 
> I think the failing packages are nothing particularly interesting, and
> it's very easy to fix, so if no concerns arise in the next very few
> days, I'm going to open a bug to dpkg to have the build flag turned on
> by default.

This change got included in dpkg 1.18.10.

Thanks,
Guillem

Bug#833274: ITP: jctools -- Java Concurrency Tools for the JVM

[Emmanuel Bourg]

Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: jctools
  Version : 1.2.1
  Upstream Author : Nitsan Wakart
* URL : http://jctools.github.io/JCTools/
* License : Apache-2.0
  Programming Lang: Java
  Description : Java Concurrency Tools for the JVM

JCTools offers some concurrent data structures currently missing from the JDK:
 * SPSC/MPSC/SPMC/MPMC variations for concurrent queues:
   * SPSC - Single Producer Single Consumer (Wait Free, bounded and unbounded)
   * MPSC - Multi Producer Single Consumer (Lock less, bounded and unbounded)
   * SPMC - Single Producer Multi Consumer (Lock less, bounded)
   * MPMC - Multi Producer Multi Consumer (Lock less, bounded)
 * An expanded queue interface (MessagePassingQueue):
   * relaxedOffer/Peek/Poll: trade off conflated guarantee on full/empty queue
 state with improved performance.
   * drain/fill: batch read and write methods for increased throughput
 and reduced contention

JCTools is a new dependency of Netty (libnetty-java).
The package will be maintained by the Java Team.