linux_4.10~rc6-1~exp1_multi.changes is NEW

binary:affs-modules-4.10.0-rc6-4kc-malta-di is NEW. binary:affs-modules-4.10.0-rc6-5kc-malta-di is NEW. binary:affs-modules-4.10.0-rc6-loongson-3-di is NEW. binary:affs-modules-4.10.0-rc6-octeon-di is NEW. binary:ata-modules-4.10.0-rc6-4kc-malta-di is NEW. binary:ata-modules-4.10.0-rc6-5kc-malta-di

Processing of linux_4.10~rc6-1~exp1_multi.changes

linux_4.10~rc6-1~exp1_multi.changes uploaded successfully to localhost along with the files: linux_4.10~rc6-1~exp1.dsc linux_4.10~rc6.orig.tar.xz linux_4.10~rc6-1~exp1.debian.tar.xz linux-doc-4.10_4.10~rc6-1~exp1_all.deb linux-headers-4.10.0-rc6-common_4.10~rc6-1~exp1_all.deb linux-manu

Re: Do I have to do anything to make sure ext4lazyinit works as being advertised ?

in-line :- On 01/02/2017, Lennart Sorensen wrote: > On Wed, Feb 01, 2017 at 12:46:48AM +0530, shirish शिरीष wrote: >> Now I have few queries - >> >> a. Are my assumptions wrong ? > > About the doing the init on a future boot, yes you are wrong. Ah...ok. > > 2.6.37 apparently. My bad ...

Re: Do I have to do anything to make sure ext4lazyinit works as being advertised ?

On Wed, Feb 01, 2017 at 12:46:48AM +0530, shirish शिरीष wrote: > Hi all, > > Warning - is a bit of a long read. > > >From what all I read and understood, ext4lazyinit simply makes you > start using the hdd without creating all the inodes for your system. > The only way that you know ext4lazyinit

Bug#852749: Aw: Re: Bug#852749: linux-image-4.9.0-1-amd64: usb-audio-device not working since kernel 4.9.0.1

Hello, i have tested the patches following the link you gave me, and there is a partitial sucess. The error message did not show up and there where no audio related errors in syslog. The device was recognized correctly and the toneport-module was loaded without errors or warnings. But audio pla

Do I have to do anything to make sure ext4lazyinit works as being advertised ?

Hi all, Warning - is a bit of a long read. >From what all I read and understood, ext4lazyinit simply makes you start using the hdd without creating all the inodes for your system. The only way that you know ext4lazyinit is working is when you see it via iotop. But when using debian-installer is t

Processed: Re: Bug#853736: bugs.debian.org: Battery sometimes not detected (Macbook Air 2011 and Macbook Pro 2012)

Processing control commands: > reassign -1 linux-image-4.9.0-1-amd64 Bug #853736 [bugs.debian.org] bugs.debian.org: Battery sometimes not detected (Macbook Air 2011 and Macbook Pro 2012) Bug reassigned from package 'bugs.debian.org' to 'linux-image-4.9.0-1-amd64'. Ignoring request to alter found

[PATCH RESEND] Documentation/sphinx: prevent generation of .pyc files in the source tree

Use PYTHONDONTWRITEBYTECODE=1 to prevent python from creating .pyc files in the source tree. Python 3.2 has a __pycache__ scheme [1], but before that the only alternative seems to be to copy the source files to the build tree to ensure the .pyc files are created there too. Just prevent .pyc file ge

Processed: Re: Bug#852556: linux-image-4.9.0-1-amd64: [Regression] Trendnet's TU-ET100C Pegasus II based LAN to USB adapter stopped to work

Processing control commands: > tag -1 -moreinfo +patch Bug #852556 [src:linux] linux-image-4.9.0-1-amd64: [Regression] Trendnet's TU-ET100C Pegasus II based LAN to USB adapter stopped to work Removed tag(s) moreinfo. Bug #852556 [src:linux] linux-image-4.9.0-1-amd64: [Regression] Trendnet's TU-E

Bug#852556: linux-image-4.9.0-1-amd64: [Regression] Trendnet's TU-ET100C Pegasus II based LAN to USB adapter stopped to work

Control: tag -1 -moreinfo +patch On viernes, 27 de enero de 2017 03:45:51 ART Ben Hutchings wrote: > Control: tag -1 patch moreinfo > > Please test whether the attached patch fixes this. You can find > instructions for rebuilding the kernel package at: > https://kernel-handbook.alioth.debian.or

Re: Sphinx builds always write to the source directory

On Tue, 31 Jan 2017 09:32:20 +0200 Jani Nikula wrote: > On Tue, 31 Jan 2017, Ben Hutchings wrote: > > I'm having trouble with the Debian packaging of kernel documentation. > > We try to build everything in a separate output directory (underneath > > debian/build), but the new Sphinx-based build

Bug#853170: fails to boot on debian's MP30-AR1 systems [regression]

Quick test with 4.9.2-2 with new arm64 kernel config: boots 4.9.6-3 work old arm64 kernel config: booms This hints that numerous kernel config changes we did are probably not the reason, but some of the kernel changes between 4.9.2 and 4.9.6. Especially between 4.9.5 and 4.9.6 a bulk of arm64 ch

Bug#853728: linux-image-4.9.0-1-amd64: Wifi and bluetooth stop working

Package: src:linux Version: 4.9.2-2 Severity: normal Dear Maintainer, After upgrade i lost connection to my wifi and bluetooth. Network manager doesn't show the wifi options 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: ideapad_bluetooth: Bluetooth So

linux_4.9.2-2~bpo8+1_amd64.changes ACCEPTED into jessie-backports, jessie-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Jan 2017 23:03:20 +0100 Source: linux Binary: linux-source-4.9 linux-support-4.9.0-0.bpo.1 linux-doc-4.9 linux-manual-4.9 linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 libusbip-de

Bug#853519: linux: ftbfs with GCC-7

Package: src:linux Version: 4.9.2-2 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-7 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone

Re: Sphinx builds always write to the source directory

On Tue, 31 Jan 2017, Ben Hutchings wrote: > I'm having trouble with the Debian packaging of kernel documentation. > We try to build everything in a separate output directory (underneath > debian/build), but the new Sphinx-based build system writes to the > source directory. > > Firstly, Python cr