On 2016-10-17 08:07, Gianfranco Costamagna wrote:
Hi all
changed something and sponsored in deferred/12
Thanks, this has been a good learning experience.
Also thanks for fixing the bug references!
Thomas
On 2016-10-16 10:00, Gianfranco Costamagna wrote:
dh_auto_configure already injects some flags such as libdir and
multiarch stuff
it would be nice to remove them
[..]
Also, please take the opportunity to fix the changelog as josch
pointed out :)
Hi Gianfranco and Johannes,
the issues you
Hi Thomas,
(package removed from deferred queue)
>I have uploaded a new version to mentors with the two changes you
>mentioned in your mails today:
>- Using dh_auto_configure instead of calling ./configure directly.
mm nack :)
dh_auto_configure already injects some flags such as libdir and
Hi,
Quoting Thomas Pircher (2016-09-14 20:21:14)
> Changes since the last upload:
>
>* Non-maintainer upload.
>* New upstream release (closes: #833081, #811988, #798624, #645616).
I once made a similar mistake in one of my packages and just listed all the
closed bugs without writing
On 2016-10-15 12:35, Gianfranco Costamagna wrote:
BTW for a next update would be nice to consider using dh_auto_configure
instead of directly calling ./configure
Hi Gianfranco,
I have uploaded a new version to mentors with the two changes you
mentioned in your mails today:
- Using
On 2016-10-11 22:22, Gianfranco Costamagna wrote:
I see you forgot to probably run dh_clean
(I see debian/autoreconf.before and debian/autoreconf.after files)
D'oh. They were leftovers from a previous build and are gone now.
and I still see a libcgicc3-dev package (instead of libcgicc-dev)
Gianfranco Costamagna:
> Hi,
>
>> I have uploaded a new package to mentors, with the two outstanding
>
>> issues fixed.
>
> not sure...
> I see you forgot to probably run dh_clean
> (I see debian/autoreconf.before and debian/autoreconf.after files)
>
> [...]
>
> G.
>
That needs a
Hi,
>I have uploaded a new package to mentors, with the two outstanding
>issues fixed.
not sure...
I see you forgot to probably run dh_clean
(I see debian/autoreconf.before and debian/autoreconf.after files)
and I still see a libcgicc3-dev package (instead of libcgicc-dev)
>Thanks again for
On 2016-10-11 16:18, Gianfranco Costamagna wrote:
let me know that last two bits and I'll probably sponsor in deferred/10
(due to the high changes number)
(Adding Chris to the loop, in case he as maintainer has a different
opinion)
Hi Gianfranco,
I have uploaded a new package to mentors,
Hi,
>I missed to add you and 837...@bugs.debian.org in my last mail. In the
>upload to mentors from last week I have addressed your feedback (at
>least I think I did, that is). The only thing I'm not entirely sure
>about is the missing build-dependency on pkg-config as build-dependency,
>as
Hi Gianfranco,
I missed to add you and 837...@bugs.debian.org in my last mail. In the
upload to mentors from last week I have addressed your feedback (at
least I think I did, that is). The only thing I'm not entirely sure
about is the missing build-dependency on pkg-config as
On 2016-09-28 22:37, Gianfranco Costamagna wrote:
[..] drop the explicit dependencies since dh-autoreconf already
depends on automake and libtool? If this is the customary way then
I'll
drop the explicit dependencies on automake and libtool.
I think so. dh-autoreconf should be enough (with
Hi
> They are both used in the build. But if I understand you right, are you
> suggesting to drop the explicit dependencies since dh-autoreconf already
> depends on automake and libtool? If this is the customary way then I'll
> drop the explicit dependencies on automake and libtool.
I think
On 2016-09-18 19:11, Thomas Pircher wrote:
Thinking again, I guess that's not correct. This would require the
packages to be renamed to libcgicc3.
Hi,
I have uploaded a new build to debian mentors for further review.
https://mentors.debian.net/package/libcgicc
This build should address the
On 2016-09-18 17:39, Thomas Pircher wrote:
W: libcgicc5: package-name-doesnt-match-sonames libcgicc3
This should be fixed by the renaming from libcgicc5* -> libcgicc*.
Thinking again, I guess that's not correct. This would require the
packages to be renamed to libcgicc3.
Thomas
On 2016-09-15 10:49, Gianfranco Costamagna wrote:
changes are huge, but being half mia, and on lowNMU threshold...
(and too many bugs here, so lets do it)
First of all, thanks for the detailed review.
I have addressed most issues but not yet uploaded a new version to
mentors, pending a couple
Forgot lintian
9)
I: libcgicc source: binary-control-field-duplicates-source field "section" in
package libcgicc5
I: libcgicc source: quilt-patch-missing-description
0002-Non-empty-html-index.patch
I: libcgicc source: quilt-patch-missing-description
003-no-old-style-config.patch
W: libcgicc5:
control: owner -1 !
control: tags -1 moreinfo
Hi,> * Non-maintainer upload.
changes are huge, but being half mia, and on lowNMU threshold...
(and too many bugs here, so lets do it)
> * New upstream release (closes: #833081, #811988, #798624, #645616).> *
> Updated to Standards-Version
Package: sponsorship-requests
Severity: normal
Dear mentors,
having been unsuccessful in contacting the maintainer of this package
and after
having consulted m...@debian.org, I am looking for a sponsor for the
package
"libcgicc"
* Package name: libcgicc
Version : 3.2.16-0.1
19 matches
Mail list logo
