Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Gianfranco Costamagna
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 mentioned in

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Johan Van de Wauw
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

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Johan Van de Wauw
On Thu, Aug 20, 2015 at 11:19 AM, Gianfranco Costamagna costamagnagianfra...@yahoo.it 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

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Johan Van de Wauw
On Thu, Aug 20, 2015 at 10:29 AM, Gianfranco Costamagna costamagnagianfra...@yahoo.it 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

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Jakub Wilk
* Gianfranco Costamagna costamagnagianfra...@yahoo.it, 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

Re: Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Sebastiaan Couwenberg
On 20-08-15 12:52, Jakub Wilk wrote: * Gianfranco Costamagna costamagnagianfra...@yahoo.it, 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

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Gianfranco Costamagna
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 a

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Johan Van de Wauw
On Thu, Aug 20, 2015 at 12:29 PM, Gianfranco Costamagna costamagnagianfra...@yahoo.it 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

Re: Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Gianfranco Costamagna
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 link

Re: Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Jakub Wilk
* Gianfranco Costamagna costamagnagianfra...@yahoo.it, 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

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Gianfranco Costamagna
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

Bug#796191: RFS: libharu/2.3.0+dfsg-1~exp1

2015-08-20 Thread Gianfranco Costamagna
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/triplet, so this is no longer show-stopper. nice to know :) If the symlink lives in architecture-specific directory, it's not an