[How to install using pre-compiled packages]

1 minute ago, Thulium said:

That was my bad, I changed the text to reflect the correct name, but the actual link was pointing at the internal hostname. I fixed the link, try again :-)

That worked.  Thanks.  I look forward to your friend releasing that script, or someone possibly making a "proper" debian/ subfolder in the git project for easier debian packaging.

[How to install using pre-compiled packages]

Hmm.  I get that I can't find an IP to that name.

I'm based in the US in case that matters.

[How to install using pre-compiled packages]

13 minutes ago, Thulium said:

I took a look, but I take it you would like to have the original uncompiled git source in those packages? My current setup doesn't really allow for this. It does the following:

- Maintain a local copy of the repo (the 'meta' script that builds trinitycore runs 'git pull' before compiling)
- Build the software according to the build recipe I defined
- Package the software according to the package recipe
- Push the resulting package to the repo

This allows me to save a lot of disk space (I only have 1 copy of the source per branch), and it *should* be possible to redo any older builds by checking out that version in git.

I'm using a script a colleague made, I will link it in the post once he posted in on Github (it's on his todo-list). So that part of this setup I cannot share, as it is not my work.

However, I'm cool with sharing the recipes I made for the build script (see attachment). But I do ask that if you make improvements/changes to let me know. So I can incorporate them in the scripts I use.

I also just updated the build script to look for the correct version of the TDB when the source files mention it ;-)

trinitycore-recipes.tgz

Thanks.  I think this file is what I'm looking for.  Too bad I can't seem to reach it.  Maybe I'm trying to fetch it too soon?

[How to install using pre-compiled packages]

1 hour ago, Thulium said:

Edit: oh, btw, I missed that question, what kind of sources would you like to know/have? I've only followed the original compilation instructions :-)

Cheers!

What I'd be happy with is the tarball of the debian/ subdirectory you used for making these packages.

But if you are willing to go a step further and make source_version.orig.tar.gz and then do "dpkg-source -b trinitycore-version/" to create the source packages, that'd be great.  I was able to manually fetch the .deb files from your repository.

Another thing to consider:  launchpad.net allows you to create recipes combining your work with the original git repository (I still haven't learned how to do this myself).  You could go this route and make it so that the sources are compiled by a remote machine for different architectures with little effort.  I think Debian has a similar repository you can do this with as well.

[How to install using pre-compiled packages]

Is there any chance you'll also include the source debian mixings into the repository?  Also, I am having some problems with apt-get update:

Reading package lists... Done
E: Failed to fetch http://repo.element-networks.nl/dists/custom/Release  No Hash entry in Release file /var/lib/apt/lists/partial/repo.element-networks.nl_dists_custom_Release which is considered strong enough for security purposes
E: Some index files failed to download. They have been ignored, or old ones used instead.
root@taz:~/#

I'm using Ubuntu 16.04 LTS 64-bit.