Your message dated Sat, 2 Dec 2017 17:39:10 +0100 with message-id <20171202163910.aheotz7gykbluojt@betterave.cristau.org> and subject line Re: Bug#863956: unblock: golang-1.7/1.7.6-1, golang-1.8/1.8.3-1 has caused the Debian Bug report #863956, regarding unblock: golang-1.7/1.7.6-1, golang-1.8/1.8.3-1 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.) -- 863956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863956 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: golang-1.7/1.7.6-1, golang-1.8/1.8.3-1
- From: Hilko Bengen <bengen@debian.org>
- Date: Fri, 02 Jun 2017 11:46:33 +0200
- Message-id: <87tw3yzpqe.fsf@msgid.hilluzination.de>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Dear release team, please unblock packages golang-1.7 and golang-1.8. Package golang-1.7 in stretch would be upgraded from version 1.7.4-2 to 1.7.6-1. Package golang-1.8 in stretch would be upgraded from version 1.8.1-1 to 1.8.3-1. Both are minor bugfix releases and fix security issue CVE-2017-8932. There are no changes regarding the packaging except that golang-1.7/1.7.6-1 drops a timezone-related patch that has been applied upstream. Cheers, -Hilko [1] https://golang.org/doc/devel/release.html#go1.7.minor [2] https://golang.org/doc/devel/release.html#go1.8.minor
--- End Message ---
--- Begin Message ---
- To: Hilko Bengen <bengen@debian.org>, 863956-done@bugs.debian.org
- Cc: Jonathan Wiltshire <jmw@debian.org>
- Subject: Re: Bug#863956: unblock: golang-1.7/1.7.6-1, golang-1.8/1.8.3-1
- From: Julien Cristau <jcristau@debian.org>
- Date: Sat, 2 Dec 2017 17:39:10 +0100
- Message-id: <20171202163910.aheotz7gykbluojt@betterave.cristau.org>
- In-reply-to: <87poefy42l.fsf@msgid.hilluzination.de>
- References: <87tw3yzpqe.fsf@msgid.hilluzination.de> <20170606214358.24dwui7a6j7brpfz@powdarrmonkey.net> <87shjclpgo.fsf@nomad.hilluzination.de> <20170606224327.vh7caemyzszv2n7k@powdarrmonkey.net> <87poefy42l.fsf@msgid.hilluzination.de>
On Wed, Jun 7, 2017 at 21:45:38 +0200, Hilko Bengen wrote: > I'm sorry for not including or even thinking about this information for > my initial request (mistake #1). > > By using a too simple grep-dctrl query (mistake #2), I included source > packages that only generate golang-*-dev packages which are > "Architecture: all" and which only contain a copy of the source code in > /usr/share/gocode. There is no need to rebuild those packages. > > Using a query that ignores the "Architecture: all" packages... > > ,---- > | apt-cache dumpavail | \ > | grep-dctrl \ > | -F Built-Using 'golang-1.7' -a \ > | '(' --not -F Architecture all ')' \ > | -s Source,Package,Version > `---- > > ... my count for the number of source packages drops from 107 to 63, see > below. This still is too much, right? > > In any case, is there going to be a way to rebuild/update those > remaining 63 source packages via a point release? > No, that's way too much churn for stable. Cheers, Julien, going through his -release mail backlog
--- End Message ---