Your message dated Sun, 16 Dec 2018 12:20:13 +0000
with message-id <e1gyvp3-0008kw...@fasolo.debian.org>
and subject line Bug#910228: fixed in ruby-gitlab 4.5.0-2
has caused the Debian Bug report #910228,
regarding ruby-gitlab: file conflict with gitlab-cli
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 ow...@bugs.debian.org
immediately.)


-- 
910228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gitlab
Version: 4.5.00-1
Severity: serious
Affects: src:python-gitlab
X-Debbugs-CC: bou...@debian.org, sop...@freexian.com

Both ruby-gitlab and gitlab-cli ship /usr/bin/gitlab and
/usr/share/man/man1/gitlab.1.gz

This is a violation of the first paragraph of Debian Policy § 10.1

https://www.debian.org/doc/debian-policy/ch-files.html

I suggest that both packages rename their scripts. How about
ruby-gitlab and python-gitlab?

Thanks,
Jeremy Bicha

--- End Message ---
--- Begin Message ---
Source: ruby-gitlab
Source-Version: 4.5.0-2

We believe that the bug you reported is fixed in the latest version of
ruby-gitlab, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond <s...@debian.org> (supplier of updated ruby-gitlab package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 26 Nov 2018 17:30:03 +0100
Source: ruby-gitlab
Binary: ruby-gitlab
Architecture: source
Version: 4.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Sebastien Delafond <s...@debian.org>
Description:
 ruby-gitlab - Ruby wrapper and CLI for the GitLab API
Closes: 910228
Changes:
 ruby-gitlab (4.5.0-2) unstable; urgency=medium
 .
   [ Sébastien Delafond ]
   * Rename /usr/bin/gitlab to /usr/bin/ruby-gitlab (Closes: #910228)
   * Add myself to Uploaders
Checksums-Sha1:
 a47b59af465073a9445ce19ae64b7860bc3f6f34 1769 ruby-gitlab_4.5.0-2.dsc
 c002d05d06e3e03b79cb3f68602295c84ab9430a 3556 ruby-gitlab_4.5.0-2.debian.tar.xz
 0edcd7f6c7c943356d59896ed3b69d4e13999350 9986 
ruby-gitlab_4.5.0-2_amd64.buildinfo
Checksums-Sha256:
 c02768cc529a4e49a983a46513b8ec0191659a1bf96c11ee8ea17a08ec2f0665 1769 
ruby-gitlab_4.5.0-2.dsc
 d384891c5341b539d449e43534e99382ed21c624de31f0ccca3c24f5273a8026 3556 
ruby-gitlab_4.5.0-2.debian.tar.xz
 0735f7b8c6c20eabcda12ff4771828146b1985e02f7f2462efd65077874b855d 9986 
ruby-gitlab_4.5.0-2_amd64.buildinfo
Files:
 260a40df397131a22b4ae24ce6d61049 1769 ruby optional ruby-gitlab_4.5.0-2.dsc
 ea1893d893d3deffb62608bbf0d3481c 3556 ruby optional 
ruby-gitlab_4.5.0-2.debian.tar.xz
 d3f58d8bb8ecb70b515c44c82bcb7107 9986 ruby optional 
ruby-gitlab_4.5.0-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAlwWP28ACgkQEL6Jg/PV
nWQOiAf+LmGgnZXq2wUf6QSOKXUNlDckeiKQDZTmg9ihGcJXoW0aSCZ3e7r88aqT
j2JK9otIcKK7DC5BDe/d56zKP+Jefg3lh2B57+bpSsymWHcLA4ZfHIGt6CB/As/z
9jJpowW95r+Gv17DZT9uruzUwKE+ENTLyMxfw3nvtsxsqrKXPA5j273WluGpE/SU
6VczSZjEmSKt1RVJ1AbwAuCYBdKDl+fpu8Y/GqXpHAzh7vKQ+HybtlhNbJ5sBmXV
OJ1qWRJdxleKW+6hEP0rERb6CLOeJN64wgyaZfqeRz7psBG7BTcEnk9A07fKdGxO
0TRNdx6atBp3PkhhP+KT7TFlnHywmw==
=pdvS
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to