SPEC files and Debian directory to build own packages #243

ruben-herold · 2017-04-25T15:10:34Z

hi,

this will be no real bug only a wish. It would be nice to have a spec file for rpm based distributions
or an example debian directory for debian based distributions to build own packages.

ydahhrk · 2017-04-25T15:48:44Z

(My hands are a little full right now. Will read docs and respond to this properly in about 48 hours.)

ruben-herold · 2017-04-27T09:03:35Z

No Problem :-)

ydahhrk · 2017-04-27T22:42:28Z

Ok,

@TheRedTrainer is working on this.

Debian documentation states that kernel modules are considered "high complexity packages" and we've never done this before so I personally would not expect this to be done in less than a month.

He will be working in both packaging frameworks (RPM and Debian).

@TheRedTrainer: DKMS might simplify this.

ruben-herold · 2017-05-01T16:20:16Z

I can test centos 7 packages

TheRedTrainer · 2017-05-22T20:45:04Z

I've created a new branch for this issue ( #issue243 ) including the jool-dkms-mkdeb and jool-dkms-mkdsc folders that contain the Makefile and debian files (control, postinst, copyright, changelog, rules, etc. ) required by DKMS to build the deb and dsc packages for debian based linux distributions. I also included the SPEC file for RPM packages.

The packages created using these files install the jool kernel modules (nat64 and SIIT) and the userspace apps. It is necessary to use DKMS to create the packages (I've included a basic guide in README file).

Please excuse the delay, if you want I could send you an example for the RPM package, @ruben-herold .
The packages were tested on Ubuntu 14-17, Debian 8 and Centos 7 (all in VMware), but I think more tests (in a non virtual machine) would be nice. Could you please test them on Centos 7 and give us some feedback? Thanks!

ruben-herold · 2017-06-12T14:17:07Z

@TheRedTrainer it would be nice if you can sen me an package.
I will also try to build some in my env. Can you give me a link to your src rpm?

TheRedTrainer · 2017-06-14T17:02:54Z

@ruben-herold
I've included the src.rpm and noarch.rpm files built using dkms.
jool-3.5.3-dkms.rpm.zip

ydahhrk · 2017-07-27T19:05:24Z

Still there isn't much feedback so postponing to next release.

ruben-herold · 2017-08-30T10:56:34Z

sorry for my long silence, I had some stress here.. Your noarch rpm installed fine. I will now setup a machine to test it in a limited production environment. Can you supply me with:

how to build own noarch packages
A package for the current version

TheRedTrainer · 2017-08-30T18:48:43Z

Don't worry, @ruben-herold . I'm glad that the RPM worked! I'm busy right now, but as soon as I'm free I'll work with the packages for the current version. If you wanna know how to build the noarch rpm/deb/dsc packages, you can take a look at this link:

https://github.com/NICMx/Jool/tree/master/dkms-packaging

It contains the READ.me file and all the directories/files required by DKMS to build the packages. However, it could be necessary to modify some files and configurations for deb/dsc building package templates in order to comply some debian packaging requirements and standards, so please keep that in mind.

If you have any questions, please tell me and I'll help you as soon as I can.

ruben-herold · 2017-09-04T19:41:06Z

@TheRedTrainer thx works without any problems. I have now one system as nat64 statefull running.

ruben-herold · 2017-09-15T08:09:05Z

@TheRedTrainer do you integrate the systemd scripts from #250

TheRedTrainer · 2017-09-20T21:32:26Z

@ruben-herold I'm sorry for the delay. I didn't integrate the systemd scripts yet, because we need more testing for that issue and I'm kinda busy, but the changes for this issue was merged into master, so if you access to the branch for issue 250 you can see both issues solved.

edmont · 2018-01-17T09:16:36Z

Hi, I just tried to build Jool 3.5.6 for Debian Buster (testing), following the guide. After managing to resolve some issues with the guide[1], I got this error in the last step:

# dkms mkdeb -m jool -v 3.5.6 --source-only
Using /var/lib/dkms/jool/3.5.6/source/jool-dkms-mkdeb
copying template...
modifying debian/changelog...
modifying debian/compat...
modifying debian/control...
modifying debian/copyright...
modifying debian/dirs...
modifying debian/postinst...
modifying debian/prerm...
modifying debian/README.Debian...
modifying debian/rules...
copying legacy postinstall template...
Copying source tree...
Building binary package...dpkg-buildpackage: warning: using a gain-root-command while being root
 dpkg-source --before-build jool-dkms-3.5.6
 fakeroot debian/rules clean
make[1]: *** No rule to make target 'clean'.  Stop.
make: [clean] Error 2 (ignored)
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
 debian/rules build
make[1]: *** No targets specified and no makefile found.  Stop.
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
(bad exit status: 2)
Error! There was a problem creating your deb.

How to solve it?

[1] Issues in dkms-packaging/README.md:

In step 2, the package debhelper it is also a requirement (I got the error: make: dh_testdir: Command not found).
In step 4, there is a typo: just remove the space between - and v.
In step 7, there is a typo: just remove the extra ).

TheRedTrainer · 2018-01-17T20:32:30Z

@edmont Thank you for the report. We're still trying to figure out what happened, but we found a workaround that works for us: Skip the 3rd step entirely. Something like this:

sudo dkms remove -m jool/3.5.6 --all
sudo rm -r /usr/src/jool*

# It *has* to be called lowercase "jool-" then the version number.
sudo cp -r /path/to/Jool /usr/src/jool-3.5.6

# Might be a good idea to do this if you copied the repository, 
# instead of the release zip contents.
sudo rm -r /usr/src/jool-3.5.6/.git

sudo dkms build -m jool -v 3.5.6

# Does not need sudo.
# We do not recall why we're including "--source-only", 
# but I suppose that you can tweak this to your needs.
dkms mkdeb -m jool -v 3.5.6 --source-only

ydahhrk · 2018-01-17T22:23:25Z

sudo dkms remove -m jool/3.5.6 --all
sudo rm -r /usr/src/jool*`

Might want to add (for cleanup, just in case)

rm -r /path/to/Jool/jool-dkms-mk*

edmont · 2018-01-18T09:02:10Z

Thanks guys, that problem was solved that way but still no .deb generated:

# dkms mkdeb -m jool -v 3.5.6 --source-only
Using /etc/dkms/template-dkms-mkdeb
copying template...
modifying debian/changelog...
modifying debian/compat...
modifying debian/control...
modifying debian/copyright...
modifying debian/dirs...
modifying debian/postinst...
modifying debian/prerm...
modifying debian/README.Debian...
modifying debian/rules...
copying legacy postinstall template...
Copying source tree...
Building binary package...dpkg-buildpackage: warning: using a gain-root-command while being root
 dpkg-source --before-build jool-dkms-3.5.6
 fakeroot debian/rules clean
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
 debian/rules build
 fakeroot debian/rules binary
dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use)
dh_shlibdeps: Compatibility levels before 9 are deprecated (level 7 in use)
 dpkg-genbuildinfo --build=binary
 dpkg-genchanges --build=binary >../jool-dkms_3.5.6_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build jool-dkms-3.5.6


DKMS: mkdeb completed.
Moving built files to /var/lib/dkms/jool/3.5.6/deb...mv: cannot stat '/tmp/dkms.ROv1Jp/jool-dkms_3.5.6_amd64.deb': No such file or directory
(bad exit status: 1)
Cleaning up temporary files...

ydahhrk · 2018-01-18T16:11:04Z

dh_installdirs: Compatibility levels before 9 are deprecated (level 7 in use)
dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use)
dh_shlibdeps: Compatibility levels before 9 are deprecated (level 7 in use)

Compatibility level 7 is defined in <path-to-jool>/dkms-packaging/deb/jool-dkms-mkd*/compat. This meas that these files are still lingering somewhere you don't want them to.

Find them and delete them. The only DKMS file you want in your build is <path-to-jool>/dkms.conf.

Edit: You can also start from scratch and simply skip step 3.

TheRedTrainer · 2018-01-19T02:26:59Z

I think I found what could the issue be. I tested on Debian Buster too (installing dkms using apt-get) with the same results. Only when I removed dkms, downloaded the latest version from github (https://github.com/dell/dkms) and compiled/installed that version, the dkms mkdeb command worked correctly. I'm still testing to confirm this, using other configuration.

Which dkms version do you have @edmont ?

edmont · 2018-01-19T07:53:46Z

@TheRedTrainer:
dkms: 2.2.1.0

TheRedTrainer · 2018-01-19T22:57:53Z

Thanks @edmont . The latest dkms version that I downloaded from github is the 2.5, I don't know why the apt-get install that version.

I found the cause for the first issue that you reported: a Makefile was missing in jool-dkms-mkdeb and jool-dkms-mkdsc directories.

As seen at the beginning of "dkms mkdeb" command output, (as far as I know) when dkms is trying to build the deb package, it needs a set of files required for debian packaging (for more information https://wiki.debian.org/Packaging/Intro ) that contains info about log of changes, source and package description, copyright, post installation scripts, pre removal scripts, etc. If dkms can't find these directories and files in /usr/src/jool-VERSION/jool-dkms-mkdeb/ , then the template files and directories located in /etc/dkms/ are copied and used for the package building (that is the reason because technically you can skip step 3, at the cost of not including all your custome configuration).

The jool-dkms-mkdeb includes the "debian" folder that contains all these files (changelog, compat, control, copyright, dirs, postinst, prerm, rules). However, it is also required a Makefile that is not included in jool-dkms-mkdeb and jool-dkms-mkdsc folders. It seems that this file wasn't required in dkms previous versions because it was copied from template files. I will immediately include the missing Makefile in the branch issue243.

About the second issue (the failure when moving built files), I only could fix it updating the dkms version in Debian buster. I can't find the precise reason why the generated deb files can't be moved from temporal directory to jool location. I think it could be some compatibility issues with the dkms version available in apt-get.

edmont · 2018-01-22T08:39:09Z

Thanks @TheRedTrainer, I tried issue243 branch and first issue is solved. But make debs fails with the master branch of dell/dkms 😡 I think I'll wait for things to settle up since this is not urgent for me.

One question, once the deb is created, is it kernel version independent?

edmont · 2019-02-22T11:40:06Z

@ydahhrk I'm failing to build Jool 3.5.7 in Armbian:

user@nanopineo:~$ sudo dkms build -m jool -v 3.5.7

Creating symlink /var/lib/dkms/jool/3.5.7/source ->
                 /usr/src/jool-3.5.7

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area......
make -j4 KERNELRELEASE=4.19.20-sunxi -C /lib/modules/4.19.20-sunxi/build SUBDIRS=/var/lib/dkms/jool/3.5.7/build/mod/stateful modules && make -C /lib/modules/4.19.20-sunxi/build SUBDIRS=/var/lib/dkms/jool/3.5.7/build/mod/stateless modules........(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.20-sunxi (armv7l)
Consult /var/lib/dkms/jool/3.5.7/build/make.log for more information.

user@nanopineo:~$ cat /var/lib/dkms/jool/3.5.7/build/make.log
DKMS make.log for jool-3.5.7 for kernel 4.19.20-sunxi (armv7l)
Fri Feb 22 11:32:53 UTC 2019
make: Entering directory '/usr/src/linux-headers-4.19.20-sunxi'
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/empty.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/db.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/rfc6056.o
  CC [M]  /var/lib/dkms/jool/3.5.7/build/mod/stateful/bib/db.o
/bin/sh: 1: ./scripts/recordmcount: not found
scripts/Makefile.build:303: recipe for target '/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/empty.o' failed
make[1]: *** [/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/empty.o] Error 127
make[1]: *** Deleting file '/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/empty.o'
make[1]: *** Waiting for unfinished jobs....
/bin/sh: 1: ./scripts/recordmcount: not found
scripts/Makefile.build:303: recipe for target '/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/rfc6056.o' failed
make[1]: *** [/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/rfc6056.o] Error 127
make[1]: *** Deleting file '/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/rfc6056.o'
/bin/sh: 1: ./scripts/recordmcount: not found
scripts/Makefile.build:303: recipe for target '/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/db.o' failed
make[1]: *** [/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/db.o] Error 127
make[1]: *** Deleting file '/var/lib/dkms/jool/3.5.7/build/mod/stateful/pool4/db.o'
/bin/sh: 1: ./scripts/recordmcount: not found
scripts/Makefile.build:303: recipe for target '/var/lib/dkms/jool/3.5.7/build/mod/stateful/bib/db.o' failed
make[1]: *** [/var/lib/dkms/jool/3.5.7/build/mod/stateful/bib/db.o] Error 127
make[1]: *** Deleting file '/var/lib/dkms/jool/3.5.7/build/mod/stateful/bib/db.o'
Makefile:1520: recipe for target '_module_/var/lib/dkms/jool/3.5.7/build/mod/stateful' failed
make: *** [_module_/var/lib/dkms/jool/3.5.7/build/mod/stateful] Error 2
make: Leaving directory '/usr/src/linux-headers-4.19.20-sunxi'

ydahhrk · 2019-02-23T14:23:01Z

@edmont It' s normal; 3.5.7 does not support kernel 4.19.

Please try 4.0.0. If it gives you serius trouble, we can consider adding 4.19 support for 3.5 as a workaround.

edmont · 2019-02-25T12:03:34Z

@ydahhrk I just tested with v4.0.0 (from GitHub, since the gzipped file does not include the dkms-packaging folder), and I'm having the exact same error as with v3.5.7. Do you have record of other users building Jool for Armbian?

ydahhrk · 2019-02-26T07:57:52Z

(from GitHub, since the gzipped file does not include the dkms-packaging folder)

Ahhh. This would explain it.

The dkms-packaging/ folder has never been production-ready. If it were, I could upload the Debian packages right away.

I mean, I made dkms-packaging/ somewhat work for 3.5.7, but it had its quirks. This one, for example. And because it was still considered unfinished, updating it for the sake of Jool 4 was quickly dropped from the scope of .0.0.

I'm sorry for the confusion. I thought that not mentioning it in the documentation was enough to scare users away from it, but I guess you found that README, huh.

I mean you can still install the modules via DKMS, you just can't build packages. At least not with dkms-packaging/.

edmont · 2019-04-03T09:28:42Z

Thanks @ydahhrk, 4.0.0 with DKMS install works for me by the moment. But having the .deb option would be much better :)

ydahhrk · 2019-04-03T16:02:26Z

But having the .deb option would be much better :)

Sorry about that. I got temporarily assigned to a different project and can't focus on Jool at the moment. This is why it's taking so long.

edmont · 2019-04-04T08:38:28Z

@ydahhrk oops! I just realized I made a too fast checking and overlooked that the kernel module for 4.0.0 was not installed correctly. Actually I'm having the same problem as with 3.5.7 about recordmcount not found.

It looks like the headers for this distribution don't come with compiled scripts. I tried to make them myself, resulting in other errors. I'll see if some other release gives better results: https://dl.armbian.com/nanopineo/

edmont · 2019-04-04T11:01:51Z

No luck with Armbian_5.65_Nanopineo_Ubuntu_bionic_next_4.14.78 or Armbian_5.75_Nanopineo_Debian_stretch_next_4.19.20.

Does it make any sense to cross compile Jool within the Armbian building system?
https://docs.armbian.com/Developer-Guide_Build-Preparation/

edmont · 2019-04-04T16:39:48Z

I found this Armbian issue: armbian/build#1278

So I built a complete image based on the repository and was able to build the Jool 4.0.0 module with DKMS.

@ydahhrk , do you see an easy way to include the Jool sources in the Armbian tree so that it becomes present in the final image?

ydahhrk · 2019-04-04T17:03:07Z

So I built a complete image based on the repository and was able to build the Jool 4.0.0 module with DKMS.

Welp. I was barely finished installing qemu and downloading an Armbian image to get started. Sorry for not being any help.

@ydahhrk , do you see an easy way to include the Jool sources in the Armbian tree so that it becomes present in the final image?

No, but that might be simply because I still have little to no experience both with Armbian, and with pushing Jool natively into anything.

If Armbian is Debian-based, won't the official debian package we'll eventually end up with be any help? It will install the modules via DKMS, IIRC.

edmont · 2019-04-05T07:29:06Z

If Armbian is Debian-based, won't the official debian package we'll eventually end up with be any help? It will install the modules via DKMS, IIRC.

Yeah, I agree. It's worth to focus the effort into the official Debian package.

Package building reports several warnings, but Lintian is silent. Package seems to install userspace tools with no issues. This commit is the first in a series intended to finally nail #243. Unit tests and kernel modules have not been updated yet. Fixes #264 and the userspace half of #243.

edmont · 2019-07-23T14:25:02Z

Hi! I see there are good advances with Jool 4.0.3!

I was able to build jool-dkms for amd64 with dkms mkdeb jool/4.0.3. However, for armv7l I get this error:

dpkg-shlibdeps: error: no dependency information found for /root/jool-4.0.3/src/usr/util/.libs/libjoolutil.so.0 (used by debian/jool-dkms/usr/src/jool-4.0.3/src/usr/argp/.libs/libjoolargp.so)
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/jool-dkms.substvars debian/jool-dkms/usr/src/jool-4.0.3/src/usr/util/.libs/libjoolutil.so debian/jool-dkms/usr/src/jool-4.0.3/src/usr/util/.libs/libjoolutil.so.0 debian/jool-dkms/usr/src/jool-4.0.3/src/usr/util/.libs/libjoolutil.so.0.0.0 debian/jool-dkms/usr/src/jool-4.0.3/src/usr/nl/.libs/libjoolnl.so debian/jool-dkms/usr/src/jool-4.0.3/src/usr/nl/.libs/libjoolnl.so.0 debian/jool-dkms/usr/src/jool-4.0.3/src/usr/nl/.libs/libjoolnl.so.0.0.0 debian/jool-dkms/usr/src/jool-4.0.3/src/usr/nl/.libs/libjoolnl.so.0.0.0T debian/jool-dkms/usr/src/jool-4.0.3/src/usr/iptables/libxt_JOOL.so debian/jool-dkms/usr/src/jool-4.0.3/src/usr/iptables/libxt_JOOL_SIIT.so debian/jool-dkms/usr/src/jool-4.0.3/src/usr/argp/.libs/libjoolargp.so debian/jool-dkms/usr/src/jool-4.0.3/src/usr/argp/.libs/libjoolargp.so.0 debian/jool-dkms/usr/src/jool-4.0.3/src/usr/argp/.libs/libjoolargp.so.0.0.0 debian/jool-dkms/usr/src/jool-4.0.3/src/usr/argp/.libs/libjoolargp.so.0.0.0T returned exit code 255
dh_shlibdeps: Aborting due to earlier error
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
(bad exit status: 2)
Error! There was a problem creating your deb.

And by the way, how to build the jool-tools package?

Thanks!

ydahhrk · 2019-07-23T18:48:47Z

However, for armv7l I get this error:

Interesting. I haven't actually tried to cross-compile; it seems I haven't gotten to that step yet.

In any case, I'm not using dkms mkdeb, and jool-dkms is supposed to be architecture-independent (as it's only code). See below.

And by the way, how to build the jool-tools package?

I'm using this workspace to generate everything. (The script might need a GUI. If this is a problem, comment out lines 41, 47 and 54 as a workaround for now.)

ydahhrk · 2019-07-23T19:07:15Z

By the way: It seems it's taking a little doing to get the packages sponsored into Debian. If you don't actually care about the package generation and just want to play with them, I uploaded my current build here and here.

sudo apt install ./jool-dkms_4.0.3-1_all.deb ./jool-tools_4.0.3-1_amd64.deb
sudo apt remove jool-dkms jool-tools

Status:

edmont · 2019-07-24T11:24:32Z

@ydahhrk thanks! I got to build the two packages! I had to comment those lines to get rid of some signature errors (also devscripts is required for line 54). By the way, I'm not cross compiling, just building natively in a different architecture.

ydahhrk · 2019-08-02T17:16:46Z

Update: The package was sponsor-approved and uploaded the to the NEW queue. It's awaiting review from the "ftpteam."

According to Vincent Bernat (our sponsor),

The package will sit in NEW for some time for someone to review it (mostly to check debian/copyright, but they also check some technical details too). Once it is accepted, it will move to unstable.

So I guess we're almost there. Assuming it's not bounced back, of course.

This link was mailed to me. I think it's the closest I have to a status report page. (You have to Ctrl+F "jool".)

edmont · 2019-08-05T05:18:07Z

That's good news!

ydahhrk · 2019-11-20T22:49:23Z

Jool made it into unstable in November 12, and already transitioned to testing in November 16. Some instructions for installing the unstable version were already documented in case anyone's interested. Maintaining this package is now a separate perpetual effort independent of this issue.

Closing.

PrasanthiVarma · 2022-01-21T21:24:38Z

@ruben-herold I've included the src.rpm and noarch.rpm files built using dkms. jool-3.5.3-dkms.rpm.zip

Can you please help me with the SPEC file you used to create RPM

ydahhrk · 2022-01-22T04:22:16Z

@PrasanthiVarma https://raw.githubusercontent.com/NICMx/Jool/21d499a5c4d82e1493ca9912aaeadfc6bbf46f88/dkms-packaging/rpm/jool-dkms-mkrpm.spec

It's very outdated. I have no memory of what happened to this effort.

It seems I accidentally deleted it as part of a refactor, and completely forgot afterwards.

Sorry.

PrasanthiVarma · 2022-01-23T20:16:40Z

@PrasanthiVarma https://raw.githubusercontent.com/NICMx/Jool/21d499a5c4d82e1493ca9912aaeadfc6bbf46f88/dkms-packaging/rpm/jool-dkms-mkrpm.spec

It's very outdated. I have no memory of what happened to this effort.

It seems I accidentally deleted it as part of a refactor, and completely forgot afterwards.

Sorry.

No problem.Thank you very much for your help!!!!

ydahhrk added the New feature label Apr 25, 2017

ydahhrk assigned TheRedTrainer Apr 27, 2017

ydahhrk added this to the 3.5.4 milestone Jun 5, 2017

ydahhrk added the Status: Coded Needs testing and release label Jul 10, 2017

ydahhrk modified the milestones: 3.5.5, 3.5.4 Jul 27, 2017

ydahhrk removed this from the 3.5.5 milestone Nov 10, 2017

ydahhrk mentioned this issue Nov 10, 2017

init / systemd scripts missing #250

Closed

ydahhrk mentioned this issue Jan 23, 2019

Merge Jool into nftables #273

Open

ydahhrk added Status: Stuck Development paused due to unavailable external input and removed Status: Coded Needs testing and release labels Aug 28, 2019

ydahhrk unassigned TheRedTrainer Aug 28, 2019

This was referenced Sep 24, 2019

jool: Update Jool to the latest version (4.0.x) openwrt/packages#9349

Closed

run Jool in docker get "Jool hasn't been modprobed" #295

Closed

ydahhrk closed this as completed Nov 20, 2019

ydahhrk removed the Status: Stuck Development paused due to unavailable external input label Nov 20, 2019

SPEC files and Debian directory to build own packages #243

SPEC files and Debian directory to build own packages #243

Comments

ruben-herold commented Apr 25, 2017

ydahhrk commented Apr 25, 2017

ruben-herold commented Apr 27, 2017

ydahhrk commented Apr 27, 2017 • edited Loading

ruben-herold commented May 1, 2017

TheRedTrainer commented May 22, 2017 • edited by ydahhrk Loading

ruben-herold commented Jun 12, 2017 • edited Loading

TheRedTrainer commented Jun 14, 2017

ydahhrk commented Jul 27, 2017

ruben-herold commented Aug 30, 2017

TheRedTrainer commented Aug 30, 2017 • edited Loading

ruben-herold commented Sep 4, 2017

ruben-herold commented Sep 15, 2017

TheRedTrainer commented Sep 20, 2017

edmont commented Jan 17, 2018 • edited Loading

TheRedTrainer commented Jan 17, 2018

ydahhrk commented Jan 17, 2018 • edited Loading

edmont commented Jan 18, 2018

ydahhrk commented Jan 18, 2018 • edited Loading

TheRedTrainer commented Jan 19, 2018

edmont commented Jan 19, 2018

TheRedTrainer commented Jan 19, 2018 • edited Loading

edmont commented Jan 22, 2018

edmont commented Feb 22, 2019

ydahhrk commented Feb 23, 2019

edmont commented Feb 25, 2019

ydahhrk commented Feb 26, 2019 • edited Loading

edmont commented Apr 3, 2019

ydahhrk commented Apr 3, 2019

edmont commented Apr 4, 2019 • edited Loading

edmont commented Apr 4, 2019

edmont commented Apr 4, 2019

ydahhrk commented Apr 4, 2019

edmont commented Apr 5, 2019

edmont commented Jul 23, 2019

ydahhrk commented Jul 23, 2019

ydahhrk commented Jul 23, 2019

edmont commented Jul 24, 2019

ydahhrk commented Aug 2, 2019

edmont commented Aug 5, 2019

ydahhrk commented Nov 20, 2019

PrasanthiVarma commented Jan 21, 2022

ydahhrk commented Jan 22, 2022

PrasanthiVarma commented Jan 23, 2022

ydahhrk commented Apr 27, 2017 •

edited

Loading

TheRedTrainer commented May 22, 2017 •

edited by ydahhrk

Loading

ruben-herold commented Jun 12, 2017 •

edited

Loading

TheRedTrainer commented Aug 30, 2017 •

edited

Loading

edmont commented Jan 17, 2018 •

edited

Loading

ydahhrk commented Jan 17, 2018 •

edited

Loading

ydahhrk commented Jan 18, 2018 •

edited

Loading

TheRedTrainer commented Jan 19, 2018 •

edited

Loading

ydahhrk commented Feb 26, 2019 •

edited

Loading

edmont commented Apr 4, 2019 •

edited

Loading