Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.devel.testing > #1272 > unrolled thread

Bug#988003: Bullseye upgrade report

Started byPaul Gevers <elbrus@debian.org>
First post2021-05-13 22:10 +0200
Last post2021-05-14 16:50 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.debian.devel.testing

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#988003: Bullseye upgrade report Paul Gevers <elbrus@debian.org> - 2021-05-13 22:10 +0200
    Bug#988003: Bullseye upgrade report Paul Gevers <elbrus@debian.org> - 2021-05-14 07:20 +0200
      Bug#988003: Bullseye upgrade report Jose Caban <asskoala@gmail.com> - 2021-05-14 16:50 +0200

#1272 — Bug#988003: Bullseye upgrade report

FromPaul Gevers <elbrus@debian.org>
Date2021-05-13 22:10 +0200
SubjectBug#988003: Bullseye upgrade report
Message-ID<CepOF-7uv-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hi Jose,

Thank you for reporting your issues.

On 03-05-2021 17:29, Jose Caban wrote:
>   No, though guile-2.2-libs is apparently held back.

Is this still the case? Do you know *why* it's kept back? I downloaded
the plexmediaserver, but it's doesn't have any dependencies, so that
can't be it.

I checked the list of reverse dependencies of guile-2.2-libs, but none
of the packages in your list has been upgraded. I didn't check yet if
all those reverse dependencies are newer in bullseye.

Can you check which packages depend on guile-2.2-libs?
paul@mulciber ~ $ sudo apt remove guile-2.2-libs --simulate

Paul

paul@mulciber ~ $ reverse-depends guile-2.2-libs -l
aisleriot
autogen
denemo
dico-module-guile
gnubik
guile-2.2
guile-2.2-dev
guile-cairo
guile-g-wrap
guile-gnome2-glib
guile-gnome2-gtk
guile-gnutls
guix
gwave
libgwrap-runtime2
meep
meep-mpi-default
meep-openmpi
xbindkeys

[toc] | [next] | [standalone]


#1273

FromPaul Gevers <elbrus@debian.org>
Date2021-05-14 07:20 +0200
Message-ID<CeyoW-4rQ-3@gated-at.bofh.it>
In reply to#1272

[Multipart message — attachments visible in raw view] — view raw

Hi Jose,

Bear with me, this is my first time really digging into an upgrade report.

On 14-05-2021 02:03, Jose Caban wrote:
> I was able to get past it by doing a “dist-upgrade”, I thought it was my
> fault and that's what google said.

Hmm, you already did an $(apt full-upgrade) which *should* take care of
it. Did you use apt-get when you ran the "dist-upgrade"? Did any
packages get removed in the dist-upgrade process?

> I've attached the output from that command, seems as though it can be
> removed? I'm not sure what pulled it in.  If there's anything else I
> can do to help, please let me know.

I wouldn't do that, either this stack, or the alternative one going to
be installed while removing are needed by other pieces on your system. I
don't see any reason why you'd want to make the switch.

Paul

[toc] | [prev] | [next] | [standalone]


#1275

FromJose Caban <asskoala@gmail.com>
Date2021-05-14 16:50 +0200
Message-ID<CeHix-17Q-5@gated-at.bofh.it>
In reply to#1273

[Multipart message — attachments visible in raw view] — view raw

So when I did the dist-upgrade, the only thing to get changed was guile
upgrading itself, I don’t recall anything else changing.

I did it shortly after the full upgrade.

Yeah I’m not touching it. It’s my programming/NAS/ source code server box
so I just need that sucker to be reliable.

—J

On Fri, May 14, 2021 at 01:14 Paul Gevers <elbrus@debian.org> wrote:

> Hi Jose,
>
> Bear with me, this is my first time really digging into an upgrade report.
>
> On 14-05-2021 02:03, Jose Caban wrote:
> > I was able to get past it by doing a “dist-upgrade”, I thought it was my
> > fault and that's what google said.
>
> Hmm, you already did an $(apt full-upgrade) which *should* take care of
> it. Did you use apt-get when you ran the "dist-upgrade"? Did any
> packages get removed in the dist-upgrade process?
>
> > I've attached the output from that command, seems as though it can be
> > removed? I'm not sure what pulled it in.  If there's anything else I
> > can do to help, please let me know.
>
> I wouldn't do that, either this stack, or the alternative one going to
> be installed while removing are needed by other pieces on your system. I
> don't see any reason why you'd want to make the switch.
>
> Paul
>
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.devel.testing


csiph-web