Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[amd64] from stable to unstable
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
newbie64
n00b
n00b


Joined: 27 Mar 2010
Posts: 5

PostPosted: Sat Mar 27, 2010 1:12 pm    Post subject: [amd64] from stable to unstable Reply with quote

Good afternoon. I'm sorry for my bad english but I'll try to describe my problem. I installed gentoo amd64 and everything works fine, but I need to rebuild my world with ~amd64 (unstable branch). Every time I attempted to do this I had problems with compilation and dependencies. I even had a huge trouble with mounting my partitions because of some problems with fstab. Would you please advice me how to emerge -uDN world more safely or just give me some useful links to read about this problem. Google didn't help me... Thanks a lot.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6929
Location: Austria

PostPosted: Sat Mar 27, 2010 1:26 pm    Post subject: Reply with quote

Well, you can't really avoid breakage and blocks to happen. Isn't arch still on baselayout-1 for example? Just make sure that you won't miss any important output from portage during the emerge, there's something you can do about it though.

Why do you have to move to ~arch anyway?

1.) Make sure there aren't any careless entries (ones without version string) in /etc/package.unmask/ that would unmask even more 'evil' package versions that had been otherwise still keyworded until now.
2.) Check for gcc and glibc updates - they will occur. Do them first with 'emerge -1v gcc glibc'. Probably the same for boost and boost-build
3.) emerge -uva system //don't miss any elog messages at the end of emerge, act as instructed
4.) emerge -uvaDN system //don't miss any elog messages at the end of emerge, act as instructed
5.) emerge -uvaD world //don't miss any elog messages at the end of emerge, act as instructed
6.) emerge -uvaDN world //don't miss any elog messages at the end of emerge, act as instructed
7.) Make sure your system is consistent: revdep-rebuild -- -va //Might want to do that even earlier, e.g. between any of the above major emerge steps.

At any point, blocks could appear because an installed version of a package may require older versions of dependencies. Several solutions may be valid there: temporarily uninstalling the package in question, or bringing the package forward with a manual emerge, then resume your actual emerge update.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
newbie64
n00b
n00b


Joined: 27 Mar 2010
Posts: 5

PostPosted: Sat Mar 27, 2010 1:37 pm    Post subject: Reply with quote

Well, for example I want to have a last version of GNOME. Emerging it from unstable branch there were many dependencies that needed updating too. GNOME is just one example above many packages that's versions are rather old in stable branch. I thought it'll be better to move to ~arch then resolving every local problem. My friends also keeps unstable systems on their desktops, but they haven't got so many problems with ~x86 as I can see. Maybe I'm wrong but I really hope I'll got it. Thanks for advice, I'll try to follow your manual. :)
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Sat Mar 27, 2010 2:22 pm    Post subject: Reply with quote

I would not use ~arch or even arch. I just manage my masking and unmasking. Yes it does take longer to do that but in my opinion it works best this way.

BTW did you know that keywords can be a folder and not just a file.

I mean I have folders
/etc/portage/package.keywords/
/etc/portage/package.mask/
/etc/portage/package.unmask/
/etc/portage/package.use/

and inside that I put keyword files or link to files in my overlay or other overlays.

Code:
jmd0 package.keywords # ls -al
total 76
drwxr-xr-x  2 root root 4096 Mar 21 21:29 .
drwxr-xr-x 13 root root 4096 Mar 13 23:41 ..
lrwxrwxrwx  1 root root   57 Dec 13  2008 amd64 -> ../layman/jmd-gentoo/Other/portage/package.keywords/amd64
-rw-r--r--  1 root root 3684 Mar 21 03:10 common
lrwxrwxrwx  1 root root   62 Apr 10  2009 gnome-2.26 -> ../layman/jmd-gentoo/Other/portage/package.keywords/gnome-2.26
lrwxrwxrwx  1 root root   62 Sep 29 22:37 gnome-2.28 -> ../layman/jmd-gentoo/Other/portage/package.keywords/gnome-2.28
-rw-r--r--  1 root root   26 Feb  4  2009 kde
lrwxrwxrwx  1 root root   69 May 13  2009 kde-4.3.keywords -> ../layman/kde-testing/Documentation/package.keywords/kde-4.3.keywords
lrwxrwxrwx  1 root root   74 May 13  2009 kde-4.3.keywords.extra -> ../layman/jmd-gentoo/Other/portage/package.keywords/kde-4.3.keywords.extra
lrwxrwxrwx  1 root root   69 Feb  9 18:17 kde-4.4.keywords -> ../layman/kde-testing/Documentation/package.keywords/kde-4.4.keywords
-rw-r--r--  1 root root   21 Feb  9 18:21 kde-4.4.keywords-extra
-rw-r--r--  1 root root  245 Aug 14  2009 koffice-2
-rw-r--r--  1 root root 8156 Mar 27 00:29 local
lrwxrwxrwx  1 root root   58 Dec 13  2008 mythtv -> ../layman/jmd-gentoo/Other/portage/package.keywords/mythtv
-rw-r--r--  1 root root  665 Dec  5 19:27 mythtv-svn
-rw-r--r--  1 root root    0 Jun 21  2009 out.txt
lrwxrwxrwx  1 root root   64 Dec 13  2008 postgres-8.2 -> ../layman/jmd-gentoo/Other/portage/package.keywords/postgres-8.2
-rw-r--r--  1 root root  475 Mar 13 23:42 qt-4.6
-rw-r--r--  1 root root   70 Nov 24 00:30 samba-3.4
-rw-r--r--  1 root root  165 Mar  1 08:55 samba-3.5
-rw-r--r--  1 root root 2400 Mar 16 20:46 x11
lrwxrwxrwx  1 root root   59 May 13  2009 x11-1.6 -> ../layman/jmd-gentoo/Other/portage/package.keywords/x11-1.6


Hmm, looks like I need to do some spring cleaning..

Here is my gnome-2.28 keywords file from my overlay

http://github.com/drescherjm/jmdgentoooverlay/raw/master/Other/portage/package.keywords/gnome-2.28

If you look at this file you will notice something that you think is odd. I have no ~x86 or ~amd64 at all. This is not needed and without it I can use the same file for both ~x86 and ~amd64 and also for /etc/portage/package.unmask/ if needed. I have done this for years..
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
newbie64
n00b
n00b


Joined: 27 Mar 2010
Posts: 5

PostPosted: Sat Mar 27, 2010 4:32 pm    Post subject: Reply with quote

Such a nice expirience. Thx a lot, I'll try to.
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Sat Mar 27, 2010 7:47 pm    Post subject: Reply with quote

One other thing you can do to save time is to use autounmask.

http://gentoo-portage.com/app-portage/autounmask

I used to use that a lot but now I prefer to hand edit individual mask files or just echo additions via the shell.
_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
newbie64
n00b
n00b


Joined: 27 Mar 2010
Posts: 5

PostPosted: Sat Mar 27, 2010 8:02 pm    Post subject: Reply with quote

And BTW I've got one more question. Since my last world rebuilding I had some troubles with fstab. Ectually I didn't read portage output and that was my fault. Am I right that if some initialization params's of partitions will change there will be no problems if I'll set them as UUIDs in my fstab? (Im talking about situation if hda, for example, will become hda or even sda1 will be changed to sdb).
Back to top
View user's profile Send private message
drescherjm
Advocate
Advocate


Joined: 05 Jun 2004
Posts: 2779
Location: Pittsburgh, PA, USA

PostPosted: Sat Mar 27, 2010 8:07 pm    Post subject: Reply with quote

I use UUIDS. They work well.

/etc/fstab
Code:
#The following mounts using UUIDs instead of drives. This way I can move drives and not worry about changing the mounts
UUID=9138f62b-97e2-4fb3-bdad-7120d2aa3e77       /boot           ext2            noauto,noatime  1 2
UUID=d317541c-0f05-426d-9dc6-99ea8e872680       /               auto            noatime,nodiratime,commit=60,barrier=1          0 1
UUID=a77299ac-3f74-424a-af7d-f05e93f52e98       none            swap            sw              0 0



/boot/grub
Code:

default=0
timeout=20
splashimage=/boot/grub/splash.xpm.gz

title=Gentoo Linux (2.6.27.45-sound-seq-dirty)
  root (hd0,0)
  kernel /kernel-genkernel-x86_64-2.6.27.45-sound-seq-dirty root=/dev/ram0 init=/linuxrc real_root=UUID=d317541c-0f05-426d-9dc6-99ea8e872680 console=tty0 real_rootflags=data=writeback
#console=ttyS0,115200
  initrd /initramfs-genkernel-x86_64-2.6.27.45-sound-seq-dirty


You can get the UUID easily with the blkid command

Code:
jmd0 ~ # blkid
/dev/sdc1: UUID="16a41f81-32de-4112-9f6a-f03df75a9aff" TYPE="ext2"
/dev/sdd1: UUID="ctdUII-EonR-MtSz-gnWi-d8bM-PD2Q-SH9a15" TYPE="LVM2_member"
/dev/sde1: UUID="cOSFB0-pn72-GcZe-DzE2-0GYv-25Jh-gqMtj5" TYPE="LVM2_member"
/dev/mapper/vg_temp-emulation: UUID="e743dd25-154d-4510-adc2-9b6df78cd78b" TYPE="xfs"
/dev/mapper/vg_temp-mythdata1: UUID="0c774cb9-9ec5-415c-81ea-4c0321b89c8f" TYPE="xfs"
/dev/mapper/vg_temp-other_data: UUID="b411363a-ec9f-4080-ad07-bd5540a5e61e" TYPE="xfs"
/dev/mapper/vg_temp-music: UUID="4faf7c9e-090f-40eb-b656-03ff3439df4f" TYPE="ext4dev"
/dev/mapper/vg2-home: UUID="d9ee094a-42fa-4cfc-8ed2-d1011cd07b28" TYPE="xfs"
/dev/mapper/vg2-virtulization: UUID="f9fd666a-0ab9-43a1-b823-5bca2791938a" TYPE="xfs"
/dev/mapper/vg2-temp_data: UUID="e83ac35b-26b9-4f58-8302-d4b3defe15f5" TYPE="ext4dev"
/dev/mapper/vg2-distfiles: UUID="f03c9f50-6413-4def-abfd-52bcdefd2ef2" TYPE="ext4dev"
/dev/mapper/vg2-emulation: UUID="a1d42bf9-0895-4d5b-9d08-9f5b48898122" TYPE="ext4dev"
/dev/mapper/vg2-swap: UUID="20906209-8c45-483a-9cf5-f9f918ab167d" TYPE="swap"
/dev/mapper/vg_2t0-mythdata0: UUID="82730fc8-9122-4ddd-96f8-e452a56fb5e6" TYPE="ext4dev"
/dev/mapper/vg_2t0-mythdata1: UUID="b2e6c8da-f379-41a1-b1c1-936393c983cb" TYPE="ext4dev"
/dev/mapper/vg_2t0-mythdata2: UUID="abb6808f-4ffa-495c-90b5-ec40902e974f" TYPE="ext4dev"
/dev/mapper/vg1-projects: UUID="3814ef82-7414-427a-b2dc-0f316155ca2a" TYPE="xfs"
/dev/mapper/vg1-portage: UUID="2191ad33-9884-4864-93e2-0c17fcbd4354" TYPE="ext4dev"
/dev/mapper/vg1-emulation: UUID="f4fcea4d-a55a-4161-82e7-70ff40b24e5a" TYPE="ext4dev"
/dev/mapper/vg_2t0-downloads: UUID="dc6109e9-6e47-4613-b36c-aab233840bba" TYPE="ext4dev"
/dev/mapper/vg--ssd-portage: UUID="3cf1f690-fd15-4455-862f-9d1352029d50" TYPE="ext4dev"
/dev/mapper/vg--ssd-temp: UUID="9e89e551-f3ea-4335-a90e-d1f1e452afd8" TYPE="ext4dev"
/dev/sdc2: UUID="bd8ae50b-9f50-47cb-b594-272bff66ed34" TYPE="swap"
/dev/sdc5: UUID="889fc24d-b214-42a5-b445-1a213a4e43cc" TYPE="xfs"
/dev/sdc6: UUID="WDh4BK-aSea-0pcY-97C2-Jzvh-7Q3K-vExD9J" TYPE="LVM2_member"
/dev/sdf1: UUID="9a80ad32-a098-4771-ae7f-849b6efc583f" TYPE="ext4dev"
/dev/sda1: UUID="9138f62b-97e2-4fb3-bdad-7120d2aa3e77" TYPE="ext2"
/dev/sda2: UUID="a77299ac-3f74-424a-af7d-f05e93f52e98" TYPE="swap"
/dev/sda5: UUID="d317541c-0f05-426d-9dc6-99ea8e872680" TYPE="ext4dev"
/dev/sda6: UUID="Uppmcj-1MJQ-1tZ2-jk78-90qr-RZBX-1WOV30" TYPE="LVM2_member"
/dev/sdb1: UUID="cq87cX-EHsH-TsLe-nift-Tsqw-hIiv-lxsZqi" TYPE="LVM2_member"

_________________
John

My gentoo overlay
Instructons for overlay
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum