Re: terminal will not wak after hibernation

[Joe]

On Tue, 10 Jul 2018 14:14:11 +1000
Zenaan Harkness  wrote:

> On Mon, Jul 09, 2018 at 05:27:44PM -0400, Celejar wrote:
> > On Sat, 7 Jul 2018 20:32:03 +0100
> > Joe  wrote:
> >   
> > > On Sat, 7 Jul 2018 11:24:59 -0400
> > > Dan Ritter  wrote:  
> > 
> > ...
> >   
> > > > The majority of machines can do suspend-to-RAM and/or
> > > > suspend-to-disk and wake up smoothly afterwards.
> > > >   
> > > 
> > > I'll take your word for it. I've never seen such a combination. I
> > > give suspend a try on my Gigabyte/AMD sid machine now and then,
> > > but it seems to work for no more than two weeks in any year.
> > > Currently it is leaving orphaned inodes, so I'm not experimenting
> > > too much.
> > > 
> > > Years ago, I used to spend time fixing it, but after a while I
> > > realised it would only break again a month later, so I've stopped
> > > bothering. I've yet to see a laptop/netbook screen backlight come
> > > on again after suspend...  
> > 
> > ?! Many people have suspend working fine (although many certainly
> > don't); suspend-to-ram has been working flawlessly (AFAICT) out of
> > the box on my Lenovo ThinkPad W550s.  
> 
> In the APM days, Debian/Linux suspend was flawless for years.
> 
> Then ACPI came along and things have been iffy for a decade.
> 
> However, suspend-to-RAM (suspend, as opposed to hibernate) has worked
> very well here (Lenovo X220) for the last few years.
> 
> Possibly OP/Joe has some customization he regularly implements,
> causing his problem? IDK of course...
> 

Not that I know of. But I'm not an IT professional, dealing with
hundreds of machines. I've had a couple of laptops and an Acer netbook,
fairly mainstream, and a few desktops. 

For example, the netbook has a fairly recent Stretch installation. If I
manually select 'Suspend', that works and appears to come back up
normally. If I close the lid, when I open it again, the display stays
black. From keyboard and mouse action, it looks as if it is awake
normally, there's just no display. It's not really of any use in that
state, and needs to be killed with the four-second power button thing.

As I've posted, I have a moderately old desktop Gigabyte MB, with a
fairly old sid installation, on which suspend to RAM has occasionally
worked. At the moment, the only way to resume is to poke the power
button, it no longer wakes up on keyboard or mouse action, when it
wakes it sits for fifteen seconds then reboots. Yes, I know about swap
naming, I've been through all that and in any case, swap isn't involved
in suspend to RAM. It has worked reliably within the last year, but not
for more than a couple of weeks.

I can't recall any machine on which I've run Linux working properly as
regards suspend. OK, it's only half a dozen or so computers, but zero
out of six isn't an impressive performance.

-- 
Joe

Re: anybody maintaining lxc and lxd in Debian?

[Jonathan Dowland]

On Fri, Jul 06, 2018 at 09:56:58AM +0200, Harald Dunkel wrote:

is anybody maintaining lxc in Debian? I have the impression that
it has been orphaned. And I don't dare to hope for #768073 anymore.


Ah yes I'd forgotten about that (I was involved for a while). But
looking at the current status it's not as bleak as I feared; the last
dependency was finally finished in February.


Does everybody interested in virtualization use Ubuntu now?


No; in the grand scheme of virtualization LXD is still quite niche. But
I hope we'll see it in Debian soon none-the-less.

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: Separate /home directories etc?

[Jonathan Dowland]

On Fri, Jul 06, 2018 at 04:54:53PM -0400, Matthew Crews wrote:

Separate partitions
Pros: if your / partition drive fails, it does not take /home with it


You are conflating drives and partitions, here. Both partitions could be
on the same physical drive, and a drive failure would affect both in
that case.


--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Buster and apt wanting to remove tons of packages...

[sgarrulo]

Hello everyone!
I had an installation of debian stable (stretch) which was fully upgraded 
something
like a couple of months ago. Then I passed it to testing (buster).

Now I'm facing this situation:
* 5031 installed packages
* 1292 upgradable packages

If I do a normal upgrade, 676 packages are to be upgraded, but only the gtk/qt 
unrelated ones
(for example, apache2-doc but none of the apache2 *real* packages, or 
vim-addon-manager and vim-doc
but none of the vim *real* packages, and so on)

And if I try to upgrade, let's say, vim-* packages, it wants to remove a ton of 
seemingly unrelated
packages, like calibre, evolution, gir1.2-*, gstreamer things, kid3, libqt5-*, 
pidgin, vlc-*, etc etc...

This happens when I try to upgrade or install apparently *anything* related to 
GUI programs (GTK/Qt related).

I am worried to make an upgrade like that.

What can I do to debug this situation and try to understand which package(s) 
is/are breaking everything?

I have no pinned packages.

Thank you in advance!

No full upgrade to Nvidia 390.67 from bpo

[mlnl]

Hi,

i'm using stretch-backports but i can't get the full upgrade to Nvidia
390.67. The aptitude log shows:

Aptitude 0.8.7: log report
Mon, Jul  9 2018 14:04:18 +0200
Will install 9 packages, and remove 0 packages.

[HOLD, DEPENDENCIES] libegl1-mesa:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] libegl1-mesa-dev:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] libgbm1:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] libgl1-mesa-dev:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] libgl1-mesa-glx:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] libglapi-mesa:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] libgles2-mesa:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] libwayland-egl1-mesa:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] mesa-common-dev:amd64 13.0.6-1+b2
[HOLD, DEPENDENCIES] nvidia-alternative:amd64 390.48-2~bpo9+3
[HOLD, DEPENDENCIES] nvidia-vdpau-driver:amd64 390.48-2~bpo9+3
[HOLD] libcuda1:amd64 390.48-2~bpo9+3
[HOLD] libegl-nvidia0:amd64 390.48-2~bpo9+3
[HOLD] libgl1-nvidia-glvnd-glx:amd64 390.48-2~bpo9+3
[HOLD] libgles-nvidia1:amd64 390.48-2~bpo9+3
[HOLD] libgles-nvidia2:amd64 390.48-2~bpo9+3
[HOLD] libgles1-nvidia:amd64 390.48-2~bpo9+3
[HOLD] libgles2-nvidia:amd64 390.48-2~bpo9+3
[HOLD] libglx-nvidia0:amd64 390.48-2~bpo9+3
[HOLD] libnvcuvid1:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-cfg1:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-compiler:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-egl-wayland1:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-eglcore:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-encode1:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-fatbinaryloader:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-fbc1:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-glcore:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-ifr1:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-ml1:amd64 390.48-2~bpo9+3
[HOLD] libnvidia-ptxjitcompiler1:amd64 390.48-2~bpo9+3
[HOLD] nvidia-driver:amd64 390.48-2~bpo9+3
[HOLD] nvidia-driver-bin:amd64 390.48-2~bpo9+3
[HOLD] nvidia-driver-libs:amd64 390.48-2~bpo9+3
[HOLD] nvidia-egl-icd:amd64 390.48-2~bpo9+3
[HOLD] nvidia-egl-wayland-icd:amd64 390.48-2~bpo9+3
[HOLD] nvidia-kernel-dkms:amd64 390.48-2~bpo9+3
[HOLD] nvidia-kernel-support:amd64 390.48-2~bpo9+3
[HOLD] nvidia-opencl-icd:amd64 390.48-2~bpo9+3
[HOLD] nvidia-smi:amd64 390.48-2~bpo9+3
[HOLD] nvidia-vulkan-icd:amd64 390.48-2~bpo9+3
[HOLD] xserver-xorg-video-nvidia:amd64 390.48-2~bpo9+3
[UPGRADE] nvidia-cuda-mps:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-detect:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-egl-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-egl-wayland-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-kernel-source:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-legacy-check:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-libopencl1:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-opencl-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
[UPGRADE] nvidia-vulkan-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1

Any hints, what i can do to solve the problem?

Thx.
-- 
mlnl

Re: Editing a piped in stream?

[mick crane]

On 2018-07-08 17:41, John Darrah wrote:

On 7/8/2018 7:00 AM, Richard Owlett wrote:


Until this thread I didn't have concept of "stream editor", much less 
the existence of "sed".

I had heard of "AWK", but had an image of it being a regex parser.


Awk is easy to learn because it is a minimal language. It can do
anything sed can do and much more. I am always surprised that so many
people opt to build long commands with cut/sed instead of using awk.
FWIW, I use mawk because it is orders of magnitude faster than gawk.

-- john



I'd like to learn some awk having found it handy once.
apt says mawk is installed

in /usr/bin I have
lrwxrwxrwx  1 root root 21 Apr  2 22:29 awk -> 
/etc/alternatives/awk

-rwxr-xr-x  1 root root 658072 Jan 25 12:55 gawk
-rwxr-xr-x  1 root root   3189 Jan 25 12:55 igawk
-rwxr-xr-x  1 root root 121976 Mar 23  2012 mawk
lrwxrwxrwx  1 root root 22 Apr  2 22:29 nawk -> 
/etc/alternatives/nawk


"awk" returns options for gawk and "mawk does nothing ( back to prompt)

In /etc/alternatives there is
awk
awk.1.gz
nawk
nawk.1.gz

how to run mawk ?


mick



--
Key ID4BFEBB31

Re: Editing a piped in stream?

[Greg Wooledge]

On Tue, Jul 10, 2018 at 01:16:09PM +0100, mick crane wrote:
> I'd like to learn some awk having found it handy once.
> apt says mawk is installed
> 
> in /usr/bin I have
> lrwxrwxrwx  1 root root 21 Apr  2 22:29 awk -> /etc/alternatives/awk
> -rwxr-xr-x  1 root root 658072 Jan 25 12:55 gawk
> -rwxr-xr-x  1 root root   3189 Jan 25 12:55 igawk
> -rwxr-xr-x  1 root root 121976 Mar 23  2012 mawk
> lrwxrwxrwx  1 root root 22 Apr  2 22:29 nawk ->
> /etc/alternatives/nawk
> 
> "awk" returns options for gawk and "mawk does nothing ( back to prompt)

So, what's the problem?

> how to run mawk ?

mawk

You have already run it once, with no arguments, and it did nothing.
Now try giving it some arguments.

wooledg:~$ mawk -v foo=bar 'BEGIN {print foo}'
bar

See, just like awk.

PAM-CGFS[xxx]: Failed to get list of controllers

[Richard Hector]

Hi all,

I'm getting messages like this in auth.log:

PAM-CGFS[xxx]: Failed to get list of controllers

Web searches generally hint at a link with LXC, and this is on an LXC
host, but doesn't seem to directly relate to the containers - it shows
up when anyone logs in, starts a cron session, or similar.

The server in question is one I inherited, not one I set up myself.

I have another LXC host (which I did set up) that doesn't do this - one
difference is that that one doesn't have libpam-cgfs installed, which is
probably significant ... but I'm reluctant to just uninstall it from the
problem host without fully understanding what I'm losing. It doesn't
have any hard dependencies from other packages, but there may be
something else I haven't found yet relying on it.

Both are stretch, and I think both were upgraded from jessie.

Any tips on what's causing it, and whether it's a problem?

Thanks,
Richard



signature.asc
Description: OpenPGP digital signature

Re: Editing a piped in stream?

[mick crane]

On 2018-07-08 12:18, Andy Smith wrote:

Hello,

On Sun, Jul 08, 2018 at 07:39:07AM +0200, john doe wrote:

The issue here is that we don't know what the OP wants


A situation sadly familiar when dealing with this particular
poster's threads.

Also in the general case, if you ever find yourself parsing the
output of "ls", you will probably find that there is a better way to
be doing what you're trying to do. There are a lot of issues with
parsing "ls" output:




Cheers,
Andy


about 10 years ago on another mailing list there was a guy who claimed 
to be dyslexic who said was uncertain of things but once you'd 
deciphered the jumble of words was asking quite complicated networking 
questions and would come back with a knowledgeable other question ( once 
you'd deciphered it ) I did think it might be a wind up.


mick

--
Key ID4BFEBB31

Re: Editing a piped in stream?

[mick crane]

On 2018-07-10 13:31, Greg Wooledge wrote:

On Tue, Jul 10, 2018 at 01:16:09PM +0100, mick crane wrote:

I'd like to learn some awk having found it handy once.
apt says mawk is installed

in /usr/bin I have
lrwxrwxrwx  1 root root 21 Apr  2 22:29 awk -> 
/etc/alternatives/awk

-rwxr-xr-x  1 root root 658072 Jan 25 12:55 gawk
-rwxr-xr-x  1 root root   3189 Jan 25 12:55 igawk
-rwxr-xr-x  1 root root 121976 Mar 23  2012 mawk
lrwxrwxrwx  1 root root 22 Apr  2 22:29 nawk ->
/etc/alternatives/nawk

"awk" returns options for gawk and "mawk does nothing ( back to 
prompt)


So, what's the problem?


how to run mawk ?


mawk

You have already run it once, with no arguments, and it did nothing.
Now try giving it some arguments.

wooledg:~$ mawk -v foo=bar 'BEGIN {print foo}'
bar

See, just like awk.


OK
mick
--
Key ID4BFEBB31

Re: Buster and apt wanting to remove tons of packages...

[Joe]

On Tue, 10 Jul 2018 12:55:26 +0200
sgarrulo  wrote:

> Hello everyone!
> I had an installation of debian stable (stretch) which was fully
> upgraded something like a couple of months ago. Then I passed it to
> testing (buster).
> 
> Now I'm facing this situation:
> * 5031 installed packages
> * 1292 upgradable packages
> 
> If I do a normal upgrade, 676 packages are to be upgraded, but only
> the gtk/qt unrelated ones (for example, apache2-doc but none of the
> apache2 *real* packages, or vim-addon-manager and vim-doc but none of
> the vim *real* packages, and so on)
> 
> And if I try to upgrade, let's say, vim-* packages, it wants to
> remove a ton of seemingly unrelated packages, like calibre,
> evolution, gir1.2-*, gstreamer things, kid3, libqt5-*, pidgin, vlc-*,
> etc etc...
> 
> This happens when I try to upgrade or install apparently *anything*
> related to GUI programs (GTK/Qt related).
> 
> I am worried to make an upgrade like that.
> 
> What can I do to debug this situation and try to understand which
> package(s) is/are breaking everything?
> 
> I have no pinned packages.
> 

It's probably not a single package. I run an unstable workstation, this
sort of thing is not that unusual. Whole subsystems get upgraded, such
as GTK or the kf5 stuff, but not everything is ready at once. Also, many
applications dependent on this subsystem have precise dependencies
specified, and are not happy with the new libraries. Those applications
have to be upgraded, not necessarily to change them, but to mark them as
compatible with the new libraries after testing. So a major change can
require hundreds of dependent packages to be revised. This kind of
thing never happens in stable, but is fairly common in testing and
unstable.

What I do is to temporarily switch from upgrade-system to Synaptic. It
is relatively quick to select a few innocent-looking packages from the
big list, and check that they go through without a problem. After a few
tries, you can see where the trouble is, and leave those packages at
the current state. People comfortable with the aptitude interactive
interface can do the same there, but for some reason, I prefer
Synaptic. Generally the state of difficulty lasts only a few days,
though it can go on for a week or two sometimes. 

It's the price you pay for having more up-to-date software than stable
has. At the point of release of a new Debian stable, testing is
identical to it. At the time of the next release, about two years
later, testing is very different, many changes of architecture of major
systems having been made. If you use testing or unstable over this
period, you have to ride out these upheavals, hoping that nothing
important breaks. About eighteen months after release, testing is
frozen for bug fixing before the next release, and the ride is much
smoother after that. It's quieter in unstable as well, since unstable
has to be kept in a condition where it can be copied into testing after
the release occurs, so changes to unstable have to be kept within
limits. All hell breaks loose at release time...

-- 
Joe

Re: Editing a piped in stream?

[john doe]

On 7/10/2018 2:16 PM, mick crane wrote:

On 2018-07-08 17:41, John Darrah wrote:

On 7/8/2018 7:00 AM, Richard Owlett wrote:


Until this thread I didn't have concept of "stream editor", much less 
the existence of "sed".

I had heard of "AWK", but had an image of it being a regex parser.


Awk is easy to learn because it is a minimal language. It can do
anything sed can do and much more. I am always surprised that so many
people opt to build long commands with cut/sed instead of using awk.
FWIW, I use mawk because it is orders of magnitude faster than gawk.

-- john



I'd like to learn some awk having found it handy once.
apt says mawk is installed

in /usr/bin I have
lrwxrwxrwx  1 root root 21 Apr  2 22:29 awk -> 
/etc/alternatives/awk

-rwxr-xr-x  1 root root 658072 Jan 25 12:55 gawk
-rwxr-xr-x  1 root root   3189 Jan 25 12:55 igawk
-rwxr-xr-x  1 root root 121976 Mar 23  2012 mawk
lrwxrwxrwx  1 root root 22 Apr  2 22:29 nawk -> 
/etc/alternatives/nawk


"awk" returns options for gawk and "mawk does nothing ( back to prompt)



At the end of those 'gawk' options:

"gawk is a pattern scanning and processing language.
By default it reads standard input and writes standard output."

$ printf "%s" "123 456 789" | awk '{print $2}'
456

--
John Doe

debian/testing repo question

[Hans]

Hi folks, 

I know, I had discussed a similar question ago, but testing is still a miracle 
for me.

Is there an automatism, why or when packages got removed from testing or ist 
this always done manually by the developers?

This time I struggled about "cqrlog", which was accepted in testing, then 3 
months later removed without a clear reason but same version added in sid?  

However, I discovered, there is a new version available, but has broken 
dependencies (just a single lib is missing!) . 

But the removal of "cqrlog" looked as it was done by some cronjob. 

On the other hand, it is not understandable, why to remove a package, when its 
dependencies touches other packages. When it was prior existent, then the 
dependencies of the later package should be adjusted and not the existing one 
(or just remove it). 

The logic of debian/testing is still a miracle for me, looks like changes are 
done one time so, the other time so. 

Sorry, please do not feel beeing attacked, it is just the way it is looking 
for me. :)

Testing is a miracle

Best regards

Hans

Re: Buster and apt wanting to remove tons of packages...

[Cindy-Sue Causey]

On 7/10/18, sgarrulo  wrote:
> Hello everyone!
> I had an installation of debian stable (stretch) which was fully upgraded
> something
> like a couple of months ago. Then I passed it to testing (buster).
>
> Now I'm facing this situation:
> * 5031 installed packages
> * 1292 upgradable packages
>
> If I do a normal upgrade, 676 packages are to be upgraded, but only the
> gtk/qt unrelated ones
> (for example, apache2-doc but none of the apache2 *real* packages, or
> vim-addon-manager and vim-doc
> but none of the vim *real* packages, and so on)
>
> And if I try to upgrade, let's say, vim-* packages, it wants to remove a ton
> of seemingly unrelated
> packages, like calibre, evolution, gir1.2-*, gstreamer things, kid3,
> libqt5-*, pidgin, vlc-*, etc etc...
>
> This happens when I try to upgrade or install apparently *anything* related
> to GUI programs (GTK/Qt related).
>
> I am worried to make an upgrade like that.
>
> What can I do to debug this situation and try to understand which package(s)
> is/are breaking everything?
>
> I have no pinned packages.
>
> Thank you in advance!


Hi.. Been there, done that, filed a bug, got fussed at, vented here at
Debian-User. Moral of the Story: I don't file ANY BUGS anymore. I
spend that time advocating important subjects related to #Life
instead. lol!

What you experienced is one aspect of the design of how package
upgrades work. As you saw in your case, overriding by manually
installing ("cherry picking") Developer-held packages can be dangerous
for the health of your current install.

Those packages have been held back for a reason. I still don't fully
grasp why those packages even show in our face. I a-sume it's just
somehow part of the system of erasing certain to-do's on a development
checklist to help keep the perpetual upgrade process moving onward and
upward.

I just deleted a bunch of other junk I wrote to instead ask an
important question that might help others help you:

What path did you take to upgrade to where you are this second?

Me? I zap mine and start over via debootstrap because it's just more
"cognitively friendly" *for me*. Others go some version of the
"apt-get dist-upgrade" route which is trustworthy and viable.

Simply changing things, e.g. /etc/apt/sources.list, to point to a
higher or lower distribution, not so much. That sometimes starts a
ticking time bomb toward almost inevitable self-destruction. ALSO been
there, done THAT a very long time ago. *NEVER... EVER... AGAIN!* :D

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

* runs with duct tape *

Re: Buster and apt wanting to remove tons of packages...

[Roberto C . Sánchez]

On Tue, Jul 10, 2018 at 09:39:44AM -0400, Cindy-Sue Causey wrote:
> 
> Hi.. Been there, done that, filed a bug, got fussed at, vented here at
> Debian-User. Moral of the Story: I don't file ANY BUGS anymore. I
> spend that time advocating important subjects related to #Life
> instead. lol!
> 
Sadly, that does happen from time to time.  I am sorry if you had a bad
experience.  Still, I would like to encourage you and everyone else to
continue filing bugs.  Most Debian package maintainers are very
responsive and try to maintain high quality for their packages.  The bug
reports from users help improve that process.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: debian/testing repo question

[Roberto C . Sánchez]

On Tue, Jul 10, 2018 at 03:31:09PM +0200, Hans wrote:
> Hi folks, 
> 
> I know, I had discussed a similar question ago, but testing is still a 
> miracle 
> for me.
> 
> Is there an automatism, why or when packages got removed from testing or ist 
> this always done manually by the developers?
> 
> This time I struggled about "cqrlog", which was accepted in testing, then 3 
> months later removed without a clear reason but same version added in sid?  
> 
Clear reason is here:

https://tracker.debian.org/pkg/cqrlog


testing migrations

excuses:
348 days old (5 needed)
Updating cqrlog introduces new bugs: #867140
Piuparts tested OK - 
https://piuparts.debian.org/sid/source/c/cqrlog.html
Not considered


> However, I discovered, there is a new version available, but has broken 
> dependencies (just a single lib is missing!) . 
> 
> But the removal of "cqrlog" looked as it was done by some cronjob. 
> 
That is correct.  When a package in testing has a release-critical bug
filed against it, the package is scheduled for automatic removal after
some period of time.  If the maintainer responds with an upload the
fixes the bug, the package is allowed to remain.  If the maintainer
takes no action the package is removed.  This is done ensure a high
quality set of packages for the next release.

Recall that the purpose of the testing distribution is not to serve as a
more up to date stable version for users.  It is meant to be the
preparation area for the next stable release.

The bug that triggered the removal of cqrlog (#867140) has to do with
the transition to openssl 1.1.

> On the other hand, it is not understandable, why to remove a package, when 
> its 
> dependencies touches other packages. When it was prior existent, then the 
> dependencies of the later package should be adjusted and not the existing one 
> (or just remove it). 
> 

Most packages that are built against openssl 1.0 need non-trivial source
code changes to work with openssl 1.1.  Many packages have been removed
as a result of this transition.

> The logic of debian/testing is still a miracle for me, looks like changes are 
> done one time so, the other time so. 
> 
> Sorry, please do not feel beeing attacked, it is just the way it is looking 
> for me. :)
> 
> Testing is a miracle
> 
Again, the logic has to do with the intended purpose of testing.  If you
need stability, then run stable.  If you can deal with the occasional
disruption, then unstable is probably best for staying current with
packages.  Testing should really only be used by those are specifically
working toward the development of the next Debian stable release.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Looking for ratings of all-in-one printers for Linux (Ubuntu in particular)

[Dan Ritter]

On Mon, Jul 09, 2018 at 11:38:41PM -0400, Michael Stone wrote:
> On Mon, Jul 09, 2018 at 07:05:52PM -0400, Dan Ritter wrote:
> > On Mon, Jul 09, 2018 at 06:53:44PM -0400, Michael Stone wrote:
> > > On Mon, Jul 09, 2018 at 06:39:29PM -0400, Dan Ritter wrote:
> > > > You're both missing the main point, which is that a Brother
> > > > printer with BRscript/3 is essentially a Postscript printer, and
> > > > you can treat it as one. No drivers needed.
> > > 
> > > So you can use it as an all-in-one postscript printer/scanner?
> > 
> > You can use it as a printer. As far as I know there is no such
> > thing as a "postscript scanner".
> 
> Well, the original question (see subject line) was about all-in-one
> printers, which implies more than just printing. It would be sad to see the
> point of the question lost in all the back and forth.
> 
> > The Brother all-in-ones tend to have "scan-to-network" abilities,
> > though, and that doesn't require a driver -- just an internal
> > FTP or SAMBA server to receive the files. My workplace has a
> > bunch of these. Walk up, select Scan, select Network, and put
> > your document(s) in. You get PDFs or TIFFs in your filesystem.
> 
> That's more of a document scan feature, not so great for scanning tasks
> where you want more control.

Yes. The all-in-ones are terrible at that, proprietary software
or not.

-dsr-

Re: debian/testing repo question

[Hans]

Hi Robert,

thanks for your quick response. So, doi I see this correct and can I say: 
There is an automatismn for a package removal, which will be interrupted, when 
the maintainer is responding within a period of time and the reason for the 
removal was eliminated (i.e. fixed a bug or uploaded a newer version). 
Whenever a maintainer does nothing, the package got to be removed, when its 
dependencies inmtefere with other dependencies, but is left, when its 
dependencies do not harm anything. Can I say so?

And did I understand you correctly: Using unstable or stable is better than to 
use testing? If I understood this correctly, then the logical result would be, 
that testing has to expect more trouble (for users) than stable or unstable,

Most users I am supporting are using stable, but some are using testing. 
Should I advise them to upgrade tu unstable?

Best

Hans

 

Re: Buster and apt wanting to remove tons of packages...

[The Wanderer]

On 2018-07-10 at 06:55, sgarrulo wrote:

> Hello everyone!
> I had an installation of debian stable (stretch) which was fully 
> upgraded something like a couple of months ago. Then I passed it to
> testing (buster).
> 
> Now I'm facing this situation:
> * 5031 installed packages
> * 1292 upgradable packages
> 
> If I do a normal upgrade, 676 packages are to be upgraded, but only
> the gtk/qt unrelated ones (for example, apache2-doc but none of the
> apache2 *real* packages, or vim-addon-manager and vim-doc but none of
> the vim *real* packages, and so on)
> 
> And if I try to upgrade, let's say, vim-* packages, it wants to
> remove a ton of seemingly unrelated packages, like calibre,
> evolution, gir1.2-*, gstreamer things, kid3, libqt5-*, pidgin, vlc-*,
> etc etc...
> 
> This happens when I try to upgrade or install apparently *anything*
> related to GUI programs (GTK/Qt related).
> 
> I am worried to make an upgrade like that.
> 
> What can I do to debug this situation and try to understand which
> package(s) is/are breaking everything?

If I were experiencing a similar situation, what I'd do is try to
simultaneously install both one of the packages that triggers the
cascade and one or more of the packages which the cascade wants to
remove, and keep adding packages to the install command until I get a
dependency-resolution failure.

E.g., assuming that trying to upgrade 'vim' triggers the cascade and the
cascade wants to remove calibre, evolution, and pidgin:

$ apt-get install vim calibre evolution pidgin

(In case it wasn't obvious: an 'install' operation on an
already-installed package which has a newer available version triggers
an install of that newer version, i.e., an upgrade.)

If you get a successful upgrade attempt which doesn't trigger the
cascade, you can let it proceed, then try the mass upgrade again. If the
mass upgrade still produces the cascade, you can repeat the
some-small-subset-of-packages manual install process.

If on the other hand the manual install command *does* trigger the
cascade, you should cancel it and add more package names to the install
command.

Keep repeating those two until either the cascade disappears from the
mass-upgrade attempt, or you get a "request cannot be fulfilled"
dependency-resolution failure.

If the cascade disappears along the way, you're in good shape; just
complete the mass upgrade. (Unfortunately, this doesn't really help
figure out what caused the bug in the first place.)

If you get a dependency-resolution failure, the packages involved should
give you a hint about which packages have dependency relationships which
are leading to the cascade.

The next step involves looking at those packages and their dependency
relationships, and I can't describe the process very well without a
real-world example to hand.

Once you've identified the dependency relationship which resulted in the
cascade, it's probably fairly straightforward to determine what bug
report to file and what package to file it against.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: debian/testing repo question

[The Wanderer]

On 2018-07-10 at 10:10, Hans wrote:

> Hi Robert,
> 
> thanks for your quick response. So, doi I see this correct and can I
> say: There is an automatismn for a package removal, which will be
> interrupted, when the maintainer is responding within a period of
> time and the reason for the removal was eliminated (i.e. fixed a bug
> or uploaded a newer version). Whenever a maintainer does nothing, the
> package got to be removed, when its dependencies inmtefere with other
> dependencies, but is left, when its dependencies do not harm
> anything. Can I say so?
> 
> And did I understand you correctly: Using unstable or stable is
> better than to use testing? If I understood this correctly, then the
> logical result would be, that testing has to expect more trouble (for
> users) than stable or unstable,
> 
> Most users I am supporting are using stable, but some are using
> testing. Should I advise them to upgrade tu unstable?

*NO*.

Unstable should be run only by people who are willing to accept
considerable risk of system breakage, and report bugs when things do
break, and (if possible) be involved in trying to fix those bugs. It
should certainly not be run by anyone without enough technical savvy to
support their own systems.

If you aren't willing to accept risk at all, run stable.

If stable isn't enough, but you aren't willing to accept the full risk
that comes with running unstable, run testing - but accept that this
involves a risk that packages you previously installed may disappear
from the repositories, either temporarily or permanently.

If testing isn't enough, and you're willing to accept the full risk that
any and/or every part of your system might break (possibly in unfixable
ways), then run unstable - but accept that if something breaks as a
result of doing so, you get to keep the pieces.

If none of those three options is good enough, then you're probably out
of luck.


For myself, I track stable+testing, dist-upgrade on at least a weekly
basis, and deal with occasional breakage when it happens.


(I'm really surprised to see someone with an @debian.org address
advising people to run unstable for any other reason than helping with
developing Debian. Cherry-picking a single package from unstable for
new-version reasons may be one thing, but tracking unstable on a
production system is dangerous and inadvisable, and I've gotten multiple
machines into unsupportable configurations that way. I've also seen it
stated repeatedly on debian-devel that people not interested in helping
develop / improve Debian should not run sid.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Buster and apt wanting to remove tons of packages...

[Hans]

Please also note, tzhat there is a difference, between using apt (apt-get) and 
aptitude.

The way, I prefewr, is using apt-get upgrade (which installs only newer 
packages, and let the problematic ones uninstalled), then using apt-get full-
upgrade.

When there are packages deinstalled, reinstall them afterwards.

I know, this is not the best way. 

As itr was mentioned before: Using aptitude (tzhe ncurses gui) can show you, 
which packages are causing trouble. You can set them to hold (aptitude hold 
packagename) and then analyse, what dependencies are causing the trouble.

One package after the other. Yes, it  is annoying, I agree.

Hope this helps still

Best regards

Hans

Re: debian/testing repo question

[Hans]

> 
> For myself, I track stable+testing, dist-upgrade on at least a weekly
> basis, and deal with occasional breakage when it happens.

So do I. But in the past I (some years agho) I ran unstable but never got iun 
big trouble (I believe, I wa just luicky, wasn't I?)


Best 

Hans

Re: Looking for ratings of all-in-one printers for Linux (Ubuntu in particular)

[Gene Heskett]

On Tuesday 10 July 2018 10:09:04 Dan Ritter wrote:

> On Mon, Jul 09, 2018 at 11:38:41PM -0400, Michael Stone wrote:
> > On Mon, Jul 09, 2018 at 07:05:52PM -0400, Dan Ritter wrote:
> > > On Mon, Jul 09, 2018 at 06:53:44PM -0400, Michael Stone wrote:
> > > > On Mon, Jul 09, 2018 at 06:39:29PM -0400, Dan Ritter wrote:
> > > > > You're both missing the main point, which is that a Brother
> > > > > printer with BRscript/3 is essentially a Postscript printer,
> > > > > and you can treat it as one. No drivers needed.
> > > >
> > > > So you can use it as an all-in-one postscript printer/scanner?
> > >
> > > You can use it as a printer. As far as I know there is no such
> > > thing as a "postscript scanner".
> >
> > Well, the original question (see subject line) was about all-in-one
> > printers, which implies more than just printing. It would be sad to
> > see the point of the question lost in all the back and forth.
> >
> > > The Brother all-in-ones tend to have "scan-to-network" abilities,
> > > though, and that doesn't require a driver -- just an internal
> > > FTP or SAMBA server to receive the files. My workplace has a
> > > bunch of these. Walk up, select Scan, select Network, and put
> > > your document(s) in. You get PDFs or TIFFs in your filesystem.
> >
> > That's more of a document scan feature, not so great for scanning
> > tasks where you want more control.
>
> Yes. The all-in-ones are terrible at that, proprietary software
> or not.
>
> -dsr-

In the case of the Brother AIO's not so, mine can do an xsane controlled 
scan in single sheet load mode any size and location on an 11x17 glass. 
It also has a document feeder but xsane does not do duplex except as 
single images. In the case of my MFC-J6920DW, I don't believe the scan 
mechanism can turn the page over but once, which it does by default as 
the ADF works. But you can pick the page up from the output table, and 
without turning it over, place it back on the input ramp, as it actually 
scans the top of the sheet as its fed thru, becoming the bottom on the 
output table. Typical of the ADF's, the scanner head remains fixed but 
the paper is pulled across it.

One thing I might point out is that when driven from an ethernet port, 
there is always a 7 second lag between the access transmission to it, 
and its actually waking up to respond. This is caused by a bad checksum 
of the first 6 commands sent at 1 second intervals, but then the driver 
sends good stuff, ANAICT, till the end of that job.  Verified by 
wireshark watching the net traffic. Why the bad tcp checksum, I haven't 
a clue, but except for the wakeup delay, it just works. Presumably not a 
problem with a usb drive, but the location of the usb plug within the 
housing precludes access with a recommended maximum usb cable length of 
5 feet, unless you put a hub within 15 inches or so of the MFC, the rest 
of the cable is in the machine, useing up the majority of the cables max 
length in the circuitous path inside the machine.

Would I buy another Brother? Yes.
-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: debian/testing repo question

[Roberto C . Sánchez]

On Tue, Jul 10, 2018 at 10:27:19AM -0400, The Wanderer wrote:
> 
> (I'm really surprised to see someone with an @debian.org address
> advising people to run unstable for any other reason than helping with
> developing Debian.

I say that because testing gets "stuck" in various ways.  In particular,
library transitions can  result in the removal of many packages from
testing because of delays in updating them.

> Cherry-picking a single package from unstable for
> new-version reasons may be one thing, but tracking unstable on a
> production system is dangerous and inadvisable,

Using anything other than stable on a production system is rather high
risk.  Testing gets no security support.  Suppose that a package you are
using has a new upsrteam release come out to fix security issues.  The
security team will backport those fixes to stable.  The maintainer will
usually upload a new version to unstable.  There are instances where
that new version also introduces new bugs and is prevented from
migrating to testing.  So now you have a package with potentially severe
security vulnerabilities that you cannot update from Debian sources.

That sounds like a real problem to me.  Of course, there is no guarantee
that unstable will get the latest security-fixed version in a timely
manner.

> and I've gotten multiple
> machines into unsupportable configurations that way. I've also seen it
> stated repeatedly on debian-devel that people not interested in helping
> develop / improve Debian should not run sid.)
> 

That is true of both testing and unstable.  Counterintuitively, unstable
tends to stay broken for shorter periods than testing.  So, for users
who are not willing or able to deal with lengthy delays in problems
being fixed, testing is a bad choice.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: debian/testing repo question

[Roberto C . Sánchez]

On Tue, Jul 10, 2018 at 04:10:22PM +0200, Hans wrote:
> 
> Most users I am supporting are using stable, but some are using testing. 
> Should I advise them to upgrade tu unstable?
> 
For non-production use, unstable or testing should be fine.  Both will
be broken from time-to-time.  The question is whether you are willing to
deal with the different forms of breakage you are likely to encounter
with each.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: debian/testing repo question

[Cindy-Sue Causey]

On 7/10/18, The Wanderer  wrote:
>
> (I'm really surprised to see someone with an @debian.org address
> advising people to run unstable for any other reason than helping with
> developing Debian. Cherry-picking a single package from unstable for
> new-version reasons may be one thing, but tracking unstable on a
> production system is dangerous and inadvisable, and I've gotten multiple
> machines into unsupportable configurations that way. I've also seen it
> stated repeatedly on debian-devel that people not interested in helping
> develop / improve Debian should not run sid.)


+1,000. I played with Sid because it was a cool, nerdy thing to be
able do *so easily*. A few months in, it became very clear just how
UNSTABLE Sid is. It's called that for a reason.

Sid is *NOT* for usage situations where #Life itself... or on a lesser
scale perhaps one's financial status... may possibly be relying on a
computer being available every second Humanly possible.

Stable Stretch right now could be used to change the Lives of poverty
level people by spending time teaching them how to access it via the
very minimalist debootstrap install way. It's a game changer that I
personally haven't been able to duplicate elsewhere so far. *cough*
Hint: I've looked.

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

* Sid and I are on a break. *

Re: Looking for ratings of all-in-one printers for Linux (Ubuntu in particular)

[David Wright]

On Mon 09 Jul 2018 at 19:05:52 (-0400), Dan Ritter wrote:
> On Mon, Jul 09, 2018 at 06:53:44PM -0400, Michael Stone wrote:
> > On Mon, Jul 09, 2018 at 06:39:29PM -0400, Dan Ritter wrote:
> > > You're both missing the main point, which is that a Brother
> > > printer with BRscript/3 is essentially a Postscript printer, and
> > > you can treat it as one. No drivers needed.

I'm not really interested in a PostScript printer per se, but in a
printer that handles PDFs natively. Is this the same thing?

> > So you can use it as an all-in-one postscript printer/scanner?
> 
> You can use it as a printer. As far as I know there is no such
> thing as a "postscript scanner".

What I would understand by the expression "postscript scanner" is
something that scans a document and yields a PDF file. I think
a lot of scanners (most?) will also scan to a JPEG file.

> The Brother all-in-ones tend to have "scan-to-network" abilities,
> though, and that doesn't require a driver -- just an internal
> FTP or SAMBA server to receive the files. My workplace has a 
> bunch of these. Walk up, select Scan, select Network, and put
> your document(s) in. You get PDFs or TIFFs in your filesystem.

That's the sort of thing, but I'm used to it writing the files
onto a USB stick (and prefer that).

Cheers,
David.

Re: Looking for ratings of all-in-one printers for Linux (Ubuntu in particular)

[Dan Ritter]

On Tue, Jul 10, 2018 at 12:53:20PM -0500, David Wright wrote:
> On Mon 09 Jul 2018 at 19:05:52 (-0400), Dan Ritter wrote:
> > On Mon, Jul 09, 2018 at 06:53:44PM -0400, Michael Stone wrote:
> > > On Mon, Jul 09, 2018 at 06:39:29PM -0400, Dan Ritter wrote:
> > > > You're both missing the main point, which is that a Brother
> > > > printer with BRscript/3 is essentially a Postscript printer, and
> > > > you can treat it as one. No drivers needed.
> 
> I'm not really interested in a PostScript printer per se, but in a
> printer that handles PDFs natively. Is this the same thing?

No, but PDF is a simplified, compressed PostScript. It's very
little work for your Debian machine to take a PDF, decapsulate
it and send it off to a PostScript printer. (In this case, a
clone of PostScript.)



> That's the sort of thing, but I'm used to it writing the files
> onto a USB stick (and prefer that).

Most of them do that, too.

-dsr-

Re: Separate /home directories etc?

[David Wright]

On Sun 08 Jul 2018 at 07:47:48 (-0500), Richard Owlett wrote:
> On 07/06/2018 03:47 PM, Richard Owlett wrote:
> >In response to a unrelated post to a LUG, I was asked if I had a
> >separate /home directory. Short answer -- no.
> >
> >I abandoned WinXP when Jessie had become stable.
> >The installer defaults {I assume for cause} to putting every thing
> >on one partition/directory.
> >
> >Where may I read about pros/cons ?
> >TIA
> 
> On 07/06/2018 03:54 PM, Matthew Crews wrote:
> >>Pros to keeping same partition together
> >>Pros: less hassle
> >>Cons: if your / partition drive fails, it takes /home with it
> >>
> >>Separate partitions
> >>Pros: if your / partition drive fails, it does not take /home with it
> >>Pros: easier to run multiple distros
> >>Cons: more hassle
> 
> That was succinct.
> 
> On 07/06/2018 06:40 PM, ntrfug wrote:
> >
> >>The home directory contains not only "personal data" but configuration
> >>directories for all your apps.
> >>
> >>I long ago settled on a middle-of-the-road solution--I have a partition
> >>mounted on /home/ntrfug/files which contains all my "data" such as
> >>email, photos, documents, non-distribution software, bank statements,
> >>etc. I've been doing this for ~20 years and I still like it. I can
> >>reinstall nuking the home directory to take advantage of updated
> >>configurations but still keep my word processing documents, email, and
> >>general umm, stuff.
> >>
> 
> That illustrates why I phrased my question {"Where may I read about
> pros/cons ?"} as I did.
> 
> I expecting referrals to "essay"/"HowTo"/"tutorial"/??? .
> There have bee several descriptions of how&why individuals do what they do.
> 
> I was expecting an article which surveyed the topic, seeing "the
> forest not the trees".

Is it a big enough topic to deserve a whole article? I would expect
articles on partitioning to mention it in passing, as for example:
https://wiki.archlinux.org/index.php/partitioning
(The Debian wikis are rather shallow.)
But, as it stresses, "It is essentially personal preference" as to
how you arrange your partitions, because it depends so much on how
you use your system.

Their caveat on sharing /home has been emphasised here in stronger
terms by Greg, and really applies more to DE users than people like me.
https://lists.debian.org/debian-user/2018/07/msg00337.html

With the number of Debian installations you have, I would expect a
shared home to be very useful as it makes your personal tools more
immediately available. It might be useful to hear whether you have
much dotfile trouble, and how you circumvent it. This could be a
useful application of your WhereAmI and EditingPipedSreams threads.
But only you can be the judge of the pros and cons for your system.

Cheers,
David.

Re: A "Where am I" routine

[David Wright]

On Fri 06 Jul 2018 at 06:25:43 (-0500), Richard Owlett wrote:
> I multi-boot several configurations &/or releases of Debian.
> I will run identical test scripts on each.
> I want to store the results in a common logging file.

If you're going to compare your test runs, you might be better off
storing the results in separate files, either named for the
configuration, or in directories named that way. It's a lot easier to

diff -u configuration-A/test-2.log configuration-B/test-2.log | less

than to compare the corresponding lines from different sections of the
same, common logging file (involving a lot of plumbing).

Cheers,
David.

Re: More on locale

[jpff]

I have those files except the last htl one.

I should have added that I have been running this macine for years and 
this started recently, a month or two I think.


On Tue, 10 Jul 2018, Zenaan Harkness wrote:


On Mon, Jul 09, 2018 at 06:37:19PM +0100, John wrote:

A short time ago I sought your advice about messages  I am getting
about locales  I thought I did what was suggested but I still see

  CC   libclamav_internal_utils_nothreads_la-strlcat.lo
../libtool: line 1748: warning: setlocale: LC_CTYPE: cannot change
locale (en_US.UTF-8)
when compiling, and

(firefox-esr:11622): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.

from firefox.  There are other similar.   I have not got this problem
on any other machine.  How can I fix it, and ensure it does not happen
again?


I'm not sure, but try running locate on your locale e.g.:

$ locate en_US.UTF-8
/usr/share/X11/locale/en_US.UTF-8
/usr/share/X11/locale/en_US.UTF-8/Compose
/usr/share/X11/locale/en_US.UTF-8/XI18N_OBJS
/usr/share/X11/locale/en_US.UTF-8/XLC_LOCALE
/usr/share/doc/libx11-dev/i18n/compose/en_US.UTF-8.html


If you don't have those (or similar) locale files, you need to enable
and generate that (evidently required, based on your environment)
locale.

Good luck,

Re: Looking for ratings of all-in-one printers for Linux (Ubuntu in particular)

[Brian]

On Tue 10 Jul 2018 at 14:20:50 -0400, Dan Ritter wrote:

> On Tue, Jul 10, 2018 at 12:53:20PM -0500, David Wright wrote:
> > On Mon 09 Jul 2018 at 19:05:52 (-0400), Dan Ritter wrote:
> > > On Mon, Jul 09, 2018 at 06:53:44PM -0400, Michael Stone wrote:
> > > > On Mon, Jul 09, 2018 at 06:39:29PM -0400, Dan Ritter wrote:
> > > > > You're both missing the main point, which is that a Brother
> > > > > printer with BRscript/3 is essentially a Postscript printer, and
> > > > > you can treat it as one. No drivers needed.
> > 
> > I'm not really interested in a PostScript printer per se, but in a
> > printer that handles PDFs natively. Is this the same thing?
> 
> No, but PDF is a simplified, compressed PostScript. It's very
> little work for your Debian machine to take a PDF, decapsulate
> it and send it off to a PostScript printer. (In this case, a
> clone of PostScript.)

"decapsulates"? Please explain; it is a term I've not encountered in
relation to printers. (The query was about printers which *natively*
accept a PDF and just print it without any CUPS involvement).

> > That's the sort of thing, but I'm used to it writing the files
> > onto a USB stick (and prefer that).
> 
> Most of them do that, too.

Most printers on Debian do what?

-- 
Brian.

Re: A "Where am I" routine

[john doe]

On 7/10/2018 8:40 PM, David Wright wrote:

On Fri 06 Jul 2018 at 06:25:43 (-0500), Richard Owlett wrote:

I multi-boot several configurations &/or releases of Debian.
I will run identical test scripts on each.
I want to store the results in a common logging file.


If you're going to compare your test runs, you might be better off
storing the results in separate files, either named for the
configuration, or in directories named that way. It's a lot easier to

diff -u configuration-A/test-2.log configuration-B/test-2.log | less



The option '-s' is also useful to know if the files are identical.

--
John Doe

Re: Looking for ratings of all-in-one printers for Linux (Ubuntu in particular)

[Brian]

On Tue 10 Jul 2018 at 12:53:20 -0500, David Wright wrote:

> On Mon 09 Jul 2018 at 19:05:52 (-0400), Dan Ritter wrote:
> > On Mon, Jul 09, 2018 at 06:53:44PM -0400, Michael Stone wrote:
> > > On Mon, Jul 09, 2018 at 06:39:29PM -0400, Dan Ritter wrote:
> > > > You're both missing the main point, which is that a Brother
> > > > printer with BRscript/3 is essentially a Postscript printer, and
> > > > you can treat it as one. No drivers needed.
> 
> I'm not really interested in a PostScript printer per se, but in a
> printer that handles PDFs natively. Is this the same thing?
> 
> > > So you can use it as an all-in-one postscript printer/scanner?
> > 
> > You can use it as a printer. As far as I know there is no such
> > thing as a "postscript scanner".

The adjective refers to the printer not the scanner. So you are (in
your misunderstanding) are correct.
 
> What I would understand by the expression "postscript scanner" is
> something that scans a document and yields a PDF file. I think

An interesting thought.

> a lot of scanners (most?) will also scan to a JPEG file.

Only if the SANE frontend supports it.

> > The Brother all-in-ones tend to have "scan-to-network" abilities,
> > though, and that doesn't require a driver -- just an internal
> > FTP or SAMBA server to receive the files. My workplace has a 
> > bunch of these. Walk up, select Scan, select Network, and put
> > your document(s) in. You get PDFs or TIFFs in your filesystem.
> 
> That's the sort of thing, but I'm used to it writing the files
> onto a USB stick (and prefer that).

Try using a Brother aio on linux without the non-free Brother-provided
brscan-skey software. If that isn't a "driver" - what is?

-- 
Brian.

Re: Buster and apt wanting to remove tons of packages...

[Jochen Spieker]

sgarrulo:
>
> I had an installation of debian stable (stretch) which was fully upgraded 
> something
> like a couple of months ago. Then I passed it to testing (buster).

There should not be that many changes, but I generally would only
upgrade to a newer release when the current system is up-to-date with
regards to its current version.

> If I do a normal upgrade, 676 packages are to be upgraded, but only the 
> gtk/qt unrelated ones
> (for example, apache2-doc but none of the apache2 *real* packages, or 
> vim-addon-manager and vim-doc
> but none of the vim *real* packages, and so on)

I would start with that, if only to get these packages out of the way.

> And if I try to upgrade, let's say, vim-* packages, it wants to remove a ton 
> of seemingly unrelated
> packages, like calibre, evolution, gir1.2-*, gstreamer things, kid3, 
> libqt5-*, pidgin, vlc-*, etc etc...
> 
> This happens when I try to upgrade or install apparently *anything* related 
> to GUI programs (GTK/Qt related).

You can use aptitude's TUI to investigate these things. It should at
least help explain why this happens. It is very possible (or likely),
that testing is just in bad shape for this upgrade right now.

(And no, reporting this as a bug is of no help here because the Debian
release process is not designed to support what you are trying to do at
a random point in time.)

> I am worried to make an upgrade like that.

Rightly so.

> What can I do to debug this situation and try to understand which package(s) 
> is/are breaking everything?

Aptitude. I do not like how it behaves and how you control it, but for
this kind of investigation it is without alternative. Instead of the TUI
you can also use 'aptitude why' and 'aptitude why-not'.

J.
-- 
People talking a foreign language are romantic and mysterious.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

THANKYOU**Googleplex - was (Re: Separate /home directories etc?)

[Richard Owlett]

On 07/10/2018 01:28 PM, David Wright wrote:

[snip]
Is it a big enough topic to deserve a whole article? I would expect
articles on partitioning to mention it in passing, as for example:
https://wiki.archlinux.org/index.php/partitioning


That, with the benefit of article it references, is exactly what I was 
looking for.
In making the point that partitioning schemes are a *PERSONAL Y UNIQUE* 
choice, it {and linked articles} give background for reasoned choices.


{As a bonus, one of the articles may have given me a hint to resolve a 
perceived problem [N.B. word choice;] I have with GRUB2.}


A more complete response will follow after a detailed read and much 
cogitation.


IOW  *THANK YOU* !!

Re: A "Where am I" routine

[Richard Owlett]

On 07/10/2018 01:40 PM, David Wright wrote:

On Fri 06 Jul 2018 at 06:25:43 (-0500), Richard Owlett wrote:

I multi-boot several configurations &/or releases of Debian.
I will run identical test scripts on each.
I want to store the results in a common logging file.


If you're going to compare your test runs, you might be better off
storing the results in separate files,


I wish a common log file.
I was envisioning a "function" {wrong word?}, which would return "Where 
you came from" as an introductory header.
A better response later, I've just been given a hint to solving 2 
(apparently unrelated) problems of higher priority.


P.S. You supplied the hint ;}

Re: Debian testing - release number

[David Wright]

On Fri 06 Jul 2018 at 08:41:58 (+), Curt wrote:
> On 2018-07-06, David Wright  wrote:
> 
> > Hmm, I struggle to see the connection between what I asked for and
> > what you wrote. From your later post, I guess the answer is that
> > editing /etc/debian_version risks provoking expletives from other
> > users of the system.
> >
> > That said, I do agree with what you wrote.
> 
> So wait, now, after saying this
> 
>  What seems to be lost on people who feel a pressing need for
>  /etc/debian_version to contain a number to satisfy some script that
>  they have written (which seems to be the usual reason) is that
>  /etc/debian_version is a configuration file. Look in the
>  .deb file and there it is, along with /etc/issue{,.net} which
>  determine how you are greeted {locally,remotely}. So admins are
>  free to set them all how they like.

That paragraph is a correct quotation of what I wrote.

> we discover that what you actually believe is, although admins are free to do
> so (like you're free to blindfold yourself and jog in the middle of the 
> freeway
> at rush hour in L.A with a broom sticking out of your wazoo), you'd have to be
> insane to actually edit /etc/debian_version, which is *not*, in fact, a
> configuration file

This is something you just made up and is unrelated to what I have written.

> (because that's what Wooledge said that you're agreeing
> with here)?

[I think you mean "because that's what Wooledge said, which you're agreeing
with here".]

Perhaps you have temporarily forgotten how quoting should work on a
mailing list, and therefore your interpretation of
https://lists.debian.org/debian-user/2018/07/msg00199.html
is completed erroneous. Read what I posted:

1)

"[DW] Hmm, I struggle to see the connection between what I asked for
 and what you wrote."

In other words, this reply:

'[GW] Your hypothetical case describes a shell script that is
 supposed to detect what version of Debian it's running on,
 for whatever reason.
 If this script doesn't know how to handle the string
 "testing/unstable" then it's doing a really crappy job of
 "supporting" Debian systems.'

does not answer:

"[DW] Would you explain what is unsafe about it and why
 /etc/debian_version is a configuration file, or offer
 a sensible alternative."

2)

"[DW] That said, I do agree with what you wrote."

In other words, I agree with the statement I quoted there:

'[GW] Your hypothetical case describes a shell script that is
 supposed to detect what version of Debian it's running on,
 for whatever reason.
 If this script doesn't know how to handle the string
 "testing/unstable" then it's doing a really crappy job of
 "supporting" Debian systems.'

It doesn't mean I agree with everything they ever wrote in the thread
on the matter, just what I quoted, which is why I quoted it.

> So, Joey Hess is a crazy idiot, for instance?

Why would you think of calling Joey a "crazy idiot"?

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81249
> 
>  Local changes made to /etc/debian_version (in this case changing it from
>  "testing/unstable" to "unstable" since that is what this system is really
>  using) are wiped out when the package is upgraded or reinstalled:

The evidence presented in the bug report clearly shows that
/etc/debian_version gets overwritten, so one has to assume that,
at the time, it wasn't flagged as a conffile. That's supported
by typing:

$ zgrep -A7 '(2.2.8)' /usr/share/doc/base-files/changelog.gz

There was some debate around this time about what /etc/debian_version
should contain during development, as you can see with:

$ zgrep -A16 '(2.2.6)' /usr/share/doc/base-files/changelog.gz

The fact that /etc/debian_version *is* a *configuration* file
was clearly promulgated in:

https://lists.debian.org/debian-devel/2001/01/msg00502.html

Cheers,
David.

VPN suggestions?

[Dennis Wicks]

Greetings;

I want to set up a VPN for several computers in my house
that are all on a local network.

And suggestions, hints, warnings?

TIA!!
Dennis

Re: VPN suggestions?

[Ben Finney]

Dennis Wicks  writes:

> I want to set up a VPN for several computers in my house that are all
> on a local network.

What do you mean by “set up a VPN”?

Is it sufficient to pay someone else to host the VPN, and your computers
connect to that VPN managed by someone else?

Do you expect to manage the VPN software? The hardware? Or do you want
that job done by someone else?

> And suggestions, hints, warnings?

Be sure that the VPN is run by someone invested in *your* security. This
excludes parties that offer “zero cost VPN” to all-comers; their
incentive is mostly to turn your traffic into money, which almost
certainly conflicts with your privacy.

So, that means either you (or a party who already has your trust and has
no conflict with your interests) set up the VPN specifically for you;
or, you find a managed VPN for whom *you are the customer*, so that they
will want to serve your needs and not someone else's.

Once you explain more what your purpose is (and what you mean by “set up
a VPN”), we can give more specific advice.

-- 
 \   “One of the most important things you learn from the internet |
  `\   is that there is no ‘them’ out there. It's just an awful lot of |
_o__)‘us’.” —Douglas Adams |
Ben Finney

Re: VPN suggestions?

[Gene Heskett]

On Tuesday 10 July 2018 19:26:17 Ben Finney wrote:

> Dennis Wicks  writes:
> > I want to set up a VPN for several computers in my house that are
> > all on a local network.
>
> What do you mean by “set up a VPN”?
>
> Is it sufficient to pay someone else to host the VPN, and your
> computers connect to that VPN managed by someone else?
>
> Do you expect to manage the VPN software? The hardware? Or do you want
> that job done by someone else?
>
> > And suggestions, hints, warnings?
>
> Be sure that the VPN is run by someone invested in *your* security.
> This excludes parties that offer “zero cost VPN” to all-comers; their
> incentive is mostly to turn your traffic into money, which almost
> certainly conflicts with your privacy.
>
> So, that means either you (or a party who already has your trust and
> has no conflict with your interests) set up the VPN specifically for
> you; or, you find a managed VPN for whom *you are the customer*, so
> that they will want to serve your needs and not someone else's.
>
> Once you explain more what your purpose is (and what you mean by “set
> up a VPN”), we can give more specific advice.

+100 on this advice.

For instance, and this is just one way, decades ago I set all my stuff up 
on 192.168.xx.zz addresses, which are NOT propagated thru a router to 
the internet or vice versa.

I have one outward facing address at a fixed ipv4 address determined by 
the MAC of the router. That router is running dd-wrt. As is a spare that 
has its MAC set to clone the main router. It also runs iptables and 
dnsmasq. All local addresses are in the hosts files, identical on all 
machines, with resolv.conf set to search hosts, dns. The dns is the 
routers local address on all machines, so that if where I want to go is 
not a local address obtainable from the hosts file, then the router is 
queried, which if dnsmasq has not already cached the lookup, sends the 
dns request on to my ISP's dns server. And it all happens in 
milliseconds, so my access to the net from any of my machines is 
transparent. Yet in nearly 2 decades, only one person has been able to 
get into this system, and he was both invited and given the login/pw's 
to do it.

As a guard dog, dd-wrt has very quick reflexes and sharp teeth.

And there is nothing virtual about it. Yet it Just Works(TM).

I do have a couple 8 port switches in order to give me that connectivity 
here, and in the garage, plus a 4 port hub in a smaller outbuilding to 
hook it all up. That 90 foot piece of cat5 to that outbuilding from the 
house has now been blowing in the wind for nearly 2 decades, surviving a 
100+ mph blow that took down 4, 30 yo 40+ ft pine trees, part of this 
houses roof, and about 70 feet of privacy fence. And it still works.

Thats how I do it.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: VPN suggestions?

[Joe Pfeiffer]

Dennis Wicks  writes:

> Greetings;
>
> I want to set up a VPN for several computers in my house
> that are all on a local network.
>
> And suggestions, hints, warnings?

Your question as stated doesn't really explain why you want a VPN, and
what you're planning to do with it.  All you've mentioned is a private
network; if that's all you're doing, there's no reason to have a virtual
private network on top of it.

FWIW, I've got a few machines at home that are networked, but get in
remotely from my laptop using a VPN.  It's hosted on one of my machines,
and I'm just using openvpn.

Re: Required help on local Debain mirror

[Zenaan Harkness]

On Wed, Aug 30, 2017 at 12:31:06PM -0500, David Wright wrote:
> On Wed 30 Aug 2017 at 17:27:31 (+0200), Christian Seiler wrote:
> > Hi there,
> > 
> > Am 2017-08-29 11:57, schrieb Kala Techies:
> > >I am using (Debian GNU/Linux 6.0.10 (squeeze)) in my environment and I
> > >want to update all systems using one local mirror.
> > 
> > I don't think it's a good idea to setup a real local mirror,
> > as that means you'll download the entire archive, which is
> > likely going to be a _lot_ more stuff (especially if you
> > download all available architectures) than upgrading each
> > machine individually.
> > 
> > What you'll rather want is to setup a local proxy server
> > that'll cache the packages. This way you'll only download
> > what you actually need, but you'll also only download it
> > once.
> > 
> > I can recommend the apt-cacher-ng package for that.
> 
> However, be prepared for problems if you run a version of
> apt-cacher-ng as old as squeeze's.
> 
> I still run apt-cacher-ng on a wheezy machine and have had to switch
> between the backports and backports-sloppy versions, currently the
> latter, 0.9.1-1~bpo7+1. The main failures have been (1) expiration of
> old packages¹, (2) new compression schemes² for Packages files, (3)
> new InRelease files and (4) servicing apt-listbugs³ searches. I use it
> for wheezy and jessie, but have made no attempt to use it with
> stretch; is that when hashed indexing started?
> 
> I don't know how many of these issues will affect a constituency of
> totally squeeze PCs; I guess that depends on whether the mirrors
> being used have been updating their apt methods, and if there are
> squeeze backports.
> 
> ¹ie the archive grows for ever.
> ²eg .xz and/or .bz2 files.
> ³my current command sequence for upgrading is the unwieldy
> # apt-get -o Acquire::http::Proxy="http://192.168.1.19:3142/"; update
> # apt-get -d -o Acquire::http::Proxy="http://192.168.1.19:3142/"; upgrade
> # apt-get upgrade

Some years ago I had much success running squid proxy server on a
gateway / router box, and as long as your sources for your internal
network boxes are used protocols cached by squid, it works well.

apt-cacher-ng and the like are a little more intelligent though,
AFAIK, knowing to immediately discard things which always change for
example... but perhaps someone has already written equivalent squid
rule files...

As a bonus with squid - it caches other things - e.g. images, web
content etc - someone watches a 300MiB YouTube and emails a
co-worker, who immediately also watches it - the second one hits the
cache. That was years ago though, so these days you might need extra
config for such sites:

https://wiki.squid-cache.org/ConfigExamples/DynamicContent/YouTube

https://serverfault.com/questions/9281/how-can-i-cache-youtube-videos-with-squid-cache

How well or possible or what's required to "break HTTPS" and make
squid work with e.g. https://youtube.com is another question :)

Re: Separate /home directories etc?

[Matthew Crews]

On 7/10/18 3:28 AM, Jonathan Dowland wrote:
> On Fri, Jul 06, 2018 at 04:54:53PM -0400, Matthew Crews wrote:
>> Separate partitions
>> Pros: if your / partition drive fails, it does not take /home with it
> 
> You are conflating drives and partitions, here. Both partitions could be
> on the same physical drive, and a drive failure would affect both in
> that case.
> 
> 

True, the main reason you would want /home to be in a separate partition
is to put it on a separate physical drive. However, random file system
corruption could still theoretically take out the / partition without
actually damaging the device. In that case, /home being separate would
spare your data.

Another reason you would want a separate /home partition is to use a
separate file system. For example, you could run / as BTRFS, while /home
would be XFS or ext4.

Re: No full upgrade to Nvidia 390.67 from bpo

[Matthew Crews]

On 7/10/18 5:14 AM, mlnl wrote:
> Hi,
> 
> i'm using stretch-backports but i can't get the full upgrade to Nvidia
> 390.67. The aptitude log shows:
> 
> Aptitude 0.8.7: log report
> Mon, Jul  9 2018 14:04:18 +0200
> Will install 9 packages, and remove 0 packages.
> 
> [HOLD, DEPENDENCIES] libegl1-mesa:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] libegl1-mesa-dev:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] libgbm1:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] libgl1-mesa-dev:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] libgl1-mesa-glx:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] libglapi-mesa:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] libgles2-mesa:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] libwayland-egl1-mesa:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] mesa-common-dev:amd64 13.0.6-1+b2
> [HOLD, DEPENDENCIES] nvidia-alternative:amd64 390.48-2~bpo9+3
> [HOLD, DEPENDENCIES] nvidia-vdpau-driver:amd64 390.48-2~bpo9+3
> [HOLD] libcuda1:amd64 390.48-2~bpo9+3
> [HOLD] libegl-nvidia0:amd64 390.48-2~bpo9+3
> [HOLD] libgl1-nvidia-glvnd-glx:amd64 390.48-2~bpo9+3
> [HOLD] libgles-nvidia1:amd64 390.48-2~bpo9+3
> [HOLD] libgles-nvidia2:amd64 390.48-2~bpo9+3
> [HOLD] libgles1-nvidia:amd64 390.48-2~bpo9+3
> [HOLD] libgles2-nvidia:amd64 390.48-2~bpo9+3
> [HOLD] libglx-nvidia0:amd64 390.48-2~bpo9+3
> [HOLD] libnvcuvid1:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-cfg1:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-compiler:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-egl-wayland1:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-eglcore:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-encode1:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-fatbinaryloader:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-fbc1:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-glcore:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-ifr1:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-ml1:amd64 390.48-2~bpo9+3
> [HOLD] libnvidia-ptxjitcompiler1:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-driver:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-driver-bin:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-driver-libs:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-egl-icd:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-egl-wayland-icd:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-kernel-dkms:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-kernel-support:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-opencl-icd:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-smi:amd64 390.48-2~bpo9+3
> [HOLD] nvidia-vulkan-icd:amd64 390.48-2~bpo9+3
> [HOLD] xserver-xorg-video-nvidia:amd64 390.48-2~bpo9+3
> [UPGRADE] nvidia-cuda-mps:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-detect:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-egl-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-egl-wayland-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-kernel-source:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-legacy-check:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-libopencl1:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-opencl-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> [UPGRADE] nvidia-vulkan-common:amd64 390.48-2~bpo9+3 -> 390.67-2~bpo9+1
> 
> Any hints, what i can do to solve the problem?
> 
> Thx.
> 

The only way I was able to resolve this was to uninstall the nvidia
drivers from the main repo, then reinstall via backport repo. Be careful
doing this though.

Remember to make sure you have the kernel headers for your specific
linux kernel installed as well, or else DKMS will fail, and you will be
left with a partially broken system.

How to"apt update" from an USB key ?

[Pierre Couderc]

On an ultraslim (ACER swift 3) I have no CDROM no Ethernet, only an USB key.
I have installed stretch (without GUI) from the USB key, and now I want 
to install connman, but I do not success to apt-cdrom on an USB.

I have googled but did not find a correct howto to do that...

Thanks in advance
PC

Re: How to"apt update" from an USB key ?

[john doe]

On 7/11/2018 7:10 AM, Pierre Couderc wrote:
On an ultraslim (ACER swift 3) I have no CDROM no Ethernet, only an USB 
key.
I have installed stretch (without GUI) from the USB key, and now I want 
to install connman, but I do not success to apt-cdrom on an USB.

I have googled but did not find a correct howto to do that...



Why not updating/installing using your internet connection?

If the package that you want to install is on your usb key you will need 
to modify /etc/apt/sources.list accordingly.:


https://askubuntu.com/questions/3576/how-to-make-usb-drive-as-local-repository

--
John Doe

Re: How to"apt update" from an USB key ?

[john doe]

On 7/11/2018 7:55 AM, Pierre Couderc wrote:

On 07/11/2018 07:27 AM, john doe wrote:

On 7/11/2018 7:10 AM, Pierre Couderc wrote:
On an ultraslim (ACER swift 3) I have no CDROM no Ethernet, only an 
USB key.
I have installed stretch (without GUI) from the USB key, and now I 
want to install connman, but I do not success to apt-cdrom on an USB.

I have googled but did not find a correct howto to do that...



Why not updating/installing using your internet connection?

Because I have no internet connexion for the moment...


If the package that you want to install is on your usb key 
For the moment, my usb key contians a dd 
if=debian-9.4.0-amd64-DVD-1.iso  of=/dev/sdc

you will need to modify /etc/apt/sources.list accordingly.:

https://askubuntu.com/questions/3576/how-to-make-usb-drive-as-local-repository 

I had soon tried many of the solutions proposed here and none did work. 
Maybe, you have a specific idea about which is "the" correct one ?




No, other then insuring that the pkg that you want is on that "dvd".

--
John Doe

Re: anybody maintaining lxc and lxd in Debian?

[Harald Dunkel]

On 7/10/18 12:36 PM, Jonathan Dowland wrote:
> On Fri, Jul 06, 2018 at 09:56:58AM +0200, Harald Dunkel wrote:
>> is anybody maintaining lxc in Debian? I have the impression that
>> it has been orphaned. And I don't dare to hope for #768073 anymore.
>
> Ah yes I'd forgotten about that (I was involved for a while). But
> looking at the current status it's not as bleak as I feared; the last
> dependency was finally finished in February.
>

I saw the updates in #768073. Good to know that it hasn't been forgotten.

How about LXC? In the meantime I built and tried Ubuntu's version 3.0.1
on Stretch. It builds fine. The package upgrade path was a little bit
rough, but it seems to work. Didn't try apparmor, though. Kernel was
4.16.12-1~bpo9+1.

One problem here: LXC 2.1 (not available in Debian) could be used to
migrate to the new config file format. 3.0.1 doesn't support the old
format anymore, i.e. running LXC 2.0 it is *mandatory* to adjust the
config files for 3.0.1 (using the provided lxc-update-config script).


Regards
Harri