* [ISSUE] wired-notify : Cargo.lock --locked @ 2024-02-17 10:04 biopsin 2024-02-17 13:18 ` tranzystorekk ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: biopsin @ 2024-02-17 10:04 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 1264 bytes --] New issue by biopsin on void-packages repository https://github.com/void-linux/void-packages/issues/48794 Description: ### Is this a new report? Yes ### System Info Linux voidx 5.10.209_1 #1 SMP UTC x86_64 GNU/Linux ### Package(s) Affected wired-notify : update to 0.10.4_1 ### Does a report exist for this bug with the project's home (upstream) and/or another distro? Upstream: no void: https://github.com/void-linux/void-packages/pull/43233 ### Expected behaviour Cargo.lock is updated I looked at other packages with same issue and while Cargo.lock is supplied in wired-notify I just ran `cargo generate-lockfile` for a successfull build unless there is a bether patch approach? ### Actual behaviour ``` => wired-notify-0.10.4_1: running do_build ... error: the lock file /builddir/wired-notify-0.10.4/Cargo.lock needs to be updated but was passed to prevent this If you want to try to generate the lock file without accessing the network, remove th d flag and use --offline instead. => ERROR: wired-notify-0.10.4_1: do_build: '${make_cmd} build --release --locked --ta ST_TARGET} ${configure_args}' exited with 101 => ERROR: in do_build() at common/build-style/cargo.sh:8 ``` ### Steps to reproduce ./xbps-src pkg wired-notify ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: wired-notify : Cargo.lock --locked 2024-02-17 10:04 [ISSUE] wired-notify : Cargo.lock --locked biopsin @ 2024-02-17 13:18 ` tranzystorekk 2024-02-17 13:18 ` tranzystorekk 2024-02-20 15:27 ` [ISSUE] [CLOSED] " cinerea0 2 siblings, 0 replies; 4+ messages in thread From: tranzystorekk @ 2024-02-17 13:18 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 309 bytes --] New comment by tranzystorekk on void-packages repository https://github.com/void-linux/void-packages/issues/48794#issuecomment-1950146705 Comment: this is a common oversight when publishing `cargo packages`, upstream should be notified that the version in `Cargo.toml` doesn't match the one in `Cargo.lock` ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: wired-notify : Cargo.lock --locked 2024-02-17 10:04 [ISSUE] wired-notify : Cargo.lock --locked biopsin 2024-02-17 13:18 ` tranzystorekk @ 2024-02-17 13:18 ` tranzystorekk 2024-02-20 15:27 ` [ISSUE] [CLOSED] " cinerea0 2 siblings, 0 replies; 4+ messages in thread From: tranzystorekk @ 2024-02-17 13:18 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 309 bytes --] New comment by tranzystorekk on void-packages repository https://github.com/void-linux/void-packages/issues/48794#issuecomment-1950146705 Comment: this is a common oversight when publishing `cargo` packages, upstream should be notified that the version in `Cargo.toml` doesn't match the one in `Cargo.lock` ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ISSUE] [CLOSED] wired-notify : Cargo.lock --locked 2024-02-17 10:04 [ISSUE] wired-notify : Cargo.lock --locked biopsin 2024-02-17 13:18 ` tranzystorekk 2024-02-17 13:18 ` tranzystorekk @ 2024-02-20 15:27 ` cinerea0 2 siblings, 0 replies; 4+ messages in thread From: cinerea0 @ 2024-02-20 15:27 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 1267 bytes --] Closed issue by biopsin on void-packages repository https://github.com/void-linux/void-packages/issues/48794 Description: ### Is this a new report? Yes ### System Info Linux voidx 5.10.209_1 #1 SMP UTC x86_64 GNU/Linux ### Package(s) Affected wired-notify : update to 0.10.4_1 ### Does a report exist for this bug with the project's home (upstream) and/or another distro? Upstream: no void: https://github.com/void-linux/void-packages/pull/43233 ### Expected behaviour Cargo.lock is updated I looked at other packages with same issue and while Cargo.lock is supplied in wired-notify I just ran `cargo generate-lockfile` for a successfull build unless there is a bether patch approach? ### Actual behaviour ``` => wired-notify-0.10.4_1: running do_build ... error: the lock file /builddir/wired-notify-0.10.4/Cargo.lock needs to be updated but was passed to prevent this If you want to try to generate the lock file without accessing the network, remove th d flag and use --offline instead. => ERROR: wired-notify-0.10.4_1: do_build: '${make_cmd} build --release --locked --ta ST_TARGET} ${configure_args}' exited with 101 => ERROR: in do_build() at common/build-style/cargo.sh:8 ``` ### Steps to reproduce ./xbps-src pkg wired-notify ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-02-20 15:27 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2024-02-17 10:04 [ISSUE] wired-notify : Cargo.lock --locked biopsin 2024-02-17 13:18 ` tranzystorekk 2024-02-17 13:18 ` tranzystorekk 2024-02-20 15:27 ` [ISSUE] [CLOSED] " cinerea0
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).