likcoras composed on 2018-01-11 16:17 (UTC+0900):
> On 01/11/2018 04:08 PM, Felix Miata wrote:
>> ...
>> err:9 http://ftp.debian.org/debian stretch-backports/main i386 Packages
>> 404 Not Found...
>
> Try adding a trailing slash to the deb url:
>
> http://ftp.debian.org/debian/
> and not
>
On 01/11/2018 04:08 PM, Felix Miata wrote:
> ...
> err:9 http://ftp.debian.org/debian stretch-backports/main i386 Packages
> 404 Not Found...
Try adding a trailing slash to the deb url:
http://ftp.debian.org/debian/
and not
http://ftp.debian.org/debian
Trying to get a non-broken recent version of mc, the instructions on
https://backports.debian.org/Instructions/ fail[1]. How can I get a non-broken
relatively recent mc package installed, e.g. patched 4.8.19, or 4.8.20? Breakage
was fixed 15 months ago[2].
[1] # apt-get update
...
err:9 http://ftp
On 01/06/2018 06:58 PM, Rob Hurle wrote:
Hi All,
I'm running Stretch and yesterday I did my normal:
sudo apt-get update
sudo apt-get upgrade
It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config and
image files, etc) in place of 4.9.0-4-686-pae versions. Now the system
won't
deloptes composed on 2018-01-11 01:12 (UTC+0100):
> David Wright wrote:
>>> It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config and
>>> image files, etc) in place of 4.9.0-4-686-pae versions. Now the system
>> ↑↑↑ really? It's a different package so
>> it should install
David Wright wrote:
>> It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config and
>> image files, etc) in place of 4.9.0-4-686-pae versions. Now the system
>
> ↑↑↑ really? It's a different package so
> it should install alongside the old one.
no, this is one and the same pa
Greg Wooledge wrote:
> Moreover, the simple zcat|cpio -i no longer works with stretch's initrd
> images. They're in a different format, and you have to use
> lsinitramfs or unmkinitramfs to see or extract their contents.
>
> On a jessie system, the zcat|cpio -i may still work (not sure about
> b
On 2018-01-10 16:58 -0500, Felix Miata wrote:
> In the case of stable Debian release kernel versioning at least, the .0 in
> both
> seem to be entirely superfluous. Does any other integer ever appear in place
> of
> that 0?
No. The trailing .0 is only there to appease programs that do not work
David Wright composed on 2018-01-10 15:12 (UTC-0600):
> On Tue 09 Jan 2018 at 18:18:27 (-0500), Felix Miata wrote:
>> Here's a portion of /boot/ on one I just updated minutes ago:
>> lrwxrwxrwx 1 26 Jan 9 17:47 initrd -> initrd.img-4.9.0-5-686-pae
>> lrwxrwxrwx 1 26 Jan 9 17:47 i
I have a QEMU/KVM virtual machine on which I linked a USB device.
I use testing, however with the 4.14.0-2 of testing, the VM does not
start because it cannot access the USB device. Running the same testing
userland, but with kernel 4.9.0-5 from stable, everything works. What
could be the reason,
On Tue 09 Jan 2018 at 18:18:27 (-0500), Felix Miata wrote:
> Here's a portion of /boot/ on one I just updated minutes ago:
>
> lrwxrwxrwx 1 26 Jan 9 17:47 initrd -> initrd.img-4.9.0-5-686-pae
> lrwxrwxrwx 1 26 Jan 9 17:47 initrd-cur -> initrd.img-4.9.0-5-686-pae
> -rw-r--r-- 1 17
On Wed, Jan 10, 2018 at 03:56:17PM -0500, Felix Miata wrote:
> deloptes composed on 2018-01-10 19:48 (UTC+0100):
>
> > 7.1 if you need to examine initrd
>
> > cd /tmp/
> > mkdir test
> > cd test/
> > zcat /boot/initrd.img- | cpio -id
>
> > do whatever you
deloptes composed on 2018-01-10 19:48 (UTC+0100):
> 7.1 if you need to examine initrd
> cd /tmp/
> mkdir test
> cd test/
> zcat /boot/initrd.img- | cpio -id
> do whatever you need to do
> find . ! -name *~ | cpio -H newc --create | gzip -9
>> /boo
On Sun 07 Jan 2018 at 13:58:25 (+1100), Rob Hurle wrote:
> I'm running Stretch and yesterday I did my normal:
>
> sudo apt-get update
> sudo apt-get upgrade
>
> It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config and
> image files, etc) in place of 4.9.0-4-686-pae versions. Now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jan 10, 2018 at 07:10:03PM +, Brian wrote:
> On Wed 10 Jan 2018 at 17:13:09 +0100, to...@tuxteam.de wrote:
[...]
> > Downside is that it does the panoramic tour via PS and thus generates
> > fairly hefty PDFs.
>
> With plain text files a
On Wed 10 Jan 2018 at 10:31:14 +, Brian wrote:
> On Wed 10 Jan 2018 at 09:02:08 +, Curt wrote:
>
> > On 2018-01-09, David Wright wrote:
>
> [...]
>
> > > And that's without discussing whether having to install a TeX system
> > > is any better than installing LibreOffice.
> >
> > Yes,
On Wed 10 Jan 2018 at 17:13:09 +0100, to...@tuxteam.de wrote:
> On Wed, Jan 10, 2018 at 09:38:47AM -0600, David Wright wrote:
>
> And to be fair, results can be pretty exciting, depending on the
> actual file content...
>
> I would go with a2ps, too, btw.
>
> Downside is that it does the panora
Elisabetta Falivene wrote:
> It wasn't me to configure the machine in the first place so is a bit
> tricky. I can give more information if you can point me out what you could
> need. thank you a lot
well it is interesting to know if you have raid or so, if your boot and root
are on LVM, or probab
Elisabetta Falivene wrote:
>>> Unfortunately is already 'most'.
>> Please check if you have a file /etc/initramfs-tools/conf.d/driver-policy
>> or any other file containing a different configuration. Anything in
>> /etc/initramfs-tools/conf.d/ takes precedence over the main config file.
> Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jan 10, 2018 at 09:38:47AM -0600, David Wright wrote:
> On Wed 10 Jan 2018 at 10:46:43 (+0100), to...@tuxteam.de wrote:
[text, yeah!]
> > But for me, (La)TeX *are* text :-)
>
> Yes, you can put me in the text camp, and a little further over
On Wed 10 Jan 2018 at 10:46:43 (+0100), to...@tuxteam.de wrote:
> On Wed, Jan 10, 2018 at 09:02:08AM +, Curt wrote:
>
> [...]
>
> > You (a thirty-year veteran latex user we learn elsewhere): Please explain
> > the
> > first step (which is how to create a latex file).
> >
> > > than TeX/La
On Wed, Jan 10, 2018 at 08:22:51AM -0600, Richard Owlett wrote:
I multi-boot several varieties of Debian.
When booting one specific install I many repetitions to the effect
that it is beginning a specific script.
It then proceeds to bring up an apparently normal system.
Would this be logged s
On 2018-01-10 14:58, MAS Jean-Louis wrote:
Le 10/01/2018 à 12:30, Jonathan Sélea a écrit :
It was installed because CraftCMS depends on it :)
According to term.log - unattended-upgrade performed the update
2018-01-06 06:41 and every package was updated (including
php7.1-mbstring)
Just two
On Wed 10 Jan 2018 at 08:22:51 (-0600), Richard Owlett wrote:
> I multi-boot several varieties of Debian.
> When booting one specific install I many repetitions to the effect
> that it is beginning a specific script.
>
> It then proceeds to bring up an apparently normal system.
>
> Would this be
On Wed 10 Jan 2018 at 11:34:57 (+), Steve McIntyre wrote:
> hosack...@gmail.com wrote:
> >
> >This is a bug report. I tried to use the reporting system, but it did not
> >seem to be appropriate. So, I will give a narrative:
> >
> >This is what happened.
> >I decided to install Debian on my smal
On Wed 10 Jan 2018 at 10:41:12 (+), Jonathan Dowland wrote:
> On Tue, 2018-01-09 at 23:34 -0500, The Wanderer wrote:
> > If the entry was not changed to be commented out during the conclusion
> > of the initial OS install procedure, that sounds like an issue
> > indeed, although a relatively mi
I multi-boot several varieties of Debian.
When booting one specific install I many repetitions to the effect that
it is beginning a specific script.
It then proceeds to bring up an apparently normal system.
Would this be logged somewhere?
Where?
TIA
Le 10/01/2018 à 12:30, Jonathan Sélea a écrit :
> It was installed because CraftCMS depends on it :)
>
> According to term.log - unattended-upgrade performed the update
> 2018-01-06 06:41 and every package was updated (including php7.1-mbstring)
>
> Just two minutes after that, unattended-upgrade
On 01/09/2018 07:54 PM, John Hosack wrote:
Hello,
This is a bug report. I tried to use the reporting system, but it did not
seem to be appropriate. So, I will give a narrative:
This is what happened.
I decided to install Debian on my small machine (Asus eeePC 900A, 1GB
ram, 4GB storage). So I
On 10-01-2018, at 10h 46'43", to...@tuxteam.de wrote about "Re: How to create a
PDF-Printer from the command line"
>
> But for me, (La)TeX *are* text :-)
>
+1
Ionel
>
>
> > Unfortunately is already 'most'.
>
> Please check if you have a file /etc/initramfs-tools/conf.d/driver-policy
> or any other file containing a different configuration. Anything in
> /etc/initramfs-tools/conf.d/ takes precedence over the main config file.
>
Thank you, it was "dep" indeed!
On Mon, Jan 8, 2018 at 5:20 PM, Richard Hector
wrote:
> On 09/01/18 04:36, francis picabia wrote:
> > I have the option to install
> > the stretch kernel and run in a hybrid version for awhile, but I'm not
> sure
> > if there will be problems with that workaround.
>
> The jessie-backports kernel
On 2018-01-10 at 05:41, Jonathan Dowland wrote:
> On Tue, 2018-01-09 at 23:34 -0500, The Wanderer wrote:
>
>> If the entry was not changed to be commented out during the
>> conclusion of the initial OS install procedure, that sounds like an
>> issue indeed, although a relatively minor one. But th
On 01/10/2018 04:41 AM, Jonathan Dowland wrote:
On Tue, 2018-01-09 at 23:34 -0500, The Wanderer wrote:
If the entry was not changed to be commented out during the conclusion
of the initial OS install procedure, that sounds like an issue
indeed, although a relatively minor one. But the inclusion
hosack...@gmail.com wrote:
>
>This is a bug report. I tried to use the reporting system, but it did not
>seem to be appropriate. So, I will give a narrative:
>
>This is what happened.
>I decided to install Debian on my small machine (Asus eeePC 900A, 1GB
>ram, 4GB storage). So I selected debian-9.
Elisabetta Falivene wrote:
> Unfortunately is already 'most'.
Please check if you have a file /etc/initramfs-tools/conf.d/driver-policy
or any other file containing a different configuration. Anything in
/etc/initramfs-tools/conf.d/ takes precedence over the main config file.
> There is a way
It was installed because CraftCMS depends on it :)
According to term.log - unattended-upgrade performed the update
2018-01-06 06:41 and every package was updated (including php7.1-mbstring)
Just two minutes after that, unattended-upgrade runs again and removes
php7.1-mbstring and only that pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jan 10, 2018 at 12:01:50PM +0100, Jonathan Sélea wrote:
> Hi
>
> I am running Debian Stretch but with sury.org repository. :)
>
> Jonathan Download suggested that I checked what package is depending
> php7.1-mbstring on with:
>
> apt rdepe
Hi
I am running Debian Stretch but with sury.org repository. :)
Jonathan Download suggested that I checked what package is depending
php7.1-mbstring on with:
apt rdepends php7.1-mbstring
php7.1-mbstring
Reverse Depends:
Depends:
php7.1-mbstring-dbgsym (= 7.1.13-1+0~20180105151623.14+stre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jan 10, 2018 at 11:17:50AM +0100, Jonathan Sélea wrote:
> Good morning,
>
> I am trying to figure out why apt did remove this particular package
> when unattended-upgrade ran a couple of days ago:
>
>
> Start-Date: 2018-01-06 06:43:44
> Comm
On Tue, 2018-01-09 at 23:34 -0500, The Wanderer wrote:
> If the entry was not changed to be commented out during the conclusion
> of the initial OS install procedure, that sounds like an issue
> indeed, although a relatively minor one. But the inclusion of the
> entry in sources.list is not an erro
Hi!
On Wed, 2018-01-10 at 11:17 +0100, Jonathan Sélea wrote:
> I am trying to figure out why apt did remove this particular package
> when unattended-upgrade ran a couple of days ago:
The most likely explanation is that it was automatically-installed as a
dependency of another package, and an up
>
> looks like initrd and/or udev
> There were similar issues with upgrade from wheezy to jessie in my upgrades
> as well.
> I usually boot with usb stick and fix the initrd - you might need to
> configure or reconfigure few things. the easiest to try is to recreate
> initrd.
Yes, all the hints p
On Wed 10 Jan 2018 at 09:02:08 +, Curt wrote:
> On 2018-01-09, David Wright wrote:
[...]
> > And that's without discussing whether having to install a TeX system
> > is any better than installing LibreOffice.
>
> Yes, I know, you're all flying to the moon in 1969 and must fit
> everything
>
>
> > Truly, it boots correctly with the old kernel 3.2, but not with 3.16.
> >
> > In the kernel 3.16 case, moreover, when the initramfs prompt is shown, it
> > seems not to load the usb keyboard so i'm truly able to do anything.
>
> This sounds like the initramfs doesn't have the appropriate mo
Good morning,
I am trying to figure out why apt did remove this particular package
when unattended-upgrade ran a couple of days ago:
Start-Date: 2018-01-06 06:43:44
Commandline: /usr/bin/unattended-upgrade Remove: php7.1-mbstring:amd64
(7.1.13-1+0~20180105151623.14+stretch~1.gbp1086fa)
End-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jan 10, 2018 at 09:02:08AM +, Curt wrote:
[...]
> You (a thirty-year veteran latex user we learn elsewhere): Please explain the
> first step (which is how to create a latex file).
>
> > than TeX/LaTeX is a useless way to turn a *text*
On 2018-01-09, David Wright wrote:
>
> Perhaps before this protracted, tangential and niggling subthread
> becomes acrimonious or invidious, it might be easier to just state
Well, it did, through no fault of mine own, I must say, turn both
acrimonious and invidious. I have been neither (up till n
48 matches
Mail list logo
