Bug#889028: fixed in minissdpd 1.5.20161216-2

2018-02-15 Thread Maria K.

Hi,

On Tue, 13 Feb 2018 11:02:21 +0100 Thomas Goirand wrote:
> On 02/02/2018 08:34 PM, f4...@f4fxl.org wrote:
> > Hi,
> >
> > I beg your pardon, but this looks like a half baked feature.
> > IMHO package is missing some sort of migration from previous versions.
> > Packages are not supposed to require manual steps or shall prompt the
> > user what to do during update.
>
> Could you explain what's wrong with the migration ? The file is in
> /etc/default, so it's marked as CONFFILES, and as such, if you changed
> it, dpkg will do a prompt. In my case, it did:
>
> Setting up minissdpd (1.5.20161216-2~bpo9+1) ...
> Installing new version of config file /etc/default/minissdpd ...
> Installing new version of config file /etc/init.d/minissdpd ...
>
> I don't see any trouble here...
>
> If you do, please explain.

I've used apt for upgrading packages, I only got the error message. I'm

>
> > Previous version seemed to accept 0.0.0.0 to listen on all interfaces,
> > it is unclear what is required to achieve the same.
>
> As much as I understand, you're supposed to just configure one interface
> or IP pool, and miniupnpd will listen on all IPs on that device / pool.
>
> /usr/sbin/minissdpd --help explains this.
>
> If you just enter an interface name, like let's say eth0, then it will
> listen on that. If you enter 0.0.0.0/0, then it will listen on
> everything, no mater what. I tried putting 0.0.0.0 without the trailing
> /0, and it looks like also working.
>
> > Moreover, entering a
> > valid address like the example specified in the error message also 
fails.

>
> Contributions, suggestions, ideas are more than welcome for improving
> the package.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
>



Bug#889028: fixed in minissdpd 1.5.20161216-2

2018-02-13 Thread

Hi,  
  
AFAIK I never changed the file in /etc/default. And even if I did so, the 
package installation should not just abruptlly stop, some sort of problem 
resolution shall be presented to the user.  
I had 0.0.0.0, and minissdpd was not happy with it. Maybe it has been fixed 
since then, since I changed to my wlan interface.  
Will test again with 0.0.0.0  
  
Regards,  
Geoffrey  
  
  
- - - - - -

  


Geoffrey Merck  
F4FXL / KC3FRA  
[http://www.f4fxl.org](http://www.f4fxl.org "Geoffrey Merck Website")  
  
  

> On 02/02/2018 08:34 PM, f4...@f4fxl.org wrote:   
>  > Hi,   
>  >   
>  > I beg your pardon, but this looks like a half baked feature.   
>  > IMHO package is missing some sort of migration from previous versions.   
>  > Packages are not supposed to require manual steps or shall prompt the   
>  > user what to do during update.   
>   
>  Could you explain what's wrong with the migration ? The file is in   
>  /etc/default, so it's marked as CONFFILES, and as such, if you changed   
>  it, dpkg will do a prompt. In my case, it did:   
>   
>  Setting up minissdpd (1.5.20161216-2~bpo9+1) ...   
>  Installing new version of config file /etc/default/minissdpd ...   
>  Installing new version of config file /etc/init.d/minissdpd ...   
>   
>  I don't see any trouble here...   
>   
>  If you do, please explain.   
>   
>  > Previous version seemed to accept 0.0.0.0 to listen on all interfaces,   
>  > it is unclear what is required to achieve the same.   
>   
>  As much as I understand, you're supposed to just configure one interface   
>  or IP pool, and miniupnpd will listen on all IPs on that device / pool.   
>   
>  /usr/sbin/minissdpd --help explains this.   
>   
>  If you just enter an interface name, like let's say eth0, then it will   
>  listen on that. If you enter 0.0.0.0/0, then it will listen on   
>  everything, no mater what. I tried putting 0.0.0.0 without the trailing   
>  /0, and it looks like also working.   
>   
>  > Moreover, entering a   
>  > valid address like the example specified in the error message also fails.  
>  
>   
>  Contributions, suggestions, ideas are more than welcome for improving   
>  the package.   
>   
>  Cheers,   
>   
>  Thomas Goirand (zigo)
  



Bug#889028: fixed in minissdpd 1.5.20161216-2

2018-02-13 Thread Thomas Goirand
On 02/02/2018 08:34 PM, f4...@f4fxl.org wrote:
> Hi,
> 
> I beg your pardon, but this looks like a half baked feature.
> IMHO package is missing some sort of migration from previous versions.
> Packages are not supposed to require manual steps or shall prompt the
> user what to do during update.

Could you explain what's wrong with the migration ? The file is in
/etc/default, so it's marked as CONFFILES, and as such, if you changed
it, dpkg will do a prompt. In my case, it did:

Setting up minissdpd (1.5.20161216-2~bpo9+1) ...
Installing new version of config file /etc/default/minissdpd ...
Installing new version of config file /etc/init.d/minissdpd ...

I don't see any trouble here...

If you do, please explain.

> Previous version seemed to accept 0.0.0.0 to listen on all interfaces,
> it is unclear what is required to achieve the same.

As much as I understand, you're supposed to just configure one interface
or IP pool, and miniupnpd will listen on all IPs on that device / pool.

/usr/sbin/minissdpd --help explains this.

If you just enter an interface name, like let's say eth0, then it will
listen on that. If you enter 0.0.0.0/0, then it will listen on
everything, no mater what. I tried putting 0.0.0.0 without the trailing
/0, and it looks like also working.

> Moreover, entering a
> valid address like the example specified in the error message also fails.

Contributions, suggestions, ideas are more than welcome for improving
the package.

Cheers,

Thomas Goirand (zigo)



Bug#889028: fixed in minissdpd 1.5.20161216-2

2018-02-02 Thread

Hi,  
  
I beg your pardon, but this looks like a half baked feature.  
IMHO package is missing some sort of migration from previous versions. Packages 
are not supposed to require manual steps or shall prompt the user what to do 
during update.  
Previous version seemed to accept 0.0.0.0 to listen on all interfaces, it is 
unclear what is required to achieve the same. Moreover, entering a valid 
address like the example specified in the error message also fails.  
  
Kind Regards,  
Geoffrey  
  
On Fri, 02 Feb 2018 15:26:33 + Yangfl  wrote:  
> Source: minissdpd  
> Source-Version: 1.5.20161216-2  
>   
> We believe that the bug you reported is fixed in the latest version  
of  
> minissdpd, which is due to be installed in the Debian FTP archive.  
>   
> A summary of the changes between this version and the previous one is  
> attached.  
>   
> Thank you for reporting the bug, which will now be closed.  If you  
> have further comments please address them to 
> [889...@bugs.debian.org](mailto:889...@bugs.debian.org),  
> and the maintainer will reopen the bug report if appropriate.  
>   
> Debian distribution maintenance software  
> pp.  
> Yangfl  (supplier of updated minissdpd package)  
>   
> (This message was generated automatically at their request; if you  
> believe that there is a problem with it please contact the archive  
> administrators by mailing 
> [ftpmas...@ftp-master.debian.org](mailto:ftpmas...@ftp-master.debian.org))  
>   
>   
> -BEGIN PGP SIGNED MESSAGE-  
> Hash: SHA256  
>   
> Format: 1.8  
> Date: Fri, 02 Feb 2018 00:54:30 +0800  
> Source: minissdpd  
> Binary: minissdpd  
> Architecture: source amd64  
> Version: 1.5.20161216-2  
> Distribution: unstable  
> Urgency: medium  
> Maintainer: Thomas Goirand   
> Changed-By: Yangfl   
> Description:  
>  minissdpd  - keep memory of all UPnP devices that announced  
themselves  
> Closes: 889028 889138  
> Changes:  
>  minissdpd (1.5.20161216-2) unstable; urgency=medium  
>  .  
>* Fix missing /etc/default/minissdpd (Closes: #889028)  
>* Allow specifying IPv4 addresses (Closes: #889138)  
>* Temporarily fix FTBFS on Hurd  
>* Enable pristine-tar in debian/gbp.conf  
> Checksums-Sha1:  
>  9b4dc11d75645b5c8517ac64423050f05bb9a1ac 1974  
minissdpd_1.5.20161216-2.dsc  
>  11bc785ac05d7b6455f894186916e7bb45e9d16d 6092  
minissdpd_1.5.20161216-2.debian.tar.xz  
>  463041be460a6187ade6ffbcd8caea16a450c6f3 53024 minissdpd-  
dbgsym_1.5.20161216-2_amd64.deb  
>  a16e7d36cc8587dc56c17c2e36a981d7749008dd 5818  
minissdpd_1.5.20161216-2_amd64.buildinfo  
>  6de5dc3252dea52567e8863070ac78abd460216a 27076  
minissdpd_1.5.20161216-2_amd64.deb  
> Checksums-Sha256:  
>  bfea1da1e73c0bea36762695fb1c28c4ee8aea50a213b821f964aff06c1ab07e  
1974 minissdpd_1.5.20161216-2.dsc  
>  d458107c3fb0a837dbdf0b6380df6c9406121ae4de52264d543d58e657100c36  
6092 minissdpd_1.5.20161216-2.debian.tar.xz  
>  4fdab8d134b4f87fd61908e3aaf252caf10d2784b6bfe569eeab4860ccfe4312  
53024 minissdpd-dbgsym_1.5.20161216-2_amd64.deb  
>  42f52ef2f2cc751aa59d849e8e7c998e3faf52462fbc7743361f6952df953d9b  
5818 minissdpd_1.5.20161216-2_amd64.buildinfo  
>  790cf2570a41328b682818aa675c5766e6a9f7bd411f7fdfd8d5efbaa11bd421  
27076 minissdpd_1.5.20161216-2_amd64.deb  
> Files:  
>  32f779fb0a88a9f1e5d9a1e2fb22c640 1974 net optional  
minissdpd_1.5.20161216-2.dsc  
>  76537652c3a92505bf5fb40b650f4ebe 6092 net optional  
minissdpd_1.5.20161216-2.debian.tar.xz