I am pleased to announce that John Poelstra is our first appointment
to the Fedora Project Board for this cycle. His term will last until
the selection process following the release of Fedora 13, in
accordance with the Board's established succession planning.
Many of our contributors know John
李建 wrote:
Good,the method you give is simple.I'll test later.My repo table in sql now
is following,Did you can tell me what's mean about state=3 ? and state=1
,and state=2 ?
from koji/__init__.py:
REPO_STATES = Enum((
'INIT',
'READY',
'EXPIRED',
'DELETED',
'PROBLEM',
))
So
Hi,
in koji for Fedora/s390x I have 2 builds for wxGTK package
https://s390.koji.fedoraproject.org/koji/packageinfo?packageID=7367
wxGTK-2.8.9-4.fc11
wxGTK-2.8.10-1.fc11
the higher NVR build is older
but the lower NVR is used in the buildroot used to build a package (like
wxPython) that
Dan Horák wrote:
Hi,
in koji for Fedora/s390x I have 2 builds for wxGTK package
https://s390.koji.fedoraproject.org/koji/packageinfo?packageID=7367
wxGTK-2.8.9-4.fc11
wxGTK-2.8.10-1.fc11
the higher NVR build is older
but the lower NVR is used in the buildroot used to build a package (like
Conrad Meyer wrote:
On Wednesday 03 June 2009 10:23:05 pm Ralf Corsepius wrote:
Let me try an analogy: How do you handle defects/malfunctions with your
car?
Did a bunch of hobbyists from around the world build your car by communicating
over the internet?
Have you ever seen an open source
On 03.06.2009 21:28, Thorsten Leemhuis wrote:
As you might remember, we collected a list of questions that a few days
ago were sent to the Candidates of the next Fedora Board/FESCo
Elections(¹). I got most answers back in between (dgilmore should follow
soon; no response from ianweller yet,
On Wednesday 03 June 2009 11:40:42 pm Ralf Corsepius wrote:
Conrad Meyer wrote:
On Wednesday 03 June 2009 10:23:05 pm Ralf Corsepius wrote:
Let me try an analogy: How do you handle defects/malfunctions with your
car?
Did a bunch of hobbyists from around the world build your car by
Kevin Kofler wrote:
Steve Grubb wrote:
Not if its closed. How would I be notified that the fix is in Fedora? If
the bug is severe enough, shouldn't the upstream commit be applied to
Fedora's package and the package pushed out for testing? Is all this going
to happen if the bug is closed?
On Thu, Jun 04, 2009 at 07:23:05AM +0200, Ralf Corsepius wrote:
Steven M. Parrish wrote:
Many people have mentioned that it is not right to ask the users to
file their bug reports upstream. I ask why not?
Let me summarize what I already wrote elsewhere in this thread:
* Users aren't
Dne Thu, 4 Jun 2009 08:34:40 +0200
Valent Turkovic valent.turko...@gmail.com napsal(a):
I'm testing Rawhide with latest updates and KPackageKit fails to do
updates, I get this error log:
http://fpaste.org/paste/13851
It is works for you haven't tested it please do, if it works for you
then
Kevin Kofler wrote:
Ralf Corsepius wrote:
I consider maintainers redirecting arbitrary reporters to upstreams to
be rude and hostile, because they are presuming the reporter to be
* interested in tracking down bugs
If you don't care about your bug, why are you reporting it in the first
place?
Am Mittwoch, den 03.06.2009, 10:09 -0700 schrieb Johannes Erdfelt:
On Wed, Jun 03, 2009, Christoph Höger choe...@cs.tu-berlin.de wrote:
I see a small problem with evolution when sending to mailinglists.
Obviously evolution puts: Mime-version: 1.0 in the header, hypermail
searches for
On Jueves 04 Junio 2009 08:59:23 Ralf Corsepius escribió:
Kevin Kofler wrote:
Steve Grubb wrote:
Not if its closed. How would I be notified that the fix is in Fedora? If
the bug is severe enough, shouldn't the upstream commit be applied to
Fedora's package and the package pushed out for
Hello,
I don't want to start a long thread, but just to ask a couple questions for
my own clarification. Does a maintainer's responsibilities end with
packaging bugs? IOW, if there is a problem in the package that is _broken
code_ do they need to do something about it or is it acceptable for
Does trying to become a packager.
Involve being currently a Developer,
as in Programming skills\certification,
whether Perl\Python\c++ etc.
Frank
--
msn: frankly3d skype: frankly3d
Mailing-List Reply to: Mailing-List
Still Learning, Unicode where possible
--
fedora-devel-list mailing list
On Miércoles 03 Junio 2009 22:27:13 Kevin Kofler escribió:
Jaroslav Reznik wrote:
Most bugs are filled by quite technically skilled users. For average
users it doesn't depend if it is RH bugzilla or upstream's bugzilla -
it's too complicated for them. I know - it's another story... For
On 06/04/2009 01:13 PM, Frank Murphy (Frankly3d) wrote:
Does trying to become a packager.
Involve being currently a Developer,
as in Programming skills\certification,
whether Perl\Python\c++ etc.
Not necessarily. It's useful to understand the codebase but if you have
a active upstream
On Miércoles 03 Junio 2009 23:35:07 Adam Williamson escribió:
On Wed, 2009-06-03 at 22:57 +0200, Kevin Kofler wrote:
Steve Grubb wrote:
And then should the bug be closed hoping that one day you pull in a
package that solves the user's problem?
If the bug is fixed upstream, the Fedora
Am Donnerstag, den 04.06.2009, 09:30 +0200 schrieb Christoph Höger:
Am Mittwoch, den 03.06.2009, 10:09 -0700 schrieb Johannes Erdfelt:
On Wed, Jun 03, 2009, Christoph Höger choe...@cs.tu-berlin.de wrote:
I see a small problem with evolution when sending to mailinglists.
Obviously
1. How did you find out about Fedora Test Days?
fedora-devel-list
2. Was sufficient documentation available to help you participate in a
Fedora Test Day? If not, what did you find missing or in need of
improvement?
mostly, see examples:
good:
Test Day:2009-03-26 Nouveau
/sbin/lspci -d
2009/6/4 Michal Schmidt mschm...@redhat.com:
Dne Thu, 4 Jun 2009 08:34:40 +0200
Valent Turkovic valent.turko...@gmail.com napsal(a):
I'm testing Rawhide with latest updates and KPackageKit fails to do
updates, I get this error log:
http://fpaste.org/paste/13851
It is works for you haven't
My own opinion is that the package maintainer is responsible for
reporting bugs upstream when they are able to reproduce them.
One reason for my belief is that I've seen the situation from the other
side: as an upstream maintainer for a package, getting bug reports
directly from users of a
Jaroslav Reznik, Wed, 03 Jun 2009 13:01:01 +0200:
Most bugs are filled by quite technically skilled users.
It doesn't seem so from my point of view. Depends on the importance of
the bug (when Xorg doesn't start at all, they find a way to bugzilla).
Moreover, we want to move from fora to
Ralf Corsepius, Wed, 03 Jun 2009 14:01:46 +0200:
We are not forcing anyone to do anything but we think direct
communication between user and developer is much more better
I consider maintainers redirecting arbitrary reporters to upstreams to
be rude and hostile, because they are presuming
Matej Cepl wrote:
but I think if somebody
skilled in programming Perl (hint, hint) would work on https://
bugzilla.redhat.com/show_bug.cgi?id=189813 (and its upstream
counterparts), situation of our reporters COULD improve.
Matěj
Is it time then to setup
On Wed June 3 2009, Kevin Kofler wrote:
And I don't think we can make bug reports any easier, the point is that the
information is required, those complicated forms are there to request the
information we need.
I disagree:
On https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora there are
Adam Williamson, Wed, 03 Jun 2009 14:35:07 -0700:
There's an obvious answer to this question: we track the importance of
issues to Fedora via the Fedora bug tracker, not via upstream bug
trackers. There's no way I can mark a bug in the KDE bug tracker as
blocking the release of Fedora 12.
For
Hi,
I submitted ampache (http://ampache.org/) for review, but I was told that it
could not use any external software
bundled in the code. In fact, it uses getid3, a file that seems to come from
horde (horde/Browser.php),
and some others.
According to the weekpedia
On Wed, 3 Jun 2009 18:31:27 -0300, Paulo wrote:
Hi.
As I don't have the time to maintain audacious any more I'm orphaning the
following packages:
audacious
audacious-plugins
libmowgli
mcs
The last two are dependencies which, as far as I am aware, are used by
nothing else.
On 06/04/2009 03:53 PM, Paulo Cavalcanti wrote:
Hi,
I submitted ampache (http://ampache.org/) for review, but I was told
that it could not use any external software
bundled in the code. In fact, it uses getid3, a file that seems to come
from horde (horde/Browser.php),
and some others.
2009/6/4 Mary Ellen Foster mefos...@gmail.com:
2009/6/4 Michal Schmidt mschm...@redhat.com:
http://fpaste.org/paste/13851
Looks like https://bugzilla.redhat.com/show_bug.cgi?id=502399
Actually, it's probably https://bugzilla.redhat.com/show_bug.cgi?id=503989 ...
Sorry, should have read the
On Thu, Jun 4, 2009 at 6:23 AM, Paulo Cavalcanti pro...@gmail.com wrote:
Hi,
I submitted ampache (http://ampache.org/) for review, but I was told that it
could not use any external software
bundled in the code. In fact, it uses getid3, a file that seems to come from
horde
On Thu, 4 Jun 2009, Till Maas wrote:
I tried to add such a table[0], but I failed to enable the horizotnal
scrollbar. I even enabled javascript for the wiki, but it still does not
work.
Is this somehow broken in our mediawiki CSS setup? I noticed the css files
contain overflow:hidden in
On Thu, Jun 4, 2009 at 7:33 AM, Paulo Cavalcanti pro...@gmail.com wrote:
On Thu, Jun 4, 2009 at 8:00 AM, David Nalley da...@gnsa.us wrote:
On Thu, Jun 4, 2009 at 6:23 AM, Paulo Cavalcanti pro...@gmail.com wrote:
Hi,
I submitted ampache (http://ampache.org/) for review, but I was told
Rahul Sundaram wrote:
On 06/04/2009 01:13 PM, Frank Murphy (Frankly3d) wrote:
Does trying to become a packager.
Involve being currently a Developer,
as in Programming skills\certification,
whether Perl\Python\c++ etc.
Not necessarily. It's useful to understand the codebase but if you have
a
On Wed June 3 2009, James Laska wrote:
1. How did you find out about Fedora Test Days?
devel mailing list
2. Was sufficient documentation available to help you participate in a
Fedora Test Day? If not, what did you find missing or in need of
improvement?
Yes.
3. Did you encounter any
Le Jeu 4 juin 2009 12:04, Till Maas a écrit :
In conclusion, more than 66% of the form elements can be removed for
the unexperienced bug reporter.
Last time I reported this problem in the bugzilla component of redhat
bugzilla (I complained about all the columns in list view no one uses
when
On 06/04/2009 05:48 PM, Nicolas Mailhot wrote:
Last time I reported this problem in the bugzilla component of redhat
bugzilla (I complained about all the columns in list view no one uses
when last change is not even displayed) the answer was that the
people in charge did not want to deviate
David Nalley wrote:
On Thu, Jun 4, 2009 at 7:33 AM, Paulo Cavalcanti pro...@gmail.com wrote:
On Thu, Jun 4, 2009 at 8:00 AM, David Nalley da...@gnsa.us wrote:
On Thu, Jun 4, 2009 at 6:23 AM, Paulo Cavalcanti pro...@gmail.com wrote:
Hi,
I submitted ampache (http://ampache.org/)
* Till Maas [04/06/2009 13:41] :
In conclusion, more than 66% of the form elements can be removed for the
unexperienced bug reporter. Also the component selection process could be
made
You are seeing some of these elements because you are in the 'editbugs'
group. Unexperienced bug
Hi all,
my client-side certificate is expired. I tried to generate a new
one on the Fedora Account System, but I get an error saying Your
certificate could not be generated.. Not very helpful as an error
message. I do not know what should I do. Can someone help?
Thanks,
Andrea.
--
Ralf Corsepius wrote:
You are still presuming your users to be interested in developing and
working on your package.
This simply does not apply - They want to use your package.
I see 2 possibilities:
* either the user wants his/her bug fixed, in that case he/she is
responsible for reporting
Tim Waugh wrote:
It can be a frustrating experience because the person reporting the bug
can never be quite sure which version they are using (due to additional
patches used in packaging), and generally are not able to try out
suggested patches or pull from a source code repository.
We can
On Thu, Jun 4, 2009 at 9:28 AM, Jon Ciesla l...@jcomserv.net wrote:
David Nalley wrote:
On Thu, Jun 4, 2009 at 7:33 AM, Paulo Cavalcanti pro...@gmail.com
wrote:
On Thu, Jun 4, 2009 at 8:00 AM, David Nalley da...@gnsa.us wrote:
On Thu, Jun 4, 2009 at 6:23 AM, Paulo Cavalcanti
Paulo Cavalcanti wrote:
On Thu, Jun 4, 2009 at 9:28 AM, Jon Ciesla l...@jcomserv.net
mailto:l...@jcomserv.net wrote:
David Nalley wrote:
On Thu, Jun 4, 2009 at 7:33 AM, Paulo Cavalcanti
pro...@gmail.com mailto:pro...@gmail.com wrote:
On Thu, Jun
On 06/04/2009 06:57 PM, Paulo Cavalcanti wrote:
Thank you Jon. I will start with getid3.
It would be nice if we had a list of packages missing available elsewhere,
so people, interested in helping, could choose what to pack.
http://fedoraproject.org/wiki/Package_maintainers_wishlist
You are still presuming your users to be interested in developing and
working on your package.
This simply does not apply - They want to use your package.
I see 2 possibilities:
* either the user wants his/her bug fixed, in that case he/she is
responsible for reporting it to the
On Thu, Jun 4, 2009 at 9:48 AM, Michael Schwendt mschwe...@gmail.comwrote:
On Wed, 3 Jun 2009 18:46:27 +0200, Ralf wrote:
Hi.
As I don't have the time to maintain audacious any more I'm orphaning the
following packages:
audacious
audacious-plugins
libmowgli
mcs
The last
On Thu, Jun 4, 2009 at 10:29 AM, Jon Ciesla l...@jcomserv.net wrote:
Paulo Cavalcanti wrote:
On Thu, Jun 4, 2009 at 9:28 AM, Jon Ciesla l...@jcomserv.net wrote:
David Nalley wrote:
On Thu, Jun 4, 2009 at 7:33 AM, Paulo Cavalcanti pro...@gmail.com
wrote:
On Thu, Jun 4, 2009 at 8:00
Ralf Corsepius wrote:
Me thinks, your are just being lazy and are trying to rudely push around
Fedora's user base. customer-friendliness is something entirely
different from your attitude.
Fedora's customers aren't paying us anything, so they can't expect to get
the equivalent of paid
On 06/03/2009 07:48 PM, Chuck Anderson wrote:
Not necessarily. I don't see why the Fedora Project couldn't qualify
as a Sponsored Participant on Internet2 [1]. In fact, Red Hat is
already connected in Raleigh.
I think this is because they're technically on NC State University.
~spot
--
Matej Cepl wrote:
I am quite surprised to totally agree with you this time ;-), and I am
even more surprised to finally a situation where actually technology
could help to resolve interpersonal problems, but I think if somebody
skilled in programming Perl (hint, hint) would work on https://
Adam Williamson wrote:
There's an obvious answer to this question: we track the importance of
issues to Fedora via the Fedora bug tracker, not via upstream bug
trackers. There's no way I can mark a bug in the KDE bug tracker as
blocking the release of Fedora 12.
If the bug is important enough
On Thu, Jun 4, 2009 at 3:51 PM, Till Maas opensou...@till.name wrote:
On Thu June 4 2009, Andrea Musuruane wrote:
my client-side certificate is expired. I tried to generate a new
one on the Fedora Account System, but I get an error saying Your
certificate could not be generated.. Not very
On 06/02/09 07:10, H. Peter Anvin wrote:
Bernie Innocenti wrote:
On 06/02/09 03:43, H. Peter Anvin wrote:
Bernie Innocenti wrote:
Disk /dev/sdb: 2055 MB, 2055208960 bytes
221 heads, 2 sectors/track, 9081 cylinders
I don't know where fdisk, the Linux kernel, or whatever come up with
these
Michal Hlavinka wrote:
What if upstream answers: ok, thanks for bug report, please try this
patch... or I've fixed it in repo, please try svn snapshot, if it's fixed
for you?
In that case we can roll a fixed package (e.g. as a scratch build). (If
upstream says try a current snapshot, it
Kevin Kofler wrote:
Ralf Corsepius wrote:
Me thinks, your are just being lazy and are trying to rudely push around
Fedora's user base. customer-friendliness is something entirely
different from your attitude.
Fedora's customers aren't paying us anything,
That's the way it was\is setup.
H. Peter Anvin wrote:
Bernie Innocenti wrote:
On 06/02/09 03:43, H. Peter Anvin wrote:
Bernie Innocenti wrote:
Disk /dev/sdb: 2055 MB, 2055208960 bytes
221 heads, 2 sectors/track, 9081 cylinders
I don't know where fdisk, the Linux kernel, or whatever come up with
these kinds of geometries.
Frank Murphy (Frankly3d) wrote:
Does trying to become a packager.
Involve being currently a Developer,
as in Programming skills\certification,
whether Perl\Python\c++ etc.
And to answer that part, you don't need any sort of certification to become
a Fedora packager, you just need to write one
Compose started at Thu Jun 4 06:15:04 UTC 2009
Summary:
Added Packages: 0
Removed Packages: 0
Modified Packages: 0
Broken deps for ppc64
--
cabal2spec-0.12-1.fc11.noarch requires ghc 0:6.10.1-7
--
fedora-devel-list
On Thu, 2009-06-04 at 08:54 +0200, Ralf Corsepius wrote:
Conrad Meyer wrote:
On Wednesday 03 June 2009 11:40:42 pm Ralf Corsepius wrote:
Conrad Meyer wrote:
On Wednesday 03 June 2009 10:23:05 pm Ralf Corsepius wrote:
Let me try an analogy: How do you handle defects/malfunctions with your
On Thu, 4 Jun 2009, Tom \spot\ Callaway wrote:
On 06/03/2009 07:48 PM, Chuck Anderson wrote:
Not necessarily. I don't see why the Fedora Project couldn't qualify
as a Sponsored Participant on Internet2 [1]. In fact, Red Hat is
already connected in Raleigh.
I think this is because they're
What if upstream answers: ok, thanks for bug report, please try this
patch... or I've fixed it in repo, please try svn snapshot, if it's
fixed for you?
In that case we can roll a fixed package (e.g. as a scratch build). (If
upstream says try a current snapshot, it should be fixed, I'll
On Thu, Jun 04, 2009 at 10:56:34AM -0400, Seth Vidal wrote:
On Thu, 4 Jun 2009, Tom \spot\ Callaway wrote:
On 06/03/2009 07:48 PM, Chuck Anderson wrote:
Not necessarily. I don't see why the Fedora Project couldn't qualify
as a Sponsored Participant on Internet2 [1]. In fact, Red Hat is
Michal Hlavinka wrote:
Yes, but how will you notice reporter needs (your) help if bug is closed
upstream?
By CCing ourselves on the upstream bug when we close ours.
Kevin Kofler
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
2009/6/4 Kevin Kofler kevin.kof...@chello.at:
Michal Hlavinka wrote:
Yes, but how will you notice reporter needs (your) help if bug is closed
upstream?
By CCing ourselves on the upstream bug when we close ours.
Kevin Kofler
Speaking as a semi-frequent reporter of Fedora KDE bugs, I
Mary Ellen Foster wrote:
2009/6/4 Kevin Kofler kevin.kof...@chello.at:
Michal Hlavinka wrote:
Yes, but how will you notice reporter needs (your) help if bug is closed
upstream?
By CCing ourselves on the upstream bug when we close ours.
Kevin Kofler
Speaking as a semi-frequent
On Wed, Jun 3, 2009 at 11:43 PM, Frank Murphy (Frankly3d)
frankl...@gmail.com wrote:
Does trying to become a packager.
Involve being currently a Developer,
as in Programming skills\certification,
whether Perl\Python\c++ etc.
I would put it this way there should be an expectation that
David Tardon wrote:
On Thu, Jun 04, 2009 at 07:23:05AM +0200, Ralf Corsepius wrote:
Steven M. Parrish wrote:
Many people have mentioned that it is not right to ask the users to
file their bug reports upstream. I ask why not?
Let me summarize what I already wrote elsewhere in this thread:
*
On 06/04/2009 02:01 AM, Tim Waugh wrote:
My own opinion is that the package maintainer is responsible for
reporting bugs upstream when they are able to reproduce them.
One reason for my belief is that I've seen the situation from the other
side: as an upstream maintainer for a package,
I wish I knew how to organize some optional program language specific
skills development sessions aimed at packagers that made sense..but I
don't. Nothing like a cert or anything like that, but to introduce
packagers and potential packagers to languages just as a good skills
building
On 06/04/2009 10:18 PM, Mathieu Bridon (bochecha) wrote:
I'd love to learn how autotools, setuptools, and other equivalents for
other languages work. Not necessarily because I want to build a
project using those, but because I sometimes have a hard time figuring
out how to patch a Makefile in
Kevin Kofler wrote:
Ralf Corsepius wrote:
Signing up for an upstream Bugzilla account takes at most 5 minutes,
... when being interested in an upstream ... wasting much more time on
investigating issues ...
There are other packages and packagers (noteworthy many of the @RH) who
exhibit
On Thu, 2009-06-04 at 17:27 +0100, Paul Howarth wrote:
I'll happily raise upstream bugs myself but it irks me when maintainers
close Fedora bugs with the UPSTREAM resolution without actually taking
the upstream fix and bringing it into Fedora.
If I've reported a bug in Fedora bugzilla
On Wednesday 03 June 2009 04:57:32 pm Kevin Kofler wrote:
Steve Grubb wrote:
And then should the bug be closed hoping that one day you pull in a
package that solves the user's problem?
If the bug is fixed upstream, the Fedora report can be reopened with a
request to backport the fix (but
On Thu, 2009-06-04 at 10:08 +0200, Michal Hlavinka wrote:
2. Was sufficient documentation available to help you participate in a
Fedora Test Day? If not, what did you find missing or in need of
improvement?
mostly, see examples:
good:
Test Day:2009-03-26 Nouveau
/sbin/lspci -d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think it is simple BAD to close bugreports with upstream!
For me as enduser of fedora i have one bugzilla and i really like
to help with bugreports, try things if maintainer needs better explains
what happens.
But i have no time and no energy to
On Thu, 4 Jun 2009, Reindl Harald wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think it is simple BAD to close bugreports with upstream!
For me as enduser of fedora i have one bugzilla and i really like
to help with bugreports, try things if maintainer needs better explains
what
Just to chime in here...
I personally try and do the following with my bugs:
- Look over the inital report.
- Move to ASSIGNED and ask the reporter any further info I need to try
and figure out if it's a packaging issue or upstream or bug or
enhancement or what.
- If its a packaging
Bernie Innocenti wrote:
Equally weird. The only standard ones are 64 heads, 32 sectors and
255 heads, 63 sectors.
Indeed, repartitioning the USB stick with 32 sectors and 255 heads fixed
boot for a previously unbootable computer.
32x255? That's an odd mix? Does 32x64 work on that
On Thu, Jun 4, 2009 at 11:37 AM, Ralf Corsepius rc040...@freenet.de wrote:
David Tardon wrote:
Let me try another analogy: How do you handle health problems?
You'll visit your doctor. You'll expect him to identify the problem and
to take appropriate steps to solve your issue--that may well
On Thu, 2009-06-04 at 14:16 +0200, Till Maas wrote:
3. Did you encounter any obstacles preventing participation in Fedora
test Days? How might they have been avoided? Did you discover any
workaround?
The live iso images failed to be converted to live usb media on F10 with a
strange
On 06/04/09 20:51, H. Peter Anvin wrote:
Bernie Innocenti wrote:
Equally weird. The only standard ones are 64 heads, 32 sectors and
255 heads, 63 sectors.
Indeed, repartitioning the USB stick with 32 sectors and 255 heads fixed
boot for a previously unbootable computer.
32x255? That's
Bernie Innocenti wrote:
Sorry, I mistyped the numbers. It was really 255 heads, 63 sectors:
(parted) p
Model: LEXAR JD EXPRESSION (scsi)
Disk /dev/sdb: 123,86,26
Sector size (logical/physical): 512B/512B
BIOS cylinder,head,sector geometry: 123,255,63. Each cylinder is 8225kB.
I guess I understand why the following URL is no longer valid,
but perhaps the ErrorDocument doesn't work by mistake?
http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/x86_64/iso/
Forbidden
You don't have permission to access
/pub/fedora/linux/releases/11/Fedora/x86_64/iso/
Krzysztof Halasa schrieb:
I guess I understand why the following URL is no longer valid,
but perhaps the ErrorDocument doesn't work by mistake?
http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/x86_64/iso/
Forbidden
The reason is, that the release date of F-11 was sliped
Hi,
Gnote is a port of Tomboy to C++ and will be default in GNOME for Fedora 12
Transmission is a GTK app and the default torrent client for Fedora in
GNOME and Xfce (Live CD)
Both are active and responsive upstreams and do have frequent releases.
If anyone want to be comaintainer, feel free to
On Thu, Jun 4, 2009 at 11:22 AM, Rahul Sundaram
sunda...@fedoraproject.org wrote:
Both are active and responsive upstreams and do have frequent releases.
If anyone want to be comaintainer, feel free to apply. If you have a
good understanding of the codebase or would be able to help with fixes,
On Thu, 4 Jun 2009, Krzysztof Halasa wrote:
I guess I understand why the following URL is no longer valid,
but perhaps the ErrorDocument doesn't work by mistake?
http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/x86_64/iso/
f11 is not yet released.
-sv
--
A new libmowgli release has been built in devel tree (F-12), which
changes the SONAME from libmowgli.so.1 to libmowgli.so.2. Rebuilds are
needed for
conky
kadu-audacious_mediaplayer
mcs
audacious-plugin*
I've rebuilt mcs already and continue with peeking at audacious and its
plugins.
Hi,
Right now if I do yum grouplist I see something like:
...
Portuguese Support
Romanian Support
Ruby
Russian Support
Samoan Support
Sanskrit Support
Sardinian Support
Serbian Support
Sindhi Support
Slovak Support
Slovenian Support
Somali Support
Sound
On Thu, Jun 04, 2009 at 08:45:21PM +0200, Reindl Harald wrote:
I think it is simple BAD to close bugreports with upstream!
+1 That's one step away from just ignoring the user.
So i think the maintainer should play as relay, taking fedora-bugreports
and in many cases report them with much
On Thu, 2009-06-04 at 21:12 +0200, Krzysztof Halasa wrote:
I guess I understand why the following URL is no longer valid,
but perhaps the ErrorDocument doesn't work by mistake?
http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/x86_64/iso/
Forbidden
You don't have
I think a package maintainers responsibilities should be to incorporate
any back-ported bug fixes, and ensure the package is reasonably fit for
end users... if they can't do this, I don't think they should be
packaging that software (whether it be due to individual skill set, or
simply the
Bill Nottingham pisze:
(If you've never used a construct like %if 0%{?fedora} in your spec
file, you can disregard this message.)
Many packages in Fedora use release-based conditionals such as:
...
%if 0%{?rhel}
%endif
%if 0%{?fedora} 10
%endif
%{?fedora:%global _with_xfce
We are aware of the kpackagekit issue and are awaiting a release from the
upstream developers. It should be released later today and after a bit of
testing I will get it into the repo asap.
SMP
I'm testing Rawhide with latest updates and KPackageKit fails to do
updates, I get this error
Till Maas wrote:
If the new bugfix release update is created, do you include there all RH
bugs that are closed UPSTREAM but fixed with this update?
Well, we try to reference fixed bugs, but often we don't even know that a
bug was fixed by an upstream bugfix release until after the fact. In fact
Steve Grubb wrote:
When bugs are closed, they disappear from the reporter's bz frontpage.
That's a Bugzilla misfeature (not to say bug). Bugzilla should default to
showing closed bugs. Not just for this case, but also to avoid duplicate
reports for:
* NOTABUG reports (which keep getting
Mary Ellen Foster wrote:
Speaking as a semi-frequent reporter of Fedora KDE bugs, I can say
that the process works pretty well for me. Of course, I'm probably
somewhat more engaged in the process than average (e.g., I maintain a
few packages myself, and I've had an account at bugs.kde.org for
Adam Williamson wrote:
If, say, the bug is in a package that gets frequent releases, and was
filed on the development release, you can just use CLOSED UPSTREAM,
because you can rely on the fact that there'll be a new upstream release
of the package soon after the upstream report is fixed, you
1 - 100 of 239 matches
Mail list logo
