"fatal: A branch named 'meta-orig' already exists."

"fatal: A branch named 'meta-orig' already exists."

[Robert P. J. Day]

  oh, what fresh hell is this?

... snip ...
NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_validate_branches (log file is located at
/home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
ERROR: Logfile of failure stored in:
/home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
Log data follows:
| DEBUG: Executing shell function do_validate_branches
| NOTE: Setting branch meta to
9e70b482d3773abf92c9c5850e134cbca1d5651f
| fatal: A branch named 'meta-orig' already exists.

  this is building core-image-minimal for qemux86, and i'm assuming
this is not fedora rawhide related.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: "fatal: A branch named 'meta-orig' already exists."

[Bruce Ashfield]

On 2015-03-31 6:26 PM, Robert P. J. Day wrote:
>
>    oh, what fresh hell is this?
>
> ... snip ...
> NOTE: Preparing RunQueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: Function failed: do_validate_branches (log file is located at
> /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
> ERROR: Logfile of failure stored in:
> /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
> Log data follows:
> | DEBUG: Executing shell function do_validate_branches
> | NOTE: Setting branch meta to
> 9e70b482d3773abf92c9c5850e134cbca1d5651f
> | fatal: A branch named 'meta-orig' already exists.
>
>    this is building core-image-minimal for qemux86, and i'm assuming
> this is not fedora rawhide related.

You've got a borked tree sitting in work-shared. If you clean-all
and start again, does it show up ?

If it repeats, then it very well could be the version of git in
rawhide that is causing the issue.

Bruce

>
> rday
>

Re: "fatal: A branch named 'meta-orig' already exists."

[Robert P. J. Day]

On Tue, 31 Mar 2015, Bruce Ashfield wrote:

> On 2015-03-31 6:26 PM, Robert P. J. Day wrote:
> >
> >    oh, what fresh hell is this?
> >
> > ... snip ...
> > NOTE: Preparing RunQueue
> > NOTE: Executing SetScene Tasks
> > NOTE: Executing RunQueue Tasks
> > ERROR: Function failed: do_validate_branches (log file is located at
> > /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
> > ERROR: Logfile of failure stored in:
> > /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
> > Log data follows:
> > | DEBUG: Executing shell function do_validate_branches
> > | NOTE: Setting branch meta to
> > 9e70b482d3773abf92c9c5850e134cbca1d5651f
> > | fatal: A branch named 'meta-orig' already exists.
> >
> >    this is building core-image-minimal for qemux86, and i'm assuming
> > this is not fedora rawhide related.
>
> You've got a borked tree sitting in work-shared. If you clean-all
> and start again, does it show up ?
>
> If it repeats, then it very well could be the version of git in
> rawhide that is causing the issue.

  i started with a fresh build, got a validate_branches error, and
used "bb" to dump the log file for that step:

///// START /////

DEBUG: Executing shell function do_validate_branches
NOTE: Setting branch meta to 9e70b482d3773abf92c9c5850e134cbca1d5651f
error: The following untracked working tree files would be removed by checkout:
	.gitignore
	.mailmap
	COPYING
	CREDITS
	Documentation/00-INDEX
	Documentation/ABI/README
	Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads
	Documentation/ABI/obsolete/sysfs-bus-usb
	Documentation/ABI/obsolete/sysfs-class-rfkill
	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus
	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus
	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra
	Documentation/ABI/removed/devfs
	Documentation/ABI/removed/dv1394
	Documentation/ABI/removed/ip_queue
	Documentation/ABI/removed/net_dma
	Documentation/ABI/removed/o2cb
	Documentation/ABI/removed/raw1394
	Documentation/ABI/removed/video1394
	Documentation/ABI/stable/firewire-cdev
	Documentation/ABI/stable/o2cb
	Documentation/ABI/stable/syscalls
	Documentation/ABI/stable/sysfs-acpi-pmprofile
	Documentation/ABI/stable/sysfs-bus-firewire
	Documentation/ABI/stable/sysfs-bus-usb
	Documentation/ABI/stable/sysfs-bus-xen-backend
	Documentation/ABI/stable/sysfs-class-backlight
	Documentation/ABI/stable/sysfs-class-rfkill
	Documentation/ABI/stable/sysfs-class-tpm
	Documentation/ABI/stable/sysfs-class-ubi
	Documentation/ABI/stable/sysfs-class-udc
	Documentation/ABI/stable/sysfs-devices-node
	Documentation/ABI/stable/sysfs-devices-system-cpu
	Documentation/ABI/stable/sysfs-devices-system-xen_memory
	Documentation/ABI/stable/sysfs-driver-ib_srp
	Documentation/ABI/stable/sysfs-driver-qla2xxx
	Documentation/ABI/stable/sysfs-driver-usb-usbtmc
	Documentation/ABI/stable/sysfs-driver-w1_ds28e04
	Documentation/ABI/stable/sysfs-firmware-efi-vars
	Documentation/ABI/stable/sysfs-firmware-opal-dump
	Documentation/ABI/stable/sysfs-firmware-opal-elog
	Documentation/ABI/stable/sysfs-module
	Documentation/ABI/stable/sysfs-transport-srp
	Documentation/ABI/stable/thermal-notification
	Documentation/ABI/stable/vdso
	Documentation/ABI/testing/configfs-spear-pcie-gadget
	Documentation/ABI/testing/configfs-usb-gadget
	Documentation/ABI/testing/configfs-usb-gadget-acm
	Documentation/ABI/testing/configfs-usb-gadget-ecm
	Documentation/ABI/testing/configfs-usb-gadget-eem
	Documentation/ABI/testing/configfs-usb-gadget-ffs
	Documentation/ABI/testing/configfs-usb-gadget-hid
	Documentation/ABI/testing/configfs-usb-gadget-loopback
	Documentation/ABI/testing/configfs-usb-gadget-mass-storage
	Documentation/ABI/testing/configfs-usb-gadget-midi
	Documentation/ABI/testing/configfs-usb-gadget-ncm
	Documentation/ABI/testing/configfs-usb-gadget-obex
	Documentation/ABI/testing/configfs-usb-gadget-phonet
	Documentation/ABI/testing/configfs-usb-gadget-rndis
	Documentation/ABI/testing/configfs-usb-gadget-serial
	Documentation/ABI/testing/configfs-usb-gadget-sourcesink
	Documentation/ABI/testing/configfs-usb-gadget-subset
	Documentation/ABI/testing/configfs-usb-gadget-uac1
	Documentation/ABI/testing/configfs-usb-gadget-uac2
	Documentation/ABI/testing/debugfs-driver-genwqe
	Documentation/ABI/testing/debugfs-ec
	Documentation/ABI/testing/debugfs-ideapad
	Documentation/ABI/testing/debugfs-olpc
	Documentation/ABI/testing/debugfs-pfo-nx-crypto
	Documentation/ABI/testing/debugfs-pktcdvd
	Documentation/ABI/testing/dev-kmsg
	Documentation/ABI/testing/evm
	Documentation/ABI/testing/ima_policy
	Documentation/ABI/testing/procfs-diskstats
	Documentation/ABI/testing/pstore
	Documentation/ABI/testing/sysfs-ata
	Documentation/ABI/testing/sysfs-block
	Documentation/ABI/testing/sysfs-block-bcache
	Documentation/ABI/testing/sysfs-block-dm
	Documentation/ABI/testing/sysfs-block-rssd
	Documentation/ABI/testing/sysfs-block-zram
	Documentation/ABI/testing/sysfs-bus-acpi
	Documentation/ABI/testing/sysfs-bus-bcma
	Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10
	Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x
	Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel
	Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc
	Documentation/ABI/testing/sysfs-bus-css
	Documentation/ABI/testing/sysfs-bus-event_source-devices-events
	Documentation/ABI/testing/sysfs-bus-event_source-devices-form
Aborting
ERROR: Could not checkout meta branch from known hash 9e70b482d3773abf92c9c5850e134cbca1d5651f
WARNING: /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/run.do_validate_branches.11619:1 exit 1 from
  exit 1
ERROR: Function failed: do_validate_branches (log file is located at /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.11619)

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: "fatal: A branch named 'meta-orig' already exists."

[Bruce Ashfield]

On 2015-04-01 3:07 AM, Robert P. J. Day wrote:
> On Tue, 31 Mar 2015, Bruce Ashfield wrote:
>
>> On 2015-03-31 6:26 PM, Robert P. J. Day wrote:
>>>
>>>     oh, what fresh hell is this?
>>>
>>> ... snip ...
>>> NOTE: Preparing RunQueue
>>> NOTE: Executing SetScene Tasks
>>> NOTE: Executing RunQueue Tasks
>>> ERROR: Function failed: do_validate_branches (log file is located at
>>> /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
>>> ERROR: Logfile of failure stored in:
>>> /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
>>> Log data follows:
>>> | DEBUG: Executing shell function do_validate_branches
>>> | NOTE: Setting branch meta to
>>> 9e70b482d3773abf92c9c5850e134cbca1d5651f
>>> | fatal: A branch named 'meta-orig' already exists.
>>>
>>>     this is building core-image-minimal for qemux86, and i'm assuming
>>> this is not fedora rawhide related.
>>
>> You've got a borked tree sitting in work-shared. If you clean-all
>> and start again, does it show up ?
>>
>> If it repeats, then it very well could be the version of git in
>> rawhide that is causing the issue.
>
>    i started with a fresh build, got a validate_branches error, and
> used "bb" to dump the log file for that step:

There's definitely something wrong or a strange integration between
the version of git and that tree.

Without a place to poke at this, there's not much I can say about
actually changing that behaviour.

All my local builds are green, all the yocto release builds are green,
etc, so this is somehow specific to your build and location
environment.

This is on a fully up to date master ?

Bruce

>
> ///// START /////
>
> DEBUG: Executing shell function do_validate_branches
> NOTE: Setting branch meta to 9e70b482d3773abf92c9c5850e134cbca1d5651f
> error: The following untracked working tree files would be removed by checkout:
> 	.gitignore
> 	.mailmap
> 	COPYING
> 	CREDITS
> 	Documentation/00-INDEX
> 	Documentation/ABI/README
> 	Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads
> 	Documentation/ABI/obsolete/sysfs-bus-usb
> 	Documentation/ABI/obsolete/sysfs-class-rfkill
> 	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus
> 	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus
> 	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra
> 	Documentation/ABI/removed/devfs
> 	Documentation/ABI/removed/dv1394
> 	Documentation/ABI/removed/ip_queue
> 	Documentation/ABI/removed/net_dma
> 	Documentation/ABI/removed/o2cb
> 	Documentation/ABI/removed/raw1394
> 	Documentation/ABI/removed/video1394
> 	Documentation/ABI/stable/firewire-cdev
> 	Documentation/ABI/stable/o2cb
> 	Documentation/ABI/stable/syscalls
> 	Documentation/ABI/stable/sysfs-acpi-pmprofile
> 	Documentation/ABI/stable/sysfs-bus-firewire
> 	Documentation/ABI/stable/sysfs-bus-usb
> 	Documentation/ABI/stable/sysfs-bus-xen-backend
> 	Documentation/ABI/stable/sysfs-class-backlight
> 	Documentation/ABI/stable/sysfs-class-rfkill
> 	Documentation/ABI/stable/sysfs-class-tpm
> 	Documentation/ABI/stable/sysfs-class-ubi
> 	Documentation/ABI/stable/sysfs-class-udc
> 	Documentation/ABI/stable/sysfs-devices-node
> 	Documentation/ABI/stable/sysfs-devices-system-cpu
> 	Documentation/ABI/stable/sysfs-devices-system-xen_memory
> 	Documentation/ABI/stable/sysfs-driver-ib_srp
> 	Documentation/ABI/stable/sysfs-driver-qla2xxx
> 	Documentation/ABI/stable/sysfs-driver-usb-usbtmc
> 	Documentation/ABI/stable/sysfs-driver-w1_ds28e04
> 	Documentation/ABI/stable/sysfs-firmware-efi-vars
> 	Documentation/ABI/stable/sysfs-firmware-opal-dump
> 	Documentation/ABI/stable/sysfs-firmware-opal-elog
> 	Documentation/ABI/stable/sysfs-module
> 	Documentation/ABI/stable/sysfs-transport-srp
> 	Documentation/ABI/stable/thermal-notification
> 	Documentation/ABI/stable/vdso
> 	Documentation/ABI/testing/configfs-spear-pcie-gadget
> 	Documentation/ABI/testing/configfs-usb-gadget
> 	Documentation/ABI/testing/configfs-usb-gadget-acm
> 	Documentation/ABI/testing/configfs-usb-gadget-ecm
> 	Documentation/ABI/testing/configfs-usb-gadget-eem
> 	Documentation/ABI/testing/configfs-usb-gadget-ffs
> 	Documentation/ABI/testing/configfs-usb-gadget-hid
> 	Documentation/ABI/testing/configfs-usb-gadget-loopback
> 	Documentation/ABI/testing/configfs-usb-gadget-mass-storage
> 	Documentation/ABI/testing/configfs-usb-gadget-midi
> 	Documentation/ABI/testing/configfs-usb-gadget-ncm
> 	Documentation/ABI/testing/configfs-usb-gadget-obex
> 	Documentation/ABI/testing/configfs-usb-gadget-phonet
> 	Documentation/ABI/testing/configfs-usb-gadget-rndis
> 	Documentation/ABI/testing/configfs-usb-gadget-serial
> 	Documentation/ABI/testing/configfs-usb-gadget-sourcesink
> 	Documentation/ABI/testing/configfs-usb-gadget-subset
> 	Documentation/ABI/testing/configfs-usb-gadget-uac1
> 	Documentation/ABI/testing/configfs-usb-gadget-uac2
> 	Documentation/ABI/testing/debugfs-driver-genwqe
> 	Documentation/ABI/testing/debugfs-ec
> 	Documentation/ABI/testing/debugfs-ideapad
> 	Documentation/ABI/testing/debugfs-olpc
> 	Documentation/ABI/testing/debugfs-pfo-nx-crypto
> 	Documentation/ABI/testing/debugfs-pktcdvd
> 	Documentation/ABI/testing/dev-kmsg
> 	Documentation/ABI/testing/evm
> 	Documentation/ABI/testing/ima_policy
> 	Documentation/ABI/testing/procfs-diskstats
> 	Documentation/ABI/testing/pstore
> 	Documentation/ABI/testing/sysfs-ata
> 	Documentation/ABI/testing/sysfs-block
> 	Documentation/ABI/testing/sysfs-block-bcache
> 	Documentation/ABI/testing/sysfs-block-dm
> 	Documentation/ABI/testing/sysfs-block-rssd
> 	Documentation/ABI/testing/sysfs-block-zram
> 	Documentation/ABI/testing/sysfs-bus-acpi
> 	Documentation/ABI/testing/sysfs-bus-bcma
> 	Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10
> 	Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x
> 	Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel
> 	Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc
> 	Documentation/ABI/testing/sysfs-bus-css
> 	Documentation/ABI/testing/sysfs-bus-event_source-devices-events
> 	Documentation/ABI/testing/sysfs-bus-event_source-devices-form
> Aborting
> ERROR: Could not checkout meta branch from known hash 9e70b482d3773abf92c9c5850e134cbca1d5651f
> WARNING: /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/run.do_validate_branches.11619:1 exit 1 from
>    exit 1
> ERROR: Function failed: do_validate_branches (log file is located at /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.11619)
>
> rday
>

Re: "fatal: A branch named 'meta-orig' already exists."

[Robert P. J. Day]

On Wed, 1 Apr 2015, Bruce Ashfield wrote:

> On 2015-04-01 3:07 AM, Robert P. J. Day wrote:
> > On Tue, 31 Mar 2015, Bruce Ashfield wrote:
> >
> > > On 2015-03-31 6:26 PM, Robert P. J. Day wrote:
> > > >
> > > >     oh, what fresh hell is this?
> > > >
> > > > ... snip ...
> > > > NOTE: Preparing RunQueue
> > > > NOTE: Executing SetScene Tasks
> > > > NOTE: Executing RunQueue Tasks
> > > > ERROR: Function failed: do_validate_branches (log file is located at
> > > > /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
> > > > ERROR: Logfile of failure stored in:
> > > > /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
> > > > Log data follows:
> > > > | DEBUG: Executing shell function do_validate_branches
> > > > | NOTE: Setting branch meta to
> > > > 9e70b482d3773abf92c9c5850e134cbca1d5651f
> > > > | fatal: A branch named 'meta-orig' already exists.
> > > >
> > > >     this is building core-image-minimal for qemux86, and i'm assuming
> > > > this is not fedora rawhide related.
> > >
> > > You've got a borked tree sitting in work-shared. If you clean-all
> > > and start again, does it show up ?
> > >
> > > If it repeats, then it very well could be the version of git in
> > > rawhide that is causing the issue.
> >
> >    i started with a fresh build, got a validate_branches error, and
> > used "bb" to dump the log file for that step:
>
> There's definitely something wrong or a strange integration between
> the version of git and that tree.
>
> Without a place to poke at this, there's not much I can say about
> actually changing that behaviour.
>
> All my local builds are green, all the yocto release builds are green,
> etc, so this is somehow specific to your build and location
> environment.
>
> This is on a fully up to date master ?

... snip ...

  yup. and i realize that fedora rawhide isn't supported here, but if
there's something funky about fedora rawhide that's causing this, best
to figure it out earlier than later. i'll try more testing later, but
i've redone this test three times, same result each time.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: "fatal: A branch named 'meta-orig' already exists."

[Bruce Ashfield]

On Wed, Apr 1, 2015 at 7:24 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Wed, 1 Apr 2015, Bruce Ashfield wrote:
>
>> On 2015-04-01 3:07 AM, Robert P. J. Day wrote:
>> > On Tue, 31 Mar 2015, Bruce Ashfield wrote:
>> >
>> > > On 2015-03-31 6:26 PM, Robert P. J. Day wrote:
>> > > >
>> > > >     oh, what fresh hell is this?
>> > > >
>> > > > ... snip ...
>> > > > NOTE: Preparing RunQueue
>> > > > NOTE: Executing SetScene Tasks
>> > > > NOTE: Executing RunQueue Tasks
>> > > > ERROR: Function failed: do_validate_branches (log file is located at
>> > > > /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
>> > > > ERROR: Logfile of failure stored in:
>> > > > /home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
>> > > > Log data follows:
>> > > > | DEBUG: Executing shell function do_validate_branches
>> > > > | NOTE: Setting branch meta to
>> > > > 9e70b482d3773abf92c9c5850e134cbca1d5651f
>> > > > | fatal: A branch named 'meta-orig' already exists.
>> > > >
>> > > >     this is building core-image-minimal for qemux86, and i'm assuming
>> > > > this is not fedora rawhide related.
>> > >
>> > > You've got a borked tree sitting in work-shared. If you clean-all
>> > > and start again, does it show up ?
>> > >
>> > > If it repeats, then it very well could be the version of git in
>> > > rawhide that is causing the issue.
>> >
>> >    i started with a fresh build, got a validate_branches error, and
>> > used "bb" to dump the log file for that step:
>>
>> There's definitely something wrong or a strange integration between
>> the version of git and that tree.
>>
>> Without a place to poke at this, there's not much I can say about
>> actually changing that behaviour.
>>
>> All my local builds are green, all the yocto release builds are green,
>> etc, so this is somehow specific to your build and location
>> environment.
>>
>> This is on a fully up to date master ?
>
> ... snip ...
>
>   yup. and i realize that fedora rawhide isn't supported here, but if
> there's something funky about fedora rawhide that's causing this, best
> to figure it out earlier than later. i'll try more testing later, but
> i've redone this test three times, same result each time.


I completely agree .. better to sort this out sooner rather than later, I'm just
trying to narrow down on a  configuration that allows me to see the problem
and poke at the smouldering pile. If git is doing something different now, it
won't be hard to fix, but hands on, versus code inspection, is the real
trick here.

Bruce

>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
>
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: "fatal: A branch named 'meta-orig' already exists."

[Robert P. J. Day]

On Wed, 1 Apr 2015, Bruce Ashfield wrote:

... snip ...

> I completely agree .. better to sort this out sooner rather than
> later, I'm just trying to narrow down on a configuration that allows
> me to see the problem and poke at the smouldering pile. If git is
> doing something different now, it won't be hard to fix, but hands
> on, versus code inspection, is the real trick here.

  for a quick test, i started a new project on my fedora rawhide
system:

* latest checkout of poky
* core-image-minimal
* qemuarm (as opposed to initial qemux86, just to be different)

  the initial fetch worked fine (taking advantage of numerous tarballs
i've collected over the months):

  $ bitbake -c fetchall core-image-minimal

  then:

  $ bitbake linux-yocto

which quickly produces the error at the bottom of this note as
displayed by "bb". i'm baffled ... does the kernel tree have some
new, untracked garbage in it that is causing this?

  the native git is version 2.3.0.

rday

$ bb log linux-yocto validate_branches
DEBUG: Executing shell function do_validate_branches
NOTE: Setting branch meta to 9e70b482d3773abf92c9c5850e134cbca1d5651f
error: The following untracked working tree files would be removed by checkout:
	.gitignore
	.mailmap
	COPYING
	CREDITS
	Documentation/00-INDEX
	Documentation/ABI/README
	Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads
	Documentation/ABI/obsolete/sysfs-bus-usb
	Documentation/ABI/obsolete/sysfs-class-rfkill
	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus
	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus
	Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra
	Documentation/ABI/removed/devfs
	Documentation/ABI/removed/dv1394
	Documentation/ABI/removed/ip_queue
	Documentation/ABI/removed/net_dma
	Documentation/ABI/removed/o2cb
	Documentation/ABI/removed/raw1394
	Documentation/ABI/removed/video1394
	Documentation/ABI/stable/firewire-cdev
	Documentation/ABI/stable/o2cb
	Documentation/ABI/stable/syscalls
	Documentation/ABI/stable/sysfs-acpi-pmprofile
	Documentation/ABI/stable/sysfs-bus-firewire
	Documentation/ABI/stable/sysfs-bus-usb
	Documentation/ABI/stable/sysfs-bus-xen-backend
	Documentation/ABI/stable/sysfs-class-backlight
	Documentation/ABI/stable/sysfs-class-rfkill
	Documentation/ABI/stable/sysfs-class-tpm
	Documentation/ABI/stable/sysfs-class-ubi
	Documentation/ABI/stable/sysfs-class-udc
	Documentation/ABI/stable/sysfs-devices-node
	Documentation/ABI/stable/sysfs-devices-system-cpu
	Documentation/ABI/stable/sysfs-devices-system-xen_memory
	Documentation/ABI/stable/sysfs-driver-ib_srp
	Documentation/ABI/stable/sysfs-driver-qla2xxx
	Documentation/ABI/stable/sysfs-driver-usb-usbtmc
	Documentation/ABI/stable/sysfs-driver-w1_ds28e04
	Documentation/ABI/stable/sysfs-firmware-efi-vars
	Documentation/ABI/stable/sysfs-firmware-opal-dump
	Documentation/ABI/stable/sysfs-firmware-opal-elog
	Documentation/ABI/stable/sysfs-module
	Documentation/ABI/stable/sysfs-transport-srp
	Documentation/ABI/stable/thermal-notification
	Documentation/ABI/stable/vdso
	Documentation/ABI/testing/configfs-spear-pcie-gadget
	Documentation/ABI/testing/configfs-usb-gadget
	Documentation/ABI/testing/configfs-usb-gadget-acm
	Documentation/ABI/testing/configfs-usb-gadget-ecm
	Documentation/ABI/testing/configfs-usb-gadget-eem
	Documentation/ABI/testing/configfs-usb-gadget-ffs
	Documentation/ABI/testing/configfs-usb-gadget-hid
	Documentation/ABI/testing/configfs-usb-gadget-loopback
	Documentation/ABI/testing/configfs-usb-gadget-mass-storage
	Documentation/ABI/testing/configfs-usb-gadget-midi
	Documentation/ABI/testing/configfs-usb-gadget-ncm
	Documentation/ABI/testing/configfs-usb-gadget-obex
	Documentation/ABI/testing/configfs-usb-gadget-phonet
	Documentation/ABI/testing/configfs-usb-gadget-rndis
	Documentation/ABI/testing/configfs-usb-gadget-serial
	Documentation/ABI/testing/configfs-usb-gadget-sourcesink
	Documentation/ABI/testing/configfs-usb-gadget-subset
	Documentation/ABI/testing/configfs-usb-gadget-uac1
	Documentation/ABI/testing/configfs-usb-gadget-uac2
	Documentation/ABI/testing/debugfs-driver-genwqe
	Documentation/ABI/testing/debugfs-ec
	Documentation/ABI/testing/debugfs-ideapad
	Documentation/ABI/testing/debugfs-olpc
	Documentation/ABI/testing/debugfs-pfo-nx-crypto
	Documentation/ABI/testing/debugfs-pktcdvd
	Documentation/ABI/testing/dev-kmsg
	Documentation/ABI/testing/evm
	Documentation/ABI/testing/ima_policy
	Documentation/ABI/testing/procfs-diskstats
	Documentation/ABI/testing/pstore
	Documentation/ABI/testing/sysfs-ata
	Documentation/ABI/testing/sysfs-block
	Documentation/ABI/testing/sysfs-block-bcache
	Documentation/ABI/testing/sysfs-block-dm
	Documentation/ABI/testing/sysfs-block-rssd
	Documentation/ABI/testing/sysfs-block-zram
	Documentation/ABI/testing/sysfs-bus-acpi
	Documentation/ABI/testing/sysfs-bus-bcma
	Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10
	Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x
	Documentation/ABI/testing/sysfs-bus-coresight-devices-funnel
	Documentation/ABI/testing/sysfs-bus-coresight-devices-tmc
	Documentation/ABI/testing/sysfs-bus-css
	Documentation/ABI/testing/sysfs-bus-event_source-devices-events
	Documentation/ABI/testing/sysfs-bus-event_source-devices-form
Aborting
ERROR: Could not checkout meta branch from known hash 9e70b482d3773abf92c9c5850e134cbca1d5651f
WARNING: /home/rpjday/oe/builds/qemuarm/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_473e2f3788-r0/temp/run.do_validate_branches.11303:1 exit 1 from
  exit 1
ERROR: Function failed: do_validate_branches (log file is located at /home/rpjday/oe/builds/qemuarm/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_473e2f3788-r0/temp/log.do_validate_branches.11303)
$

Re: "fatal: A branch named 'meta-orig' already exists."

[Robert P. J. Day]

On Wed, 1 Apr 2015, Bruce Ashfield wrote:

... again, snip ...

> I completely agree .. better to sort this out sooner rather than
> later, I'm just trying to narrow down on a configuration that allows
> me to see the problem and poke at the smouldering pile. If git is
> doing something different now, it won't be hard to fix, but hands
> on, versus code inspection, is the real trick here.

  ok, now i'm confused about where i'm getting my kernel source from.
with a fresh build for qemux86 and deliberately not using any of my
local mirror content, i did:

  $ bitbake -c fetchall linux-yocto

assuming the fetch would take a while due to, you know, git checkout.

  the first puzzler is that my downloads directory very quickly
contained (among other things):

-rw-rw-r--. 1 rpjday rpjday 81688872 Feb  8 22:20 linux-3.19.tar.xz

should i have expected that? why do i suddenly have what looks like a
stock linux-3.19 tarball when git should be used for this?

  and here's the salient bit from the fetch log file, clearly showing
a sizable tarball being downloaded from downloads.yoctoproject.org:

///// START /////
DEBUG: For url
git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=standard/common-pc,meta;name=machine,meta
returning
http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.19.git.tar.gz
... cut ...
DEBUG: Fetching
http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.19.git.tar.gz
using command '/usr/bin/env wget -t 2 -T 30 -nv --passive-ftp
--no-check-certificate -P /home/rpjday/oe/builds/qemux86/downloads
'http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.19.git.tar.gz''
DEBUG: Fetcher accessed the network with the command /usr/bin/env wget
-t 2 -T 30 -nv --passive-ftp --no-check-certificate -P
/home/rpjday/oe/builds/qemux86/downloads
'http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.19.git.tar.gz'
/// END ///

  that tarball is 927M as you can see here:

http://downloads.yoctoproject.org/mirror/sources/

dated mar 24, so that's fairly new and makes me wonder if there's
something weird/broken about it. waiting for wget to finish ... ok,
done. now try to cuild:

  $ bitbake linux-yocto

hmmmmmmm ... and it's already blown by the validate_branches task, so
suddenly, no problem. weird.

  it is entirely possible that, because i was using a local mirror
loaded with tarballs, an earlier kernel tarball was being picked up
and wasn't compatible with later content. after dropping any reference
to my local mirror, validate_branches appears to work.

  still curious as to the presence of the linux-3.19 xz tarball in my
downloads directory.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================