Bug#856727: [Pkg-nginx-maintainers] Bug#856727: libnginx-mod-http-headers-more-filter: Configuration directive more_clear_headers is missing

2017-03-08 Thread Joni Orponen
2017-03-08 7:52 GMT+01:00 Christos Trochalakis <ctrochala...@debian.org>: > On Sat, Mar 04, 2017 at 12:23:40PM +0000, Joni Orponen wrote: > >> Package: libnginx-mod-http-headers-more-filter >> Version: 1.10.3-1~bpo8+1 >> Severity: important >> >> >>

Bug#856727: libnginx-mod-http-headers-more-filter: Configuration directive more_clear_headers is missing

2017-03-04 Thread Joni Orponen
Package: libnginx-mod-http-headers-more-filter Version: 1.10.3-1~bpo8+1 Severity: important https://github.com/openresty/headers-more-nginx-module#more_clear_headers Nginx headers-more used to ship with more_clear_headers in Debian. Was this removed on purpose? -- System Information: Debian

Bug#800721:

2015-10-10 Thread Joni Orponen
cycle: --- google.com ping statistics --- 100 packets transmitted, 94 received, 6% packet loss, time 107310ms rtt min/avg/max/mdev = 12.219/6037.145/19665.521/4837.827 ms, pipe 13 Performance returns to normal after a full reboot cycle. -- Joni Orponen

Bug#793544:

2015-10-10 Thread Joni Orponen
Testing with a manually placed iwlwifi-7265-13.ucode: I'm getting it to fail in a matter of hours instead of a matter of minutes, but power cycling the radio does not restore full functionality anymore and a full reboot cycle is required. -- Joni Orponen

Bug#793544: firmware-iwlwifi: iwlwifi-7265-11.ucode and iwlwifi-7265-12.ucode missing for linux 4.0

2015-10-09 Thread Joni Orponen
http://www.intellinuxwireless.org/. Based on the table there and my dmesg output, the driver shipping in linux-image-amd64 4.1+67~bpo8+1 is LinuxCore 10 and the latest firmware currently shipping in firmware-iwlwifi 0.44~bpo8+1 is meant to be used with LinuxCore7. -- Joni Orponen

Bug#793544:

2015-10-09 Thread Joni Orponen
[ 3812.426415] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Digging into the topic a bit more: I'm getting the firmware v10 (already unsupported by upstream) to crash under a sustained heavier network load. To recover, even though the driver tries to recover itself,

Bug#800721:

2015-10-09 Thread Joni Orponen
/. on the initial driver startup? -- Joni Orponen

Bug#679214: grub-pc: Grub2 fails to boot from a degraded mdraid RAID6

2013-02-07 Thread Joni Orponen
Package: grub-pc Version: 2.00-13 Followup-For: Bug #679214 This bug still exists in grub 2.00 on Debian. The trigger cause seems to be 'extra' devices in mdraid arrays. RAID1 2 RAID5 3 RAID6 4 Can anyone else reproduce this with a 6 disk array and / on LVM? -- Package-specific info:

Bug#679214: grub-pc: Grub2 fails to boot from a degraded mdraid RAID6

2012-06-27 Thread Joni Orponen
Package: grub-pc Version: 1.99-22.1 Severity: important Tags: d-i My setup: Wheezy businesscard install daily build (2012-06-25) MBR on disks One partition per disk 6 disk mdraid RAID6 / and /boot on LVM / and /boot as ext4 (in fact on the same partition) The installer installs everything fine,

Bug#636322: logwatch: Unmatched entries for smartd offline and conveyance tests.

2011-08-02 Thread Joni Orponen
Package: logwatch Version: 7.3.6.cvs20090906-1squeeze1 Severity: minor From my logwatch output: - Smartd Begin /dev/sda [SAT] : started scheduled Short self-test 1 Time(s) **Unmatched Entries** Device: /dev/sda [SAT], starting scheduled