Bug#823474: RFS: btrfs-progs/4.5.2-0.1~exp1
On 9 May 2016 at 13:18, Gianfranco Costamagna <locutusofborg@debian.org> wrote:
>>Per https://wiki.debian.org/ftpmaster_Removals , I filed Bug #823848
>>"as an RC bug on the package".
>
> I have reassigned it to ftpmasters, I don't think there is need to wait for
> the maintainer opinion, this is a binary without source.
Thank you.
>>I did two runs of license-reconsile, after fixing the MIT/X11 license
>>issue for config/install-sh. In the first run I kept the existing
>>GPL-2+ designations; wc -l returned 212 lines. For the second run I
>>changed most instances of GPL-2+ to GPL-2; wc -l returned 126. Based
>>on this, and the fact that the official btrfs-progs*/COPYING file
>>states:
>
> I see README.md saying this is GPL-2, so you might want to change to GPL-2
> and list all the GPL-2+ files explicitly.
Done. I did a couple of nme runs in a sid chroot, and then fixed
lintian errors. It might be possible to compact the debian/copying
stanza, but my goal was maximum correctness so I didn't take any
risks. Lintian said that copyright entries for config/* weren't
necessary. Is this true? I removed them on the assumption that they
were.
>>Thank you for notifying me of this Gianfranco. It also affects>oldstable and
>>stable. Is this an RC/serious level bug for all affected versions?
>
> BTW this might be RC, but I'm not sure it is worth fixing it in stable.
>
> I'll wait for some more appropriate answer here maybe :)
Ok, I'll wait too. :-)
Updated package has been uploaded to the same location. If
successfully completing a license review/update isn't on a
debian-mentorship checklist, then it really ought to be! Thank you
for the opportunity to learn something of fundamental importance to
the Debian-way of doing things.
One more concern: E - Package closes bugs in a wrong way. Bug
#801192 does not belong to this package. I know this is a "teaching
moment." What is the correct way to tag #801192 (owned by
btrfs-tools) so that it can be closed by btrfs-progs? I'd like to
send the email to control@ myself, and I suspect this needs to be done
before you upload this package. ;-)
Cheers,
Nicholas
Reply to: