On Tue, Nov 14, 2017 at 6:05 PM, Adam Cécile <adam.cec...@hitec.lu> wrote:
> Hi, > > It's usually considered as being a bad practise to put the Debian > packaging itself into the upstream tree because it conflicts with the > "real" packaging if it gets uploaded to Debian. > But that's probably something we can figure out easily (maybe use another > folder name and add hacky step in CI renaming the folder to Debian). > I'm not sure if I understand this. I used to maintain a debian package that was uploaded to debian/ubuntu official repos and there we just kept a `debian` folder inside the source tree (https://github.com/dmtcp/dmtcp). With every upstream release, we updated the debian packaging to reflect an updated version, etc. and that seemed to work fine. However, that was a simpler package to maintain compared to Mesos, so I can imagine concerns around that :). > How would you do that ? Do you have workers running Debian/Ubuntu ? It's > quite easy to create the package for any target (including foreign > architectures, thanks to QEmu userland binary wrapper) but I don't think it > can be done from a RHEL-based worker. > > Yeah, the ASF CI has Ubuntu workers that should work. However, to ensure a sane environment, I would recommend using Debian/Ubuntu containers just like we do for the CentOS builds. That way we can test/run it locally to debug any issues and so on. Does that sound reasonable? > Regards, Adam. > > > On 11/14/2017 11:56 PM, Kapil Arya wrote: > > Hi Adam, > > I am wondering if you would have some time to bring your debian packaging > into Mesos source tree. We can then use the ASF Jenkins CI to build and > publish packages to bintray just like we started doing for CentOS 6/7? This > will also allow the community to more actively participate in maintaining > it in future. > > Best, > Kapil > > On Wed, Sep 13, 2017 at 2:08 PM, Adam Cécile <adam.cec...@hitec.lu> wrote: > >> In case someone's interrested in, I added 1.1.3 debs on my repository: >> >> https://packages.le-vert.net/mesos/ >> >> >> On 09/09/2017 06:40 PM, Adam Cecile wrote: >> >> Hey, >> >> Well that's not really a problem, I can provide 1.1.x packages if your >> interested in. >> >> Regards, Adam. >> >> On September 8, 2017 10:47:23 AM GMT+02:00, Tomek Janiszewski >> <jani...@gmail.com> <jani...@gmail.com> wrote: >>> >>> @Adam Thanks for taking care of this. There is one problem, Mesos 1.1.3 >>> is missing in provided repository. >>> >>> @Kapil What is the status of official Apache Mesos packages? At Mesos >>> Developer Community Meeting (Jan 26, 2017) you presented a proposal for >>> this: https://youtu.be/m7WzKia68Rg >>> >>> wt., 5 wrz 2017 o 15:31 użytkownik Adam Cecile <adam.cec...@hitec.lu> >>> napisał: >>> >>>> On 09/05/2017 11:55 AM, Oskar Jagodziński wrote: >>>> > Hi all, >>>> > >>>> > What is standard interval between release of mesos package and >>>> > 'official' .deb build by Mesosphere? Mesos 1.1.3 was released 11 days >>>> > ago and there is no package at >>>> > https://open.mesosphere.com/downloads/mesos/ only rc-packages >>>> > https://open.mesosphere.com/downloads/mesos-rc/ are up to date. >>>> > >>>> Hello, >>>> >>>> >>>> First, I like to make an important statement: >>>> >>>> *I'm not an official mesosphere guy* >>>> >>>> That being said, Mesosphere package are binary copy of CentOS built file >>>> into a deb container. That's not what I call a Debian package at all and >>>> I already had severe issue with that (libcurl-nss backed built which >>>> does not support https on Debian-based system). >>>> >>>> For this reason, I create my own Mesos package, as a REAL debian >>>> package, built from sources in a clean environment using pbuilder. I >>>> also provide armhf and arm64 build because I've plan for that ;-) >>>> >>>> These package are in-use at three customers place and work just fine. I >>>> provide multiple branches packages and build them with additional >>>> network isolator using libnl and XFS disk isolator. >>>> >>>> >>>> It's available there: >>>> >>>> https://packages.le-vert.net/mesos/ >>>> >>>> Feel free to do what the f*** you want, use the repository directly, >>>> sync it, rebuild debs from sources packages... >>>> >>>> >>>> Regards, Adam. >>>> >>>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> >> >> > >
