[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#988963: marked as done (libgc1c2: please drop obsolete Conflicts on libgc1)

Your message dated Wed, 4 Aug 2021 20:40:30 +0200
with message-id <957a385f-857d-b7fd-dda3-34618c960067@debian.org>
and subject line Re: Bug#991721: release-notes: mention known RC bugs in bullseye
has caused the Debian Bug report #988963,
regarding libgc1c2: please drop obsolete Conflicts on libgc1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
988963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988963
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: normal
X-Debbugs-Cc: vagrant@debian.org

On numerous systems I have upgraded recently, the process of:

  apt upgrade --without-new-pkgs
  apt full-upgrade

Results in at least one package (guile-2.2-libs, zile, sometimes others)
in an un-upgraded state.

Running a second "apt full-upgrade" seems to take care of the issue.

Maybe upgrading apt in-between "apt upgrade --without-new-pkgs" and "apt
full-upgrade" would resolve the issue?


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 04-08-2021 12:06, Justin B Rye wrote:
> This and #988963 look okay to me [...]
So, closing.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: