Hey,
On Sat, 2025-04-12 at 08:10 +0200, Johannes Schauer Marin Rodrigues wrote:
> On Wed, 5 Mar 2025 10:07:15 +0100 Sjoerd Simons wrote:
> > On Tue, Mar 04, 2025 at 11:42:17AM +0100, Diederik de Haas wrote:
> > > On Thu Feb 27, 2025 at 2:30 PM CET, Johannes Schauer Marin Rod
On Sun, Mar 02, 2025 at 06:27:28AM -0500, Andres Salomon wrote:
> This bug will get fixed with the next source upload (probably on Tuesday). I
> had to do a binary upload due to NEW processing, which I wasn't
> anticipating.
Afaict this ended up being fixed in 133.0.6943.141-2+b1 ?
>
> On 3/2/25
On Tue, Mar 04, 2025 at 11:42:17AM +0100, Diederik de Haas wrote:
> Hi,
>
> On Thu Feb 27, 2025 at 2:30 PM CET, Johannes Schauer Marin Rodrigues wrote:
> > Source: mesa
> > Version: 25.0.0-1
> > Severity: serious
> >
> > this is a regression from mesa 24.3.4-3. I'm filing with RC severity because
Package: raspi-firmware
Version: 1.20240424+ds-4
Severity: normal
Seems the latest versions no longer include the brcmfmac43456-sdio firwmare,
which is required e.g. for wireless on rpi 400
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstab
On Fri, Oct 04, 2024 at 01:37:02PM +0200, Ben Hutchings wrote:
> On Sat, 28 Sep 2024 03:09:54 + gabriel wrote:
> > Package: src:linux
> > Version: 6.11-1~exp1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> >
> > ipu6 mipi camera drivers were not part of previous kernels, now they have
gt; Version: 2.1.13-1.1
> Severity: normal
> X-Debbugs-Cc: 356...@bugs.debian.org, 367...@bugs.debian.org,
> 430...@bugs.debian.org, 499...@bugs.debian.org,
> 845...@bugs.debian.org, 901...@bugs.debian.org, Sjoerd Simons
> , Package Salvaging Team
>
>
> Hi
>
> I'
Source: python-google-auth
Version: 1.5.1-3
Severity: wishlist
Hey,
Version 2.0 was released well over a year ago now :). It would be great to
update to a reent 2.x version
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (5
Hey,
On Sat, 2023-01-14 at 16:30 +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Thu, Jan 12, 2023 at 02:51:05PM +0100, Diederik de Haas wrote:
> > On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
> > > Fwiw there is a general regression with AMDGPU M
Source: linux
Followup-For: Bug #1028451
Fwiw there is a general regression with AMDGPU MST on linux 6.1; tracked
upstream
here:
https://gitlab.freedesktop.org/drm/amd/-/issues/2171
As the original report was about a second displayport on a docking station I
would guess it's the same issue. Fo
fo under the Revision:
> field.)
> However it maybe best trying to find someone who has the affected
> hardware revision that can confirm the problem exists and that
> the patch actually resolves it.
I can confirm both the problem and the patch solving it :)
--
Sjoerd Simons
Hey,
Fwiw; MR for prepping an update to cargo 0.56 is available at:
https://salsa.debian.org/rust-team/cargo/-/merge_requests/9
Full example update on my salsa repo:
https://salsa.debian.org/sjoerd/cargo/-/tree/debian/experimental
On Tue, Aug 10, 2021 at 11:13:05AM +0200, Sjoerd Simons
Hey,
On Fri, 2021-10-01 at 14:12 +0200, Julien Cristau wrote:
> On Fri, Oct 01, 2021 at 10:14:27AM +0200, Sjoerd Simons wrote:
> > Package: ca-certificates
> > Version: 20210119
> > Severity: normal
> >
> > This is a similar situation as #961907. The DST Roo
Package: ca-certificates
Version: 20210119
Severity: normal
This is a similar situation as #961907. The DST Root CA X3 certificate in
ca-certificates has expired, which is a signer for "ISRG Root X1", which in
turn i used by Letsencrypt. This causes some (older?) SSL implementation to
mark letsenc
On Wed, Jan 27, 2021 at 10:52:17AM +0900, Mike Hommey wrote:
> Source: cargo
> Version: 0.47.0-3
> Severity: wishlist
>
> Firefox now requires version 0.48, latest upstream is 0.50, and unstable
> is on 0.47.
Fwiw; with Cargo 0.51 the new resolver feature has been stablelized [0]. I'm
starting to
Control: severity -1 serious
Bumping severity up to serious; Due to this issue node-got on rebuild will not
get all expected nodejs packages in the binary package, causing it to be
broken. Which is obviously somewhat serious e.g. when it has to be rebuild due
to a security fix or similar
On Fri,
Package: dh-r
Severity: normal
Tags: ftbfs
Hey,
For context: we've got a debian derivative distribution that builds using
open-build-system (aka OBS). Unlike the debian buildd the apt cache isn't
available in the builds and if it was made available it would only be for the
set of installed packag
re succeeds to start.
>
> 5) Remove dbus-user-session
> $ sudo apt purge dbus-user-session
> $ sudo reboot
>
> 6) Log into Cinnamon from GDM
> Note: pipewire fails to start.
--
Sjoerd Simons
Package: user-mode-linux
Version: 5.10um1+b1
Severity: grave
On startup of uml in e.g. fakemachine it panics straight away:
```
$ fakemachine -b uml "uname -a"
kmsg_dump:
<5>Linux version 5.10.5 (buildd@x86-conova-01) (gcc (Debian 10.2.1-6) 10.2.1
20210110, GNU ld (GNU Binutils for Debian) 2.35.
On Tue, Dec 29, 2020 at 11:46:22AM +0100, Silvério Santos wrote:
> Package: pipewire
> Version: 0.3.15-1
> Severity: normal
>
> Dear Maintainer,
>
> Since the update to KDE Plasma 5.20 Dolphin makes the whole session crash,
> displaying the login screen instead of completing the following process
On Mon, Feb 15, 2021 at 02:37:53PM +0100, Michael Schaller wrote:
> I've installed `xdg-desktop-portal-gtk` and rebooted but that didn't
> solve the issue either.
> From the timestamps it looks like `xdg-desktop-portal` isn't starting
> fast enough.
>
> ```
> $ journalctl --user --boot --output=sh
ticast IP4LL .local domain
-
-if [ -x /usr/lib/avahi/avahi-daemon-check-dns.sh ]; then
- exec /usr/lib/avahi/avahi-daemon-check-dns.sh
-fi
diff -Nru avahi-0.7/debian/changelog avahi-0.7/debian/changelog
--- avahi-0.7/debian/changelog 2018-04-27 12:59:11.0 +0200
+++ avahi-0.7/debian/changel
y
not empty
```
the maint script helpers only remove the old config files in those
directories later ; and don't seem to remove empty directories (though
in practise those should be harmless ofcourse)
--
Sjoerd Simons
on :/
I can have a look at giving you a more specific reproduction method if
you can't trigger it but that will probably take a few days at least;
from the code it seems it somewhat wack-a-mole still though..
> On Wed, Jan 15, 2020 at 10:03 PM Sjoerd Simons
> wrote:
>
> > P
Package: slirp
Version: 1:1.0.17-9
Severity: important
The last upload fixes slirp crashes directly on startup on amd64; It now just
crashes
when starting to use it
backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x5567818fa30b in tcp_reass (tp=tp@entry=0x55678
ment for slirp based on libslirp (or uml being
able to use libslirp directly) would probably be best for everyone as
libslirp is actually maintained :)
--
Sjoerd Simons
On Mon, 2020-01-06 at 16:58 +, Anton Ivanov wrote:
>
> On 06/01/2020 16:21, Ritesh Raj Sarraf wrote:
> > Control: tag -1 +help
> >
> > On Mon, 2020-01-06 at 10:38 +0100, Sjoerd Simons wrote:
> > > On my sid system:
> > > ```
> > > $ strin
Package: user-mode-linux
Version: 5.4-1um-2
Followup-For: Bug #928924
On my sid system:
```
$ strings /usr/bin/linux.uml | grep port-helper
/usr/lib//uml/port-helper
```
So the path is still incorrect even with newer upstream kernels.
-- System Information:
Debian Release: bullseye/sid
APT pre
Package: slirp
Version: 1:1.0.17-8+b1
Severity: grave
Hey;
When starting slirp it crashes almost immediately; Backtrace from gdb:
```
(gdb) bt
#0 ip_slowtimo () at ip_input.c:457
#1 0x55568a82 in main_loop () at ./main.c:980
#2 0x97c6 in main (argc=1, argv=0x7fffdf38) a
Package: device-tree-compiler
Version: 1.4.7-3
Followup-For: Bug #877125
This seems a bug of debians own making; debian/rulies copes the upstream
Makefiles warnigns && Werror and then explicitly sets those as CFLAGS for the
build. However this means that they'll get applied *both* to libfdt and
py
Source: mesa
Version: 19.1.0-1
Severity: normal
Hey,
Panfrost debuted in mesa 19.1.0, but it's stil really early days. Some of my
collegues hacking on panfrost mentioned they'd feel quite uneasy if 19.1 with
panfrost enabled made its way into testing and creating a bad image for
panfrost.
The h
On Thu, 2019-02-28 at 13:45 +0100, Markus Koschany wrote:
> Hi Sjoerd,
>
> Am 28.02.19 um 13:38 schrieb Sjoerd Simons:
> > Source: netty
> > Version: 4.1.33-1
> > Severity: important
> > Tags: ftbfs
> > Justification: fails to build from source
> >
&
1) apertis; urgency=medium
+
+ * Build native parts without Werror as that can cause build failures
+
+ -- Sjoerd Simons Thu, 28 Feb 2019 11:08:13
+0100
+
netty (1:4.1.33-1) unstable; urgency=medium
* Team upload.
diff -Nru netty-4.1.33/debian/patches/disable-Werror.patch
netty-4.1.33/
g 2019-02-27 14:19:28.0 +0100
@@ -1,3 +1,11 @@
+hikaricp (2.7.1-1co1) apertis; urgency=medium
+
+ * d/p/drop-java9-classifier.patch: Added, drop the java9 classifier if build
+with jdk >= 9. Prevents packages from hitting FTBS when building against
+hikaricp build with jdk 9 w
Package: libitext-java
Version: 2.1.7-12
Severity: serious
Tags: patch
Hey,
When rebuilding bouncy-castle the jar doesn't seem to have the same classpath
built-in as older builds did; specifically comparing a rebuild with an old
debian build the MANIFEST.MF has the following diff (among other bit
On Tue, 2019-02-26 at 12:40 +0100, Emmanuel Bourg wrote:
> Le 26/02/2019 à 12:22, Sjoerd Simons a écrit :
>
> > ASM7 mode seems to have been introduced in the gradle v5.x series.
> > Not
> > sure if it makes sense for buster to upgrade to that (I really
> > don
On Tue, 2019-02-26 at 11:35 +0100, Emmanuel Bourg wrote:
> Le 26/02/2019 à 10:20, Sjoerd Simons a écrit :
>
> > I've atteched the output of running docker build on the DockerFile
> > i
> > attached to reproduce the issue; The relevant part in the gradle
> > bu
On Mon, 2019-02-25 at 23:59 +0100, Emmanuel Bourg wrote:
> Thank you for the report Sjoerd. What error did you get when
> compiling
> gradle with the rebuilt bsh?
>
> Emmanuel Bourg
Btw; I tested with forcing bsh to build with openjdk-8 instead and then
the issue doesn't occur while building grad
Source: bsh
Version: 2.0b4-19
Severity: serious
When building bsh with openjdk-11 it seems that afterwards building packages
using it fails e.g. after rebuilding bsh gradle fails to build.
Attached is a dockerfile which nicely shows the issue
-- System Information:
Debian Release: buster/sid
A
Package: gringo
Version: 5.3.0
Severity: serious
Hey,
Gringo seems to FTBS in buster due to:
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dp
Source: isorelax
Version: 2004-11
Severity: serious
Hey,
Rebuilding isorelax fails to build with:
javadoc: error - The code being documented uses packages in the unnamed module,
but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named
modules.
The reproducible build log
Source: icu4j
Version: 62.1-1
Severity: serious
Hey,
Rebuilding icu4j sees to FTBS with:
javadoc: error - The code being documented uses packages in the unnamed module,
but the packages defined in file:///usr/share/doc/default-jdk/api/ are in named
modules.
The reproducible builds log is showi
Source: node-es6-promise
Version: 4.2.5-1
Severity: serious
On a buster docker image:
```
# apt-get build-dep node-es6-promise
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an imp
Package: rng-tools5
Severity: wishlist
Hey,
Filing it against this pacakge as the rng-tools seems to be in some odd
transitional limbo.
Looking into the entropy debacle (especially on my devboards) and how other
distributions do things I noticed that e.g. fedora ships rng-tools 6.x from
https://
On Tue, 2018-08-28 at 10:51 +0100, Simon McVittie wrote:
> Source: telepathy-idle
> Version: 0.2.0-2
> Severity: normal
>
> telepathy-idle still lists me and Jonny Lamb in its Uploaders; we
> removed
> ourselves from Uploaders in the VCS in 2014 and 2016 respectively.
> The
> package's metadata al
On Tue, 2018-08-28 at 10:48 +0100, Simon McVittie wrote:
> Source: telepathy-rakia
> Version: 0.8.0-3
> Severity: normal
>
> telepathy-spec still lists me and Jonny Lamb in its Uploaders; we
> removed
> ourselves from Uploaders in the VCS in 2014 and 2016 respectively.
> The
> package's metadata a
19:01:22.0 +0200
+++ ne10-1.2.1/debian/changelog 2018-08-10 12:26:58.0 +0200
@@ -1,3 +1,9 @@
+ne10 (1.2.1-3co1) apertis; urgency=medium
+
+ * Fix build on armhf
+
+ -- Sjoerd Simons Fri, 10 Aug 2018 12:26:58 +0200
+
ne10 (1.2.1-3) unstable; urgency=medium
* Update copyright
Package: jenkins-job-builder
Version: 2.0.3-1
Severity: grave
Hey,
installing jenkins-job-builder gives the following error:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
python3-jenkins-job-
Package: qemu-user-static
Version: 1:2.11+dfsg-1
Followup-For: Bug #887892
Hey,
I'm seeing the same when using debos for the same reasons as vmbootstrap will
be slow. Both tools wrap debootstrap and for foreign architectures will run the
debootstrap second stage in a chroot user qemu-user-static
Source: linux
Severity: normal
Hey,
The DRM_DP_AUX_CHARDEV exposes the DP aux channel to userspace, this is used by
e.g. fwupmgr to allow it to upgrade firmware of Dell Type-C Docking stations.
Please enable this option :)
-- System Information:
Debian Release: buster/sid
APT prefers unstable-
838d9982ae75459000741f2e08f405a42 Mon Sep 17 00:00:00 2001
From: Sjoerd Simons
Date: Fri, 9 Jun 2017 11:58:07 +0200
Subject: [PATCH] [armhf] Enable CONFIG_PCI_HOST_GENERIC to support PCI in
armhf vm's
---
debian/config/armhf/config | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/c
Package: qemu-system
Version: 1:2.8+dfsg-6
Severity: normal
Hey,
For $reasons i'm exposing /boot over a filesystem share with the host system,
fsdev is setup as followed on the qemu command line:
-fsdev
local,security_model=none,id=fsdev-fs0,path=/srv/mp30-ar1-cbg-0-armhf-0-boot
Unfortunately
Package: jenkins-job-builder
Version: 1.6.1-1
Severity: wishlist
Hey,
Jenkins-job-builder was release a some time ago (specifically 2.0.0.0b2), among
other things this features support for pipeline project types which are a very
useful new feature in jenkins 2.
Please consider updating the packa
Package: ifupdown
Version: 0.8.19
Severity: normal
Hey,
Upstart is no longer in stretch/unstable, so the integration in it for ifupdown
is
rather pointless. Probably good to remove.
Fwiw, I ran into this due to one of my ARM boards not booting as the upstart
integration happened to trigger #861
Package: systemd
Version: 233-5
Severity: normal
Hey,
The systemd helper for init-tools is trying to be nice and helpful by
triggering a daemon reload iff systemd cannot find the service which includes
it (e.g. due to the generator not having run yet when the lsb service is
triggered)
Package: systemd
Version: 233-5
Severity: important
Tags: upstream
Hey,
There is a known issue in systemd that after a daemon reload it lost track of
where in an Exec* sequence it was, which causes the remaining commands not to
run.
I ran into a pretty nasty corner-case yesterday causing one of
Package: golang-github-docker-docker-dev
Version: 1.13.0~ds1-1
Severity: important
Hey,
The opts subdir in docker now refers to packages in the api subdirectory, so
that should ship as well to get things to build
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT polic
Package: docker.io
Version: 1.13.0~ds1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Trying to build docker.io in a pbuilder seems to fails with quite a few
occurances of EPERM in the testsuite. I wonder how this could have build under
fakeroot
Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hey,
runc fails to build on stretch after updating the bits the build-depends
require, it looks they're not strict enough for:
* golang-git
Source: etcd
Version: 3.1.2+dfsg
Severity: serious
Justification: fails to build from source
Looks like etcd needs at least golang-github-coreos-pkg >= 3, when trying to
build against an older versions (as e.g. present in stretch) the build fails
iwth:
src/github.com/coreos/etcd/tools/functiona
Source: etcd
Version: 3.1.2+dfsg-1
Severity: normal
When trying to build against the stretch version of
golang-github-xiang90-probing-0.0 the following error is seen:
src/github.com/coreos/etcd/rafthttp/probing_status.go:54: s.Err undefined
(type probing.Status has no field or method Err)
Plea
Source: etcd
Version: 3.1.2+dfsg
Severity: serious
Justification: fails to build from source
Hey,
When trying to build etcd i get:
okgithub.com/coreos/etcd/wal 19.322s
? github.com/coreos/etcd/wal/walpb [no test files]
dh_auto_test: go test -v -p 6 -run=Test github.com/coreos/etcd
gith
Package: containerd
Version: 0.2.3~git20161117.78.03e5862~ds1-1
Severity: serious
Justification: fails to build from source
Hey,
Trying to rebuild containerd went wrong, seems the build-depends on
golang-golang-x-sys-dev and golang-github-docker-go-connections-dev are
missing.
-- System Informat
Package: libgtk-3-0
Version: 3.22.9-1
Severity: grave
Tags: upstream
Hey,
In the wayland session ever since upgrading to 3.22.9 i'm getting spurious key
repeats in some applications.
This is likely to be https://bugzilla.gnome.org/show_bug.cgi?id=779374
-- System Information:
Debian Release:
Package: obs-server
Version: 2.7.1-10
Severity: important
Hey,
Our publisher shows:
Feb 20 13:08:00 niobium bs_publish[14097]: publish failed for
home:alee:branches:apertis:16.03:development, 16.03 : dpkg-scanpackages
failed: 256
And indeed dpkg-scanpackages isn't installed. obs-server s
Package: systemd
Version: 232-18
Severity: important
Tags: patch
Hey,
One of my VPNs runs dnsmasq and seems to trigger systemd-resolved to fail the
lookup with dnssec errors:
neon.elements: resolve call failed: DNSSEC validation failed: no-signature
This got fixed upstream in 97c2ea26456f21334
Package: libwebkit2gtk-4.0-37
Version: 2.14.4-1
Severity: grave
Hey,
Both epiphany and evolution show blank output when trying to render
website/e-mails. Downgrading libwebkit2gtk-4.0-37 to 2.14.3 seems to solve the
issue.
>From some notes on #debian-gnome this might be caused by:
https://bugs
Package: obs-build
Version: 20170201-1
Severity: normal
The wrong path is used to print the debootstrap log on failure, fixed in
https://github.com/openSUSE/obs-build/pull/335
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'uns
Package: obs-build
Version: 20170201-1
Severity: important
Hey,
Some packages trigger binfmt_misc to be mounted, which leaks if not unmounted
after build.
A patch for that is available at
https://github.com/openSUSE/obs-build/pull/331/commits/7f0efeeba7f62a8266166f8def79ff503b7455bc
-- System I
Package: obs-build
Version: 20170201-1
Severity: important
Tags: patch
the patch in the last upoad tried to mount shm on /dev/$myroot/shm which won't
work. This got fixed in the last update of the PR #331 for obs-build
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT
Package: obs-build
Version: 20170201-1
Severity: important
the ptmx in the debootstrap chroot ended up not being usable, this breaks
package builds which rely on a pts/tty. Fixed in:
https://github.com/openSUSE/obs-build/pull/331/commits/fc08c45072851779ce67fa2f92e509dc39e5ed27
-- System Infor
Package: binfmt-support
Version: 2.1.6-2
Severity: wishlist
As of linux 4.8 the binfmt format added the F flag which causes an emulators to
be opened non-lazily, which means it can be used in a chroot without needing
the emulator to be installed in the chroot. (Incredibly useful when chrooting
in
Package: obs-build
Version: 20160921-1
Severity: important
When using the debootstrap recipe the build root doesn't get fully setup e.g.
etc/hosts is missing as well as the virtual filesystem mounts. This causes some
packages to fail.
I've submitted some fixes for that upstream in:
https://gith
Package: obs-worker
Version: 2.7.1-9
Severity: normal
While doing a test build of quite a few diferent package, I'm running into an
issues like:
[ 25s] /srv/obs/run/worker/1/build/init_buildsystem: fork: retry:
Resource temporarily unavailable
Starting from systemd v231 each service gets 15% o
Package: obs-worker
Version: 2.7.1-9
Severity: normal
obs-worker is a, well, not very nice init script which runs all the worker
instances (under screen of all things). This means that all systemd's
functionality applies to all instances together rather then specific ones, e.g.
this means resource
Package: obs-build
Version: 20160921-1
Severity: important
Tags: upstream
The obs-build version in debian, at least when used with the debootstrap recip
seems to leak devpts mounts (3 are present during the build, only one seems to
get unmounted after the build, leaking 2).
Upstream cleaned up mo
Package: obs-build
Version: 20160921-1
Severity: important
Tags: upstream patch
The dpkg-dev version present in xenial has a bug where it'll fail iff there are
symlinks present under the path it's pointed to. This causes the debian
debootstrap recipe to fail when building for xenial.
Fixes for th
Package: obs-worker
Version: 2.7.1-9
Severity: grave
The package creates an obsworker user on install, however the init scripts
tries to chown some files to the non-existing obs-run user causing it to fail.
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500
Package: lava-dispatcher
Version: 2016.12-1
Severity: normal
According to the installing on debian documentation, when only using V2 one can
leave the default tftp (/srv/tftp) directory as the one configured for
tftpd-hpa, however this doesn't work giving the following error in the log.
- {"dt":
Package: lava-dispatcher
Version: 2016.12-1
Severity: normal
Lava dispatcher has a dependency on ser2net, but this is only needed if usng
ser2net to provide serial for DUTs. Please downgrade ser2net dependency to a
recommends
-- System Information:
Debian Release: stretch/sid
APT prefers unstab
Package: bmap-tools
Version: 3.2-4
Severity: important
Hey,
Since 3.2-2 copying from a http location is broken:
$ bmaptool copy
https://images.apertis.org/daily/16.06/images/target/amd64-uefi/20160718.0/apertis-16.06-target-amd64-uefi_20160718.0-collabora.btrfs.img.gz
/tmp/test.img
bmaptool: i
Package: apitrace
Version: 7.1+git20160531.2d78bef0+repack-1
Severity: wishlist
apitrace Retracers like e.g. egltrace can currently only use X11 as the window
system. For more modular window system support, apitrace has support for using
the waffle library (e.g. libwaffle-dev and friends). Please
Package: apitrace
Version: 6.1+git20150626.62ad71c6+repack-1.1+b1
Severity: wishlist
Hey,
The apitrace git snapshot is ~11 months old by now, it would be great to see a
newer version in Debian.
Specfically eglSwapBuffersWithDamage was implemented last week, which is
required to trace programs us
On Thu, Jan 16, 2014 at 08:44:14AM +0100, Raphael Hertzog wrote:
> Control: retitle -1 document how to un-ignore files ignored by default in
> "3.0 (native)" and "3.0 (quilt)"
>
> On Wed, 15 Jan 2014, peter green wrote:
> > When attempting to build such a package using the 3.0 native format
> > t
Package: jenkins-job-builder
Version: 1.3.0+2015.12.15.git136.959eb4b909-1
Followup-For: Bug #806715
This has been broken by the following patch:
debian/patches/patches/0005-builders-add-publish-over-ssh-support-as-a-build-ste.patch
This patch hasn't been merged upstream and the review commen
Source: linux
Severity: wishlist
Hey,
In current debian kernels CONFIG_GPIO_SYSFS is only set for ARM kernels. This
options allows userspace to directly tinker with GPIO (if they're not bound
by a driver). Which is quite useful on development boards with GPIO extension
headers to tinker with elec
angelog b/debian/changelog
index 0ffed44..27c2e8b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-git (1.0.1+git137-gc8b8379-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+
+ -- Sjoerd Simons Wed, 02 Dec 2015 20:14:07 +0100
+
python-git (1.0.1+git
0d85947bca5cd Mon Sep 17 00:00:00 2001
From: Sjoerd Simons
Date: Tue, 1 Dec 2015 09:45:54 +0100
Subject: [PATCH] Pass components to debootstrap --second-stage
Commit e24e4b in debootstrap fixed setup_available to work in the
--foreign case (iotw at the second stage). Unfortunately this breaks
thing
upg 1.4.19-6
debootstrap suggests no packages.
-- no debconf information
>From 6621d8304cb79dcc6e07098caaf6eaa56fe8594a Mon Sep 17 00:00:00 2001
From: Sjoerd Simons
Date: Tue, 1 Dec 2015 09:09:07 +0100
Subject: [PATCH] Fix multiple components usage for --foreign
commit e24e4b00673673
[1]: Leaving directory '/«BUILDDIR»/u-boot-2015.10+dfsg1'
> make: *** [build] Error 2
>
>
> I'm wondering if it wouldn't be cleaner to add support to upstream's
> Makefile to build u-boot-spl-dtb.rksd images, rather than muck around
> in
> debian/rules?
Something i've been thinking about but didn't have the time for, that
should solve your issue with cross-building indeed.
> Or simply document the process to generate the rksd images
> in README.Debian?
Personally I think the less runes are needed for people to update u-
boot on their devices the better. But that should work fine as a
temporary measure at least :)
--
Sjoerd Simons
Package: firmware-brcm80211
Version: 0.44
Severity: wishlist
BCM4339 SDIO has been added to the upstream linux-firmware git repository
earlier this year, please including it in the firmware-brcm80211 package.
For reference this is the brcm/brcmfmac4339-sdio.bin file
-- System Information:
Debi
On Wed, 2015-07-08 at 08:11 +0200, Daniel Baumann wrote:
> On 07/08/2015 08:09 AM, Sjoerd Simons wrote:
> > That's weird, that patch is against git HEAD of the deiban branch
> > on git://live-systems.org/git/live-build.git, am i looking at
> > the wrong git repository
t/live-build.git, am i looking at the wrong git
repository/git branch or did you not push it
just yet ?
--
Sjoerd Simons
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
75bafb3c41a20bdab30bc984aa7d2 Mon Sep 17 00:00:00 2001
From: Sjoerd Simons
Date: Tue, 7 Jul 2015 10:35:44 +0200
Subject: [PATCH] Fix running of local hooks
Commit 50794b1de broke running any local chroot hooks as it's both
looking in the wrong spot to see if there are any hooks and if it
t1.16.3-3
Versions of packages live-build suggests:
ii debian-keyring 2015.06.19
ii gpgv1.4.19-3
-- no debconf information
>From 8807f764683bbec3d00d8a5a1d1d75a28317ea68 Mon Sep 17 00:00:00 2001
From: Sjoerd Simons
Date: Fri, 26 Jun 2015 15:10:30 +020
Package: arcanist
Version: 0~git20150613-1
Severity: important
In current unstable arc diff fails with:
Exception
ERR-CONDUIT-CORE: Invalid parameter information was passed to method
'differential.query', could not decode JSON serialization. Data:
{"authors":["PHID-USER-tiexds33yvgetrvgglxc"],
On Fri, 2015-05-08 at 19:09 -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On Wednesday 06 May 2015 11:52:32 Sjoerd Simons wrote:
> [snip]
> > dir being the full path to the source files, basedir /usr, when dir
> > doesn't
> > start with /usr this is a noop, bu
Source: qtwebkit
Version: 2.3.4.dfsg-3
Severity: normal
Tags: patch
Hey,
When building qtwebkit in a directory under /usr (e.g. /usr/src) the following
compiler error occurs:
In file included from
/usr/src/packages/BUILD/qtwebkit-2.3.4.dfsg/Source/WebKit/qt/declarative/qdeclarativewebview_p.h:2
tag 770734 - moreinfo unreproducible
tag 770734 + patch
thanks
On Fri, May 01, 2015 at 09:43:31AM +0200, Sjoerd Simons wrote:
> Remaking the policy file fails because there is no src/hostname directory in
> the out-of-tree build... In turn the reason there isn't a src/hostname
>
On Sat, Apr 04, 2015 at 07:48:28AM -0700, Daniel Schepler wrote:
> On Wed, Jan 21, 2015 at 8:04 AM, Michael Biebl wrote:
>
> > Hi Daniel,
> >
> > Am 23.11.2014 um 19:02 schrieb Daniel Schepler:
> >
> > > I can't reproduce this with a vanilla pbuilder setup, so I'm not sure
> > what's
> > > causin
Package: linux
Severity: wishlist
Hey,
The ARM linux image packages install DTB files in /usr/lib//,
as a DTB is required to boot most modern arm systems typically the right file
has to be copied to a bootloader accessible filesystem before usage (e.g.
/boot). On current Debian systems this tends
1 - 100 of 959 matches
Mail list logo
