Bug#808041: s390-zfcp: Install Debian on FC-attached SCSI devices on s390 (patches)
Hi, On Tue, Dec 15, 2015 at 03:15:42PM +0100, Hendrik Brueckner wrote: > Below you can find the patches for the FCP configuration utility. > The patch set consists of five patches: > > 1. A README file describing how to use the FCP configuration utility. > 2. Generic interfaces and functions to manage CCW devices on s390. > 3. Functions to manage FCP devices. > 4. The FCP configuration utility. > 5. Debian packaging files to build the Debian Installer udeb. > > Initial tests to configure FCP devices ran successful on z/VM and LPAR > using FCP devices with and without N_Port ID virtualization (NPIV). > > Review and feedback of the patches is very welcome! As a beginner in > Debian packaging, please review the Debian packaging files. I took the liberty to push the patchset to [1]. This will still require review, but any potential fix-up commits can just be based on your work. (I hope to have some more time over the holidays to review, but as said I can't test it.) Kind regards and thanks Philipp Kern [1] http://anonscm.debian.org/cgit/d-i/s390-zfcp.git signature.asc Description: Digital signature
Bug#807442: patch
On Tue, Dec 08, 2015 at 03:17:49PM -0700, dann frazier wrote: > diff -Nru s390-tools-1.32.0/debian/changelog > s390-tools-1.32.0/debian/changelog > --- s390-tools-1.32.0/debian/changelog2015-10-25 17:12:02.0 > +0100 > +++ s390-tools-1.32.0/debian/changelog2015-12-08 23:14:52.0 > +0100 > @@ -1,3 +1,9 @@ > +s390-tools (1.32.0-2) UNRELEASED; urgency=medium > + > + * Add dbginfo.sh. (Closes: #807442) > + > + -- dann frazier <da...@debian.org> Tue, 08 Dec 2015 22:33:52 +0100 > + > s390-tools (1.32.0-1) unstable; urgency=medium > >* New upstream release > diff -Nru s390-tools-1.32.0/debian/s390-tools.install > s390-tools-1.32.0/debian/s390-tools.install > --- s390-tools-1.32.0/debian/s390-tools.install 2014-07-26 > 23:59:18.0 +0200 > +++ s390-tools-1.32.0/debian/s390-tools.install 2015-12-08 > 23:08:30.0 +0100 > @@ -10,6 +10,10 @@ > /sbin/dasdview > /usr/share/man/man8/dasdview.8 > > +# dbginfo.sh > +/sbin/dbginfo.sh > +/usr/share/man/man1/dbginfo.sh.1 > + > # fdasd > /sbin/fdasd > /usr/share/man/man8/fdasd.8 Three comments: * dbginfo.sh should tell the user that the information in the tarball is sensitive. * The resulting tarball should be 0600 by default. (The script needs to run as root anyway, but placing the result world-readable in /tmp does not seem smart.) * Unless this is expected to be in /sbin, given that it's user invoked and not usually scripted, should this be in /usr/sbin instead? Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#807168: debian-installer-netboot-images: required resources not declared as build-dependencies (fetches via network)
On Sun, Dec 06, 2015 at 06:02:48PM +0530, Jonas Smedegaard wrote: > debian-installer-netboot-images source package is less than 6k in size. > Clearly the main part of the resulting binary packages come from > fetching resources over the network (apparently using wget). > > Debian Policy includes the following in §4.2: > > > If build-time dependencies are specified, it must be possible to build > > the package and produce working binaries on a system with only > > essential and build-essential packages installed and also those > > required to satisfy the build-time relationships (including any > > implied relationships). > > I can only interpret above as disallowing fetching resources over the > network using wget. Is it legal to build a unique arch:all package per architecture? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#806239: Updating ca-certificates through stable-updates
> Could I perhaps convince you to file this (kind of) request as a pu bug? > They are much easier for us to track than mails to the mailing list. > I appreciate that you might have been sending this mail to avoid the > pu-bug. Unfortunately, we often end up forgetting the mail on our TODO > list if it is not listed in the bug tracker. There's that and it helps to look at the debdiff to see what the actual changes are. Cert updates are likely to be much easier on us than packaging/script updates. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#804381: jessie-pu: package s390-dasd/0.0.32~deb8u1
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
I'd like to update s390-dasd 0.0.32 from stretch to sid, as
0.0.32~deb8u1. The debdiff is attached. It fixes installation of Debian
within KVM on System z and within full-system emulation using qemu.
The critical hunk is this:
@@ -233,7 +235,8 @@
return get_channel_input ();
else if (di_tree_size (channels) > 0)
return get_channel_select ();
- return WANT_ERROR;
+ di_info("s390-dasd: no channel found");
+ return WANT_FINISH;
}
This lets s390-dasd exit cleanly if no DASD disks are found. Within qemu
virtio is used to provide disks, which is totally different from what
traditionally used to happen on the mainframe.
The remaining changes are .po updates, mainly in the comments, and
the logging of the various error conditions s390-dasd emits. Without
the logging you cannot deduce why it exited with a failure.
I'm also happy to skip the .po changes if needed, but it seemed cleaner
to just backport stretch's current version.
Kind regards and thanks
Philipp Kern
diff -Nru s390-dasd-0.0.30/dasd-config.c s390-dasd-0.0.32/dasd-config.c
--- s390-dasd-0.0.30/dasd-config.c 2013-12-04 00:53:16.0 +0100
+++ s390-dasd-0.0.32/dasd-config.c 2015-11-01 22:37:03.0 +0100
@@ -1,4 +1,5 @@
#include
+#include
#include
#include
#include
@@ -224,6 +225,7 @@
channel_current = di_tree_lookup (channels, );
if (channel_current)
return WANT_NEXT;
+ di_error("s390-dasd: could not get selected channel device %d", dev);
return WANT_ERROR;
}
@@ -233,7 +235,8 @@
return get_channel_input ();
else if (di_tree_size (channels) > 0)
return get_channel_select ();
- return WANT_ERROR;
+ di_info("s390-dasd: no channel found");
+ return WANT_FINISH;
}
static enum state_wanted enable (void)
@@ -242,14 +245,23 @@
struct sysfs_attribute *attr;
device = sysfs_open_device ("ccw", channel_current->name);
- if (!device)
+ if (!device) {
+ di_error("s390-dasd: could not open device %s",
+ channel_current->name);
return WANT_ERROR;
+ }
attr = sysfs_get_device_attr (device, "online");
- if (!attr)
+ if (!attr) {
+ di_error("s390-dasd: could not read online attribute for %s",
+ channel_current->name);
return WANT_ERROR;
- if (sysfs_write_attribute (attr, "1", 1) < 0)
+ }
+ if (sysfs_write_attribute (attr, "1", 1) < 0) {
+ di_error("s390-dasd: could not set %s online: %s",
+ channel_current->name, strerror(errno));
return WANT_ERROR;
+ }
sysfs_close_device (device);
diff -Nru s390-dasd-0.0.30/debian/changelog s390-dasd-0.0.32/debian/changelog
--- s390-dasd-0.0.30/debian/changelog 2014-03-14 22:59:51.0 +0100
+++ s390-dasd-0.0.32/debian/changelog 2015-11-01 22:59:19.0 +0100
@@ -1,3 +1,18 @@
+s390-dasd (0.0.32) unstable; urgency=medium
+
+ * If no channel is found, exit cleanly. This allows s390-dasd to step
+out of the way on VMs with virtio disks.
+ * Log error conditions.
+
+ -- Philipp Kern <pk...@debian.org> Sun, 01 Nov 2015 22:59:11 +0100
+
+s390-dasd (0.0.31) unstable; urgency=medium
+
+ [ Updated translations ]
+ * Turkish (tr.po) by Mert Dirik
+
+ -- Christian Perrier <bubu...@debian.org> Sun, 26 Jul 2015 09:15:33 +0200
+
s390-dasd (0.0.30) unstable; urgency=low
[ Dmitrijs Ledkovs ]
diff -Nru s390-dasd-0.0.30/debian/po/be.po s390-dasd-0.0.32/debian/po/be.po
--- s390-dasd-0.0.30/debian/po/be.po 2013-12-04 00:53:16.0 +0100
+++ s390-dasd-0.0.32/debian/po/be.po 2015-05-23 19:12:43.0 +0200
@@ -11,11 +11,13 @@
# Nasciona Piatrouskaja <nas...@tut.by>, 2006.
# Paul Petruk <berser...@neolocation.com>, 2007.
# Pavel Piatruk <piatru...@gmail.com>, 2008, 2009, 2011.
-# Viktar Siarheichyk <v...@eq.by>, 2010, 2011, 2012.
+# Viktar Siarheichyk <v...@eq.by>, 2010, 2011, 2012, 2015.
# Translations from iso-codes:
# Alastair McKinstry <mckins...@debian.org>, 2004.
# Alexander Nyakhaychyk <nyakhayc...@gmail.com>, 2009.
# Ihar Hrachyshka <ihar.hrachys...@gmail.com>, 2007, 2010.
+# Viktar Siarheichyk <viсs...@eq.by>, 2014.
+# Viktar Siarheichyk <v...@fsfe.org>, 2014, 2015.
msgid ""
msgstr ""
"Project-Id-Version: be\n"
@@ -23,8 +25,7 @@
"POT-Creation-Date: 2010-03-30 23:19+\n"
"PO-Revision-Date: 2010-07-06 01:58+0300\n"
"Last-Translator: Viktar Siarheichyk <v...@eq.by>\n"
-"Language-Team: Belarusian (Official spelling) <debian-l10n-belarusian@lists."
-"debian.org>\n"
+"Language-Team: Belarusian <i...@mova.org>\n"
"Language: be\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
diff -Nru s390-das
Bug#804383: jessie-pu: package libinfinity/0.6.7-1~deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu I would like to upload libinfinity 0.6.7-1 from stretch as 0.6.7-1~deb8u1 to jessie (debdiff of 0.6.6-1 to 0.6.7-1 attached). To quote the upstream NEWS file of this maintenance release: * Fix a possible crash when an entry is removed from the document browser. * Fix a possible crash in infinoted when access control lists are enabled. * Fix an assertion failure when operating with text documents and using glib 2.46 or newer. The release contains a little bit of autotools, changelog, and po churn, but apart from that does only contain the above changes. If needed I can back out the glib 2.46 change, although I'd prefer to upload the whole thing as the change is arguably more correct even with older glibs. Kind regards and thanks Philipp Kern diff -Nru libinfinity-0.6.6/ChangeLog libinfinity-0.6.7/ChangeLog --- libinfinity-0.6.6/ChangeLog 2015-05-13 02:57:57.089748067 +0200 +++ libinfinity-0.6.7/ChangeLog 2015-10-14 01:34:53.805216085 +0200 @@ -1,6 +1,115 @@ +commit a7bdd262474898d180285129f5aed3e87b04461a +Author: Armin Burgmeier <ar...@arbur.net> +Date: Tue Oct 13 19:34:35 2015 -0400 + +Release libinfinity 0.6.7 + + NEWS | 8 + 1 file changed, 8 insertions(+) + +commit d447fc406c0ceb2766f69ffec28f017baa7ed7a9 +Author: Armin Burgmeier <ar...@arbur.net> +Date: Mon Oct 12 19:51:50 2015 -0400 + +InfTextChunk: fix segment lookup for offset=0 (#10) + +This used to work with glib 2.42, but it seems that the semantics of +g_sequence_search() have changed with respect to what item is returned +when the comparison function returns 0. The behavior in that case is not +documented. Fix this by passing a different comparison function that +never returns 0, so that there is no ambiguity in which segment is +returned. + + libinftext/inf-text-chunk.c | 29 - + 1 file changed, 28 insertions(+), 1 deletion(-) + +commit 3fb2be4fb355ed44541d6da486dc73c5dd739ca3 +Author: Armin Burgmeier <ar...@arbur.net> +Date: Mon Oct 12 19:51:40 2015 -0400 + +Fix integrity check in inf_text_chunk_get_byte_index_utf8() + + libinftext/inf-text-chunk.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +commit 4fc1227317eea35b87e10686daf467642c9abe1e +Author: Armin Burgmeier <ar...@arbur.net> +Date: Tue Jun 9 21:20:23 2015 -0400 + +Fix uninitialized variable when suggesting a SASL mechanism + + libinfinity/common/inf-xmpp-connection.c | 1 + + 1 file changed, 1 insertion(+) + +commit 28dd0736c7618861dd9a23e8793e4db865ce6a5e +Author: Armin Burgmeier <ar...@arbur.net> +Date: Sun Jun 7 21:27:23 2015 -0400 + +InfXmppConnection: Fix strncmp invocation when suggesting SASL mechanism + + libinfinity/common/inf-xmpp-connection.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +commit 4dfaf22925dbe12008627d0a604b179fd6e4b7b4 +Author: Armin Burgmeier <ar...@arbur.net> +Date: Wed May 27 22:21:22 2015 -0400 + +Fix g_free / g_slice_free mismatch + + libinfinity/server/infd-directory.c | 18 -- + 1 file changed, 16 insertions(+), 2 deletions(-) + +commit d17398a0f850a79ffbe78c10bbe8ebfd0cd5e63c +Author: Armin Burgmeier <ar...@arbur.net> +Date: Wed May 27 21:12:28 2015 -0400 + +InfdDirectory: Fix error reply to client when session proxy cannot +be created + + libinfinity/server/infd-directory.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +commit 822b227c662e5fcaab3c1bdfdf224eebaefe7728 +Author: Armin Burgmeier <ar...@arbur.net> +Date: Sat May 23 14:39:59 2015 -0400 + +Fix session becoming inconsistent with active local users during +subscription + +When the server sends the vector time of local users during subscription, +it now sends the last send vector instead of the real value of the +user time, +so that subsequent state vector diffs are consistent for the newly joined +client. + +Conflicts: + libinfinity/adopted/inf-adopted-session.c + + libinfinity/adopted/inf-adopted-session.c | 34 - + 1 file changed, 33 insertions(+), 1 deletion(-) + +commit cf4588011a5023af36d6393f1f724a11742b84f1 +Author: Armin Burgmeier <ar...@arbur.net> +Date: Fri May 22 19:22:26 2015 -0400 + +Fix a possible crash when removing a browser entry + + libinfgtk/inf-gtk-browser-store.c | 5 + + libinfgtk/inf-gtk-browser-view.c | 11 +++ + 2 files changed, 16 insertions(+) + +commit 4522baf6a975f38e6874c90695b00af0d2854dfc +Author: Armin Burgmeier <ar...@arbur.net> +Date: Tue May 12 20:58:49 2015 -0400 + +Post-release bump to 0.6.7 + + configure.ac | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + commit a5bc24e87714d3c3fa75711c5d06b9b8e4c81d53 Author: Armin Burgmeier <ar...@arbur.net> -Date: Tue May 12 20:12:52 2015 -0400 +Date: Tue May 12 20:
Bug#801913: init-premount boot script is now superfluous
On 2015-10-16 02:09, Stephen Powell wrote: Now that sysconfig-hardware brings DASD devices online before the permanent root file system is mounted, the script usr/share/initramfs-tools/scripts/init-premount/sysconfig_hardware is superfluous. It is no longer needed. It should be dropped from the package. That's one less piece of code to maintain, and one less item that needs to be included in the initial RAM file system image file. I'm not sure I agree with this assertion. It is a fallback if you do not have the disk configuration in the initrd and instead want to bring the devices online from the kernel command-line. But possibly the correct way there is to provide the disk list to dasd_mod.dasd rather than relying on root= parsing? Kind regards and thanks Philipp Kern
Bug#800772: Password leaked into process list with p7zip
Package: file-roller Version: 3.14.1-1 Severity: important When producing an encrypted 7z archive the following leaks into ps output: /usr/lib/p7zip/7z a -bd -y -p -mx=7 -i@ -- The password should instead be passed via stdin or through some other mechanism because this way it is leaked to other users on the same system. -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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 file-roller depends on: ii bzip21.0.6-7+b3 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii libarchive13 3.1.2-11 ii libc62.19-18+deb8u1 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u2 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1+deb8u1 ii libjson-glib-1.0-0 1.0.2-1 ii libmagic11:5.22+15-2 ii libnautilus-extension1a 3.14.1-2 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-3 ii nautilus-data3.14.1-2 ii p7zip-full 9.20.1~dfsg.1-4.1+deb8u1 Versions of packages file-roller recommends: ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gvfs 1.22.2-1 ii unar 1.8.1-3+b1 ii yelp 3.14.1-1 Versions of packages file-roller suggests: pn arj pn lha pn lzip ii lzma 9.22-2 ii lzop 1.03-3 pn ncompress pn rpm2cpio pn rzip ii sharutils1:4.14-2 pn unace pn unalz ii unzip6.0-16 ii xz-utils [lzma] 5.1.1alpha+20120614-2+b3 ii zip 3.0-8 pn zoo -- no debconf information
Bug#800793: jessie-pu: package netcfg/1.131+deb8u1
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
I would like to fix netcfg in stable and allow KVM on s390x to boot the
installer with working networking. The simple patch is this and is
already in testing.
diff --git a/debian/changelog b/debian/changelog
index 8dc90b9..4f2d3bc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+netcfg (1.131+deb8u1) stable; urgency=medium
+
+ * Fix is_layer3_qeth on s390x to avoid bailing out if the network
+driver is not qeth. (Closes: #798376)
+
+ -- Philipp Kern <pk...@debian.org> Sat, 03 Oct 2015 18:42:26 +0200
+
netcfg (1.131) unstable; urgency=medium
* Kill the DHCP client on Linux again and keep it running on kFreeBSD.
diff --git a/netcfg-common.c b/netcfg-common.c
index 7c2c002..376e6ca 100644
--- a/netcfg-common.c
+++ b/netcfg-common.c
@@ -293,11 +293,11 @@ int is_layer3_qeth(const char *iface)
goto out;
}
-buf[slen + 1] = '\0';
+buf[slen] = '\0';
driver = strrchr(buf, '/') + 1;
if (strcmp(driver, "qeth") != 0) {
-di_error("no qeth found: %s", driver);
+di_info("no qeth found: %s", driver);
goto out;
}
Kind regards and thanks
Philipp Kern
Bug#798376: debian-installer: configuring the network device fails on s390x if network devive is virtio_net and not qeth
Hi,
On Tue, Sep 08, 2015 at 03:35:41PM +0100, Gerhard Stenzel wrote:
> I would like to bring the following problem with the debian-installer
> to your attention:
[...]
> #if defined(__s390__)
> // Layer 3 qeth on s390(x) cannot do arping to test gateway reachability.
> int is_layer3_qeth(const char *iface)
> {
> .
>
> if (strcmp(driver, "qeth") != 0) {
> di_error("no qeth found: %s", driver);
> goto out;
> }
I actually fixed that locally a month ago at Debconf but couldn't test
it on emulated qemu. Apparently the issue with virtio_net not loading
does not apply to KVM and there it just works.
Updated package incoming for stretch at least. We will need to check
about backporting quite a bunch of s390x fixes to stable.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
Bug#795954: sysconfig-hardware contains various syntax errors in "case" commands
On Tue, Aug 18, 2015 at 06:07:57AM -0400, Stephen Powell wrote: > The sysconfig-hardware package contains a number of syntax errors in "case" > commands. The "case" command requires that after each pattern specification > there must be a command list, and this command list must be terminated by > a double semicolon. This is incorrect if you look at POSIX: The compound-list for each list of patterns, with the possible exception of the last, shall be terminated with ";;". http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html "Case Conditional Construct" > In some places, the only thing between the end of the pattern > specification and the double semicolon is a comment. A comment is not > a list. A null command (a colon) will do, but there must be at least > one command present to constitute a list. In other places, there is > no double semicolon to terminate the list. This also is a violation > of the rules of valid syntax. Well, all of the scripts declare that they are run with bash. It's clearer to pass in the : built-in and I couldn't find language lawyering that would allow the empty compound-list here at first glance, but it's also highly unlikely that bash will change in a fashion that forbids this. To improve correctness it makes sense to apply the patch. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#797340: choose-mirror: use httpredir.debian.org by default
On Sat, Aug 29, 2015 at 01:05:07PM -0400, Michael Gilbert wrote: This article [0] had some extensive complaints about Debian, one of which is that the installer has too many screens (apparently 20 in their case). Setting a default mirror without user intervention would nicely save 3 of those steps, and httpredir.debian.org is in many ways the ideal mirror selection anyway. I have seen issues with this. It might be good for the general case of apt where you see what the failure is and can retry if needed. But in the US it caused me some aborted installations because there was some mirror in the rotation that was broken. debian-installer - I guess in this case debootstrap - does not retry a broken file. (apt also doesn't do that but it's harder to figure out in d-i what's going on.) Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#647317: CVE-2011-4092
On 2015-07-22 13:15, Jonathan Wiltshire wrote: Recently you fixed one or more security problems and as a result you closed this bug. These problems were not serious enough for a Debian Security Advisory, so they are now on my radar for fixing in the following suites through point releases: squeeze (6.0.8) - use target oldstable Please prepare a minimal-changes upload targetting each of these suites, and submit a debdiff to the Release Team [0] for consideration. They will offer additional guidance or instruct you to upload your package. This was a fix by removal. Maybe your script should match for +rm fixed versions? Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793204: RM: net6 -- ROM; obsolete
Package: ftp.debian.org Severity: normal net6 had obby as its only reverse-depends. It is now gone and there is no other known user of the library. Let's remove it. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629430: Ends up as the default for text documents
On Mon, Jun 06, 2011 at 10:11:13AM -0700, Josh Triplett wrote: Gobby seems to have managed to end up as the default program used to open text documents, at least in some circumstances. This should never happen; gobby should exist on the list of available options, but never as the default. It seems to me as if this is working correctly now, at least in Jessie. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#459613: save all documents at once
On Mon, Jan 07, 2008 at 05:08:03PM +0100, Nico Golde wrote: if you work with a large set of files (e.g. source code) it's always a pain to save all files before you start compiling. It would be nice to have a Save all documents button. This has been fixed in gobby-infinote which is now the default. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#636051: gobby-0.5: Status display not correctly updated/cleared
On Sat, Jul 30, 2011 at 04:42:58PM +0200, Simon Kainz wrote: Trying to connectto a non existant host displays a ,essgae Could not resolve hostname hostname in the status bar. After a sucessful connection attempt, this message does not get cleared, so it seems like there is still some problem concerning hostname resolving. This has in the meantime been fixed. The status is now displayed with the server entry in the list, rather than in the status bar. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#605901: gobby-0.5: gobby stores everything in ~/.infinote-records
Control: reopen -1 Control: reassign -1 gobby Control: tag -1 + upstream On Sat, Dec 04, 2010 at 04:08:23PM +0100, Christoph Kluenter wrote: Gobby stores everthing in a log in ~/.infinote-records There is no option to delete the log. The log does not get truncated automatically. It is not even clear that the log belongs to gobby. It could reach back for years. There should be an option for deleting old logs on startup. This is still a valid bug report. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#681520: gobby-0.5: please add shortcut for changing font size
Control: reopen -1 Control: reassign -1 gobby On Fri, Jul 13, 2012 at 02:44:31PM -0600, Ansgar Burchardt wrote: It would be nice if there was a shortcut to change the font size inside gobby, eg. [Ctrl]-[+] and [Ctrl]-[-]. This is still a vali feature request. In a way it should be supported by GtkSourceView. On the other hand it would make projector use much easier. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#788605: gobby: Please add bookmarks
On Sat, Jun 13, 2015 at 02:33:17PM +, Damyan Ivanov wrote: Strangely, when the same URL is entered in the File→Open Location dialog, the result is Failed to open infinote:// Requested location not supported. Shall I report that as a separate bug? Basically it's another bug. I have filed [1] for this, but you won't get a Debian bug update once it's fixed. ;) Kind regards and thanks Philipp Kern [1] https://github.com/gobby/gobby/issues/82 signature.asc Description: Digital signature
Bug#788605: gobby: Please add bookmarks
Control: reopen -1 Control: reassign -1 gobby-infinote On Sat, Jun 13, 2015 at 07:41:21AM +, Damyan Ivanov wrote: I wish gobby had support for bookmarks. It is very annoying to have to connect to gobby.deban.org (thankfully there's the quick connection box, but that doesn't connect right after selecting the server from the history, you have to also press enter), then navigate through the tree to find the document you want to work on. All of the above could be streamlined via bookmarks - up and running in just two clicks. This is still a valid feature request for gobby-infinote. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#792764: RM: sobby -- ROM; obsolete
Package: ftp.debian.org Severity: normal sobby is the dedicated server for the old gobby which was recently removed. So this package should go away as well. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792765: RM: obby -- ROM; obsolete
Package: ftp.debian.org Severity: normal With the removal of the old gobby, obby (the library) is obsolete and can be removed. It has one rdepends (sobby), whose removal is being requested in #792764. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792212: RM: gobby-infinote -- ROM; obsolete, replaced by gobby-infinote
Package: ftp.debian.org Severity: normal gobby-infinote (aka gobby 0.5.x) is the successor to gobby. gobby 0.4.x is obsolete and not developed anymore. Please remove it from the archive. Please do not remove the gobby binary package, as it's still provided and built by gobby-infinote. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788605: gobby: Please add bookmarks
On Sat, Jun 13, 2015 at 07:41:21AM +, Damyan Ivanov wrote: I wish gobby had support for bookmarks. It is very annoying to have to connect to gobby.deban.org (thankfully there's the quick connection box, but that doesn't connect right after selecting the server from the history, you have to also press enter), then navigate through the tree to find the document you want to work on. All of the above could be streamlined via bookmarks - up and running in just two clicks. I'll forward it upstream, thanks. Note that you can pass URLs to Gobby, so in theory you could at least create a launcher that opens the document at the correct location. But I realize that this has a lot more overhead than a list of (server, path) tuples that are presented as quick jump entries. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786720: jessie-pu: package libinfinity/0.6.6-1~deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu I'd like to update libinfinity in jessie from 0.6.5-1 to 0.6.6-1. That maintenance upstream release contains a three line fix for a security issue (CVE-2015-3886), one fix to avoid some failing assertions when handling the cursor while editing a document and a crash fix in the client code. I'd upload the version as 0.6.6-1~deb8u1 to jessie. The release noise is fairly minimal, see the attached diff between 0.6.5-1 (stable) and 0.6.6-1 (unstable). I can also pull any of the patches into 0.6.5-1 and base a +deb8u1 off that. Kind regards and thanks Philipp Kern diff -Nru libinfinity-0.6.5/ChangeLog libinfinity-0.6.6/ChangeLog --- libinfinity-0.6.5/ChangeLog 2015-01-18 02:29:29.071909458 +0100 +++ libinfinity-0.6.6/ChangeLog 2015-05-13 02:57:57.089748067 +0200 @@ -1,3 +1,99 @@ +commit a5bc24e87714d3c3fa75711c5d06b9b8e4c81d53 +Author: Armin Burgmeier ar...@arbur.net +Date: Tue May 12 20:12:52 2015 -0400 + +Release libinfinity 0.6.6 + + NEWS | 9 + + 1 file changed, 9 insertions(+) + +commit 3862714b942fe626308f06e01730df7b48921faf +Author: Armin Burgmeier ar...@arbur.net +Date: Tue May 12 20:55:41 2015 -0400 + +Fix make distcheck for recent automake versions + +Recent automake versions run with a more restrictive umask, so that the +version.xml files are created with read-only permissions. This fails when +trying to override them, so remove them explicitly before. + + docs/reference/Makefile.am | 2 ++ + 1 file changed, 2 insertions(+) + +commit 06fa9455c687a67e4fc2c2f201817c64c73a3fcf +Author: Armin Burgmeier ar...@arbur.net +Date: Mon May 11 22:59:34 2015 -0400 + +Fix expired certificate validation (gobby #61) + + libinfgtk/inf-gtk-certificate-manager.c | 6 -- + 1 file changed, 4 insertions(+), 2 deletions(-) + +commit 244c7e8d69b98330ac7a285922c6fcb0a167ae20 +Author: Armin Burgmeier ar...@arbur.net +Date: Tue May 5 20:45:45 2015 -0400 + +Update caret position when only updating fixline state + +When the user inserts some newlines that are swallowed by the fixline +buffer, then still advance the user's cursor such that newly +to-be-written +text is inserted after the imaginary newline. + + libinftext/inf-text-fixline-buffer.c | 54 ++ + 1 file changed, 54 insertions(+) + +commit fb0c8532694476f3f624f66eb12becf851147e27 +Author: Armin Burgmeier ar...@arbur.net +Date: Mon May 4 20:31:12 2015 -0400 + +fixline buffer: Fix crash when iterating backwards through empty +base buffer + + libinftext/inf-text-fixline-buffer.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +commit da06a82642c1d2d0d5a44f1ea3f62ad0b2b22c9a +Author: Armin Burgmeier ar...@arbur.net +Date: Sun May 3 17:07:46 2015 -0400 + +Fix insert/erase notifications in InfTextFixlineBuffer + +The notifications were missing when the fixline buffer was modified +directly +with the API, and not in response to modifications to the underlying base +buffer. + + libinftext/inf-text-fixline-buffer.c | 10 ++ + 1 file changed, 10 insertions(+) + +commit 9b009160dd658fe9272d69025a8225b02eafb8de +Author: Armin Burgmeier ar...@arbur.net +Date: Thu Apr 30 21:37:23 2015 -0400 + +Fix create_end_iter() implementation in InfTextFixlineBuffer + + libinftext/inf-text-fixline-buffer.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +commit 8990cf98ab43f3aca6a7bf12e9608b0e2e9b5c70 +Author: Armin Burgmeier ar...@arbur.net +Date: Fri Apr 3 13:04:24 2015 -0400 + +Fix a crash when the server explicitly changes client account to default + + libinfinity/client/infc-browser.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +commit 0ce00121225662125b2ae4e48ff5d9f712e86a70 +Author: Armin Burgmeier ar...@arbur.net +Date: Sat Jan 17 20:33:25 2015 -0500 + +Post-release bump to 0.6.6 + + configure.ac | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + commit 1a0ff8091afdfe831d317d10c377a8a025ea259d Author: Armin Burgmeier ar...@arbur.net Date: Sat Jan 17 20:19:38 2015 -0500 diff -Nru libinfinity-0.6.5/configure libinfinity-0.6.6/configure --- libinfinity-0.6.5/configure 2015-01-18 02:21:51.575927350 +0100 +++ libinfinity-0.6.6/configure 2015-05-13 02:14:48.253651523 +0200 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for libinfinity 0.6.5. +# Generated by GNU Autoconf 2.69 for libinfinity 0.6.6. # # Report bugs to ar...@arbur.net. # @@ -590,8 +590,8 @@ # Identity of this package. PACKAGE_NAME='libinfinity' PACKAGE_TARNAME='libinfinity' -PACKAGE_VERSION='0.6.5' -PACKAGE_STRING='libinfinity 0.6.5' +PACKAGE_VERSION='0.6.6' +PACKAGE_STRING='libinfinity 0.6.6' PACKAGE_BUGREPORT='ar...@arbur.net' PACKAGE_URL='' @@ -1416,7 +1416,7 @@ # Omit some internal or obsolete options to make the list
Bug#769030: closed by Debian FTP Masters ftpmas...@ftp-master.debian.org (Bug#769030: fixed)
On 2015-04-09 22:30, Ansgar Burchardt wrote: was this the only change applied? Because there were more packages in the subject. No, I updated the other two packages as well. However dak override can only update one package at a time so I closed the bug report with the first of the changes. Thanks! Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782133: gobby: wrongly archived as metapackage
On 2015-04-08 12:21, Jonas Smedegaard wrote: In the control file, gobby is declared a metapackage - likely missed after the transition form gobby-0.5. Missed is the wrong word: #769030. Also no clue if all of them were changed. Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769030: closed by Debian FTP Masters ftpmas...@ftp-master.debian.org (Bug#769030: fixed)
Hi Ansgar, On 2015-04-09 12:39, ow...@bugs.debian.org wrote: #769030: override: gobby-infinote:oldlibs/extra, gobby-0.5:oldlibs/extra, gobby-0.5-dbg:oldlibs/extra, gobby:net/optional [...] We believe that the bug you reported is now fixed; the following changes were made to the overrides... Concerning package gobby-infinote... Operating on the unstable suite Changed priority from optional to extra Changed section from net to oldlibs was this the only change applied? Because there were more packages in the subject. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
On Wed, Feb 18, 2015 at 10:05:27PM +, Steven Chamberlain wrote: We did expect that during freeze, some regressions may be introduced that affect only GNU/kFreeBSD, and we'd have to fix things up in our unofficial release, perhaps rolling packages back to an older version, or uploading a patched version with +kfreebsd suffix. So, I'm happy if you decide to revert this. At first glance, it reads like a limitation of udhcpc/dhcp6c only? Killing it sounds like a workaround (which perhaps creates other issues), and an ifdef linux also seems wrong in this context (and for Ubuntu). kill-all-dhcp could be told never to kill ISC dhclient, but that too is wrong, as this is also used to implement the 'Cancel' button in the netcfg dialogs. Maybe there is still a better solution? Or perhaps we could add something that kills *only* udhcpc/dhcp6c, could clearly annotate it as this is a workaround for bug #768188. Then it shouldn't affect Ubuntu, or derivatives/ports using ISC DHCP at all. And if many years pass before someone comes back to look at this, they should understand why it's there. Not killing the DHCP clients is the right thing to do. Leases really should be refreshed during d-i, everything else is madness. But that's not even what's happening with dhclient because it's being run in one-shot mode (-1) and will exit after it acquired a lease successfully. The revert I supposed would've been for jessie as the DHCPv6 hang is quite a nasty regression on Linux. But for the future we should really a) use one client on all the platforms and b) let it renew the lease properly. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
On Tue, Feb 10, 2015 at 09:22:25AM +0100, Philipp Kern wrote: On Sun, Feb 08, 2015 at 04:21:25PM +0100, Philipp Kern wrote: On the other hand it also seems wrong for di_exec_shell_log to continue after the invoked binary exited. I suspect that'd mean ppoll() and proper signal handling, but I'm at a loss right now how to do that properly in C. Maybe that's the right place to fix it in the meantime. I guess signalfd would make this rather neat, but it's not available on FreeBSD. :( The alternative would be to overwrite the SIGCHLD signal handler regardless of what has been set before and handle the signal in the library. So now I guess the question is if we revert the change that broke it: Don't kill_dhcp_client without reason (Closes: #757711, #757988) Do not kill_dhcp_client after setting the hostname and domain, otherwise Linux udhcpc will stop renewing its lease, and on other platforms dhclient will de-configure the network interface (Closes: #757711, #757988) At this point kFreeBSD is no longer a release architecture and the other platform using dhclient is Ubuntu. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#731940: buildd.debian.org: consider stderr as well as stdout before timeout
On Sun, Feb 15, 2015 at 10:30:11AM +0100, Johannes Schauer wrote: I'm CCing the sbuild maintainers because it probably needs to be fixed there first. Should instead this bug not be reassigned to sbuild? This bug even has a patch - fixing it should be trivial. Yeah, fix it in mainline sbuild. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
On Sun, Feb 08, 2015 at 04:21:25PM +0100, Philipp Kern wrote: On the other hand it also seems wrong for di_exec_shell_log to continue after the invoked binary exited. I suspect that'd mean ppoll() and proper signal handling, but I'm at a loss right now how to do that properly in C. Maybe that's the right place to fix it in the meantime. I guess signalfd would make this rather neat, but it's not available on FreeBSD. :( The alternative would be to overwrite the SIGCHLD signal handler regardless of what has been set before and handle the signal in the library. Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776735: error: no alternatives for gobby
On 2015-02-10 10:24, Goswin von Brederlow wrote: As a side node the old, unconditional removal of the alternatives violates the idempotency of the script. The installation can fail, which I think happened in my case due to other packages failing, or be aborted after the preinst has run. Then when the installation is tried again removing the alternative fails because it is already gone. Fair point. Thanks! Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777566: RM: gobby [all] -- ROM; NVIU
Package: ftp.debian.org Severity: normal Please delete the gobby arch:all binary package 0.4.13-2 from sid. It has been superseded by the 0.5.0-4 arch:any binary package built by gobby-infinote. Please also delete the gobby source package 0.4.13-2, along with the other binaries built from it (gobby-0.4 and gobby-0.4-dbg) from sid. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776735: error: no alternatives for gobby
On Sat, Jan 31, 2015 at 11:15:22PM +0100, Goswin von Brederlow wrote: Updating gobby from 0.4.13-1 to 0.5.0-4 fails with: Preparing to unpack .../gobby_0.5.0-4_amd64.deb ... update-alternatives: error: no alternatives for gobby dpkg: error processing archive /var/cache/apt/archives/gobby_0.5.0-4_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 2 Did this legitimally happen upon upgrade? Because I would've expected gobby-0.4 and gobby-0.5 to have been around. (Of course one can force this to appear using dpkg -i and not satisfying dependencies, just wondering if that happened here.) I'll fix it anyhow, just trying to figure out if that needs to go into jessie. Kind regards and thanks for the report Philipp Kern signature.asc Description: Digital signature
Bug#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
On Thu, Dec 18, 2014 at 03:04:38PM +0100, Peter Valdemar Mørch wrote: netcfg: Do not kill_dhcp_client after setting the hostname and domain, otherwise Linux udhcpc will stop renewing its lease, and on other platforms dhclient will de-configure the network interface (#757711, #757988). The call chain is this: udpkg --configure --force-configure netcfg \_ netcfg Z \_ dhcp6c \_ udhcpc udpkg does not collect netcfg's exit code. Instead it continues poll()ing to forward stderr. It receives the SIGCHLD but does not act upon it with a wait() or waitpid(). The function udpkg uses to invoke netcfg's configure comes from libdebian-installer: [...] snprintf(buf, sizeof(buf), exec %s configure, config); if ((r = di_exec_shell_log(buf)) != 0) [...] Essentially dhcp6c and udhcpc need to be daemonized off correctly once they go into lease acquired, renew in the background mode and close their file descriptors[*]. However doing that early likely loses logging, so it'd be best if the programs would do the right thing. At least udhcpc calls bb_daemonize(0), which doesn't do any fd closing. For dhcp6c (wide-dhcpv6-client) we currently force foreground mode (-f). It is not sufficient for netcfg to simply close stderr, as all producers need to close it, as far as I understand. On the other hand it also seems wrong for di_exec_shell_log to continue after the invoked binary exited. I suspect that'd mean ppoll() and proper signal handling, but I'm at a loss right now how to do that properly in C. Maybe that's the right place to fix it in the meantime. Kind regards Philipp Kern [*] It has been a long-standing problem with some d-i (maybe just Ubuntu with isc-dhcp-client) that leases are not renewed during the runtime of the installation. Which might break networking when the switch throws you off post-expiry. signature.asc Description: Digital signature
Bug#776142: unblock: libinfinity/0.6.5-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libinfinity
libinfinity 0.6.5 contains multiple crash fixes. I'd feel much better if
those were included in the package. The diff is slightly noisy, but
mostly because of the new tarball (noise in the changelog, the
documentation output, and translations). A debdiff reduced to *.ac and
*.c changes is attached.
Changelog:
* Fix a crash when sending unsubscribe message causes connection failure
* InfdDirectory: Fail add-subdirectory request if name already exists
* Fix assertion failure when directory without storage is disposed
* Fix a memory leak in the plugin manager
* Make sure messages are not attempted to be sent on closed connections
* Add a missing status notify in InfXmppConnection
* Fix error message in server log when a client certificate is not
trusted
* Fix possible memory corruption on insert in fixline buffer
Only relevant for FreeBSD and Mac OS X:
* Check whether we need -lresolv for res_query() (gobby #23)
* infinoted-plugin-document-stream: Only use MSG_NOSIGNAL if available
(#7)
* inf-name-resolver: Include arpa/nameser.h and
arpa/nameser_compat.h
unblock libinfinity/0.6.5-1
--- libinfinity-0.6.3/configure.ac 2014-10-09 19:28:17.794128998 +0200
+++ libinfinity-0.6.5/configure.ac 2015-01-18 02:14:02.575945693 +0100
@@ -1,4 +1,4 @@
-m4_define([libinfinity_version], [0.6.3])
+m4_define([libinfinity_version], [0.6.5])
m4_define([libinfinity_api_version], [0.6])
m4_define([libinfinity_libtool_version], [0:0:0])
@@ -125,7 +125,41 @@
if test $platform = 'win32'; then
infinity_LIBS=$infinity_LIBS -lws2_32 -ldnsapi
else
- infinity_LIBS=$infinity_LIBS -lresolv
+ # Check whether we need libresolv for res_query()
+ # Can't use AC_SEARCH_LIBS because res_query is a macro defined in
+ # resolv.h
+ AC_MSG_CHECKING(for res_query)
+ AC_TRY_LINK(
+[
+ #include sys/types.h
+ #include netinet/in.h
+ #include arpa/nameser.h
+ #include resolv.h
+],
+[res_query(NULL, 0, 0, NULL, 0);],
+[
+ # res_init() available in libc
+ AC_MSG_RESULT(yes)
+],
+[
+ LIBS=-lresolv
+ AC_TRY_LINK(
+[
+ #include sys/types.h
+ #include netinet/in.h
+ #include arpa/nameser.h
+ #include resolv.h
+],
+[res_query(NULL, 0, 0, NULL, 0);],
+[
+ AC_MSG_RESULT(in libresolv)
+ LIBS=
+ infinity_LIBS=$infinity_LIBS -lresolv # res_init available in libresolv
+],
+[AC_MSG_ERROR(res_query not provided by either libc or libresolv)]
+ )
+]
+ )
fi
###
--- libinfinity-0.6.3/infinoted/infinoted-plugin-manager.c 2014-08-29 16:48:38.249337739 +0200
+++ libinfinity-0.6.5/infinoted/infinoted-plugin-manager.c 2015-01-06 13:31:49.049584900 +0100
@@ -781,6 +781,8 @@
g_hash_table_unref(priv-connections);
g_hash_table_unref(priv-sessions);
+ g_free(priv-path);
+
G_OBJECT_CLASS(parent_class)-finalize(object);
}
--- libinfinity-0.6.3/infinoted/plugins/infinoted-plugin-certificate-auth.c 2014-08-29 16:48:38.253337778 +0200
+++ libinfinity-0.6.5/infinoted/plugins/infinoted-plugin-certificate-auth.c 2015-01-06 13:26:07.697569755 +0100
@@ -136,7 +136,7 @@
if(res != GNUTLS_E_SUCCESS)
inf_gnutls_set_error(error, res);
else if( (verify_result GNUTLS_CERT_INVALID) != 0)
- inf_gnutls_certificate_verification_set_error(error, res);
+ inf_gnutls_certificate_verification_set_error(error, verify_result);
if(error != NULL)
{
--- libinfinity-0.6.3/infinoted/plugins/infinoted-plugin-document-stream.c 2014-10-09 19:28:17.798128984 +0200
+++ libinfinity-0.6.5/infinoted/plugins/infinoted-plugin-document-stream.c 2015-01-18 02:14:02.575945693 +0100
@@ -40,6 +40,8 @@
#include string.h
#include errno.h
+#include config.h
+
typedef enum _InfinotedPluginDocumentStreamStatus {
INFINOTED_PLUGIN_DOCUMENT_STREAM_NORMAL,
INFINOTED_PLUGIN_DOCUMENT_STREAM_RECEIVING,
@@ -882,7 +884,17 @@
do
{
-bytes = send(stream-socket, data, len, MSG_NOSIGNAL);
+bytes = send(
+ stream-socket,
+ data,
+ len,
+#ifdef HAVE_MSG_NOSIGNAL
+ MSG_NOSIGNAL
+#else
+ 0
+#endif
+);
+
errcode = errno;
if(bytes 0)
@@ -990,7 +1002,11 @@
stream-socket,
stream-recv_queue.data + queue_offset,
stream-recv_queue.alloc - queue_offset,
+#ifdef HAVE_MSG_NOSIGNAL
MSG_NOSIGNAL
+#else
+ 0
+#endif
);
errcode = errno;
--- libinfinity-0.6.3/libinfinity/client/infc-session-proxy.c 2014-08-29 16:48:38.265337895 +0200
+++ libinfinity-0.6.5/libinfinity/client/infc-session-proxy.c 2015-01-06 16:49:15.242110509 +0100
@@ -120,7 +120,11 @@
);
}
- infc_session_proxy_release_connection(proxy);
+ /* If an error occurs while sending the session-unsubscribe message, the
+ * connection is released
Bug#746967: buildd.debian.org: d-i daily builds happen with unsigned code from alioth
On Thu, Sep 11, 2014 at 10:49:06PM +0200, Aurelien Jarno wrote: If we choose this solution, here is a quick and dirty patch against di-autobuild to do that. It's basically changing the hardcoded paths and call to schroot. There is probably more fixes/cleanup to do, but it's just a proof of concept to show this solution works without additional privilege on the porterboxes. Note that I haven't tried the upload part, but I guess it's just a matter of having the right packages installed (if not already the case). We probably want to have a dedicated d-i account for that on the porterbox. Also we have only one amd64/i386 porterbox, and the current script doesn't support that, but that should be easy to test. If this solution is chosen, I'll be happy to continue working on this script as time permits. I'm ok with this approach for the time being. Obviously building on real infrastructure the way other stuff is built would be even better. (For instance binNMUing the unstable d-i into experimental every day, or similar.) Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#773712: unblock: jenkins-job-builder/0.9.0-0.1
retitle 773712 pre-approval: unblock: jenkins-job-builder/0.9.0-0.1 tag 773712 + confirmed thanks On Mon, Dec 22, 2014 at 03:29:36PM +0100, Michael Prokop wrote: The version of jenkins-job-builder as available in current jessie is totally broken with regards to its feature to delete Jenkins jobs. There's a fix available from upstream which I included in version 0.9.0-0.2. I've also verified that the fix works as needed. Please unblock package jenkins-job-builder: unblock jenkins-job-builder/0.9.0-0.2 Debdiff of the package versions as in jessie vs. what I just uploaded to Debian/unstable (not yet accepted there though/disclaimer): Looks good to me, but still not accepted. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#773515: unblock: mono/3.2.8+dfsg-9
tag 773515 + confirmed thanks On Fri, Dec 19, 2014 at 11:55:00AM +, Jo Shields wrote: Please unblock package mono There are a couple of long-standing bugs in the Mono package, which are fixed by this proposed upload to Unstable. #771389 prevents IPv6 from working in Mono-based apps It's a behavior change, but I'm inclined to let you fix the resolver here to be in line with the remainder of the distribution. #773509 and #773511 relate to the mono-runtime-dbg package not being correctly populated (and currently being useless) Looks fine. Please go ahead with the upload and report back once it has been accepted. Kind regards and thanks for your efforts Philipp Kern signature.asc Description: Digital signature
Bug#773515: unblock: mono/3.2.8+dfsg-9
On Fri, Dec 19, 2014 at 11:55:00AM +, Jo Shields wrote: Please unblock package mono This doesn't seem to have hit sid yet. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#773515: unblock: mono/3.2.8+dfsg-9
retitle 773515 pre-approval: mono/3.2.8+dfsg-9 thanks On Mon, Dec 22, 2014 at 10:11:51AM +, Jo Shields wrote: On 22/12/14 09:35, Philipp Kern wrote: On Fri, Dec 19, 2014 at 11:55:00AM +, Jo Shields wrote: Please unblock package mono This doesn't seem to have hit sid yet. I was scolded for asking the release team should I upload this, will it be accepted for Jessie? and told to file an unblock bug. So it's a pre-approval. Re-titling appropriately. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#768188: Jessie Installer hangs after processing DHCPv6 stateful addressing
On Thu, Dec 18, 2014 at 03:04:38PM +0100, Peter Valdemar Mørch wrote: This occurs in in our work environment in VMware Workstation and Proxmox when using bridged eth0, but not when using NAT. In my home network, the exact same procedure goes through without any hangs for both bridged and NAT. VMware Workstation's IPv6 support is full of sadness. Which virtualization do you use with Proxmox? But please tell me: Why is there no Router Advertisement in the packet dump? I see Router Solicitations and DHCPv6 interactions, but no RA. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#769961: hard-coded UIDs and GIDs
On Fri, Dec 12, 2014 at 01:32:59PM +0100, Hans-Christoph Steiner wrote: Right now, the package is only installable on systems that do not have the linux-image meta-package installed and are very likely to in a chroot. So that eliminates the majority of Debian installs as candidates where this package is installable. Ideally there would be a way to actually detect the Android kernel, I have not found that way. I wonder if you could probe for either ashmem or binder? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#766773: Bug#772476: nmu: irssi-plugin-xmpp_0.52+git20140102-2
On Sun, Dec 07, 2014 at 04:49:18PM +0100, gregor herrmann wrote: It seems that after irssi-plugin-otr, now irssi-plugin-xmpp needs a binNMU as well against the new irssi. Cf. #766773 for details. If you agree could you please: nmu irssi-plugin-xmpp_0.52+git20140102-2 . ALL . -m Rebuild against irssi 0.8.17. I did that now. But this seems wrong to me to begin with. There should be package dependencies that express this. (And essentially new uploads by irssi would be transitions.) Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#766932: wheezy-pu: package wireless-regdb/2014.10.07-1~deb7u1
Control: tag -1 + confirmed Hi, On Sun, Oct 26, 2014 at 03:07:00AM +, Ben Hutchings wrote: I have again updated wireless-regdb in unstable to a new upstream release. There have been many changes to the database based on new regulations and information about additional countries. These should also go into stable so that users can easily comply with current laws and use the full permitted ranges of frequency and transmit power. please go ahead. Thanks! Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#717457: pu: package oss4/4.2-build2006-2+deb7u2
Hi, On Sat, Aug 03, 2013 at 07:09:58PM +0200, Andreas Beckmann wrote: Attached is a new version of the patch with the dependency on libc6-dev replaced by libc6-dev [!alpha !ia64 !hurd-i386] | libc0.3-dev [hurd-i386] | libc6.1-dev [alpha ia64] | libc-dev (as used by build-essential). hurd-i386 doesn't make sense for a linux-any package. alpha is not a release architecture in wheezy. So I think this could be simplified as libc6-dev [!ia64] | libc6.1-dev [ia64]. I wonder if the single provider of libc-dev would just be picked correctly if that'd be used. Assuming that you tested that in a minimal chroot and that this is sufficient vs. build-essential, I'd be inclined to approve the upload. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#717445: pu: package ndiswrapper/1.57-1+deb7u1
Control: tag -1 + moreinfo Hi, On Sun, Jan 26, 2014 at 02:57:22PM +0100, Julian Andres Klode wrote: I'm most likely going to ship the patch below in 1.59-2, it just drops the detection and hard-codes the modprobe.d/ndiswrapper.conf file, as the other locations are not supported anymore. if this request still applies, please provide an updated debdiff against stable of what you want to ship. Thanks! Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#762194: Summary:Re: Bug#762194: Proposal for upgrades to jessie (lendows 1)
On Sat, Nov 29, 2014 at 07:15:08PM +0100, Svante Signell wrote: One claim is changed, see below. On Fri, 2014-11-28 at 12:56 +0100, Svante Signell wrote: Hello, In summary: a) Upgrades should _not_ change init: whatever is installed should be kept. b) New installs should get systemd-sysv as default init with a debconf message about alternative init systems. Since there is no interest in adding a debconf message on new installs, I wish for a menu entry in the advanced part of the installer to be able to install a new system with sysvinit-core or upstart! That's even more unlikely than to add a debconf message (which would be package-owned). Yes, debian-installer is frozen. This would add new udebs, new strings, new everything. We're actually trying to release. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#762194: Summary:Re: Bug#762194: Proposal for upgrades to jessie (lendows 1)
On 2014-11-29 21:30, Steve Langasek wrote: Debian releases when it's ready. If large numbers of our users are going to have a bad experience with jessie as a result of being switched to systemd, then we should take appropriate steps to address that, even if that means unfreezing the installer. Sure. But where is the evidence for that? Is there a bug that has been agreed upon to be RC? I am not saying that making init systems a choice in the installer is the right solution here; I don't think that it is. But I also don't think that the release freeze can reasonably be an argument against it. Not even the release freeze, rather the d-i freeze. Unless this is RC for d-i, that is. Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599128: binNMU numbers not shown in webui except for sid/unstable
On Fri, Nov 28, 2014 at 05:26:27PM +, Wookey wrote: This demo only lasts as long as 'xz-utils' has binNMUskew. Pick any other package that currently does to demonstrate the issue: This URL (for unstable) shows binNMU versions in the 'Version' column https://buildd.debian.org/status/package.php?p=xz-utilssuite=sid Thus URL (for jessie) only shows the base version https://buildd.debian.org/status/package.php?p=xz-utilssuite=jessie This does not seem to be a bug in pgstatus, which just displays what the database returns. Clearly it is a different manifestation of the above 'wb nmu' issue I just spent some time perusing the pgstatus and wanna build sources. I didn't find anything in pgstatus which special-cases by suite when displaying package.php. It just asks the database for version and binary_nmu_version and displays those. So, unsurprisingly, this seems to be in wanna-build. That's normal and a long-standing issue. Is there a problem with this except cosmetics? We don't claim to export the authoritative source of binary versions of source packages. (Obtaining it is left as an exercise to the reader, as every package can have a different binary version number. A rebuild might theoretically stop producing a certain binary package, etc. That being said, Installed-Version aka installed_version is what wb nmu actually uses to determine the next NMU version to use - because wanna-build does not actually know.) Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#769693: Please giveback libjogl2-java
On Sat, Nov 15, 2014 at 06:44:05PM +0100, gregor herrmann wrote: libjogl2-java failed to build on arm64, ppc64el, and s390x because of a bug in gluegen2 (#769003) which should be fixed in 2.2.4-2. Can you please gb libjogl2-java on those architectures? Something like (apologies if I got the syntax wrong): gb libjogl2-java_2.2.4+dfsg-1 . arm64 ppc64el s390x dw libjogl2-java_2.2.4+dfsg-1 . arm64 ppc64el s390x . -m 'libgluegen2-build-java (= 2.2.4-2), libgluegen2-rt-java (= 2.2.4-2)' The packages you specified are already available (arch:all, but even -jni is there already), so the dep-wait is not necessary. I gave the package back on the architectures you requested. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#769693: Please giveback libjogl2-java
On Sat, Nov 15, 2014 at 10:02:10PM +0100, gregor herrmann wrote: On Sat, 15 Nov 2014 21:58:22 +0100, Philipp Kern wrote: gb libjogl2-java_2.2.4+dfsg-1 . arm64 ppc64el s390x dw libjogl2-java_2.2.4+dfsg-1 . arm64 ppc64el s390x . -m 'libgluegen2-build-java (= 2.2.4-2), libgluegen2-rt-java (= 2.2.4-2)' The packages you specified are already available (arch:all, but even -jni is there already), so the dep-wait is not necessary. Right; I'm just never sure if/when chroots on the buildds get updated. Sadly a dep-wait would not help here, as it's server-side. But then it only matters if the package is part of the base build chroot (like perl, or debhelper, or glibc). In that case there's another magic bit (extra-depends) that temporarily adds more stringent dependencies to the build-depends list. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#769591: unblock: owfs/2.9p8-6
Control: tag -1 + confirmed On Fri, Nov 14, 2014 at 09:06:08PM +0100, Vincent Danjean wrote: Please unblock package owfs Hi, In #769523, it has been reported that some spurious output can occurs when installing owfs-common. The reason is that ls is used to find with shell globs some files to handle but, when the glob do not match anything, ls complain. The bug is not RC but it occurs on (some) upgrade and the fix is really simple (redirect stderr of ls to /dev/null). As the bug is not RC, I ask you is it would be ok to upload this fix now (or if I must wait for jessie release). I know it is a purely cosmetic bug, no bad behavior is involved in any case. Sounds good to me. Please ping the bug once it has reached the archive. Thanks. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#769394: unblock: gamera/3.4.1+svn1423-2
On Sat, Nov 15, 2014 at 03:04:39AM +0100, Daniel Stender wrote: For my package Gamera another RC bug (#766740) remains and I'm working on a solution, I'm going to file another unblock request, when it's in Sid. Question regarding the upcoming new package I would like to ask in front: In the meanwhile I've forwarded some patches and toggled the patch header accordingly. These changes are already in the SVN repo. The changes for 3.4.1+svn1423-3 are going to be on top of these automatically - would it be alright to include that also, next to the fix of the remaining RC bug, or would that be a clean violation of the freeze policy in terms of that only changes are necessary to fix the bug are allowed, and I would have to work around the SVN situation? If you just changed metadata on top of the patches, that shouldn't pose a problem when reviewing. If patch content itself changed, that'd be different. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#766921: [Piuparts-devel] Bug#766921: piuparts fails with ValueError: too many values to unpack when dpkg prints a warning
On Wed, Oct 29, 2014 at 01:58:00PM +0100, Holger Levsen wrote: On Sonntag, 26. Oktober 2014, Simon Fondrie-Teitler wrote: When running piuparts, if sh or dkpg return warnings, they get included in the output that piuparts tries to parse and it prints a stack trace. indeed, thanks for your bug report! I'm not sure why gcc is not found, that may be its own bug. I have no idea neither... Further help and patches very much welcome! ;) I've noticed you're running piuparts on sid, I suspect the problem exist in wheezy (maybe just in theory..) too but dpkg behaves differently there... piuparts works for me on jessie if I add gcc to the minbase set by editing the debootstrap script. I guess an easy workaround would be passing in --include=gcc to debootstrap, but then we still don't know the root cause. ;-) But it's probably better to do that than having it broken out of the box on jessie. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#769316: unblock: gobby-infinote/0.5.0-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package gobby-infinote
The changes to gobby-infinote include a tiny cleanup (non-existent recommends
libinfinity-0.5-dbg to libinfinity-0.6-dbg) plus a fix to a not-cleaned-up
alternative.
diff -Nru gobby-infinote-0.5.0/debian/changelog
gobby-infinote-0.5.0/debian/changelog
--- gobby-infinote-0.5.0/debian/changelog 2014-10-19 10:31:47.0
+
+++ gobby-infinote-0.5.0/debian/changelog 2014-11-12 01:43:38.0
+
@@ -1,3 +1,10 @@
+gobby-infinote (0.5.0-4) unstable; urgency=medium
+
+ * Correct libinfinity-0.6-dbg recommends on gobby-dbg.
+ * Remove the gobby-0.5 alternative unconditionally. (Closes: #768242)
+
+ -- Philipp Kern pk...@debian.org Wed, 12 Nov 2014 02:42:44 +0100
+
gobby-infinote (0.5.0-3) unstable; urgency=medium
* Update debian/copyright to reflect the re-licensing from GPL to
diff -Nru gobby-infinote-0.5.0/debian/control
gobby-infinote-0.5.0/debian/control
--- gobby-infinote-0.5.0/debian/control 2014-10-18 22:01:56.0 +
+++ gobby-infinote-0.5.0/debian/control 2014-11-12 01:42:42.0 +
@@ -31,7 +31,7 @@
Depends: ${misc:Depends}, gobby (= ${binary:Version})
Breaks: gobby-0.5-dbg ( 0.5.0-2~)
Replaces: gobby-0.5-dbg ( 0.5.0-2~)
-Recommends: libinfinity-0.5-dbg, libgtkmm-2.4-dbg
+Recommends: libinfinity-0.6-dbg, libgtkmm-2.4-dbg
Description: infinote-based collaborative text editor - debugging symbols
Gobby is an editor which allows one to edit text documents and source files
collaboratively over a network. All users could work on the file
diff -Nru gobby-infinote-0.5.0/debian/gobby-0.5.postinst
gobby-infinote-0.5.0/debian/gobby-0.5.postinst
--- gobby-infinote-0.5.0/debian/gobby-0.5.postinst 1970-01-01
00:00:00.0 +
+++ gobby-infinote-0.5.0/debian/gobby-0.5.postinst 2014-11-12
12:06:10.0 +
@@ -0,0 +1,4 @@
+#!/bin/sh
+set -e
+update-alternatives --remove gobby /usr/bin/gobby-0.5
+#DEBHELPER#
unblock gobby-infinote/0.5.0-4
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768914: netcfg/wireless_wpa is type string, not type password
On Mon, Nov 10, 2014 at 05:07:25PM +1100, Trent W. Buck wrote: I just installed wheezy over WPA and ran into #694068. While investigating that, I grepped for my PSK across /. I found it in /var/log/installer/cdebconf/questions.dat under netcfg/wireless_wpa. It is stored in cleartext; the file is only readable by root. In templates.dat (same dir), I see Name: netcfg/wireless_wpa Type: string Description: WPA/WPA2 passphrase [...] Since it's a PASSPHRASE, shouldn't it be Type: password? Normal users cannot read questions.dat, so I don't think this is an immediate problem. (FWIW hostapd's wpa_psk_file option lets each device have its own PSK, so when Mallet is sacked and his PSK is revoked, he can't simply spoof Alice's MAC and use his PSK to get in. I don't use EAP-TLS client certs because support for that is depressingly limited. This means my PSKs are more secret than your typical home network where there's one shared PSK that everyone knows.) That discussion popped up earlier. The problem with Type: password is that you don't see what you're typing in d-i and this may be desirable given long complex passphrases (the over the shoulder attack was discarded). Sadly there's no easy way to toggle display in debconf (yet). But then this is the first time I read about this use of PSK instead of normal EAP keying. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#768920: RM: gobby-infinote/0.4.13-2
On Mon, Nov 10, 2014 at 08:55:20AM +, Adam D. Barratt wrote: What about sobby? That has both build- and runtime dependencies on both libobby and libnet6. sobby too, please. (How could I forget this... But then dak rm was very confused due to gobby(bin) being provided by !gobby(src).) Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#769030: override: gobby-infinote:oldlibs/extra, gobby-0.5:oldlibs/extra, gobby-0.5-dbg:oldlibs/extra, gobby:net/optional
Package: ftp.debian.org Severity: normal Hi, I'm trying to get rid of old packages. There used to be gobby-0.4 and gobby-0.5, both supporting incompatible protocols. I moved to provide gobby-0.5 only, in the regular gobby package. For a transitional period (i.e. jessie) I need the old packages to stay around to ensure a proper upgrade path. They will be removed in due course after jessie's release. However I need adjustments of the overrides to reflect this fact: make gobby a regular package and put the versioned packages into oldlibs. Please apply the change suggested in the subject. Thanks! Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768920: RM: gobby-infinote/0.4.13-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove the following *source* packages from jessie: gobby 0.4.13-2 net6 1:1.3.14-2 obby 0.4.8-1 gobby-infinote has taken over the gobby package just in time for the jessie freeze. I do not want gobby-0.4 to stay around for jessie, it won't receive any more updates upstream. net6 and obby are support packages only around for gobby-0.4 and can (and should) hence go as well. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765327: lintian fails if the machine has a link-local IPv6 nameserver configured
Package: libnet-dns-perl,lintian Severity: normal This is likely a bug in libnet-dns-perl but I wonder if there are network accesses from lintian. % lintian ./openclonk_5.5.1-1_amd64.changes warning: Cannot load check binaries unresolvable name: fe80::4ee6:76ff:fe51:ae30%eth0 at /usr/share/perl5/Email/Valid.pm line 41. Compilation failed in require at /usr/share/perl5/Lintian/Check.pm line 27. BEGIN failed--compilation aborted at /usr/share/perl5/Lintian/Check.pm line 27. Compilation failed in require at /usr/share/lintian/checks/binaries.pm line 30. BEGIN failed--compilation aborted at /usr/share/lintian/checks/binaries.pm line 30. Compilation failed in require at /usr/share/perl5/Lintian/CheckScript.pm line 253. This is due to: % cat /etc/resolv.conf [...] nameserver 10.0.3.1 nameserver fe80::4ee6:76ff:fe51:ae30%eth0 [...] The syntax is perfectly valid and understood by glibc, but apparently libemail-valid-perl tries to resolve(!?) it and fails. No, it just loads Net::DNS::Resolver: $Resolver = Net::DNS::Resolver-new; So it seems what explodes is Resolver/Base.pm's nameservers sub. The message lintian displays is rather awkward: for a runtime error (runtime configuration not parsable) one gets compilation failed. But I guess the load is already guarded, hence the warning? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lintian depends on: ii binutils 2.24.51.20140918-1 ii bzip2 1.0.6-7 ii diffstat 1.58-1 ii file 1:5.19-2 ii gettext0.19.2-2 ii hardening-includes 2.5+nmu1 ii intltool-debian0.35.0+20060710.1 ii libapt-pkg-perl0.1.29+b2 ii libarchive-zip-perl1.38-1 ii libclass-accessor-perl 0.34-1 ii libclone-perl 0.37-1+b1 ii libdpkg-perl 1.17.13 ii libemail-valid-perl1.195-1 ii libfile-basedir-perl 0.03-1 ii libipc-run-perl0.92-1 ii liblist-moreutils-perl 0.33-2+b1 ii libparse-debianchangelog-perl 1.2.0-1.1 ii libtext-levenshtein-perl 0.09-1 ii libtimedate-perl 2.3000-2 ii liburi-perl1.64-1 ii man-db 2.6.7.1-1 ii patchutils 0.3.3-1 ii perl [libdigest-sha-perl] 5.20.1-1 ii t1utils1.37-2.1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.18-3+b1 ii perl5.20.1-1 ii perl-modules [libautodie-perl] 5.20.1-1 Versions of packages lintian suggests: pn binutils-multiarch none ii dpkg-dev 1.17.13 ii libhtml-parser-perl3.71-1+b2 ii libtext-template-perl 1.46-1 ii libyaml-perl 1.12-1 ii xz-utils 5.1.1alpha+20120614-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764156: wheezy-pu: package debian-archive-keyring/2014.1~deb7u1
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, I would like to update the attached package update of debian-archive-keyring to proposed-updates. This is a backport of the package in unstable, which adds the Jessie key and replaces my key signing key with the current one in the keyring. Kind regards Philipp Kern diff -Nru debian-archive-keyring-2012.4/active-keys/add-jessie-stable debian-archive-keyring-2014.1~deb7u1/active-keys/add-jessie-stable --- debian-archive-keyring-2012.4/active-keys/add-jessie-stable 1970-01-01 01:00:00.0 +0100 +++ debian-archive-keyring-2014.1~deb7u1/active-keys/add-jessie-stable 2014-08-31 07:22:29.0 +0200 @@ -0,0 +1,68 @@ +Comment: add Jessie stable key (ID: CBF8D6FD518E17E1) +Date: Sun, 31 Aug 2014 07:22:29 +0200 +Action: import +Data: + -BEGIN PGP PUBLIC KEY BLOCK- + Version: GnuPG v1 + + mQINBFIPYFgBEAC2wn0GKL3a6ZI3WtoiRRNYeVEwiSr8xP1zhk+Xavi4XsoHPsru + vo+9DvDiIcID8zDkcbt7QG8QvLP7yN6ucKcZhGOO+NFwKtkDsmEpG35/e17j+M74 + IgrrDs1Z249JwGXb28YN6u6KQBcDudcPFeQ5oZa1bnjgFYHVIxLvriBAoiCf7sT8 + WBfqYoNnIm6w+uEJDK9p3x+6BsJx+lBSUH0ZFGGjnZg+FMhW+IgdkRK9q7y8ofJ6 + HVH1W34qJWTGdYybywJqyaiNbIG7w9a6zbInfOSWEcCTzv6qukK0qzSQecL3cxsD + 7MKbQuQKM3qHb2FDQPnMDuiZKKDb8/zL9sn7xj/OVVpk8nkwMT3wirdQ1EaKz+XM + 7NKu32TjUWsBZpZTHvip13Tu4E17/oeeB6xyjWXu8TDJyBbMXoHv28Ab+pj098it + 1UFZnGlQZRMEa15V7O6f1ym9jyWATGVZii7iH8M73bXGEhEbPT58YBzll0olIHZf + AjtxcONdX82bJDHVo0Fv/Ww4hoitC/6PfdksKpVV2s708OlXGyzBSQg1CE0ozJzK + xnAf6veD+Zol62RkmVwKihvwvK/oE04hyH5eWY+/A1NRyESVeTpI1JJ3URfYLufh + XNBsYjA6mpAgymBJs6+TODDLbquRyhUiKVhfaEmHihp6jz748jvXPU7W+QARAQAB + tDtKZXNzaWUgU3RhYmxlIFJlbGVhc2UgS2V5IDxkZWJpYW4tcmVsZWFzZUBsaXN0 + cy5kZWJpYW4ub3JnPokCPQQTAQgAJwUCUg9gWAIbAwUJDwmcAAULCQgHAwUVCAoJ + CwUWAgMBAAIeAQIXgAAKCRDL+Nb9UY4X4fOGD/94LCoWsVVV+gPfP8R9FCafg5x6 + 5y3QkuL7WlatQbTpZyVZK5XiaoIiWi31lZ3fHG3SRYoqbyYatcVIf8/m9LlRJLOB + ZwQW02sM7jLqf7oA3XLyUnpwgb4xQiNr0Wvdi7aL70/AJaNPL+J7EQZMLppIKoZU + 28UYIfuA7MCJbJXPBr7hBsyzolf6A0qVh7KSaIpdX7Rt3aHcmFkb3iSty99KHN1N + zjb+Y13AE0aXGaEbabZaH3b2cZ2/jrGp6VY2eB6qN0iIa+qQ0nkzR5lFsVq4R85E + Rhcwv6Zr8fp6IiNN/JIs5M1GJoFE8wkR7fEaQ6WK8QB/K2dUQ6y0LtA2t6rUcEVi + 8+/+Nerhal33KlT4ivUbE6X4Z4YqRqfKXDT0juJZR/LLjHWRQHy+pWPAs5DumCNi + J0xkieW6quZ80QoYOWZkyDEemWjgFknYepuT9zHPWeJqavJ5U7copMVdJ/41ESq/ + +J0NREgcWC++aJJdxNwfbOwtQbC+5/fCj0N9gOe6/rpu3BAi99CG6Si9KfBqAbCi + RzfjmLJkHjmAVCjCcduakSI/PfYW2DGS9Yt142zTuxsZP2hqGXFaBlGHbVyvh9Du + yJAPfnF6W22ueFYPoMayR3EqyGTQDohhuxZuYokp/nQZdS7AdV9tHbuMNh7f+dnc + 9u5+C3hTLYgLSvFsQYkEHAQQAQgABgUCVAH+wQAKCRBQw2NNOikc+ZdKH/44JOGM + S536RkWApUXR5b9LIlLyznjOFhf1FQuaoEvzFuY0L6bmD81QOh3r1qzMvB6Ic8Xp + 891gjsL1mqvGLKmHInhcbsplq3XmVoXdDeHjbeUz+QEOLs6mNtLk7eR3Xs7jJQuO + kYCmLY2SfVpP43tqlYwxW8IMXM8rP/XyJAut3+UFPRZznYBDSSYNv8KusxTCDgFO + i2elJiyyrljkoW/MNHBCEVrKAI9zOLkStPVnDQJjogDsWl3zpRq24byllWz/Ye67 + OdCXyLw+/6Xpm4v97Jx64crC+qreBa53D8nMnRaKV9eE9yV7p5hKfoTyyO05DYCM + 1MoQtDbIz9y/Jm09QfQuR04zJVNur7wi5dJKR7Cd3WqBPNX4u0x03UFap8dB5OdI + JVYbvFXZdvDBvqPq7XPThnqXGlrdkQjIMke2cCuC7RirmibFnm3ExLkeAaiCXNEY + tB5LF/01tGSAei4nHrSYfcnz2GvSVqMl9RmqaIEICoHEIOBJwNMs2iLhGYM1qF7I + tUobKjHPpJjmIqIQTMBlQOKUMSKWfSzXcrPEdGBk+pEeTJbZHVh5SALu1ENCUUam + D8l5FDbXesU9A2yiozUTznvcsmLbrlk78AWUtIxQCRCu+Ua9JaNUaCW0s2ooBAlU + bXYSHWt4CVccPDA1FEkqN8+IP2kxq1IZ5bidVLaY0jOtLzy8AMVjUaO/orRUk8zf + ThFN85TG6Y67oXIsELfvFFovo5aYjx8X95xm5jb3hFInwNh0GNdv0bmHS6pb0Vjn + 8WwDJ0emSocaOHMV0fKKFqHHqZ/hJfq3NRx0RbJGG6rqYAy36EkDzVL2uS+t7Zo/ + g1SQ6mByZfX6ylJGNhLgeLkoiupRam8d7CvW1yTmDlZfn7dV++Nfq/s7j3vC1Kr6 + uO+7Mbw97Sb4acxXX1acHb31qFudvec5sMYK2bl76txcE8oYT2AgXXgPKhkMEAPW + peUuiE7ou0Z0JKVdhdK5qItSa0Hz83I4GRCg21//UTmhGcWgTBe9w9OV2wtQTKeb + Dy9RK9b3WksLOU1l45/c6dxKlwcymCB43adefHcLexCIl/kIX9lrYRJkWpYJg8AQ + V5msc3TAQZreNvFat+igBRrpbBQOA/oaj41yqjsO04xsqrEcFIh7KyLGbproJy2+ + WB4D1tXOJCyMFRLCYa4wqPCdtf7wCMoIRCXRZzYjj9vBmi/6D7lDWSJvk5bqwGY8 + sfS3oYw/yIW8QtUVzyDTchuVp0er7W2AbE5Hwxx8oa9r1hvX7x2aXPlA198DLKbu + FDhd6STmiEOggZNad/dkVWz/pIDppi0bhUZhSxqTxV4+pl5y7wQ3bSOBtZre4lSB + ZzZOMnyYe5MvqndRiQIcBBABCAAGBQJUAiR8AAoJEMXOXcLFQs1ZZtoQAJ9m5wV/ + zVw/LOLoT1Foe23MPl6kGdMcCZLvyRyEGnqK58X59GjjT56JEBwLo8lI5acqhBrN + N55/qgcn1Yp5R/KYfz3fYfuHVLexxe3bKWx+Q0LNdQZIPFx/Ly7krRefIE6K1def + SqbyU62sjMXheVDeh5kdTAjgXWZvesjg+ZyXgZnaTf+8x4Fc0llFyqZsLEnxE1qP + U4KLlxUH55j8uUv1dn3wGFuvaURuqwLAIDnIZfsiE05rx8iNZfbxBnQmt2Nrs1x3 + 78aEtQX/kb4HfPreY1BBM3pZiqszOzGB552kP4LoQSm7w8NUfsxEwSDCPeKR4Yk7 + 4eSBfdQIQBPmt9rggNXqw5Si4RRGT6WpKwGFq0QLIC6C1vkiQQqqq13d3w38mIf9 + tb+GDpKGBmkiVD0JBmXDMvCrBfS44HZUZIlhvnB2ME8mQHLhQdCz+saYAixzCwuA + oVpcN3AP0Tl4MBE+xfrM5OlWhWFjjPbjVb29aJdBqsDBNFc2LyissNwn2/RjW/Kg + Scd/zQ2QN57fPQhfbFcbUKbpI49D8iWxk14rYXfV3lfTgkPYGxo/3UQMmRvZ9wdw + ffsCmIuyeAXPkNZbBMADDhD5zU47wfvgEcvK5cfuuNIrY66euUE5hw/wg1VHb/+8 + 2a65h59CeW4zAYbU/0t47ghTDi/ybqTVbcsp + =kPlg + -END PGP PUBLIC KEY BLOCK- + diff -Nru debian-archive-keyring-2012.4/active-keys/index debian-archive-keyring-2014.1~deb7u1
Bug#752450: ftp.debian.org: please consider to strongly tighten the validity period of Release files
On Sun, Sep 14, 2014 at 09:52:00PM +0200, Joerg Jaspert wrote: Also, going down to such small intervals means we MUST resign, even if there is no update at all in the archive (so an extra cronjob, just to be sure). That's no problem in the main archive, there is always enough going on, but security can go way longer without an update (which is why such a (weekly) cronjob exists on security). Unless ftp-master is down because of breakage and all Debian systems will start showing warnings because the resign did not take place. Resilience through not serving the world directly has some value. I guess these days we have a mirror that's fairly up to date to potentially start serving from, once the key is restored (I assume it is not synced). Not sure if that's true for security-master. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
On Fri, Sep 05, 2014 at 09:55:24AM +0200, Cyril Brulebois wrote: Steven Chamberlain ste...@pyro.eu.org (2014-08-31): On 31/08/14 07:00, Philipp Kern wrote: Is perhaps the same true for stop_rdnssd() on the next line? So Steven committed a patch in to git, getting rid of the dhcp part; Philipp, should I upload that and we'll figure out the rdnssd part another time? ACK. I wanted to look at it today, but meh. rdnssd isn't as critical as it won't take your interface down if you kill it. You just won't get updated DNS information. Kind regards and thanks Philipp Kern signature.asc Description: Digital signature
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
On Fri, Aug 29, 2014 at 11:25:28PM +0200, Cyril Brulebois wrote: I'd be slightly happier if Philipp would comment on this since he seems to be the one having committed this change. See: | commit 8802ca520d9e91542d92bbfa5b2fc412a31cf2e2 | Author: Matt Palmer mpal...@hezmatt.org | Date: Sun Jan 30 22:29:42 2011 +1100 | | IPv6 support for using rDNS to preseed hostnames | | A lot of refactoring to make the code cleaner and simpler, but the | IPv6-specific changes were actually relatively small. | | Rebased-and-modified-by: Philipp Kern pk...@debian.org http://anonscm.debian.org/cgit/d-i/netcfg.git/commit/?id=8802ca520d9e91542d92bbfa5b2fc412a31cf2e2 I did some archeology and I'll spare you the details. That kill_dhcp_client is totally wrong where it is now, so LGTM. Thanks. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#754856: buildd.debian.org: please remove s390* from p-a-s for ldc
On Wed, Aug 27, 2014 at 09:44:14AM +0300, Konstantinos Margaritis wrote: On Sat, 26 Jul 2014 17:20:08 +0200 Philipp Kern pk...@debian.org wrote: Sure, but first you need to upload a build that's arch-restricted. Then we try to drop the package from P-a-s anyway so that the architecture field is authoritative. upload of 0.14.0-1 fixed that, I am in the process of working on the ports individually using the porterboxes, don't know when I'm going to be done, but arches will be enabled on a per-case basis. You'll also need to request binary removal from unstable: out of date on armel: ldc (from 1:0.13.0-1) out of date on kfreebsd-amd64: ldc, libllvm-bindings-d (from 0.9.1+hg1634-1) out of date on kfreebsd-i386: ldc, libllvm-bindings-d (from 0.9.1+hg1634-1) out of date on powerpc: ldc, libllvm-bindings-d (from 0.9.1+hg1634-1) Kind regards Philipp Kern` signature.asc Description: Digital signature
Bug#759794: insighttoolkit4: FTBFS on amd64 with ENOSPC
On Sat, Aug 30, 2014 at 03:34:32PM +0200, Gilles Filippini wrote: insighttoolkit4 repeatedly FTBFS on amd64 [1] because of ENOSPC. A manual build on porterbox barriere.debian.org reported a need of ~44GB while it failed on buildd barber at approx 37GB of disk space. [1] https://buildd.debian.org/status/logs.php?pkg=insighttoolkit4arch=amd64 I really don't know how the build space could be optimized. The only solutions I can think of right now are: * force the build on a buildd with at least 44GB of free space * do a source + amd64 binary upload instead of source only upload. Note: this is blocking the ongoing hdf5 transition. I wonder if we should standardize on 50 GB everywhere. But then at some point there needs to be a cut-off. And if the packaging could be optimized to need less (i.e. avoid unnecessary disk use), that'd be splendid. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#759794: insighttoolkit4: FTBFS on amd64 with ENOSPC
On Sat, Aug 30, 2014 at 10:32:50PM +0200, Kurt Roeckx wrote: On Sat, Aug 30, 2014 at 08:10:41PM +0200, Philipp Kern wrote: On Sat, Aug 30, 2014 at 03:34:32PM +0200, Gilles Filippini wrote: insighttoolkit4 repeatedly FTBFS on amd64 [1] because of ENOSPC. A manual build on porterbox barriere.debian.org reported a need of ~44GB while it failed on buildd barber at approx 37GB of disk space. [1] https://buildd.debian.org/status/logs.php?pkg=insighttoolkit4arch=amd64 I really don't know how the build space could be optimized. The only solutions I can think of right now are: * force the build on a buildd with at least 44GB of free space * do a source + amd64 binary upload instead of source only upload. Note: this is blocking the ongoing hdf5 transition. I wonder if we should standardize on 50 GB everywhere. But then at some point there needs to be a cut-off. And if the packaging could be optimized to need less (i.e. avoid unnecessary disk use), that'd be splendid. I actually don't have an amd64 buildd that has both enough RAM and disk space. Brahms is the only one with enough disk space, but it only has 2 GB of RAM and gcc gets OOM killed there. I'd argue that 2 GB of RAM for a builder is a tad silly these times. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#734539: blocking the ppc64el architecture bootstrap
On Tue, Aug 26, 2014 at 11:10:31PM +0200, Aurelien Jarno wrote: On Mon, Aug 25, 2014 at 06:36:33AM +0200, Philipp Kern wrote: On Mon, Aug 25, 2014 at 05:27:30AM +0200, Aurelien Jarno wrote: The ppc64el architecture has been added to the Debian archive. Your package net6 fails to build as reported in bug #734539 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. This package should go away and I'm currently preparing the packages that make this possible. I don't mind a NMU if it is really blocking something. net6 is blocking sobby and obby, but if you are going to upload a new version of themnot using net6, I'll just wait. All of them are supposed to go away. I'll think about them updating once more because I can't anticipate NEW delay, but I don't actually want them in testing. If you have a list override, drop them from it. ;-) (I can't drop them from testing yet because of bad interactions with gobby-0.5 about what owns the gobby package.) Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#758115: Disabled wait state X'32EE' on IPL of zIPL
On Sun, Aug 24, 2014 at 08:43:30PM +0200, Bastian Blank wrote: On Sun, Aug 24, 2014 at 08:34:45PM +0200, Bastian Blank wrote: On Sun, Aug 24, 2014 at 08:05:45PM +0200, Bastian Blank wrote: On Fri, Aug 22, 2014 at 07:21:31PM -0400, Stephen Powell wrote: 32ea: a7 f4 00 01 j 32ec sclp_wait_for_int+0x84 32ee: 07 07 nopr%r7 gcc 4.9 decides that this must never happen and adds a trap in this location, so this a is deliberate way to stop the process. I found the culprit: The tree-isolate-paths pass in gcc 4.9. If I disable this pass I get: And -fno-delete-null-pointer-checks seems to be the correct option. Thanks! I uploaded that to replace the gcc-4.8 build dependency. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#758115: Disabled wait state X'32EE' on IPL of zIPL
On Fri, Aug 22, 2014 at 07:21:31PM -0400, Stephen Powell wrote:
static inline int wait(void)
{
do {
load_wait_psw(0x010200018000ULL,
S390_lowcore.external_new_psw);
33d0: e3 20 d0 00 00 04 lg %r2,0(%r13)
33d6: a7 39 01 b0 lghi%r3,432
33da: c0 e5 ff ff fc f7 brasl %r14,2dc8 load_wait_psw
if (S390_lowcore.ext_int_code == 0x1004)
33e0: e3 10 00 86 00 91 llgh%r1,134
33e6: a7 1e 10 04 chi %r1,4100
33ea: a7 74 00 06 jne 33f6
sclp_wait_for_int+0x9a
33ee: a7 28 00 02 lhi %r2,2
33f2: a7 f4 00 08 j 3402
sclp_wait_for_int+0xa6
return ETIMEOUT;
} while (S390_lowcore.ext_int_code != 0x2401);
33f6: a7 1e 24 01 chi %r1,9217
33fa: a7 74 ff eb jne 33d0
sclp_wait_for_int+0x74
33fe: a7 28 00 00 lhi %r2,0
Would be interesting how the disassembly looks on your system.
Indeed. Here is what I got:
-
static inline int wait(void)
{
do {
load_wait_psw(0x010200018000ULL,
S390_lowcore.external_new_psw);
32d6: a7 39 01 b0 lghi%r3,432
32da: e3 20 d0 00 00 04 lg %r2,0(%r13)
32e0: c0 e5 ff ff fb b8 brasl %r14,2a50 load_wait_psw
if (S390_lowcore.ext_int_code == 0x1004)
32e6: 48 10 00 86 lh %r1,134
32ea: a7 f4 00 01 j 32ec sclp_wait_for_int+0x84
32ee: 07 07 nopr%r7
-
With gcc-4.8:
static inline int wait(void)
{
do {
load_wait_psw(0x010200018000ULL,
S390_lowcore.external_new_psw);
331e: e3 20 d0 00 00 04 lg %r2,0(%r13)
3324: a7 39 01 b0 lghi%r3,432
3328: c0 e5 ff ff fb ac brasl %r14,2a80 load_wait_psw
if (S390_lowcore.ext_int_code == 0x1004)
332e: e3 10 00 86 00 91 llgh%r1,134
3334: a7 1e 10 04 chi %r1,4100
3338: a7 84 00 0a je 334c sclp_wait_for_int+0x9c
return ETIMEOUT;
} while (S390_lowcore.ext_int_code != 0x2401);
333c: a7 1e 24 01 chi %r1,9217
3340: a7 74 ff ef jne 331e sclp_wait_for_int+0x6e
return 0;
3344: a7 28 00 00 lhi %r2,0
3348: a7 f4 00 04 j 3350 sclp_wait_for_int+0xa0
That does look much better for 3338, 3340, not really for 3348 (to 3350). It
does fix the issue at hand, but it's a band-aid at most. I installed the
package on wheezy (compiled on sid) and it booted...
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690282: Status of bug #690282
reassign 690282 ruby-pgplot severity 690282 serious retitle 690282 ruby-pgplot fails to build within Debian (build-depends on non-free) thanks On Wed, Aug 20, 2014 at 09:46:44AM +0200, Ole Streicher wrote: because I just also was trapped by this bug, I'd like to know if there was any progress since it was reported? Are there any plans to fix it? Anything one can help to get this solved? Oh sure. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#734539: blocking the ppc64el architecture bootstrap
On Mon, Aug 25, 2014 at 05:27:30AM +0200, Aurelien Jarno wrote: The ppc64el architecture has been added to the Debian archive. Your package net6 fails to build as reported in bug #734539 and the build log is available on [1]. It would be very nice if you can upload a fixed version of this package. Don't hesitate to ask questions if you need help to fix this bug. If you lack time for that, I can also proceed with an NMU. This package should go away and I'm currently preparing the packages that make this possible. I don't mind a NMU if it is really blocking something. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#758488: python3: float conversion broken on s390x
severity 758488 important thanks Hi, thank you for your followup. On 2014-08-18 01:44, Matthias Klose wrote: int to float casts are working with python2, but are completely broken with python3: float(1) 1073741824.0 float(-1) -1073741824.0 - does this work with python3-dbg? It does work with python3-dbg. Which indeed points to some (new?) CPU instruction breaking things. - if yes, please find out which optimization, or which wrong code causes this, and send a patch or workaround. the python3.4 testsuite looks good, except for some failing test_dbm tests and a failing test_signal test. Hrm. I should have looked for that, that's a good pointer. It turns out that it works on zelenka in a sid chroot as well, which indicates breakage under Hercules. Under this assumption it likely does not break the world, hence I'm downgrading this bug. I'll try to run the python3.4 testsuite. I won't have time to handle this until late September. Understood. Thanks. Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758488: python3: float conversion broken on s390x
Package: python3-minimal Version: 3.4.1-1 Severity: serious X-Debbugs-Cc: debian-s...@lists.debian.org The datetime module fails its initialization assertions on s390x with python3 upon import: import datetime Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python3.4/datetime.py, line 619, in module microseconds=99) File /usr/lib/python3.4/datetime.py, line 395, in __new__ assert abs(microseconds) 3.1e6 AssertionError (Disregard slight shifts in the line numbers.) The actual problem is this: float(99) 1073740750258176.0 Sadly python3-minimal fails to configure because of this, which in turn lets other packages being upgraded fail to fully install. int to float casts are working with python2, but are completely broken with python3: float(1) 1073741824.0 float(-1) -1073741824.0 Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758115: Disabled wait state X'32EE' on IPL of zIPL
On Fri, Aug 15, 2014 at 10:46:54AM +0200, Michael Holzheu wrote: On Thu, 14 Aug 2014 21:45:53 -0400 (EDT) Stephen Powell zlinux...@wowway.com wrote: On Thu, 14 Aug 2014 10:32:42 -0400 (EDT), Philipp Kern wrote: Hrm. Odd. It shouldn't be because the brokeness relates to the C library, not to the C compiler itself and zipl does not use the C library. Again, we must distinguish between zipl, the Linux command which runs at a Linux shell prompt, and zIPL, the boot loader proper, a customized version of which is written out by zipl when zipl gets run. zipl, the command which runs at a Linux shell prompt, most certainly does use the C library. It is written in C, it is compiled by the C compiler, and, at execution time, it uses the C run-time library, just like any other C program. zIPL, which is written out by zipl, does not use the C library. Or does it? Well, not the regular C library, no. But it does use a minimalist run-time library. In the source package, look at zipl/boot/libc.c. Yes, even zIPL, the boot loader proper, does use a C library of sorts. Just for confirmation: Stephen is right. The zipl tool is a normal C program that uses the glibc. The zipl boot loader code under the boot source directory does not use the glibc or any other external library. Before s390-tools-1.24.0 it was written 100% in assembler. With s390-tools-1.24.0 we have rewritten the code in C and have added our own minimal libc. I should've written (e)glibc instead of C library. It's what I meant. I tried to simplify things and failed. The question of is this Hercules was also more related to where is the value coming from, as CP might do things differently. So Hercules should log the whole PSW. I can also only see it logging that and the CPU address/ID, not a wait state code. Do you happen to have the PSW handy? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#757988: Bug#757711: Bug#757988: kfreebsd: troubles with dhcp (configuration going away)
On Wed, Aug 13, 2014 at 07:05:47PM +0100, Steven Chamberlain wrote:
On 13/08/14 18:05, Cyril Brulebois wrote:
What I'd like to get figured out is what changed between images that
weren't hitting this problem, and the newly published ones.
What changed is dhclient from isc-dhcp-client-udeb gained a signal
handler that responds to SIGKILL by releasing the DHCP lease and
deconfiguring the interfaces. I've just tested that the version in
wheezy d-i didn't trap the signal; Linux udhcpc doesn't either.
This is a 'feature' introduced in ISC DHCP 4.3.0, which first reached
testing on 2014-07-16; I've tested that d-i Alpha 1 wasn't affected by
this bug (dhclient is killed but the interface stays configured) :
@@ -681,6 +692,10 @@ main(int argc, char **argv) {
dmalloc_outstanding = 0;
#endif
+/* install signal handlers */
+ signal(SIGINT, dhcp_signal_handler); /* control-c */
+ signal(SIGTERM, dhcp_signal_handler); /* kill */
+
(from
http://anonscm.debian.org/gitweb/?p=pkg-dhcp/isc-dhcp.git;a=commitdiff;h=b2a56ecb808768dbc5bd4be60fcf9c9f93d8e802#patch16
)
Either way, netcfg killing the DHCP client seems wrong to me, because
I'd expect the kind of issues Philipp Kern described; if you're going
to use DHCP, you ought to renew your lease and not let it expire?
Ubuntu uses -1, which means they don't have anything left to kill at that
point.
I agree that this killing does not make sense. Especially when the network
configuration is complete you want daemons like dhclient and rdnssd to stick
around in case dynamic configuration changes (rdnssd) and to keep up the
state / communicate own presence on the network (dhclient).
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
Bug#758115: Disabled wait state X'32EE' on IPL of zIPL
On Thu, Aug 14, 2014 at 06:49:20AM -0400, Stephen Powell wrote: Justification: The entire system is unbootable After installing s390-tools version 1.24.1-1 and re-running zipl, a reboot of the system causes a disabled wait PSW to be loaded during boot, with a wait state code of X'32EE', prior to the zipl menu being written out. The system is unbootable. This may be related to the general brokenness of C on s390x in jessie/sid. Hrm. Odd. It shouldn't be because the brokeness relates to the C library, not to the C compiler itself and zipl does not use the C library. That being said, I had to recompile s390-tools on sid, and I do not run sid due to the C breakage. It worked before the recompilation, hence there might be a change in sid vs. wheezy that caused this. You are talking about Hercules, right? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#757711: Bug#757988: kfreebsd: troubles with dhcp (configuration going away)
Hi, On Thu, Aug 14, 2014 at 07:32:22PM +0200, Cyril Brulebois wrote: Now, I think there are several questions to answer: 1. What were the reasons for having arch-dependent dhcp clients? 2. Are those reasons still valid? = Maybe think about moving to a single client if possible, at least for consistency's sake (and probably maintenance costs). The answer to the first question is likely answered by looking at some git history, and possible links to bug reports. As for the second, we'll likely need porter input. as I guessed from memory, here's one: commit 75b4faa11bda438e34b5140934f6b812d1a69040 Author: Samuel Thibault sthiba...@debian.org Date: Thu Mar 3 18:10:31 2011 +0100 Make netcfg depend on isc-dhcp-client-udeb on hurd-any too for the same reason as kfreebsd: no support for udhcp in busybox. If this is still true I don't know. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#757711: netcfg: promptly kills dhclient, deconfigures interface
On Tue, Aug 12, 2014 at 02:45:25AM +0200, Cyril Brulebois wrote: That I don't know. Maybe try and compare with netcfg + dhcp client du jour on Linux, and see whether netcfg's behaviour is different in both cases, or the dhcp client's one, or the kernel's one. In the end there's a lot of sadness around what we do, what Ubuntu does, and what the end result is. Ubuntu uses isc-dhcp-client, so the same as on kfreebsd-* and might as well have some additional patches to netcfg because of this. But at work we do use Ubuntu and found that dhclient is called with -1. If the lease expires during installation and your switch does DHCP snooping, you lose network during installation because the DHCP client does not continue to renew it. This is anecdotal experience but divergence between Linux and kfreebsd wrt DHCP might mean that certain problems need to be solved twice or certain failure modes only happen in one or another, with userspace being the reason, not even the kernel difference. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#756907: cinnamon-screensaver: no longer buildable on non-linux
On Sun, Aug 03, 2014 at 01:50:24PM +0200, Cyril Brulebois wrote:
Source: cinnamon-screensaver
Version: 2.2.4-4
Severity: serious
Justification: FTBFS
Hi,
your package can no longer be built on non-linux architectures:
| cinnamon-screensaver build-depends on missing:
| - libsystemd-login-dev
as can be seen here:
https://buildd.debian.org/status/package.php?p=cinnamon-screensaversuite=sid
The outdated binaries on kfreebsd-* are therefore preventing your
package from migrating. Hence this pseudo-FTBFS serious bug report.
AFAICS the following patch should fix this:
diff -Nru cinnamon-screensaver-2.2.4/debian/control
cinnamon-screensaver-2.2.4/debian/control
--- cinnamon-screensaver-2.2.4/debian/control 2014-07-26 15:52:14.0
+
+++ cinnamon-screensaver-2.2.4/debian/control 2014-08-10 10:22:49.0
+
@@ -16,7 +16,7 @@
libgnomekbd-dev (= 2.91.91),
libgtk-3-dev (= 3.0.0),
libpam0g-dev,
- libsystemd-login-dev,
+ libsystemd-login-dev [linux-any],
libx11-dev,
libxext-dev,
libxklavier-dev,
diff -Nru cinnamon-screensaver-2.2.4/debian/rules
cinnamon-screensaver-2.2.4/debian/rules
--- cinnamon-screensaver-2.2.4/debian/rules 2014-07-26 15:52:14.0
+
+++ cinnamon-screensaver-2.2.4/debian/rules 2014-08-10 10:17:44.0
+
@@ -2,6 +2,8 @@
export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
+LOGIN_INFRA_YES := $(shell dpkg-architecture -qDEB_HOST_ARCH -ilinux-any
echo systemd || echo console-kit)
+LOGIN_INFRA_NO := $(shell dpkg-architecture -qDEB_HOST_ARCH -ilinux-any
echo console-kit || echo systemd)
%:
dh $@ --parallel --with=autoreconf,gnome
@@ -12,8 +14,8 @@
override_dh_auto_configure:
dh_auto_configure -- \
--enable-locking \
- --with-console-kit=no \
- --enable-systemd \
+ --with-$(LOGIN_INFRA_YES)=yes \
+ --with-$(LOGIN_INFRA_NO)=no \
--libexecdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/cinnamon-screensaver
override_dh_install:
Note that --enable-systemd was wrong, it's actually --with-systemd. But it
defaults to auto, so that's good. consolekit does not need additional build
dependencies as the application is just talking dbus to the service.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
Bug#757533: debian-archive-keyring: source package signed by removed key
severity 757533 normal thanks On Fri, Aug 08, 2014 at 07:41:11PM -0400, Michael Gilbert wrote: The archive keyring package is currently signed by Philip Kern's old removed key. Since this package contains the keys to archive, it really needs a valid signature. The key has neither been revoked nor compromised. It just cannot be used for new uploads nor to authenticate to Debian's systems. So I completely disagree with the inflated severity you laid out here (and potential MBFs). We will update the package with the new Jessie key soon, though, which should fix this issue as the package will need to be backported. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#719028: pdf2svg: produces imprecise paths
tag -1 + moreinfo thanks Hi, On Wed, Aug 07, 2013 at 11:57:56PM +0200, Christoph Haag wrote: to convert a pdf (exported from inkscape) did work fine and as expected with pdf2svg 0.2.1-2+b1 but version pdf2svg 0.2.1-2+b3 produces imprecise paths. compare sample files: http://www.forkable.eu/memo/SANDBOX/130807_reportbug-pdfsvg.tar.gz so that file is no longer there and was not attached to the bug. That makes going back to this bug quite hard. Have updates in the meantime resolved this issue or is it still present? Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#756172: ITP: ssh-cron -- cron-like job scheduler than handles ssh key passphrases
On Sun, Jul 27, 2014 at 08:40:03AM -0700, tony mancill wrote: It seems like with Ganneff's trigger mechanism, one attack vector is to steal a backup of the passphraseless key and spoof the source IP - now you can run the trigger at will. Having a passphrase on the key could at least slow the attacker down. I could imagine using ssh-cron together with command= for a higher level of security. Uhm, spoof the source IP? This is not UDP, you'd also need to get traffic back redirected to you. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#682342: (forw) Bug#682342: a fix for dhcp search path issues'
On Wed, May 22, 2013 at 07:03:37AM +0200, Christian PERRIER wrote:
Phil, you've been one of the most active ppl on netcfg. Care to comment?
- Forwarded message from Sean Noonan sean.noo...@twosigma.com -
Date: Tue, 21 May 2013 18:28:09 +
From: Sean Noonan sean.noo...@twosigma.com
To: '682...@bugs.debian.org' 682...@bugs.debian.org
Subject: Bug#682342: a fix for dhcp search path issues
Reply-To: Sean Noonan sean.noo...@twosigma.com, 682...@bugs.debian.org
X-Mailing-List: debian-b...@lists.debian.org archive/latest/173316
X-CRM114-Status: Good ( pR: 30.0127 )
We recently ran into this problem. The expedient way to fix it is to replace
the netcfg binary in the initrd with one compiled using the following patch.
--- dhcp.c 2013-01-13 08:23:24.0 -0500
+++ ../dhcp.c 2013-05-21 14:25:55.613957486 -0400
@@ -591,7 +591,7 @@
preseed_hostname_from_fqdn(client, buf);
}
-if (netcfg_get_hostname (client, netcfg/get_hostname,
hostname, 1)) {
+if (netcfg_get_hostname (client, netcfg/get_hostname,
hostname, !have_domain)) {
/*
* Going back to POLL wouldn't make much sense.
* However, it does make sense to go to the retry
- End forwarded message -
I think this patch is incomplete and still needs to strip the domain
off the hostname to preserve behavior if an FQDN is passed in with the
hostname. That way the domain name passed by DHCP will override the
domain part of the hostname.
New possible (untested) patch attached.
Kind regards
Philipp Kern
diff --git a/dhcp.c b/dhcp.c
index aa37bd0..d694f67 100644
--- a/dhcp.c
+++ b/dhcp.c
@@ -591,7 +591,7 @@ int netcfg_activate_dhcp (struct debconfclient *client, struct netcfg_interface
preseed_hostname_from_fqdn(client, buf);
}
-if (netcfg_get_hostname (client, netcfg/get_hostname, hostname, 1)) {
+if (netcfg_get_hostname (client, netcfg/get_hostname, hostname, !have_domain)) {
/*
* Going back to POLL wouldn't make much sense.
* However, it does make sense to go to the retry
diff --git a/netcfg-common.c b/netcfg-common.c
index 4445d12..9abf32e 100644
--- a/netcfg-common.c
+++ b/netcfg-common.c
@@ -1043,14 +1043,24 @@ int netcfg_get_hostname(struct debconfclient *client, char *template, char *host
continue;
}
-if (accept_domain (s = strchr(hostname, '.'))) {
-di_info(Detected we have an FQDN; splitting and setting domain);
-if (s[1] == '\0') { /* somehostname. - . should be ignored */
+if (s = strchr(hostname, '.')) {
+di_info(Detected an FQDN in hostname);
+if (s[1] == '\0') {
+/* somehostname. - . should be ignored */
*s = '\0';
-} else { /* assume we have a valid domain name given */
-strncpy(domain, s + 1, MAXHOSTNAMELEN);
-debconf_set(client, netcfg/get_domain, domain);
-have_domain = 1;
+di_info(Stripped trailing dot from hostname);
+} else {
+/* assume that the domain is valid and copy it if
+ * accept_domain is set; just use the hostname if
+ * it is unset
+ */
+if (accept_domain) {
+strncpy(domain, s + 1, MAXHOSTNAMELEN);
+ di_info(Setting domain to %s, domain);
+debconf_set(client, netcfg/get_domain, domain);
+have_domain = 1;
+}
+/* strip the domain from the hostname */
*s = '\0';
}
}
signature.asc
Description: Digital signature
Bug#754856: buildd.debian.org: please remove s390* from p-a-s for ldc
tag 754856 + moreinfo thanks On Tue, Jul 15, 2014 at 11:26:07AM +0300, Konstantinos Margaritis wrote: Please remove s390/s390x entries from p-a-s for the ldc package. Since I took over the package, I'd like to check what's it's current status with s390* is, if it doesn't I can take it with upstream and if it's easily fixable I can fix it, if not I'll just remove it from the arch list. But as it is in p-a-s right now, it's not much help. Please try to build it on the porterbox first. It built an unusable binary before, which is a bad failure case (#580876). Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#754856: buildd.debian.org: please remove s390* from p-a-s for ldc
On Sat, Jul 26, 2014 at 05:30:57PM +0300, Konstantinos Margaritis wrote: Please try to build it on the porterbox first. It built an unusable binary before, which is a bad failure case (#580876). I've already done this, in fact I'm doing this for all the architectures where it fails(kfreebsd-*, powerpc, mips*, s390x*). So far it fails on all of those, but I'm talking to upstream to eventually fix the failures. In the meantime I'm going to remove the failing arches from the control Architecture field and downgrade the bugs -even when they compiled they were never actually working and supported. Still, I would like to have control of the architecture field and not p-a-s. That way I could easily enable it when it starts to actually work. Sure, but first you need to upload a build that's arch-restricted. Then we try to drop the package from P-a-s anyway so that the architecture field is authoritative. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#715519: debsums: missing file /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg (from debian-archive-keyring package)
tag 715519 + moreinfo thanks Hi, On Wed, Jul 10, 2013 at 08:15:11AM +0800, jida...@jidanni.org wrote: # debsums -ce debsums: missing file /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg (from debian-archive-keyring package) debsums: missing file /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg (from debian-archive-keyring package) debsums: missing file /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg (from debian-archive-keyring package) debsums: missing file /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg (from debian-archive-keyring package) That's all I know. can you still reproduce this? I'd think that this is fixed by recent changes in either dpkg or debsums. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#739411: udpkg: Support for data.tar, control.tar and control.tar.xz
tag -1 + pending thanks Hi, On Tue, Feb 18, 2014 at 01:01:48PM +0100, Guillem Jover wrote: Here's a patch series adding data.tar, control.tar and control.tar.xz support, the uncompressed member support just out of completeness. To create a deb package with a different control.tar compression you can use «dpkg-deb --uniform-compression pkg/» for example. Note I've only tested «udpkg -c» and «udpkg -f», the changes in unpacking are pretty obvious, but testing them would be nice. I've also used cat for the uncompressed members as I didn't think further optimization there was worth it(?). I've also tried to use the prevailing coding-style, which in some cases conflicted with the immediate surrounding code. given KiBi's analysis there's no immediate rush to go all-xz for jessie, but we should still land the patches to udpkg, of course. As for the cat: You went from ar -p %s %s%s|%s -c|tar -x to ar -p %s %s%s|%s|tar -x. I guess you could have moved the pipe into the output of decompression_tool as well and do ar -p %s %s%s%s|tar -x with |gunzip -c, |unxz -c, and . But then I think your approach is clear to readers, so that's good. ;-) I pushed your patches to the repository. Very much thanks for them. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#755409: Package should not be part of jessie
Source: net6,obby,gobby-0.4 Severity: serious I'd like to drop gobby 0.4 (not 0.4.9x aka 0.5) from Jessie. This means that net6, obby, and gobby-0.4 should be removed from testing. Further development focus will be on the 0.5 series. signature.asc Description: Digital signature
Bug#755411: build transitional package gobby
Package: gobby-0.5 Version: 0.4.94-6 Severity: normal Take over the gobby transitional package from gobby 0.4 and depend on 0.5 only. Put it into oldlibs as a proper transitional package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755409: Package should not be part of jessie
# #755411 - changing the transitional package - needs to be done # first, before removing the old packages. block 755409 by 755411 severity 755409 important -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754906: prints spurious warnings on purge
Package: gummiboot Version: 44-1 Severity: minor /etc/kernel/postrm.d/zz-update-gummiboot is called twice and when called the second time the kernel is already removed. And because the rm is not guarded with an existence check, it errors on the console: pkern@honeybee:~$ sudo dpkg --purge linux-image-3.14-1-rt-amd64 (Reading database ... 118363 files and directories currently installed.) Removing linux-image-3.14-1-rt-amd64 (3.14.9-1) ... Ok, proceeding with removing running kernel image. /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-3.14-1-rt-amd64 /etc/kernel/postrm.d/zz-update-grub: Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.14-1-amd64 Found initrd image: /boot/initrd.img-3.14-1-amd64 Found linux image: /boot/vmlinuz-3.13-1-amd64 Found initrd image: /boot/initrd.img-3.13-1-amd64 Adding boot menu entry for EFI firmware configuration done /etc/kernel/postrm.d/zz-update-gummiboot: Remove 3.14-1-rt-amd64 from ESP The link /vmlinuz is a damaged link Removing symbolic link vmlinuz You may need to re-run your boot loader The link /initrd.img is a damaged link Removing symbolic link initrd.img You may need to re-run your boot loader Purging configuration files for linux-image-3.14-1-rt-amd64 (3.14.9-1) ... /etc/kernel/postrm.d/zz-update-gummiboot: Remove 3.14-1-rt-amd64 from ESP rm: cannot remove ‘/boot/efi/ed6099b79356a7a21b779a95538f82cc/3.14-1-rt-amd64/’: No such file or directory rm: cannot remove ‘/boot/efi/loader/entries/ed6099b79356a7a21b779a95538f82cc-3.14-1-rt-amd64.conf’: No such file or directory -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gummiboot depends on: ii libblkid1 2.20.1-5.8 ii libc6 2.19-5 Versions of packages gummiboot recommends: ii systemd 204-14 gummiboot suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754911: autoreconf should build-conflict with autoconf2.13
Package: gummiboot Version: 44-1 Severity: normal For me package building fails because dh_autoreconf does not take m4/ into account. But this is a strange failure case: pkern@simplex ~/src/gummiboot-44 (git)-[master] % autoreconf -f -i configure.ac:57: error: AM_COND_IF: no such condition ARCH_IA32 /usr/share/aclocal-1.14/cond-if.m4:23: AM_COND_IF is expanded from... configure.ac:57: the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: error: echo failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 Okay... But it works from autogen.sh! 1 pkern@simplex ~/src/gummiboot-44 (git)-[master] % grep autoreconf autogen.sh autoreconf --force --install --symlink Okay... pkern@simplex ~/src/gummiboot-44 (git)-[master] % autoreconf --force --install configure.ac:35: installing 'build-aux/compile' configure.ac:34: installing 'build-aux/config.guess' configure.ac:34: installing 'build-aux/config.sub' configure.ac:31: installing 'build-aux/install-sh' configure.ac:31: installing 'build-aux/missing' Makefile.am: installing 'build-aux/depcomp' What!? export ACLOCAL_PATH = m4 in debian/rules fixes the issue, but this is weird. Surely enough there's ACLOCAL_AMFLAGS in Makefile.am, too, which specifies the m4 subdir. That's because the autoreconf wrapper we ship handles --install differently from -i and shells out to autoreconf2.50 if it finds the former. pkern@simplex ~/src/gummiboot-44 (git)-[master] % dpkg -S /usr/bin/autoreconf diversion by autoconf2.13 from: /usr/bin/autoreconf diversion by autoconf2.13 to: /usr/bin/autoreconf2.50 autoconf, autoconf2.13: /usr/bin/autoreconf Argh. And autoreconf2.50 works as expected. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gummiboot depends on: ii libblkid1 2.20.1-5.8 ii libc6 2.19-7 Versions of packages gummiboot recommends: ii systemd 204-14 gummiboot suggests no packages. -- Configuration Files: /etc/default/gummiboot changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753682: gummiboot: FTBFS with GCC 4.9 due to undefined va_copy in EFI binary
On Fri, Jul 11, 2014 at 02:58:20PM +0200, Julian Andres Klode wrote: That's true. IMO Gnu EFI needs to be patched to not include efistdarg.h by default and hide the vaargs functions if the header is not included. That would fix all issues. Or change it to define the va functions in terms of GCC builtins. This should work as well IMO. I think it'd be easiest to just stub out va_copy as well (it's used in lib/print.c - as long as the stdlib.h include remains patched out): #define va_copy(d,s) ((d) = (s)) That resolves the dangling reference at gnu-efi compile-time and lets gummiboot compile. I did not test the end result, but we're talking about DbgPrint which gummiboot does not even use. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#754906: prints spurious warnings on purge
On 2014-07-15 21:46, Julian Andres Klode wrote: I'll try to fix this, but until we see a new upload of gnu-efi removing the undefined va_copy symbol from its static library, there won't be any new gummiboot upload. See Bug#753682 for more information and possible solutions on that issue. We need some more pressure there, gnu-efi is currently unusable and not fit for release. I updated that bug. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753937: New upstream version 1.1.1
Hi, On Sun, Jul 06, 2014 at 02:44:59PM +0200, Steinar H. Gunderson wrote: I've released Cubemap 1.1.1; it contains two small but still useful fixes. Please take a look when you have the time -- it should be a simple uupdate. sadly it does not compile cleanly for me due to missing includes: g++ -MMD -MP -D_FORTIFY_SOURCE=2 -Wall -O2 -g -pthread -o input.o -c input.cpp input.cpp: In function ‘bool parse_url(const string, std::string*, std::string*, std::string*, std::string*, std::string*)’: input.cpp:66:11: error: ‘stderr’ was not declared in this scope fprintf(stderr, ooo user='%s' host='%s'\n, user-c_str(), host-c_str()); ^ input.cpp:66:76: error: ‘fprintf’ was not declared in this scope fprintf(stderr, ooo user='%s' host='%s'\n, user-c_str(), host-c_str()); ^ Makefile:16: recipe for target 'input.o' failed That's due to 8a2129f4c808600d6151f724dcbd816188d3d1c6. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#751721: Figure out how to deal with ABI changes
Package: linux Severity: normal Hi there, apparently we only guarantee that with a new ABI version, old modules are still compatible. The reverse, new modules with an old kernel, seems as important to me, though. There are many ways a kernel can be updated on disk that are not necessarily triggered by user action. But the consequence of the current ABI policy is that you might find yourself unable to remove or insert modules because the kernel image has been auto-updated and the new modules can no longer be inserted. This causes silent breakage wrt auto-loading or noisy one like this: pkern@hub:~$ sudo modprobe loop [sudo] password for pkern: ERROR: could not insert 'loop': Unknown symbol in module, or unknown parameter (see dmesg) pkern@hub:~$ strings /boot/vmlinuz-3.2.0-4-amd64 |grep Debian 3.2.0-4-amd64 (debian-ker...@lists.debian.org) #1 SMP Debian 3.2.57-3 pkern@hub:~$ dmesg | grep loop [5575038.225037] loop: Unknown symbol bdgrab (err 0) To tell people to always reboot when their kernel image is updated, is kind of flawed. They might not be aware and suddenly the device they plugged in does not work. They might get a reboot notification, of course, but might also not realize that it can break their running system. Ubuntu claims with every update that there is an unavoidable ABI change. I guess that's why. It at least sidesteps this issue if you handle ABI changes that way. Of course it also makes d-i more brittle unless you keep old ABI versions around and do not decruft them. Kind regards and thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
