Re: Bug#571136: 1.0.76 breaks qemu'd debootstrap

[Jason Heeris]

I've just tried a live-build cross build of an armhf image from an amd64
VM, with debootstrap 1.0.78, and had it fail this way too.

Debian: stretch (last updated five minutes ago)
live-build: 1:20151215 (but reports as 5.0~a11-1)
debootstrap: 1.0.78
qemu: 1:2.5+dfsg-5

The command to reproduce the error is:

  lb config \
--apt-indices none \
--apt-source-archives false \
--distribution wheezy \
--binary-images hdd \
--hdd-size 512 \
--architectures armhf \
--bootstrap-qemu-arch armhf \
--bootstrap-qemu-static /usr/bin/qemu-arm-static \
--firmware-binary false \
--firmware-chroot false

  sudo lb build 2>&1 | tee build_log

The final part of the build log says:

  P: Running debootstrap second stage under QEMU
  I: Keyring file not available at
/usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror
https://mirrors.kernel.org/debian
  P: Begin unmounting filesystems...
  P: Saving caches...
  /usr/bin/env: apt-get: No such file or directory

Full log: https://gist.github.com/detly/52a830858f539682764f

Is this a bug? Or am I doing something unsupported?

I didn't know enough to know if this was a -live or -boot issue. (Also,
sorry for breaking threading, but I wasn't subscribed to -boot.)

Cheers,
Jason Heeris

Re: s390-zfcp: Not sure I want to send translators on this bunch of cryptic strings to translate

[Philipp Kern]

On 2016-02-09 07:41, Bastian Blank wrote:

On Tue, Feb 09, 2016 at 07:22:19AM +0100, Christian PERRIER wrote:

As a consequence, I'm highly tempted to mark all these strings as "non
translatable". Indeed they are.

Just do it.


Sounds good to me. Sorry for the hassle.

Kind regards
Philipp Kern

Bug#213013: Account Verification

[PayPal Online Security]

Dear Valued User,

Our automatic security system indicates that someone was trying to use your 
account without your consent.

When PayPal limits an account, we are simply asking you to provide information 
which verifies your identity that links to your account.

We have sent you this notification hoping that you would provide some 
information with us; thus verifying that you are the legitimate account holder.
By downloading and filling in the form that we have supplied in the 
'attachment', you may proceed to verifying your account.

Please note that your account will be restored back to its normal state after 
you have provided valid information in the form.

We apologize for the inconvenience this may have caused. We hope this issue 
gets resolved today.

Sincerely,
PayPal Account Security Team



verification.html
Description: Binary data

Re: s390-zfcp: Not sure I want to send translators on this bunch of cryptic strings to translate

[Christian PERRIER]

Quoting Philipp Kern (pk...@debian.org):
> On 2016-02-09 07:41, Bastian Blank wrote:
> >On Tue, Feb 09, 2016 at 07:22:19AM +0100, Christian PERRIER wrote:
> >>As a consequence, I'm highly tempted to mark all these strings as "non
> >>translatable". Indeed they are.
> >Just do it.
> 
> Sounds good to me. Sorry for the hassle.


Committed in git. 

However, please notice that the released version doesn't seem to have
been committed or push in git. And probably not tagged as well.




signature.asc
Description: PGP signature

Bug#571136: 1.0.76 breaks qemu'd debootstrap (1.0.78)

[Jason Heeris]

I've just tried a live-build cross build of an armhf image from a stretch
amd64
VM, with debootstrap 1.0.78, and had it fail this way too.

live-build: 1:20151215 (but reports as 5.0~a11-1)
debootstrap: 1.0.78
qemu: 1:2.5+dfsg-5

The command to reproduce the error is:

  lb config \
--apt-indices none \
--apt-source-archives false \
--distribution wheezy \
--binary-images hdd \
--hdd-size 512 \
--architectures armhf \
--bootstrap-qemu-arch armhf \
--bootstrap-qemu-static /usr/bin/qemu-arm-static \
--firmware-binary false \
--firmware-chroot false

  sudo lb build 2>&1 | tee build_log

The final part of the build log says:

  P: Running debootstrap second stage under QEMU
  I: Keyring file not available at
/usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror
https://mirrors.kernel.org/debian
  P: Begin unmounting filesystems...
  P: Saving caches...
  /usr/bin/env: apt-get: No such file or directory

The full log is attached.

Cheers,
Jason Heeris

PS. Sorry for (a) not using reportbug, but I'm not at that machine right
now;
and (b) the multiple postings.


build_log
Description: Binary data

[PATCH grub-installer master] put grub-installer modifications in grub.d

[Jonathan Toppins]

To prevent loss of config when grub-pc is updated and the user naively
chooses to take the maintainer's version any intelligent modifications
done during installation will be lost.

Instead we take advantage of the fact that the grub-pc package in
Debian since tag 2.00-10 contained some version of reading
/etc/default/grub.d/*.cfg to read additional configuration without
triggering a ucf missmatch.

Reported-by: Curt Brune 
Signed-off-by: Jonathan Toppins 
---

Please consider this for backport to Jessie, I was able to cherry-pick
this patch cleanly on top of version 1.117+deb8u1. Also of note I only
tested with a rebuilt Jessie installer using monolithic and localudebs
version of grub-installer udeb.

Thanks!

 grub-installer | 13 +++--
 1 file changed, 3 insertions(+), 10 deletions(-)

diff --git a/grub-installer b/grub-installer
index 8b4531231e09..c6d911e882d8 100755
--- a/grub-installer
+++ b/grub-installer
@@ -1151,16 +1151,9 @@ if [ "$serial" ] ; then
mv $ROOT/boot/grub/$menu_file.new $ROOT/boot/grub/$menu_file
;;
grub-pc|grub-efi*)
-   if grep -q "^GRUB_TERMINAL=" $ROOT/etc/default/grub; then
-   sed -i $ROOT/etc/default/grub -e 
"s/^\(GRUB_TERMINAL\)=.*/\1=serial/g"
-   else
-   echo "GRUB_TERMINAL=serial" >> $ROOT/etc/default/grub
-   fi
-   if grep -q "^GRUB_SERIAL_COMMAND=" $ROOT/etc/default/grub ; then
-   sed -i $ROOT/etc/default/grub -e 
"s/^\(GRUB_SERIAL_COMMAND\)=.*/\1=\"`grub_serial_console $serial`\"/g"
-   else
-   echo "GRUB_SERIAL_COMMAND=\"`grub_serial_console 
$serial`\"" >> $ROOT/etc/default/grub
-   fi
+   mkdir -p $ROOT/etc/default/grub.d
+   echo "GRUB_TERMINAL=serial" > 
$ROOT/etc/default/grub.d/00-installer-defaults.cfg
+   echo "GRUB_SERIAL_COMMAND=\"`grub_serial_console $serial`\"" >> 
$ROOT/etc/default/grub.d/00-installer-defaults.cfg
update_grub # propagate to grub.cfg
;;
esac
-- 
2.1.4

Bug#571136: 1.0.76 breaks qemu'd debootstrap (1.0.78)

[Marco d'Itri]

On Feb 10, Jason Heeris  wrote:

> I've just tried a live-build cross build of an armhf image from a stretch
> amd64
> VM, with debootstrap 1.0.78, and had it fail this way too.
This is about #813232. I posted a candidate patch, but nobody cared.
Feel free to test it and report if it works.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Re: [PATCH grub-installer master] put grub-installer modifications in grub.d

[Christian PERRIER]

Quoting Jonathan Toppins (jtopp...@cumulusnetworks.com):
> To prevent loss of config when grub-pc is updated and the user naively
> chooses to take the maintainer's version any intelligent modifications
> done during installation will be lost.
> 
> Instead we take advantage of the fact that the grub-pc package in
> Debian since tag 2.00-10 contained some version of reading
> /etc/default/grub.d/*.cfg to read additional configuration without
> triggering a ucf missmatch.
> 
> Reported-by: Curt Brune 
> Signed-off-by: Jonathan Toppins 
> ---
> 
> Please consider this for backport to Jessie, I was able to cherry-pick
> this patch cleanly on top of version 1.117+deb8u1. Also of note I only
> tested with a rebuilt Jessie installer using monolithic and localudebs
> version of grub-installer udeb.

Hello,

It's very likely to be lost unless you send this as a bug
report, against grub-installer.




signature.asc
Description: PGP signature