[Test-Announce] 2011-09-05 @ 15:00 UTC - Fedora QA Meeting (?)

WHAT: Fedora QA Meeting WHEN: 15:00 UTC (11:00 EDT, 08:00 PDT) WHERE: #fedora-meeting So it's meeting time again on Monday, except that it's a vacation in both Canada and the U.S., so myself and Tim Flink, and perhaps some of our North American community members, won't be present. If someone else

Re: Marking zapped bugs

On Fri, 2011-09-02 at 15:43 -0700, Adam Williamson wrote: > On Fri, 2011-09-02 at 18:33 -0400, Matt McCutchen wrote: > > > > We clearly > > > want to bugs to be CLOSED, not open with a quasi-closed keyword or > > > whiteboard field. > > > > I'm not sure who "we" is, but I disagree. The generally

Re: Notice of intent: patching glibc

On Sat, 2011-09-03 at 00:50 +0200, Jan Kratochvil wrote: > On Fri, 02 Sep 2011 23:02:04 +0200, Adam Williamson wrote: > > about the 'fedora' branch of upstream glibc. > > GDB uses a similar style for the merged patchsets in the Archer repository: > > http://pkgs.fedoraproject.org/gitweb/?p=

Re: Marking zapped bugs

* Adam Williamson [03/09/2011 00:21] : > > Hum, I didn't realize our resolutions were so customized, I thought they > were the upstream ones; this is what I've been told when discussing > custom resolutions in the past. It's certainly something you could > propose as an enhancement by filing a bug

Re: Notice of intent: patching glibc

On Fri, 02 Sep 2011 23:02:04 +0200, Adam Williamson wrote: > about the 'fedora' branch of upstream glibc. GDB uses a similar style for the merged patchsets in the Archer repository: http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-archer.patch;hb=f16 > Given that this

Re: Notice of intent: patching glibc

On Sep 2, 2011, at 3:39 PM, Simo Sorce wrote: > On Fri, 2011-09-02 at 22:28 +0200, Jakub Jelinek wrote: >> On Fri, Sep 02, 2011 at 01:20:19PM -0700, Adam Williamson wrote: >>> Is there a specific reason glibc does this? >> >> Yes. >> >>> Can it not have a set of patches, one per change, as is usu

Re: Marking zapped bugs

On Fri, 2011-09-02 at 18:33 -0400, Matt McCutchen wrote: > > We clearly > > want to bugs to be CLOSED, not open with a quasi-closed keyword or > > whiteboard field. > > I'm not sure who "we" is, but I disagree. The generally accepted > definition of CLOSED is that the resolution is final unless

Re: Notice of intent: patching glibc

On Fri, 2011-09-02 at 22:28 +0200, Jakub Jelinek wrote: > On Fri, Sep 02, 2011 at 01:20:19PM -0700, Adam Williamson wrote: > > Is there a specific reason glibc does this? > > Yes. > > > Can it not have a set of patches, one per change, as is usual practice? > > Fedora glibc sources are from git,

Re: Marking zapped bugs

On Fri, 2011-09-02 at 13:54 -0700, Adam Williamson wrote: > Hum, I didn't realize our resolutions were so customized, I thought they > were the upstream ones; this is what I've been told when discussing > custom resolutions in the past. It's certainly something you could > propose as an enhancement

Re: Notice of intent: patching glibc

On Fri, 2011-09-02 at 13:43 -0700, Adam Williamson wrote: > On Fri, 2011-09-02 at 22:28 +0200, Jakub Jelinek wrote: > > On Fri, Sep 02, 2011 at 01:20:19PM -0700, Adam Williamson wrote: > > > Is there a specific reason glibc does this? > > > > Yes. > > > > > Can it not have a set of patches, one p

Re: Marking zapped bugs

On Fri, 2011-09-02 at 16:43 -0400, Matt McCutchen wrote: > On Fri, 2011-09-02 at 12:29 -0700, Adam Williamson wrote: > > On Fri, 2011-09-02 at 14:01 -0400, Matt McCutchen wrote: > > > > > What you're really saying is that most maintainers want to work from a > > > list of unexpired bugs. But ther

Re: Marking zapped bugs

Matt McCutchen (m...@mattmccutchen.net) said: > We have a number of options here which vary in implementation effort and > how much burden they impose on user and/or maintainer to get what they > want from an inadequate representation: > > 1. Status quo: hard to distinguish expired from WONTFIX.

Re: Notice of intent: patching glibc

On Fri, 2011-09-02 at 22:28 +0200, Jakub Jelinek wrote: > On Fri, Sep 02, 2011 at 01:20:19PM -0700, Adam Williamson wrote: > > Is there a specific reason glibc does this? > > Yes. > > > Can it not have a set of patches, one per change, as is usual practice? > > Fedora glibc sources are from git,

Re: Marking zapped bugs

On Fri, 2011-09-02 at 12:29 -0700, Adam Williamson wrote: > On Fri, 2011-09-02 at 14:01 -0400, Matt McCutchen wrote: > > > What you're really saying is that most maintainers want to work from a > > list of unexpired bugs. But there are ways to achieve that other than > > marking all the expired b

Re: Notice of intent: patching glibc

On Fri, Sep 02, 2011 at 01:20:19PM -0700, Adam Williamson wrote: > Is there a specific reason glibc does this? Yes. > Can it not have a set of patches, one per change, as is usual practice? Fedora glibc sources are from git, and the bit diff is just generated diff between the upstream snapshot a

Re: Notice of intent: patching glibc

On Wed, 2011-08-31 at 08:50 +0200, Andreas Schwab wrote: > Please wait until I am finished working on it. This is not a bug that > can be easily reproduced. I note that this is fixed in -7: thanks. However, checking how it was fixed was rather painful... http://pkgs.fedoraproject.org/gitweb/?p=g

Re: Marking zapped bugs

On Fri, 2011-09-02 at 14:01 -0400, Matt McCutchen wrote: > What you're really saying is that most maintainers want to work from a > list of unexpired bugs. But there are ways to achieve that other than > marking all the expired bugs WONTFIX. Maintainers can always filter on > the currently maint

Outage: database and vpn server outage: 2011-09-07 21UTC

Outage: database and vpn server outage: 2011-09-07 21UTC There will be an outage starting at 2011-09-07 21:00 UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2011-09-07 21:00

Re: Marking zapped bugs

[Finally returning to this issue. If your mail client doesn't thread across this time span, see https://lists.fedoraproject.org/pipermail/devel/2010-November/145105.html for the previous part of the thread.] On Fri, 2010-11-05 at 12:19 -0700, Adam Williamson wrote: > On Thu, 2010-11-04 at 16:10

F-16 Branched report: 20110902 changes

Compose started at Fri Sep 2 13:15:30 UTC 2011 Broken deps for x86_64 -- 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmpagent.so.25()(64bit) 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmpmibs.so.25()(64bit)

Yum/Bugzilla feature requests

Recently while running Fedora 16, my attempt at: yum update --skip-broken failed with: warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 069c8460: NOKEY Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64 The GPG keys listed for the "Fedora 16 -

Re: Initscript migration to systemd: triggerun called on downgrade

Petr Pisar (ppi...@redhat.com) said: > Then why does migration how-to use triggerun instead of triggerpostun? > I cannot see reason why the code should be executed on downgrade. %triggerpostun runs after the old version is uninstalled - you can't save any state then. Bill -- devel mailing list

Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

On Fri, 2011-09-02 at 09:27 -0600, Jonathan Corbet wrote: > > The questions is how do we want to handle this? At least we should > > release note this I guess, but perhaps we can do something smarter? > > Perhaps the first thing to do is to try to figure out if it's only me. > Nobody else has gri

Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

On Fri, Sep 02, 2011 at 09:27:12 -0600, Jonathan Corbet wrote: > > Nobody else has griped on the Rawhide front, but, then, I think I may be > about the only Rawhide user left (and people keep telling me that I > shouldn't be there either). If it's only me I'll figure out how to put I use rawh

Re: bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

On Fri, 02 Sep 2011 09:18:31 +0200 Hans de Goede wrote: > Which is in essence the problem you are seeing here Jonathan, after > my bluez update, your bluetooth dongle is actually being out into > HCI mode, so that it can for example also be used to sync with your > phone, use a bluetooth headset,

Re: Will we finally get firefox 6.0.1???

On Friday, September 02, 2011 12:47:06 AM Joshua C. wrote: > Not exactly. The source code was synced to the mirrors on August 30th, > so it's more than 3 days... Like Harald said, the issue is already fixed in Fedora (since August 31th). Aside from distrusting a certain CA there were no further

rawhide report: 20110902 changes

Compose started at Fri Sep 2 08:15:27 UTC 2011 Broken deps for x86_64 -- FlightGear-2.0.0-6.fc16.x86_64 requires libosgViewer.so.74()(64bit) FlightGear-2.0.0-6.fc16.x86_64 requires libosgUtil.so.74()(64bit) FlightGear

Re: Initscript migration to systemd: triggerun called on downgrade

On 2011-09-02, Iain Arnell wrote: > On Fri, Sep 2, 2011 at 9:53 AM, Petr Pisar wrote: >> On 2011-09-01, Bill Nottingham wrote: >>> Petr Pisar (ppi...@redhat.com) said: I'm migrating quota_nld service (provided by quota_nld subpackage of quota spec) to systemd. Offical howto

Re: Initscript migration to systemd: triggerun called on downgrade

On Fri, Sep 2, 2011 at 9:53 AM, Petr Pisar wrote: > On 2011-09-01, Bill Nottingham wrote: >> Petr Pisar (ppi...@redhat.com) said: >>> I'm migrating quota_nld service (provided by quota_nld subpackage of >>> quota spec) to systemd. >>> >>> Offical howto >>>

Re: Initscript migration to systemd: triggerun called on downgrade

On 2011-09-01, Bill Nottingham wrote: > Petr Pisar (ppi...@redhat.com) said: >> I'm migrating quota_nld service (provided by quota_nld subpackage of >> quota spec) to systemd. >> >> Offical howto >>

bluez and hci's which initially come up as hid (was Re: Some days it just doesn't pay to update)

Hi Jonathan, Adam, et all, Wed Aug 31 Jonathan Corbet wrote: > So, I thought...LWN writing is almost done for the day, why not do an > update and see what happens? > > What happened: > > - My Logitech bluetooth keyboard, which has Just Worked for years, >doesn't work anymore. Grub still