Re: [arch-general] mercurial in Extra out of date
Thanks, all Im not realized untill now that not only those packages in AUR could be flaged or commented, but any in the repository. On Wed, Jul 7, 2010 at 11:59 AM, Allan McRae al...@archlinux.org wrote: On 07/07/10 13:43, PT M. wrote: On Wed, Jul 7, 2010 at 11:36 AM, Dan McGeedpmc...@gmail.com wrote: On Tue, Jul 6, 2010 at 10:33 PM, PT M.pen...@gmail.com wrote: It's been a week since mercurial 1.6 released, extra/mercurial 1.5.4-1 is still in the repository. OMG! Raise the alarm!!! You do realize none of us are full-time around here, right? The maintainer will get to it when he can. Until then, learn to use ABS. calm down calm down ... if I sent this to the wrong place, sorry, i just wanted the maintainer got noticed, maybe i shoud sent to him directly? No. It has been flagged out-of-date on the web interface so the maintainer already knows about it. Allan -- Arch Linuxer, Pythoner, Geek -- Blog: http://apt-blog.net
Re: [arch-general] [PATCH 01/48] Bashification of initscripts
On Wed, 2010-07-07 at 14:03 +1000, Allan McRae wrote:
Here is a quick review on all these patches. I recommend that the lvm
and crypttab changes get a decent amount of testing before these go live
as they are the biggest changes being done.
Tighten up the console size finding code a bit.
Add some white space in test construct:
if ((STAT_COL==0)); then
if (( STAT_COL == 0 )); then
and throughout these patches
Maybe when all the other bugs are fixed. :)
Simplify the code that clears USECOLOR.
The following condition is removed with no commit message to explain why
if [ $? = 3 ]; then
TERM_COLOURS=8
An exitval of 3 means tput has no idea what terminal type we are running
on, and I figured that it is after to default to not using colorized
output in that case.
Replace trivial use of grep with bash regex conditional.
- if [ -n $CONSOLEMAP ] echo $LOCALE | /bin/grep -qi utf ; then
+ [[ $CONSOLEMAP $LOCALE =~ UTF|utf ]] CONSOLEMAP=
Use ... ${LOCALE,,} == utf ]] to accurately replicate the grep
Hmmm... I had not seen that parameter expansion before. New to bash
4.1?
Replace slightly too long echo staement with a here document.
^^ typo
I actually find the echo more readable
Well, then Thomas can keep it or drop it as he prefers.
Change the daemon runnign loop to use a case statement.
Quote daemon names.
Merge these commits
Both rc.single and rc.shutdown use the same code to kill everything.
+ # $1 = where we are being called from.
+ # This is used to determine which hooks to run.
- Add separater line here...
+ # Find daemons NOT in the DAEMONS array. Shut these down first
Why has this been removed:
-if [ -x /etc/rc.local.shutdown ]; then
- /etc/rc.local.shutdown
-fi
Ah... it has been moved to another place in another commit. Please
document these sorts of changes in your commit message and preferably do
the entire move in one commit.
Will fix.
Flatten LVM deactivation if block in rc.shutdown.
This change does not do the same thing and I do not see where it gets
replicated
-if [ -f /etc/crypttab -a -n $(/bin/grep -v ^# /etc/crypttab |
/bin/grep -v ^$) ]; then
+if [[ -f /etc/crypttab ]]; then
All the second bit of that test does is to see if there is actual
content in /etc/crypttab. I handle that in the read loop by zapping
comments and blank lines with parameter expansion and conditional checks
instead -- the greps end up reading the whole file anyways.
Replicated via parameter expansion and conditionals:
[[ $line ${line:0:1} != '#' ]] || continue
eval nspo=(${line%#*})
Also another:
+if [[ $USELVM =~ yes|YES
- ${USELVM,,} == yes
bashify bringing up the loopback adaptor.
Add a commit message as that is doing a lot more than bashifing.
Already fixed in the last round of rebasing.
Bashify locale setting.
$LOCALE =~ utf|UTF
Allan
--
Victor Lowther
LPIC2 UCP RHCE
Re: [arch-general] [PATCH 01/48] Bashification of initscripts
On Jul 6, 2010, at 11:25 PM, Dan McGee dpmc...@gmail.com wrote: If there was one thing I wasn't so fond of in these patches, it seemed like there were too many. Some people like larger patches, some like smaller ones. It is easier to merge smaller ones together than it is to split larger ones apart. The beauty of git is the ability to go back and squash and split patches in a way that makes a lot more sense to others- it might not have been the way or order you did things in, but you should try as hard as possible to make a commit the largest logical unit that makes sense, but still small enough to grasp fully. Ya, I wanted to get feedback to see if the larger Arch community was interested before going too much farther. If there are ever closely-related changes strewn across multiple patches in a patch set, you should probably think about merging those commits. -Dan
Re: [arch-general] screen goes blank on reboot after 1st pacman Su of new install!!!???
It would appear that on Jul 7, Myra Nelson did say: Joe: I gave up on gpm in a terminal before x is started. I never could manage to get to work right. Whereas I've almost always got gpm working... In fact I had it working on this install (right after blacklisting nouveau, got me a semi-usable console, right up until I installed nvidia. (sigh) But for anything short of boot screen error messages, I can redirect or tee into a file and use vim's :r command to include anything I really want. It's just such a pain that way... The other thing I've noticed about the onboard graphics is some manufacturers seem to modify the drivers slightly. I had one laptop with ATI onboard and the only drivers I could make work were the ones from the laptop manufacturer. Now why doesn't that surprise me??? Glad you got it working, mostly at least. Me too! Heck now that it's working, I've had time to fully configure xfce, e16 my operational favorite, e17... Course I may like _USING_ e17 best, but configuring it is always a chore. For example this time the keyboard shortcut assignment tool kept ignoring the keyboard (2 out of 3 times) when I'd want to set up shortcuts to exec things like: xterm -bg darkviolet -fg green -fn 12x24 -geometry 92x30 Fortunately I figured out that I could use the mouse pointer to mark the syntax example that always needs to be deleted, then a right click on the marked text let me cut it, and finally by switching to a terminal window with an editor session open, I could create the text of the command there, and then mark it with the mouse, switch back to the semi-functional shortcut routine and paste the text it wouldn't let me type... sigh But I can't complain too much, Once I manage to get it configured to taste, E17 has always been a pleasure to use... At this point I've got Arch sufficiently squared away for me to consider making my next project installing Xubuntu an another partition... But not tonight! Thanks again to everyone who offered advice... -- | --- ___ | 0 - Joe (theWordy) Philbrook | ^ J(tWdy)P |~\___/~ jtw...@ttlc.net
