On Thu, Aug 31, 2023 at 01:29:17PM -0300, Joao Eriberto Mota Filho wrote:
> Dear Simon Ruderich,
>
> Currently blhc fails to build from source in Debian Sid. This issue was
> detected in Salsa[1].
>
> [1] https://salsa.debian.org/debian/blhc/-/jobs/4635438
Hi Eriberto,
should b
Hi,
upgrading to xpra 3.1.3 (latest 3.1 release) also fixes this bug.
The existing debian/ builds fine with 3.1.3, only the
systemd.patch needs to be removed (no longer necessary as
upstream now uses /etc/default/xpra).
Best,
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+
Hello,
the attached patch works for me as workaround for Bullseye. It adds the
missing file and updates the #include path to it. Apply it with
cd / && patch -p1 < /path/to/patch
With the patch I can successfully build kernels which use GCC
plugins on Bullseye.
Is it possible to apply a
Package: golang-1.16
Version: 1.16.3-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: si...@ruderich.org
Hello,
since the update to 1.16.3-1 I cannot build any packages with
go-1.16:
$ printf 'package main\nmain(){}' > x.go
$ /usr/lib/go-1.16/bin/go run x.go
#
0/debian/changelog
--- kpatch-0.3.2/debian/changelog 2017-04-01 21:33:40.0 +0200
+++ kpatch-0.5.0/debian/changelog 2018-04-13 15:56:07.615948149 +0200
@@ -1,3 +1,9 @@
+kpatch (0.5.0-0.1) unstable; urgency=medium
+
+ * Package 0.5.0.
+
+ -- Simon Ruderich <si...@ruderich.org> Fri, 13 Apr 2018
On Mon, Jun 05, 2017 at 12:38:15PM +0300, Adrian Bunk wrote:
> How would that break things for *jessie* users?
>
> The runit-init package is not in jessie, and the runit package in jessie
> does not provide /sbin/init
Ah, sorry for that. I thought that runit-init was already in
Jessie and didn't
Package: runit
Version: 2.1.2-9.2
Severity: grave
Justification: renders package unusable
Hello,
With the recent removal of runit-init in -9.1 /sbin/init is no
longer provided breaking the boot for users depending on runit as
init system. So a user happily running runit in Jessie will have
a
On Tue, Nov 15, 2016 at 08:47:41AM +0100, Johannes Schauer wrote:
> Hi,
>
> recently, dpkg switched from the triplettable to architecture
> quadruplets. When now trying to run blhc with the new libdpkg-perl, one
> will get:
>
> Undefined subroutine ::Arch::debarch_to_debtriplet called at
>
On Mon, Sep 08, 2014 at 11:30:48PM -0300, Felipe Sateler wrote:
Could you propose a patch filtering out the characters plus (+), minus
(-) signs, and periods (.)?
Sure, revised patch is attached.
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id:
On Wed, Sep 03, 2014 at 06:17:52PM -0400, Felipe Sateler wrote:
The problem is that such a blacklist could include other invalid shell
characters: + comes to mind, but I don't know the entire set of
character which are allowed as shell variables, as opposed to the
valid make allowed chars.
On Wed, Sep 03, 2014 at 03:37:01PM -0400, Felipe Sateler wrote:
The change proposed by Simon prepends every variable known to make
that starts with DEB_ , along with its value, to the invocation of
dpkg-buildflags. The problem is that some make variable names are
illegal as shell variable
Source: ogmrip
Version: 1.0.1-1
Severity: serious
Justification: Policy 2.2.1
Hello,
ogmrip depends on mencoder which is not currently available in
Debian unstable which makes the package uninstallable.
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id:
f5b7faa05990eea9bb90b3e8720592d446b9223e Mon Sep 17 00:00:00 2001
Message-Id: f5b7faa05990eea9bb90b3e8720592d446b9223e.1377642612.git.si...@ruderich.org
From: Simon Ruderich si...@ruderich.org
Date: Wed, 28 Aug 2013 00:30:09 +0200
Subject: [PATCH] Handle new format of binNMUs.
---
apt-listchanges.py | 11
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
Description: Don't set the hardening flags manually.
Instead take them from dpkg-buildflags which automatically disables
unsupported flags on the current architecture.
.
Prevents build failure on e.g. kfreebsd.
Author: Simon
reopen 669495
thanks
Dear Maintainer,
Please don't disable all hardening flags just because one
hardening option causes a build failure.
The problem is the pie hardening option which can cause
-fPIC/-fPIE conflicts (libraries must be built/linked with -fPIC,
binaries with -fPIE).
Most build
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
Description: Use build flags from environment (dpkg-buildflags).
Necessary for hardening flags.
.
Also strip -pie/-fPIE from CFLAGS/LDFLAGS when used to link libraries. It
conflicts with -fPIC.
Author: Simon
From: Simon Ruderich si...@ruderich.org
Date: Tue, 6 Mar 2012 02:00:48 +0100
Subject: [PATCH] Enforce valid signed repositories by default.
---
debian/NEWS | 19 ++
debian/pbuilder-test/00_prepinstall |2 +-
pbuilder-checkparams| 18
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Mar 06, 2012 at 02:29:25AM +0100, Simon Ruderich wrote:
I tested it with the official Debian repository, signed and
unsigned local repositories and it works fine for me. But I'm
only a normal pbuilder user, so I might have missed
Package: util-linux
Version: 2.20.1-1
Followup-For: Bug #650534
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
It looks like an autoreconf is all that's necessary. The attached
patch modifies mount/Makefile.in (the result of the autoreconf)
to fix the build for now.
Regards,
Simon
-
19 matches
Mail list logo
