Migrating to the 2011 Tree

drobbins · 2011-08-06 19:48:56

Hi All,

In a few days, I am going to stop updating the older portage trees on GitHub that many users are still using for emerge --sync, so users should switch to the new "portage-mini-2011" tree. You should also do this if you are still using the portage-mini-2010 tree. It's important to switch to our new 2011 tree so that "emerge --sync" will continue to work when these older trees are removed.

To see what tree you are currently pulling from when running emerge --sync, type this:

# cat /usr/portage/.git/config

Then look at the "url" setting under the [remote "origin"] section.

If it ends with "portage.git", you are using the big non-mini-manifest tree that will be retired in a few days. So you should switch to the 2011 tree using the instructions below.

If it ends with "portage-mini-2010.git", you are using the mini-manifest 2010 tree - the 2011 tree is more compact and 2010 will be retired soon too, so you should switch to 2011 using the instructions below..

If it ends with "portage-mini-2011.git", you are already using the latest 2011 tree and you don't need to perform any additional steps.

Note: due to how git works, switching to the 2011 tree involves backing up your old tree and then getting a fresh new copy of the 2011 tree. It's not enough to just tweak a configuration file, due to the way git works. Instructions on how to do it can be found below:

HOW TO UPDATE TO THE 2011 TREE
=============================

If you are using "portage.git" or "portage-mini-2010.git", here's how to update to the latest 2011 tree:

1. First, emerge --sync and emerge -u portage to ensure you have the latest version of Portage running.
2. Then, back up your old Portage tree:

# cd /usr
# mv portage portage.old

3. Next, edit /etc/make.conf and remove any hard-coded SYNC= variable from the file. The latest Portage has the correct default. You probably have a SYNC= line even if you didn't add it yourself. You need to ensure it's removed.

4. Now, grab the new 2011 tree by running "emerge --sync".
5. "cat /usr/portage/.git/config" and ensure that the "url" line ends in "portage-mini-2011.git" - this confirms you now have the latest 2011 tree.
6. Make sure your new tree is working fine, emerge a few things, etc.
7. Once you have confirmed that your new Portage tree is working, you can now "rm -rf /usr/portage.old" to save some disk space.

You are now fully migrated to the new 2011 mini-manifest tree This tree will be active through mid-2012.

Best Regards,

Daniel

d2_racing · 2011-08-06 21:12:54

At 4.1, after running the emerge --sync, you need to run this :

# mv portage.sync portage

Then you will be able to go to point 5.

Last edited by d2_racing (2011-08-06 21:18:05)

drobbins · 2011-08-06 23:12:36

d2, if you need to do that then there is a bug in portage or another error. Portage should be able to sync a tree from scratch.

just1602 · 2011-08-06 23:14:27

I didn't need to do that, I think portage move portage.sync in portage automaticly. After, we juste have to rm -r portage.sync.

@++

Justin : )

rh1 · 2011-08-07 01:45:38

The "current" branch used by the portage-9999 ebuild still has SYNC pointing at the 2010 mini-tree.

d2_racing · 2011-08-07 14:32:11

I'm gonna retry today. More info soon

d2_racing · 2011-08-07 19:22:11

Ok, I checked and now it's working.

I don't know why I had to run mv then...

aramis_qc · 2011-08-08 00:35:16

Do we still need a SYNC variable in /etc/make.conf after portage had been migrated to 2011 ?

rh1 · 2011-08-08 01:52:32

Do we still need a SYNC variable in /etc/make.conf after portage had been migrated to 2011 ?

No, the default for SYNC is set to use the 2011 mini-tree

pascalbrax · 2011-08-10 09:39:09

worked flawless!

what's new?

golodhrim · 2011-08-10 12:06:18

nothing only cleaner and smaller

zdavatz · 2011-08-31 13:06:08

I done as advised and now I get in the 5 steps and now I get:

/usr> sudo emerge --sync
Portage repository is currently empty.
>>> Using /usr/portage.sync/portage as temporary clone directory...
>>> Starting initial git clone with git://github.com/funtoo/portage-mini-2010.git...
Cloning into portage...
fatal: remote error:
Could not find Repository funtoo/portage-mini-2010

Any hints?

Best
Zeno

zdavatz · 2011-08-31 13:30:26

This did not work either.

1. /usr/portage/.git> sudo cp -r ../../portage.old/.git/* .
2. cd ../
3. sudo git stash
4. sudo git reset --hard
5. sudo emerge --sync

I am now trying to do:
1. cd /usr
2. sudo git clone git://github.com/funtoo/portage-mini-2011.git
3. mv portage-mini-2011 portage
4. mv portage.sync portage.sync.old
5. emerge --sync

This seems to work.

Best
Zeno

Last edited by zdavatz (2011-08-31 13:35:59)

zdavatz · 2011-08-31 14:02:33

After upgrading one of my servers I am now stuck with upgrading portage (note: I could not emerge portage before the upgrade to portage-mini-2011.git because the emerge --sync failed and it tells me I am on the latest version: 2.2_rc67-r2).

So I followed your steps, upgraded to portage-mini-2011.git and now I am stuck with upgrading portage with the following error:

>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: '/usr/portage/sys-apps/portage/portage-2.2.2.ebuild'
!!! Manifest is empty: '/usr/portage/sys-devel/automake-wrapper/Manifest'
!!! Manifest is empty: '/usr/portage/virtual/yacc/Manifest'
!!! A file is not listed in the Manifest: '/usr/portage/dev-lang/perl/perl-5.10.0-r1.ebuild'
!!! A file is not listed in the Manifest: '/usr/portage/sys-devel/automake/automake-1.10.3.ebuild'
!!! A file is not listed in the Manifest: '/usr/portage/sys-devel/binutils/binutils-2.16.1-r3.ebuild'
!!! A file is not listed in the Manifest: '/usr/portage/app-misc/realpath/realpath-1.15-r1.ebuild'
!!! A file is not listed in the Manifest: '/usr/portage/app-admin/perl-cleaner/perl-cleaner-2.10.ebuild'
!!! A file is not listed in the Manifest: '/usr/portage/sys-devel/libtool/libtool-1.3.5.ebuild'

A bit of a catch 22 I would say.

Any hints?

Best
Zeno

rh1 · 2011-08-31 15:22:01

Try

FEATURES="mini-manifest" emerge -1 portage

I don't remember when mini-manifest was introduced but if that doesn't work post back and we can help you fix it. Basically you'll need to clone the git repo for portage source code and manually move it in place of your current portage.

zdavatz · 2011-09-01 08:46:55

This worked very smooth, thank you!

I am having a second issue on my local machine. emerge --sync worked but now I want to upgrade portage and this results in:

>>> Downloading 'https://www.github.com/funtoo/portage-f … 1-06-26-r6'
--2011-09-01 10:45:13-- https://www.github.com/funtoo/portage-f … 1-06-26-r6
Resolving www.github.com... 207.97.227.243
Connecting to www.github.com|207.97.227.243|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/funtoo/portage-funto … 1-06-26-r6 [following]
--2011-09-01 10:45:14-- https://github.com/funtoo/portage-funto … 1-06-26-r6
Resolving github.com... 207.97.227.239
Connecting to github.com|207.97.227.239|:443... connected.
ERROR: cannot verify github.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV CA-1':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
!!! Couldn't download 'portage-funtoo-merged-2011-06-26-r6.tar.gz'. Aborting.
* Fetch failed for 'sys-apps/portage-2.3-r4', Log file:
* '/var/tmp/portage/sys-apps/portage-2.3-r4/temp/build.log'

I checked, there is not such file.

I searched the internet and I do have the latest openssl and wget installed.

Any more hints?

Best
Zeno

angry_vincent · 2011-09-01 09:57:54

You need to recompile openssl, update the certificates, recompile wget and try again

zdavatz · 2011-09-07 15:37:01

Thanks for your help. I did both (openssl and wget) - how do I update the certificates?

drobbins · 2011-09-07 21:57:14

once you recompile wget and openssl, it should take care of the certificate issue so you shouldn't need to do anything with certificates. If that's not the case, let us know.

zdavatz · 2011-09-19 06:57:26

Dear Daniel

This is not the case. I done both and I still get the same error:

>>> Emerging (1 of 1) sys-apps/portage-2.3-r7
>>> Downloading 'http://distfiles.gentoo.org/distfiles/p … a55.tar.gz'
--2011-09-19 08:54:39-- http://distfiles.gentoo.org/distfiles/p … a55.tar.gz
Resolving distfiles.gentoo.org... 140.211.166.134, 156.56.247.195, 216.165.129.135, ...
Connecting to distfiles.gentoo.org|140.211.166.134|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2011-09-19 08:54:40 ERROR 404: Not Found.

>>> Downloading 'https://www.github.com/funtoo/portage-f … .2_alpha55'
--2011-09-19 08:54:40-- https://www.github.com/funtoo/portage-f … .2_alpha55
Resolving www.github.com... 207.97.227.243
Connecting to www.github.com|207.97.227.243|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/funtoo/portage-funto … .2_alpha55 [following]
--2011-09-19 08:54:40-- https://github.com/funtoo/portage-funto … .2_alpha55
Resolving github.com... 207.97.227.239
Connecting to github.com|207.97.227.239|:443... connected.
ERROR: cannot verify github.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance EV CA-1':
Unable to locally verify the issuer's authority.
To connect to github.com insecurely, use `--no-check-certificate'.
!!! Couldn't download 'portage-funtoo-2.3-stable-staging-merged-2.2_alpha55.tar.gz'. Aborting.
* Fetch failed for 'sys-apps/portage-2.3-r7', Log file:
* '/var/tmp/portage/sys-apps/portage-2.3-r7/temp/build.log'

* net-misc/wget
Latest version available: 1.12-r3
Latest version installed: 1.12-r3

* dev-libs/openssl
Latest version available: 1.0.0e
Latest version installed: 1.0.0e

Best
Zeno

zdavatz · 2011-09-27 07:58:35

Any further hints why this still does not work?

angry_vincent · 2011-09-27 10:04:24

This is weird, looks like your box is screwed somehow, there're no more reports. Anyway I uploaded the tarabll to osuosl, you can try to fetch it manually and update portage.
http://ftp.osuosl.org/pub/funtoo/distfi … a55.tar.gz

jonathan183 · 2011-09-27 21:52:13

Recently updated ... ended up manually modifying /usr/portage/.git/config set the url line to

        url = git://github.com/funtoo/portage-mini-2011.git

to get things to work ... it had been a while since I had done updates
running emerge -avuDN system && emerge -avuDN world

zdavatz · 2011-09-28 06:40:06

@angry_vincent

Thanks! I downloaded that tarball and I placed it to /usr/portage/distfiles,

And it worked! Thank you!

@jonathan183

My git-config already is:

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git://github.com/funtoo/portage-mini-2011.git
[branch "funtoo.org"]
remote = origin
merge = refs/heads/funtoo.org

Best
Zeno

jonathan183 · 2011-09-29 21:01:53

The combination of commenting out SYNC= in /etc/make.conf, modifying /usr/portage/.git/config, and an emerge --sync was sufficient to get me going ... anyway glad you got things sorted

#1 2011-08-06 19:48:56

Migrating to the 2011 Tree

#2 2011-08-06 21:12:54

Re: Migrating to the 2011 Tree

#3 2011-08-06 23:12:36

Re: Migrating to the 2011 Tree

#4 2011-08-06 23:14:27

Re: Migrating to the 2011 Tree

#5 2011-08-07 01:45:38

Re: Migrating to the 2011 Tree

#6 2011-08-07 14:32:11

Re: Migrating to the 2011 Tree

#7 2011-08-07 19:22:11

Re: Migrating to the 2011 Tree

#8 2011-08-08 00:35:16

Re: Migrating to the 2011 Tree

#9 2011-08-08 01:52:32

Re: Migrating to the 2011 Tree

#10 2011-08-10 09:39:09

Re: Migrating to the 2011 Tree

#11 2011-08-10 12:06:18

Re: Migrating to the 2011 Tree

#12 2011-08-31 13:06:08

Re: Migrating to the 2011 Tree

#13 2011-08-31 13:30:26

Re: Migrating to the 2011 Tree

#14 2011-08-31 14:02:33

Re: Migrating to the 2011 Tree

#15 2011-08-31 15:22:01

Re: Migrating to the 2011 Tree

#16 2011-09-01 08:46:55

Re: Migrating to the 2011 Tree

#17 2011-09-01 09:57:54

Re: Migrating to the 2011 Tree

#18 2011-09-07 15:37:01

Re: Migrating to the 2011 Tree

#19 2011-09-07 21:57:14

Re: Migrating to the 2011 Tree

#20 2011-09-19 06:57:26

Re: Migrating to the 2011 Tree

#21 2011-09-27 07:58:35

Re: Migrating to the 2011 Tree

#22 2011-09-27 10:04:24

Re: Migrating to the 2011 Tree

#23 2011-09-27 21:52:13

Re: Migrating to the 2011 Tree

#24 2011-09-28 06:40:06

Re: Migrating to the 2011 Tree

#25 2011-09-29 21:01:53

Re: Migrating to the 2011 Tree

Board footer