upgrading RH 9 system->Fedora with iso files and apt only
by Didier Casse
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
1 year, 4 months
pdftk retired?
by Michael J Gruber
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
1 year, 8 months
apitrace, bundled libbacktrace
by Sandro Mani
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
5 years, 5 months
Bad default error policy causes printing issues and BIG usability issues
by Valent Turkovic
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?
7 years, 9 months
F21 Self Contained Change: Replace Bacula with Bareos
by Jaroslav Reznik
= 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
8 years, 1 month
Koji build failure: noarch vs. arch?
by Jerry James
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/
8 years, 2 months
DNF and mock
by Miroslav Suchý
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
8 years, 2 months
Packagers: incomplete Obsoletes and undead packages
by Michael Schwendt
This is about Rawhide.
The list for F21 is similar, which is especially strange with regard to
any packages that should be marked as dead in dist git already then.
"Dead" = a dead.package file in dist git exists, but builds of the package
are still found in the repo(s). Package has not been retired fully yet.
"Undead" = no dead.package file in dist git found.
"Only obsolete subpackages" = non-trivial, but for some of those cases
there are really some missing Obsoletes tags and an incomplete set of
builds is left in the repo (e.g. a -devel subpkg but its base pkg is
obsoleted).
[...]
Dead and all builds obsoleted:
------------------------------
drwright
obsoleted by: gnome-settings-daemon
python-twisted-conch
obsoleted by: python-twisted
python-twisted-lore
obsoleted by: python-twisted
python-twisted-mail
obsoleted by: python-twisted
python-twisted-names
obsoleted by: python-twisted
python-twisted-news
obsoleted by: python-twisted
python-twisted-runner
obsoleted by: python-twisted
python-twisted-web2
obsoleted by: python-twisted
python-twisted-words
obsoleted by: python-twisted
qca2
obsoleted by: qca
Undead and all builds obsoleted:
--------------------------------
golang-launchpad-gocheck
obsoleted by: golang-gopkg-check
kopete-cryptography
obsoleted by: kopete
kwallet
obsoleted by: kwalletmanager
lxshortcut
obsoleted by: libfm
mate-dialogs
obsoleted by: mate-desktop
min-metadata-service
obsoleted by: min-cloud-agent
openstack-marconi
obsoleted by: openstack-zaqar
php-channel-deepend
obsoleted by: php-deepend-Mockery
php-channel-symfony2
obsoleted by: php-symfony
php-symfony-icu
obsoleted by: php-symfony
python-XStatic-Angular-Cookies
obsoleted by: python-XStatic-Angular
superiotool
obsoleted by: coreboot-utils
xorg-x11-glamor
obsoleted by: xorg-x11-server
zeroinstall-injector
obsoleted by: 0install
Only obsolete subpackage(s):
----------------------------
kactivities ['kactivities'] 4 left
obsoleted by: kf5-kactivities
left: kactivities-devel
left: kactivities-libs
left: kactivities-nepomuk
left: kactivities-nepomuk-devel
mmdb ['mmdb'] 1 left
obsoleted by: mmdb2
left: mmdb-devel
python-twisted-core ['python-twisted-core'] 1 left
obsoleted by: python-twisted
left: python-twisted-core-doc
razorqt ['razorqt-notifications'] 22 left
obsoleted by: lxqt-notificationd
left: lightdm-razorqt
left: razorqt
left: razorqt-about
left: razorqt-appswitcher
left: razorqt-autosuspend
left: razorqt-config
left: razorqt-data
left: razorqt-desktop
left: razorqt-globalkeyshortcuts
left: razorqt-libs
left: razorqt-libs-devel
left: razorqt-openssh-askpass
left: razorqt-panel
left: razorqt-policykit-agent
left: razorqt-power
left: razorqt-runner
left: razorqt-session
left: razorqt-theme-ambiance
left: razorqt-theme-amego
left: razorqt-theme-green
left: razorqt-theme-light
left: razorqt-themes
ruby-gnome2 ['ruby-gtksourceview2', 'ruby-gtksourceview2-devel'] 24 left
obsoleted by: rubygem-gtksourceview2
left: ruby-bonobo2
left: ruby-bonobo2-devel
left: ruby-bonoboui2
left: ruby-bonoboui2-devel
left: ruby-gconf2
left: ruby-gconf2-devel
left: ruby-gnome2
left: ruby-gnome2-devel
left: ruby-gnomecanvas2
left: ruby-gnomecanvas2-devel
left: ruby-gnomeprint2
left: ruby-gnomeprint2-devel
left: ruby-gnomeprintui2
left: ruby-gnomeprintui2-devel
left: ruby-gnomevfs
left: ruby-gnomevfs-devel
left: ruby-gtkglext
left: ruby-gtkglext-devel
left: ruby-gtksourceview
left: ruby-gtksourceview-devel
left: ruby-libart2
left: ruby-libart2-devel
left: ruby-libglade2
left: ruby-libglade2-devel
8 years, 2 months
