[arch-dev-public] What not to do when packaging (vbetool)
shiningxc at gmail.com
Sun Jan 13 17:23:57 EST 2008
James Rayner wrote:
> On Sun, December 30, 2007 07:02, Dan McGee wrote:
>> Problem here:
>> There are about 4 revisions in a row of this, and none of them had a
>> pkgrel bump. Our dbscripts suck, but it looks like they got messed up
>> parsing the dependencies into the sync DB, leaving a nice little
>> problem on my system:
>> $ testdb
>> missing dependency for vbetool : libx86
>> The package contains the correct deps (zlib and libx86), but the sync
>> db only contains zlib. Thus, my system is "broken" at the moment. We
>> need to be careful when it comes to this kind of situation. If you
>> make a dependency change to a package, you must ensure you bump the
>> pkgrel when changing the PKGBUILD. It isn't the end of the world if
>> the end user doesn't see a built package for every pkgrel bump- that
>> is really for our internal use anyway.
> Oh. It was an update from vbetool 0.7 to 1.0... so I didn't see the need
> for a PKGREL bump. Didn't realise I had to bump it with each commit also
> -- thought it had to just be right for when the final package went up.
Would it be possible to bump this package now then?
I just ran testdb on one of my box, which reminded me of this issue.
More information about the arch-dev-public