Today I tried to use few Fedora tools and was greet with nice tracebacks
when gave wrong arguments or something other happened. But that's not
why I am writing.
What surprised me more is that Fedora tools are still Python 2.x based.
Someone may write "so what?" but I think that using legacy version
should have some end date. 6 years passed since Python 3.0 release...
When I worked at Canonical there was a goal to move both internal and
public tools to Python 3.x version. IIRC started somewhere around 12.04
and today when you look at Ubuntu Touch you will not find Python 2.7
there. Similar with other tools.
Can it be done? Maybe not in a month but who knows - f22 cycle?
- Status buildrequires cleanup work (davids & nils!)
- Docker update / Rocket container check
- Status rpm mechanisms for multiple config subpackages
- Status rpm mechanisms for factory reset files
- Base WG ownership of generic network install images
(keep it on the agenda, until all WG members are back from PTO)
- Open Floor
Thanks & regards, Phil
Philipp Knirsch | Tel.: +49-711-96437-470
Manager Core Services | Fax.: +49-711-96437-111
Red Hat GmbH | Email: Phil Knirsch <pknirsch(a)redhat.com>
Wankelstrasse 5 | Web: http://www.redhat.com/
D-70563 Stuttgart, Germany
Compose started at Fri Dec 5 07:15:02 UTC 2014
Broken deps for armhfp
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-mapreduce
avro-mapred-1.7.5-9.fc21.noarch requires hadoop-client
openstack-nova-compute-2014.1.2-1.fc21.noarch requires libvirt-daemon-xen
ostree-grub2-2014.11-1.fc21.armv7hl requires grub2
spring-maps-default-0.1-12.fc21.noarch requires spring
syntastic-d-3.5.0-1.fc21.noarch requires ldc
* Tue Dec 02 2014 Vratislav Podzimek <vpodzime(a)redhat.com> - 21.48.21-1
- Revert "Make Python's default encoding detection work on Live installations
* Mon Dec 01 2014 Samantha N. Bueno <sbueno+anaconda(a)redhat.com> - 21.48.20-1
- Revert "Search for a valid stage1 device on disks with stage1 mount points
- Make Python's default encoding detection work on Live installations
- Force translation files download instead of skipping them (#1169023)
* Fri Nov 28 2014 Vratislav Podzimek <vpodzime(a)redhat.com> - 21.48.19-1
- Search for a valid stage1 device on disks with stage1 mount points (#1168118)
* Thu Nov 27 2014 Vratislav Podzimek <vpodzime(a)redhat.com> - 21.48.18-1
- Tell curl it should follow redirects when fetching updates.img (#1168561)
- Snapshot free space after clearpart for swap suggestion (#1167965) (vpodzime)
* Wed Nov 26 2014 Samantha N. Bueno <sbueno+anaconda(a)redhat.com> - 21.48.17-1
- Make sure storage info bar is displayed (#1166730) (bcl)
- Fix SELINUX_DEFAULT import (#1167047) (bcl)
- Fix noselinux cmdline default (#1167047) (bcl)
Size change: 219043 bytes
* Thu Nov 27 2014 Pete Travis <me(a)petetravis.com> - 21.08-1
- Updated, many new items. See Release Notes for details.
Size change: 17250 bytes
* Wed Dec 03 2014 Samantha N. Bueno <sbueno+anaconda(a)redhat.com> - 0.61.13-1
- Fix pyparted version in spec file. (sbueno+anaconda)
- Revert "Prune actions before cancelling them" (sbueno+anaconda)
- Revert "Update partitions' numbers and names when adding new partition
- Revert "Return device's children sorted by name" (sbueno+anaconda)
* Thu Nov 27 2014 Vratislav Podzimek <vpodzime(a)redhat.com> - 0.61.12-1
- Prune actions before cancelling them (vpodzime)
- Try to get FS info first before doing an FS check (vpodzime)
- Reverting partition's size shouldn't require it to be aligned (#1165714)
* Wed Nov 26 2014 Samantha N. Bueno <sbueno+anaconda(a)redhat.com> - 0.61.11-1
- Update partitions' numbers and names when adding new partition (#1166598)
- Return device's children sorted by name (vpodzime)
- Run dosfsck in non-interactive mode (#1167959) (bcl)
Size change: 1748 bytes
* Fri Nov 28 2014 <bruno(a)wolff.to> - 0.21.10-1
- This build corresponds to RC4 which will likely end up being used for final
- The upstream commit used is 59e73c16ee88d29d0c0d923bba43c0cdc53d8a01
* Fri Nov 28 2014 <bruno(a)wolff.to> - 0.21.9-1
- This is intended to match what is used for f21 final
Size change: 1004 bytes
Added Packages: 0
Removed Packages: 0
Modified Packages: 4
Size of added packages: 0 (0 )
Size change of modified packages: 239045 (233 k)
Size of removed packages: 0 (0 )
Size change: 239045 (233 k)
Compose finished at Fri Dec 5 11:21:52 UTC 2014
sorry for late response to all your feedback , been off-grid ( rural AZ
+ ATT => fail )
@owen - thks for feedback re backlighting - got dimming set via xfce
power settings - dimming seems about same as osx but power use still
sucks (4 hrs) so something is missing - have noticed there seems no
setting for % brightness for normal use -could probably get by with
75-80% and this might be a big impact - does gnome have better power
settings ? will load gnome tonight and see. If dimming and backlight
pcts are avail to user then user can set to their own preference
otherwise a default can be provided - apparently osx picks some default
that most seem happy with and the life is impressive
@kevin - yes, you're right on - should be good by default (then allow
user mods). Need good setting capability and then better docs with
powertop, tuned (yeah they seem only for monitoring but then auto-tune
sounds like some optimization program
re lenovo with powertop thks for feedback - will try with
@Ivan hola, (soy ir Chile y Argentina en marzo - en donde vives ?) see
my comments below, let's start after F21 release
re suspend - probably hardware specific - happy to say we've found F20
suspend works perfectly on Air and Acer 720 Chromebook
re all those steps - oh I thought I left corp America behind :) I hope
we can do with less bureaucracy and maybe just some old fashioned
hacking and trial / error but I do recognize that testing with Rawhide
might be correct for latest changes
our next step will be to upgrade to F21 since it's final in a week, then
test auto-tune and backlight as above and see if significant difference.
While we're on it (in the form "how many devs do we have"): How
hard/impossible/unsuitable would it be to get a usable estimate on the #
of users, per package?
Here are so many problems, technical, policy, resources, (others?). That
said, feedback in the form "How many users uses/installs my package"
would IMHO be a great input for any packager. It would be the difference
between dropping the package in a black hole vs getting a message back
from the community.
Lets face it: I envy those who can measure the usage from a download
counter or so. Can we have something similar?
Could we even give people a badge when users actually uses a package ?
(hrmpf :) )
At the Fedora 21 Final Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 21 Final by Fedora QA, Release Engineering
Fedora 21 will be publicly available on Tuesday, December 09, 2014.
Meeting details can be seen here:
Thanks everyone, this is a huge achievement after almost one year long
development cycle and many changes not only under the hood how we
produce Fedora! And now, let's back to work on to the next Next Fedora
test-announce mailing list
are already to be push to stable without passing to test repo .
But for what I see: "stable karma: 0" it shouldn't be pulled to stable
even with karma 4 .
I had an idea
why not ? be possible, set in Bodhi request, the minimum time to be in
for firefox minimum time could be 1 or 2 days, but not 0 :)
and setting 0 .
Sérgio M. B.
Through some series of accidents, the python-pyudev package in Fedora is
assigned to clockfor(a)redhat.com. This account has been closed since at
least early 2013. The email address isn't "invalid" exactly in that
emails won't bounce, but it is a black hole from which no responses will
return, and as such I am skipping to the later parts of the
nonresponsive maintainer process.
So: does anyone know how to contact Chris Lockfort, or if he is still
interested in maintaining python-pyudev? If he is not, I would like to
take over the package.
For the documentation of unresponsiveness, here's all the bugs, ain't
none responded to: