Bug#581182: changing severity

2010-07-18 Thread Manoj Srivastava 
severity 581182  important
thanks

Hi,

On Fri, Jun 04 2010, Christoph Anton Mitterer wrote:

 severity 581182 grave
 stop

 Changing severity to grave (makes the package in question unusable or
 mostly so) as it seems that also 2.6.32 kernels are affected, which are
 now in unstable, and therefore make this package unusable there.


So, I tried the latest stable kernel, 2.6.34.1:

,[ Commands used ]
| export MODULE_LOC=/usr/local/src/kernel/modules
| 
| ev=$(uname -n)
| if [ -n $1 ]; then
|   ev=$1
| fi
| 
| make-kpkg --rootcmd=fakeroot --append-to-version=-$ev kernel_image
| fakeroot make-kpkg   --append-to-version=-$ev modules_image
`


,
| __ sudo dpkg -i 
linux-image-2.6.34.1-anzu_2.6.34.1-anzu-10.00.Custom_amd64.deb\
|
nvidia-kernel-2.6.34.1-anzu_195.36.24-1+2.6.34.1-anzu-10.00.Custom_amd64.deb
| Selecting previously deselected package linux-image-2.6.34.1-anzu.
| (Reading database ... 375994 files and directories currently installed.)
| Unpacking linux-image-2.6.34.1-anzu (from 
linux-image-2.6.34.1-anzu_2.6.34.1-anzu-10.00.Custom_amd64.deb) ...
| Examining /etc/kernel/preinst.d/
| Done.
| Selecting previously deselected package nvidia-kernel-2.6.34.1-anzu.
| Unpacking nvidia-kernel-2.6.34.1-anzu (from 
nvidia-kernel-2.6.34.1-anzu_195.36.24-1+2.6.34.1-anzu-10.00.Custom_amd64.deb) 
...
| Setting up linux-image-2.6.34.1-anzu (2.6.34.1-anzu-10.00.Custom) ...
| Running depmod.
| Examining /etc/kernel/postinst.d.
| run-parts: executing /etc/kernel/postinst.d/dkms 2.6.34.1-anzu 
/boot/vmlinuz-2.6.34.1-anzu
| run-parts: executing /etc/kernel/postinst.d/force-build-link 2.6.34.1-anzu 
/boot/vmlinuz-2.6.34.1-anzu
| run-parts: executing /etc/kernel/postinst.d/initramfs 2.6.34.1-anzu 
/boot/vmlinuz-2.6.34.1-anzu
| run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.34.1-anzu 
/boot/vmlinuz-2.6.34.1-anzu
| Running postinst hook script update-grub.
| Generating grub.cfg ...
| Found linux image: /boot/vmlinuz-2.6.34.1-anzu
| Found linux image: /boot/vmlinuz-2.6.34-anzu
| Found linux image: /boot/vmlinuz-2.6.32.8-anzu
| Found linux image: /boot/vmlinuz-2.6.32.7-anzu
| Found linux image: /boot/vmlinuz-2.6.32.1-anzu
| Found linux image: /boot/vmlinuz-2.6.32-anzu
| Found memtest86 image: /memtest86.bin
| Found memtest86+ image: /memtest86+_multiboot.bin
| Found Ubuntu 7.04 (7.04) on /dev/sda2
| done
| Setting up nvidia-kernel-2.6.34.1-anzu 
(195.36.24-1+2.6.34.1-anzu-10.00.Custom) ...
`

Then I tried:
make-kpkg --rootcmd=fakeroot --append-to-version=-anzu buildpackage

And that failed. So, the buildpackage target is borked. That
 does not make it mostly useless. I'll look into the issue; in the
 meanwhile, you can build, individually, the packages you need; though
 I understand no changes files means you can't sign the result (hence
 important severity)

manoj

-- 
I have great faith in fools -- self confidence my friends call it. Edgar
Allan Poe
Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#581182: changing severity

2010-07-18 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

 severity 581182  important
Bug #581182 [kernel-package] kernel-package: make-kpkg buildpackage fails with 
2.6.33
Severity set to 'important' from 'grave'

 thanks
Stopping processing here.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#581182: changing severity

2010-07-17 Thread gregor herrmann 
On Fri, 04 Jun 2010 15:30:29 +0200, Christoph Anton Mitterer wrote:

 Changing severity to grave (makes the package in question unusable or
 mostly so) as it seems that also 2.6.32 kernels are affected, which are
 now in unstable, and therefore make this package unusable there.

I disagree with the unusable assumption; I've been using make-kpkg
successfully with all 2.6.3x kernels [0].


Cheers,
gregor

[0] although without --initrd and with the kernel_image target;
last invocation from my bash history from Wednesday:
$ DISTCC_HOSTS=localhost/2 192.168.0.252/2 192.168.0.1/2 time fakeroot 
make-kpkg -j 6 --append-to-version .201007141816 --revision 1 kernel_image

-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin,  developer - http://www.debian.org/
 `. `'   Member of VIBE!AT  SPI, fellow of Free Software Foundation Europe
   `-BOFH excuse #149:  Dew on the telephone lines. 


signature.asc
Description: Digital signature

Bug#581182: changing severity

2010-07-17 Thread Christoph Anton Mitterer 
Well but for most systems you need --inird(s) and kernel_image is
only part of the story,... have you tried build_package, or modules?

So I really doubt that this justifies downgrading the severity... (just
for the benefit to hide a RC bug)...


Cheers,
Chris.

On Sat, 2010-07-17 at 12:55 +0200, gregor herrmann wrote:
 On Fri, 04 Jun 2010 15:30:29 +0200, Christoph Anton Mitterer wrote:
 
  Changing severity to grave (makes the package in question unusable or
  mostly so) as it seems that also 2.6.32 kernels are affected, which are
  now in unstable, and therefore make this package unusable there.
 
 I disagree with the unusable assumption; I've been using make-kpkg
 successfully with all 2.6.3x kernels [0].
 
 
 Cheers,
 gregor
 
 [0] although without --initrd and with the kernel_image target;
 last invocation from my bash history from Wednesday:
 $ DISTCC_HOSTS=localhost/2 192.168.0.252/2 192.168.0.1/2 time fakeroot 
 make-kpkg -j 6 --append-to-version .201007141816 --revision 1 kernel_image
 



smime.p7s
Description: S/MIME cryptographic signature