Re: sendmail libc6 [was: Squid2, how to handle incompatible upgrade]
Miquel van Smoorenburg [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: The only pain I had to face was that I had to upgrade my libc6 and that upgrade broke sendmail, so I had to upgrade sendmail as well. Uh - oh .. please check out this bug: #27334: libc6: breaks sendmail, probably problem in resolver details at http://www.debian.org/Bugs/db/27/27334.html This is release-critical, IMO. I agree this is release critical. However, the problem went away when I upgraded to the sendmail in Slink (8.9.1, I think). Before that, I was using the sendmail in Hamm. I did not downgraded my libc6. peloy.-
Re: sendmail libc6 [was: Squid2, how to handle incompatible upgrade]
In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: Miquel van Smoorenburg [EMAIL PROTECTED] wrote: #27334: libc6: breaks sendmail, probably problem in resolver details at http://www.debian.org/Bugs/db/27/27334.html This is release-critical, IMO. I agree this is release critical. However, the problem went away when I upgraded to the sendmail in Slink (8.9.1, I think). Before that, I was using the sendmail in Hamm. I did not downgraded my libc6. I had this problem with sendmail-8.9.1-x and libc6_2.0.7u-2. Only downgrading to libc6_2.0.7t-1 helped. Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
sendmail libc6 [was: Squid2, how to handle incompatible upgrade]
In article [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: The only pain I had to face was that I had to upgrade my libc6 and that upgrade broke sendmail, so I had to upgrade sendmail as well. Uh - oh .. please check out this bug: #27334: libc6: breaks sendmail, probably problem in resolver details at http://www.debian.org/Bugs/db/27/27334.html This is release-critical, IMO. Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
Re: Squid2, how to handle incompatible upgrade
Miquel van Smoorenburg [EMAIL PROTECTED] wrote: Never mind - I forgot how I handled it the last time, from the 1.0 to the 1.1 upgrade. Just test in the preinst for the previous version and show a warning, upgrade instructions and a prompt there. Seemed to work the last time .. so it will probably work this time as well. Hi Mike, I downloaded your squid-2 package and installed it in our production server and everything seems to be running smoothly. The only pain I had to face was that I had to upgrade my libc6 and that upgrade broke sendmail, so I had to upgrade sendmail as well. Other than that, the new squid.conf was easy to set up (provided that my squid 1.2 squid.conf file was in good shape). Thanks! peloy.-
Squid2, how to handle incompatible upgrade
I'm currently maintaining squid, and squid-2.0 has been released. We have been running the beta versions on our own machines for quite some time and it's much better/faster than the 1.2 versions. However the problem is dat squid-2.0 is totally incompatible with squid-1.2. The cache directory and file format has changed, and the config file format has changed .. in fact it's a new package. How do I handle this? Should I just make a new package squid2 that conflicts with squid-1.2? If I do that, I have the problem that the squid source package creates 4 binary packages. Should I do a new upload of the latest squid-1.2 with only the squid .deb, and upload the rest with squid2? Hmm I've formulated the above as questions, but I plan to do this soon (before the freeze) if nobody objects. Or has a better idea, ofcourse! Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
Re: Squid2, how to handle incompatible upgrade
In article [EMAIL PROTECTED], Miquel van Smoorenburg [EMAIL PROTECTED] wrote: However the problem is dat squid-2.0 is totally incompatible with squid-1.2. The cache directory and file format has changed, and the config file format has changed .. in fact it's a new package. Never mind - I forgot how I handled it the last time, from the 1.0 to the 1.1 upgrade. Just test in the preinst for the previous version and show a warning, upgrade instructions and a prompt there. Seemed to work the last time .. so it will probably work this time as well. Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
Re: Squid2, how to handle incompatible upgrade
[EMAIL PROTECTED] (Miquel van Smoorenburg) writes: Never mind - I forgot how I handled it the last time, from the 1.0 to the 1.1 upgrade. Just test in the preinst for the previous version and show a warning, upgrade instructions and a prompt there. Seemed to work the last time .. so it will probably work this time as well. This sounds fine to me. I'm looking forward to squid2. I did notice a reference on the mailing list (no specifics), on a way you could keep your existing cache hierarchy with squid2. Mike.
Re: Squid2, how to handle incompatible upgrade
On 8 Oct 1998, Miquel van Smoorenburg wrote: In article [EMAIL PROTECTED], Miquel van Smoorenburg [EMAIL PROTECTED] wrote: However the problem is dat squid-2.0 is totally incompatible with squid-1.2. The cache directory and file format has changed, and the config file format has changed .. in fact it's a new package. Never mind - I forgot how I handled it the last time, from the 1.0 to the 1.1 upgrade. Just test in the preinst for the previous version and show a warning, upgrade instructions and a prompt there. Seemed to work the last time .. so it will probably work this time as well. sounds good to me. btw, i'm already using your squid 1.2-beta23-1 package on several machines. works well. craig -- craig sanders
Re: Squid2, how to handle incompatible upgrade
Miquel van Smoorenburg wrote: I'm currently maintaining squid, and squid-2.0 has been released. We have been running the beta versions on our own machines for quite some time and it's much better/faster than the 1.2 versions. However the problem is dat squid-2.0 is totally incompatible with squid-1.2. The cache directory and file format has changed, and the config file format has changed .. in fact it's a new package. How do I handle this? Should I just make a new package squid2 that conflicts with squid-1.2? I would'n't like to introduce a new set of packages. You should however ensure that the old configuration file is saved. Wrt. spool file: I believe that it is acceptable to blow the old spool away if the new squid gains more speed. If I do that, I have the problem that the squid source package creates 4 binary packages. Should I do a new upload of the latest squid-1.2 with only the squid .deb, and upload the rest with squid2? Depends on the purpose of the other packages... Regards, Joey -- The only stupid question is the unasked one.
Re: Squid2, how to handle incompatible upgrade
In article [EMAIL PROTECTED], Michael Alan Dorman [EMAIL PROTECTED] wrote: I did notice a reference on the mailing list (no specifics), on a way you could keep your existing cache hierarchy with squid2. Yes, by running the old and the new server at the same time and requesting all stored data from the old cache .. something that's pretty much impossible for our situation. Besides it only works if you have plenty of free space, and it would probably take hours if not days for a big cache . Hey it's just cached data .. Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
