[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#842919: marked as done (transition: xen)

Your message dated Wed, 16 Nov 2016 10:06:27 +0100
with message-id <42c52df8-3f11-8872-7130-160b741a63da@debian.org>
and subject line Re: Bug#842919: transition: xen (vs. grub2) [and 1 more messages]
has caused the Debian Bug report #842919,
regarding transition: xen
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
842919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842919
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi.  This is the update from Xen 4.6 to Xen 4.8, as previously
discussed.  (Currently, Xen 4.8.0 RC3.  I expect the Xen 4.8.0 release
to be out by the time Debian freezes.)

libxen-* contains libraries needed for management tools.   The
corresponding xen-utils-* packages are intended to be coinstallable,
so perhaps a "smooth" transition may still be possible ?  (Contrary to
what the autogenerated transition tracker thinks.)

All that is needed from the build-rdeps is a rebuild.  That is, of:
  libvirt qemu xenwatch python-pyxenstore collectd grub2

I have checked that they all build against the new libxen{-4.8,-dev},
at least on amd64.  I don't anticipate trouble on other architectures.

I am filing this transition bug now even though the armhf buildd has
yet to get to the package.  It seems like it nearly 4 days behind
right now.  Instead, I have verified on a porterbox that the armhf
build is successful.  I hope that is sufficient.

I think the Ben file generated by reportbug from my responses to the
prompts is about right.

Thanks for your attention.  Please let me know if I have done anything
wrong.  This is the first time I have been responsible for a
transition.

Thanks,
Ian.


Ben file:

title = "xen";
is_affected = .depends ~ "libxen-4.6" | .depends ~ "libxen-4.8";
is_good = .depends ~ "libxen-4.8";
is_bad = .depends ~ "libxen-4.6";


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

--- End Message ---
--- Begin Message --- 
On 07/11/16 17:21, Ian Jackson wrote:
> Emilio Pozuelo Monfort writes:
>> I don't plan to binNMU any package that doesn't depend on
>> libxen-4.6. IOW, only qemu and libvirt will be rebuilt.
> 
> Please go ahead (unless it needs to wait for xen itself to clear the
> buildd queues).
> 
> (There are no sourceful uploads needed for this transition.)

That happened and xen migrated. Let's close this.

Cheers,
Emilio

--- End Message ---
Reply to: