[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Problems to package and upload a Java application with Maven Build system



Dear all,

First of all, sorry because I'm newbie and this is the first application I have tried to package. So far, the process didn't throw any errors, so I supposed it was fine, but now I'm struggled with some problems.

The application I'm trying to package is WallpaperDownloader, a GUI Java-based application which uses Maven as build system (https://bitbucket.org/eloy_garcia_pca/wallpaperdownloader). Those are the steps I have followed so far:

01.- I installed Debian and switched to Sid
02.- I cloned the master branch from the upstream repo in Bitbucket: git clone https://bitbucket.org/eloy_garcia_pca/wallpaperdownloader.git
03.- I installed manually all the dependencies needed from Debian repository (sudo apt install liblog4j1.2-java libslf4j-java libcommons-io-java libjsoup-java libjna-java)
04.- I installed all the tools needed for building the package (sudo apt install git build-essential devscripts debhelper javahelper maven-debian-helper apt-file)
05.- I executed mh_make (I have used maven debian helper for creating the initial structure instead of dh_make)
06.- I modified rules and control files. You can see the definitive files if you go to the code repository and navigate to debian folder (https://bitbucket.org/eloy_garcia_pca/wallpaperdownloader/src)
07.- I created some new files for the packaging process: wallpaperdownloader.install, wallpaperdownloader.manifest, wallpaperdownloader.manpages
08.- I created the Debian package using dpkg-buildpackage -b -rfakeroot -us -uc from the root directory of the wallpaperdownloader application. WARNING: ONLY three files were generated in this process: wallpaperdownloader_2.7-1_all.deb, wallpaperdownloader_2.7-1_amd64.buildinfo, wallpaperdownloader_2.7-1_amd64.changes. No orig.tar.gz, no .dsc files were automatically generated.

09.- I checked the package with lintian. No warnings, no errors (I removed all of them one by one before).
10.- I installed the generated package and it installs properly.
11.- I opened a bug (ITP) against WNPP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863572
12.- I opened a bug (RFS) against sponsorship-requests: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864174
13.- Then, I realized that I needed to upload the package to https://mentors.debian.net/ in order to look for a person to sponsor my package so this is what I did:
    13.1.- I modified changelog file in order to reflect the WNPP bug which would close
    13.2.- I created a GPG key to sign my package
    13.3.- I signed the package (changes file)
    13.4.- I created an account on https://mentors.debian.net and I set my GPG public key
    13.5.- I configured dput and executed. The three files were uploaded without any problem but... this is the problem: The package is dropped silently on the server side and it is not published on mentors site!!!

What am I doing wrong? I think dsc file and orig.tar.gz file are mandatory the first time a package is uploaded. Could it be the problem?. On the other hand, how can I generate those files using mh_make?. Using dh_make those packages are created on the fly right?. Or... maybe the problem is that I should have uploaded the package before opening the RFS bug against sponsoship-requests?. I'm lost at this point and I would appreciate any help.

Thank you very much for your time.

Best regards,

Eloy

--
Eloy García Almadén

Reply to: