Portage utility: bumper

[Pythonhead]

I wrote a utility for portage named "bumper".

You notice that version 2.0 is out for your favorite software, but portage only has 1.0 (foobar-1.0.ebuild) and you want it now.

bumper will copy the 1.0 ebuild to your portage overlay directory, creating the necessary directories, and name it foobar-2.0.ebuild. It will then create a digest, which will also download the new package. It also copies any non-digest files in ${FILESDIR}.

Its a Python script you can get here:
http://dev.gentoo.org/~pythonhead/bumper/bumper-0.0.10

Usage:

Code: Select all

bumper app-games/pacman-1.0 2.0

Its also useful for simply copying an ebuild from your PORTDIR to your overlay (no version bump) for editing. Just use the same version number:

Code: Select all

bumper apps-foo/boo-1.0 1.0

[pjp]

Moved from Portage & Programming.

[TheCoop]

wouldnt it be better as a bash script?

ie:

Code: Select all

<get PORTAGE_OVERLAY from make.conf using some obsfusticated sed command>
cp $1 overlay/$2 etc /w name changes
ebuild <new ebuild> digest
emerge <ebuild>

why python?

[AgenT]

Neat! I think this calls for a request!

[Pythonhead]

wouldnt it be better as a bash script?

What difference does the language matter as long as it works?

ie:

Code: Select all

<get PORTAGE_OVERLAY from make.conf using some obsfusticated sed command>
cp $1 overlay/$2 etc /w name changes
ebuild <new ebuild> digest
emerge <ebuild>

why python?

Well, thats nice pseudo-code, but my Python psudeo-code looked about the same before I actually wrote the finished code. Look at all the error checking in my code.

Why Python? It sounds better than "bash".

Write in in bash if it'll make you feel better.

[floam]

It kinda pukes with something like:

Code: Select all

bumper app-misc/blah-1.0.1-r1 blah-2.0

It trys to look in app-misc/blah-1.0.1/

[Pythonhead]

It kinda pukes with something like:

Code: Select all

bumper app-misc/blah-1.0.1-r1 blah-2.0

It trys to look in app-misc/blah-1.0.1/

Thanks Floam!

EDIT: Fixed in version 0.0.2, same link in first post.

[floam]

Also gets messed up if people have multiple PORTDIR_OVERLAY's. In recent versions of portage it is legal to do a
PORTDIR_OVERLAY="/usr/local/portage /usr/local/portage2" or similar, which I happen to use. Could the script only use the first directory? Right now it dies with a Couldn't copy file error.

[Pythonhead]

Also gets messed up if people have multiple PORTDIR_OVERLAY's. In recent versions of portage it is legal to do a
PORTDIR_OVERLAY="/usr/local/portage /usr/local/portage2" or similar, which I happen to use. Could the script only use the first directory? Right now it dies with a Couldn't copy file error.

Ok, thanks for the heads up. I didn't know you could use more than one PORTDIR_OVERLAY. It would be easy enough to fix it to check the first one, but let me read up on it and see why people would use two. Was this announced somewhere? I'd like to be a little more informed before I change it.

How does portage use it? Does the first one take precedence over the second?

[floam]

PythonHead: You see a few mentions of it in the portage changelog. The first takes precidence. I use it because I have a script that does some weird stuff there to specific ebuilds and I don't want it affecting my real overlay. People could also use it to sync up with like the breakmygentoo.net development gnome stuff and able to keep it seperate, and stuff like that. It's a very little used feature.

[Pythonhead]

PythonHead: You see a few mentions of it in the portage changelog. The first takes precidence. I use it because I have a script that does some weird stuff there to specific ebuilds and I don't want it affecting my real overlay. People could also use it to sync up with like the breakmygentoo.net development gnome stuff and able to keep it seperate, and stuff like that. It's a very little used feature.

Ok, good enough. I'll go update it to use the first one in the list.

[wizy]

This is great. I do this by hand a lot of the time, thank you.

[Pythonhead]

This is great. I do this by hand a lot of the time, thank you.

Thank you.

Version 0.3 is ready and fixes the multiple overlay directory bug, thanks Floam.

http://abeni.sourceforge.net/ebuilds/bumper-0.3

[floam]

Thanks! Works almost great now One more suggestion, since many ebuilds have patches and stuff they need in the /files/ dir, maybe you should copy that over to overlay as well?

[Pythonhead]

Thanks! Works almost great now :) One more suggestion, since many ebuilds have patches and stuff they need in the /files/ dir, maybe you should copy that over to overlay as well?

Ok, I'll test that out. I'm not sure how well that will work since the names of patches are tied to the version number. It'd be some trick to guess the patch names, since there isn't a standard. If it doesn't work out, I'll have a message showing the files that were copied that aren't digests.

Thanks for the suggestion.

[floam]

Yeah, you can't really be sure itll always work, but just moving /files/ over and then basically s/oldversion/newversion/'ing all the filenames seems like it would work a good percent of the time.

[Pythonhead]

Bumper 0.4 is ready for testing:

From the ChangeLog:

- Changed delimiter for PORTDIR_OVERLAY from space to colon.
http://bugs.gentoo.org/show_bug.cgi?id=10803
http://bugs.gentoo.org/show_bug.cgi?id=26773
- Copy non-digest files from ${FILESDIR}
- More error checking for env vars, warn and exit if no PORTDIR_OVERLAY
- Exits if user isn't root

[asph]

pythonhead rules!
thanks, nice app (also for learning python)

[floam]

Code: Select all

( floam  ~ ) bumper enchant-1.0.0 enchant-1.1.1
Traceback (most recent call last):
  File "/usr/bin/bumper", line 99, in ?
    cat, p = ebuild_from.split("/")
ValueError: unpack list of wrong size

[Pythonhead]

Code: Select all

( floam  ~ ) bumper enchant-1.0.0 enchant-1.1.1
Traceback (most recent call last):
  File "/usr/bin/bumper", line 99, in ?
    cat, p = ebuild_from.split("/")
ValueError: unpack list of wrong size

You should be using this instead:

Code: Select all

bumper app-text/enchant-1.0.0 enchant-1.1.1

I'll fix it so it shows the usage message though, thanks.

[Pythonhead]

Version 0.5 is out and works with newer versions of portage. The code is cleaned up a bit thanks to the use of gentoolkit.py now.

EDIT
0.6 is ready for testing due to major problem in 0.5:

http://dev.gentoo.org/~pythonhead/bumper-0.6

[floam]

I think "0.0.4 - Changed delimiter for PORTDIR_OVERLAY from space to colon." was incorrect. While the portage documentation says a colon should be used, looking in the source shows that it actually uses a space to seperate multiple overlays. Trying to use colons will cause in an error:

Code: Select all

( floam@Aluminium ~ ) emerge -puD world
!!! Invalid PORTDIR_OVERLAY (not a dir): /usr/local/overlays/personal/:/usr/local/overlays/public

[JasonRogers]

2 problems actually.
First, I had to change line#53

Code: Select all

+++ l = os.listdir(package_path)
--- l = os.listdir(pacakge_path)

Second, I get this error trying to bump resin-2.1.9 which is located in net-www/resin

Code: Select all

# bumper net-www/resin-2.1.9 3.0.8
!!! aux_get(): ebuild for 'net-www/resin-resin-3.0.8' does not exist at:
!!!            /usr/portage/net-www/resin-resin/resin-resin-3.0.8.ebuild
Error - Can't find ebuild for net-www/resin-2.1.9

Give the category and ebuild name in this format:
bumper games-arcade/pacman-0.1 0.2

So I thought that perhaps I need to just use 'resin' instead of 'resin-2.1.9', but then I get this error.

Code: Select all

eanus resin # bumper net-www/resin 3.0.8
!!! aux_get(): ebuild for 'net-www/resin-resin-3.0.8' does not exist at:
!!!            /usr/portage/net-www/resin-resin/resin-resin-3.0.8.ebuild
Error - Can't find ebuild for net-www/resin

Give the category and ebuild name in this format:
bumper games-arcade/pacman-0.1 0.2

What's with the '/usr/portage/net-www/resin-resin/resin-resin-3.0.8.ebuild'? Shouldn't it be '/usr/portage/net-www/resin/resin-3.0.8.ebuild'?

[Pythonhead]

I think "0.0.4 - Changed delimiter for PORTDIR_OVERLAY from space to colon." was incorrect. While the portage documentation says a colon should be used, looking in the source shows that it actually uses a space to seperate multiple overlays. Trying to use colons will cause in an error:

Code: Select all

( floam@Aluminium ~ ) emerge -puD world
!!! Invalid PORTDIR_OVERLAY (not a dir): /usr/local/overlays/personal/:/usr/local/overlays/public

Thanks, changed to space.

[Pythonhead]

JasonRogers, sorry, guess I should watch my own threads. I fixed the typo in the latest version:

http://dev.gentoo.org/~pythonhead/bumper/bumper-0.0.8

As for the second problem, I'm not sure what happened, but you may have been caught when they were changing categories? I see resin is in www-servers now, not net-www.