question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

packit srpm ignores actions

See original GitHub issue

I’m currently testing packit for cockpit-podman, to move away from the cockpituous rpm/Fedora scripts. I did a first naïve branch which just adds a packit.yaml.

I tried to build an srpm:

$ git clone -b packit https://github.com/martinpitt/cockpit-podman
$ cd cockpit-podman
$ packit srpm
ERROR    
Unexpected exception occurred,
please fill an issue here:
https://github.com/packit-service/packit/issues

This is due to cockpit-podman.spec not existing. The error message is unhelpful, but that’s issue #290. The point here is that packit.yaml has an action to build the spec:

actions:
  prepare-files: make cockpit-podman.spec
  create-archive: make dist-gzip

but this doesn’t seem to get run – there is no cockpit-podman.spec in the tree after the failing command. I also tried pre-sync:, that doesn’t work either.

After manually running make cockpit-podman.spec, packit srpm stops crashing and builds an srpm, but it generates a default tarball, instead of using make dist-gzip.

So it seems the srpm command generally ignores actions?

packit-0.2.0-1.fc31.noarch

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
martinpittcommented, May 2, 2019

Let’s discuss the changelog bits in issue #298, to keep it in one place.

Possibly it could be done with a hook, but I think implementing a sane default behaviour in packit would be better than replicating the same hook across most/all packit.yaml files out there.

0reactions
lachmanfrantisekcommented, May 2, 2019

But that’s the wrong place – it needs to happen in packit propose-update

The post-upstream-clone is used in the propose-update as well.

If I got you correctly:

  • For propose-update, you cannot update an upstream version and copy the content to the distgit.
  • For srpm, the upstream specfile is ok.

Would it help to add a new hook to propose-update after the sync and before the distgit commit? (Run from the distgit directory.)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Configuration - Packit
Deployed Packit (on GitHub or GitLab) ignores this setting, because Packit ... dependencies that are needed for your actions to be run when...
Read more >
Actions · teemtee/tmt · GitHub
Annotate commands, command line elements and shell scripts pre-commit #3693: Pull request #1730 synchronize by happz.
Read more >
Debugging Python Code · Blog - Tomáš Tomeček
I'd just put breakpoint() statement in the code where I want to prompt for the debugger. And then just run the code: $...
Read more >
draft-gandhi-spring-stamp-srpm-06 - Performance Measurement ...
As the reply test packet is not generated by the STAMP Session-Reflector, the STAMP Session-Sender ignores the 'Session-Sender Sequence Number', ...
Read more >
Configuring and managing networking Red Hat Enterprise ...
Configuring NetworkManager to ignore certain devices" Collapse section "15. ... Packet filtering software, such as the firewalld service, the nftables ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found