Re: spam filtering question?

[Jonathan Dowland]

On Fri, Dec 09, 2016 at 10:27:50PM -0500, Karen Lewellen wrote:
> shellworld.net the shell service where I do most of my internet work is
> using Ubuntu.
> For reasons that I  find rather confusing spam assassin  is well no longer
> filtering at the level it did previously.
> Has something happened to the program ?

Most likely the volume or nature of the spam you are receiving has changed,
rather than the filters. If the SpamAssassin instance has the bayesian 
classifier
enabled (you might be able to tell by the headers it adds to your mail), then
it may learn some traits from the more recent spam, if there is a feedback loop
in place for you to report spam.

> Is there a better spam filtering option for shell servers that I might
> suggest to our administrator?

I find crm114 to be excellent. Depending on precicely how the shell server has
mail setup, you might be able to set it up for yourself, running on top of the
service offered by the shell service, as an additional layer of filtering.


signature.asc
Description: Digital signature

Re: LVM RAID vs LVM over MD

[Jonathan Dowland]

On Tue, Dec 06, 2016 at 10:53:30AM +1100, Igor Cicimov wrote:
> It depends. If you are using cloud services with remote shared storage like
> AWS EBS it does not make sense using LVM on top of RAID. To me it is just
> adding complexity to already complex SAN storage. You also have no idea
> what the block devices presented to the VM are coming from it might be a
> file coming over iSCSI. I've been using LVM raid on AWS EBS for years
> without any issues. My advice is test and match them all before you make
> your decision each ones user case and experience is different.

I should have prefixed my answer with "If you want RAID...". I don't
personally use RAID anywhere, myself, at the moment.

In the situation you describe then you are doing logical volume management
elsewhere and you would indeed not need LVM. You should also address redundancy
at that other layer so you wouldn't need (local) RAID either, either LVM or MD
based, IMHO.

You don't explain why you chose to use LVM RAID over mdadm, but as I said, I
wouldn't use either in your case.

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

understanding how localization works in Debian

[Martin T]

Hi,

I read the "Configuring the System for Another Language" paragraph in
"The Debian Administrator's Handbook" and am I correct that
localization works in a way that:

1) pam_env.so sets the environmental variables seen in the output of
locale command based on configuration files(for example
/etc/default/locale) when user logs in

2) nl_langinfo(), setlocale() and (some) other glibc functions used in
programs ask environment variables seen in the output of locale
command

3) based on those environment variables nl_langinfo(), setlocale(),
etc functions check the locale information in
/usr/lib/locale/locale-archive database and change their output
accordingly

4) /usr/lib/locale/locale-archive database is generated with
locale-gen utility based on entries in /etc/locale.gen file and locale
template/configuration files in /usr/share/i18n/locales/

Did I understand this correctly?



thanks,
Martin

Re: network setup

[Brian]

On Sun 11 Dec 2016 at 19:43:06 -0500, Jude DaShiell wrote:

> I tried manual network configuration and debian renamed wlan0 to
> wlx00c0ca364bd2 for some reason.  If I do ip a that shows up as possible
> wifi connection.  Unfortunately ifup doesn't recognize that device name.

It is unclear (to me, at least) what you are trying to achieve and with
what tools. Would you please say whether you are trying to configure a
*single* wireless connection or is roaming involved?

-- 
Brian.

How to upgrade / compile an ARM kernel?

[Robert Latest]

Hi all,

I have this old hardkernel odroid-u2 chugging away as a slow but
reliable mediaserver. It's a few years old and uses a Debian Wheezy  I
downloaded from Hardkernel's site.

I now wanted to connect a two-bay USB/SATA adapter, but the odroid
only sees one of the drives. Maybe it's something else, but probably
it's just due to an old kernel / udev. So I dist-upgraded to jessy but
got stuck halfway because the kernel is too old (3.0.57). Soon I found
out that upgrading the kernel isn't as straightforward as on i386,
first because of the (probably pretty simple) uboot loader, and
secondly because there is a large variety of ARM SoC flavors, each of
which requires its own kernel.

So any tips? Am I even on the right path that the "invisibility"
of one of the SATA drives is due to the old kernel /udev?

I'm willing to build a new kernel for this thing. Last time I did that
was probably literally almost 20 years ago. Also I'll probably need
some sort of serial adapter, as the only way I currently communicate
with this thing is via ssh; i.e., if the kernel won't boot I won't
know why.

Any tips?

Thanks,
robert


rl@odroid:~$ cat /proc/cpuinfo
Processor: ARMv7 Processor rev 0 (v7l)
processor: 0
BogoMIPS: 1992.29

processor: 1
BogoMIPS: 1992.29

processor: 2
BogoMIPS: 1992.29

processor: 3
BogoMIPS: 1992.29

Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x3
CPU part: 0xc09
CPU revision: 0

Hardware: ODROIDU2
Revision: 
Serial: 
rl@odroid:~$ dmesg | head
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.0.57 (root@linaro-ubuntu-desktop) (gcc
version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #12 SMP Mon Jun 3
00:09:36 UTC 2013
[0.00] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
[0.00] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[0.00] Machine: ODROIDU2
[0.00] Memory policy: ECC disabled, Data cache writealloc
[0.00] CPU EXYNOS4412 (id 0xe4412220)
[0.00] exynos4_init_clocks: initializing clocks
[0.00] S3C24XX Clocks, Copyright 2004 Simtec Electronics
rl@odroid:~$

Re: understanding how localization works in Debian

[Greg Wooledge]

On Mon, Dec 12, 2016 at 01:58:12PM +0200, Martin T wrote:
> 1) pam_env.so sets the environmental variables seen in the output of
> locale command based on configuration files(for example
> /etc/default/locale) when user logs in

Maybe, maybe not.  The LC_* and LANG variables can come from many
different places.  I think, however, that you are focusing on the
libc/application level that uses these variables, and not their
origin.  So for your purposes, "LC_* and LANG are set somehow".

> 2) nl_langinfo(), setlocale() and (some) other glibc functions used in
> programs ask environment variables seen in the output of locale
> command
> 
> 3) based on those environment variables nl_langinfo(), setlocale(),
> etc functions check the locale information in
> /usr/lib/locale/locale-archive database and change their output
> accordingly
> 
> 4) /usr/lib/locale/locale-archive database is generated with
> locale-gen utility based on entries in /etc/locale.gen file and locale
> template/configuration files in /usr/share/i18n/locales/
> 
> Did I understand this correctly?

I am confused.  There are basically three interaction points between
you and the locale system, and you don't seem to have focused on any
of them.

1) LC_* and LANG are set somehow by the end user or by the local OS.

2) The local system admin runs "dpkg-reconfigure locales" to determine
   which locales are "generated".  End users can only receive translations
   from locales that are generated on the local system.

3) Applications are written with localization (l10n) support using the
   features of whichever language they're written in, e.g. _("...").

For a more detailed look at #1, see https://wiki.debian.org/Locale
(And even that is woefully incomplete thanks to the proliferation
of Desktop Environments, and the ridiculous inadequacy of the PAM
environment variable system.)

For a more detailed look at #3, see
https://www.gnu.org/software/gettext/manual/gettext.html

Re: How to upgrade / compile an ARM kernel?

[Eike Lantzsch]

On Monday, 12 December 2016 14:20:45 PYST Robert Latest wrote:
> Hi all,
> 
> I have this old hardkernel odroid-u2 chugging away as a slow but
> reliable mediaserver. It's a few years old and uses a Debian Wheezy  I
> downloaded from Hardkernel's site.
> 
> I now wanted to connect a two-bay USB/SATA adapter, but the odroid
> only sees one of the drives. Maybe it's something else, but probably
> it's just due to an old kernel / udev. So I dist-upgraded to jessy but
> got stuck halfway because the kernel is too old (3.0.57). Soon I found
> out that upgrading the kernel isn't as straightforward as on i386,
> first because of the (probably pretty simple) uboot loader, and
> secondly because there is a large variety of ARM SoC flavors, each of
> which requires its own kernel.
> 
> So any tips? Am I even on the right path that the "invisibility"
> of one of the SATA drives is due to the old kernel /udev?
> 
> I'm willing to build a new kernel for this thing. Last time I did that
> was probably literally almost 20 years ago. Also I'll probably need
> some sort of serial adapter, as the only way I currently communicate
> with this thing is via ssh; i.e., if the kernel won't boot I won't
> know why.
> 
> Any tips?
Yes, this question seems to be better placed at
debian-...@lists.debian.org
and you might be better off with a minimal image of Jessie for odroid and then 
do a fresh install IMHO. It's the faster path.

Nvidia legacy 340 package was removed?

[tier]

What we will use insted?

Using EasyCAP USB video capture device

[rhkramer]

Is anyone here using the EasyCAP USB video capture device?

If so, what software are you using?  (I want to capture video and audio.)

Comments / suggestions?

(I have one of these, but I haven't tried using it so far...)

Re: Nvidia legacy 340 package was removed?

[Teemu Likonen]

tier [2016-12-12 21:18:22+06] wrote:

> What we will use insted?

Nvidia 340 is still in Jessie as package nvidia-driver but it is also in
jessie-backports as package nvidia-legacy-340xx-driver. Here's what my
system tells:

$ apt-cache policy '^nvidia-(legacy-[0-9]+xx-)?driver$'

nvidia-driver:
  Installed: 367.57-2~bpo8+1
  Candidate: 367.57-2~bpo8+1
  Version table:
 *** 367.57-2~bpo8+1 0
100 http://ftp.fi.debian.org/debian/ jessie-backports/non-free amd64 
Packages
100 /var/lib/dpkg/status
 340.96-1 0
500 http://ftp.fi.debian.org/debian/ jessie/non-free amd64 Packages
nvidia-legacy-340xx-driver:
  Installed: (none)
  Candidate: 340.98-1~bpo8+1
  Version table:
 340.98-1~bpo8+1 0
100 http://ftp.fi.debian.org/debian/ jessie-backports/non-free amd64 
Packages
nvidia-legacy-304xx-driver:
  Installed: (none)
  Candidate: 304.131-1
  Version table:
 304.131-8~bpo8+2 0
100 http://ftp.fi.debian.org/debian/ jessie-backports/non-free amd64 
Packages
 304.131-1 0
500 http://ftp.fi.debian.org/debian/ jessie/non-free amd64 Packages

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: Desktop freeze

[Jérémy Lal]

Hi,

i'm having a very similar issue with epiphany-browser and chromium,
using gnome-shell in debian/sid.
The content inside the window stops being refreshed completely,
but i can still move the window around without it displaying garbage.
I'm not sure on which package i should report this.

Jérémy

Tip: nmtui NetworkManager, Terminal Interface (also Bug#694068 + hostname)

[Cindy-Sue Causey]

Hi..

Sharing the existence of the Debian package called "nmtui" because the
only 5 references to it in possibly 200,000 emails are from this past
week k/t Debian-Accessibility and Debian-User listservs [1], [2].
Thought maybe nmtui's interface might prove more user friendly for
those who found nothing else helped when setting up networking.

Being familiar with the acronym, GUI, for graphical user interface,
that "TUI" leaped off the page. Per its manual page, nmtui is "Text
User Interface for controlling NetworkManager". If one follows the
nmtui acronym per chatter out and about, NetworkManager
text/textual/text-based user interface works, too.

>From "man nmtui":

+++ BEGIN "man nmtui" SNIPPET +++

DESCRIPTION
   nmtui is a curses‐based TUI application for interacting with
NetworkManager. When
   starting nmtui, the user is prompted to choose the activity to
perform unless it was
   specified as the first argument.

   The supported activities are:

   edit
   Show a connection editor that supports adding, modifying,
viewing and deleting
   connections. It provides similar functionality as
nm-connection-editor.

   connect
   Show a list of available connections, with the option to
activate or deactivate
   them. It provides similar functionality as nm-applet.

   hostname
   Set the system hostname.

   Corresponding to above activities, nmtui also comes with
binaries named nmtui-edit,
   nmtui-connect, and nmtui-hostname to skip the selection of the
activities.

SEE ALSO
   nmcli(1), nm-applet(1), nm-connection-editor(1), NetworkManager(8).

+++ END "man nmtui" SNIPPET +++

If anyone has feedback on nmtui's apparently very ready access to
changing hostname, that might help others down the road. My memory is
that topic was possibly discussed very recently.

This is an awfully easy way to change hostname. It's even offering
that point of change to my normal user. I can't afford to lose my
computer's operability today so I haven't tested that part to see if
it at least asks for root's password before committing that change.

Related to this on that same Debian-Accessibility thread [3], there's
a bug that maybe someone with network programming strengths could
please check out:

Debian Bug report logs - #694068
Date: Fri, 23 Nov 2012 14:33:02 UTC
netcfg: Wireless connectivity present during an install but absent afterwards
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068

Reading that bug, kneejerk is that correcting that is going to help
*ALL* Debian Users. It feels like that bug's title reads similar to
content in several Debian-User threads (also) lately..

Hope knowledge of nmtui helps someone.. at some point.. some day. Good luck!

Cindy :)

[1] Re: stretch orca and wifi connection setup @ Debian-Accessibility
https://lists.debian.org/debian-accessibility/2016/12/msg00031.html

[2] Re: Where are WiFi passwords (WPA keys) stored? @ Debian-User
https://lists.debian.org/debian-user/2016/12/msg00171.html

[3] Re: stretch orca and wifi connection setup @ Debian-Accessibility
https://lists.debian.org/debian-accessibility/2016/12/msg00023.html

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with plastic sporks *

Re: Package update problem...

[Mark Neidorff]

On Sunday, 12/11/16 02:45:41 PM kamaraju kusumanchi wrote:
> On Fri, Dec 9, 2016 at 3:17 PM, Mark Neidorff  
wrote:
> > I'm running Jesse 8.6 with a KDE desktop.
> > 
> > I get a desktop notification that there is one or more package 
updates
> > available.  I select the package(s) and then I'm asked for 
authentication.
> > I type in the root password, but it is rejected.  I also try my user
> > password, but that is also rejected. (Tried multiple times, so it doesn't
> > seem to be a typo problem)
> > 
> > If I go to the command line--as root--and do apt-get update and 
upgrade,
> > then the update installs correctly.
> > 
> > This sounds like something easy to fix, but I just don't know where to 
fix
> > and what fix to apply. Please let me know.
> 
> The technical term you are looking for is called "Privilege escalation".
> 
> On a Debian system, "administrative" privileges are required to
> install/upgrade/remove packages. When you run the command as root, 
you
> have all the necessary privileges. A normal user does not have them
> enabled by default. This explains why the commands fail unless they
> are run as root. One possible approach (I am only guessing here and
> have not tested this) is to grant the necessary privileges to this
> user and see if the KDE application respects that.
> 
> You can do this by modifying /etc/sudoers which is explained in
> https://www.debian.org/doc/manuals/debian-reference/ch01.en.html#_sudo_confi
> guration
> https://www.debian.org/doc/manuals/debian-reference/ch04.en.html#_sudo
> https://debian-handbook.info/browse/stable/sect.config-misc.html#sect.shari
> ng-admin-rights
> 
> The only caution is that /etc/sudoers can't be edited interactively in
> an editor. You need to use another program called visudo to do that.
> 
> You can accomplish some really complex tasks by tweaking the sudoers
> configuration file (see man sudoers for all the gory details). But for
> your use case, granting ALL permissions to one normal user should
> probably be sufficient.
> 
> hope that helps
> raju

Sorry to seem stubborn, but I don't consider giving a user account full 
administrative access acceptable, even if there is only one user on the 
system.  My reasoning is that by default if the user goes to a "naughty" 
web page and somehow downloads destructive software only the user's 
files are at risk.  But, with full administrative access, the entire system 
(plus any attached networks) are at risk.

Question: Is not allowing an administrative (software update)task to run 
when the root password is given a bug or is it by design?  If by design, why?  

I see two alternatives to your suggestion, neither of which is convenient.
1. When I get a notification, log off and then log in as root.  Then when the 
updates are downloaded and applied, log back in as the user.
2. When I get a notification, use "su" to change to the root user and then 
do the updates.

Both of these add more steps.  If I have to add these steps, then I have to.  
But, I have been using linux (and KDE) for a long time and up until now, 
when an update arrives I select to apply the update, give the root 
password, and the update is installed.  Now, when I get an update 
notification and supply the root password to apply the update, the update 
is not applied. (I am returned to the password prompt)

Thanks,

Mark  

Re: How to upgrade / compile an ARM kernel?

[Robert Latest]

Thanks for the tip, I'll take my question next door.

Plasma: keyboard crash

[Hans]

Hi folks,

from time to time in plasma 5 I have the problem, that the keyboard stops its 
function. Is there a way to restart the keyboard without restarting plasma?

Thanks for any hints.

Best

Hans

Re: understanding how localization works in Debian

[Martin T]

On Mon, Dec 12, 2016 at 3:47 PM, Greg Wooledge  wrote:
> On Mon, Dec 12, 2016 at 01:58:12PM +0200, Martin T wrote:
>> 1) pam_env.so sets the environmental variables seen in the output of
>> locale command based on configuration files(for example
>> /etc/default/locale) when user logs in
>
> Maybe, maybe not.  The LC_* and LANG variables can come from many
> different places.  I think, however, that you are focusing on the
> libc/application level that uses these variables, and not their
> origin.  So for your purposes, "LC_* and LANG are set somehow".
>
>> 2) nl_langinfo(), setlocale() and (some) other glibc functions used in
>> programs ask environment variables seen in the output of locale
>> command
>>
>> 3) based on those environment variables nl_langinfo(), setlocale(),
>> etc functions check the locale information in
>> /usr/lib/locale/locale-archive database and change their output
>> accordingly
>>
>> 4) /usr/lib/locale/locale-archive database is generated with
>> locale-gen utility based on entries in /etc/locale.gen file and locale
>> template/configuration files in /usr/share/i18n/locales/
>>
>> Did I understand this correctly?
>
> I am confused.  There are basically three interaction points between
> you and the locale system, and you don't seem to have focused on any
> of them.
>
> 1) LC_* and LANG are set somehow by the end user or by the local OS.
>
> 2) The local system admin runs "dpkg-reconfigure locales" to determine
>which locales are "generated".  End users can only receive translations
>from locales that are generated on the local system.
>
> 3) Applications are written with localization (l10n) support using the
>features of whichever language they're written in, e.g. _("...").
>
> For a more detailed look at #1, see https://wiki.debian.org/Locale
> (And even that is woefully incomplete thanks to the proliferation
> of Desktop Environments, and the ridiculous inadequacy of the PAM
> environment variable system.)
>
> For a more detailed look at #3, see
> https://www.gnu.org/software/gettext/manual/gettext.html
>

Greg,

thank you for reply! I do understand that LC_* and LANG variables can
come from various places. For example even pushed by SSH client.
However, were my other three points incorrect? As I understand it,
some glibc functions(for example nl_langinfo(), setlocale()) use those
LC_* and LANG variables to change the program output(for example first
day of the week in cal command) based on locale data in
/usr/lib/locale/locale-archive database.



thanks,
Martin

Black Screen on First Boot

[Dan Norton]

Greetings,

The netinst of jessie from a flash drive, graphic install, went well 
like it did on another PC, but on this old PC the boot after install 
produced a black screen.


vbeinfo lists some display settings followed by "Preferred mode 
1360x768", but this mode is not in the list. There is an * beside 
1024x768x32 in the list. Is that the mode used during the install?


What is the "Preferred mode 1360x768" for? Is that for the kernel? I 
tried to change that by doing this:


grub> set root=(hd0,1)
grub> set gfxpayload=1024x768
grub> linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/sda1
grub> initrd /boot/initrd.img-3.16.0-4-686-pae
grub> boot

But that still resulted in a black screen. What should be done instead?

 - Dan

Re: Where to report wl bad behavior ?

[kamaraju kusumanchi]

> 2016-12-11 20:59 GMT+01:00 kamaraju kusumanchi
> :
>>
>> How and where did you get the wireless driver? If the driver is not
>> part of the official Debian software repository, I do not see how
>> filing a bug report would help. Your best shot is to complain to the
>> upstream yourself or use a different hardware.
>>
>> raju
>> --
>> Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
>
>
On Mon, Dec 12, 2016 at 12:46 AM, Laurent Debian
 wrote:
> Hi
> it is. It's in the non-free depot.
>  And AFAIK, it is the only one making works "properly" this kind of chipset
> (broadcom 4360...)
> And I don't like the idea to open up a mac book pro find the wifi chip and
> change it?

Hi Laurent,

It is better to reply to the list instead of writing to me personally.
That way others will also be able to help you and the conversations
will be part of the archive.

Coming back to your question... Yes, you can file a bug report on a
package that is in the non-free component of Debian.

hth
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Re: Package update problem...

[kamaraju kusumanchi]

On Mon, Dec 12, 2016 at 12:50 PM, Mark Neidorff  wrote:
>
> Sorry to seem stubborn, but I don't consider giving a user account full
> administrative access acceptable, even if there is only one user on the
> system. My reasoning is that by default if the user goes to a "naughty" web
> page and somehow downloads destructive software only the user's files are at
> risk. But, with full administrative access, the entire system (plus any
> attached networks) are at risk.

I do not think you are being stubborn. You do not have to give the
normal user ALL permissions. But you have to give him some permissions
to be able to install/update/remove packages. For example, I
configured my /etc/sudoers file such that my normal user account can
run apt-get and install packages. Giving ALL permissions just makes
things simpler but /etc/sudoers can be fine tuned to give just as much
as control as needed.


> Question: Is not allowing an administrative (software update)task to run
> when the root password is given a bug or is it by design? If by design, why?

I do not understand the question. I am not here to defend any
particular design choice. I can help you with how it can be done but
not why it should be done one way or another. That is beyond my
expertise.

> I see two alternatives to your suggestion, neither of which is convenient.
>
> 1. When I get a notification, log off and then log in as root. Then when the
> updates are downloaded and applied, log back in as the user.
>

No. There is no need to logoff. For example, whenever I want to
install a package, I simply open a konsole and run

sudo apt-get update
sudo apt-get install PKGNAME

as a normal user. When it asks for password, I supply the password of
my user account (not the password of the root account).

> 2. When I get a notification, use "su" to change to the root user and then
> do the updates.

That is one way. I find sudo a bit more easier than su. Since with
sudo, you do not even have to know the root password (once it is
setup).

> But, I have been using linux (and KDE) for a long time and up until now,
> when an update arrives I select to apply the update, give the root password,
> and the update is installed. Now, when I get an update notification and
> supply the root password to apply the update, the update is not applied. (I
> am returned to the password prompt)

hmm... no idea on this part. What program does KDE run when you try to
update packages? May be run it from command line and see if it gives
an error?

hth
raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Re: Plasma: keyboard crash

[kamaraju kusumanchi]

On Mon, Dec 12, 2016 at 3:41 PM, Hans  wrote:
> Hi folks,
>
> from time to time in plasma 5 I have the problem, that the keyboard stops its
> function. Is there a way to restart the keyboard without restarting plasma?

How have you determined that the problem is with plasma 5 and not
something else? What happens when you run a different desktop
environment?

raju
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

current testing

[Jim McCloskey]

Hello after a long absence. Following up (in a sense) on the recent
thread about the wisdom of mixing elements from the stable and
testing/unstable distributions, I wanted to ask about how stable
current testing is.

I used to run the testing distribution as a matter of course, but have
been too busy at work in recent times to devote the necessary time to
that project. I miss the fun of it and I'd like to test-drive the
upgrade.

If the past is a good guide, though, this close to a release, running
the testing distribution has been a reassuringly boring experience. Is
that so at present? I'd be particularly curious about the transition
(back) to ffmpeg. Is that transition actually in place in stretch?
And there is or was the big Perl transition. Are there other things to
worry about before running dist-upgrade?

If anyone has relevant experience I'd appreciate hearing about it.

Thanks,

Jim