On Fri, 2019-10-18 at 23:37 +0800, Shengjing Zhu wrote:
> On Fri, Oct 18, 2019 at 2:38 PM Samuel Thibault > wrote:
> > Hello,
> >
> > Shengjing Zhu, le ven. 18 oct. 2019 13:26:58 +0800, a ecrit:
> > > When calling open(fifo_fd, O_WRONLY | O_NONBLOCK) on an fifo
> > > file, which has
> > > no
On Wed, 2019-10-16 at 18:16 -0400, Alfred M. Szmidt wrote:
> Thats the meaning of vendor lock-in.
Dear Alfred, can't we just agree that we disagree?
On Mon, 2019-10-14 at 22:41 -0400, Richard Stallman wrote:
>
> If systemD is be hard to replace, that is a kind of lock-in. But it
> isn't _vendor_ lock-in. systemD, like most free software packages,
> is not tied to any particular vendor. Indeed, the usual concept of
> "vendor" for free
On Mon, 2019-10-14 at 22:41 -0400, Richard Stallman wrote:
>
> If systemD is be hard to replace, that is a kind of lock-in. But it
> isn't _vendor_ lock-in. systemD, like most free software packages,
> is not tied to any particular vendor. Indeed, the usual concept of
> "vendor" for free
On Mon, 2019-10-14 at 12:13 -0400, Paul Smith wrote:
> On Mon, 2019-10-14 at 12:07 +0200, Svante Signell wrote:
> > Perhaps we should divide free software into two groups: 1) Really
> > free software where Freedom 1 applies and 2) not-so-free software
> > where Freedom 1 d
On Mon, 2019-10-14 at 12:13 -0400, Paul Smith wrote:
> On Mon, 2019-10-14 at 12:07 +0200, Svante Signell wrote:
> > Perhaps we should divide free software into two groups: 1) Really
> > free software where Freedom 1 applies and 2) not-so-free software
> > where Freedom 1 d
On Sun, 2019-10-13 at 21:44 -0400, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider]]]
> [[[ whether defending the US Constitution against all enemies,]]]
> [[[ foreign or domestic, requires you to follow Snowden's example.]]]
>
> Indeed,
On Sun, 2019-10-13 at 21:44 -0400, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider]]]
> [[[ whether defending the US Constitution against all enemies,]]]
> [[[ foreign or domestic, requires you to follow Snowden's example.]]]
>
> Indeed,
On Fri, 2019-10-11 at 03:11 +0530, Arun Isaac wrote:
> > For what it is worth, I have some personal answers to some of these
> > questions here:
> >
> > https://wingolog.org/archives/2019/10/08/thoughts-on-rms-and-gnu
>
> I largely agree with the thoughts you have expressed in this blog
>
On Thu, 2019-10-10 at 16:32 +0200, Ludovic Courtès wrote:
> Hi!
>
> Mathieu, I guess you can go ahead and rename ‘core-updates-next’ to
> ‘core-updates’ if nobody’s done it yet.
>
> Let’s get the ball rolling!
What's the status of the GNU/Hurd port with this core-updates release,
better or
On Thu, 2019-10-10 at 19:22 +, Jean Louis wrote:
>
>
> > Your problem is that you published this statement to guix-devel. If
> > you don't mind, I'll forward your mail to gnu-system-discuss, which
> > is the appropriate mailing list.
>
> I don't mind.
Sorry Jean Louis, I was addressing
On Thu, 2019-10-10 at 19:22 +, Jean Louis wrote:
>
>
> > Your problem is that you published this statement to guix-devel. If
> > you don't mind, I'll forward your mail to gnu-system-discuss, which
> > is the appropriate mailing list.
>
> I don't mind.
Sorry Jean Louis, I was addressing
On Thu, 2019-10-10 at 16:29 +0200, Ludovic Courtès wrote:
> Hi Jean-Louis,
> You’ve made your point now; I see you’ve even set up a web page to
> collect hatred messages against me.
>
> I ask you to stop using the Guix mailing lists for this now. I will
> propose to the Guix maintainers to put
On Thu, 2019-10-10 at 16:29 +0200, Ludovic Courtès wrote:
> Hi Jean-Louis,
> You’ve made your point now; I see you’ve even set up a web page to
> collect hatred messages against me.
>
> I ask you to stop using the Guix mailing lists for this now. I will
> propose to the Guix maintainers to put
Dear Guix, and other people signing that statement.
cc: RMS
I do also have problems with your campaign against RMS. Publishing such
a statement as a blog entry for Guix is very inappropriate. Especially
in the context of the recent defaming campaign on him personally on
social media, making him
On Sun, 2019-09-22 at 10:45 +0200, Svante Signell wrote:
>
> > Replacing the cross-built versions with dynamically built native versions of
> > xz
> > and guile-2.0, I did come further, but need help interpreting the log file,
> > attached: make-boot0-4.2.1.drv.gz. Wher
retitle 765971 ITP: eudev -- udev fork, independent of systemd trunk.
owner 765971 !
thanks
This package is already packaged by Devuan, and as so the Debian version will
get an +debian1 extension. Current Devuan version is 3.2.7-6 from Feb 9, 2019.
Latest upstream version is 3.2.8 from May 20,
retitle 765971 ITP: eudev -- udev fork, independent of systemd trunk.
owner 765971 !
thanks
This package is already packaged by Devuan, and as so the Debian version will
get an +debian1 extension. Current Devuan version is 3.2.7-6 from Feb 9, 2019.
Latest upstream version is 3.2.8 from May 20,
On Sat, 2019-09-21 at 18:47 +0200, Svante Signell wrote:
> On Sat, 2019-09-21 at 13:26 +0200, Svante Signell wrote:
>
> > Extracting bash, mkdir, tar, xz and guile and run them with --version shows
> > that at least xz and guile are corrupt:
> >
> > gnu/packages/b
On Sat, 2019-09-21 at 13:26 +0200, Svante Signell wrote:
> Extracting bash, mkdir, tar, xz and guile and run them with --version shows
> that at least xz and guile are corrupt:
>
> gnu/packages/bootstrap/i586-gnu/xz --version
> gnu/packages/bootstrap/i586-gnu/xz: Error creating a
On Fri, 2019-09-20 at 21:12 +0200, Jonathan Brielmaier wrote:
> On 20.09.19 20:48, Svante Signell wrote:
> If I got your situation correctly you need to do the following steps.
>
> 1. Obtain the guix git repo
> git clone https://git.savannah.gnu.org/git/guix.git
> cd guix/
>
On Sat, 2019-09-21 at 00:18 +0200, Ricardo Wurmus wrote:
> Svante Signell writes:
>
> > ./pre-inst-env guix build --target=i586-pc-gnu bootstrap-tarballs 2>&1 | tee
> > ../bootstrap-tarballs-i586-pc-gnu.log
> >
> > Build took around two days, and the l
On Fri, 2019-09-20 at 19:49 +0200, Svante Signell wrote:
> On Fri, 2019-09-20 at 19:03 +0200, Ricardo Wurmus wrote:
> > Svante Signell writes:
> >
> > > On a GNU/Linux amd64 qemu image:
> > >
> > >
> > > dpkg -S /usr/share/guile/site/2.2
>
On Fri, 2019-09-20 at 19:03 +0200, Ricardo Wurmus wrote:
> Svante Signell writes:
>
> > On a GNU/Linux amd64 qemu image:
> >
> >
> > dpkg -S /usr/share/guile/site/2.2
> > guile-sqlite3, guile-gcrypt, guile-bytestructures, guile-ssh, guile-json:
> > /
On Tue, 2019-09-10 at 10:10 +0200, Svante Signell wrote:
> On Sun, 2019-09-08 at 22:55 +0200, Ludovic Courtès wrote:
> > Hi,
> >
> > Ricardo Wurmus skribis:
> >
> > > I believe the problem is in Guix, which lets the builds for i586-gnu use
> > > G
file:
hurd-i386/tg-WRLCK-upgrade.diff
Additionally the two upstream commits are reversed by:
revert-git-lockf-0.diff
revert-git-fcntl64.diff
If you are working with git these commits are more easily mage there.
Thanks!
sysdeps/mach/hurd/Changelog
2019-01-12 Svante Signell
* Update copyright
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
Signell
* file-lock.c: Make flock work regardless of the
mode in which the file was opened.
2019-02-12 Svante Signell
* file-lock.c: Comment out "Make flock work without R or W mode"
2019-02-01 Svante Signell
* Update copyright years.
* file-record-lock.c(diskfs_S_file_r
tags 935304 -wontfix
thanks
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
tags 935304 -wontfix
thanks
reopen 935304
found 935304 243-1
severity 935304 important
thanks
On Tue, 2019-09-10 at 11:10 +0200, Michael Biebl wrote:
> Am 10.09.19 um 11:03 schrieb Svante Signell:
> > severity 935304 important
> > thanks
> >
> > Michael: Next time you lower the importan
reopen 935304
found 935304 243-1
severity 935304 important
thanks
On Tue, 2019-09-10 at 11:10 +0200, Michael Biebl wrote:
> Am 10.09.19 um 11:03 schrieb Svante Signell:
> > severity 935304 important
> > thanks
> >
> > Michael: Next time you lower the importan
severity 935304 important
thanks
Michael: Next time you lower the importance of this bug, please give a
motivation. It is not especially instructive doing such a thing without
explaining why.
___
Pkg-systemd-maintainers mailing list
severity 935304 important
thanks
Michael: Next time you lower the importance of this bug, please give a
motivation. It is not especially instructive doing such a thing without
explaining why.
On Sun, 2019-09-08 at 22:55 +0200, Ludovic Courtès wrote:
> Hi,
>
> Ricardo Wurmus skribis:
>
> > I believe the problem is in Guix, which lets the builds for i586-gnu use
> > Guile 2.2, but generates scripts for Guile 2.0. We probably need to
> > change it use Guile 2.0 there as it is done for
On Wed, 2019-09-04 at 09:52 +0200, Ricardo Wurmus wrote:
> Svante Signell writes:
>
> > On Wed, 2019-09-04 at 06:31 +0200, Svante Signell wrote:
> > > unpacking bootstrap Guile to '/gnu/store/ncp3yhr6c38kqvgb8c967vnhly59yf1m-
> > > guile-bootstrap-2.0'...
>
On Wed, 2019-09-04 at 06:31 +0200, Svante Signell wrote:
>
> unpacking bootstrap Guile to '/gnu/store/ncp3yhr6c38kqvgb8c967vnhly59yf1m-
> guile-bootstrap-2.0'...
This stuff comes from gnu/packages/bootstrap.scm
#!~a
export GUILE_SYSTEM_PATH=~a/share/guile/2.0
export GUILE_SYSTEM_COMP
On Wed, 2019-09-04 at 00:01 +0200, Ricardo Wurmus wrote:
> Svante Signell writes:
>
> Did you copy this from Debian and moved it into the store? That’s a
> very bad idea.
Sorry, my fault. I was tired and worked on different boxes and Linux+Hurd VMs.
The status is now that .
On Tue, 2019-09-03 at 23:26 +0200, Ricardo Wurmus wrote:
>
> What are the contents of /gnu/store/alzim8hg6zqvs9s33frh7m9z211lryk3-
> bootstrap-binaries-0/bin/tar?
Something strange:
# ls -l /gnu/store/alzim8hg6zqvs9s33frh7m9z211lryk3-bootstrap-binaries-
0/bin/tar
-r-xr-xr-x 2 root root 445560
On Tue, 2019-09-03 at 16:34 +0200, Svante Signell wrote:
>
> > How can I rebuild from scratch to watch the output on the console?
Seems to be to wipe out /gnu/store and /var/{guix,log}
> This time bash crashed... Took a screen shot of the qemu console. I have to
> replace
On Tue, 2019-09-03 at 14:58 +0200, Ricardo Wurmus wrote:
> Hi Svante,
>
> This looks very much like the tar segfault I encountered when I last
> played with the Hurd port.
>
> My notes say this:
>
> --8<---cut here---start->8---
> - tar fails to run when
On Sun, 2019-09-01 at 20:01 +0200, Svante Signell wrote:
...
I think it is time to wrap up a little now on the Hurd port.
Attached are patches I made. Save for some indentation misses.
gnu_local.mk.diffguix_scripts_perform-download.scm.diff
gnu_packages_bootstrap.scm.diff
On Sun, 2019-09-01 at 15:28 +0200, Svante Signell wrote:
> On Sun, 2019-09-01 at 11:11 +0200, Svante Signell wrote:
> And btw: info guix speaks Spanish as default :( Must be a bug!
I've come a little further:
Extracting the files from the cross-built files "bash mkdir tar xz&q
On Sun, 2019-09-01 at 11:11 +0200, Svante Signell wrote:
> On Sat, 2019-08-31 at 19:27 +0200, Svante Signell wrote:
>
> I have some further guix/guile questions when building and running guix on
> GHU/Hurd natively
>
> On the GNU/Hurd image:
> download and unpack guix-1
On Sat, 2019-08-31 at 19:27 +0200, Svante Signell wrote:
I have some further guix/guile questions when building and running guix on
GHU/Hurd natively
On the GNU/Hurd image:
download and unpack guix-1.0.1.tar.gz
cd guix-1.0.1
1) When building guix from source
./configure --with-courage --prefix
On Sat, 2019-08-31 at 14:12 +0200, Ricardo Wurmus wrote:
> Svante Signell writes:
>
> >
> > which g++
> > /home/guest/.guix-profile/bin/g++
>
> This is not the GCC that’s used by Guix to build things. See also that
> during the build GCC 5.5.0 is used, no
On Sat, 2019-08-31 at 10:13 +0200, Julien Lepiller wrote:
> > On Sat, 2019-08-31 at 00:17 +0200, Ricardo Wurmus wrote:
> > > Svante Signell writes:
> > >
> > > > Sorry but the tarballs have files like ./bin/tar Where to unpack
> > them
On Sat, 2019-08-31 at 00:17 +0200, Ricardo Wurmus wrote:
> Svante Signell writes:
>
> > On Fri, 2019-08-30 at 23:30 +0200, Ricardo Wurmus wrote:
> > > Svante Signell writes:
> > >
> > > > Where to install the bootstrap-binaries: Natively in GNU/Hurd,
On Fri, 2019-08-30 at 23:30 +0200, Ricardo Wurmus wrote:
> Svante Signell writes:
>
> > Where to install the bootstrap-binaries: Natively in GNU/Hurd, which already
> > hase.g. /bin/tar from the tar package or within Guix on amd64? But
> > installing
> > tar to /bin
On Fri, 2019-08-30 at 20:25 +0200, Svante Signell wrote:
> On Fri, 2019-08-30 at 19:14 +0200, Julien Lepiller wrote:
> > > a écrit :
> > >
> > Thanks I'll try to install them. It seems like gcc is a little old, do
> > > you have
> > > notes somewhere o
On Fri, 2019-08-30 at 19:14 +0200, Julien Lepiller wrote:
> > a écrit :
> >
> Thanks I'll try to install them. It seems like gcc is a little old, do
> > you have
> > notes somewhere on how these cross-built packages were created?
>
> > I assume they can be built them within guix e.g. on
On Fri, 2019-08-30 at 01:36 +0200, Ricardo Wurmus wrote:
> Hi Svante,
>
> Here’s what I wrote about this on IRC:
>
> --8<---cut here---start->8---
> [12:36:12] gnu_srs: get a Debian GNU/Hurd, then build the Guix
> dependencies from source.
>
On Thu, 2019-08-29 at 21:25 +0200, Svante Signell wrote:
> Hello,
>
> After a lot of quirks I managed to get guix built natively on Debian
> GNU/Hurd. What to do next?
I managed to start the guix-daemon. Next seems to be the bootstrap
binaries:
guix build hello
guix build: error: co
Hello,
After a lot of quirks I managed to get guix built natively on Debian
GNU/Hurd. What to do next?
Thanks!
On Sun, 2019-08-25 at 21:40 +0200, Joan Lledó wrote:
> Hello,
>
> I'm working on the lwip debian package, when building, I found it
> fails
> on kfreebsd's boxes:
>
> https://buildd.debian.org/status/package.php?p=lwip
>
> I'd like to fix the problems, and for that I need to have a virtual
>
On Thu, 2019-08-22 at 17:01 -0400, Mark H Weaver wrote:
> Hi Svante,
>
> Svante Signell writes:
>
> It looks like this issue was already fixed in Guile 2.0.14, by commit
> f2764cb1031379c47a17c02fef3f8164a6ce9cda on the 'stable-2.0' branch:
>
>
> https://git.sava
Source: guile-2.0
Version: 2.0.13+1-5.1
Severity: important
Tags: ftbfs, patch, fixed-upstream
User: debian-h...@lists.debian.org
Usertags: hurd
Hello,
Currently guile-2.0 FTBFS on GNU/Hurd due to one test failing. The
attached upstream patch, renamed to 0006-fix-hurd-statprof-test.patch
fixes
--- Begin Message ---
Ping!
On Thu, 2019-08-15 at 14:29 +0200, Svante Signell wrote:
> Hello,
>
> When building Debian version 2.0.13+1-5.1 one test fails making the
> whole build to fail. The problem is in the file test-
> suite/tests/statprof.test. According to that f
Source: graphite2
Version: 1.3.13-7
Severity: important
Tags: ftbfs, patch
User: debian-h...@lists.debian.org
Usertags: hurd
Hello,
Currently graphite2 FTBFS on GNU/Hurd due to one failing test
awamicmp3. The attached patch tests_CMakeLists.txt.diff omits that test
for Hurd printing a warning
Source: graphite2
Version: 1.3.13-7
Severity: important
Tags: ftbfs, patch
User: debian-h...@lists.debian.org
Usertags: hurd
Hello,
Currently graphite2 FTBFS on GNU/Hurd due to one failing test
awamicmp3. The attached patch tests_CMakeLists.txt.diff omits that test
for Hurd printing a warning
Hello,
When building Debian version 2.0.13+1-5.1 one test fails making the
whole build to fail. The problem is in the file test-
suite/tests/statprof.test. According to that file it is known that
ITIMER_PROF is not implemented:
;; Throw `unresolved' upon ENOSYS. This is used to skip tests on
;;
On Mon, 2019-08-12 at 23:56 +0200, Samuel Thibault wrote:
> Samuel Thibault, le lun. 12 août 2019 23:50:22 +0200, a ecrit:
> > Svante Signell, le lun. 12 août 2019 23:08:10 +0200, a ecrit:
> > > On Mon, 2019-08-12 at 20:34 +0200, Samuel Thibault wrote:
> > > What ab
On Mon, 2019-08-12 at 20:34 +0200, Samuel Thibault wrote:
>
> Since the arch:all packages shared with the linux ports come into
> play, one sometimes have to juggle a bit indeed. Usually the packages
> coming from unreleased are meant to fix things, so better rather try
> them as suggested above:
Source: aom
Version: 1.0.0-3
Severity: important
Tags: ftbfs, patch
User: debian-k...@lists.debian.org
Usertags: kfreebsd
Hello,
Currently aom FTBFS on GNU/kFreeBSD due to missing port to that
architecture. The attached patches fixes that problem.
The the patches
Source: aom
Version: 1.0.0-3
Severity: important
Tags: ftbfs, patch
User: debian-k...@lists.debian.org
Usertags: kfreebsd
Hello,
Currently aom FTBFS on GNU/kFreeBSD due to missing port to that
architecture. The attached patches fixes that problem.
The the patches
Hello,
Due to that the patch for polickit-1 in #923420 is not applied no
working desktop is possible w/o installing systemd (via libpam-systemd)
as pid 1. This effectively excludes usage of other init systems for
desktop usage. Please explain your decision on why desktops for other
init systems
Hello,
Due to that the patch for polickit-1 in #923420 is not applied no
working desktop is possible w/o installing systemd (via libpam-systemd)
as pid 1. This effectively excludes usage of other init systems for
desktop usage. Please explain your decision on why desktops for other
init systems
Hello,
Due to that the patch for polickit-1 in #923420 is not applied no
working desktop is possible w/o installing systemd (via libpam-systemd)
as pid 1. This effectively excludes usage of other init systems for
desktop usage. Please explain your decision on why desktops for other
init systems
On Fri, 2019-08-09 at 12:06 +0100, Jonathan Wiltshire wrote:
> On Fri, Aug 09, 2019 at 12:55:02PM +0200, Svante Signell wrote:
> > On Fri, 2019-08-09 at 11:41 +0100, Adam D. Barratt wrote:
> > > Control: severity -1 normal
> > >
> > > On 2019-08-09 11:
On Fri, 2019-08-09 at 12:06 +0100, Jonathan Wiltshire wrote:
> On Fri, Aug 09, 2019 at 12:55:02PM +0200, Svante Signell wrote:
> > On Fri, 2019-08-09 at 11:41 +0100, Adam D. Barratt wrote:
> > > Control: severity -1 normal
> > >
> > > On 2019-08-09 11:
On Fri, 2019-08-09 at 11:41 +0100, Adam D. Barratt wrote:
> Control: severity -1 normal
>
> On 2019-08-09 11:33, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> > > severity 934132 important
> > Bug #934132 [release.debian.org] unblock:
On Fri, 2019-08-09 at 11:41 +0100, Adam D. Barratt wrote:
> Control: severity -1 normal
>
> On 2019-08-09 11:33, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> > > severity 934132 important
> > Bug #934132 [release.debian.org] unblock:
Source: gimp
Version: 2.10.8-2
Severity: important
Tags: ftbfs, patch
User: debian-h...@lists.debian.org
Usertags: hurd
Hello,
Currently gimp FTBFS on GNU/Hurd due to a new PATH_MAX issue. The
attached patch fixes that problem.
Maybe both hurd-specific patches should be submitted upstream, even
On Fri, 2019-08-02 at 02:33 +0200, Samuel Thibault wrote:
> Hello,
>
> Matthias Klose, le lun. 08 juil. 2019 13:37:00 +0200, a ecrit:
> > The hurd-i386 and kfreebsd-* builds had some missing symbols, seen
> > in ...
> Here is a mach implementation for the native thread ids, and the
> patch to
On Fri, 2019-08-02 at 02:33 +0200, Samuel Thibault wrote:
> Hello,
>
> Matthias Klose, le lun. 08 juil. 2019 13:37:00 +0200, a ecrit:
> > The hurd-i386 and kfreebsd-* builds had some missing symbols, seen
> > in ...
> Here is a mach implementation for the native thread ids, and the
> patch to
Source: sysvinit
Version: 2.95-3
Severity: important
Tags: ftbfs, patch
User: debian-k...@lists.debian.org
Usertags: kfreebsd
Hello,
Currently sysvinit FTBFS on GNU/kFreeBSD due to that c_line is not a
member of struct termios for that architecture. The attached patch
fixes that problem.
(Even
On Thu, 2019-06-27 at 18:05 +0200, Ludovic Courtès wrote:
> Hello Guix!
>
> People rightfully suggested having some sort of a roadmap for what’s
> next. Many of us certainly have specific ideas in mind, but having
> that written down can certainly clarify what this project is about to
>
On Wed, 2019-06-26 at 12:14 -0300, elementar wrote:
> Where do I find kFreeBSD-amd64 isos, from testing or unstable?
>
> Em sex, 12 de abr de 2019 17:49, Joerg Jaspert
> escreveu:
> > Hi
> >
> > back in August 2018 we discussed architecture inclusion into
> > unstable/experimental.
> >
> >
On Wed, 2019-06-26 at 12:14 -0300, elementar wrote:
> Where do I find kFreeBSD-amd64 isos, from testing or unstable?
>
> Em sex, 12 de abr de 2019 17:49, Joerg Jaspert
> escreveu:
> > Hi
> >
> > back in August 2018 we discussed architecture inclusion into
> > unstable/experimental.
> >
> >
On Wed, 2019-06-26 at 12:14 -0300, elementar wrote:
> Where do I find kFreeBSD-amd64 isos, from testing or unstable?
>
> Em sex, 12 de abr de 2019 17:49, Joerg Jaspert
> escreveu:
> > Hi
> >
> > back in August 2018 we discussed architecture inclusion into
> > unstable/experimental.
> >
> >
On Tue, 2019-04-23 at 09:10 +0200, Jaromil wrote:
> On Mon, 22 Apr 2019, Rick Moen wrote:
>
> > Dan, it is _not_ time for you to leave. Please stay.
>
> Well Rick, at this point considering all the dust Dan is kicking up
> in
> public, apparently now intentionally, I'd say he better leave. All
On Mon, 2019-04-22 at 19:53 +0200, Samuel Thibault wrote:
> Samuel Thibault, le lun. 22 avril 2019 19:37:35 +0200, a ecrit:
> > with the following sources.list entries:
> >
> > deb http://ftp.ports.debian.org/debian-ports sid main
> > deb http://ftp.ports.debian.org/debian-ports experimental main
On Sun, 2019-04-14 at 11:33 +0200, Samuel Thibault wrote:
> Svante Signell, le dim. 14 avril 2019 10:52:19 +0200, a ecrit:
> >
> > I cannot follow your reasoning here, e.g. at
> > http://ftp.ports.debian.org/debian-ports/pool-hurd-i386/main/g/glibc/
> > there are no s
On Sun, 2019-04-14 at 11:33 +0200, Samuel Thibault wrote:
> Svante Signell, le dim. 14 avril 2019 10:52:19 +0200, a ecrit:
> >
> > I cannot follow your reasoning here, e.g. at
> > http://ftp.ports.debian.org/debian-ports/pool-hurd-i386/main/g/glibc/
> > there are no s
On Sat, 2019-04-13 at 21:03 +, Rene wrote:
> Hello,
>
> Only to share the status of the tests I have done:
>
> * Currently I run Guix (v0.14.0) on Debian/Hurd which takes
> approximately 2 days to compile and generate the Hurd binaries
> through `guix system init ..`.
>
> * There are some
On Sun, 2019-04-14 at 10:29 +0200, Samuel Thibault wrote:
> Svante Signell, le dim. 14 avril 2019 10:23:42 +0200, a ecrit:
> > One problem with debian-ports is that the sources, most interesting
> > the
> > *.debian.tar.* files. You cannot any longer add deb-src to the
> &g
On Sun, 2019-04-14 at 10:29 +0200, Samuel Thibault wrote:
> Svante Signell, le dim. 14 avril 2019 10:23:42 +0200, a ecrit:
> > One problem with debian-ports is that the sources, most interesting
> > the
> > *.debian.tar.* files. You cannot any longer add deb-src to the
> &g
On Sat, 2019-04-13 at 12:59 +0200, Aurelien Jarno wrote:
> On 2019-04-13 12:37, Samuel Thibault wrote:
> > Hello,
> >
> > Before even thinking about uploading the hurd-i386 and kfreebsd
> > unstable/experimental packages to debian-ports, is there enough
> > disk space for this on it? It seems my
On Sat, 2019-04-13 at 12:59 +0200, Aurelien Jarno wrote:
> On 2019-04-13 12:37, Samuel Thibault wrote:
> > Hello,
> >
> > Before even thinking about uploading the hurd-i386 and kfreebsd
> > unstable/experimental packages to debian-ports, is there enough
> > disk space for this on it? It seems my
On Sat, 2019-04-13 at 12:18 +0200, Samuel Thibault wrote:
>
> He rightfully means he does not want patches, but patches getting
> submitted upstream, so he does not have to maintain them. A Debian
> package maintainer is not supposed to maintain patches long-term.
Then the question of which
On Sat, 2019-04-13 at 11:51 +0200, Carsten Schoenert wrote:
> Am 13.04.19 um 11:15 schrieb Svante Signell:
>
> > Please give up on Debian. They clearly have no interest in anything
> > non-linux or non-systemd, that is fully clear. Let's make a joint
> > effort to mak
Hello,
I've followed this list for some time now, but not subscribed until
now. I know Manolis Ragkousis has been working on making GNU/Hurd
running under Guix and Shepherd. What is the current status? How much
work is needed to be fully supported? And which are the current
problems?
What about
On Sat, 2019-04-13 at 10:58 +0200, Samuel Thibault wrote:
> Joerg Jaspert, le sam. 13 avril 2019 10:24:53 +0200, a ecrit:
> > On 15371 March 1977, Samuel Thibault wrote:
> >
>
> Well, it's very odd that a team decision is suddenly made with a
> two-week effect without asking whether the schedule
On Sat, 2019-04-13 at 10:58 +0200, Samuel Thibault wrote:
> Joerg Jaspert, le sam. 13 avril 2019 10:24:53 +0200, a ecrit:
> > On 15371 March 1977, Samuel Thibault wrote:
> >
>
> Well, it's very odd that a team decision is suddenly made with a
> two-week effect without asking whether the schedule
On Sat, 2019-04-13 at 10:58 +0200, Samuel Thibault wrote:
> Joerg Jaspert, le sam. 13 avril 2019 10:24:53 +0200, a ecrit:
> > On 15371 March 1977, Samuel Thibault wrote:
> >
>
> Well, it's very odd that a team decision is suddenly made with a
> two-week effect without asking whether the schedule
further, making Devuan extinct. Is that
> your goal?
Katolaz and CenturionDan, please continue with your work on Devuan. You should
all be able to agree and make sensible decicions in the very small caretakers
group. Behave as grown-ups, please.
On Thu, 2019-04-11 at 23:12 +0200, info at smallinn
On Thu, 2019-04-11 at 23:52 +0200, info at smallinnovations dot nl wrote:
> On 11-04-19 23:38, Daniel Reurich wrote:
> > > Have I missed something? I want Katolaz back.
> > > Who is CenturionDan? And why does he have that much power?
> > I am CenturionDan. I don't have any power over Devuan, and
Forwarding this mail to DNG too. I think this is relevant to the discussion.
Thanks!
--- Begin Message ---
On Thu, 2019-04-11 at 20:47 +0200, Jaromil wrote:
> dear devs
>
> for having caused the distress of trust within the caretakers group
> beyond our agreed liabilities (see licensing
On Tue, 2019-03-12 at 13:37 +0100, Sylvestre Ledru wrote:
> Hello,
>
> Le 03/02/2019 à 15:28, Svante Signell a écrit :
>
> > I will submit these patches to upstream too, in due time.
> Do you have an update about that?
>
> This is hard to maintain these patches (rebas
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
401 - 500 of 4854 matches
Mail list logo
