Re: Forester project - Anaconda kickstart with Redfish
> Could you do some compare and contrast with cobbler? Sure, Forester is focused on image-based provisioning it does not (and probably never will) support traditional RPM installation like Cobbler. This is an experiment targeted on those who would like to apply cloud provisioning workflow in their own bare-metal (or virtualized) datacenter. It currently supports "liveimg" Anaconda provisioning and support for "ostreesetup/ostreecontainer" is planned. Instead of managing repositories of any kind, you just upload an image into Forester and deploy it, similarly to IaaS clouds. Now, it might not be clear what these features of Anaconda do so let me explain. With various tools (for example osbuilder or lorax), you can create a Fedora OS image that is in various formats (AMI, qcow2, raw and ISO). The last mentioned is actually a bootable Anaconda-based installer that contains a tarball with the OS, Anaconda in this case partitions disks and copy the files. In case of OSTree it is similar but the content is not a tarball but a OSTree repository. > Because what I would really like to see is more people helping out with > cobbler development. I spent over a decade maintaining Satellite 6 provisioning capabilities which take similar approach as Cobbler (PXE, DHCP and repositories management), however, I want to explore a different workflow which is not based on DHCP management (which does not work with IPv6), not based on PXE (UEFI HTTP Boot leverages TCP/HTTP/TLS stack in modern firmware) and not based on any kind of repository management. Forester is different, it has no ambitions to replace Cobbler or Satellite 6 it is purely just an Anaconda image deployer over network. One of the main theme is that Forester is easy to configure - no need to set up PXE, DHCP is optional and thanks to Redfish and UEFI HTTP Boot feature, it is extremely simple to use. Thanks for the feedback! -- lzap ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Forester project - Anaconda kickstart with Redfish
> Question: is osbuild/Image Builder a hard dependency here? What if I > wanted to use appliance-tools, lorax, or kiwi based images? Good point, not a hard dependency at all. I am trying to keep things simple as much as possible because I feel like the project website is already difficult to understand. But Anaconda is the only dependency, essentially the project is nothing else than a HTTP endpoint which can serve kickstart, grub configuration and the bootloader itself and Anaconda second stage plus the image (tarball). In fact, it could also do RPM-based installations at some point, but again I want to keep it simple for now. I only know lorax (livemedia-creator) and I actually tested it once, I haven’t tried the others. Essentially, the Forester project expects to be able to apply the "liveimg" anaconda statement in order to deploy an image. > Basically, all you need to do is file a fedora infrastructure ticket > asking for a mailing list under either lists.fedoraproject.org, Thanks a bunch! Created: https://pagure.io/fedora-infrastructure/issue/11594 -- lzap ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Forester project - Anaconda kickstart with Redfish
Hello, I would love to introduce you the Forester project: unattended bare-metal image-based Anaconda installation service. Forester provides unattended bare-metal installation network boot workflow for Fedora, Red Hat or compatible OS images created by Image Builder. It utilizes modern technologies like UEFI HTTP Boot, Redfish, Anaconda, SecureBoot and X509 for fast and secure image-based OS installations. Forester is a simple service with REST/RPC API and CLI. The project is currently in early development and I am looking for feedback of any form. For more info, demo recording and documentation, head over to: https://foresterorg.github.io/ I would also like to create a mailing list and since the project is related to both Fedora and Anaconda, I was thinking to apply for project membership under the Fedora family. Can someone help me with that? I was trying to find some more info about the formal process on Fedora wiki pages without much success. Thanks! Later. -- lzap ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F36 Change proposal: No ifcfg by default (Self-Contained Change)
For the record, I also created an issue for NetworkManager project. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/895 I think this would be a huge help for many of us migrating to the new syntax - there are endless combinations of configurations and we need to support many of them. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change proposal: No ifcfg by default (Self-Contained Change)
Hello, I represent one of system integrators (Foreman configuration and provisioning management open source project). Thanks for the info. I would like to ask for taking into consideration shipping some kind of syntax validation tool that could be executed to validate syntax of the new-style configuration. It would be important to have it implemented in a way that it does not require running NetworkManager, so users could actually use it even within kickstart %post section. We are not only interested in pure syntax check, but also semantic validation - depending on NetworkManager version, many of values are not considered valid and NetworkManager fails to bring connection up. If such tool would have support for multiple versions of NetworkManager, like ksvalidator do, that would be the best possible user experience. One could easily check if a configuration is valid for particular NM version (thus Fedora or RHEL version). In addition, if such a tool was distributed as a subpackage, we could totally integrate this into our CI suite to regularly test our provisioning templates responsible for generating NetworkManager configurations. A precedent is grub2 which has a solid validator which we run in our CI to catch issues and bugs beforehand. Thanks and cheers! -- lzap ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Account System and Bugzilla Mismatch email
Hey, I got an email asking me to change my fedora email to match my BZ account. Problem is, in BZ I have to use my redhat account which allows me to be granted special permissions for RH-related bugs. Fedora wants to do this for the same reason, however I'd like to separate my upstream contribution and all accounts from my work account, therefore I'd like to continue using my private email. Is this something that can be solved? Like by adding a special field which is used to link BZ so users can set these individually? Thanks. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: What could prevent from screen blanking / DPMS
I am gonna repost this in desktop, sorry for the incorrect list. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
What could prevent from screen blanking / DPMS
Hey, I have pretty minimal i3wm install and I recently tried to set up blanking and DPMS, but the thing is it does not work: $ xset s blank s 10 dpms 10 15 20 $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 0002 XKB indicators: 00: Caps Lock: off01: Num Lock:on 02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 660repeat rate: 25 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 0bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 10cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: catalogue:/etc/X11/fontpath.d,built-ins DPMS (Energy Star): Standby: 10Suspend: 15Off: 20 DPMS is Enabled Monitor is On What could prevent blanking and suspend from happening and how to debug this? I don't have any screensaver installed, could this be an issue? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
How to deprecate a subpackage
Hey,
I have a subpackage which is not needed anymore in the new version of the
package. Is my assumption correct that for a smooth upgrade path I should
simply delete the subpackage and make the main package to obsolete it:
Obsoletes: %{name}-gtk2
Provides: %{name}-gtk2
Looks like rpmlint wants me to add version, I can do that.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Missing gtk2 library in workrave - build help
Hey, I am trying to bump version of package named workrave which was not originally added by me, I have been able to fix all the issues so far except one: https://kojipkgs.fedoraproject.org//work/tasks/7540/42797540/build.log error: File not found: /builddir/build/BUILDROOT/workrave-1.10.37-1.fc33.x86_64/usr/lib64/libworkrave-gtk2-private-1.0.so.* Here is the SPEC: https://src.fedoraproject.org/rpms/workrave/blob/master/f/workrave.spec I am trying to find out why autotools is not building this library, can you give me advice how to get there? Thanks. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: ActionNotAllowed: policy violation (build_from_srpm)
Facepalm. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
ActionNotAllowed: policy violation (build_from_srpm)
Hey guys, I am trying to build a SRPM since mockbuild does not work due to (1). # fedpkg srpm # fedpkg build --srpm /home/lzap/work/fedpkg/workrave/workrave-1.10.37-1.fc33.src.rpm But getting %SUBJ%: https://koji.fedoraproject.org/koji/taskinfo?taskID=42794359 What is wrong? I believe my kerberos is correct: # kinit Ticket cache: KEYRING:persistent:1000:1000 Default principal: l...@fedoraproject.org Valid starting Expires Service principal 27.3.2020 11:19:54 28.3.2020 08:57:58 HTTP/koji.fedoraproject@fedoraproject.org renew until 3.4.2020 09:57:58 27.3.2020 10:21:05 28.3.2020 08:57:58 HTTP/src.fedoraproject@fedoraproject.org renew until 3.4.2020 09:57:58 27.3.2020 08:57:59 28.3.2020 08:57:58 krbtgt/fedoraproject@fedoraproject.org renew until 3.4.2020 09:57:58 (1) https://bugzilla.redhat.com/show_bug.cgi?id=1812872 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Autoconf help: missing X11 dependency
Thanks all, this config.log is really useful. Had no idea. Now fighting with python2 vs python3 but that's another story. TY ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Autoconf help: missing X11 dependency
This was helpful, thank. It's missing c++ compiler when it tries to compile the "test program". I guess I need to add that. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Autoconf help: missing X11 dependency
Just in case there is somebody with autotools-X-ray glasses, here is the
autoconf bit:
https://paste.fedoraproject.org/paste/6KSdRXVFSSVb1PfENZf3JA
And the current build requires:
# adding this does not help there must be more
BuildRequires: libX11-devel
BuildRequires: libXtst-devel
BuildRequires: libXScrnSaver-devel
BuildRequires: pkgconfig(ice)
BuildRequires: pkgconfig(sm)
BuildRequires: pkgconfig(glib-2.0) >= 2.28.0
BuildRequires: pkgconfig(gio-2.0) >= 2.26.0
BuildRequires: pkgconfig(gtk+-3.0) >= 3.0.0
BuildRequires: pkgconfig(sigc++-2.0) >= 2.2.4.2
BuildRequires: pkgconfig(glibmm-2.4) >= 2.28.0
BuildRequires: pkgconfig(gtkmm-3.0) >= 3.0.0
BuildRequires: gobject-introspection-devel >= 0.6.7
BuildRequires: pkgconfig(indicator3-0.4) >= 0.3.19
BuildRequires: pkgconfig(dbusmenu-glib-0.4) >= 0.1.1
BuildRequires: pkgconfig(dbusmenu-gtk3-0.4) >= 0.3.95
BuildRequires: python-cheetah
BuildRequires: pkgconfig(gstreamer-1.0)
BuildRequires: pkgconfig(libpulse) >= 0.9.15
BuildRequires: pkgconfig(libpulse-mainloop-glib) >= 0.9.15
BuildRequires: gettext
BuildRequires: intltool
BuildRequires: autoconf, automake, libtool, autoconf-archive
BuildRequires: desktop-file-utils
%if 0%{?gnome_flashback}
BuildRequires: pkgconfig(libpanel-applet)
%endif
%if 0%{?xfce} || 0%{?mate}
BuildRequires: pkgconfig(gtk+-2.0) >= 2.6.0
%endif
%if 0%{?xfce}
BuildRequires: pkgconfig(libxfce4panel-1.0) >= 4.4
%endif
%if 0%{?mate}
BuildRequires: pkgconfig(libmatepanelapplet-4.0)
%endif
Thanks for help.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Autoconf help: missing X11 dependency
Hello, my package "workrave" won't build with Rawhide, configure script complains: checking for X... no configure: error: X11 required on Unix platform However it keeps complaining even when I add BuildRequires: libX11-devel. I don't understang which particular (sub)library it needs, generated configure is a bit unreadable (really!) and even debugging it with +x is not really helpful as it is a storm of tests. Any idea how to debug this? What X11 library am I missing? Any recent changes in the X11 libraries? This is a regression, it was working fine. Thanks. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: RFC: Change the default hostname for Fedora 26+
> Thoughts on how to generate these random strings are of course up for > discussion. Given that initial machine creation may have limited available I am fighting against human unreadable names in hostnames (specifically in datacenters) and I created a little tool [1] that generates human readable and memorizable names made out of frequently occurring given names and surnames from the 1990 US Census (public domain data - confirmed with Fedora legal). This gives about 33 million unique total names. Examples: velma-pratico.my.lan angie-warmbrod.my.lan grant-goodgine.my.lan alton-sieber.my.lan velma-vanbeek.my.lan don-otero.my.lan sam-hulan.my.lan We could consider similar approach for default hostnames. I can imagine the US names can be confusing, we can swap these with colors or other words to make it little bit less confusing (e.g. "blue-star"). This is definitely nicer than "Fedora-c4feb4b3", I don't like sharing same prefixes, this makes tab expansion unusable, it usually needs wider columns in lists etc. Distribution name is, I think, not relevant when it comes to naming computers. It is just a name, "yellow-dog" isn't that bad, is it? Another thing that should be take into account is not doing this randomly, but seeding the algorithm based on hardware specifics (MAC, serial number), so when system is reprovisioned, it gets the very same hostname. This approach can be combined with the above one if needed, giving: - human readable names - memorizable names - consistent names after reinstallation [1] https://github.com/lzap/deacon This is a rubygem, but this kind of thing is trivial (and fun) to write, I can give a hand implementing this in Python in order to allow Anaconda to do this if folks like my idea. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F25 System Wide Change: Use /etc/distro.repos.d as default reposdir
> >> /etc/repos.d is less typing. Yes, please! With a symlink /etc/yum.repos.d to it. > The .d suffix is a meaningful distinction. It denotes a drop-in directory > (where > anything placed in it is meant to be automatically picked up and used, > assuming > it is in the correct format). Sure. I always find annoying when there are two entities: something.conf something.d/ so in order to expend the directory, I need to tab twice. I hope there will be no repos.conf :-) -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Include livenet and nbd dracut plugins on the Fedora Live ISO
> dracut itself contains the configuration about what modules get built > into the initramfs in what situations. Live images use a generic (--no- > hostonly) initramfs. I'd talk to the dracut maintainer about the > appropriate way to add these. Hmm, it looks like dracut-live contains the module livenet and dracut-network contains nbd module. But where is the place with the list of plugins to be included for workstation live spin? Can't find these. I don't believe we include all the plugins as on Fedora 23 Live there is no "livenet" module from what I understand (does not work for me). -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Include livenet and nbd dracut plugins on the Fedora Live ISO
> It's probably defined in the lorax template [1] which is part of what > live-media-creator uses. Currently for F-23 we actually use > livecd-creator but in F-24 we'll be moving to lmc because it then uses > the same code paths etc as the rest of the tools we use to build the > distro so that's where the change should land. Ok, thanks. It looks like livenet is already included by default, so I expect to have it in F24 then. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Some analysis on the size of the minimal and Server installs of Fedora 23
> > b'plymouth-scripts': 121 > > b'plymouth': 121 > This really does not need to be on minimal installation. I agree, also it looks like in CentOS 7 minimal install there are also some bootloader-related images in /usr/share/backgrounds/* which are also pretty big. I assume the same for fedora. Locale is about 100 MB (installed size), this is worth investigating as well. Some spins might not need them: localedef --list-archive | grep -iv 'en_US' | xargs localedef -v --delete-from-archive mv /usr/lib/locale/locale-archive /usr/lib/locale/locale-archive.tmpl /usr/sbin/build-locale-archive Also cracklib library can be compressed (and it works just fine): gzip -9 /usr/share/cracklib/pw_dict.pwd Few (little bit more dirty) tricks are in our Foreman Discovery Image (Fedora/CentOS based distro to server as MaaS discovery tool): https://github.com/theforeman/foreman-discovery-image/blob/master/25-minimize.ks Here, it's little bit extreme (we are removing RPM database, all documentation etc) because the distro runs from memory (as Live one). Posting this here because it's relevant. Any more tips how to save more space are highly appreciated! -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Include livenet and nbd dracut plugins on the Fedora Live ISO
Hello, I would like to have livenet / nbd plugins to be present on the initram disk of Fedora Workstation Live DVD, but I struggle to find a place where to send a patch. Can you help me where should I file this? Must be some dracut script that builds those, or is this the official kernel that ships with Fedora system? These modules are small, but it will offer possibility to boot Fedora Live via PXE from network (HTTP, FTP or NBD). It has few dependencies (nbd-client, curl) but those are tiny and I assume curl is already in the minimal installation anyway. Use case: A neighbour shows up with a broken Windows laptop without a CD/DVD drive apparently and I have no USB stick with up-to-date Fedora Live image handy. With my proposal implemented, I can offer connecting to my network, booting up Fedora and to try things out. In dozens of minutes, new happy Fedora user walks out of my doors :-) I would like to carry on with a change to livecd-tools providing helper script livecd-to-pxe-livenet and livecd-to-pxe-nbd to help with creating those configurations. If this turns to be a bad idea, then I will design the helper scripts to generate the kernel/image from a running system, but then users need to run compatible distro to successfully generate it. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Some analysis on the size of the minimal and Server installs of Fedora 23
> What i've been doing on a number of small devices lately is strip all > comments from all files, which frees up a lot of disk space. Can you share the script please, I am interested (also kinda embedded space I work on). -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Poll: How users use DNF
Going to chip in with: /usr/bin/yum -d 0 -e 0 -y install PACKAGE This is what default Fedora package provider does in Puppet. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Are we rebasing xorg-x11 packages in F20?
Hello, my desktop was completely broken this morning because my startup scripts rely on xrandr utility. An older update from this summer which I applied recently changed it's output so device ids now contain dash characters (e.g. instead VGA0 I see VGA-1). I just wonder why this landed into stable repository. The package changelog really shows it's a rolling release kinda thing. http://pkgs.fedoraproject.org/cgit/xorg-x11-server-utils.git/log/?h=f20 I understand some packages has exceptions, like kernel, firmware and such things. But xorg tools? Thanks for explanation. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Are we rebasing xorg-x11 packages in F20?
Using what gfxchip? VGA0 I don't remember ever seeing. Most I remember seeing: Yeah, that was a typo. It's actually DP-1 and LVDS-0 (Thinkpad T403s with Intel). Anyway, this changed from DP1 and LVDS0. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Are we rebasing xorg-x11 packages in F20?
Anyhow, I hit the same thing this morning, with LVDS1 changing to LVDS-0, HDMI3 to HDMI-2 and VGA1 to VGA-0. This was on an Intel adapter. Exactly. I use i3wm and I use xrandr to determine if I have my laptop docked with IPS panel, docked with VGA monitor or standalone. Then I setup all my workspace appropriately. It's not a big deal, however, it was rather unexpected in the middle of a stable release... Yeah, I have fixed that after 10 minutes this morning. I just want to ask *why* we rebase things for stable releases. If I want to live on the edge, I use Rawhide. I don't understand why I noticed this today, it looks like the latest update was a Critical Path one (???) when Fedora 20 was stable for six months. https://admin.fedoraproject.org/updates/FEDORA-2014-7331/xorg-x11-server-utils-7.7-6.fc20 Something is not right here. a) We should not be bumping up versions of packages for stable releases. b) We should definitely not do this with Critical Paths. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Are we rebasing xorg-x11 packages in F20?
There's an intel driver from 18th november, for example: https://admin.fedoraproject.org/updates/FEDORA-2014-15384/xorg-x11-drv-intel-2.21.15-9.fc20 This seems to be much more related to your issues. I don't had any output renaming recently in the past year (Nouveau here). That answers the question why I experienced the change today, and not six months ago :-) I understand why drivers are updated for stable releases, that's fine. Not sure about the Critical Path (graphics drivers can bite, more testing time is perhaps the better) but if this is our policy, there must be some reasons for that. Thanks! -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Mozilla enabled ads in Firefox and they're active in Fedora
Being bombarded with questions when you just want to get to using something isn't the best user experience, and I think in general something we've been trying to reduce. This doesn't need to be must-choice. A checkbox won't hurt, but I am not UX expert. Having that said, this is not a valid point when I suggest not to do the decision for the user. How would that be implemented? What would it apply to? The firstboot script would drop a config value to the user home directory (touch ~/.no-ads) and call some kind of script distributed in a separate package that would re-configure all the programs to opt-out according to this setting. The first one would be Firefox. I am not aware of any other package in Fedora that have ads, but this way we could have a policy how to deal with those. Each package could drop a script that would do the work into let's say /etc/ads-opt-out.d/ or similar. But if you'd ask me to do the decision for the user, I'd definitely respond with no ads. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Enable tapping by default
What can we do to make this happen? I am not interested in tapping at all (I actually hate random clicks and I always disable this), but if you really want to see this, why don't you start a new screen in Gnome to present a selection during the first boot. Maybe Gnome folks will like the idea, maybe not. For myself, one another configuration screen would not be a problem. I'd always go with disable option. Anyway this pretty much answers your question I guess. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Mozilla enabled ads in Firefox and they're active in Fedora
What does the community think of it? Is it okay for our flagship applications to carry ads and report tracking data? Can't we let the user to decide during the firstboot or Firefox first startup? Since browsers already do the opt-out, we could do the same. This global OS setting would then apply on all apps. I believe there will be more than just the Firefox case soon. I will always vote to opt-out, but there are maybe users who do not care. It's even worse. I know people who *want* to see advertisments. To us this sounds like extreme, but let's admit it - we are biased a bit. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Attempting to contact unresponsive maintainer - jomara
I'm planning on being the maintainer. What do I need to do to take over these packages so that the maintainer is no longer considered unresponsive? Some setting for updating the mailing address? Spec update? If you have a chance to contact Jordan he can assign the packages to you in pkgdb easily. If not, I think the process is to orphan them and then pick them up: http://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Orphan packages in rawhide
launchy (maintained by: lzap) launchy-2.5-11.fc22.src requires boost-devel = 1.55.0-4.fc22 I don't understand why this package is included in the list. I still maintain it, it builds fine. Can someone explain? I am short of caffeine. LZ -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Orphan packages in rawhide
It depends on boost which in turn depends on mpich which was orphaned. Oh, I've forced out this option from my mind. Interesting. Well, launchy is not much maintained software and not in wide use. I am fine with orphaning it. Thanks -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: No more deltarpms by default
because it needs to build the complete xz-compressed RPM there was a discussion here not that long ago Is the XZ the only option for RPMs now? Can't it do it uncompressed? Or at least gzip -1. Or Rich can add new feature to his ultra-blazing-fast multi-core XZ decompressor. Compression :-) -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: No more deltarpms by default
Ok I think the above thread explains it, the Jonathan's mail lists what would be needed and it looks like there are some blockers on the infra side. Disregard. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: New Group Calls For Boycotting Systemd
and others integration like crontab should be modular Systemd as cron is something that is built in. If you want a replacement, just install it and don't use this. It's a relatively small feature and it consumes just few kilobytes on your drive. It makes a lot of sense to have this burnt in because you can take control of your jobs from milisecond one. Things like run this two minutes after boot, or when my system is idle, or when an unit is (de)activated. Things like that. Plus in the containers you save one extra process. There is always a threshold between monolithic and modular design. Systemd is not only monolithic, it is modular as well. Some features is in core, some are modules (separate binaries with DBUS API). I think developers found the right threshold for most of the features. Even for chron-like feature there are good reasons. Even if you don't like chron-like features in core, send a patch with compilation option to turn if off. Not sure if maintainers will like it. I'd rather see this feature everywhere but this is solely my opinion. -- Later, Lukas #lzap Zapletal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
GNU GPL licensed alphabet icon set
Hello, our project is looking for a simple GNU GPL v2 (or compatible) licensed icon set with simple icons of all latin letters. Ideally each letter in a circle or square with different background colors for each letter. Something like: http://www.iconarchive.com/show/multipurpose-alphabet-icons-by-hydrattz.html I'd prefer something simple that looks fine in tiny variants (21x21 px). Now, does anyone have a snippet or hack how to generate this with ImageMagick/GIMP/anything from Fedora? Thanks. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: GNU GPL licensed alphabet icon set
On Wed, Jun 25, 2014 at 04:54:36PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
COLORS=(red blue); LABELS=(A B); for N in $(seq 0 1); do convert -size
21x21 xc:${COLORS[$N]} -fill white -pointsize 21 -gravity center -draw
text 0,2 '${LABELS[$N]}' -fill none -stroke white -draw rectangle 0,0
20,20 ${LABELS[$N]}.png; done
Only works in rawhide, but ... wow, brilliant.
Yeah, decent hacking here :-)
It works on F20 for me as well.
Thanks
https://github.com/lzap/foreman-dummy-icons
--
Later,
Lukas lzap Zapletal
irc: lzap #theforeman
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Replace Yum With DNF
It alredy has, it is called dnf-plugins-core all tools in dnf is implemented as plugins there is extending the dnf command line Is there a migration for users and developers document? A page with yum commands on the left and corresponding commands with dnf on the right. Including developer things like scripts from yum-utils (yum-builddep etc). Thanks. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Puppet update and SELinux policy
Hey all, I am going to push the update to stable. There were no reports of misbehavior. In any case, check for AVC denials after Puppet upgrade and relabel system if necessary. LZ On Tue, Apr 22, 2014 at 02:46:33PM +0200, Lukas Zapletal wrote: Hello, we are rolling out update of Puppet to 3.4.3 in Fedora 20 and Rawhide that adds one important change. We have found that puppet master was running unconfined, therefore the Puppet SELinux policy was not effective in Fedoras. The puppet package update fixes one little issue (missing runtime dependency) and corrects startup wrappers for systemd which puts Puppet Master into the correct SELinux domain puppetmaster_t. Since this has some security impact, we have decided to backport this change into Fedora 20 too. https://admin.fedoraproject.org/updates/puppet-3.4.3-3.fc20 Until now, puppet master was running unconfined (this is a regression), the update might need relabelling of the system (/etc/puppet, /var/lib/puppet) or checking out audit.log. Please help me with testing this update: yum --enablerepo=updates-testing update selinux-policy puppet puppet-server Thanks for help. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Puppet update and SELinux policy
Okay, count me in. Is there a BZ already in place for reporting issues or should such reports just go straight to Bodhi, or simply back here? There is this one: https://bugzilla.redhat.com/show_bug.cgi?id=1012426 Thanks a lot. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Fedora 20 Puppet update and SELinux policy
Hello, we are rolling out update of Puppet to 3.4.3 in Fedora 20 and Rawhide that adds one important change. We have found that puppet master was running unconfined, therefore the Puppet SELinux policy was not effective in Fedoras. The puppet package update fixes one little issue (missing runtime dependency) and corrects startup wrappers for systemd which puts Puppet Master into the correct SELinux domain puppetmaster_t. Since this has some security impact, we have decided to backport this change into Fedora 20 too. https://admin.fedoraproject.org/updates/puppet-3.4.3-3.fc20 Until now, puppet master was running unconfined (this is a regression), the update might need relabelling of the system (/etc/puppet, /var/lib/puppet) or checking out audit.log. Please help me with testing this update: yum --enablerepo=updates-testing update selinux-policy puppet puppet-server Thanks for help. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 System Wide Change: Ruby193 in SCL
Stupid question: what in rails depends on v8 exactly? Not sure if this has been answered already, but it's the asset pipeline precompilation, a build requirement. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: F21 System Wide Change: Ruby193 in SCL
This is a great change that actually allows other teams that heavily relies on Fedoras to put their software on hold for two Fedora releases. Fedora is really a fast moving target and the same for Ruby. Catching up costs lot of effort. This gives us usually one extra release to put things on hold when huge changes are in the Fedora/Ruby world. Which is - ehm - every single release? :-) Big up for this change. LZ On Mon, Apr 14, 2014 at 04:16:42PM +0200, Jaroslav Reznik wrote: = Proposed System Wide Change: Ruby193 in SCL = https://fedoraproject.org/wiki/Changes/Ruby193_in_SCL Change owner(s): Marcela Mašláňová mmasl...@redhat.com Ruby 1.9.3 with Rails 3.2.8 is still commonly used by many projects. Let's provide Ruby and Rails in SCL even for Fedora. Rails depends on exact v8 version, which means v8 3.14 must have also their own SCL as part of the SCL. == Detailed Description == Ruby 1.9.3 with Rails 3.2.8 is still commonly used by many projects. This change aims to provide Ruby 1.9.3 and Rails 3.2.8. Rails depends on exact v8 version, which means v8 3.14 must have also their own SCL as part of this change. == Scope == * Proposal owners: Marcela ** create the actual collections, at start in Copr and on SCL upstream [1] * Other developers: Cloud WG ** test SCL with their apps * Release engineering: ** create branches in dist-git ** add Ruby193 packages into compose [1] https://www.softwarecollections.org/en/ ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: SELinux RPM scriplet issue annoucement
One note on that topic: I found myself giving karma to an update, while I tested different version (actually a completely different build). It would be good if giving karma would require to insert a hash or something generated from the package itself (rpm -q -qf something package), header or signature. Portal could check the hash and only accept karma for those users, who obviously installed the package. It could be optional as well. This could prevent mis-giving karma while testing different version of a package. The portal could instruct user to run specific one (short) command to get the hash and to put it in the form. This is just an idea. Question arises when the package consist of multiple subpackage (only to test the base one?) and also how much intrusive this would be for folks. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: SELinux RPM scriplet issue annoucement
that could be easier solved by force anybody to use easy-karma instead the webinterface because that only asks for the current installed packages Oh, I did not know fedora-easy-karma. We should advertise with the update tickets on Bodhi perhaps. Actually this could improve things. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: really stop really commits (really!)
On Mon, Dec 16, 2013 at 03:10:08AM -0700, T.C. Hollingsworth wrote: I do commit locally although I probably don't want push the snapshot sources, because I update them later, when time comes. +1 This should happen rarely enough that having to use `git commit --no-verify` to bypass it wouldn't be too much trouble? I am all for these kinds of checks and I appreciate your effort. These are all good ideas, but please let's do not do this on the git level. This is not appropriate place when we already have a nice layer for this kinds of tests: fedpkg. Every time a maintainer want to build a package using fedpkg, we can add this kind of hooks and verify what is necessary in the similar form you recommend (with the option to skip). Let's build a new command fedpkg check to do explicit checks as well which can help when fixing those mistakes. We do not want to get to the state when packages being committed are automatically being built in koji (using git hooks). Because what you recommend here effectively leads to this happy ending - you might unintentionally seed this kind of approach. I was already there and believe me - this is not what we want to do. :) LZ -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ABRT in the comps group 'standard'
On Fri, Dec 06, 2013 at 01:06:14PM +, Jóhann B. Guðmundsson wrote: My mother would be puzzled, if ABRT would popup on her Fedora box. Your mother will be puzzled with crashing application as well. Better to explain ABRT and have less crashing applications then the opposite. ABRT does not fix the application for his mother We all do fix the application for his mother, after it's reported by ABRT or any other means :-) -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Duplicate review request for rubygem-vagrant
And how vagrant differs from rhc and other client command line tools that are distributed as gems and follow this convention? What I would like to see in both rhc and vagrant would be: Provides: rhc respectively Provides: vagrant It feels natural to me, I have issued yum install rhc several times already. Annoying. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: LVM thin provisioning and virt-manager
On Wed, Oct 16, 2013 at 10:25:30AM +0100, Richard Jones wrote: qemu-img create -f qcow2 -b backing -o preallocation=metadata,compat=1.1 snapshot Backing file and preallocation cannot be used at the same time This is RHEL6, is behavior different now in Fedora? Other options do not work apparently. But it looks like I could pre-allocate metadata on the backing image. Would that help at all? These numbers sound exiting! -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Orphaning Lanuchy
Hello, I want to orphan Launchy, MacOS-like launcher. If you want to adopt, please contact me off-list, thank you. LZ -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: COPR
On Wed, Sep 04, 2013 at 09:04:10AM +0200, Miroslav Suchy wrote: Compare it to Copr and OBS approach, when package is build in VM and after that backend will retrieve the results from VM. So on builder (of OBS and COPR) is no sensitive information at all. Are we able to evaluate, how much slower this is? Currently Fedora Koji is pretty fast, I usually get near-to-instant build pick-ups. I can imagine spawning a VM can be slower. At least when using full QEMU/KVM. I see the point that containers/selinux and such technologies can do better in here. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: f20 systemd rpm isn't signed!
If something goes wrong with systemd, suspicion goes up exponentially (*Jokingly* ;-) -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Merging accounts on ask.fedoraproject.org
On Fri, Aug 16, 2013 at 09:05:34PM +1000, Ankur Sinha wrote: You should be able to click on your profile and then use the manage login methods to merge your logins etc. That works just fine in my case, thanks! -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Merging accounts on ask.fedoraproject.org
Hello, when the site was launched, I used my generic OpenID account, but now I would like to merge also my Fedora OpenID to it. I tried to login using FAS and it just created a new one. Searching around did not reveal any merging possibilities (maybe I am just blind - help me here please). Thanks! -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Relying on $PATH in RPM scriplets + little bit of marketing
On Fri, Jul 26, 2013 at 06:00:04PM +0100, Richard Jones wrote: IMHO there's probably a case for filing a bug with upstream cloud-init and getting them to drop something like: Environment=PATH=[some predictable path] into cloud-init-0.7.2/systemd/cloud-*.service. Oh, good point. Thank you Richard! https://bugzilla.redhat.com/show_bug.cgi?id=990910 Comment Nine thousands to go, whoo! Which reminds me - are we prepared from the marketing perspective? I can imagine Phoronix.com to publish an article Red Hat reaches million bugs. We should have some PR prepared explaining that we track features there (I can imagine writing mostly features there :-) /Comment -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Relying on $PATH in RPM scriplets + little bit of marketing
On Thu, Aug 01, 2013 at 10:06:15AM +0200, Lukas Zapletal wrote: Which reminds me - are we prepared from the marketing perspective? I can imagine Phoronix.com to publish an article Red Hat reaches million bugs. We should have some PR prepared explaining that we track features there (I can imagine writing mostly features there :-) I should think twice before sending an e-mail. The all above applies, but more to Fedora of course: Fedora reaches million bugs. The whole point is: these are not just bugs! ;-) Ok back to work, this only proves that hackers like me are really bad in marketing. LZ -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Relying on $PATH in RPM scriplets
Hey, since we provide cloud images starting with Fedora 19, I noticed that cloud-init, which is used in these, does not execute user shell scripts with $PATH set properly which is causing issues for packages that does not provide full paths in scriplets. I know we have some examples which relies on $PATH set to at least /usr/bin and /sbin, for example: http://fedoraproject.org/wiki/Packaging:UsersAndGroups I am searching for page that says one can rely on the $PATH. Cannot find it. Thanks! -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F20 System Wide Change: Visible Cloud
On Mon, Jul 15, 2013 at 12:22:22PM +0200, Jaroslav Reznik wrote: downloadable cloud images (in qcow2 and raw.xz format) produced and released I know that it is convenient to expose qcow2 images uncompressed so users are able to upload them directly into clouds via httpd. Qcow2 is compressed already by default (is that zlib?) so I am wondering if there is any way of re-compressing the image with -9 option so we are sure the size is the best we can offer. Currently qemu-img does not offer that. Size comparison between qcow2 vs raw.xz shows that there are most likely some gaps we can fill in the qcow2 size. Just throwing in some ideas. Maybe not that relevant for this, I apologize. -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F20 System Wide Change: No Default Syslog
On Mon, Jul 15, 2013 at 01:04:00PM +0200, Miroslav Suchy wrote: Yes, I know. But I spoke about *default*. I would like to have traditional syslog as default. But that does not follow the concept systemd is taking. You are voting against this feature proposal then I guess :-) -- Later, Lukas lzap Zapletal irc: lzap #theforeman -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Orphaning Docky
Hello all, although package Docky was lot of work for me (licensing patching etc) I am no longer using it and last two releases were very unstable. There are couple of bugzillas reported mainly because of gconf migration. Docky is an advanced shortcut bar that sits at the edges of your screen. It provides easy access to some of the files, folders and applications on your computer, displays which applications are currently running, holds windows in their minimized state and more. Docky is written in mono. http://wiki.go-docky.com Please ping me if you are interested to maintain the package. -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora ARM F18 Beta VFAD - Test Images posted
Pardon my ignorance, but where can I find the kernel images? These are just root systems, right? I'd love to try Kirkwood on NSA-310. Thanks! LZ On Mon, Dec 03, 2012 at 12:57:19PM -0500, Paul Whalen wrote: Please join us today (December 3rd, 2012) in #fedora-arm on Freenode for another Fedora ARM VFAD. There are a number of pre-created F18 ARM Beta TC1 images available for testing, including: Pandaboard, Trimslice, vexpress (QEMU) and Kirkwood. Images can be downloaded from: http://scotland.proximity.on.ca/arm-nightlies/vault/f18-beta-tc1/ Please help us track the results by adding your findings to: https://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/2012-12-03-VFAD-Fedora_18_Beta All help is appreciated and we look forward to your participation. Thanks, Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Any progress in Software Center in Fedora effort?
On Sun, Oct 07, 2012 at 06:51:26PM +0200, tim.laurid...@gmail.com wrote: The ultimate software center is a web application, like Google playstore. +1 Why to waste time creating a desktop app when this could be in the cloud already. Plus this could be turned into a desktop web app easily, browser just need to handle links correctly. Remember Lindows with their Click-And-Run (TM) technology? It was a great idea by the way, years before App Store and these kinds of things. http://en.wikipedia.org/wiki/Linspire -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fixing Puppet in Fedora/EPEL
Fedora Infrastructure has begun using ansible for some system setup and other orchestration/automation tasks. Our (just beginning) public repos of it are here: http://infrastructure.fedoraproject.org/cgit/ansible.git/ Just out of my curiosity, is Fedora Infra going to replace Puppet with this, or you are planning to use these two technologies in parallel? Thanks -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fixing Puppet in Fedora/EPEL
On Fri, Oct 19, 2012 at 07:35:28PM -0400, Matthew Miller wrote: * Move EPEL 6, Fedora = 17 to use Puppet 3.0. Speaking for my previous job, it would really be unfortunate to have a non-compatible update of puppet in EPEL. Unless accompanied by very loud trumpets and fireworks beforehand, the day that update went out would be a very sad and busy day for a number of sysadmins. +1 I vote for having puppet3 and not touching the default version. This will be more challenging, but we all know a bit about puppet upgrades and transitions - it can be big pain. -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fixing Puppet in Fedora/EPEL
I'm sure that 2.6 won't last for the life of EL5, let alone EL6. At the same time, I didn't push to get 2.7 in EPEL because it isn't a completely compatible update. And 3.0 was coming so I figured we could wait to see what things looked like when it did. The alternative would have been more updates and more potential to break things and annoy the users who were perfectly happy with how 2.6 was working. (Those that needed the newest shiny or were supporting Fedora 17 could get newer bits from yum.puppetlabs.com.) Yes, but this this is not really necessary. From the EPEL FAQ: *** How long are EPEL packages updated? --- The plan is for EPEL packages to get updates as long as the corresponding RHEL release is supported. That is 10 years after the initial release according to the current errata support policy for 5 and 6 releases. How can we be sure that someone will maintain the packages until end of life of the distribution the packages were built for? - The only way to be sure is to do it yourself, which is coincidentally the reason EPEL was started in the first place. Software packages in EPEL are maintained on a voluntary basis. If you to want ensure that the packages you want remain available, get involved directly in the EPEL effort. More experienced maintainers help review your packages and you learn about packaging. If you can, get your packaging role included as part of your job description; EPEL has written a generic description that you can use as the basis for adding to a job description. We do our best to make this a healthy project with many contributors who take care of the packages in the repository, and the repository as a whole, for all releases until RHEL closes support for the distribution version the packages were built for. That is seven years after release (currently) -- a long time frame, and we know a lot can happen in seven years. Your participation is vital for the success of this project. *** Users have been warned (and asked for help). -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 17 'tig' package update change
Hello, I have noticed that latest tig update in Fedora 17 changed it's behavior. Default key binding is different, j and k keys now automatically change from change-list to change-content, therefore I need to hit the tab key. Annoying, I want the mutt-like behavior back :-) Anyone noticed the change? -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Going to orphan: tritonus
Hey all, I'm going to orphan tritonus package, it's an old java audio api that does not build anymore on Rawhide and getting it working would require too much time on OpenJDK 1.7. Ping me if you are interested in any way. -- Later, Lukas lzap Zapletal #katello #systemengine -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
