Removing Publican and fop from EPEL5
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The last week or so has seen a couple of patches going into fop in the Fedora repositories. I recently became a co-maintainer of fop in EPEL5 and was trying to bring fop into current there. Unfortunately there are many dependency failures there that it's going to be a lot of work to bring it up to where we need it. The actual need, from my point of view, is to get Publican working properly. fop provides the engine for creating PDFs in Publican and is a necessary function for the Fedora Docs project. That said, the current version of Publican in EPEL5 is very old and outdated. Near current version of Publican is already in EPEL6 and I believe fop is in RHEL6 repositories.
I say all that to ask this: Is anyone currently using fop or Publican in EPEL5 or can we get rid of those bits?
I have no problem working to bring fop upto speed in EPEL5 if someone needs it but I'd hate to do all the work if no one is using it.
- -Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJQxllPAAoJEIB2q94CS7PR+SsP/ifVjMU1szcMf4BvuksDOZWC
y+0k4E1z0AGSFjn5NEuBDi46DO6v6DQj2iTeW6AkzSoTCQCmE8q5Gxc2q2QFB1Hx
ookZAx+UuuPxRCFwfNmijZvrArkgqeGilnxYR8dU7GmkMFcNafxMQbECyfaX6I16
p19rWAV+Ie0rcU4iCqYEJT7VnBI7lWDdjquM8fGL+dlENEhSh7AUb8gFi47X/0jB
hphyIYwjdCIAvDQSuOxYCALXAAXeZo86yaN+UOsR68zIvE+9uOZyGgYyaOOLrsba
mMbuovki6YBQLJdGcnxZeh0f/9ECRD4nIRUyA19lum374+L+qT0Rmm3Yi2mk+fPm
qJSSYTGlaFSduLTseFgD4tefuwqhvbUE6jp+QcZMxIgdo6Z/EtZkGoObD4xIpAym
SmU+p8naGPDsNmOaO540EPWyytzXxCIOn4kjJs5A+zPEI7kEufinl8rcQpS9DLgU
MIDvgMKveEvWcvqsjVRac5Mgdme49Je4ZSu2xB2P70+7nqbP6eIJMKIJd3cb77y9
+1JtDZd1KWMDIlmNNbM9DGUlluwOG1sGGm2ScRCeqqOgHX5XLsn/10fCH6jb05n0
tRej80Lj7NWLDHzHkkQFpM8XaDc+f2keqEsvRGo3YY7i3Seld3EmgvIrctrG6O5C
WlhWc7uF74FI+Yl/xW50
=DysH
-----END PGP SIGNATURE-----
10 years, 9 months
Release Notes needs karma
by John J. McDonough
We are way behind in getting the beta release notes out. They are now
in Bodhi and need karma. Please give them a test and some love.
The RPM includes English, Dutch, Ukranian, Japanese and Chinese.
--McD
10 years, 9 months
Docs Meeting 10 December 2012
by Zach Oglesby
Meeting summary
---------------
* Roll Call (zoglesby, 14:00:35)
* Follow up on last week's action items (zoglesby, 14:02:39)
* Fedora 18 schedule (zoglesby, 14:03:07)
* LINK:
http://jreznik.fedorapeople.org/schedules/f-18/f-18-docs-tasks.html
(zoglesby, 14:03:13)
* string freeze for guides is 18 December (zoglesby, 14:03:52)
* F18 final is scheduled for 8 Jan (zoglesby, 14:04:01)
* Create GA Announcement start 17 December (zoglesby, 14:05:31)
* ACTION: zoglesby to get GA Announcement moving on docs-list
(zoglesby, 14:08:31)
* Release Notes (zoglesby, 14:10:37)
* LINK: https://fedorahosted.org/fesco/ticket/907#comment:3
(zoglesby, 14:11:17)
* ACTION: zoglesby to remove Liberation fonts text from Release Notes
(zoglesby, 14:15:28)
* Outstanding BZ Tickets (zoglesby, 14:17:24)
* 120 open bugs (zoglesby, 14:17:51)
* LINK: http://tinyurl.com/lbrq84 (zoglesby, 14:17:58)
* Open floor discussion (zoglesby, 14:18:31)
* LINK:
https://fedoraproject.org/wiki/Talking_points_SOP?rd=Talking_Points_SOP
(jreznik, 14:20:44)
* ACTION: jreznik to mail docs-list about working on Talking Points
(zoglesby, 14:23:10)
Action Items
------------
* zoglesby to get GA Announcement moving on docs-list
* zoglesby to remove Liberation fonts text from Release Notes
* jreznik to mail docs-list about working on Talking Points
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2012-12-10/fedora_docs.20...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2012-12-10/fedora_docs.20...
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2012-12-10/fedora_docs.20...
10 years, 9 months
Fedora Docs Meeting Reminder
by Ben Cotton
This is an automated message to remind you that we will be meeting at 1400 UTC in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.
10 years, 9 months
Tomorrow's meeting
by Ben Cotton
Hi gang,
I'm at the LISA conference this week and probably won't be able to run
tomorrow's meeting. Open invite for someone to seize the day!
10 years, 9 months
A conflict in F18 Release Notes
by Tiansworld
In release notes directory change section:
For most users, this change will be invisible because the Release Notes
are viewed by selecting the menu choice. However, some users go directly
to the file, or may have their own internal links. For these users,
changing the location without warning before the release could be a
problem, so the Release Notes are not being moved this release.
Beginning with Fedora 18, the Release Notes are stored in
/usr/share/doc/fedora-release-notes-18.0/.
The first paragraph says that it will not be moved "this release", but
the next paragraph says it will be move to
/usr/share/doc/fedora-release-notes-18.0/.
It's a contradictory.
I remember that the first paragraph is for Fedora 17 release notes. It
should be changed now.
I filed a bug[1].
[1] https://bugzilla.redhat.com/show_bug.cgi?id=885071
--
Regards,
Tiansworld
Fedora Project Contributor
10 years, 9 months
install guide notes: bootloader
by Adam Williamson
Hey, folks (Jack especially). I have it on my (very long) todo list to
look through the changes to the installation guide and see if I can
contribute anything, but we were talking about this in #anaconda this
morning and I thought I'd outline it for the install guide before I
forget the plan again. Handling of bootloader install is somewhat
different in newUI. This is all about BIOS - UEFI is completely
different.
So what newUI is capable of is either installing the bootloader to a
partition MBR, or not installing the bootloader at all. Currently there
is no option to install bootloader to a partition, which was possible in
oldUI. Installing the bootloader to a partition is done only by those
who multiboot various OSes using a 'chainload' system - they have a
bootloader in the MBR which 'chainloads' bootloaders for each of their
OSes, each of which resides in the / or /boot partition for that OS.
The plan is for those who have such setups to just not install a
bootloader at all, and then do their bootloader configuration manually
post-install. Anyone who for some reason doesn't want a bootloader
installed to an MBR gets to do their own configuration.
In the UI you are able to specify which disk the bootloader should be
installed to (or that it shouldn't be installed at all). You do this on
the 'disk selection' screen - the first screen you see after clicking on
the 'Installation Destination' spoke. You have to click on 'Full disk
summary and options...' and you get a dialog that lets you pick the
target disk for the bootloader. To set it to not install a bootloader at
all, right now, this is the procedure:
"highlight whatever disk has the bootloader check, click the button, and
it'll unset that device for receiving the bootloader. Thus, you should
not get a bootloader installed."
clumens notes that this isn't the best UI, but changing it would break
string freeze. See https://bugzilla.redhat.com/show_bug.cgi?id=867469
for details.
If you do not select a target disk, anaconda will default to installing
the bootloader to the MBR of the first disk (of those selected as
'install target disks' on the picker screen) that appears to be a viable
target, in enumeration order (so it'll try sda, then sdb, then sdc, and
so on, and the first one which passes the 'bootloader target' tests gets
the bootloader). This part is unchanged from F17.
Hope that's useful! Thanks.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
10 years, 9 months
Re: New User Questionnaire
by Brad Bailey
Ideally, there would be a separate guide for each of the 4 major desktop spins. I know how very frustrating it is to be totally new, and the available documentation in front of me doesn't apply.
I fully understand your point about open ended questions will provide us with more information. As I said on the wiki, most people are more likely to fill something out if they never have to take their hand off the mouse. I really like the idea though. When in doubt, choose both! I think I'll add an "optional" more data field beside/under each question.
> On 12/03/2012 05:26 PM, brad.b82 wrote:
> > I would like to start working on a Migration Guide for New Users. To
> > get to that point, we need to know what issues the new users are
> > facing. To answer that, I came up with a quick New User Questionnaire
> > to collect information. Please take a look at it and bring up your
> > own ideas and suggestions.
> >
> > http://fedoraproject.org/wiki/New_User_Questionnaire
> >
> >
> A migration guide is a good idea. What do you want to focus on - the
> GNOME desktop environment and general tools or something else? You might
> want to talk to pkovar. He is doing some stuff related to GNOME and
> would probably be thrilled to hear from you.
>
> Your questions are very good. the only improvement I can see is in
> phrasing. I would probably use open questions instead of or in
> combination with Yes/No questions to get more detailed information:
>
> "What do you do when you want to find and install a program but do not
> know the exact name for? (For example, a program that helps you use your
> digital camera)? "
>
> "Are you able to find a replacement for the common programs you are
> accustomed to using? How do you go about it?"
>
> Florian
>
> --
>
10 years, 9 months
