Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-16 Thread Svante Signell via evolution-list
On Sat, 2019-03-16 at 20:36 +0100, Svante Signell wrote: > > On Sat, Mar 16, 2019 at 8:32 PM Andre Klapper wrote: > > On Sat, 2019-03-16 at 20:26 +0100, Svante Signell wrote: > > > Do I need to have systemd as boot manager? > > > Do I need systemd (logind st

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-16 Thread Svante Signell via evolution-list
On Sat, Mar 16, 2019 at 8:32 PM Andre Klapper wrote: > On Sat, 2019-03-16 at 20:26 +0100, Svante Signell wrote: > > Do I need to have systemd as boot manager? > > Do I need systemd (logind stuff) for evolution to function? > > Do I need network-manager? I don't have nei

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-16 Thread Svante Signell via evolution-list
On Sat, Mar 16, 2019 at 7:06 PM Andre Klapper wrote: > On Sat, 2019-03-16 at 18:01 +0100, Svante Signell wrote: > > > > On Sat, Mar 16, 2019 at 11:22 AM Pete Biggs wrote: > > > > > > It is specifically not an Evolution error, it's something that is > >

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-16 Thread Svante Signell via evolution-list
On Sat, Mar 16, 2019 at 11:22 AM Pete Biggs wrote: > > > > [imapx:*] Failed to open a new connection, while having 0 opened, with > error: Error reading data from TLS socket: The specified session has been > invalidated for some reason.; will limit connections: no > > > > Have you done any

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-15 Thread Svante Signell via evolution-list
/Drafts' On Fri, Mar 15, 2019 at 9:22 PM Andre Klapper wrote: > On Fri, 2019-03-15 at 21:06 +0100, Svante Signell wrote: > > How do I debug evo? Do I have to build it from source? > > https://wiki.gnome.org/Apps/Evolution/Debugging > > andre > -- > Andre

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-15 Thread Svante Signell via evolution-list
I have now downgraded all depending packages to a known working evolution on another box. Still the same problems. How do I debug evo? Do I have to build it from source? On Fri, Mar 15, 2019 at 12:56 PM Svante Signell wrote: > Here is what I get when starting evo from the command l

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-15 Thread Svante Signell via evolution-list
reason. Which evo program prints mail_folder_cache_note_store_thread? On Fri, Mar 15, 2019 at 12:52 PM Patrick O'Callaghan wrote: > On Fri, 2019-03-15 at 01:16 +0100, Svante Signell via evolution-list > wrote: > > How to reply to a selected list?? With this ... web interface I'm not >

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-15 Thread Svante Signell via evolution-list
I've tried OAuth2 too, same error message. On Fri, Mar 15, 2019 at 11:30 AM Pete Biggs wrote: > > > > > > > BTW: I've chosen to authenticate with password but no request for it > > pops up, I wonder why? > > Probably because it never gets that far. > > Is there any particular reason why you

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-15 Thread Svante Signell via evolution-list
< evolution-list@gnome.org> wrote: > On Fri, 2019-03-15 at 01:16 +0100, Svante Signell via evolution-list > wrote: > > How to reply to a selected list?? With this ... web interface I'm > > not even able to see my own postings. > > And following a thread is awful :(

[Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-15 Thread Svante Signell
Hi, Suddenly evo refuses to read mail from my email account: Failed to open folder. The reported error was “Error reading data from TLS socket: The specified session has been invalidated for some reason.”. And: Failed to finish trust prompt for “a...@gmail.com” No PEM-encoded certificate found.

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-14 Thread Svante Signell via evolution-list
How to reply to a selected list?? With this ... web interface I'm not even able to see my own postings. And following a thread is awful :(. and how to choose top/bottom and which previous replies to include? Who sucks most, google? On Fri, Mar 15, 2019 at 1:04 AM Svante Signell wrote: > Ma

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-14 Thread Svante Signell via evolution-list
Maybe this is the time to abandon evolution: Too much entangled with gnome et al.. mutt? On Fri, Mar 15, 2019 at 12:45 AM Svante Signell wrote: > ping works fine :) > > > On Fri, Mar 15, 2019 at 12:43 AM Steve Edmonds > wrote: > >> Can you ping imap.gmail.com, if no

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-14 Thread Svante Signell via evolution-list
ping works fine :) On Fri, Mar 15, 2019 at 12:43 AM Steve Edmonds wrote: > Can you ping imap.gmail.com, if not you may have a network setup error. > Do you have a firewall or antivirus that could be blocking your connection. > > On 15/03/2019 12:01, Svante Signell via evolutio

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-14 Thread Svante Signell via evolution-list
With correct spelling. Please help! This mails is sent by the webmail version of gmail :( On Fri, Mar 15, 2019 at 12:00 AM Svante Signell wrote: > Pleas jelp! > > On Thu, Mar 14, 2019 at 8:44 PM Svante Signell > wrote: > >> And: >> Error while Checking for

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-14 Thread Svante Signell via evolution-list
Pleas jelp! On Thu, Mar 14, 2019 at 8:44 PM Svante Signell wrote: > And: > Error while Checking for new mail at “a...@gmail.com”. > Could not connect to imap.gmail.com: Network is unreachable > Do I need network-manager?? > ___ evoluti

Re: [Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-14 Thread Svante Signell via evolution-list
And: Error while Checking for new mail at “a...@gmail.com”. Could not connect to imap.gmail.com: Network is unreachable Do I need network-manager?? ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit

[Evolution] Problems with evo: Error writing data to TLS socket: The specified session has been invalidated for some reason.

2019-03-14 Thread Svante Signell via evolution-list
Hi, Suddenly evo refuses to read mail from my email account: Failed to open folder. The reported error was “Error reading data from TLS socket: The specified session has been invalidated for some reason.”. And: Failed to finish trust prompt for “a...@gmail.com” No PEM-encoded certificate found.

Re: kfreebsd mount missing libbsd.so.0 -> it is not installed.

2019-03-12 Thread Svante Signell
On Tue, 2019-03-12 at 13:35 +0100, Thomas Schweikle wrote: > Package: kfreeBSD-kernel > > Booting Debian GNU/kfreeBSD fails because mount does not find > libbsd.so.0 and mount not build as static or libbsd.so.0 not part of > boot filesystem. > > Any idea on how to recover? On a box running

Re: Need help with mach_printf()

2019-03-08 Thread Svante Signell
On Fri, 2019-03-08 at 11:45 +0100, Samuel Thibault wrote: > Perhaps you rather have to use > > settrans -cap /dev/null /usr/bin/env > LD_LIBRARY_PATH=/home/srs/hurd.debs/0.9.git20190303-1.3/libfshelp-tests/libs > /hurd/null Using the /usr/bin/env trick seems to work. Maybe the example by Thomas

Re: Need help with mach_printf()

2019-03-08 Thread Svante Signell
On Fri, 2019-03-08 at 11:42 +0100, Svante Signell wrote: > On Fri, 2019-03-08 at 11:39 +0100, Svante Signell wrote: > > On Fri, 2019-03-08 at 11:28 +0100, Samuel Thibault wrote: > > > Use mach_print for a start, to avoid any potential problem with vsnprintf > > > etc.

Re: Need help with mach_printf()

2019-03-08 Thread Svante Signell
On Fri, 2019-03-08 at 11:39 +0100, Svante Signell wrote: > On Fri, 2019-03-08 at 11:28 +0100, Samuel Thibault wrote: > > Use mach_print for a start, to avoid any potential problem with vsnprintf > > etc. > > > > Svante Signell, le ven. 08 mars 2019 11:16:32 +0100, a e

Re: Need help with mach_printf()

2019-03-08 Thread Svante Signell
On Fri, 2019-03-08 at 11:28 +0100, Samuel Thibault wrote: > Use mach_print for a start, to avoid any potential problem with vsnprintf etc. > > Svante Signell, le ven. 08 mars 2019 11:16:32 +0100, a ecrit: > > (cd libs; ln -s libtrivfs.so.0.3 libtrivfs.so.0) > > export L

Need help with mach_printf()

2019-03-08 Thread Svante Signell
Hi, As written on bug-hurd IRC. Attached is the relevant code. Thanks! /* Copyright (C) 1994, 2002, 2015-2019 Free Software Foundation, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-03-03 Thread Svante Signell
On Fri, 2019-03-01 at 07:04 -0800, Samuel Thibault wrote: > Svante Signell, le lun. 25 févr. 2019 10:25:01 +0100, a ecrit: > > Unfortunately, the situation has not improved with it :( > > > > The SIGILL failures are now SIGABRT and SIGSEGV as they became with the

Re: [!!] Do not upgrade coreutils to 8.30-2

2019-02-27 Thread Svante Signell
On Wed, 2019-02-27 at 13:36 -0800, Samuel Thibault wrote: > Hello, > > In version 8.30-2, a fix was added to coreutils to make it use > renameat2, but it happens that it wasn't supported in hurd's glibc, > and thus the "mv" command would fail completely. I have pushed a fix > to glibc, to be

Bug#922731: llvm-toolchain-7: Unjustified API breakage introduced by Debian patch

2019-02-26 Thread Svante Signell
ping! On Wed, 2019-02-20 at 12:51 +0100, Svante Signell wrote: > On Wed, 2019-02-20 at 09:21 +0100, Sylvestre Ledru wrote:

PATCH: gccgo for GNU/Hurd: Was: Re: gcc-8_8.3.0-2_source.changes ACCEPTED into unstable

2019-02-26 Thread Svante Signell
On Tue, 2019-02-26 at 08:39 +, Debian FTP Masters wrote: > > Accepted: > > Format: 1.8 > Date: Tue, 26 Feb 2019 09:26:57 +0100 > Source: gcc-8 > Architecture: source > Version: 8.3.0-2 > Distribution: unstable > Urgency: medium > Maintainer: Debian GCC Maintainers > Changed-By: Matthias

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-02-25 Thread Svante Signell
On Thu, 2019-02-21 at 20:56 +0100, Samuel Thibault wrote: > Hello, > > Mmmm, while having a look at glibc-2.29, I realized one patch was > missing, to enable thread-specific signal delivery. It looks like > fixing this gets to go to better work. I'll run the glibc testsuite > and probably

Bug#922731: llvm-toolchain-7: Unjustified API breakage introduced by Debian patch

2019-02-20 Thread Svante Signell
On Wed, 2019-02-20 at 09:21 +0100, Sylvestre Ledru wrote: > Le 20/02/2019 à 09:19, Dun Hum a écrit : > > > Would you have a testcase which shows the issue? This to make sure we > > > don't regress again > > > in the future. > > The simplest test case is the following one, it only checks that the

Re: [PATCH] Updated patches for the port of gccgo to GNU/Hurd

2019-02-11 Thread Svante Signell
On Mon, 2019-02-11 at 10:27 -0800, Ian Lance Taylor wrote: > On Mon, Feb 11, 2019 at 3:10 AM Svante Signell > wrote: > > On Sun, 2019-02-10 at 22:08 -0800, Ian Lance Taylor wrote: > > > On Sun, Feb 10, 2019 at 3:41 AM Svante Signell > > > wrote: > > > >

Re: [PATCH] Updated patches for the port of gccgo to GNU/Hurd

2019-02-11 Thread Svante Signell
On Sun, 2019-02-10 at 22:08 -0800, Ian Lance Taylor wrote: > On Sun, Feb 10, 2019 at 3:41 AM Svante Signell > wrote: > > On Sat, 2019-02-09 at 23:57 +0100, Svante Signell wrote: > > > On Sat, 2019-02-09 at 14:40 -0800, Ian Lance Taylor wrote: > > > > On Fri, Feb

Re: [PATCH] Updated patches for the port of gccgo to GNU/Hurd

2019-02-10 Thread Svante Signell
On Sat, 2019-02-09 at 23:57 +0100, Svante Signell wrote: > On Sat, 2019-02-09 at 14:40 -0800, Ian Lance Taylor wrote: > > On Fri, Feb 8, 2019 at 3:07 PM Matthias Klose wrote: > > > On 07.02.19 06:04, Ian Lance Taylor wrote: > > What are the lines before that in the log?

Re: [PATCH] Updated patches for the port of gccgo to GNU/Hurd

2019-02-09 Thread Svante Signell
On Sat, 2019-02-09 at 14:40 -0800, Ian Lance Taylor wrote: > On Fri, Feb 8, 2019 at 3:07 PM Matthias Klose wrote: > > On 07.02.19 06:04, Ian Lance Taylor wrote: > What are the lines before that in the log? For some reason libtool is > being invoke with no source files. The lines before the

Bug#921246: llvm-toolchain-7: FTBFS on kfreebsd-any

2019-02-05 Thread Svante Signell
On Tue, 2019-02-05 at 12:12 +0100, Sylvestre Ledru wrote: > Le 05/02/2019 à 12:05, Svante Signell a écrit : > > reopen 921246 > > found 921246 1:7.0.1-6 > > thanks > > > > On Mon, 2019-02-04 at 09:02 +0100, Sylvestre Ledru wrote: > > > When you work o

Bug#921246: llvm-toolchain-7: FTBFS on kfreebsd-any

2019-02-03 Thread Svante Signell
On Sun, 2019-02-03 at 23:39 +0100, Sylvestre Ledru wrote: > Le 03/02/2019 à 17:21, Sylvestre Ledru a écrit : > > Le 03/02/2019 à 15:28, Svante Signell a écrit : > > > Source: llvm-toolchain-7 > > > Version: 7_7.0.1-4 > > > Severity: important > >

Re: [PATCH] 1(3) hurd+glibc: Support for file record locking

2019-02-03 Thread Svante Signell
On Sat, 2019-02-02 at 14:34 +0100, Samuel Thibault wrote: > Hello, > So can you confirm my guesswork above? If, so, then only keep the first > line (the second line doesn't make sense in my guesswork), and mention > that while fcntl requires WR access for exclusive lock, flock doesn't. I've now

Re: [PATCH] 1(3) hurd+glibc: Support for file record locking

2019-02-02 Thread Svante Signell
On Sat, 2019-02-02 at 14:34 +0100, Samuel Thibault wrote: > Hello, > > Thanks for the fixes! YW! > Svante Signell, le sam. 02 févr. 2019 11:52:56 +0100, a ecrit: > > On Sun, 2018-12-30 at 21:21 +0100, Samuel Thibault wrote: > > > Svante Signell, le sam. 22 déc. 2

[PATCH] 3(3) hurd+glibc: Support for file record locking

2019-02-02 Thread Svante Signell
the series file: #hurd-i386/git-fcntl64.diff #hurd-i386/git-lockf-0.diff #hurd-i386/tg-WRLCK-upgrade.diff Thanks! sysdeps/mach/hurd/Changelog 2019-01-12 Svante Signell * Update copyright years. 2018-12-21 Svante Signell * hurd-i386/fcntl.diff: Add the required new arguments when calling

[PATCH] 2(3) hurd+glibc: Support for file record locking

2019-02-02 Thread Svante Signell
Attached is the second part of the patches for file record locking: libnetfs_file_record_lock.patch pflocal_fs.c.patch hurd_add_RPC.patch Thanks! hurd/ChangeLog 2019-02-01 Svante Signell * Update copyright years. 2018-01-05 Svante Signell * Update copyright years. * fs.defs: Add new

[PATCH] 1(3) hurd+glibc: Support for file record locking

2019-02-02 Thread Svante Signell
entries. Thanks! libdiskfs/ChangeLog 2019-02-01 Svante Signell * Update copyright years. * file-record-lock.c(diskfs_S_file_record_lock): Don't set rendezvous to MACH_PORT_NULL. 2018-12-07 Svante Signell * Update copyright years. * dir-lookup.c(diskfs_S_dir_lookup): Call

Re: Bug#920618: initscripts: errors with /dev/shm on Hurd

2019-02-02 Thread Svante Signell
On Sat, 2019-02-02 at 06:41 +0100, Samuel Thibault wrote: > Svante Signell, le sam. 02 févr. 2019 01:07:48 +0100, a ecrit: > > > > I'm having a look :) > > Thanks! :) Seem to work fine, after removing the broken links /run/shm -> /dev/shm and /dev/shm -> /run/shm. So

Re: GNUstep - check for reuse address

2019-01-29 Thread Svante Signell
On Sat, 2016-01-09 at 00:37 +0100, Samuel Thibault wrote: > Svante Signell, on Fri 08 Jan 2016 21:59:56 +0100, wrote: > > > Yes. And SO_REUSEADDR won't help there :) > > > > Samuel, this is exactly what the SO_REUSEADDR in pflocal should do: > > Except no Unix mak

Re: GNUstep - check for reuse address

2019-01-29 Thread Svante Signell
On Fri, 2016-01-08 at 21:59 +0100, Svante Signell wrote: > On Fri, 2016-01-08 at 16:43 +0100, Samuel Thibault wrote: > > Pino Toscano, on Fri 08 Jan 2016 16:40:08 +0100, wrote: > > > In data venerdì 8 gennaio 2016 13:34:46, Samuel Thibault ha > > > scritto: > >

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Mon, 2019-01-28 at 22:43 +0100, Samuel Thibault wrote: > Svante Signell, le lun. 28 janv. 2019 21:50:50 +0100, a ecrit: > > Thread 4 hit Breakpoint 2, __GI___sigaltstack (argss=0x3005c84, oss=0x0) at > > ../sysdeps/mach/hurd/sigaltstack.c:55 > > 55 in ../sysdeps/ma

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Mon, 2019-01-28 at 21:28 +0100, Samuel Thibault wrote: > Svante Signell, le lun. 28 janv. 2019 20:22:42 +0100, a ecrit: > > $24 = {ss_sp = 0x9501c, ss_size = 45028, ss_flags = 1} > > Actually these values look odd. You could check with a breakpoint > whether sigaltstack() is

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Mon, 2019-01-28 at 20:27 +0100, Svante Signell wrote: > On Mon, 2019-01-28 at 20:24 +0100, Samuel Thibault wrote: > > Svante Signell, le lun. 28 janv. 2019 20:23:38 +0100, a ecrit: > > > On Mon, 2019-01-28 at 20:18 +0100, Samuel Thibault wrote: > > > > It's odd t

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Mon, 2019-01-28 at 20:46 +0100, Samuel Thibault wrote: > Svante Signell, le lun. 28 janv. 2019 20:27:48 +0100, a ecrit: > > #0 runtime.sigtramp (sig=20, info=0x659551c, context=0x6595328) at > > Could you also print _hurd_global_sigstate->actions[20] , *info, and &g

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Mon, 2019-01-28 at 20:24 +0100, Samuel Thibault wrote: > Svante Signell, le lun. 28 janv. 2019 20:23:38 +0100, a ecrit: > > On Mon, 2019-01-28 at 20:18 +0100, Samuel Thibault wrote: > > > It's odd to have this all to 0... Do you have a backtrace to have an > > &

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Mon, 2019-01-28 at 20:18 +0100, Samuel Thibault wrote: > > It's odd to have this all to 0... Do you have a backtrace to have an > idea how we end up here? See next email.

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Mon, 2019-01-28 at 20:07 +0100, Svante Signell wrote: > On Sat, 2019-01-26 at 23:24 +0100, Samuel Thibault wrote: > > Samuel Thibault, le jeu. 24 janv. 2019 13:19:52 +0100, a ecrit: > > > Svante Signell, le jeu. 24 janv. 2019 12:11:25 +0100, a ecrit: > > > > Howe

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-28 Thread Svante Signell
On Sat, 2019-01-26 at 23:24 +0100, Samuel Thibault wrote: > Samuel Thibault, le jeu. 24 janv. 2019 13:19:52 +0100, a ecrit: > > Svante Signell, le jeu. 24 janv. 2019 12:11:25 +0100, a ecrit: > > > However, all these tests are still failing, but now mainly with SIGABRT or > &g

Re: I do not have internet on my GNU/Hurd vm

2019-01-26 Thread Svante Signell
On Sat, 2019-01-26 at 10:46 -0500, Joshua Branson wrote: > Hello, > > At the moment I do not have internet access on my GNU/Hurd vm. I'm not > certain how to go about fixing it. I'll attach the script that I use to > start my vm. I would be open to any help. #-net

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-25 Thread Svante Signell
On Thu, 2019-01-24 at 13:19 +0100, Samuel Thibault wrote: > Svante Signell, le jeu. 24 janv. 2019 12:11:25 +0100, a ecrit: > > I've built and installed glibc-2.28-5 with the patches in > > https://sourceware.org/bugzilla/show_bug.cgi?id=24110 > > Thanks! > > &g

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-24 Thread Svante Signell
On Wed, 2019-01-23 at 16:36 +0100, Samuel Thibault wrote: > Svante Signell, le mer. 23 janv. 2019 15:37:06 +0100, a ecrit: > > I'll take a look. Maybe these issues are causing the SIGILL errors in the > > gcc libgo tests. > > They might be indeed. Hello, I've built and i

Re: [Bug hurd/24110] SS_DISABLE never set in stack_t value returned by sigaltstack

2019-01-23 Thread Svante Signell
Hi, I'll take a look. Maybe these issues are causing the SIGILL errors in the gcc libgo tests. BBL. On Wed, 2019-01-23 at 00:28 +0100, Samuel Thibault wrote: > Hello, > > Could somebody give this a try? > > Samuel > > samuel.thiba...@ens-lyon.org, le dim. 20 janv. 2019 16:48:19 +, a

Add split_stack support for GNU/Hurd

2019-01-12 Thread Svante Signell
Lance Taylor and Matthis Klose. Thanks! gcc/config/ChangeLog 2018-10-10 Svante Signell * gcc/config/i386/gnu.h: Enable split-stack support Index: gcc-snapshot-20181019-1.1/src/gcc/config/i386/gnu.h === --- gcc-snapshot-20181019

Bug#918884: python-psutil: FTBFS on kfreebsd-any

2019-01-10 Thread Svante Signell
Source: python-psutil Version: 5.4.8-1 Severity: important Tags: ftbfs, patch User: debian-k...@lists.debian.org Usertags: kfreebsd Hello, Currently python-psutil FTBFS on GNU/kFreeBSD a missing port to that architecture. Attached are two patches, kfreebsd-port.diff and kfreebsd-port- test.diff

Re: Removing a package from unstable

2019-01-06 Thread Svante Signell
On Sun, 2019-01-06 at 18:37 +0100, Mattia Rizzolo wrote: > On Sun, Jan 06, 2019 at 04:41:51PM +0100, Ole Streicher wrote: > > That is a different thing: once the dependencies on Hurd are fixed, > > you > > Of course the hurd issue turned out more complex once I actually read > past the first

Bug#917806: gdb: FTBFS on kfreebsd-any

2018-12-30 Thread Svante Signell
Source: gdb Version: 8.2.1-1 Severity: important Tags: ftbfs, patch User: debian-k...@lists.debian.org Usertags: kfreebsd Hello, Currently libdrm FTBFS on GNU/kFreeBSD due to a change of "struct nlist" in the header file /usr/include/bsd/nlist.h. Attached is a patch to make gdb build properly

[PATCH] 3(3) hurd+glibc: Support for file record locking

2018-12-22 Thread Svante Signell
the series file: #hurd-i386/git-fcntl64.diff #hurd-i386/git-lockf-0.diff #hurd-i386/tg-WRLCK-upgrade.diff Thanks!sysdeps/mach/hurd/Changelog 2018-12-21 Svante Signell * hurd-i386/fcntl.diff: Add the required new arguments when calling the updated RPC file_record_lock. 2018-12-04 Svante Signell

[PATCH] 2(3) hurd+glibc: Support for file record locking

2018-12-22 Thread Svante Signell
Attached is the second part of the patches for file record locking: libnetfs_file_record_lock.patch pflocal_fs.c.patch hurd_add_RPC.patch Thanks!hurd/ChangeLog 2018-01-05 Svante Signell * Update copyright years. * fs.defs: Add new argument rendezvous: mach_port_send_t to RPC file_record_lock

[PATCH] 1(3) hurd+glibc: Support for file record locking

2018-12-22 Thread Svante Signell
entries. Thanks!libdiskfs/ChangeLog 2018-12-07 Svante Signell * Update copyright years. * dir-lookup.c(diskfs_S_dir_lookup): Call fshelp_rlock_tweak() with new last argument rendezvous = MACH_PORT_NULL. * file-lock.c(diskfs_S_file_lock): Likewise. * file-record-lock.c

[PATCH] 1(2) hurd+glibc: Support for file record locking

2018-12-22 Thread Svante Signell
): Add new argument mach_port_t rendezvous. 2017-01-05 Svante Signell * Update copyright years and headers. 2016-05-23 Svante Signell * define temporary CPP_FLAGS until glibc is updated * file-lock-stat.c: Port from cthreads to libpthread. * file-lock.c: Likewise. * file-record-lock

[PATCH] 1(2) hurd+glibc: Support for file record locking

2018-12-22 Thread Svante Signell
): Add new argument mach_port_t rendezvous. 2017-01-05 Svante Signell * Update copyright years and headers. 2016-05-23 Svante Signell * define temporary CPP_FLAGS until glibc is updated * file-lock-stat.c: Port from cthreads to libpthread. * file-lock.c: Likewise. * file-record-lock

Bug#848631: Can I take over the xpdf package?

2018-12-21 Thread Svante Signell
Hi Manasori, I was never allowed to maintain that package since I wanted to use the upstream backend. Debian requested that I should continue to support the from xpdf upstream diverging poppler backend. As I see xpdf with the poppler backend is already maintained by the Debian QA Group . Latest

Bug#848631: Can I take over the xpdf package?

2018-12-21 Thread Svante Signell
Hi Manasori, I was never allowed to maintain that package since I wanted to use the upstream backend. Debian requested that I should continue to support the from xpdf upstream diverging poppler backend. As I see xpdf with the poppler backend is already maintained by the Debian QA Group . Latest

Re: adduser not working?

2018-12-20 Thread Svante Signell
On Thu, 2018-12-20 at 11:23 -0500, Joshua Branson wrote: > Almudena Garcia writes: > > > Are you tried to install perl? > > Feels that adduser command exists, but need perl to run. > > Maybe...I feel like perl is installed by default. Maybe I'm wrong. > > Regardless, when I'm in my hurd vm, I

Re: RFC: [PATCH hurd 1/6] Add file record locking support: libfshelp_rlock.patch

2018-12-07 Thread Svante Signell
On Mon, 2018-12-03 at 12:17 +0100, Samuel Thibault wrote: > Samuel Thibault, le lun. 03 déc. 2018 12:14:42 +0100, a ecrit: > > to which you'd pass MACH_PORT_NULL for now. And in the server, in the > > GETLK case, set the l_pid field to -1 for now. > > More precisely: in the server, for now set

Bug#914897: debating the wrong thing

2018-12-05 Thread Svante Signell
On Tue, 2018-12-04 at 21:58 +0100, Ansgar Burchardt wrote: > > If we keep merged-/usr as default then we can /recommend/ people to > install usrmerge to switch to merged-/usr; reducing the difference > between newly-installed and existing setups is a good idea IMHO. I > think I filed a report

Bug#914897: debating the wrong thing

2018-12-05 Thread Svante Signell
On Tue, 2018-12-04 at 21:58 +0100, Ansgar Burchardt wrote: > > If we keep merged-/usr as default then we can /recommend/ people to > install usrmerge to switch to merged-/usr; reducing the difference > between newly-installed and existing setups is a good idea IMHO. I > think I filed a report

Re: Bug#914897: debating the wrong thing

2018-12-05 Thread Svante Signell
On Tue, 2018-12-04 at 21:58 +0100, Ansgar Burchardt wrote: > > If we keep merged-/usr as default then we can /recommend/ people to > install usrmerge to switch to merged-/usr; reducing the difference > between newly-installed and existing setups is a good idea IMHO. I > think I filed a report

Re: Comment on glibc2.28: Re: [PATCH glibc] Add file record locking support

2018-12-03 Thread Svante Signell
On Mon, 2018-12-03 at 16:25 +0100, Samuel Thibault wrote: > Svante Signell, le lun. 03 déc. 2018 16:01:37 +0100, a ecrit: > > On Sat, 2018-12-01 at 19:30 +0100, Samuel Thibault wrote: > > > I forgot here: > > > > Is this really needed? > > Please quote a b

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

2018-12-03 Thread Svante Signell
On Sun, 2018-12-02 at 21:04 +0100, Marc Haber wrote: > > The next debhelper change might choose to give / instead of /usr as a > target directory by default, moving hundreds of megabytes from /usr to / > over time. This solution was proposed by GNU/Hurd several years ago, and was scrapped due to

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

2018-12-03 Thread Svante Signell
On Sun, 2018-12-02 at 21:04 +0100, Marc Haber wrote: > > The next debhelper change might choose to give / instead of /usr as a > target directory by default, moving hundreds of megabytes from /usr to / > over time. This solution was proposed by GNU/Hurd several years ago, and was scrapped due to

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

2018-12-03 Thread Svante Signell
On Sun, 2018-12-02 at 21:04 +0100, Marc Haber wrote: > > The next debhelper change might choose to give / instead of /usr as a > target directory by default, moving hundreds of megabytes from /usr to / > over time. This solution was proposed by GNU/Hurd several years ago, and was scrapped due to

Re: Comment on glibc2.28: Re: [PATCH glibc] Add file record locking support

2018-12-03 Thread Svante Signell
On Sat, 2018-12-01 at 19:30 +0100, Samuel Thibault wrote: > I forgot here: Is this really needed? From git-fcntl64.diff: Index: glibc-2.28/sysdeps/mach/hurd/fcntl.c === --- glibc-2.28.orig/sysdeps/mach/hurd/fcntl.c +++

Re: RFC: [PATCH hurd 1/6] Add file record locking support: libfshelp_rlock.patch

2018-12-02 Thread Svante Signell
On Mon, 2016-02-08 at 23:33 +0100, Samuel Thibault wrote: > Svante Signell, on Mon 08 Feb 2016 12:51:42 +0100, wrote: > > 1) Locks are inherited by fork, they should not. Test program: libfshelp- > > tests/fork.c > > As I mentioned previously, this should be fine for n

Comment on glibc2.28: Re: [PATCH glibc] Add file record locking support

2018-12-01 Thread Svante Signell
On Thu, 2015-01-08 at 12:40 +0100, Svante Signell wrote: > Hi, > > Attached is the patch adding support for file record locking in glibc, > as implemented in Hurd by Neal Walfield and others. This patch should be > applied after the corresponding hurd patch series in case

Comment on glibc2.28: Re: [PATCH glibc] Add file record locking support

2018-12-01 Thread Svante Signell
On Thu, 2015-01-08 at 12:40 +0100, Svante Signell wrote: > Hi, > > Attached is the patch adding support for file record locking in glibc, > as implemented in Hurd by Neal Walfield and others. This patch should be > applied after the corresponding hurd patch series in case

Re: RFC: [PATCH hurd 3/6] Add file record locking support: libtrivfs_file_record_lock.patch

2018-12-01 Thread Svante Signell
On Sun, 2018-11-18 at 13:50 +0100, Samuel Thibault wrote: > Samuel Thibault, le dim. 18 nov. 2018 13:46:22 +0100, a ecrit: > > Svante Signell, le dim. 18 nov. 2018 13:44:40 +0100, a ecrit: > > > On Sun, 2018-11-18 at 01:13 +0100, Samuel Thibault wrote: > > > > I don't

Re: usrmerge -- plan B?

2018-11-21 Thread Svante Signell
On Wed, 2018-11-21 at 14:43 +, Holger Levsen wrote: > Hi Simon, > > On Wed, Nov 21, 2018 at 02:05:42PM +, Simon McVittie wrote: > [...] > > > Another question is, why? > > [...] > > thank you very much for explaining in detail why usrmerge is sensible > and the right thing to do for

Re: [DNG] /usr to merge or not to merge... that is the question

2018-11-21 Thread Svante Signell
On Wed, 2018-11-21 at 12:17 +, Roger Leigh wrote: > Hi folks, > > I've been following the discussion with interest. It's certainly not a > new discussion, since I remember debating it a good few years back, but > there are still the same opinions and thoughts on the topic that I >

Re: usrmerge -- plan B?

2018-11-21 Thread Svante Signell
On Wed, 2018-11-21 at 13:09 +0100, Marc Haber wrote: > On Wed, 21 Nov 2018 10:52:22 +0100, Adam Borowski > wrote: > > I am seriously claiming that RHEL is in the place Solaris was in 2010. > > Rapidly falling user share (like Solaris, it was ubiquitous in the past!), > > acquired by a company

Re: RFC: [PATCH hurd 3/6] Add file record locking support: libtrivfs_file_record_lock.patch

2018-11-18 Thread Svante Signell
On Sun, 2018-11-18 at 01:13 +0100, Samuel Thibault wrote: > Hello, > > Triggered by an IRC discussion, I had a look at this old mail still > in my mbox: > > Justus Winter, le lun. 08 févr. 2016 15:04:14 +0100, a ecrit: > > > Quoting Svante Signell (2016-02-08 12:53

Bug#746442: Please make /etc/rc.local non-executable by default

2018-11-15 Thread Svante Signell
On Thu, 2018-11-15 at 12:01 -0800, Josh Triplett wrote: > On Thu, Nov 15, 2018 at 08:44:03PM +0100, Thorsten Glaser wrote: > > On Thu, 15 Nov 2018, Josh Triplett wrote: > > > (Personally, I *wish* that /etc/rc.local didn't exist at all by > > > default > > > and you had to *create* it if you

Bug#913140: ghc: FTBFS on kfreebsd-any

2018-11-07 Thread Svante Signell
Source: ghc Version: 8.4.3+dfsg1-4 Severity: important Tags: ftbfs, patch User: debian-k...@lists.debian.org Usertags: kfreebsd Hello, Currently ghc FTBFS on GNU/kFreeBSD since 8.2.2-6. Attached is a patch to fix this by adding kfreebsdgnu to GHC_CONVERT_OS in aclocal.m4. Thanks!Index:

Bug#913140: ghc: FTBFS on kfreebsd-any

2018-11-07 Thread Svante Signell
Source: ghc Version: 8.4.3+dfsg1-4 Severity: important Tags: ftbfs, patch User: debian-k...@lists.debian.org Usertags: kfreebsd Hello, Currently ghc FTBFS on GNU/kFreeBSD since 8.2.2-6. Attached is a patch to fix this by adding kfreebsdgnu to GHC_CONVERT_OS in aclocal.m4. Thanks!Index:

Re: GOOS updated: Port of gccgo to GNU/Hurd

2018-11-03 Thread Svante Signell
ping, no feedback so far, is anything missing/are the patches rejected? On Sat, 2018-10-27 at 20:43 +0200, Svante Signell wrote: > Hello, > > As advised by the Debian gcc maintainer Matthias Klose and golang > developer Ian Lance Taylor I'm (re-)submitting the patches for > th

Re: Some lwip, dde, and rump related wiki changes

2018-10-27 Thread Svante Signell
Hi Joshua, pfinit -> pfinet On Sat, 2018-10-27 at 15:58 +0200, Samuel Thibault wrote: > Hello, > > Joshua Branson, le sam. 27 oct. 2018 10:08:28 -0400, a ecrit: > > Hello,  I've mentioned that DDE is no longer being maintained and > > pointed people to the rump webpage, which is one that I just

Re: Port of gccgo to GNU/Hurd

2018-10-22 Thread Svante Signell
On Mon, 2018-10-22 at 11:15 +0200, Svante Signell wrote: > Hello, > > As advised by the Debian gcc maintainer Matthias Klose and golang > developer Ian Lance Taylor (Cc:ed) I'm (re-)submitting the patches > for the port of gccgo to GNU/Hurd. > > The 13 patches are: Due t

Re: tinysshd dependency on systemd

2018-10-21 Thread Svante Signell
On Sun, 2018-10-21 at 23:04 +0200, Vincent Bernat wrote: >  ❦ 21 octobre 2018 18:12 GMT, Ivan Shmakov : > > > > > You know, in almost twenty years of using GNU/Linux, I think > > it’s the first time I’m requested /not/ to report bugs and > > contribute patches.  How times did change,

Re: Debian Buster release to partially drop non-systemd support

2018-10-19 Thread Svante Signell
On Fri, 2018-10-19 at 09:37 +0200, Philipp Kern wrote: > On 2018-10-19 08:39, Narcis Garcia wrote: > > El 18/10/18 a les 22:07, Bernd Zeimetz ha escrit: > > > For my packages I can state that I do not have a single machine > > > which is not using systemd - and to be honest - I won't waste my > >

Re: Debian Buster release to partially drop non-systemd support

2018-10-19 Thread Svante Signell
On Fri, 2018-10-19 at 09:37 +0200, Philipp Kern wrote: > On 2018-10-19 08:39, Narcis Garcia wrote: > > El 18/10/18 a les 22:07, Bernd Zeimetz ha escrit: > > > For my packages I can state that I do not have a single machine > > > which is not using systemd - and to be honest - I won't waste my > >

Bug#908847: llvm-toolchain-6.0: FTBFS on hurd-i386

2018-10-18 Thread Svante Signell
On Thu, 2018-10-18 at 16:55 +0200, Samuel Thibault wrote: > Sylvestre Ledru, le jeu. 18 oct. 2018 16:52:46 +0200, a ecrit: > > > > > Do you want me to forward this upstream or are you going to do it? > > Svante, that's a question for you ;) Sylvestre, If you have the time and the channel to

Re: Debian Buster release to partially drop non-systemd support

2018-10-15 Thread Svante Signell
On Mon, 2018-10-15 at 17:06 +0200, Samuel Thibault wrote: > > It's a matter of people subscribing to the > pkg-sysvinit-de...@lists.alioth.debian.org list and discussing there, > I > don't see why anything heavier would be needed. I thought alioth was no more, but maybe the mailing list remains?

Re: Debian Buster release to partially drop non-systemd support

2018-10-15 Thread Svante Signell
On Mon, 2018-10-15 at 17:06 +0200, Samuel Thibault wrote: > > It's a matter of people subscribing to the > pkg-sysvinit-de...@lists.alioth.debian.org list and discussing there, > I > don't see why anything heavier would be needed. I thought alioth was no more, but maybe the mailing list remains?

Re: Debian Buster release to partially drop non-systemd support

2018-10-15 Thread Svante Signell
On Mon, 2018-10-15 at 17:06 +0200, Samuel Thibault wrote: > > It's a matter of people subscribing to the > pkg-sysvinit-de...@lists.alioth.debian.org list and discussing there, > I > don't see why anything heavier would be needed. I thought alioth was no more, but maybe the mailing list remains?

Bug#904289: libgo build failure with GCC trunk 20181004

2018-10-08 Thread Svante Signell
On Fri, 2018-10-05 at 21:10 +0200, Svante Signell wrote: > On Fri, 2018-10-05 at 01:38 +0200, Matthias Klose wrote: > > Hi Svante, > > > > please have a look at the recent libgo build failure with GCC trunk > > 20181004 after the libgo merge.  Please could you update th

Bug#904289: libgo build failure with GCC trunk 20181004

2018-10-08 Thread Svante Signell
On Fri, 2018-10-05 at 21:10 +0200, Svante Signell wrote: > On Fri, 2018-10-05 at 01:38 +0200, Matthias Klose wrote: > > Hi Svante, > > > > please have a look at the recent libgo build failure with GCC trunk > > 20181004 after the libgo merge.  Please could you update th

Bug#900240: Upstream fixes of cmake for GNU/Hiurd

2018-10-05 Thread Svante Signell
Hello Samuel, Time to make an NMU of cmake. The needed patches are now committed upstream, see below: From: Brad King Subject: Re: CMake | Port to GNU Hurd (#18337) AFAIK the only changes were 3c0bfb59 and c990649b. The former is already in 3.12.3. The latter will be in 3.13.

<    1   2   3   4   5   6   7   8   9   10   >