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?
You'r
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
car?
Did a bunch of hobbyists from around the world build you
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
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,
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 car
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 ignore this message, if not then reply if you need some more
feedback from me and I will open a
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? If so, I think it would be safer to stop driving
immediat
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 necessarily developers.
* Users aren't necessarily interested in getting
On Wed June 3 2009, Thorsten Leemhuis wrote:
> I had planed to put them in the wiki as a table was well, but ran out of
> time, sorry (²).
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
On Mon, Jun 01, 2009 at 06:45:07PM -0400, Tom spot Callaway wrote:
> On 06/01/2009 06:45 PM, Jesse Keating wrote:
> > If we had I2 in PHX this would get a lot faster.
>
> We just need to hold some classes and get the PHX datacenter certified
> as a University. ;)
Not necessarily. I don't see why
Andreas Thienemann wrote:
> Leaving a bit more time between the cut-off date for the questionaire and
> the town hall meeting should hopefully fix that.
Yes, there needs to be more time between the end of nominations and the town
hall meetings. When I went to sleep yesterday, the meeting time was
On Wed, 3 Jun 2009, Paul W. Frields wrote:
> Thorsten, thanks not only to you for doing this,
Yeah. Thanks a lot as well.
> I'm disappointed this ended up being a more difficult process than you
> intended, but I have no doubt we can improve it for the next cycle.
Leaving a bit more time betwee
>> Why are the relevant Obsoletes missing (commented out)?
>
> Because if they were there, everyone would get the OLPC-patched package
> instead of the stock Fedora one. They should be Conflicts, not Obsoletes.
> But ideally the whole situation should be fixed so OLPC doesn't need a
> patched GConf
On Wed, 2009-06-03 at 09:21 -0500, King InuYasha wrote:
> 6. If they were planned better, then maybe I would be able to set
> aside time to do them. I would like to participate in future Test
> Days.
You're right that we generally only get the meat of the test cases and
so forth up about 48 hours
On Wed, 2009-06-03 at 11:25 +0100, David Woodhouse wrote:
> On Tue, 2009-06-02 at 16:17 -0400, Steve Grubb wrote:
> >
> > 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? I
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 report can be reopened with a
> request to backport the fix (
On Wed, Jun 3, 2009 at 1:46 PM, Ralf Ertzinger 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 e
Either bugzilla.redhat.com works as the center bugzilla for all
components in Fedora
and those maintaining or are responsible for these components for being
in Fedora
work as the liaison between the reporter and upstream...
Or
We redirect reporters directly from the beginning to upstream bugzilla
Michael Schwendt wrote:
> Why are the relevant Obsoletes missing (commented out)?
Because if they were there, everyone would get the OLPC-patched package
instead of the stock Fedora one. They should be Conflicts, not Obsoletes.
But ideally the whole situation should be fixed so OLPC doesn't need a
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 that should only be done if it's important
enough that it canno
On 06/03/2009 04:55 PM, Josh Boyer wrote:
> On Wed, Jun 03, 2009 at 04:24:16PM -0400, Bill Nottingham wrote:
>> Thorsten Leemhuis (fed...@leemhuis.info) said:
>>> The answers are quite interesting and as far as I can see can be quite
>>> helpful to decide whom to (not) vote for. So if you plan to
On Wed, Jun 03, 2009 at 09:28:36PM +0200, 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 respons
On Wed, 2009-06-03 at 22:43 +0200, Emmanuel Seyman wrote:
> * Mathieu Bridon (bochecha) [03/06/2009 22:41] :
> >
> > So as a package maintainer, you don't want a bug in a software you
> > maintain to be fixed ?
>
> Not everyone agrees on what is a bug.
That's a feature ;)
P.Yves
--
fedora-deve
Bill Nottingham wrote:
> Depends on the bug/issue. For security isses, I don't think
> CLOSED->UPSTREAM is appropriate, unless it requires a major architecture
> of the code base. Similarly, if an app is crashing immediately on startup,
> it's not something we necessarily want to just hope upstream
On Wed, Jun 03, 2009 at 04:24:16PM -0400, Bill Nottingham wrote:
>Thorsten Leemhuis (fed...@leemhuis.info) said:
>> The answers are quite interesting and as far as I can see can be quite
>> helpful to decide whom to (not) vote for. So if you plan to vote in the
>> elections I'd suggest you go and
Juha Tuomala wrote:
> Would to make the report then if she says 'no'? :)
We'll just close it as INSUFFICIENT_DATA as with any other ignored needinfo
request. To get the bug fixed, they need to report it to the proper place.
> It's a fact that knowledge increases when you move steps to upstream.
Steve Grubb wrote:
> For the record, I agree with this sentiment. If there's a bug in my
> packages, I want to fix it and not cause the reporter to have to get
> upstream bz accounts or join upstream mail lists just because they
> reported a problem. I will interact with the reporter until I see th
* Mathieu Bridon (bochecha) [03/06/2009 22:41] :
>
> So as a package maintainer, you don't want a bug in a software you
> maintain to be fixed ?
Not everyone agrees on what is a bug.
Emmanuel
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/
Ralf Corsepius wrote:
> I stopped reporting bugs against Fedora's evolution, because its @RH
> maintainer preferred to close bugs and tried to push me around to
> upstream. Wrt. evolution, I was an ordinary user and am not interested
> in getting further involved.
Signing up for an upstream Bugzil
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? Only very few peop
>> I agree. Demanding them to take any responsibility
>> on that report, even testing it again makes them just
>> think twice next time to report anything.
> [snip]
>> Exactly. If the reporter wants to take part to that
>> communication, good. But that should not expected.
>>
>> More reports is bet
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 these people
> forums are much more better.
Uh, forums are a hor
> 1. How did you find out about Fedora Test Days?
Planet.fp.o
> 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?
Documentation was excellent.
> 3. Did you encounter any obstacles preventing
Juha Tuomala wrote:
> I agree. Demanding them to take any responsibility
> on that report, even testing it again makes them just
> think twice next time to report anything.
[snip]
> Exactly. If the reporter wants to take part to that
> communication, good. But that should not expected.
>
> More re
Thorsten Leemhuis (fed...@leemhuis.info) said:
> The answers are quite interesting and as far as I can see can be quite
> helpful to decide whom to (not) vote for. So if you plan to vote in the
> elections I'd suggest you go and read the answers!
Thanks for doing this!
Bill
--
fedora-devel-lis
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?
You're supposed to be
On Wed, 3 Jun 2009, Bill Nottingham wrote:
Jesse Keating (jkeat...@redhat.com) said:
On Wed, 2009-06-03 at 13:49 -0400, Seth Vidal wrote:
And the optimization there is fairly well known. We need to read in and
not change the prestodelta file. It's on my short-ish createrepo list.
Hrm, bill
Matej Cepl (mc...@redhat.com) said:
> > Depends on the bug/issue. For security isses, I don't think
> > CLOSED->UPSTREAM is appropriate, unless it requires a major architecture
> > of the code base. Similarly, if an app is crashing immediately on
> > startup, it's not something we necessarily want
Steven M. Parrish wrote:
> I can only speak for myself and not the other triagers. I work solely on
> KDE issues because in addition to triage I also maintain several KDE
> packages and work closely with the other maintainers. The upstream method
> we use was discussed and agreed to as the best s
Jesse Keating (jkeat...@redhat.com) said:
> On Wed, 2009-06-03 at 13:49 -0400, Seth Vidal wrote:
> > And the optimization there is fairly well known. We need to read in and
> > not change the prestodelta file. It's on my short-ish createrepo list.
>
> Hrm, bill thought it was something on the ma
James Laska wrote:
> 1. How did you find out about Fedora Test Days?
fedora-devel-announce
> 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?
The instructions were sufficient.
> 3. Did you e
> It might have helped to find the problem earlier -- I for example got
> the impression that a lot of people had problems with the storage
> rewrite and thus aborted their tests with Alpha or Beta.
There was no storage rewrite in the Alpha, so this isn't the case there.
For the beta, you are corr
Hi!
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, who seems to be traveling or
something according
> > An earlier freeze would have just frozen the work unfinished. The
> > rewrite was a massive undertaking and we knew it was going to take
> > longer than the release cycle to finish. Freezing earlier wouldn't have
> > helped.
>
> Then it should have been done in a work branch and targeted for
James Laska wrote:
===
1. How did you find out about Fedora Test Days?
Test-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 enco
On Wed, 3 Jun 2009, Jesse Keating wrote:
On Wed, 2009-06-03 at 13:49 -0400, Seth Vidal wrote:
And the optimization there is fairly well known. We need to read in and
not change the prestodelta file. It's on my short-ish createrepo list.
Hrm, bill thought it was something on the mash side, w
On Wed, 2009-06-03 at 13:49 -0400, Seth Vidal wrote:
> And the optimization there is fairly well known. We need to read in and
> not change the prestodelta file. It's on my short-ish createrepo list.
Hrm, bill thought it was something on the mash side, where he validates
the signature of all the
On Wed, Jun 03, 2009 at 10:10:26 -0400,
James Laska wrote:
>
> 1. How did you find out about Fedora Test Days?
Mostly I saw them in the mailing lists first, but saw reminders in FWN.
> 2. Was sufficient documentation available to help you participate in a
> Fedora Test Day? If not, what di
On Wed, 03 Jun 2009 11:41:33 -0500, Jon wrote:
> I use it, and will take it if the co-maintainer isn't interested.
There is no co-maintainer, just the EPEL maintainer as "watcher".
I'll Release Ownership in pkgdb after sending this mail.
--
fedora-devel-list mailing list
fedora-devel-list@redh
On Wed, 3 Jun 2009, Jesse Keating wrote:
On Wed, 2009-06-03 at 08:55 -0400, Paul W. Frields wrote:
If the FAD identifies some tangibles (hardware, etc.) that would help
alleviate some of the time problems, I can tell you that Spot and I
will do our best to procure them. From what I've heard
On Mon, Apr 20, 2009 at 11:36 PM, Toshio Kuratomi wrote:
> Mono-2.4 has been built for ppc64 in F11 and devel. So people should be
> able to start rebuilding packages to include ppc64 as well as the other
> arches. There's a few wrinkles to watch out for:
>
> 1) Packages with dependencies will h
On Wed, Jun 03, 2009, Christoph Höger 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 MIME-version: and cannot find that string. So it adds it.
> In turn my mail provider bounces the
Hi folks,
I see a small problem with evolution when sending to mailinglists.
Obviously evolution puts: Mime-version: 1.0 in the header, hypermail
searches for MIME-version: and cannot find that string. So it adds it.
In turn my mail provider bounces the return message that should be sent
to me co
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.
There is an accompanying package in the Voldemort Repository which con
Michael Schwendt wrote:
I'm looking for somebody to become the "chkrootkit" package owner,
preferably not anyone who just wants to increase the list of owned
packages for some doubtful metrics.
There are no open tickets for chkrootkit in Fedora. Last upstream release
has been in Dec 2007. Upstre
On Wed, 2009-06-03 at 08:55 -0400, Paul W. Frields wrote:
> If the FAD identifies some tangibles (hardware, etc.) that would help
> alleviate some of the time problems, I can tell you that Spot and I
> will do our best to procure them. From what I've heard others
> describe up until now, it doesn'
I'm looking for somebody to become the "chkrootkit" package owner,
preferably not anyone who just wants to increase the list of owned
packages for some doubtful metrics.
There are no open tickets for chkrootkit in Fedora. Last upstream release
has been in Dec 2007. Upstream has been responsive, bu
On 06/03/2009 09:25 PM, James Laska wrote:
> Thanks for the feedback!
>
> On Wed, 2009-06-03 at 20:16 +0530, Rahul Sundaram wrote:
>>
>>> 5. What follow-up actions do you expect after the Test Day? Are
>> your
>>> expectations currently being met?
>>
>> Yes. Although I was hoping there would be a
On Sun, May 31, 2009 at 3:47 AM, Valent Turkovic
wrote:
> Which tools would you recommend somebody uses to make this welcome screen?
You should probably talk to the people who craft the Live Desktop
image and the harddrive install that results from it. If the point of
this is to target new users
> https://bugzilla.redhat.com/show_bug.cgi?id=484862
>
>
>
>
>
> --- Comment #2 from John (J5) Palmieri 2009-06-03
> 11:45:26 EDT ---
> Of course it conflicts with GConf2. It is GConf2 with a patch. Pretty much
> binary ABI compatible unless the two have diverged recently. It shouldn't b
Thanks for the feedback!
On Wed, 2009-06-03 at 20:16 +0530, Rahul Sundaram wrote:
>
> > 5. What follow-up actions do you expect after the Test Day? Are
> your
> > expectations currently being met?
>
> Yes. Although I was hoping there would be a test day for Ext4.
I was too, but there were some
On Wed, 3 Jun 2009, James Laska wrote:
> ===
>
> 1. How did you find out about Fedora Test Days?
Planet.fp.o
> 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
> improveme
> On Tuesday 02 June 2009 06:17:02 pm Steven M. Parrish wrote:
> > This is from the official Bugzappers page
> > https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#Upstream
> >in
>
> So, this raises the question about bugzappers. Should they be making the
> determination for maintaine
On 06/03/2009 02:38 PM, Tom "spot" Callaway wrote:
On 06/03/2009 09:01 AM, Josh Boyer wrote:
Oh, and time. Always need time. If you or spot could procure time, let me
know ;)
Man, if I knew how to do that, I'd be a lot wealthier than I am now. ;)
Extend the day to 36 hours
Go
On 06/03/2009 07:40 PM, James Laska wrote:
> 1. How did you find out about Fedora Test Days?
>
Mailing list, forum and blog posts
> 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?
Genera
Compose started at Wed Jun 3 06:15:03 UTC 2009
Updated Packages:
anaconda-11.5.0.59-1.fc11
-
* Tue Jun 02 2009 Chris Lumens - 11.5.0.59-1
- Do not show disabled repos such as rawhide during the install (#503798).
(jkeating)
Summary:
Added Packages: 0
Removed Packages
On 06/03/2009 09:01 AM, Josh Boyer wrote:
> Oh, and time. Always need time. If you or spot could procure time, let me
> know ;)
Man, if I knew how to do that, I'd be a lot wealthier than I am now. ;)
~spot
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/m
James Laska wrote:
>
> 1. How did you find out about Fedora Test Days?
Mailing list posting.
>
> 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, I found everything I needed on the c
On Wed, Jun 3, 2009 at 06:46, Ralf Corsepius wrote:
> Michael Schwendt wrote:
>
>> On Wed, 03 Jun 2009 14:06:45 +0200, Ralf wrote:
>>
>> I consider users (esp. bug reporters) not to be "the dumb pigs eating the
>>> hog wash they get for free", or "clueless comsumer masses" aborbing anything
>>>
On Wed, Jun 3, 2009 at 9:10 AM, James Laska wrote:
> Greetings,
>
> The Fedora QA team would like your feedback on Fedora 11 Test Days. You
> may have seen Adam Williamson's planet post [1] kicking off Fedora 12
> Test Day planning. We're interested in identifying areas for
> improvement to inc
On Wed, Jun 03, 2009 at 10:01:58AM -0400, 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 hap
On 06/03/2009 03:55 PM, Matthias Clasen wrote:
On Wed, 2009-06-03 at 14:16 +0200, Denis Leroy wrote:
On 06/03/2009 01:48 PM, Josh Boyer wrote:
On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote:
In an effort to focus more on FOSS upstream development, I am going to
be orphaning some o
Greetings,
The Fedora QA team would like your feedback on Fedora 11 Test Days. You
may have seen Adam Williamson's planet post [1] kicking off Fedora 12
Test Day planning. We're interested in identifying areas for
improvement to increase participation and improve effectiveness.
Please take 10-1
Matthias Clasen wrote:
On Wed, 2009-06-03 at 14:16 +0200, Denis Leroy wrote:
On 06/03/2009 01:48 PM, Josh Boyer wrote:
On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote:
In an effort to focus more on FOSS upstream development, I am going to
be orphaning some of my Fedo
Muayyad AlSadi wrote:
> maybe a trivial pygtk script ?
>
> --
> fedora-devel-list mailing list
> fedora-devel-list@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
+1
I was just about to suggest that. And, if alot of the text items are not
embedded directly (i.e. loaded fr
On Tuesday 02 June 2009 06:17:02 pm Steven M. Parrish wrote:
> This is from the official Bugzappers page
> https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#Upstreamin
So, this raises the question about bugzappers. Should they be making the
determination for maintainers that the re
On Wed, 2009-06-03 at 14:16 +0200, Denis Leroy wrote:
> On 06/03/2009 01:48 PM, Josh Boyer wrote:
> > On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote:
> >> In an effort to focus more on FOSS upstream development, I am going to
> >> be orphaning some of my Fedora packages in the near fut
Michael Schwendt wrote:
On Wed, 03 Jun 2009 14:06:45 +0200, Ralf wrote:
I consider users (esp. bug reporters) not to be "the dumb pigs eating
the hog wash they get for free", or "clueless comsumer masses" aborbing
anything they don't pay for with money, but them to be the foundation of
your w
On Wed, Jun 03, 2009 at 08:55:48AM -0400, Paul W. Frields wrote:
>On Tue, Jun 02, 2009 at 08:15:32PM -0400, Josh Boyer wrote:
>> We are facing some real limitations on our turn around time for
>> things at the moment and they are only going to get worse as we have
>> newer releases that will get th
On Wed, 03 Jun 2009 14:06:45 +0200, Ralf wrote:
> I consider users (esp. bug reporters) not to be "the dumb pigs eating
> the hog wash they get for free", or "clueless comsumer masses" aborbing
> anything they don't pay for with money, but them to be the foundation of
> your work and them to be
On Tue, Jun 02, 2009 at 08:15:32PM -0400, Josh Boyer wrote:
> We are facing some real limitations on our turn around time for
> things at the moment and they are only going to get worse as we have
> newer releases that will get the delta rpms. At the same time, the
> same people are getting raked
On Tuesday 02 June 2009 11:09:49 pm Ralf Corsepius wrote:
> Kevin Kofler wrote:
> > Steve Grubb wrote:
> >> 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 pr
On Tuesday 02 June 2009 07:34:17 pm Kevin Kofler wrote:
> Steve Grubb wrote:
> > 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
On 06/03/2009 01:48 PM, Josh Boyer wrote:
On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote:
In an effort to focus more on FOSS upstream development, I am going to
be orphaning some of my Fedora packages in the near future, starting
with this first batch.
brasero (high-maintenance)
Can anyone check on this?
https://bugzilla.redhat.com/show_bug.cgi?id=503830
I know that the bug reports get to the anaconda maintenance list, but
I was worried that it might affect future fedora upgrades.
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Adminis
Michael Schwendt wrote:
On Wed, 03 Jun 2009 05:09:49 +0200, Ralf wrote:
Kevin Kofler wrote:
Steve Grubb wrote:
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 pro
Rahul Sundaram wrote:
On 06/03/2009 05:18 PM, Josh Boyer wrote:
On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote:
In an effort to focus more on FOSS upstream development, I am going to
be orphaning some of my Fedora packages in the near future, starting
with this first bat
Jaroslav Reznik wrote:
On Miércoles 03 Junio 2009 05:09:49 Ralf Corsepius escribió:
Kevin Kofler wrote:
Steve Grubb wrote:
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 the
On 06/03/2009 05:18 PM, Josh Boyer wrote:
> On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote:
>> In an effort to focus more on FOSS upstream development, I am going to
>> be orphaning some of my Fedora packages in the near future, starting
>> with this first batch.
>>
>> brasero (hig
On Wed, Jun 03, 2009 at 09:20:54AM +0200, Denis Leroy wrote:
> In an effort to focus more on FOSS upstream development, I am going to
> be orphaning some of my Fedora packages in the near future, starting
> with this first batch.
>
> brasero (high-maintenance)
Wait... didn't we just make this
On 05/06/2008 03:54 PM, Brian Pepple wrote:
On Tue, 2008-05-06 at 07:26 -0700, Toshio Kuratomi wrote:
Brian, we probably want to list the ways to deal with bug reports in the
policy as many maintainers don't realize how many options there are for
getting help fixing a bug.
Here's wha
On Mon, Jun 01, 2009 at 08:15:48AM +0300, Pasi Kärkkäinen wrote:
> Hello.
>
> Yesterday I installed latest F11/rawhide. The default installed kernel
> (2.6.29 something) works fine.
>
> I compiled custom 2.6.30-rc6 kernel, and created initrd for it, and tried
> booting it.
>
> Booting process
> dates (inactive upstream)
I'll take this one.
Peter
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
On Miércoles 03 Junio 2009 11:52:37 Juha Tuomala escribió:
> On Wednesday 03 June 2009 11:47:26 Jaroslav Reznik wrote:
> > PS: I'm not saying to not report bugs to RH bugzilla, we can help then
> > but lack of direct communication between user and developer is issue,
>
> You're assuming that all th
On 06/03/2009 12:50 PM, Denis Leroy wrote:
> In an effort to focus more on FOSS upstream development, I am going to
> be orphaning some of my Fedora packages in the near future, starting
> with this first batch.
>
> transmission
Taken this. Co-maintainers welcome.
Rahul
--
fedora-devel-list m
Hello,
I want to split uClibc from busybox package - is here a volunteer who is
willing to take care about it?
Ivana Hutarova Varekova
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
On Tue, 2009-06-02 at 16:17 -0400, Steve Grubb wrote:
>
> 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
On Wednesday 03 June 2009 11:47:26 Jaroslav Reznik wrote:
> PS: I'm not saying to not report bugs to RH bugzilla, we can help then but
> lack of direct communication between user and developer is issue,
You're assuming that all those users are engineers and technical
people. That might be tru
On Wed, 03 Jun 2009 05:09:49 +0200, Ralf wrote:
> Kevin Kofler wrote:
> > Steve Grubb wrote:
> >> 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
On Wednesday 03 June 2009 02:34:17 Kevin Kofler wrote:
> It's the reporter's job to report the bug upstream when asked to do so.
Would to make the report then if she says 'no'? :)
> Fixing bugs often requires two-way communication, so it's important for
> upstream to have a real reporter to ta
1 - 100 of 110 matches
Mail list logo
