Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #224970 > unrolled thread
| Started by | Gene Heskett <gheskett@shentel.net> |
|---|---|
| First post | 2020-07-19 14:10 +0200 |
| Last post | 2020-07-21 21:40 +0200 |
| Articles | 20 on this page of 69 — 10 participants |
Back to article view | Back to linux.debian.user
Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 14:10 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 14:20 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 15:50 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 16:00 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 16:30 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 16:40 +0200
Re: Slic3r --gui won't run Frank <zuiderduin@gmx.com> - 2020-07-19 17:40 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 17:40 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 18:20 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 18:40 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 19:10 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 19:20 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:10 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 12:50 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 19:20 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 19:30 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 19:40 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:30 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 20:30 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:50 +0200
Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 21:40 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:30 +0200
Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-19 20:30 +0200
Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-19 20:40 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:50 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:20 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:00 +0200
Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-20 16:20 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 18:30 +0200
Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 19:10 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 19:10 +0200
Re: Debian and Raspberry Pi4 (was: Slic3r --gui won't run). Reco <recoverym4n@enotuniq.net> - 2020-07-20 19:50 +0200
Re: Debian and Raspberry Pi4 (was: Slic3r --gui won't run). Andrew Cater <amacater@gmail.com> - 2020-07-20 23:40 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 20:00 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-21 08:50 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-21 09:10 +0200
Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-21 13:50 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-21 15:00 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-23 08:10 +0200
Re: Slic3r --gui won't run Steve McIntyre <steve@einval.com> - 2020-07-24 13:00 +0200
Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-21 21:00 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 18:00 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 18:10 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 18:50 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 19:40 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:40 +0200
Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 07:00 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 11:00 +0200
Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 17:10 +0200
Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 17:20 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 19:40 +0200
Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 19:50 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 20:40 +0200
Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-20 22:20 +0200
Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 20:40 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:30 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 17:40 +0200
Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 17:50 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 18:00 +0200
Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 19:50 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-21 08:50 +0200
Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-21 20:50 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-23 08:20 +0200
Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 19:50 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:20 +0200
Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 15:10 +0200
Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 19:00 +0200
Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 19:30 +0200
Re: Slic3r --gui won't run mick crane <mick.crane@gmail.com> - 2020-07-21 21:40 +0200
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2020-07-19 21:40 +0200 |
| Message-ID | <Aunkd-1Pe-5@gated-at.bofh.it> |
| In reply to | #225007 |
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
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2020-07-19 20:30 +0200 |
| Message-ID | <Aumet-1d4-1@gated-at.bofh.it> |
| In reply to | #224992 |
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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | rhkramer@gmail.com |
|---|---|
| Date | 2020-07-19 20:30 +0200 |
| Message-ID | <Aumet-1d4-3@gated-at.bofh.it> |
| In reply to | #224990 |
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?
[toc] | [prev] | [next] | [standalone]
| From | rhkramer@gmail.com |
|---|---|
| Date | 2020-07-19 20:40 +0200 |
| Message-ID | <Aumo9-1gf-9@gated-at.bofh.it> |
| In reply to | #225000 |
On Sunday, July 19, 2020 02:27:24 PM rhkramer@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?
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2020-07-19 20:50 +0200 |
| Message-ID | <AumxP-1jM-7@gated-at.bofh.it> |
| In reply to | #225000 |
On Sunday 19 July 2020 14:27:24 rhkramer@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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-07-20 13:20 +0200 |
| Message-ID | <AuBZT-2ni-3@gated-at.bofh.it> |
| In reply to | #225006 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-07-20 13:00 +0200 |
| Message-ID | <AuBGy-21h-11@gated-at.bofh.it> |
| In reply to | #225000 |
[Multipart message — attachments visible in raw view] — view raw
On Du, 19 iul 20, 14:27:24, rhkramer@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
[toc] | [prev] | [next] | [standalone]
| From | rhkramer@gmail.com |
|---|---|
| Date | 2020-07-20 16:20 +0200 |
| Message-ID | <AuEO5-45D-7@gated-at.bofh.it> |
| In reply to | #225030 |
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.)
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2020-07-20 18:30 +0200 |
| Message-ID | <AuGPT-5hp-7@gated-at.bofh.it> |
| In reply to | #225041 |
On Monday 20 July 2020 10:11:40 rhkramer@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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-07-20 19:10 +0200 |
| Message-ID | <AuHsB-5JT-3@gated-at.bofh.it> |
| In reply to | #225051 |
On Mon 20 Jul 2020 at 12:24:35 (-0400), Gene Heskett wrote: > On Monday 20 July 2020 10:11:40 rhkramer@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.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-07-20 19:10 +0200 |
| Message-ID | <AuHsC-5JT-11@gated-at.bofh.it> |
| In reply to | #225051 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2020-07-20 19:50 +0200 |
| Subject | Re: Debian and Raspberry Pi4 (was: Slic3r --gui won't run). |
| Message-ID | <AuI5k-5WG-7@gated-at.bofh.it> |
| In reply to | #225058 |
On Mon, Jul 20, 2020 at 08:01:17PM +0300, 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. > > And buster doesn't work with that kernel because... ? Because, strictly speaking, *Debian* buster cannot run at Raspberry Pi 4 at all - see [1]. There's some big progress with sid, though - [2]. The short and the long of it is that Gene is using *Raspbian*, but prefers to get help about it here. One could get away with Raspbian kernel and Debian chroot, I suppose, but that's cheating. Reco [1] https://lists.debian.org/msgid-search/20200426195815.GA5215@xanadu.blop.info [2] https://gwolf.org/2020/07/raspberry-pi-4-now-running-your-favorite-distribution.html
[toc] | [prev] | [next] | [standalone]
| From | Andrew Cater <amacater@gmail.com> |
|---|---|
| Date | 2020-07-20 23:40 +0200 |
| Subject | Re: Debian and Raspberry Pi4 (was: Slic3r --gui won't run). |
| Message-ID | <AuLFT-88Q-7@gated-at.bofh.it> |
| In reply to | #225065 |
[Multipart message — attachments visible in raw view] — view raw
https://raspi.debian.net/tested-images/ - there's at least one image there for the 4GB Raspberry Pi 4 from Gunnar Wolf - but note that this is still a work in progress. It's certainly possible: other folk have got this to boot using experimental UEFI - it's there such that you don't _have_ to use Raspberry Pi OS any more. On Mon, Jul 20, 2020 at 5:48 PM Reco <recoverym4n@enotuniq.net> wrote: > On Mon, Jul 20, 2020 at 08:01:17PM +0300, 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. > > > > And buster doesn't work with that kernel because... ? > > Because, strictly speaking, *Debian* buster cannot run at Raspberry > Pi 4 at all - see [1]. There's some big progress with sid, though - [2]. > > The short and the long of it is that Gene is using *Raspbian*, but > prefers to get help about it here. > > One could get away with Raspbian kernel and Debian chroot, I suppose, but > that's cheating. > > Reco > > [1] > https://lists.debian.org/msgid-search/20200426195815.GA5215@xanadu.blop.info > [2] > https://gwolf.org/2020/07/raspberry-pi-4-now-running-your-favorite-distribution.html > >
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2020-07-20 20:00 +0200 |
| Message-ID | <AuIf0-601-9@gated-at.bofh.it> |
| In reply to | #225058 |
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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-07-21 08:50 +0200 |
| Message-ID | <AuUg9-4Qu-1@gated-at.bofh.it> |
| In reply to | #225067 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2020-07-21 09:10 +0200 |
| Message-ID | <AuUzw-5ck-1@gated-at.bofh.it> |
| In reply to | #225088 |
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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2020-07-21 13:50 +0200 |
| Message-ID | <AuYWt-7NM-3@gated-at.bofh.it> |
| In reply to | #225088 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2020-07-21 15:00 +0200 |
| Message-ID | <Av02d-8p4-3@gated-at.bofh.it> |
| In reply to | #225105 |
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 <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-07-23 08:10 +0200 |
| Message-ID | <AvCAy-6JK-19@gated-at.bofh.it> |
| In reply to | #225106 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | Steve McIntyre <steve@einval.com> |
|---|---|
| Date | 2020-07-24 13:00 +0200 |
| Message-ID | <Aw3AK-6iL-9@gated-at.bofh.it> |
| In reply to | #225106 |
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. steve@einval.com "You can't barbecue lettuce!" -- Ellie Crane
[toc] | [prev] | [next] | [standalone]
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web