linux-signed_2.3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Sep 2016 03:49:45 +0100
Source: linux-signed
Binary: kernel-image-4.7.0-1-amd64-di nic-modules-4.7.0-1-amd64-di 
nic-wireless-modules-4.7.0-1-amd64-di nic-shared-modules-4.7.0-1-amd64-di 
serial-modules-4.7.0-1-amd64-di usb-serial-modules-4.7.0-1-amd64-di 
ppp-modules-4.7.0-1-amd64-di pata-modules-4.7.0-1-amd64-di 
cdrom-core-modules-4.7.0-1-amd64-di firewire-core-modules-4.7.0-1-amd64-di 
scsi-core-modules-4.7.0-1-amd64-di scsi-modules-4.7.0-1-amd64-di 
loop-modules-4.7.0-1-amd64-di btrfs-modules-4.7.0-1-amd64-di 
ext4-modules-4.7.0-1-amd64-di isofs-modules-4.7.0-1-amd64-di 
jfs-modules-4.7.0-1-amd64-di ntfs-modules-4.7.0-1-amd64-di 
xfs-modules-4.7.0-1-amd64-di fat-modules-4.7.0-1-amd64-di 
md-modules-4.7.0-1-amd64-di multipath-modules-4.7.0-1-amd64-di 
usb-modules-4.7.0-1-amd64-di usb-storage-modules-4.7.0-1-amd64-di 
pcmcia-storage-modules-4.7.0-1-amd64-di fb-modules-4.7.0-1-amd64-di 
input-modules-4.7.0-1-amd64-di event-modules-4.7.0-1-amd64-di 
mouse-modules-4.7.0-1-amd64-di nic-pcmcia-modules-4.7.0-1-amd64-di
 pcmcia-modules-4.7.0-1-amd64-di nic-usb-modules-4.7.0-1-amd64-di 
sata-modules-4.7.0-1-amd64-di core-modules-4.7.0-1-amd64-di 
acpi-modules-4.7.0-1-amd64-di i2c-modules-4.7.0-1-amd64-di 
crc-modules-4.7.0-1-amd64-di crypto-modules-4.7.0-1-amd64-di 
crypto-dm-modules-4.7.0-1-amd64-di efi-modules-4.7.0-1-amd64-di 
ata-modules-4.7.0-1-amd64-di mmc-core-modules-4.7.0-1-amd64-di 
mmc-modules-4.7.0-1-amd64-di nbd-modules-4.7.0-1-amd64-di 
squashfs-modules-4.7.0-1-amd64-di speakup-modules-4.7.0-1-amd64-di 
virtio-modules-4.7.0-1-amd64-di uinput-modules-4.7.0-1-amd64-di 
sound-modules-4.7.0-1-amd64-di hyperv-modules-4.7.0-1-amd64-di 
udf-modules-4.7.0-1-amd64-di fuse-modules-4.7.0-1-amd64-di 
linux-image-4.7.0-1-amd64 kernel-image-4.7.0-1-arm64-di 
nic-modules-4.7.0-1-arm64-di nic-wireless-modules-4.7.0-1-arm64-di 
nic-shared-modules-4.7.0-1-arm64-di ppp-modules-4.7.0-1-arm64-di 
cdrom-core-modules-4.7.0-1-arm64-di scsi-core-modules-4.7.0-1-arm64-di 
scsi-modules-4.7.0-1-arm64-di
 loop-modules-4.7.0-1-arm64-di btrfs-modules-4.7.0-1-arm64-di 
ext4-modules-4.7.0-1-arm64-di isofs-modules-4.7.0-1-arm64-di 
jfs-modules-4.7.0-1-arm64-di xfs-modules-4.7.0-1-arm64-di 
fat-modules-4.7.0-1-arm64-di md-modules-4.7.0-1-arm64-di 
multipath-modules-4.7.0-1-arm64-di usb-modules-4.7.0-1-arm64-di 
usb-storage-modules-4.7.0-1-arm64-di fb-modules-4.7.0-1-arm64-di 
input-modules-4.7.0-1-arm64-di event-modules-4.7.0-1-arm64-di 
nic-usb-modules-4.7.0-1-arm64-di sata-modules-4.7.0-1-arm64-di 
core-modules-4.7.0-1-arm64-di i2c-modules-4.7.0-1-arm64-di 
crc-modules-4.7.0-1-arm64-di crypto-modules-4.7.0-1-arm64-di 
crypto-dm-modules-4.7.0-1-arm64-di efi-modules-4.7.0-1-arm64-di 
ata-modules-4.7.0-1-arm64-di mmc-modules-4.7.0-1-arm64-di 
nbd-modules-4.7.0-1-arm64-di squashfs-modules-4.7.0-1-arm64-di 
virtio-modules-4.7.0-1-arm64-di uinput-modules-4.7.0-1-arm64-di 
leds-modules-4.7.0-1-arm64-di udf-modules-4.7.0-1-arm64-di 
fuse-modules-4.7.0-1-arm64-di linux-image-4.7.0-1-arm64
 kernel-image-4.7.0-1-armmp-di nic-modules-4.7.0-1-armmp-di 
nic-wireless-modules-4.7.0-1-armmp-di nic-shared-modules-4.7.0-1-armmp-di 
ppp-modules-4.7.0-1-armmp-di pata-modules-4.7.0-1-armmp-di 
scsi-core-modules-4.7.0-1-armmp-di scsi-modules-4.7.0-1-armmp-di 
loop-modules-4.7.0-1-armmp-di btrfs-modules-4.7.0-1-armmp-di 
ext4-modules-4.7.0-1-armmp-di isofs-modules-4.7.0-1-armmp-di 
jfs-modules-4.7.0-1-armmp-di fat-modules-4.7.0-1-armmp-di 
md-modules-4.7.0-1-armmp-di multipath-modules-4.7.0-1-armmp-di 
usb-modules-4.7.0-1-armmp-di usb-storage-modules-4.7.0-1-armmp-di 
fb-modules-4.7.0-1-armmp-di input-modules-4.7.0-1-armmp-di 
event-modules-4.7.0-1-armmp-di nic-usb-modules-4.7.0-1-armmp-di 
sata-modules-4.7.0-1-armmp-di core-modules-4.7.0-1-armmp-di 
crc-modules-4.7.0-1-armmp-di crypto-modules-4.7.0-1-armmp-di 
crypto-dm-modules-4.7.0-1-armmp-di efi-modules-4.7.0-1-armmp-di 
ata-modules-4.7.0-1-armmp-di mmc-modules-4.7.0-1-armmp-di 
nbd-modules-4.7.0-1-armmp-di
 squashfs-modules-4.7.0-1-armmp-di virtio-modules-4.7.0-1-armmp-di 
uinput-modules-4.7.0-1-armmp-di zlib-modules-4.7.0-1-armmp-di 
leds-modules-4.7.0-1-armmp-di udf-modules-4.7.0-1-armmp-di 
fuse-modules-4.7.0-1-armmp-di mtd-modules-4.7.0-1-armmp-di 
linux-image-4.7.0-1-armmp linux-image-4.7.0-1-armmp-lpae 
kernel-image-4.7.0-1-686-di nic-modules-4.7.0-1-686-di 
nic-wireless-modules-4.7.0-1-686-di nic-shared-modules-4.7.0-1-686-di 
serial-modules-4.7.0-1-686-di usb-serial-modules-4.7.0-1-686-di 
ppp-modules-4.7.0-1-686-di pata-modules-4.7.0-1-686-di 
cdrom-core-modules-4.7.0-1-686-di firewire-core-modules-4.7.0-1-686-di 
scsi-core-modules-4.7.0-1-686-di scsi-modules-4.7.0-1-686-di 
loop-modules-4.7.0-1-686-di btrfs-modules-4.7.0-1-686-di 
ext4-modules-4.7.0-1-686-di isofs-modules-4.7.0-1-686-di 
jfs-modules-4.7.0-1-686-di ntfs-modules-4.7.0-1-686-di 
xfs-modules-4.7.0-1-686-di fat-modules-4.7.0-1-686-di 

Bug#836255: marked as done (DTBs are no longer bundled)

[Debian Bug Tracking System]

Your message dated Wed, 07 Sep 2016 04:48:39 +
with message-id 
and subject line Bug#836255: fixed in linux-signed 2.3
has caused the Debian Bug report #836255,
regarding DTBs are no longer bundled
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.)


-- 
836255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.7.0-1-armmp-lpae
Severity: important

Hi,

starting with 4.7 the DTBs are not part of the package anymore:

# dpkg -L linux-image-4.5.0-2-armmp-lpae|grep dtb|wc -l
349
# dpkg -L linux-image-4.6.0-1-armmp-lpae|grep dtb|wc -l
363
# dpkg -L linux-image-4.7.0-1-armmp-lpae|grep dtb|wc -l
0

which in return makes flash-kernel fail, and the kernel can not be
properly booted (on devices depending on flash-kernel).
--- End Message ---
--- Begin Message ---
Source: linux-signed
Source-Version: 2.3

We believe that the bug you reported is fixed in the latest version of
linux-signed, 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 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux-signed 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)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Sep 2016 03:49:45 +0100
Source: linux-signed
Binary: kernel-image-4.7.0-1-amd64-di nic-modules-4.7.0-1-amd64-di 
nic-wireless-modules-4.7.0-1-amd64-di nic-shared-modules-4.7.0-1-amd64-di 
serial-modules-4.7.0-1-amd64-di usb-serial-modules-4.7.0-1-amd64-di 
ppp-modules-4.7.0-1-amd64-di pata-modules-4.7.0-1-amd64-di 
cdrom-core-modules-4.7.0-1-amd64-di firewire-core-modules-4.7.0-1-amd64-di 
scsi-core-modules-4.7.0-1-amd64-di scsi-modules-4.7.0-1-amd64-di 
loop-modules-4.7.0-1-amd64-di btrfs-modules-4.7.0-1-amd64-di 
ext4-modules-4.7.0-1-amd64-di isofs-modules-4.7.0-1-amd64-di 
jfs-modules-4.7.0-1-amd64-di ntfs-modules-4.7.0-1-amd64-di 
xfs-modules-4.7.0-1-amd64-di fat-modules-4.7.0-1-amd64-di 
md-modules-4.7.0-1-amd64-di multipath-modules-4.7.0-1-amd64-di 
usb-modules-4.7.0-1-amd64-di usb-storage-modules-4.7.0-1-amd64-di 
pcmcia-storage-modules-4.7.0-1-amd64-di fb-modules-4.7.0-1-amd64-di 
input-modules-4.7.0-1-amd64-di event-modules-4.7.0-1-amd64-di 
mouse-modules-4.7.0-1-amd64-di nic-pcmcia-modules-4.7.0-1-amd64-di
 pcmcia-modules-4.7.0-1-amd64-di nic-usb-modules-4.7.0-1-amd64-di 
sata-modules-4.7.0-1-amd64-di core-modules-4.7.0-1-amd64-di 
acpi-modules-4.7.0-1-amd64-di i2c-modules-4.7.0-1-amd64-di 
crc-modules-4.7.0-1-amd64-di crypto-modules-4.7.0-1-amd64-di 
crypto-dm-modules-4.7.0-1-amd64-di efi-modules-4.7.0-1-amd64-di 
ata-modules-4.7.0-1-amd64-di mmc-core-modules-4.7.0-1-amd64-di 
mmc-modules-4.7.0-1-amd64-di nbd-modules-4.7.0-1-amd64-di 
squashfs-modules-4.7.0-1-amd64-di speakup-modules-4.7.0-1-amd64-di 
virtio-modules-4.7.0-1-amd64-di uinput-modules-4.7.0-1-amd64-di 
sound-modules-4.7.0-1-amd64-di hyperv-modules-4.7.0-1-amd64-di 
udf-modules-4.7.0-1-amd64-di fuse-modules-4.7.0-1-amd64-di 
linux-image-4.7.0-1-amd64 kernel-image-4.7.0-1-arm64-di 
nic-modules-4.7.0-1-arm64-di nic-wireless-modules-4.7.0-1-arm64-di 
nic-shared-modules-4.7.0-1-arm64-di ppp-modules-4.7.0-1-arm64-di 
cdrom-core-modules-4.7.0-1-arm64-di scsi-core-modules-4.7.0-1-arm64-di 
scsi-modules-4.7.0-1-arm64-di
 loop-modules-4.7.0-1-arm64-di btrfs-modules-4.7.0-1-arm64-di 
ext4-modules-4.7.0-1-arm64-di isofs-modules-4.7.0-1-arm64-di 
jfs-modules-4.7.0-1-arm64-di xfs-modules-4.7.0-1-arm64-di 
fat-modules-4.7.0-1-arm64-di md-modules-4.7.0-1-arm64-di 
multipath-modules-4.7.0-1-arm64-di usb-modules-4.7.0-1-arm64-di 
usb-storage-modules-4.7.0-1-arm64-di fb-modules-4.7.0-1-arm64-di 
input-modules-4.7.0-1-arm64-di event-modules-4.7.0-1-arm64-di 
nic-usb-modules-4.7.0-1-arm64-di sata-modules-4.7.0-1-arm64-di 
core-modules-4.7.0-1-arm64-di i2c-modules-4.7.0-1-arm64-di 
crc-modules-4.7.0-1-arm64-di crypto-modules-4.7.0-1-arm64-di 
crypto-dm-modules-4.7.0-1-arm64-di efi-modules-4.7.0-1-arm64-di 
ata-modules-4.7.0-1-arm64-di mmc-modules-4.7.0-1-arm64-di 
nbd-modules-4.7.0-1-arm64-di squashfs-modules-4.7.0-1-arm64-di 

Bug#775541: NFS mounts fail at boot after Debian 8.5 upgrade

[paul . szabo]

Dear Vincent,

> Could you provide a bit more information about the package versions
> on your system?
> dpkg -l rpcbind nfs-common nfs-kernel-server systemd

psz@como:~$ dpkg -l rpcbind nfs-common nfs-kernel-server systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   
Architecture  Description
+++-=-=-=-===
ii  nfs-common1:1.2.8-9 i386
  NFS support files common to client and server
ii  nfs-kernel-server 1:1.2.8-9 i386
  support for NFS kernel server
ii  rpcbind   0.2.1-6+deb8u1i386
  converts RPC program numbers into universal addresses
ii  systemd   215-17+deb8u4.psz i386
  system and service manager

The systemd packages are my "own", with my (trivial!) patches as per
https://bugs.debian.org/803013

> Also I think the output of these commands would be helpful
> systemd-analyze critical-path remote-fs-pre.target
> systemd-analyze critical-path nfs-kernel-server.service

I think you meant critical-chain:

psz@como:~$ systemd-analyze critical-chain remote-fs-pre.target
...
remote-fs-pre.target @98ms


psz@como:~$ systemd-analyze critical-chain nfs-kernel-server.service
...
nfs-kernel-server.service +223ms
  basic.target @4.819s
timers.target @4.818s
  systemd-tmpfiles-clean.timer @4.818s
sysinit.target @4.816s
  console-setup.service @4.813s +1ms
kbd.service @4.753s +58ms
  system.slice @108ms
-.slice @103ms

Cheers, Paul

Bug#775541: NFS mounts fail at boot after Debian 8.5 upgrade

[Vincent McIntyre]

Hello Paul

I read your feedback on this issue with interest.
Could you provide a bit more information about the package versions
on your system?

dpkg -l rpcbind nfs-common nfs-kernel-server systemd

Also I think the output of these commands would be helpful

systemd-analyze critical-path remote-fs-pre.target
systemd-analyze critical-path nfs-kernel-server.service

As to your question about After=rpcbind.service vs rpcbind.target,
I think rpcbind.target is correct as you're trying to express
that you want mounting remote filesystems to wait until everything
to do with getting rpcbind going is complete. But I'm far from sure.

Kind regards
Vince

Re: About package linux-image-rt-amd64

[Ben Hutchings]

On Tue, 2016-09-06 at 21:43 +0200, José Agustín Terol Sanchis wrote:
> That totally makes sense!
> 
> I supose that removing the meta-package is better than leave it there,
> since it could remain outdated or cause any kind of conflicts, right?

This is how it works:

- The 'linux-latest' source package is built for a specific Linux ABI
version (currently, 4.7.0-1)
- It builds a meta-package for each of the kernel configurations
enabled for that version, which no longer includes the 'rt-amd64'
configuration
- The FTP team periodically removes binary packages that are not built
by the latest version of a source package ('decrufting')

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


signature.asc
Description: This is a digitally signed message part

Re: About package linux-image-rt-amd64

[José Agustín Terol Sanchis]

That totally makes sense!

I supose that removing the meta-package is better than leave it there,
since it could remain outdated or cause any kind of conflicts, right?

Thank you again,
Agus Terol


2016-09-06 21:31 GMT+02:00 Uwe Kleine-König 
:

> Hello,
>
> On Tue, Sep 06, 2016 at 09:00:36PM +0200, José Agustín Terol Sanchis wrote:
> > A few days ago, I saw that meta-package linux-image-rt-amd64 was
> available
> > on sid. However, it is no more there. Also, I would say this is not the
> > first time I have seen realtime kernal related packages appear and
> disapper
> > on Debian sid (even in testing).
>
> Usually the rt image is provided if there is an rt patch set for the
> given kernel version. See
> https://www.kernel.org/pub/linux/kernel/projects/rt/ for available
> patches.
>
> Best regards
> Uwe
>
>
> --
> Pengutronix e.K.   | Uwe Kleine-König|
> Industrial Linux Solutions | http://www.pengutronix.de/  |
>

Re: About package linux-image-rt-amd64

[Uwe Kleine-König]

Hello,

On Tue, Sep 06, 2016 at 09:00:36PM +0200, José Agustín Terol Sanchis wrote:
> A few days ago, I saw that meta-package linux-image-rt-amd64 was available
> on sid. However, it is no more there. Also, I would say this is not the
> first time I have seen realtime kernal related packages appear and disapper
> on Debian sid (even in testing).

Usually the rt image is provided if there is an rt patch set for the
given kernel version. See
https://www.kernel.org/pub/linux/kernel/projects/rt/ for available
patches.

Best regards
Uwe
 

-- 
Pengutronix e.K.   | Uwe Kleine-König|
Industrial Linux Solutions | http://www.pengutronix.de/  |

About package linux-image-rt-amd64

[José Agustín Terol Sanchis]

Hi,

A few days ago, I saw that meta-package linux-image-rt-amd64 was available
on sid. However, it is no more there. Also, I would say this is not the
first time I have seen realtime kernal related packages appear and disapper
on Debian sid (even in testing).

So, I am a bit confused about kernel team's policies regarding realtime
kernel packaging. Could anyone shed some light on this issue?

Also, is there any plan to get that package back to Debian unstable? I
mean, currently I can directly install linux-image-4.6.0-1-rt-amd64, but I
feel a bit insecure/unconfortable doing that. Having a meta-package
pointing to the last package would seem to me "the correct way".

Thank you in advance,
Agus Terol

Processed: your mail

[Debian Bug Tracking System]

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

> tags 825840 - help
Bug #825840 [linux] bterm: inverts red and blue in localechooser
Removed tag(s) help.
> tags 825840 + patch
Bug #825840 [linux] bterm: inverts red and blue in localechooser
Added tag(s) patch.
> found 825840 4.5.4-1
Bug #825840 [linux] bterm: inverts red and blue in localechooser
There is no source info for the package 'linux' at version '4.5.4-1' with 
architecture ''
Unable to make a source version for version '4.5.4-1'
Marked as found in versions 4.5.4-1.
>
End of message, stopping processing here.

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

Bug#825840: localechooser: image display inverts red and blue color

[Samuel Thibault]

Mathieu Malaterre, on Tue 06 Sep 2016 08:03:53 +0200, wrote:
> On Tue, Sep 6, 2016 at 2:32 AM, Samuel Thibault  wrote:
> > I really don't think it's a bterm bug, its only change of behavior is
> > when type or visual changes, which is not the case. It however does
> > use FBIOPUTCMAP, whose implementation does seem suspicious in offb for
> > RockHo.
> 
> I did initially look into that direction (see the early bug report).
> However when I realized that other TERM did not have the color
> inversion I suspected that bterm was assuming BGR instead of RGB.

What happens is that other terms do not use FBIOPUTCMAP.

There is no risk that bogl gets RGB wrong in there, it just fills a
struct fb_cmap, which has explicit "red", "green", and "blue" field
names :)

> I will try your suggested patch, but I fear it will break every single
> other TERM out there (at least in assumption of color organisation).

They don't use it, so they don't risk breaking.

Samuel

Bug#825840: localechooser: image display inverts red and blue color

[Mathieu Malaterre]

Hi Samuel,

On Tue, Sep 6, 2016 at 2:32 AM, Samuel Thibault  wrote:
> Control: reassign -1 linux
>
> Mathieu Malaterre, on Mon 05 Sep 2016 07:26:15 +0200, wrote:
>> Frame buffer device information:
>> Name: OFfb ATY,RockHo
>> Address : 0x9c008000
>> Size: 614400
>> Type: PACKED PIXELS
>> Visual  : PSEUDOCOLOR
>
>> Frame buffer device information:
>> Name: ATI Radeon 5962
>> Address : 0x9800
>> Size: 33554432
>> Type: PACKED PIXELS
>> Visual  : PSEUDOCOLOR
>
> Ok, so they look very similar. However, one thing that is different
> is the way they handle FBIOPUTCMAP, i.e. offb_setcolreg(). ATY,RockHo
> is not actually recognized by the offb driver, and it reverts to
> "cmap_simple", which may not actually be the proper way for RockHo, and
> it might very well be simply setting rgb in the wrong order.  You could
> try to patch this over in there: turn
>
> case cmap_simple:
> writeb(regno, par->cmap_adr);
> writeb(red, par->cmap_data);
> writeb(green, par->cmap_data);
> writeb(blue, par->cmap_data);
> break;
>
> into
>
> case cmap_simple:
> writeb(regno, par->cmap_adr);
> writeb(blue, par->cmap_data);
> writeb(green, par->cmap_data);
> writeb(red, par->cmap_data);
> break;
>
> I really don't think it's a bterm bug, its only change of behavior is
> when type or visual changes, which is not the case. It however does
> use FBIOPUTCMAP, whose implementation does seem suspicious in offb for
> RockHo.

I did initially look into that direction (see the early bug report).
However when I realized that other TERM did not have the color
inversion I suspected that bterm was assuming BGR instead of RGB.

I will try your suggested patch, but I fear it will break every single
other TERM out there (at least in assumption of color organisation).

-M
PS: I'll send the screenshots separately.