devel January 2015

devel@lists.fedoraproject.org

257 participants
265 discussions

Outage Notification - 2009-07-01 01:00 UTC
by Mike McGrath 24 Aug '23

24 Aug '23

There will be an outage starting at 2009-07-01 01:00 UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2009-07-01 01:00 UTC' Affected Services: Buildsystem CVS / Source Control Unaffected Services: Database DNS Fedora Hosted Fedora People Fedora Talk Mail Mirror System Torrent Translation Services Websites Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/1496 Reason for Outage: Final migration step for new cvs server. It will hopefully be offline for only 30-45 minutes. The additional time is for some further tuning if needed and some verification steps. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. _______________________________________________ Fedora-devel-announce mailing list Fedora-devel-announce(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce

2 1

upgrading RH 9 system->Fedora with iso files and apt only
by Didier Casse 17 Jan '22

17 Jan '22

I have the yarrow's iso files on my HD in a RH9 system. Let's say I want to upgrade selected packages using an "apt-get install" pointing to my iso-mounted files, how do I do it? i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc.. Then what is the complete procedure to make my apt look into my own HD to upgrade packages. Can anybody redirect me to the correct resource or some literature hanging on the web? Thanks. Assume also that I do not wish to burn CDs! I do not want to use apt-cdrom. Thanks. With kind regards, Didier. --- PhD student Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: slsbdfc at nus dot edu dot sg \or\ didierbe at sps dot nus dot edu dot sg Website: http://ssls.nus.edu.sg

6 9

pdftk retired?
by Michael J Gruber 08 Sep '21

08 Sep '21

I just git a "broken dependencies" notice for a package that I maintain. The reason is that "pdftk" got retired just the other day. I may have missed a corresponding post on fedora-devel, but I think a heads up notice to maintainers of depending packages may be in order before you retire a package, as a general idea. You see, unretiring a package is so much more work than changing maintainership. As for pdftk: I see 2 failed builds for version 1.45 and none for the current version 2.02 (which probably breaks the api anyways). What are the plans? Retire pdftk completely? Start fresh with pdftk2? pdflabs, the maker of pdftk, provide binary as well as source rpms for pdftk 2.02, by the way. I might even look into packaging it but don't want to duplicate any existing efforts. Michael

17 26

git push permission denied
by Neal Becker 10 Feb '21

10 Feb '21

I just had to setup a new machine, and new ssh keys. I visited https://admin.fedoraproject.org/accounts/user/edit/xxxx I chose my new id_rsa.pub to upload. But I get: git push --verbose Pushing to ssh://nbecker@pkgs.fedoraproject.org/mercurial Permission denied (publickey). fatal: The remote end hung up unexpectedly Hints?

4 5

apitrace, bundled libbacktrace
by Sandro Mani 17 Dec '17

17 Dec '17

Hi, apitrace 5.0 bundles libbacktrace, which looks like is living within the gcc sources. libbacktrace is not build as a shared library from the gcc sources, and not packaged. Is it feasible to build libbacktrace as a shared library and ship it in a corresponding package? Or should I rather go for a bundling exception request? Thanks, Sandro

8 9

Bad default error policy causes printing issues and BIG usability issues
by Valent Turkovic 31 Aug '15

31 Aug '15

Hi, currently default error policy for printers in Fedora is "Stop printer" on any error which is a really bad default. I have run across this issue LOTS of times with regular Fedora desktop users who don't get why has their printer stopped working, there is no UI queue to warn users, there is no easy way to "Start printer" with one click after it has been stopped. It is just a big mess. Even worse, previous versions of Gnome control panel (if I remember correctly) had option to change default error policy, now that option is removed and you can get to it only by installing system-config-printers tool, something regular users have no idea about even exists, and it is not installed by default. There are too many examples which are simple user errors but result in priner going offline (stopped) and this is really bad, because after any small error users can't print any more. For example: user trying to print while he/she is not at home so his/hers printer is not available, user trying to print but has forgot to connect usb priner cable, user trying to print but haven't turned it on, user printing to wifi printer but while connected to different wifi network... Any of these actions is simple uses error but results in permanently disabling of priner (Stops printer) and users can't print even when they resolve issue that was stopping them from accessing the printer. Now Fedora is what is stopping them from printing. Who is responsible for user experience of Fedora desktop? To whom should I point this issue to?

4 5

DNF 0.6.0 Released
by Ales Kozumplik 10 Apr '15

10 Apr '15

Hello, New minor version was released yesterday. All summed up on our blog: http://dnf.baseurl.org/2014/08/12/dnf-0-6-0-released/ Cheers, Ales

2 5

F21 Self Contained Change: Replace Bacula with Bareos
by Jaroslav Reznik 09 Apr '15

09 Apr '15

= Proposed Self Contained Change: Replace Bacula with Bareos = https://fedoraproject.org/wiki/Changes/Bareos Change Owner(s): Simone Caronni <negativo17 at gmail.com> The powerful Bacula network backup solution has switched from being Open Source friendly to being almost closed source. Originally the project was conceived totally as Open Source, but since the creation of Bacula Systems and its proprietary Bacula Enterprise Edition product, the Open Source (now called "Community Edition") has received less and less updates and is mostly abandoned. == Detailed description == The most important points that are left "abandoned" are the following: * Installation scripts and updates to makefiles are not updated anymore. * New plugins and functionalities are not added anymore, except those in the "core" daemons. * Gaphical (and buggy) console has not received any update in almost two years. * Patches and bugs opened in the bug tracker are mostly left abandoned. Even trivial fixes are not imported in the source. * Windows binaries are no longer provided, nor the source for the clients has been updated. Even if compiled with difficulties, there is no support for recent Windows versions. A former Bacula developer, frustrated by the situation created the fork Bareos a long time ago from Bacula 5.2.x (the current Fedora and RHEL 7 version). This version has now received '''a lot of bugfixes''' compared to the original Bacula source. This makes compilation and installation a lot easier than it was with Bacula. On top of this, a '''lot of new features''' have been added; some unique to Bareos but many available only in the closed source Bacula Enterprise. Here is the list of new features compared to the current Bacula 5.2.13: * http://www.bareos.org/en/whats_new.html Some highlights include NDMP support for enterprise class storage (NetApp, etc.), support for enterprise class tape libraries and Windows support (including Windows Server 2012) with Bareos generated binaries. For further details on why a Bacula fork was created please look at the following links: * http://www.bareos.org/en/faq/items/why_fork.html Bareos can also be '''fully compatible with Bacula''' by setting a specific configuration directive in the Daemon configuration files; thus providing the option for RHEL 6/7 users to interoperate with Fedora systems. * http://www.bareos.org/en/faq/items/bareos_bacula_compatibility.html == Scope == To accomplish the goal, the following Bacula packages need to be replaced with Bareos equivalents: bacula bacula-docs Currently, the same Fedora packages can be rebuilt as they are, to work also on CentOS/RHEL 5 and 6, upgrading the EPEL or official Bacula packages in the distributions. This is to have a consistent backup infrastructure across all the Fedora/CentOS/RHEL ecosystem. To ease installation, a repository for installing those packages on a CentOS/RHEL system do exist: http://repos.fedorapeople.org/repos/slaanesh/bacula/README.txt The idea is the same for Bareos: import into Fedora 21 packages that can be rebuilt for all supported Fedora/RHEL/CentOS releases and provide a repository that can upgrade any Bacula release currently installed in the system with the new one. In detail; the upgrade scenarios supported when going from Bacula to Bareos would be: From Bacula 2.4: * RHEL/CentOS 5 with EPEL repository From Bacula 5.0: * RHEL/CentOS 6 From Bacula 5.2.13: * Fedora 18+ * RHEL/CentOS 5 * RHEL/CentOS 6 As written before, the change is impacting only Fedora 21, the list of upgrades supported are only for users who want a consistent backup solution across the enterprise. === External activities === Proposal owners: I'm the current Bacula mantainer in Fedora and will complete the transition in time for the release. Other developers: N/A (not a System Wide Change) Release engineering: the release engineering team should make sure the new Bareos packages are in place instead of the current Bacula packages for the new release. Policies and guidelines: N/A (not a System Wide Change) _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

6 8

Koji build failure: noarch vs. arch?
by Jerry James 29 Mar '15

29 Mar '15

I just had a weird failure on a koji builder: http://koji.fedoraproject.org/koji/taskinfo?taskID=8776617 The SRPM creation step failed, with this output: error: parse error in expression error: /builddir/build/SPECS/libpuma.spec:119: bad %if condition Building target platforms: noarch Building for target noarch Child return code was: 1 EXCEPTION: Command failed. See logs for output. It is complaining about this line in the spec file: %if %{__isa_bits} == 64 and, from the mention of noarch, my guess is that the complaint is triggered because whatever is doing the parsing thinks this is a noarch package. It is not. It is an archful package, with a noarch -doc subpackage. What component is doing this parsing? Was it changed recently? Because that same construct in the spec file didn't cause a problem the last time I built this package. Also, the package builds without trouble in mock. Thanks, -- Jerry James http://www.jamezone.org/

7 16

DNF and mock
by Miroslav Suchý 16 Mar '15

16 Mar '15

I just spoke with two members of DNF team about default usage of DNF in mock. I would like to share outcomes of this meeting. First I would like to state that you can already optionally use DNF in your mock by setting: config_opts['package_manager'] = 'dnf' in your /etc/mock/site-defaults.cfg It is present in mock for half a year and all known problems have been resolved for some time. You can even set this option per chroot target. E.g. put this line only in /etc/mock/fedora-rawhide-x86_64.cfg and then only rawhide-x86_64 builds will use dnf while everything else will use yum. DNF should be default packager manager in Fedora 22, so I started thinking how it affects mock. I have a notion, that after branching of Fedora 22 I will change /etc/mock/fedora-rawhide-*.cfg to use DNF by default. I.e. everything build for Fedora 23 would use DNF for building. At the outset I thought that we use yum for older targets (epel-7, fedora-22..) indefinitely. Or to be precise until those targets will be EOLed. But that would imply that yum have to be present in Fedora until Fedora 40 [1]. This is very unlikely to happen. More realistic expectation is that yum will disappear around Fedora 27 [2]. Which means that in Fedora 27 you either will be unable to build packages for epel-7 or you will have to use DNF. This is quite distant future and we will try our best to make this transition as much flawless as possible. I just want to make you aware in advance. Of course if you want to help, you are very welcome. I expect that we will be building Fedora 22- always by yum due to short Fedora life cycle. Yum will be still present in Fedora 24 for sure. [1] https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates [2] It’s Difficult to Make Predictions, Especially About the Future -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

13 30

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel January 2015