lighttpd is marked for autoremoval from testing

2019-04-18 Thread Debian testing autoremoval watch
lighttpd 1.4.53-3 is marked for autoremoval from testing on 2019-05-19

It is affected by these RC bugs:
926885: lighttpd: CVE-2019-11072



Bug#765653: marked as done (Xine freezes and crash when changing dvb channel in Debian Jessie beta 2 Xfce)

2019-04-18 Thread Debian Bug Tracking System
Your message dated Fri, 19 Apr 2019 01:49:23 +
with message-id 

and subject line using vlc
has caused the Debian Bug report #765653,
regarding Xine freezes and crash when changing dvb channel in Debian Jessie 
beta 2 Xfce
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.)


-- 
765653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: xine_ui
Version: 0.99.9-1.1

Xine ui freezes amd crash when changing dvb channel in Debian Jessie beta 2 Xfce
( 
cdimage.debian.org/cdimage/jessie_di_beta_2/i386/iso-cd/debian-jessie-DI-b2-i386-xfce-CD-1.iso)

TV stick driver:dvb-usb-af9015.fw

VLC works with dvb.

With verbose=5 it crash when changing channel:
gui_xine_open_and_play():
mrl: 'dvb://Yle TV1(YLE)',
sub 'NONE',
start_pos 0, start_time 0, av_offset 0, spu_offset 0.
ao_flush (loop running: 1)
net_buf_ctrl: dvbspeed OFF

net_buf_ctrl: nbc_put_cb: stops buffering

net_buf_ctrl: nbc_set_speed_normal
*** Error in `xine': munmap_chunk(): invalid pointer: 0x0a28c2e8 ***


This is output with default verbose level and when it freezes:

debian@debian:~$ xine
This is xine (X11 gui) - a free video player v0.99.9.
(c) 2000-2014 The xine Team.
vo_vdpau: vdpau API version : 1
vo_vdpau: vdpau implementation description : NVIDIA VDPAU Driver Shared Library 
 340.46  Wed Sep 24 13:59:24 PDT 2014
vo_vdpau: maximum video surface size for chroma type 4:2:2 is 4096x4096
vo_vdpau: maximum video surface size for chroma type 4:2:0 is 4096x4096
vo_vdpau: maximum output surface size is 16384x16384
vo_vdpau: hold a maximum of 10 video output surfaces for reuse
vo_vdpau: using 3 output surfaces of size 1920x1200 for display queue
vdpau_set_property: property=1, value=0
vo_vdpau: deinterlace: none
vo_vdpau: set_scaling_level=0
vo_vdpau: enabled features: inverse_telecine=0
vo_vdpau: disable noise reduction.
vo_vdpau: disable sharpness.
vo_vdpau: skip_chroma = 0
input_dvb: continuing in get_instance
vdpau_set_property: property=8, value=100
vdpau_set_property: property=13, value=100
[mp3 @ 0xa5885a0] Header missing
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa588060] Invalid frame dimensions 0x0.
[mpegts @ 0xa504f20] max_analyze_duration 500 reached
[NULL @ 0xa588cc0] start time is not set in estimate_timings_from_pts
[NULL @ 0xa5893e0] start time is not set in estimate_timings_from_pts
[NULL @ 0xa589b40] start time is not set in estimate_timings_from_pts
Input #0, mpegts, from 'dvb://Yle TV1(YLE)':
  Duration: 00:00:06.89, start: 607.192256, bitrate: 2220 kb/s
  Program 17 
Stream #0.0[0x200]: Video: mpeg2video (Main), yuv420p, 720x576 [PAR 64:45 
DAR 16:9], 15000 kb/s, 25 fps, 90k tbn, 50 tbc
Stream #0.1[0x28a](fin): Audio: mp2, 48000 Hz, 2 channels, s16p, 224 kb/s
Stream #0.2[0x403](fin): Subtitle: dvbsub
Stream #0.3[0x1388](fin): Subtitle: [6][0][0][0] / 0x0006
Stream #0.4[0x1771]: Data: [5][0][0][0] / 0x0005
  Program 33 
  Program 81 
  Program 113 
  Program 155 
  Program 529 
  Program 3347 
  Program 4369 
  Program 4401 
  Program 4433 
vo_vdpau: deinterlace: none
vo_vdpau: set_scaling_level=0
vo_vdpau: enabled features: inverse_telecine=0
vo_vdpau: disable noise reduction.
vo_vdpau: disable sharpness.
vo_vdpau: skip_chroma = 0
input_dvb: continuing in get_instance
vdpau_set_property: property=8, value=100
vdpau_set_property: property=13, value=100
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mp3 @ 0xa588cc0] Header missing
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpeg2video @ 0xa5893e0] Invalid frame dimensions 0x0.
[mpegts @ 0xa5885a0] max_analyze_duration 500 reached
[NULL @ 0xa507fa0] start time is not set in estimate_timings_from_pts

Bug#926305: nis startup scripts are completely broken

2019-04-18 Thread Elimar Riesebieter
* Anton Ivanov  [2019-04-18 15:05 +0100]:

> That is not an advice.
> 
> If nscd is a required dependency, NIS should bring it in.

This is not a "must have"

> 
> Presently it is not.
> 
> Still broken

The advice is also mentioned in the changelog:

  * Drop -no-dbus from YPBINDARGS= in /etc/default/nis.
We no longer build nis with NetworkManager/D-Bus support, so setting
this option made ypbind fail to start. (Closes: #906436)

So setting "YPBINDARGS=" in /etc/default/nis should be your first step to get
nis working in buster ;-)

Elimar
-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche


signature.asc
Description: PGP signature


Bug#926305: closed by Elimar Riesebieter (Re: Bug#926305: nis startup scripts are completely broken)

2019-04-18 Thread Anton Ivanov

Please reopen.

Advice is no replacement for a Depends in the package control file.

As shipped the package is still broken and at the reported severity - 
breaking most of the system


A.

On 18/04/2019 14:48, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the nis package:

#926305: nis startup scripts are completely broken

It has been closed by Elimar Riesebieter .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Elimar Riesebieter 
 by
replying to this email.



--
Anton R. Ivanov
https://www.kot-begemot.co.uk/



Bug#926305: nis startup scripts are completely broken

2019-04-18 Thread Anton Ivanov

That is not an advice.

If nscd is a required dependency, NIS should bring it in.

Presently it is not.

Still broken

A.

On 18/04/2019 14:43, Elimar Riesebieter wrote:

* Elimar Riesebieter  [2019-04-03 11:06 +0200]:


* Anton Ivanov  [2019-04-03 09:43 +0100]:


Package: nis
Version: 3.17.1-3+b1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Startup scripts are completely broken. Something in the systemd 
conversion/autogeneration.

The ypbind binary is never started, the script goes into "backgrounded" and 
fails. From there
on the system is unusable - you cannot log in, UIDs and groups do not resolve, 
etc.

The same system operated correctly before buster upgrade and will operate 
correctly if
ypbind is invoked from the command line.

This looks like a pure systemd conversion issue of some sort.

At my systems installing nscd helped. As well setting "YPBINDARGS="
in /etc/default/nis must be.

This bug should be closed as there is no response from the reporter.
As well it seems to be fixed following the advices given above,
though.

Elimar


--
Anton R. Ivanov
https://www.kot-begemot.co.uk/



Bug#927368: irqbalance: Should be Multi-Arch: foreign

2019-04-18 Thread Ben Hutchings
Package: irqbalance
Version: 1.5.0-3
Severity: normal

15:05 < Diziet> Starting SMP IRQ Balancer: irqbalancestart-stop-daemon: unable 
to start /usr/sbin/irqbalance (Exec format error)
15:06 < Diziet> What fun, if you install linux-image-amd64 on an i386 host it 
pulls in irqbalance:amd64 and then refuses to start ?
15:06 < Diziet> Oh I've booted the i386 kernel

This error would have been avoided if irqbalance's control file
declared "Multi-Arch: foreign", as dpkg would then favour the primary
architecture.

(linux-image packages will stop recommending irqbalance soon as it
doesn't seem to be generally useful any more, so this isn't a high
priority.)

Ben.

-- System Information:
Debian Release: buster/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)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages irqbalance depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-8
ii  libcap-ng0 0.7.9-2
ii  libglib2.0-0   2.58.3-1
ii  libncursesw6   6.1+20181013-2
ii  libnuma1   2.0.12-1
ii  libsystemd0241-2
ii  libtinfo6  6.1+20181013-2
ii  lsb-base   10.2019031300
ii  runit-helper   2.8.6

irqbalance recommends no packages.

irqbalance suggests no packages.

-- debconf information:
  irqbalance/enable: true
  irqbalance/oneshot: false



Bug#926305: marked as done (nis startup scripts are completely broken)

2019-04-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Apr 2019 15:43:59 +0200
with message-id <20190418134359.t6sqscgqkem7i...@pippin.home.lxtec.de>
and subject line Re: Bug#926305: nis startup scripts are completely broken
has caused the Debian Bug report #926305,
regarding nis startup scripts are completely broken
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.)


-- 
926305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nis
Version: 3.17.1-3+b1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Startup scripts are completely broken. Something in the systemd 
conversion/autogeneration.

The ypbind binary is never started, the script goes into "backgrounded" and 
fails. From there
on the system is unusable - you cannot log in, UIDs and groups do not resolve, 
etc.

The same system operated correctly before buster upgrade and will operate 
correctly if
ypbind is invoked from the command line.

This looks like a pure systemd conversion issue of some sort.

-- Package-specific info:

NIS domain: home 

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nis depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  hostname   3.21
ii  libc6  2.28-8
ii  libgdbm6   1.18.1-4
ii  libsystemd0241-1
ii  lsb-base   10.2019031300
ii  make   4.2.1-1.2
ii  netbase5.6
ii  rpcbind [portmap]  1.2.5-0.3

nis recommends no packages.

Versions of packages nis suggests:
pn  nscd  

-- Configuration Files:
/etc/yp.conf changed [not included]

-- debconf information:
* nis/domain: home
--- End Message ---
--- Begin Message ---
* Elimar Riesebieter  [2019-04-03 11:06 +0200]:

> * Anton Ivanov  [2019-04-03 09:43 +0100]:
> 
> > Package: nis
> > Version: 3.17.1-3+b1
> > Severity: critical
> > Justification: breaks unrelated software
> > 
> > Dear Maintainer,
> > 
> > Startup scripts are completely broken. Something in the systemd 
> > conversion/autogeneration.
> > 
> > The ypbind binary is never started, the script goes into "backgrounded" and 
> > fails. From there
> > on the system is unusable - you cannot log in, UIDs and groups do not 
> > resolve, etc.
> > 
> > The same system operated correctly before buster upgrade and will operate 
> > correctly if
> > ypbind is invoked from the command line.
> > 
> > This looks like a pure systemd conversion issue of some sort.
> 
> At my systems installing nscd helped. As well setting "YPBINDARGS="
> in /etc/default/nis must be.

This bug should be closed as there is no response from the reporter.
As well it seems to be fixed following the advices given above,
though.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


signature.asc
Description: PGP signature
--- End Message ---


Bug#926305: nis startup scripts are completely broken

2019-04-18 Thread Elimar Riesebieter
* Elimar Riesebieter  [2019-04-03 11:06 +0200]:

> * Anton Ivanov  [2019-04-03 09:43 +0100]:
> 
> > Package: nis
> > Version: 3.17.1-3+b1
> > Severity: critical
> > Justification: breaks unrelated software
> > 
> > Dear Maintainer,
> > 
> > Startup scripts are completely broken. Something in the systemd 
> > conversion/autogeneration.
> > 
> > The ypbind binary is never started, the script goes into "backgrounded" and 
> > fails. From there
> > on the system is unusable - you cannot log in, UIDs and groups do not 
> > resolve, etc.
> > 
> > The same system operated correctly before buster upgrade and will operate 
> > correctly if
> > ypbind is invoked from the command line.
> > 
> > This looks like a pure systemd conversion issue of some sort.
> 
> At my systems installing nscd helped. As well setting "YPBINDARGS="
> in /etc/default/nis must be.

This bug should be closed as there is no response from the reporter.
As well it seems to be fixed following the advices given above,
though.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--


signature.asc
Description: PGP signature