Public bug reported:
Binary package hint: dpkg
Bug #153132 brought this to my attention.
I use Ubuntu. Bug #153132 covers a menial splash screen change in
openoffice.org-kde, a package I don't have since I don't use Kubuntu.
Other packages in the openoffice.org series got a simple rebuild from
the updating of openoffice.org-kde.
Although nothing changed (according to the changelog), I still had to
update the entire openoffice.org series. My understanding indicates
this patch did not affect me at all on the source code and toolchain
flag/version level; but rather, only users of openoffice.org-kde, and
only via the openoffice.org-kde package. I spent a good deal of
bandwidth applying a non-update.
Users on slow links may not enjoy this so much, not when 200MB of
updates have to come down a 128K ISDN line because a file in a 200KB
package got updated.
I suspect without toolchain or header file changes, updates would only
affect a limited number of files in a limited set of packages generated
by a build. Why does dpkg not support a patch process that can generate
patch debs based on binary comparison (whole files, not binary patching;
though binary patching might improve things further when one line of
code gets a change)?
** Affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
--
Massive, meaningless updates
https://bugs.launchpad.net/bugs/155329
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
