Skip to content

Deprecate dpkg completion#1639

Open
guillemj wants to merge 1 commit into
scop:mainfrom
guillemj:pu/upstream-dpkg
Open

Deprecate dpkg completion#1639
guillemj wants to merge 1 commit into
scop:mainfrom
guillemj:pu/upstream-dpkg

Conversation

@guillemj
Copy link
Copy Markdown

@guillemj guillemj commented Jun 2, 2026

To make it possible for dpkg to provide its own bash completion, the support here needs to be namespaced. In addition, the support for dpkg-reconfigure (which is actually provided by debconf not dpkg), needs to be split.

Because the dpkg completion provides public interfaces used by other completion scripts, the completion imported into dpkg will preserve those public functions for backwards compatibility for now. Ideally bash-completions would switch those functions into another file. But that's left for later to be able to unblock the integration with the next dpkg upstream release 1.23.8.

Fixes: #694

@guillemj
Copy link
Copy Markdown
Author

guillemj commented Jun 2, 2026

Sorry, just noticed now that this was against the now stale master branch, will rebase tomorrow against main instead and force push.

@akinomyoga
Copy link
Copy Markdown
Collaborator

We've already moved those files so that no conflicts happen. This PR seems to rename non-existent files, though I'm not sure why GitHub interface doesn't report conflicts. You base on an old commit between 2.13.0--2.14.0. If you intend to submit a patch to a certain version packaged in a distribution, could you please submit the patch to the package maintainer? If you intend to submit it here, could you please rebase the branch on top of the latest main branch and re-examine the changes that you try to add?

To make it possible for dpkg to provide its own bash completion, the
support here needs to be namespaced. In addition, the support for
dpkg-reconfigure (which is actually provided by debconf not dpkg),
needs to be split, as well as the support for alternatives which is
an old fork from the dpkg updates-alternatives.

Because the dpkg completion provides public interfaces used by other
completion scripts, the completion imported into dpkg will preserve
those public functions for backwards compatibility for now. Ideally
bash-completions would switch those functions into another file.

Fixes: scop#694
@guillemj guillemj force-pushed the pu/upstream-dpkg branch from c9290bb to f3997df Compare June 2, 2026 02:51
@guillemj
Copy link
Copy Markdown
Author

guillemj commented Jun 2, 2026

We've already moved those files so that no conflicts happen. This PR seems to rename non-existent files, though I'm not sure why GitHub interface doesn't report conflicts. You base on an old commit between 2.13.0--2.14.0. If you intend to submit a patch to a certain version packaged in a distribution, could you please submit the patch to the package maintainer? If you intend to submit it here, could you please rebase the branch on top of the latest main branch and re-examine the changes that you try to add?

Right, see my comment which seems crossed at the same time as yours. I've now rebased it and force pushed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dpkg integration upstream

2 participants