On Wed, Sep 25, 2013 at 5:58 AM, Thomas Moschny
wrote:
> See https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Done
Daniel
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.
Hi,
On Tue, Sep 17, 2013 at 11:10 AM, Thomas Moschny
wrote:
> I'd like to retire the python-jinja package, containing the Jinja1
> template engine, which has been superseded by Jinja2 for a very long
> time. Jinja2 is packaged as python-jinja2 in Fedora.
>
> However, there's one package left that
On Tue, Aug 27, 2013 at 9:30 AM, Peter Robinson wrote:
>
>> xorg-x11-drv-geode
>
>
> geode is used on the OLPC XO-1 and is maintained by Daniel Drake (dsd) and
> he's basically done all recent commits for upstream releases and fixes
> unless it's been something l
Hi,
We're pleased to announce the release of OLPC OS 13.1.0 for XO-1,
XO-1.5, XO-1.75 and XO-4. Details of new features, known issues, and
how to download/install/upgrade can all be found in the release notes:
http://wiki.laptop.org/go/Release_notes/13.1.0
Many thanks to all contributors, testers
Hi Bill
I see that initscripts in F18 ships this udev rule:
ACTION=="add", SUBSYSTEM=="net", PROGRAM="/lib/udev/rename_device",
RESULT=="?*", ENV{INTERFACE_NAME}="$result"
I'm trying to tackle some problems related to interface renaming, and
understanding how this works would be useful.
But I c
On Sun, Oct 28, 2012 at 11:27 PM, Peter Hutterer
wrote:
> Can you file a bug for this please so we can keep track of it in case this
> breaks something? You almost certainly also want the fix to fdo #55738
> http://lists.x.org/archives/xorg-devel/2012-October/034062.html
Thanks, filed as https://
Hi Peter,
Would it be OK for me to add the following touchscreen input fixes to
xorg-x11-server in F18 + rawhide?
Sync TouchListener memory allocation with population in TouchSetupListeners()
http://lists.x.org/archives/xorg-devel/2012-October/034149.html
Xi: Don't check for TOUCH_END, it's neve
Hi Danishka,
On Fri, Aug 31, 2012 at 10:28 AM, Danishka Navin wrote:
> Hi Daniel,
>
> I would like to join for testing for the next release.
>
> How may I proceed?
Great! We just posted our first F18 development build for the next
release which will be called 13.1.0.
I assume you have an XO wit
Hi,
We're pleased to announce the release of OLPC OS 12.1.0 for XO-1,
XO-1.5 and XO-1.75. Details of new features, known issues, and how to
download/install/upgrade can all be found in the release notes:
http://wiki.laptop.org/go/Release_notes/12.1.0
Many thanks to all contributors, testers, upst
Hi,
I'm porting olpc-dm to F18 /
https://fedoraproject.org/wiki/Features/DisplayManagerRework
Thanks for the good documentation.
The only detail that I'm unclear about is this one:
# Add the following line only if the DM can do Plymouth internally
Conflicts=plymouth-quit.service
What does it m
Hi,
Last week I tried a preupgrade from F16 to F17 beta.
When rebooting into the preupgrade environment, the upgrade failed in usrmove:
Make a copy of /mnt/sysimage/usr/bin
Merge the copy with /mnt/sysimage/bin
cp: cannot overwrite directory /mnt/sysimage/usr/bin.usrmove-new/mkdir
with non-direc
On Wed, Nov 30, 2011 at 5:15 PM, Sam Varshavchik wrote:
> Daniel Drake writes:
>
>> My understanding is that this reconstruction is a background task, is
>> there really a need for this to hold up boot?
>>
>> This behaviour comes from
>> 0064-90mdraid-wait-for
On Thu, Dec 1, 2011 at 3:20 AM, Jes Sorensen wrote:
> Haven't noticed that one here - however when reporting RAID issues,
> please include details on the type of RAID you are using (regular Linux
> mdadm RAID, IMSM (BIOS RAID) etc.).
Sorry for not specifying earlier - mdraid, raid 1 created with
Hi,
Just installing Fedora 16 on a new system. We set up a RAID1 with mdadm for /.
On boot, we're finding that if there is a RAID inconsistency, dracut
is waiting for mdadm reconstruction to complete before booting the
system. This means that after a power outage or other condition that
would cau
On Fri, Sep 30, 2011 at 11:30 PM, Daniel Drake wrote:
> However, it now has a text scaling factor in gsettings that I was not
> aware of. So I guess I just need to find an appropriate factor that
> makes fonts look OK on the XO.
One problem faced here is that (as noted earlier) Cantarel
On Fri, Sep 30, 2011 at 6:05 PM, Jef Spaleta wrote:
> On Fri, Sep 30, 2011 at 8:47 AM, Tomasz Torcz wrote:
>> Or
>> http://svn.gnome.org/viewvc/gnome-settings-daemon/branches/gnome-2-24/plugins/xsettings/gsd-xsettings-manager.c?view=markup#249
>> (line 249)?
>
> I'm not sure that's relevant for
On Fri, Sep 30, 2011 at 2:47 PM, Nicolas Mailhot
wrote:
> Someone Gnome-side decided to not trust xorg dpi and added a new heuristic to
> 'correct' it
I know this is part of a rant.. but any chance you could quantify that
point with a link to a commit, blog post, mailing list discussion,
somethin
On Fri, Sep 30, 2011 at 12:09 PM, Felix Miata wrote:
> Sounds to me like your F14 is using correct DPI while your F16 is forced to
> 96. Does your F14 have /etc/X11/xorg.conf file or a non-empty
> /etc/X11/xorg.conf.d/?
Bad DPI could certainly be a cause. However, xdpyinfo reports the
correct val
Hi,
I'm working on bringing OLPC up-to-date with all the great efforts
with GNOME 3, systemd, etc.
On the OLPC XO laptops we have quite a strange screen - it is small
(152mm x 114mm) but very high resolution (1200x900 i.e. 201 dots per
inch).
Previously, on Fedora 14, we had to adjust the defaul
On 11 February 2011 16:34, Dennis Gilmore wrote:
> yes you need to push them though bodhi.
I'm having trouble here.
olpc-powerd-31-1.fc15 is the version made before the rebuild
olpc-powerd failed to compile in the rebuild due to using a gcc flag
which no longer exists.
(that was olpc-powerd-31-
20 matches
Mail list logo
