[Solved] DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

causes inifinte boot loop - i rechecked twice to make sure this is the package that causes this.

Who made this update and what's it for?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

I thoughtlessly installed it. -- And it didn't cause me any problems. Sometimes installing something simply activates a disaster you already have waiting.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

I also update it, I had 3 reboots there is normally lit my n900, but I hope the next reboot no recurrence of the problem.

someone else had this problem to report it and correct it?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Here is the old package and what does:D

http://maemo.org/packages/view/libxau6/ new package
http://maemo.org/packages/package_in....0.3-2osso1.1/ old package

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Just did the update together with busybox and bootmenu.
everything OK, no problems at all,
after reading this thread, I rebooted 3 times without any problems.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

http://maemo.org/packages/package_in...meego1141+0m6/ - doesn't have a maintainer and has "meego" in version string... and, what's worse it's again the situation when a package in extras-devel have the same name as package from "Maemo 5 device root filesystem" nad SSU repositories... (reminds me of SDL_mixer, which might also break something after installation). Are you sure it didn't cause conflicts with other packages, e.g. maemo-fremantle-pr? Did you install by ham, fam, apt-get, fapt-get?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

i installed by 'apt-get update' as i always do...

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

strange, I uploaded this and added myself as the maintainer, don't know why I'm not the maintainer.

I compiled this as a build-depend for other libs needed for meego.

It's devel after all...
Has anyone beside impeham experienced any problems?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Did you consider using different name? ;) it looks like whole lot of other software now depends on it and even simple update of psx emulator or even apt-get update with extras-devel enabled (i guess we all have xserver-xorg-core package) will install this one... if extra functions are needed only for meego and the package itself is in Maemo core, it could always be called e.g. libaux-power (busybox-power, kernel-power, etc. ;)) and have "provides" and "replaces" flags set in debian config file. Feel free to correct me if I'm wrong, but pushing to extras-devel package with exact same name as a package in other repo is plain wrong :)

edit: i still have osso version installed, so can't help you with testing, if i update (in case it will get pushed with some other updates), i will let you know here in this thread.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Nice security hole if it does reboot loop for some (even without, was wondering if Nokia started upgrading packages from 2 years ago seeing this go live)

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

it caused me too, reboot loops and red light blink, how can i correct this?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

BackupMenu if you ask captain hindsight, reflash if else

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Updated to the "meego version" too and my phone survived a full boot (incl. battery out for some seconds) ... smells fishy though ...

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Wipe your phone with a dry cloth. Put in rice overnight, might get rid of that smell

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Sounds like thing, that should be quickly replaced with package containingold version with bumped version number, as dirty quickfix for people that already installed it. Or someone got better idea?

marmistrz, I appreciate Your good will, but could You please use some common sense? As misiak said, Your upload is wrong, wrong, and plain wrong. Please, ask before uploading something that don't have extras-testing and/or extras installation candidate, as You're overwriting -devel one, with only -devel possible.

Agreed on it being security hole, though.

/Estel

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Estel: while I agree with your point, this is extras-devel we are speaking about, standard warnings apply (or have they gone to sh...?, not many people still flash big red warnings about it), it IS for devel purposes, do you really mindlessly click 'update all' with devel as source???

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Someone phucked up. Thanks for the warning boys, i'm updating my system just before leaving for another three weeks, and it showed up in FAM.
@marmisterz: Sure its devel, but please use another name so that it will not conflict with the tested version, will you? If it's for MeeGo-related stuff but mangles with an root/SSU contained package, this is nasty.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Actually the SDL_mixer with support for ogg and mp3 fixes a few problems and is full mixer vs wav only provided by Nokia (does conflict with some packages requiring this version of mixer, that is true, another repo hell example)

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Thanks for this - I recommend everyone who got it installed to manually overwrite using original version, via dpkg -i <downloaded_file>.

@szopin
While I agree about it being -devel "and the usual warnings", it's not the point here. It got same name as package from SSU repos, thus overwriting it during update, despite *not* being proper actualization, nor it was meant to. Plain wrong situation. Yea, it's mainly due to lack of common sense on uploader side (sadly, which he got history for :/ ), but also a secutiry hole in repos system.

The later will be probably addressed via Community OBS, but for now, some quick fix is needed.

/Estel

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Assuming you're going for vacation... does not compute. I delayed updating busybox-power for 2 months, as it is a tool I use daily/all the time. Checking the thread if people will report any issues regularly. Don't believe any update will fix anything if I got stable system (in the long run it might bring goodies, but mostly those are bugfixes, have no bugs to cry - why rush with update??? Unless I'm in testy mood, but right before vacation? got burned once, enough)

And seriously, those should return:

BEWARE OF EXTRAS-DEVEL!
UPDATE ONLY IF YOU KNOW WHAT YOU'RE DOING WITH THIS REPO AS SOURCE (or if you're a tester)

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Will defend marmistrz here. devel is devel. It is for development and testing, people who got this as a constant source and count on it not breaking their system are at their fault. Maybe testing (moving devel to testing) is going too slow for most, or maybe they require constant feel of being bleeding edge... devel should stay devel, fix things elsewhere

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

if i wasen't know as Dr Frost or Frost, i would so use that as my user name, can't stop thinking about south park right now and how ignoring a person one would be.

-------

You should not have updated that package.

/Captain Hindsight.

-------
sorry for the brain fart hehe, and thanks for the warning about this package..

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Nope. But also possibly being without Inet for quite some time, so like always fetching the latest updates a couple days before.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

For? Expecting a bugfix? Sure. Having a working PC do we download 'Antivirus-helps-protect-your-compooter-from-ID-thieves.exe' just so we are safe from threats? Devel got close to none verification of uploader (or is email @emails.for.that.one.page.registering.com worth anything?) so should be treated as untrustworthy source. Those warnings should return. Update-all is an option for extras only (maybe extras-testing too, not sure)

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

OK. Sorry, I didn't expect any issues to come out.
1. Is it possible to delete the package from -devel (or make it not install)
2. Is it possible to tell in debian/rules to use the libraries from somewhere else to link and -dev files from somewhere else to include (only editing debian/rules, not all the source files) and so on?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Not sure on deletion part, but maybe just download source of previous version, touch all files and push as maemo2 version or something?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

It'll be still confusing. If the build-depend is libxau-dev (>= 1.0.5) it'll be accepted and it shouldn't. Any other ideas?
edit: Is there some extras-devel admin so that I can contact him to remove the package from repo?

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Wait, pushing previous source/build will depend on newer??? No way to remove failed or wrong depends? Not sure I got that right

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Nope, there are no packages that depend on newer libxau6 uploaded yet.
But I wouldn't port it if it wasn't needed as a depend for other apps (libxi6, which depends on libx11 and libxau6 and so on and so on)

If I make libxau6 v. 1.0.6...maemo2 containing the old files, it'll satisfy build-deps for sources which depend on newer version. This may be veeery confusing

If I could tell make: use the version from /opt/meecolay/include for includes (when it's not full path, just like "#include <iostream>") and libs from /opt/meecolay/lib for linking.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

I cannot help you with first question, but a good start for me would be contacting repo admins/maintainers (are they active? I remember there was an issue when Pali wanted to become Titan's power kernel maintainer). If it breaks important system package, it may even be a good idea to contact council. Maybe even qgil, his maemo.org's profile states he is from Nokia and happily he seems to still care about N900).

Ad.2
I guess you would need to change makefiles or configs (if they are properly written, maybe it would require only a change of DEBIAN/rules file). You have to trick the linker to link to other library/other version of library, try debian packaging tutorials, I remember reading somewhere about similar situation, but don't get over excited - afaik even somewhat-official Debian multimedia repositories have conflicts wth official Debian repos due to package versions conflicts (what a mess...). You should definitely change something anyway, I know this is extras-devel, but some packages take forever to go higher (or even they never make it), many people have devel enabled just for software like psx or other game console emulators, to name a few.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

actually no need to touch files, he would just need to change package metadata under DEBIAN/... folder (forgot which file, I haven't slept well today) to higher version.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

This can be tried: http://stackoverflow.com/questions/5...r-gcc-in-linux
and LD_LIBRARY_PATH

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Big thanks to the life saver backupmenu (and my disciplined every week phone backup :))

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

It still will confuse build-depends

Hey!! I've got an idea! I'll make it conflict with libxau6 (<< 1.0.6)

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Wow, total ignoramus here, but no ctrl-z option for such cases in autobuilder is worrying, thought pushing previous version with bumped number would be sufficient, seems not, marmistrz - good luck ;)

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Yeah, extras-devel is dangerous! Just like sharp knives ... if you don't handle them properly they just might explode into your face!
Using extras-devel can brick your phone but that doesn't mean that it shouldn't be reported and fixed! So much for the fish ... ;)

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

This is hinting at problems with promotion, if one adds devel for certain software he should still be very wary of updating-all with devel included. Update critical component with your psx emulator? Why not, what could go wrong... this is why the warnings used to be issued on per-post basis. I do know (I myself keep devel included all the time, though I review what is proposed for update) most people do this, but it is not problem with devel, we could move development outside of maemo, but it is even worse solution, it is problem with old and forgotten rule

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

The problem is, these packages use ">=version" or no version string at all, so imagine:

1. package maintaner (e.g. of psx emu) uploads new sources to autobuilder
2. autobuilder builds it using broken libxau6 package
3. new package rolls out, depending on new version of libxau6
4. someone sees update - "oh well, what can possibly go wrong, it's just an psx emu, update!"
5. ham/fam/whatever sees update of depending library, so it says "oh, sweet! install it, too!" (and you can't expect non-programmers to be worried even it shows a message about upgrading some other packages, that is normal when upgrading some packages...)
6. nuclear holocaust ensues

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

So how would older source packaged as maemo2 version not stop it? FAP/HAM downloads latest which is older - nuclear holocaust prevented.

Re: DO NOT UPDATE TO LATEST libxau6 PACKAGE!!!
 

Is there a way to restore old version of libXau... via RescueOS? Because I stuck in reboot loop and even backupmenu's restored rootfs didn't help...