Fedora Packaging

• Thread Index

• Confused by non-numeric version in release guideline
  • From: Richard W.M. Jones
• max. rpm file name length
  • From: Ralf Corsepius
• how to make use of bug-buddy bugreport files ?
  • From: Gregory Hosler
• Re: Re: Package ownership of local state files (/var/lib)?
  • From: Jonathan Underwood
• Re: Package ownership of local state files (/var/lib)?
  • From: Enrico Scholz
• Re: meta-package guideline needed ?
  • From: Rex Dieter
• easing external software installation - discussion
  • From: David Timms
• Re: meta-package guideline needed ?
  • From: seth vidal
• Re: meta-package guideline needed ?
  • From: David Timms
• Re: meta-package guideline needed ?
  • From: Itamar Reis Peixoto
• Re: meta-package guideline needed ?
  • From: Nicolas Mailhot
• Re: meta-package guideline needed ?
  • From: Jonathan Underwood
• Re: meta-package guideline needed ?
  • From: Nicolas Mailhot
• Re: meta-package guideline needed ?
  • From: Nicolas Mailhot
• Re: meta-package guideline needed ?
  • From: Jonathan Underwood
• Re: meta-package guideline needed ?
  • From: David Timms
• Re: meta-package guideline needed ?
  • From: Patrice Dumas
• meta-package guideline needed ?
  • From: David Timms
• Re: Package ownership of local state files (/var/lib)?
  • From: Ralf Corsepius
• Package ownership of local state files (/var/lib)?
  • From: Jonathan Underwood
• Re: New font packaging guidelines
  • From: Nicolas Mailhot
• Re: Update guidelines for using darcs based sources in packages
  • From: Yaakov Nemoy
• Re: Update guidelines for using darcs based sources in packages
  • From: Till Maas
• Re: Update guidelines for using darcs based sources in packages
  • From: Yaakov Nemoy
• Re: Update guidelines for using darcs based sources in packages
  • From: Toshio Kuratomi
• Update guidelines for using darcs based sources in packages
  • From: Yaakov Nemoy
• Re: Summary of the 2009-01-06 Packaging Committee meeting
  • From: Enrico Scholz
• Re: Re: Summary of the 2009-01-06 Packaging Committee meeting
  • From: Jeremy Katz
• Re: Re: Summary of the 2009-01-06 Packaging Committee meeting
  • From: Paul Howarth
• Re: Summary of the 2009-01-06 Packaging Committee meeting
  • From: Jeremy Katz
• Re: Won't be making the FPC meeting tonight
  • From: Dominik 'Rathann' Mierzejewski
• Won't be making the FPC meeting tonight
  • From: Hans de Goede
• Res: How to create a .spec file for a software that user cmake?
  • From: Henrique Junior
• Re: How to create a .spec file for a software that user cmake?
  • From: Toshio Kuratomi
• How to create a .spec file for a software that user cmake?
  • From: Henrique Junior
• Re: Re: fontpackages template warnings
  • From: Ville Skyttä
• Re: Re: fontpackages template warnings
  • From: Nicolas Mailhot
• Re: Re: fontpackages template warnings
  • From: Nicolas Mailhot
• Re: Re: fontpackages template warnings
  • From: Ville Skyttä
• Re: Re: fontpackages template warnings
  • From: Sarantis Paskalis
• Re: fontpackages template warnings
  • From: Nicolas Mailhot
• Problems accessing Koji website.
  • From: Henrique Junior
• Re: Missing links in Packaging:Debuginfo
  • From: Tom "spot" Callaway
• Missing links in Packaging:Debuginfo
  • From: Ville Skyttä
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Mamoru Tasaka
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Patrice Dumas
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Till Maas
• Font package splitting clarification
  • From: Nicolas Mailhot
• Font package naming guidelines
  • From: Nicolas Mailhot
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Patrice Dumas
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Jesse Keating
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Jason L Tibbitts III
• Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Axel Thimm
• Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Karsten Hopp
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Ralf Corsepius
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Ralf Corsepius
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Jesse Keating
• Re: Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Tom "spot" Callaway
• Re: Usage of {_libdir} or {_lib} in noarch packages
  • From: Ralf Corsepius
• Usage of {_libdir} or {_lib} in noarch packages
  • From: Karsten Hopp
• Re: Ownership of /usr/share/gnome/help
  • From: Patrice Dumas
• Re: Ownership of /usr/share/gnome/help
  • From: Toshio Kuratomi
• Re: Ownership of /usr/share/gnome/help
  • From: Patrice Dumas
• Re: Ownership of /usr/share/gnome/help
  • From: Toshio Kuratomi
• Re: Ownership of /usr/share/gnome/help
  • From: Toshio Kuratomi
• Re: Ownership of /usr/share/gnome/help
  • From: Jason L Tibbitts III
• Re: Ownership of /usr/share/gnome/help
  • From: Matthias Clasen
• Re: Ownership of /usr/share/gnome/help
  • From: Toshio Kuratomi
• Re: Ownership of /usr/share/gnome/help
  • From: Jason L Tibbitts III
• Re: Ownership of /usr/share/gnome/help
  • From: Jason L Tibbitts III
• Re: Ownership of /usr/share/gnome/help
  • From: Toshio Kuratomi
• Ownership of /usr/share/gnome/help
  • From: Jason L Tibbitts III
• Re: "ratify"
  • From: Toshio Kuratomi
• Re: "ratify"
  • From: Jason L Tibbitts III
• Re: guidelines for dbus services
  • From: Toshio Kuratomi
• Re: "ratify"
  • From: Toshio Kuratomi
• "ratify"
  • From: Andrew Overholt
• Re: Including a patched version of an upstream library -- advice?
  • From: Tom "spot" Callaway
• Including a patched version of an upstream library -- advice?
  • From: Mary Ellen Foster
• Re: Group tag for Java libraries and their documentation
  • From: Tom "spot" Callaway
• Re: Group tag for Java libraries and their documentation
  • From: Patrice Dumas
• Re: Group tag for Java libraries and their documentation
  • From: Mary Ellen Foster
• Re: Group tag for Java libraries and their documentation
  • From: Patrice Dumas
• Group tag for Java libraries and their documentation
  • From: Mary Ellen Foster
• guidelines for dbus services
  • From: Matthias Clasen
• adding INSTALL="install -p" to %configure
  • From: Till Maas
• Re: MinGW subpackages of OCaml packages
  • From: Richard W.M. Jones
• Re: MinGW subpackages of OCaml packages
  • From: Toshio Kuratomi
• Re: MinGW subpackages of OCaml packages
  • From: Richard W.M. Jones
• Re: MinGW subpackages of OCaml packages
  • From: Jason L Tibbitts III
• Re: MinGW subpackages of OCaml packages
  • From: Ralf Corsepius
• Re: MinGW subpackages of OCaml packages
  • From: Richard W.M. Jones
• Re: MinGW subpackages of OCaml packages
  • From: Ralf Corsepius
• Re: MinGW subpackages of OCaml packages
  • From: Ralf Corsepius
• Re: MinGW subpackages of OCaml packages
  • From: Toshio Kuratomi
• Re: MinGW subpackages of OCaml packages
  • From: Richard W.M. Jones
• Re: Updates to Eclipse Plugin packaging guidelines
  • From: Jason L Tibbitts III
• Re: Updates to Eclipse Plugin packaging guidelines
  • From: Andrew Overholt
• Re: Updates to Eclipse Plugin packaging guidelines
  • From: Mary Ellen Foster
• Task work needed
  • From: Jesse Keating
• Re: Error when building: gimptool-2.0: Permission denied
  • From: Fabian Deutsch
• Error when building: gimptool-2.0: Permission denied
  • From: Fabian Deutsch
• Re: Problems with the .info file
  • From: Jason L Tibbitts III
• Problems with the .info file
  • From: Fabian Affolter
• MinGW subpackages of OCaml packages
  • From: Richard W.M. Jones
• Re: LGPLv2.1 vs. LGPLv2
  • From: Tom "spot" Callaway
• Re: Packaging Javadocs for subpackages
  • From: Dominik 'Rathann' Mierzejewski
• Packaging Javadocs for subpackages
  • From: Brennan Ashton
• LGPLv2.1 vs. LGPLv2
  • From: Chuck Anderson
• Re: underscore in tryton modules
  • From: Ignacio Vazquez-Abrams
• Re: underscore in tryton modules
  • From: Tom "spot" Callaway
• Re: underscore in tryton modules
  • From: Dan Horák
• Re: underscore in tryton modules
  • From: Tom "spot" Callaway
• underscore in tryton modules
  • From: Dan Horák
• Re: rubygem with extension written in C
  • From: Mamoru Tasaka
• New Fedora fonts packaging guidelines
  • From: Nicolas Mailhot
• Re: rubygem with extension written in C
  • From: Tom "spot" Callaway
• Re: f11 build error
  • From: Paul Howarth
• Re: f11 build error
  • From: Gregory Hosler
• Re: f11 build error
  • From: Bill Nottingham
• f11 build error
  • From: Gregory Hosler
• Re: Questions about dependencies in rpm packages
  • From: Ignacio Vazquez-Abrams
• Questions about dependencies in rpm packages
  • From: Olivier Bourdon
• Re: BuildRequires: /lib/ld-linux.so.2 + mock
  • From: Jussi Lehtola
• Re: *.h files in a directory under %{_libdir}?
  • From: Daniel P. Berrange
• Re: *.h files in a directory under %{_libdir}?
  • From: Ralf Corsepius
• Re: *.h files in a directory under %{_libdir}?
  • From: Richard W.M. Jones
• Re: BuildRequires: /lib/ld-linux.so.2 + mock
  • From: Ignacio Vazquez-Abrams
• Re: BuildRequires: /lib/ld-linux.so.2 + mock
  • From: Jussi Lehtola
• Re: BuildRequires: /lib/ld-linux.so.2 + mock
  • From: Ignacio Vazquez-Abrams
• BuildRequires: /lib/ld-linux.so.2 + mock
  • From: Jussi Lehtola
• Re: Vim compile options in Fedora
  • From: Patrice Dumas
• Vim compile options in Fedora
  • From: Timandahaf
• Re: patching datafile locations for upstream projects ?
  • From: Patrice Dumas
• patching datafile locations for upstream projects ?
  • From: Jani Mikkonen
• Re: *.h files in a directory under %{_libdir}?
  • From: Ralf Corsepius
• Re: *.h files in a directory under %{_libdir}?
  • From: Mamoru Tasaka
• *.h files in a directory under %{_libdir}?
  • From: Mary Ellen Foster
• Hi all!
  • From: Uwe Kubosch
• Re: rubygem with extension written in C
  • From: Mamoru Tasaka
• Re: Packaging rubygem-passenger and "mod_rails"
  • From: Mamoru Tasaka
• Re: Packaging rubygem-passenger and "mod_rails"
  • From: Jeroen van Meeuwen
• Re: Packaging rubygem-passenger and "mod_rails"
  • From: Mamoru Tasaka
• Re: Packaging rubygem-passenger and "mod_rails"
  • From: Mamoru Tasaka
• Packaging rubygem-passenger and "mod_rails"
  • From: Jeroen van Meeuwen
• Re: rubygem with extension written in C
  • From: Mamoru Tasaka
• Re: rubygem with extension written in C
  • From: David Lutterkort
• Re: rubygem with extension written in C
  • From: Mamoru Tasaka
• Re: rubygem with extension written in C
  • From: David Lutterkort
• Re: rubygem with extension written in C
  • From: Mamoru Tasaka
• Re: rubygem with extension written in C
  • From: David Lutterkort
• rubygem with extension written in C
  • From: Mamoru Tasaka
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Thorsten Leemhuis
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Jason L Tibbitts III
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Jason L Tibbitts III
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Nicolas Mailhot
• Re: README.Dist is preferrable to README.Fedora
  • From: Ralf Corsepius
• Re: README.Dist is preferrable to README.Fedora
  • From: Ralf Corsepius
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Dominik 'Rathann' Mierzejewski
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Richard W.M. Jones
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Jason L Tibbitts III
• Re: README.Dist is preferrable to README.Fedora
  • From: Ralf Corsepius
• Re: README.Dist is preferrable to README.Fedora
  • From: Ville Skyttä
• Re: README.Dist is preferrable to README.Fedora
  • From: Mamoru Tasaka
• Re: README.Dist is preferrable to README.Fedora
  • From: Paul Howarth
• Re: README.Dist is preferrable to README.Fedora
  • From: Thorsten Leemhuis
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Jussi Lehtola
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• Re: README.Dist is preferrable to README.Fedora
  • From: Mamoru Tasaka
• Re: README.Dist is preferrable to README.Fedora
  • From: Dominik 'Rathann' Mierzejewski
• README.Dist is preferrable to README.Fedora
  • From: Patrice Dumas
• BR exception could be simplified
  • From: Patrice Dumas
• Re: package without .elc files and emacs guidelines
  • From: Jonathan Underwood
• Re: package without .elc files and emacs guidelines
  • From: Ville Skyttä
• Re: package without .elc files and emacs guidelines
  • From: Jonathan Underwood
• Re: Updates to Eclipse Plugin packaging guidelines
  • From: Denis Leroy
• Re: Moonlight support within MonoDevelop
  • From: Tom "spot" Callaway
• Moonlight support within MonoDevelop
  • From: Paul
• Re: Re: PackagingDrafts/AutoConf
  • From: Till Maas
• package without .elc files and emacs guidelines
  • From: Patrice Dumas
• Re: Updates to Eclipse Plugin packaging guidelines
  • From: Jason L Tibbitts III
• Re: Updates to Eclipse Plugin packaging guidelines
  • From: Tom "spot" Callaway
• Updates to Eclipse Plugin packaging guidelines
  • From: Andrew Overholt
• Re: PackagingDrafts/AutoConf
  • From: Braden McDaniel
• Re: Fontconfig rules installation guidelines change proposal
  • From: Nicolas Mailhot
• Re: Re: PackagingDrafts/AutoConf
  • From: Braden McDaniel
• Re: Fontconfig rules installation guidelines change proposal
  • From: Nicolas Mailhot
• Re: Re: PackagingDrafts/AutoConf
  • From: Ralf Corsepius
• Re: PackagingDrafts/AutoConf
  • From: Enrico Scholz
• Re: Re: PackagingDrafts/AutoConf
  • From: Ralf Corsepius
• Re: PackagingDrafts/AutoConf
  • From: Till Maas
• Re: Re: PackagingDrafts/AutoConf
  • From: Braden McDaniel
• Re: PackagingDrafts/AutoConf
  • From: Patrice Dumas
• Re: PackagingDrafts/AutoConf
  • From: Enrico Scholz
• Re: PackagingDrafts/AutoConf
  • From: Ralf Corsepius
• Re: PackagingDrafts/AutoConf
  • From: Braden McDaniel
• Re: PackagingDrafts/AutoConf
  • From: Ralf Corsepius
• Re: PackagingDrafts/AutoConf
  • From: Braden McDaniel
• Re: PackagingDrafts/AutoConf
  • From: Toshio Kuratomi
• Re: PackagingDrafts/AutoConf
  • From: Tom "spot" Callaway
• Re: libgdiplus-devel subpackage
  • From: Ralf Corsepius
• Re: libgdiplus-devel subpackage
  • From: Sergio Pascual
• libgdiplus-devel subpackage
  • From: Paul
• Fontconfig rules installation guidelines change proposal
  • From: Nicolas Mailhot
• Re: Re: rakarrack - alternative desktop categories
  • From: David Timms
• PackagingDrafts/AutoConf
  • From: Braden McDaniel
• Re: Re: rakarrack - alternative desktop categories
  • From: Matthias Clasen
• Re: Re: rakarrack - alternative desktop categories
  • From: David Timms
• Re: Re: Packaging emacs modes: EL/F compatibility
  • From: Toshio Kuratomi
• Re: Re: Packaging emacs modes: EL/F compatibility
  • From: Michel Salim
• Re: Re: Packaging emacs modes: EL/F compatibility
  • From: Patrice Dumas
• Re: Re: Packaging emacs modes: EL/F compatibility
  • From: Stephen John Smoogen
• Re: Re: Packaging emacs modes: EL/F compatibility
  • From: Michel Salim
• Re: app-local feature libraries, plugins
  • From: Matt Domsch
• Re: app-local feature libraries, plugins
  • From: John Dennis
• Re: app-local feature libraries, plugins
  • From: Jeffrey Ollie
• Re: Re: Packaging emacs modes: EL/F compatibility
  • From: Ville Skyttä
• app-local feature libraries, plugins
  • From: Matt Domsch
• Re: Packaging emacs modes: EL/F compatibility
  • From: Michel Salim
• Re: how to include rpm-specific files in the spec
  • From: Jarod Wilson
• Re: how to include rpm-specific files in the spec
  • From: Jarod Wilson
• Re: how to include rpm-specific files in the spec
  • From: Hubert Plociniczak
• Re: how to include rpm-specific files in the spec
  • From: Rex Dieter
• Packaging emacs modes: EL/F compatibility
  • From: Michel Salim
• how to include rpm-specific files in the spec
  • From: Hubert Plociniczak
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ralf Corsepius
• Re:Re: how to update the unifdef without network when compiling kernel src for x86_64 arch
  • From: xkdcc
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: how to update the unifdef without network when compiling kernel src for x86_64 arch
  • From: Paul Howarth
• how to update the unifdef without network when compiling kernel src for x86_64 arch
  • From: xkdcc
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ralf Corsepius
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Debarshi Ray
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ralf Corsepius
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ralf Corsepius
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jens Petersen
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Dominik 'Rathann' Mierzejewski
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Toshio Kuratomi
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ed Hill
• Re: The role of %{_libexecdir} for using environment-modules
  • From: dominik
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Dominik 'Rathann' Mierzejewski
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Rex Dieter
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Toshio Kuratomi
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Toshio Kuratomi
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Rex Dieter
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ed Hill
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Denis Leroy
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Rex Dieter
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Dominik 'Rathann' Mierzejewski
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ed Hill
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Denis Leroy
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ralf Corsepius
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jason L Tibbitts III
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Patrice Dumas
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Denis Leroy
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jens Petersen
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Ed Hill
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Jens Petersen
• Re: The role of %{_libexecdir} for using environment-modules
  • From: Tom "spot" Callaway
• The role of %{_libexecdir} for using environment-modules
  • From: Jussi Lehtola
• Re: package review template
  • From: Toshio Kuratomi
• Re: looking for a sponsor and review ;)
  • From: Luca Foppiano
• Re: looking for a sponsor and review ;)
  • From: Rex Dieter
• Re: package review template
  • From: Jason L Tibbitts III
• Re: package review template
  • From: Richard W.M. Jones
• looking for a sponsor and review ;)
  • From: Luca Foppiano
• Re: package review template
  • From: Jens Petersen
• Re: time for a review-oh-matic?
  • From: Jens Petersen
• Re: package review template
  • From: Patrice Dumas
• Re: package review template
  • From: Till Maas
• Re: time for a review-oh-matic?
  • From: Chris Weyl
• Re: package review template
  • From: Ralf Corsepius
• Re: time for a review-oh-matic?
  • From: Daniel P. Berrange
• Re: package review template
  • From: Ralf Corsepius
• Re: time for a review-oh-matic?
  • From: Patrice Dumas
• time for a review-oh-matic?
  • From: Chris Weyl
• Re: package review template
  • From: Patrice Dumas
• Re: package review template
  • From: Patrice Dumas
• Re: package review template
  • From: Daniel P. Berrange
• Re: package review template
  • From: Jon Ciesla
• Re: package review template
  • From: Patrice Dumas
• Re: package review template
  • From: Dominik 'Rathann' Mierzejewski
• Re: package review template
  • From: Ralf Corsepius
• Re: package review template
  • From: Till Maas
• Re: package review template
  • From: Patrice Dumas
• Re: package review template
  • From: Ralf Corsepius
• Re: package review template
  • From: Till Maas
• Re: package review template
  • From: Patrice Dumas
• Re: package review template
  • From: Till Maas
• Re: package review template
  • From: Ralf Corsepius
• package review template
  • From: Jens Petersen
• Re: Procedure for renaming a package?
  • From: Ville Skyttä
• Re: Broken links to initscript guidelines on Packaging/ScriptletSnippets
  • From: Tom "spot" Callaway
• Broken links to initscript guidelines on Packaging/ScriptletSnippets
  • From: Todd Zullinger
• Re: Procedure for renaming a package?
  • From: Tom "spot" Callaway
• Re: Procedure for renaming a package?
  • From: Debarshi Ray
• Procedure for renaming a package?
  • From: Timothy Selivanow
• Re: Question about how libgcj-devel requires zlib
  • From: Paul Howarth
• Re: Question about how libgcj-devel requires zlib
  • From: Denis Leroy
• Re: Request : removal of gtk-sharp
  • From: Toshio Kuratomi
• Request : removal of gtk-sharp
  • From: Paul
• Re: Please do not redefine %_bindir
  • From: Ralf Corsepius
• Re: Please do not redefine %_bindir
  • From: Tom "spot" Callaway
• Please do not redefine %_bindir
  • From: Michael A. Peters
• Broken URL in review process page
  • From: Debarshi Ray
• Re: Question about how libgcj-devel requires zlib
  • From: Rex Dieter
• Re: Question about how libgcj-devel requires zlib
  • From: Bruno Wolff III
• Re: Next FPC?
  • From: Hans de Goede
• Re: Question about how libgcj-devel requires zlib
  • From: Panu Matilainen
• Next FPC?
  • From: Richard W.M. Jones
• Re: Question about how libgcj-devel requires zlib
  • From: Ralf Corsepius
• Re: Question about how libgcj-devel requires zlib
  • From: Nicolas Mailhot
• Re: Question about how libgcj-devel requires zlib
  • From: Panu Matilainen
• Re: Question about how libgcj-devel requires zlib
  • From: Ralf Corsepius
• Re: Question about how libgcj-devel requires zlib
  • From: Panu Matilainen
• Re: Question about how libgcj-devel requires zlib
  • From: Ralf Corsepius
• Re: Question about how libgcj-devel requires zlib
  • From: Panu Matilainen
• Re: Question about how libgcj-devel requires zlib
  • From: Panu Matilainen
• Re: Question about how libgcj-devel requires zlib
  • From: Bruno Wolff III
• Re: Question about how libgcj-devel requires zlib
  • From: Bruno Wolff III
• Re: Question about how libgcj-devel requires zlib
  • From: seth vidal
• Re: Question about how libgcj-devel requires zlib
  • From: seth vidal
• Re: Question about how libgcj-devel requires zlib
  • From: Tom "spot" Callaway
• Re: Question about how libgcj-devel requires zlib
  • From: seth vidal
• Re: Question about how libgcj-devel requires zlib
  • From: Bruno Wolff III
• Re: Question about how libgcj-devel requires zlib
  • From: seth vidal
• Question about how libgcj-devel requires zlib
  • From: Bruno Wolff III
• Re: %doc and %attr problems
  • From: Dominik 'Rathann' Mierzejewski
• Re: %doc and %attr problems
  • From: Paul Howarth
• %doc and %attr problems
  • From: François Kooman
• Re: Re: OpenSuse / Fedora Packaging Compatibility?
  • From: Seth Vidal
• Re: OpenSuse / Fedora Packaging Compatibility?
  • From: Nicolas Mailhot
• Re: OpenSuse / Fedora Packaging Compatibility?
  • From: Axel Thimm
• Re: OpenSuse / Fedora Packaging Compatibility?
  • From: Roland Wolters
• OpenSuse / Fedora Packaging Compatibility?
  • From: Ken Sedgwick
• Re: Re: Use of Internal Libraries
  • From: Toshio Kuratomi
• Re: Re: Use of Internal Libraries
  • From: Dominik 'Rathann' Mierzejewski
• Re: Re: Use of Internal Libraries
  • From: Dominik 'Rathann' Mierzejewski
• Re: Use of Internal Libraries
  • From: Axel Thimm
• Re: Use of Internal Libraries
  • From: Axel Thimm
• Re: Use of Internal Libraries
  • From: Axel Thimm
• Re: Re: Use of Internal Libraries
  • From: Toshio Kuratomi
• Re: Re: Use of Internal Libraries
  • From: Dominik 'Rathann' Mierzejewski
• Re: Re: Use of Internal Libraries
  • From: Dominik 'Rathann' Mierzejewski
• Re: Use of Internal Libraries
  • From: Axel Thimm
• Re: Use of Internal Libraries
  • From: Axel Thimm
• Re: Use of Internal Libraries
  • From: Axel Thimm
• Re: Re: Use of Internal Libraries
  • From: Dominik 'Rathann' Mierzejewski
• Re: Re: Use of Internal Libraries
  • From: Dominik 'Rathann' Mierzejewski
• Re: Re: Use of Internal Libraries
  • From: Ralf Corsepius
• Re: Use of Internal Libraries
  • From: Axel Thimm
• Re: Re: Group tag in spec files
  • From: Panu Matilainen
• Re: Use of Internal Libraries
  • From: Toshio Kuratomi
• Re: Use of Internal Libraries
  • From: Nigel Jones
• Re: Use of Internal Libraries
  • From: Toshio Kuratomi
• Re: Use of Internal Libraries
  • From: Paul
• Use of Internal Libraries
  • From: Nigel Jones
• Re: Are there *any* guidelines for what "Group:" an application should go in?
  • From: Patrice Dumas
• Re: rpmlint non-standard-[ug]id, non-standard-dir-perm
  • From: Ville Skyttä
• Re: rpmlint non-standard-[ug]id, non-standard-dir-perm
  • From: Tom "spot" Callaway
• rpmlint non-standard-[ug]id, non-standard-dir-perm
  • From: Chuck Anderson
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Paul Howarth
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Tom "spot" Callaway
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Pavel Shevchuk
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Rex Dieter
• Re: Packaging mono - RFC
  • From: Toshio Kuratomi
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Pavel Shevchuk
• Re: Packaging mono - RFC
  • From: Tom "spot" Callaway
• Re: Re: Long and "advertising" descriptions
  • From: Patrice Dumas
• Re: Re: Long and "advertising" descriptions
  • From: Thorsten Leemhuis
• Re: Packaging mono - RFC
  • From: Paul Howarth
• Packaging mono - RFC
  • From: Paul
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Seth Vidal
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Tom "spot" Callaway
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Matthias Clasen
• Re: Re: Long and "advertising" descriptions
  • From: Ralf Corsepius
• Re: Re: Long and "advertising" descriptions
  • From: Patrice Dumas
• Re: Long and "advertising" descriptions
  • From: David A. Wheeler
• Re: Re: Long and "advertising" descriptions
  • From: Ralf Corsepius
• Re: Long and "advertising" descriptions
  • From: Thorsten Leemhuis
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: zing
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Dominik 'Rathann' Mierzejewski
• Re: Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Tom "spot" Callaway
• Long and "advertising" descriptions (was: Fedora 8 Update: enlightenment-0.16.999.043-3.fc8)
  • From: Thorsten Leemhuis
• Re: Re: Group tag in spec files
  • From: Ville Skyttä
• Re: Group tag in spec files
  • From: Axel Thimm
• Using newish rpm features in Fedora buildsys
  • From: Ville Skyttä
• Re: Re: Group tag in spec files
  • From: Ville Skyttä
• Re: Group tag in spec files
  • From: Axel Thimm
• Re: Group tag in spec files
  • From: Toshio Kuratomi
• Re: Group tag in spec files
  • From: Tom "spot" Callaway
• Group tag in spec files
  • From: Tim Jackson
• Re: combining code from GPLv2 and Artistic (Perl)
  • From: Tom "spot" Callaway
• combining code from GPLv2 and Artistic (Perl)
  • From: Chuck Anderson
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Nicolas Mailhot
• Re: How to handle unversioned upstream tarballs?
  • From: Jason L Tibbitts III
• Re: How to handle unversioned upstream tarballs?
  • From: Denis Leroy
• Re: How to handle unversioned upstream tarballs?
  • From: Patrice Dumas
• Re: How to handle unversioned upstream tarballs?
  • From: Jason L Tibbitts III
• Re: How to handle unversioned upstream tarballs?
  • From: Ignacio Vazquez-Abrams
• Re: How to handle unversioned upstream tarballs?
  • From: Jason L Tibbitts III
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Rajesh Krishnan
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Richard W.M. Jones
• Re: How to handle unversioned upstream tarballs?
  • From: Axel Thimm
• Re: How to handle unversioned upstream tarballs?
  • From: Ignacio Vazquez-Abrams
• Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Jens Petersen
• Re: Simple cvs extras suggestion
  • From: Jason L Tibbitts III
• Re: Simple cvs extras suggestion
  • From: Michel Salim
• Re: How to handle unversioned upstream tarballs?
  • From: Jason L Tibbitts III
• Re: How to handle unversioned upstream tarballs?
  • From: Philip Prindeville
• Re: How to handle unversioned upstream tarballs?
  • From: Jason L Tibbitts III
• How to handle unversioned upstream tarballs?
  • From: Philip Prindeville
• Re: Calling graphical tools generically e.g. text editor
  • From: Axel Thimm
• Re: Calling graphical tools generically e.g. text editor
  • From: Axel Thimm
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Rajesh Krishnan
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Yaakov Nemoy
• Re: Re: Calling graphical tools generically e.g. text editor
  • From: Tim Jackson
• Re: Calling graphical tools generically e.g. text editor
  • From: Tim Jackson
• Re: Re: Calling graphical tools generically e.g. text editor
  • From: Rex Dieter
• Re: Calling graphical tools generically e.g. text editor
  • From: Axel Thimm
• Re: Calling graphical tools generically e.g. text editor
  • From: Patrice Dumas
• Re: Calling graphical tools generically e.g. text editor
  • From: Rex Dieter
• Re: Calling graphical tools generically e.g. text editor
  • From: Patrice Dumas
• Re: Calling graphical tools generically e.g. text editor
  • From: Rex Dieter
• Calling graphical tools generically e.g. text editor
  • From: Tim Jackson
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Rajesh Krishnan
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Jens Petersen
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Tom "spot" Callaway
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Yaakov Nemoy
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Jens Petersen
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Jason L Tibbitts III
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Yaakov Nemoy
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Jens Petersen
• Re: Re: Game data packaging
  • From: Michel Salim
• Re: Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Jason L Tibbitts III
• Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Yaakov Nemoy
• Re: problem with mock, builds only static library
  • From: Denis Leroy
• Re: Game data packaging
  • From: Marcin Zajączkowski
• Re: problem with mock, builds only static library
  • From: Bruno Postle
• Re: Include ia64 tracker bug in review guidelines
  • From: Paul Howarth
• Re: Include ia64 tracker bug in review guidelines
  • From: Michel Salim
• Include ia64 tracker bug in review guidelines
  • From: Debarshi Ray
• Re: Macro expansion problem
  • From: Axel Thimm
• Re: Re: Game data packaging
  • From: Michel Salim
• Re: Re: Macro expansion problem
  • From: Michel Salim
• Re: Macro expansion problem
  • From: Jason L Tibbitts III
• Re: Re: Macro expansion problem
  • From: Jarod Wilson
• Re: Macro expansion problem
  • From: Axel Thimm
• Re: Macro expansion problem
  • From: Michel Salim
• Re: Macro expansion problem
  • From: Rex Dieter
• Re: Macro expansion problem
  • From: Axel Thimm
• Re: Macro expansion problem
  • From: Tom Lane
• Macro expansion problem
  • From: Michel Salim
• Re: Game data packaging
  • From: Marcin Zajączkowski
• Re: Game data packaging
  • From: Michał Bentkowski
• Re: Game data packaging
  • From: Hans de Goede
• Game data packaging
  • From: Marcin Zajączkowski
• Re: Re: GNUstep filesystem layout discussion
  • From: Patrice Dumas
• Re: Re: GNUstep filesystem layout discussion
  • From: Dominik 'Rathann' Mierzejewski
• Re: Re: GNUstep filesystem layout discussion
  • From: Rex Dieter
• Re: Re: GNUstep filesystem layout discussion
  • From: Dominik 'Rathann' Mierzejewski
• Re: GNUstep filesystem layout discussion
  • From: Axel Thimm
• Re: Re: GNUstep filesystem layout discussion
  • From: Michel Salim
• Re: Re: GNUstep filesystem layout discussion
  • From: Rex Dieter
• Re: GNUstep filesystem layout discussion
  • From: Axel Thimm
• Re: GNUstep filesystem layout discussion
  • From: Dominik 'Rathann' Mierzejewski
• Re: GNUstep filesystem layout discussion
  • From: Axel Thimm
• Re: Re: GNUstep filesystem layout discussion
  • From: Dominik 'Rathann' Mierzejewski
• Re: GNUstep filesystem layout discussion
  • From: Axel Thimm
• Re: Re: GNUstep filesystem layout discussion
  • From: Michel Salim
• Re: GNUstep filesystem layout discussion
  • From: Dominik 'Rathann' Mierzejewski
• Re: GNUstep filesystem layout discussion
  • From: Axel Thimm
• GNUstep filesystem layout discussion
  • From: Michel Salim
• Re: [Fedora-haskell-list] Revised Haskell Guidelines 2008.08.13
  • From: Jens Petersen
• Re: Removal of illegal packages
  • From: Matthias Kilian
• Re: Removal of illegal packages
  • From: jdong
• Re: Removal of illegal packages
  • From: Stephen Sweeney
• Re: Removal of illegal packages
  • From: Guus Sliepen
• Removal of illegal packages
  • From: Stephen Sweeney
• problem with mock, builds only static library
  • From: Bruno Postle
• Re: resolving rpmlint absolute symlinks issue
  • From: Axel Thimm
• Re: resolving rpmlint absolute symlinks issue
  • From: David Timms
• Re: resolving rpmlint absolute symlinks issue
  • From: spot
• resolving rpmlint absolute symlinks issue
  • From: David Timms
• Re: Simple cvs extras suggestion
  • From: Jason L Tibbitts III
• Re: Simple cvs extras suggestion
  • From: Patrice Dumas
• Re: Advise on the Samba4/OpenChange stack
  • From: Andrew Bartlett
• Re: Next meeting?
  • From: Jason L Tibbitts III
• Next meeting?
  • From: Anthony Green
• Re: Simple cvs extras suggestion
  • From: Jason L Tibbitts III
• Re: Simple cvs extras suggestion
  • From: Till Maas
• Re: Re: Best way to add a line to a config file from another package?
  • From: Vasile Gaburici
• Re: Advise on the Samba4/OpenChange stack
  • From: Toshio Kuratomi
• Revised Haskell Guidelines 2008.08.13
  • From: Yaakov Nemoy
• Re: Best way to add a line to a config file from another package?
  • From: Patrice Dumas
• Re: Best way to add a line to a config file from another package?
  • From: Patrice Dumas
• Re: Best way to add a line to a config file from another package?
  • From: Vasile Gaburici
• Advise on the Samba4/OpenChange stack
  • From: Andrew Bartlett
• Re: Simple cvs extras suggestion
  • From: Toshio Kuratomi
• Simple cvs extras suggestion
  • From: Robin Norwood
• Re: Best way to add a line to a config file from another package?
  • From: Axel Thimm
• Re: Best way to add a line to a config file from another package?
  • From: Vasile Gaburici
• Re: Best way to add a line to a config file from another package?
  • From: Vasile Gaburici
• Re: Best way to add a line to a config file from another package?
  • From: Patrice Dumas
• Best way to add a line to a config file from another package?
  • From: Vasile Gaburici
• Re: Extending PatchUpstreamStatus to include other added content (e.g. desktop files)
  • From: Vasile Gaburici
• Re: Extending PatchUpstreamStatus to include other added content (e.g. desktop files)
  • From: Ralf Corsepius
• Extending PatchUpstreamStatus to include other added content (e.g. desktop files)
  • From: Till Maas
• Re: Are there *any* guidelines for what "Group:" an application should go in?
  • From: Vasile Gaburici
• Re: Are there *any* guidelines for what "Group:" an application should go in?
  • From: Toshio Kuratomi
• Are there *any* guidelines for what "Group:" an application should go in?
  • From: Vasile Gaburici
• Re: Re: OCaml library packaging - no-arch for non-devel?
  • From: Panu Matilainen
• Re: OCaml library packaging - no-arch for non-devel?
  • From: Axel Thimm
• Re: OCaml library packaging - no-arch for non-devel?
  • From: Richard W.M. Jones
• Re: OCaml library packaging - no-arch for non-devel?
  • From: Tom "spot" Callaway
• Re: OCaml library packaging - no-arch for non-devel?
  • From: Richard W.M. Jones
• Re: OCaml library packaging - no-arch for non-devel?
  • From: Richard W.M. Jones
• Re: OCaml library packaging - no-arch for non-devel?
  • From: Daniel P. Berrange
• OCaml library packaging - no-arch for non-devel?
  • From: Alan Dunn
• fedora-usermgmt - again
  • From: Axel Thimm
• Problems with creating gitosis package
  • From: John A. Khvatov
• Re: can Blargg's NTSC libraries be included in fedora ?
  • From: David Timms
• Re: can Blargg's NTSC libraries be included in fedora ?
  • From: Hans de Goede
• Re: can Blargg's NTSC libraries be included in fedora ?
  • From: Tom "spot" Callaway
• can Blargg's NTSC libraries be included in fedora ?
  • From: David Timms
• Re: A few links broken in the ReviewGuidelines
  • From: Jason L Tibbitts III
• Re: A few links broken in the ReviewGuidelines
  • From: Till Maas
• Re: A few links broken in the ReviewGuidelines
  • From: Jesse Keating
• Re: A few links broken in the ReviewGuidelines
  • From: Thorsten Leemhuis
• Re: A few links broken in the ReviewGuidelines
  • From: Tom "spot" Callaway
• Re: A few links broken in the ReviewGuidelines
  • From: David Timms
• Re: A few links broken in the ReviewGuidelines
  • From: Tom "spot" Callaway
• A few links broken in the ReviewGuidelines
  • From: Thorsten Leemhuis
• Re: supporting closed source operating systems?
  • From: Alexandre Oliva
• Re: Adding mod_ban to proftpd?
  • From: Philip Prindeville
• Re: Adding mod_ban to proftpd?
  • From: Matthias Saou
• Adding mod_ban to proftpd?
  • From: Philip Prindeville
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: Libtool 2.x?
  • From: Matthias Clasen
• Libtool 2.x?
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: broken links in Packaging/SourceURL
  • From: Tom "spot" Callaway
• broken links in Packaging/SourceURL
  • From: Jens Petersen
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Fwd: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Nicolas Mailhot
• Re: Remakes legality question
  • From: Hans de Goede
• Re: Are debuginfos packaged for F9 updates?
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: Are debuginfos packaged for F9 updates?
  • From: Ville Skyttä
• Are debuginfos packaged for F9 updates?
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Jonathan Underwood
• Remakes legality question
  • From: Christian Morales Vega
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Nicolas Mailhot
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Nicolas Mailhot
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Nicolas Mailhot
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Nicolas Mailhot
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Anthony Green
• TeX fonts, part one [Was: Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages]
  • From: Vasile Gaburici
• Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages
  • From: Nicolas Mailhot
• Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages
  • From: Patrice Dumas
• Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages
  • From: Nicolas Mailhot
• Re: Case-insensitive "yum install"?
  • From: Nicolas Mailhot
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Jason Tibbitts
• Re: Case-insensitive "yum install"?
  • From: seth vidal
• Re: Case-insensitive "yum install"?
  • From: Tom "spot" Callaway
• Case-insensitive "yum install"?
  • From: Chris Ball
• Re: Proposed amendment to general packaging guidelines: no bundling of fonts in other packages
  • From: Dominik 'Rathann' Mierzejewski
• Proposed amendment to general packaging guidelines: no bundling of fonts in other packages
  • From: Nicolas Mailhot
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Anthony Green
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Anthony Green
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Dominik 'Rathann' Mierzejewski
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Ralf Corsepius
• Packaging xulrunner extensions: dependencies
  • From: Ville-Pekka Vainio
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Toshio Kuratomi
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Richard W.M. Jones
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Jesse Keating
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Daniel P. Berrange
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Hans de Goede
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Jason Tibbitts
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Tom "spot" Callaway
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Richard W.M. Jones
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Tom "spot" Callaway
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Richard W.M. Jones
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Tom "spot" Callaway
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Richard W.M. Jones
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Tom "spot" Callaway
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Richard W.M. Jones
• Re: rakarrack - alternative desktop categories
  • From: David Timms
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Anthony Green
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Ralf Corsepius
• Re: Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Tom "spot" Callaway
• Re: Early MinGW packaging guidelines draft
  • From: Toshio Kuratomi
• Fedora Packaging Committee Meeting (Tuesday July 22)
  • From: Tom "spot" Callaway
• Re: Early MinGW packaging guidelines draft
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Yaakov Nemoy
• Re: Re: supporting closed source operating systems?
  • From: Toshio Kuratomi
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Yaakov Nemoy
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Yaakov Nemoy
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Toshio Kuratomi
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: Re: supporting closed source operating systems?
  • From: Toshio Kuratomi
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: supporting closed source operating systems?
  • From: Axel Thimm
• Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: supporting closed source operating systems?
  • From: Alexandre Oliva
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Fedora Common Lisp update
  • From: Anthony Green
• Re: supporting closed source operating systems?
  • From: Axel Thimm
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: Re: Regarding PHP guidelines -- pear packages
  • From: Rakesh Pandit
• Re: Re: Regarding PHP guidelines -- pear packages
  • From: Remi Collet
• Re: Early MinGW packaging guidelines draft
  • From: Dominik 'Rathann' Mierzejewski
• Re: Early MinGW packaging guidelines draft
  • From: Ralf Corsepius
• Re: Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: supporting closed source operating systems?
  • From: Jeff Spaleta
• Re: supporting closed source operating systems?
  • From: Axel Thimm
• Re: Early MinGW packaging guidelines draft
  • From: Dominik 'Rathann' Mierzejewski
• Re: Early MinGW packaging guidelines draft
  • From: Richard W.M. Jones
• Re: supporting closed source operating systems? (was: Early MinGW packaging guidelines draft)
  • From: Daniel P. Berrange
• Re: Re: supporting closed source operating systems?
  • From: Daniel P. Berrange
• Re: Re: supporting closed source operating systems?
  • From: Richard W.M. Jones
• Re: supporting closed source operating systems?
  • From: Rex Dieter
• Re: supporting closed source operating systems?
  • From: Axel Thimm
• Re: supporting closed source operating systems? (was: Early MinGW packaging guidelines draft)
  • From: Richard Jones
• Re: supporting closed source operating systems? (was: Early MinGW packaging guidelines draft)
  • From: Stephen John Smoogen
• Re: supporting closed source operating systems? (was: Early MinGW packaging guidelines draft)
  • From: Anthony Green
• supporting closed source operating systems? (was: Early MinGW packaging guidelines draft)
  • From: Axel Thimm
• Re: Early MinGW packaging guidelines draft
  • From: Axel Thimm
• Re: Regarding PHP guidelines -- pear packages
  • From: Axel Thimm