Re: [DNG] eudev missing dependency

On Tue, 2017-12-26 at 18:51 +0100, J. Fahrner wrote: > Hi, > > udevd calls mtp-probe: > > udevd[436]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe  > /sys/devices/pci:00/:00:14.0/usb3/3-4 3 2': No such file or  > directory > > mtp-probe is contained in libmtp-runtime, so eudev

Re: [DNG] udev-finish: No such file or directory

On Wed, 2017-12-27 at 08:30 +0100, J. Fahrner wrote: > Am 2017-12-27 07:57, schrieb Ralph Ronnquist: > > Probably you have the dangling link /etc/rcS.d/S11udev-finish (or > > similar), which would be a remnant from the udev package, and it > > should have been removed when udev was removed. > > >

Bug#885249: yoshimi: FTBFS on hurd-i386: PATH_MAX undeclared

tags 885289 patch thanks On Mon, 2017-12-25 at 22:49 -0500, Aaron M. Ucko wrote: > Source: yoshimi > Version: 1.5.6-2 > Severity: important > Tags: upstream > Justification: fails to build from source > User: debian-h...@lists.debian.org > Usertags: hurd-i386 > The Hurd notoriously has no static

Bug#885249: yoshimi: FTBFS on hurd-i386: PATH_MAX undeclared

tags 885289 patch thanks On Mon, 2017-12-25 at 22:49 -0500, Aaron M. Ucko wrote: > Source: yoshimi > Version: 1.5.6-2 > Severity: important > Tags: upstream > Justification: fails to build from source > User: debian-h...@lists.debian.org > Usertags: hurd-i386 > The Hurd notoriously has no static

Re: [DNG] eudev naming of network interfaces

On Tue, 2017-12-26 at 19:17 +0100, J. Fahrner wrote: > Hi, > is there some problem with the naming of network interfaces? > > I have the following lines in my boot log: > > Sat Dec 23 10:41:48 2017: [] Configuring network  > interfaces...ifquery: unknown interface eth0 > Sat Dec 23 10:41:48

Bug#885012: extrace: FTBFS on non-Linux: linux/connector.h absent

On Fri, 2017-12-22 at 16:03 -0500, Aaron M. Ucko wrote: > Source: extrace > Version: 0.4-1 > Severity: important > Justification: fails to build from source > User: debian-h...@lists.debian.org > Usertags: hurd-i386 > > Builds of extrace for (non-release) non-Linux architectures (just > hurd-i386

Re: [DNG] Long boot wait after upgrade to ascii

On Sat, 2017-12-23 at 16:38 -0500, Hendrik Boom wrote: > On Sat, Dec 23, 2017 at 04:37:10PM +0100, J. Fahrner wrote: > > > > I now looked up the UUID, entered it in > > /etc/initramfs-tools//conf.d/resume, and now it works as before. > > > > The question remains: which step during dist-upgrade

Bug#881569: [Fwd: gdb: FTBFS on hurd-i386]

Hello, These patches was submitted to Debian November 13 2017. Nothing has happened so far, so maybe upstream would be interested to consider the patches for next release. Thanks! --- Begin Message --- Source: gdb Version: 8.0-1 Severity: important Tags: patch User: debian-h...@lists.debian.org

[Fwd: gdb: FTBFS on hurd-i386]

Hello, These patches was submitted to Debian November 13 2017. Nothing has happened so far, so maybe upstream would be interested to consider the patches for next release. Thanks! --- Begin Message --- Source: gdb Version: 8.0-1 Severity: important Tags: patch User: debian-h...@lists.debian.org

Bug#767847: gworkspace: FTBFS on hurd-i386

On Thu, 2017-12-21 at 00:22 +0200, Yavor Doganov wrote: > Ivan Vučica wrote: > > Also malloc(...)+1 should be malloc(...+1). > > That's right, it is the latter in my patch. > > > Also strncpy() IIRC doesn’t add a nul terminator. > > Correct, it is added with a special assignment after the loop,

Re: [DNG] Working with ASCII *ERRATUM*

On Fri, 2017-12-22 at 11:53 +0100, Didier Kryn wrote: > Le 22/12/2017 à 08:58, Didier Kryn a écrit : > > > > PS please find my patch in attachment. > > This was the wrong patch, against /lib/udev/ifupdown-hotplug,  > falsely renamed. > > Now I attach the right one. Hi, Attached is

Re: race condition destroying condition variables

On Thu, 2017-12-21 at 17:32 -0500, Brent W. Baccala wrote: > Well, I've got a patch that might work, but I'm having a lot of > trouble testing it. > > I can't dpkg-buildpackage the Debian glibc package. > > It gets into the test routines, then a bunch of the math tests crash > with SIGSEGVs and

Bug#853783: Reopen 853783

On Thu, 2017-12-21 at 13:08 +, Brian Potkin wrote: > /var/lib/hp/hplip.state. [plugin] installed = 1 eula = 1 version = 3.16.7 Independent of which version is installed: libhpmud0_3.16.7+repack0-1_amd64.deb libsane-hpaio_3.16.7+repack0-1_amd64.deb scanimage > test.png

Bug#853783: Reopen 853783

On Thu, 2017-12-21 at 13:08 +, Brian Potkin wrote: > /var/lib/hp/hplip.state. [plugin] installed = 1 eula = 1 version = 3.16.7 Independent of which version is installed: libhpmud0_3.16.7+repack0-1_amd64.deb libsane-hpaio_3.16.7+repack0-1_amd64.deb scanimage > test.png

Bug#853783: Reopen 853783

On Wed, 2017-12-13 at 23:24 +, Brian Potkin wrote: > On Wed 13 Dec 2017 at 22:17:27 +0100, Svante Signell wrote: > > > reopen 853783 > > thanks > > > > Since I have not obtained a mail from you about the scanner problems since > > Tue, > > 28 Feb

Bug#853783: Reopen 853783

On Wed, 2017-12-13 at 23:24 +, Brian Potkin wrote: > On Wed 13 Dec 2017 at 22:17:27 +0100, Svante Signell wrote: > > > reopen 853783 > > thanks > > > > Since I have not obtained a mail from you about the scanner problems since > > Tue, > > 28 Feb

Re: [PATCH] LwIP translator

On Tue, 2017-12-19 at 19:21 +0100, Samuel Thibault wrote: > Joan Lledó, on mar. 19 déc. 2017 19:11:40 +0100, wrote: > > - The patches in debian/patches are not enough to make the server > > work, for instance, we're calling lwip_poll() which is not in 2.0.3 > > nor any patch in the package. I

Re: SIGILL problems with Hurd port of GO in gcc-8, and rpctrace bugs.

On Tue, 2017-12-19 at 10:39 +0100, Samuel Thibault wrote: > Svante Signell, on mar. 19 déc. 2017 10:36:22 +0100, wrote: > > And FYI: gdb is totally unusable, the only output is threads are created an > > then > > a hard hang of gdb, only resolvable with kill -9 from another

Re: SIGILL problems with Hurd port of GO in gcc-8, and rpctrace bugs.

On Sun, 2017-11-19 at 20:04 -0500, Brent W. Baccala wrote: > On Fri, Nov 17, 2017 at 3:14 PM, Svante Signell <svante.sign...@gmail.com> > wrote: > > Thanks a lot for your patches for rpctrace. Now more failing programs > > can be traced, where the standard version fai

Re: [DNG] ascii an waiting for dhcp on boot

On Mon, 2017-12-18 at 16:00 +0100, Didier Kryn wrote: > Le 18/12/2017 à 15:58, Svante Signell a écrit : > > On Mon, 2017-12-18 at 15:32 +0100, Didier Kryn wrote: > > >   I've just done apt-get source ifupdown. > > > > > >   The source contains two

Bug#853783: Reopen 853783

On Mon, 2017-12-18 at 14:55 +, Brian Potkin wrote: > On Wed 13 Dec 2017 at 23:24:29 +, Brian Potkin wrote: > > > On Wed 13 Dec 2017 at 22:17:27 +0100, Svante Signell wrote: > > > > > reopen 853783 > > > thanks > > > > > Svante

Bug#853783: Reopen 853783

On Mon, 2017-12-18 at 14:55 +, Brian Potkin wrote: > On Wed 13 Dec 2017 at 23:24:29 +, Brian Potkin wrote: > > > On Wed 13 Dec 2017 at 22:17:27 +0100, Svante Signell wrote: > > > > > reopen 853783 > > > thanks > > > > > Svante

Re: [DNG] ascii an waiting for dhcp on boot

On Mon, 2017-12-18 at 15:32 +0100, Didier Kryn wrote: > I've just done apt-get source ifupdown. > > The source contains two patches: > 0001-Fix-a-crash-when-multiple-interfaces-are-specified-f.patch > 0001-Unconditionally-ifup-hotplug-interfaces > > So it seems things are well

Re: [DNG] Interface names changed after eudev installation

On Thu, 2017-12-14 at 08:22 +0100, Dr. Nikolaus Klepp wrote: > Am Mittwoch, 13. Dezember 2017 schrieb Yevgeny Kosarzhevsky: > > Hello, > > > > > > I have run upgrade recently and got eudev installed. > > After reboot I've got some weird names of interfaces: wlp4s0 and > > wwp0s20f0u3i12 instead

Bug#853783: Reopen 853783

reopen 853783 thanks Since I have not obtained a mail from you about the scanner problems since Tue, 28 Feb 2017 I reopen this bug. Your replies have not reached me. And you cannot expect me to look at the web page for all bugs I've submitted. I see that my email address, and the bug number is

Bug#853783: Reopen 853783

reopen 853783 thanks Since I have not obtained a mail from you about the scanner problems since Tue, 28 Feb 2017 I reopen this bug. Your replies have not reached me. And you cannot expect me to look at the web page for all bugs I've submitted. I see that my email address, and the bug number is

Re: [DNG] Text editor ?

On Mon, 2017-12-11 at 08:04 +0100, J. Fahrner wrote: > Am 2017-12-10 23:25, schrieb Renaud (Ron) OLGIATI: > > Thanks, I should have been more precise: one with a GUI. > > My favourite GUI text editor is Geany. emacs of course :) ___ Dng mailing list

Re: How to build only amd64 and avoid building gcc for 32 and x32?

On Sat, 2017-12-09 at 00:42 +0100, Svante Signell wrote: > Hi, > > The title says it all. It is a little annoying to have to build gcc-x > for all multilib architectures. Where to set a build only for amd64 in > debian/rules* or DEB_BUILD_OPTIONS? > > Trying to build gcc

[Fwd: Short talk on 34c3?]

Forwarding to bug-hurd--- Begin Message --- Hi everyone, the FSFE is planning a session on the 34th Chaos Communication Congress about Free operating systems that are not based on Linux. We want to promote "free software diversity" and would love have someone introduce Debian GNU/kFreeBSD and/or

Re: [DNG] Installing & running eudev broke USB drives auto-listing in Thunar.

rdon (again). Hi Steve, Nice of you to write this message. Just one nitpcick: This mail contains: On Sat, 9 Dec 2017 11:06:05 + > aitor_czr <aitor_...@gnuinos.org> wrote: and the quote should have been: On Sat, 2017-12-09 at 11:06 +, aitor_czr wrote: > Dear Svante, > On 09/12/17

Re: [DNG] two dhcp configurations

On Sat, 2017-12-09 at 22:51 +, KatolaZ wrote: > On Sat, Dec 09, 2017 at 04:34:34PM -0500, Hendrik Boom wrote: > > Somehow I have two dhcp configuration files: /etc/dhcp/dhcpd.conf and /etc/dhcpd.conf > > >   $ apt-file search dhcpd.conf > > says that the former comes from isc-dhcp-server

Re: [DNG] Installing & running eudev broke USB drives auto-listing in Thunar.

On Fri, 2017-12-08 at 01:23 +0100, aitor_czr wrote: > > On 12/09/2017 12:47 AM, Svante Signell wrote: > > Hi aitor, > > > > Looking at the above it was a small nitpick, i.e. a typo in my > > understanding, not a harsh comment. > > > > Have a nice day

Re: [DNG] Installing & running eudev broke USB drives auto-listing in Thunar.

On Fri, 2017-12-08 at 18:23 +, aitor_czr wrote: > > (just a small nitpick: My last name is Signell, with two l's in the > > end) >   > No need to be harsh..., it was just a typo. Hi aitor, Looking at the above it was a small nitpick, i.e. a typo in my understanding, not a harsh comment.

How to build only amd64 and avoid building gcc for 32 and x32?

Hi, The title says it all. It is a little annoying to have to build gcc-x for all multilib architectures. Where to set a build only for amd64 in debian/rules* or DEB_BUILD_OPTIONS? Trying to build gcc-8-8-20171128-1 fails with: /usr/include/gnu/stubs.h:13:11: fatal error: gnu/stubs-x32.h: No

Re: [DNG] ascii an waiting for dhcp on boot

On Wed, 2017-12-06 at 20:08 +0900, Olaf Meeuwissen wrote: > > Downgrade to 0.8.13?  From the changelog for 0.8.14: > >   * Ignore link state when bringing up hotplug interfaces at boot. > Closes: #814785, #834820 > > # Had a quick look and it *seems* udev is involved somehow ... Just an

Re: [DNG] Installing & running eudev broke USB drives auto-listing in Thunar.

On Sat, 2017-12-02 at 17:19 +0100, Edward Bartolo wrote: > On 1st Dec 2017, Svante Signel wrote: > "This is a last warning. If you are continuing to not quote previous > mails, I'll never reply to a posting from you again. Learn some > netiquette!" > > Sorry, I had no intention to be rude. Gmail

Re: [DNG] netiquette Was: Re: Installing & running eudev broke USB drives auto-listing in Thunar.

On Fri, 2017-12-01 at 22:55 +, Rowland Penny wrote: > I hope they do not learn from you, your attitude is atrocious. > Eduardo has a valid problem and perhaps he isn't replying in exactly > the way you want, but so what, be polite and ask again in plain > questions for what you need to try

Re: [DNG] netiquette

On Fri, 2017-12-01 at 23:44 +0100, Antony Stone wrote: > On Friday 01 December 2017 at 23:10:10, Svante Signell wrote: > > > PS: Who is the best female skier currently? > > Downhill, slalom, cross-country, or other? Ah, I thought merely about cross-country. You know, No

[DNG] netiquette Was: Re: Installing & running eudev broke USB drives auto-listing in Thunar.

On Fri, 2017-12-01 at 21:55 +, Olav Selseng Vestreim wrote: > On Friday 1. December 2017 11.10.57 Svante Signell wrote: > > Hi again, > > > > This is a last warning. If you are continuing to not quote previous > > mails, > > I'll never reply to a p

Re: Need help about choosing MSc thesis

On Fri, 2017-12-01 at 16:57 +0330, behnam mohammad karimi wrote: > Hi > I want work on HURD for my MSc thesis. So I want some paper about HURD or > kernel development, but I can't find any paper   > Can u help me? Do u have any paper? (2015 or later) Hi, There is a rather recent Bachelors

Re: [DNG] Installing & running eudev broke USB drives auto-listing in Thunar.

Hi again, This is a last warning. If you are continuing to not quote previous mails, I'll never reply to a posting from you again. Learn some netiquette! On Fri, 2017-12-01 at 10:46 +0100, Edward Bartolo wrote: > These are the results. For what? With udev installed (which eudev version are you

Re: [DNG] Installing & running eudev broke USB drives auto-listing in Thunar.

On Fri, 2017-12-01 at 09:31 +0100, Edward Bartolo wrote: > This installation was done on ASCII. > > Before this installation Thunar used to auto-list USB thumbdrives. > Running pstree shown udevd is running instead of eudevd although I do > not know whether eudev and udev use exactly the same

Re: [DNG] eudev in experimental for ascii

On Mon, 2017-11-27 at 13:05 +0100, Edward Bartolo wrote: > Can I install eudev without having to use the experimental repository? Add experimental temporarily to sources.list, apt-get update, apt-get download udev, etc., remove eperimental from sources.list HTH

[DNG] Package naming: Was Re: eudev in experimental for ascii

On Mon, 2017-11-27 at 11:11 +, KatolaZ wrote: > On Mon, Nov 27, 2017 at 11:42:04AM +0100, Jaromil wrote: > > > Dear D1rs, > > it looks like the package might have hiccups when multiarch is > enabled. In particular, it seems that on amd64 with multiarch enabled > and i386 active, the i386

Re: [DNG] ifconfig deprecated?

On Tue, 2017-11-21 at 23:50 +0100, Adam Borowski wrote: > > No one is removing ifconfig yet, it's merely not installed by default > anymore -- so if you insist, just "apt install net-tools". > > ifconfig is inadequate for a number of widespread setups, though, and will > provide bad output

Re: Fix gcc-7 and gcc-8 build of GO for Hurd and not kFreeBSD in debian/rules.defs

On Mon, 2017-11-20 at 14:04 +0100, Aurelien Jarno wrote: > On 2017-11-20 13:20, Svante Signell wrote: > > On Thu, 2017-11-16 at 20:39 +0100, Svante Signell wrote: > > > > Seeing the recent update of debian/rules.defs in gcc-7 a mistake was > > revealed in the patch deb

Fix gcc-7 and gcc-8 build of GO for Hurd and not kFreeBSD in debian/rules.defs

On Thu, 2017-11-16 at 20:39 +0100, Svante Signell wrote: Seeing the recent update of debian/rules.defs in gcc-7 a mistake was revealed in the patch debian_rules.defs for both gcc-7 and gcc-8. The correct patch is inlined below: --- a/debian/rules.defs 2017-11-20 12:59:25.0 +0100 +++ b

[DNG] openrc-init: Was Re: Please provide systemd-free libreswan package

On Sat, 2017-11-18 at 01:51 -0500, Steve Litt wrote: > On Fri, 17 Nov 2017 08:42:51 -0500 > "Ismael L. Donis Garcia" wrote: > > > But I understand that the new versions of openrc already bring the  > > possibility of functioning as an init system independently. > > > > In

[DNG] openrc init: Was Re: Please provide systemd-free libreswan package

On Fri, 2017-11-17 at 08:42 -0500, Ismael L. Donis Garcia wrote: > But I understand that the new versions of openrc already bring the  > possibility of functioning as an init system independently. > > In that case, openrc could not be used as an alternative init? Yes, openrc is now able to be

Re: SIGILL problems with Hurd port of GO in gcc-8, and rpctrace bugs.

On Thu, 2017-11-16 at 17:59 -0500, Brent W. Baccala wrote: > On Thu, Nov 16, 2017 at 5:55 PM, Svante Signell <svante.signell@gmail > .com> wrote: > > > Perhaps you could try those patches and see if they fix your > > problem?  If not, > > > then it's someth

Re: SIGILL problems with Hurd port of GO in gcc-8, and rpctrace bugs.

On Thu, 2017-11-16 at 12:25 -0500, Brent W. Baccala wrote: > On Wed, Nov 15, 2017 at 11:53 AM, Svante Signell <svante.sign...@gmail.com> > wrote: > > Has rpctrace been thoroughly tested on multi-thread applications? > > Please, give feedback on this if you have p

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Thu, 2017-11-16 at 14:12 +0100, Svante Signell wrote: > On Wed, 2017-11-15 at 21:54 +0100, Svante Signell wrote: > > > > Attached is an updated patch for gcc-7. An updated patch for gcc-8 will follow > shortly when I have build tested gcc-8 go on both Linux and Hurd. >

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Thu, 2017-11-16 at 14:12 +0100, Svante Signell wrote: > On Wed, 2017-11-15 at 21:54 +0100, Svante Signell wrote: > > > > Attached is an updated patch for gcc-7. An updated patch for gcc-8 will follow > shortly when I have build tested gcc-8 go on both Linux and Hurd. >

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Thu, 2017-11-16 at 14:12 +0100, Svante Signell wrote: > On Wed, 2017-11-15 at 21:54 +0100, Svante Signell wrote: > > > > Attached is an updated patch for gcc-7. An updated patch for gcc-8 will follow > shortly when I have build tested gcc-8 go on both Linux and Hurd. >

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Wed, 2017-11-15 at 21:54 +0100, Svante Signell wrote: > On Wed, 2017-11-15 at 21:40 +0100, Matthias Klose wrote: > > On 06.11.2017 16:36, Svante Signell wrote: > > > Hi, > > > > > > Attached are patches to enable gccgo to build properly on Debian

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Wed, 2017-11-15 at 21:54 +0100, Svante Signell wrote: > On Wed, 2017-11-15 at 21:40 +0100, Matthias Klose wrote: > > On 06.11.2017 16:36, Svante Signell wrote: > > > Hi, > > > > > > Attached are patches to enable gccgo to build properly on Debian

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Wed, 2017-11-15 at 21:54 +0100, Svante Signell wrote: > On Wed, 2017-11-15 at 21:40 +0100, Matthias Klose wrote: > > On 06.11.2017 16:36, Svante Signell wrote: > > > Hi, > > > > > > Attached are patches to enable gccgo to build properly on Debian

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Wed, 2017-11-15 at 21:40 +0100, Matthias Klose wrote: > On 06.11.2017 16:36, Svante Signell wrote: > > Hi, > > > > Attached are patches to enable gccgo to build properly on Debian > > GNU/Hurd on gcc-7 (7-7.2.0-12). > > sysinfo.go:6744:7: error: redefinition

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Wed, 2017-11-15 at 21:40 +0100, Matthias Klose wrote: > On 06.11.2017 16:36, Svante Signell wrote: > > Hi, > > > > Attached are patches to enable gccgo to build properly on Debian > > GNU/Hurd on gcc-7 (7-7.2.0-12). > > sysinfo.go:6744:7: error: redefinition

Re: Hurd port for gcc-7 go PATCH 1-3(15)

On Wed, 2017-11-15 at 21:40 +0100, Matthias Klose wrote: > On 06.11.2017 16:36, Svante Signell wrote: > > Hi, > > > > Attached are patches to enable gccgo to build properly on Debian > > GNU/Hurd on gcc-7 (7-7.2.0-12). > > sysinfo.go:6744:7: error: redefinition

SIGILL problems with Hurd port of GO in gcc-8, and rpctrace bugs.

Hi, It seems like the Hurd port of GO will be available in next upload of gcc-8. I've put some go code/debug info/printouts from a failing test at: http://darnasus.sceen.net/~gnu_srs/gccgo-8/index0_tests/ The only difference between the OK and nOK cases is the number of arrays. There seems to be

Bug#881569: gdb: FTBFS on hurd-i386

Source: gdb Version: 8.0-1 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd, experimental Hi, gdb FTBFS on GNU/Hurd due to three reasons: - Usage of PATH_MAX in gdb/remote.c - Recent changes in Hurd failing the build of gdb/gnu-nat.c - A name clash of struct

Re: [DNG] Documentation format philosophies

On Sat, 2017-11-11 at 13:33 -0500, Steve Litt wrote: > > >  We use LaTEX in technical documents,  > > LaTeX is wonderful *for what it does*, which is make beautifully > typeset documents whose linefeeds are determined at compile time, not > at read time (like ePub, HTML or Xhtml). The problem is

Hurd port for gcc-8 go PATCH 11-15(15)

* add-gnu-to-libgo-headers.diff: Add gnu to libgo headers for build. * add-gnu-to-libgo-test-headers.diff: Add gnu to libgo headers for tests. * src_libgo_go_go_build_syslist.go.diff: Add gnu to the goosList. * src_libgo_go_syscall_syscall_gnu_test.go.diff: gnu-specific file for tests involving

Hurd port for gcc-8 go PATCH 11-15(15)

* add-gnu-to-libgo-headers.diff: Add gnu to libgo headers for build. * add-gnu-to-libgo-test-headers.diff: Add gnu to libgo headers for tests. * src_libgo_go_go_build_syslist.go.diff: Add gnu to the goosList. * src_libgo_go_syscall_syscall_gnu_test.go.diff: gnu-specific file for tests involving

Hurd port for gcc-8 go PATCH 11-15(15)

* add-gnu-to-libgo-headers.diff: Add gnu to libgo headers for build. * add-gnu-to-libgo-test-headers.diff: Add gnu to libgo headers for tests. * src_libgo_go_go_build_syslist.go.diff: Add gnu to the goosList. * src_libgo_go_syscall_syscall_gnu_test.go.diff: gnu-specific file for tests involving

Hurd port for gcc-8 go PATCH 4-10(15)

* src_libgo_build.diff: configure.ac, Makefile.* and shell script patches. * src_libgo_go_crypto.diff: Certificate go files. * src_libgo_go_net.diff: OS-specific net go files. * src_libgo_go_os.diff: OS-specific os go files. * src_libgo_go_runtime.diff: OS-specific runtime go files. *

Hurd port for gcc-8 go PATCH 4-10(15)

* src_libgo_build.diff: configure.ac, Makefile.* and shell script patches. * src_libgo_go_crypto.diff: Certificate go files. * src_libgo_go_net.diff: OS-specific net go files. * src_libgo_go_os.diff: OS-specific os go files. * src_libgo_go_runtime.diff: OS-specific runtime go files. *

Hurd port for gcc-8 go PATCH 4-10(15)

* src_libgo_build.diff: configure.ac, Makefile.* and shell script patches. * src_libgo_go_crypto.diff: Certificate go files. * src_libgo_go_net.diff: OS-specific net go files. * src_libgo_go_os.diff: OS-specific os go files. * src_libgo_go_runtime.diff: OS-specific runtime go files. *

Hurd port for gcc-8 go PATCH 1-3(15)

Hi, Attached are patches to enable gccgo to build properly on Debian GNU/Hurd on gcc-8 (8-8-20171108-1). The first two patches are Debian-specific: Enable build of gccgo for GNU/Hurd: * debian_rules.defs.diff Define patches for the generated series file: * debian_rules.patch.diff The third

Hurd port for gcc-8 go PATCH 1-3(15)

Hi, Attached are patches to enable gccgo to build properly on Debian GNU/Hurd on gcc-8 (8-8-20171108-1). The first two patches are Debian-specific: Enable build of gccgo for GNU/Hurd: * debian_rules.defs.diff Define patches for the generated series file: * debian_rules.patch.diff The third

Hurd port for gcc-8 go PATCH 1-3(15)

Hi, Attached are patches to enable gccgo to build properly on Debian GNU/Hurd on gcc-8 (8-8-20171108-1). The first two patches are Debian-specific: Enable build of gccgo for GNU/Hurd: * debian_rules.defs.diff Define patches for the generated series file: * debian_rules.patch.diff The third

Hurd port for gcc-7 go PATCH 11-15(15)

* add-gnu-to-libgo-headers.diff: Add gnu to libgo headers for build. * add-gnu-to-libgo-test-headers.diff: Add gnu to libgo headers for tests. * src_libgo_go_go_build_syslist.go.diff: Add gnu to the goosList. * src_libgo_go_syscall_syscall_gnu_test.go.diff: gnu-specific file for tests involving

Hurd port for gcc-7 go PATCH 11-15(15)

* add-gnu-to-libgo-headers.diff: Add gnu to libgo headers for build. * add-gnu-to-libgo-test-headers.diff: Add gnu to libgo headers for tests. * src_libgo_go_go_build_syslist.go.diff: Add gnu to the goosList. * src_libgo_go_syscall_syscall_gnu_test.go.diff: gnu-specific file for tests involving

Hurd port for gcc-7 go PATCH 11-15(15)

* add-gnu-to-libgo-headers.diff: Add gnu to libgo headers for build. * add-gnu-to-libgo-test-headers.diff: Add gnu to libgo headers for tests. * src_libgo_go_go_build_syslist.go.diff: Add gnu to the goosList. * src_libgo_go_syscall_syscall_gnu_test.go.diff: gnu-specific file for tests involving

Hurd port for gcc-7 go PATCH 4-10(15)

* src_libgo_build.diff: configure.ac, Makefile.* and shell script patches. * src_libgo_go_crypto.diff: Certificate go files. * src_libgo_go_net.diff: OS-specific net go files. * src_libgo_go_os.diff: OS-specific os go files. * src_libgo_go_runtime.diff: OS-specific runtime go files. *

Hurd port for gcc-7 go PATCH 4-10(15)

* src_libgo_build.diff: configure.ac, Makefile.* and shell script patches. * src_libgo_go_crypto.diff: Certificate go files. * src_libgo_go_net.diff: OS-specific net go files. * src_libgo_go_os.diff: OS-specific os go files. * src_libgo_go_runtime.diff: OS-specific runtime go files. *

Hurd port for gcc-7 go PATCH 4-10(15)

* src_libgo_build.diff: configure.ac, Makefile.* and shell script patches. * src_libgo_go_crypto.diff: Certificate go files. * src_libgo_go_net.diff: OS-specific net go files. * src_libgo_go_os.diff: OS-specific os go files. * src_libgo_go_runtime.diff: OS-specific runtime go files. *

Hurd port for gcc-7 go PATCH 1-3(15)

Hi, Attached are patches to enable gccgo to build properly on Debian GNU/Hurd on gcc-7 (7-7.2.0-12). The first two patches are Debian-specific: Enable build of gccgo for GNU/Hurd: * debian_rules.defs.diff Define patches for the generated series file: * debian_rules.patch.diff The third enables

Hurd port for gcc-7 go PATCH 1-3(15)

Hi, Attached are patches to enable gccgo to build properly on Debian GNU/Hurd on gcc-7 (7-7.2.0-12). The first two patches are Debian-specific: Enable build of gccgo for GNU/Hurd: * debian_rules.defs.diff Define patches for the generated series file: * debian_rules.patch.diff The third enables

Hurd port for gcc-7 go PATCH 1-3(15)

Hi, Attached are patches to enable gccgo to build properly on Debian GNU/Hurd on gcc-7 (7-7.2.0-12). The first two patches are Debian-specific: Enable build of gccgo for GNU/Hurd: * debian_rules.defs.diff Define patches for the generated series file: * debian_rules.patch.diff The third enables

Re: [DNG] Fresh install of Ascii (was Re: Redhat CEO answers questions)

On Wed, 2017-11-01 at 17:06 +0200, Lars Noodén wrote: > On 11/01/2017 05:04 PM, Juergen Moebius wrote: > > it is possible to install a fresh "full" copy of ascii, not an update? > > I neverless updated my systems, sorry. A new installation is allways > > the better way for my. > > Not yet.  

Re: Switching to sysvinit-core fails miserably in buster/sid

On Wed, 2017-10-25 at 18:03 +, Felipe Sateler wrote: > Mea Culpa. This was a bug in the "defaults-disabled" implementation. I  > have just uploaded a fixed version. Hi, when trying to follow which patches are applied to sysvinit, the git link given in the package page, 

Re: Unsustainable debian/rules as official build entry point?

On Wed, 2017-10-18 at 16:31 +0100, Wookey wrote: > On 2017-10-18 12:08 +, Felipe Sateler wrote: > I quite often use the debian/rules binary{-arch,-indep} interface when > doing porting/bootstrapping work (i.e the package built but something > goes wrong in the packaging process so I want to

Re: Unsustainable debian/rules as official build entry point?

On Wed, 2017-10-18 at 11:54 +0100, Simon McVittie wrote: > On Wed, 18 Oct 2017 at 11:57:55 +0200, Svante Signell wrote: > > Building some packages for GNU/Hurd has been impossible in the > > past, since also tests are run under fakeroot. > > Is there some reason why this w

Re: Unsustainable debian/rules as official build entry point?

On Wed, 2017-10-18 at 11:36 +0200, Guillem Jover wrote: > Hi! > > So, dpkg 1.19.0 and 1.19.0.1 had a bug where the build target was not > being called when building packages. Thanks, this problem has finally been revealed officially. Are you sure this problem is not older than version 1.19.x? 

Bug#858995: wget: FTBFS on hurd-i386

Cc: debian-hurd Another ping, almost two months later. On Sun, 2017-08-27 at 10:30 +0200, Svante Signell wrote: > found 858995 1.19.1-4 > thanks > > ping again > > The upstream patch has already been added to grep and findutils > (#867120). >

Re: wget: FTBFS on hurd-i386

Cc: debian-hurd Another ping, almost two months later. On Sun, 2017-08-27 at 10:30 +0200, Svante Signell wrote: > found 858995 1.19.1-4 > thanks > > ping again > > The upstream patch has already been added to grep and findutils > (#867120). >

Re: [DNG] Upgrade to ascii not possible?

On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote: > On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote: > > Hello, > > > > I've stuck on upgrading to ascii as there is no init-system-helpers > > available. > > Is there any solution? > > > > I see it in ascii main repo. What error message are

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Wed, 2017-09-27 at 17:56 +0200, Samuel Thibault wrote: > Samuel Thibault, on mer. 27 sept. 2017 14:53:18 +0200, wrote: > > Svante Signell, on mer. 27 sept. 2017 11:43:34 +0200, wrote: > > > What else did you find? > > > > That was mostly that, exactly :) &

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Tue, 2017-09-26 at 22:07 +0200, Samuel Thibault wrote: > Hello, > > This time it looks correct :) > > (just a couple of nitpicks which I'll just fix). I saw that I forgot to free (cwd) immediately in execve.c. Do you want an updated patch? Additionally I wrote in spawni.c: /* Absolute path

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Tue, 2017-09-26 at 16:24 +0200, Samuel Thibault wrote: > That should be “filename” instead of “file”. Yes of course. That was merely a copy/paste error. Thanks for finding it. > Take the case of PATH containing e.g. :bin: , and your current directory > contains a bin directory which contains

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Mon, 2017-09-25 at 18:01 +0200, Samuel Thibault wrote: > Svante Signell, on lun. 25 sept. 2017 17:51:52 +0200, wrote: > > The following tests still reveal unwanted behaviour: (where to change ?) These two tests are now OK. > It's in the PATH lookup case, just below where you add

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Sun, 2017-09-24 at 15:58 +0200, Svante Signell wrote: > On Sun, 2017-09-24 at 15:22 +0200, Samuel Thibault wrote: > > Hello, > > > > Svante Signell, on dim. 24 sept. 2017 15:17:02 +0200, wrote: > > > On Fri, 2017-09-22 at 20:27 +0200, Samuel Thibault wrote: >

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Sun, 2017-09-24 at 15:22 +0200, Samuel Thibault wrote: > Hello, > > Svante Signell, on dim. 24 sept. 2017 15:17:02 +0200, wrote: > > On Fri, 2017-09-22 at 20:27 +0200, Samuel Thibault wrote: > I however realize: we of course need the same for spawni() (using > getcwd

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Fri, 2017-09-22 at 20:27 +0200, Samuel Thibault wrote: > Hello, > > > +  file_t file = __file_name_lookup (file_name, O_EXEC, 0); > > This creates a file_t, so return paths have to deallocate it (just > like it is done at the end of the function). Fixed. > Along the way, you could move the

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Thu, 2017-09-21 at 14:46 +0200, Samuel Thibault wrote: > Svante Signell, on jeu. 21 sept. 2017 10:11:42 +0200, wrote: > > Sorry. Now I've built glibc successfully. > > Should this warning be fixed with a cast too? > > Casting is almost never the right solution. > &g

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Thu, 2017-09-21 at 09:39 +0200, Svante Signell wrote: > On Thu, 2017-09-21 at 01:01 +0200, Samuel Thibault wrote: > > Svante Signell, on mer. 20 sept. 2017 08:46:49 +0200, wrote: > > > I changed the patch for __execve() to keep file_name if the path is > > > ab

Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

On Thu, 2017-09-21 at 01:01 +0200, Samuel Thibault wrote: > Svante Signell, on mer. 20 sept. 2017 08:46:49 +0200, wrote: > > I changed the patch for __execve() to keep file_name if the path is absolute > > and > > call realpath() for relative paths. > > But then if y

Re: [DNG] Systemd-free => Gnome-free? [Was: Re: Gnome?

On Wed, 2017-09-20 at 17:41 +1000, Erik Christiansen wrote: > On 19.09.17 15:56, J. Fahrner wrote: > > I'm wondering why people cry when they don't get Gnome and why they try to > > And that's not possible for Gnome, because Gnome depends on systemd. > > If you want Gnome you have to live with

<    4   5   6   7   8   9   10   11   12   13   >