Hi again,
I just now noticed that the QA information on the mentors site of my
package[0] says that I have no debhelper compatibility level set and
that I don't have a watch file, but both are there in the package I
uploaded. I have no idea what went wrong.
Also, strangely, when I downloaded the
Hi again,
I just now noticed that the QA information on the mentors site of my
package[0] says that I have no debhelper compatibility level set and
that I don't have a watch file, but both are there in the package I
uploaded. I have no idea what went wrong.
Also, strangely, when I downloaded the
Am 03.11.2015 um 17:35 schrieb Gianfranco Costamagna:
> (please ping me when you fixed those, I don't look to mentors otherwise)
Hi Gianfranco,
I have just uploaded a new version with two patches to mentors.
The git repository I use for maintaining can now also be found on
github[0] (I use
On Sat, Oct 31, 2015 at 11:26 PM, Tim Dengel wrote:
> The second issue is, as you said, the use of git. But adding git to the
> build dependencies would not solve this, since the .git directory is not
> contained in the original tarball, so git couldn't extract the version
> from it anyways.
>
>
Hi,
>Thanks!
>I think what helped me the most (apart from reading lots of
>documentation) was looking at existing packages in the archive.
>I specifically looked at packages using the SCons build system, since
>that is not natively supported by debhelper (like autotools is for example).
>That
Am 30.10.2015 um 10:13 schrieb Gianfranco Costamagna:
> well, I started packaging in 2013 and I didn't provide good packages on the
> first tries.
> (actually I'm still doing packaging mistakes)
>
> You seem to be a better packager than me, and you told you are on your first
> packaging
Hi Tim,
>Hmm, I'm not really sure what you mean with that, but alright.
well, I started packaging in 2013 and I didn't provide good packages on the
first tries.
(actually I'm still doing packaging mistakes)
You seem to be a better packager than me, and you told you are on your first
Am 27.10.2015 um 11:53 schrieb Gianfranco Costamagna:
> Hi,
>
> (let me say, based on your answers I have difficulties in understanding how
> possibly
> your first package can be so good :) )
Hmm, I'm not really sure what you mean with that, but alright.
> well, first there is a
Hi,
(let me say, based on your answers I have difficulties in understanding how
possibly
your first package can be so good :) )
>I installed into debian/package because "man dh_auto_install" told me
>that "[...]the files are installed into debian/package/ if there is only
>one binary package.
Am 26.10.2015 um 19:00 schrieb Gianfranco Costamagna:
> Hi, the packaging looks good to me (note: I didn't do a full review)
Hi, thanks for looking at my package!
> however I don't like your dh_auto_install target override.
>
> dh_auto_install should install into debian/tmp, not into
Control: owner -1 !
Hi, the packaging looks good to me (note: I didn't do a full review)however I
don't like your dh_auto_install target override.
dh_auto_install should install into debian/tmp, not into debian/package.
I propose you to use dh_install like this:
override_dh_install:
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "gnome-twitch"
* Package name: gnome-twitch
Version : 0.1.0-1
Upstream Author : Vincent Szolnoky
* URL :
12 matches
Mail list logo