I made a test with v3.11-rc5-saucy:
# md5sum linux-* ecb40827ad3979c503cc0c2d1972317e linux-headers-3.11.0-031100rc5_3.11.0-031100rc5.201308112135_all.deb fee51a20890c8f040ad5cf8f9b34cfc1 linux-headers-3.11.0-031100rc5-generic_3.11.0-031100rc5.201308112135_amd64.deb 1e8feff839613a7ecee2ed6d2ea8e722 linux-image-3.11.0-031100rc5-generic_3.11.0-031100rc5.201308112135_amd64.deb #
The problem is still exists.
One question: If i upgrade to 13.04, then i must open a new bug ID, or can continue with this?
I made a test with v3.11-rc5-saucy:
# md5sum linux-* 503cc0c2d197231 7e linux-headers- 3.11.0- 031100rc5_ 3.11.0- 031100rc5. 201308112135_ all.deb 40ad5cf8f9b34cf c1 linux-headers- 3.11.0- 031100rc5- generic_ 3.11.0- 031100rc5. 201308112135_ amd64.deb ecee2ed6d2ea8e7 22 linux-image- 3.11.0- 031100rc5- generic_ 3.11.0- 031100rc5. 201308112135_ amd64.deb
ecb40827ad3979c
fee51a20890c8f0
1e8feff839613a7
#
The problem is still exists.
One question: If i upgrade to 13.04, then i must open a new bug ID, or can continue with this?