View Full Version : Please do not upgrade to breezy *yet*
shimon
April 18th, 2005, 12:34 AM
There are many bugs which will leave your system not usable and there is nothing new to upgrade to besides gaim as the merge with sid hasn't started yet....
But if you are going to ingore all warnings install apt-listbugs so you can see the bugs in the package BEFORE installing it.... Also there have been many famost bugs in sid that might happen to breezy.... Like imcomplete rm scripts ones that format the whole hardrive....
YOU HAVE BEEN WARNED!
MicroChris
April 18th, 2005, 12:43 AM
Im guessing theres no way to "downgrade" to Hoary after the Breezy install? I did the stupid thing of using Breezy as my main distro, which I definitely don't want to do..
Switching the repos back to Hoary wouldnt be safe Im guessing? :?
shimon
April 18th, 2005, 01:36 AM
If you don't know about apt-pinning you for sure shouldn't be using breezy
yusufk
April 18th, 2005, 04:15 AM
Ok, so we've ignored all warnings before this one and dont know about apt-pinning, now what?
Can u tell us about downgrading to Hoary or apt-pinning, or is it too late for either.
p.s. I last updated 2 days ago, everythings cool so far?
shimon
April 18th, 2005, 06:29 AM
Gooooooooooooooooooooooooooooooooooooooooooooooooo ogle it
az
April 18th, 2005, 07:26 AM
The point really is that Breezy is for development. It will become stable in five and a half-months. Many things will break and then be fixed again by then. If you do not want a system that breaks, stick with Hoary.
Package management goes to great lengths to not break your system by updgrading. Dependancies can be handled incrementally, but not the other way around. So, no, there is no easy way to downgrade.
Change your sources.list back to Hoary if nothing is broken, and keep on going. You should still get your security updates....
Seth
April 18th, 2005, 09:38 AM
Most of us are using Breezy because we *want* to test new stuff. I don't care if things break; I know how to fix them. Perhaps you should clarify your admonition a little bit. Breezy needs testing even now.
(And I like having the new version of Synergy, so Gaim isn't the "only thing changed". I've gotten over 100 updates in Breezy. Some are pretty significant.)
piccolotux
April 18th, 2005, 10:02 AM
Most of us are using Breezy because we *want* to test new stuff. I don't care if things break; I know how to fix them. Perhaps you should clarify your admonition a little bit. Breezy needs testing even now.
(And I like having the new version of Synergy, so Gaim isn't the "only thing changed". I've gotten over 100 updates in Breezy. Some are pretty significant.)
So you did upgrade libc6 to 2.3.5... major issues?
Thanks
Steven Myers
April 18th, 2005, 10:05 AM
Most of us are using Breezy because we *want* to test new stuff. I don't care if things break; I know how to fix them. Perhaps you should clarify your admonition a little bit. Breezy needs testing even now.
(And I like having the new version of Synergy, so Gaim isn't the "only thing changed". I've gotten over 100 updates in Breezy. Some are pretty significant.)
I second this post because I have had SOME keyboard issues, applications opening out of knowhere, and apps not working at all, but these have been fixed by myself, and also bug reports have been sent, but to be honest, it's really the user that makes breezy the most of what it is, and yes if you don't know about apt-pinning, do go back to hoary and get security updates for now until breezy is clean
Also do google as well, I found some useful information about the apt-pinning for myself and the other devs I chat with and they find it useful as well, so there is really a good side to working with breezy's repo's/dependencies.
Also just a quick note to those that might find firewalls useful, and of course this is a no brainer to all dev's but for the newbies, please do not download or install "kmyfirewall"
IF you do, you will not be able to login due to /home/usr/.ICEauthority dir is not being read.
If you do come accross this error the following command does work.
chmod 777 /home/yourname/.ICEauthority
rm -Rf /home/yourname/.ICEauthority
P.S I did this mistake so I don't think anyone else will want to follow that. ;)
hard_i
April 18th, 2005, 10:07 AM
So you did upgrade libc6 to 2.3.5... major issues?
Thanks
i've upgraded to libc6 2.3.5 , havent noticed any issues .. yet :smile:
Seth
April 18th, 2005, 10:55 AM
i've upgraded to libc6 2.3.5 , havent noticed any issues .. yet :smile:
Me neither ;-)
Whiffle
April 18th, 2005, 10:57 AM
Im using breezy...hasn't given me any trouble...yet....
dabeej
April 18th, 2005, 11:01 AM
I personally was going to upgrade soon because of mono, maybe I will try to build those packages in hoary. In fact, I am now.
yusufk
April 18th, 2005, 11:23 AM
I dont know about apt-pinning, but I will be goooooogling it soon hopefully, just hoped that there'd be a quick and easy reply. I myself am a developer and although Im quite new to the Linux world, Im a keen learner and believe that the best way to learn is when u have to, i.e. when things break. So, I'll be sticking with Breezy, like I did with Hoary when it was being developed.
Anyway, I think that its important to have a users like me so that things get tested and reported, even though my development input is non-existent (for now).
p,s, if u dont hear from me in a while, u know y.
Glanz
April 18th, 2005, 11:54 AM
You may apt pin via synaptic via the 'package' drop-down menu then choosing 'lock-version', or you can create an apt preferences file with pinning choices in it. You may also choose which version to prioritize when updating via synaptic 'preferences.' Check this link for starters::
http://jaqque.sbih.org/kplug/apt-pinning.html
and
http://www.argon.org/~roderick/apt-pinning.html (http://www.argon.org/%7Eroderick/apt-pinning.html)
Reb
April 18th, 2005, 04:03 PM
The only issue I've had with Breezy is that aspell's not working in programs (it is working, manually).
JamesLast
April 19th, 2005, 08:53 AM
So you did upgrade libc6 to 2.3.5... major issues?
Thanks
No issues during normal running of software, however compilation of xorg-cvs now fails, it boils out at xc/programms/Xserver/fb with the following errors:
gcc -c -O2 -march=k8 -fno-strength-reduce -fno-strict-aliasing -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -fPIC -I../../../programs/Xserver/fb -I../../../programs/Xserver/mi -I../../../programs/Xserver/include -I../../../exports/include/X11 -I../../../include/fonts -I../../../programs/Xserver/hw/xfree86/common -I../../../programs/Xserver/render -I../../../include/extensions -I../../../programs/Xserver/Xext -I../../.. -I../../../exports/include -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DRENDER -DRANDR -DXFIXES -DDAMAGE -DCOMPOSITE -DXEVIE -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DDLOPEN_HACK -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DXORG_VERSION_CURRENT="(((6) * 10000000) + ((8) * 100000) + ((99) * 1000) + 3)" -D_XSERVER64 -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO -DIN_MODULE -DXFree86Module -mmmx -Winline --param inline-unit-growth=10000 --param large-function-growth=10000 -DUSE_MMX -msse -DUSE_SSE fbmmx.c
In file included from /usr/include/stdlib.h:433,
from /usr/lib/gcc/x86_64-linux/4.0.0/include/mm_malloc.h:30,
from /usr/lib/gcc/x86_64-linux/4.0.0/include/xmmintrin.h:41,
from fbmmx.c:37:
/usr/include/sys/types.h:151: error: duplicate 'unsigned'
In file included from /usr/lib/gcc/x86_64-linux/4.0.0/include/mm_malloc.h:30,
from /usr/lib/gcc/x86_64-linux/4.0.0/include/xmmintrin.h:41,
from fbmmx.c:37:
/usr/include/stdlib.h:622:24: error: macro "abort" passed 1 arguments, but takes just 0
In file included from /usr/lib/gcc/x86_64-linux/4.0.0/include/xmmintrin.h:1211,
from fbmmx.c:37:
/usr/lib/gcc/x86_64-linux/4.0.0/include/emmintrin.h:1390: error: syntax error before '__m128'
/usr/lib/gcc/x86_64-linux/4.0.0/include/emmintrin.h:1396: error: syntax error before '__m128i'
/usr/lib/gcc/x86_64-linux/4.0.0/include/emmintrin.h:1402: error: syntax error before '__m128d'
/usr/lib/gcc/x86_64-linux/4.0.0/include/emmintrin.h:1408: error: syntax error before '__m128i'
/usr/lib/gcc/x86_64-linux/4.0.0/include/emmintrin.h:1414: error: syntax error before '__m128'
/usr/lib/gcc/x86_64-linux/4.0.0/include/emmintrin.h:1420: error: syntax error before '__m128d'
...
Compilation of ubuntus-xorg source-package fails also.
Greetings James
vBulletin® v3.7.4, Copyright ©2000-2008, Jelsoft Enterprises Ltd.