Re: Forward porting a package

To: "debian-devel@lists.debian.org" <debian-devel@lists.debian.org>
Subject: Re: Forward porting a package
From: "Boylan, Ross" <Ross.Boylan@ucsf.edu>
Date: Wed, 10 May 2017 00:52:51 +0000
Message-id: <[🔎] CY1PR05MB266613D7429C06D9A88DF9AC87EC0@CY1PR05MB2666.namprd05.prod.outlook.com>
In-reply-to: <[🔎] CY1PR05MB2666A8DCEE91BBCF6BEDD7A687EF0@CY1PR05MB2666.namprd05.prod.outlook.com>
References: <[🔎] CY1PR05MB2666D8D74AA8A4C746497FDE87EF0@CY1PR05MB2666.namprd05.prod.outlook.com>,<[🔎] CY1PR05MB2666A8DCEE91BBCF6BEDD7A687EF0@CY1PR05MB2666.namprd05.prod.outlook.com>

Oops, I misspoke, the old system is Debian 5, lenny.
The system the disks are on is running Debian 7, wheezy.
And the system I am targetting is Debian 8, jessie.

So the chroot would be lenny while the real system wouldl be wheezy.

The wheezy system already hosts VM's with libvirt.  But getting things working as a VM seems a bit tricky.  I can't simply hand the disks over to the VM because the host is using them too.  And I'm concerned that anything I give to the VM will end up with vm control info written to it, at least if I'm not careful.

Ross

Reply to:

References:
- Forward porting a package
  - From: "Boylan, Ross" <Ross.Boylan@ucsf.edu>
- Re: Forward porting a package
  - From: "Boylan, Ross" <Ross.Boylan@ucsf.edu>

Prev by Date: Re: Forward porting a package
Next by Date: Re: Forward porting a package
Previous by thread: Re: Forward porting a package
Next by thread: Bug#862235: ITP: node-dot -- Concise and fast javascript templating
Index(es):
- Date
- Thread