Hi all - especially Slavec and Tim :-)
I don't know if somebody is on the devuan mailinglist, so I'll place this link here: https://lists.dyne.org/lurker/message/20171214.132959.b8c0d989.en.html
Could TDE provide official packages or a an official repository for devuan ascii, as KatolaZ ( KatolaZ katolaz@freaknet.org ) is asking for (see posting below)?
As fas as I can tell, Slavecs repository has been stable for ages now, and it works perfectly with ascii. So ... take the chance?
Nik
Am Donnerstag, 14. Dezember 2017 schrieb KatolaZ:
On Thu, Dec 14, 2017 at 03:17:22PM +0100, Dr. Nikolaus Klepp wrote:
[cut]
During the sprint, you might also be asked to try/test/check theming material, new packages, provisional installation material, and the like. Thanks in advance for any help you will be able to provide.
Come on: let's put ASCII out.
The Dev1Devs
@ KDE: KDE3 continued as TDE aka trinitydesktop.org https://trinitydesktop.org/ works perfect on jessie. It would be very nice, if it could be included as an alternative DE for all those who like KDE3 but dislike all newer KDE incarnations and the GTK3-stuff.
Hi,
I agree, but this just depends on the availability of the TDE team to package it for Devuan. I don't think we have the workforce to do that, atm.
Hope this makes sense.
KatolaZ
Hi Nik,
Devuan Ascii is the equivalent of Debian Stretch. Currently, TDE official packages for Debian Stretch are not yet available. For now, the only option is to use Preliminary Stable Builds repository. And the same repository can also be used for Devuan - packages for Debian can be used on Devuan without modification. See:
https://wiki.trinitydesktop.org/DevuanInstall https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
There is one new information: Now you can use the mirror of Preliminary Stable Builds repository located on the official TDE server! Instead of http://mirror.xcer.cz/trinity-sb you can now use http://mirror.ppa.trinitydesktop.org/trinity-sb
Is this information sufficient for this moment?
Cheers
Hi Slavek,
Am Donnerstag, 14. Dezember 2017 schrieb Slávek Banko:
Hi Nik,
Devuan Ascii is the equivalent of Debian Stretch. Currently, TDE official packages for Debian Stretch are not yet available. For now, the only option is to use Preliminary Stable Builds repository. And the same repository can also be used for Devuan - packages for Debian can be used on Devuan without modification. See:
https://wiki.trinitydesktop.org/DevuanInstall https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
There is one new information: Now you can use the mirror of Preliminary Stable Builds repository located on the official TDE server! Instead of http://mirror.xcer.cz/trinity-sb you can now use http://mirror.ppa.trinitydesktop.org/trinity-sb
Is this information sufficient for this moment?
Cheers
I've switched to mirror.ppa.trinitydesktop.org, thank you.
Now this is where I have some problems with my workflow:
I cloned "tde-packaging", switched to r14.0.x. Then I cloned "tqt3", "cd tqt3", "cp ../tde-packaging/debian/squeeze/dependencies/tqt3/debian .". Now "debuild -b -uc -us" builds the packages without errors.
Is this the intend way to build debian packages or is there a beter way?
I ask, because if I understand the devuan build process correct ( https://dev1galaxy.org/viewtopic.php?id=549 ), then I have to build a repository per subproject with "tde"+"tde-packaging" merged togather. No big deal, but could get interesting :-)
Nik
Dr. Nikolaus Klepp wrote:
I cloned "tde-packaging", switched to r14.0.x. Then I cloned "tqt3", "cd tqt3", "cp ../tde-packaging/debian/squeeze/dependencies/tqt3/debian .". Now "debuild -b -uc -us" builds the packages without errors.
Is this the intend way to build debian packages or is there a beter way?
yes this is the way I use also.
I asked for automated build scripts and Michele mentioned something about making such public, but I don't know what happened. I wrote one big Makefile that I used to build the packages with their dependencies, but its rather fast and dirty solution - so I prefer not to show it :)
However you are on the right path if you stick to the base version - i.e. you rebuild packages that are same branch that you are on. Example 14.0.5/14.0.5. You'll probably have issues if you build 14.1.0 and run them on base 14.0.5 and you'll need to rebuild dependencies too.
I was intending to setup repo for 14.1 (DEVELOPMENT), but did not find time so far to read the howto. However it might be that after I migrate my build machine I could also find some time to do this around or after Christmas. I've been using this for almost an year now without problems.
regards
Hi deloptes!
Am Freitag, 15. Dezember 2017 schrieb deloptes:
Dr. Nikolaus Klepp wrote:
I cloned "tde-packaging", switched to r14.0.x. Then I cloned "tqt3", "cd tqt3", "cp ../tde-packaging/debian/squeeze/dependencies/tqt3/debian .". Now "debuild -b -uc -us" builds the packages without errors.
Is this the intend way to build debian packages or is there a beter way?
yes this is the way I use also.
I asked for automated build scripts and Michele mentioned something about making such public, but I don't know what happened. I wrote one big Makefile that I used to build the packages with their dependencies, but its rather fast and dirty solution - so I prefer not to show it :)
However you are on the right path if you stick to the base version - i.e. you rebuild packages that are same branch that you are on. Example 14.0.5/14.0.5. You'll probably have issues if you build 14.1.0 and run them on base 14.0.5 and you'll need to rebuild dependencies too.
I was intending to setup repo for 14.1 (DEVELOPMENT), but did not find time so far to read the howto. However it might be that after I migrate my build machine I could also find some time to do this around or after Christmas. I've been using this for almost an year now without problems.
regards
Ok, I see. Well, I would like to stay with 14.0.5 till 14.1 is official. I tried to figure out a way how I can integrate the TDE sources in the devuan build infrastructue. This is how far I have come with the official available parts (example just for the tqt3):
"apt-get source libtqt3-headers" downloads "tqt-x11-free-14.0.5~pre5", which will result in packages named e.g. "libtqt3-mt_14.0.5~pre5-0debian9.0.0+1_amd64.deb". The package name that is in the repository is "libtqt3-mt_4%3a14.0.5~pre5-0debian9.0.0+1_amd64.deb" - so not that far off what the source package creates. The "same" sources obtained via git "git clone --recursive https://scm.trinitydesktop.org/scm/git/tqt3; cd tqt3; git checkout r14.0.x" and then copied over the "debian"-folder from tde-packaging creates packages named "libtqt3-mt_3.3.8-d-0ubuntu0_amd64.deb" - which I did not expect to happen. That leads to the conclusion, that both ways will end in a usable way of integrating the sources into devuan infrastructure.
Let's dig deeper :-)
"tqt-x11-free-14.0.5~pre5/debian/changelog" implies, that there should be a perfectly fine git repository for integration in devuan:
tqt-x11-free (4:14.0.5~pre5-0debian9.0.0+1) stretch; urgency=low
* Automated git build for a944a8634fc7472ffd40e22cd5848a9b027c7b36
-- Slávek Banko slavek.banko@axis.cz Sun, 30 Jul 2017 10:54:45 +0200
This git repository (wherever it may be) is most likely the perfect starting poinz for what I need. The procedure lined out by KatolaZ here ( https://dev1galaxy.org/viewtopic.php?id=549 ) does not sound that much demanding, when there is an upstream git repository that receives all the patches. The only work to be done right now is "copy the sources" (which is quite straightforward) and "get the naming right to devuan instead of debian" (dhich is handled by the d1h helper program).
So ... this is exactly what I'd like to do: get TDE into devuan ASCII. Now I'm asking Slavek the repository to make that happen :-)
Nik
Dr. Nikolaus Klepp wrote:
The "same" sources obtained via git "git clone --recursive https://scm.trinitydesktop.org/scm/git/tqt3; cd tqt3; git checkout r14.0.x" and then copied over the "debian"-folder from tde-packaging creates packages named "libtqt3-mt_3.3.8-d-0ubuntu0_amd64.deb" - which I did not expect to happen. That leads to the conclusion, that both ways will end in a usable way of integrating the sources into devuan infrastructure.
I think the sources changelog was either for ubuntu or for debian kde. Custom version or maintainer mode is needed.
regards
Hi! Am Samstag, 16. Dezember 2017 schrieb deloptes:
Dr. Nikolaus Klepp wrote:
The "same" sources obtained via git "git clone --recursive https://scm.trinitydesktop.org/scm/git/tqt3; cd tqt3; git checkout r14.0.x" and then copied over the "debian"-folder from tde-packaging creates packages named "libtqt3-mt_3.3.8-d-0ubuntu0_amd64.deb" - which I did not expect to happen. That leads to the conclusion, that both ways will end in a usable way of integrating the sources into devuan infrastructure.
oops, my typo: should be "unusable" instead of "usable"
I think the sources changelog was either for ubuntu or for debian kde. Custom version or maintainer mode is needed.
regards
That makes sense, as the changelog comes with the debian source package. Just where to get a copy or how to make it to "maintainer mode"?
Nik
I asked for automated build scripts and Michele mentioned something about making such public, but I don't know what happened. I wrote one big Makefile that I used to build the packages with their dependencies, but its rather fast and dirty solution - so I prefer not to show it :)
Hi Emanoil (and others), Slavek and I have done some work on this, but again stopped for lack of time or for other priorities :-( We are more focused on releasing Slavek's scripts at the moment, which support building for multiple distros at the same time and in automated way. I can make my scripts available "as they are" if you want, perhaps with a little explanation coming together. Nevertheless I use a different packaging convention than the "standard" TDE packages, although it should not be too difficult to adapt them. These scripts are more focused on local builds (one distro at a time - again they could be adapted if needed) and allows to build package with a simple one line command (in fact the whole TDE could be built with a single command). Let me know if you are interested in them :-) Cheers Michele
Hi Michele,
Am Sonntag, 17. Dezember 2017 schrieb Michele Calgaro:
I asked for automated build scripts and Michele mentioned something about making such public, but I don't know what happened. I wrote one big Makefile that I used to build the packages with their dependencies, but its rather fast and dirty solution - so I prefer not to show it :)
Hi Emanoil (and others), Slavek and I have done some work on this, but again stopped for lack of time or for other priorities :-( We are more focused on releasing Slavek's scripts at the moment, which support building for multiple distros at the same time and in automated way. I can make my scripts available "as they are" if you want, perhaps with a little explanation coming together. Nevertheless I use a different packaging convention than the "standard" TDE packages, although it should not be too difficult to adapt them. These scripts are more focused on local builds (one distro at a time - again they could be adapted if needed) and allows to build package with a simple one line command (in fact the whole TDE could be built with a single command). Let me know if you are interested in them :-) Cheers Michele
That would be a great help!
Nik
On 2017/12/17 04:59 PM, Dr. Nikolaus Klepp wrote:
Hi Michele,
Am Sonntag, 17. Dezember 2017 schrieb Michele Calgaro:
I asked for automated build scripts and Michele mentioned something about making such public, but I don't know what happened. I wrote one big Makefile that I used to build the packages with their dependencies, but its rather fast and dirty solution - so I prefer not to show it :)
Hi Emanoil (and others), Slavek and I have done some work on this, but again stopped for lack of time or for other priorities :-( We are more focused on releasing Slavek's scripts at the moment, which support building for multiple distros at the same time and in automated way. I can make my scripts available "as they are" if you want, perhaps with a little explanation coming together. Nevertheless I use a different packaging convention than the "standard" TDE packages, although it should not be too difficult to adapt them. These scripts are more focused on local builds (one distro at a time - again they could be adapted if needed) and allows to build package with a simple one line command (in fact the whole TDE could be built with a single command). Let me know if you are interested in them :-) Cheers Michele
That would be a great help!
Nik
Sure, no problem Nik. Since today I have some free time, I have started to polish them up and adapt them to be used in a more generic way. Not too many changes, but since I think this could be useful to several people, it could be worth to add them to the packaging repo so that anyone interested can get them easily. I will try to finish everything by Christmas if I can :-) Cheers Michele
On 2017/12/17 05:59 PM, Dr. Nikolaus Klepp wrote:
Hi Michele,
Am Sonntag, 17. Dezember 2017 schrieb Michele Calgaro:
I asked for automated build scripts and Michele mentioned something about making such public, but I don't know what happened. I wrote one big Makefile that I used to build the packages with their dependencies, but its rather fast and dirty solution - so I prefer not to show it :)
Hi Emanoil (and others), Slavek and I have done some work on this, but again stopped for lack of time or for other priorities :-( We are more focused on releasing Slavek's scripts at the moment, which support building for multiple distros at the same time and in automated way. I can make my scripts available "as they are" if you want, perhaps with a little explanation coming together. Nevertheless I use a different packaging convention than the "standard" TDE packages, although it should not be too difficult to adapt them. These scripts are more focused on local builds (one distro at a time - again they could be adapted if needed) and allows to build package with a simple one line command (in fact the whole TDE could be built with a single command). Let me know if you are interested in them :-) Cheers Michele
That would be a great help!
Nik
Just thought of providing an update on this. Work is in progress to release building scripts for building TDE on a single machine for debian/ubuntu and even create a local repository for your distro if you wish. It is progressing slowly because I don't have as much time to dedicate to TDE as I used to do until a year ago, but it is progressing. There are several changes required to make the scripts more user friendly, to switch to the standard package name format used for TDE packages (I use a different naming convention on my machine) and to build for the various debian/ubuntu versions. We (Slavek and I) are going through them and try to test them properly, so it is taking some time.
Happy New Year to all!!
Cheers Michele
-
deloptes -
Dr. Nikolaus Klepp -
Michele Calgaro -
Slávek Banko