Bug#770761: intel-microcode: should Depends: on the first working linux-image version (e.g. backports)

2014-12-06 Thread Henrique de Moraes Holschuh
On Fri, 05 Dec 2014, Kenyon Ralph wrote:
 On 2014-11-27T14:05:25-0200, Henrique de Moraes Holschuh h...@debian.org 
 wrote:
Versions of packages intel-microcode recommends:
ii  initramfs-tools  0.109.1
   
   This is going to be a problem as well.  I will consider switching to a
   Depends.
  
  I've switched to a depends for backports, I can undo this easily if it
  causes problems.  Unstable and stable will remain with a recommends.
 
 The change from Recommends to Depends for initramfs-tools is
 preventing upgrade from intel-microcode 3.20140913.1~bpo70+1 to
 3.20140913.1~bpo70+2. I have dracut installed instead of

Kenyon, can you please file a new wishlist bug against intel-microcode
requesting dracut support?

Right now, there is no reason to use the 3.x branch of intel-microcode (i.e.
the one that has a Depends: initramfs-tools with dracut in Debian wheezy.
The whole point of the backported intel-microcode packages is early
initramfs support for initramfs-tools.

Since you're using dracut in Debian wheezy, please switch back to the stable
(wheezy) intel-microcode packages for the moment.

I will work with you in the new bug report I asked you to open, so that we
can address proper dracut support for early intel microcode updates.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


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



Bug#770761: intel-microcode: should Depends: on the first working linux-image version (e.g. backports)

2014-12-05 Thread Kenyon Ralph
On 2014-11-27T14:05:25-0200, Henrique de Moraes Holschuh h...@debian.org 
wrote:
   Versions of packages intel-microcode recommends:
   ii  initramfs-tools  0.109.1
  
  This is going to be a problem as well.  I will consider switching to a
  Depends.
 
 I've switched to a depends for backports, I can undo this easily if it
 causes problems.  Unstable and stable will remain with a recommends.

The change from Recommends to Depends for initramfs-tools is
preventing upgrade from intel-microcode 3.20140913.1~bpo70+1 to
3.20140913.1~bpo70+2. I have dracut installed instead of
initramfs-tools, so to upgrade, I would have to replace dracut with
initramfs-tools. My understanding is that dracut is the replacement
for initramfs-tools.

-- 
Kenyon Ralph

-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages intel-microcode depends on:
ii  iucode-tool  1.1.1-1~bpo70+1

Versions of packages intel-microcode recommends:
pn  initramfs-tools  none

intel-microcode suggests no packages.

-- no debconf information


signature.asc
Description: Digital signature


Bug#770761: intel-microcode: should Depends: on the first working linux-image version (e.g. backports)

2014-11-30 Thread Luca Capello
Hi Henrique,

On Thu, 27 Nov 2014 14:05:25 -0200, Henrique de Moraes Holschuh wrote:
 On Sun, 23 Nov 2014, Henrique de Moraes Holschuh wrote:
  On Sun, 23 Nov 2014, Luca Capello wrote:
   while installing a new Debian wheezy following our internal
   instructions[1] that worked flawlessly in the past, I was quite
   surprised by the error message about not supported kernel appeared
   during the intel-microcode installation.
  
  ...
  
   1) the default apt-listchanges/which debconf value is news, which means
  that on upgrades the above message is not shown, instead it should
 
  have been added to debian/NEWS.
  
  It *is* in NEWS.Debian.  However, it won't work right for the backported
  package because the version heading in the NEWS file does not end with a
  ~.
 
 I have tested this, and apt-listchanges *did* display the NEWS entry on
 upgrade both from the stable version, and the previous backported version.

My fault, I was thinking something and writing another thing: it should
have been which means that on *new installations* the above message is
not shown.

 But this thing is known to be flaky, and the test procedure requires
 removing the apt-listchanges database (which could easily defuse a bug), so
 I will repload with a bumped version in the NEWS file in hope that it will
 ensure more people gets the warning.

Thank you.

   2) AFAIK, if a backport package needs a feature of another backport
  package to work on a stable installation, than the second package
  should be a Depends:.
 
  That I can't do.  This is a runtime dependency on the kernel version you're
  building the initramfs *for*.  It is not even related to whatever kernel
  you're running at the time the initramfs is built.

Exactly because it is not related to the kernel you are running, but on
*at least* one kernel package installed IMHO it is an hard Depends: for
Debian.

  If you don't need any of the features in the backported intel-microcode
  package, why were using it instead of the stable package?  early microcode
  update support is the whole *point* of the backported package...

IMHO there are two problems in your reasoning: first, how do I know if I
need any of the features in the backported package?  If I have to
manually check them *before* installing the package I do not see why I
would use the Debian package at all.

Second, the previous backported package worked with no problems, it is
the new version that actually stopped working ;-)

To solve both problems there should be a way to say: look, you are
installing a package that requires a newer kernel version...

   Versions of packages intel-microcode recommends:
   ii  initramfs-tools  0.109.1
  
  This is going to be a problem as well.  I will consider switching to a
  Depends.
 
 I've switched to a depends for backports, I can undo this easily if it
 causes problems.  Unstable and stable will remain with a recommends.

Thank you very much!  However, this does not seem to automatically pull
a backported kernel:
=
# apt-get update
[...]
# apt-get install -d -t wheezy-backports initramfs-tools
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  initramfs-tools
1 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
Need to get 0 B/92.6 kB of archives.
After this operation, 3,072 B of additional disk space will be used.
[...]
# 
=

BTW, this is not the first time you are so supportive on one of the bugs
 I have reported, it is a pleasure to deal with you :-D

Thx, bye,
Gismo / Luca


signature.asc
Description: Digital signature


Bug#770761: intel-microcode: should Depends: on the first working linux-image version (e.g. backports)

2014-11-27 Thread Henrique de Moraes Holschuh
On Sun, 23 Nov 2014, Henrique de Moraes Holschuh wrote:
 On Sun, 23 Nov 2014, Luca Capello wrote:
  while installing a new Debian wheezy following our internal
  instructions[1] that worked flawlessly in the past, I was quite
  surprised by the error message about not supported kernel appeared
  during the intel-microcode installation.
 
 ...
 
  1) the default apt-listchanges/which debconf value is news, which means
 that on upgrades the above message is not shown, instead it should
 have been added to debian/NEWS.
 
 It *is* in NEWS.Debian.  However, it won't work right for the backported
 package because the version heading in the NEWS file does not end with a
 ~.

I have tested this, and apt-listchanges *did* display the NEWS entry on
upgrade both from the stable version, and the previous backported version.

But this thing is known to be flaky, and the test procedure requires
removing the apt-listchanges database (which could easily defuse a bug), so
I will repload with a bumped version in the NEWS file in hope that it will
ensure more people gets the warning.

  Versions of packages intel-microcode recommends:
  ii  initramfs-tools  0.109.1
 
 This is going to be a problem as well.  I will consider switching to a
 Depends.

I've switched to a depends for backports, I can undo this easily if it
causes problems.  Unstable and stable will remain with a recommends.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


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



Bug#770761: intel-microcode: should Depends: on the first working linux-image version (e.g. backports)

2014-11-23 Thread Luca Capello
Package: intel-microcode
Version: 3.20140913.1~bpo70+1
Severity: important
User: cont...@itopie.ch
Usertags: debian-packaging

Hi there,

while installing a new Debian wheezy following our internal
instructions[1] that worked flawlessly in the past, I was quite
surprised by the error message about not supported kernel appeared
during the intel-microcode installation.

[1] https://docs.itopie.ch/installation/debian

Anyway, I rebooted and since there was still no intel-microcode loaded I
checked the debian/changelog:

--8---cut here---start-8---
intel-microcode (3.20140913.1~bpo70+1) wheezy-backports; urgency=medium

  * Rebuild for wheezy-backports (no changes)
  * THIS PACKAGE REQUIRES LINUX KERNEL 3.10 OR LATER, YOU MUST USE A
BACKPORTED OR CUSTOM KERNEL.  If you use the regular Debian stable
(wheezy) kernel (Linux 3.2), please use the stable (wheezy)
intel-microcode package.

 -- Henrique de Moraes Holschuh h...@debian.org  Thu, 30 Oct 2014 16:19:08 
-0200
--8---cut here---end---8---

I am sorry, but I see two important errors here:

1) the default apt-listchanges/which debconf value is news, which means
   that on upgrades the above message is not shown, instead it should
   have been added to debian/NEWS.

2) AFAIK, if a backport package needs a feature of another backport
   package to work on a stable installation, than the second package
   should be a Depends:.

Thx, bye,
Gismo / Luca

-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages intel-microcode depends on:
ii  iucode-tool  1.1-1~bpo70+1

Versions of packages intel-microcode recommends:
ii  initramfs-tools  0.109.1

intel-microcode suggests no packages.

-- no debconf information


signature.asc
Description: Digital signature


Bug#770761: intel-microcode: should Depends: on the first working linux-image version (e.g. backports)

2014-11-23 Thread Henrique de Moraes Holschuh
On Sun, 23 Nov 2014, Luca Capello wrote:
 while installing a new Debian wheezy following our internal
 instructions[1] that worked flawlessly in the past, I was quite
 surprised by the error message about not supported kernel appeared
 during the intel-microcode installation.

...

 1) the default apt-listchanges/which debconf value is news, which means
that on upgrades the above message is not shown, instead it should
have been added to debian/NEWS.

It *is* in NEWS.Debian.  However, it won't work right for the backported
package because the version heading in the NEWS file does not end with a
~.

I will fix that.

And I am likely to file a bug on apt-listchages, too: it shouldn't be
skipping entries it didn't display previously just because they are in the
future.

 2) AFAIK, if a backport package needs a feature of another backport
package to work on a stable installation, than the second package
should be a Depends:.

That I can't do.  This is a runtime dependency on the kernel version you're
building the initramfs *for*.  It is not even related to whatever kernel
you're running at the time the initramfs is built.

If you don't need any of the features in the backported intel-microcode
package, why were using it instead of the stable package?  early microcode
update support is the whole *point* of the backported package...

 Versions of packages intel-microcode recommends:
 ii  initramfs-tools  0.109.1

This is going to be a problem as well.  I will consider switching to a
Depends.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


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