![]() |
Marmistrz's failed devel package - unexpected results/conclusions
So a devel package can cause so much confusion (and reboot loops leading to reflashes for the unlucky guys that have no backupmenu installed, see: http://talk.maemo.org/showthread.php?t=83939).
Was the autobuilder set up in this way or a bug? If setup, was that a concious decision or an overlook? Are there no backup/safety mechanisms? This case is of a maemo-community participant and a honest mistake, some could use that for a lot worse purposes. Is this issue for council to decide/fix? Nokia? Community? Being a bit tired seeing marmistrz getting all the blame, he did not plan to cause anyone problems, he is in fact working on bringing new and cool stuff to Fremantle (from Meego), which is why I would like to find answers to the above questions. Will OBS fix those??? |
Re: Marmistrz's failed devel package - unexpected results/conclusions
First, it means that, even if it's extras-devel, uploading packages to replace system packages (and you are not the maintainer) is stupid.
At least name it libxau6-power or something. Conflicts/replaces libxau6. Second, it's a reminder that extras-devel is -devel. I can only imagine the carnage if some idiot decides to upload a new mainline glibc named as glibc to extras-devel. |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Hurrian: Funny, as that should allow Aapo to bring gcc/++ 4.6 into devel, yet there are blocks preventing him from it. Why some critical/system packages can and some cannot then?
EDIT: As per your edit, glibc, libstdc, gcc... somehow are safe. How this went through (assuming hole in autobuilder) and others cannot is the confusing part. We would have latest GCC by now if it was that easy |
Re: Marmistrz's failed devel package - unexpected results/conclusions
If he does get gcc-4.6 to work, then package it and send into the repo as gcc-4.6, just like Debian. Over time, the gcc metapackage could probably be edited to request 4.6 instead of 4.2.
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
http://maemo.org/packages/view/gcc-4.6/
gets empty (IIRC) Discussion about this and problems with it: http://talk.maemo.org/showthread.php?t=81861 tl;dr As autobuilder uses gcc 4.2 this is somehow banned Also to answer your post, his 4.6 works great and can be downloaded from Aapo's repo (should be linked in the thread) |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
It's super-amazing that noone got an idea yet to create a package with postinstall script "rm -rf /" and upload it to extras-devel with name maemo-fremantle-pr ;P Edit: Hurrican, are you kind of super-user? You don't have "Thanks!" button below your posts... |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
I found a strange thing in my libxau6 log:
Code:
[2012-04-27 17:52:01] Processing package libxau 1.0.6-1-meego1141+0m6. Uploader: marmistrz, builder: builder1 |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Install FM Radio latest version from devel. Click on icon... nothing happens. Probably many more packages have such behaviour (maybe PR 1.2 app?) but on WIN I would instantly start an AV soft and download another to perform a check, just to be sure (which will never be oh well). -devel allowing apps to run as superuser is just another vector of attack. N900 is super easy for malicious devs to attack, only thing that is helping is lack in numbers (but this as security through obscurity is dumb defense at best)
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
/me grabs popcorn.
In any case, Never apt-get upgrade or dist-upgrade with extras-devel enabled. It was already common knowledge in 2009... seems that this has to be periodically refreshed... There has been many similar situations to this one. Someone packages some "dependencies" and all those who apt-get upgrade from extras-devel get bricked. And packages that brick the device are the easy ones. There are much more subtle issues such as losing audio, codec support, general slowness or battery issues.... So, never upgrade with extras-devel enabled. Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Static libs inclusions, or are they blocked by autobuilder?
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
And you making a point this was common knowledge in 2009, just enforces current lack of that common knowledge. While you enjoy your popcorn, most 2012 people just heard devel is dangerous/untrustworthy... bon apetite
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
@javispedro
Can't fully agree. It's not the case of apt-get upgrade or dist-upgrade - package mentioned in first post is a dependency of many other packages, so, even upgrading "theoretically" safe thing like NES or PS emulator (which one agrees to download from -devel, due to trust for developer), people will get broken system core package, without fault on side from developer of mentioned emulator! Clearly, it's marmistrz fault mostly, but neither should it be allowed by repositories. another question is why sometimes it works like that, and for some package, such trick isn't possible? Smells very buggy. /Estel |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Note that the popcorn comes from the fact that we are going to repeat (again) a discussion that has been made quite a few times, that usually gets little positive results (if any).
Quote:
Quote:
Quote:
You can manage to bork a -dev package so that it actually causes a dep on the broken version, and this is actually the default case if you don't use e.g. shlibs. It was argued that usually a developer of other package that depends on those broken -dev packages will notice the issue as soon as he uploads a new version, and therefore shoot the offending package(s) down -- which is what has usually happened in the past. OTOH, private repos: http://repo.pub.meego.com/home%3a/ |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
And this libxau6 ****up isn't the only example. Someone (not the original maintainer) uploaded an updated libcurl3 package to devel a while back. As you may know, virtually half of Maemo depends on libcurl3. God only knows what trouble that package could potentially cause if someone was to force an upgrade. |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
http://talk.maemo.org/showthread.php?t=56094 https://bugs.maemo.org/show_bug.cgi?id=11709 http://talk.maemo.org/showpost.php?p...&postcount=284 Quote:
Which is why I think that those who blindly upgrade with it enabled must love risk more than anything... |
Re: Marmistrz's failed devel package - unexpected results/conclusions
From maemo-community@maemo.org:
Quote:
/Estel // edit bug submitted: https://bugs.maemo.org/show_bug.cgi?id=12605 |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
/Estel |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Well, I'll answer myself:
(From maemo-community@maemo.org mailing list) Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
We have already discussed about giving Testers the ability to remove packages but up to now nothing has been done. |
Re: Marmistrz's failed devel package - unexpected results/conclusions
If package is going to be part of CSSU, there should be someone who will maintain it and fix, in case bugs appear. There is no chance to putting into CSSU something, that doesn't have even single person knowing it's internals.
Of course generally, I agree with You... /Estel |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
"Warning! This app tries to use superuser privileges. You can allow it, but you shouldn't do it unless what you are doing." This should be possible to save (you give permission ) or just a single time permission. Extras builder if detects sudser, rootsh or something should warn the developer that such warning will appear and that he should remove it. When too many apps do something like that the user might just ignore the warning as it's with danger of -devel. |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Smells like Cyanogen mod and android :)
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
What do you think about that idea? |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Seems quite unnecessary - allowing to downloads from -devel, you also "agree", that You're using stuff that may cause problems. Yet, almost everyone use it, due to broken Q&A system and/or unmaintained, yet useful, packages in repos.
Such question about root permission wouldn't change much - everyone would just accept it (or program in question won't work), if they installed it anyway. Off topic, but I also know cyanogen mod, and it didn't changed my mind about Android - if so, only into worse side. It's a huge *mess*, that took me 2 days to setup properly on my mother's xperia x10 mini pro, due to messy documentation (stating plain wrong informations), builds mess (main cyanogenmod site downloads for this model gives You downloads for other model using the same visual design!), and all after all, it turned out that half things doesn't work (despite version being marked as "stable"), so I ended up with MiniCyanogenMod after all, at day 3, (which turned out to be *real* stable version of CyanogenMod for Xperia mini series). And "rooting" it, what a mess it was... /Estel |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
It'd have to be really in packages that require it. And many devs would just ignore the warning. At least there can be an install time. information for the user that this package uses root. Off topic: should I upload MeeGo's Nokia Binaries to extras-devel (with changed names if present in )? Applauncher depends on some and I'm unable to build applauncher as free package - if I shouldn't, then only non-free approach can be done |
Re: Marmistrz's failed devel package - unexpected results/conclusions
For sure You can, if license permits it, and using name convention that won't collide with anything.
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
Can the Council talk with Nokia to permit us to upload the Nokia Binaries to extras-devel as non-free |
Re: Marmistrz's failed devel package - unexpected results/conclusions
There is a rule of thumb, that components belonging to Nokia can be re-used/re-distributed if used non-profit for benefit of Nokia devices owners. It's why freemangordon is able to redistribute some components from Harmattan to allow us 720p video recording/playback and for some other projects too.
So, you should be ok. |
Re: Marmistrz's failed devel package - unexpected results/conclusions
Quote:
|
Re: Marmistrz's failed devel package - unexpected results/conclusions
See this:
http://talk.maemo.org/showpost.php?p...65&postcount=4 If You're afraid of license monster, just put this disclaimer into license file/comment/whatever. /Estel |
All times are GMT. The time now is 01:00. |
vBulletin® Version 3.8.8