F12 to require "i686", but which CPUs do not qualify?

2009-08-13 Thread Tony Nelson 
I've noticed that F12 will require a CPU with "i686" architecture, and 
that my Athlon 1.2GHz won't qualify.  I accept that F11 is the last 
Fedora release that I'll be able to use.  My concern is that many 
present Fedora users will be unpleasantly surprised that a new 
installation doesn't work, or at least that they've wasted the 
download.

The Release Notes, starting with the F12 Alpha Release Notes, should 
tell users about this, and so should the release announcements.  The 
difficulty is in telling them what exactly is an "i686" CPU, as that is 
defined by GCC and is said to be a moving target (over the years).  I'm 
hoping that someone qualified can make the appropriate changes to the 
Releases Notes wiki (I don't know what all the requirements are, though 
I do know that the Athlon does not support SSE/SSE2).

Is there a simple way for ordinary users to know if their CPU is 
expected to work on F12 (as an "i686" according to GCC)?  Is there a 
tool to run that doesn't require downloading F12?

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: F12 to require "i686", but which CPUs do not qualify?

2009-08-14 Thread Tony Nelson 
I'm late replying -- had trouble with my mail server -- so I'm moving 
all my replies to Bill Nottingham's post, as I think he can fix the 
wiki pages most authoritatively to not say that Athlons will not work,
if that is indeed the proper thing to do, given that so many packages 
depend on packages that are only built for SSE2.

<https://fedoraproject.org/wiki/Features/F12X86Support>
<https://fedoraproject.org/wiki/Talk:Features/F12X86Support>

If necessary, I can install Rawhide and see if it boots, and then edit 
the above wiki page and the Alpha release notes, but I'd prefer if 
someone who already uses an Athlon-core processor on Rawhide did it.


On 09-08-13 10:34:58, Peter Robinson wrote:
> Tony Nelson wrote:
 ...
> > Is there a simple way for ordinary users to know if their CPU is
> > expected to work on F12 (as an "i686" according to GCC)?  Is there 
> > a tool to run that doesn't require downloading F12?
> 
> https://fedoraproject.org/wiki/Features/F12X86Support
> 
> Its outlined in the link above. An athlon should be fine. Basically 
> if its i586 + cmov it should work. You can tell if you have cmov by
> looking at /proc/cpuinfo.

According to that link, an Athlon is specifically excluded.  According 
to the Talk:Features/F12X86Support link 
<https://fedoraproject.org/wiki/Talk:Features/F12X86Support>, SSE2 is 
required.


> Originally it wasn't planned to support them but there was enough
> discussion to change peoples minds :-)

If that has changed, then those wiki pages need updating, as well as 
the Release Notes and release announcements.  Thanks.


On 09-08-13 10:35:29, Jon Ciesla wrote:
> Quoting Bill Nottingham:
> 
> Given the loud feedback, I've updated the proposal at:
>   https://fedoraproject.org/wiki/Features/F12X86Support
> 
> The revised proposal:
> 
> - Build all packages for i686 (this requires cmov)
> - Optimize for Atom
> 
> Why?
 ...

That doesn't actually quite say about SSE2, but at 
<https://fedoraproject.org/wiki/Talk:Features/F12X86Support>:

> _Bill Nottingham_ Once a set has been decided on, this should be 
> pretty trivial. With respect to the proposal, 'grep sse2 /proc/
> cpuinfo' should work.

Bill?

-- 

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: F12 to require "i686", but which CPUs do not qualify?

2009-08-14 Thread Tony Nelson 
On 09-08-14 09:20:04, Naheem Zaffar wrote:
> Not Bill, but from my understanding, SSE2 was originally going to be
> required and that question must have been presented and answered at
> that point. Once the main page got updated after discussion, the 
> original questions that no longer apply have not been removed.

Apparantly I'm not making myself clear.  That page specifically 
excludes all AMD processors before the Geode LX, thus it excludes the 
Athlon:

> * pre-AMD Geode processors

It may be that discussions have happened elsewhere, but the current
F12 Feature page does exclude the Athlon and similar processors.


> 2009/8/14 Tony Nelson
> >
> >
> > That doesn't actually quite say about SSE2, but at
> > <https://fedoraproject.org/wiki/Talk:Features/F12X86Support>:
> >
> > > _Bill Nottingham_ Once a set has been decided on, this should be
> > > pretty trivial. With respect to the proposal, 'grep sse2 /proc/
> > > cpuinfo' should work.
> >
> > Bill?

-- 

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Default heuristics for variable-format displays

2009-09-15 Thread Tony Nelson 
On 09-09-15 12:06:54, Adam Jackson wrote:
 ...
> def mode_dpi_cmp(x, y):
>   return cmp(abs(x.dpi - 96), abs(y.dpi - 96))
 ...

The names x and y suggest coordinates to me.  I'd have read the code 
right the first time if the names had been a and b.

> def best_mode(modes, dpi_known = True):
>   l = filter(lambda x: x.refresh >= 72, modes)


If the sort is stable, how about sorting by highest refresh rate first? 
That way an 85 Hz refresh (if available) would be preferred over a 75 
Hz refresh rate.  (I expect the 72 Hz is to separate out LCDs which 
usually have a fixed rate of about 60 Hz.)

l = filter(lambda a: a.refresh >= 72, modes).sorted(
key=lambda a: -a.refresh )

(BTW, use key instead of cmp in the other cases as well.)

>   if l == []:
>   l = modes
>   if dpi_known:
>   l.sort(cmp=mode_dpi_cmp)
>   else:
>   l.sort(cmp=mode_size_cmp)
>   return l[0]
 ...

In any case, thank you for working on it (my bz is 522155 "RFE choose
sensible resolution during boot").

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Default heuristics for variable-format displays

2009-09-22 Thread Tony Nelson 
On 09-09-21 11:46:41, Alexander Boström wrote:
> Here's my suggestion...
> 
>   def mode_megapixels(mode):
>   return mode.width * mode.height
> 
>   # Sort by best refresh rate.
>   modes.sort(key=lambda mode: -mode['refresh'])
> 
>   # Prefer to balance refresh rate vs. pixels.
>   if dpi_known:
>   acceptable = filter(lambda mode: mode.dpi >= 90,
> modes)
>   if len(acceptable) > 0:
>   # Anything above 90 DPI is good enough
>   # for a default.

This is wrong, as it will produce more or less random resolutions up to 
the maximum supported by the monitor, which is in fact the motivation 
for doing better.  The modes close to 90 DPI should be preferred.

>   # Pick the one with the best refresh.
>   return acceptable[0]
> 
>   # DPI not known or too low, balance refresh vs. pixels.
>   best_megapixels = max(modes, mode_megapixels)
>   acceptable = filter(lambda mode: megapixels(mode) >=
>   best_megapixels / 2)
>   # Pick the mode with the highest refresh rate and at least
>   # half the max possible number of pixels.
>   acceptable[0]

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: yum-presto not on by default

2009-09-24 Thread Tony Nelson 
On 09-09-24 16:25:46, Matthias Clasen wrote:
> On Thu, 2009-09-24 at 16:22 -0400, Seth Vidal wrote:
> 
> > I don't consider the single command a 
> > significant barrier, either way.
> 
> Maybe not for people who maintain yum...

Most CLI users will be fine, but innocent GUI users would benefit from 
a hint in the PackageKit GUI, if one could be added.  How about a 
checkbox "Delta-RPMS", with text in a mouse-hover:  checked "updates 
use less bandwidth but are slower to install"; unchecked "updates use 
more bandwidth but are faster to install".  If yum-presto isn't 
installed, dim the checkbox and have the mouse-hover suggest installing 
yum-presto for smaller downloads.

Of course, if nightly automatic updates are being done, the time won't 
matter.

I do wish more of the updates were delta'd.  Today I had 81 MB total 
size, which became 17 MB delta-RPMs (for 45 MB rebuilt) plus 36 MB 
regular, for a total of 53 MB, a savings of about 1/3.  (Not that it 
matters here; I have DSL.)

-- 

TonyN.:'   
  '  


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Opinions on packaging ATLAS (for the x86 architecture)

2009-09-25 Thread Tony Nelson 
On 09-09-25 10:41:56, Deji Akingunola wrote:
> Hi all,
> 
> I would like to know your opinion (or any guideline, if it exists) 
> for the best way to package the ATLAS library for the x86 arch ATM. 
 ...

> i). Create a generic x86 'atlas' main package for the P6 
> architecture,
 ...

Currently, the default atlas contains SSE and no SSE.  AIUI, even no 
SSE is faster than no ATLAS.  Still, I would hope that the proper 
variant is chosen at run time, or at least install time.  If so, the 
proper packaging for ATLAS is a single package built for all x86 (or 
x64 or SPARK or whatever) variants.  (My own machine would benefit from 
a 3DNOW build.)

-- 

TonyN.:'   
  '  


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Opinions on packaging ATLAS (for the x86 architecture)

2009-09-26 Thread Tony Nelson 
On 09-09-26 08:32:45, Kevin Kofler wrote:
 ...
> Of course the root of the problem is ATLAS's lack of support for 
> runtime CPU feature detection ...

Presumably that could be added to the Fedora package as a patch.  It's 
SMOP to check the CPU and load the proper library, if someone who knew 
how were to do it.  Other distros might also use such a patch.  Then 
there would be only one package per arch, containing all variants.

> ... (The ATLAS developers expect everybody to compile a tuned ATLAS 
> for their own machine and show only very limited interest in binary 
> packaging.)

I haven't been able to get that to work [1], but it does take over 3 
hours to fail.  I don't think most users can be expected to build their 
own ATLAS.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=525818

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: [Fedora-packaging] Exemption for bundling local copy of system library?

2009-09-29 Thread Tony Nelson 
On 09-09-29 15:37:10, Toshio Kuratomi wrote:

> I would argue no.  The guidelines are written to apply to all
> libraries except with very limited exceptions to keep this from 
> happening because security vulnerabilities are not limited to network 
> facing code, suid code, or any other class that we've been able to 
> identify.  The libz vulnerability many years ago is the classic 
> example of this.  Many programs were embedding libz, many statically. 
> When a security vulnerability in libz was discovered, we had to find 
> all of those programs, remove the vulnerable library, patch any code 
> that didn't work with the newer version, and rebuild all of those 
> packages.  This is not what you want to do when you are in the time-
> constrained situation of putting out a zero day update to the code.
 ...

If the number of exceptional packages is kept small, and the exeptions 
were to Provide "private_libfoo" (for each "foo" lib), then would it 
be manageable enough?  At least it would be easy to find the broken 
packages, though they would still need to be fixed.

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: rpmnew files

2009-10-20 Thread Tony Nelson 
On 09-10-20 17:49:28, nodata wrote:
> Hi,
> 
> What's with the extra rpmnew files on an upgrade?
> 
> Some examples:
> # md5sum  /etc/pki/tls/openssl.cnf.rpmnew /etc/pki/tls/openssl.cnf
> 7c8f8d809c5b618e1604207525161101  /etc/pki/tls/openssl.cnf.rpmnew
> 7c8f8d809c5b618e1604207525161101  /etc/pki/tls/openssl.cnf
 ...

Let me tell you about the `cmp` command.  In my case:

# cmp /etc/yum.repos.d/rpmfusion-free.repo*
# cmp /usr/lib/security/classpath.security*
/usr/lib/security/classpath.security /usr/lib/security/
classpath.security.rpmnew differ: byte 1874, line 39

:-)


> /var/lib/games/same-gnome.Small.scores.rpmnew
> /var/log/mail/statistics.rpmnew
> 
> Not sure why we would ever need an rpmnew file for that: should these
> be labelled as something other than config files?

Or perhaps not make .rpmnew files for empty config files.


> Another one:
> 
> # md5sum /usr/share/info/dir.rpmnew /usr/share/info/dir
> 91ba35a21c163a55982bedaab076bc7f  /usr/share/info/dir.rpmnew
> 0737290f14a0ce86986de276d1083783  /usr/share/info/dir
> # wc -l /usr/share/info/dir.rpmnew /usr/share/info/dir
> 22 /usr/share/info/dir.rpmnew
>   2127 /usr/share/info/dir
>   2149 total
> 
> I didn't change this file. That's weird. Same case here:
 ...

It's actually a sort of database for the info command.

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Fedora PPC for oldworld Mac?

2009-10-28 Thread Tony Nelson 
Sorry to bug developers, but I didn't get any bites from PPC users on 
fedora-list.

Does Fedora PPC work or install on oldworld PCI Macs, such as a beige 
G3 desktop?  My impression is that no one has tried it on an oldworld 
Mac in the last few releases, and that getting it to boot at all would 
be an adventure.

(Otherwise I'm going to try Debian Lenny, which is said to work, but 
about which I know nothing.  The machine has 416 MB memory and I'll 
install a 40 GB hard disk for Linux, so other than speed it should be 
good to go.)

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Fedora PPC for oldworld Mac?

2009-10-28 Thread Tony Nelson 
On 09-10-28 18:24:49, Josh Boyer wrote:
> On Wed, Oct 28, 2009 at 06:17:31PM -0400, Tony Nelson wrote:
> >Sorry to bug developers, but I didn't get any bites from PPC
> >users on fedora-list.
> >
> >Does Fedora PPC work or install on oldworld PCI Macs, such as
> >a beige G3 desktop?  My impression is that no one has tried it
> >on an oldworld
> 
> 
> No, it doesn't.  The ppc specific release notes cover that here:
> 
> http://docs.fedoraproject.org/release-notes/f11/en-US/
> index.html#sect-Release_Notes-Hardware_Requirements

I'd looked at the release notes.  They says "Minimum CPU: PowerPC 
G3..." and "Although Old World machines should work, they require a 
special bootloader which is not included in the Fedora distribution."  
My question is whether anyone has tried it in any recent Fedora
release and knows whether "should" means "do" or "don't".

(FWIW, the special bootloader is BootX, and Debian Lenny is installing 
now, so /some/ form of Linux works.  I just don't know anything but 
hearsay about Debian.  I see it uses "apt".)

-- 

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Fedora PPC for oldworld Mac?

2009-10-29 Thread Tony Nelson 
On 09-10-29 08:18:30, David Woodhouse wrote:
> On Wed, 2009-10-28 at 22:25 -0400, Tony Nelson wrote:
> > On 09-10-28 18:24:49, Josh Boyer wrote:
> > > On Wed, Oct 28, 2009 at 06:17:31PM -0400, Tony Nelson wrote:
> > > >Sorry to bug developers, but I didn't get any bites from PPC
> > > >users on fedora-list.
> > > >
> > > >Does Fedora PPC work or install on oldworld PCI Macs, such as
> > > >a beige G3 desktop?  My impression is that no one has tried it
> > > >on an oldworld
> > > 
> > > 
> > > No, it doesn't.  The ppc specific release notes cover that here:
> > > 
> > > http://docs.fedoraproject.org/release-notes/f11/en-US/
> > > index.html#sect-Release_Notes-Hardware_Requirements
> > 
> > I'd looked at the release notes.  They says "Minimum CPU: PowerPC 
> > G3..." and "Although Old World machines should work, they require a 
> > special bootloader which is not included in the Fedora
> > distribution."  My question is whether anyone has tried it in any 
> > recent Fedora release and knows whether "should" means "do" or 
> > "don't".
> > 
> > (FWIW, the special bootloader is BootX, and Debian Lenny is 
> > installing now, so /some/ form of Linux works.  I just don't know  
> > anything but hearsay about Debian.  I see it uses "apt".)
> 
> I don't know of anyone who's tried it recently, but in the past we've
> fixed things in the kernel to make it work properly on OldWorld Macs
> and it _has_ been known to work fine.

I received a reply off-list from someone who did sucessfully install 
F11 on an oldworld Mac.


> It _ought_ to work if you sort out the bootloader.

I was able to get a Debian Lenny install working (after sorting out the 
bootloader :-), so I am encouraged.

-- 

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Fedora PPC for oldworld Mac?

2009-10-29 Thread Tony Nelson 
On 09-10-29 16:41:57, King InuYasha wrote:
> On Thu, Oct 29, 2009 at 7:18 AM, David Woodhouse
> wrote:
> 
> > On Wed, 2009-10-28 at 22:25 -0400, Tony Nelson wrote:
> > > On 09-10-28 18:24:49, Josh Boyer wrote:
> > > > On Wed, Oct 28, 2009 at 06:17:31PM -0400, Tony Nelson wrote:
> > > > >Sorry to bug developers, but I didn't get any bites from PPC
> > > > >users on fedora-list.
> > > > >
> > > > >Does Fedora PPC work or install on oldworld PCI Macs, such as
> > > > >a beige G3 desktop?  My impression is that no one has tried it
> > > > >on an oldworld
> > > >
> > > >
> > > > No, it doesn't.  The ppc specific release notes cover that 
> > > > here:
> > > >
> > > > http://docs.fedoraproject.org/release-notes/f11/en-US/
> > > > index.html#sect-Release_Notes-Hardware_Requirements
> > >
> > > I'd looked at the release notes.  They says "Minimum CPU: PowerPC
> > > G3..." and "Although Old World machines should work, they require
> > > a special bootloader which is not included in the Fedora
> > > distribution."  My question is whether anyone has tried it in any 
> > > recent Fedora release and knows whether "should" means "do" or 
> > > "don't".
> > >
> > > (FWIW, the special bootloader is BootX, and Debian Lenny is
> > > installing now, so /some/ form of Linux works.  I just don't know 
> > > anything but hearsay about Debian.  I see it uses "apt".)
> >
> > I don't know of anyone who's tried it recently, but in the past
> > we've fixed things in the kernel to make it work properly on 
> > OldWorld Macs and it _has_ been known to work fine.
> >
> If Mac OS isn't bootable, then you need to use quik (
> http://penguinppc.org/bootloaders/quik/ ) instead of BootX.

I don't think that would help fix the unbootable MacOS, but in any
case quik doesn't work if Linux is installed on a drive not the boot 
drive, as it is here.

-- 

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Fedora PPC for oldworld Mac?

2009-11-02 Thread Tony Nelson 
On 09-11-02 13:07:09, Dan Williams wrote:

> oldworld topped out at 366MHz anyway right?  (the 333 and 366 Beige 
> G3 were only sold from 1998-08-12 -> 1999-01-01 too)  That's pretty 
> much the minimum you'd need to run Fedora anyway these days...  Not 
> sure it's really worth it, you'll need at least 256MB of RAM anyway, 
> and those things used 168-pin 3.3V DIMMs which are pretty hard to 
> find these days.

FWIW, my machine, a beige G3, is 233 MHz and has accumulated 416 MiB 
over the years.  It handles Debian Lenny Iceweasel OK, but then, my 
main computer is a 1.2 GHz Athlon.


> The Blue & White G3 was the first New World machine I think.

Yes.


> Remember too that you'll need your boot partition within the first 
> 8GB of the drive as the firmware can't handle booting from a 
> partition which ends anywhere past that.

I'm using BootX, so it's not an issue.  (Fiddling with buggy 
openfirmware seems like something to avoid, anyway.)

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Roopesh's Birthday Calendar

2009-11-13 Thread Tony Nelson 
On 09-11-13 16:13:20, Ikem Krueger wrote:
> > Please click on the link below and enter your birthday for me.  I 
> am creating a birthday calendar for myself.  Don't worry, it'll take 
> less than a minute (and you don't have to enter your year of birth).
> 
> Spam? o.O

Phishing.

-- 

TonyN.:'   
  '  


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Local users get to play root?

2009-11-18 Thread Tony Nelson 
On 09-11-18 13:44:43, nodata wrote:
> Am 2009-11-18 19:16, schrieb Bruno Wolff III:
> > On Wed, Nov 18, 2009 at 17:45:26 +,
> >Bastien Nocera  wrote:
> >>
> >> Once we get the new user management stuff into F13 [1], we'd
> >> probably tighten that rule so that only admins are given the 
> >> option, or all users but with the need to authenticate as an 
> >> admin.
> >
> > This seems pretty reasonable.
> 
> I don't like the way Fedora is going with this: digging out something 
> that works and saying "we'll replace it later" makes no sense. Make 
> it work now, or *keep it in*.

Fedora has always been this way.  Have you tried to use sound or video 
in the past few releases?  I think it's called "creative destruction".

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Local users get to play root?

2009-11-18 Thread Tony Nelson 
On 09-11-18 20:09:18, Bastien Nocera wrote:
> On Wed, 2009-11-18 at 13:50 -0500, Tony Nelson wrote:
 ..
> > Fedora has always been this way.  Have you tried to use sound or
> > video in the past few releases?  I think it's called "creative
> > destruction".
> 
> And I'm sure the passive-aggressive in you filed bugs.

Yes, I did.  Might not have been the passive-aggressive in me, though.  
Don't be smarmy.

-- 

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Local users get to play root?

2009-11-19 Thread Tony Nelson 
On 09-11-19 05:06:16, Bastien Nocera wrote:
> On Thu, 2009-11-19 at 01:48 -0500, Tony Nelson wrote:
> > On 09-11-18 20:09:18, Bastien Nocera wrote:
> > > On Wed, 2009-11-18 at 13:50 -0500, Tony Nelson wrote:
> >  ..
> > > > Fedora has always been this way.  Have you tried to use sound 
> > > > or video in the past few releases?  I think it's called 
> > > > "creative destruction".
> > > 
> > > And I'm sure the passive-aggressive in you filed bugs.
> > 
> > Yes, I did.  Might not have been the passive-aggressive in me,
> > though.  Don't be smarmy.
> 
> I'm not being smarmy. You just insulted my work, and the work of many
> other people. I think I'm entitled to an explanation, don't you?

No.  If you don't know what Fedora is all about, read the mailing list, 
even this thread.  If you still feel insulted, /grow up/, it's time for 
you to be a big boy now.

-- 

TonyN.:'   <mailto:tonynel...@georgeanelson.com>
  '  <http://www.georgeanelson.com/>

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: abrt and bugzilla

2009-11-20 Thread Tony Nelson 
On 09-11-20 07:06:34, Jiri Moskovcak wrote:
> On 11/20/2009 12:24 PM, Matthew Booth wrote:
 ...
> > 5. Can abrt give me a list of submitted BZs so I can browse them if
> > I want to?
> 
> This is in our TODO: ABRT should find possible duplicates and offer
> the reporter to browse them and manually mark them as a duplicate.
 ...

Like Debian's reportbug command?  It's probably worth a look.

-- 

TonyN.:'   
  '  


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Improve the way rpm decides what is newer

2009-11-21 Thread Tony Nelson 
On 09-11-21 06:40:45, drago01 wrote:
 ...
> You misunderstood me, I was not suggesting adding another epoch but
> simply bump the %{epoch}  for every release.

If this were really important to do, just putting the release first in 
the version would take care of it without dragging in Epochs.

Epoch is the big hammer, and is troublesome to use in practice.

-- 

TonyN.:'   
  '  


-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: acctcom for linux

2009-12-16 Thread Tony Nelson 
On 09-12-16 18:19:17, Jesse Keating wrote:
> On Tue, 2007-05-01 at 08:38 -0400, William W. Austin wrote:
> > 05/01/2007 05:38:26 AM (Tue, 01 May 2007 08:38:26 -0400)
> 
> Your date is still wrong.

No, the date is correct.  That's when the message was sent the first 
time around -- it's in the list archives.

I don't think he reads the list anymore.  I don't think he's aware that 
this is happening, so I've CC'd him.

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: Koji stuck?

2009-12-19 Thread Tony Nelson 
On 09-12-19 17:19:37, Orcan Ogetbil wrote:
 ...
> There is a -O2 flag issue that causes some builds to hang. Maybe 
> those emacs hangs are related to this bug in gcc
> It happened to 2 of my packages. Removing -O2 makes things compile in
> my packages. (No I didn't do official builds without -O2 flag)
> 
> Someone filed a bug about this a while ago but unfortunately gcc
> maintainers don't seem to care much. Anything we can do about this?
> Can we use -O1 instead? The fact is these packages will not compile 
> if there will be a mass rebuild. And this needs to be fixed at some 
> point before F-13 is out.

`man gcc` suggests that one can find out the differences between -On 
levels with:

$ gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts
$ gcc -c -Q -O1 --help=optimizers > /tmp/O1-opts
$ diff /tmp/O{1,2}-opts | grep enabled

(and the man page also lists differences).

Perhaps only one of the added optimizations is the problem and 
disabling that one will fix it.  A bug report about that particular 
optimization on a particular file might get better results.  I suppose 
I'd disable half of the added optimizations at a time on a problem file 
until I found the one that causes the hangs.

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: End of days?

2010-01-06 Thread Tony Nelson 
On 10-01-06 17:54:10, Robert Relyea wrote:
> On 01/06/2010 01:43 PM, Orion Poplawski wrote:
> > [or...@orca fedora/devel]$ ls */dead.package | wc -l
> > 666
> >
> We're ok. The original number may have been 616:
> http://www.csad.ox.ac.uk/POxy/beast616.htm

No, that's merely the most common "correction" by those with a little 
knowledge.  666 was the number for Neron Ceaser, while 616 was for Nero 
Ceaser (latinized form of name).  Of course, the reference was actually 
to Domitian, who was Emperor when the Temple in Jerusalem was destroyed 
(again) after yet another revolt by the Jews.  Mentioning the current 
Emperor in an unflattering way would get one killed, hence the code.

-- 

TonyN.:'   
  '  

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list