[Aptitude-devel] Bug#819943: really should add an unforbid-version command

[Manuel A. Fernandez Montecelo]

2016-04-05 04:09 積丹尼 Dan Jacobson:
>So indeed in the man page
>
>           To remove the forbidden version without installing the
>           candidate version, the current version should be appended: "install
>           <package>=<version>".
>
>
>is utterly totally wrong. Please remove it.


  # aptitude search --disable-columns -F '%c%a%M %p %v %V' debian-keyring
  i  debian-keyring 2016.01.20 2016.03.22

  # aptitude forbid-version debian-keyring=2016.03.22
  No packages will be installed, upgraded, or removed.
  0 packages upgraded, 0 newly installed, 0 to remove and 185 not upgraded.
  Need to get 0 B of archives. After unpacking 0 B will be used.

  # aptitude search --disable-columns -F '%c%a%M %p %v %V' debian-keyring
  iF debian-keyring 2016.01.20 2016.03.22

  # aptitude install debian-keyring=2016.01.20
  debian-keyring is already installed at the requested version (2016.01.20)
  debian-keyring is already installed at the requested version (2016.01.20)
  No packages will be installed, upgraded, or removed.
  0 packages upgraded, 0 newly installed, 0 to remove and 184 not upgraded.
  Need to get 0 B of archives. After unpacking 0 B will be used.
  Current status: 185 (+1) upgradable.

  # aptitude search --disable-columns -F '%c%a%M %p %v %V' debian-keyring
  i  debian-keyring 2016.01.20 2016.03.22

Q.E.D.

I.e., works as intended and documented.


>set debian-reference-en
>aptitude forbid-version $@
>aptitude search $@ #shows F
>aptitude install $@=2.59 # abort with n, we don't want to install it.
>aptitude search $@ #still F

Exactly, because by saying "n" you didn't complete the action to "remove
the forbid on that version".

Installing a version that it's already installed is harmless, so you
don't need to say no.

So again it works as expected and documented.  You wouldn't want the
state modified if you reply "no" to a question to modify the state, that
would be a much more serious bug.


>Please change it to
>
>           Currently there is no way to remove the forbidden version without installing the
>           candidate version.
>
>Or better
>
>           Currently there is no way to remove the forbidden version NOTATION without installing the
>           candidate version.

Nope.


Also, more in general, it would be useful if you stop reporting
duplicate bugs reported only weeks ago (often by you, e.g. 773023 and
804103) or looking for unexisting problems, then discussing to death and
looking for further things to modify in the same bug report so they can
never be closed.

That keeps maintainers wasting time chasing and handling bug reports
rather than working on more important problems, and wasting time
repeating again and again the reasons why they don't want to change
things that you suggest.

If the reason why you don't try to avoid duplicate bugs is
"but... but... there are too many!", consider whether your actions
submitting dozens of inane bugs or duplicates to aptitude without
searching for them is contributing to piling lots of bugs that then are
difficult to triage and search; or if they are of any benefit to the
advancement of aptitude as a whole to deal with these inane and
duplicate reports rather than working on more important issues.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>