Patching psutils

entodoays · 2015-04-09 06:37:29

According to the developer of Gnome-Manual-Duplex, the official "psutils" package is a very old one and the original developer uses patchsets to improve the utility instead of real version numbers. The "official" package includes files that are dates 1995/1996!

Shouldn't Arch include these patchsets in the package included in the repos? If not, how do I go about patching it? I need Gnome-Manual-Duplex and this requires a patched psutils.

Raynman · 2015-04-09 07:39:08

The Arch package is at version 1 patchlevel 17. That's the latest according to the currently listed homepage. What patches are you after?

runical · 2015-04-09 08:03:28

If I look at the PKGBUILD, I see no patching. However, I don't see any patches on the homepage either. Looking at the source tarball (the one on the arch servers and the official one), I see that all files are from 1997, so I assume that all of the patches are in there (where else?). The makefile provided should do the patching, not the packager. The tarballs also seem to be identical (save the name).

I think the package should be up to date. Your friend should do more research before he comes to the conclusion that "Arch Sucks"

If you really want to know if the package is up to date, contact the maintainer or file a bug. In the meanwhile, ask for help on the AUR page of the gnome-manual-duplex package, as I think that the problem is most likely there.

EDIT: Just realized that he is probably not talking about the patch level from the psutils homepage, but about third party patches. These might be worthwhile, if they are maintained and findable. The probable reason why Arch doesn't have those is that Arch provides vanilla packages without patching. Open a bug report on flyspray (with ALL relevant data!) or create your own PKGBUILD for the patched version.

Last edited by runical (2015-04-09 08:10:30)

tomk · 2015-04-09 08:34:12

runical wrote:

If I look at the PKGBUILD, I see no patching.

Look a bit harder, particularly at lines 18 and 24:
https://projects.archlinux.org/svntogit … es/psutils

But yes, it's clear from your link that the GMD guy is referring to a Fedora patch, not an upstream one.

entodoays · 2015-04-09 08:46:31

I never patched a package yet and never created a PKGBUILD so am lost how to go about it. Searching the wiki seems to indicate that it should:
1. Download the Psutils source package and patch.
2. Use the "patch" command to patch source.
3. Build.
4. Install.

Any help, please?

WorMzy · 2015-04-09 09:06:40

Tomk has linked you to the official PKGBUILD, download that, and modify it to suit your needs.

'man PKGBUILD' if you get stuck.

runical · 2015-04-09 09:11:12

tomk wrote:

runical wrote:
If I look at the PKGBUILD, I see no patching.
Look a bit harder, particularly at lines 18 and 24:
https://projects.archlinux.org/svntogit … es/psutils
But yes, it's clear from your link that the GMD guy is referring to a Fedora patch, not an upstream one.

I saw that. I meant no patching from a different source. Should have been more specific (that patch only seems to change the make paremeters). Sorry for the confusion.

Last edited by runical (2015-04-09 09:11:24)

Raynman · 2015-04-09 09:14:12

WorMzy wrote:

Tomk has linked you to the official PKGBUILD, download that, and modify it to suit your needs.

You could update it to do the patching in prepare().

entodoays · 2015-04-09 11:03:15

So actually I would try to compile it without patching it but compiling it simply with the default paper size set to A4 instead of Letter. That sounds easy. I simply modified the PKGBUILD but it refers to a 'psutils-1.17.diff' which is not found in the sources.archlinux.org. I found it here: https://github.com/KaOSx/main/blob/mast … -1.17.diff. I built the package again, installed it but to no avail. I noticed that the diff file changes A4 to Letter. I tried removing these two lines but buid failed. How do I generate a new diff file without this change?

Raynman · 2015-04-09 11:32:55

That psutils-1.17.diff should be right there with the PKGBUILD (in abs or git if you click "source files" on the webinterface).

To update the patch, I think just leaving the original line (with a4) would work; of course you have to remove the minus sign. Otherwise you'd have to remove everything up to and including those two lines and adjust the "@@ -19,16 +19,16 @@" bit to match. (Or use the command at the top of the .diff file to regenerate it.)

Stefan Husmann · 2015-04-09 20:48:46

Well I tried, neither the Ubuntu nor the Fedora patch even apply without modification.

This PKGBUILD together with this patchfile at least compile. Please try it.

Alad · 2015-04-09 21:20:11

Do you have the issue described in that SF bug report, OP?

I'm also curious as to why you want gnome-manual-duplex in particular, there's e.g duplexpr if your hardware is limited. If you have a driver issue which doesn't let you use the duplex function instead, you should mention it as well.

Last edited by Alad (2015-04-09 21:37:54)

entodoays · 2015-04-11 07:11:36

The developer of Gnome Manual Duplex came up with a workaround that renders the use of a patched psutils probably unnecessary although I'm not 100% sure. For the time being I put this issue on hold.

Arch Linux

#1 2015-04-09 06:37:29

Patching psutils

#2 2015-04-09 07:39:08

Re: Patching psutils

#3 2015-04-09 08:03:28

Re: Patching psutils

#4 2015-04-09 08:34:12

Re: Patching psutils

#5 2015-04-09 08:46:31

Re: Patching psutils

#6 2015-04-09 09:06:40

Re: Patching psutils

#7 2015-04-09 09:11:12

Re: Patching psutils

#8 2015-04-09 09:14:12

Re: Patching psutils

#9 2015-04-09 11:03:15

Re: Patching psutils

#10 2015-04-09 11:32:55

Re: Patching psutils

#11 2015-04-09 20:48:46

Re: Patching psutils

#12 2015-04-09 21:20:11

Re: Patching psutils

#13 2015-04-11 07:11:36

Re: Patching psutils

Board footer