Breakages and News tracking Debian Testing

[zerozero]

[let's kick-off this one]

First worthwhile report:
- new kernel update

Start-Date: 2013-03-17 12:39:01
Commandline: apt-get dist-upgrade
Upgrade: libmp3lame-dev:amd64 (3.99.5-dmo1, 3.99.5-dmo2), libmtp9:amd64 (1.1.3-35-g0ece104-4, 1.1.3-35-g0ece104-5), xserver-xorg-video-ati:amd64 (6.14.4-7, 6.14.4-8), libmtp-runtime:amd64 (1.1.3-35-g0ece104-4, 1.1.3-35-g0ece104-5), gstreamer0.10-alsa:amd64 (0.10.36-1, 0.10.36-1.1), libgstreamer-plugins-base0.10-dev:amd64 (0.10.36-1, 0.10.36-1.1), perl:amd64 (5.14.2-19, 5.14.2-20), perl-base:amd64 (5.14.2-19, 5.14.2-20), perl-modules:amd64 (5.14.2-19, 5.14.2-20), linux-image-3.2.0-4-amd64:amd64 (3.2.35-2, 3.2.39-2), linux-headers-3.2.0-4-amd64:amd64 (3.2.35-2, 3.2.39-2), ruby1.8:amd64 (1.8.7.358-6, 1.8.7.358-7), libmp3lame0:amd64 (3.99.5-dmo1, 3.99.5-dmo2), libmp3lame0:i386 (3.99.5-dmo1, 3.99.5-dmo2), linux-headers-3.2.0-4-common:amd64 (3.2.35-2, 3.2.39-2), libmtp-dev:amd64 (1.1.3-35-g0ece104-4, 1.1.3-35-g0ece104-5), mtp-tools:amd64 (1.1.3-35-g0ece104-4, 1.1.3-35-g0ece104-5), gir1.2-gst-plugins-base-0.10:amd64 (0.10.36-1, 0.10.36-1.1), gstreamer0.10-x:amd64 (0.10.36-1, 0.10.36-1.1), libgstreamer-plugins-base0.10-0:amd64 (0.10.36-1, 0.10.36-1.1), libgstreamer-plugins-base0.10-0:i386 (0.10.36-1, 0.10.36-1.1), libperl5.14:amd64 (5.14.2-19, 5.14.2-20), libmtp-common:amd64 (1.1.3-35-g0ece104-4, 1.1.3-35-g0ece104-5), libruby1.9.1:amd64 (1.9.3.194-8, 1.9.3.194-8.1), linux-libc-dev:amd64 (3.2.35-2, 3.2.39-2), linux-libc-dev:i386 (3.2.35-2, 3.2.39-2), xserver-xorg-video-radeon:amd64 (6.14.4-7, 6.14.4-8), libruby1.8:amd64 (1.8.7.358-6, 1.8.7.358-7), ruby1.9.1:amd64 (1.9.3.194-8, 1.9.3.194-8.1), gstreamer0.10-plugins-base:amd64 (0.10.36-1, 0.10.36-1.1)
End-Date: 2013-03-17 12:41:09

and this one is an update i was waiting for some time (the changelog is impressive (both 39.2 and 39.1);
for me specially fixed the freezing with sandy/ivy-bridge processors (no need anymore to push in liquorix kernels), but also

• samsung-laptop: Disable on EFI hardware, to avoid damaging it
• nouveau: Support for newer nvidia chipsets (Closes: #690284)
• radeon: Support for HD7000 'Southern Islands' chips

[cwwgateway]

That's interesting... I've been using liquorix kernels for some time now, but I'm using the normal Debian kernel on my SolydK 64-bit (tracking SolydXK Testing). I've never noticed freezing on Debian kernels that was related to Sandy Bridge (Core i7 2760QM), but it's good that it's fixed for those who need it.

[zerozero]

for me it's almost unusable: 5-10 min idle and the system freezes completely to a point where only hard reboot will do;
there's several (lots actually) of bugs filled in against kernel 3.2 (not only on debian but also in ubuntu/mint).
might be a combination of some specific cpus (mine is the i7-3770K) and MB (i remember reading something about that as well)

[cwwgateway]

Today we have a kernel update (and some multimedia updates):

Code: Select all

Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libfdk-aac0
The following packages will be upgraded:
  ffmpeg libavcodec54 libavdevice54 libavfilter3 libavformat54 libavutil51
  libavutil51:i386 libpostproc52 libswresample0 libswscale2
  linux-headers-3.2.0-4-amd64 linux-headers-3.2.0-4-common
  linux-image-3.2.0-4-amd64 linux-libc-dev python-reportbug synaptic
16 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 36.1 MB of archives.
After this operation, 1,019 kB of additional disk space will be used.
Do you want to continue [Y/n]? y

[zerozero]

yep, here is the 41-2 we talked about some time ago

Code: Select all

Linux amadeu 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux

[cwwgateway]

Yes, I guess it's migrated from Sid. Getting closer and closer to wheezy's release now .

[zerozero]

this means almost certainly that after the freeze we will jump to 3.8.x or even 3.9.
i don't see Ben uploading another interim kernel to sid in such a short time and then migrate the one from experimental (and surely he won't upload another revision to the next stable, not if it's as close to be released as we are expecting)

[cwwgateway]

The 304.88 NVIDIA drivers (the ones Gene had trouble with) have entered testing:

Code: Select all

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libgl1-nvidia-alternatives libgl1-nvidia-glx libglx-nvidia-alternatives
  libxnvctrl0 libxvmcnvidia1 nvidia-alternative nvidia-detect nvidia-glx
  nvidia-kernel-dkms nvidia-settings nvidia-vdpau-driver
  xserver-xorg-video-nvidia
12 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 18.4 MB of archives.
After this operation, 1,072 kB of additional disk space will be used.
Do you want to continue [Y/n]? n
Abort.

[stelios]

Total number of release-critical bugs: 1581
Number concerning the current stable release: 883
Number concerning the next release: 40



The number of critical bugs is down to just 40 and no new bugs were reported the last 24 hours.

Total number of release-critical bugs: 40
Number that have a patch: 13
Number that have a fix prepared and waiting to upload: 3
Number that are being ignored: 0

[cwwgateway]

Thanks stelios. Down to 39 bugs now .

I'm still slightly hesitant to upgrade until I make a more recent backup (because I got my system messed up somewhere between NVIDIA updates and kernel updates a couple of weeks ago). I wiped the USB that PartedMagic was on to put SolydX on it (which I installed yesterday), so now I have to put PartedMagic back on. Then I'll do the upgrade.

[stelios]

"We now have a target date of the weekend of 4th/5th May for the release. We have checked with core teams, and this seems to be acceptable for everyone. This means we are able to begin the final preparations for a release of Debian 7.0 — 'Wheezy'. The intention is only to lift the date if something really critical pops up that is not possible to handle as an errata, or if we end up technically unable to release that weekend (e.g. a required machine crashes or d-i explodes in a giant ball of fire). Every other RC fix that does not make it in time will be r1 material. Please be sure to contact us about the RC fixes you would like included in the point release!"

https://lists.debian.org/debian-devel-a ... 00006.html

So, 29 bugs left ..

http://bugs.debian.org/release-critical/

[cwwgateway]

"We now have a target date of the weekend of 4th/5th May for the release. We have checked with core teams, and this seems to be acceptable for everyone. This means we are able to begin the final preparations for a release of Debian 7.0 — 'Wheezy'. The intention is only to lift the date if something really critical pops up that is not possible to handle as an errata, or if we end up technically unable to release that weekend (e.g. a required machine crashes or d-i explodes in a giant ball of fire). Every other RC fix that does not make it in time will be r1 material. Please be sure to contact us about the RC fixes you would like included in the point release!"

https://lists.debian.org/debian-devel-a ... 00006.html

So, 29 bugs left ..

http://bugs.debian.org/release-critical/

Great news . Looking at udd, there are 21 bugs left (IIRC there were somewhere around 15 a couple of days ago). Looking at your link there are 24... Either way it's progress, and I'm looking forward to installing and using wheezy

[cwwgateway]

Well this is only a breakage if you're running iceweasel from experimental (and I bet most of you aren't), but iceweasel 21.0 (actually it's technically a problem with the xulrunner-21.0 package) requires libc6 >=2.15, which means right now you can only use it in Sid for the time being.

Code: Select all

christopher@chris-laptop:~$ dist-upgrade
[sudo] password for christopher: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  iceweasel orage
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Code: Select all

christopher@chris-laptop:~$ policy iceweasel
iceweasel:
  Installed: 20.0-1
  Candidate: 21.0-1
  Package pin: 21.0-1
  Version table:
     21.0-1 900
          1 http://ftp.us.debian.org/debian/ experimental/main amd64 Packages
 *** 20.0-1 900
        100 /var/lib/dpkg/status
     10.0.12esr-1+nmu1 900
        500 http://ftp.us.debian.org/debian/ testing/main amd64 Packages

Code: Select all

christopher@chris-laptop:~$ sudo apt-get install iceweasel
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 iceweasel : Depends: xulrunner-21.0 (>= 21.0-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
christopher@chris-laptop:~$ sudo apt-get install xulrunner-21.0
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xulrunner-21.0 : Depends: libc6 (>= 2.15) but 2.13-38 is to be installed
                  Depends: libmozjs21d (= 21.0-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

[zerozero]

meaning that more and more packages are depending on libc6 >2.15 (the transition has to be imminent)

[cwwgateway]

meaning that more and more packages are depending on libc6 >2.15 (the transition has to be imminent)

Yes . IIRC, google-chrome-unstable also requires libc6 >=2.15. And so does the version of libreoffice that's currently in Sid (4.0.3).

Hopefully it will transition soon (but it seems like it'll be a little while).

[cwwgateway]

Xfce 4.10 entered Testing . It's not a major update from SolydX's version, but it's worth noting. And you can't upgrade if you have the default apt pinning.

[zerozero]

not a breakage (quite the opposite a smooth upgrade)

Code: Select all

 zerozero@k64-vb ~ $ uname -a
Linux k64-vb 3.9-1-amd64 #1 SMP Debian 3.9.6-1 x86_64 GNU/Linux

linux 3.9.6 is on testing and in our next UP

[ane champenois]

Xfce 4.10 entered Testing . It's not a major update from SolydX's version, but it's worth noting. And you can't upgrade if you have the default apt pinning.

Not a major update but it brings corrections of minor bugs
Most of them are listed here: http://mail.xfce.org/pipermail/xfce-ann ... hread.html

[Frobozky]

My upgrade to kernel 3.9-1 is not going as well. When I restarted, I boot to the tty1 login screen, so the graphic interface isn't starting. I rebooted and chose the 3.2 kernel from grub and everything works fine. When I try reinstalling the new kernel and watching details I see the message Does not represent valid dkms.conf.file and No built_module_name for record # 0. I use nvidia drivers and I installed without the plymouth option.

[zerozero]

Frobozky
the error you see is related to ndiswrapper

Code: Select all

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.9-1-amd64 /boot/vmlinuz-3.9-1-amd64
Error! Bad return status for module build on kernel: 3.9-1-amd64 (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.57/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.9-1-amd64 /boot/vmlinuz-3.9-1-amd64
update-initramfs: Generating /boot/initrd.img-3.9-1-amd64
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.9-1-amd64 /boot/vmlinuz-3.9-1-amd64
run-parts: executing /etc/kernel/postinst.d/zz-extlinux 3.9-1-amd64 /boot/vmlinuz-3.9-1-amd64

i see it also a few times along the upgrade, that is not the issue.
the issue is your nvidia graphic card drivers. you have to re-install them.

Code: Select all

sudo apt-get install --reinstall nvidia-kernel-dkms