Bug#921815: debootstrap umount "host" /proc when running in a Docker container
control: tags -1 -moreinfo Hi Sorry for the late response. I wasn't subscribed to the bug (I assume?). On 23.02.2020 14.01, Hideki Yamane wrote: When running debootstrap inside a Docker container, debootstrap umount both /proc and $TARGET/proc. How do I check it? - run docker - get debootstrap 1.0.110 and install it - debootstrap sid sid - /proc is there inside docker as below Did you use a privileged container? /proc can't be unmounted in a regular non-privileged container. I just tried and "/proc" is unmounted: $ docker run --privileged --rm -t -i debian:stretch-backports bash $ apt-get update && apt-get install -y -t stretch-backports debootstrap $ debootstrap stretch chroot $ ls /proc # it is empty I also tried the debootstrap version in sid: $ docker run --privileged --rm -t -i debian:sid bash $ apt-get update && apt-get install -y debootstrap $ debootstrap sid chroot $ ls /proc # it is empty Also please see the MRs: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/26 https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/27 https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/30 I'm not sure which approach is the best, but Eicke did a short analysis: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/26#note_171042 root@b49ab8b7f3eb:~# ls /proc/ 1 crypto iomemkpageflagspartitions sysrq-trigger 19486 devices ioports loadavg pressure sysvipc acpi diskstatsirq locks sched_debug thread-self asound dma kallsyms meminfo schedstattimer_list buddyinfo driver kcoremisc self tty busexecdomains key-usersmodules slabinfo uptime cgroupsfb keys mountssoftirqs version cmdlinefilesystems kmsg mtrr stat vmallocinfo consoles fs kpagecgroup net swapsvmstat cpuinfointerrupts kpagecount pagetypeinfo sys zoneinfo --- - Kristian Klausen
Bug#921815: debootstrap umount "host" /proc when running in a Docker container
I have opened a MR: https://salsa.debian.org/installer-team/debootstrap/merge_requests/26
Bug#919659: live-build: building in docker fails with mounting /proc unmount /sys [UPDATE]
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921815 and https://salsa.debian.org/installer-team/debootstrap/merge_requests/26
Bug#921815: debootstrap umount "host" /proc when running in a Docker container
Package: debootstrap Version: 1.0.110~bpo9+1 Hi When running debootstrap inside a Docker container, debootstrap umount both /proc and $TARGET/proc. This is due to a missing check at: https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L104 Due to the missing check debootstrap umount "$TARGET/proc", which is a symlink to /proc [1]. I will open a MR shortly. [1] https://salsa.debian.org/installer-team/debootstrap/blob/67a3c1c5f7ef44a6596f75b787289b3392c50759/scripts/debian-common#L68 - Kristian Klausen
Bug#885455: live-boot: Please drop wget from initrd (busybox provides wget)
> > Am Mittwoch, den 21.02.2018, 10:08 +0100 schrieb Raphael Hertzog: > > Hello, > > > > On Wed, 27 Dec 2017, Benjamin Drung wrote: > > > The wget binary depends on many libraries. On Debian 9 (stretch) > > > these > > > are: libffi6, libgnutls30, libhogweed4, libidn11, libidn2-0, > > > libnettle6, > > > libp11-kit0, libpsl5, libtasn1-6, libunistring0. In total 8 > > > megabytes. > > > This increases the initramfs size a lot. To save space, use wget > > > from > > > busybox instead. Commit 4328832d0 that adds wget does not give a > > > reason > > > why busybox's wget is not used. A patch is tested and attached. > > > > The usual reason is for "https" support. Have you tried to use https > > URLs in the various places where we can use URLs? > > Okay. I did some tests in a minimal schroot environment: > > (stretch)root@konstrukt:~# dpkg -s busybox | grep ^Version > Version: 1:1.22.0-19+b3 > (stretch)root@konstrukt:~# busybox wget https://bugs.debian.org/ > wget: not an http or ftp url: https://bugs.debian.org/ > > (buster)root@konstrukt:~# dpkg -s busybox | grep ^Version > Version: 1:1.27.2-2 > (buster)root@konstrukt:~# busybox wget https://bugs.debian.org/ > Connecting to bugs.debian.org (209.87.16.39:443) > Connecting to www.debian.org (5.153.231.4:443) > index.html 100% |***| 18089 0:00:00 ETA > > So busybox in stretch does not support HTTPS, but it supports HTTPS in > testing/unstable. Busybox version of wget does not check the certificate at all, which defeat the purpose of https. Tested with (on testing): busybox wget 'https://untrusted-root.badssl.com/' and busybox wget 'https://expired.badssl.com/' - Kristian
Bug#845034: Updated patch
Hello Attached is a updated patch, which disable the ldconfig aux-cache (/var/cache/ldconfig/aux-cache), as it isn't reproducible (at least not on my system). Can I in anyway help getting this merged? - Kristian Klausen diff --git a/debian/control b/debian/control index cc7c32d..33c1185 100644 --- a/debian/control +++ b/debian/control @@ -25,7 +25,7 @@ Package: initramfs-tools-core Architecture: all Multi-Arch: foreign Recommends: ${busybox:Recommends} -Depends: klibc-utils (>= 2.0.4-8~), cpio, kmod | module-init-tools, udev, ${misc:Depends} +Depends: klibc-utils (>= 2.0.4-8~), cpio (>= 2.12), kmod | module-init-tools, udev, ${misc:Depends} Suggests: bash-completion Breaks: initramfs-tools (<< 0.121~), ${busybox:Breaks} Replaces: initramfs-tools (<< 0.121~) diff --git a/mkinitramfs b/mkinitramfs index 24715d5..fcdcb47 100755 --- a/mkinitramfs +++ b/mkinitramfs @@ -151,6 +151,7 @@ if dpkg --compare-versions "${version}" lt "2.6.38" 2>/dev/null; then echo "linux-2.6 likely misses ${COMPRESS} support, using gzip" fi +[ "${compress}" = gzip ] && [ -n "${SOURCE_DATE_EPOCH}" ] && compress="gzip -n" [ "${compress}" = lzop ] && compress="lzop -9" [ "${compress}" = xz ] && compress="xz --check=crc32" @@ -332,7 +333,7 @@ rm -f "${DESTDIR}/lib/modules/${version}"/modules.*map # make sure that library search path is up to date cp -ar /etc/ld.so.conf* "$DESTDIR"/etc/ -if ! ldconfig -r "$DESTDIR" ; then +if ! ldconfig -X -N -r "$DESTDIR" ; then [ $(id -u) != "0" ] \ && echo "ldconfig might need uid=0 (root) for chroot()" >&2 fi @@ -372,8 +373,18 @@ fi # preserve permissions if root builds the image, see #633582 [ "$(id -ru)" != 0 ] && cpio_owner_root="-R 0:0" +# if SOURCE_DATE_EPOCH is set, try and create a reproducible image +if [ -n "${SOURCE_DATE_EPOCH}" ]; then + # ensure that no timestamps are newer than $SOURCE_DATE_EPOCH + find "${DESTDIR}" -newermt "@${SOURCE_DATE_EPOCH}" -print0 | \ + xargs -0r touch --no-dereference --date="@${SOURCE_DATE_EPOCH}" + + # --reproducible requires cpio >= 2.12 + cpio_reproducible="--reproducible" +fi + # work around lack of "set -o pipefail" for the following pipe: -# cd "${DESTDIR}" && find . | cpio --quiet $cpio_owner_root -o -H newc | gzip >>"${outfile}" || exit 1 +# cd "${DESTDIR}" && find . | LC_ALL=C sort | cpio --quiet $cpio_owner_root $cpio_reproducible -o -H newc | gzip >>"${outfile}" || exit 1 exec 3>&1 eval ` # http://cfaj.freeshell.org/shell/cus-faq-2.html @@ -382,7 +393,9 @@ eval ` { find . 4>&-; echo "ec1=$?;" >&4 } | { - cpio --quiet $cpio_owner_root -o -H newc 4>&-; echo "ec2=$?;" >&4 + LC_ALL=C sort + } | { + cpio --quiet $cpio_owner_root $cpio_reproducible -o -H newc 4>&-; echo "ec2=$?;" >&4 } | ${compress} >>"${outfile}" echo "ec3=$?;" >&4 ` diff --git a/mkinitramfs.8 b/mkinitramfs.8 index 4c8bae5..b61fdeb 100644 --- a/mkinitramfs.8 +++ b/mkinitramfs.8 @@ -105,6 +105,12 @@ should not be mounted with the .B noexec mount option. +If +.B SOURCE_DATE_EPOCH +is set, +.B mkinitramfs +attempts to generate a reproducible ramdisk. + .SH FILES .TP .I /etc/initramfs-tools/initramfs.conf
Bug#854004: Sv: Bug#854004: live-config: keyboard configuration in live-build image now working
Hello Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818065 One way to fix it, is adding /etc/default/keyboard and running the console-setup.sh in hook (theory, I haven't tested it). Regards Kristian Klausen Fra: sp113438 <sp113...@telfort.nl> Sendt: 3. februar 2017 01:46 Til: debian-l...@lists.debian.org Cc: Dieter Scholz; 854...@bugs.debian.org Emne: Bug#854004: live-config: keyboard configuration in live-build image now working On Thu, 02 Feb 2017 23:49:15 +0100 Dieter Scholz <rd-d...@gmx.net> wrote: Hello, keyboard-layouts=de ? keyboard-layout=de perhaps, just a guess? greetings > Package: live-config > Version: 5.20170112 > Severity: normal > Tags: l10n > > Hello, > > I tried to build a customized live image with live-build. To > configure my keyboard I'm using the following boot append options: > > locales=de_DE.UTF-8 timezone=Europe/Berlin keyboard-model=pc105 > keyboard-layouts=de > > I found these options in the man page. > > They have no effect when I boot my CD. If I execute > > dpkg-reconfigure -f noninteractive console-tools > > my keyboard is working. I additionally booted a stock live CDs using > the above params - without success either. So I think it's a bug. > > Kind regards > > Dieter > > -- System Information: > Debian Release: 9.0 > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.9.0-1-amd64 (SMP w/1 CPU core) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages live-config depends on: > ii live-config-systemd [live-config-backend] 5.20170112 > > Versions of packages live-config recommends: > ii iproute2 4.9.0-1 > ii keyboard-configuration 1.158 > ii live-config-doc 5.20170112 > ii live-tools 1:20151214+nmu1 > ii locales 2.24-8 > ii sudo 1.8.19p1-1 > ii user-setup 1.67 > > Versions of packages live-config suggests: > ii pciutils 1:3.5.2-1 > ii wget 1.18-4 > > -- no debconf information >
Bug#818065: Sv: Bug#818065: console-setup is not read correctly at boottime and must be started manually
Hello Anton > Yes, in this case setupcon is never run from console-setup.sh. However > there is no need to use setupcon in order to configure the font because > this is done by /lib/udev/rules.d/90-console-setup.rules and the > keyboard is configured by /lib/systemd/system/keyboard-setup.service. keyboard-setup.service doesn't seems to configure the layout, rerunning it change nothing but as soon I rerun console-setup.service the layout is fixed. > How big is is this image? Will it be possible to send it to me so I can > test? Around ~ 700MB, but I need to strip a few thing out before I can share it. I'm properly just gonna upload it to my webserver. Regards Kristian Klausen
Bug#818065: console-setup is not read correctly at boottime and must be started manually
Hello I have just experienced this issue after "upgrading" (rebuilding) my live image to stretch from jessie. As it is a live-image, every boot is "first boot" as Anton said could give issue. So I looked a bit on the code, and I think the issue is caused by line 11 in console-setup (*), the line make so console-setup.sh does nothing at first run after boot, and as console-setup.service is only run once per boot, setupcon (which configure keyboard layout) is never run. How did this ever get into testing? :) * https://anonscm.debian.org/cgit/d-i/console-setup.git/tree/init/console-setup.sh?id=85d541bcfe7557caee0e544ac6c547f97174db32#n11 Regards Kristian Klausen
Bug#842641: Sv: Bug#842641: RFS: autoconf/2.69-10~bpo8+1
Hi G > Kristian, are you happy with that? > You set yourself as uploader for the backport, so I take the answer as "yes" > (and the upload will show under my ddpo account, so I'll see probably issues Yes that is correct. Kristian Fra: Gianfranco CostamagnaSendt: 31. oktober 2016 16:56 Til: Ben Pfaff; Alexander Wirt; 842...@bugs.debian.org Cc: pfaff...@debian.org; klausenb...@hotmail.com Emne: Re: Bug#842641: RFS: autoconf/2.69-10~bpo8+1 Hi Alex, Ben, Kristian >Gianfranco, are you planning to take responsibility for uploading this >as it changes in Debian proper? It is probably not a big >responsibility, because autoconf changes rarely. I'm willing to sponsor >the uploads. I would prefer Kristian to take care of this, but yeah, I'm planning to help/sponsor him for jessie lifespan, since I'm interested in connman backports, and meh, we are talking about one/two uploads each year :) Kristian, are you happy with that? You set yourself as uploader for the backport, so I take the answer as "yes" (and the upload will show under my ddpo account, so I'll see probably issues too here) BTW Ben if you want to take care for the backport by yourself, I'm happy to cancel or give you the task :) Gianfranco
Bug#842641: RFS: autoconf/2.69-10~bpo8+1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "autoconf". Some packages depends on the new --runstatedir option which was added in 2.69-9, before they can be built for jessie-backports. Ex connman. Is this request okay with you Ben, or do you want to handle it? * Package name : autoconf Version : 2.69-10~bpo8+1 Upstream Author : autoc...@gnu.org * URL : https://www.gnu.org/software/autoconf/autoconf.html * License : GPL-3+ Section : devel It builds those binary packages: autoconf - automatic configure script builder autoconf-doc - automatic configure script builder documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/autoconf Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/autoconf/autoconf_2.69-10~bpo8+1.dsc More information about hello can be obtained from https://www.gnu.org/software/autoconf/autoconf.html Changes since the last upload: autoconf (2.69-10~bpo8+1) jessie-backports; urgency=medium * Rebuild for jessie-backports. -- Kristian Klausen <klausenb...@hotmail.com> Sun, 30 Oct 2016 22:40:42 +0000 Regards, Kristian Klausen
Bug#839871: Connman not working with some routers due to not following RFC.
Package: connman Version: 1.32-0.1 Severity: important Hello Connman 1.32 doesn't follow the RFC regarding the order of some dhcp options. This result in Connman not working with some routers/dhcp server, for example the D-Link DSR-1000. It took me some hours to figure that out, and my patch was upstreamed today. Could this be cherry-picked? https://git.kernel.org/cgit/network/connman/connman.git/commit/?id=fee1e4fec7a78480e5a4d7b8c5d43e679c148829 So we/I don't need to wait for Conman 1.34. - Kristian Klausen
Bug#833741: Sv: Bug#833741: pepperflashplugin-nonfree: Feature request?: Download from Adobe instead of Google.
Hello I have created a patch while implement this (see attachment). This should also fix that it break (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839543), every time Google change something regarding the Chrome apt repository. - Kristian Klausen Fra: Bart Martens <ba...@debian.org> Sendt: 8. august 2016 18:48 Til: James C; 833...@bugs.debian.org Emne: Bug#833741: pepperflashplugin-nonfree: Feature request?: Download from Adobe instead of Google. On Mon, Aug 08, 2016 at 11:11:57PM +1200, James C wrote: > Package: pepperflashplugin-nonfree > Version: 1.8.1 > Severity: wishlist > > Dear Maintainer, > > Apparently Adobe now has Pepper Flash available for download from their site. > This is just Pepper Flash, not the whole Chrome browser. > Also, an update to the 32-bit version seems to be available. > See: > http://forum.mepiscommunity.org/viewtopic.php?t=40254 Indeed. > > (This was mentioned in the discussion for #831058, > but I think it deserves a new bug report.) I agree, thanks. > > I'm not sure if this counts as a bug, so I've marked it wishlist, Perfect. > but if it was possible to switch to downloading from the Adobe site, > it would speed up the download, and make the 32-bit version available again. Yes, I'm considering that. Regards, Bart Martens --- a/update-pepperflashplugin-nonfree 2016-10-02 16:05:04.678209065 +0200 +++ b/update-pepperflashplugin-nonfree 2016-10-02 16:48:31.644832357 +0200 @@ -30,7 +30,7 @@ exit 1 } -[ `id -u` = "0" ] || die_hard "must be root" +[ "$(id -u)" = "0" ] || die_hard "must be root" show_usage() { echo "Usage:" @@ -43,18 +43,15 @@ exit 1 } -getopt_temp=`getopt -o iusfvq --long install,uninstall,status,fast,verbose,quiet,beta,unstable,unverified \ - -n 'update-pepperflashplugin-nonfree' -- "$@"` || show_usage +getopt_temp="$(getopt -o iusfvq --long install,uninstall,status,verbose,quiet \ + -n 'update-pepperflashplugin-nonfree' -- "$@")" || show_usage eval set -- "$getopt_temp" || show_usage ACTION=none -fast=no verbose=no quiet=no -variant=stable -verified=yes -while [ true ] +while true do case "$1" in -i|--install) @@ -69,10 +66,6 @@ ACTION="--status" shift ;; - -f|--fast) - fast=yes - shift - ;; -v|--verbose) verbose=yes shift @@ -81,18 +74,6 @@ quiet=yes shift ;; - --beta) - variant=beta - shift - ;; - --unstable) - variant=unstable - shift - ;; - --unverified) - verified=no - shift - ;; --) shift break @@ -104,111 +85,31 @@ esac done -[ "$ACTION" != "none" -a $# -eq 0 ] || show_usage +([ "$ACTION" != "none" ] && [ $# -eq 0 ]) || show_usage [ "$quiet" != "yes" ] || verbose=no [ "$verbose" != "yes" ] || echo "options : $getopt_temp" -latestfile=latest-$variant-verified.txt -[ "$verified" != "no" ] || latestfile=latest-$variant.txt - -UNPACKDIR=`mktemp -d /tmp/pepperflashplugin-nonfree.XX` || die_hard "mktemp failed" -echo "$UNPACKDIR" | grep -q "^/tmp/pepperflashplugin-nonfree\." || die_hard "paranoia" -cd "$UNPACKDIR" || die_hard "cd failed" - -[ "$verbose" != "yes" ] || echo "temporary directory: $UNPACKDIR" - -do_cleanup() { - [ "$verbose" != "yes" ] || echo "cleaning up temporary directory $UNPACKDIR ..." - cd / - echo "$UNPACKDIR" | grep -q "^/tmp/pepperflashplugin-nonfree\." || die_hard "paranoia" - rm -rf "$UNPACKDIR" -} - die_hard_with_a_cleanup() { return_0 - do_cleanup die_hard "$1" } trap "die_hard_with_a_cleanup interrupted" INT -cachedir=/var/cache/pepperflashplugin-nonfree - -wgetquiet=' -q ' -wgetfast='-t 3 -T 15 ' -wgetalways=' -nd -P . ' -wgetprogress=' -v --progress=dot:default ' - -if [ "$ACTION" = "--install" -o "$ACTION" = "--status" ] +if [ "$ACTION" = "--install" ] || [ "$ACTION" = "--status" ] then - installed=`strings /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` - - [ ! -f $cachedir/$latestfile ] || [ `wc -l $cachedir/$latestfile | cut -f 1 -d ' '` -eq 2 ] || rm $cachedir/$latestfile - - if [ -f $cachedir/$latestfile ] - then - chromeversion=`head -n 1 $cachedir/$latestfile` - flashversion=`tail -n 1 $cachedir/$latestfile` + arch="" + if [ "$(dpkg --print-architecture)" = "amd64" ]; then + arch="x86-64" + elif [ "$(dpkg --print-architecture)" = "i386"
Bug#827296: #827296 - connman: Connman slow down the boot when no network available
Hi Yes it was changed in June, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812209 - Kristian > Subject: Bug#827296: #827296 - connman: Connman slow down the boot when no > network available > From: a...@debian.org > Date: Fri, 2 Sep 2016 13:55:21 +0200 > To: klausenb...@hotmail.com > CC: 827...@bugs.debian.org; flor...@biree.name; cont...@bugs.debian.org > > Hi, > > so NM does enable the wait job by default also? Just timeout > difference? If not I tend to agree that whatever the NM default is > this one should have as well (assuming folks are happy with NM boot > behaviour). > > Let me know, > > - Alexander > > 2016-09-02 11:05 GMT+02:00 Kristian Klausen <klausenb...@hotmail.com>: >> Never mind, maybe I should reread the bug report next time before I >> respond.. >> >> >> >> From: klausenb...@hotmail.com >> To: a...@debian.org; 827...@bugs.debian.org >> CC: flor...@biree.name; cont...@bugs.debian.org >> Subject: RE: Bug#827296: #827296 - connman: Connman slow down the boot when >> no network available >> Date: Fri, 2 Sep 2016 11:03:15 +0200 >> >> >> Hello Alexander >> >> NetworkManager don't enable it as default which Connman does. >> I think that is what the bug report is about :) >> >> Regards >> Kristian Klausen >> >>> Subject: Bug#827296: #827296 - connman: Connman slow down the boot when no >>> network available >>> From: a...@debian.org >>> Date: Fri, 2 Sep 2016 10:53:45 +0200 >>> To: 827...@bugs.debian.org >>> CC: flor...@biree.name; cont...@bugs.debian.org >>> >>> tags 827296 + moreinfo >>> severity 827296 normal >>> thanks >>> >>> Hi, >>> >>> this seems to be a feature. Seems you were able to resolve this issue? >>> Anything you think that should be done here? >>> >>> Network Manager also has a similar wait job. timeout there is 30 >>> seconds. connman just seem to have a higher default timeout in code >>> (120 seconds). >>> >>> You could customize the job with --timeout=30 or we could use that as >>> the default in the package if we feel there is strong reason to >>> believe that majority of debian users will want the shorter timeout. >>> >>> Let me know if you are happy with the ability to tweak by yourself... >>> >>> Thanks, >>> >>> - Alexander >>> >
Bug#827296: #827296 - connman: Connman slow down the boot when no network available
Hello Alexander NetworkManager don't enable it as default which Connman does. I think that is what the bug report is about :) Regards Kristian Klausen > Subject: Bug#827296: #827296 - connman: Connman slow down the boot when no > network available > From: a...@debian.org > Date: Fri, 2 Sep 2016 10:53:45 +0200 > To: 827...@bugs.debian.org > CC: flor...@biree.name; cont...@bugs.debian.org > > tags 827296 + moreinfo > severity 827296 normal > thanks > > Hi, > > this seems to be a feature. Seems you were able to resolve this issue? > Anything you think that should be done here? > > Network Manager also has a similar wait job. timeout there is 30 > seconds. connman just seem to have a higher default timeout in code > (120 seconds). > > You could customize the job with --timeout=30 or we could use that as > the default in the package if we feel there is strong reason to > believe that majority of debian users will want the shorter timeout. > > Let me know if you are happy with the ability to tweak by yourself... > > Thanks, > > - Alexander >
Bug#827296: #827296 - connman: Connman slow down the boot when no network available
Never mind, maybe I should reread the bug report next time before I respond.. From: klausenb...@hotmail.com To: a...@debian.org; 827...@bugs.debian.org CC: flor...@biree.name; cont...@bugs.debian.org Subject: RE: Bug#827296: #827296 - connman: Connman slow down the boot when no network available Date: Fri, 2 Sep 2016 11:03:15 +0200 Hello Alexander NetworkManager don't enable it as default which Connman does. I think that is what the bug report is about :) Regards Kristian Klausen > Subject: Bug#827296: #827296 - connman: Connman slow down the boot when no > network available > From: a...@debian.org > Date: Fri, 2 Sep 2016 10:53:45 +0200 > To: 827...@bugs.debian.org > CC: flor...@biree.name; cont...@bugs.debian.org > > tags 827296 + moreinfo > severity 827296 normal > thanks > > Hi, > > this seems to be a feature. Seems you were able to resolve this issue? > Anything you think that should be done here? > > Network Manager also has a similar wait job. timeout there is 30 > seconds. connman just seem to have a higher default timeout in code > (120 seconds). > > You could customize the job with --timeout=30 or we could use that as > the default in the package if we feel there is strong reason to > believe that majority of debian users will want the shorter timeout. > > Let me know if you are happy with the ability to tweak by yourself... > > Thanks, > > - Alexander >
Bug#827296: connman: Connman slow down the boot when no network available
I just checked NetworkManager, and they only install it (NetworkManager-wait-online.service) but does not enable it. I think that is the correct behavior, next time someone update connman they could fix this bug :) > Subject: Bug#827296: connman: Connman slow down the boot when no network > available > Date: Thu, 16 Jun 2016 18:23:31 +0200 > From: flor...@biree.name > To: klausenb...@hotmail.com > CC: sub...@bugs.debian.org > > Le Tue, 14 Jun 2016 20:54:15 +0200, > Kristian Klausen <klausenb...@hotmail.com> a écrit : > >> I'm not sure this is connman fault (??). >> >> This is causing by newer connman which include >> connman-wait-online.service. You should be able to fix it by >> disabling connman-wait-online.service > > This solution works, thanks! > It's still strange to have by default this big behavior > change which slow down the boot … > > > > > -- > Florian Birée > 06 52 92 15 32 > > En ces temps d'état policier, ne les laissons pas lire nos mails, > chiffrons-les ! https://emailselfdefense.fsf.org/fr/index.html
Bug#827296: connman: Connman slow down the boot when no network available
I'm not sure this is connman fault (??). This is causing by newer connman which include connman-wait-online.service. You should be able to fix it by disabling connman-wait-online.service https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ is worth reading. > Subject: Bug#827296: connman: Connman slow down the boot when no network > available > From: flor...@biree.name > To: sub...@bugs.debian.org > Date: Tue, 14 Jun 2016 19:56:08 +0200 > > Package: connman > Version: 1.32-0.1 > Severity: normal > > Dear Maintainer, > > When no network (wired or wireless) is available, systemd hang on an long > time (around 2 minutes), waiting connman to find a network before continuing > the boot. > > This is very anoying for a laptop. Some times ago (I can't remember when > and with which version of connman or systemd), already with connman and > systemd, the boot was normal even when no network was available. > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > > Kernel: Linux 4.5.0-2-686-pae (SMP w/1 CPU core) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages connman depends on: > ii dbus 1.10.8-1 > ii init-system-helpers 1.34 > ii libc6 2.22-11 > ii libdbus-1-3 1.10.8-1 > ii libglib2.0-0 2.48.1-1 > ii libgnutls30 3.4.13-1 > ii libreadline6 6.3-8+b4 > ii libxtables11 1.6.0-2 > ii lsb-base 9.20160601 > > Versions of packages connman recommends: > pn bluez > pn ofono > ii wpasupplicant 2.3-2.3 > > Versions of packages connman suggests: > pn indicator-network > > -- no debconf information >
Bug#825239: RFS: pepperflashplugin-nonfree/1.8.1+deb8u1 [RC] [NMU]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "pepperflashplugin-nonfree" * Package name: pepperflashplugin-nonfree Version : 1.8.1+deb8u1 Upstream Author : Bart Martens <ba...@debian.org> * URL : http://wiki.debian.org/PepperFlashPlayer * License : GPL3 Section : web It builds those binary packages: pepperflashplugin-nonfree - Pepper Flash Player - browser plugin To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pepperflashplugin-nonfree Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.1+deb8u1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: pepperflashplugin-nonfree (1.8.1+deb8u1) jessie; urgency=medium * Non-maintainer upload. * Update Google public key. Closes: #823005. * Remove 32 bit support. Closes: #816848. -- Kristian Klausen <klausenb...@hotmail.com> Fri, 20 May 2016 15:08:52 +0200 Regards, Kristian Klausen
Bug#824859: jessie-pu: package pepperflashplugin-nonfree/1.8.1+deb8u1
Hi Adam You definitely correct, I did the fix for 1.8.1 manual and simply forgot to change that line. Fixed debdiff diff -Nru pepperflashplugin-nonfree-1.8.1/debian/changelog pepperflashplugin-nonfree-1.8.1+deb8u1/debian/changelog --- pepperflashplugin-nonfree-1.8.1/debian/changelog 2014-12-21 11:38:47.0 +0100 +++ pepperflashplugin-nonfree-1.8.1+deb8u1/debian/changelog 2016-05-20 15:25:49.0 +0200 @@ -1,3 +1,11 @@ +pepperflashplugin-nonfree (1.8.1+deb8u1) jessie; urgency=medium + + * Non-maintainer upload. + * Update Google public key. Closes: #823005. + * Remove 32 bit support. Closes: #816848. + + -- Kristian Klausen <klausenb...@hotmail.com> Fri, 20 May 2016 15:08:52 +0200 + pepperflashplugin-nonfree (1.8.1) unstable; urgency=medium * debian/control: Pre-Depends: ca-certificates. Closes: #773629. diff -Nru pepperflashplugin-nonfree-1.8.1/debian/control pepperflashplugin-nonfree-1.8.1+deb8u1/debian/control --- pepperflashplugin-nonfree-1.8.1/debian/control 2014-12-21 11:40:47.0 +0100 +++ pepperflashplugin-nonfree-1.8.1+deb8u1/debian/control 2016-05-24 23:17:59.0 +0200 @@ -7,7 +7,7 @@ Homepage: http://wiki.debian.org/PepperFlashPlayer Package: pepperflashplugin-nonfree -Architecture: i386 amd64 +Architecture: amd64 Depends: debconf | debconf-2.0, wget, gnupg, libatk1.0-0, libcairo2, libfontconfig1, libfreetype6, libgcc1, libglib2.0-0, libgtk2.0-0 (>= 2.14), libnspr4, libnss3, libpango-1.0-0 | libpango1.0-0, libstdc++6, libx11-6, libxext6, libxt6, libcurl3-gnutls, binutils, ${misc:Depends}, ${shlibs:Depends} Pre-Depends: ca-certificates Suggests: chromium, ttf-mscorefonts-installer, ttf-dejavu, ttf-xfree86-nonfree, hal diff -Nru pepperflashplugin-nonfree-1.8.1/pubkey-google.txt pepperflashplugin-nonfree-1.8.1+deb8u1/pubkey-google.txt --- pepperflashplugin-nonfree-1.8.1/pubkey-google.txt 2013-07-07 23:30:38.0 +0200 +++ pepperflashplugin-nonfree-1.8.1+deb8u1/pubkey-google.txt 2016-05-20 15:09:27.0 +0200 @@ -1,5 +1,5 @@ -BEGIN PGP PUBLIC KEY BLOCK- -Version: GnuPG v1.4.12 (GNU/Linux) +Version: GnuPG v1.4.2.2 (GNU/Linux) mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z @@ -11,89 +11,88 @@ 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl -eW1hc3RlckBnb29nbGUuY29tPohGBBARAgAGBQJI0l69AAoJEOX7qSII6c/vXlAA -nRMVIdPPqa3pK5spqHhTm5ousadaAJ4/R1aIaCBuXZ7USVxAG4XZJSy4MohGBBAR -AgAGBQJI6REUAAoJEB/WbxUKhkqxtRMAoMPojw3H7kfP06xbTBcV6l4iL/C3AJ98 -nOh6qM4/P7WiIKmnT85zTThqL4hGBBARAgAGBQJI6lFPAAoJEIYuYz+rQ7NyBkEA -mgNkqNBIDVilTtYcmHQAY85o8IlaAJ9NjeoM2kbcm0jZF1T6s9BXSumdF4hGBBAR -AgAGBQJJDe71AAoJEPtAr6/rDx3gTqEAoLj8mkNVfhZtuZc//dUc/+CT+wy5AJ9I -GZ+DJxo1Uw88O3/JmTNY+E1UMohGBBARAgAGBQJJytn7AAoJELHZ4eeDAWJpb5QA -njQH8SI8gYJe+pOwslqnxkvqMi36AKCFJ5BT72qPwUi2yU78tL0/RFavlYhGBBAR -AgAGBQJJzsFXAAoJEPaz08bs2Ur9dK4AoIl6RPzXvTP8yfp0seh4kRC5uUQMAJ40 -K5qygoSMgEiUkSbePn/bY9Xal4hGBBARAgAGBQJJ0uWaAAoJEK2TkXqe2Mfq/RgA -njEsJepPsxEis/lDD7YuM/t85FliAJ0d0Ddbp8ifzIZOLBLvUouw+wl2k4hGBBAR -AgAGBQJLhWfpAAoJEO982nELrv7lkLcAoMMz2LXDqwm5zNvgDzfk4TK359RMAJ42 -WbSlBnHBse8opPGZxP5OGTxOCohGBBARAgAGBQJLmFHwAAoJEPbGY9YaoejMdW4A -oMBWV6GZPH7xh18Grvesqhdmt6JDAKCjSVQQj3qqVo9TfixY9wqfl6C1JohGBBAR -AgAGBQJMhzgkAAoJEI1KrrtrN/ZMWDYAnj18QFBbCKR+91iRgk9f9ZLlPBanAJ9Q -2TwtmywhpbSPTIKeHofbQAlQGohJBBARAgAJBQJI6JhfAgcAAAoJEDl7jO4+/nb3 -mvgAoMLktv7ux+CWSAYt3596ieWdmCWAAJ9jkPCZ7Y3IDDft1FpJF+B6o1gIaIhJ -BBARAgAJBQJI6JiJAgcAAAoJEFU+IjujcFDZxR8An2tmuQcxpz+G0Hi3BSH+qSLY -2UexAJsG2mT5eU64GLg4Nv/0n1IVooCd+ohJBBARAgAJBQJI6Ji/AgcAAAoJEEgY -SAfSQni5F1EAn0125ALPoZkC8lcgWCtaCqa7E+mKAKCGbXJl6Yp8xO+VzmU2Y6AI -UP1Ia4hJBBARAgAJBQJI6lluAgcAAAoJEDUGMV/UfORJRSwAmwcMo8TpMMdpolFH -nr9qbrG0OZFzAJ40G4I0ppq1JCXbgkqP/gz31S2ozYhjBBMRAgAjAhsDBgsJCAcD -AgQVAggDBBYCAwECHgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJ -Lv+XZleb6HN4zOcFAJEAniSFbuv8V5FSHxeRimHx25671az+iQEcBBABAgAGBQJG -i+tTAAoJEO703Vx2zDVi0G8H/0uf1abwRVQ6/3gB5NtwNyNDZjcglrhvrjEerrBf -W2PDNwCw2eZ7tiBIdWzv4gPCEr7U3PiuJGcPr6vVKplIGHIatNP4DySilg8WT8Rk -I5ng+qhZl1VslcOf1tXRqn+ual3DJeDiE8P4EGdMmDwHzNXJ1g4ZzJGQ0Px5fSvS -f6l+yma5/YRcEKP1AqkWbcA0aIX3yYYWhBxOpZSF0FIQEJiSU3AUkclq+nkvOHc+ -gyJWh3UMEdNmbwizYB+AZxHOTduPCJGxMVFPFHz258owhmFE4KaCuVqDg2wjvGED -fFMlY1BPrCZJv8wRIi43Z7etj08fG+r7NbKYf0+gN3+xQWiJARwEEAECAAYFAkwf -8fMACgkQytrzOKUJG1b1XAgAi4W4zCU32w9QIGpVRL5x6Zh8XaRV5PDhyYYwBHqO -wIXs6ukG2BweCN3tpLZwKJBnKsBpfMzctZu4sR7g7P2fLgwmf108XIB3lk0SPc2+ -2clVkw3FD4riTNdydwKJweVSVRDngnsShwA11UwGZd3oo2Vol3lyu6P1vw6G8vTI -68E6hBDwoEWHVGuBezJNr7mMklp3RGzL9jpI7weGseP3FNFdiWLo1xRpx0RLbQZC -k6PiK6SMb7hfeSZ6x96IHDmPrcoZOKas8nLT58JMhGdy8aI3h1jj5bT3FCWIeB3n -6j9C/YJb9Ho3/caLfverKfCnrnSFxenVP5XU1KOk79J1N4kBHAQQAQIABgUCT+xD -3wAKCRAutzB2dnteCbodB/4ga4iQQSpWXJHL6tUEhTv/HYXuAXIoKPVmp3Rbos3z -NPtDVF+COVuSzkefiero1O78
Bug#824859: jessie-pu: package pepperflashplugin-nonfree/1.8.1+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi This makes pepperflash work again on jessie, it fix rc bug #823005 and #816848. But not #818540, which isn't relevant for jessie, as jessie isn't getting APT 1.2.7. - Kristian diff -Nru pepperflashplugin-nonfree-1.8.1/debian/changelog pepperflashplugin-nonfree-1.8.1+deb8u1/debian/changelog --- pepperflashplugin-nonfree-1.8.1/debian/changelog2014-12-21 11:38:47.0 +0100 +++ pepperflashplugin-nonfree-1.8.1+deb8u1/debian/changelog 2016-05-20 15:25:49.0 +0200 @@ -1,3 +1,11 @@ +pepperflashplugin-nonfree (1.8.1+deb8u1) jessie; urgency=medium + + * Non-maintainer upload. + * Update Google public key. Closes: #823005. + * Remove 32 bit support. Closes: #816848. + + -- Kristian Klausen <klausenb...@hotmail.com> Fri, 20 May 2016 15:08:52 +0200 + pepperflashplugin-nonfree (1.8.1) unstable; urgency=medium * debian/control: Pre-Depends: ca-certificates. Closes: #773629. diff -Nru pepperflashplugin-nonfree-1.8.1/pubkey-google.txt pepperflashplugin-nonfree-1.8.1+deb8u1/pubkey-google.txt --- pepperflashplugin-nonfree-1.8.1/pubkey-google.txt 2013-07-07 23:30:38.0 +0200 +++ pepperflashplugin-nonfree-1.8.1+deb8u1/pubkey-google.txt2016-05-20 15:09:27.0 +0200 @@ -1,5 +1,5 @@ -BEGIN PGP PUBLIC KEY BLOCK- -Version: GnuPG v1.4.12 (GNU/Linux) +Version: GnuPG v1.4.2.2 (GNU/Linux) mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z @@ -11,89 +11,88 @@ 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl -eW1hc3RlckBnb29nbGUuY29tPohGBBARAgAGBQJI0l69AAoJEOX7qSII6c/vXlAA -nRMVIdPPqa3pK5spqHhTm5ousadaAJ4/R1aIaCBuXZ7USVxAG4XZJSy4MohGBBAR -AgAGBQJI6REUAAoJEB/WbxUKhkqxtRMAoMPojw3H7kfP06xbTBcV6l4iL/C3AJ98 -nOh6qM4/P7WiIKmnT85zTThqL4hGBBARAgAGBQJI6lFPAAoJEIYuYz+rQ7NyBkEA -mgNkqNBIDVilTtYcmHQAY85o8IlaAJ9NjeoM2kbcm0jZF1T6s9BXSumdF4hGBBAR -AgAGBQJJDe71AAoJEPtAr6/rDx3gTqEAoLj8mkNVfhZtuZc//dUc/+CT+wy5AJ9I -GZ+DJxo1Uw88O3/JmTNY+E1UMohGBBARAgAGBQJJytn7AAoJELHZ4eeDAWJpb5QA -njQH8SI8gYJe+pOwslqnxkvqMi36AKCFJ5BT72qPwUi2yU78tL0/RFavlYhGBBAR -AgAGBQJJzsFXAAoJEPaz08bs2Ur9dK4AoIl6RPzXvTP8yfp0seh4kRC5uUQMAJ40 -K5qygoSMgEiUkSbePn/bY9Xal4hGBBARAgAGBQJJ0uWaAAoJEK2TkXqe2Mfq/RgA -njEsJepPsxEis/lDD7YuM/t85FliAJ0d0Ddbp8ifzIZOLBLvUouw+wl2k4hGBBAR -AgAGBQJLhWfpAAoJEO982nELrv7lkLcAoMMz2LXDqwm5zNvgDzfk4TK359RMAJ42 -WbSlBnHBse8opPGZxP5OGTxOCohGBBARAgAGBQJLmFHwAAoJEPbGY9YaoejMdW4A -oMBWV6GZPH7xh18Grvesqhdmt6JDAKCjSVQQj3qqVo9TfixY9wqfl6C1JohGBBAR -AgAGBQJMhzgkAAoJEI1KrrtrN/ZMWDYAnj18QFBbCKR+91iRgk9f9ZLlPBanAJ9Q -2TwtmywhpbSPTIKeHofbQAlQGohJBBARAgAJBQJI6JhfAgcAAAoJEDl7jO4+/nb3 -mvgAoMLktv7ux+CWSAYt3596ieWdmCWAAJ9jkPCZ7Y3IDDft1FpJF+B6o1gIaIhJ -BBARAgAJBQJI6JiJAgcAAAoJEFU+IjujcFDZxR8An2tmuQcxpz+G0Hi3BSH+qSLY -2UexAJsG2mT5eU64GLg4Nv/0n1IVooCd+ohJBBARAgAJBQJI6Ji/AgcAAAoJEEgY -SAfSQni5F1EAn0125ALPoZkC8lcgWCtaCqa7E+mKAKCGbXJl6Yp8xO+VzmU2Y6AI -UP1Ia4hJBBARAgAJBQJI6lluAgcAAAoJEDUGMV/UfORJRSwAmwcMo8TpMMdpolFH -nr9qbrG0OZFzAJ40G4I0ppq1JCXbgkqP/gz31S2ozYhjBBMRAgAjAhsDBgsJCAcD -AgQVAggDBBYCAwECHgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJ -Lv+XZleb6HN4zOcFAJEAniSFbuv8V5FSHxeRimHx25671az+iQEcBBABAgAGBQJG -i+tTAAoJEO703Vx2zDVi0G8H/0uf1abwRVQ6/3gB5NtwNyNDZjcglrhvrjEerrBf -W2PDNwCw2eZ7tiBIdWzv4gPCEr7U3PiuJGcPr6vVKplIGHIatNP4DySilg8WT8Rk -I5ng+qhZl1VslcOf1tXRqn+ual3DJeDiE8P4EGdMmDwHzNXJ1g4ZzJGQ0Px5fSvS -f6l+yma5/YRcEKP1AqkWbcA0aIX3yYYWhBxOpZSF0FIQEJiSU3AUkclq+nkvOHc+ -gyJWh3UMEdNmbwizYB+AZxHOTduPCJGxMVFPFHz258owhmFE4KaCuVqDg2wjvGED -fFMlY1BPrCZJv8wRIi43Z7etj08fG+r7NbKYf0+gN3+xQWiJARwEEAECAAYFAkwf -8fMACgkQytrzOKUJG1b1XAgAi4W4zCU32w9QIGpVRL5x6Zh8XaRV5PDhyYYwBHqO -wIXs6ukG2BweCN3tpLZwKJBnKsBpfMzctZu4sR7g7P2fLgwmf108XIB3lk0SPc2+ -2clVkw3FD4riTNdydwKJweVSVRDngnsShwA11UwGZd3oo2Vol3lyu6P1vw6G8vTI -68E6hBDwoEWHVGuBezJNr7mMklp3RGzL9jpI7weGseP3FNFdiWLo1xRpx0RLbQZC -k6PiK6SMb7hfeSZ6x96IHDmPrcoZOKas8nLT58JMhGdy8aI3h1jj5bT3FCWIeB3n -6j9C/YJb9Ho3/caLfverKfCnrnSFxenVP5XU1KOk79J1N4kBHAQQAQIABgUCT+xD -3wAKCRAutzB2dnteCbodB/4ga4iQQSpWXJHL6tUEhTv/HYXuAXIoKPVmp3Rbos3z -NPtDVF+COVuSzkefiero1O78/7zwNoOTY+fZiD1WuFtI6JGl68MjV2ArzWcbKt65 -yl1fAF7JNWVIZNW160rnHj7SCZCkB32i5DOXOZkIZalsM4IsTUmXAoc+M3+Nv6tQ -spWpT5RQVt8lp6DUUXDDl1ykSO6Rz2OEZjS6xAMbE86FxpNlblh+qELwzzkeoU5x -bM2dRAYFKFAQ4N2zvq35ovbPiebtjqHrPOYlmyzgvcSWlvB0qiKLxHbSaPgwlloq -2RnIo6gbD8LFfmoIk3H5Rxvl8SJh41POYjHiKzCS6XuqiQEcBBABAgAGBQJQtg1x -AAoJEHcWd0TJ6OQomb4H/0ujiHzxWF+0KCOhe4A1ermVAxuGtkQ1w8w9YTTil5Lk -CAPUvjxNWExZ44XCm08s9Bw5HbuJIwSp2Z3ixIv0ZkfVj1QUogcgffeoCcgPiFzb -JEPV5JrIIJG27A+LVACo6DQPkW6eHvPqknC6NfBx7xS72cvLNUiQyxeH5VU49KH9 -43vZaCIwBmqYfA0KcEwcbCGYrTFiVE5ayUVNVj+IRrjykWBg1/bPUCs+dGHEDUIC -tDiixAF6LAoAiBQAyvRHBk8k8toCE6DA5tFRkuxtZXpuluNoYoURrtvRAorNUEgU -XbAQEluY2plZxdNl3A4imx8DXegw7QNXIIRT/N17ko6JAhwEEAECAAYFAk
Bug#824706: RM: pepperflashplugin-nonfree [i386] -- RoQA; ANAIS
Package: ftp.debian.org Severity: normal Hello I did a NMU package of pepperflashplugin-nonfree which Gianfranco Costamagna sponsored. Among the 3 RC bugs I fixed, I fixed #816848 by dropping i386. As Google has dropped 32 bit Google Chrome on Linux, we can't provide a 32 bit pepperflash any longer. So if you could please remove i386 from unstable. I'm not aware of any reverse dependencies. - Kristian
Bug#818540: fix for 818540 never made it into Debian?
Hi Dan Google has dropped 32 bit support for Chrome on Linux See bug 816848 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816848), I'm not sure why the i386 package is still present. - Kristian > Subject: Bug#818540: fix for 818540 never made it into Debian? > From: jida...@jidanni.org > To: klausenb...@hotmail.com > CC: 818...@bugs.debian.org > Date: Thu, 19 May 2016 04:20:33 +0800 > > https://packages.debian.org/search?keywords=pepperflashplugin-nonfree > shows you only updated non - i386 :-( >
Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]
Hi again G :) > 1) why 1.8.3+nmu1 and not 1.8.2+nmu1? Isn't I'm supposed to raise the version number? or is "+nmu1" enough? > 2) why UNRELEASED? please set unstable I didn't noticed it. > "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug > #818540? It part of the fix, but not needed to fix #818540 (as I understand). > (attaching the debdiff between debian and ubuntu, I'm not talking about > fields like changelog entries No file attached here? You talking about this file correct? https://patches.ubuntu.com/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.2ubuntu1.patch I did as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818540#39 suggested, do you disagree with that solution? Is the original solution preferred? Just pushed to mentors. - Kristian > Date: Fri, 13 May 2016 19:41:25 + > From: locutusofb...@debian.org > To: klausenb...@hotmail.com; ba...@debian.org; 824...@bugs.debian.org > Subject: Re: Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU] > > control: owner -1 ! > control: tags -1 moreinfo > > > Hi, some questions about versioning and changelog: > > 1) why 1.8.3+nmu1 and not 1.8.2+nmu1? > 2) why UNRELEASED? please set unstable > > "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug > #818540? > > the other stuff LGTM, I hope to sponsor it soon :) > > BTW did you see the ubuntu diff? > you might want to take some bits > > (attaching the debdiff between debian and ubuntu, I'm not talking about > fields like changelog entries > and maintainer field, more about the update script) > > thanks! > > G. > > > Il Venerdì 13 Maggio 2016 15:39, Kristian Klausen <klausenb...@hotmail.com> > ha scritto: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "pepperflashplugin-nonfree": > > * Package name : pepperflashplugin-nonfree > Version : 1.8.3+nmu1 > Upstream Author : Bart Martens <ba...@debian.org> > * URL : http://wiki.debian.org/PepperFlashPlayer > * License : GPL3 > Section : Browser plugin > > It builds those binary packages: > > pepperflashplugin-nonfree > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/pepperflashplugin-nonfree > > > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc > > > Changes since the last upload: > > pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium > > * Non-maintainer upload. > * Update Google public key. Closes: #823005. > * Remove 32 bit support. Closes: #816848. > * Don't treat `apt-get update` warnings as errors. Closes: #818540. > * Validate deb file with sha256sum. > > -- Kristian Klausen <klausenb...@hotmail.com> Fri, 13 May 2016 14:44:52 +0200 > > > Regards, > Kristian Klausen
Bug#824186: RFS: pepperflashplugin-nonfree/1.8.3+nmu1 [RC] [NMU]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "pepperflashplugin-nonfree": * Package name : pepperflashplugin-nonfree Version : 1.8.3+nmu1 Upstream Author : Bart Martens <ba...@debian.org> * URL : http://wiki.debian.org/PepperFlashPlayer * License : GPL3 Section : Browser plugin It builds those binary packages: pepperflashplugin-nonfree To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pepperflashplugin-nonfree Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/contrib/p/pepperflashplugin-nonfree/pepperflashplugin-nonfree_1.8.3+nmu1.dsc Changes since the last upload: pepperflashplugin-nonfree (1.8.3+nmu1) UNRELEASED; urgency=medium * Non-maintainer upload. * Update Google public key. Closes: #823005. * Remove 32 bit support. Closes: #816848. * Don't treat `apt-get update` warnings as errors. Closes: #818540. * Validate deb file with sha256sum. -- Kristian Klausen <klausenb...@hotmail.com> Fri, 13 May 2016 14:44:52 +0200 Regards, Kristian Klausen
Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages
Arjen could you try removing: PATH="/root/usr/bin:/root/usr/sbin:/root/bin:/root/sbin:/usr/bin:/usr/sbin:/bin:/sbin" export PATH from /lib/live/boot/9990-aaa-fixme.sh and see if it works? - Kristian > Subject: Bug#823069: live-boot-initramfs-tools: Kernel panic while booting > live with Debian stretch busybox/live packages > From: b...@decadent.org.uk > To: 823...@bugs.debian.org > CC: util-li...@packages.debian.org > Date: Mon, 9 May 2016 17:55:55 +0100 > > Control: clone -1 -2 > Control: reassign -2 util-linux > Control: severity -2 important > Control: affects -2 live-boot-initramfs-tools > Control: retitle -1 live-boot-initramfs-tools: wrongly adds directories in > /root to the PATH > Control: retitle -2 util-linux: 'mount -o move' does not work with virtual > filesystems > > On Sat, 30 Apr 2016 16:07:25 +0200 Arjen Balfoort> wrote: > [...] >> mount: /dev is write-protected, mounting read-only >> mount: /dev is not a block device >> >> The error is caused in >> /usr/share/initramfs-tools/scripts/init-bottom/udev >> Line: mount -n -o move /dev ${rootmnt}/dev > [...] > > This is a side-effect of my change in busybox 1.22.0-19, but I don't > think that change was wrong. > > live-boot-initramfs-tools adds directories under /root to $PATH, which > was formerly harmelss but now actually does result in some commands > being loaded from there. You must stop doing this; it is not > supportable and I will not support it. > > In particular, this mount command now invokes util-linux's mount. That > refuses to perform a move if the source filesystem was not mounted from > a block device. There is no good reason for this and obviously it > works with busybox and klibc's implementations of mount. > > Ben. > > -- > Ben Hutchings > If you seem to know what you are doing, you'll be given more to do.
Bug#823116: Rotation not working on Skylake with TearFree option
Subject: Rotation not working on skylake with TearFree option Package: xserver-xorg-video-intel Version: 2:2.99.917+git20160325-1 Severity: normal Tags: upstream Dear Maintainer, Rotation isn't working on Skylake with the TearFree option. I get the following error: xrandr --output "HDMI2" --rotate "left" xrandr: Configure crtc 0 failed crtc 0: disable screen 0: 1080x1920 285x506 mm 96.25dpi crtc 0:1920x1080 60.00 +0+0 "HDMI2" crtc 0: disable crtc 1: disable crtc 2: disable crtc 3: disable screen 0: revert crtc 0: revert crtc 1: revert crtc 2: revert crtc 3: revertThe issue seems only to affect left/right rotation, not normal/inverted. I got in contact with a Intel dev on irc, which was able to reproduce it and it has now been fixed upstream. Commit https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=c62177ec321e009a1abcdc969dd808fb37136013 specifically he told me. I haven't tested yet, that it fix the bug, but I will do as soon I get access to the hardware again. - Kristian
Bug#822846: Add option to mount /lib/live/mount/medium read-write
Package: live-boot Version: 1:20151213 Severity: normal Tags: upstream Dear Maintainer, Currently /lib/live/mount/medium is mounted with ro,noatime, which isn't preferable for all use-case. For my use-case it need to be mounted rw, so I can replace kernel, initrd and squashfs with my update script which run as a cronjob in the image. Then we get the next problem, when we mount it rw, we need to fsck it at least once in a while. We can't use the normal initramfs fsck, as it only add fsck. for filesystems listed in /etc/fstab, at least I don't think we can do that. Reading on Arch Linux wiki (https://wiki.archlinux.org/index.php/fsck) it seems like fsck can do it. We just need to write /lib/live/mount/medium to /etc/fstab (with pass 2 <=), I think we can do that in the fsck hook with some simple greb. cat /etc/mtab | awk '{$6=2; print}' >> /etc/fstab I have created my own branch in live-boot (kristian), and added a "live-media-mount-opts" option. I think it work, but need to test it. If someone could help review it, I would appreciate that! - Kristian
Bug#822685: FW: example auto/config exit code is always 0, even on error.
Subject: example/auto/config always exit with code 0, even on error. Package: live-build Version: 1:20151213 Severity: normal Tags: upstream Dear Maintainer, The included example auto/config currently always exit with exit code 0 (success). Even on error, this is because it use a pipe (to pipe it to a log file) lb build noauto "${@}" 2>&1 | tee build.log I don't think it can be fixed without changing shell to something like bash. - Kristian
Bug#822684: example auto/config exit code is always 0, even on error.
Subject: example/auto/config always exit with code 0, even on error. Package: live-build Version: git head Severity: normal Tags: upstream Dear Maintainer, The included example auto/config currently always exit with exit code 0 (success). Even on error, this is because it use a pipe (to pipe it to a log file) lb build noauto "${@}" 2>&1 | tee build.log I don't think it can be fixed without changing shell to something like bash. - Kristian
Bug#801712: Mirror patch fix
Fixed a typo (FILESYTEM instant of FILESYSTEM), also changed text above ext2fs_default_journal_size from "stolen from" to "adapted from". - Kristian losetup.sh.patch Description: Binary data
Bug#801712: Updated patch
Attached is a updated patch some improvement. Most important we dropped the "loop" and made the code more meaningful. Thanks to adrian15 for the help! losetup.sh.patch Description: Binary data
Bug#801712: Patch
Attached is a updated tested patch. The ext2fs_default_journal_size logic is stolen from lib/ext2fs/mkjournal.c, where the input and output is in blocks. Generally the default block size is 4096 (/etc/mke2fs.conf) so I just multiplied the numbers with 4096. I call ext2fs_default_journal_size twice, to ensure that JOURNAL_SIZE is correct, as the "final size" could require a bigger journal size. df report the "overhead" as: /dev/loop2p1 571204 547844 11424 98% /mnt - Kristian Klausen
Bug#801712: Patch
Forgot to attach patch. losetup.sh.patch Description: Binary data
Bug#801712: hdd-size=auto not working with EXT3/EXT4
Subject: hdd-size=auto not working with EXT3/EXT4 Package: live-build Version: 5.0~a8-1 Severity: normal Tags: upstream, patch Dear Maintainer, At the moment I manually set hdd-size to around 50 megabyte more than my live image require. As the Calculate_partition_size does not take into account, that ext3/ext4 has a journal. I have attached a patch, it not "perfect" or tested, but should give you a idea about how to fix it. Some useful links: http://lists.openwall.net/linux-ext4/2010/01/11/3 (how the journal size is calculated) http://linux.die.net/man/8/mkfs.ext4 (usage type, default block size) ftp://hgdownload.cse.ucsc.edu/cbsebackups.old/encode-01/etc/mke2fs.conf (mke2fs.conf) Regards Kristian Klausen functions_losetup.sh.patch Description: Binary data
Bug#789300: cache.sh if same device check don't work with symlink
Subject: Support building image without root. Package: live-build Version: 5.0~a8-1 Severity: normal Tags: upstream, patch Dear Maintainer, At the momemt I build my live build images inside a privileged docker container with Gitlab CI Multirunner. I have attached a volume (/cache), and before I start lb build I symlink it. The problem is cache.sh think it the same device, so it try to hard link copy, which of course don't work. ( Invalid cross-device link). The problem seems to be that stat without a last slash, don't follow the symlink, but only check there the link is stored. See for you self. [kristian@arch-hp-laptop ~]$ mkdir test [kristian@arch-hp-laptop ~]$ stat --printf '%d\n' test 2051 [kristian@arch-hp-laptop ~]$ ln -s /tmp symlink [kristian@arch-hp-laptop ~]$ stat --printf '%d\n' /tmp 33 [kristian@arch-hp-laptop ~]$ stat --printf '%d\n' symlink 2051 [kristian@arch-hp-laptop ~]$ stat --printf '%d\n' symlink/ 33 Patch attached. Regards Kristian Klausen -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages live-build depends on: ii cdebootstrap 0.6.4 ii debootstrap 1.0.67 Versions of packages live-build recommends: ii cpio2.11+dfsg-4.1 ii live-boot-doc 4.0.2-1 ii live-config-doc 4.0.4-1 ii live-manual-html [live-manual] 1:4.0.1-1 live-build suggests no packages. -- no debconf information symlink.patch Description: Binary data
Bug#788764: live-build: Support building image without root.
Subject: live-build: Support building image without root. Package: live-build Version: 5.0~a8-1 Severity: wishlist Tags: upstream Dear Maintainer, At the momemt there seems to be no way to build a live image without root. In our environment we start lb build everytime a commit is pushed to our Git repo. But as live build reguire root. Everyone with access to the Git repo in practice have root access on the build server, and can install malicious software. Trying running lb build with fakeroot and fakechroot result in: lb config . /etc/fakechroot/debootstrap.env fakeroot fakechroot lb build | tee fake.log fake.log uploaded here: http://sprunge.us/eWUZ debootstrap.log uploaded here: http://sprunge.us/jdfe Regards Kristian Klausen -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages live-build depends on: ii cdebootstrap 0.6.4 ii debootstrap 1.0.67 Versions of packages live-build recommends: ii cpio2.11+dfsg-4.1 ii live-boot-doc 4.0.2-1 ii live-config-doc 4.0.4-1 ii live-manual-html [live-manual] 1:4.0.1-1 live-build suggests no packages. -- no debconf information