Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #69595 > unrolled thread

Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed

Started byBart Martens <bartm@debian.org>
First post2021-02-22 12:10 +0100
Last post2022-05-19 04:40 +0200
Articles 6 — 4 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed Bart Martens <bartm@debian.org> - 2021-02-22 12:10 +0100
    Processed: Re: Bug#983314: linux-base: perf fails to report that  linux-perf-5.10 is not installed "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-02-26 07:00 +0100
    Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed Salvatore Bonaccorso <carnil@debian.org> - 2021-02-26 07:00 +0100
      Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed Jose R Rodriguez <jose.r.r@metztli.com> - 2021-02-26 08:10 +0100
      Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed Salvatore Bonaccorso <carnil@debian.org> - 2021-02-27 17:40 +0100
    Bug#983314: marked as done (linux-base: perf fails to report that  linux-perf-5.10 is not installed) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-05-19 04:40 +0200

#69595 — Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed

FromBart Martens <bartm@debian.org>
Date2021-02-22 12:10 +0100
SubjectBug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed
Message-ID<BLhgd-3s6-1@gated-at.bofh.it>
Package: linux-base
Version: 4.6
Severity: minor
File: /usr/bin/perf

Observed behavior:

$ perf
/usr/bin/perf: line 13: exec: perf_5.10: not found

Expected behavior:

$ perf
/usr/bin/perf: line 14: exec: perf_5.10: not found
E: linux-perf-5.10 is not installed.

[toc] | [next] | [standalone]


#69621 — Processed: Re: Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2021-02-26 07:00 +0100
SubjectProcessed: Re: Bug#983314: linux-base: perf fails to report that linux-perf-5.10 is not installed
Message-ID<BMEkp-4oM-3@gated-at.bofh.it>
In reply to#69595
Processing control commands:

> tags -1 + confirmed
Bug #983314 [linux-base] linux-base: perf fails to report that linux-perf-5.10 is not installed
Added tag(s) confirmed.

-- 
983314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983314
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#69622

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-02-26 07:00 +0100
Message-ID<BMEkp-4oM-1@gated-at.bofh.it>
In reply to#69595
Control: tags -1 + confirmed

Hi Bart,

On Mon, Feb 22, 2021 at 11:57:56AM +0100, Bart Martens wrote:
> Package: linux-base
> Version: 4.6
> Severity: minor
> File: /usr/bin/perf
> 
> Observed behavior:
> 
> $ perf
> /usr/bin/perf: line 13: exec: perf_5.10: not found
> 
> Expected behavior:
> 
> $ perf
> /usr/bin/perf: line 14: exec: perf_5.10: not found
> E: linux-perf-5.10 is not installed.

That's intersting, confirmed. The script is the same since the buster
release without changes, but it looks it behaves differently in a buster
vs.  unstable/bullseye environment when the replacement ${version%%-*}
is involved after the version setting:

,---- [ perf-minimal ]
| #!/bin/bash
|
| version="$(uname -r)"
| version="${version%%-*}"
| shopt -s execfail
| exec "perf_$version" "$@"
| echo >&2 "E: not installed."
| exit 1
`----

In an buster environment:

++ uname -r
+ version=4.19.0-14-amd64
+ version=4.19.0
+ shopt -s execfail
+ exec perf_4.19.0
./perf-minimal: line 6: exec: perf_4.19.0: not found
+ echo 'E: not installed.'
E: not installed.
+ exit 1

In an unstable environment:

bash -x ./perf-minimal 
++ uname -r
+ version=4.19.0-14-amd64
+ version=4.19.0
+ shopt -s execfail
+ exec perf_4.19.0
./perf-minimal: line 6: exec: perf_4.19.0: not found

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#69623

FromJose R Rodriguez <jose.r.r@metztli.com>
Date2021-02-26 08:10 +0100
Message-ID<BMFq9-5fE-1@gated-at.bofh.it>
In reply to#69622
On Fri, 2021-02-26 at 06:47 +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + confirmed
> 
> Hi Bart,
> 
> On Mon, Feb 22, 2021 at 11:57:56AM +0100, Bart Martens wrote:
> > Package: linux-base
> > Version: 4.6
> > Severity: minor
> > File: /usr/bin/perf
> > 
> > Observed behavior:
> > 
> > $ perf
> > /usr/bin/perf: line 13: exec: perf_5.10: not found
> > 
> > Expected behavior:
> > 
> > $ perf
> > /usr/bin/perf: line 14: exec: perf_5.10: not found
> > E: linux-perf-5.10 is not installed.

FYI Debian Buster backports AMD64 provides 'Expected behavor' in a debian
packaging for 5.10.15-2 reiser4 build hack running in an AMD Epyc/Ryzen cloud
instance:
https://metztli.it/buster/perf.png

> 
> That's intersting, confirmed. The script is the same since the buster
> release without changes, but it looks it behaves differently in a buster
> vs.  unstable/bullseye environment when the replacement ${version%%-*}
> is involved after the version setting:
> 
> ,---- [ perf-minimal ]
> > #!/bin/bash
> > 
> > version="$(uname -r)"
> > version="${version%%-*}"
> > shopt -s execfail
> > exec "perf_$version" "$@"
> > echo >&2 "E: not installed."
> > exit 1
> `----
> 
> In an buster environment:
> 
> ++ uname -r
> + version=4.19.0-14-amd64
> + version=4.19.0
> + shopt -s execfail
> + exec perf_4.19.0
> ./perf-minimal: line 6: exec: perf_4.19.0: not found
> + echo 'E: not installed.'
> E: not installed.
> + exit 1
> 
> In an unstable environment:
> 
> bash -x ./perf-minimal 
> ++ uname -r
> + version=4.19.0-14-amd64
> + version=4.19.0
> + shopt -s execfail
> + exec perf_4.19.0
> ./perf-minimal: line 6: exec: perf_4.19.0: not found
> 
> Regards,
> Salvatore
> 

Best Professional Regards.

-- 
-- 
Jose R R
http://metztli.it
-----------------------------------------------------------------------
Download Metztli Reiser4: Debian Buster w/ Linux 5.9.16 AMD64
-----------------------------------------------------------------------
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
-----------------------------------------------------------------------
or SFRN 5.1.3, Metztli Reiser5 https://sf.net/projects/debian-reiser4/
-----------------------------------------------------------------------
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/

[toc] | [prev] | [next] | [standalone]


#69644

FromSalvatore Bonaccorso <carnil@debian.org>
Date2021-02-27 17:40 +0100
Message-ID<BNaNj-7cK-5@gated-at.bofh.it>
In reply to#69622
Hi,

On Fri, Feb 26, 2021 at 06:47:57AM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + confirmed
> 
> Hi Bart,
> 
> On Mon, Feb 22, 2021 at 11:57:56AM +0100, Bart Martens wrote:
> > Package: linux-base
> > Version: 4.6
> > Severity: minor
> > File: /usr/bin/perf
> > 
> > Observed behavior:
> > 
> > $ perf
> > /usr/bin/perf: line 13: exec: perf_5.10: not found
> > 
> > Expected behavior:
> > 
> > $ perf
> > /usr/bin/perf: line 14: exec: perf_5.10: not found
> > E: linux-perf-5.10 is not installed.
> 
> That's intersting, confirmed. The script is the same since the buster
> release without changes, but it looks it behaves differently in a buster
> vs.  unstable/bullseye environment when the replacement ${version%%-*}
> is involved after the version setting:
> 
> ,---- [ perf-minimal ]
> | #!/bin/bash
> |
> | version="$(uname -r)"
> | version="${version%%-*}"
> | shopt -s execfail
> | exec "perf_$version" "$@"
> | echo >&2 "E: not installed."
> | exit 1
> `----
> 
> In an buster environment:
> 
> ++ uname -r
> + version=4.19.0-14-amd64
> + version=4.19.0
> + shopt -s execfail
> + exec perf_4.19.0
> ./perf-minimal: line 6: exec: perf_4.19.0: not found
> + echo 'E: not installed.'
> E: not installed.
> + exit 1
> 
> In an unstable environment:
> 
> bash -x ./perf-minimal 
> ++ uname -r
> + version=4.19.0-14-amd64
> + version=4.19.0
> + shopt -s execfail
> + exec perf_4.19.0
> ./perf-minimal: line 6: exec: perf_4.19.0: not found

Experimenting further a bit, and set up a buster system then only
updated bash seems to trigger the issue:

root@bash-test:~# ./perf-minimal
./perf-minimal: line 6: exec: perf_4.19.0: not found
E: not installed.
root@bash-test:~# apt-get install bash
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  bash-doc
Recommended packages:
  bash-completion
The following packages will be upgraded:
  bash
1 upgraded, 0 newly installed, 0 to remove and 213 not upgraded.
Need to get 1,417 kB of archives.
After this operation, 31.7 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 bash amd64 5.1-2+b1 [1,417 kB]
Fetched 1,417 kB in 0s (14.8 MB/s)
(Reading database ... 20940 files and directories currently installed.)
Preparing to unpack .../bash_5.1-2+b1_amd64.deb ...
Unpacking bash (5.1-2+b1) over (5.0-4) ...
Setting up bash (5.1-2+b1) ...
update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
root@bash-test:~# ./perf-minimal
./perf-minimal: line 6: exec: perf_4.19.0: not found
root@bash-test:~#

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#75273 — Bug#983314: marked as done (linux-base: perf fails to report that linux-perf-5.10 is not installed)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2022-05-19 04:40 +0200
SubjectBug#983314: marked as done (linux-base: perf fails to report that linux-perf-5.10 is not installed)
Message-ID<EoEeZ-gqO9-11@gated-at.bofh.it>
In reply to#69595

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 19 May 2022 02:33:55 +0000
with message-id <E1nrVz9-0002kp-2k@fasolo.debian.org>
and subject line Bug#983314: fixed in linux-base 4.9
has caused the Debian Bug report #983314,
regarding linux-base: perf fails to report that linux-perf-5.10 is not installed
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.)


-- 
983314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983314
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web