[GH-ISSUE #1067] copr repo for firetools #725

Closed
opened 2026-05-05 06:31:50 -06:00 by gitea-mirror · 7 comments
Owner

Originally created by @indolering on GitHub (Jan 23, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1067

I would like to run Firetools, but you don't have a copr repo and I don't want them to get out-of-sync.

Originally created by @indolering on GitHub (Jan 23, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1067 I would like to run Firetools, but you don't have a copr repo and I don't want them to get out-of-sync.
gitea-mirror 2026-05-05 06:31:50 -06:00
Author
Owner

@xahare commented on GitHub (Jan 24, 2017):

till then, heres an atom feed https://github.com/netblue30/firejail/releases.atom

<!-- gh-comment-id:274750121 --> @xahare commented on GitHub (Jan 24, 2017): till then, heres an atom feed https://github.com/netblue30/firejail/releases.atom
Author
Owner

@netblue30 commented on GitHub (Jan 24, 2017):

Coper repos are maintained outside the project. I'll have a new firetools release in the next two weeks, or maybe just a test release, and there will be a rpm package available. In this moment firetools git repo is a war zone, so probably is a good idea to stick with the old release.

<!-- gh-comment-id:274802215 --> @netblue30 commented on GitHub (Jan 24, 2017): Coper repos are maintained outside the project. I'll have a new firetools release in the next two weeks, or maybe just a test release, and there will be a rpm package available. In this moment firetools git repo is a war zone, so probably is a good idea to stick with the old release.
Author
Owner

@indolering commented on GitHub (Jan 24, 2017):

Coper repos are maintained outside the project.

😢

You publish RPMs through SourceForge, is there no way to maintain a stable repo? What about using OSE?

<!-- gh-comment-id:274960202 --> @indolering commented on GitHub (Jan 24, 2017): > Coper repos are maintained outside the project. 😢 You publish RPMs through SourceForge, is there no way to maintain a stable repo? What about using [OSE](https://build.opensuse.org/)?
Author
Owner

@netblue30 commented on GitHub (Jan 25, 2017):

After the next release the repo will be stable enough to be followed live - there are big changes going in at the moment.

<!-- gh-comment-id:275115181 --> @netblue30 commented on GitHub (Jan 25, 2017): After the next release the repo will be stable enough to be followed live - there are big changes going in at the moment.
Author
Owner

@indolering commented on GitHub (Jan 27, 2017):

@netblue30 Awesome, thank you!

<!-- gh-comment-id:275790587 --> @indolering commented on GitHub (Jan 27, 2017): @netblue30 Awesome, thank you!
Author
Owner

@indolering commented on GitHub (Feb 13, 2017):

Did something change?

<!-- gh-comment-id:279271138 --> @indolering commented on GitHub (Feb 13, 2017): Did something change?
Author
Owner

@netblue30 commented on GitHub (Feb 13, 2017):

Almost ready for a new release!

<!-- gh-comment-id:279542926 --> @netblue30 commented on GitHub (Feb 13, 2017): Almost ready for a new release!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#725
No description provided.