Would HTTP Strict Transport Security be a good feature to implement on
some of the Fedora infrastructure, such as koji.fp.o, or admin.fp.o?
Incidentally I noticed that Koji-web will sometimes redirect to
plaintext URLs. A patch is at https://fedorahosted.org/koji/ticket/226
I upgraded a server that provides RPM packages from F14 to F15 about 2
months ago. Since the upgrade, createrepo is leaving behind old
prestodelta.xml.gz files. I do not see a new command line option to
remove these automatically. Is createrepo suppose to leave these files
$ rpm -q createrepo
This is my first time trying to compose F16. After the repo is
created, I get this
Traceback (most recent call last):
File "/usr/bin/pungi", line 222, in <module>
File "/usr/bin/pungi", line 120, in main
File "/usr/lib/python2.7/site-packages/pypungi/__init__.py", line 807, in doCreaterepo
self._makeMetadata(self.topdir, cachedir, compsfile, repoview=True, repoviewtitle=repoviewtitle)
File "/usr/lib/python2.7/site-packages/pypungi/__init__.py", line 783, in _makeMetadata
File "/usr/lib/python2.7/site-packages/pypungi/util.py", line 36, in _doRunCommand
raise OSError, "Got an error from %s: %s" % (command, err)
OSError: Got an error from /usr/bin/repoview: Traceback (most recent call last):
File "/usr/bin/repoview", line 932, in <module>
File "/usr/bin/repoview", line 929, in main
File "/usr/bin/repoview", line 162, in __init__
letters = self.setup_letter_groups()
File "/usr/bin/repoview", line 774, in setup_letter_groups
sqlite3.DatabaseError: file is encrypted or is not a database
Bill in Denver
I'm using mock 1.1.16 on fedora 15, and am hitting an error with the
'write_tar' related scm functionality. It looks like the creation of the
.tar.gz of the source is confusing tar, as it's being created within the
source dir. Example output:
DEBUG: Executing command: ['tar', 'czf',
DEBUG: tar: less/less-1.tar.gz: file changed as we read it
This is using tar 1.26 (from tar-1.26-2.fc15.x86_64.rpm).
Mock is being called like so:
mock -v -r mock
b0ed6/mock --no-clean --rebuild --scm-enable --scm-option method=git
--scm-option git_get="git clone
--scm-option spec="SCM_PKG.spec" --scm-option package=less --scm-option
I'm not sure if its relevant, but here's the top of my spec file:
Summary:test generated spec
I would expect the '--exclude' to have tar not care about any timestamps
on less-1.tar.gz, but it looks like it does.
some questions need you help, thanks!
1` you know the `koji call <name>` command, is there a list of what i can call?
2` how to drop a build to trash? can i submit a same build(same version and release) while the build is in trash?
3` is there a elegent way to submit a list of build, with a better order?
4` thanks all
When making a custom spin of Fedora for a specific set of machines
using pungi, I feel the need to be able to add extra files to the
ISO. In particular one or more kickstart files that can be used
during the installation. Preferably this feature should be generic,
adding some file/directory glob, IMHO.
When googling I do not seem to be the only one with this idea.
But, most of these mails are from 3+ years ago and I do not see an
option in pungi allowing me to do this (but I hope I'm wrong...).
So my question: is there a (maybe dirty) trick to do this.
Now I'm thinking of re-mkisofs'ing the ISO, running implant* etc.
again (did anyone make a script for this already?), but talking
about dirtyness, this is a pretty "expensive" way of doing it.
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204