I ran into a similar problem when creating a live build of a system. I was able
to overcome it by forcing my build process to use a single core. I used the
following build command:
taskset 0x1 sudo lb build
Perhaps there's some strange concurrency issue... I don't know. I just know
that my bui
The whole issue is with the systemd unit hardcoding the paths, which is
what that patch addresses.
I've been bitten by this as well, and I put a modified systemd unit in
/etc/systemd/system, so as long as this doesn't get fixed any package
upgrades don't break opendmarc.
Stijn
On Tue, 31 Oc
On Saturday, 22 June, 2013 08:01 PM, David Suárez wrote:
During a rebuild of all packages in sid, your package failed to build on
amd64.
A fixed package is available at
http://mentors.debian.net/debian/pool/main/f/ffgtk/ffgtk_0.8.1-3.dsc
The package is waiting for sponsorship, I have already
On Friday, 14 June, 2013 03:26 PM, Emilio Pozuelo Monfort wrote:
On 14/06/13 09:22, Emilio Pozuelo Monfort wrote:
ISTR recommending a package not in the archive was a bug, but I can't find a
reference. So if you would like to keep this that's fine with me as it won't
prevent migration of your pa
On Friday, 14 June, 2013 02:51 AM, Jeremy Bicha wrote:
Since your package is in collab-maint,
I hope you don't mind that I pushed the fix there.
furthermore, the changelog mentions the wrong ticket number ;-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
On Friday, 14 June, 2013 02:51 AM, Jeremy Bicha wrote:
Since your package is in collab-maint,
I hope you don't mind that I pushed the fix there.
a more important nitpick would be that IMO it is not a good idea to
touch the changelog until the time of release. Changing the changelog
together
On Friday, 14 June, 2013 02:51 AM, Jeremy Bicha wrote:
Ubuntu has a fix for this bug. Since your package is in collab-maint,
I hope you don't mind that I pushed the fix there.
Hello Emilio and Jeremy,
thank you for your work on this bug. Please excuse my ignorance but I
don't quite even see
On Thursday, 30 May, 2013 04:05 PM, Andreas Beckmann wrote:
a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3
Hi,
thank you for your report. Inspection of the code suggests that apart
from isdnlog whic
On 04/15/12 15:31, Axel Beckert wrote:
Hi,
FOSS tech. support wrote:
I suggest, when aptitude doesn't find a package in all mirrors, it
should automatically look out in snapshot.debian.org to fetch the
package.
I don't think that's a good idea:
It circumvents the package signi
Package: aptitude
Version: 0.6.6-1
Severity: wishlist
I suggest, when aptitude doesn't find a package in all mirrors, it
should automatically look out in snapshot.debian.org to fetch the package.
The same should be implemented in all apt implementations like software
centre (it uses APT pytho
I have the exact same problem in Squeeze (Debian testing). Here is a
list of what works and what does not.
What works:
1. Burning data into CD.
2. Burning ISO into CD.
3. Burning data into DVD.
What does not work:
1. Burning data into DVD.
When I insert a DVD+R (4.7 GB), open Brasero, and pres
11 matches
Mail list logo
