devel June 2015

devel@lists.fedoraproject.org

212 participants
250 discussions

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

DNF 1.0.1 Released
by Honza Silhan 04 Feb '16

04 Feb '16

The new release brings fixes of the most occurred errors in Fedora 22. Moreover adds SSL support in repository configuration and random sleep dnf-automatic feature. Read more in 1.0.1 release notes [1] on DNF documentation page, try it from testing and give it a karma. [1] http://dnf.readthedocs.org/en/latest/release_notes.html#id44 [*] http://dnf.baseurl.org/2015/06/12/dnf-1-0-1-released/ Honza by DNF team

9 20

Better irc policies?
by Andreas Tunek 15 Oct '15

15 Oct '15

Currently the #fedora channel on freenode requires some kind of registration. In my opinion it is pretty difficult to register on freenode (I have tried but haven't managed). Do you think it would be possible to drop the registration requirement? It is a pretty big barrier to newbies and people like me who can't find IRC help easily. I know there are a lot of bots and spam, but maybe it would be possible to try and see if it really gets bad? Best regards Andreas

12 28

F23 System Wide Change: Glibc locale subpackaging
by Jan Kurik 02 Sep '15

02 Sep '15

= Proposed System Wide Change: Glibc locale subpackaging = https://fedoraproject.org/wiki/Changes/Glibc_locale_subpackaging Change owner(s): * Mike Fabian <mfabian At redhat DOT com> * Siddhesh Poyarekar <spoyarek AT redhat DOT com> * Carlos O’Donell <codonell AT redhat DOT com> This change should make it possible to install or uninstall locales individually. == Detailed Description == Currently the file /usr/lib/locale/locale-archive contains all locales and is thus huge (103MB). For small systems (and containers) it would be useful to be able to install only a small number of locales. Recently we made it possible to install a small number of locales by supplying the rpm-macro “_install_langs”, for example rpm -i -D _install_langs="en:de_DE" glibc-common.rpm will install all English locales and all German locales which start with “de_DE”, rpm -i -D _install_langs="en_US.utf8" glibc-common.rpm will install only the en_US.utf8 locale, rpm -i -D _install_langs="POSIX" glibc-common.rpm will install nothing (but the POSIX/C is still available because it is builtin into glibc). But this approach works only during an Anaconda based install when Anaconda supplies the _install_langs rpm-macro. When glibc is updated later, the _install_langs macro will not be supplied on the command line during the update and the default value “all” of “_install_langs” from /usr/lib/rpm/macros will be used and all locales come back during an update. Therefore, this solution is far from perfect. It should be made possible to install and uninstall locales individually, for example by having a separate package for the locales for each language. Installing such a package would add these locales to locale-archive, uninstalling it would remove them. Anaconda then needs to be changed to handle such language packages. == Scope == * Proposal owners: 1. Figure out the best approach to to install/uninstall locales 2. Make sure that locales added manually by the user are not destroyed (currently they are lost when glibc is updated) * Other developers: Anaconda needs to be made aware of the new approach to handle installation/uninstallation of locales * Release engineering: I am not sure whether this has affects release engineering, probably the packages in the install image change when parts are split out of glibc-common. * Policies and guidelines: No, this change does not require updates to policies and guidelines. * Trademark approval: not needed for this Change -- Jan Kuřík _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

9 13

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel June 2015