Discussion:
help with /etc/mach/conf
Walter Hieber
2006-03-16 03:00:08 UTC
Permalink
Okay so I'm trying to setup mach again on the new system and here is
what I keep getting:
mach
Could not read location file /etc/mach/location: EOL while scanning
single-quoted string (location, line 14)
***@Yoper ~ $
Below is my conf.

See if you can spot the bug. Thanks

I know it must be a quotation mark or something.
# mach system configuration file -*-
python -*-

# These configuration options can be overridden on per-root basis in
# /etc/mach/dist

# Spinner theme
config['spinner'] = {
'wheel': '/-\|',
'text': '<-WORKING->',
'point': ".:':",
}

# Directories
config['dirs'] = {
'states': '/var/lib/mach/states',
'roots': '/var/lib/mach/roots',
'results': '/var/lib/mach/results',
'tmps': '/var/cache/mach/tmp',
'packages': '/var/cache/mach/packages',
'archives': '/var/cache/mach/archives',
}

# Default root
config['defaultroot'] = 'yoper-2.2-testing'

# Files created in the root
config['files'] = {
'/etc/resolv.conf': '''
#nameserver 215.237.151.97
#nameserver 215.237.150.33
nameserver 4.2.2.1
''',
'/etc/hosts': '''
127.0.0.1 localhost localhost.localdomain
''',
'/usr/bin/apt-sigchecker': '''#!/bin/bash
while read p; do
/bin/true
done
'''
}

config['script-success'] = "echo Results:"

# Additional macros
config['macros'] = {
'Packager': 'Walter C. Hieber <notfilled for post-odAbcf0Mc9JJm/Hvfsr4+***@public.gmane.org>',
'vendor': 'Yoper Ltd.',
}
Edward Johnson
2006-03-16 07:39:26 UTC
Permalink
Is mach still being used?

i thought everything is being done at the buildserver?
Post by Walter Hieber
Okay so I'm trying to setup mach again on the new system and here is
mach
Could not read location file /etc/mach/location: EOL while scanning
single-quoted string (location, line 14)
Below is my conf.
See if you can spot the bug. Thanks
I know it must be a quotation mark or something.
# mach system configuration file -*-
python -*-
# These configuration options can be overridden on per-root basis in
# /etc/mach/dist
# Spinner theme
config['spinner'] = {
'wheel': '/-\|',
'text': '<-WORKING->',
'point': ".:':",
}
# Directories
config['dirs'] = {
'states': '/var/lib/mach/states',
'roots': '/var/lib/mach/roots',
'results': '/var/lib/mach/results',
'tmps': '/var/cache/mach/tmp',
'packages': '/var/cache/mach/packages',
'archives': '/var/cache/mach/archives',
}
# Default root
config['defaultroot'] = 'yoper-2.2-testing'
# Files created in the root
config['files'] = {
'/etc/resolv.conf': '''
#nameserver 215.237.151.97
#nameserver 215.237.150.33
nameserver 4.2.2.1
''',
'/etc/hosts': '''
127.0.0.1 localhost localhost.localdomain
''',
'/usr/bin/apt-sigchecker': '''#!/bin/bash
while read p; do
/bin/true
done
'''
}
config['script-success'] = "echo Results:"
# Additional macros
config['macros'] = {
'vendor': 'Yoper Ltd.',
}
_______________________________________________
yoper-dev mailing list
https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
Tobias Gerschner
2006-03-16 07:56:50 UTC
Permalink
Hi,
Post by Edward Johnson
Is mach still being used?
i thought everything is being done at the buildserver?
Mach is not obligatory. But it raises your skill exponentially if you
use it. Since you can dig into the buildenvironment and try things
out. The buildserver does not offer you the possibility to learn for
you. Once you're somewhat skilled you don't need mach that often. Only
for complicated packages.
Post by Edward Johnson
Post by Walter Hieber
Okay so I'm trying to setup mach again on the new system and here is
mach
Could not read location file /etc/mach/location: EOL while scanning
single-quoted string (location, line 14)
Look at /etc/mach/location , line 14 there is a single quotation mark
missing somewhere.

regards


--
Tobias Gerschner
Member of Board of Yoper Ltd. NZ

Knowing is not enough; we must apply. Willing is not enough; we must do.
Edward Johnson
2006-03-16 08:37:31 UTC
Permalink
Post by Tobias Gerschner
Hi,
Post by Edward Johnson
Is mach still being used?
i thought everything is being done at the buildserver?
Mach is not obligatory. But it raises your skill exponentially if you
use it. Since you can dig into the buildenvironment and try things
out. The buildserver does not offer you the possibility to learn for
you. Once you're somewhat skilled you don't need mach that often. Only
for complicated packages.
does this mean i can also contribute packages i build using mach?
Post by Tobias Gerschner
Post by Edward Johnson
Post by Walter Hieber
Okay so I'm trying to setup mach again on the new system and here is
mach
Could not read location file /etc/mach/location: EOL while scanning
single-quoted string (location, line 14)
Look at /etc/mach/location , line 14 there is a single quotation mark
missing somewhere.
regards
--
Tobias Gerschner
Member of Board of Yoper Ltd. NZ
Knowing is not enough; we must apply. Willing is not enough; we must do.
_______________________________________________
yoper-dev mailing list
https://morpheus.pingos.org/cgi-bin/mailman/listinfo/yoper-dev
Tobias Gerschner
2006-03-16 08:49:14 UTC
Permalink
Hi,
Post by Edward Johnson
Post by Tobias Gerschner
Hi,
Post by Edward Johnson
Is mach still being used?
i thought everything is being done at the buildserver?
Mach is not obligatory. But it raises your skill exponentially if you
use it. Since you can dig into the buildenvironment and try things
out. The buildserver does not offer you the possibility to learn for
you. Once you're somewhat skilled you don't need mach that often. Only
for complicated packages.
does this mean i can also contribute packages i build using mach?
If you want to see rpms from you on yoper.com than you MUST use the
buildserver it is our way to ensure that packages are built properly
and apply to some packaging guidelines:
http://www.yoper.com/wiki/index.php?title=Yoper_Packagers_Guidelines#New_guidelines
.

However you can build rpms that work flawlessly on any yoper machine
if you use mach the way it was shipped on the ISO. Work flawlessly
means you compile your applications cleanly against the least minimum
of required packages. To make it a proper package for the general user
also think about providing a convenient default configuration (e.g. as
cups does currently NOT have).


regards

--
Tobias Gerschner
Member of Board of Yoper Ltd. NZ

Knowing is not enough; we must apply. Willing is not enough; we must do.
Loading...