mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1067] copr repo for firetools #725
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#725
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@xahare commented on GitHub (Jan 24, 2017):
till then, heres an atom feed https://github.com/netblue30/firejail/releases.atom
@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.
@indolering commented on GitHub (Jan 24, 2017):
😢
You publish RPMs through SourceForge, is there no way to maintain a stable repo? What about using OSE?
@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.
@indolering commented on GitHub (Jan 27, 2017):
@netblue30 Awesome, thank you!
@indolering commented on GitHub (Feb 13, 2017):
Did something change?
@netblue30 commented on GitHub (Feb 13, 2017):
Almost ready for a new release!