On Sun, May 28, 2017 at 6:53 AM, Nis Martensen wrote:
> Hey Sandro!
>
>> should we revert to the previous behavior of get_command_output before
>> introducing other regressions?
>
> Having re-read the code again, I can't see any risk of introducing other
> regressions.
all
Hey Sandro!
> should we revert to the previous behavior of get_command_output before
> introducing other regressions?
Having re-read the code again, I can't see any risk of introducing other
regressions.
Only lsb_release_info() and get_arch() directly return the result of
get_command_output(),
Hey Nis!
On Tue, Apr 25, 2017 at 5:56 PM, Nis Martensen wrote:
> Let's fix this before we find out exactly what else was broken by my
> patch in reportbug 7.1.6.
should we revert to the previous behavior of get_command_output before
introducing other regressions?
--
Paul Wise wrote:
> Package: reportbug
> Version: 7.1.6
> Severity: minor
>
> The architecture field is currently split into two lines:
>
> Architecture: amd64
> (x86_64)
>
> With earlier versions of reportbug it was only one line:
>
> https://bugs.debian.org/823456
> Architecture: amd64
Package: reportbug
Version: 7.1.6
Severity: minor
The architecture field is currently split into two lines:
Architecture: amd64
(x86_64)
With earlier versions of reportbug it was only one line:
https://bugs.debian.org/823456
Architecture: amd64 (x86_64)
-- System Information:
Debian Release:
5 matches
Mail list logo