[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#886511: marked as done (RFS: svxlink/17.12.1-1 [shlib version change requires NEW])

Your message dated Sun, 14 Jan 2018 11:43:29 +0100
with message-id <20180114104329.GC30891@coldtobi.de>
and subject line Re: Fwd: RFS: svxlink/17.12.1-1 [shlib version change requires NEW]
has caused the Debian Bug report #886511,
regarding RFS: svxlink/17.12.1-1 [shlib version change requires NEW]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
886511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886511
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "svxlink"

 * Package name    : svxlink
   Version         : 17.12.1-1
   Upstream Author : Tobias Blomberg
 * URL             : https://www.svxlink.org
 * License         : GPL-2+, LGPL-2.1, WOL, Zlib, MIT, CC0-1.0
   Section         : hamradio

It builds those binary packages:

 libasyncaudio-dev - AsyncAudio library for SvxLink (development files)
 libasyncaudio1.5 - AsyncAudio library for SvxLink
 libasynccore-dev - AsyncCore library for SvxLink (development files)
 libasynccore1.5 - AsyncCore library for SvxLink
 libasynccpp-dev - AsyncCpp library for SvxLink (development files)
 libasynccpp1.5 - AsyncCpp library for SvxLink
 libasyncqt-dev - AsyncQt library for SvxLink (development files)
 libasyncqt1.5 - AsyncQt library for SvxLink
 libecholib-dev - EchoLib library for SvxLink (development files)
 libecholib1.3 - EchoLib library for SvxLink
 qtel  - Graphical client for the EchoLink® protocol
 qtel-icons - Icons for graphical client for the EchoLink® protocol
 remotetrx  - Remote controller for radio transceivers
 svxlink-calibration-tools - Calibration tools for SvxLink amateur radio suite
 svxlink-gpio - GPIO control scripts SvxLink amateur radio server
 svxlink-server - Voice-over-IP server for ham radio operators
 svxreflector - Conference server for SvxLink amateur radio servers

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/svxlink


  Alternatively, one can download the package with dget using this command:

    dget -x https://mentors.debian.net/debian/pool/main/s/svxlink/svxlink_17.12.1-1.dsc

  More information about hello can be obtained from https://www.example.com.

  Changes since the last upload:

  * New upstream release
  * Marked qtel-icons Multi-Arch: foreign
  * Changed ownership of qso_recorder and propagation_monitor in $datadir
  * Bumped async library versions to 1.5
  * Bumped echolib library version to 1.3.3
  * Set compat to 11
  * Set Build-Depends: debhelper (>= 11)
  * Set Standards-Version: 4.1.3

  Regards,
   Felix Lechner

--- End Message ---
--- Begin Message --- 
Hi Felix,

Sure I'll take a look!

Let's get started with the review:

- The dbgsym migration code: You can drop it now:
  For one, the manual dbg symbols were never in a stable release and additionally it can
  be dropped "a release later"
- You'd likely want to update the copyright years for the debian/* part.
- Please check your patches whether can they can be upstreamed.
  (at least the systemd one, maybe also the compiler flags one)
- There is a debian/old directory... Can it go?

Those are not critical, so I will upload after this mail. But please consider
the remarks for subsequent uploads!

(I've checked that there are no reverse dependencies, so an upload to sid
is ok -- no transition needed.)

Thanks for the contribution to Debian!

--
tobi

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: