similar to: Plan for libguestfs 1.34

Displaying 20 results from an estimated 2000 matches similar to: "Plan for libguestfs 1.34"

2015 Nov 24
0
Plan for libguestfs 1.32
Libguestfs 1.30 was released on 2015-07-21 and because of my wish to rebase libguestfs in RHEL 7.3, I'd like to release 1.32 in early December. Please follow-up if there are features / blockers / bugs that need to be addressed for 1.32. As usual, bugs which have "1.32" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see
2015 Jun 30
5
Plan for libguestfs 1.30
It has been a ludicrously long time (over 8 months) since the last stable release of libguestfs. So I'd like to plan a new 1.30 release soon. Please follow-up if there are features / blockers / bugs that need to be addressed for 1.30. As usual, bugs which have "1.30" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see
2014 Jan 24
2
Plan for libguestfs 1.26
It has been 3 months since the last stable release of libguestfs. I'd like to plan a new 1.26 release towards the middle/end of next month. There are some virt-builder features I'd like to get in before then: - virt-builder needs to be able to use Linux distro published cloud images as a source (without requiring a lot of manual config as now) - virt-builder must be able to
2014 Oct 10
0
Re: Plan for libguestfs 1.28
HI, Richard Is there any plan to make daemon to directly run on the hypervisor, not starting a guest? e.g. directly export a guest image to be a block device on the hypervisor? On Tue, Oct 7, 2014 at 8:28 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > It has been an amazing 6½ months since the last stable release of > libguestfs. > > I'd like to plan a new 1.28 release
2013 Oct 03
0
Plan for libguestfs 1.24
It has been 5 months since the last stable release of libguestfs and over that time we've accumulated many exciting new features. It's time to plan for the release of libguestfs 1.24. As usual, bugs which have "1.24" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see a list of those here, currently empty:
2017 Feb 17
2
Plan for libguestfs 1.36
Libguestfs 1.34 was released on 2016-08-08, which is about 6 months ago. I'd would like to think about what needs work for the next stable 1.36 release, which might happen at the end of this month. Any new APIs added in the 1.35 cycle will become supported and guaranteed when we release 1.36, so we need to check those. See: git diff v1.34.0 -- generator/actions.ml It looks like there
2014 Oct 08
0
Virt-v2v conversion issue
Hi, I meet an amazing issue, when I convert a raw file to the oVirt environment using virt-v2v. All seems to work fine, my VM is composed of 9 disks, the processes finishes without any trouble, the files are well present in the right import volume, but only the first system disk appear un my oVirt Import VM. I've retried twice and had the same issue . Here the results of the conversion : [
2014 Oct 07
7
Plan for libguestfs 1.28
It has been an amazing 6½ months since the last stable release of libguestfs. I'd like to plan a new 1.28 release soon. Please follow-up if there are features / blockers / bugs that need to be addressed for 1.28. As usual, bugs which have "1.28" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see a list of those here
2016 Jul 22
3
Re: Plan for libguestfs 1.34
On Fri, Jul 22, 2016 at 11:15:55AM +0200, Pino Toscano wrote: > On Tuesday, 12 July 2016 20:37:56 CEST Richard W.M. Jones wrote: > > Libguestfs 1.32 was released on 2016-01-06, which is over 6 months > > ago. In fact the previous stable version of libguestfs (1.30) was > > released on 2015-07-21, almost exactly 12 months ago. Are we heading > > for a 6 month release
2016 Jul 23
0
Re: Plan for libguestfs 1.34
On Fri, Jul 22, 2016 at 10:25:54AM +0100, Richard W.M. Jones wrote: > On Fri, Jul 22, 2016 at 11:15:55AM +0200, Pino Toscano wrote: > > On Tuesday, 12 July 2016 20:37:56 CEST Richard W.M. Jones wrote: > > > Libguestfs 1.32 was released on 2016-01-06, which is over 6 months > > > ago. In fact the previous stable version of libguestfs (1.30) was > > > released on
2016 Jul 22
0
Re: Plan for libguestfs 1.34
On Tuesday, 12 July 2016 20:37:56 CEST Richard W.M. Jones wrote: > Libguestfs 1.32 was released on 2016-01-06, which is over 6 months > ago. In fact the previous stable version of libguestfs (1.30) was > released on 2015-07-21, almost exactly 12 months ago. Are we heading > for a 6 month release cycle? Not officially. Anyway, I would like > you to think about what needs work for
2017 Apr 05
1
Key table name malformed
MJ, I put some extra info on this for the list. This is a new Debian Jessie install with sernet samba packages. The Keytab file is not created with sernet 4.6.1 packages but it is with the sernet 4.5.7 samba packages. Bug list show some keytab reported but i dont see any related to this.
2019 Feb 14
3
Geany 1.34
On Thu, 14 Feb 2019 at 12:47, H <agents at meddatainc.com> wrote: > > On 02/14/2019 05:58 PM, Tate Belden wrote: > > FWIW, on Fedora 29, I'm running Geany 1.34.1 and didn't have to enable > > anything other than the default repositories. So, it'd appear to at least > > be in the stream. > > > > geany-1.34.1-2.fc29.x86_64 > > > > On
2016 Jul 12
2
Do we need a rebase bug for RHEL 7.4?
Hi Pino, $subject -- do we intend to rebase libguestfs, virt-v2v and virt-p2v in RHEL 7.4? If yes, we should file the rebase bug soon. Pros: - The RHEL 7.3 package has 151 patches on top of 1.32.6. Rebasing would get almost all those patches. Not rebasing would mean (at predicted growth rate) shipping ~300-400 patches. - Backporting patches is currently hard work since the code
2019 Feb 14
2
Geany 1.34
FWIW, on Fedora 29, I'm running Geany 1.34.1 and didn't have to enable anything other than the default repositories. So, it'd appear to at least be in the stream. geany-1.34.1-2.fc29.x86_64 On Thu, Feb 14, 2019 at 8:53 AM H <agents at meddatainc.com> wrote: > On 01/04/2019 04:17 AM, H wrote: > > Does anyone know if Geany 1.34 is headed to one of the repositories? I
2019 Feb 14
2
Geany 1.34
On 02/14/2019 08:19 PM, Stephen John Smoogen wrote: > On Thu, 14 Feb 2019 at 13:25, Stephen John Smoogen <smooge at gmail.com> wrote: >> On Thu, 14 Feb 2019 at 12:47, H <agents at meddatainc.com> wrote: >>> On 02/14/2019 05:58 PM, Tate Belden wrote: >>>> FWIW, on Fedora 29, I'm running Geany 1.34.1 and didn't have to enable >>>>
2009 Oct 30
5
adding SAN "diskspace" to CentOS system residing on VMware
Hey, group, I've got a system installed on a VMware VM. The SAN administrator allocated me more disk space from the (EMC) SAN and I need ultimately to create another partition to mount on the filesystem. Two (initial) questions about this: What steps do I need to take prior to creating a new partition with fdisk? (The SAN space, BTW, is connected through VMware.) The OS is already
2012 Jul 30
2
distance matrix and hclustering
Dear R Users,i am very new to R. I want your help on an issue regarding distance matrix and cluster analysis i had discharge data of 4 rivers(a,b,c,d) in 4 vectors each having 364 values > dput(qmu)structure(list(a = c(0.26, 0.25, 0.25, 0.25, 0.24, 0.23, 0.22, 0.21, 0.21, 0.21, 0.2, 0.19, 0.19, 0.19, 0.19, 0.18, 0.18, 0.18, 0.17, 0.17, 0.17, 0.17, 0.17, 0.17, 0.17, 0.17, 0.17, 0.17, 0.17, 0.17,
2011 Jul 27
3
Reorganize(stack data) a dataframe inducing names
Dear Contributors, thanks for collaboration. I am trying to reorganize data frame, that looks like this: n1.Index Date PX_LAST n2.Index Date.1 PX_LAST.1 n3.Index Date.2 PX_LAST.2 1 NA 04/02/07 1.34 NA 04/02/07 1.36 NA 04/02/07 1.33 2 NA 04/09/07 1.34 NA 04/09/07
2012 Apr 27
1
Help with software raid + LVM on Centos 6
Hi all, Please excuse the many posts. Wondering if any one can help me with the the setup. I have 2x2TBdisks. I would like to mirror them. I would like to create two LVMs so that I can snap shot from one to the other. During Centos 6 install, how would I go about this as its confusing? So far I am here; 1) Created the following raid devices; md0 500MB (use it for /boot) md1 4000MB (use it