Your message dated Thu, 20 Aug 2015 16:16:24 + (UTC)
with message-id <369241047.8412344.1440087384911.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1
has caused the Debian Bug report #796191,
regarding RFS: libharu/2.3.0+dfsg-1~exp1
to be
Hi Jakub,
>This particular package doesn't contain any executables, AFAICS.
true
>It is now permitted to put architecture-dependent headers files in
>/usr/include/, so this is no longer show-stopper.
nice to know :)
>If the symlink lives in architecture-specific directory, it's not an
>is
* Gianfranco Costamagna , 2015-08-20, 12:39:
A -dev package may contain an architecture dependent -config
executable, that cannot be included in a M-A: same package.
This particular package doesn't contain any executables, AFAICS.
The same goes for headers which vary across architectures.
I
Hi,
>A -dev package may contain an architecture dependent -config executable,
>that cannot be included in a M-A: same package. The same goes for
>headers which vary across architectures.
>
>If there are no architecture dependent files in a -dev package M-A: same
>should be fine.
isn't the so l
On Thu, Aug 20, 2015 at 12:29 PM, Gianfranco Costamagna
wrote:
> now the changelog has one line extra (line 1)
>
> and maybe you can remove something, like a double
> "Imported Upstream version 2.3.0+dfsg"
I changed it to avoid confusion.
> regarding multiarch
>
> "Pre-Depends: ${misc:Pre-Depen
On 20-08-15 12:52, Jakub Wilk wrote:
> * Gianfranco Costamagna , 2015-08-20, 10:29:
>> "Pre-Depends: ${misc:Pre-Depends}" should be added,
>
> FWIW, ${misc:Pre-Depends} was required for partial squeeze->wheezy
> upgrades. It is no longer necessary.
>
>> and the dev package should not marked as mu
* Gianfranco Costamagna , 2015-08-20, 10:29:
"Pre-Depends: ${misc:Pre-Depends}" should be added,
FWIW, ${misc:Pre-Depends} was required for partial squeeze->wheezy
upgrades. It is no longer necessary.
and the dev package should not marked as multiarch same.
Why not?
--
Jakub Wilk
>I do remove them now. Not in the previous release where the tarball
>was made with make dist (vs github snapshot now).
ok, so it is dfsg, well!
now the changelog has one line extra (line 1)
and maybe you can remove something, like a double
"Imported Upstream version 2.3.0+dfsg"
(but this is
On Thu, Aug 20, 2015 at 11:19 AM, Gianfranco Costamagna
wrote:
>>Looking at the policy I think it is better to document this in
>>debian/copyright. I like to document why I remove files from the
>>original source.
>
>
> but you didn't remove them anymore, right?
> anyway, let me know your solutio
Hi Johan
>Ok, I will check - some time since I last did this.
ack
>Should I do so before uploading to experimental?
nope, experimental will setup an automatic tracker for you, they might even
tell you to go for unstable whenever you like
>Looking at the policy I think it is better to docu
On Thu, Aug 20, 2015 at 10:29 AM, Gianfranco Costamagna
wrote:
> Control: owner -1 !
> Control: tag -1 moreinfo
>
> Hi Johan,
>
> multiarch should be mentioned in control file.
>
> https://wiki.debian.org/Multiarch/Implementation
Ok, I will check - some time since I last did this.
>
>
>
> this
Control: owner -1 !
Control: tag -1 moreinfo
Hi Johan,
> * Imported Upstream version 2.3.0 (Closes: #726069)
> * Bump standards version (no changes needed)
> * Bump library package number
> * Update install filename
> * Switch to debhelper 9 - enable multiarch
multiarch should be mentione
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "libharu"
* Package name: libharu
Version : 2.3.0+dfsg-1~exp1
Upstream Author : [fill in name and email of upstream]
* URL : http://libharu.org
* License
Your message dated Sun, 15 Mar 2015 06:44:22 +
with message-id
and subject line closing RFS: libharu/2.2.1-2 (update)
has caused the Debian Bug report #755049,
regarding RFS: libharu/2.2.1-2 (update)
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 28 Oct 2014 19:06:11 +
with message-id <20141028190611.gg22...@master.debian.org>
and subject line closing duplicate RFS, see 755049
has caused the Debian Bug report #766421,
regarding RFS: libharu/2.2.1-2
to be marked as done.
This means that you claim th
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "libharu"
* Package name: libharu
Version : 2.2.1-2
Upstream Author : [fill in name and email of upstream]
* URL : http://libharu.org/
* License : zl
tags 755049 moreinfo
thanks
Hi Johan,
Please:
1. Update the packaging years in d/copyright.
2. If you removed files from original tarball, add a dfsg suffix to version.
3. Fix these lintian messages:
I: libhpdf-2.3.0: hardening-no-fortify-functions
usr/lib/x86_64-linux-gnu/libhpdf-2.3.0.so
I:
> * Package name: libharu
> Version : 2.3.0-1
> [...]
> libharu is already packaged in debian, this is just an update to the last
> upstream version. It will require a rebuild of the depending packages:
> saga
> udav
> mathgl
> emboss
> falconpl
It may be wise to change the package
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "libharu"
* Package name: libharu
Version : 2.3.0-1
Upstream Author : Takeshi Kanno, Antony Dovgal (see copyrightfile)
* URL : http://www.libharu.org
* License
Your message dated Mon, 17 Mar 2014 04:25:30 +
with message-id
and subject line closing RFS: libharu/2.2.1-2
has caused the Debian Bug report #728105,
regarding RFS: libharu/2.2.1-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Control: tag -1 moreinfo
Hi Johan,
Your package mostly looks good, but in debian/changelog you claim that
you've fixed #727409 by running autoreconf, but that's not the case.
In addition to adding a build-dep on dh-autoreconf, you also need the
following in debian/rules:
%:
dh $@ --with auto
Package: sponsorship-requests
Dear mentors,
I am looking for a sponsor for my package "libharu"
* Package name: libharu
Version : 2.2.1-2
Upstream Author : [fill in name and email of upstream]
* URL : http://libharu.org/
* License : zlib
Section
Hi,
[...]
> >> I am looking for a sponsor for the new version 2.2.1-1
> >> of my package "libharu".
> >>
[...]
Looks good. Built, signed, and uploaded.
Best,
Michael
pgpwxxdN84WF6.pgp
Description: PGP signature
Dear Michael,
Thanks for reviewing. Sorry for the late reply - I've been without
internet at home until yesterday.
On Sat, Jul 30, 2011 at 3:03 AM, Michael Tautschnig wrote:
>> I am looking for a sponsor for the new version 2.2.1-1
>> of my package "libharu".
>>
>> It builds these binary packag
Hi,
> Dear mentors,
>
> I am looking for a sponsor for the new version 2.2.1-1
> of my package "libharu".
>
> It builds these binary packages:
> (new) libhpdf-2.2.1 - C library for generating pdf files
> libhpdf-dev - C library for generating pdf files (development files)
>
> I've tested the pa
On Thu, Jul 14, 2011 at 1:18 PM, Paul Wise wrote:
> On Thu, Jul 14, 2011 at 1:14 PM, Johan Van de Wauw wrote:
>
>> - I've removed the .symbols because it is a bit irrelevant in a
>> package whose name changes when the so-name changes (see discussion on
>> d.mentors: [0].
>> [0]: http://lists.debia
On Thu, Jul 14, 2011 at 1:14 PM, Johan Van de Wauw wrote:
> - I've removed the .symbols because it is a bit irrelevant in a
> package whose name changes when the so-name changes (see discussion on
> d.mentors: [0].
> [0]: http://lists.debian.org/debian-mentors/2011/07/msg00365.html
Ahh, the packa
Dear mentors,
I am looking for a sponsor for the new version 2.2.1-1
of my package "libharu".
It builds these binary packages:
(new) libhpdf-2.2.1 - C library for generating pdf files
libhpdf-dev - C library for generating pdf files (development files)
I've tested the package and lintian does no
On Fri, Jun 18, 2010 at 10:27 PM, Johan Van de Wauw
wrote:
> 1) the source package contains bindings for python, pascal, freebasic,
> ruby and C#. Since my knowledge of those languages is too small to
> support these bindings, I chose not to package them (yet).
Fair enough.
> 2) Somewhat relate
Dear mentors/sponsors,
I have updated my libharu package, a C library for generating pdf files.
dget
http://mentors.debian.net/debian/pool/main/l/libharu/libharu_2.1.0+dfsg-1.dsc
Three notes:
1) the source package contains bindings for python, pascal, freebasic,
ruby and C#. Since my knowledge
On Thu, May 20, 2010 at 4:38 PM, Johan Van de Wauw
wrote:
> Makes sense. So is it ok to move the (updated) long description to the
> -dev package and use only a short description for libhpdf?
Probably yes. Obviously not everything will apply.
> I was randomly searching other libraries, and coul
Dear Paul,
Thanks for your (extensive!) review. Most of your comments were clear,
but still a few questions here:
On May 16, 5:50 am, Paul Wise wrote:
> The libhpdf-dev package description should have more detail than the
> libhpdf-2.1.0 description since the latter will always be
> automatical
On Sat, May 15, 2010 at 7:57 PM, Johan Van de Wauw
wrote:
> I am looking for a sponsor for my package "libharu".
Here is a review:
I assume you have read libpkg-guide and its bug reports?
The libhpdf-dev package description should have more detail than the
libhpdf-2.1.0 description since the l
Dear mentors,
I am looking for a sponsor for my package "libharu".
Package name: libharu
Version : 2.1.0-1
Upstream Author : Takeshi Kanno ,
Antony Dovgal , libh...@googlegroups.com
URL : http://libharu.org
License : ZLIB/LIBPNG License (see below)
Sect
34 matches
Mail list logo
