On 17/10/13 15:56, مصعب الزعبي wrote:
> LOL ^_^
>
> I have 7 review requests , 5 of them ready , but no sponsors !!!
>
On the other side, just complaining won't help anyone. Given, everybody
is more or less overloaded, it would help you in reviewing others
packages as well, even IF you're NOT in
On 10/19/2013 06:36 PM, Adam Williamson wrote:
On Sat, 2013-10-19 at 09:45 -0400, Gene Czarcinski wrote:
* https://bugzilla.redhat.com/show_bug.cgi?id=1017435 - "Anaconda uses
LVM when Standard Partition is selected in text mode" (anaconda) - this
bug has been verified fixed by the update
https
How about, if it's not an EPEL repo, you make a separate release package
for it? Just like the "epel-release" package, but pinted to your
repository, so it's a separate installation and not part of EPEL? Then it
would be moe like repoforge, jpackage, Percona, and Jenkins repos.
On Fri, Oct 18, 20
Hello,
there's a new DNF release available in F20 [1] and rawhide today. Bug
1021087 that causes users to see tracebacks on upgrade transactions with
obsoleting packages (typically experienced when one tries to upgrade to
f20 using the --releasever parameter) is fixed in 0.4.5. Please see the
Compose started at Sun Oct 20 09:15:02 UTC 2013
Broken deps for armhfp
--
[blueman]
blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3
blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp
[bwm-ng]
bwm-ng-0.6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think better solution is "everyone (sponsors, packagers, packager
candidates) must go one step further".
We all have important works to do outside of Fedora Project and one
cannot pretend "special attentions" from others quickly.
I myself thought th
Greetings.
Some of you may have noted that there was no rawhide compose pushed out
saturday or today.
The compose is failing and I think it's related to the createrepo
update that landed in rawhide on friday:
https://bugzilla.redhat.com/show_bug.cgi?id=1021162
Has the details.
More eyes on
Hi,
as a first advice: Please do not top post:
http://fedoraproject.org/wiki/Mailing_list_guidelines#If_You_Are_Replying_to_a_Message
On Thu, Oct 17, 2013 at 03:56:00PM +0200, مصعب الزعبي wrote:
> LOL ^_^
>
> I have 7 review requests , 5 of them ready , but no sponsors !!!
If you provided links
On Oct 20, 2013, at 4:38 AM, Gene Czarcinski wrote:
>
>
> Before 20.25.1, if you had an existing swap on a regular partition or a
> logical volume and you specified --noformat, that swap specification was
> added to fstab. With 20.25.1, this is no longer the case and you wind up
> with no s
Hi,
hi I'm working on the packet guayadeque, when creating the rpm package
on Fedora 20 you get the following error message:
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=853553
There is a problem during the fedora 19+ package building related to svn:
-- Found Subversion: /usr/bin/svn (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/20/2013 08:31 PM, Martin Gansser wrote:
> Hi,
>
> hi I'm working on the packet guayadeque, when creating the rpm
> package on Fedora 20 you get the following error message:
>
> bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=853553
>
> T
*snip*
>
>
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group
> lists, how to get sponsored. Just waiting might be a solution, but
> probably not the fastest one.
>
> Matthias
>
> --
>
I don't agree with this. The sponsorship process is as much an
introduction to the commu
Hi list,
I am not currently a sponsored maintainer but have submitted a few
review requests[1][2] as well as a proposed update to the acpi package[3].
The acpi package have not been updated in a while and I would like to
offer to help out in any way that I can.
In my first request[1] I have p
On Sun, 20 Oct 2013 22:12:15 +0200, Johan Swensson wrote:
> Hi list,
>
> I am not currently a sponsored maintainer but have submitted a few
> review requests[1][2] as well as a proposed update to the acpi package[3].
>
> The acpi package have not been updated in a while and I would like to
> o
Hi all,
last April the following bug report was opened:
https://bugzilla.redhat.com/show_bug.cgi?id=947457
As I stated on bugzilla, metadata-extractor was just needed by JOSM.
Updating metadata-extractor would break JOSM. Anyway I suggested to
patch JOSM to use a newer version of metadata-extr
Hi,
https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#Compiler_flags
mentions only %optflags to be required for packages but I noticed that
%configure sets LDFLAGS to a value different than %optflags:
rpm --eval %configure
[...]
LDFLAGS="${LDFLAGS:--Wl,-z,relro }"; expo
Il 20/10/2013 23:37, Andrea Musuruane ha scritto:
Hi all,
last April the following bug report was opened:
https://bugzilla.redhat.com/show_bug.cgi?id=947457
As I stated on bugzilla, metadata-extractor was just needed by JOSM.
Updating metadata-extractor would break JOSM. Anyway I suggested
Nico Kadel-Garcia wrote:
> How about, if it's not an EPEL repo, you make a separate release package
> for it? Just like the "epel-release" package, but pinted to your
> repository, so it's a separate installation and not part of EPEL? Then it
> would be moe like repoforge, jpackage, Percona, and Je
Till Maas wrote:
> https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#Compiler_flags
>
> mentions only %optflags to be required for packages but I noticed that
> %configure sets LDFLAGS to a value different than %optflags:
>
> rpm --eval %configure
> [...]
> LDFLAGS="${LD
Martin Gansser wrote:
> There is a problem during the fedora 19+ package building related to svn:
>
> -- Found Subversion: /usr/bin/svn (found version "1.8.3")
> CMake Error at /usr/share/cmake/Modules/FindSubversion.cmake:83 (message):
> Command "/usr/bin/svn info /builddir/build/BUILD/guayadeque
# Fedora Quality Assurance Meeting
# Date: 2013-10-21
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
It's meeting time again! There's Beta stuff to discuss, of course, some
follow ups from last week, an
21 matches
Mail list logo