qink is marked for autoremoval from testing

[Debian testing autoremoval watch]

qink 0.3.5-6 is marked for autoremoval from testing on 2016-08-22

It is affected by these RC bugs:
831070: qink: FTBFS with GCC 6: icontheme.cpp:423:39: error: call of overloaded 
'abs(unsigned int)' is ambiguous

polygraph is marked for autoremoval from testing

[Debian testing autoremoval watch]

polygraph 4.3.2-3 is marked for autoremoval from testing on 2016-08-12

It is affected by these RC bugs:
831125: polygraph: FTBFS with GCC 6: ContainerBodyIter.cc:75:22: error: no 
match for 'operator!=' (operand types are 'ofixedstream' and 'int')

Bug#826718: Fwknop 2.6.9 packaged

[Michael Rash]

On Wed, Aug 10, 2016 at 1:52 PM, Franck Joncourt 
wrote:

> Hi Santiago,
>
> Thanks for your quick reply. I did add the deb files to the bug report to
> provide them to users since it has been a while since the last real update
> of fwknop on Debian.
>
> I am almost ready to push new files to debian mentor (updated package with
> QA upload + patches + lintian fixes) - I have just detected a minor problem
> with hardening flags. I hoped I could achieve this before going on holidays
> but I currently run out of time. I will continue at the end of August and I
> would be delighted if you or Gregor could sponsor the upload if you have
> time.
>
> I would like to maintain the fwknop package again but with my family and
> my job it is sometimes difficult to find the time to do it correctly. I may
> be unavailable for weeks and that is why I resigned.
>

Hello Franck,

Just wanted to thank you for putting together the new package...

--Mike



>
> Best regards,
>
> --
> Franck Joncourt
>

Processed: retitle 833972 to socks4-server: uses deprecated BSD union wait type

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 833972 socks4-server: uses deprecated BSD union wait type
Bug #833972 [src:socks4-server] socks4-server
Changed Bug title to 'socks4-server: uses deprecated BSD union wait type' from 
'socks4-server'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833972: socks4-server

[Aurelien Jarno]

Source: socks4-server
Version: 4.3.beta2-19
Severity: important
Tags: patch upstream

Dear Maintainer,

glibc 2.24 has removed the deprecated BSD union wait type if favor of
the POSIX.1 interface using W* macros from  (such as
WEXITSTATUS) [1].

glibc 2.24 is already available in experimental and will plan to upload
it to sid in the next days/weeks. This will cause socks4-server to fail
to build from source. You will find attached a patch to fix the issue.
It unconditionally uses the "new" interface as the GNU libc supports it
since at least 1995, probably even earlier.
 
Please also note that this will not break the existing binaries, just
building the package from source.

Thanks,
Aurelien

[1] https://sourceware.org/ml/libc-alpha/2016-02/msg00342.html

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u socks4-server-4.3.beta2/rftp/cmds.c socks4-server-4.3.beta2/rftp/cmds.c
--- socks4-server-4.3.beta2/rftp/cmds.c
+++ socks4-server-4.3.beta2/rftp/cmds.c
@@ -1262,7 +1262,7 @@
 	int pid;
 	sig_t old1, old2;
 	char shellnam[40], *shell, *namep; 
-#if defined(SOLARIS) || defined(__alpha) || defined(SCO) || defined(ISC)
+#if defined(SOLARIS) || defined(__alpha) || defined(SCO) || defined(ISC) || defined (__GLIBC__)
 int status;
 #else
 union wait status;

Bug#826718: Fwknop 2.6.9 packaged

[Franck Joncourt]

Hi Santiago,

Thanks for your quick reply. I did add the deb files to the bug report to
provide them to users since it has been a while since the last real update
of fwknop on Debian.

I am almost ready to push new files to debian mentor (updated package with
QA upload + patches + lintian fixes) - I have just detected a minor problem
with hardening flags. I hoped I could achieve this before going on holidays
but I currently run out of time. I will continue at the end of August and I
would be delighted if you or Gregor could sponsor the upload if you have
time.

I would like to maintain the fwknop package again but with my family and my
job it is sometimes difficult to find the time to do it correctly. I may be
unavailable for weeks and that is why I resigned.

Best regards,

--
Franck Joncourt

Bug#826718: Fwknop 2.6.9 packaged

[Santiago Vila]

On Wed, Aug 10, 2016 at 06:09:15PM +0200, Franck Joncourt wrote:

> I have packaged fwknop 2.6.9. I have used the latest git commit from Debian
> repository to add my changes.
> Please find enclosed files. If you could give it a try and upload them
> since I am not the maintainer anymore and I may be a bit rusty :) Check
> debian archive for changes,

Even if the package is currently orphaned, you can become the
maintainer again if you wish, and you can also make a QA upload if you
still care about the package enough to update it but not enough to
maintain it.

But please follow established procedures for that. For example, if you
need a sponsor, try debian-mentors, or upload the package to
mentors.debian.net, or maybe both.

In particular, sending binary .deb packages to the BTS should be
completely unnecessary. We work with sources. Binary packages are
created automatically.

Thanks.

Processed: Add patch tag

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 826718 + patch
Bug #826718 [src:fwknop] Please update fwknop
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
826718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833843: Acknowledgement (vlock: Upstream source not reachable)

[Sean Whitton]

On Wed, Aug 10, 2016 at 03:06:16PM +0200, Cesare Leonardi wrote:
> I think i've found the current home of the vlock package:
> https://github.com/toidinamai/vlock
> 
> The last release is 2.2.3 (2011), while Debian is at 2.2.2.
> However, the reposistory last commit is 12 may 2009, so no activity from
> upstream.

To be clear, the last commit is 2009 but the latest /tag/ is the 2011
2.2.3 tag.  So not as inactive as the commit history would suggest.

> Cesare.
> 

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#783602: marked as done (wicd *should* autoconnect if GUI is open)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 15:44:01 +0200
with message-id <20160810134401.ga23...@zira.vinc17.org>
and subject line Re: Bug#783602: wicd *should* autoconnect if GUI is open
has caused the Debian Bug report #783602,
regarding wicd *should* autoconnect if GUI is open
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 ow...@bugs.debian.org
immediately.)


-- 
783602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wicd-daemon
Version: 1.7.2.4-4.1
Severity: normal

>From /usr/share/wicd/daemon/wicd-daemon.py:

# We don't want to rescan/connect if the gui is open.
if self.gui_open:
if self.debug_mode:
print "Skipping autoconnect because GUI is open."
return

Why? This is a really annoying misfeature, I frequently keep the window
somewhere on the background, and I thought there was some bug in wicd
preventing it from reconnecting to the network.

Could this please be removed or made optional?

Thanks.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/mksh

Versions of packages wicd-daemon depends on:
ii  adduser  3.112+nmu1
ii  dbus 1.4.16-1
ii  debconf  1.5.50
ii  ethtool  1:3.9-1
ii  iproute  1:3.9.0-5
ii  iputils-ping 3:20100418-3
ii  isc-dhcp-client  4.2.4-4.1
ii  lsb-base 4.1+Debian13
ii  net-tools1.60-26
ii  psmisc   22.19-1
ii  python   2.7.8-2
ii  python-dbus  0.84.0-2
ii  python-gobject   3.14.0-1
ii  python-wicd  1.7.2.4-4.1
ii  udhcpc   1:1.22.0-14
ii  wireless-tools   29-2
ii  wpasupplicant1.1-1

Versions of packages wicd-daemon recommends:
ii  rfkill 0.4-1
ii  wicd-cli [wicd-client] 1.7.2.4-4.1
ii  wicd-curses [wicd-client]  1.7.2.4-4.1
ii  wicd-gtk [wicd-client] 1.7.2.4-4.1

Versions of packages wicd-daemon suggests:
ii  pm-utils  1.4.1-15

Versions of packages wicd depends on:
ii  wicd-cli [wicd-client] 1.7.2.4-4.1
ii  wicd-curses [wicd-client]  1.7.2.4-4.1
ii  wicd-gtk [wicd-client] 1.7.2.4-4.1

Versions of packages wicd-cli depends on:
ii  python  2.7.8-2

Versions of packages wicd-cli recommends:
ii  sudo  1.7.0-1

Versions of packages wicd-gtk depends on:
ii  python 2.7.8-2
ii  python-glade2  2.24.0-4
ii  python-gtk22.24.0-4

Versions of packages wicd-gtk recommends:
ii  gksu   2.0.2-2+b1
ii  python-notify  0.1.1-3

Versions of packages wicd-curses depends on:
ii  python2.7.8-2
ii  python-urwid  1.2.1-2+b1

Versions of packages wicd-curses recommends:
ii  sudo  1.7.0-1

Versions of packages python-wicd depends on:
ii  python  2.7.8-2
--- End Message ---
--- Begin Message ---
Version: 1.7.3-1

On 2016-08-10 15:33:31 +0200, Vincent Lefevre wrote:
> Control: forcemerge 582567 783602

One cannot forcemerge to an archived bug. So I'm just closing it.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582567 for
more information.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)--- End Message ---

Bug#833929: wicd-daemon: takes time to reconnect / autoconnect after connection loss

[Vincent Lefevre]

Package: wicd-daemon
Version: 1.7.4+tb2-2
Severity: normal

After an automatic disconnection, wicd-daemon didn't try to reconnect
(there was nothing in the wicd logs, not even anything about the
disconnection). After more than 3 minutes, I closed the GUI, and wicd
immediately reconnected just after that. In the logs:

[...]
2016/08/09 11:54:29 :: bound to 192.168.0.6 -- renewal in 109067 seconds.
2016/08/09 11:54:29 :: DHCP connection successful
2016/08/09 11:54:29 :: not verifying
2016/08/09 11:54:29 :: Connecting thread exiting.
2016/08/09 11:54:32 :: Sending connection attempt result success
2016/08/09 11:54:48 :: hidden
2016/08/10 15:20:52 :: Autoconnecting...
2016/08/10 15:20:52 :: No wired connection present, attempting to autoconnect 
to wireless network
2016/08/10 15:20:56 :: hidden
2016/08/10 15:20:56 :: lefevre has no never connect value
2016/08/10 15:20:56 :: trying to automatically connect to...lefevre
2016/08/10 15:20:56 :: Connecting to wireless network lefevre
[...]

I don't think the problem was due to the fact that the GUI was open,
or there would be something in the logs as in the past (bug 582567,
now fixed).

I suppose that wicd didn't notice the disconnection fast enough, and
then I closed the GUI, it did a check or this was just a coincidence.

Anyway, more than 3 minutes is too long. I wonder how much it would
have taken if I didn't close the GUI...

Note: this is particularly important when one doesn't have a physical
access to the machine.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wicd-daemon depends on:
ii  adduser  3.115
ii  dbus 1.10.8-1
ii  debconf  1.5.59
ii  ethtool  1:4.6-1
ii  iproute2 4.6.0-2
ii  iputils-ping 3:20150815-2
ii  isc-dhcp-client  4.3.4-1
ii  lsb-base 9.20160629
ii  net-tools1.60+git20150829.73cef8a-2
ii  psmisc   22.21-2.1+b1
ii  python-dbus  1.2.4-1
ii  python-gobject   3.20.1-1
ii  python-wicd  1.7.4+tb2-2
pn  python:any   
ii  wireless-tools   30~pre9-11
ii  wpasupplicant2.5-2+v2.4-1

Versions of packages wicd-daemon recommends:
ii  rfkill 0.5-1
ii  wicd-curses [wicd-client]  1.7.4+tb2-2
ii  wicd-gtk [wicd-client] 1.7.4+tb2-2

Versions of packages wicd-daemon suggests:
pn  pm-utils  

Versions of packages wicd depends on:
ii  wicd-curses [wicd-client]  1.7.4+tb2-2
ii  wicd-gtk [wicd-client] 1.7.4+tb2-2

Versions of packages wicd-gtk depends on:
ii  python-glade2  2.24.0-5
ii  python-gtk22.24.0-5
pn  python:any 

Versions of packages wicd-gtk recommends:
ii  gksu   2.0.2-9
ii  python-notify  0.1.1-4

Versions of packages wicd-curses depends on:
ii  python-urwid  1.3.1-2+b1
pn  python:any

Versions of packages wicd-curses recommends:
ii  sudo  1.8.17p1-2

Versions of packages python-wicd depends on:
pn  python:any  

-- Configuration Files:
/etc/wicd/encryption/templates/active changed:
wpa
wpa-peap
wpa-psk
wpa-psk-hex
wpa2-leap
wpa2-peap
wep-hex
wep-passphrase
wep-shared
leap
ttls
eap
peap
peap-eduroam
peap-tkip
eap-tls
psu


-- debconf information:
* wicd/users:

Bug#783602: wicd *should* autoconnect if GUI is open

[Vincent Lefevre]

Control: forcemerge 582567 783602

On 2015-04-28 11:57:50 +0200, Andrew Shadura wrote:
> Package: wicd-daemon
> Version: 1.7.2.4-4.1
> Severity: normal
> 
> >>From /usr/share/wicd/daemon/wicd-daemon.py:
> 
> # We don't want to rescan/connect if the gui is open.
> if self.gui_open:
> if self.debug_mode:
> print "Skipping autoconnect because GUI is open."
> return

This was the same issue as bug 582567, now fixed (the above code is
no longer there). There are still issues with autoconnect, but this
is not related with this bug.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)