On Wed, Nov 22, 2017 at 07:34:15PM +0100, Marius Bakke wrote:
> This is a known problem in glibc that has recently been fixed AFAICT.
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=21041
>
> It was also "backported" to the 2.26 release branch:
>
>
On Sun, Aug 06, 2017 at 04:29:33PM -0400, Leo Famulari wrote:
> Recently several serious bugs were fixed in Oniguruma,
> CVE-2017-{9224,9225,9226,9227,9228,9229}:
[...]
> I'm not sure exactly which Oniguruma release fixed the bugs.
I'm still not sure, but our PHP package is using the latest
On Mon, Jul 16, 2018 at 01:14:30PM -0400, Leo Famulari wrote:
> There is a new release of Crypto++ available. I'm not sure if this
> addresses whatever issue was mentioned in the original advisory.
Crypto++ was updated to 8.0.0 in January 2019.
https://www.cryptopp.com/release800.html
>
On Tue, Feb 26 2019, Leo Famulari wrote:
It will aid debugging if you can tell us which commit you
upgraded from, as well.
Good call.
I think the last Guix commit that I was branched from (where Emacs
worked properly) was e36d043882462f2252aa8e6fe7c34bfbee6d3175.
Given the lack of response to this report, and the inherent difficulty
in reproducing the issue, I'm closing this bug.
If I notice it again and find an effective reproducer, I'll re-open it.
signature.asc
Description: PGP signature
The Hurd `patch` patch was adjusted in commit
ec07ba1ff73d6317470517ccf530a4a89b216f23
signature.asc
Description: PGP signature
On Tue, Feb 26, 2019 at 11:49:07AM +1100, Carlo Zancanaro wrote:
> I updated my Guix installation and user profile yesterday, and since then
> Emacs has started crashing. I've attached the output of running "emacs -Q".
>
> I'm using my own branch of Guix that is based on
>
I updated my Guix installation and user profile yesterday, and
since then Emacs has started crashing. I've attached the output of
running "emacs -Q".
I'm using my own branch of Guix that is based on
089a2c51ff4d4d8ddd180001b25535019c0d35c0, but I haven't modified
Emacs. As a workaround I am
Well, this report was too vague to be of much use. Closing :)
signature.asc
Description: PGP signature
I've added a comment warning about this issue in commit
848b3749b2e9741d2fb7c0cc531d7536474700c1.
signature.asc
Description: PGP signature
Efraim made several commits in March 2018 that gave descriptive
file names to the SVN checkouts of packages in (gnu packages tex).
I haven't noticed any more mystery svn-checkouts since then, so I'm
closing this bug.
signature.asc
Description: PGP signature
The list of files to be rebuild has been updated several times since
this bug was filed, so I'm closing it now.
signature.asc
Description: PGP signature
Qt was updated to 5.11.3 in commit
c82cd3a7bd5d7a85fb48a37c3a5e37fbe3ed6738. Thanks Efraim!
signature.asc
Description: PGP signature
The requested features were added in commit
f1de676ea82c2bed9a435fce37ade0186296bfc9.
Thanks, Ludo!
signature.asc
Description: PGP signature
Since this bug was filed, Ghostscript has received more scrutiny and
serious bugs continue to be found.
The recommendation of the researchers seems to be to disable and remove
Ghostscript unless a Postcript interpreter is actually necessary.
Barring that, we should keep our package up to date
Leo Famulari writes:
> It was recently reported that libidn2 can cause issues for domains whose
> names contain underscores, and maybe some other characters, too. It
> matters to us because we build GnuTLS with libidn2.
>
> I'm not sure yet what the solution is for us. Help wanted!
>
> Original
Leo Famulari writes:
> While working on the bug 'Changing package source URLs from git:// to
> https://' [0], I noticed an issue with the sources for guile-emacs.
>
> We currently fetch this source code over the unauthenticated GIT
> protocol. It is also available over HTTPS. However, these two
I'm closing this because we have a new build farm as the default source
of substitutes.
Control messages should be sent to the debbugs server, not to a specific
bug addess.
Closing a bug is simpler, just send a message to xyz-d...@debbugs.gnu.org.
Andreas
I noticed that if you call "guix COMMAND" for some COMMANDs without any
options given, they produce something which is not very useful to the
user. I first noticed it with guix pack:
When "guix pack" is run without any options, it builds an empty pack:
$ guix pack
close 34649
The problem disappeared. Either user error or bug was fixed since
reporting.
—Marco
On Mon, Feb 25, 2019 at 12:20:40AM -0600, Matthew Brooks wrote:
> Thanks for the info, and sorry for the trouble. This isn't actually a foreign
> distro, my OS declaration just doesn't use %desktop-services, so the
> automatic setuid handling wasn't there. Thanks to your info I was able to
>
Hello,
I could not 'guix pull' on my recently installed Guix (on Ubuntu 18.04).
Pull log attached.
—Marco
Updating channel 'guix' from Git repository at
'https://git.savannah.gnu.org/git/guix.git'...
Building from this channel:
guix https://git.savannah.gnu.org/git/guix.git 5c06a18
24 matches
Mail list logo
