Re: Slic3r --gui won't run

[Steve McIntyre]

Gene Heskett wrote:
>
>So please tell me why, despite all the other distributions using your 
>code base to make extremely stable versions of buster, has debian rather 
>pointedly, indeed gone out of your way, to unsupport the rpi's?

Nobody has "gone out of their way" to *unsupport* anything. That's a
particularly cynical (and frankly downright insulting) way to describe
things.

There's two things in play here:

 * Debian's is a Free Software project. Platforms that depend on
   non-free things for core things (like boot) are never going to be
   as well-supported as platforms where we can include everything
   needed. Other distributions may not care so much, that's up to
   them.
   
   Part of our commitment to Free Software includes providing the
   pieces for others to use how they want, hence Armbian / Raspbian /
   Ubuntu / Mint (and many others) can release their own
   differently-focussed OS without having to invent it all from
   scratch.

 * Debian is a volunteer project - people basically work on what
   interests them. That means that some things may not get the focus
   or effort that some users would like. There's scope to get involved
   or to convince existing developers to work on different stuff.

On the Pi 4, it looks like there's finally (IMHO) a good option -
using an EDK2 build in flash allows you to have a properly Free OS on
top of that, using UEFI to boot. If I had an interest in the Pi,
that's what I would be playing with.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Ma, 21 iul 20, 14:42:02, rhkra...@gmail.com wrote:
> On Tuesday, July 21, 2020 02:47:47 AM Andrei POPESCU wrote:
> > On Lu, 20 iul 20, 13:46:28, Greg Wooledge wrote:
> > > If synaptic is pulling in *-backports without you manually DOING
> > > something to select the backport over the standard version, then
> > > synaptic is broken.  Broken-er.  More broken-er.
> > 
> > In synaptic's defence, it probably doesn't have a choice if -backports
> > (and -security?) is the only available repository. See Gene's original
> > sources.list.
> 
> I can look for the reference, but somewhere I read (recently, but as with all 
> google searches, it could have been from the previous century) something to 
> the effect that, well, I forget which way it worked, but somehow that maybe 
> non 
> backport applications would get a pin value like 100 so that backport 
> applications would only be installed if somehow they had a higher pin value 
> (or something like that).

APT's default priority is 500, exceptions in Debian are 'experimental' 
(1) and 'backports' (100).

Because installed packages have priority 100 as well, for a properly 
configured (old)stable + backports system you must use '-t' to install 
packages from backports.

Upgrades will then automatically pull from backports (because the 
versions are higher than the "regular" repository).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Ma, 21 iul 20, 08:52:07, Gene Heskett wrote:
> 
> What has amazed me from the gitgo, is that the single most popular by a 
> wide margin, arm based board, outnumbering all others combined by a 
> wide margin, gets zero support from debian. 

Debian's contribution to hardware support is limited to enabling 
specific options in the kernel or, occasionally, backporting patches 
that have already been accepted upstream.

Other distributions are either using different kernels or non-upstreamed 
patches.

Video support often requires closed source drivers, that nobody bothered 
to package for 'nonfree' (assuming they are even distributable).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[mick crane]

On 2020-07-19 13:00, Gene Heskett wrote:

Greetings all;

Very disapointed in the results from the openscad to Cura to ender 3 
pro

results. Forstarters, no support for gcodes g2/g3 so everything has to
be cobbled up with short straight lines.

So I installed slic3r. but all I get is the help screen which is 
several

pages long. But one of the options is to start it with -gui as option.

That also fails, looking for Wx.

Full error report:

gene@coyote:~/Downloads/stl.stf/files$ slic3r --gui
Can't locate Wx.pm in @INC (you may need to install the Wx module) 
(@INC

contains: /usr/bin/lib /usr/lib/slic3r/ /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24
/usr/share/perl/5.24 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base)
at /usr/lib/slic3r/Slic3r/GUI/AboutDialog.pm line 6.
BEGIN failed--compilation aborted
at /usr/lib/slic3r/Slic3r/GUI/AboutDialog.pm line 6.
Compilation failed in require at /usr/lib/slic3r/Slic3r/GUI.pm line 8.
BEGIN failed--compilation aborted at /usr/lib/slic3r/Slic3r/GUI.pm line
8.
Compilation failed in require at (eval 77) line 1.

This is stretch, uptodate. What can I do?  Backports doesn't seem to be
enabled.

Cheers, Gene Heskett


excuse me for not knowing what I'm talking about but if is a Perl module 
you are after cannot use cpan ?


mick
--
Key ID4BFEBB31

Re: Slic3r --gui won't run

[rhkramer]

On Monday, July 20, 2020 10:11:40 AM rhkra...@gmail.com wrote:
> On Monday, July 20, 2020 06:58:10 AM Andrei POPESCU wrote:
> > "the latest candidate version" would be more accurate. If you think this
> > wording is an improvement feel free to file a wishlist bugs against
> > 'apt' (the package).
> 
> Thanks -- I'll probably let that percolate in my head for a little while
> before I file a bug -- it's probably good wording, but there is no need to
> jump to a conclusion -- maybe we (collectively) will come up with
> something better or recognize this as the best choice.

...

> Thanks!  (But, nothing shows up there as pinned -- I probably have a lot
> more to learn here, but, as my current problem is solved, may not dig into
> it.)

Darn. I shouldn't have said that -- I seem to be going down the rabbit hole 
;-(

I've decided to think further about a possible bug report, and the following 
is sort of a first draft / thinking out loud approach to the subject (with some 
false starts along the way.  I had a headache when I wrote this, I'm trying to 
dress it up a little, but not sure how well I'll do.

I see it in two parts (as you read on) -- first establishing the possible 
situations reflected by the existing message, and then some brainstorming on 
possible changes to the message.

The messages is like this:

= 
Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) but 3.0.4+dfsg-4~bpo9+1 is to be 
installed
=

There can be 2 (or 3?) cases when that message appears:

   * the bpo9 (to use some improvised shorthand) version is to be installed, 
but would not satisfy the dependency for the package you've asked apt-get (or 
similar) to install (can this be the case? -- this is not the case I 
encountered, and I'm not 100% sure it can occur -- more discussion somewhere 
below)

   * the bpo9 version is already installed, but does not satisfy the 
dependency for the package you've asked apt-get (or similar) to install (this 
is the case I encountered (for openssh-server on Wheezy))

   * is there another case?

So, I don't like the wording as is (I mean, it took me (and, apparently, Gene) 
too much effort to understand it).  

I'm not sure I like calling it a candidate, either, especially if it is 
already installed.  

And, if the only case is the one where it has already been installed (I bring 
this up because the 2nd is the only case that I've encountered (iirc)), then 
wording more like might be more helpful:

Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) is required, but 
3.0.4+dfsg-4~bpo9+1 is installed

Hmm, maybe the first case can come up when the non-bpo9 version is already a 
dependency for some other package, and removing it to install the bp09 would 
break that other package (not the one that apt-get is attempting to install)?

But for that case, wording like this might be better:

Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) is required for , but 3.0.4+dfsg-4~bpo9+1 is installed (required) 
for 

 might display the list of other packages, or just say 
"other packages" (as long as there is a tool to easily discover those other 
packages, which I believe there is, but I can't instantly recite the tool / 
command).

Or, somewhat combinging the two cases (that I've discussed so far) -- for 
either case (note the optional part (in square brackets)):

Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) is required for , but 3.0.4+dfsg-4~bpo9+1 is installed [for 
]

An alternate wording to consider if the current installed version (the bpo9) 
version could be " ... is an orphan"  (Even though, in a way, iiuc, that 
should not occur -- I mean, iiuc, if a package is not required, running apt-
get -autoremove will remove such packages.  

Hmm, I guess add  a caveat / question -- if a package has been installed as a 
dependency for an application / program installed by the user by means other 
than the debian packaging system, I don't think that apt[-get] will recognize 
it as a dependency?

As another comment, now that I understand the message, it isn't as hard to 
understand, but what about the next newbie to that message?

Re: Slic3r --gui won't run

[rhkramer]

On Tuesday, July 21, 2020 02:47:47 AM Andrei POPESCU wrote:
> On Lu, 20 iul 20, 13:46:28, Greg Wooledge wrote:
> > If synaptic is pulling in *-backports without you manually DOING
> > something to select the backport over the standard version, then
> > synaptic is broken.  Broken-er.  More broken-er.
> 
> In synaptic's defence, it probably doesn't have a choice if -backports
> (and -security?) is the only available repository. See Gene's original
> sources.list.

I can look for the reference, but somewhere I read (recently, but as with all 
google searches, it could have been from the previous century) something to 
the effect that, well, I forget which way it worked, but somehow that maybe non 
backport applications would get a pin value like 100 so that backport 
applications would only be installed if somehow they had a higher pin value 
(or something like that).

Maybe that goes out the window if all / the only repositories were backport 
repositories?

(BTW, if it's not yet clear, I'm going down the rabbit hole ;-(

Re: Slic3r --gui won't run

[Gene Heskett]

On Tuesday 21 July 2020 07:45:03 Greg Wooledge wrote:

> On Tue, Jul 21, 2020 at 09:43:52AM +0300, Andrei POPESCU wrote:
> > Most of the hardware support is in the kernel and as far as I can
> > tell buster should run with a 4.2 kernel (required by systemd).
>
> The release notes for buster say that it requires a 3.2 kernel due
> to GNU libc.
>
> https://www.debian.org/releases/buster/amd64/release-notes/ch-informat
>ion.en.html#glibc-and-linux
>
> This is the reason why my VPS, which is running under a 2.6 kernel,
> cannot be upgraded past stretch.
>
> To the best of my knowledge, there is no reason Gene couldn't run
> buster with his 3.10 kernel.  At least, nothing in the release notes
> counter-indicates it.  Actual experience may dictate otherwise.

The other consideration in the case of the pi's is that up until part way 
thru the 4.19 series, there was no support for its video hdwe, forceing 
us to use the framebuffer, whose update rate is about 2 to 3 fps at 
best.  With that support enabled, full screen glxgears runs at 60 fps. 
Without that, the backplot for linuxcnc is 2 or 3 seconds behind the 
machine.

What has amazed me from the gitgo, is that the single most popular by a 
wide margin, arm based board, outnumbering all others combined by a wide 
margin, gets zero support from debian. I did a netinstall of buster, 
which almost worked, but because it was for arm64, had unusable for 
linuxcnc multi-millisecond latency, where the armhf can do latencies of 
15 microseconds, not great, but good enough.  And it took me a couple 
days after the install, to get enough networking stuff blown away and 
make it work on my host file based network. I spent weeks building 
preempt-rt kernels without building anything that would install. 
Questions asking for help were always blown off.

Then I found raspbian was also makeing buster, but for armhf.  And they 
could supply the src for a realtime-preempt kernel, no support, just the 
src. So I built it, and using what I learned, I figured out a way to 
install it, and made a 30meg tarball others could install. You can even 
get it from my web page. But the install is not by conventional methods, 
read and follow the readme.

So please tell me why, despite all the other distributions using your 
code base to make extremely stable versions of buster, has debian rather 
pointedly, indeed gone out of your way, to unsupport the rpi's?

Thank you.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Greg Wooledge]

On Tue, Jul 21, 2020 at 09:43:52AM +0300, Andrei POPESCU wrote:
> Most of the hardware support is in the kernel and as far as I can tell 
> buster should run with a 4.2 kernel (required by systemd).

The release notes for buster say that it requires a 3.2 kernel due
to GNU libc.

https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#glibc-and-linux

This is the reason why my VPS, which is running under a 2.6 kernel,
cannot be upgraded past stretch.

To the best of my knowledge, there is no reason Gene couldn't run
buster with his 3.10 kernel.  At least, nothing in the release notes
counter-indicates it.  Actual experience may dictate otherwise.

Re: Slic3r --gui won't run

[Gene Heskett]

On Tuesday 21 July 2020 02:43:52 Andrei POPESCU wrote:

> On Lu, 20 iul 20, 13:52:38, Gene Heskett wrote:
> > On Monday 20 July 2020 13:01:17 Andrei POPESCU wrote:
> > > On Lu, 20 iul 20, 12:24:35, Gene Heskett wrote:
> > > > FWIW, it installs and runs fine on a pi4 running buster 10.4.
> > > > But I don't have space close enough to the pi4 to put the
> > > > printer within reach of it. I've 3 other machines, all running
> > > > wheezy because thats the last RTAI kernel the linuxcnc folks
> > > > have built, but wheezy of course is done, so if I want to put
> > > > slic3r on one of those, I'll have to build it from scratch.
> > >
> > > And buster doesn't work with that kernel because... ?
> >
> > Generally a lack of support for newer hardware, its a
> > 3.20-something-RT, that claims PAE but does not work above 3 gigs of
> > installed memory, using swap by the gigabyte if you try. But its the
> > best we have for realtime on wintel style hardware.
>
> Most of the hardware support is in the kernel and as far as I can tell
> buster should run with a 4.2 kernel (required by systemd).

No clue aboutthe pi's. They don't have an RTAI kit as its not portable to 
the arms, but a 4.19 built right on the pi, for armhf works reasonably 
well.

> Kind regards,
> Andrei


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Lu, 20 iul 20, 13:46:28, Greg Wooledge wrote:
> On Mon, Jul 20, 2020 at 01:41:58PM -0400, Gene Heskett wrote:
> > On Monday 20 July 2020 11:41:04 Greg Wooledge wrote:
> > > Why in the name of all that is unholy did you install ONE HUNDRED
> > > SEVENTY-ONE backported packages?!?
> > >
> > > What were you THINKING?
> > Automatic install by synaptic as they became available over the years.
> 
> That's not how backports are intended to WORK.  Every one is a special
> snowflake.  You have to type "-t stretch-backports" (or analogous
> repository selection option) on your command in order to get them.
> 
> If synaptic is pulling in *-backports without you manually DOING something
> to select the backport over the standard version, then synaptic is
> broken.  Broken-er.  More broken-er.
 
In synaptic's defence, it probably doesn't have a choice if -backports 
(and -security?) is the only available repository. See Gene's original 
sources.list.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Lu, 20 iul 20, 13:52:38, Gene Heskett wrote:
> On Monday 20 July 2020 13:01:17 Andrei POPESCU wrote:
> 
> > On Lu, 20 iul 20, 12:24:35, Gene Heskett wrote:
> > > FWIW, it installs and runs fine on a pi4 running buster 10.4. But I
> > > don't have space close enough to the pi4 to put the printer within
> > > reach of it. I've 3 other machines, all running wheezy because thats
> > > the last RTAI kernel the linuxcnc folks have built, but wheezy of
> > > course is done, so if I want to put slic3r on one of those, I'll
> > > have to build it from scratch.
> >
> > And buster doesn't work with that kernel because... ?
> >
> Generally a lack of support for newer hardware, its a 3.20-something-RT, 
> that claims PAE but does not work above 3 gigs of installed memory, 
> using swap by the gigabyte if you try. But its the best we have for 
> realtime on wintel style hardware.

Most of the hardware support is in the kernel and as far as I can tell 
buster should run with a 4.2 kernel (required by systemd).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[rhkramer]

On Monday, July 20, 2020 02:34:11 PM Gene Heskett wrote:
> By setting synaptic to prefer oldstable, and removing the stuff slic3r
> complained about, then re-installing the oldstable stuff, with about 3
> trips around the mulberry bush, I got it to run!!!  All w/o a reboot.

Hurrah!

Re: Slic3r --gui won't run

[David Wright]

On Mon 20 Jul 2020 at 13:38:46 (-0400), Gene Heskett wrote:
> On Monday 20 July 2020 10:59:59 David Wright wrote:
> > On Mon 20 Jul 2020 at 04:53:13 (-0400), Gene Heskett wrote:
> > > On Monday 20 July 2020 00:49:48 David Wright wrote:
> > > > On Sun 19 Jul 2020 at 11:55:05 (-0400), Gene Heskett wrote:
> > > > > On Sunday 19 July 2020 09:56:10 Reco wrote:
> > > > > > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > > > > > Looks like my apt/sources.d is not uptodate?
> > > > > >
> > > > > > Looks like it is. Because [1] shows libwx-perl, and it's a
> > > > > > real package.
> > > > > >
> > > > > > [1] https://packages.debian.org/stretch/libwx-perl
> > > > >
> > > > > I found a page that shows what my sources.list should look like,
> > > > > made it so, but still can't install libwx-perl because there is
> > > > > not a perl-api-5.24.1 and a matching lib.  If this is a
> > > > > dependency of slic3r
> > > >
> > > >   ↑ lose that hyphen.
> > > >
> > > > Package: perl-base
> > > > Source: perl
> > > > Version: 5.24.1-3+deb9u6
> > > > Essential: yes
> > > >
> > > > You must have this.
> > > >
> > > > Provides: libfile-path-perl, libfile-temp-perl,
> > > > libio-socket-ip-perl, libscalar-list-utils-perl, libsocket-perl,
> > > > libxsloader-perl, perlapi-5.24.1
> > > >
> > > > On Sun 19 Jul 2020 at 14:30:54 (-0400), Gene Heskett wrote:
> > > > > On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> > > > > > On Du, 19 iul 20, 12:47:45, Gene Heskett wrote:
> > > > > > > Did that Andrei, updated apt-get, apt-get now gives a
> > > > > > > reason. Depends on 2 more packages, but adding them to the
> > > > > > > apt-get install line gets this:
> > > > > >
> > > > > > If APT can't find a solution adding more packages to the
> > > > > > install line won't help.
> > > > > >
> > > > > > > The following packages have unmet dependencies:
> > > > > > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (<
> > > > > > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > > > >Depends: libwxgtk-media3.0-dev (<
> > > > > > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > > > > E: Unable to correct problems, you have held broken
> > > > > > > packages.
> > > > > > >
> > > > > > > I'm about out of patience for the day. I have been screwing
> > > > > > > with this since about 5AM, and its now 12:45 local.  And I
> > > > > > > am damned tired of apt-gets inability to name the package
> > > > > > > thats breaking it.
> > > > > >
> > > > > > Considering how your sources.list looked like there's a
> > > > > > non-zero probability your system is in an inconsistent state
> > > > > > due to packages from stretch-backports that shouldn't be
> > > > > > there.
> > > > > >
> > > > > > The easiest way to find all installed packages from backports
> > > > > > is to run
> > > > > >
> > > > > > aptitude search '?narrow(?installed,?archive(backports))'
> > > > > >
> > > > > >
> > > > > > Yes, I know you wrote you don't trust 'aptitude', this is just
> > > > > > a search :)
> > > > >
> > > > > that spits out about 3 or 4 lines of text and blanks it, in
> > > > > about 100 millisecs, and will not redirect to |less. No line
> > > > > feeds IOW. I don't read at 20k wpm, so I've no clue what its
> > > > > trying to tell me.
> > > >
> > > > Nothing at that point; it's just building indices.
> > > >
> > > > BTW you could find that out by running   script   before the
> > > > command, and looking at ./typescript afterwards. In fact, you
> > > > might save a lot of time and effort when you're
> > > > individualistically configuring your systems by always running
> > > > script. Because ./typescript gets overwritten each time, I wrap
> > > > it:
> > > >
> > > > scrip is a function
> > > > scrip ()
> > > > {
> > > > script "typescript-$HOSTNAME-$(date +%Y-%m-%d-%H-%M-%S)-$1"
> > > > }
> > > >
> > > > $ dpkg -l | grep '\ > > >
> > > > will likely give you a list of your backports as you don't trust
> > > > aptitude.
> > >
> > > I added perl-base to the list; but get this:
> > >
> > > gene@coyote:~$ sudo apt-get install --allow-downgrades perl-base
> > > libwxgtk3.0-dev=3.0.2+dfsg-4 libwxgtk-media3.0-dev=3.0.2+dfsg-4
> > > [sudo] password for gene:
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > perl-base is already the newest version (5.24.1-3+deb9u7).
> >
> > Which fits my prediction that you'd have it; no need to try and
> > install it again.
> >
> > > Some packages could not be installed. This may mean that you have
> > > requested an impossible situation or if you are using the unstable
> > > distribution that some required packages have not yet been created
> > > or been moved out of Incoming.
> > > The following information may help to resolve the situation:
> > >
> > > The following packages have unmet dependencies:
> > >  libwxgtk-media3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but
> > > 

Re: Slic3r --gui won't run

[Gene Heskett]

On Monday 20 July 2020 13:48:12 Greg Wooledge wrote:

> On Mon, Jul 20, 2020 at 01:38:46PM -0400, Gene Heskett wrote:
> > These 4 pkgs have now been downgraded to oldstable. And now a launch
> > of slic3r --gui yells about a missing Wx.pm.  Not Wx3.pm, but Wx.pm.
> >
> > What perl pkg, available for stretch, contains that module?
>
> You have two ways to find out.
>
> One is to install the apt-file package, and use it locally.
>
> The other way is to search for the filename in the repositories, using
> the https://packages.debian.org/ web site (or the judd bot in IRC).

apt-file was helpfull, thank you. It gave me the final clue.

By setting synaptic to prefer oldstable, and removing the stuff slic3r 
complained about, then re-installing the oldstable stuff, with about 3 
trips around the mulberry bush, I got it to run!!!  All w/o a reboot.

Now to find if its any better than Cura.

Thanks a bunch all.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Gene Heskett]

On Monday 20 July 2020 13:01:17 Andrei POPESCU wrote:

> On Lu, 20 iul 20, 12:24:35, Gene Heskett wrote:
> > FWIW, it installs and runs fine on a pi4 running buster 10.4. But I
> > don't have space close enough to the pi4 to put the printer within
> > reach of it. I've 3 other machines, all running wheezy because thats
> > the last RTAI kernel the linuxcnc folks have built, but wheezy of
> > course is done, so if I want to put slic3r on one of those, I'll
> > have to build it from scratch.
>
> And buster doesn't work with that kernel because... ?
>
Generally a lack of support for newer hardware, its a 3.20-something-RT, 
that claims PAE but does not work above 3 gigs of installed memory, 
using swap by the gigabyte if you try. But its the best we have for 
realtime on wintel style hardware.

> Kind regards,
> Andrei


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Greg Wooledge]

On Mon, Jul 20, 2020 at 01:38:46PM -0400, Gene Heskett wrote:
> These 4 pkgs have now been downgraded to oldstable. And now a launch of 
> slic3r --gui yells about a missing Wx.pm.  Not Wx3.pm, but Wx.pm.
> 
> What perl pkg, available for stretch, contains that module?

You have two ways to find out.

One is to install the apt-file package, and use it locally.

The other way is to search for the filename in the repositories, using
the https://packages.debian.org/ web site (or the judd bot in IRC).

Re: Slic3r --gui won't run

[Greg Wooledge]

On Mon, Jul 20, 2020 at 01:41:58PM -0400, Gene Heskett wrote:
> On Monday 20 July 2020 11:41:04 Greg Wooledge wrote:
> > Why in the name of all that is unholy did you install ONE HUNDRED
> > SEVENTY-ONE backported packages?!?
> >
> > What were you THINKING?
> Automatic install by synaptic as they became available over the years.

That's not how backports are intended to WORK.  Every one is a special
snowflake.  You have to type "-t stretch-backports" (or analogous
repository selection option) on your command in order to get them.

If synaptic is pulling in *-backports without you manually DOING something
to select the backport over the standard version, then synaptic is
broken.  Broken-er.  More broken-er.

Re: Slic3r --gui won't run

[Gene Heskett]

On Monday 20 July 2020 11:41:04 Greg Wooledge wrote:

> On Mon, Jul 20, 2020 at 11:37:53AM -0400, Gene Heskett wrote:
> > On Monday 20 July 2020 07:24:41 Andrei POPESCU wrote:
> > > dpkg -l | grep '\ >
> > 171
>
> Why in the name of all that is unholy did you install ONE HUNDRED
> SEVENTY-ONE backported packages?!?
>
> What were you THINKING?
Automatic install by synaptic as they became available over the years.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Gene Heskett]

On Monday 20 July 2020 10:59:59 David Wright wrote:

> On Mon 20 Jul 2020 at 04:53:13 (-0400), Gene Heskett wrote:
> > On Monday 20 July 2020 00:49:48 David Wright wrote:
> > > On Sun 19 Jul 2020 at 11:55:05 (-0400), Gene Heskett wrote:
> > > > On Sunday 19 July 2020 09:56:10 Reco wrote:
> > > > > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > > > > Looks like my apt/sources.d is not uptodate?
> > > > >
> > > > > Looks like it is. Because [1] shows libwx-perl, and it's a
> > > > > real package.
> > > > >
> > > > > [1] https://packages.debian.org/stretch/libwx-perl
> > > >
> > > > I found a page that shows what my sources.list should look like,
> > > > made it so, but still can't install libwx-perl because there is
> > > > not a perl-api-5.24.1 and a matching lib.  If this is a
> > > > dependency of slic3r
> > >
> > >   ↑ lose that hyphen.
> > >
> > > Package: perl-base
> > > Source: perl
> > > Version: 5.24.1-3+deb9u6
> > > Essential: yes
> > >
> > > You must have this.
> > >
> > > Provides: libfile-path-perl, libfile-temp-perl,
> > > libio-socket-ip-perl, libscalar-list-utils-perl, libsocket-perl,
> > > libxsloader-perl, perlapi-5.24.1
> > >
> > > On Sun 19 Jul 2020 at 14:30:54 (-0400), Gene Heskett wrote:
> > > > On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> > > > > On Du, 19 iul 20, 12:47:45, Gene Heskett wrote:
> > > > > > Did that Andrei, updated apt-get, apt-get now gives a
> > > > > > reason. Depends on 2 more packages, but adding them to the
> > > > > > apt-get install line gets this:
> > > > >
> > > > > If APT can't find a solution adding more packages to the
> > > > > install line won't help.
> > > > >
> > > > > > The following packages have unmet dependencies:
> > > > > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (<
> > > > > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > > >Depends: libwxgtk-media3.0-dev (<
> > > > > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > > > E: Unable to correct problems, you have held broken
> > > > > > packages.
> > > > > >
> > > > > > I'm about out of patience for the day. I have been screwing
> > > > > > with this since about 5AM, and its now 12:45 local.  And I
> > > > > > am damned tired of apt-gets inability to name the package
> > > > > > thats breaking it.
> > > > >
> > > > > Considering how your sources.list looked like there's a
> > > > > non-zero probability your system is in an inconsistent state
> > > > > due to packages from stretch-backports that shouldn't be
> > > > > there.
> > > > >
> > > > > The easiest way to find all installed packages from backports
> > > > > is to run
> > > > >
> > > > > aptitude search '?narrow(?installed,?archive(backports))'
> > > > >
> > > > >
> > > > > Yes, I know you wrote you don't trust 'aptitude', this is just
> > > > > a search :)
> > > >
> > > > that spits out about 3 or 4 lines of text and blanks it, in
> > > > about 100 millisecs, and will not redirect to |less. No line
> > > > feeds IOW. I don't read at 20k wpm, so I've no clue what its
> > > > trying to tell me.
> > >
> > > Nothing at that point; it's just building indices.
> > >
> > > BTW you could find that out by running   script   before the
> > > command, and looking at ./typescript afterwards. In fact, you
> > > might save a lot of time and effort when you're
> > > individualistically configuring your systems by always running
> > > script. Because ./typescript gets overwritten each time, I wrap
> > > it:
> > >
> > > scrip is a function
> > > scrip ()
> > > {
> > > script "typescript-$HOSTNAME-$(date +%Y-%m-%d-%H-%M-%S)-$1"
> > > }
> > >
> > > $ dpkg -l | grep '\ > >
> > > will likely give you a list of your backports as you don't trust
> > > aptitude.
> >
> > I added perl-base to the list; but get this:
> >
> > gene@coyote:~$ sudo apt-get install --allow-downgrades perl-base
> > libwxgtk3.0-dev=3.0.2+dfsg-4 libwxgtk-media3.0-dev=3.0.2+dfsg-4
> > [sudo] password for gene:
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > perl-base is already the newest version (5.24.1-3+deb9u7).
>
> Which fits my prediction that you'd have it; no need to try and
> install it again.
>
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> >  libwxgtk-media3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> >  Depends: libwxgtk-media3.0-0v5 (=
> > 3.0.2+dfsg-4) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> >  libwxgtk3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> >

Re: Slic3r --gui won't run

[David Wright]

On Mon 20 Jul 2020 at 19:49:42 (+0300), Andrei POPESCU wrote:
> On Lu, 20 iul 20, 09:01:17, Greg Wooledge wrote:
> > On Sun, Jul 19, 2020 at 08:38:22PM +0300, Andrei POPESCU wrote:
> > > The easiest way to find all installed packages from backports is to run
> > > 
> > > aptitude search '?narrow(?installed,?archive(backports))'
> > 
> > Actually, the *easiest* way to find all packages from backports
> > is to run
> > 
> > dpkg -l | grep 'bpo[0-9]'
>  
> I apologize for the poor choice of words, especially since the use of 
> '?narrow' is not necessarily the obvious choice (it certainly wasn't for 
> me when I learned about it).
> 
> 'apt-show-versions' is another possible method, though it is yet another 
> package to install

It does confirm that every backports package I've installed, in
distributions since jessie, has got bpo in the version field.

> and I'm not sure how informative it is about packages 
> that are not part of a repository known to APT.

It gives lines like:

linux-image-4.19.0-5-amd64:amd64 4.19.37-5+deb10u2 installed: No available 
version in archive
xtoolwait:amd64 1.3-6.2 installed: No available version in archive

Cheers,
David.

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Lu, 20 iul 20, 12:24:35, Gene Heskett wrote:
> 
> FWIW, it installs and runs fine on a pi4 running buster 10.4. But I don't 
> have space close enough to the pi4 to put the printer within reach of 
> it. I've 3 other machines, all running wheezy because thats the last 
> RTAI kernel the linuxcnc folks have built, but wheezy of course is done, 
> so if I want to put slic3r on one of those, I'll have to build it from 
> scratch.

And buster doesn't work with that kernel because... ?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[David Wright]

On Mon 20 Jul 2020 at 12:24:35 (-0400), Gene Heskett wrote:
> On Monday 20 July 2020 10:11:40 rhkra...@gmail.com wrote:
> > On Monday, July 20, 2020 06:58:10 AM Andrei POPESCU wrote:
> > > "the latest candidate version" would be more accurate. If you think
> > > this wording is an improvement feel free to file a wishlist bugs
> > > against 'apt' (the package).
> >
> > Thanks -- I'll probably let that percolate in my head for a little
> > while before I file a bug -- it's probably good wording, but there is
> > no need to jump to a conclusion -- maybe we (collectively) will come
> > up with something better or recognize this as the best choice.
> > […]
> > (I would like to help Gene with his problem, but I think you're giving
> > the best advice on this atm.  (I was trying to tell him that the
> > problem package(s) that he is looking for is (are) those named in the
> > apt-get install command, but don't think I was very clear.)
> 
> What is upsetting me is that there is not, from the wording coming back 
> out of apt, any way to identify the package that needs (apparently) to 
> be downgraded, that starts this whole mess.  Since this all seems to 
> start with the slic3r's --gui option, IMNSHO it should have been 
> something that apt should have solved for when I installed slic3r. But 
> apparently the author didn't list the Depends pulled in if the --gui 
> option was enabled.

If you only need libwx-perl to run the --gui option, then it wouldn't
be appropriate to list it as a Depends, would it. At most, it would be
a Recommends; perhaps just a Suggests.

The packages that need downgrading are listed in your error message.
Whether you *can* downgrade just those packages them with 171 backports
on your system is another matter. (There might be second order
dependencies, and then third order, etc.)

> Change of subject, what do we have that can process and display a .step 
> file?

Please. Etiquette.

Cheers,
David.

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Lu, 20 iul 20, 09:01:17, Greg Wooledge wrote:
> On Sun, Jul 19, 2020 at 08:38:22PM +0300, Andrei POPESCU wrote:
> > The easiest way to find all installed packages from backports is to run
> > 
> > aptitude search '?narrow(?installed,?archive(backports))'
> 
> Actually, the *easiest* way to find all packages from backports
> is to run
> 
> dpkg -l | grep 'bpo[0-9]'
 
I apologize for the poor choice of words, especially since the use of 
'?narrow' is not necessarily the obvious choice (it certainly wasn't for 
me when I learned about it).

'apt-show-versions' is another possible method, though it is yet another 
package to install and I'm not sure how informative it is about packages 
that are not part of a repository known to APT.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Gene Heskett]

On Monday 20 July 2020 10:11:40 rhkra...@gmail.com wrote:

> On Monday, July 20, 2020 06:58:10 AM Andrei POPESCU wrote:
> > "the latest candidate version" would be more accurate. If you think
> > this wording is an improvement feel free to file a wishlist bugs
> > against 'apt' (the package).
>
> Thanks -- I'll probably let that percolate in my head for a little
> while before I file a bug -- it's probably good wording, but there is
> no need to jump to a conclusion -- maybe we (collectively) will come
> up with something better or recognize this as the best choice.
>
> > > I'm guessing that someone would describe the situation of the old
> > > openssh- client as being pinned, but does that word ever appear
> > > somewhere to describe the situation?  (I mean like, can you run
> > > apt-get (or something else) and get a list of pinned packages with
> > > the word "pinned" next to them?
> >
> > You are looking for 'apt policy' (with no package).
>
> Thanks!  (But, nothing shows up there as pinned -- I probably have a
> lot more to learn here, but, as my current problem is solved, may not
> dig into it.)
>
> (I would like to help Gene with his problem, but I think you're giving
> the best advice on this atm.  (I was trying to tell him that the
> problem package(s) that he is looking for is (are) those named in the
> apt-get install command, but don't think I was very clear.)

What is upsetting me is that there is not, from the wording coming back 
out of apt, any way to identify the package that needs (apparently) to 
be downgraded, that starts this whole mess.  Since this all seems to 
start with the slic3r's --gui option, IMNSHO it should have been 
something that apt should have solved for when I installed slic3r. But 
apparently the author didn't list the Depends pulled in if the --gui 
option was enabled.

FWIW, it installs and runs fine on a pi4 running buster 10.4. But I don't 
have space close enough to the pi4 to put the printer within reach of 
it. I've 3 other machines, all running wheezy because thats the last 
RTAI kernel the linuxcnc folks have built, but wheezy of course is done, 
so if I want to put slic3r on one of those, I'll have to build it from 
scratch.

Change of subject, what do we have that can process and display a .step 
file?

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Lu, 20 iul 20, 11:41:04, Greg Wooledge wrote:
> On Mon, Jul 20, 2020 at 11:37:53AM -0400, Gene Heskett wrote:
> > On Monday 20 July 2020 07:24:41 Andrei POPESCU wrote:
> > 
> > > dpkg -l | grep '\ > 171
> 
> Why in the name of all that is unholy did you install ONE HUNDRED
> SEVENTY-ONE backported packages?!?
> 
> What were you THINKING?
 
This might have happened accidentally when installing on / upgrading a 
system with nothing but -backports in sources.list.

Gene, in that list there's probably (hopefully!) only a few packages 
that you really need at a newer version. If you can identify those you 
could try to downgrade the rest.

Do mind downgrading a package is not officially supported. It may or may 
not work, depending on the package.

Removing the newer version and installing the older version instead is 
the safe approach.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Greg Wooledge]

On Mon, Jul 20, 2020 at 11:37:53AM -0400, Gene Heskett wrote:
> On Monday 20 July 2020 07:24:41 Andrei POPESCU wrote:
> 
> > dpkg -l | grep '\ 171

Why in the name of all that is unholy did you install ONE HUNDRED
SEVENTY-ONE backported packages?!?

What were you THINKING?

Re: Slic3r --gui won't run

[Gene Heskett]

On Monday 20 July 2020 07:24:41 Andrei POPESCU wrote:

> dpkg -l | grep '\http://geneslinuxbox.net:6309/gene>

Re: Slic3r --gui won't run

[Greg Wooledge]

On Mon, Jul 20, 2020 at 09:59:59AM -0500, David Wright wrote:
> AFAICT the problem packages are listed above:
> 
> wx3.0-headers 3.0.4+dfsg-4~bpo9+1
> libwxgtk-media3.0-0v5 3.0.4+dfsg-4~bpo9+1
> libwxgtk3.0-0v5   3.0.4+dfsg-4~bpo9+1
> libwxbase3.0-dev  3.0.4+dfsg-4~bpo9+1
> 
> It wants to install the mainstream versions of these packages.

> I can only assume that's because there are higher versions in
> backports, but you're on stretch (of some sort) so I can't check here.

Here's what it should look like on an untainted stretch system:

$ apt-cache policy wx3.0-headers libwxgtk-media3.0-0v5 libwxgtk3.0-0v5 
libwxbase3.0-dev
wx3.0-headers:
  Installed: (none)
  Candidate: 3.0.2+dfsg-4
  Version table:
 3.0.2+dfsg-4 500
500 https://deb.debian.org/debian stretch/main amd64 Packages
libwxgtk-media3.0-0v5:
  Installed: (none)
  Candidate: 3.0.2+dfsg-4
  Version table:
 3.0.2+dfsg-4 500
500 https://deb.debian.org/debian stretch/main amd64 Packages
libwxgtk3.0-0v5:
  Installed: (none)
  Candidate: 3.0.2+dfsg-4
  Version table:
 3.0.2+dfsg-4 500
500 https://deb.debian.org/debian stretch/main amd64 Packages
libwxbase3.0-dev:
  Installed: (none)
  Candidate: 3.0.2+dfsg-4
  Version table:
 3.0.2+dfsg-4 500
500 https://deb.debian.org/debian stretch/main amd64 Packages

Gene has made his life harder by doing something outside of the norm,
again, and has not taken responsibility for his own changes, again.

As you said, backported (or third-party) packages that are in the way
should be removed.

Re: Slic3r --gui won't run

[David Wright]

On Mon 20 Jul 2020 at 04:53:13 (-0400), Gene Heskett wrote:
> On Monday 20 July 2020 00:49:48 David Wright wrote:
> > On Sun 19 Jul 2020 at 11:55:05 (-0400), Gene Heskett wrote:
> > > On Sunday 19 July 2020 09:56:10 Reco wrote:
> > > > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > > > Looks like my apt/sources.d is not uptodate?
> > > >
> > > > Looks like it is. Because [1] shows libwx-perl, and it's a real
> > > > package.
> > > >
> > > > [1] https://packages.debian.org/stretch/libwx-perl
> > >
> > > I found a page that shows what my sources.list should look like,
> > > made it so, but still can't install libwx-perl because there is not
> > > a perl-api-5.24.1 and a matching lib.  If this is a dependency of
> > > slic3r
> >
> >   ↑ lose that hyphen.
> >
> > Package: perl-base
> > Source: perl
> > Version: 5.24.1-3+deb9u6
> > Essential: yes
> >
> > You must have this.
> >
> > Provides: libfile-path-perl, libfile-temp-perl, libio-socket-ip-perl,
> > libscalar-list-utils-perl, libsocket-perl, libxsloader-perl,
> > perlapi-5.24.1
> >
> > On Sun 19 Jul 2020 at 14:30:54 (-0400), Gene Heskett wrote:
> > > On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> > > > On Du, 19 iul 20, 12:47:45, Gene Heskett wrote:
> > > > > Did that Andrei, updated apt-get, apt-get now gives a reason.
> > > > > Depends on 2 more packages, but adding them to the apt-get
> > > > > install line gets this:
> > > >
> > > > If APT can't find a solution adding more packages to the install
> > > > line won't help.
> > > >
> > > > > The following packages have unmet dependencies:
> > > > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~)
> > > > > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > >Depends: libwxgtk-media3.0-dev (<
> > > > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > > E: Unable to correct problems, you have held broken packages.
> > > > >
> > > > > I'm about out of patience for the day. I have been screwing with
> > > > > this since about 5AM, and its now 12:45 local.  And I am damned
> > > > > tired of apt-gets inability to name the package thats breaking
> > > > > it.
> > > >
> > > > Considering how your sources.list looked like there's a non-zero
> > > > probability your system is in an inconsistent state due to
> > > > packages from stretch-backports that shouldn't be there.
> > > >
> > > > The easiest way to find all installed packages from backports is
> > > > to run
> > > >
> > > > aptitude search '?narrow(?installed,?archive(backports))'
> > > >
> > > >
> > > > Yes, I know you wrote you don't trust 'aptitude', this is just a
> > > > search :)
> > >
> > > that spits out about 3 or 4 lines of text and blanks it, in about
> > > 100 millisecs, and will not redirect to |less. No line feeds IOW. I
> > > don't read at 20k wpm, so I've no clue what its trying to tell me.
> >
> > Nothing at that point; it's just building indices.
> >
> > BTW you could find that out by running   script   before the command,
> > and looking at ./typescript afterwards. In fact, you might save a lot
> > of time and effort when you're individualistically configuring your
> > systems by always running script. Because ./typescript gets
> > overwritten each time, I wrap it:
> >
> > scrip is a function
> > scrip ()
> > {
> > script "typescript-$HOSTNAME-$(date +%Y-%m-%d-%H-%M-%S)-$1"
> > }
> >
> > $ dpkg -l | grep '\ >
> > will likely give you a list of your backports as you don't trust
> > aptitude.
> >
> I added perl-base to the list; but get this:
> 
> gene@coyote:~$ sudo apt-get install --allow-downgrades perl-base 
> libwxgtk3.0-dev=3.0.2+dfsg-4 libwxgtk-media3.0-dev=3.0.2+dfsg-4
> [sudo] password for gene:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> perl-base is already the newest version (5.24.1-3+deb9u7).

Which fits my prediction that you'd have it; no need to try and
install it again.

> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libwxgtk-media3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>  Depends: libwxgtk-media3.0-0v5 (= 3.0.2+dfsg-4) 
> but 3.0.4+dfsg-4~bpo9+1 is to be installed
>  libwxgtk3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxgtk3.0-0v5 (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> Those packages that are named aas to be 

Re: Slic3r --gui won't run

[rhkramer]

On Monday, July 20, 2020 06:58:10 AM Andrei POPESCU wrote:
> "the latest candidate version" would be more accurate. If you think this
> wording is an improvement feel free to file a wishlist bugs against
> 'apt' (the package).
> 

Thanks -- I'll probably let that percolate in my head for a little while 
before I file a bug -- it's probably good wording, but there is no need to jump 
to a conclusion -- maybe we (collectively) will come up with something better 
or recognize this as the best choice.

> > I'm guessing that someone would describe the situation of the old
> > openssh- client as being pinned, but does that word ever appear
> > somewhere to describe the situation?  (I mean like, can you run apt-get
> > (or something else) and get a list of pinned packages with the word
> > "pinned" next to them?
> 
> You are looking for 'apt policy' (with no package).

Thanks!  (But, nothing shows up there as pinned -- I probably have a lot more 
to learn here, but, as my current problem is solved, may not dig into it.)

(I would like to help Gene with his problem, but I think you're giving the 
best advice on this atm.  (I was trying to tell him that the problem 
package(s) that he is looking for is (are) those named in the apt-get install 
command, but don't think I was very clear.)

Re: Slic3r --gui won't run

[Greg Wooledge]

On Sun, Jul 19, 2020 at 08:38:22PM +0300, Andrei POPESCU wrote:
> The easiest way to find all installed packages from backports is to run
> 
> aptitude search '?narrow(?installed,?archive(backports))'

Actually, the *easiest* way to find all packages from backports
is to run

dpkg -l | grep 'bpo[0-9]'

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 23:49:48, David Wright wrote:
> On Sun 19 Jul 2020 at 11:55:05 (-0400), Gene Heskett wrote:
> > On Sunday 19 July 2020 09:56:10 Reco wrote:
> > > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > > Looks like my apt/sources.d is not uptodate?
> > >
> > > Looks like it is. Because [1] shows libwx-perl, and it's a real
> > > package.
> > >
> > > [1] https://packages.debian.org/stretch/libwx-perl
> > 
> > I found a page that shows what my sources.list should look like, made it 
> > so, but still can't install libwx-perl because there is not a 
> > perl-api-5.24.1 and a matching lib.  If this is a dependency of slic3r 
> 
>   ↑ lose that hyphen.
> 
> Package: perl-base
> Source: perl
> Version: 5.24.1-3+deb9u6
> Essential: yes
> 
> You must have this.
> 
> Provides: libfile-path-perl, libfile-temp-perl, libio-socket-ip-perl, 
> libscalar-list-utils-perl, libsocket-perl, libxsloader-perl, perlapi-5.24.1
> 
> On Sun 19 Jul 2020 at 14:30:54 (-0400), Gene Heskett wrote:
> > On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> > >
> > > The easiest way to find all installed packages from backports is to
> > > run
> > >
> > > aptitude search '?narrow(?installed,?archive(backports))'
> > 
> > that spits out about 3 or 4 lines of text and blanks it, in about 100 
> > millisecs, and will not redirect to |less. No line feeds IOW. I don't 
> > read at 20k wpm, so I've no clue what its trying to tell me.
> 
> Nothing at that point; it's just building indices.

Right, it might not output anything, if Gene in the meantime removed 
-backports from sources.list.
 
> $ dpkg -l | grep '\ 
> will likely give you a list of your backports as you don't trust aptitude.

Yep.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 14:30:54, Gene Heskett wrote:
> On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> >
> > The easiest way to find all installed packages from backports is to
> > run
> >
> > aptitude search '?narrow(?installed,?archive(backports))'
> 
> that spits out about 3 or 4 lines of text and blanks it, in about 100 
> millisecs, and will not redirect to |less. No line feeds IOW. I don't 
> read at 20k wpm, so I've no clue what its trying to tell me.

Must be something about your configuration, it works fine here, also the 
redirect to 'less'.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 14:45:27, Gene Heskett wrote:
> 
> That would be very nice, but the docs for pinning stuff is damned near 
> a secret,

The documentation is in 'man apt_preferences', 'apropos' (a.k.a. man -k) 
finds it.

> and involves (apparently) more ways than the /e/a/preferences.list.  
> I've managed to do it but can't recall how I did it 4 years later. And 
> I've done it on a rpi4 to lock in the preempt-rt kernel I built and 
> installed, but rpi4.coyote.den/etc/apt/preferences.d is empty.  So I'm 
> zip help, sorry.

Besides the /etc/apt/preferences file and files under 
/etc/apt/preferences.d the following mechanism (that I'm aware of) 
exist:

 - Repositories with different priorities (experimental, -backports)
   
   These are equivalent to pinning the entire source to the same 
   priority

 - The Default-Release setting and the '-t/--target-release' switch
   
   This sets the priority for the corresponding release to 990.


APT (the package manager) will also respect dpkg 'hold's, which are the 
simple version of "pin this package to whatever version is installed 
right now". Synaptic probably also knows about these.

Aptitude in addition has 'hold's, mostly used to tweak the (interactive) 
dependency resolver. As far as I know these are only used by aptitude.


Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 14:27:24, rhkra...@gmail.com wrote:
> 
> Aside: The funny thing to me (which someone might comment on) -- I absolutely 
> know that the old version of openssh-client is installed (by running ssh -V), 
> but I ran apt-get again (after installing openssh-server) and it tells me 
> that 
> openssh-client is the latest version, which is pretty much a clear lie.

"the latest candidate version" would be more accurate. If you think this 
wording is an improvement feel free to file a wishlist bugs against 
'apt' (the package).
 
> But, ok.  Somewhere, during my reading / googling before solving the problem, 
> I came across the word "pin" (or pinned) and I was looking for an apt-get or 
> other command to find out which packages might be pinned (to the best of my 
> knowledge, I've never intentionally pinned anything on my Wheezy installation 
> (which, by the way, is what I was dealing with).
> 
> I'm guessing that someone would describe the situation of the old openssh-
> client as being pinned, but does that word ever appear somewhere to describe 
> the situation?  (I mean like, can you run apt-get (or something else) and get 
> a list of pinned packages with the word "pinned" next to them? 

You are looking for 'apt policy' (with no package).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 14:06:31, Gene Heskett wrote:
> >
> Stretch, is apt-get country.

The 'apt' command was introduced in APT version 1.0 (jessie).

> But:
> 
> gene@coyote:~/Downloads/stl.stf/files$ apt policy libwxgtk3.0-dev
> libwxgtk3.0-dev:
>   Installed: 3.0.4+dfsg-4~bpo9+1
>   Candidate: 3.0.4+dfsg-4~bpo9+1
>   Version table:
>  *** 3.0.4+dfsg-4~bpo9+1 100
> 100 /var/lib/dpkg/status
>  3.0.2+dfsg-4 500
> 500 https://deb.debian.org/debian stretch/main amd64 Packages
> gene@coyote:~/Downloads/stl.stf/files$ apt policy libwxgtk-media3.0-dev
> libwxgtk-media3.0-dev:
>   Installed: 3.0.4+dfsg-4~bpo9+1
>   Candidate: 3.0.4+dfsg-4~bpo9+1
>   Version table:
>  *** 3.0.4+dfsg-4~bpo9+1 100
> 100 /var/lib/dpkg/status
>  3.0.2+dfsg-4 500
> 500 https://deb.debian.org/debian stretch/main amd64 Packages
> 
> Running low on hair here. Nothing makes sense.

This shows you have the stretch-backports versions already installed. 

Try removing them and recheck the output. "Candidate:" should then be 
the stretch version

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Gene Heskett]

On Monday 20 July 2020 00:49:48 David Wright wrote:

> On Sun 19 Jul 2020 at 11:55:05 (-0400), Gene Heskett wrote:
> > On Sunday 19 July 2020 09:56:10 Reco wrote:
> > > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > > Looks like my apt/sources.d is not uptodate?
> > >
> > > Looks like it is. Because [1] shows libwx-perl, and it's a real
> > > package.
> > >
> > > [1] https://packages.debian.org/stretch/libwx-perl
> >
> > I found a page that shows what my sources.list should look like,
> > made it so, but still can't install libwx-perl because there is not
> > a perl-api-5.24.1 and a matching lib.  If this is a dependency of
> > slic3r
>
>   ↑ lose that hyphen.
>
> Package: perl-base
> Source: perl
> Version: 5.24.1-3+deb9u6
> Essential: yes
>
> You must have this.
>
> Provides: libfile-path-perl, libfile-temp-perl, libio-socket-ip-perl,
> libscalar-list-utils-perl, libsocket-perl, libxsloader-perl,
> perlapi-5.24.1
>
> On Sun 19 Jul 2020 at 14:30:54 (-0400), Gene Heskett wrote:
> > On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> > > On Du, 19 iul 20, 12:47:45, Gene Heskett wrote:
> > > > Did that Andrei, updated apt-get, apt-get now gives a reason.
> > > > Depends on 2 more packages, but adding them to the apt-get
> > > > install line gets this:
> > >
> > > If APT can't find a solution adding more packages to the install
> > > line won't help.
> > >
> > > > The following packages have unmet dependencies:
> > > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~)
> > > > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > >Depends: libwxgtk-media3.0-dev (<
> > > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > E: Unable to correct problems, you have held broken packages.
> > > >
> > > > I'm about out of patience for the day. I have been screwing with
> > > > this since about 5AM, and its now 12:45 local.  And I am damned
> > > > tired of apt-gets inability to name the package thats breaking
> > > > it.
> > >
> > > Considering how your sources.list looked like there's a non-zero
> > > probability your system is in an inconsistent state due to
> > > packages from stretch-backports that shouldn't be there.
> > >
> > > The easiest way to find all installed packages from backports is
> > > to run
> > >
> > > aptitude search '?narrow(?installed,?archive(backports))'
> > >
> > >
> > > Yes, I know you wrote you don't trust 'aptitude', this is just a
> > > search :)
> >
> > that spits out about 3 or 4 lines of text and blanks it, in about
> > 100 millisecs, and will not redirect to |less. No line feeds IOW. I
> > don't read at 20k wpm, so I've no clue what its trying to tell me.
>
> Nothing at that point; it's just building indices.
>
> BTW you could find that out by running   script   before the command,
> and looking at ./typescript afterwards. In fact, you might save a lot
> of time and effort when you're individualistically configuring your
> systems by always running script. Because ./typescript gets
> overwritten each time, I wrap it:
>
> scrip is a function
> scrip ()
> {
> script "typescript-$HOSTNAME-$(date +%Y-%m-%d-%H-%M-%S)-$1"
> }
>
> $ dpkg -l | grep '\
> will likely give you a list of your backports as you don't trust
> aptitude.
>
> Cheers,
> David.
I added perl-base to the list; but get this:

gene@coyote:~$ sudo apt-get install --allow-downgrades perl-base 
libwxgtk3.0-dev=3.0.2+dfsg-4 libwxgtk-media3.0-dev=3.0.2+dfsg-4
[sudo] password for gene:
Reading package lists... Done
Building dependency tree
Reading state information... Done
perl-base is already the newest version (5.24.1-3+deb9u7).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libwxgtk-media3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
 Depends: libwxgtk-media3.0-0v5 (= 3.0.2+dfsg-4) 
but 3.0.4+dfsg-4~bpo9+1 is to be installed
 libwxgtk3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
   Depends: libwxgtk3.0-0v5 (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
   Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
E: Unable to correct problems, you have held broken packages.

Those packages that are named aas to be instalkled, are in fact 
installed.

Now, if I have intentionally "held" broken packages, should those 
packages not be mentioned in preferences.d?

gene@coyote:~$ ls -l /etc/apt/preferences.d/
total 0

I don't have all of the apt stuff installed, but I'm going to add aptsh 
and apt-show-versions. Somewhere, and I have asked how to get apt to 
actually name 

Re: Slic3r --gui won't run

[David Wright]

On Sun 19 Jul 2020 at 11:55:05 (-0400), Gene Heskett wrote:
> On Sunday 19 July 2020 09:56:10 Reco wrote:
> > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > Looks like my apt/sources.d is not uptodate?
> >
> > Looks like it is. Because [1] shows libwx-perl, and it's a real
> > package.
> >
> > [1] https://packages.debian.org/stretch/libwx-perl
> 
> I found a page that shows what my sources.list should look like, made it 
> so, but still can't install libwx-perl because there is not a 
> perl-api-5.24.1 and a matching lib.  If this is a dependency of slic3r 

  ↑ lose that hyphen.

Package: perl-base
Source: perl
Version: 5.24.1-3+deb9u6
Essential: yes

You must have this.

Provides: libfile-path-perl, libfile-temp-perl, libio-socket-ip-perl, 
libscalar-list-utils-perl, libsocket-perl, libxsloader-perl, perlapi-5.24.1

On Sun 19 Jul 2020 at 14:30:54 (-0400), Gene Heskett wrote:
> On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> > On Du, 19 iul 20, 12:47:45, Gene Heskett wrote:
> > > Did that Andrei, updated apt-get, apt-get now gives a reason.
> > > Depends on 2 more packages, but adding them to the apt-get install
> > > line gets this:
> >
> > If APT can't find a solution adding more packages to the install line
> > won't help.
> >
> > > The following packages have unmet dependencies:
> > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > >Depends: libwxgtk-media3.0-dev (< 3.0.3~)
> > > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > >
> > > I'm about out of patience for the day. I have been screwing with
> > > this since about 5AM, and its now 12:45 local.  And I am damned
> > > tired of apt-gets inability to name the package thats breaking it.
> >
> > Considering how your sources.list looked like there's a non-zero
> > probability your system is in an inconsistent state due to packages
> > from stretch-backports that shouldn't be there.
> >
> > The easiest way to find all installed packages from backports is to
> > run
> >
> > aptitude search '?narrow(?installed,?archive(backports))'
> >
> >
> > Yes, I know you wrote you don't trust 'aptitude', this is just a
> > search :)
> 
> that spits out about 3 or 4 lines of text and blanks it, in about 100 
> millisecs, and will not redirect to |less. No line feeds IOW. I don't 
> read at 20k wpm, so I've no clue what its trying to tell me.

Nothing at that point; it's just building indices.

BTW you could find that out by running   script   before the command,
and looking at ./typescript afterwards. In fact, you might save a lot
of time and effort when you're individualistically configuring your
systems by always running script. Because ./typescript gets
overwritten each time, I wrap it:

scrip is a function
scrip () 
{ 
script "typescript-$HOSTNAME-$(date +%Y-%m-%d-%H-%M-%S)-$1"
}

$ dpkg -l | grep '\

Re: Slic3r --gui won't run

[Reco]

On Sun, Jul 19, 2020 at 02:49:24PM -0400, Gene Heskett wrote:
> The following packages have unmet dependencies:
>  libwxgtk-media3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>  Depends: libwxgtk-media3.0-0v5 (= 3.0.2+dfsg-4) 
> but 3.0.4+dfsg-4~bpo9+1 is to be installed
>  libwxgtk3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxgtk3.0-0v5 (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
> E: Unable to correct problems, you have held broken packages.

In Depends it shows you packages that you should add to the list of
"apt-get install" with appropriate versions.

apt-get install --allow-downgrades libwxgtk3.0-dev=3.0.2+dfsg-4 \
libwxgtk-media3.0-dev=3.0.2+dfsg-4 \
wx3.0-header=3.0.2+dfsg-4 \
libwxgtk-media3.0-0v5=3.0.2+dfsg-4 \
wx3.0-headers=3.0.2+dfsg-4 \
libwxgtk3.0-0v5=3.0.2+dfsg-4 \
libwxbase3.0-dev= 3.0.2+dfsg-4

Repeat a process several times, adding packages each time.

And I'm not trying to offend you, or something, but the this whole mess
could be avoided by not installing this and that and a kitchen sink from
the backports.

Reco

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 14:28:45 Reco wrote:

> On Sun, Jul 19, 2020 at 02:20:13PM -0400, Gene Heskett wrote:
> > On Sunday 19 July 2020 13:18:16 Reco wrote:
> > > On Sun, Jul 19, 2020 at 01:05:55PM -0400, Gene Heskett wrote:
> > > > Now apt-get is bitching because it thinks I'm asking for version
> > > > 3.0.3 but only 3.0.4 stuff is available:
> > > >
> > > > The following packages have unmet dependencies:
> > > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~)
> > > > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > >Depends: libwxgtk-media3.0-dev (<
> > > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > > E: Unable to correct problems, you have held broken packages.
> > > >
> > > > WHAT IS THE NAME OF THE BROKEN
> > > > PACKAGE
> > >
> > > No need to shout. It says here loud and clear that you should
> > > downgrade libwxgtk3.0-dev, libwxgtk-media3.0-dev and their
> > > dependencies.
> > >
> > > Reco
> >
> > apt policy says the newer ones are installed already, so I
> > tried --allow-downgrades, but that is ignored and I still don't have
> > a clue what package is breaking it.
>
> Something like this should do it.
>
> apt-get install --allow-downgrades libwxgtk3.0-dev=3.0.2+dfsg-4 \
>   libwxgtk-media3.0-dev=3.0.2+dfsg-4
>
> Add other libwxgtk* packages to the list as needed.
>
> Reco
gene@coyote:~$ sudo apt-get install --allow-downgrades 
libwxgtk3.0-dev=3.0.2+dfsg-4 libwxgtk-media3.0-dev=3.0.2+dfsg-4
[sudo] password for gene:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libwxgtk-media3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
 Depends: libwxgtk-media3.0-0v5 (= 3.0.2+dfsg-4) 
but 3.0.4+dfsg-4~bpo9+1 is to be installed
 libwxgtk3.0-dev : Depends: wx3.0-headers (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
   Depends: libwxgtk3.0-0v5 (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
   Depends: libwxbase3.0-dev (= 3.0.2+dfsg-4) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
E: Unable to correct problems, you have held broken packages.


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 14:27:24 rhkra...@gmail.com wrote:

> On Sunday, July 19, 2020 01:05:55 PM Gene Heskett wrote:
> > Now apt-get is bitching because it thinks I'm asking for version
> > 3.0.3 but only 3.0.4 stuff is available:
> >
> > The following packages have unmet dependencies:
> >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> >Depends: libwxgtk-media3.0-dev (< 3.0.3~)
> > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> >
> > WHAT IS THE NAME OF THE BROKEN PACKAGE
>
> I just solved a very similar problem (for ssh) with the aid of google
> and such (I'm sort of proud of myself ;-)
>
> Anyway, what I had to do, for the package that had the message about
> the newer package to be installed, I had to do something like this
> (may not have the syntax exactly right, and the first time I ran it, I
> ran it with -s just to see what was going to happen):
>
> apt-get -s install libwxgtk3.0-dev=3.0.3
>
> In my case, the message specified an old version in a form like:
> 3.0.4+dfsg-4~bpo9+1, so I'm not sure the 3.0.3 is specific enough.  Or
> maybe the equal sign can be replaced with a < or a <= (=<)?
>
> After I successfully installed the old version of the file that was
> holding me back (openssh-client), then I was able to install my
> desired package (openssh- server).
>
> Aside: The funny thing to me (which someone might comment on) -- I
> absolutely know that the old version of openssh-client is installed
> (by running ssh -V), but I ran apt-get again (after installing
> openssh-server) and it tells me that openssh-client is the latest
> version, which is pretty much a clear lie.
>
> But, ok.  Somewhere, during my reading / googling before solving the
> problem, I came across the word "pin" (or pinned) and I was looking
> for an apt-get or other command to find out which packages might be
> pinned (to the best of my knowledge, I've never intentionally pinned
> anything on my Wheezy installation (which, by the way, is what I was
> dealing with).
>
> I'm guessing that someone would describe the situation of the old
> openssh- client as being pinned, but does that word ever appear
> somewhere to describe the situation?  (I mean like, can you run
> apt-get (or something else) and get a list of pinned packages with the
> word "pinned" next to them?

That would be very nice, but the docs for pinning stuff is damned near a 
secret, and involves (apparently) more ways than 
the /e/a/preferences.list. I've managed to do it but can't recall how I 
did it 4 years later. And I've done it on a rpi4 to lock in the 
preempt-rt kernel I built and installed, but 
rpi4.coyote.den/etc/apt/preferences.d is empty.  So I'm zip help, sorry.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[rhkramer]

On Sunday, July 19, 2020 02:27:24 PM rhkra...@gmail.com wrote:
> On Sunday, July 19, 2020 01:05:55 PM Gene Heskett wrote:
> > Now apt-get is bitching because it thinks I'm asking for version 3.0.3
> > but only 3.0.4 stuff is available:
> > 
> > The following packages have unmet dependencies:
> >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > 
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > 
> >Depends: libwxgtk-media3.0-dev (< 3.0.3~) but
> > 
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> > 
> > WHAT IS THE NAME OF THE BROKEN PACKAGE

BTW: Just one more comment on misleading language, even though (in my case) 
apt-get talked about the package to be installed, that package was the one 
already installed (not "to be installed").

Oh, and maybe I should say that the names of the broken packages are:

libwxgtk3.0-dev 
libwxgtk-media3.0-dev

Nothing new below this line.


> Anyway, what I had to do, for the package that had the message about the
> newer package to be installed, I had to do something like this (may not
> have the syntax exactly right, and the first time I ran it, I ran it with
> -s just to see what was going to happen):
> 
> apt-get -s install libwxgtk3.0-dev=3.0.3
> 
> In my case, the message specified an old version in a form like:
> 3.0.4+dfsg-4~bpo9+1, so I'm not sure the 3.0.3 is specific enough.  Or
> maybe the equal sign can be replaced with a < or a <= (=<)?
> 
> After I successfully installed the old version of the file that was holding
> me back (openssh-client), then I was able to install my desired package
> (openssh- server).
> 
> Aside: The funny thing to me (which someone might comment on) -- I
> absolutely know that the old version of openssh-client is installed (by
> running ssh -V), but I ran apt-get again (after installing openssh-server)
> and it tells me that openssh-client is the latest version, which is pretty
> much a clear lie.
> 
> But, ok.  Somewhere, during my reading / googling before solving the
> problem, I came across the word "pin" (or pinned) and I was looking for an
> apt-get or other command to find out which packages might be pinned (to
> the best of my knowledge, I've never intentionally pinned anything on my
> Wheezy installation (which, by the way, is what I was dealing with).
> 
> I'm guessing that someone would describe the situation of the old openssh-
> client as being pinned, but does that word ever appear somewhere to
> describe the situation?  (I mean like, can you run apt-get (or something
> else) and get a list of pinned packages with the word "pinned" next to
> them?

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:

> On Du, 19 iul 20, 12:47:45, Gene Heskett wrote:
> > Did that Andrei, updated apt-get, apt-get now gives a reason.
> > Depends on 2 more packages, but adding them to the apt-get install
> > line gets this:
>
> If APT can't find a solution adding more packages to the install line
> won't help.
>
> > The following packages have unmet dependencies:
> >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> >Depends: libwxgtk-media3.0-dev (< 3.0.3~)
> > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> >
> > I'm about out of patience for the day. I have been screwing with
> > this since about 5AM, and its now 12:45 local.  And I am damned
> > tired of apt-gets inability to name the package thats breaking it.
>
> Considering how your sources.list looked like there's a non-zero
> probability your system is in an inconsistent state due to packages
> from stretch-backports that shouldn't be there.
>
> The easiest way to find all installed packages from backports is to
> run
>
> aptitude search '?narrow(?installed,?archive(backports))'
>
>
> Yes, I know you wrote you don't trust 'aptitude', this is just a
> search :)
>
> Kind regards,
> Andrei

that spits out about 3 or 4 lines of text and blanks it, in about 100 
millisecs, and will not redirect to |less. No line feeds IOW. I don't 
read at 20k wpm, so I've no clue what its trying to tell me.

Thanks Andrei.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Reco]

On Sun, Jul 19, 2020 at 02:20:13PM -0400, Gene Heskett wrote:
> On Sunday 19 July 2020 13:18:16 Reco wrote:
> 
> > On Sun, Jul 19, 2020 at 01:05:55PM -0400, Gene Heskett wrote:
> > > Now apt-get is bitching because it thinks I'm asking for version
> > > 3.0.3 but only 3.0.4 stuff is available:
> > >
> > > The following packages have unmet dependencies:
> > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > >Depends: libwxgtk-media3.0-dev (< 3.0.3~)
> > > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > >
> > > WHAT IS THE NAME OF THE BROKEN PACKAGE
> >
> > No need to shout. It says here loud and clear that you should
> > downgrade libwxgtk3.0-dev, libwxgtk-media3.0-dev and their
> > dependencies.
> >
> > Reco
> apt policy says the newer ones are installed already, so I 
> tried --allow-downgrades, but that is ignored and I still don't have a 
> clue what package is breaking it.

Something like this should do it.

apt-get install --allow-downgrades libwxgtk3.0-dev=3.0.2+dfsg-4 \
libwxgtk-media3.0-dev=3.0.2+dfsg-4

Add other libwxgtk* packages to the list as needed.

Reco

Re: Slic3r --gui won't run

[rhkramer]

On Sunday, July 19, 2020 01:05:55 PM Gene Heskett wrote:
> Now apt-get is bitching because it thinks I'm asking for version 3.0.3
> but only 3.0.4 stuff is available:
> 
> The following packages have unmet dependencies:
>  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxgtk-media3.0-dev (< 3.0.3~) but
> 3.0.4+dfsg-4~bpo9+1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> WHAT IS THE NAME OF THE BROKEN PACKAGE

I just solved a very similar problem (for ssh) with the aid of google and such 
(I'm sort of proud of myself ;-)

Anyway, what I had to do, for the package that had the message about the newer 
package to be installed, I had to do something like this (may not have the 
syntax exactly right, and the first time I ran it, I ran it with -s just to see 
what was going to happen):

apt-get -s install libwxgtk3.0-dev=3.0.3

In my case, the message specified an old version in a form like: 
3.0.4+dfsg-4~bpo9+1, so I'm not sure the 3.0.3 is specific enough.  Or maybe 
the equal sign can be replaced with a < or a <= (=<)?

After I successfully installed the old version of the file that was holding me 
back (openssh-client), then I was able to install my desired package (openssh-
server).

Aside: The funny thing to me (which someone might comment on) -- I absolutely 
know that the old version of openssh-client is installed (by running ssh -V), 
but I ran apt-get again (after installing openssh-server) and it tells me that 
openssh-client is the latest version, which is pretty much a clear lie.

But, ok.  Somewhere, during my reading / googling before solving the problem, 
I came across the word "pin" (or pinned) and I was looking for an apt-get or 
other command to find out which packages might be pinned (to the best of my 
knowledge, I've never intentionally pinned anything on my Wheezy installation 
(which, by the way, is what I was dealing with).

I'm guessing that someone would describe the situation of the old openssh-
client as being pinned, but does that word ever appear somewhere to describe 
the situation?  (I mean like, can you run apt-get (or something else) and get 
a list of pinned packages with the word "pinned" next to them? 

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 13:24:14 Andrei POPESCU wrote:

> On Du, 19 iul 20, 20:18:16, Reco wrote:
> > On Sun, Jul 19, 2020 at 01:05:55PM -0400, Gene Heskett wrote:
> > > Now apt-get is bitching because it thinks I'm asking for version
> > > 3.0.3 but only 3.0.4 stuff is available:
> > >
> > > The following packages have unmet dependencies:
> > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > >Depends: libwxgtk-media3.0-dev (<
> > > 3.0.3~) but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > >
> > > WHAT IS THE NAME OF THE BROKEN PACKAGE
> >
> > No need to shout. It says here loud and clear that you should
> > downgrade libwxgtk3.0-dev, libwxgtk-media3.0-dev and their
> > dependencies.
>
> By the way, I'm wondering why -dev packages are even needed.
>
> Gene, please show us the output of
>
> apt -V install libwx-perl

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libwx-perl : Depends: wxperl-gtk2-3-0-2-uni-gcc-3-4
  Depends: libalien-wxwidgets-perl (>= 0.65+dfsg~) but it is 
not going to be installed
E: Unable to correct problems, you have held broken packages.

The 2 packages name are  already installed acc apt policy

> Kind regards,
> Andrei


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 13:18:16 Reco wrote:

> On Sun, Jul 19, 2020 at 01:05:55PM -0400, Gene Heskett wrote:
> > Now apt-get is bitching because it thinks I'm asking for version
> > 3.0.3 but only 3.0.4 stuff is available:
> >
> > The following packages have unmet dependencies:
> >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> >Depends: libwxgtk-media3.0-dev (< 3.0.3~)
> > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> >
> > WHAT IS THE NAME OF THE BROKEN PACKAGE
>
> No need to shout. It says here loud and clear that you should
> downgrade libwxgtk3.0-dev, libwxgtk-media3.0-dev and their
> dependencies.
>
> Reco
apt policy says the newer ones are installed already, so I 
tried --allow-downgrades, but that is ignored and I still don't have a 
clue what package is breaking 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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 13:14:32 Andrei POPESCU wrote:

> On Du, 19 iul 20, 13:05:55, Gene Heskett wrote:
> > Now apt-get is bitching because it thinks I'm asking for version
> > 3.0.3 but only 3.0.4 stuff is available:
> >
> > The following packages have unmet dependencies:
> >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> >Depends: libwxgtk-media3.0-dev (< 3.0.3~)
> > but 3.0.4+dfsg-4~bpo9+1 is to be installed
> > E: Unable to correct problems, you have held broken packages.
>
> Just ignore the error message and concentrate on the other
> information.
>
> Please show us the output of:
>
> apt policy libwxgtk3.0-dev
> apt policy libwxgtk-media3.0-dev
>
Stretch, is apt-get country. But:

gene@coyote:~/Downloads/stl.stf/files$ apt policy libwxgtk3.0-dev
libwxgtk3.0-dev:
  Installed: 3.0.4+dfsg-4~bpo9+1
  Candidate: 3.0.4+dfsg-4~bpo9+1
  Version table:
 *** 3.0.4+dfsg-4~bpo9+1 100
100 /var/lib/dpkg/status
 3.0.2+dfsg-4 500
500 https://deb.debian.org/debian stretch/main amd64 Packages
gene@coyote:~/Downloads/stl.stf/files$ apt policy libwxgtk-media3.0-dev
libwxgtk-media3.0-dev:
  Installed: 3.0.4+dfsg-4~bpo9+1
  Candidate: 3.0.4+dfsg-4~bpo9+1
  Version table:
 *** 3.0.4+dfsg-4~bpo9+1 100
100 /var/lib/dpkg/status
 3.0.2+dfsg-4 500
500 https://deb.debian.org/debian stretch/main amd64 Packages

Running low on hair here. Nothing makes sense.

>
> Kind regards,
> Andrei

Thanks Andrei.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 12:47:45, Gene Heskett wrote:
> 
> Did that Andrei, updated apt-get, apt-get now gives a reason. Depends on 
> 2 more packages, but adding them to the apt-get install line gets this:

If APT can't find a solution adding more packages to the install line 
won't help.
 
> The following packages have unmet dependencies:
>  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxgtk-media3.0-dev (< 3.0.3~) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> I'm about out of patience for the day. I have been screwing with this 
> since about 5AM, and its now 12:45 local.  And I am damned tired of 
> apt-gets inability to name the package thats breaking it.

Considering how your sources.list looked like there's a non-zero 
probability your system is in an inconsistent state due to packages from 
stretch-backports that shouldn't be there.

The easiest way to find all installed packages from backports is to run

aptitude search '?narrow(?installed,?archive(backports))'


Yes, I know you wrote you don't trust 'aptitude', this is just a search :)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Reco]

On Sun, Jul 19, 2020 at 08:24:14PM +0300, Andrei POPESCU wrote:
> On Du, 19 iul 20, 20:18:16, Reco wrote:
> > On Sun, Jul 19, 2020 at 01:05:55PM -0400, Gene Heskett wrote:
> > > Now apt-get is bitching because it thinks I'm asking for version 3.0.3 
> > > but only 3.0.4 stuff is available:
> > > 
> > > The following packages have unmet dependencies:
> > >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but 
> > > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > >Depends: libwxgtk-media3.0-dev (< 3.0.3~) but 
> > > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > > E: Unable to correct problems, you have held broken packages.
> > > 
> > > WHAT IS THE NAME OF THE BROKEN PACKAGE
> > 
> > No need to shout. It says here loud and clear that you should downgrade
> > libwxgtk3.0-dev, libwxgtk-media3.0-dev and their dependencies.
> 
> By the way, I'm wondering why -dev packages are even needed.

They are the dependency of libalien-wxwidgets-perl believe it or not :)

Reco

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 20:18:16, Reco wrote:
> On Sun, Jul 19, 2020 at 01:05:55PM -0400, Gene Heskett wrote:
> > Now apt-get is bitching because it thinks I'm asking for version 3.0.3 
> > but only 3.0.4 stuff is available:
> > 
> > The following packages have unmet dependencies:
> >  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but 
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> >Depends: libwxgtk-media3.0-dev (< 3.0.3~) but 
> > 3.0.4+dfsg-4~bpo9+1 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> > 
> > WHAT IS THE NAME OF THE BROKEN PACKAGE
> 
> No need to shout. It says here loud and clear that you should downgrade
> libwxgtk3.0-dev, libwxgtk-media3.0-dev and their dependencies.

By the way, I'm wondering why -dev packages are even needed.

Gene, please show us the output of

apt -V install libwx-perl

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Reco]

On Sun, Jul 19, 2020 at 01:05:55PM -0400, Gene Heskett wrote:
> Now apt-get is bitching because it thinks I'm asking for version 3.0.3 
> but only 3.0.4 stuff is available:
> 
> The following packages have unmet dependencies:
>  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxgtk-media3.0-dev (< 3.0.3~) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> WHAT IS THE NAME OF THE BROKEN PACKAGE

No need to shout. It says here loud and clear that you should downgrade
libwxgtk3.0-dev, libwxgtk-media3.0-dev and their dependencies.

Reco

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 13:05:55, Gene Heskett wrote:
> 
> Now apt-get is bitching because it thinks I'm asking for version 3.0.3 
> but only 3.0.4 stuff is available:
> 
> The following packages have unmet dependencies:
>  libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
>Depends: libwxgtk-media3.0-dev (< 3.0.3~) but 
> 3.0.4+dfsg-4~bpo9+1 is to be installed
> E: Unable to correct problems, you have held broken packages.

Just ignore the error message and concentrate on the other information.

Please show us the output of:

apt policy libwxgtk3.0-dev
apt policy libwxgtk-media3.0-dev


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 12:32:40 Reco wrote:

> On Sun, Jul 19, 2020 at 12:19:02PM -0400, Gene Heskett wrote:
> > On Sunday 19 July 2020 10:32:12 Reco wrote:
> > > On Sun, Jul 19, 2020 at 10:28:08AM -0400, Gene Heskett wrote:
> > > > Whats my sources.list suposed to look like?
> > >
> > > One of the possible ways of doing it:
> > >
> > > deb http://ftp.debian.org/debian/ stretch main contrib non-free
> > > deb http://security.debian.org/ stretch/updates main contrib
> > > non-free
> >
> > Made it so,
>
> Did you? How many *other* "deb" strings do you have?
> I.e.
>
> grep -R "^deb " /etc/apt/sources.list*
>
> > refreshed synaptic,
>
> For the ease of troubleshooting do not use this. Please use
> conventional "apt-get"
>
I am slowly learning that but its the only gui package manager I can 
usually trust, I've had aptitude destroy an install by essentially 
formatting the disk 4 damned times now and it will never get another 
chance. It follows dependencies until the disk is blanked and there is 
no stopping it once it decides to clean house. No response to anything 
you do from the keyboard, only the power switch or system reset, all 4 
of which have only been recovered from by a re-install followed by 
several hours of amrecover.

Now apt-get is bitching because it thinks I'm asking for version 3.0.3 
but only 3.0.4 stuff is available:

The following packages have unmet dependencies:
 libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
   Depends: libwxgtk-media3.0-dev (< 3.0.3~) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
E: Unable to correct problems, you have held broken packages.

WHAT IS THE NAME OF THE BROKEN PACKAGE

> Reco


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 12:00:28 Andrei POPESCU wrote:

> On Du, 19 iul 20, 11:55:05, Gene Heskett wrote:
> > On Sunday 19 July 2020 09:56:10 Reco wrote:
> > > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > > Looks like my apt/sources.d is not uptodate?
> > >
> > > Looks like it is. Because [1] shows libwx-perl, and it's a real
> > > package.
> > >
> > > Reco
> > >
> > > [1] https://packages.debian.org/stretch/libwx-perl
> >
> > I found a page that shows what my sources.list should look like,
> > made it so, but still can't install libwx-perl because there is not
> > a perl-api-5.24.1 and a matching lib.  If this is a dependency of
> > slic3r or slic34-prussa, why did it not complain when I installed
> > slic3r a couple weeks back?  I'll remove it and start all over, if
> > it will let me.
> >
> > Rebooted, still gives me instant broken-packages for a mark on
> > libwx-perl.
> >
> > My current sources.list:
> >
> > # deb cdrom:[Unofficial LinuxCNC 'Stretch' amd64 Live/Install
> > 2018-10-27T16:56]/ stretch main
> >
> > # deb cdrom:[Unofficial LinuxCNC 'Stretch' amd64 Live/Install
> > 2018-10-27T16:56]/ stretch main
> >
> > # deb http://ftp.us.debian.org/debian/ stretch main
> > # deb-src http://ftp.us.debian.org/debian/ stretch main
> >
> > deb http://security.debian.org/debian-security/ stretch/updates
> > non-free contrib main deb http://deb.debian.org/debian/
> > stretch-backports nob-free contrib main
>
>  ^
> (but this is not your problem)
>
> > # deb http://deb.debian.org/debian/ stretch-oldstable non-free
> > contrib main
>
> There is no such thing as 'stretch-oldstable', it's either 'stretch'
> or 'oldstable'. I would suggest 'stretch'
>
> > # deb-src http://security.debian.org/debian-security/
> > stretch/updates main
> >
> > # stretch-updates, previously known as 'volatile'
> > # deb http://ftp.us.debian.org/debian/ stretch-updates main
> > # deb-src http://ftp.us.debian.org/debian/ stretch-updates main
> > EOF
> >
> > So what do I need to fix?
>
> Add
>
> deb https://deb.debian.org/debian/ stretch non-free contrib main
>
> or change the disabled line from above and don't forget to run
> 'apt update'.
>
> Hope this helps,
> Andrei

Did that Andrei, updated apt-get, apt-get now gives a reason. Depends on 
2 more packages, but adding them to the apt-get install line gets this:

The following packages have unmet dependencies:
 libalien-wxwidgets-perl : Depends: libwxgtk3.0-dev (< 3.0.3~) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
   Depends: libwxgtk-media3.0-dev (< 3.0.3~) but 
3.0.4+dfsg-4~bpo9+1 is to be installed
E: Unable to correct problems, you have held broken packages.

I'm about out of patience for the day. I have been screwing with this 
since about 5AM, and its now 12:45 local.  And I am damned tired of 
apt-gets inability to name the package thats breaking it.

Thank you for trying.



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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Reco]

On Sun, Jul 19, 2020 at 12:19:02PM -0400, Gene Heskett wrote:
> On Sunday 19 July 2020 10:32:12 Reco wrote:
> 
> > On Sun, Jul 19, 2020 at 10:28:08AM -0400, Gene Heskett wrote:
> > > Whats my sources.list suposed to look like?
> >
> > One of the possible ways of doing it:
> >
> > deb http://ftp.debian.org/debian/ stretch main contrib non-free
> > deb http://security.debian.org/ stretch/updates main contrib non-free
> 
> Made it so,

Did you? How many *other* "deb" strings do you have?
I.e.

grep -R "^deb " /etc/apt/sources.list*


> refreshed synaptic,

For the ease of troubleshooting do not use this. Please use conventional
"apt-get"

Reco

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 10:32:12 Reco wrote:

> On Sun, Jul 19, 2020 at 10:28:08AM -0400, Gene Heskett wrote:
> > Whats my sources.list suposed to look like?
>
> One of the possible ways of doing it:
>
> deb http://ftp.debian.org/debian/ stretch main contrib non-free
> deb http://security.debian.org/ stretch/updates main contrib non-free
>
> Reco

Made it so, refreshed synaptic, marking libwx-perl is still instant 
broken-packages. unmark it. do edit menu/fix-broken and get this, which 
has to set a record for lack of info.

E: Unable to correct problems, you have held broken packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be 
caused by held packages.
E: Unable to correct dependencies

Is apt-get that incapable of showing us the f.. reason?


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Andrei POPESCU]

On Du, 19 iul 20, 11:55:05, Gene Heskett wrote:
> On Sunday 19 July 2020 09:56:10 Reco wrote:
> 
> > On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > > Looks like my apt/sources.d is not uptodate?
> >
> > Looks like it is. Because [1] shows libwx-perl, and it's a real
> > package.
> >
> > Reco
> >
> > [1] https://packages.debian.org/stretch/libwx-perl
> 
> I found a page that shows what my sources.list should look like, made it 
> so, but still can't install libwx-perl because there is not a 
> perl-api-5.24.1 and a matching lib.  If this is a dependency of slic3r 
> or slic34-prussa, why did it not complain when I installed slic3r a 
> couple weeks back?  I'll remove it and start all over, if it will let 
> me.
> 
> Rebooted, still gives me instant broken-packages for a mark on libwx-perl.
> 
> My current sources.list:
> 
> # deb cdrom:[Unofficial LinuxCNC 'Stretch' amd64 Live/Install 
> 2018-10-27T16:56]/ stretch main 
> 
> # deb cdrom:[Unofficial LinuxCNC 'Stretch' amd64 Live/Install 
> 2018-10-27T16:56]/ stretch main 
> 
> # deb http://ftp.us.debian.org/debian/ stretch main 
> # deb-src http://ftp.us.debian.org/debian/ stretch main  
> 
> deb http://security.debian.org/debian-security/ stretch/updates non-free 
> contrib main  
> deb http://deb.debian.org/debian/ stretch-backports nob-free contrib main  
 ^
(but this is not your problem)

> # deb http://deb.debian.org/debian/ stretch-oldstable non-free contrib main  

There is no such thing as 'stretch-oldstable', it's either 'stretch' or 
'oldstable'. I would suggest 'stretch'

> # deb-src http://security.debian.org/debian-security/ stretch/updates 
> main 
> 
> # stretch-updates, previously known as 'volatile'
> # deb http://ftp.us.debian.org/debian/ stretch-updates main 
> # deb-src http://ftp.us.debian.org/debian/ stretch-updates main 
> EOF
> 
> So what do I need to fix?

Add

deb https://deb.debian.org/debian/ stretch non-free contrib main

or change the disabled line from above and don't forget to run
'apt update'.

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 09:56:10 Reco wrote:

> On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > Looks like my apt/sources.d is not uptodate?
>
> Looks like it is. Because [1] shows libwx-perl, and it's a real
> package.
>
> Reco
>
> [1] https://packages.debian.org/stretch/libwx-perl

I found a page that shows what my sources.list should look like, made it 
so, but still can't install libwx-perl because there is not a 
perl-api-5.24.1 and a matching lib.  If this is a dependency of slic3r 
or slic34-prussa, why did it not complain when I installed slic3r a 
couple weeks back?  I'll remove it and start all over, if it will let 
me.

Rebooted, still gives me instant broken-packages for a mark on libwx-perl.

My current sources.list:

# deb cdrom:[Unofficial LinuxCNC 'Stretch' amd64 Live/Install 
2018-10-27T16:56]/ stretch main 

# deb cdrom:[Unofficial LinuxCNC 'Stretch' amd64 Live/Install 
2018-10-27T16:56]/ stretch main 

# deb http://ftp.us.debian.org/debian/ stretch main 
# deb-src http://ftp.us.debian.org/debian/ stretch main  

deb http://security.debian.org/debian-security/ stretch/updates non-free 
contrib main  
deb http://deb.debian.org/debian/ stretch-backports nob-free contrib main  
# deb http://deb.debian.org/debian/ stretch-oldstable non-free contrib main  
# deb-src http://security.debian.org/debian-security/ stretch/updates main 

# stretch-updates, previously known as 'volatile'
# deb http://ftp.us.debian.org/debian/ stretch-updates main 
# deb-src http://ftp.us.debian.org/debian/ stretch-updates main 
EOF

So what do I need to fix?

Removed and reinstalled scic3r & slic3r-prussa, no deps listed.
Somethings fubar.

Thank you Reco

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Reco]

Hi.

On Sun, Jul 19, 2020 at 05:35:04PM +0200, Frank wrote:
> Op 19-07-2020 om 16:32 schreef Reco:
> > On Sun, Jul 19, 2020 at 10:28:08AM -0400, Gene Heskett wrote:
> > > Whats my sources.list suposed to look like?
> > 
> > One of the possible ways of doing it:
> > 
> > deb http://ftp.debian.org/debian/ stretch main contrib non-free
> > deb http://security.debian.org/ stretch/updates main contrib non-free
> > 
> > Reco
> 
> Don't use ftp.debian.org.
> 
> https://wiki.debian.org/ftp.debian.org

Feel free to provide another set of strings for sources.list,
verbatim.

Reco

Re: Slic3r --gui won't run

[Frank]

Op 19-07-2020 om 16:32 schreef Reco:

On Sun, Jul 19, 2020 at 10:28:08AM -0400, Gene Heskett wrote:

Whats my sources.list suposed to look like?


One of the possible ways of doing it:

deb http://ftp.debian.org/debian/ stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free

Reco


Don't use ftp.debian.org.

https://wiki.debian.org/ftp.debian.org

Regards,
Frank

Re: Slic3r --gui won't run

[Reco]

On Sun, Jul 19, 2020 at 10:28:08AM -0400, Gene Heskett wrote:
> Whats my sources.list suposed to look like?

One of the possible ways of doing it:

deb http://ftp.debian.org/debian/ stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free

Reco

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 09:56:10 Reco wrote:

> On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> > Looks like my apt/sources.d is not uptodate?
>
> Looks like it is. Because [1] shows libwx-perl, and it's a real
> package.
>
> Reco
>
> [1] https://packages.debian.org/stretch/libwx-perl
Whats my sources.list suposed to look like?
 

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Reco]

On Sun, Jul 19, 2020 at 09:45:41AM -0400, Gene Heskett wrote:
> Looks like my apt/sources.d is not uptodate?

Looks like it is. Because [1] shows libwx-perl, and it's a real
package.

Reco

[1] https://packages.debian.org/stretch/libwx-perl

Re: Slic3r --gui won't run

[Gene Heskett]

On Sunday 19 July 2020 08:15:51 Reco wrote:

>   Hi.
>
> On Sun, Jul 19, 2020 at 08:00:17AM -0400, Gene Heskett wrote:
> > That also fails, looking for Wx.
>
> apt-get install libwx-perl
>
> Reco

gene@coyote:~/Downloads/stl.stf/files$ sudo apt-get install libwx-perl
[sudo] password for gene:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libwx-perl is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libwx-perl' has no installation candidate

Looks like my apt/sources.d is not uptodate?


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Slic3r --gui won't run

[Reco]

Hi.

On Sun, Jul 19, 2020 at 08:00:17AM -0400, Gene Heskett wrote:
> That also fails, looking for Wx.

apt-get install libwx-perl

Reco