Your message dated Sat, 31 Dec 2022 22:34:43 +0000
with message-id <e1pbkr9-00hxkg...@fasolo.debian.org>
and subject line Bug#1027449: fixed in ruby-dbm 1.1.0-2
has caused the Debian Bug report #1027449,
regarding d/copyright is wrong
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.)


-- 
1027449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-dbm
Severity: serious
User: paul...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

I've filed the bug since I wasn't sure if my email made it through due
to SMTP issues. Since I didn't see anything in git or any other acks,
I'll file the bug to help with tracking the issue.

I've marked this package for ACCEPT last night.

The debian/coypright file describes source files, not binaries. It looks
like ruby-dbm's copyright file added GPL-3+ because of the GDBM
implementation we link to, which is a welcome degree of diligence I do
appreciate, but it may change without the involvement of this source
package (if the implementation were to change, or how a downstream
changes the way the deb is built). If we had to list all the licensing
information of all our build-deps / links, things would get very messy
indeed! I'd expect someone to look through the dependency tree iff they
need to determine the binary distribution terms.

  paultag (on behalf of the ftpteam)

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: ruby-dbm
Source-Version: 1.1.0-2
Done: Antonio Terceiro <terce...@debian.org>

We believe that the bug you reported is fixed in the latest version of
ruby-dbm, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro <terce...@debian.org> (supplier of updated ruby-dbm 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: SHA256

Format: 1.8
Date: Sat, 31 Dec 2022 19:17:33 -0300
Source: ruby-dbm
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Antonio Terceiro <terce...@debian.org>
Closes: 1027449
Changes:
 ruby-dbm (1.1.0-2) unstable; urgency=medium
 .
   * debian/copyright: drop notes about licensing of resulting binaries
     (Closes: #1027449)
Checksums-Sha1:
 f77d8b30a18242d82325c4c845293f47cbfd0783 1991 ruby-dbm_1.1.0-2.dsc
 b78d574c76eae8a775399219431c7a018a3f28cf 2452 ruby-dbm_1.1.0-2.debian.tar.xz
 1034332d51aa9f058741c0b385768de3f93b8bdc 9806 ruby-dbm_1.1.0-2_amd64.buildinfo
Checksums-Sha256:
 43d0542ee920f5877cecbf6d7d3c4459d8e2163b4fcd146e35007a4f940562e9 1991 
ruby-dbm_1.1.0-2.dsc
 e800c0121e981f3821788c29aa31f7de7c9f59f434a8559cf7808beef358ac9c 2452 
ruby-dbm_1.1.0-2.debian.tar.xz
 e14719ddb4b79998c317df73f794f79f4e60539da631d37e1fcbed549869d9cc 9806 
ruby-dbm_1.1.0-2_amd64.buildinfo
Files:
 646ecd0f532064a489d0645daeb89b5a 1991 ruby optional ruby-dbm_1.1.0-2.dsc
 59fc0e454a117f7b9bc172d18bc9d259 2452 ruby optional 
ruby-dbm_1.1.0-2.debian.tar.xz
 c6efacec72674c13281eb9038c59a1ea 9806 ruby optional 
ruby-dbm_1.1.0-2_amd64.buildinfo

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

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmOwtbkACgkQ/A2xu81G
C96KOw/+P/0xOLExH19AI+/G7Dr/CdGIIxQ8OCRxShfGh6XWG3aLroCIEt1Ag8LS
of/l9CQZItoTu/yJG7xZMbwnQOOkGO8qmyf/lOMrERm09mkqqy/tvHi/Jo90HKeC
6Stlt/EMqGZFlXRDn6Qqee9c5xbJ69CQSOZxLzaC64F2mcmJYCfARFB74By2/Xyn
LWXGssKeM50naubXl/ubQjlVU5E3d0A4/xS0iHba8a5SXhRpwzTH40bZeqjClLcq
NCvZ4cD0UnQm8K9seMcWdjPhSbcCQfLwNX1OeePGGgfqCUS1057Jq39NeAxA49Px
nZPdakt7y9h++S4GhFfDuAfZTL6Q0w8/7e8LhFPe0oBvYUWtG6frtvKkLgWr1Cvi
1jXHT3VFhXYzXiGW38wY8O41b+CGfd3KRFVNPxtJsqCjV8yTo1YAOT6Rj+dL6HaA
M7j7AxXMu6QxdD7d4olHQa3aXtQmrw0QXBv0to1WU0zj/XFrky6lV3TOWw+McB+T
QIlNiX1BkLd0Arjbjx49iloaSGvgZXa7OosrJP88xA20jDnWOQRs0LDM64o7rhi+
xpwnuhLWPLejZLwwSYL1nSvOD7zY7GOj5w3C8zNWr8a/hMqr/5JxgrVy16lVLAU1
LOh6hA7+17nvAgrqccR2PSidsmV0cIZjqgH4PR83gVsh7mioPI8=
=8BgY
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to