Bug#834244: Acknowledgement (libedit2: where_history() does not work. read_history() fails to update history_length.)
Hello,
I attach a short .c example to demonstrate the actual problem,
and I correct my message.
It is the sum history_base + history_length which causes me grief.
The behaviour of where_history() is unexpected to me, but I'm not
sure whether its usage in ngspice is correct.
Regards,
Robert
// adapted example from
// (compile "wget -O - https://cnswww.cns.cwru.edu/php/chet/readline/history.html#SEC18 | html2text | perl -ne 'print if(/^ #include/../^ }/)' > ex-0.c")
//
// (diff "ex-0.c" "ex-1.c" "-u0 -b -w")
//
// two compilation incantations, one for -lreadline, one for -ledit
// (compile "gcc -o ex-1.e -Wall -DEDITLINE ex-1.c -ledit")
// (compile "gcc -o ex-1.r -Wall -DREADLINE ex-1.c -lreadline")
//
// I expect history_base + history_length being the user visible position
// the thing one might use to print a "prompt"
// This works for -lreadline, but doesn't for -ledit
// It is not obvious for me, whether where_history() should do something
// similiar. It doesn't in different ways for both libraries
// In ngspice, there is a history_set_pos(history_length) before invoking
// readline(). then where_history() does the job, but only for -lreadline
//
// call ex-1.l and ex-1.r, enter some lines, and compare the printed values
// especially for history_base + history_length which does not increment beyond 1
// for libedit
// enter "list" for additional curiosity
// further experiment entering "bla", "bla", "save",
// then restart and enter "read", "bla"
// ==> history_length will jump as expected, but only after the next line
#include
#include
#include
#ifdef READLINE
#include
#endif
#ifdef EDITLINE
#include
#endif
int
main (argc, argv)
int argc;
char **argv;
{
char line[1024], *t;
int len, done = 0;
line[0] = 0;
using_history ();
// stifle_history(5);
while (!done)
{
// history_set_pos(history_length);
printf ("history wh=%d / hb+hl=%d / hb=%d hl=%d > ",
where_history(), history_base + history_length,
history_base, history_length);
fflush (stdout);
t = fgets (line, sizeof (line) - 1, stdin);
if (t && *t)
{
len = strlen (t);
if (t[len - 1] == '\n')
t[len - 1] = '\0';
}
if (!t)
strcpy (line, "quit");
if (line[0])
{
char *expansion;
int result;
result = history_expand (line, &expansion);
if (result)
fprintf (stderr, "%s\n", expansion);
if (result < 0 || result == 2)
{
free (expansion);
continue;
}
add_history (expansion);
strncpy (line, expansion, sizeof (line) - 1);
free (expansion);
}
if (strcmp (line, "quit") == 0)
done = 1;
else if (strcmp (line, "save") == 0)
write_history ("history_file");
else if (strcmp (line, "read") == 0)
read_history ("history_file");
else if (strcmp (line, "list") == 0)
{
register HIST_ENTRY **the_list = NULL;
register int i;
#ifdef READLINE
HISTORY_STATE *xx = history_get_history_state ();
// offset+length seems to be the actual user visible history position
the_list = history_list ();
fprintf(stderr, "history_list() = %p, history_get_history_state()->entries = %p, ->offset=%d ->length=%d, ->size=%d\n",
the_list, xx->entries, xx->offset, xx->length, xx->size);
#endif
fprintf (stderr, " wh=%d / hb=%d hl=%d\n",
where_history(), history_base, history_length);
if (the_list)
for (i = 0; the_list[i]; i++)
printf ("%d: %s\n", i + history_base, the_list[i]->line);
}
else if (strncmp (line, "delete", 6) == 0)
{
int which;
if ((sscanf (line + 6, "%d", &which)) == 1)
{
HIST_ENTRY *entry = remove_history (which);
if (!entry)
fprintf (stderr, "No such entry %d\n", which);
else
{
free ((char *) entry->line);
free (entry);
}
}
else
{
fprintf (stderr, "non-numeric arg given to `delete'\n");
}
}
}
exit(0);
}
Bug#811987: fixed in ceres-solver 1.11.0~dfsg0-4
Hi, Am 12.08.2016 um 19:55 schrieb Santiago Vila: > Still FTBFS: > > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.11.0~dfsg0-5.rbuild.log this appears to be a different bug due to a new eigen3 release and not related to the bug you reopened. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#806042: guile-2.0: FTBFS when built with dpkg-buildpackage -A (No such file or directory)
found 806042 2.0.11+1-11 thanks This still happens in this version: - make[5]: Leaving directory '/<>/guile-2.0-2.0.11+1' make[4]: Leaving directory '/<>/guile-2.0-2.0.11+1' make[3]: Leaving directory '/<>/guile-2.0-2.0.11+1' make[2]: Leaving directory '/<>/guile-2.0-2.0.11+1' make[1]: Leaving directory '/<>/guile-2.0-2.0.11+1' debian/rules override_dh_install-indep make[1]: Entering directory '/<>/guile-2.0-2.0.11+1' rm -f debian/tmp/usr/lib/x86_64-linux-gnu/libguile*.la test "guile.info guile.info-1 guile.info-10 guile.info-2 guile.info-3 guile.info-4 guile.info-5 guile.info-6 guile.info-7 guile.info-8 guile.info-9" = \ "guile.info guile.info-1 guile.info-10 guile.info-2 guile.info-3 guile.info-4 guile.info-5 guile.info-6 guile.info-7 gu ile.info-8 guile.info-9" dh_install -i --fail-missing \ -Xusr/share/info/dir \ -Xusr/share/info/r5rs.info dh_install: usr/share/man/man1/guile.1 exists in debian/tmp but is not installed to anywhere dh_install: missing files, aborting debian/rules:226: recipe for target 'override_dh_install-indep' failed make[1]: *** [override_dh_install-indep] Error 255 make[1]: Leaving directory '/<>/guile-2.0-2.0.11+1' debian/rules:99: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 - Thanks.
Bug#833849: systemd: localed fails to start if /etc/default/keyboard is missing
Hello Simon, Felipe, Felipe Sateler [2016-08-12 11:16 -0300]: > Thanks for the patch.This makes a lot of sense, especially because > ENOENT is tolerated everywhere in that file. Indeed, thanks! I added a test case for this which reproduced the failure and confirms the fix: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=2e9ebeb Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Bug#827517: xul-ext-ublock-origin: Missing icons in uBlock's popup UI
Followup-For: Bug #827517 Package: xul-ext-ublock-origin Version: 1.8.4+dfsg-1 Dear Maintainer, This bug is still present in the current versions of ublock-origin and firefox-esr. Reading the previous messages I understand that the bug has been fixed starting from firefox 48 but there is no indication that the same issue could be resolved in the current esr version of firefox. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xul-ext-ublock-origin depends on: ii firefox-esr 45.3.0esr-1 ii fonts-font-awesome 4.6.3~dfsg-1 ii iceweasel 45.3.0esr-1 xul-ext-ublock-origin recommends no packages. xul-ext-ublock-origin suggests no packages. -- no debconf informatio
Bug#833656: cme fails with dpkg error
On Sun, Aug 14, 2016 at 12:36:03AM +0200, gregor herrmann wrote:
>use AptPkg::Config '$_config';
>use AptPkg::System '$_system';
>use AptPkg::Version;
>use AptPkg::Cache ;
>
>$_config->init;
>$_system = $_config->system;
>my $vs = $_system->versioning;
>my $apt_cache = AptPkg::Cache->new ;
This is a bit puzzling, but I am guessing that the bug is in apt:
getDpkgStatusLocation is modifying the global _config object of libapt-pkg in
such a way that if debSystem::Initialize is called twice, the results will be
different.
As far as I can make out, the code appears to be modifying the configuration
in order to get a derived value for Dir::State::status, which it then returns
so that the caller can set the value. This means that you are effectively
doing:
Cnf.Set("Dir::State::status", {
Cnf.Set("Dir::State::status", "status");
return Cnf.FindFile("Dir::State::status");
});
along with some other manipulations. If I understand your intent correctly, I
would recommend rewriting getDpkgStatusLocation to take a const reference to
the Configuration, and to use an internal temporary instance. A brief comment
to explain what the heck it is trying to achieve wouldn't go astray either.
You could argue that the Initialize method shouldn't be called twice, but that
may be out of the caller's hands.
To clarify what's actually happening here, this line:
$_config->init;
invokes pkgInitConfig under the hood, on the global C++ _config object. This
populates it with general APT things, e.g. Dir::State, but not Debian-specific
things like Dir::State::status. After that, the following line:
$_system = $_config->system;
calls pkgInitSystem, passing in the global _config object, and populating the
global _system object (which is magically bound to $_system, so that
assignment works). That indirectly calls debSystem::Initialize, which sets
Debian-specific things like Dir::State::status and Dir::State::extended_status.
Adding some debugging of the working code from the example directory, after
the $_config->init line I get as expected:
RootDir=
Dir=/
Dir::State=var/lib/apt/
Dir::State::status=
Dir::State::extended_states=
and after the $_system = ... line:
RootDir=
Dir=/
Dir::State=var/lib/apt/
Dir::State::status=/var/lib/dpkg/status
Dir::State::extended_states=extended_states
For the case of libconfig-model-dpkg-perl, I'm seeing the following for after
the init:
RootDir=
Dir=
Dir::State=var/lib/apt/
Dir::State::status=var/lib/dpkg/status
Dir::State::extended_states=extended_states
which suggests that the _config object has been modified prior to this code
being run. Not sure where, perhaps there is another use of AptPkg in cme?
--bod
Bug#834285: teeworlds: testing has incompatible nethash
Package: teeworlds Version: 0.6.2+dfsg-2 Severity: important Dear Maintainer, when trying to connect to a 0.6.3 server with the teeworld client provided in debian testing, it shows : 'Wrong version. Server is running '0.6 626fce9a778df4d4' and client '0.6 e42d81cd67b8c7bc'' debian stable version is not affected. thanks for your help! best regards, Gaël -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages teeworlds depends on: ii libc6 2.23-4 ii libfreetype6 2.6.3-3+b1 ii libgl1-mesa-glx [libgl1] 11.2.2-1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libsdl1.2debian 1.2.15+dfsg1-4 ii libstdc++66.1.1-10 ii libwavpack1 4.80.0-1 ii teeworlds-data0.6.2+dfsg-2 ii zlib1g1:1.2.8.dfsg-2+b1 teeworlds recommends no packages. teeworlds suggests no packages. -- no debconf information
Bug#805076: lintian: Only check PHP modules if they contain a .php file
Package: lintian Version: 2.5.46 Followup-For: Bug #805076 Dear Maintainer, there have been quite some releases since I opened this. Is there anything I can improve to get this included? Cheers Jochen -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages lintian depends on: ii binutils 2.27-5 ii bzip2 1.0.6-8 ii diffstat 1.61-1 ii file 1:5.28-4 ii gettext 0.19.8.1-1 ii hardening-includes2.8+nmu2 ii intltool-debian 0.35.0+20060710.4 ii libapt-pkg-perl 0.1.29+b5 ii libarchive-zip-perl 1.59-1 ii libclass-accessor-perl0.34-1 ii libclone-perl 0.38-2 ii libdata-alias-perl1.20-1+b1 ii libdpkg-perl 1.18.10 ii libemail-valid-perl 1.200-1 ii libfile-basedir-perl 0.07-1 ii libipc-run-perl 0.94-1 ii liblist-moreutils-perl0.416-1 ii libparse-debianchangelog-perl 1.2.0-10 ii libperl5.22 [libdigest-sha-perl] 5.22.2-3 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii liburi-perl 1.71-1 ii libyaml-libyaml-perl 0.41-6+b1 ii man-db2.7.5-1 ii patchutils0.3.4-1 ii perl 5.22.2-3 ii t1utils 1.39-2 ii xz-utils 5.1.1alpha+20120614-2.1 Versions of packages lintian recommends: ii dpkg 1.18.10 pn libperlio-gzip-perl ii perl 5.22.2-3 ii perl-modules-5.22 [libautodie-perl] 5.22.2-3 Versions of packages lintian suggests: pn binutils-multiarch ii dpkg-dev 1.18.10 ii libhtml-parser-perl3.72-2 ii libtext-template-perl 1.46-1 -- no debconf information
Bug#672449: x11vnc: Option -no6 and -noipv6 do not seem to have effect
On Wed, 23 Jul 2014 14:53:13 -0700 Kristian Erik Hermansen wrote: > # x11vnc -safer -listen 127.0.0.1 -no6 -bg -display :0 2>&1 | egrep -i 'tcp6' > 23/07/2014 14:48:42 Autoprobing TCP6 port > 23/07/2014 14:48:42 Autoprobing selected TCP6 port 5900 I've found that it's possible to avoid this behavior by using -rfbportv6 -1 together with -rfbport in order to specify an ipv4 port. It is necessary to specify an ipv4 port via the -rfbport argument in order to prevent rfbScreen->autoPort from triggering the "Autoprobing" code that opens an ipv6 socket here: https://github.com/LibVNC/libvncserver/blob/LibVNCServer-0.9.10/libvncserver/sockets.c#L159
Bug#834245: RFS: arasan/19.0.1-1 [ITP] -- a strong chess engine using xboard
reopen 834245 stop Sorry my mistake, reopening.
Bug#827245: missing backend for pool type 11 (zfs)
Tyler Fenby wrote: > I can confirm that the ZFS backend works as expected on Debian after > recompiling libvirt with only a couple lines added to debian/rules to > enable the configure flag. thanks for looking into this. I cloned libvirt from git://anonscm.debian.org/pkg-libvirt/libvirt.git when i first submitted the bug report, and installed all the build-deps but whenever I try to compile it, I just gets lots of errors about redeclarations. compiling on sid with dpkg-buildpackage -b -us -uc: ... enum VIR_TYPED_PARAM_UINT from /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h redeclared in /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h enum VIR_TYPED_PARAM_STRING_OKAY from /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h redeclared in /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h enum VIR_CONNECT_CLOSE_REASON_ERROR from /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h redeclared in /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h enum VIR_TYPED_PARAM_LLONG from /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h redeclared in /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h Makefile:2307: recipe for target '../../../docs/apibuild.py.stamp' failed make[3]: *** [../../../docs/apibuild.py.stamp] Error 2 make[3]: Leaving directory '/home/cas/git/forks/libvirt/libvirt/debian/build/docs' Makefile:2001: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/cas/git/forks/libvirt/libvirt/debian/build' Makefile:1898: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/cas/git/forks/libvirt/libvirt/debian/build' dh_auto_build: make -j1 returned exit code 2 debian/rules:131: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 The changes required to enable ZFS support seem obvious and straight-forward. maybe i should try building in a jessie or testing VM? craig ps: i've really got to find out why i don't get auto-subscribed to bug reports I submit. I only saw your email because I checked the BTS web page.
Bug#805076: lintian: Only check PHP modules if they contain a .php file
Jochen Sprickerhof:
> Package: lintian
> Version: 2.5.46
> Followup-For: Bug #805076
>
> Dear Maintainer,
>
> there have been quite some releases since I opened this. Is there anything I
> can improve to get this included?
>
> Cheers Jochen
> [...]
Hi,
Apologies for missing this.
It would be good to optimise this a bit. Something like (from finger
memory rather than tested code):
if (any { $_->basename =~ m/\.php$/i } $info->sorted_index) {
Would be a vast improvement over creating a huge string of all source
files in the package only to apply single regex to it.
Thanks,
~Niels
Bug#833528: multipath-tools: Multipathd reports failed paths as active, but with increased error count.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, On Fri, 2016-08-05 at 16:13 +0300, Panos Gotsis wrote: > We have our nodes installed with the latest patched jessie. The OS version > comes with > multipath-tools-0.5.0-6+deb8u2. The system uses iscsi to connect to a SAN > storage (Netapp). > > The multipathd daemon starts properly and assembles the multipath devices for > the iscsi LUNs. > However, when testing how it handles failures, we are seeing that for LUNs > that we have set > offline or delete completely on our storage system, the output of multipath -l > or, even > better, dmsetup status, is not showing these paths as failed, but as active, > and it only > increments the fail_count counter. Can you share the steps you followed for deleting the LUNs ? Were the LUNs in use on the Host, when you deleted it on the target ? Did you rescan your session on the Host, after deleting the LUNs on the target ? - -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXsC+jAAoJEKY6WKPy4XVpNBwP/0+THJUvbGGGVsrkSN/FU29s 9SBxnf4cDZM9K9EhmiwH+eW3votJ8u1No2hHVP6D9JKaJ8fbDaccF7iHFVxhdRhR oTUY4YoyoOMpny9xkkqGkLd4UOFyRAFJiv2+dIsCS5q/5qTLvgFCmQpGWMS0W44t L68GO15Oz64WA7MS4l7Jn+fhevUbFBBfVjcu26YHYy/lkyfG5zdL60s+BLOmZGeB D3ptKJYEp9J7eOTfEo0oJqBAhh2V4XoztY8OyTC1eR8jruwmGzEIwmW+9GKgVwFG uGCFLvg/nkxHp8Ra2Tvv3g4xLKgfE7H6oUHSGt30mmtPWXdQTKEjhETqrsS2/XKg WU0OK6q/Fho7SaeAUE9CAiwL4PqXnt5k+0pDoyb1JaLO3opvb03iUaVECy7p9iYv EpW/+5/PlWu7vitvubAOgSI/T4ErPu7vz75XGjLtqh0CD+rr2p3htFwC79xi0m7H VMq/yTz0oIKX6jyhWJAWuxefzNPKrBJ7ViL/LtzXfjDU6zutlTTOF8lecaK2YyYT 8MUhVd1J8tWsuLNyB8MOv+mgubvUiDAUboojBxASxVgtApjaUVn3gaNY/UJ6CwCy 5CAlwrpS/QV5V3VhgPSNKjydD+QLY5eT7KnOL+wCC8Ce7hAoFkqa+/pM+B/p15YM Y49H4wsRj6oAsjprOa6u =PZnQ -END PGP SIGNATURE-
Bug#636126: segfaults when skype account is enabled.
Actually I find this problem even more serious then that because it does this even though I have Skype installed. For pidgin not to crash I have to run Skype and login first, otherwsie this happens:1. Pidgin runs Skype.2. Wait for a bit (whether logging in to Skype or not)3. Pidgin crashes.4. Restart pidgin with Skype open but not logged in.5. Pidgin crashes I don't know if this problem comes from pidgin-skype, or pidgin itself... I would expect a stable package to cope with the unexpected and not just die.
Bug#811987: fixed in ceres-solver 1.11.0~dfsg0-4
fixed 811987 1.11.0~dfsg0-4 thanks On Sun, 14 Aug 2016, Philipp Huebner wrote: > Hi, > > Am 12.08.2016 um 19:55 schrieb Santiago Vila: > > Still FTBFS: > > > > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.11.0~dfsg0-5.rbuild.log > > this appears to be a different bug due to a new eigen3 release and not > related to the bug you reopened. You are right, they seem different. I'll file a different bug, then. Thanks.
Bug#834287: caja-extensions: FTBFS: ./autogen.sh: 80: shift: can't shift that many
Source: caja-extensions Version: 1.14.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, caja-extensions fails to build from source in unstable/amd64: [..] Setting up libice-dev:amd64 (2:1.0.9-1+b1) ... Setting up glib-networking:amd64 (2.48.2-1) ... Setting up libxcomposite1:amd64 (1:0.4.4-1) ... Setting up libxcb-shm0:amd64 (1.11.1-1.1) ... Setting up libxcb-shape0:amd64 (1.11.1-1.1) ... Setting up libxrender1:amd64 (1:0.9.9-2) ... Setting up libxcb1-dev:amd64 (1.11.1-1.1) ... Setting up libxcb-glx0-dev:amd64 (1.11.1-1.1) ... Setting up libavahi-client3:amd64 (0.6.32-1) ... Setting up libx11-dev:amd64 (2:1.6.3-1) ... Setting up libxft2:amd64 (2.3.2-1) ... Setting up libharfbuzz-dev:amd64 (1.2.7-1+b1) ... Setting up libxcb-sync-dev:amd64 (1.11.1-1.1) ... Setting up fontconfig (2.11.0-6.5) ... Regenerating fonts cache... done. Setting up libcups2:amd64 (2.1.4-4) ... Setting up libegl1-mesa:amd64 (11.2.2-1) ... Setting up libfontconfig1-dev:amd64 (2.11.0-6.5) ... Setting up libx11-xcb-dev:amd64 (2:1.6.3-1) ... Setting up libsm-dev:amd64 (2:1.2.2-1+b1) ... Setting up libxext6:amd64 (2:1.3.3-1) ... Setting up libxfixes3:amd64 (1:5.0.2-1) ... Setting up libatspi2.0-0:amd64 (2.20.2-1) ... Setting up x11proto-fixes-dev (1:5.0-2) ... Setting up libgdk-pixbuf2.0-0:amd64 (2.34.0-1) ... Setting up libxcb-shm0-dev:amd64 (1.11.1-1.1) ... Setting up libsoup2.4-1:amd64 (2.54.1-1) ... Setting up gir1.2-gdkpixbuf-2.0:amd64 (2.34.0-1) ... Setting up libxrender-dev:amd64 (1:0.9.9-2) ... Setting up libsoup-gnome2.4-1:amd64 (2.54.1-1) ... Setting up gir1.2-soup-2.4 (2.54.1-1) ... Setting up libstartup-notification0:amd64 (0.12-4) ... Setting up libxcb-dri2-0-dev:amd64 (1.11.1-1.1) ... Setting up libgssdp-1.0-3:amd64 (0.14.16-1) ... Setting up libxcb-render0-dev:amd64 (1.11.1-1.1) ... Setting up x11proto-damage-dev (1:1.2.1-2) ... Setting up libxft-dev (2.3.2-1) ... Setting up gtk-update-icon-cache (3.20.7-1) ... Setting up libgdk-pixbuf2.0-dev (2.34.0-1) ... Setting up libxcb-dri3-dev:amd64 (1.11.1-1.1) ... Setting up libxcursor1:amd64 (1:1.1.14-1+b1) ... Setting up libxext-dev:amd64 (2:1.3.3-1) ... Setting up libpango-1.0-0:amd64 (1.40.1-1) ... Setting up libwayland-egl1-mesa:amd64 (11.2.2-1) ... Setting up libxcb-shape0-dev:amd64 (1.11.1-1.1) ... Setting up libatk-bridge2.0-0:amd64 (2.20.1-3) ... Setting up librest-0.7-0:amd64 (0.8.0-1) ... Setting up libxxf86vm1:amd64 (1:1.1.4-1) ... Setting up libxxf86vm-dev:amd64 (1:1.1.4-1) ... Setting up libxfixes-dev:amd64 (1:5.0.2-1) ... Setting up gir1.2-gssdp-1.0:amd64 (0.14.16-1) ... Setting up x11proto-composite-dev (1:0.4.2-2) ... Setting up libxrandr2:amd64 (2:1.5.0-1) ... Setting up libxi6:amd64 (2:1.7.6-1) ... Setting up gir1.2-atspi-2.0 (2.20.2-1) ... Setting up libsoup2.4-dev (2.54.1-1) ... Setting up libcairo2:amd64 (1.14.6-1+b1) ... Setting up libxinerama1:amd64 (2:1.1.3-1+b1) ... Setting up libxcursor-dev:amd64 (1:1.1.14-1+b1) ... Setting up libxcb-randr0-dev:amd64 (1.11.1-1.1) ... Setting up libxdamage1:amd64 (1:1.1.4-2+b1) ... Setting up libxrandr-dev:amd64 (2:1.5.0-1) ... Setting up libgupnp-1.0-4:amd64 (0.20.18-1) ... Setting up libxcomposite-dev (1:0.4.4-1) ... Setting up libcairo-script-interpreter2:amd64 (1.14.6-1+b1) ... Setting up libxcb-xfixes0-dev:amd64 (1.11.1-1.1) ... Setting up libstartup-notification0-dev:amd64 (0.12-4) ... Setting up libcairo-gobject2:amd64 (1.14.6-1+b1) ... Setting up libxdamage-dev:amd64 (1:1.1.4-2+b1) ... Setting up libxtst6:amd64 (2:1.2.2-1+b1) ... Setting up libpangoft2-1.0-0:amd64 (1.40.1-1) ... Setting up libxinerama-dev:amd64 (2:1.1.3-1+b1) ... Setting up libgssdp-1.0-dev (0.14.16-1) ... Setting up libxcb-present-dev:amd64 (1.11.1-1.1) ... Setting up libxi-dev (2:1.7.6-1) ... Setting up libcairo2-dev (1.14.6-1+b1) ... Setting up gir1.2-freedesktop:amd64 (1.48.0-3) ... Setting up libpangoxft-1.0-0:amd64 (1.40.1-1) ... Setting up gir1.2-gupnp-1.0:amd64 (0.20.18-1) ... Setting up libpangocairo-1.0-0:amd64 (1.40.1-1) ... Setting up gir1.2-pango-1.0:amd64 (1.40.1-1) ... Setting up libxtst-dev:amd64 (2:1.2.2-1+b1) ... Setting up libegl1-mesa-dev:amd64 (11.2.2-1) ... Setting up libpango1.0-dev (1.40.1-1) ... Setting up librsvg2-2:amd64 (2.40.16-1) ... Setting up libgupnp-1.0-dev:amd64 (0.20.18-1) ... Setting up libatspi2.0-dev (2.20.2-1) ... Setting up librsvg2-common:amd64 (2.40.16-1) ... Setting up libatk-bridge2.0-dev:amd64 (2.20.1-3) ... Setting up adwaita-icon-theme (3.20-3) ... update-alternatives: using /usr/share/icons/Adwaita/cursor.theme to provide /usr/share/icons/default/index.theme (x-cursor-theme) in auto mode Setting up libgtk-3-0:amd64 (3.20.7-1) ... Setting up libcaja-extension1:a
Bug#834286: ccbuild: FTBFS: yylex.cc:1093:25: error: expected constructor, destructor, or type conversion before '(' token
Source: ccbuild Version: 2.0.7-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ccbuild fails to build from source in unstable/amd64: [..] Preparing to unpack .../24-libx11-6_2%3a1.6.3-1_amd64.deb ... Unpacking libx11-6:amd64 (2:1.6.3-1) ... Selecting previously unselected package libbobcat4. Preparing to unpack .../25-libbobcat4_4.02.00-1_amd64.deb ... Unpacking libbobcat4 (4.02.00-1) ... Selecting previously unselected package libbobcat-dev. Preparing to unpack .../26-libbobcat-dev_4.02.00-1_amd64.deb ... Unpacking libbobcat-dev (4.02.00-1) ... Selecting previously unselected package libboost1.61-dev:amd64. Preparing to unpack .../27-libboost1.61-dev_1.61.0+dfsg-2.1_amd64.deb ... Unpacking libboost1.61-dev:amd64 (1.61.0+dfsg-2.1) ... Selecting previously unselected package libboost-dev:amd64. Preparing to unpack .../28-libboost-dev_1.61.0.2_amd64.deb ... Unpacking libboost-dev:amd64 (1.61.0.2) ... Setting up libcurl3:amd64 (7.50.1-1) ... Setting up libp11-kit-dev:amd64 (0.23.2-4) ... Setting up libtasn1-6-dev:amd64 (4.9-4) ... Setting up cmake-data (3.5.2-2) ... Setting up libboost1.61-dev:amd64 (1.61.0+dfsg-2.1) ... Setting up libfl-dev:amd64 (2.6.1-1) ... Setting up pkg-config (0.29-4) ... Setting up libgnutlsxx28:amd64 (3.5.2-2) ... Processing triggers for libc-bin (2.23-4) ... Setting up libmilter1.0.1:amd64 (8.15.2-4) ... Setting up libgnutls-openssl27:amd64 (3.5.2-2) ... Processing triggers for man-db (2.7.5-1) ... Setting up libboost-dev:amd64 (1.61.0.2) ... Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ... Setting up libgmpxx4ldbl:amd64 (2:6.1.1+dfsg-1) ... Setting up libx11-data (2:1.6.3-1) ... Setting up libxau6:amd64 (1:1.0.8-1) ... Setting up liblzo2-2:amd64 (2.08-1.2) ... Setting up libidn11-dev (1.33-1) ... Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ... Setting up libjsoncpp1:amd64 (1.7.2-1) ... Setting up libgmp-dev:amd64 (2:6.1.1+dfsg-1) ... Setting up flex (2.6.1-1) ... Setting up libarchive13:amd64 (3.2.1-2) ... Setting up nettle-dev (3.2-1) ... Setting up cmake (3.5.2-2) ... Setting up libxcb1:amd64 (1.11.1-1.1) ... Setting up libx11-6:amd64 (2:1.6.3-1) ... Setting up libgnutls28-dev:amd64 (3.5.2-2) ... Setting up libbobcat4 (4.02.00-1) ... Setting up libbobcat-dev (4.02.00-1) ... Setting up ccbuild-build-deps (2.0.7-2) ... Processing triggers for libc-bin (2.23-4) ... ** ** Environment ** ** PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOSTNAME=3d7c5368ee10 TERM=xterm PAGER=more DISPLAY=:0 DOCKER_IMAGE=lamby-debian-sid DEB_BUILD_OPTIONS=parallel=9 PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip HOME=/home/lamby LOGNAME=lamby SHLVL=1 PWD=/home/lamby/temp/cdt.20160814095116.Vbg3qTPyBD.db.ccbuild/ccbuild-2.0.7 OLDPWD=/home/lamby/temp/cdt.20160814095116.Vbg3qTPyBD.db.ccbuild GPG_TTY=/dev/console QUILT_PATCHES=debian/patches QUILT_NO_DIFF_INDEX=1 QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index DEBEMAIL=la...@debian.org DEBFULLNAME=Chris Lamb EDITOR=vim LESS=-cgiFx4M GPG_KEY=1E953E27D4311E58 BLASTER=A220 I5 D1 H5 P330 T6 _=/usr/bin/env ** ** Building ccbuild 2.0.7-2 on amd64 ** ** dpkg-buildpackage -rfakeroot -D -us -uc -b dpkg-buildpackage: info: source package ccbuild dpkg-buildpackage: info: source version 2.0.7-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by tony mancill dpkg-source --before-build ccbuild-2.0.7 dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean dh_clean debian/rules build dh build dh_testdir dh_update_autotools_config dh_auto_configure cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -- The C compiler identification is GNU 6.1.1 -- The CXX compiler identification is GNU 6.1.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for worki
Bug#777182: kerberos-configs: please make the build reproducible
tags 777182 + pending thanks Hi Sam, > It's a fairly static package, and I don't think reproducible builds adds > enough value to this package to justify an upload just for this patch. [..] > I will include it in the next upload. I would agree; best to be somewhat conservative for packages such as this. I've taken the pro-active step of tagging it as ``pending`` to reflect your intention to include it, however. > I'd prefer not an NMU for this issue alone Naturally. Whilst the Reproducible Builds effort has come a long way, we're not at the "NMU" stage yet. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#834288: RFS: dblatex/0.3.8-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dblatex" Package name: dblatex Version : 0.3.8-1 Upstream Author : Benoît Guillon URL : http://dblatex.sourceforge.net/ License : GPL V2+ Section : text It builds those binary packages: dblatex - Produces DVI, PostScript, PDF documents from DocBook sources dblatex-doc - Documentation for dblatex To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dblatex Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dblatex/dblatex_0.3.8-1.dsc More information about hello can be obtained from https://www.example.com. Changes since the last upload: * New upstream release * Drop a temporary lintian override regarding a copyright file spelling error as it has been fixed upstream. * Standards-Version: 3.9.8 + Move documentation and examples to separate package dblatex-doc. * Actualize debian/watch. Regards, Andreas Hoenen -- Andreas Hoenen GPG: 1024D/B888D2CE A4A6 E8B5 593A E89B 496B 82F0 728D 8B7E B888 D2CE signature.asc Description: PGP signature
Bug#834032: dict-gcide: fails to purge - command in postrm not found
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Andreas, Thanks for the bug report. On Thu, 2016-08-11 at 15:55 +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed to purge due > to a command not found. According to policy 7.2 you cannot rely on the > depends being available during purge, only the essential packages are > available for sure. > Yes. This looks very odd. And the english is not very clear. It says, "but the depended-on package is more likely to be available if the package declares a dependency". The dependency is well defined in dict-gcide. But the above statement of "more likely" is to be satisfied by whom. How is the installation done in piuparts ? The removal below shows dpkg being invoked directly. So, does dpkg honor the package relationships ? > Filing this as important because a.) it's a clear policy violation (to > not clean up at purge) b.) having a piuparts clean archive is a release > goal since lenny and c.) this package being piuparts buggy blocks > packages depending on it from being tested by piuparts (and thus > possibly the detection of more severe problems). > > >From the attached log (scroll to the bottom...): > > 0m33.2s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp9_Z9Q9', > 'dpkg', '--purge', 'dict-gcide'] > 0m33.2s DUMP: > (Reading database ... 6241 files and directories currently installed.) > Removing dict-gcide (0.48.2) ... > Purging configuration files for dict-gcide (0.48.2) ... > /var/lib/dpkg/info/dict-gcide.postrm: 7: /var/lib/dpkg/info/dict- > gcide.postrm: dictdconfig: not found > dpkg: error processing package dict-gcide (--purge): > subprocess installed post-removal script returned error exit status 127 > Errors were encountered while processing: > dict-gcide > 0m33.2s DEBUG: Command failed (status=1), but ignoring error: ['chroot', > '/tmp/piupartss/tmp9_Z9Q9', 'dpkg', '--purge', 'dict-gcide'] - -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXsDZWAAoJEKY6WKPy4XVpn6kP/iWlMD2IImtQJ4UBbNrOVuAd YWVBp7O0BcSxHSNQ4yDwnIhNB540dsvhXwiqL1+LeXtmbDARBg8K/EZ2YtSWCcJr 0L22nurrBk3CyMDxXdjOfwooSlswyDm7Duz7SvjJAOxDploDqJSCkoXVOghrmPJB aCzkZPXV2IVmTzIl/RtA5qTrLfxsmjQpIkfLZSdawIBDXbf6DtyN6Minef8H3MKa tX+AshpVZOhgcAIvTClm0NOopGF0unag0jPhjMfqrugYj9g7rY8zzAY01WvHCLYz BrLbE1A2j7VBeHGS2JCAdFTVv0tYw4A4J8d766gabirro8T0q7b8UUq64Vn4cc44 nkwtVWhQ/t/ZB4fNboQMYBUtrZUSSAy+c5YveqpENIOMAlP5QtTw3AAL1tUZ3FSG 2s5DRyAzQyh+EVCmdZRDIuZVsLtJBGGhrIkCG2kEw337LfrT7MTIogggTvk7BU/n epy+ss2dJt9A/jrfkZNnI+lC13RB++LcXwTQ8p7mVTN/Cd10MT4nJEfau1eYnvXN UUWaY3ap1Qz6GU0DpKqM6F+RBGnGtguMOy+D4fK9U+L4gsyX3ioQBjnahFPZJXbK OnLY4Iw/rQE5tJn1jkihByzFVYUnB2bU5mwbAqRUsUQFkZLGi86TFcOcvSYflx4Q IbhSyNLLb6JANLa+KbDR =B6BX -END PGP SIGNATURE-
Bug#797539: cadabra: please make the build reproducible
I'd really appreciate it if you could NMU it Chris. Cheers, Iulian On Sun, Aug 14, 2016 at 01:58:36AM +0100, Chris Lamb wrote: > Dear Maintainer, > > > Source: cadabra > > Version: 1.29-1 > > Tags: patch > > There hasn't seem to be any update on this bug in 348 days, in which > time the Reproducible Builds effort has come on a long way. :) > > Would you consider applying this patch and uploading? > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`-
Bug#834289: override: kde-sc-dev-latest:metapackages/optional, kdenetwork:metapackages/optional
Package: ftp.debian.org Severity: normal Hi, kde-sc-dev-latest and kdenetwork are metapackages, so please update the overrides accordingly. Thanks, -- Pino
Bug#834244: libedit2: where_history() does not work. read_history() fails to update history_length.
Le 13/08/2016 à 19:35, larice a écrit : > Package: libedit2 > Version: jessie + stretch > Severity: normal > Tags: upstream > > Dear Maintainer, > >* What led up to the situation? > Using debian package ngspice. > > * What exactly did you do (or not do) that was effective (or ineffective)? > The debian package ngspice is configured to use libedit (--with-libedit). > ngspice uses the libedit function where_history() to format a prompt > for the next command. > The prompt is expected to increment with every entered command. > It does not so due to this bug. If ngspice is compiled to use libreadline > instead of libedit, then it does work. > I tried to work around, using history_base + history_length instead of > where_history(). > This does almost work. But ngspice calls read_history() (part of libedit) > to read the history from a file. And the implementation if read_history() > in libedit does not update history_length, causing the very first prompt > being incorrect. I think you should report this bug directly to upstream as it is not a packaging issue. S
Bug#834271: notmuch: FTBFS in testing
On Sun, 14 Aug 2016, David Bremner wrote: > Attached please find a debdiff that fixes the problem in unstable. I'm > fairly certain it's the same problem (same spurious output) as in > testing. I'm not sure when I'll be able to upload this, so if someone > wants to NMU/sponsor it, feel free. Great. I've uploaded 0.22.1-3 exactly as reflected in the patch (excluding the artifact where debian/.gitignore is removed, as such file is not present in the Debian source package for 0.22.1-2). Thanks a lot.
Bug#834290: Warn about libraries with excessive priority?
Package: lintian Version: 2.5.46 Severity: wishlist Now that Lintian no longer warns about dependencies on packages with lower priorities, I think it would make sense for Lintian to warn about library packages with excessively high priorities. In general, a library package should only get pulled in on a system because some other package depends on it; no library package needs installation on a system where nothing uses it. Given that, I don't think it makes sense for any library package to have a priority higher than "optional". More concretely: I'd propose a warning on packages in section "libs" with names matching "^lib.*" and not "-bin$", that have a priority of "required", "important", or "standard". I've reviewed every single package in Debian that would match that rule, and I can confirm that it would produce zero false positives. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils 2.27-5 ii bzip2 1.0.6-8 ii diffstat 1.61-1 ii file 1:5.28-4 ii gettext 0.19.8.1-1 ii hardening-includes2.8+nmu2 ii intltool-debian 0.35.0+20060710.4 ii libapt-pkg-perl 0.1.29+b5 ii libarchive-zip-perl 1.59-1 ii libclass-accessor-perl0.34-1 ii libclone-perl 0.38-2 ii libdata-alias-perl1.20-1+b1 ii libdpkg-perl 1.18.10 ii libemail-valid-perl 1.200-1 ii libfile-basedir-perl 0.07-1 ii libipc-run-perl 0.94-1 ii liblist-moreutils-perl0.416-1 ii libparse-debianchangelog-perl 1.2.0-10 ii libperl5.22 [libdigest-sha-perl] 5.22.2-3 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii liburi-perl 1.71-1 ii libyaml-libyaml-perl 0.41-6+b1 ii man-db2.7.5-1 ii patchutils0.3.4-1 ii perl 5.22.2-3 ii t1utils 1.39-2 ii xz-utils 5.1.1alpha+20120614-2.1 Versions of packages lintian recommends: ii dpkg 1.18.10 pn libperlio-gzip-perl ii perl 5.22.2-3 ii perl-modules-5.22 [libautodie-perl] 5.22.2-3 Versions of packages lintian suggests: pn binutils-multiarch ii dpkg-dev 1.18.10 ii libhtml-parser-perl3.72-2 pn libtext-template-perl -- no debconf information
Bug#834293: ITP: zplug -- next-generation plugin manager for zsh
Package: wnpp Severity: wishlist Owner: "ChangZhuo Chen (陳昌倬)" * Package name: zplug Version : 2.1.0 Upstream Author : Masaki Ishiyama * URL : https://zplug.sh/ * License : Expat Programming Lang: zsh Description : next-generation plugin manager for zsh zplug is a next-generation plugin manager for zsh, with the following features: . * Can manage everything * Zsh plugins/UNIX commands on GitHub and Bitbucket * Gist files (gist.github.com) * Externally managed plugins e.g., oh-my-zsh plugins/themes * Binary artifacts on GitHub Releases * Local plugins * etc. (you can add your own sources!) * Super-fast parallel installation/update * Support for lazy-loading * Branch/tag/commit support * Post-update, post-load hooks * Dependencies between packages * Unlike antigen, no ZSH plugin file (*.plugin.zsh) required * Interactive interface (fzf, peco, zaw, and so on) * Cache mechanism for reducing the startup time -- ChangZhuo Chen (陳昌倬) Debian Developer (https://nm.debian.org/public/person/czchen) Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B signature.asc Description: PGP signature
Bug#776938: sendfile: please make the build reproducible
Dear Maintainer, > Source: sendfile > Version: 2.1b.20080616-4.1 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777020: ucspi-tcp: please make the build reproducible
Dear Maintainer, > Source: ucspi-tcp > Version: 1:0.88-3 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#776940: cvs-mailcommit: please make the build reproducible
Dear Maintainer, > Source: cvs-mailcommit > Version: 1.19-2 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#834291: lv2-c++-tools: FTBFS: undefined reference to `boost::system::generic_category()'
Source: lv2-c++-tools Version: 1.0.5-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, lv2-c++-tools fails to build from source in unstable/amd64: [..] Selecting previously unselected package libxml2-utils. Preparing to unpack .../148-libxml2-utils_2.9.4+dfsg1-1+b1_amd64.deb ... Unpacking libxml2-utils (2.9.4+dfsg1-1+b1) ... Selecting previously unselected package libgtk2.0-dev. Preparing to unpack .../149-libgtk2.0-dev_2.24.30-4_amd64.deb ... Unpacking libgtk2.0-dev (2.24.30-4) ... Selecting previously unselected package libglibmm-2.4-dev:amd64. Preparing to unpack .../150-libglibmm-2.4-dev_2.48.1-1_amd64.deb ... Unpacking libglibmm-2.4-dev:amd64 (2.48.1-1) ... Selecting previously unselected package libpangomm-1.4-dev:amd64. Preparing to unpack .../151-libpangomm-1.4-dev_2.40.0-1_amd64.deb ... Unpacking libpangomm-1.4-dev:amd64 (2.40.0-1) ... Selecting previously unselected package libatkmm-1.6-dev:amd64. Preparing to unpack .../152-libatkmm-1.6-dev_2.24.2-1_amd64.deb ... Unpacking libatkmm-1.6-dev:amd64 (2.24.2-1) ... Selecting previously unselected package libgtkmm-2.4-dev:amd64. Preparing to unpack .../153-libgtkmm-2.4-dev_1%3a2.24.4-2+b1_amd64.deb ... Unpacking libgtkmm-2.4-dev:amd64 (1:2.24.4-2+b1) ... Setting up libedit2:amd64 (3.1-20150325-1+b1) ... Setting up libobjc4:amd64 (6.1.1-11) ... Setting up libgtk2.0-common (2.24.30-4) ... Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ... Setting up libmpx0:amd64 (5.4.1-1) ... Setting up libpng16-16:amd64 (1.6.24-2) ... Setting up libjbig0:amd64 (2.1-3.1) ... Setting up libpthread-stubs0-dev:amd64 (0.3-4) ... Setting up fonts-dejavu-core (2.36-1) ... Processing triggers for libglib2.0-0:amd64 (2.48.1-2) ... No schema files found: doing nothing. Setting up xorg-sgml-doctools (1:1.11-1) ... Setting up libxml2-utils (2.9.4+dfsg1-1+b1) ... Setting up libdirectfb-1.2-9:amd64 (1.2.10.0-5.2+b1) ... Setting up libgdk-pixbuf2.0-common (2.34.0-1) ... Setting up libasan2:amd64 (5.4.1-1) ... Setting up libdatrie1:amd64 (0.2.10-2) ... Setting up libtiff5:amd64 (4.0.6-2) ... Setting up x11proto-kb-dev (1.0.7-1) ... Setting up libboost1.61-dev:amd64 (1.61.0+dfsg-2.1) ... Setting up ucf (3.0036) ... Setting up libgirepository-1.0-1:amd64 (1.48.0-3) ... Setting up libfreetype6:amd64 (2.6.3-3+b1) ... Setting up libgraphite2-3:amd64 (1.3.8-1) ... Setting up libatk1.0-data (2.20.0-1) ... Setting up pkg-config (0.29-4) ... Setting up libpixman-1-0:amd64 (0.33.6-1) ... Setting up xtrans-dev (1.3.5-1) ... Setting up gir1.2-glib-2.0:amd64 (1.48.0-3) ... Setting up libglib2.0-data (2.48.1-2) ... Processing triggers for libc-bin (2.23-4) ... Setting up x11proto-xinerama-dev (1.2.1-2) ... Setting up libpixman-1-dev (0.33.6-1) ... Setting up libatk1.0-0:amd64 (2.20.0-1) ... Setting up x11proto-randr-dev (1.5.0-1) ... Setting up libgcc-5-dev:amd64 (5.4.1-1) ... Processing triggers for systemd (231-1) ... Setting up libexpat1-dev:amd64 (2.2.0-1) ... Processing triggers for man-db (2.7.5-1) ... Setting up shared-mime-info (1.6-1) ... Setting up libpcrecpp0v5:amd64 (2:8.39-1) ... Setting up libpcre32-3:amd64 (2:8.39-1) ... Setting up icu-devtools (57.1-2) ... Setting up libpcre16-3:amd64 (2:8.39-1) ... Setting up libboost-dev:amd64 (1.61.0.2) ... Setting up libthai-data (0.1.25-1) ... Setting up libjpeg62-turbo-dev:amd64 (1:1.5.0-1) ... Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ... Setting up x11-common (1:7.7+16) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of start. Setting up hicolor-icon-theme (0.15-1) ... Setting up libglib2.0-bin (2.48.1-2) ... Setting up libgraphite2-dev (1.3.8-1) ... Setting up libsigc++-2.0-0v5:amd64 (2.8.0-2) ... Setting up libx11-data (2:1.6.3-1) ... Setting up libxau6:amd64 (1:1.0.8-1) ... Setting up libdbus-1-3:amd64 (1.10.8-1) ... Setting up liblzo2-2:amd64 (2.08-1.2) ... Setting up libllvm3.6v5:amd64 (1:3.6.2-3) ... Setting up libavahi-common-data:amd64 (0.6.32-1) ... Setting up libstdc++-5-dev:amd64 (5.4.1-1) ... Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ... Setting up libobjc-5-dev:amd64 (5.4.1-1) ... Setting up libpcre3-dev:amd64 (2:8.39-1) ... Setting up gir1.2-atk-1.0 (2.20.0-1) ... Setting up fontconfig-config (2.11.0-6.5) ... Setting up x11proto-core-dev (7.0.29-1) ... Setting up libsigc++-2.0-dev:amd64 (2.8.0-2) ... Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ... Setting up libxau-dev:amd64 (1:1.0.8-1) ... Setting up libthai0:amd64 (0.1.25-1) ... Setting up libicu-dev (57.1-2) ... Setting up libglib2.0-dev (2.48.1-2) ... Setting up libclang1-3.6:amd64 (1:3.6
Bug#777179: p0f: please make the build reproducible
Dear Maintainer, > Source: p0f > Version: 2.0.8-2 > Tags: patch There hasn't seem to be any update on this bug in 555 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#776967: erc: please make the build reproducible
Dear Maintainer, > Source: erc > Version: 5.3-1ubuntu2 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777428: libtnt: please make the build reproducible
Dear Maintainer, > Source: libtnt > Version: 1.2.6-1 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#778951: prima: please make the build reproducible
Dear Maintainer, > Source: prima > Version: 1.28-1.3build1 > Tags: patch There hasn't seem to be any update on this bug in 539 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets
Control: clone -1 -2 -3 Control: retitle -1 psql ident without existing sys-user unclear error Control: tags -1 -moreinfo Control: retitle -2 psql incorrectly falls back to TCP in ident case Control: tags -1 -moreinfo Control: retitle -3 psql alters credentials with dbuser iso dbadmin Hi Christoph, On 13-08-16 23:22, Christoph Anton Mitterer wrote: > See below... went actually much faster than I'd have expected. Thanks, that was helpful (for the ident/peer case). And just to be sure, I assume everything we discuss here is done with the backported version of dbconfig. There are too many changes since Jessie to investigate that now (I may check once we identified all issues). > I think it already shows the possible problem that happens: >> populating database via sql... warning: ident method specified but local >> account doesn't exist. >> warning: ident method specified but local account doesn't exist. > > It thinks the account doesn't exist (which is correct, but doesn't > really matter) and I'd blindly assume now it falls back to TCP for this > reason? Yes, it does that by design and it does really matter. However, as seen in this bug, I guess it should just fail instead, right? We fill the database with the database user credentials to avoid the need for the administrator credentials (requiring the administrator credentials for anything that isn't strictly needing it is a bug¹ that I intent to close soon), so using the administrator credentials to solve this issue is a no-go. I wasn't aware of the possibility to have system-user to postgresql-user mapping, so I am afraid that we need an additional debconf question to ask for the system-user name that will be used for the connection in case of ident/peer. After writing the above, I found where the fallback to TCP happens: the logic of _dbc_psql_cmd_args checks for the password instead of the method. Should be easy to fix, but alone it will change the fallback from TCP/$dbc_dbuser to ident/root and still fail (I think). > populating database via sql... warning: ident method specified but local > account doesn't exist. > warning: ident method specified but local account doesn't exist. > su -s /bin/sh root -c "env HOME='/tmp/dbconfig-common.psql_home.RIlqrF' > PGPASSFILE='/tmp/dbconfig-common.psql_home.RIlqrF/.pgpass' PGSSLMODE='prefer' > psql --set \"ON_ERROR_STOP=1\" -q -h 'localhost' -U 'icinga' icinga" 2>&1. should have read icinga The user to use is here is determined by the _dbc_psql_local_username function in /usr/share/dbconfig-common/internal/pgsql. Could you also create the debugging info for the TCP issue you reported? I cloned this bug to separate out that issue and leave the moreinfo tag standing for that issue. Paul ¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475829 signature.asc Description: OpenPGP digital signature
Bug#777419: socklog: please make the build reproducible
Dear Maintainer, > Source: socklog > Version: 2.1.0-8 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#778431: tkrat: please make the build reproducible
Dear Maintainer, > Source: tkrat > Version: 1:2.2cvs20100105-true-dfsg-6ubuntu1 > Tags: patch There hasn't seem to be any update on this bug in 546 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777287: beav: please make the build reproducible
Dear Maintainer, > Source: beav > Version: 1:1.40-18build1 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#834292: gr-radar: FTBFS: estimator_cw_impl.h:49:36: error: 'constexpr' needed for in-class initialization of static data member
Source: gr-radar Version: 0.0.0.20160126-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, gr-radar fails to build from source in unstable/amd64: [..] Policy CMP0026 is not set: Disallow use of the LOCATION target property. Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy command to set the policy and suppress this warning. The LOCATION property should not be read from target "gnuradio-radar". Use the target name directly with add_custom_command, or use the generator expression $, as appropriate. Call Stack (most recent call first): python/CMakeLists.txt:65 (GR_ADD_TEST) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property): Policy CMP0045 is not set: Error on non-existent target in get_target_property. Run "cmake --help-policy CMP0045" for policy details. Use the cmake_policy command to set the policy and suppress this warning. get_target_property() called with non-existent target "/usr/bin/python2". Call Stack (most recent call first): python/CMakeLists.txt:65 (GR_ADD_TEST) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property): Policy CMP0045 is not set: Error on non-existent target in get_target_property. Run "cmake --help-policy CMP0045" for policy details. Use the cmake_policy command to set the policy and suppress this warning. get_target_property() called with non-existent target "/home/lamby/temp/cdt.20160814095335.F8ZHT3Njfu.db.gr-radar/gr-radar-0.0.0.20160126/python/qa_ofdm_divide_vcvc.py". Call Stack (most recent call first): python/CMakeLists.txt:65 (GR_ADD_TEST) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property): Policy CMP0026 is not set: Disallow use of the LOCATION target property. Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy command to set the policy and suppress this warning. The LOCATION property should not be read from target "gnuradio-radar". Use the target name directly with add_custom_command, or use the generator expression $, as appropriate. Call Stack (most recent call first): python/CMakeLists.txt:66 (GR_ADD_TEST) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property): Policy CMP0045 is not set: Error on non-existent target in get_target_property. Run "cmake --help-policy CMP0045" for policy details. Use the cmake_policy command to set the policy and suppress this warning. get_target_property() called with non-existent target "/usr/bin/python2". Call Stack (most recent call first): python/CMakeLists.txt:66 (GR_ADD_TEST) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property): Policy CMP0045 is not set: Error on non-existent target in get_target_property. Run "cmake --help-policy CMP0045" for policy details. Use the cmake_policy command to set the policy and suppress this warning. get_target_property() called with non-existent target "/home/lamby/temp/cdt.20160814095335.F8ZHT3Njfu.db.gr-radar/gr-radar-0.0.0.20160126/python/qa_os_cfar_2d_vc.py". Call Stack (most recent call first): python/CMakeLists.txt:66 (GR_ADD_TEST) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property): Policy CMP0026 is not set: Disallow use of the LOCATION target property. Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy command to set the policy and suppress this warning. The LOCATION property should not be read from target "gnuradio-radar". Use the target name directly with add_custom_command, or use the generator expression $, as appropriate. Call Stack (most recent call first): python/CMakeLists.txt:67 (GR_ADD_TEST) This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property): Policy CMP0045 is not set: Error on non-existent target in get_target_property. Run "cmake --help-policy CMP0045" for policy details. Use the cmake_policy command to set the policy and suppress this wa
Bug#779164: khmerconverter: please make the build reproducible
Dear Maintainer, > Source: khmerconverter > Version: 1.4-1 > Tags: patch There hasn't seem to be any update on this bug in 536 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#778216: uclibc: please make the build reproducible
Dear Maintainer, > Source: uclibc > Version: 0.9.32-1 > Tags: patch There hasn't seem to be any update on this bug in 548 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777357: yocto-reader: please make the build reproducible
Dear Maintainer, > Source: yocto-reader > Version: 0.9.4 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#790355: hylafax: please make the build reproducible
Dear Maintainer, > Source: hylafax > Version: 3:6.0.6-6 > Tags: patch There hasn't seem to be any update on this bug in 412 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#778946: madlib: please make the build reproducible
Dear Maintainer, > Source: madlib > Version: 1.3.0-2.1 > Tags: patch There hasn't seem to be any update on this bug in 539 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777290: biff: please make the build reproducible
Dear Maintainer, > Source: biff > Version: 1:0.17.pre2412-5 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#779166: gnarwl: please make the build reproducible
Dear Maintainer, > Source: gnarwl > Version: 3.6.dfsg-6.2ubuntu1 > Tags: patch There hasn't seem to be any update on this bug in 536 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777409: ftpcopy: please make the build reproducible
Dear Maintainer, > Source: ftpcopy > Version: 0.6.7-2 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#779061: udev-discover: please make the build reproducible
Dear Maintainer, > Source: udev-discover > Version: 0.2.2-1 > Tags: patch There hasn't seem to be any update on this bug in 537 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#834296: Dependencies mixed up between voctomix and voctomix-core
Package: voctomix-core Version: 0.3.1-1.1 As the author of voctomix I'd like to report, that the Dependencies between voctomix and voctomix-core are a little bit mixed up. As far as I can see, the voctomix-Package contains the example scripts. The following dependencies/suggest, that are currently on voctomix-core are only required to run the example scripts and are not required for the voctomix-core. These should be moved to the voctomix package: - gstreamer1.0-tools - fbset - python3-pyinotify - gstreamer1.0-libav - rlwrap Peter signature.asc Description: OpenPGP digital signature
Bug#827245: [Pkg-libvirt-maintainers] Bug#827245: missing backend for pool type 11 (zfs)
On Sun, Aug 14, 2016 at 06:15:25PM +1000, Craig Sanders wrote: > Tyler Fenby wrote: > > I can confirm that the ZFS backend works as expected on Debian after > > recompiling libvirt with only a couple lines added to debian/rules to > > enable the configure flag. > > thanks for looking into this. > > I cloned libvirt from git://anonscm.debian.org/pkg-libvirt/libvirt.git > when i first submitted the bug report, and installed all the build-deps > but whenever I try to compile it, I just gets lots of errors about > redeclarations. > > compiling on sid with dpkg-buildpackage -b -us -uc: > > ... > enum VIR_TYPED_PARAM_UINT from > /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h > redeclared in > /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h > enum VIR_TYPED_PARAM_STRING_OKAY from > /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h > redeclared in > /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h > enum VIR_CONNECT_CLOSE_REASON_ERROR from > /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h > redeclared in > /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h > enum VIR_TYPED_PARAM_LLONG from > /home/cas/git/forks/libvirt/libvirt/debian/build/docs/../include/libvirt/libvirt-common.h > redeclared in > /home/cas/git/forks/libvirt/libvirt/docs/../include/libvirt/libvirt-common.h > Makefile:2307: recipe for target '../../../docs/apibuild.py.stamp' failed > make[3]: *** [../../../docs/apibuild.py.stamp] Error 2 > make[3]: Leaving directory > '/home/cas/git/forks/libvirt/libvirt/debian/build/docs' > Makefile:2001: recipe for target 'all-recursive' failed > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory '/home/cas/git/forks/libvirt/libvirt/debian/build' > Makefile:1898: recipe for target 'all' failed > make[1]: *** [all] Error 2 > make[1]: Leaving directory '/home/cas/git/forks/libvirt/libvirt/debian/build' > dh_auto_build: make -j1 returned exit code 2 > debian/rules:131: recipe for target 'build' failed > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > The changes required to enable ZFS support seem obvious and > straight-forward. maybe i should try building in a jessie or testing VM? It builds find in a uptodate pbuilder chroot so no idea what happens. Maybe it clashes with a installed libvirt-dev package? I've pushed the changes to enable zfs pool support on kfreebsd. Cheers, -- Guido
Bug#834263: dbconfig-pgsql: "ident" auth method with UNIX sockets
Control: tags -1 moreinfo Hi On 13-08-16 23:31, Christoph Anton Mitterer wrote: > When having UNIX sockets in dbconfig-common, it still uses the term "ident" as > the auth mode. Could you be a bit more verbose what you find this? The debconf questions should be correct nowadays. > But it should be noticed that "peer" as a actual name is only available > since postgresql 9.1 (though all older versions are upstream unsupported), > so when an older version is used "peer" is not understood by postgresql. > Anyway I don't think this is anyhow specified/used when dbconfig invokes > postgresql, or is it? If I understand correctly from the response I got half a year ago from the PostgreSQL maintainer, it doesn't matter what it is called. The behavior hasn't changed AFAIK. Paul signature.asc Description: OpenPGP digital signature
Bug#786755: reprotest provides this feature…
Hi, [11:27] < pabs> 09:18:15> should we close #786755 in devscripts with a Suggests: reprotest? [11:27] < zwiebelbot> 09:18:19> Debian#786755: devscripts: please include a reproducible builds script - https://bugs.debian.org/786755 [11:27] < pabs> 09:18:22> ceridwen: ^ [11:27] < pabs> 09:19:38> or Recommends perhaps? I think a suggest would be fine, at least for now. Maybe this could become a recommends: once reproducible builds are a reality (and not a QA project) in Debian… -- cheers, Holger signature.asc Description: Digital signature
Bug#834266: dbconfig-pgsql: support specifying the socket dir and socket "port"
Control: tags -1 confirmed On 13-08-16 23:36, Christoph Anton Mitterer wrote: > Severity: wishlist Ack. I have considered this since Debconf 15 but decided it was not on the top of my list. > As of now it seems, on cannot configure the socket dir and "port" that is > used by dbconfig, when UNIX sockets are used with postgresql. Correct. > Instead it seems it would always use /var/run/postgresql/.s.PGSQL.5432. It just calls the psql command line tool and doesn't specify anything specific on this front (yet), so uses whatever psql is using. Paul signature.asc Description: OpenPGP digital signature
Bug#797539: cadabra: please make the build reproducible
Hi, > > Would you consider applying this patch and uploading? > I'd really appreciate it if you could NMU it Chris. I would, but I can't seem to find a solution to #808634 right this second.. If you could follow up to that, then I would be happy to. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#808634: cadabra: FTBFS: manipulator.hh: fatal error: sigc++/object.h: No such file or directory
> fatal error: sigc++/object.h: No such file or directory Some more info: $ pkg-config modglue --cflags -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include sigc++/object.h is not in libsigc++-2.0-dev but it is in libsigc++-1.2-dev. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#776941: dh-kpatches: please help make builds reproducible
Dear Maintainer, > Source: dh-kpatches > Version: 0.99.36+nmu2 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777009: debian-builder: please make the build reproducible
Dear Maintainer, > Source: debian-builder > Version: 1.8 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777403: leave: please make the build reproducible
Dear Maintainer, > Source: leave > Version: 1.12-2 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777297: ccze: please make the build reproducible
Dear Maintainer, > Source: ccze > Version: 0.2.1-2ubuntu1 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777297: ccze: please make the build reproducible
Dear Maintainer, > Source: ccze > Version: 0.2.1-2ubuntu1 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777398: ssmtp: please make the build reproducible
Dear Maintainer, > Source: ssmtp > Version: 2.64-8 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777364: vmm: please make the build reproducible
Dear Maintainer, > Source: vmm > Version: 0.6.2-1 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777008: uucpsend: please make the build reproducible
#Dear Maintainer, > Source: uucpsend > Version: 1.1-4 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777417: ipsvd: please make the build reproducible
Dear Maintainer, > Source: ipsvd > Version: 1.0.0-3 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#776876: daemontools: please make the build reproducible
Dear Maintainer, > Source: daemontools > Version: 1:0.76-6ubuntu1 > Tags: patch There hasn't seem to be any update on this bug in 558 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777282: aewm++-goodies: please make the build reproducible
Dear Maintainer, > Source: aewm++-goodies > Version: 1.0-9 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#834297: lv2-c++-tools: FTBFS with new boost
Package: src:lv2-c++-tools Version: 1.0.5-2 Severity: serious Dear maintainer: This package currently fails to build from source in stretch: -- g++ programs/lv2peg/lv2peg.o -Llibraries/paq/ -lpaq -Wl,-z,relro -o programs/lv2peg/lv2peg programs/lv2peg/lv2peg.o: In function `__static_initialization_and_destruction_0': /usr/include/boost/system/error_code.hpp:221: undefined reference to `boost::system::generic_category()' /usr/include/boost/system/error_code.hpp:222: undefined reference to `boost::system::generic_category()' /usr/include/boost/system/error_code.hpp:223: undefined reference to `boost::system::system_category()' collect2: error: ld returned 1 exit status Makefile.template:236: recipe for target 'programs/lv2peg/lv2peg' failed make[2]: *** [programs/lv2peg/lv2peg] Error 1 make[2]: Leaving directory '/build/lv2-c++-tools-JBIRzR/lv2-c++-tools-1.0.5' dh_auto_build: make -j1 returned exit code 2 debian/rules:10: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/build/lv2-c++-tools-JBIRzR/lv2-c++-tools-1.0.5' -- Full build log available here: https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/lv2-c++-tools_1.0.5-2.rbuild.log Thanks.
Bug#777430: pixmap: please make the build reproducible
Dear Maintainer, > Source: pixmap > Version: 2.6pl4-18ubuntu1 > Tags: patch There hasn't seem to be any update on this bug in 553 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#776949: fake: please make the build reproducible
Dear Maintainer, > Source: fake > Version: 1.1.11-1 > Tags: patch There hasn't seem to be any update on this bug in 557 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777446: gpsmanshp: please make the build reproducible
Dear Maintainer, > Source: gpsmanshp > Version: 1.2-5 > Tags: patch There hasn't seem to be any update on this bug in 552 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#779135: sgabios: please make the build reproducible
Dear Maintainer, > Source: sgabios > Version: 0.0~svn8-3 > Tags: patch There hasn't seem to be any update on this bug in 536 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#797543: xotcl: please make the build reproducible
Dear Maintainer, > Source: xotcl > Version: 1.6.8-1 > Tags: patch There hasn't seem to be any update on this bug in 348 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#777486: mimefilter: please make the build reproducible
Dear Maintainer, > Source: mimefilter > Version: 1.7 > Tags: patch There hasn't seem to be any update on this bug in 552 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
severity 834220 minor thanks Hi, On Sat, Aug 13, 2016 at 02:34:32PM +0200, Thomas Hackert wrote: > > On Sat, Aug 13, 2016 at 12:19:44PM +0200, Thomas Hackert wrote: > > > while trying to get a backtrace for a crash with an installed > > > extension, I started LO from command line with "soffice > > > --backtrace". To my astonishment LO crashes, when > > > > You mean it only happens with --backtrace or also without? Your title > > suggests the first. > > Yes. It only happens if I start LO from command line with "soffice > --backtrace". OK, then IMHO it's even minor, since normal users won't do that :) > > But yes, if you want a --backtrace, you DO need the -dbgsym packages. They > > contain the debug symbols. Without them a backtrace not very useful. > > But still it should not crash immediately ... ;) That's true. I was aiming at your "I don't want to install the -dbgsym packages". Regards, Rene
Bug#834298: nis: Can't ypbind
Package: nis Version: 3.17-35 Severity: grave Justification: renders package unusable Hi, since 3.17-35 I can't bind to my nisserver anymore. Downgrading to 3.17-34 succeeded. Please notice: 3.17-35: # ldd $(which ypbind) linux-vdso.so.1 (0x7ffdb879f000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f8380e26000) libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7f8380c0e000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f838086c000) /lib64/ld-linux-x86-64.so.2 (0x56204e973000) 3.17-34: # ldd $(which ypbind) linux-vdso.so.1 (0x7ffe2a7f6000) libslp.so.1 => /usr/lib/x86_64-linux-gnu/libslp.so.1 (0x7f71748d1000) libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 (0x7f71746aa000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7f717445a000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7f7174207000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7f7173ef6000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f7173cd8000) libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7f7173ac) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f717371f000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7f7173396000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7f717330e000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7f7173105000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f7172e92000) /lib64/ld-linux-x86-64.so.2 (0x556d37459000) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7f7172c8e000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f7172a73000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7f717284b000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7f7172634000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f717242c000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f7172208000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f7171ef9000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f7171cf5000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7f7171ae) I tried ypbind-mt-1.38 as well which binds just fine, though. -- Elimar -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-galadriel-lxtec-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nis depends on: ii debconf [debconf-2.0] 1.5.59 ii hostname 3.18 ii libc6 2.23-4 ii libdbus-1-31.10.8-1 ii libdbus-glib-1-2 0.106-1 ii libgdbm3 1.8.3-14 ii libglib2.0-0 2.48.1-2 ii libslp11.2.1-11 ii lsb-base 9.20160629 ii make-guile [make] 4.1-9 ii netbase5.3 ii rpcbind [portmap] 0.2.3-0.5 nis recommends no packages. Versions of packages nis suggests: pn nscd
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
On Sat, Aug 13, 2016 at 02:47:22PM +0200, Thomas Hackert wrote: > it is only 4k in size and empty, but I will attach it to this mail. If it's empty, well you don't need a empty file.. But most probably reportbug-ng failed again. What a surprise. NOT. Maybe you should use reportbug again? common sense says that ypu don't need to do that ;) Anyways, in your initial post you said "while trying to get a backtrace for a crash with an installed extension,"... So please list me all installed extensions. (reportbug would have done so...) /usr/lib/libreoffice/program/unopkg list /usr/lib/libreoffice/program/unopkg list --shared /usr/lib/libreoffice/program/unopkg list --bundled In any case, it is almost impossible to "support" any random extension in any random development state here. They can do so much and also cause crashes.. Did you try withot the extension? (I see you moved the user dir, so a user-installed one should have gone away - but maybe you installed some not in Debian system-wide?) Regards, Rene
Bug#834273: kmailtransport: FTBFS in testing
¡Hola Santiago! El 2016-08-14 a las 02:24 +0200, Santiago Vila escribió: Package: src:kmailtransport Version: 16.04.2-2 Severity: serious This package currently fails to build from source in stretch: -- cd /build/kmailtransport-16.04.2/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DKCOREADDONS_LIB -DKF5MailTransport_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB -DTRANSLATION_DOMAIN=\"libmailtransport5\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/build/kmailtransport-16.04.2/obj-x86_64-linux-gnu/src -I/build/kmailtransport-16.04.2/src -isystem /usr/include/KF5/KWallet -isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem /usr/include/KF5/AkonadiCore -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KItemModels -isystem /usr/include/KF5/KMime -isystem /usr/include/KF5/Akonadi/KMime -isystem /usr /include/KF5/akonadi/kmime -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KService -isystem /usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KAuth -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/KF5/KCompletion -g -O2 -fdebug-prefix-map=/build/kmailtransport-16.04.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -pedantic -fPIC -fvisibility=hid den -fvisibility-inlines-hidden -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -fPIC -fexceptions -o CMakeFiles/KF5MailTransport.dir/resourcesendjob.cpp.o -c /build/kmailtransport-16.04.2/src/resourcesendjob.cpp In file included from /usr/include/KF5/AkonadiCore/exception.h:28:0, from /usr/include/KF5/AkonadiCore/item.h:26, from /build/kmailtransport-16.04.2/src/filteractionjob_p.h:25, from /build/kmailtransport-16.04.2/src/outboxactions_p.h:24, from /build/kmailtransport-16.04.2/src/outboxactions.cpp:20: /usr/include/KF5/AkonadiCore/std_exception.h:1:40: fatal error: /usr/include/c++/5/exception: No such file or directory #include "/usr/include/c++/5/exception" ^ compilation terminated. -- This issue is caused by akonadi, and the migration to g++-6, the file /usr/include/KF5/AkonadiCore/std_exception.h is generated and includes the mentioned full path (/usr/include/c++/5/exception or /usr/include/c++/6/exception), which is a bad idea (tm)... I've uploaded new version of akonadi that will be compiled against g++-6, and this issue will be solved when akonadi migrates to stretch. If I have the time, I would like to fix the generated std_exception.h so this is not a problem in future g++ upgrades. There are full logs available here: https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/kmailtransport.html Happy hacking, -- "Brilliant opportunities are cleverly disguised as insolvable problems." -- Gardener's Philosophy "The reverse is also true." -- Corollary Saludos /\/\ /\ >< `/ signature.asc Description: Digital signature
Bug#834299: reprotest: please include README.md in the binary package
Package: reprotest Severity: wishlist The README.md file from the source package is very helpful for understanding how to interact with reprotest, please include it in the reprotest binary package. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#834300: reprotest: binary package includes copies of autopkgtest-* manual pages
Package: reprotest
Version: 0.2
Severity: minor
Usertags: embed
The reprotest binary package includes copies of the autopkgtest-*
manual pages under its own directory that is outside the normal paths
for manual pages. The code for reprotest doesn't appear to use them.
$ dpkg -L reprotest | grep 1
/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-chroot.1
/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-lxc.1
/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-lxd.1
/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-null.1
/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-qemu.1
/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-schroot.1
/usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-ssh.1
$ apt-file search -x 'autopkgtest-.*\.1'
autopkgtest: /usr/share/man/man1/autopkgtest-build-lxc.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-build-lxd.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-buildvm-ubuntu-cloud.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-chroot.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-lxc.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-lxd.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-null.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-qemu.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-schroot.1.gz
autopkgtest: /usr/share/man/man1/autopkgtest-ssh.1.gz
reprotest: /usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-chroot.1
reprotest: /usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-lxc.1
reprotest: /usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-lxd.1
reprotest: /usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-null.1
reprotest: /usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-qemu.1
reprotest: /usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-schroot.1
reprotest: /usr/lib/python3/dist-packages/reprotest/virt/autopkgtest-ssh.1
$ dpkg -L reprotest | xargs zgrep -F .1 | grep -v copyright
/usr/lib/python3/dist-packages/reprotest/lib/VirtSubproc.py:
time.sleep(0.1)
/usr/lib/python3/dist-packages/reprotest/lib/VirtSubproc.py:
time.sleep(0.1)
/usr/lib/python3/dist-packages/reprotest/lib/VirtSubproc.py:
time.sleep(0.1)
/usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py:
time.sleep(0.1)
/usr/lib/python3/dist-packages/reprotest/virt/qemu:s =
socket.create_connection(('127.0.0.1', p))
/usr/lib/python3/dist-packages/reprotest/virt/ssh:time.sleep(0.1)
/usr/lib/python3/dist-packages/reprotest-0.2.egg-info/PKG-INFO:Metadata-Version:
1.1
/usr/share/doc/reprotest/changelog.gz:reprotest (0.1) unstable; urgency=medium
-- System Information:
Debian Release: stretch/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages reprotest depends on:
ii apt-utils 1.3~pre3
ii diffoscope 56
ii libdpkg-perl1.18.10
ii procps 2:3.3.12-2
ii python3-debian 0.1.28
pn python3:any
Versions of packages reprotest recommends:
ii autodep8 0.7.1
ii disorderfs 0.4.3-1
ii locales-all 2.23-4
pn qemu-system
ii qemu-utils 1:2.6+dfsg-3
ii schroot 1.6.10-2+b1
reprotest suggests no packages.
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#834220: libreoffice: Reproducible after installing LanguageTool extension in a clean environment
Package: libreoffice
Version: 1:5.1.5~rc2-1
Followup-For: Bug #834220
Hello Rene, *,
I have tried to reproduce this bug in a clean environment (I hope
you count a Debian installation in VirtualBox as "Clean" ... ;) ):
1. Downloaded
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
and created a Debian VM in VirtualBox
2. Installed it in "Expert GUI mode" and selected XFCE as well as
KDE as DEs
3. After the installation was finished, I started LO from command
line ("soffice --backtrace") - leads to a "gbd>" promt
4. Started "soffice" (without "--backtrace") to see if LO wants to
recover something
5. Started "soffice --backtrace" - LO started
6. Neither + nor click on any module crashes LO
7. Downloaded
http://extensions.libreoffice.org/extension-center/texmaths-1/releases/0.42/texmaths-0-42.oxt
and installed it in LO
8. Closed LO and restarted it with "soffice --backtrace" - no crash
with + or any click on one of the modules
9. Downloaded https://languagetool.org/download/LanguageTool-3.4.oxt
and installed it in LO
10. In LO "Tools - LanguageTool - Options" and click on "Help"
button shows a long warning
11. Closed LO
12. Started LO with again "soffice --backtrace"
13. + - crash
So, this crash only appears after installing the LanguageTool
extension - but I am still confused as it crashes LO with the
"--backtrace" parameter from command line as well ... :( LO's own
version 5.1.5.2, 5.2.0.4 or 5.2.1.1 does not show this crash - even
with installed LanguageTool extension.
Do you need any further information? I have only added
deb http://ftp.de.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.debian.org/debian/ testing main contrib non-free
to /etc/apt/sources.list (without an additional "apt-get update &
apt-get upgrade" to reproduce it with Testing's LO version ... ;)
Have a nice day
Thomas.
-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.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 /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libreoffice depends on:
ii dpkg 1.18.10
ii fonts-dejavu 2.36-1
ii fonts-sil-gentium-basic1.1-7
ii libreoffice-avmedia-backend-gstreamer 1:5.1.5~rc2-1
ii libreoffice-base 1:5.1.5~rc2-1
ii libreoffice-calc 1:5.1.5~rc2-1
ii libreoffice-core 1:5.1.5~rc2-1
ii libreoffice-draw 1:5.1.5~rc2-1
ii libreoffice-impress1:5.1.5~rc2-1
ii libreoffice-java-common1:5.1.5~rc2-1
ii libreoffice-math 1:5.1.5~rc2-1
ii libreoffice-report-builder-bin 1:5.1.5~rc2-1
ii libreoffice-writer 1:5.1.5~rc2-1
ii python3-uno1:5.1.5~rc2-1
libreoffice recommends no packages.
Versions of packages libreoffice suggests:
ii cups-bsd2.1.4-4
ii default-jre [java5-runtime] 2:1.8-57
ii gstreamer1.0-libav 1.8.2-1
pn gstreamer1.0-plugins-bad
ii gstreamer1.0-plugins-base 1.8.2-1
ii gstreamer1.0-plugins-good 1.8.2-1
ii gstreamer1.0-plugins-ugly 1.8.2-1
ii hunspell-de-at [hunspell-dictionary]20160407-1
ii hunspell-de-ch [hunspell-dictionary]20160407-1
ii hunspell-de-de [hunspell-dictionary]20160407-1
ii hunspell-en-us [hunspell-dictionary]20070829-6
ii hyphen-de [hyphen-hyphenation-patterns] 1:5.1.3-2
ii hyphen-en-us [hyphen-hyphenation-patterns] 2.8.8-3
ii iceweasel 45.2.0esr-1
ii imagemagick 8:6.8.9.9-7.2
ii libgl1-mesa-glx [libgl1]11.2.2-1
pn libreoffice-grammarcheck
ii libreoffice-help-de [libreoffice-help-5.1] 1:5.1.5~rc2-1
ii libreoffice-help-en-us [libreoffice-help-5.1] 1:5.1.5~rc2-1
ii libreoffice-kde 1:5.1.5~rc2-1
ii libreoffice-l10n-de [libreoffice-l10n-5.1] 1:5.1.5~rc2-1
pn libreoffice-officebean
ii libsane 1.0.25-2+b1
ii libxrender1 1:0.9.9-2
pn myspell-dictionary
ii mythes-de [mythes-thesaurus]20160424-3
ii mythes-de-ch [mythes-thesaurus] 20160424-3
ii mythes-en-us [mythes-thesaurus] 1:5.1.3-2
pn openclipart2-libreoffice | openclipart-libreoffice
ii openjdk-8-jre [java5-runtime]
Bug#834273: kmailtransport: FTBFS in testing
On Sun, Aug 14, 2016 at 12:14:55PM +0200, Maximiliano Curia wrote: > I've uploaded new version of akonadi that will be compiled against g++-6, > and this issue will be solved when akonadi migrates to stretch. Please consider also an upload of kmailtransport having a versioned Build-Depends: akonadi (>= version-that-does-not-make-kmailtransport-to-fail) so that in case this version arrives at testing before the fixed akonadi version, I will get a "build-dependencies not met" error, which is a lot nicer than the FTBFS error. Thanks.
Bug#834296: Dependencies mixed up between voctomix and voctomix-core
control: tags -1 + pending Hi Peter, On Sun, Aug 14, 2016 at 11:12:00AM +0200, Peter Körner wrote: > As the author of voctomix I'd like to report, that the Dependencies > between voctomix and voctomix-core are a little bit mixed up. > > As far as I can see, the voctomix-Package contains the example scripts. > The following dependencies/suggest, that are currently on voctomix-core > are only required to run the example scripts and are not required for > the voctomix-core. These should be moved to the voctomix package: > > - gstreamer1.0-tools > - fbset > - python3-pyinotify > - gstreamer1.0-libav > - rlwrap thanks for your nice bug and clear report, I've just committted the fix to git and will soon upload this. btw, looking at the recent commits I've seen that configuration files in /etc/voctomix are now also being considered, which is a feature I think would be worth a 0.3.2 release alone! -- cheers, Holger signature.asc Description: Digital signature
Bug#834301: ruby-fog-rackspace and ruby-fog: error when trying to install together
Package: ruby-fog,ruby-fog-rackspace Version: ruby-fog/1.37.0-1 Version: ruby-fog-rackspace/0.1.1-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2016-08-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 46% Extracting templates from packages: 92% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libyaml-0-2:amd64. (Reading database ... 10961 files and directories currently installed.) Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ... Unpacking libyaml-0-2:amd64 (0.1.6-3) ... Selecting previously unselected package gcc-6-base:amd64. Preparing to unpack .../gcc-6-base_6.1.1-11_amd64.deb ... Unpacking gcc-6-base:amd64 (6.1.1-11) ... Setting up gcc-6-base:amd64 (6.1.1-11) ... (Reading database ... 10975 files and directories currently installed.) Preparing to unpack .../libstdc++6_6.1.1-11_amd64.deb ... Unpacking libstdc++6:amd64 (6.1.1-11) over (4.8.2-19) ... Processing triggers for libc-bin (2.23-4) ... Setting up libstdc++6:amd64 (6.1.1-11) ... Processing triggers for libc-bin (2.23-4) ... Selecting previously unselected package libssl1.0.2:amd64. (Reading database ... 10989 files and directories currently installed.) Preparing to unpack .../libssl1.0.2_1.0.2h-1_amd64.deb ... Unpacking libssl1.0.2:amd64 (1.0.2h-1) ... Selecting previously unselected package libgcrypt20:amd64. Preparing to unpack .../libgcrypt20_1.7.2-2_amd64.deb ... Unpacking libgcrypt20:amd64 (1.7.2-2) ... Selecting previously unselected package libicu57:amd64. Preparing to unpack .../libicu57_57.1-2_amd64.deb ... Unpacking libicu57:amd64 (57.1-2) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.4+dfsg1-1+b1_amd64.deb ... Unpacking libxml2:amd64 (2.9.4+dfsg1-1+b1) ... Selecting previously unselected package openssl. Preparing to unpack .../openssl_1.0.2h-1_amd64.deb ... Unpacking openssl (1.0.2h-1) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../ca-certificates_20160104_all.deb ... Unpacking ca-certificates (20160104) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ... Unpacking libffi6:amd64 (3.2.1-4) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.1.1+dfsg-1_amd64.deb ... Unpacking libgmp10:amd64 (2:6.1.1+dfsg-1) ... Selecting previously unselected package libxslt1.1:amd64. Preparing to unpack .../libxslt1.1_1.1.28-4_amd64.deb ... Unpacking libxslt1.1:amd64 (1.1.28-4) ... Selecting previously unselected package rubygems-integration. Preparing to unpack .../rubygems-integration_1.10_all.deb ... Unpacking rubygems-integration (1.10) ... Selecting previously unselected package ruby-did-you-mean. Preparing to unpack .../ruby-did-you-mean_1.0.0-2_all.deb ... Unpacking ruby-did-you-mean (1.0.0-2) ... Selecting previously unselected package ruby-minitest. Preparing to unpack .../ruby-minitest_5.9.0-1_all.deb ... Unpacking ruby-minitest (5.9.0-1) ... Selecting previously unselected package ruby-net-telnet. Preparing to unpack .../ruby-net-telnet_0.1.1-2_all.deb ... Unpacking ruby-net-telnet (0.1.1-2) ... Selecting previously unselected package ruby-power-assert. Preparing to unpack .../ruby-power-assert_0.3.0-1_all.deb ... Unpacking ruby-power-assert (0.3.0-1) ... Selecting previously unselected package ruby-test-unit. Preparing to unpack .../ruby-test-unit_3.1.7-2_all.deb ... Unpacking ruby-test-unit (3.1.7-2) ... Selecting previously unselected package libruby2.3:amd64. Preparing to unpack .../libruby2.3_2.3.1-5_amd64.deb ... Unpacking libruby2.3:amd64 (2.3.1-5) ... Selecting previously unselected package ruby2.3. Preparing to unpack .../ruby2.3_2.3.1-5_amd64.deb ... Unpacking ruby2.3 (2.3.1-5) ... Selecting previously unselected package ruby. Preparing to unpack .../ruby_1%3a2.3.0+4_amd64.deb ... Unpacking ruby (1:2.3.0+4) ... Selecting previously unselected package rake. Preparing to unpack .../archives/rake_10.5.0-2_all.deb ... Unpacking rake (10.5.0-2) ... Selecting previously unselected package ruby-blankslate. Preparing to unpack .../ruby-blankslate_3.1.3-1_all.deb ... Unpacking ruby-blankslate (3.1.3-1) ... Selecting previously unselected package ruby-builder. Preparing to unpack .../ruby-builder_3.2.2-4_all.deb ... Unpacking ruby-builder (3.2.2-4) ... Selecting previously unselected package ruby-cfpropertylist. Preparing to unpack .../ruby-cfpropertylist_2.2.8-1_all.deb ... Unpacking ruby-cfpropertylist (2.2.8-1) ... Selecting previously unselected package ruby-excon. Preparing to unpack .../ruby-excon_0.49.0-2_all.deb ... Unpacking ruby-excon (0.49.0-2) ... Selecting previously unselected package ruby-fission. Preparing to unpack .../rub
Bug#745027: Status
Hello Markus, On 2016/08/12 21:59, Markus Unterwaditzer wrote: > > I see that you have added a few patches to your Debian package. > > > 0001-Do-not-require-setuptools-scm.patch > > I couldn't find how you're getting the sourcecode, but this should not be > necessary if you're using the tarballs from PyPI. See > https://vdirsyncer.pimutils.org/en/stable/packaging.html#obtaining-the-source-code > > It appears that python3-setuptools-scm is also available in Debian, so adding > it as build dependency (instead of runtime dependency) should be possible. > > It seems that this is a bit unclear as I've discovered a similar patch in > Fedora. Please rather reach out and discuss things with me before doing this. > I'm saying this because I suspect that the metadata for the installed package > will be wrong (Python software can query the installed version of a package > with the `pkg_resources` module) because setup.py now doesn't contain any > version information. I have reworked to use Pypi instead and keep setuptools_scm in place. > ... > > 0003-Skip-ssl-tests.patch > > This might be caused by the `HTTP_PROXY` and `HTTPS_PROXY` envvars. I'd try > unsetting them in the build environment. These variables are not set, I don't know why it's trying to use proxy (maybe it somehow finds out there's no network access so this is a fallback?) > > > 0004-Include-license-from-copyright-file.patch > > As far as I understand, this is including this file: > https://github.com/fpytloun/debian-vdirsyncer/blob/master/debian/copyright > > However, the LICENSE file should be included in the PyPI package. License files are autogenerated from d/copyright and shipped with every package. So it should not be included in package directly (eg. like in this case) but just referenced or included (see patch content) otherwise Lintian will complain. > > Please do reach out if you encounter problems. Thank you for your feedback. Filip signature.asc Description: Digital signature
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
Hello Rene, *, On Sun, Aug 14, 2016 at 12:01:15PM +0200, Rene Engelhard wrote: > On Sat, Aug 13, 2016 at 02:34:32PM +0200, Thomas Hackert wrote: > > > On Sat, Aug 13, 2016 at 12:19:44PM +0200, Thomas Hackert wrote: > > > > while trying to get a backtrace for a crash with an installed > > > > extension, I started LO from command line with "soffice > > > > --backtrace". To my astonishment LO crashes, when > > > > > > You mean it only happens with --backtrace or also without? Your title > > > suggests the first. > > > > Yes. It only happens if I start LO from command line with "soffice > > --backtrace". > > OK, then IMHO it's even minor, since normal users won't do that :) Well, but people in QA at LO or some users trying to get a backtrace to report a bug ... ;) > > > But yes, if you want a --backtrace, you DO need the -dbgsym packages. They > > > contain the debug symbols. Without them a backtrace not very useful. > > > > But still it should not crash immediately ... ;) > > That's true. I was aiming at your "I don't want to install the -dbgsym > packages". But how do I install the debug packages? Neither "apt-cache search libreoffice dbg" or "libreoffice debug" show anything. "apt-cache search dbgsym" does only show mariadb, openhpi packages and owfs-dbg ... :( Do I need an special entry to my sources.list? Have a nice day Thomas. -- Yeah, well that's why it's numbered 2.3.1... it's for those of us who miss NT-like uptimes
Bug#834296: Dependencies mixed up between voctomix and voctomix-core
Hi Holger, On 14.08.2016 12:28, Holger Levsen wrote: > btw, looking at the recent commits I've seen that configuration files in > /etc/voctomix are now also being considered, which is a feature I think would > be worth a 0.3.2 release alone! That's nothing new and already since 0.1 like this: https://github.com/voc/voctomix/blob/0.1/voctocore/lib/config.py#L13 Compare that to the 0.3.1 version: https://github.com/voc/voctomix/blob/0.3.1/voctocore/lib/config.py#L12 I do however plan to do a 0.4 release after FOSS4G in ~3 Weeks with some new features. Let's continue this on IRC, not here where it doesn't belong. Regards, Peter signature.asc Description: OpenPGP digital signature
Bug#834296: Dependencies mixed up between voctomix and voctomix-core
On Sun, Aug 14, 2016 at 12:37:56PM +0200, Peter Körner wrote: > > btw, looking at the recent commits I've seen that configuration files in > > /etc/voctomix are now also being considered, which is a feature I think > > would > > be worth a 0.3.2 release alone! > That's nothing new and already since 0.1 like this: [...] > Compare that to the 0.3.1 version: sorry for the noise: when I thought this, i had log at the most recent commits in the (local) git master branch (which only had+has 0.3.1 and where these commits where more current) and not in the remote master branch… > I do however plan to do a 0.4 release after FOSS4G in ~3 Weeks with some > new features. yay! -- cheers, Holger signature.asc Description: Digital signature
Bug#745025: Looking for sponsor
Hello, finally got some time to move this forward. I have packaged dependencies for vdirsyncer and vdirsyncer itself is waiting for review and upload [1]. I also completely rework Khal packaging, waiting for review as well [2]. So I am expecting Khal will reach Debian unstable soon :-) --- [1] https://github.com/fpytloun/debian-vdirsyncer [2] https://github.com/fpytloun/debian-khal Filip On Mon, 18 Apr 2016 18:14:47 +0200 Helmut Grohne wrote: > Hi Filip, > > On Fri, Jan 29, 2016 at 04:13:48PM +0100, Filip Pytloun wrote: > > I have prepare khal package: > > http://mentors.debian.net/package/khal > > > > Is there anyone interested in sponsoring it? > > I am interested in this package and would like to see it included in > Debian. I spent a brief look into it already and found a number of > issues: > > * debian/copyright: The license grant for the MIT license suspiciously >looks like a GPL grant and references the non-existent file >/usr/share/common-licenses/MIT. > * khal.conf.sample should be installed using dh_installexamples instead >of dh_installdocs. > * Your patches say what they are doing, but the patch headers lack >reasoning on why they are necessary (in particular the second patch). > * It seems that you are packaging khal as a Python2 application, but >upstream only declares it working with Python3. Is there any reason >not to use Python3? > * Instead of installing the manual page twice, please use a symbolic >link. Try using dh_link. > > At least the copyright issue is a blocker. > > If you update the package, please Cc me, so I can have another look. > > Helmut > > signature.asc Description: Digital signature
Bug#832101: Installing pulseaudio-module-udev
I don't this bug should have been closed just yet. The original reporter obviously had a difficult time figuring out where the problem lay, and no doubt countless others will too. At the very least a message needs to go out in apt-get upgrade telling people that they should and cite that pauvcontrol will loose functionality if they don't; but ideally the "error" message in pavucontrol needs changing to something like: ``` No devices were found. If you expected to see devices here, check that you have pulseaudio-module-udev installed. ```
Bug#833656: cme fails with dpkg error
On Sun, Aug 14, 2016 at 05:27:39PM +1000, Brendan O'Dea wrote:
> This is a bit puzzling, but I am guessing that the bug is in apt:
> getDpkgStatusLocation is modifying the global _config object of libapt-pkg in
> such a way that if debSystem::Initialize is called twice, the results will be
> different.
No, the setting of Dir::State::status is guarded by a check for
existence, so you could call it a million times and still get the same
result.
The problem is the value it sets the first time around is not a value
which starts with "/" as it expects "Dir" to be set, but it isn't in
this case, so that later then the "Dir::State::status" value is read via
FindFile it will recognize that Dir::state::status isn't an absolute
path (as it is missing the / in the front) and hence prefixes the values
of Dir::state and Dir – which by now are set letting you end up with a:
/ (<- Dir)
var/lib/apt (<- Dir::state)
var/lib/dpkg/status (<- Dir::state::status, which is what it generates if
neither Dir nor Dir::state where set at the time this value was set itself,
but it "should" be /var/lib/dpkg/status – mind the gap^Wslash)
> Cnf.Set("Dir::State::status", {
> Cnf.Set("Dir::State::status", "status");
> return Cnf.FindFile("Dir::State::status");
> });
So, for brevities sake lets say its: Cnf.CndSet("Dir::State::status", …
> along with some other manipulations. If I understand your intent correctly, I
> would recommend rewriting getDpkgStatusLocation to take a const reference to
> the Configuration, and to use an internal temporary instance. A brief comment
Your are right, that works in the current instance (I tried something else
first where it wouldn't have work and … If all you have is a hammer…) and it is
actually a bit shorter by avoiding the back and forth, too. Thanks!
> To clarify what's actually happening here, this line:
>
> $_config->init;
>
> invokes pkgInitConfig under the hood, on the global C++ _config object. This
> populates it with general APT things, e.g. Dir::State, but not Debian-specific
> things like Dir::State::status. After that, the following line:
>
> $_system = $_config->system;
>
> calls pkgInitSystem, passing in the global _config object, and populating the
> global _system object (which is magically bound to $_system, so that
> assignment works). That indirectly calls debSystem::Initialize, which sets
> Debian-specific things like Dir::State::status and
> Dir::State::extended_status.
That is what is supposed to happen, yes (at least as far as the description
goes, no idea about the perl part)
> Adding some debugging of the working code from the example directory, after
> the $_config->init line I get as expected:
>
> RootDir=
> Dir=/
> Dir::State=var/lib/apt/
> Dir::State::status=
> Dir::State::extended_states=
>
> and after the $_system = ... line:
>
> RootDir=
> Dir=/
> Dir::State=var/lib/apt/
> Dir::State::status=/var/lib/dpkg/status
> Dir::State::extended_states=extended_states
>
> For the case of libconfig-model-dpkg-perl, I'm seeing the following for after
> the init:
>
> RootDir=
> Dir=
> Dir::State=var/lib/apt/
> Dir::State::status=var/lib/dpkg/status
> Dir::State::extended_states=extended_states
>
> which suggests that the _config object has been modified prior to this code
> being run. Not sure where, perhaps there is another use of AptPkg in cme?
The first is correct, the later indicates that $_config->init was never called
as Dir couldn't be empty in that case (and that Dir::State gets its default
value here is actually an unattended but harmless side effect of the dpkg/status
finding code in its current form). Given that the error message has a '/' in
front I lean towards assuming that the configuration is eventually initialized,
just too late.
Best regards
David Kalnischkies
signature.asc
Description: PGP signature
Bug#790355: hylafax: please make the build reproducible
Hello Chris, Il giorno dom, 14/08/2016 alle 10.30 +0100, Chris Lamb ha scritto: > Dear Maintainer, > > Source: hylafax > > Version: 3:6.0.6-6 > > Tags: patch > > There hasn't seem to be any update on this bug in 412 days, in which > time the Reproducible Builds effort has come on a long way. :) > > Would you consider applying this patch and uploading? I am working on a new upload. I hope to make it in a few weeks. Thanks, Giuseppe
Bug#834302: pd-flite: please make the build reproducible
Source: pd-flite Version: 0.02.3-1 Severity: wishlist Tags: patch upstream User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps username X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the "reproducible builds" effort [1], we have noticed that pd-flite could not be built reproducibly. It embeds the build date and username into the binary. The attached patch strips this to get a reproducible build. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/patches/reproducible-build.patch b/debian/patches/reproducible-build.patch new file mode 100644 index 000..d533807 --- /dev/null +++ b/debian/patches/reproducible-build.patch @@ -0,0 +1,13 @@ +Author: Reiner Herrmann +Description: Strip build date and user to get reproducible build + +--- a/flite.c b/flite.c +@@ -48,7 +48,6 @@ + + static const char *flite_description = + "flite: Text-to-Speech external v" PACKAGE_VERSION " by Bryan Jurish\n" +- "flite: compiled on " PACKAGE_BUILD_DATE " by " PACKAGE_BUILD_USER "\n" + ; + //static char *flite_acknowledge = "flite: based on code by "; + //static char *flite_version = "flite: PD external v%s by Bryan Jurish"; diff --git a/debian/patches/series b/debian/patches/series index 21011bc..93247f5 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1,2 @@ fix-help-files-install-dir.patch +reproducible-build.patch signature.asc Description: PGP signature
Bug#827245: [Pkg-libvirt-maintainers] Bug#827245: missing backend for pool type 11 (zfs)
On Sun, Aug 14, 2016 at 11:34:22AM +0200, Guido Günther wrote: > It builds find in a uptodate pbuilder chroot so no idea what > happens. I'll try it in a jessie VM when I get some spare time. > Maybe it clashes with a installed libvirt-dev package? Nope, i don't have that installed. > I've pushed the changes to enable zfs pool support on kfreebsd. Why not on linux? zfs is available in debian now. craig -- craig sanders
Bug#831884: Pending fixes for bugs in the libnet-ip-xs-perl package
tag 831884 + pending thanks Some bugs in the libnet-ip-xs-perl package are closed in revision be5fc91446075bb3a3a02ba78a7c4fea9c8d49b7 in branch 'master' by Salvatore Bonaccorso The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-ip-xs-perl.git/commit/?id=be5fc91 Commit message: Drop Depends on libip-country-perl The Build-Depends on libip-country-perl was removed already in the packaging repository before the initial upload, but the Depends got forotten. IP::Country is not used within Net::IP::XS. Closes: #831884
Bug#831884: Pending fixes for bugs in the libnet-ip-xs-perl package
tag 831884 + pending thanks Some bugs in the libnet-ip-xs-perl package are closed in revision cece03f8c7b8869f8b5affd98395ee7ea21d2697 in branch 'master' by Salvatore Bonaccorso The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-ip-xs-perl.git/commit/?id=cece03f Commit message: Drop Depends on libip-country-perl The Build-Depends on libip-country-perl was removed already in the packaging repository before the initial upload, but the Depends got forotten. IP::Country is not used within Net::IP::XS. Closes: #831884
Bug#827245: [Pkg-libvirt-maintainers] Bug#827245: missing backend for pool type 11 (zfs)
On Sun, Aug 14, 2016 at 11:34:22AM +0200, Guido Günther wrote: > I've pushed the changes to enable zfs pool support on kfreebsd. BTW, i've been experimenting with docker.io recently. It has support for zfs (as well as btrfs and aufs and others) enabling ZFS support is as simple as adding two lines to /etc/default/docker: OPTIONS="--storage-driver zfs" DOCKER_OPTS="-s zfs" and creating a zfs subvolume mounted at /var/lib/docker. FYI: Package: docker.io Version: 1.11.2~ds1-6 Depends: adduser, containerd (>= 0.2.1~), iptables, runc (>= 0.1.0~), init-system-helpers (>= 1.18~), libapparmor1 (>= 2.6~devel), libc6 (>= 2.17), libdevmapper1.02.1 (>= 2:1.02.97), libsqlite3-0 (>= 3.7.15), libsystemd0 Recommends: ca-certificates, cgroupfs-mount | cgroup-lite, git, xz-utils Suggests: aufs-tools, btrfs-progs, debootstrap, docker-doc, rinse, zfs-fuse | zfsutils Description-en: Linux container runtime craig -- craig sanders
Bug#834297: lv2-c++-tools: FTBFS with new boost
Control: merge 834291 -1 On 14/08/16 10:51, Santiago Vila wrote: > Package: src:lv2-c++-tools > Version: 1.0.5-2 > Severity: serious > > Dear maintainer: > > This package currently fails to build from source in stretch: Duplicate of #834291, but only by 22 minutes :) James signature.asc Description: OpenPGP digital signature
Bug#834304: RM: queuegraph -- RoQA, RoM; obsolete, dead upstream, low popcorn
Package: ftp.debian.org Severity: normal The MIA team was pointed to this package and the maintainer replied to this ping and recommended removal of the package: > No, I'm afraid I don't have the time to maintain Debian packages anymore. > Looking at https://www.arschkrebs.de/postfix/queuegraph/ , there hasn't > been a queuegraph release since 2007, so it's unlikely to be compatible > with a modern Postfix release. I'd suggest just deprecating and deleting > the package. There are no r-deps. -- tobi (for the MIA Team)
Bug#834303: calibre: Unhandled exception when editing books
Package: calibre
Version: 2.60.0+dfsg-1
Severity: important
Dear Maintainer,
After an upgrade a few days ago, I can no longer edit books using Calibre.
I open Calibre, open the editing window, and so far so good. Now I double click
on an xhtml file, and instead of the file opening for editing, I get the
following error.
calibre 2.60 embedded-python: False is64bit: True
Linux-4.6.0-1-amd64-x86_64-with-debian-stretch-sid Linux ('64bit', 'ELF')
('Linux', '4.6.0-1-amd64', '#1 SMP Debian 4.6.2-1 (2016-06-15)')
Python 2.7.12+
Linux: ('debian', 'stretch/sid', '')
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/gui2/tweak_book/boss.py", line 1375, in
edit_file_requested
return self.edit_file(name, syntax)
File "/usr/lib/calibre/calibre/gui2/tweak_book/boss.py", line 1354, in
edit_file
self.init_editor(name, editor, data, use_template=bool(use_template))
File "/usr/lib/calibre/calibre/gui2/tweak_book/boss.py", line 1329, in
init_editor
editor.data = data
File "/usr/lib/calibre/calibre/gui2/tweak_book/editor/widget.py", line 191,
in fset
self.editor.load_text(val, syntax=self.syntax, doc_name=editor_name(self))
File "/usr/lib/calibre/calibre/gui2/tweak_book/editor/text.py", line 172, in
load_text
self.highlighter.set_document(self.document(), doc_name=doc_name)
File "/usr/lib/calibre/calibre/gui2/tweak_book/editor/syntax/base.py", line
107, in set_document
doc.contentsChange.connect(self.reformat_blocks)
TypeError: connect() failed between contentsChange(int,int,int) and
reformat_blocks()
I get the same error for txt, xml, opf, and ncx files. I tested jpgs, and they
open without error.
I had expected the editing window to open normally.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages calibre depends on:
ii calibre-bin2.60.0+dfsg-1+b1
ii fonts-liberation 1.07.4-1
ii imagemagick8:6.8.9.9-7.2
ii libjs-mathjax 2.6.1-1
ii poppler-utils 0.44.0-3
ii python-apsw3.8.11.1-r1-1+b2
ii python-beautifulsoup 3.2.1-1
ii python-chardet 2.3.0-2
ii python-cherrypy3 3.5.0-2
ii python-cssselect 0.9.2-1
ii python-cssutils1.0-4.1
ii python-dateutil2.4.2-1
ii python-dbus1.2.4-1
ii python-feedparser 5.1.3-3
ii python-imaging 3.3.0-1
ii python-lxml3.6.0-1
ii python-markdown2.6.6-1
ii python-mechanize 1:0.2.5-3
ii python-netifaces 0.10.4-0.1+b2
ii python-pil 3.3.0-1
ii python-pkg-resources 20.10.1-1.1
ii python-pyparsing 2.1.7+dfsg1-1
ii python-pyqt5 5.7+dfsg-1
ii python-pyqt5.qtsvg 5.7+dfsg-1
ii python-pyqt5.qtwebkit 5.7+dfsg-1
ii python-routes 2.3.1-2
ii python2.7 2.7.12-2
ii xdg-utils 1.1.1-1
Versions of packages calibre recommends:
ii python-dnspython 1.14.0-3
calibre suggests no packages.
-- no debconf information
Bug#834306: O: autotrace -- bitmap to vector graphics converter
Package: wnpp Severity: normal The current maintainer of autotrace, Edgar Antonio Palma de la Cruz , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: autotrace Binary: autotrace, libautotrace3, libautotrace-dev Version: 0.31.1-16+nmu1.2 Maintainer: Edgar Antonio Palma de la Cruz Build-Depends: debhelper (>= 8), autotools-dev, pkg-config, libpng-dev, libpstoedit-dev (>= 3.42-1.1), libmagickcore-dev, dh-autoreconf Architecture: any Standards-Version: 3.9.2 Format: 3.0 (quilt) Files: 4b7dc02ac0d1a658bff25a23ae9ca686 1994 autotrace_0.31.1-16+nmu1.2.dsc 54eabbb38d2076ded6d271e1ee4d0783 362718 autotrace_0.31.1.orig.tar.gz e75ca240480126badedd5453e86fba45 176340 autotrace_0.31.1-16+nmu1.2.debian.tar.xz Checksums-Sha1: cd111749b58e5203130072f83bd79547a512ebf5 1994 autotrace_0.31.1-16+nmu1.2.dsc 679e4912528030b86f23db5b99e60f8e7df883fd 362718 autotrace_0.31.1.orig.tar.gz c4072b63484f2fc21ddae890268fff25183b8035 176340 autotrace_0.31.1-16+nmu1.2.debian.tar.xz Checksums-Sha256: fa075da7f5bfb0026bc4b80dbe77aaa847c2f003f23683c6e74ba9217c6e1f27 1994 autotrace_0.31.1-16+nmu1.2.dsc 5a1a923c3335dfd7cbcccb2bbd4cc3d68cafe7713686a2f46a1591ed8a92aff6 362718 autotrace_0.31.1.orig.tar.gz ed43aff23559d224462740e41fbbcb4bdd11f5d49f96d37c87e098c5ab393032 176340 autotrace_0.31.1-16+nmu1.2.debian.tar.xz Homepage: http://autotrace.sourceforge.net/ Package-List: autotrace deb graphics optional arch=any libautotrace-dev deb libdevel optional arch=any libautotrace3 deb libs optional arch=any Directory: pool/main/a/autotrace Priority: source Section: graphics Package: autotrace Source: autotrace (0.31.1-16+nmu1.2) Version: 0.31.1-16+nmu1.2+b1 Installed-Size: 84 Maintainer: Edgar Antonio Palma de la Cruz Architecture: amd64 Depends: libautotrace3 (>= 0.31.1), libc6 (>= 2.14), libgomp1 (>= 4.2.1) Description-en: bitmap to vector graphics converter AutoTrace is a program for converting bitmaps to vector graphics. The aim of the AutoTrace project is the development of a freely-available application similar to CorelTrace or Adobe Streamline. In some aspects it is already better. Originally created as a plugin for the GIMP, AutoTrace is now a standalone program. Description-md5: 69db748e2ac00ca339dfeb7713e5c78b Homepage: http://autotrace.sourceforge.net/ Tag: implemented-in::c, interface::commandline, role::program, scope::application, scope::utility, use::converting, works-with::image, works-with::image:raster, works-with::image:vector Section: graphics Priority: optional Filename: pool/main/a/autotrace/autotrace_0.31.1-16+nmu1.2+b1_amd64.deb Size: 49162 MD5sum: 2b734c2c13cff9ad583bb69f21135382 SHA256: ef394c3721b60b0cf66cb9c7a06f1a69604f3393fd24cabb5e7221db50bca125 Package: libautotrace3 Source: autotrace (0.31.1-16+nmu1.2) Version: 0.31.1-16+nmu1.2+b1 Installed-Size: 233 Maintainer: Edgar Antonio Palma de la Cruz Architecture: amd64 Depends: libc6 (>= 2.14), libgomp1 (>= 4.2.1), libmagickcore-6.q16-2 (>= 8:6.8.8.2), libpng16-16 (>= 1.6.2-1), libpstoedit0c2a, zlib1g (>= 1:1.1.4) Description-en: bitmap to vector graphics converter, shared library files Runtime shared library files needed by programs that link with the AutoTrace bitmap-to-vector graphics converter. About the usage of the library see http://autotrace.sourceforge.net/frontline Description-md5: 38782a660cb883fa07fab21b582ef8ab Homepage: http://autotrace.sourceforge.net/ Tag: role::shared-lib Section: libs Priority: optional Filename: pool/main/a/autotrace/libautotrace3_0.31.1-16+nmu1.2+b1_amd64.deb Size: 103216 MD5sum: a4ac6df05f75d72c0e458e4496c62f47 SHA256: f644ac9ab052a7555db33843c6541366bd8155d6aba5d753d47c0304c2c5bf3e Package: libautotrace-dev Source: autotrace (0.31.1-16+nmu1.2) Version: 0.31.1-16+nmu1.2+b1 Installed-Size: 412 Maintainer: Edgar Antonio Palma de la Cruz Architecture: amd64 Depends: libautotrace3 (= 0.31.1-16+nmu1.2+b1), libc6-dev | libc-dev, libpng-dev, libpstoedit-dev (>= 3.42-1.1), libmagickcore-dev Recommends: pkg-config (>= 0.18) Description-en: bitmap to vector graphics converter, development files Static library and header include files needed for developing programs using the AutoTrace bitmap-to-vector graphics converter. Here is a sample program that uses libautotrace. Description-md5: d579cb9d3d23aeeaf0ae0ef4d204566a Homepage: http://autotrace.sourceforge.net/ Tag: devel::library, implemented-in::c, role::devel-lib Section: libdevel Priority: optional Filename: pool/main/a/autotrace/libautotrace-dev_0.31.1-16+nmu1.2+b1_amd64.deb Size: 116836 MD5sum: 6acc6ac2047ef006c2863e04fb81f118 SHA256: 2ab705069e8ea7a52e504979a71cb9f8ab6ac8ad8c332b5475cd3
