ainst 'recovering from backups' since that would have taken
longer (just to copy the data around) than fixing the real problem.
no data got lost or corrupted.
kind regards
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
dev
ct owners to move stuff
> away. i've done mine already :)
if you do that, please send us a mail or open us a ticket in admin-trac
so we can delete the project for good (and make sure there are no old
piles of code of misleading stubs laying around.
to use someone elses infra. i know
>> i'll use my own :)
>
>
> Hmm. By what mechanism do we "migrate" all the projects currently on
> projects.om.org? There is a lot of good information in there.
there is no mechanism and thats another reason not to do it ;)
in' easily, but could not find
the real cause, even after hours of grepping through gforge.
means we fixed the perms and left it doing its job (which it does fine
99% of the time.
also it uses a chroot internally which makes things one level more
exiting when getting 'some path
any admin stuff, including giving myself admin power again!
> Can someone with the proper privileges please change my role back to
> "Admin" for me?
should work again
--
Joachim Steiger
Openmoko Central Services
___
devel mailing l
report bugs with down services of any kind via
http://admin-trac.openmoko.org
that way all our admins know something is down and can coordinate the S&R.
kind regards
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
> On Mon, Aug 11, 2008 at 10:33 PM, Joachim Steiger <[EMAIL PROTECTED]> wrote:
>>> Is it possible to configure Trac so that only certain people (OM
>>> employees) can edit the components/milestones/severity fields?
>> in theory yes, but then i would be
"recently closed as duplicate" filter to the list
> of available reports at http://docs.openmoko.org/trac/report/ , and
> instructing users to look at that before reporting any new issues?
> That would at least catch the case of users submitting multiple
> reports fo
which does this:
http://blog.madism.org/index.php/2007/02/21/123-git-tricks
see also
http://admin-trac.openmoko.org/trac/ticket/1492
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.openmoko.org
https
e wiki:
http://wiki.openmoko.org/wiki/CommunityRepository
kind regards
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
ince the
modmagic should fit in any case when trying this.
sounds like it should be in some howto when modversion restriction is
getting implemented. ;)
regards
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.open
s.
> |
> | Maybe someone can nuke this package...
> |
> |
> http://buildhost.openmoko.org/daily-feed/om-gta02/kernel-image-2.6.24_2.6.24+git25+8533927964761f4e2078ccd8607b90f5acc60b93-r0_om-gta02.ipk
removed.
--
Joachim Steiger
Openmoko Central Services
__
for that.
alsa should stay what it is. a driver framework.
adding more layering violations doesn't help (and would hinder pushing
stuff upstream in the long run)
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
/bugzilla.mozilla.org/show_bug.cgi?id=215243
not funny, not nice, not sane. rather sad to be true.
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
irst need anything thats trust and not 'gave me
enough money to shut up'.
regards
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
project and doesn't have the resources to host it
himself.
--
Joachim Steiger
Openmoko Central Services
___
devel mailing list
devel@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/devel
blem and hacked
in a workaround for now
for more details see
http://admin-trac.openmoko.org/trac/ticket/1451
but your account should work again.
please delete the secondary account if you got your old one working.
regards
--
Joachim Steiger
Openmoko C
17 matches
Mail list logo
