[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#897046: marked as done (RFS: link-grammar/5.5.0-1 [QA upload])

Your message dated Tue, 01 May 2018 14:04:32 -0400
with message-id <87o9hz9rrj.fsf@sergiodj.net>
and subject line Re: Bug#897046: RFS: link-grammar/5.4.4-1 [QA upload]
has caused the Debian Bug report #897046,
regarding RFS: link-grammar/5.5.0-1 [QA upload]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
897046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897046
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for a QA upload of the link-grammar
package.

My changes are summarized in the latest changelog entry:

  link-grammar (5.4.4-1) unstable; urgency=medium

    * QA upload.
    * New upstream release.
    * Update symbols file.
    * Remove trailing whitespace from debian/changelog in order to
      silence the file-contains-trailing-whitespace Lintian tag.
    * Upgrade to debhelper compat version 11.
    * Remove the empty file debian/patches/series.
    * Use HTTPS URI in debian/watch.
    * Upgrade to Standards-Version 4.1.4 (no changes).
    * Add debian/python3-link-grammar.lintian-overrides to override the
      python-package-depends-on-package-from-other-python-variant
      Lintian tag.
    * Update Vcs-Browser and Vcs-Git fields in debian/control.
    * Update Homepage field in debian/control and Source field in
      debian/copyright to use HTTPS.
    * Remove incorrect Multi-Arch fields in debian/control.

   -- Fabian Wolff <fabi.wolff@arcor.de>  Fri, 27 Apr 2018 15:35:36 +0200


I have to admit that I'm not entirely sure about the Multi-Arch fields
that I removed. The link-grammar binary package installs an
architecture-dependent binary into /usr/bin, but it was marked
Multi-Arch: foreign, which looked suspect to me. Also, the
liblink-grammar-java package seems to have an incorrect Multi-Arch
field according to the Multiarch hinter:

  https://tracker.debian.org/pkg/link-grammar

Other than that, I made sure that the autopkgtests pass and that the
package is mostly Lintian-clean, save for several
package-has-unnecessary-activation-of-ldconfig-trigger warnings
(which, according to the Lintian tag documentation, might be due to a
debhelper bug) and an orig-tarball-missing-upstream-signature warning
(which I would blame on git-buildpackage, see #872864).

The package is available on Mentors:

  https://mentors.debian.net/package/link-grammar

Thank you!

Best regards,
Fabian

--- End Message ---
--- Begin Message --- 
On Tuesday, May 01 2018, Fabian Wolff wrote:

> On Mon, Apr 30, 2018 at 08:27:02PM -0400, Sergio Durigan Junior wrote:
>> Hm, I think you forgot to push the upstream/pristine-tar branches,
>> because I can't rebuild the tarball here.  Could you do that, please?
>
> Are you sure? The upstream/5.5.0 tag seems to be available in the
> Salsa repository:
>
>   https://salsa.debian.org/debian/link-grammar/tags/upstream%2F5.5.0
>
> Also, I just tried to reproduce your problem by cloning the Salsa
> repository in an empty directory on my system and then running
> gbp-buildpackage, but everything worked fine for me. Could you perhaps
> give me some more details about your problem?

That's strange.  I had the repository cloned from salsa here, and doing
"git pull" wouldn't pull the changes to the pristine-tar/upstream
branches.  I deleted everything and cloned again, and now I have the
most recent commits.

Anyway, I've uploaded the package now.  Thanks a lot.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: