Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "uriparser"
Package name: uriparser
Version : 0.8.0.1-1
URL : http://uriparser.sourceforge.net/
License : BSD-3-clause, LGPL-2.1+, GPL-3.0+
S
Your message dated Sun, 13 Jul 2014 08:13:04 +0200
with message-id <1405231984.6262.6.camel@merkur>
and subject line Debian bug #754515
has caused the Debian Bug report #754515,
regarding RFS: uriparser/0.8.0+dfsg-1 [ITA]
to be marked as done.
This means that you claim that the problem has been de
Hello,
on upstream is now a dfsg-free Version available.
I close this bug and upload a new package without "+dfsg".
Thanks
Jörg
--
pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E
pgp Key: BE581B6E
CAcert Key S/N: 0E:D4:56
Jörg Frings-Fürst
D-54526 Niederkail
Threema: SYR8S
Hi Tong,
I think that no exist a place. But I use it:
$ find /usr/share/doc -name '*changelog.Debian.gz*' -exec cat {} >>
changelogs.gz \;
You can use zcat, zgrep or mcview to read the changelogs.gz file. I
prefer mcview.
Regards,
Eriberto
2014-07-13 0:16 GMT-03:00 T o n g :
>
> I'm wondering
Your message dated Sun, 13 Jul 2014 04:24:03 +
with message-id
and subject line closing RFS: thinkpad-scripts/3.5.1-1 [ITP]
has caused the Debian Bug report #731036,
regarding RFS: thinkpad-scripts/3.5.1-1 [ITP]
to be marked as done.
This means that you claim that the problem has been dealt w
Dear Yukiharu and Jeremy,
thanks for your answers.
Yes, I know about git-buildpakcage and will use it in last ressort.
There are multiple reasons why I prefer to base my packages on the upstream Git
repository when it exists.
First, in my experience, this tremendously eases the exchange of patc
Hi,
What's that '-i' is for in the 'debuild -i' command?
I was looking for it in debuild & dpkg-buildpackage man pages but still
wasn't sure what it is for.
The actual whole command I use is:
debuild -i -us -uc -b
I found that if I use -i I will get the following problems, whereas if -i
Hi,
I'm wondering if there is a central place that I can search for all Debian
change logs for all packages, to see if the same lintian problem I'm
having now have been dealt with before, and also see how exactly those
lintian problems are fixed.
Thanks
--
To UNSUBSCRIBE, email to debian
> I don't think that this was the author's intention. There are plenty
> of Info.plist files where GPL 2.0 is stated, but it doesn't mean "GPL
> 2.0 only". To be sure, you could clarify with upstream (write to
> gap-dev-disc...@nongnu.org rather than via Savannah's interface).
>From a legal poin
Hi,
wow, amazing that you are still investing your time in improving my packaging -
thanks a lot! :D
Quoting Jakub Wilk (2014-07-12 18:24:26)
> I don't doubt that compatibility.min.js is needed. What I questioned is
> whether we ever need compatibility.js in the binary package.
Indeed. I missed
* Johannes Schauer , 2014-07-12, 13:06:
Is the non-minified version used by pdf2htmlEX at runtime at all? I
think it isn't, but I could be wrong. If it's not, then maybe get rid
of the symlink, and drop libjs-pdf from Depends?
Yes it is. You can check that it is used by running the test suite
On Sat, 12 Jul 2014 09:36:34 +0200, Vincent Bernat wrote:
> I think this warning hide another problem with your modifications is
> that the SCRIPTSCOMMON tag doesn't get extended anymore. Ensure that
> dh_installscripts-common is still executed.
Ah, you are right.
script -c "debuild -i -us -uc
On Sat, 12 Jul 2014 13:23:16 +, T o n g wrote:
> override_dh_auto_install:
> install -m 755 ddclient \
> $(DESTDIR)/usr/sbin/ddclient
>
> install -D -m 755 debian/ddclient.NetworkManager \
> $(
)/etc/NetworkManager/dispatcher.d/50-ddclient
> dh_auto_install
>
On Sat, 12 Jul 2014 13:14:23 +, T o n g wrote:
>>> # main packaging script based on dh7 syntax %:
>>> dh $@
>>>
>>> override_dh_auto_install:
>>> install -m 755 ddclient \
>>> $(DESTDIR)/usr/sbin/ddclient
>>>
>>> install -D -m 755 debian/ddclient.NetworkManager \
>>> $(
On 2014-07-12 13:45:52 +0900 (+0900), Charles Plessy wrote:
[...]
> I am blocking on the fact that he uses gnulib in a way that the
> version number of his program is expressed only via a Git tag.
> Thus, given that Debian source package are based on tar archives,
> the version number is lost unles
On Sat, 12 Jul 2014 09:27:32 +0200, Vincent Bernat wrote:
>> # main packaging script based on dh7 syntax %:
>> dh $@
>>
>> override_dh_auto_install:
>> install -m 755 ddclient \
>>$(DESTDIR)/usr/sbin/ddclient
>>
>> install -D -m 755 debian/ddclient.NetworkManager \
>>
Subject says it all - I've been working on this a bit, and I have a few
problems - I hope these aren't too newbie of questions.
Presently I'm working on EFL, Enlightenment Foundation Library, which
is the lion's share of the work in terms of dependencies.
1. I have a dependency on liborc, that n
Hi,
Quoting Jakub Wilk (2014-07-12 11:50:39)
> It would guard against the possibility of losing source.
>
> But it could still happen that compatibility.js and compatibility.min.js
> versions (in /usr/share/pdf2htmlEX/) don't match.
okay. Indeed that's undesirable.
> Is the non-minified versio
* Johannes Schauer , 2014-07-12, 09:40:
Hmm, there is no protection against the two versions getting of sync.
Which means that there is no guarantee that we are shipping source for
the minified version. :(
But setting "Built-Using: pdf.js" would guard against that, would it
not?
It would gu
Riley Baird wrote:
> On 11/07/14 17:46, Yavor Doganov wrote:
> > The license is GPL-2+, AFAICS.
>
> *Most* of GMastermind is released under GPL-2+. However, the README
> indicates that, as a whole, GMastermind is released under GPL-2 (so,
> it would apply to all files without a license header).
I
Hello, Chariles
You might known git-buildpackage. I did not know 'datamash'
But I'd like to tell you:
[When upstream uses GIT]
(http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.UPSTREAM-GIT)
How about is docuemnt? You may make branches and sometime would l
On 2014-07-12 09:36, Vincent Bernat wrote:
> ❦ 12 juillet 2014 05:19 GMT, T o n g :
>
>> Do I need to care about the lintian problems from the binary package that
>> I maintain/build?
>
> Yes, you need to handle at least errors and warnings.
>
>> For the following problems, I have no idea whe
Hi,
Quoting Jakub Wilk (2014-07-11 23:48:15)
> * Johannes Schauer , 2014-07-11, 21:33:
> >How did you find them? I ran codespell but that didnt find the ones you
> >found.
>
> I read carefully the source code. :-) (I admit that vim's spell checking
> helped me a bit.)
I just discovered that my
❦ 12 juillet 2014 05:19 GMT, T o n g :
> Do I need to care about the lintian problems from the binary package that
> I maintain/build?
Yes, you need to handle at least errors and warnings.
> For the following problems, I have no idea where they come from:
>
> N: Processing binary package ddc
❦ 12 juillet 2014 03:51 GMT, T o n g :
> # main packaging script based on dh7 syntax
> %:
> dh $@
>
> override_dh_auto_install:
> install -m 755 ddclient \
> $(DESTDIR)/usr/sbin/ddclient
>
> install -D -m 755 debian/ddclient.NetworkManager \
> $(DESTDIR)/etc/Ne
25 matches
Mail list logo
