Marking this as "won't fix"; karmic support was dropped a long time ago,
so it's too late to worry about this upgrade path now.
** Changed in: loggerhead (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I just discovered the same thing. Repositories served through
loggerhead had stopped working when I upgraded the server in June.
Sadly I had nobody inform me until I found bug reports linking to fixes
in my (now stale) repositories.
I got it working again by creating a /etc/serve-branches.conf lo
The loss of functionality caused by the change of server and/or
configuration file format/use strikes me as being a retrograde step.
Unless I am missing something.
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You received this bug not
Correct, it's not currently possible.
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
When last I looked in to it, which was about a year ago, there was not.
I doubt support has been added in the mean time.
Sadly, loggerhead documentation is minimal and hard to find.
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You re
Is there any way of setting the front page titles and headers with the
new configuration file structures?
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You received this bug notification because you are a member of Ubuntu
Bugs, which i
OK the problem appears to be that Loggerhead now runs as user loggerhead
which is incomptible with user www-data that is used by Apache. This
make dealing with permissions irritating. I guess I will add loggerhead
to the www-data group.
--
Lucid upgrade switch to serve-branches.conf without pro
Oh, I see, you can't have space around the =. This is irritating. At
least the server now starts. Sadly it just says "Internal Server Error"
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You received this bug notification because yo
Redge, Your proposed minimal /etc/serve-branches.conf file fails to
work for me:
|> sudo sh -x /etc/init.d/loggerhead start
+ PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
+ DESC=Loggerhead Bazaar Branch Browser
+ NAME=loggerhead
+ PIDFILE=/var/run/loggerhead.pid
+ SCRIPTNAME
Saving the following as /etc/serve-branches.conf will at least allow the
loggerhead daemon to start:
served_branches=
prefix=
port=8080
** Changed in: loggerhead (Ubuntu)
Status: New => Confirmed
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad
the serve-branches.conf is called in /etc/init.d/loggerdhaed.
Loggerhead should at least proposes a default serve-branches.conf.
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You received this bug notification because you are a member
On 16 April 2010 11:50, Michael Hudson wrote:
> I guess we could do something in the packaging so that you at least know
> that something has changed -- but /etc/loggerhead.conf and /etc/serve-
> branches.conf are not in (remotely) the same format, and indeed they are
> interpreted by different en
If it's a bash script it's probably added in the packaging.
- Martin
On 16/04/2010 11:50 AM, "Ian Clatworthy"
wrote:
Lionel,
I'd like to get this sorted ASAP but I'm pretty new to the loggerhead
code base. Looking through the code, I can't see where the name of the
config file is set or where
I guess we could do something in the packaging so that you at least know
that something has changed -- but /etc/loggerhead.conf and /etc/serve-
branches.conf are not in (remotely) the same format, and indeed they are
interpreted by different end points.
We could perhaps try to convert them in comm
Lionel,
I'd like to get this sorted ASAP but I'm pretty new to the loggerhead
code base. Looking through the code, I can't see where the name of the
config file is set or where the settings are loaded. Maybe I'm blind or
maybe it's a packaging issue? Can you explain how you've configured
Loggerhea
Ian > it might not be trivial because it looks like format are
differents. So far, I was unable to find any example of serve-
branches.conf to write my own. I have no idea of what is expected.
By reading the script, I figured out that it should be a simple bash
script that assigns some local varia
Maybe Loggerhead ought to still look for Loggerhead.conf if server-
branch.conf is not there?
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Current workaround : keeping the Karmic package.
--
Lucid upgrade switch to serve-branches.conf without providing one
https://bugs.launchpad.net/bugs/563118
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
18 matches
Mail list logo
