Re: [E-devel] EFL 1.19.0-beta3 (from git) package for Debian Experimental
On Thu, 23 Mar 2017 09:07:40 -0400 Ross Vandegrift said: > On Thu, Mar 23, 2017 at 07:04:14PM +0900, Carsten Haitzler wrote: > > On Thu, 23 Mar 2017 00:21:38 -0700 Jose R R said: > > > > > you dont have to disable tests... you actually HAVE to enable them with > > --with-tests=regular or --with-tests=coverage ... AND you then also have to > > do "make check" to compile AND run them... it requires effort to enable > > them and run them. > > He's attempting to use the packaging from Debian experimental, which > enables & automatically runs make check. then remove those bits. :) make check does require a fairly working "user environment" - eg a login session to fully run as it tests things that are dependant on that. it all passes for me except network which is due to a firewall... (well when i ran it yesterday) > > > override_dh_auto_configure: > > > dh_auto_configure --verbose -- \ > > > --disable-rpath \ > > > --disable-silent-rules \ > > > --enable-doc \ > > > --with-profile=dev \ > > > --with-tests=regular \ > > > --with-crypto=gnutls \ > > > --disable-tslib \ > > > --enable-liblz4 \ > > > --enable-xinput22 \ > > > --enable-image-loader-webp \ > > > --enable-harfbuzz \ > > > --enable-systemd \ > > > --enable-static \ > > > --enable-image-loader-webp \ > > > --with-generic_vlc \ > > > --enable-fb \ > > > $(arch_flags) > > > > > > That's how DEBs in reference snapshot were generated *finally*. > > > > no wayland i see. :( also no ibus input method support either. > > Last I heard, using wayland was only recommended if you followed git. > If that's no longer true, it could be enabled in the next release. wayland is not perfect right now... but its actually pretty good. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com
Work-needing packages report for Mar 24, 2017
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1053 (new: 3) Total number of packages offered up for adoption: 165 (new: 0) Total number of packages requested help for: 42 (new: 0) Please refer to http://www.debian.org/devel/wnpp/ for more information. The following packages have been orphaned: libterm-readline-zoid-perl (#858394), orphaned 2 days ago Description: Pure Perl implementation of Readline libraries Reverse Depends: libtm-perl Installations reported by Popcon: 32 Bug Report URL: http://bugs.debian.org/858394 odot (#858396), orphaned 2 days ago Description: task list manager written in Gtk2-Perl Installations reported by Popcon: 16 Bug Report URL: http://bugs.debian.org/858396 perlpanel (#858395), orphaned 2 days ago Description: lean menu and launcher panel written in Perl and Gtk2 Installations reported by Popcon: 69 Bug Report URL: http://bugs.debian.org/858395 1050 older packages have been omitted from this listing, see http://www.debian.org/devel/wnpp/orphaned for a complete list. No new packages have been given up for adoption, but a total of 165 packages are awaiting adoption. See http://www.debian.org/devel/wnpp/rfa_bypackage for a complete list. For the following packages help is requested: autopkgtest (#846328), requested 113 days ago Description: automatic as-installed testing for Debian packages Reverse Depends: debci-worker openstack-pkg-tools Installations reported by Popcon: 767 Bug Report URL: http://bugs.debian.org/846328 balsa (#642906), requested 2006 days ago Description: An e-mail client for GNOME Reverse Depends: balsa-dbg Installations reported by Popcon: 690 Bug Report URL: http://bugs.debian.org/642906 busybox (#854181), requested 47 days ago Description: Tiny utilities for small and embedded systems Reverse Depends: bootcd busybox-syslogd dropbear-initramfs live-boot-initramfs-tools open-infrastructure-system-boot udhcpc udhcpd wicd-daemon zfs-initramfs Installations reported by Popcon: 195523 Bug Report URL: http://bugs.debian.org/854181 cups (#532097), requested 2847 days ago Description: Common UNIX Printing System Reverse Depends: bluez-cups boomaga chromium cinnamon-settings-daemon cloudprint cups cups-backend-bjnp cups-browsed cups-bsd cups-client (66 more omitted) Installations reported by Popcon: 178864 Bug Report URL: http://bugs.debian.org/532097 cyrus-sasl2 (#799864), requested 547 days ago Description: authentication abstraction library Reverse Depends: 389-ds-base 389-ds-base-libs 389-dsgw adcli autofs-ldap cairo-dock-mail-plug-in claws-mail claws-mail-acpi-notifier claws-mail-address-keeper claws-mail-archiver-plugin (127 more omitted) Installations reported by Popcon: 196772 Bug Report URL: http://bugs.debian.org/799864 dee (#831388), requested 251 days ago Description: model to synchronize mutiple instances over DBus Reverse Depends: dee-tools gir1.2-dee-1.0 libdee-1.0-4-dbg libdee-dev zeitgeist-core Installations reported by Popcon: 65052 Bug Report URL: http://bugs.debian.org/831388 developers-reference (#759995), requested 936 days ago Description: guidelines and information for Debian developers Installations reported by Popcon: 19876 Bug Report URL: http://bugs.debian.org/759995 devscripts (#800413), requested 541 days ago Description: scripts to make the life of a Debian Package maintainer easier Reverse Depends: apt-build apt-listdifferences aptfs arriero bzr-builddeb customdeb debci debian-builder debmake debpear (25 more omitted) Installations reported by Popcon: 13000 Bug Report URL: http://bugs.debian.org/800413 ejabberd (#767874), requested 871 days ago Description: distributed, fault-tolerant Jabber/XMPP server written in Erlang Reverse Depends: ejabberd-contrib ejabberd-mod-cron ejabberd-mod-log-chat ejabberd-mod-logsession ejabberd-mod-logxml ejabberd-mod-message-log ejabberd-mod-muc-log-http ejabberd-mod-post-log ejabberd-mod-pottymouth ejabberd-mod-rest (4 more omitted) Installations reported by Popcon: 664 Bug Report URL: http://bugs.debian.org/767874 fbcat (#565156), requested 2626 days ago Description: framebuffer grabber Installations reported by Popcon: 205 Bug Report URL: http://bugs.debian.org/565156 fgetty (#823061), requested 327 days ago Description: console-
Re: Graphical package installers & debconf (was: What's a safe way to have extensions in chromium in Debian?)
2017-03-23 22:04 GMT+01:00 Sean Whitton : > Hello Jeremy, > > On Thu, Mar 23, 2017 at 07:14:35AM -0400, Jeremy Bicha wrote: >> It is also useless for someone who will install Chromium from the >> Software app (gnome-software) included in 'gnome-core' since the >> Software app does not display debconf prompts. > > Do you know if this is a missing feature or a deliberate choice? This is likely a missing feature, since PackageKit does support Debconf prompts and GNOME PackageKit does as well. Debconf stuff is kind of hacked into it though (but given the architecture of Debconf and PackageKit, there is no better way to do this). So, I guess someone would need to implement proper Debconf support in GNOME Software. Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/
Graphical package installers & debconf (was: What's a safe way to have extensions in chromium in Debian?)
Hello Jeremy, On Thu, Mar 23, 2017 at 07:14:35AM -0400, Jeremy Bicha wrote: > It is also useless for someone who will install Chromium from the > Software app (gnome-software) included in 'gnome-core' since the > Software app does not display debconf prompts. Do you know if this is a missing feature or a deliberate choice? -- Sean Whitton signature.asc Description: PGP signature
Bug#858566: TP: node-querystring -- Node's querystring module for all engines.
Package: wnpp Severity: wishlist Owner: ro...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-querystring Version : 0.2.0 Upstream Author : Irakli Gozalishvili * URL : https://github.com/Gozala/querystring * License : Expat Programming Lang: JavaScript Description : Node's querystring module for all engines. The querystring module provides utilities for parsing and formatting URL query strings. . On the World Wide Web, a query string is the part of a uniform resource locator (URL) containing data that does not fit conveniently into a hierarchical path structure. The query string commonly includes fields added to a base URL by a Web browser or other client application, for example as part of an HTML form. . node-querystring allow one to encode, decode, parse and stringify query string . Node.js is an event-based server-side JavaScript engine. This is needed for browserify and some of my rdep of my packjages
Re: Depends/Recommends from libraries
Russ Allbery writes ("Re: Depends/Recommends from libraries"):
> It still feels like needless complexity to me,
Here is an example I just found.
Try, in a fresh stretch chroot
apt-get --no-install-recommends install libgtkspell-dev
Which you might reasonably do because you were building something
which linked against libgtk-spell. Or because you installed some
portmanteau package like ocaml-libs.
-dev libraries are typically installed because you want to build
something, not necessarily because you wanted to _use_ the features of
the runtime library.
The list that comes out is humungous and contains many things that you
probably didn't want.
aspell ? Well, at least the connection is clear, although it's
clearly wrong to get it.
fontconfig ? Probably pulled in pointlessly by one of the other
librararies.
dictionaries-common ? That's a waste of a download.
emacsen-common ? Wow.
libgtk2.0-dev, which lots of things obviously build-depend on, pulls
in fontconfig and gnome-icon-theme (a 10Mby download). I can't
believe you need gnome-icon-theme installed to compile gtk2 programs.
Ian.
Bug#858563: efl: invoking debian/rules directly does not work as intended
Source: efl Version: 1.8.6-2.5 On Thu, 23 Mar 2017 at 08:55:10 -0400, Ross Vandegrift wrote: > You only need [to pass --enable-fb explicitly] because you're calling > debian/rules directly. If you use dpkg-buildpackage then > DEB_HOST_ARCH_OS will be set, and the Makefile will automatically > add --enable-fb. This is *technically* a bug in the packaging: invoking debian/rules directly is *meant* to work. efl's debian/rules should either `include /usr/share/dpkg/default.mk` (or at least architecture.mk), or arrange for DEB_HOST_ARCH_OS to be set correctly by invoking dpkg-buildflags itself. (But I'm sure lots of other packages have the same bug: no infrastructure in Debian systematically checks for it, and for a user of Debian packages, building with dpkg-buildpackage or debuild is always preferred.) I'm filing this as a normal-severity bug, because although it's a Policy violation, it isn't a serious one IMO. Please adjust the severity up or down according to the maintainer's opinion. S
Bug#858559: ITP: node-argv -- CLI Argument Parser
Package: wnpp Severity: wishlist Owner: ro...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-argv Version : 0.0.2 Upstream Author : Corey Hart * URL : https://github.com/codenothing/argv * License : MIT Programming Lang: JavaScript Description : Node based command line argument parser node-argv is a nodejs module that does command line argument parsing. node-argv implement a strict argument parser, which means all options must be defined before parsing starts. This argument parser allow to use a modular structure for your options parsing. . Node.js is an event-based server-side JavaScript engine.
Re: [E-devel] EFL 1.19.0-beta3 (from git) package for Debian Experimental
On Thu, Mar 23, 2017 at 07:04:14PM +0900, Carsten Haitzler wrote: > On Thu, 23 Mar 2017 00:21:38 -0700 Jose R R said: > > > you dont have to disable tests... you actually HAVE to enable them with > --with-tests=regular or --with-tests=coverage ... AND you then also have to do > "make check" to compile AND run them... it requires effort to enable them and > run them. He's attempting to use the packaging from Debian experimental, which enables & automatically runs make check. > > override_dh_auto_configure: > > dh_auto_configure --verbose -- \ > > --disable-rpath \ > > --disable-silent-rules \ > > --enable-doc \ > > --with-profile=dev \ > > --with-tests=regular \ > > --with-crypto=gnutls \ > > --disable-tslib \ > > --enable-liblz4 \ > > --enable-xinput22 \ > > --enable-image-loader-webp \ > > --enable-harfbuzz \ > > --enable-systemd \ > > --enable-static \ > > --enable-image-loader-webp \ > > --with-generic_vlc \ > > --enable-fb \ > > $(arch_flags) > > > > That's how DEBs in reference snapshot were generated *finally*. > > no wayland i see. :( also no ibus input method support either. Last I heard, using wayland was only recommended if you followed git. If that's no longer true, it could be enabled in the next release. Ross
Re: [E-devel] EFL 1.19.0-beta3 (from git) package for Debian Experimental
On Wed, Mar 22, 2017 at 04:50:38AM -0700, Jose R R wrote: > First I modify debian/rules, option: --enable-fb > - > [...] > ifeq (linux,$(DEB_HOST_ARCH_OS)) > arch_flags += --enable-fb<=## Directive is overlooked. DEB > build fails *because* it's missing > [...] > override_dh_auto_configure: > dh_auto_configure --verbose -- \ > [...] > --enable-fb \ <=## Added explicitly here, satisfies dh_install > $(arch_flags) > [...] > You only need this change because you're calling debian/rules directly. If you use dpkg-buildpackage then DEB_HOST_ARCH_OS will be set, and the Makefile will automatically add --enable-fb. Ross
Re: What's a safe way to have extensions in chromium in Debian?
Hi, On Thu, Mar 23, 2017 at 12:03:00PM +0100, Martin Bagge / brother wrote: > On 2017-03-23 07:50, Sebastian Reichel wrote: > > I wonder if we could just add a boolean debconf question for this. > > It could setup /etc/chromium.d/remote-extensions based on the answer > > and provide some (dis)advantages info for selecting either option. > > Probably hard to do that without violating the importancy level of a > debconf message. > > "Copyright messages do not count as vitally important (they belong in > /usr/share/doc/package/copyright); neither do instructions on how to use > a program (these should be in on-line documentation, where all the users > can see them)." > - 3.9.1 in policy My proposal is not an instruction how to use the program, but an option changing the usability VS security aspect of the program. The information is just there, so that the user knows what his choice implies. I wasn't aware, that the graphical software installation solutions do not ask debconf questions, though. -- Sebastian signature.asc Description: PGP signature
Re: What's a safe way to have extensions in chromium in Debian?
On Thu, Mar 23, 2017 at 7:03 AM, Martin Bagge / brother wrote: > Probably hard to do that without violating the importancy level of a > debconf message. It is also useless for someone who will install Chromium from the Software app (gnome-software) included in 'gnome-core' since the Software app does not display debconf prompts. Jeremy Bicha
Re: What's a safe way to have extensions in chromium in Debian?
On 2017-03-23 07:50, Sebastian Reichel wrote: > I wonder if we could just add a boolean debconf question for this. > It could setup /etc/chromium.d/remote-extensions based on the answer > and provide some (dis)advantages info for selecting either option. Probably hard to do that without violating the importancy level of a debconf message. "Copyright messages do not count as vitally important (they belong in /usr/share/doc/package/copyright); neither do instructions on how to use a program (these should be in on-line documentation, where all the users can see them)." - 3.9.1 in policy -- brother http://sis.bthstudent.se
Re: [E-devel] EFL 1.19.0-beta3 (from git) package for Debian Experimental
On Thu, 23 Mar 2017 00:21:38 -0700 Jose R R said: > On Wed, Mar 22, 2017 at 10:56 PM, Carsten Haitzler > wrote: > > On Wed, 22 Mar 2017 04:50:38 -0700 Jose R R said: > > > >> On Tue, Mar 21, 2017 at 4:55 PM, Ross Vandegrift wrote: > >> [...] > >> > Oh I see - I misunderstood your previous message and thought you were > >> > targeting sid. You need to backport + rebuild for jessie. IIRC, the > >> > only change I needed was to remove the auto dbgsym stuff. > >> > > >> > [snip] > >> >> FAIL: tests/evas/evas_suite > >> >> === > >> >> > >> >> /mnt/caxtolli/usr/src/build/enlightenment-debian/sid-omeyi/efl-1.18.4/src/tests/evas/.libs/evas_suite: > >> >> symbol lookup > >> >> error: > >> >> /mnt/caxtolli/usr/src/build/enlightenment-debian/sid-omeyi/efl-1.18.4/src/lib/efl/.libs/libefl.so.1: > >> >> undefined symbol: _eo_call_end FAIL tests/evas/evas_suite (exit status: > >> >> 127) > >> > > >> > This seems suspicious - the linker can't find a symbol in libefl.so. > >> > Are you building with some other patches? > >> Nope. > >> > >> > > >> > [snip] > >> >> FAIL: tests/eio/eio_suite > >> >> = > >> >> > >> >> Running suite(s): Eio > >> > [snip] > >> >> 98%: Checks: 51, Failures: 1, Errors: 0 > >> >> tests/eio/eio_test_manager.c:68:F:Eio > >> >> Job:efl_io_manager_test_ls_funcs:0: Failure '(*number_of_listed_files) ! > >> >> = test_count' occurred > >> > > >> > I don't recall seeing this test fail before, sorry. > >> > > >> Ok, the above issues are from EFL 1.19.0 beta3 effort on a Debian Sid > >> (Unstable) on Reiser4 root fs. > >> > >> An EFL 1.18.4 build on Debian-Reiser4 root fs Jessie (Stable), fed > >> heavily from official jessie-backports repository, does succeed in > >> building the corresponding EFL 1.18.4 DEBs -- as long as I do three > >> modifications to relevant debian packaging. > >> > >> First I modify debian/rules, option: --enable-fb > >> - > >> [...] > >> ifeq (linux,$(DEB_HOST_ARCH_OS)) > >> arch_flags += --enable-fb<=## Directive is overlooked. DEB > >> build fails *because* it's missing > >> [...] > >> override_dh_auto_configure: > >> dh_auto_configure --verbose -- \ > >> [...] > >> --enable-fb \ <=## Added explicitly here, satisfies > >> dh_install $(arch_flags) > >> [...] > >> > > > > err so --enable-fb makes an eio test work? and makes the evas test suite > > work (which doesn't use fb access at all)... THAT i don't get... > Hold on :) ... > Assuming I disable *all* tests, debian/rules *should* generate *all* > EFL DEB packages --but it does not, log shows hint: you dont have to disable tests... you actually HAVE to enable them with --with-tests=regular or --with-tests=coverage ... AND you then also have to do "make check" to compile AND run them... it requires effort to enable them and run them. > [...] > make[2]: Leaving directory > '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' > make[1]: Leaving directory > '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' >debian/rules override_dh_install > make[1]: Entering directory > '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' > dh_install --list-missing > dh_install: Cannot find (any matches for) > "debian/tmp/usr/lib/*/evas/modules/engines/fb/*/module.so" (tried in > "." and "debian/tmp") > dh_install: libevas1-engines-fb missing files: > debian/tmp/usr/lib/*/evas/modules/engines/fb/*/module.so > dh_install: Cannot find (any matches for) > "debian/tmp/usr/lib/*/libecore_fb.so.*" (tried in "." and > "debian/tmp") > dh_install: libecore-fb1 missing files: debian/tmp/usr/lib/*/libecore_fb.so.* > dh_install: usr/bin/ecore_evas_convert exists in debian/tmp but is not > installed to anywhere > [...] that's your packaging issue there... your packages expect files you don't have (eg the fb support libs and modules) ... and they fail to package up the binary there. you are the packager here. you should know what these mean... :) fyi: 4:59PM ~/C/efl > make DESTDIR=/tmp/BLAH install ... 5:02PM ~/C/efl > ls /tmp/BLAH/usr/local/lib/libecore_fb* 4.0K /tmp/BLAH/usr/local/lib/libecore_fb.la 0 /tmp/BLAH/usr/local/lib/libecore_fb.so@ 0 /tmp/BLAH/usr/local/lib/libecore_fb.so.1@ 128K /tmp/BLAH/usr/local/lib/libecore_fb.so.1.19.0* 5:03PM ~/C/efl > ls /tmp/BLAH/usr/local/lib/evas/modules/engines/fb/v-1.19 total 192K 4.0K module.la* 188K module.so* 5:03PM ~/C/efl > ls /tmp/BLAH/usr/local/lib/ecore_evas/engines/fb/v-1.19 total 88K 4.0K module.la* 84K module.so* all there as expected in the destdir :) thats what packaging tools use - they use DESTDIR to specify "debian/tmp" athe destination dir for
Bug#858544: ITP: fpm -- build packages for multiple platforms (deb, rpm, etc) with great ease and sanity
Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)"
* Package name: fpm
Version : 1.8.1
Upstream Author : Copyright (c) 2011-2016 Jordan Sissel and contributors.
* URL : https://github.com/jordansissel/fpm
* License : Expat
Programming Lang: ruby
Description : build packages for multiple platforms (deb, rpm, etc) with
great ease and sanity
The goal of fpm is to make it easy and quick to build packages such as
rpms, debs, OSX packages, etc.
.
fpm, as a project, exists with the following principles in mind:
.
* If fpm is not helping you make packages easily, then there is a bug in
fpm.
* If you are having a bad time with fpm, then there is a bug in fpm.
* If the documentation is confusing, then this is a bug in fpm.
--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
Re: [E-devel] EFL 1.19.0-beta3 (from git) package for Debian Experimental
Hello, I just saw your initial log and the one in the mail. Is it possible that you have some other installed library that gets mixed into your build? Or some lower binary / library is currupted? There are a few things that indicate it: - In the first log the linker cannot find _efl_object_init_count, which is part of libeo.so in any case, if you are running latest git, so there is either way a broken compiler that does not make the symbol public, or a wrong libeo.so gets linked into. simular to _eo_call_end, there is no sane reason why this symbol should just disappear - Something is driving dbus mad, i have never seen those errors... And for taking a closer look and seeing which .so's are opened, maybe run the evas_suite by hand and create a strace output from it, so we can see which files are opened. So we know, thats a compiler fault or something else is wrong. Greetings bu5hm4n On Thu, Mar 23, 2017 at 12:21:38AM -0700, Jose R R wrote: > On Wed, Mar 22, 2017 at 10:56 PM, Carsten Haitzler > wrote: > > On Wed, 22 Mar 2017 04:50:38 -0700 Jose R R said: > > > >> On Tue, Mar 21, 2017 at 4:55 PM, Ross Vandegrift wrote: > >> [...] > >> > Oh I see - I misunderstood your previous message and thought you were > >> > targeting sid. You need to backport + rebuild for jessie. IIRC, the > >> > only change I needed was to remove the auto dbgsym stuff. > >> > > >> > [snip] > >> >> FAIL: tests/evas/evas_suite > >> >> === > >> >> > >> >> /mnt/caxtolli/usr/src/build/enlightenment-debian/sid-omeyi/efl-1.18.4/src/tests/evas/.libs/evas_suite: > >> >> symbol lookup > >> >> error: > >> >> /mnt/caxtolli/usr/src/build/enlightenment-debian/sid-omeyi/efl-1.18.4/src/lib/efl/.libs/libefl.so.1: > >> >> undefined symbol: _eo_call_end FAIL tests/evas/evas_suite (exit status: > >> >> 127) > >> > > >> > This seems suspicious - the linker can't find a symbol in libefl.so. > >> > Are you building with some other patches? > >> Nope. > >> > >> > > >> > [snip] > >> >> FAIL: tests/eio/eio_suite > >> >> = > >> >> > >> >> Running suite(s): Eio > >> > [snip] > >> >> 98%: Checks: 51, Failures: 1, Errors: 0 > >> >> tests/eio/eio_test_manager.c:68:F:Eio > >> >> Job:efl_io_manager_test_ls_funcs:0: > >> >> Failure '(*number_of_listed_files) != test_count' occurred > >> > > >> > I don't recall seeing this test fail before, sorry. > >> > > >> Ok, the above issues are from EFL 1.19.0 beta3 effort on a Debian Sid > >> (Unstable) on Reiser4 root fs. > >> > >> An EFL 1.18.4 build on Debian-Reiser4 root fs Jessie (Stable), fed > >> heavily from official jessie-backports repository, does succeed in > >> building the corresponding EFL 1.18.4 DEBs -- as long as I do three > >> modifications to relevant debian packaging. > >> > >> First I modify debian/rules, option: --enable-fb > >> - > >> [...] > >> ifeq (linux,$(DEB_HOST_ARCH_OS)) > >> arch_flags += --enable-fb<=## Directive is overlooked. DEB > >> build fails *because* it's missing > >> [...] > >> override_dh_auto_configure: > >> dh_auto_configure --verbose -- \ > >> [...] > >> --enable-fb \ <=## Added explicitly here, satisfies > >> dh_install > >> $(arch_flags) > >> [...] > >> > > > > err so --enable-fb makes an eio test work? and makes the evas test suite > > work > > (which doesn't use fb access at all)... THAT i don't get... > Hold on :) ... > Assuming I disable *all* tests, debian/rules *should* generate *all* > EFL DEB packages --but it does not, log shows hint: > [...] > make[2]: Leaving directory > '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' > make[1]: Leaving directory > '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' >debian/rules override_dh_install > make[1]: Entering directory > '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' > dh_install --list-missing > dh_install: Cannot find (any matches for) > "debian/tmp/usr/lib/*/evas/modules/engines/fb/*/module.so" (tried in > "." and "debian/tmp") > dh_install: libevas1-engines-fb missing files: > debian/tmp/usr/lib/*/evas/modules/engines/fb/*/module.so > dh_install: Cannot find (any matches for) > "debian/tmp/usr/lib/*/libecore_fb.so.*" (tried in "." and > "debian/tmp") > dh_install: libecore-fb1 missing files: debian/tmp/usr/lib/*/libecore_fb.so.* > dh_install: usr/bin/ecore_evas_convert exists in debian/tmp but is not > installed to anywhere > [...] > > which hints that experimental debian packaging default debian/rules directive > ifeq (linux,$(DEB_HOST_ARCH_OS)) > arch_flags += --enable-fb > > is being overlooked during build procedure. Accordingly,
Re: What's a safe way to have extensions in chromium in Debian?
On Thu, Mar 23, 2017 at 10:20:00AM +0500, Andrey Rahmatullin wrote: > On Wed, Mar 22, 2017 at 09:51:12PM +0100, Jeroen Dekkers wrote: > > If we already know this is going to be major issue, why aren't we > > doing the sensible thing and enable extensions by default > The story of extensions in Debian Chromium is a strange and sad one. > See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856183 > I cannot list all previous bugs included in that story, I think you can > find them in the changelog. Thanks, I've added a link to that bug page to https://wiki.debian.org/Chromium so that it now contains some information also on why they are disabled. Enrico -- GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini signature.asc Description: PGP signature
Re: [E-devel] EFL 1.19.0-beta3 (from git) package for Debian Experimental
On Wed, Mar 22, 2017 at 10:56 PM, Carsten Haitzler wrote: > On Wed, 22 Mar 2017 04:50:38 -0700 Jose R R said: > >> On Tue, Mar 21, 2017 at 4:55 PM, Ross Vandegrift wrote: >> [...] >> > Oh I see - I misunderstood your previous message and thought you were >> > targeting sid. You need to backport + rebuild for jessie. IIRC, the >> > only change I needed was to remove the auto dbgsym stuff. >> > >> > [snip] >> >> FAIL: tests/evas/evas_suite >> >> === >> >> >> >> /mnt/caxtolli/usr/src/build/enlightenment-debian/sid-omeyi/efl-1.18.4/src/tests/evas/.libs/evas_suite: >> >> symbol lookup >> >> error: >> >> /mnt/caxtolli/usr/src/build/enlightenment-debian/sid-omeyi/efl-1.18.4/src/lib/efl/.libs/libefl.so.1: >> >> undefined symbol: _eo_call_end FAIL tests/evas/evas_suite (exit status: >> >> 127) >> > >> > This seems suspicious - the linker can't find a symbol in libefl.so. >> > Are you building with some other patches? >> Nope. >> >> > >> > [snip] >> >> FAIL: tests/eio/eio_suite >> >> = >> >> >> >> Running suite(s): Eio >> > [snip] >> >> 98%: Checks: 51, Failures: 1, Errors: 0 >> >> tests/eio/eio_test_manager.c:68:F:Eio Job:efl_io_manager_test_ls_funcs:0: >> >> Failure '(*number_of_listed_files) != test_count' occurred >> > >> > I don't recall seeing this test fail before, sorry. >> > >> Ok, the above issues are from EFL 1.19.0 beta3 effort on a Debian Sid >> (Unstable) on Reiser4 root fs. >> >> An EFL 1.18.4 build on Debian-Reiser4 root fs Jessie (Stable), fed >> heavily from official jessie-backports repository, does succeed in >> building the corresponding EFL 1.18.4 DEBs -- as long as I do three >> modifications to relevant debian packaging. >> >> First I modify debian/rules, option: --enable-fb >> - >> [...] >> ifeq (linux,$(DEB_HOST_ARCH_OS)) >> arch_flags += --enable-fb<=## Directive is overlooked. DEB >> build fails *because* it's missing >> [...] >> override_dh_auto_configure: >> dh_auto_configure --verbose -- \ >> [...] >> --enable-fb \ <=## Added explicitly here, satisfies dh_install >> $(arch_flags) >> [...] >> > > err so --enable-fb makes an eio test work? and makes the evas test suite work > (which doesn't use fb access at all)... THAT i don't get... Hold on :) ... Assuming I disable *all* tests, debian/rules *should* generate *all* EFL DEB packages --but it does not, log shows hint: [...] make[2]: Leaving directory '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' make[1]: Leaving directory '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' debian/rules override_dh_install make[1]: Entering directory '/mnt/caxtolli/usr/src/build/enlightenment-debian/jessie-bp/efl-1.18.4' dh_install --list-missing dh_install: Cannot find (any matches for) "debian/tmp/usr/lib/*/evas/modules/engines/fb/*/module.so" (tried in "." and "debian/tmp") dh_install: libevas1-engines-fb missing files: debian/tmp/usr/lib/*/evas/modules/engines/fb/*/module.so dh_install: Cannot find (any matches for) "debian/tmp/usr/lib/*/libecore_fb.so.*" (tried in "." and "debian/tmp") dh_install: libecore-fb1 missing files: debian/tmp/usr/lib/*/libecore_fb.so.* dh_install: usr/bin/ecore_evas_convert exists in debian/tmp but is not installed to anywhere [...] which hints that experimental debian packaging default debian/rules directive ifeq (linux,$(DEB_HOST_ARCH_OS)) arch_flags += --enable-fb is being overlooked during build procedure. Accordingly, I had to explicitly add --enable-fb, at the end of options, as: override_dh_auto_configure: dh_auto_configure --verbose -- \ --disable-rpath \ --disable-silent-rules \ --enable-doc \ --with-profile=dev \ --with-tests=regular \ --with-crypto=gnutls \ --disable-tslib \ --enable-liblz4 \ --enable-xinput22 \ --enable-image-loader-webp \ --enable-harfbuzz \ --enable-systemd \ --enable-static \ --enable-image-loader-webp \ --with-generic_vlc \ --enable-fb \ $(arch_flags) That's how DEBs in reference snapshot were generated *finally*. > >> Second & third, I add your code to skip two(2) failing tests :D >> >> Skip: src/tests/eet/eet_suite.c >> Skip: src/tests/eio/eio_suite.c > > if you're disabling tests... I am not the only one. check experimental debian/changelog for references to previous deeds ;-) why not just not do "make check". i do not know > why your tests fail, but they should not. That's why I attached relevant fail logs in previous message ;-) Best Professional Regards. -- Jose R R http://metztli.it --
Re: What's a safe way to have extensions in chromium in Debian?
Hi, On Wed, Mar 22, 2017 at 12:03:02PM +0100, Enrico Zini wrote: > now we have extensions disabled in Chromium by default. If I did my > homeworks correctly, that prevents Chromium from phoning home by > default, and prevents a previous scenario where extensions could be > installed but not upgraded, becoming security issues over time. > > Now, suppose I need an extension, what is the proper way to have it in > Debian, so that it gets upgraded when needed? With that proper way, what > amount of phoning home is going to happen? > > Since this looks like it's going to be a major issue with stretch, can I > have some authoritative wiki page / FAQ entry that tells me how I can > deal with it cleanly, and that I can easily send to confused people? I wonder if we could just add a boolean debconf question for this. It could setup /etc/chromium.d/remote-extensions based on the answer and provide some (dis)advantages info for selecting either option. -- Sebastian signature.asc Description: PGP signature
