Wasn't going to openly gripe about it, sent a PM to respected nixers in the community and am guessing they'll help sort things out ... By sending it up da pipe. When/if they feel it's warranted.
Don't feel it my place to gripe, much less gripe at a respected and more experienced/knowledgeable gnu/nixer like Corenominal. Also still feel #! is pure nixy kickbuttness for beginner to more seasoned nixer(s). Should've just held off and hopefully let my gripe find it's way to the #! head honcho. Atm though, am annoyed ... though it's my own fault and still isn't my place, shrugs.
Noticed some #!'ers still having issues upgrading IW via the mozilla backports. Isn't a new thing ... Sir Ivan for one I know has mentioned it ... Back when more involved in Crunchville I had headaches due to it too. Spent a couple hrs I'll never get back trying to help some bangers deal with it. Again totally my fault/choice + am a friggin detail oriented ( read anal) kind of person ... sighs.
Anyway, it's obviously still a friggin issue. Please fix it or find a better approach than the current situation. Esp if a: Core wants IW to be the default browser and b: Puts an IW version in the #! repo. Isn't a sky is falling ... omg it's the end of the world kinda thing. Plus no disrespect ( @ all) meant towards Corenominal. As mentioned respect the guy and all the effort he puts into #!. Just 2 cents and 2 friggin tylenol for me. My fault all the way around and too much coffee as well.
I have now attempted to do my good deed for the day and repay Corenominal for his kickbutt contrib to the nixsphere. In fact I think this covers good deeds for the next mnth or so and I can go back to my regular pure evil and selfish outlook on life.
Last edited by CBizgreat! (2013-06-21 07:28:46)
Last edited by CBizgreat! (2013-06-21 16:46:58)
Last edited by pidsley (2013-06-21 17:08:34)
Last edited by CBizgreat! (2013-06-21 18:10:46)
...yes starting to get the picture now. I'm still on Statler here, where IW is in a separate crunchbang-mozilla repo which you can comment out when adding mozilla.debian. On Waldorf it's in the main Crunchbang repo where the 1001 pinning holds it down at 20 even if there's a newer version elsewhere.
Hmm, agreed less than optimal perhaps. I can see there were reasons for having a customized Crunchbang version of iceweasel, but that brings a certain responsibility, perhaps, to keep it reasonably up to date. It's especially important for a web browser.
Perhaps the pinning preference can be changed on the specific Iceweasel package, rather than the whole repo?
The best way to solve this issue is to remove Iceweasel all together. Chromium should be the default browser in Crunchbang, and in all other distros...
- apt-mark hold account
ew, that wouldn't solve the issue at all. All browsers, chrome/chromium included, need to be regularly updated to patch security holes. If Chromium became the default CrunchBang browser then corenominal would want to customize it for the same reasons as for Iceweasel (google ad revenue I'm assuming) so the same problem would exist. There would be a browser in the CrunchBang repos that would fall behind, unless maintained locally.
Last edited by CBizgreat! (2013-06-22 21:22:18)
Why not just put the #! repo at 990? It seems like 1001 just causes a bunch of problems without much benefit...
“I don't believe in charity. I believe in solidarity. Charity is so vertical. It goes from the top to the bottom. Solidarity is horizontal. It respects the other person. I have a lot to learn from other people.” - Eduardo Hughes Galeano
As always +1 Pvsage ... also as pretty usual + Vast ... also +1 the guy above in the lowering pin-priority to something other than 1001. Jmo but 1001 is a bit extreme. Corenominal has many yrs of experience + yrs of putting out kickbutt gnu/nix .. Shrugs.
isn't an necessarily major issue. More shrugs .. like John said ( Ivan said long before) + who knows how many others ... If you want a friggin branded browser version in a distro repo's .... Then perhaps keep it up to date/patched ? To tell the truth, honestly I personally have less than no reason to care anyway. Am clearly retarded for investing the time + effort in the topic. Would've been less time consuming just to do a vm install and make sure.
Came across it during a #! forum visit. Whatever n whichever ... found a fix that imo satisfies my criteria for advising other nixers ... That being, tested it myself firsthand and it worked out well .... blahblahblah. Solution that 1st popped into mind would've more than likely worked just fine too. Oh well ... tried + said my peace on the topic now. Should've kept my digital mouth shut either way.
Messing around w Waldorf in vm ... Seems to be the usual crunchy/bangy nixy kickbuttness. Would expect nothing less from Corenominal. This isn't a make or break type of deal. Hope he decides to settle on a good solution though. Mentioned ... not something I have reason to really be concerned with regardless.
Anal note: Not sure the wheezy-backports entry above is valid. It's apparently since been merged blahblahblah. Just googled and went w the 1st repo entry that looked about right. Doesn't friggin matter either way ... The mozilla repo entry is from the mozilla repo webpg and is definitely correct and for the subject under discussion in this thread ... that's really all that matters. Did as above ... worked perfectly. Blahblahblah/etc.
Last edited by CBizgreat! (2013-06-23 04:59:07)
Not a thing wrong with doing your own dirty work Debianjoe.
Am the same way myself. Never come up against a tech problem that common sense or enough experimentation or googling couldn't solve.
Goal here was to try to help others though. Once I'd opened my crawl ... Felt committed and obligated to give valid info on the topic. Ironically ... again, think the 1st thing that came to mind would've worked like a friggin charm anyway. Wasn't sure though ... when I used it had reservations .. even at the time advised others to do likewise, while still having reservations. Sighs ... don't like having reservations when acting like I know what I'm talking about and imo a hack is still a hack ... even if it works fine.
In the spirit of not being an arsehole ... wanted to KNOW ... and/or give best quality info poss before running my mouth. To the friggin point that I spent wayyyyy more time than should have researching the issue. Oh well ... am sure you get what I'm trying to say with all this babble.
Can say I did everything reasonable and then some in trying to help fellow nixers with an issue. Sadly made more of an ordeal than I should've out of it. Thought of plenty of good approaches ... Didn't have a Waldorf install handy to test them on and confirm with. Should've just friggin did the vm thing from the start, shrugs.
No worries ... learned some interesting stuff ... Hopefully solution proposed helps somebody or Corenominal takes notice and sorts it out etc. Virtualbox is friggin kewl ... Any reasonable person has to admit it's FRIGGIN AMAZING what you can get in the opensource or freeware world for $0. Still blows me mind.
Had a older version of Virtualbox on Window$ 7 just sitting there. Took an hr to bittorrent the Waldorf iso and 30mins to get it working. Plus 10 farkin minutes to confirm what I'd thought would work. Yep ... worked .. Wow. I win a kewpie doll ! Whoooooo.
Long story ... long. Meant to post this babble in the how to's/etc.
Sooner this thread sinks into the digital ether ... probably the better ... blahblahblah.
Vll! fellow bangers + nixers.
Last edited by CBizgreat! (2013-06-23 08:04:08)
Last edited by CBizgreat! (2013-06-23 11:56:12)
^ Yeppers ... called prefetching.
Personally always disable that on FF/IW/etc.
Thinks it's interesting ... but stupid. Plus don't see the benefit unless it's an all or nothing kinda thing. Prefetch everything on a webpage or don't bother. Cause your browser isn't likely to psychically choose what you're going to visit afterall. Even then ... it'd be less time + resources on a highspeed connection just to forego the tardedness me thinks and on a lowspeed connection doubly tarded. Lmao ... ah whatever. Disabling prefetch imo is a good browser tweak. As it stands ... jmo prefetching is stupid and a waste, shrugs.
DAMMIT !!! Thought of summin else to add about prefetching. Diff browser makers apparently have diff approaches to implementing it. Been a good long time since bothered thinking about it and/or researching it. One situation that comes to mind though with prefetching. Metered connections ... are more than a few places ... even in the 1st world where highspeed isn't an easy option. Leaves folks using cellular or satellite/etc highspeed. Equals EXPENSIVE ... have seen folks paying $50/mnth for 5gbs of download !!! Yikes ... if your friggin browser is prefetching everything/tonnes of crap you'll likely never even visit ... Counts against x persons bandwidth usage.
That is certainly not welcome in that situation and overage can be costly for people having to deal with that too. Guess it depends on how x browser makers implement it. But if the sucker prefetches everything ... OOoooooo, wow ... I clicked a link and it was almost instaneous !!!! Wow ... yeah great, it was downloaded and stored in cache or etc. Prefetching goes under the bizcuit rendering tricks folder pretty much.
On a highspeed dsl connection and unmetered. Still just personally ... only want my web browser downloading what I tell it to download. When it's directed to download something, shrugs.
Last edited by CBizgreat! (2013-06-23 13:18:10)