Jump to content
The Dark Mod Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About coldtobi

  • Rank
  1. Sorry, I'm not involved in Mint development (/me Debian Developer) But what you can try, as Mint is Ubuntu based and Ubuntu is Debian based, to rebuild the package locally on your machine: # Disclaimer: not tested, typed out of memory. sudo apt install devscripts # not sure if this package exists in mint, but this will allow you to verify the signature on the sources sudo apt install debian-keyring mkdir darkradiant_builddir cd darkradiant_builddir dget -x https://deb.debian.org/debian/pool/main/d/darkradiant/darkradiant_2.11.0-1.dsc # if you could not install debian-keyring, you can
  2. And it has been uploaded to Debian (unstable) already! Soon to be available on a Debian mirror near you!
  3. No worry, Debian 9 ("Stretch") will have at least version 2.1.0. Bugfixes for a stable are possible, but only to fix (severe) problems (like that what I described for Ubuntu in the boost::python thread) New versions, though, are generally out of scope -- Even if it would fix a (severe) problem; the fix would be "backported" to the old version instead. Tobi
  4. Hi greebo, do you have some release date in mind? (Debian's freeze is approaching [1] -- so if it is ready by mid-Jan* I'll make sure to upload in time ) [1] https://lists.debian.org/debian-devel-announce/2016/11/msg00002.html -- * It has to be uploaded >10 days before freeze -- deadline around Jan 25, but I also need a few days on my side. -- tobi
  5. Debian's repository is based on the release tarballs (importing them into the repository with git-buildpackage), so there is no direct relation between your and the repository I use.. This is probably the reason why it won't merge However, I can try to come up with a PR to bring up the debian/ accordingly, but this will take me a while due to some imminent buisiness trip.. See also below. I understand your requirement... However, I'd discourage to recycle version numbers.. Some ideas: Maybe something like git-describe* to generate some version string at build time, at least when there i
  6. (This in reference to http://bugs.thedarkmod.com/view.php?id=4360 where greebo and I discussed already and then decided to move the thread over here.) Quoted here again for conveniene greebo: tobi: greebo: (I will follow up later)
  7. Hi Nightcrawler, I don't know about the release policy of Ubuntu in detail (as I'm a Debian Dev), but a quick search on the net shows that they're doing it like Debian [1]: Fixes are only done to correct severe problems. While a crash is one, I guess it will still be out of scope for Ubuntu to update... As I'm pretty sure that boost::python is causing this crash, so we'd need to find and fix that boost::python problem and patch it in the very specific version that has been used in xenial. As it seems that this bug is not exposed widely, I guess the release managers won't be happy if we'd a
  • Create New...