On Mon, Jan 10, 2011 at 11:47 PM, susmit shannigrahi <
thinklinux@gmail.com>
>
>
> Nice, thanks.
> Given the size of the wiki, I am surprised that there is no
> documentation in this regard.
> I have started one: https://fedoraproject.org/wiki/Packaging/FAQ
I don't think spreading out the inf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having a problem under mock 1.1.6 on F13/x86_64 where I can't seem to
download the repo information for F14/x86_64 (all other releases/arches work
fine).
The root.log is here:
http://pastebin.com/irkWhjtg
For some reason it seems like yum can't d
On Mon, Jan 10, 2011 at 06:54:56PM -0500, Matthias Clasen wrote:
> On Mon, 2011-01-10 at 14:13 -0600, Jason L Tibbitts III wrote:
> > > "MC" == Matthias Clasen writes:
> >
> > MC> * gtk-update-icon-cache-3.0 and gtk-builder-convert-3.0 have been
> > MC> dropped (since they were identical to t
I just pushed a new release of bodhi into production.
http://bodhi.fedoraproject.org
It's a minor release that contains a small number of fixes, including:
Backend bug fixes
- Don't try and remove the -pending koji tags when resuming a push
- Don't fetch security bug deta
On Mon, 2011-01-10 at 14:13 -0600, Jason L Tibbitts III wrote:
> > "MC" == Matthias Clasen writes:
>
> MC> * gtk-update-icon-cache-3.0 and gtk-builder-convert-3.0 have been
> MC> dropped (since they were identical to their un-suffixed cousins in
> MC> the gtk2 package). If you are using gtk-u
Hello Peter,
I have one gnome-guitar (gtk mono based) at
https://bugzilla.redhat.com/show_bug.cgi?id=663018
I will take erlang-ebloom and erlang-skerl .
Thanks
On Tue, Jan 11, 2011 at 12:00 AM, Peter Lemenkov wrote:
> Hello All!
>
> I would like to swap reviews. Here are mine ones (all of them
Remi Collet writes:
> I have just notice, in the spec
> -DWITH_READLINE=ON
> Which means, according to INSTALL-SOURCE :
> * -DWITH_READLINE=bool
>Whether to use the readline library bundled with the
>distribution.
> Does this use of a bundled library is wanted ?
Not
Summary of changes:
d3b4553... Import of perl-Net-STOMP-Client. (*)
d1f9491... Populate branches. (*)
d9bb370... New 0.9 upstream. (*)
d194bf6... - Mass rebuild with perl-5.12.0 (*)
a3e18c1... New upstream 0.9.2. (*)
6d5f507... dist-git conversion (*)
363b043... Rebuild. (*)
f2399a
On Mon, 2011-01-10 at 15:00 -0500, Matthias Clasen wrote:
> I have built most packages that had a gtk3 dependency already, and
> tagged them into rawhide. The following are the leftovers:
> libindicator-gtk3
I see you committed a bump+rebuild but didn't actually push a build,
AFAICT - I can't se
Jason L Tibbitts III wrote:
>> "MC" == Matthias Clasen writes:
>
> MC> * gtk-update-icon-cache-3.0 and gtk-builder-convert-3.0 have been
> MC> dropped (since they were identical to their un-suffixed cousins in
> MC> the gtk2 package). If you are using gtk-update-icon-cache in %post
> MC> of
> "MC" == Matthias Clasen writes:
MC> * gtk-update-icon-cache-3.0 and gtk-builder-convert-3.0 have been
MC> dropped (since they were identical to their un-suffixed cousins in
MC> the gtk2 package). If you are using gtk-update-icon-cache in %post
MC> of a gtk3-using package, you should add Req
I have just tagged gtk3-2.99.0 into rawhide. There are abi and api
changes, so all dependent packages will have to be rebuilt (the most
obvious change is that the libraries are now called libg[dt]k-3.0.so
instead of libg[gt]k-x11-3.0.so).
There are a number of api changes that I am not going to li
I have just notice, in the spec
-DWITH_READLINE=ON
Which means, according to INSTALL-SOURCE :
* -DWITH_READLINE=bool
Whether to use the readline library bundled with the
distribution.
Does this use of a bundled library is wanted ?
To use the system library, option sh
Hello All!
I would like to swap reviews. Here are mine ones (all of them are
Erlang-related):
* erlang-ebloom https://bugzilla.redhat.com/652616
* erlang-skerl https://bugzilla.redhat.com/652648
* erlang-luke https://bugzilla.redhat.com/652585
* erlang-webmachine https://bugzilla.redhat.com/65254
> I think, just in case it's not clear, that the typical way this should
> be handled is that on installation the software should not create the
> necessary database; instead the creation process should be documented
> for the user to complete manually. So when the software is packaged,
> there's n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2011 09:02 AM, Adam Williamson wrote:
> On Mon, 2011-01-10 at 08:02 -0500, Stephen Gallagher wrote:
>
>> As a caveat, this is a project that always requires at least some manual
>> intervention on upgrade, as individual sites need to have an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2011 08:37 AM, Mat Booth wrote:
> On 10 January 2011 13:02, Stephen Gallagher wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> As a caveat, this is a project that always requires at least some manual
>> intervention on upgrade
Hi,
with the recent evolution-data-server 2.91.5 release in Rawhide are done
some internal changes in the soname versions and a location where the
backend files for the addressbook and calendar should be saved.
>From the commit log:
On Mon, 2011-01-10 at 08:02 -0500, Stephen Gallagher wrote:
> As a caveat, this is a project that always requires at least some manual
> intervention on upgrade, as individual sites need to have an upgrade
> script run on them. So end-users are used to taking some action.
> Unfortunately, upstream
On 10 January 2011 13:02, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> As a caveat, this is a project that always requires at least some manual
> intervention on upgrade, as individual sites need to have an upgrade
> script run on them. So end-users are used to ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One of my packages (ReviewBoard) just released a point update that makes
a problematic change for installed instances.
Specifically, they identified an issue with ReviewBoard running on
mod_wsgi that requires that an option (WSGIPassAuthorization) be
On Sun, 2011-01-09 at 11:37 -0700, susmit shannigrahi wrote:
> > My understanding was that we never touch databases in RPMs, period. We
> > don't create, modify, update, or remove. I can't recall at the moment
> > where this stems from, but the rationale, as I recall, was that we can
> > never be
22 matches
Mail list logo
