Why won't you just rename the package back to "libjpeg-progs"?
Without this nonsense migration, there won't be any issues. The reason
for libjpeg-turbo-progs, those "waaah hijack" complaints don't hold any
water anymore as libjpeg9 is gone, and I don't think the Release Team is
going to ever allow
On Thu, Sep 08, 2016 at 12:57:32AM -0400, Nicholas D Steeves wrote:
> Package: sponsorship-requests
> Severity: grave
>
> I am looking for a sponsor for an urgent NMU of "btrfs-progs". Upstream
> has marked this as an "urgent fix" <
> https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-
I've taken a brief look at this FTBFS, and it appears that it's not a
problem in imms but in torch3 (a build-dependency) which #defines min() and
max() which breaks functions mandated by C++11 and higher, and with new gcc's
focus being on C++14 compliancy, --std=c++98 doesn't appear to be enough to
${misc:Depends}.
+
+ -- Adam Borowski Sat, 30 Jul 2016 03:53:25 +0200
+
debfoster (2.7-2) unstable; urgency=medium
* update config.sub/guess. Closes: #533685
diff -u debfoster-2.7/debian/compat debfoster-2.7/debian/compat
--- debfoster-2.7/debian/compat
+++ debfoster-2.7/debian/compat
@@ -1 +1 @
-6 (Closes: #811622).
+ * Remove Andres Mejia from Uploaders, per the MIA team (Closes: #743519).
+
+ -- Adam Borowski Sat, 30 Jul 2016 04:26:19 +0200
+
crtmpserver (1.0~dfsg-5.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru crtmpserver-1.0~dfsg/debian/control
crtmpserver-1.0~d
Closes: #822030
+
+ -- Adam Borowski Wed, 03 Aug 2016 00:54:56 +0200
+
timidity (2.13.2-40.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru timidity-2.13.2/debian/rules timidity-2.13.2/debian/rules
--- timidity-2.13.2/debian/rules2015-12-23 20:12:46.0 +0100
+++ timidit
Likely related: on a test system using sysv-rc with openrc removed but not
purged, I get a screenful repeated of "insserv: warning: script 'transit'
missing LSB tags and overrides" whenever there's an rc.d operation.
--
An imaginary friend squared is a real enemy.
Package: terminal.app
Version: 0.9.8-1+nmu1+b2
Severity: grave
Justification: renders package unusable
Hi!
I'm afraid terminal.app crashes at startup in unstable; this doesn't seem to
be related to my particular setup as the same happens on three different
machines (amd64, i386, armhf) with varied
Control: retitle -1 missing dependency on gnustep-back
> >I'm afraid terminal.app crashes at startup in unstable
> Well, it seems that teminal.app doesn't depends on gnustep-back package.
>
> Instead it depends on libgnustep-gui0.25 which doesn't depends on
> gnustep-back.
Indeed, installing gn
Package: init-system-helpers
Version: 1.32
Severity: grave
Since this night's upload, uses of invoke-rc.d inside a chroot fail with:
invoke-rc.d: could not determine current runlevel
This makes a crapload of packages uninstallable -- many pretty deep in
dependency chains.
We have two /sbin/runle
On Sat, May 07, 2016 at 02:42:37AM +0200, Pierre Ynard wrote:
> That's not the idea I'd like to have about Debian. If I wanted
> a distro where unstable is broken and unusable, I would have installed
> long ago.
I'm afraid there's not enough people who care about 586 enough to maintain
it. And t
On Mon, May 09, 2016 at 08:37:13AM +0200, Johannes Schauer wrote:
> Quoting Adam Borowski (2016-05-09 04:19:23)
> > I'm afraid that today's update introduced a spurious message, emitted both
> > on package build and on chroot update:
> > "There are no foreign ar
On Sun, Jul 03, 2016 at 08:28:45PM +0200, Andreas Beckmann wrote:
> Package: openrc
> Version: 0.21-1
> Severity: serious
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
> This seems to
> @@ -430,10 +430,10 @@ check_gcc()
> -o \( $cc_maj -eq 3 -a $cc_min -lt 2 \) \
> -o \( $cc_maj -eq 4 -a $cc_min -lt 1 -a "$OS" != "darwin" \) \
> -o \( $cc_maj -eq 4 -a $cc_min -gt 9 \) \
> - -o \( $cc_maj -eq 5 -a $cc_min -gt 3 \) \
> -
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Builds of likwid 4.1 on x32 fail:
Usually, FTBFS on a non-release architecture is not a RC bug.
However, in this case, the new code is so bogus that IMHO keeping this
severity is warranted.
Yo
Package: openrc
Version: 0.20.4-2
Severity: critical
Justification: breaks unrelated software
I'm afrad the removal of diversions of /usr/sbin/{invoke,update}-rc.d
without undiverting them breaks anything that uses those scripts. This
makes many packages uninstallable:
.--===
keeps the vet away.
>From b4653519c5109967be09976e1fbf431316d07dcf Mon Sep 17 00:00:00 2001
From: Adam Borowski
Date: Tue, 8 Mar 2016 05:19:25 +0100
Subject: [PATCH] Remove dangling diverts introduced by 0.20.4-1.
---
debian/openrc.postinst | 13 +
1 file changed, 13 insertions(+
n be removed in some time, after the affected systems are fixed.
Meow!
--
A tit a day keeps the vet away.
>From b4653519c5109967be09976e1fbf431316d07dcf Mon Sep 17 00:00:00 2001
From: Adam Borowski
Date: Tue, 8 Mar 2016 05:19:25 +0100
Subject: [PATCH 1/2] Remove dangling diverts introduced by 0.20.4-1.
---
debi
On Sun, Mar 20, 2016 at 06:51:23PM +, Bas Wijnen wrote:
> That also means that programs calling dot will need graphviz in their
> Build-Depends, no matter what the default is.
As is, a number of them do call dot without the build-dependency.
> > But this is inconsistent with having graphviz i
Just lost a couple hours due to this bug.
What Vincent reported seems debatable as -c is explicitely documented as
"Read commands from the command_string operand instead of from the standard
input." which suggests the file is to be interpreted as a shell script.
But same happens for ./foo or `foo
Control: tags -1 +patch
--- libindicator-0.5.0.orig/configure.ac
+++ libindicator-0.5.0/configure.ac
@@ -66,7 +66,7 @@ AS_IF([test "x$with_gtk" = x3],
AM_CONDITIONAL(USE_GTK3, [test "x$with_gtk" = x3])
LT_LIB_M
-LIBINDICATOR_LIBS+="$LIBM"
+LIBINDICATOR_LIBS+=" $LIBM"
###
enemy.
>From b66c8027c3cb0636efd3ea26fa296b533f6606c6 Mon Sep 17 00:00:00 2001
From: Adam Borowski
Date: Thu, 21 Jul 2016 03:54:22 +0200
Subject: [PATCH] Fix FTBFS with gcc-6.
All of many errors are of only two types:
* letters after string literals, sometimes fatal: "foo"name"bar
control: tags -1 -patch
The only actual error in the copyright file that I know is claiming GPL2+
instead of GPL2 for most files.
On the other hand, the proposed patch introduces about as many serious
errors as it has entries; it's beyond worthless.
--
An imaginary friend squared is a real enem
emy.
>From 0eb439c5dc0816aa1f38150fae518818f2e03bd8 Mon Sep 17 00:00:00 2001
From: Adam Borowski
Date: Thu, 21 Jul 2016 06:36:31 +0200
Subject: [PATCH] dh 9
---
debian/bash_completion/debfoster | 41 +++
debian/compat| 2 +-
debian/control |
Package: emacsen-common
Version: 2.0.0
Severity: grave
Justification: renders package unusable
Preparing to replace emacsen-common 1.4.23 (using
.../emacsen-common_2.0.0_all.deb) ...
emacsen-common: Handling removal of emacsen flavor emacs
emacsen-common: Handling removal of emacsen flavor emacs2
On Mon, May 14, 2012 at 02:44:37PM +0200, Agustin Martin wrote:
> On Mon, May 14, 2012 at 01:12:45PM +0200, Adam Borowski wrote:
> > chdir /usr/lib/emacsen-common/packages/install: No such file or directory
> > at /usr/lib/emacsen-common/lib.pl line 27.
>
> May this be r
An update, builds with gold this time.
Untested, can't actually run it until today's evening.
The patch just sprinkles -lfoo all around without thinking what are the
nicest places. That works for a quick-and-dirty patch, but as I understand,
you'll update to compiz 0.9 later anyway so there's no
Here's an untested patch. Lacks either a Build-Conflicts:binutils-gold or a
proper fix.
--
1KB // Yo momma uses IPv4!
diff -Nurd compiz-0.8.4.orig/debian/compiz-gnome.install compiz-0.8.4/debian/compiz-gnome.install
--- compiz-0.8.4.orig/debian/compiz-gnome.install 2011-10-25 11:45:5
Of course, the "updated" patch is the good one, they got reversed in the BTS
due to greylisting.
--
1KB // Yo momma uses IPv4!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: fp-compiler
Version: 2.4.2-1
Severity: grave
Justification: renders package unusable
Any program compiled by new fpc, even just "begin end.", crashes on startup:
[/tmp]$ fpc hello.pas
Free Pascal Compiler version 2.4.2-1 [2011/03/30] for x86_64
Copyright (c) 1993-2010 by Florian Klaempfl
On Tue, Apr 05, 2011 at 12:50:25PM +0200, Abou Al Montacir wrote:
> I was not able to reproduce this, can you please ensure you have the
> correct /etc/fpc.cfg file as there is a know issue when upgrading.
>
> Please provide the output of "ls /etc/fpc.cfg"
/etc/fpc.cfg -> /etc/alternatives/fpc.cf
On Tue, Apr 05, 2011 at 02:47:31PM +0200, Abou Al Montacir wrote:
> Every thing looks correct on your system.
>
> Can you please send me the output of "aptitude show binutils"?
[~]# dpkg -l 'binutils*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-
The missing file is in texlive-latex-recommended these days.
--
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets. Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your wr
Hi, Jakob!
Do you still intend to take over tcng? You ITA-ed it in September.
There's more and more bitrot, this time a FTBFS due to changes in LaTeX.
Could you tell me whether you:
a) would take it over soon?
(ie, nothing for me to do)
b) take it later, but before Wheezy freezes?
(ie, I
Package: lletters
Version: 0.1.95+gtk2-3.1
Severity: grave
Justification: renders package unusable
On systems that don't have OSS installed and configured, pressing any
button that has an attached sound, causes a crash.
Since no linux kernel shipped in wheezy has OSS built, this makes the
packag
On Sun, Mar 17, 2013 at 05:20:13PM -0400, Michael Gilbert wrote:
> I'm also seeing this. Can you install oss4 and see if that fixes it?
With oss4, no sound is produced, and it hangs, but this appears to be
#701852.
> If so, the easiest solution is to just add a dependency on that.
It'd be quite
On Mon, Mar 18, 2013 at 09:15:16PM +0100, Stephen Kitt wrote:
> Hi,
>
> On Mon, Mar 18, 2013 at 02:47:47PM +, Steven Chamberlain wrote:
> > On 17/03/13 19:35, Adam Borowski wrote:
> > > On systems that don't have OSS installed and configured, pressing any
>
On Tue, Mar 26, 2013 at 03:06:09AM +, Debian Bug Tracking System wrote:
> Source: lletters
> Version: 0.1.95+gtk2-3.2
> .
>* Non-maintainer upload.
>* Add oss-compat dependency (closes: #703265).
I'm afraid this doesn't fix the bug, merely workarounds it in some cases.
It does change
Wheezy has stable Icedove 10, rather than one of later snapshots (I kind of
refuse to call them releases). Thus, if you have an incompatible version of
it, you have non-wheezy apt sources anyway.
It would be nice to have a newer version of firetray, but only if it works
with Icedove 10 as well.
For some history, please read
https://en.wikipedia.org/wiki/Statute_of_Monopolies_1623
>From bd1eb33d577e3aadf3d71666d665eaac5ca7d2af Mon Sep 17 00:00:00 2001
From: Adam Borowski
Date: Thu, 12 Jul 2012 02:36:02 +0200
Subject: [PATCH] Resolve a conflict between X11 Region and kdecoration
Regi
Could you please elaborate what exactly is the problem with compiz 0.8?
It works well; I use it at home (currently with xfce) and the only problem is
remembered window positions being wrong on startup.
At least the situation is worlds better than the current state of certain
other window managers
Works for me, both with gtk-window-decorator and emerald. On amd64, like
you.
> compiz: symbol lookup error: /usr/lib/compiz/libdecoration.so: undefined
> symbol: decor_property_to_quads
There are two libraries with nearly the same file name:
/usr/lib/compiz/libdecoration.so (package compiz-plu
On Sat, Jul 14, 2012 at 12:54:00AM -0600, G. Pablo Vanwoerkom wrote:
> Well, I did install compiz manually and since it didn't have "make
> uninstall", I had to uninstall manually as well.
>
> However, I think this behavior was my motivation to try to install compiz
> manually. Anyways, I removed
Package: libdbd-sqlite3-perl
Version: 1.40-1+b1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I'm afraid that your package fails to build with new sqlite3, the failing
test is:
t/53_status.t ... 1/?
# Failed test '
Package: bzr
Version: 2.6.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I'm afraid that bzr fails a number of tests, all under
bzrlib.plugins.netrc_credential_store.tests.test_netrc.TestNetrcCS
It was first seen on the x32 buildd:
http://bui
Hi!
Per the discussion upstream (https://savannah.gnu.org/bugs/?38474):
* it had been already announced, in 2005
* it goes contrary to the wording in POSIX
* the upstream change for this report was to give an error message
rather than to reinstate the behaviour
Since then, dh_shlibdeps has bee
Hi!
I was about to report this too, I was finishing checks prior to submission.
It appears that it does _not_ fail to build on amd64, but it does on i386
and x32 (on the latter after a patch I'm about to send).
--
ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.
Package: dpkg
Version: 1.16.3
Severity: grave
Justification: renders package unusable
After an interrupted dpkg run, any subsequent invocation fails with:
dpkg: error: libc6-dev:armel (Multi-Arch: no) is not co-installable
with libc6-dev which has multiple installed instances
This affects not o
Package: apt-cacher-ng
Version: 0.7.19-1
Severity: serious
After manually nuking the whole cache (troubleshooting an unrelated bug):
[] Starting apt-cacher-ng: apt-cacher-ngCache directory not writable. Check
the permissions of /var/cache/apt-cacher-ng!
failed!
This fails a "must" clause o
Hi!
Is there a reason not to NMU for this bug? It's a trivial issue.
--
⢎⣉⠂⠠⠤⡀⣄⠤⡀⠠⡅⠀⠤⡧⠄⡄⠀⡄⠀⠀⠀⠠⡅⠀⡠⠤⠄⠀⠀⠀⢴⠍⠀⡠⠤⡀⣄⠤⡀⠀⠀⠀⠤⡧⠄⣇⠤⡀⡠⠤⡀⠀⠀⠀⡄⠀⡄⡠⠤⡀⠠⠤⡀⡇⡠⠄⠀⠀⠀
⠢⠤⠃⠪⠭⠇⠇⠀⠇⠀⠣⠀⠀⠣⠄⠨⠭⠃⠣⠀⠬⠭⠂⠀⠀⠀⠸⠀⠀⠣⠤⠃⠇⠀⠀⠣⠄⠇⠀⠇⠫⠭⠁⠀⠀⠀⠣⠣⠃⠫⠭⠁⠪⠭⠇⠏⠢⠄⠀⠄⠀
(https://github.com/kilobyte/braillefont for this hack)
Package: kernel-common
Version: 13.015
Severity: grave
Justification: renders package uninstallable
Unpacking kernel-common (13.015) over (13.014+nmu3) ...
dpkg: error processing archive
/var/cache/apt/archives/kernel-common_13.015_all.deb (--unpack):
unable to open
'/usr/share/kernel-common/e
There's no separate QA team, everyone of us is a "member".
You, as the former maintainer, are the person best informed about this
package. And if you say it should be removed instead of trying to fix --
let's do so.
--
A tit a day keeps the vet away.
Package: init-system-helpers
Version: 1.25
Severity: serious
Justification: Policy 7.4
Hi!
Unpacking init-system-helpers (1.25) over (1.24) ...
dpkg: error processing archive
/var/cache/apt/archives/init-system-helpers_1.25_all.deb (--unpack):
trying to overwrite '/usr/sbin/update-rc.d', which
On Tue, Jan 26, 2016 at 11:29:07AM +1100, Brian May wrote:
> python3-click has checks to ensure it is called with a non-ASCII
> locale. Or if it is an ASCII locale, it raises a fatal error. Or at
> least it tries to raise a fatal error.
[...]
> The problem is that when building djangorestframework,
On Tue, Jan 26, 2016 at 11:57:17AM +1100, Brian May wrote:
> Adam Borowski writes:
> > My guess as to the cause of #812672 is that you have LC_CTYPE or LC_ALL set
> > to an ancient locale. These variables override LANG, the order is
> > LC_ALL>LC_CTYPE>LANG.
>
* Remove DM-Upload-Allowed.
+
+ -- Adam Borowski Tue, 26 Jan 2016 13:52:27 +0100
+
insserv (1.14.0-5) unstable; urgency=low
* Add +mountall-bootclean to $local_fs virtual facility definition in
diff -Nru insserv-1.14.0/debian/control insserv-1.14.0/debian/control
--- insserv-1.14.0/debi
Control: notfixed -1 2.76.b+dfsg0-1
Control: reopen -1
Hi!
I'm afraid that your upload to experimental, despite claiming in the
changelog that it doesn't use the droid font anymore, still has
Depends: fonts-droid. I guess you changed the code without updating
debian/control.
Also, please remove
> init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d
Uhm, guys... are you alive? This bug keeps openrc uninstallable, and will
cause its autoremoval soon.
If you're too busy and need help, I could help with fixing or NMUing, but
you need to decide whether to:
* cooperate with
ckage: source changed by Adam Borowski
dpkg-source --before-build wimlib-1.8.3
fakeroot debian/rules clean
dh clean --with=autoreconf --parallel
dh_testdir -O--parallel
dh_auto_clean -O--parallel
dh_autoreconf_clean -O--parallel
dh_clean -O--parallel
dpkg-source -b wimlib-1.8.3
dpkg-s
On Fri, Feb 12, 2016 at 12:47:09AM +0900, Benda Xu wrote:
> Thanks for the report. update-rc.d in OpenRC is a hack based on that
> from sysv-rc. I think the right way forward is to extend
> init-system-helpers to support OpenRC.
Great, that answers the question about which way to fix the bug. T
Control: tags -1 +unreproducible moreinfo
Hi!
I can't seem to reproduce this FTBFS. And it doesn't appear to be possible:
=
typedef const char Row[10];
typedef const Row Map[15];
void
internalParse( const char* line, const char
Package: nyancat-server
Version: 1.5.1-1
Severity: grave
Justification: renders package unusable
[~]# netstat -anp|grep :23
[~]#
As that's the only stated purpose of this package, I'm setting severity to
grave.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT pol
Package: libnih1
Version: 1.0.3-4.3
Severity: grave
Justification: renders package unusable
Hi!
I'm afraid today's upload of libc6 2.21 made libnih1 uninstallable.
It Depends: libc6 (>> 2.19), libc6 (<< 2.20).
As Ubuntu has libc6 2.21 since vivid, it's a matter of pulling the fixes
from upstream.
On Fri, Dec 04, 2015 at 05:09:30AM -0800, Nigra Truo wrote:
>* What led up to the situation?
> Starting up the system normally, with X11. The panic often seems to occur
> when several windows are open or when maximizing a window.
>* What exactly did you do (or not do) that was effective (or
-1,3 +1,10 @@
+crtmpserver (1.0~dfsg-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Don't hard-code dependencies (Closes: #794724).
+
+ -- Adam Borowski Sun, 25 Oct 2015 13:14:05 +0100
+
crtmpserver (1.0~dfsg-5) unstable; urgency=low
* Update the kfreebsd platfor
Hi!
I've uploaded (with Thijs Kinkhorst) a NMU for this bug to DELAYED/3.
No changes other than the removal of hardcoded library dependencies.
Please shout if there's some reason you'd like to abort this NMU.
--
⢎⣉⠂⠠⠤⡀⣄⠤⡀⠠⡅⠀⠤⡧⠄⡄⠀⡄⠀⠀⠀⠠⡅⠀⡠⠤⠄⠀⠀⠀⢴⠍⠀⡠⠤⡀⣄⠤⡀⠀⠀⠀⠤⡧⠄⣇⠤⡀⡠⠤⡀⠀⠀⠀⡄⠀⡄⡠⠤⡀⠠⠤⡀⡇⡠⠄⠀⠀⠀
⠢⠤⠃⠪⠭⠇⠇⠀⠇⠀⠣⠀⠀⠣
Package: src:libtecla
Version: 1.6.1-5
Severity: critical
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid that libtecla FTBFS in an extremely unpleasant way, killing the
buildd machine unless you somehow limit memory available to the build (AFAIK
none
> 5. Press Ctrl-C when waiting for /dev to be populated (seems to be an
>unrelated bug)
This is the cause. If you let it settle, everything works ok.
I was able to reproduce your bug at around 50% rate on a slow VM, by
pressing ^C right away when this message appears.
So it seems it's a bug
Control: retitle -1 shit happens if you interrupt important parts of boot
Control: severity -1 important
Oif, this was a _nasty_ case of BTS ping-pong. Thus, I've taken the liberty
of using semi-profanity in the title, its use is warranted :p
But really, we have two bugs here:
* udev takes ages
Package: iproute2
Version: 3.9.0-3
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
Hi!
As iproute2 builds with -Werror, new warnings that came up with gcc-4.8
(the new default on x86 and arm architectures) make it FTBFS.
lnstat.c: In f
On Fri, May 16, 2014 at 09:36:35PM +1000, Aníbal Monsalve Salazar wrote:
> My NMU patch for kbtin_1.0.14-1.1 is below, at the end of this
> message.
Looks like there's some work duplication: yesterday I prepared an upload
fixing this and also a bunch of other problems, and sent a request to
Bartos
On Fri, Aug 15, 2014 at 12:33:35AM +0200, Andreas Henriksson wrote:
> I fail to see any argument on why this is not already resolved.
Suspend and hibernate don't work if upower is upgraded, duh.
> On Mon, Aug 11, 2014 at 12:00:16AM +0200, Adam Borowski wrote:
> [...]
> > It
Package: octave-odepkg
Version: 0.8.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I'm afraid that your package fails to build on current unstable (tested on
armhf and amd64). The interesting part of the log is:
FFLAGS=-g -O2 -fstack-protect
A new version of upower packages came up -- so I just retested.
On Fri, Aug 15, 2014 at 10:30:28PM +0200, Andreas Henriksson wrote:
> On Fri, Aug 15, 2014 at 02:22:38AM +0200, Adam Borowski wrote:
> > On Fri, Aug 15, 2014 at 12:33:35AM +0200, Andreas Henriksson wrote:
> > >
reopen 747105
kthxbye
> non-sense.
Per the policy, severity for "breaks unrelated software" is "critical".
Thus, this bug is valid.
Please explain to me why a wrapper that executes, among others, "pm-suspend"
or "halt", would be related to an init system? Especially if those commands
(which in
Package: src:salt
Version: 2014.1.7+ds-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
During a rebuild of the archive on armhf, I'm afraid your package repeatedly
failed to build. It hangs forever, with tail part of the output being:
Making ou
reopen 754850
notfound 745850 4.10.1-6
found 745850 4.10.1-7
kthxbye
I'm afraid transiting to upower 0.99 does not fix this bug -- in fact,
it's its very cause (that's why I reported this against upower not
xfce4-session). As you can easily check, a non-systemd setup will not
allow suspend or hib
Package: polipo
Version: 1.0.4.1-5
Severity: grave
When attempting to upgrade or uninstall+install:
Setting up polipo (1.0.4.1-5) ...
Starting polipo: Couldn't open log file /var/log/polipo: Is a directory
invoke-rc.d: initscript polipo, action "start" failed.
That directory gets recreated even i
On Fri, Jan 17, 2014 at 01:25:28PM +0800, Rolf Leggewie wrote:
> On 17.01.2014 11:47, Adam Borowski wrote:
> > When attempting to upgrade or uninstall+install:
> > Setting up polipo (1.0.4.1-5) ...
> > Starting polipo: Couldn't open log file /var/log/polipo: Is a
Package: src:bzr
Version: 2.6.0-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I'm afraid that bzr randomly (7/8 tries) FTBFSes due to a failure of one
test on speedier machines:
=
On Tue, Jan 21, 2014 at 02:58:34AM +0100, Andreas Beckmann wrote:
> I built this locally before uploading 331.38-1 to experimental - the
> nvidia kernel module builds successfully on every official Debian kernel
> header package from squeeze to experimental including backports
Thanks!
> but of co
301 - 381 of 381 matches
Mail list logo
