Re: automate rpm signing?
by Earl
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hmm... I've had this in my .rpmmacros for quite some time now.
Although it does require user input unless you are brave enough not
to have a passphrase for you key Yikes!, it works fine with GPG for
me...
%_signature gpg
%_gpg_name <me(a)somedomain.org>
Earl
On Tue, 21 Nov 2006 22:21:57 -0500 Douglas Hubler
<dhubler(a)pingtel.com> wrote:
>rpm --addsign requires user input and is not gpg-aware
> http://lists.gnupg.org/pipermail/gnupg-users/2004-
>January/021302.html
>
>--
>Fedora-buildsys-list mailing list
>Fedora-buildsys-list(a)redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.5
wkYEARECAAYFAkVkOvYACgkQk7+e+4lPSm2ceACeLznsZqLVpDNrqgcfXXud051usg4A
nAqJh5K1bRUicjRjCrxA4GI7ib4P
=Zj78
-----END PGP SIGNATURE-----
17 years, 4 months
PATCH: plague-0.5.0: PackageJob.py: NameError _and_ YumBaseError (unable to kill its job)
by Joe Todaro
---- PROBLEM # 1 ---- Depsolve step keeps crashing due to a typo in the
script:
364 (fuse-sshfs): Starting depsolve for arches: ['x86_64', 'i386'].
Exception in thread PackageJob: 364/fuse-sshfs:
[...snip...]
> File "/usr/share/plague/server/PackageJob.py", line 513, in
> _arch_deps_solved
> base.log = logger.Logger(threshold=threshold,
file_object=sys.stdout)
> NameError: global name 'logger' is not defined
---- PROBLEM # 2 ---- Unable to kill any job that fails due to a missing
package/s in the yum repos:
> File "/usr/share/plague/server/PackageJob.py", line 548, in
_arch_deps_solved
> pkg = base.returnPackageByDep(dep)
> File "__init__.py", line 1342, in returnPackageByDep
> YumBaseError: No Package found for fuse-devel
---- PATCH ----
Here's the patch that resolved the above 2 problems for us:
----- REQUEST ----
Can someone please review it... especially the fix to PROBLEM # 2, that
could potentially be masking a bigger problem..
Here's the code for your convenience (...these are the updates we made to
the _latest_ version of PackageJob.py):
$ cd /usr/share/plague/server
$ diff PackageJob.py PackageJob.py.working
513c513
< base.log = logger.Logger(threshold=threshold,
file_object=sys.stdout)
---
> base.log = Logger(threshold=threshold,
file_object=sys.stdout)
698c698
< if self._curstage == 'waiting':
---
> if self._curstage in ['waiting', 'depsolve']:
Thanks,
Joe
17 years, 4 months
OpenSUSE Build Service?
by Jeroen Janssen
Hi,
I'm not sure if this is the correct Fedora mailinglist, but has anyone
had a look at the OpenSuSe Build Service pages (
http://en.opensuse.org/Build_Service )?
There are two presentations (from FOSDEM) about it and it seems they
have also done some experimenting with building non SuSe distributions
with this build system (like Fedora Core 4).
Is this something that also could benefit the Fedora Project?
Best regards,
Jeroen Janssen
17 years, 4 months
Problem with file: URLs
by Orion Poplawski
I'm trying with the following yum.conf.x86_64:
[main]
cachedir=/tmp/fist
#keepcache=0
#debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
tolerant=1
exactarch=1
obsoletes=1
gpgcheck=1
reposdir=./
#plugins=1
metadata_expire=1800
#exclude=\*.i?86
# repos
[core]
name=core
baseurl=file:///data/sw1/fedora/core/6/x86_64/os/
enabled=1
[updates-released]
name=updates
baseurl=file:///data/sw1/fedora/core/updates/6/x86_64/
enabled=1
[extras]
name=extras
baseurl=file:///data/sw1/fedora/extras/6/x86_64/
enabled=1
[local]
name=local
baseurl=file:///data/sw1/fedora/CoRPMS/6/x86_64/
enabled=1
pungi runs through the dependencies then chokes on the first download:
Downloading pango-1.14.6-2.fc6.i386.rpm
Traceback (most recent call last):
File "/usr/bin/pungi", line 100, in ?
main()
File "/usr/bin/pungi", line 42, in main
mygather.downloadPackages()
File "/usr/lib/python2.4/site-packages/pypungi/gather.py", line 132,
in downloadPackages
os.link(local, os.path.join(pkgdir, os.path.basename(remote)))
OSError: [Errno 2] No such file or directory
but it is there:
# ls -l /data/sw1/fedora/core/updates/6/x86_64/pango-1.14.6-2.fc6.i386.rpm
-rw-r--r-- 1 537 537 336675 Oct 30 11:53
/data/sw1/fedora/core/updates/6/x86_64/pango-1.14.6-2.fc6.i386.rpm
(Pdb) print local
pungi/cache/pango-1.14.6-2.fc6.i386.rpm
(Pdb) print pkgdir
./6/x86_64/os/Fedora
(Pdb) print os.path.basename(remote)
pango-1.14.6-2.fc6.i386.rpm
Looks like repo.getPackage(pkg) doesn't actually do anything if it is a
file: url:
repo.getPackage(pkg)
os.link(local, os.path.join(pkgdir, os.path.basename(remote)))
so there is nothing to link when we get to os.link. Looks like for
file: urls we'll need to find the path to the package in the repo and
link (or copy, if needed) that
--
Orion Poplawski
System Administrator 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
17 years, 4 months
pungi bug with cache on 2nd run?
by Jeroen Janssen
Hi,
In pypungi/gather.py line 123 there is an os.link call that results in
a OSError [errno 17] file already exists.
This happens when running pungi for the second time (without cleaning
up the cache directory. My guess is this is a slight 'copy-paste' bug,
but I'm not sure. Can you please confirm this?
Best regards,
Jeroen Janssen
17 years, 4 months
pungi & minimal installation iso?
by Jeroen Janssen
Hi,
I was wondering what exactly is needed in the comps.xml to create a
minimal (fedora core 6) installation CD (the list of packages that are
a absolute minimum to have)
If I make an 'empty' list, pungi fails because the list is empty :)
If if leave out anaconda-runtime, the building of the iso fails.
Apparently anaconda-runtime pulls a lot of stuff into the iso (xorg
for example).
If I wanted to create an installation CD (with kickstart) that
shouldn't have xorg "during" install, is this possible with the
default anaconda packages? Or does this require customization (if at
all possible?) Should I ask these questions on another mailinglist?
Best regards,
Jeroen Janssen
17 years, 4 months
pungi & checking dependencies?
by Jeroen Janssen
Hello,
I'm trying to run the latest pungi on a fresh Fedora Core 6 installation.
>From the README it states how to test it, so I ran (as root) the
following command:
pungi --comps /etc/pungi/comps.xml \
--yumconf /etc/pungi/yum.conf.i386 --destdir /srv/pungi \
--cachedir /srv/pungi/cache --arch i386 --release 6.89 \
--discs 1
(note I'm going for an i386 installation, this is different from the README).
Now I'm looking at a large list of "Checking deps of" logging,
pungi has been using 14m CPU, 117Mb Virt Memory and no sign of 'real' progress.
A small snippet of the output:
Checking deps of libgcc.i386
Checking deps of python.i386
Checking deps of glibc.i386
Checking deps of glib2.i386
Checking deps of glibc.i686
Checking deps of glibc.i686
Checking deps of glibc.i686
Checking deps of glibc.i386
Checking deps of glibc.i686
Checking deps of glibc.i686
Checking deps of glibc.i686
Checking deps of glibc.i386
Checking deps of glibc.i386
Checking deps of glibc.i686
Checking deps of bash.i386
Checking deps of glibc.i386
Checking deps of beecrypt.i386
Checking deps of glibc.i386
Checking deps of glibc.i686
Checking deps of glibc.i386
Checking deps of basesystem.noarch
Checking deps of bzip2-libs.i386
Checking deps of glibc.i686
* Any idea if this is expected to behave as I am currently seeing?
* How long should it take on a P4 3GHz with 512Mb RAM?
* Is it normal that glibc tends to be 'checked' a lot?
Best regards,
Jeroen Janssen
17 years, 4 months
pungi + existing rpm base
by Earl
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jesse,
Thanks for creating pungi!
Any ideas on how to utilize pungi with an exisintg rpm base? i.e.
I already have a hacked up remastering process and an existing dir
full of standard Fedora CORE plus some custom RPMs and I would
like to try pungi out on it?
Maybe create a comps.xml based on the dir full of RPMs then create
a local yum repo with all of the RPMs? If thats it, how do you
create comps.xml from a dir full of RPMs?
Other suggestions?
Earl
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.5
wkYEARECAAYFAkVaR8IACgkQk7+e+4lPSm2BBgCgl7445VAa5pT7fUU7EZL96xMtpzcA
n2MzP+YMy6Yc6HnSCX6NYce7ZMNb
=p1Lu
-----END PGP SIGNATURE-----
17 years, 4 months
Announcing pungi-0.1.0
by Jesse Keating
I am pleased (and scared) to announce the 0.1.0 release of pungi. This is the
first release and thus it is a bit rough around the edges, but I firmly
believe in release early release often.
With this release pungi has the ability to gather packages and their deps from
a given repo or set of repos, run anaconda tools to make installable trees,
and create CD and DVD isos (DVD only if you ask for more than one CD). I
have included some reference config files and a comps file I have been using
to develop with. Currently pungi needs to be ran on the architecture you are
composing for, although one could use mock with setarch as well. See README
for more details on design and usage of pungi.
To download pungi, visit http://linux.duke.edu/projects/pungi/release/ and
pick up either the tarball, the source rpm, or the Fedora Core 6 binary rpm.
Mercurial repo is http://linux.duke.edu/projects/pungi Discussion regarding
the use or development of pungi happens on the fedora-buildsys-list mailing
list: http://www.redhat.com/mailman/listinfo/fedora-buildsys-list Currently
bugs are not tracked anywhere other than my inbox, I will most likely rectify
this situation soon, but for now email works.
Enjoy!
--
Jesse Keating
Release Engineer: Fedora
17 years, 4 months
Mock - Anyway to override Obsoletes tag?
by Andrew Rechenberg
Good morning,
I'm trying to use mock to build some Asterisk RPMs and mock is evidently
using an Obsoletes tag in opal(-devel) to override a BuildRequires I
have in my spec for openh323(-devel).
I've built openh323(-devel) for FC6 and I've created a local repo and
placed that local repo in the mock config for fedora-6-i386-core.cfg.
The mock yum finds my openh323 RPMs (I can see if find it in the
root.log) but I guess since opal contains an Obsoletes: openh323 tag
mock is installing opal instead of my openh323 RPM. Obviously my build
fails because it can't find the openh323 files it needs to properly
build.
Is there anyway to override the Obsoletes tag? Do I need to rebuild my
openh323 RPM with another tag inside it's SPEC file?
Please CC: me on any responses as I'm subscribed.
Thanks,
Andy.
Confidentiality Notice: This e-mail message including attachments, if any, is intended
only for the person or entity to which it is addressed and may contain confidential
and/or privileged material. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by reply
e-mail and destroy all copies of the original message. If you are the intended recipient,
but do not wish to receive communications through this medium, please so advise the
sender immediately.
17 years, 5 months