I don't think it's directly related, but I also see the umask not being consistent:
$ ls -l boot/ total 42968 -rw-r--r-- 1 root root 1005798 Oct 10 00:49 abi-3.11.0-12-generic -rw-r--r-- 1 root root 1003704 Nov 4 08:44 abi-3.12.0-031200-generic -rw-r--r-- 1 root root 163251 Oct 10 00:49 config-3.11.0-12-generic -rw-r--r-- 1 root root 162643 Nov 4 08:44 config-3.12.0-031200-generic -rw-r--r-- 1 root root 11724654 Nov 4 10:13 initrd.img-3.11.0-12-generic -rw-r--r-- 1 root root 11768349 Nov 5 19:50 initrd.img-3.12.0-031200-generic -rw-r--r-- 1 root root 3285893 Oct 10 00:49 System.map-3.11.0-12-generic -rw------- 1 root root 3466224 Nov 4 08:44 System.map-3.12.0-031200-generic -rw-r--r-- 1 root root 5600016 Oct 10 00:49 vmlinuz-3.11.0-12-generic -rw------- 1 root root 5793312 Nov 4 08:44 vmlinuz-3.12.0-031200-generic
I can log this as a separate issue, though what package should it be against if it's the mainline kernel, as we see here?
I don't think it's directly related, but I also see the umask not being consistent:
$ ls -l boot/ 0-12-generic 0-031200- generic 3.11.0- 12-generic 3.12.0- 031200- generic img-3.11. 0-12-generic img-3.12. 0-031200- generic map-3.11. 0-12-generic map-3.12. 0-031200- generic 3.11.0- 12-generic 3.12.0- 031200- generic
total 42968
-rw-r--r-- 1 root root 1005798 Oct 10 00:49 abi-3.11.
-rw-r--r-- 1 root root 1003704 Nov 4 08:44 abi-3.12.
-rw-r--r-- 1 root root 163251 Oct 10 00:49 config-
-rw-r--r-- 1 root root 162643 Nov 4 08:44 config-
-rw-r--r-- 1 root root 11724654 Nov 4 10:13 initrd.
-rw-r--r-- 1 root root 11768349 Nov 5 19:50 initrd.
-rw-r--r-- 1 root root 3285893 Oct 10 00:49 System.
-rw------- 1 root root 3466224 Nov 4 08:44 System.
-rw-r--r-- 1 root root 5600016 Oct 10 00:49 vmlinuz-
-rw------- 1 root root 5793312 Nov 4 08:44 vmlinuz-
I can log this as a separate issue, though what package should it be against if it's the mainline kernel, as we see here?