|
Hai, > I just checked it. It'll work at the moment. But only because the
dependencies (and the dependency version) doesn't changed from 3.4.8 to 3.5. So
there's is no guarantee that it will work > with further releases. Yes and if depencies change, you can do
the same for these packages, and/or you can change the dependies in the control
file for example. That is what i do, if needed, i change the
control file, so least packages are from sid. And yes, there is always a risk on errors with
future releases, but that risk is always there. > On the other hand: Installing unstable software is not the way the
state system works/should work. I talked to the debian guys. That's exactly the
reason why they don't release squid 3.5 > for jessie but writing patches to
solve critical issues on their own. I do rebuild from sid, i dont install from
sid, that will give a big mess and we dont want that. Since the build also uses configure for
the packages, i dont see the problem here, maybe im missing something, but i do this for years now with squid,
and never had any problems. I use squid 3.5.12 rebuild from sid in
debian Jessie without any problem, and works better for me then 3.4.8. ( I need
the ssl part from 3.5.12+ ) The following is needed to get squid
3.5.12 in Jessie with least changes of the stable packages. squid libecap c-icap and i really dont know why there isnt any
jessie-backported package of this (jet).. since 3.5.12 is in testing since 15
dec 2015. I could not wait for that, so I changed in
debain/rules the following. Added --enable-ssl \
--with-open-ssl=/etc/ssl/openssl.cnf \ --enable-linux-netfilter And changed the changelog. I changed it to the following to keep
track of the debian packages also. squid3 (3.5.12-1lvb1-ssl) unstable;
urgency=medium I only added lvb1-ssl so it can use the
debian packages and/or my own packages. > Then I have to move every software to unstable state (because of
the security) I can install an unstable debian directly. Really, NEVER use sid for production, if
you want to get into troubles, this is the way.. Sid can change rapidly, and put your
server in an un-usable stated, i learned the hard way. Years ago. And for the security, subscribe to the debian
and squid list ( .. done ) and keep track of messages. Greetz, Louis Van: startrekfan
[mailto:startrekfan75@xxxxxxxxxx] I just checked it. It'll work at the moment. But only because the
dependencies (and the dependency version) doesn't changed from 3.4.8 to 3.5. So
there's is no guarantee that it will work with further releases. On the other hand: Installing unstable software is not the way the
state system works/should work. I talked to the debian guys. That's exactly the
reason why they don't release squid 3.5 for jessie but writing patches to solve
critical issues on their own. Then I have to move every software to unstable state (because of the
security) I can install an unstable debian directly. L.P.H. van Belle <belle@xxxxxxxxx>
schrieb am Mo., 18. Jan. 2016 um 09:07 Uhr:
|
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
