Sent from phone, thus brief. Am 22.04.2015 21:16 schrieb "David Lang" <[email protected]>: > > On Wed, 22 Apr 2015, Rainer Gerhards wrote: > >> 2015-04-21 19:50 GMT+02:00 David Lang <[email protected]>: >>> >>> hmm, it looks like there may be some other stuff in your directories that >>> it's accidentially depending on. >>> >>> root@linux-dev01:/usr/src/rsyslog-pkg-ubuntu/rsyslog# cp >>> /usr/src/raw/rsyslog/rsyslog-8.10.0.master.tar.gz . >>> >>> root@linux-dev01:/usr/src/rsyslog-pkg-ubuntu/rsyslog# >>> ../scripts/auto_daily_project.sh trusty v8-devel master >>> >>> >>> cat: LAST_VERSION.master.trusty: No such file or directory >>> rm: cannot remove '*.changes': No such file or directory >>> rm: cannot remove '*.dsc': No such file or directory >>> rm: cannot remove '*.build': No such file or directory >>> rm: cannot remove '*.debian.tar.gz': No such file or directory >>> cp: cannot stat '../trusty/master/debian': No such file or directory >> >> >> These messages are OK. I've just updated my script to do not emit most >> of them. I've also added comments to the script (please review). Along >> that've seen it includes some Adiscon email addreses, you may want to >> change that for now. I'll update that soon, but would like to dig more >> into liblognorm today. >> >>> This package has a Debian revision number but there does not seem to be >>> an appropriate original tar file or .orig directory in the parent directory; >>> (expected one of rsyslog_8.10.0.20150421165741.orig.tar.gz, >>> rsyslog_8.10.0.20150421165741.orig.tar.bz2, >>> rsyslog_8.10.0.20150421165741.orig.tar.lzma, >>> rsyslog_8.10.0.20150421165741.orig.tar.xz or 8.10.0.20150421165741.orig) >>> continue anyway? (y/n) y >> >> >> Mhhh, this should have been handled properly. Can you send me a full >> log of the run, including executed comments (set -o xtrace). I would >> need to set up a brand-new VM, and again I'd really like to look at >> liblognorm instead... > > > Ok, this is looking pretty good. It now builds and now complains about the signatures. I did the attached modification to my system to avoid it trying to sign things and upload them to launchpad (and not delete the resulting file)
The actual package build happens on launchpad. So without a ppa, this all doesn't make much sense. Then you probably better check the Debian project. I think the build process is identical, but that's all I know... Rainer > > This creates some files, but not the packages I was expecting, still digging. > > David Lang > > >> I've also asked Florian to look into your other questions and add some >> comments to the package. That'llbe breif, though, as much of it will >> no longer be true in the not so distant future. As I said, we are >> working on changing the process, and it is great to have someone >> outside of Adiscon using the scripts so we can really see what it >> takes to make them more generic. >> >> Rainer >> >>> dpkg-buildpackage -rfakeroot -d -us -uc -S -sa >>> dpkg-buildpackage: warning: using a gain-root-command while being root >>> dpkg-buildpackage: source package rsyslog >>> dpkg-buildpackage: source version 8.10.0.20150421165741-0adiscon1trusty >>> dpkg-buildpackage: source distribution trusty >>> dpkg-buildpackage: source changed by Adiscon package maintainers >>> <[email protected]> >>> dpkg-source --before-build 8.10.0.20150421165741 >>> dpkg-source: info: applying 01-dont_create_db.patch >>> fakeroot debian/rules clean >>> dh clean --with autoreconf >>> dh_testdir >>> dh_auto_clean >>> dh_autoreconf_clean >>> dh_clean >>> dpkg-source -b 8.10.0.20150421165741 >>> dpkg-source: error: can't build with source format '3.0 (quilt)': no >>> upstream tarball found at >>> ../rsyslog_8.10.0.20150421165741.orig.tar.{bz2,gz,lzma,xz} >>> dpkg-buildpackage: error: dpkg-source -b 8.10.0.20150421165741 gave error >>> exit status 255 >>> debuild: fatal error at line 1364: >>> dpkg-buildpackage -rfakeroot -d -us -uc -S -sa failed >>> >>> >>> On Tue, 21 Apr 2015, Rainer Gerhards wrote: >>> >>>> Date: Tue, 21 Apr 2015 19:05:29 +0200 >>>> From: Rainer Gerhards <[email protected]> >>>> Reply-To: rsyslog-users <[email protected]> >>>> To: rsyslog-users <[email protected]> >>>> Subject: Re: [rsyslog] looking for an example of using rsyslog-pkg-ubuntu >>>> scripts >>>> >>>> >>>> I can only speak for the daily scripts: they require exactly one tar file >>>> in the base directory, the result of make dist. >>>> >>>> Sent from phone, thus brief. >>>> Am 21.04.2015 19:01 schrieb "David Lang" <[email protected]>: >>>> >>>>> On Tue, 21 Apr 2015, Rainer Gerhards wrote: >>>>> >>>>> 2015-04-20 22:39 GMT+02:00 David Lang <[email protected]>: >>>>>> >>>>>> >>>>>> >>>>>>> these look like really useful scripts, but I'm having trouble >>>>>>> reverse-engineering them to figure out what needs to be where to make >>>>>>> them >>>>>>> work. >>>>>>> >>>>>> >>>>>> I don't have the details, but most of them are in a state of "great, >>>>>> it worked", so it's not very fine-tuned. As a side-activity, I am >>>>>> making changes to the scripts. Florian (out of office today) can >>>>>> probably comment better on the current status. >>>>>> >>>>>> Note that I have streamlined the scripts for the daily builds. These >>>>>> daily build scripts are in ./scripts/auto_daily* and are probably a >>>>>> better starting point to understand the structure. Note that the >>>>>> package build control files resides in different directories and there >>>>>> is a lot of (uncessary) duplication. That duplication will hopefully >>>>>> change soon. >>>>>> >>>>>> Rainer >>>>>> >>>>>> At one point it seems to be using the results of 'make dist' but at >>>>>> other >>>>>>> >>>>>>> >>>>>>> places it seems to be requiring an upstream source tarball. >>>>>>> >>>>>> >>>>> I'm still tripping over this problem >>>>> >>>>> This package has a Debian revision number but there does not seem to be >>>>> an appropriate original tar file or .orig directory in the parent >>>>> directory; >>>>> (expected one of rsyslog_8.10.0.20150421165741.orig.tar.gz, >>>>> rsyslog_8.10.0.20150421165741.orig.tar.bz2, >>>>> rsyslog_8.10.0.20150421165741.orig.tar.lzma, >>>>> rsyslog_8.10.0.20150421165741.orig.tar.xz or 8.10.0.20150421165741.orig) >>>>> continue anyway? (y/n) >>>>> >>>>> and if I say yes >>>>> >>>>> dpkg-source: error: can't build with source format '3.0 (quilt)': no >>>>> upstream tarball found at >>>>> ../rsyslog_8.10.0.20150421165741.orig.tar.{bz2,gz,lzma,xz} >>>>> dpkg-buildpackage: error: dpkg-source -b 8.10.0.20150421165741 gave error >>>>> exit status 255 >>>>> debuild: fatal error at line 1364: >>>>> >>>>> >>>>> what is it wanting in this file it's looking for? is it the results of >>>>> make dist? is it a tar of the git working directory? something else? does >>>>> it matter which version of code is in this tarball? >>>>> >>>>> 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. >>>>> >>>> _______________________________________________ >>>> 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. >> >> _______________________________________________ >> 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. _______________________________________________ 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.
