[Mailman-Users] Re: Upgrading mailman from 2 to 3 and private archives

Bader, Robert (Bob) writes: > I am not sure how many messages they linked but I suspect it is a > lot. They have lists they use for their groups, and will link to > the messages on their internal website. But if that is the only > option then that is what they will need to do if they want to

[Mailman-Users] Re: Upgrading mailman from 2 to 3 and private archives

Bader, Robert (Bob) wrote: > But if that is the only option then that is what they will need to do if they > want to keep the links. The other option is to keep the MM 2.1 installation and lists. You can disable mail delivery to MM 2.1 in the MTA and remove some things such as the CGIs other t

[Mailman-Users] Re: Upgrading mailman from 2 to 3 and private archives

Thanks, I am not sure how many messages they linked but I suspect it is a lot. They have lists they use for their groups, and will link to the messages on their internal website. But if that is the only option then that is what they will need to do if they want to keep the links. ---

[Mailman-Users] Re: Upgrading mailman from 2 to 3 and private archives

On 4/8/21 9:09 AM, Bader, Robert (Bob) wrote: > So looking to migrate to mailman3 from mailman2, so for archives I see the > notes below stated on the website. So just making sure I understand correctly. > > Private and Public archives will migrate over, however links to the messages > will cha

[Mailman-Users] Re: Upgrading from 2.1.12

Thanks everyone, looking at our options at the moment On Thu, Jul 23, 2020 at 7:33 PM Jim Popovitch via Mailman-Users < mailman-users@python.org> wrote: > On Thu, 2020-07-23 at 10:15 -0500, Barry S. Finkel wrote: > > > On Wed, Jul 22, 2020 at 11:40 PM Mark Sapiro wrote: > > > > > > > On 7/22/20

[Mailman-Users] Re: Upgrading from 2.1.12

On Thu, 2020-07-23 at 10:15 -0500, Barry S. Finkel wrote: > > On Wed, Jul 22, 2020 at 11:40 PM Mark Sapiro wrote: > > > > > On 7/22/20 12:54 AM, Daniel Krause via Mailman-Users wrote: > > > > Good Day > > > > > > > > We have a running 2.1.12 installation that was done long ago via an > > > > ext

[Mailman-Users] Re: Upgrading from 2.1.12

Mark Sapiro writes: > On 7/22/20 12:54 AM, Daniel Krause via Mailman-Users wrote: > > We have a running 2.1.12 installation that was done long ago via an > > external consultant. > > It hasn't been changed in years, but I would like to upgrade this to at > > least the latest 2.x version and p

[Mailman-Users] Re: Upgrading from 2.1.12

On Wed, Jul 22, 2020 at 11:40 PM Mark Sapiro wrote: On 7/22/20 12:54 AM, Daniel Krause via Mailman-Users wrote: Good Day We have a running 2.1.12 installation that was done long ago via an external consultant. It hasn't been changed in years, but I would like to upgrade this to at least the l

[Mailman-Users] Re: Upgrading from 2.1.12

Thanks Mark On Wed, Jul 22, 2020 at 11:40 PM Mark Sapiro wrote: > On 7/22/20 12:54 AM, Daniel Krause via Mailman-Users wrote: > > Good Day > > > > We have a running 2.1.12 installation that was done long ago via an > > external consultant. > > It hasn't been changed in years, but I would like to

[Mailman-Users] Re: Upgrading from 2.1.12

On 7/22/20 12:54 AM, Daniel Krause via Mailman-Users wrote: > Good Day > > We have a running 2.1.12 installation that was done long ago via an > external consultant. > It hasn't been changed in years, but I would like to upgrade this to at > least the latest 2.x version and potentially 3.x. > We w

Re: [Mailman-Users] Re: upgrading plaintext patched 2.0.13 to 2.1

At 16:03 03/01/2003, David Gibbs wrote: "Dan Phillips" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > I located "if self.data_version >= mm_cfg.DATA_FILE_VERSION:" at line > 611 of the /Mailman/MailList.py file. Is this what needs to be altered? > Do I just mak

[Mailman-Users] Re: upgrading plaintext patched 2.0.13 to 2.1

"Dan Phillips" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > I located "if self.data_version >= mm_cfg.DATA_FILE_VERSION:" at line > 611 of the /Mailman/MailList.py file. Is this what needs to be altered? > Do I just make the change to that file then run ./conf

[Mailman-Users] Re: UPGRADING continued...

> "JW" == Jacek Wojaczynski <[EMAIL PROTECTED]> writes: JW> I can go to /usr/local/mailman/bin and type "withlist -l -r JW> fix_url listname" - but I don't think I need that... Or maybe? JW> Well... I have no idea. What does it mean to share same JW> URL-space? All it means

[Mailman-Users] Re: upgrading from 1.1 to 2.0.8

I upgraded from 1.1 to 2.0.9 on my debian system this afternoon. I downloaded the unstable packages libc6_2.2.5-4_i386.deb and mailman_2.0.9-1_i386.deb from debian.org. These were all I needed to make things work and everything is working just fine. ---

[Mailman-Users] Re: upgrading from 1.1 to 2.0.8

Vik wrote: > > yeah - I did all of this, it worked fine on my test system; I'm just a bit > worried about the current lists on the production system - will it work > with lists (and archives) created by mailman 1? well it *should*. i installed the debian package of 2.0.8 on a woody machine, and

Re: [Mailman-Users] Re: upgrading from 1.1 to 2.0.8

> 1) install the debianutils dpkg-dev and dh-make packages if necessary. > 1.5) edit sources list so that you're getting testing or unstable source > packages. > 2) apt-get source mailman > 3) edit mailman-2.0.8/debian/rules as necessary (i think just commenting > out the dh_installman line is su

[Mailman-Users] Re: upgrading from 1.1 to 2.0.8

Vik wrote: > > Does anyone have any experience doing this (running 2.x on a debian/stable > system)? with a little editing, you can build the unstable package on -stable. i've also built from source on -stable. if you're already using the package, you might want to use the packaged version, sinc

[Mailman-Users] Re: Upgrading

On 2001.01.02, in , "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote: > At 7:24 AM -0500 1/2/01, Gary Wilson wrote: > > >Anyway could someone post the correct link or pass along the information on > >what needs to be done to correctly upgrade from the