Thanks for your hard work in this, indeed packaging is complicated (I tried to build myself the 8.20 and was quite difficult). I would be content if packages were provided only in the xenial (if that would be easier for you), I'm in the process of upgrading my servers, and many people must be in the process also.
2016-07-22 8:08 GMT+02:00 Rainer Gerhards <[email protected]>: > IF YOU USE THE ADISCON PPAs, YOU ***MUST*** READ THIS. YOUR SYSTEMS > WILL BREAK IN THE LONGER TERM. > > Hi all, > > I regret to announce that we need to discontinue providing current > Ubuntu packages (Adiscon PPAs) for the time being. > > The reason simply is that we do not get them up and running. I tried > for almost two weeks now, but without any success. Sometimes they work > on some platforms (like trusty), but fail on others. Sometimes the > fail on all platforms. The problem seems to be rooted in the new > libfastjson release, but even after using verbatim copies of Michael > Biebl's debian control files, I can't come to a state where all > packages works. I have to admit that I do not have the slightest idea > of why the fail; I tried various things but nothing worked out. The > root cause seems to be that -fPIC is missing on the libfastjson build, > which causes other components (liblognorm) to fail during the linking > step (I see this both in package build as well as CI). However, I have > even given the -fPIC option explicitely without experiencing any > change in behaviour. A typical error looks like this: > > > https://launchpadlibrarian.net/274413157/buildlog_ubuntu-trusty-amd64.liblognorm_2.0.0~20160722053734-0adiscon1trusty_BUILDING.txt.gz > > For almost two weeks, I focussed all my rsyslog work on the packages. > I don't think it makes sense to continue with that, especially as all > other work is blocked. So I decided to discontinue the packages for > now. I may be able to have a fresh look around mid of september/begin > of october, but that needs to be seen. > > Again, I regret this move, but it doesn't help to provide a PPA that > does not work and it also is not a useful option to completely stop > development of other components in order to become a packaging expert. > After all that I know and have read, the packages should work just as > they are. But they don't do... > > As a next step, I will change the CI envionment (most notably travis) > so that it will return back to working state, and either change or > switch off those parts that depend on the PPA repository. > > We keep the existing PPA online, and we may even partially update it > (we will investigate this possibility today or monday). In the long > term, please switch to your own PPA, as we will most probably remove > the Adiscon PPA completely by the end of the year if we can't find a > solution. We may remove it earlier if there is a good reason for it > (e.g. a security vulnerability which would require a rebuild of a > component that we cannot build). > > As it looks, we do not experience similar problems with the Centos and > debian repos. We will hopefully be able to restore them to full > operation with current versions next week or the week after. > > Thanks, > Rainer > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
