Re: [Mailman-Users] bin/upgrade has been broken since 2.1.5 (orpossibly longer)
![](https://secure.gravatar.com/avatar/457538a2d31f6f54724e0a6ffd687e86.jpg?s=120&d=mm&r=g)
Knut Auvor Grythe <knut@auvor.no> wrote, in part,
Are you installing from source or using the Debian/Ubuntu package? If the latter, remember that there are a number of Debian/Ubuntu patches applied to the source. When I looked at the patches, I was not sure what many of them did, and I was not sure of the code base upon which these patches were built. IIRC, one patch referred to 2.1.4 code. That is why I built my own package from the SourceForge source; my management would not let me install the source without a package.
Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel@anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994
![](https://secure.gravatar.com/avatar/0bfd37fe00a9dfbfa075c1f6a7abdbe9.jpg?s=120&d=mm&r=g)
On Fri, Sep 19, 2008 at 07:46:25AM -0500, Barry Finkel wrote:
I am aware of that. I therefore verified that the vanilla source had the same bug. Perhaps I shouldn't have mentioned Ubuntu at all, that sidenote seems to only throw people off.
We're not using Ubuntu because we're newbies. We're using it because Ubuntu has predictable release cycles which allows us to schedule upgrades in a proper way, and Debian doesn't. I'd never report a bug in Mailman without verifying that the bug indeed is in Mailman and not the Ubuntu packaging.
We've never had any problems with mailman itself due to patches from Ubuntu. We have had other issues though, like for instance with the logrotate script in their package, but nothing bad enough to justify the overhead of keeping a local package updated.
I agree with your management there :-)
-- Knut Auvor
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
Knut Auvor Grythe wrote:
We appreciate that, we really do!
Regretfully, you are one of the very few rare cases where someone is reporting a problem on a particular platform, and where you've actually gone and checked to make sure that the bug you're reporting is with the underlying software and not the local package. So, I hope you're not too offended when we ask the question.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
![](https://secure.gravatar.com/avatar/0bfd37fe00a9dfbfa075c1f6a7abdbe9.jpg?s=120&d=mm&r=g)
On Fri, Sep 19, 2008 at 07:46:25AM -0500, Barry Finkel wrote:
I am aware of that. I therefore verified that the vanilla source had the same bug. Perhaps I shouldn't have mentioned Ubuntu at all, that sidenote seems to only throw people off.
We're not using Ubuntu because we're newbies. We're using it because Ubuntu has predictable release cycles which allows us to schedule upgrades in a proper way, and Debian doesn't. I'd never report a bug in Mailman without verifying that the bug indeed is in Mailman and not the Ubuntu packaging.
We've never had any problems with mailman itself due to patches from Ubuntu. We have had other issues though, like for instance with the logrotate script in their package, but nothing bad enough to justify the overhead of keeping a local package updated.
I agree with your management there :-)
-- Knut Auvor
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
Knut Auvor Grythe wrote:
We appreciate that, we really do!
Regretfully, you are one of the very few rare cases where someone is reporting a problem on a particular platform, and where you've actually gone and checked to make sure that the bug you're reporting is with the underlying software and not the local package. So, I hope you're not too offended when we ask the question.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
participants (3)
-
b19141@anl.gov
-
Brad Knowles
-
Knut Auvor Grythe