On 05/11/2015 08:45 AM, M. Fioretti wrote: I don't think, these questions can be answered in "broad generality". The decision on whether to upgrade or to reinstall depends on various factors, esp. on a system's configurations, customizations and the installer's technical skills. Both approaches have pros and cons, there is no "black and white". In simple, mostly non-customized (single-user desktop) installations re-installing often is easy. To "new-comers" and less Linux-skilled people it often is "much simpler" In complex (multi-user, networked, "enterprize") installations, upgrading often is easier, because recreating/restoring your configuations can easily take a lot of time. That said, I personally almost always upgrade and rarely "re-install". Ralf

On 11/05/15 16:45, M. Fioretti wrote: I generally do not upgrade but install new. I run 2 partitions on my hd, one has the previous version and the other the new install. I then install latest versions of the apps I need then copy my working files over to the new install. This way I have the backup for a few months, then overwrite that with the next fresh install. It's worked that way for a few years now. Roger

On Mon, 11 May 2015 12:28:25 -0700 stan <stanl-fedorauser(a)vfemail.net&gt; wrote: Or, why not at EOL, simply make the updates use fedup or equivalent move to the next Fedora. THis can not be that difficult to set up. Ranjan ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth

On Tue, 12 May 2015 13:20:15 +0930 Tim <ignored_mailbox(a)yahoo.com.au&gt; wrote: Agreed: but aren't updates are always with the user's consent, unless explicitly enabled with the -y option? For instance on yum or dnf: we get: ..... Total download size: 465 M Is this ok [y/d/N]: Btw, perhaps this thread should be called something else, other than "Biting the bullet" that is not obvious to what the discussion on Fedora is. Ranjan ____________________________________________________________ FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium

On Mon, 11 May 2015 23:07:33 -0700 Joe Zeff <joe(a)zeff.us&gt; wrote: Thanks! This trailer is added by inbox.com (the mailer) as you can see in the signature. I have no control over what they add and would ignore such things in others e-mail trailers also. Having said that, it would be disappointing. I really like inbox.com. Compared to the big mailers, they do not mine e-mails (as per their statement) and above all, they are fast. Ranjan ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth

M. Fioretti wrote: Briefly, No. Surely we all have enough space on our disks nowadays to create a new partition, and install the new version there? This gives you a safety net, as you can go back to the old version, if things don't work out. Also, you can copy /etc/hosts and similar (with some care) from the old version. I did this recently, with an ancient computer (Thinkpad T43), which I'd left in another house for a couple of years, and which was running an old version of Fedora, I think Fedora-16. I was quite surprised it still seems to work fine - the internal speaker is much louder than any of its successors, so it's better for listening to the news, etc. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

On 05/11/2015 12:45 AM, M. Fioretti wrote: Well, for one thing, installing from scratch requires possibly a large number of config files, which would require remembering which ones they are, search for them in the backup and overwrite the newly installed config files, or worse: merge them into the new config files, or go through a painful edit to see what setting from the old make sense in the new, since not all settings in the old would make sense in the new. Just my $.02's worth.

On Mon, 2015-05-11 at 16:08 +1200, Rolf Turner wrote: Not to be snarky, but if upgrading terrifies you then perhaps Fedora is not the right distro for your needs. Regular updating is part of the Fedora mindset. The system is designed to be updated at least once a year. You should be wary of the consequences of *not* updating, especially in regard to security. Having said that, note that the reports of disasters are in a sense self-selecting. People complain when they have problems, but mostly keep quiet when they don't (there are exceptions of course). Personally I've not had any significant issues updating Fedora, which I do literally on a daily basis for patches, and within a week or two of each new release coming out. poc

On Mon, 2015-05-11 at 16:33 +0100, Tethys wrote: As I said, that is definitely not my experience. Upgrades rarely break anything major and problems with new releases tend to get fixed quickly. poc

On Mon, May 11, 2015 at 5:53 PM, Ralf Corsepius <rc040203(a)freenet.de&gt; wrote: It's not the upgrading process that's the problem. It's that the newer software tends to be broken in anything but the default configuration. I upgraded my girlfriend's desktop to F21 and it's literally unusable now. She has to use her laptop instead (which is also barely usable due to unwanted UI changes forced onto end users). Modern Linux is becoming like Apple - "we know what's best for you, and if you don't like that, you're wrong". Tet -- "Java is a DSL for taking large XML files and converting them to stack traces" -- Bulat Shakirzyanov

On 05/11/2015 10:16 AM, Tethys wrote: I don't agree. My F21 boxes are ANYTHING but default and they work just fine. They're part desktop, part server, part development systems, part experimental hamsters, part whatever-the-h*ll-I-need-at-the- moment. You get the idea. Granted, it took some work to get them working like _I_ want them (and I'm a nerd), but they do work well and they're all fedups from F20. That being said, I did do a raw install of F20 on a couple of them because they were updated from F16 up to F18 or F19. Many things changed and there were enough crumbs left over from those updates that it made sense to start from scratch. Thus I backed them up, blew the old stuff into the ether, installed F20 from scratch and put back the stuff I needed that aren't parts of the distro. I did have to do a bunch of recompilations because the libraries my binaries relied on changed. Note that I absolutely detest the idiotic systemd and journalctl packages (stupid, overly complex solutions for perceived problems that never really existed) and I think Gnome3 is a huge mistake. Perhaps it's OK on tablets or touchscreens, but it is SO far removed from the original Gnome and such an inexcusable resource hog that I refuse to use it and use XFCE4 instead. Mate is another viable desktop option. These are my opinions and I know I'll get blasted for them, but that's the way I see it. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Lottery: A tax on people who are bad at math. - ----------------------------------------------------------------------

Btw, I have packaged stapler and PyPDF2 for my personal use. Am very happy with them. In fact, I feel that stapler is a bit better than pdftk for me. Unfortunately, the name stapler conflicts with something else that is also on the F21 repos, so I am not sure how to proceed. O/w I would have submitted to the F repos. Ranjan ____________________________________________________________ Share photos & screenshots in seconds... TRY FREE IM TOOLPACK at http://www.imtoolpack.com/default.aspx?rc=if1 Works in all emails, instant messengers, blogs, forums and social networks.

I am sorry I do not quite understand. I presume that you mean that one should rename stapler (my packaged version) to something else. I tried doing this in the spec file. But it never worked because the spec file looks for that something else then. I could not figure out how to fix this so just created the file for my personal use. If you or someone else would like to take a look, here it is: fpaste pdf-stapler.spec Uploading (2.4KiB)... http://ur1.ca/kckv7 -> http://paste.fedoraproject.org/221087/14400891 Yes this is correct. I even wrote to the author Philip Stark asking if he would mind changing the name to avoid conflicts with this other stapler. As an author and user of software, I feel that it is useful to have clearly defined names. (Besides, the name "stapler" does not quite do justice to the full capabilities of the software.) Anyway, he said he would if I came up with a good name so I suggested a bunch, but he never responded after that. Btw, you will need PyPDF2 for which I have a working rpm (again a personal copy, no naming issues there) which I can provide to you. How do I submit this PyPDF2 to BZ? Many thanks. Ranjan -- Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses. ____________________________________________________________ Can't remember your password? Do you need a strong and secure password? Use Password manager! It stores your passwords & protects your account. Check it out at http://mysecurelogon.com/manager

Are you sure? It would make more sense to call it pdf-stapler or something similar to specify its utility. After all, this is not going to be used as a library. Is this considered to be a python module? I was thinking that it is more like an application, such as batti. Yes, I have talked to both. (Btw, Philip Stark **is** hellerbade.) The forks have now been merged back (but for one issue) according to Fred Wenzel. I read somewhere that I have to do some GPG signing? This does not appear to be on this webpage above. Also, can the files be submitted to BZ itself or does this have to be loaded somewhere else? Ranjan ____________________________________________________________ Can't remember your password? Do you need a strong and secure password? Use Password manager! It stores your passwords & protects your account. Check it out at http://mysecurelogon.com/manager

On Tue, May 12, 2015 at 10:19:39PM +0200, Suvayu Ali wrote: Actually, please keep the upstream tarball name; renaming it shouldn't be necessary. Also, the guidelines contain a recipe for source from github: https://fedoraproject.org/wiki/Packaging:SourceURL#Github What you'll need is to provide the _original_ name to the %setup macro. In this case, that'd be '%setup -q -n stapler'. It kind of depends. That is the case for python _modules_ — packages intended to be used by other python programs. However, this is a utility which happens to be written in Python — it doesn't need that prefix (but you _could_ do that). There a number of other issues in the spec file currently — I'll address them separately. -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On 06/19/2015 10:16 PM, Ranjan Maitra wrote: Very likely, errors in 1. the spec file, or 2. the tar source file(s), or 3. the patch file(s).

Kevin, Thanks! On Sat, 20 Jun 2015 09:49:39 -0600 Kevin Fenzi <kevin(a)scrye.com&gt; wrote: I tried the workaround, and was able to build PyPDF2 on f22, f23 and rawhide. However, pdf-stapler failed to build on f22 and f23, but was successful on rawhide. Where does one find the build.log? Here is the URL for the failed build on F22: http://koji.fedoraproject.org/koji/taskinfo?taskID=10170443 Many thanks and best wishes, Ranjan ____________________________________________________________ FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium

On Sun, Jun 21, 2015 at 07:52:11AM -0500, Ranjan Maitra wrote: [...chomp...chomp...chomp...] Look at the parent build: http://koji.fedoraproject.org/koji/taskinfo?taskID=10170444 + /usr/bin/python setup.py build RPM build errors: /var/tmp/rpm-tmp.6OGjea: line 31: /usr/bin/python: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.6OGjea (%build) Seems like it cannot find python, which is odd since any Fedora installation should have it, yum/dnf is written written in python! Hope this helps, -- Suvayu Open source is the future. It sets us free.

On Sun, 21 Jun 2015 08:03:47 -0600 Kevin Fenzi <kevin(a)scrye.com&gt; wrote: OK, does this mean that we have to wait for Philip Stark to bring out stapler under python3 (which he plans to do -- I can ask him about progress)? But isn't it odd that it builds under rawhide but not under f22 or f23. Ranjan ____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!

On Sun, 21 Jun 2015 08:18:09 -0600 Kevin Fenzi <kevin(a)scrye.com&gt; wrote: Thanks! The builds went through: on to the next item: now that koji has built it, what do I do for package review? Do I still have to put it up somewhere? Many thanks, Ranjan ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth

OK, BZ review requests are in for pdf-stapler: https://bugzilla.redhat.com/show_bug.cgi?id=1234210 and for PyPDF2: https://bugzilla.redhat.com/show_bug.cgi?id=1234208 Currently, pdf-stapler is set to run using pyPdf which exists on Fedora, but I am not comfortable with it, because the software creator explicitly requires PyPDF2. Hence, the second entry to allow for this to be included. (However, pdf-stapler appears to work fine with pyPdf.) Many thanks and best wishes, Ranjan ____________________________________________________________ Can't remember your password? Do you need a strong and secure password? Use Password manager! It stores your passwords & protects your account. Check it out at http://mysecurelogon.com/password-manager

Matthew, Thank you very much! This was very helpful and a learning experience (and you are right, I copied stuff from files here and there and did Hail-Mary passes to see which worked, sorry. I don't really have a lot of time to learn all this. Anyway, I decided to go with pdf-stapler. (Though Philip Stark did not respond to my suggestions, I think something like pdfsmelter or pdfforge or pdfblender pdfsynthesizer or pdfripper would have been more appropriate given that the software does much more than electronically staple pdf's.) I guess the so-called easiest way involves me writing to Phil. I have done that. Let us see what he says. I am not completely sure about this but this may become clearer once a decision is made on whether to go for the snapshot package or not. Btw, I have also posted the PyPDF2.spec (since that is also essential to this package). (I started by copying and modifying the SuSE spec file and then changed stuff to go with your e-mail here. I am not sure if I got everything.) $ fpaste PyPDF2.spec Uploading (2.6KiB)... http://ur1.ca/kx26j -> http://paste.fedoraproject.org/221361/43149204 Many thanks again! Best wishes, Ranjan ____________________________________________________________ Receive Notifications of Incoming Messages Easily monitor multiple email accounts & access them with a click. Visit http://www.inbox.com/notifier and check it out!

Hi, I have been working on this again, but am unable to compile: Here is the file: $ fpaste pdf-stapler.spec Uploading (2.2KiB)... http://ur1.ca/ml5wc -> http://paste.fedoraproject.org/224474/43224459 Here are the errors I get: $ rpmbuild -bb pdf-stapler.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.5e1XxN + umask 022 + cd /home/maitra/rpmbuild/BUILD + cd /home/maitra/rpmbuild/BUILD + rm -rf stapler-0.3.0 + /usr/bin/gzip -dc /home/maitra/rpmbuild/SOURCES/stapler-0.3.0.tar.gz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd stapler-0.3.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.0eE4rq + umask 022 + cd /home/maitra/rpmbuild/BUILD + cd stapler-0.3.0 + /usr/bin/python3 setup.py build running build running build_py creating build creating build/lib creating build/lib/staplelib copying staplelib/commands.py -> build/lib/staplelib copying staplelib/stapler.py -> build/lib/staplelib copying staplelib/tests.py -> build/lib/staplelib copying staplelib/iohelper.py -> build/lib/staplelib copying staplelib/__init__.py -> build/lib/staplelib running egg_info writing requirements to stapler.egg-info/requires.txt writing stapler.egg-info/PKG-INFO writing top-level names to stapler.egg-info/top_level.txt writing entry points to stapler.egg-info/entry_points.txt writing dependency_links to stapler.egg-info/dependency_links.txt reading manifest file 'stapler.egg-info/SOURCES.txt' writing manifest file 'stapler.egg-info/SOURCES.txt' + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.eg4I03 + umask 022 + cd /home/maitra/rpmbuild/BUILD + '[' /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64 '!=' / ']' + rm -rf /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64 ++ dirname /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64 + mkdir -p /home/maitra/rpmbuild/BUILDROOT + mkdir /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64 + cd stapler-0.3.0 + /usr/bin/python3 setup.py install -O1 --skip-build --root /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64 running install running install_lib creating /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr creating /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib creating /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4 creating /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages creating /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib copying build/lib/staplelib/commands.py -> /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib copying build/lib/staplelib/stapler.py -> /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib copying build/lib/staplelib/tests.py -> /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib copying build/lib/staplelib/iohelper.py -> /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib copying build/lib/staplelib/__init__.py -> /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib byte-compiling /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/commands.py to commands.cpython-34.pyc File "/usr/lib/python3.4/site-packages/staplelib/commands.py", line 33 print input['name'] ^ SyntaxError: Missing parentheses in call to 'print' byte-compiling /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/stapler.py to stapler.cpython-34.pyc File "/usr/lib/python3.4/site-packages/staplelib/stapler.py", line 79 print "Mode: %s" % mode ^ SyntaxError: Missing parentheses in call to 'print' byte-compiling /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/tests.py to tests.cpython-34.pyc byte-compiling /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/iohelper.py to iohelper.cpython-34.pyc File "/usr/lib/python3.4/site-packages/staplelib/iohelper.py", line 36 print "The password did not match." ^ SyntaxError: Missing parentheses in call to 'print' byte-compiling /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/__init__.py to __init__.cpython-34.pyc writing byte-compilation script '/tmp/tmpzhfhibts.py' /usr/bin/python3 -O /tmp/tmpzhfhibts.py File "/usr/lib/python3.4/site-packages/staplelib/commands.py", line 33 print input['name'] ^ SyntaxError: Missing parentheses in call to 'print' File "/usr/lib/python3.4/site-packages/staplelib/stapler.py", line 79 print "Mode: %s" % mode ^ SyntaxError: Missing parentheses in call to 'print' File "/usr/lib/python3.4/site-packages/staplelib/iohelper.py", line 36 print "The password did not match." ^ SyntaxError: Missing parentheses in call to 'print' removing /tmp/tmpzhfhibts.py running install_egg_info running egg_info writing entry points to stapler.egg-info/entry_points.txt writing top-level names to stapler.egg-info/top_level.txt writing requirements to stapler.egg-info/requires.txt writing stapler.egg-info/PKG-INFO writing dependency_links to stapler.egg-info/dependency_links.txt reading manifest file 'stapler.egg-info/SOURCES.txt' writing manifest file 'stapler.egg-info/SOURCES.txt' Copying stapler.egg-info to /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/stapler-0.3.0-py3.4.egg-info running install_scripts Installing stapler script to /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/bin + install -m 755 -d /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64//usr/sbin + ln -s ../bin/eject /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64//usr/sbin + mv /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64//usr/bin/stapler /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64//usr/bin/pdf-stapler + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /home/maitra/rpmbuild/BUILD/stapler-0.3.0 /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match. find: 'debug': No such file or directory + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/brp-compress + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 Bytecompiling .py files below /home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4 using /usr/bin/python3.4 *** Error compiling '/home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/commands.py'... File "/usr/lib/python3.4/site-packages/staplelib/commands.py", line 33 print input['name'] ^ SyntaxError: Missing parentheses in call to 'print' *** Error compiling '/home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/iohelper.py'... File "/usr/lib/python3.4/site-packages/staplelib/iohelper.py", line 36 print "The password did not match." ^ SyntaxError: Missing parentheses in call to 'print' *** Error compiling '/home/maitra/rpmbuild/BUILDROOT/pdf-stapler-0.3.0-1.fc22.x86_64/usr/lib/python3.4/site-packages/staplelib/stapler.py'... File "/usr/lib/python3.4/site-packages/staplelib/stapler.py", line 79 print "Mode: %s" % mode ^ SyntaxError: Missing parentheses in call to 'print' error: Bad exit status from /var/tmp/rpm-tmp.eg4I03 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.eg4I03 (%install) WHat is wrong? Thanks, Ranjan ____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!

On Fri, 2015-05-22 at 00:13 -0400, Kevin Cummings wrote: AFAIK the former would be valid in Python 2, but things changed with Python 3. poc

Never mind, I read your comment backwards. Indeed, this looks like a python2 vs python3 problem. On 05/22/2015 04:53 PM, Kevin Cummings wrote: -- Kevin J. Cummings kjchome(a)verizon.net cummings(a)kjchome.homeip.net cummings(a)kjc386.framingham.ma.us Registered Linux User #1232 (http://www.linuxcounter.net/)

On Fri, May 22, 2015 at 02:26:38PM +0200, Suvayu Ali wrote: There's actually just been a policy change on this: In Fedora we have multiple python runtimes, one for each supported major release. At this point that's one for python2.x and one for python3.x. If a piece of software supports python3, it must be packaged for python3. If it supports python2 as well, it may be packaged for python2. If it supports only python2 then it must not be packaged for python3. There _is_ an (unreleased?) python 3 port at <https://github.com/hellerbarde/stapler/tree/python3port>;, which could be used, but it's probably best to just consider this the last case, "only supports python2", and use "BuildRequires: python2-devel" -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Fri, May 22, 2015 at 08:59:15AM -0500, Ranjan Maitra wrote: Getting close! Basically, everything put into place by %install needs to be listed in %files. For these particular files, see: https://fedoraproject.org/wiki/Packaging:Python_Eggs The short version is that "%{python2_sitelib}/*" should catch this. Why is this still here? :) -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Fri, May 22, 2015 at 09:54:07AM -0500, Ranjan Maitra wrote: Hmmm, first thing here — you're asking for python3-devel but calling %{__python} (which is currently %{__python2}) instead of % %{__python3}, and you're using the python2 sitelib. [...] We actually have pyPdf in the distro. However, it's 1.13. Try: at the top of the file: %define pypdfversion 1.13 requires line: Requires: pyPdf = %{pypdfversion} (no need for BuildRequires), and then put this after %setup for f in setup.py stapler.egg-info/requires.txt ; do sed -i 's/pypdf == 1.12/pypdf == %{pypdfversion}/g' $f done Having made these changes, your specfile works for me and pdf-stapler appears to run — at least, it does not crash. -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Fri, May 22, 2015 at 10:46:02AM -0500, Ranjan Maitra wrote: Possibly? It should be transparent, according to the FAQ: <http://mstamy2.github.io/PyPDF2/FAQ.html#migration-from-pyPdf> However, this actually presents its _own_ problem, since there's no good way to package that in a way that lets people switch between them. I would suggest seeing if pdf-stapler works fine with pypdf 1.13, and hopefully it does, and then following (or helping with, since it seems stuck!) <https://bugzilla.redhat.com/show_bug.cgi?id=991102>;, which suggests that Fedora replace pyPdf with PyPDF2 completely. -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Fri, May 22, 2015 at 11:46:31AM -0500, Ranjan Maitra wrote: Add to the bug is probably best, since other interested people are already there. Cool :) -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Fri, May 22, 2015 at 06:25:21PM -0500, Ranjan Maitra wrote: A lot of these things come from volunteers -- in fact, even when it's people paid to work on Fedora for one reason or another, some of these packages are just because we think they're a good idea or fun or whatever, not the thing we're paid for, so that's volunteer effort. Which is a long way of saying, sometimes things just get stalled. Sometimes just "hey, I'm still interested!" can help. Failing that, offering to help yourself. :) Yeah, looks like it'l have to be made for both in order to accommodate pdf-stapler, until pdf-stapler is updated to 3. -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Fri, May 22, 2015 at 09:30:55PM -0500, Ranjan Maitra wrote: So this gets to an advanced RPM packaging topic -- subpackages. The same source RPM can produce two (or more) separate binary (or noarch) RPMs, one python2 and one python3. Right now, it's all python 2. I don't know the state for the future. It's not very many, though: $ dnf repoquery --whatrequires pyPdf krop-0:0.4.7-1.fc22.noarch pdfposter-0:0.6.0-3.fc21.noarch pdfshuffler-0:0.6.0-5.fc21.noarch python-mwlib-0:0.15.14-1.fc22.x86_64 python-xhtml2pdf-0:0.0.5-2.fc21.noarch -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

My experience with Fedora has been really good. I've run FreeBSD, Slackware and SUSE over the past 18 years and Fedora is the easiest to install and upgrade. I installed Fedora 20 on my little Dell Optiplex from an image on a flash drive and then used fedup to upgrade to 21 and then again to upgrade to the alpha of 22 and now using dnf to keep upgrading. It is very stable, have not had any problems yet. Chris in Austin, TX

On 05/12/2015 04:25 PM, Roger wrote: Yup! Me too. And, I've been known to skip various versions because I saw too many problems on the support forums I follow. The one I remember best was F10, which was getting reports of install/upgrade problems right up until it hit EOL.

Would it be possible to build a static "R" binary on a more recent Fedora distribution then use binary the binary on your Fedora 17 machine(s)? On Mon, May 11, 2015 at 12:08 PM, Rolf Turner <r.turner(a)auckland.ac.nz&gt; wrote:

On 11.05.2015, Rolf Turner wrote: Fedora upgrade mostly works fine upgrading one or two versions. But upgrading from F17 to 21? Do yourself a favour and install from scratch. It will save you a lot of hassle.

On Mon, May 11, 2015 at 04:08:23PM +1200, Rolf Turner wrote: This document exists at https://fedoraproject.org/wiki/FedUp -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader

On Mon, 11 May 2015, Rolf Turner wrote: The last version I succesfully installed was F17. I've never used FedUP, so do not know how reliable it is. Absent an upgrade, you will need to chase down the undefined references and define them. The source might have suggestions. zip uses deflate. Its source might be useful. FedUp appears to be an answer. I would need to trust it a lot to use it on an irreplaceable installation. Copy /home and /etc to external storage. Put empty filesystems on them. If /home is not already a separate partition, make it so: From a live disk: mount F17's / read-only as /F17-slash mount a partition with an empty filesystem as /home-new cd /F17-slash/home ; cp -a * .[^.]* ..?* /home-new To make F17 use it, would require editing /F17-slash/etc/fstab /F17-slash would have to be remounted writeable Boot the install disk. Tell anaconda you want a custom install. Do not tell it to format any partitions. / and /var should be separate, previously empty partitions. /home should be your /home partition. If you are lucky, all your ~/.configuration-whatever files will still be useable by their respective applications. If you run into trouble with global configuarations, the contents of the old /etc might be some help. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods