On Mon, 25 Jul 2016, David Lang wrote:
On Mon, 25 Jul 2016, David Lang wrote:
On Sun, 24 Jul 2016, Rainer Gerhards wrote:
I assume we're all aware that the lack of Ubuntu package (provided by
Adiscon or someone else, doesn't really matter) is a major barrier in
rsyslog adoption. So I'm thinking that even a ugly/crazy solution
would do, as long as we end up with (reliable) packages. So I think it
would be nice to have all the information needed for anyone to chime
in with ideas and possible solutions. Unless that information is
already somewhere and I missed it... in which case excuse my ignorance
:-S
I fully agree it would be good to fix this, I just honestly don't know
how. And I unfortunately have no time budget left to spend another two
weeks on it. I think to do it right, I would need to learn Ubuntu
packaging from the roots, and that's beyond my current time budget.
:-(
The problem is somewhere in the rsyslog-pkg-ubuntu project, and
related to this script
https://github.com/rsyslog/rsyslog-pkg-ubuntu/blob/master/scripts/auto_daily_project.sh
and the associated control files.
I didn't have time to do my own compiles this development cycle, but I am
also seeing failures building locally using this script/process.
investigating now.
In my first pass, I'm seeing that all the new libraries are being built, but
then when rsyslog goes to compile, old versions of the libraries are being
loaded into the pbuilder image, and so things are failing.
I thought I had things configured so that the pbuilder image also looked at a
local directory as a repository I recreated the index for that repository
between each package that's built so that it will build with the library
versions that I just compiled, but it appears that that didn't work for some
reason this time.
I'm continuing to investigate, starting by updating my pbuilder images.
That was enough to let my build work
rsyslog-pkg-ubuntu# git diff HEAD
diff --git a/scripts/auto_daily_project.sh b/scripts/auto_daily_project.sh
index 1e27081..51f2c1a 100755
--- a/scripts/auto_daily_project.sh
+++ b/scripts/auto_daily_project.sh
@@ -50,10 +50,10 @@ if [ -z "$szPlatform" ]; then
echo "variable szPlatform is unset" | mutt -s "$0 script error"
$RS_NOTIFY_EMAIL
exit
fi
-if [ -z "$PPA" ]; then
- echo "variable PPA is unset" | mutt -s "$0 script error"
$RS_NOTIFY_EMAIL
- exit
-fi
+#if [ -z "$PPA" ]; then
+# echo "variable PPA is unset" | mutt -s "$0 script error"
$RS_NOTIFY_EMAIL
+# exit
+#fi
# $VERSION_FILE must not exist. If it does not exist, an
# error message is emitted (this is OK) and the build is
diff --git a/scripts/config.sh b/scripts/config.sh
index 676d659..a4842df 100644
--- a/scripts/config.sh
+++ b/scripts/config.sh
@@ -2,8 +2,8 @@ PLATFORM="precise trusty vivid wily xenial yakkety"
ARCHTECT="amd64 i386"
BRANCHES="v8-stable v8-stable-testing"
# GPG KEY
-KEY_ID=AEF0CF8E
-PPA=ppa:adiscon
+#KEY_ID=AEF0CF8E
+#PPA=ppa:adiscon
# Mine
# KEY_ID=F6A93574
versions used:
# cat build.config.201607251834
./rsyslog/ branch: * master
./rsyslog/ version: v8.17.0-465-g8684fd2
./liblognorm/ branch: * master
./liblognorm/ version: v2.0.0-7-g22aa93b
./rsyslog-doc/ branch: * master
./rsyslog-doc/ version: v8.3.5-400-g76a53c0
./liblogging/ branch: * master
./liblogging/ version: v1.0.5-12-gb883f16
./librelp/ branch: * master
./librelp/ version: v1.2.12-1-g1ea0d3b
./libestr/ branch: * master
./libestr/ version: v0.1.10-3-gb60d2ce
./rsyslog-pkg-ubuntu/ branch: * master
./rsyslog-pkg-ubuntu/ version: cdc8308
./libfastjson/ branch: * master
./libfastjson/ version: 2fc4c65
./json-c/ branch: * libfastjson
./json-c/ version: b366750
David Lang
_______________________________________________
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.
