Release number and the repo

[kjpetrie]

Is it possible to rebuild a package but keep the same release number in order to change the package description without forcing everybody to re-install it?

There has been a request in the Software section (http://www.pclinuxos.com/forum/index.php/topic,81755.0.html) to add a note to the VirtualBox packages' repo descriptions as to whether they belong in the guest or the host, and I can see that would make things a lot clearer for newcomers to VirtualBox.

However, this would require a rebuild and then everyone would need to re-install at the next upgrade even though nothing has changed and it would be a complete waste of bandwidth and time. So I'm looking for a way to rebuild and get the description into the repo without forcing the system to conclude the package has been updated.

Would rebuilding without incrementing the release work and, if so, would it be acceptable?

[Was_Just19]

If you did that, no one who has it already installed would see the changes made ......

[Bald Brick]

If you did that, no one who has it already installed would see the changes made ......

I think kjpetrie's point is that nobody who has it already installed needs to see the changes made, while those who are about to install it might benefit from the extra info.

[Was_Just19]

If you did that, no one who has it already installed would see the changes made ......

I think kjpetrie's point is that nobody who has it already installed needs to see the changes made, while those who are about to install it might benefit from the extra info.

Sorry if I misread it ......  then I guess it could be done without any hassle .......  but of course would mean losing track of changes, however slight .....  and if a problem arose would one be able to determine if it was the build or  a different problem?

I wonder what would be the situation with replacing the package on the server ....  could it screw up the mirrors?  I don't know if they would get it or what parameters determine if the package propogates across the mirrors in that situation.

Do you know perchance?

[kjpetrie]

Again, it wouldn't necessarily matter whether the new packages reached the mirrors (which might well vary between mirrors) since they would be functionally identical with the previous ones. What I want to do is revise the description in the package lists to be displayed in Synaptic. Nor is there any reason I can think of not to record the change in the changelog.

The questions I have are:
Would the package lists be updated with the new info?
Where are package checksums kept?
If the new packages didn't propagate onto the mirrors would that upset the checksums?
If it is technically possible, would Texstar approve?

If not, I think the changes are better left until VB next has to be rebuilt for a different reason, as I'm conscious there's quite enough to be downloaded and installed at present without making more.

[Was_Just19]

best to ask Tex directly ...

[Texstar]

Is it possible to rebuild a package but keep the same release number in order to change the package description without forcing everybody to re-install it?

No, you need to bump the number or it will show as an obsolete package. I'd just wait until the next update of Virtualbox OSE before changing the description.