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
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.
I just had to setup a new machine, and new ssh keys.
I chose my new id_rsa.pub to upload.
But I get:
git push --verbose
Pushing to ssh://firstname.lastname@example.org/mercurial
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
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
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
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?
I'm sure those that need to know, know, but for those that haven't heard
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?
I've got the misfortune of maintaining a small number of systems that use
the cx18 driver for their HVR-1600 cards; I'm just in the process of
bringing these systems up to Fedora 21, and have discovered that
cx18-firmware was retired.
As I'm going to have to maintain the package for work purposes, I'm
volunteering to maintain it in Fedora for F21 and later. If anyone's
interested in having it available in Fedora, the review request is at:
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
On Fedora <= 21 these packages will have to stay with Coin2 to avoid
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
I've been a bit perplexed by the Fedora updates recently (talking about
F-21 specifically). Many of them appear to be obsolete the moment they
hit stable, sometimes even testing.
Take the kernel, for instance. 3.19.2-201.fc21 replaced the previous
build in bodhi on the 24th. It is still not in testing as I'm writing
this (although the updates system says it is). Take Firefox. Submitted
on 23rd, took 3 days to appear anywhere where "regular" folks can test
it (which is actually stable). Then there are updates (e.g. dovecot)
that have been built in koji, but appear nowhere, probably because
person that built it forgot to submit it.
Can we create a fedora-updates-newbuild repo or something, which would
have a different key used for signing (i.e. not the one where a human
does the signing) and could be accessed using yum pretty much
immediately after the build has been created and flagged to go into this
repo if it succeeds?
So, something like:
fedpkg build --push-to-newbuild
Stoopid? Irrelevant? Exists but I'm not aware of it?