Updated patch, which assumes the libdebian-installer4-dev package will
not be renamed. Build-Depend on a recent enough version that provides
sha256 fields.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index d6682ca..20e33a0 100644
Updated patch, which assumes the libdebian-installer4-dev package will
not be renamed. Build-Depend on a recent enough version that provides
sha256 fields.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index d6682ca..20e33a0 100644
Updated patch, which assumes the libdebian-installer4-dev package will
not be renamed. Build-Depend on a recent enough version that provides
sha256 fields.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index d6682ca..20e33a0 100644
Steven Chamberlain wrote:
> replace sum[0] with sha256 and leave sum[1] empty;
> [...] (we would drop the MD5- and SHA1-parsing code
> and make absolutely sure nobody is still using those).
The new patch attached would do that, and it remains otherwise
ABI-compatible.
It aims to be
Steven Chamberlain wrote:
> replace sum[0] with sha256 and leave sum[1] empty;
> [...] (we would drop the MD5- and SHA1-parsing code
> and make absolutely sure nobody is still using those).
The new patch attached would do that, and it remains otherwise
ABI-compatible.
It aims to be
Steven Chamberlain wrote:
> replace sum[0] with sha256 and leave sum[1] empty;
> [...] (we would drop the MD5- and SHA1-parsing code
> and make absolutely sure nobody is still using those).
The new patch attached would do that, and it remains otherwise
ABI-compatible.
It aims to be
Thanks for your comments!
Cyril Brulebois wrote:
> Steven Chamberlain <ste...@pyro.eu.org> (2017-02-27):
> > (If we really wanted, we could maybe avoid the ABI bump: [...]
>
> Given the number of reverse dependencies, I doubt this is worth abusing
> md5 storage for sha256
Thanks for your comments!
Cyril Brulebois wrote:
> Steven Chamberlain <ste...@pyro.eu.org> (2017-02-27):
> > (If we really wanted, we could maybe avoid the ABI bump: [...]
>
> Given the number of reverse dependencies, I doubt this is worth abusing
> md5 storage for sha256
Thanks for your comments!
Cyril Brulebois wrote:
> Steven Chamberlain <ste...@pyro.eu.org> (2017-02-27):
> > (If we really wanted, we could maybe avoid the ABI bump: [...]
>
> Given the number of reverse dependencies, I doubt this is worth abusing
> md5 storage for sha256
which remains the same length). The
dynamically-sized buffer it points to, would change from storing an MD5
to a SHA256 hash, and would only cause a regression where something is
still trying to validate MD5).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/configure.ac b/configure.ac
which remains the same length). The
dynamically-sized buffer it points to, would change from storing an MD5
to a SHA256 hash, and would only cause a regression where something is
still trying to validate MD5).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/configure.ac b/configure.ac
which remains the same length). The
dynamically-sized buffer it points to, would change from storing an MD5
to a SHA256 hash, and would only cause a regression where something is
still trying to validate MD5).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/configure.ac b/configure.ac
o increase it if changing SHA256 to SHA512 in the future. A
more thorough rework of this code might store the hash type (as an enum)
and length, in the di_package struct instead.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
o increase it if changing SHA256 to SHA512 in the future. A
more thorough rework of this code might store the hash type (as an enum)
and length, in the di_package struct instead.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Steven Chamberlain wrote:
> Attached is [...]
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/anna.c b/anna.c
index 4b68816..e03d34a 100644
--- a/anna.c
+++ b/anna.c
@@ -318,8 +318,8 @@ install_modules(di_packages *status, di_packages *packa
Steven Chamberlain wrote:
> Attached is [...]
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/anna.c b/anna.c
index 4b68816..e03d34a 100644
--- a/anna.c
+++ b/anna.c
@@ -318,8 +318,8 @@ install_modules(di_packages *status, di_packages *packa
Steven Chamberlain wrote:
> Attached is [...]
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/anna.c b/anna.c
index 4b68816..e03d34a 100644
--- a/anna.c
+++ b/anna.c
@@ -318,8 +318,8 @@ install_modules(di_packages *status, di_packages *packa
o increase it if changing SHA256 to SHA512 in the future. A
more thorough rework of this code might store the hash type (as an enum)
and length, in the di_package struct instead.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
eeded
to change then.
In the ideal world, the code itself would be the clear, authoritative
reference of what it is doing. I wish that we can remove all references
to md5 and sha1 there.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
eeded
to change then.
In the ideal world, the code itself would be the clear, authoritative
reference of what it is doing. I wish that we can remove all references
to md5 and sha1 there.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
eeded
to change then.
In the ideal world, the code itself would be the clear, authoritative
reference of what it is doing. I wish that we can remove all references
to md5 and sha1 there.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
hed log.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
/usr/bin/sha256sum /tmp/net-retriever-1817-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/md5sum /var/cache/a
hed log.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
/usr/bin/sha256sum /tmp/net-retriever-1817-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/md5sum /var/cache/a
hed log.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
/usr/bin/sha256sum /tmp/net-retriever-1817-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/md5sum /var/cache/a
Hi,
Bastian Blank wrote:
> This change breaks the existing ABI and therefor needs an ABI bump, but
> it is missing from the patch.
I agree, that should be done. Thanks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Hi,
Bastian Blank wrote:
> This change breaks the existing ABI and therefor needs an ABI bump, but
> it is missing from the patch.
I agree, that should be done. Thanks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Hi,
Bastian Blank wrote:
> This change breaks the existing ABI and therefor needs an ABI bump, but
> it is missing from the patch.
I agree, that should be done. Thanks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
856213).
I think archive utils have had plenty of time (10 years!) to add SHA256
fields, so it is reasonable now to require a SHA256 field be present,
and validate only that?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
published SHA256 sums in the
archive since 2007 and *still* don't use them here. I think there is a
greater risk that we forget, or be too lazy, than we do this 'too soon'.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
published SHA256 sums in the
archive since 2007 and *still* don't use them here. I think there is a
greater risk that we forget, or be too lazy, than we do this 'too soon'.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
e
the md5sums field, and the struct size is not changing); though if they
do use, I'd prefer they FTBFS so that we find out.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
e
the md5sums field, and the struct size is not changing); though if they
do use, I'd prefer they FTBFS so that we find out.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
e
the md5sums field, and the struct size is not changing); though if they
do use, I'd prefer they FTBFS so that we find out.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
e testsuite to check parsing of the
SHA256 fields; that also would result in a larger diff however.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index 3dd29e1..1b7fcd8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,16 @@
libdeb
e testsuite to check parsing of the
SHA256 fields; that also would result in a larger diff however.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index 3dd29e1..1b7fcd8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,16 @@
libdeb
e testsuite to check parsing of the
SHA256 fields; that also would result in a larger diff however.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index 3dd29e1..1b7fcd8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,16 @@
libdeb
m[1])
return check_sum (target, "sha1sum", item->sum[1], buf_name);
if (item->sum[0])
return check_sum (target, "md5sum", item->sum[0], buf_name);
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
m[1])
return check_sum (target, "sha1sum", item->sum[1], buf_name);
if (item->sum[0])
return check_sum (target, "md5sum", item->sum[0], buf_name);
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
m, 32))
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
m, 32))
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
to be a supported release until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
to be a supported release until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
This bug is not itself RC, but it will be a blocking issue for RC bugs
I'm about to file.
I intend to submit a patch for this shortly.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
This bug is not itself RC, but it will be a blocking issue for RC bugs
I'm about to file.
I intend to submit a patch for this shortly.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
This bug is not itself RC, but it will be a blocking issue for RC bugs
I'm about to file.
I intend to submit a patch for this shortly.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
pprove an unblock. I think that is why this was
filed - intended as a request for comments about a speculative upload to
DELAYED/10. You could follow-up with your own debdiff if you plan to
make your own upload for this?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: D
pprove an unblock. I think that is why this was
filed - intended as a request for comments about a speculative upload to
DELAYED/10. You could follow-up with your own debdiff if you plan to
make your own upload for this?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: D
Christoph Egger wrote:
> Steven Chamberlain <ste...@pyro.eu.org> writes:
> > Would this be possible again please :/ psmisc is still not fixed, and
> > there are still surprisingly many gcc-6 uploads.
>
> And gcc-5. Done
And, again please :)
> > (Maybe even a da
Hi Christoph,
Steven Chamberlain wrote:
> please could somebody once again kill the hung gdb
> processes?
Would this be possible again please :/ psmisc is still not fixed, and
there are still surprisingly many gcc-6 uploads.
(Maybe even a daily cron for this would be a good idea...)
v5 patch is updated with this anyway. I should see about
upstreaming this now.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Date: Thu, 16 Feb 2017 12:37:41 +
From: Steven Chamberlain <ste...@pyro.eu.org>
Subject: enable use of portable libbsd functions
Add a new con
v5 patch is updated with this anyway. I should see about
upstreaming this now.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Date: Thu, 16 Feb 2017 12:37:41 +
From: Steven Chamberlain <ste...@pyro.eu.org>
Subject: enable use of portable libbsd functions
Add a new con
--with-libbsd (which is only relevant for static
linking).
It also means, there's no need for a soname bump, transition, or
patching of reverse-depends if linux arches enabled --with-libbsd.
The debian part of the patch is unchanged since last time.
Regards,
--
Steven Chamberlain
ste
--with-libbsd (which is only relevant for static
linking).
It also means, there's no need for a soname bump, transition, or
patching of reverse-depends if linux arches enabled --with-libbsd.
The debian part of the patch is unchanged since last time.
Regards,
--
Steven Chamberlain
ste
Steven Chamberlain wrote:
> Attached is [...]
Oops.
--
Steven Chamberlain
ste...@pyro.eu.org
Date: Wed, 15 Feb 2017 12:44:13 +
From: Steven Chamberlain <ste...@pyro.eu.org>
Subject: enable use of portable libbsd functions
Add a new configure option `--with-libbsd', which allo
Steven Chamberlain wrote:
> Attached is [...]
Oops.
--
Steven Chamberlain
ste...@pyro.eu.org
Date: Wed, 15 Feb 2017 12:44:13 +
From: Steven Chamberlain <ste...@pyro.eu.org>
Subject: enable use of portable libbsd functions
Add a new configure option `--with-libbsd', which allo
with
-lbsd if necessary, and not simply -lunbound as most do currently.
Helmut Grohne suggested uploading to experimental in that case, and then
I could file patches for all the reverse-depends.
Thanks for considering,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description
with
-lbsd if necessary, and not simply -lunbound as most do currently.
Helmut Grohne suggested uploading to experimental in that case, and then
I could file patches for all the reverse-depends.
Thanks for considering,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description
to add -lbsd to the Libs.private
field of libunbound.pc, whenever it is necessary.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
to add -lbsd to the Libs.private
field of libunbound.pc, whenever it is necessary.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
ian-...@lists.debian.org>
Changed-By: Steven Chamberlain <stev...@debian.org>
Description:
freebsd-buildutils - Utilities for building FreeBSD sources
freebsd-mk - FreeBSD makefile templates for bmake
Closes: 854184 855072
Changes:
freebsd-buildutils (10.3~svn296373-7) unstable; ur
o I shall enable this feature :)
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
o I shall enable this feature :)
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Package: src:guile-2.0
Version: 2.0.13+1-2
Severity: important
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
Hello,
guile-2.0 FTBFS on kfreebsd-amd64, since the addition of
0003-tests-Avoid-race-condition-in-REPL-server-test.patch in 2.0.13+1-4
Package: src:guile-2.0
Version: 2.0.13+1-2
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hello,
guile-2.0 FTBFS on kfreebsd-amd64, since the addition of
0003-tests-Avoid-race-condition-in-REPL-server-test.patch in 2.0.13+1-4
feq ($(DEB_HOST_ARCH),kfreebsd-amd64)
# See Bug#783773 for derivation.
-MFSROOT_LIMIT := 74m
+MFSROOT_LIMIT := 78m
endif
define mkfs.ufs1
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
feq ($(DEB_HOST_ARCH),kfreebsd-amd64)
# See Bug#783773 for derivation.
-MFSROOT_LIMIT := 74m
+MFSROOT_LIMIT := 78m
endif
define mkfs.ufs1
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
> >> Steven Chamberlain <ste...@pyro.eu.org> writes:
> >> > Please could someone check the gcc-7 build on fayrfax, to see of it is
> >> > stuck again with hung gdb processes?
[...]
> > Please could you do the same again... some/all of the buildds ar
Hello,
Christoph Egger wrote:
> Steven Chamberlain <ste...@pyro.eu.org> writes:
> > Please could someone check the gcc-7 build on fayrfax, to see of it is
> > stuck again with hung gdb processes?
>
> It is, will kill it in a minute just need to remember my sudo passwo
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
it is practical (or rather, allow dpkg-buildflags to
enable it).
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
libalias7 libalias-dev
Architecture: source all
Version: 10.3~svn296373-10
Distribution: unstable
Urgency: medium
Maintainer: GNU/kFreeBSD Maintainers <debian-...@lists.debian.org>
Changed-By: Steven Chamberlain <stev...@debian.org>
Description:
libalias-dev - Development files
Hi,
Here's un updated patch including the missing part, and now using a
proper invocation of pkg-config suitable for cross-builds, as pointed
out to me by helmutg@
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--- a/debian/control
Hi,
Here's un updated patch including the missing part, and now using a
proper invocation of pkg-config suitable for cross-builds, as pointed
out to me by helmutg@
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--- a/debian/control
s, perhaps we could place a bulk order somewhere,
but... then what to do with them afterward? It's an interesting point.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
___
Debconf-discuss mai
d support in
> an upstream Unbound release rather than in the Debian package. I'll see
> about producing a patch suitable for upstream.
Yes, the configure.ac part is something we should propose to upstream:
libbsd exists in other distros and, samba uses it for example.
Thanks!
Regards,
--
Steven
d support in
> an upstream Unbound release rather than in the Debian package. I'll see
> about producing a patch suitable for upstream.
Yes, the configure.ac part is something we should propose to upstream:
libbsd exists in other distros and, samba uses it for example.
Thanks!
Regards,
--
Steven
rver-xorg-video-siliconmotion, if Jonny would
like to try rebuilding with this perhaps.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/src/smi_driver.c b/src/smi_driver.c
index 8949cae..5023e63 100644
--- a/src/smi_driver.c
+++ b/src/smi_driver.c
@@ -1787,6 +1787,9 @@ SMI_S
rver-xorg-video-siliconmotion, if Jonny would
like to try rebuilding with this perhaps.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/src/smi_driver.c b/src/smi_driver.c
index 8949cae..5023e63 100644
--- a/src/smi_driver.c
+++ b/src/smi_driver.c
@@ -1787,6 +1787,9 @@ SMI_S
t1-dev,
libfstrm-dev ,
0.8.1 was the first version to implement a modern arc4random (using
ChaCha20 cipher) and implement genentropy on kfreebsd and hurd.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
t1-dev,
libfstrm-dev ,
0.8.1 was the first version to implement a modern arc4random (using
ChaCha20 cipher) and implement genentropy on kfreebsd and hurd.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
pinion that packages should use the libbsd implementation
whereever possible, and then in Debian we would only need to maintain it
in one place, to the benefit of all reverse-deps.
Many thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/configure.ac b/configure.ac
index d850539..f
pinion that packages should use the libbsd implementation
whereever possible, and then in Debian we would only need to maintain it
in one place, to the benefit of all reverse-deps.
Many thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/configure.ac b/configure.ac
index d850539..f
ug main
then the Xorg.log should give a more detailed backtrace.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
ug main
then the Xorg.log should give a more detailed backtrace.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
such file or directory)
Did you try rebooting the machine before starting Xorg? Perhaps you
could find something relevant in your logs with:
$ cd /var/log && sudo grep dbus dpkg.log syslog
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
101 - 200 of 5971 matches
Mail list logo
