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

Groups > linux.debian.user > #255429 > unrolled thread

Debian 11 upgrade to Debian 12

Back to article view | Back to linux.debian.user

Contents

  Debian 11 upgrade to Debian 12 Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-02-28 10:10 +0100
    Re: Debian 11 upgrade to Debian 12 local10 <local10@tutanota.com> - 2023-02-28 13:30 +0100
      Re: Debian 11 upgrade to Debian 12 Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-02-28 19:20 +0100
        Re: Debian 11 upgrade to Debian 12 Jeffrey Walton <noloader@gmail.com> - 2023-02-28 19:40 +0100
        Re: Debian 11 upgrade to Debian 12 Tixy <tixy@yxit.co.uk> - 2023-02-28 19:40 +0100
          Re: Debian 11 upgrade to Debian 12 Greg Wooledge <greg@wooledge.org> - 2023-02-28 21:00 +0100
            Re: Debian 11 upgrade to Debian 12 Tixy <tixy@yxit.co.uk> - 2023-02-28 21:30 +0100
              Re: Debian 11 upgrade to Debian 12 Keith Bainbridge <keith.bainbridge.3216@gmx.com> - 2023-03-01 00:10 +0100
                Re: Debian 11 upgrade to Debian 12 <tomas@tuxteam.de> - 2023-03-01 06:40 +0100
            Re: Debian 11 upgrade to Debian 12 Jeffrey Walton <noloader@gmail.com> - 2023-02-28 21:40 +0100
              Re: Debian 11 upgrade to Debian 12 Jeffrey Walton <noloader@gmail.com> - 2023-02-28 22:10 +0100
              Re: Debian 11 upgrade to Debian 12 Brian <ad44@cityscape.co.uk> - 2023-02-28 22:10 +0100
    Re: Debian 11 upgrade to Debian 12 local10 <local10@tutanota.com> - 2023-02-28 14:20 +0100
    Re: Debian 11 upgrade to Debian 12 piorunz <piorunz@gmx.com> - 2023-03-01 12:10 +0100
    Re: Debian 11 upgrade to Debian 12 songbird <songbird@anthive.com> - 2023-03-03 05:00 +0100
      Re: Debian 11 upgrade to Debian 12 Luna Jernberg <droidbittin@gmail.com> - 2023-03-03 08:50 +0100
      Re: Debian 11 upgrade to Debian 12 local10 <local10@tutanota.com> - 2023-03-03 16:10 +0100
      Re: Debian 11 upgrade to Debian 12 Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-03 17:00 +0100
        Re: Debian 11 upgrade to Debian 12 David Wright <deblis@lionunicorn.co.uk> - 2023-03-17 05:30 +0100

#255429 — Debian 11 upgrade to Debian 12

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

All,

I just updated my media center PC from Debian Bullseye to Debian Bookworm.
The upgrade went alright. I initially had to download almost 2GB of 1640
packages. Around 600 failed to upgrade and I had to manually install them
in small chunks to fix the dependencies. Other than that the upgrade went
relatively smoothly and I am liking the new color scheme and wallpapers.

Anyone else have any good or bad experiences upgrading to bookworm.

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

[toc] | [next] | [standalone]

#255431

Feb 28, 2023, 09:04 by timothy.m.butterworth@gmail.com:

> I just updated my media center PC from Debian Bullseye to Debian Bookworm. The upgrade went alright. I initially had to download almost 2GB of 1640 packages. Around 600 failed to upgrade and I had to manually install them in small chunks to fix the dependencies. 
>

Sounds like you were doing something wrong. Some packages may fail but certainly not 600 of them, at least not the packages that were installed manually. Packages that were auto-installed should not be installed manually.

In my case, about 5 packages had to (re)installed manually when I was upgrading from Debian 11 to 12.

Regards,

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

#255435

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

On Tue, Feb 28, 2023 at 7:24 AM local10 <local10@tutanota.com> wrote:

> Feb 28, 2023, 09:04 by timothy.m.butterworth@gmail.com:
>
> > I just updated my media center PC from Debian Bullseye to Debian
> Bookworm. The upgrade went alright. I initially had to download almost 2GB
> of 1640 packages. Around 600 failed to upgrade and I had to manually
> install them in small chunks to fix the dependencies.
> >
>
> Sounds like you were doing something wrong. Some packages may fail but
> certainly not 600 of them, at least not the packages that were installed
> manually. Packages that were auto-installed should not be installed
> manually.
>
> In my case, about 5 packages had to (re)installed manually when I was
> upgrading from Debian 11 to 12.
>
All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
and that probably would have worked better.

Either way I wanted to try out Plasma Big Screen and it is running alright.
It still needs more polish. I only tested the x11 version and not the
wayland version. I will try the wayland version next.


> Regards,
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

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

#255436

On Tue, Feb 28, 2023 at 1:17 PM Timothy M Butterworth
<timothy.m.butterworth@gmail.com> wrote:
>  [...]
> All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then I ran apt update and apt upgrade. I guess I could have run apt full-upgrade and that probably would have worked better.

Yeah, you were supposed to run full-upgrade before changing
sources.list. https://wiki.debian.org/DebianUpgrade

Jeff

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

#255437

On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
[...]
> All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> and that probably would have worked better.

It would have. If you looked at the release notes [1] it suggests

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

Then lists some possible issues and there remedy.

[1] https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade

-- 
Tixy

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

#255438

On Tue, Feb 28, 2023 at 06:32:27PM +0000, Tixy wrote:
> On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> [...]
> > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> > and that probably would have worked better.
> 
> It would have. If you looked at the release notes [1] it suggests
> 
> # apt upgrade --without-new-pkgs
> # apt full-upgrade
> 
> Then lists some possible issues and there remedy.
> 
> [1] https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade

It's also worth mentioning that in bookworm, non-free firmware has been
moved to a new section called "non-free-firmware".  If you use any of
that -- most people do! -- then you either need to change "non-free" to
"non-free-firmware" or to "non-free non-free-firmware", depending on
your specific needs.

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

#255439

On Tue, 2023-02-28 at 14:52 -0500, Greg Wooledge wrote:
> On Tue, Feb 28, 2023 at 06:32:27PM +0000, Tixy wrote:
> > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > [...]
> > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > > I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> > > and that probably would have worked better.
> > 
> > It would have. If you looked at the release notes [1] it suggests
> > 
> > # apt upgrade --without-new-pkgs
> > # apt full-upgrade
> > 
> > Then lists some possible issues and there remedy.
> > 
> > [1] https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
> 
> It's also worth mentioning that in bookworm, non-free firmware has been
> moved to a new section called "non-free-firmware".  If you use any of
> that -- most people do! -- then you either need to change "non-free" to
> "non-free-firmware" or to "non-free non-free-firmware", depending on
> your specific needs.
> 

That's is the release notes too :-) (I know, there's probably only a
small minority of us who actually read the docs before upgrading.)

-- 
Tixy

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

#255445

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

+1
-- 


All the best 

Keith Bainbridge 

keith.bainbridge.3216@gmail.com 
 0447 667 468

Sent from my Android tablet, Please excuse my brevity..

On 28 February 2023 20:21:40 UTC, Tixy <tixy@yxit.co.uk> wrote:
>On Tue, 2023-02-28 at 14:52 -0500, Greg Wooledge wrote:
>> On Tue, Feb 28, 2023 at 06:32:27PM +0000, Tixy wrote:
>> > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
>> > [...]
>> > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
>> > > I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
>> > > and that probably would have worked better.
>> > 
>> > It would have. If you looked at the release notes [1] it suggests
>> > 
>> > # apt upgrade --without-new-pkgs
>> > # apt full-upgrade
>> > 
>> > Then lists some possible issues and there remedy.
>> > 
>> > [1] https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
>> 
>> It's also worth mentioning that in bookworm, non-free firmware has been
>> moved to a new section called "non-free-firmware".  If you use any of
>> that -- most people do! -- then you either need to change "non-free" to
>> "non-free-firmware" or to "non-free non-free-firmware", depending on
>> your specific needs.
>> 
>
>That's is the release notes too :-) (I know, there's probably only a
>small minority of us who actually read the docs before upgrading.)
>
>-- 
>Tixy
>

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

#255449

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

On Tue, Feb 28, 2023 at 10:20:20PM +0000, Keith Bainbridge wrote:
> +1
> -- 
> 
> 
> All the best 
> 
> Keith Bainbridge 
> 
> keith.bainbridge.3216@gmail.com 
>  0447 667 468
> 
> Sent from my Android tablet, Please excuse my brevity..

Still enough time to advertise products, still.

Cheers
- 
t

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

#255440

On Tue, Feb 28, 2023 at 2:53 PM Greg Wooledge <greg@wooledge.org> wrote:
>
> On Tue, Feb 28, 2023 at 06:32:27PM +0000, Tixy wrote:
> > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > [...]
> > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > > I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> > > and that probably would have worked better.
> >
> > It would have. If you looked at the release notes [1] it suggests
> >
> > # apt upgrade --without-new-pkgs
> > # apt full-upgrade
> >
> > Then lists some possible issues and there remedy.
> >
> > [1] https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
>
> It's also worth mentioning that in bookworm, non-free firmware has been
> moved to a new section called "non-free-firmware".  If you use any of
> that -- most people do! -- then you either need to change "non-free" to
> "non-free-firmware" or to "non-free non-free-firmware", depending on
> your specific needs.

That's a good point. That should be stated in the wiki page at
https://wiki.debian.org/DebianUpgrade .

Would saying "Bookworm and later releases ... <info on non-free
non-free-firmware>" be an accurate statement?

Jeff

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

#255441

On Tue, Feb 28, 2023 at 4:03 PM Brian <ad44@cityscape.co.uk> wrote:
>
> On Tue 28 Feb 2023 at 15:35:43 -0500, Jeffrey Walton wrote:
>
> > On Tue, Feb 28, 2023 at 2:53 PM Greg Wooledge <greg@wooledge.org> wrote:
> > >
> > > On Tue, Feb 28, 2023 at 06:32:27PM +0000, Tixy wrote:
> > > > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > > > [...]
> > > > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > > > > I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> > > > > and that probably would have worked better.
> > > >
> > > > It would have. If you looked at the release notes [1] it suggests
> > > >
> > > > # apt upgrade --without-new-pkgs
> > > > # apt full-upgrade
> > > >
> > > > Then lists some possible issues and there remedy.
> > > >
> > > > [1] https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
> > >
> > > It's also worth mentioning that in bookworm, non-free firmware has been
> > > moved to a new section called "non-free-firmware".  If you use any of
> > > that -- most people do! -- then you either need to change "non-free" to
> > > "non-free-firmware" or to "non-free non-free-firmware", depending on
> > > your specific needs.
> >
> > That's a good point. That should be stated in the wiki page at
> > https://wiki.debian.org/DebianUpgrade .
>
> Well! Get on with it. It's a wiki.

Already done: https://wiki.debian.org/DebianUpgrade

Someone should QA the change.

Jeff

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

#255442

On Tue 28 Feb 2023 at 15:35:43 -0500, Jeffrey Walton wrote:

> On Tue, Feb 28, 2023 at 2:53 PM Greg Wooledge <greg@wooledge.org> wrote:
> >
> > On Tue, Feb 28, 2023 at 06:32:27PM +0000, Tixy wrote:
> > > On Tue, 2023-02-28 at 13:16 -0500, Timothy M Butterworth wrote:
> > > [...]
> > > > All I did was modify /etc/apt/sources.list from Bullseye to Bookworm, then
> > > > I ran apt update and apt upgrade. I guess I could have run apt full-upgrade
> > > > and that probably would have worked better.
> > >
> > > It would have. If you looked at the release notes [1] it suggests
> > >
> > > # apt upgrade --without-new-pkgs
> > > # apt full-upgrade
> > >
> > > Then lists some possible issues and there remedy.
> > >
> > > [1] https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade
> >
> > It's also worth mentioning that in bookworm, non-free firmware has been
> > moved to a new section called "non-free-firmware".  If you use any of
> > that -- most people do! -- then you either need to change "non-free" to
> > "non-free-firmware" or to "non-free non-free-firmware", depending on
> > your specific needs.
> 
> That's a good point. That should be stated in the wiki page at
> https://wiki.debian.org/DebianUpgrade .

Well! Get on with it. It's a wiki.

-- 
Brian.

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

#255432

Feb 28, 2023, 12:24 by local10@tutanota.com:

> Feb 28, 2023, 09:04 by timothy.m.butterworth@gmail.com:
>
>> I just updated my media center PC from Debian Bullseye to Debian Bookworm. The upgrade went alright. I initially had to download almost 2GB of 1640 packages. Around 600 failed to upgrade and I had to manually install them in small chunks to fix the dependencies. 
>>
>
> Sounds like you were doing something wrong. Some packages may fail but certainly not 600 of them, at least not the packages that were installed manually. Packages that were auto-installed should not be installed manually.
>
> In my case, about 5 packages had to (re)installed manually when I was upgrading from Debian 11 to 12.
>

Just to add to the above:

If a package fails to upgrade, use "aptitude show <package>" to find out if the package was automatically installed. If it was then use "aptitude why <package>" to find out what manually installed package requires it, then reinstall that manually installed package, it will automatically install all the dependencies it needs.

Regards,

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

#255450

On 28/02/2023 09:03, Timothy M Butterworth wrote:
> All,
> 
> I just updated my media center PC from Debian Bullseye to Debian 
> Bookworm. The upgrade went alright. I initially had to download almost 
> 2GB of 1640 packages. Around 600 failed to upgrade and I had to manually 
> install them in small chunks to fix the dependencies. Other than that 
> the upgrade went relatively smoothly and I am liking the new color 
> scheme and wallpapers.
> 
> Anyone else have any good or bad experiences upgrading to bookworm.

I could not wait and actually upgraded last year :D Everything went 
fine, I was on typical Testing flow of packages, and bugs were present 
(especially in KDE and Radeon graphics). Now all packages are frozen, 
all bugs I was experiencing are fixed, awaiting final bug fixing and 
eventually official release. 🥰

-- 
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

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

#255529

Timothy M Butterworth wrote:
> All,
>
> I just updated my media center PC from Debian Bullseye to Debian Bookworm.
> The upgrade went alright. I initially had to download almost 2GB of 1640
> packages. Around 600 failed to upgrade and I had to manually install them
> in small chunks to fix the dependencies. Other than that the upgrade went
> relatively smoothly and I am liking the new color scheme and wallpapers.
>
> Anyone else have any good or bad experiences upgrading to bookworm.

  considering it's not released yet and has 331 RC bugs still to
be dealt with (or ignored) that's a bit of a jumping the start
line signal.

  helping to find bugs is good though too.  :)


  songbird

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

#255540

Worked good on my Raspberry Pi 3 with Unstable today too :)

On 3/2/23, songbird <songbird@anthive.com> wrote:
> Timothy M Butterworth wrote:
>> All,
>>
>> I just updated my media center PC from Debian Bullseye to Debian
>> Bookworm.
>> The upgrade went alright. I initially had to download almost 2GB of 1640
>> packages. Around 600 failed to upgrade and I had to manually install them
>> in small chunks to fix the dependencies. Other than that the upgrade went
>> relatively smoothly and I am liking the new color scheme and wallpapers.
>>
>> Anyone else have any good or bad experiences upgrading to bookworm.
>
>   considering it's not released yet and has 331 RC bugs still to
> be dealt with (or ignored) that's a bit of a jumping the start
> line signal.
>
>   helping to find bugs is good though too.  :)
>
>
>   songbird
>
>

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

#255546

Mar 3, 2023, 03:57 by songbird@anthive.com:

> considering it's not released yet and has 331 RC bugs still to
> be dealt with (or ignored) that's a bit of a jumping the start
> line signal.
>
>  helping to find bugs is good though too.  :)
>


It's a pretty decent release nevertheless. Am running Debian 12 Bookworm and it works very well for me despite some minor issues, mostly with KDE.

Regards,

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

#255552

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

On Thu, Mar 2, 2023 at 10:57 PM songbird <songbird@anthive.com> wrote:

> Timothy M Butterworth wrote:
> > All,
> >
> > I just updated my media center PC from Debian Bullseye to Debian
> Bookworm.
> > The upgrade went alright. I initially had to download almost 2GB of 164
0
> > packages. Around 600 failed to upgrade and I had to manually install them
> > in small chunks to fix the dependencies. Other than that the upgrade went
> > relatively smoothly and I am liking the new color scheme and wallpapers.
> >
> > Anyone else have any good or bad experiences upgrading to bookworm.
>
>   considering it's not released yet and has 331 RC bugs still to
> be dealt with (or ignored) that's a bit of a jumping the start
> line signal.
>
>   helping to find bugs is good though too.  :)
>

I have been running Bullseye on my notebook for almost a year with very few
problems. My sound hardware and my WiFi does not work on debian 11. My
notebook is my primary work machine and it has been working well. I look at
testing as a rolling release.  My media center Mini PC is all Intel and
everything on it just works. I wanted to try out KDE Big Screen which is
not available in Debian 11 so I had to upgrade to Debian 12. Big Screen
works ok on Wayland. I think I am missing some application packages though.
The Sound and WiFi buttons just launch a blue screen that never actually
loads. The shutdown button works fine. All in all I like it. I started
removing unneeded software to make it more streamlined. All I really need
is Dolphin, VLC and Elisa. Watch videos and listen to music.



>
>   songbird
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

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

#256115

On Fri 03 Mar 2023 at 10:57:43 (-0500), Timothy M Butterworth wrote:
> On Thu, Mar 2, 2023 at 10:57 PM songbird <songbird@anthive.com> wrote:
> > Timothy M Butterworth wrote:
> > >
> > > I just updated my media center PC from Debian Bullseye to Debian Bookworm.
> > > The upgrade went alright. I initially had to download almost 2GB of 1640
> > > packages. Around 600 failed to upgrade and I had to manually install them
> > > in small chunks to fix the dependencies. Other than that the upgrade went
> > > relatively smoothly and I am liking the new color scheme and wallpapers.
> > >
> > > Anyone else have any good or bad experiences upgrading to bookworm.
> >
> >   considering it's not released yet and has 331 RC bugs still to
> > be dealt with (or ignored) that's a bit of a jumping the start
> > line signal.
> >
> >   helping to find bugs is good though too.  :)
> 
> I have been running Bullseye on my notebook for almost a year with very few
> problems. My sound hardware and my WiFi does not work on debian 11. My
> notebook is my primary work machine and it has been working well. I look at
> testing as a rolling release.  My media center Mini PC is all Intel and
> everything on it just works. I wanted to try out KDE Big Screen which is
> not available in Debian 11 so I had to upgrade to Debian 12. Big Screen
> works ok on Wayland. I think I am missing some application packages though.
> The Sound and WiFi buttons just launch a blue screen that never actually
> loads. The shutdown button works fine. All in all I like it. I started
> removing unneeded software to make it more streamlined. All I really need
> is Dolphin, VLC and Elisa. Watch videos and listen to music.

I just tried upgrading 11→12 on a laptop of mine. The only "snag",
which was no surprise, was being left with a grub.cfg that only boots
the one, upgraded system. That was quickly rectified by grub-mkconfig
after uncommenting GRUB_DISABLE_OS_PROBER=false in /etc/default/grub.
(Thanks for putting that commented line into the file.)

Under bullseye, there were 2015 packages, including libreoffice and
texlive. I run fvwm (now called fvwm2, apparently) with no DE/DM.
It was "pure" Debian except that xtoolwait (from squeeze) was and
still is installed.

Running buster, I copied my bullseye root filesystem to a spare
partition, and adjusted the LABELs in the new copy's fstab.
I booted it up and edited the sources list to bookworm, including
adding the new non-free-firmware.

I ran apt-get update, apt-get upgrade, apt-get --purge autoremove,
apt-get dist-upgrade and apt-get --purge autoremove again, answering
no to keep my configuration files, yes to ignore any bug reports, and
yes to restarting services (including any that might have disconnected
a remote session). It was running on wifi, but I was at the console.

Statistics for the four steps: 627 upgraded and 972 not upgraded;
75 to remove and 968 not upgraded; 967 upgraded, 245 newly installed
and 13 to remove; and 79 to remove. Every thing completed smoothly,
with no dependency problems at all.

I haven't used it in anger as I don't want to disturb my dotfiles etc,
but I checked that sound played perfectly with timidity. Obviously
I've got a number of changes to read up on, with some new packages
to look over.

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web