devel February 2015

devel@lists.fedoraproject.org

221 participants
268 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

whatever happened to yum + btrfs snapshotting?
by Neal Becker 14 Mar '17

14 Mar '17

Some time back there was discussion of being able to rollback yum updates via btrfs snapshotting. As I recall, it turned out that the default btrfs install was not setup correctly to make this feasible (I had briefly tested it on my machine). I haven't heard anything since - this seems like a great idea. -- -- Those who don't understand recursion are doomed to repeat it

7 7

Bad default error policy causes printing issues and BIG usability issues
by Valent Turkovic 01 Sep '15

01 Sep '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

Firefox addon signing
by Michael Cronenworth 30 Aug '15

30 Aug '15

I'm sure those that need to know, know, but for those that haven't heard[1] Mozilla's official Firefox build will enforce addons to contain a Mozilla signature without any runtime option to disable the check. Initially this prevents Fedora packaged addons since they are unsigned. The Mozilla signing process takes time and can't be part of a package building process. Is Fedora going to get authorization to build Firefox with a runtime disable option? [1] https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experien…

25 48

SIMVoleon, SoQt rebuilt against Coin3 on f22 and rawhide
by Ralf Corsepius 14 May '15

14 May '15

Hi, as some already might have noticed, Coin3 is about to land in Fedora. Therefore, I rebuilt SIMVoleon and SoQt (two addon-packages to Coin), against Coin3 on rawhide and f22. I do not expect this to impose problems to Fedora, because I can't spot any packages depending on these in Fedora. On Fedora <= 21 these packages will have to stay with Coin2 to avoid breaking backward-compatibility. Though it's thinkable to do so, I do not plan to provide Coin3-compiled versions of these packages for fc20, f21 and Coin2-compiled versions for fc22, f23, at the moment. Please speak up now, should you have such a demand. Ralf

2 7

New Upstream Release Monitoring Systems
by Ralph Bean 21 Apr '15

21 Apr '15

I'm proud to announce that the Infrastructure team has finished deploying the first iteration of our replacement for the older, wiki-based Upstream Release Monitoring tools this week. You can read about the details of the trio of systems[1] now used to coordinate upstream release monitoring on the same old wiki page. Names of systems: - pkgdb is the familiar Fedora Package DB https://admin.fedoraproject.org/pkgdb It provides some flags used by the other systems. - anitya is the web app running at https://release-monitoring.org It is responsible for scraping upstream release sites looking for new releases. - the-new-hotness is a backend daemon that responds to fedmsg messages about upstream releases. The bugs filed in bugzilla look much the same as they did before, but for packagers there is one thing to note: the process of getting your package(s) registered for upstream release monitoring has changed. Please see the instructions[2] on the wiki page. Old packages that were listed on the wiki page have been imported to release-monitoring.org and have had their monitoring flag set in pkgdb. New packages added to Fedora now have their monitoring flag set to True by default and a script attempts to map them to an upstream project in release-monitoring.org automatically. If you want new upstream releases monitored for your package(s), you must: - Add the upstream project to anitya[3]. - Map the upstream project to a Fedora package in anitya[3]. - Enable the monitoring flag for that Fedora package in pkgdb2[4]. Note also that it is now possible to get notifications about upstream releases without bugs being filed in bugzilla. To do this, add your projects to release-monitoring.org and configure your Fedora Notifications (FMN)[5] account while leaving the monitor flag set to False in pkgdb[4]. If you encounter bugs or have requests for enhancement, as always please do file them[6][7][8].. and if you're having problems with a particular package there is a place to list those[8] also on the wiki page. [1] https://fedoraproject.org/wiki/Upstream_release_monitoring#Details [2] https://fedoraproject.org/wiki/Upstream_release_monitoring#TLDR.3B_Get_Pack… [3] https://release-monitoring.org [4] https://admin.fedoraproject.org/pkgdb [5] https://apps.fedoraproject.org/notifications [6] https://github.com/fedora-infra/anitya [7] https://github.com/fedora-infra/pkgdb2 [8] https://github.com/fedora-infra/the-new-hotness [9] https://fedoraproject.org/wiki/Upstream_release_monitoring#Requesting_Help _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

9 17

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 February 2015