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


Groups > linux.debian.bugs.rc > #353007 > unrolled thread

Bug#1059036: mdevctl FTBFS with nocheck profile: missing Build-Depends

Started byHelmut Grohne <helmut@subdivi.de>
First post2023-12-19 17:20 +0100
Last post2024-01-04 10:40 +0100
Articles 4 — 4 participants

Back to article view | Back to linux.debian.bugs.rc


Contents

  Bug#1059036: mdevctl FTBFS with nocheck profile: missing Build-Depends Helmut Grohne <helmut@subdivi.de> - 2023-12-19 17:20 +0100
    Bug#1059036: mdevctl FTBFS with nocheck profile: Cargo.toml needs adjustment Athos Ribeiro <athos.ribeiro@canonical.com> - 2023-12-22 12:50 +0100
    Bug#1059036: Thank you Athos, merged and uploading ... Christian Ehrhardt <christian.ehrhardt@canonical.com> - 2024-01-04 10:30 +0100
    Bug#1059036: marked as done (mdevctl FTBFS with nocheck profile:  missing Build-Depends) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-01-04 10:40 +0100

#353007 — Bug#1059036: mdevctl FTBFS with nocheck profile: missing Build-Depends

FromHelmut Grohne <helmut@subdivi.de>
Date2023-12-19 17:20 +0100
SubjectBug#1059036: mdevctl FTBFS with nocheck profile: missing Build-Depends
Message-ID<HMKZ3-eFDZ-11@gated-at.bofh.it>
Source: mdevctl
Version: 1.2.0-5
Severity: serious
Tags: ftbfs

mdevctl fails to build from source when building with the nocheck build
profile. Since trixie, such a failure is considered release critical by
the release team. A build log ends as follows:

|    dh_auto_install --destdir=debian/mdevctl/ -O--buildsystem=cargo
|         install -m0755 -d /<<PKGBUILDDIR>>/debian/mdevctl
|         find . ! -newermt 'jan 01, 2000' -exec touch -d@1698049260 {} +
|         env DESTDIR=debian/mdevctl /usr/share/cargo/bin/cargo install
| debian cargo wrapper: options, profiles, parallel, lto: ['nocheck', 'parallel=1'] ['nocheck'] ['-j1'] 0
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, x86_64-linux-gnu
| debian cargo wrapper: installing into destdir 'debian/mdevctl' prefix '/usr'
| debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 'CARGO_TARGET_DIR=/<<PKGBUILDDIR>>/target', '/usr/bin/cargo', '-Zavoid-dev-deps', 'install', '--verbose', '--verbose', '-j1', '--target', 'x86_64-unknown-linux-gnu', '--path', '/<<PKGBUILDDIR>>', '--root', 'debian/mdevctl/usr'],) {'check': True}
|   Installing mdevctl v1.2.0 (/<<PKGBUILDDIR>>)
| error: failed to compile `mdevctl v1.2.0 (/<<PKGBUILDDIR>>)`, intermediate artifacts can be found at `/<<PKGBUILDDIR>>/target`
| 
| Caused by:
|   no matching package named `tempfile` found
|   location searched: registry `crates-io`
|   required by package `mdevctl v1.2.0 (/<<PKGBUILDDIR>>)`
| Traceback (most recent call last):
|   File "/usr/share/cargo/bin/cargo", line 257, in <module>
|     sys.exit(main(*sys.argv[1:]))
|              ^^^^^^^^^^^^^^^^^^^
|   File "/usr/share/cargo/bin/cargo", line 247, in main
|     return install(os.getenv("DESTDIR", ""),
|            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|   File "/usr/share/cargo/bin/cargo", line 134, in install
|     logrun(["env", "RUST_BACKTRACE=1",
|   File "/usr/share/cargo/bin/cargo", line 76, in logrun
|     return subprocess.run(*args, **kwargs)
|            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|   File "/usr/lib/python3.11/subprocess.py", line 571, in run
|     raise CalledProcessError(retcode, process.args,
| subprocess.CalledProcessError: Command '['env', 'RUST_BACKTRACE=1', 'CARGO_TARGET_DIR=/<<PKGBUILDDIR>>/target', '/usr/bin/cargo', '-Zavoid-dev-deps', 'install', '--verbose', '--verbose', '-j1', '--target', 'x86_64-unknown-linux-gnu', '--path', '/<<PKGBUILDDIR>>', '--root', 'debian/mdevctl/usr']' returned non-zero exit status 101.
| dh_auto_install: error: env DESTDIR=debian/mdevctl /usr/share/cargo/bin/cargo install returned exit code 1
| make: *** [debian/rules:9: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

I guess that librust-tempfile-dev really shouldn't be annotated
<!nocheck>.

Helmut

[toc] | [next] | [standalone]


#353178 — Bug#1059036: mdevctl FTBFS with nocheck profile: Cargo.toml needs adjustment

FromAthos Ribeiro <athos.ribeiro@canonical.com>
Date2023-12-22 12:50 +0100
SubjectBug#1059036: mdevctl FTBFS with nocheck profile: Cargo.toml needs adjustment
Message-ID<HNMcp-fiN9-1@gated-at.bofh.it>
In reply to#353007
Thanks, Helmut.

This actually needs adjustment in the upstream Cargo.toml file.

The package is listed as a dependency when it should actually be listed
as a dev-dependency.

I proposed a patch upstream in https://github.com/mdevctl/mdevctl/pull/107 and filed a salsa MR to fix this package in https://salsa.debian.org/debian/mdevctl/-/merge_requests/9.

-- 
Athos Ribeiro

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


#353715 — Bug#1059036: Thank you Athos, merged and uploading ...

FromChristian Ehrhardt <christian.ehrhardt@canonical.com>
Date2024-01-04 10:30 +0100
SubjectBug#1059036: Thank you Athos, merged and uploading ...
Message-ID<HSsd5-Hdd-15@gated-at.bofh.it>
In reply to#353007

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

Thanks to Athos proposed fix that was easy to fix.
In the meantime it also has been upstream accepted and I ran a test build
with and without nocheck which both worked fine.

I updated git and I'm uploading debian/1.2.0-6

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


#353718 — Bug#1059036: marked as done (mdevctl FTBFS with nocheck profile: missing Build-Depends)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-01-04 10:40 +0100
SubjectBug#1059036: marked as done (mdevctl FTBFS with nocheck profile: missing Build-Depends)
Message-ID<HSsmJ-Hgt-15@gated-at.bofh.it>
In reply to#353007

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

Your message dated Thu, 04 Jan 2024 09:34:30 +0000
with message-id <E1rLK7S-00B2N5-12@fasolo.debian.org>
and subject line Bug#1059036: fixed in mdevctl 1.2.0-6
has caused the Debian Bug report #1059036,
regarding mdevctl FTBFS with nocheck profile: missing Build-Depends
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.)


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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web