Bug#765572: Please provide a better upgrade process

2014-11-24 Thread Mattia Rizzolo
On Thu, Oct 16, 2014 at 12:35 PM, Klaus Ethgen kl...@ethgen.de wrote:
 The new eatmydata put the .so file to another location so while
 upgrading the system, there will be many of the following error messages
 when apt is run with eatmydata:

I feel you are doing something really wrong in using apt with eatmydata. I hope 
you will not blame someone different to yourself if some bad things occur to 
your system.

ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from 
 LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

 The upgrade process should put a link in the old location and remove it
 only if LD_PRELOAD is populated with the new location.

Well, this would mean change the content of LD_PRELOAD of a running process 
(apt and children), not something wise to do. Actually the content of 
LD_PRELOAD is changed once you restart apt, not before.
I could drop a symlink, but when I'm going to remove it? I can't think of 
anything sane to do here.

A better thing to do wuold be change the eatmydata script in wheezy to do 
something more clever (e.g. by using the script currently in experimental) so 
even the libeatmydata library path change in the middle of the upgrade ld would 
know where to find it.

Either way, I'd be for just ignore the warning and go ahead. I'll think it 
better, but currently I'm overload.


-- 
regards,
Mattia Rizzolo

GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo


signature.asc
Description: GooPG digital signature


Bug#765572: Please provide a better upgrade process

2014-11-24 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Am Mo den 24. Nov 2014 um 14:03 schrieb Mattia Rizzolo:
 On Thu, Oct 16, 2014 at 12:35 PM, Klaus Ethgen kl...@ethgen.de wrote:
  The new eatmydata put the .so file to another location so while
  upgrading the system, there will be many of the following error messages
  when apt is run with eatmydata:
 
 I feel you are doing something really wrong in using apt with eatmydata. I 
 hope you will not blame someone different to yourself if some bad things 
 occur to your system.

Well, I would like to do it without eatmydata. Unfortunately is apt (or
dpkg) does a to aggressive sync orgy. In my setup (not to slow disks but
no SSD) a a bit bigger upgrade takes far over 30 minutes where it take
only 1 or 2 minutes with eatmydata. The risk that something goes wrong
in 30 minutes is much higher than in 1 minute. I also like more the
kernel to know about what should be written to disk.

I read somewhere about an idea to have a command line switch to apt
and/or dpkg to not sync that aggressive while an upgrade. That would be
a real good idea.

Finally, what do you think, eatmydata was originally the reason for? It
was exactly the complete crazy sync orgies in apt. (That is what I
heard about.)

 ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from 
  LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
 
  The upgrade process should put a link in the old location and remove it
  only if LD_PRELOAD is populated with the new location.
 
 Well, this would mean change the content of LD_PRELOAD of a running process 
 (apt and children), not something wise to do. Actually the content of 
 LD_PRELOAD is changed once you restart apt, not before.
 I could drop a symlink, but when I'm going to remove it? I can't think of 
 anything sane to do here.

Well, doesn't matter if the content changes as the process will have the
old (now deleted) file still opened. The problem are new spawned
processes who cannot find the libraries in LD_PRELOAD.

A symlink is great here. It is even easy to check if that path is still
in LD_PRELOAD. If not, that can be deleted safely.

 Either way, I'd be for just ignore the warning and go ahead. I'll think it 
 better, but currently I'm overload.

That might be ok for me too. It is only scarring first seeing that
error.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJUcz07AAoJEKZ8CrGAGfasxzUL/RDz9nbYaxRHbkevblfzZprG
OXQdRNFPqmpZ/dFbxGbOTY2y3NyVNZqo0buLf+oQa57uvb/gd+bjXHEsQY5b3zXb
E8/9BZvPvg1P9Sm7ruy/hityugSZtIdJ8fnQsgQJPlqX/PX3O+1RTM1PIjcVFVM9
13163fmVeOKS4F5SZVkjffsa6rmRSkz0Ag1mTWIKnp1MKNvUlW+n7ov0NzRH5/RK
OTguTH/Jfsd8lyHIVTWwE165iVBXylP/1rdh91uvDVJ7R0FCcRuvwSZGm/NktGpc
BXd2qBBzcSLzxOhP3HEf8XPykGTCVfhssnOghuokFlSJVEzv1fjDvf0k7AR5Lu27
j0w25oNko9aNkml6C+mCdWXriagm+QPIjFEMyTqv0fAcV8LMSgM/9LMDrw7IF6SR
KHEzNlLkCV5U8J6GkFRVQsFP3STKbTLOjCMgf96liNW2q0E1vcEgsNq5Zlqfjm5l
LMI83o4IoTa3RT6bLh6jWsEqcYF8k/dnihLzBfTBSQ==
=5B7l
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765572: Please provide a better upgrade process

2014-11-24 Thread Mattia Rizzolo
On Mon, Nov 24, 2014 at 3:14 PM, Klaus Ethgen kl...@ethgen.de wrote:
 I read somewhere about an idea to have a command line switch to apt
 and/or dpkg to not sync that aggressive while an upgrade. That would be
 a real good idea.

dpkg --force-unsafe-io
added on Thu, 25 Nov 2010 07:10:48 +0100 with the 1.15.8.6 upload.

Actually it doesn't remove all the sync calls, but a lot of them for sure.

-- 
regards,
Mattia Rizzolo

GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765572: Please provide a better upgrade process

2014-11-24 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Am Mo den 24. Nov 2014 um 15:27 schrieb Mattia Rizzolo:
 On Mon, Nov 24, 2014 at 3:14 PM, Klaus Ethgen kl...@ethgen.de wrote:
  I read somewhere about an idea to have a command line switch to apt
  and/or dpkg to not sync that aggressive while an upgrade. That would be
  a real good idea.
 
 dpkg --force-unsafe-io
 added on Thu, 25 Nov 2010 07:10:48 +0100 with the 1.15.8.6 upload.
 
 Actually it doesn't remove all the sync calls, but a lot of them for sure.

Yes, thanks, that is what I read about. There was somewhere a bit thread
about that. I was not aware that it is in the current version. Hopefully
there is a comparable config option as I do not think that I can add it
for how apt uses dpkg.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJUc0LcAAoJEKZ8CrGAGfasgxIL/0rApSYTp4Kg/+apn/z27fUd
CtfYIbPVGSx2irqaAS+AIkpZXJg1gQg4cF53psE9sgCS03PofHPewXFfSSeewqJ9
AEY4Jbe7mBp6z20twLAfxzumwc78nCSDqW554YKmWNzG9fXDjM4wLT9+loSn+rxY
jqIafb9B6HmmYWjwiIHr21pclMCTteHawYRu3F8SabxvK7nVl3iPef1ukOawFTYk
QwIsnEMGpYUimZeUZ5vqUjHq+flsGB+G4FQZWfY+FC0qb1AYQQ+MqUPBcG5Vuyyr
Aa/tyGM9Z77DztlgmS129bgtKdzoj/y2tJ6K4x3BhH6zJ+7wqmRHuXbwxh3/Io6q
XIDdBSyvtx2ATuX4cFKYhzREQSzV9tgHku1Y3ezXxWhX5yqnQu1ZsPtddYl2WwDD
bVL+daq5j6bIGDe65n3gmNmmHcaEkoxEo6X/z5VbrdUBCFNTgCOZsrSOeFyL3JYa
PdHOgq7EfPQXuPRrrbFYeDyjyys+9/coNNa/RnZjJQ==
=yTSe
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#765572: Please provide a better upgrade process

2014-11-24 Thread Mattia Rizzolo
On Mon Nov 24 2014 at 3:38:25 PM Klaus Ethgen kl...@ethgen.de wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 Hi,

 Am Mo den 24. Nov 2014 um 15:27 schrieb Mattia Rizzolo:
  On Mon, Nov 24, 2014 at 3:14 PM, Klaus Ethgen kl...@ethgen.de wrote:
   I read somewhere about an idea to have a command line switch to apt
   and/or dpkg to not sync that aggressive while an upgrade. That would be
   a real good idea.
 
  dpkg --force-unsafe-io
  added on Thu, 25 Nov 2010 07:10:48 +0100 with the 1.15.8.6 upload.
 
  Actually it doesn't remove all the sync calls, but a lot of them for
 sure.

 Yes, thanks, that is what I read about. There was somewhere a bit thread
 about that. I was not aware that it is in the current version. Hopefully
 there is a comparable config option as I do not think that I can add it
 for how apt uses dpkg.


the option: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584254#67
The bug I was talking about:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613428


Bug#765572: Please provide a better upgrade process

2014-10-16 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: eatmydata
Version: 82-2
Severity: normal

The new eatmydata put the .so file to another location so while
upgrading the system, there will be many of the following error messages
when apt is run with eatmydata:
   ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD 
cannot be preloaded (cannot open shared object file): ignored.

The upgrade process should put a link in the old location and remove it
only if LD_PRELOAD is populated with the new location.

- -- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.15.10 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to 
de_DE)
Shell: /bin/sh linked to /bin/dash

Versions of packages eatmydata depends on:
ii  libc6  2.19-11

eatmydata recommends no packages.

eatmydata suggests no packages.

- -- no debconf information

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJUP59nAAoJEKZ8CrGAGfasT5EL/0cuAah8dcklInthJGAkDp0D
nCOLhKoG8l1U8l86Ga3FM8UMY3SGaUTkiHk2z8wVnA6u3CcsoFY3anlPPihDTmNt
1esDjFRHoMBbKfy76mgfZZyQZetIbT7rDKJo//xRoEzNRc+hiyja8WeMo2IRbilX
gW6J7XOKynAs4XXdt49SHYDPLOfG3rC2Apku6YSHLa3b0atOEua2Sj1qbXIgrcwp
aiz3YF3BwISEcGZT1pH7l1Z52ESNCr62FPNiq0XbL3CaCrowedkyMU6rQIa20nyd
Cm8A6/J5yP/1FxxzMPdbXv/EQPE2/vXR4Q6WUEmsGJy2efXTkOMg37XaMpAWPZkq
1TfT110Tkfvx+CgmnOf/lJntcT///cFjKEqBsBmM4JgzNcQeLxcaJA0MXOGITTex
duQUi+n304f9CxwUrxskddThAQ+VvOpcqad2s5LumD+JbXHEaajaq4bnQwMW4AgQ
hp8prLBErPb3hPnL2pWmqulIJpqin+6xWPzYyaa96Q==
=jbIN
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org