IRC channel logs

2025-04-26.log

back to list of logs

<meati>Is there a way to update a package to an inter-release (git) version without making a really dirty commit? Addint a let block around the whole package def feels heavy-handed
<meati>also, should the revision for git-version start at 0 or 1?
<apteryx>is anyone using elogind-configuration in their home configuration? if so, especially if non-trivially, I'd like to hear from someone testing the v3 in bug#77806
<peanuts>"elogind behavior changed: power key turns computer off" https://issues.guix.gnu.org/77806
<apteryx>meati: not super important but I'd settle to use 1.
<apteryx>err, 0
<apteryx>:-)
<apteryx>meati: agreed that it's obtrusive to update to a commit snaphot; that's not a bad thing usually as we should preferably use tags or releases.
<apteryx>(diff wise)
<apteryx>jA_cOp: there's also --target-version, though I don't remember if the crate importer has support for it
<apteryx>if it does, then you can specify a partial version too using it
<apteryx>or maybe that's only accepted by 'guix refresh' so far.
<apteryx>sorry for the noise
<meaty>What is everyone else doing with their old local branches after updating/adding packages? Is there a way to tell git where they were merged into the guix repository?
<ardraidi>greetings
<ardraidi>can someone merge 73045? I got an LGTM on an earlier veriosn, so should be ready to merge.