-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2007, at 9:37 AM, Fil wrote:
> I had to tweak permisions on logs/* to be able to launch bin/
> mailmanctl
> start, as they had been created with g-w (the logs/ dir is
> correctly g+sxw)
I think I solved the permission problems in r8131.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 3, 2007, at 9:37 AM, Fil wrote:
>>> How do I fetch the dev branch, what set of commands do I use to
>>> install
>>> it and migrate a few lists. Nothing fancy, but precise urls and
>>> commands.
>>
>> Take a look at
>>
>> http://wiki.list.or
> logs and data and other writable directiory and files should be owned by
> mailman. We should be able to check them with bin/check_perms.
Yep, it works. I thought make install would have set the permissions correctly
-- Fil
___
Mailman-Developers
Fil wrote:
>>> tried to modify the list options thu the web ui and got
>>>
>>> SQLError: (OperationalError) attempt to write a readonly database 'UPDATE
>>> "List data" SET bounce_processing=? WHERE "Listdata".list_id = ?' [0, 2]
>> Who and what is the owner and permission of data/mailman.db.
>
>
> > tried to modify the list options thu the web ui and got
> >
> > SQLError: (OperationalError) attempt to write a readonly database 'UPDATE
> > "List data" SET bounce_processing=? WHERE "Listdata".list_id = ?' [0, 2]
>
> Who and what is the owner and permission of data/mailman.db.
[EMAIL PROTE
Hi Fil,
Fil wrote:
> tried to modify the list options thu the web ui and got
>
> SQLError: (OperationalError) attempt to write a readonly database 'UPDATE
> "List data" SET bounce_processing=? WHERE "Listdata".list_id = ?' [0, 2]
Who and what is the owner and permission of data/mailman.db. Are
> >How do I fetch the dev branch, what set of commands do I use to install
> >it and migrate a few lists. Nothing fancy, but precise urls and commands.
>
> Take a look at
>
> http://wiki.list.org/x/ogI
>
> and let me know what you think.
OK; I was able to follow the instructions to the point of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 2, 2007, at 12:40 PM, Fil wrote:
>> BTW, I'm hoping there will be some adventurous folks willing to test
>> out the trunk. Don't use it for anything you care about, but at this
>> point you should be able to export your MM2.1 lists and import
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 2, 2007, at 12:40 PM, Fil wrote:
>> BTW, I'm hoping there will be some adventurous folks willing to test
>> out the trunk. Don't use it for anything you care about, but at this
>> point you should be able to export your MM2.1 lists and import
> BTW, I'm hoping there will be some adventurous folks willing to test
> out the trunk. Don't use it for anything you care about, but at this
> point you should be able to export your MM2.1 lists and import them
> into the trunk.
A mini how-to would help me become adventurous again :)
How
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 29, 2006, at 5:30 PM, John W. Baxter wrote:
> On 12/29/06 2:17 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote:
>
>> I'm about to merge my SQLAlchemy branch to the trunk. I'm happy
>> enough with where this is going to commit to this approach goi
On 12/29/06 2:17 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote:
> I'm about to merge my SQLAlchemy branch to the trunk. I'm happy
> enough with where this is going to commit to this approach going
> forward.
[Loud cheering from the sidelines!!]
(An upcoming rewrite of our mail handling system w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm about to merge my SQLAlchemy branch to the trunk. I'm happy
enough with where this is going to commit to this approach going
forward. I wrote about it a bit in a news article on wiki.list.org
and I'll try to elaborate there when things sett
13 matches
Mail list logo
