Your message dated Sat, 03 Jan 2015 07:33:30 +
with message-id
and subject line Bug#774376: fixed in docker.io 1.3.3~dfsg1-2
has caused the Debian Bug report #774376,
regarding when run with old kernel, docker exec silently uses real root
filesystem as container filesystem
to be marked as don
Processing commands for cont...@bugs.debian.org:
> retitle 77 pepperflashplugin-nonfree: please support apt 1.2
Bug #77 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: apt 1.2
breaks pepperflashplugin-nonfree (1.8.1)
Changed Bug title to 'pepperflashplugin-nonfree: please support a
Your message dated Sat, 03 Jan 2015 00:48:34 +
with message-id
and subject line Bug#774424: fixed in trac-subcomponents 1.2.0+hga86f0413121f-4
has caused the Debian Bug report #774424,
regarding trac-subcomponents: Trac query broken with this plugin enabled
to be marked as done.
This means th
Dom Noble wrote:
> So I notice this bug has been reported as fixed, but i tried to do a
> apt-get upgrade over crimbo and my dpkg seems to be throwing the same
> fault in dovecot-core (1:2.2.13-11),
As I read your report it is returning an error. Bug#770695 is about a
hang during installation. Y
Hi,
On Fri, Jan 02, 2015 at 12:04:49AM +1100, Russell Sim wrote:
> > Also, please note that most of the changes in the latest uploads probably
> > don't comply with the freeze policy. If you think they do, you need to file
> > an
> > unblock request explaining why (including a debdiff).
> >
> > h
So I notice this bug has been reported as fixed, but i tried to do a
apt-get upgrade over crimbo and my dpkg seems to be throwing the same
fault in dovecot-core (1:2.2.13-11), so far I have spent a day trying to
fix this but with no luck, the init script is throwing exit code 1 which
i can see from
Package: pepperflashplugin-nonfree
Version: 1.8.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Installing apt 1.2 prevents `update-pepperflashplugin-nonfree --install`
from either updating apt or working with the cache, and breaks the current
flash
install.
The last o
Processing commands for cont...@bugs.debian.org:
> severity 774212 serious
Bug #774212 [ifupdown] ifupdown: segfault when misssing read access on
/etc/network/interfaces
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
77421
Processing control commands:
> severity -1 important
Bug #770153 [gedit] gedit segfaults when one tries to extend "tools-section"
after extending "preferences-section"
Severity set to 'important' from 'grave'
--
770153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770153
Debian Bug Tracking
control: severity -1 important
Since this has a workaround, which is used by all known gedit plugins
shipped in Debian, and since it doesn't look like upstream is working
on a fix, this really isn't release critical.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.de
On Fri, Jan 2, 2015 at 1:44 PM, John Paul Adrian Glaubitz
wrote:
> So, unless the changes to fix issues with the new flickr API are
> trivial, chances are very low that 'dfo' can be fixed for Jessie.
If someone has time, a quick search/replace of "http" for "https" in
the code might be worth an a
Package: ovirt-guest-agent
Version: 1.0.10.2.dfsg-1
Severity: serious
It hardcodes them as 175. The uid was not taken, but the gid was so the
package installation failed. Funnily enough, I was trying to fix
#767028 at the time.
Best regards,
--
Cameron Norman
On Sat, Nov 15, 2014 at 5:59 PM, Pino Toscano wrote:
> On 2014-11-15 22:57, Simon McVittie wrote:
>>
>> Control: tags 767659 + patch
>>
>> On Tue, 11 Nov 2014 at 10:33:42 +, Simon McVittie wrote:
>>>
>>> If the new symbol is public API that (in principle) other packages could
>>> use, which AFA
Your message dated Fri, 02 Jan 2015 19:18:34 +
with message-id
and subject line Bug#773085: fixed in xdg-utils 1.1.0~rc1+git20111210-7.2
has caused the Debian Bug report #773085,
regarding xdg-utils: command injection vulnerability
to be marked as done.
This means that you claim that the prob
On Thu, 1 Jan 2015 09:16:16 +1100 Martin Schwenke
wrote:
> Package: ctdb
> Version: 2.5.4+debian0-3
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> # systemctl start ctdb
> Failed to start ctdb.service: Unit ctdb.service failed to load: No
such file or direc
On Thu, Dec 11, 2014 at 3:52 PM, Guillem Jover wrote:
> A solution to the above is to simply switch the triggers to their
> noawait variants, in this case from «interest» to «interest-noawait»,
> as long as they are not critical for the activating packages, which I
> cannot tell here. Otherwise a f
Hi Jeremy!
>From the upstream website [1]:
"NOTE: This project is no longer under active development, please
contact the administrator if you're interested in taking it over."
So, unless the changes to fix issues with the new flickr API are
trivial, chances are very low that 'dfo' can be fixed f
Your message dated Fri, 02 Jan 2015 18:33:31 +
with message-id
and subject line Bug#772873: fixed in auctex 11.88-1.1
has caused the Debian Bug report #772873,
regarding auctex: Trigger cycle causes dpkg to fail processing
to be marked as done.
This means that you claim that the problem has b
Your message dated Fri, 02 Jan 2015 17:48:23 +
with message-id
and subject line Bug#773191: fixed in pyogg 1.3+repack-7
has caused the Debian Bug report #773191,
regarding python-ogg-dbg: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> tag 773191 + pending
Bug #773191 [python-ogg-dbg] python-ogg-dbg: unhandled symlink to directory
conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
773191: ht
On 1 January 2015 at 12:49, Joey Hess wrote:
> Just to be clear, my intent was not to use docker with an old kernel.
> I was just deploying a system whose configuration included docker,
> and since docker started up despite the old kernel version, it was used
> as part of the deployment.
>
> This
Your message dated Fri, 02 Jan 2015 16:18:36 +
with message-id
and subject line Bug#772365: fixed in simpleburn 1.7.0-2
has caused the Debian Bug report #772365,
regarding simpleburn: bashism in /bin/sh script
to be marked as done.
This means that you claim that the problem has been dealt wit
Hello Michael!
> Hi, since this hasn't happened yet, I went ahead and uploaded a fixed
> package to delayed/5. Please feel free to override with a maintainer
> upload.
Thanks for your help! I am Mateusz' sponsor and I was just about to go
ahead and review and upload the package. Please remove yo
Package: trac-subcomponents
Version: 1.2.0+hga86f0413121f-3
Severity: grave
Tags: patch, upstream
grave, because it makes the package in question mostly unusable
Trac queries don't work anymore, if this plugin is installed and enabled.
One gets a Python exception:
"UnicodeError: source returned
On 31/12/14 10:00, Simon McVittie wrote:
> On Mon, 29 Dec 2014 at 21:27:16 +, Debian Bug Tracking System wrote:
>> libical (1.0-1.2) unstable; urgency=medium
>> .
>>* Non-maintainer upload.
>>* Sort keys to generate reproducible source code. (Closes: #773916)
>
> This is enough to ma
Your message dated Fri, 2 Jan 2015 15:14:31 +0100
with message-id <20150102141430.ga1...@mail.waldi.eu.org>
and subject line Re: Bug#774419: Acknowledgement (ferm - dependency cycle with
basic.target under systemd)
has caused the Debian Bug report #774419,
regarding ferm - dependency cycle with ba
Package: ferm
Version: 2.2-3
Severity: grave
ferm fails to start under systemd. systemd reports a dependency cycle:
| systemd[1]: Job ferm.service/start deleted to break ordering cycle starting
with basic.target/start
ferm is not started in this case and the system is left without a packet
filte
Your message dated Fri, 02 Jan 2015 12:41:15 +
with message-id
and subject line Bug#774307: Removed package(s) from unstable
has caused the Debian Bug report #765127,
regarding openvas-libraries: FTBFS: build-dependency not installable:
libgnutls-dev
to be marked as done.
This means that you
Your message dated Fri, 02 Jan 2015 12:41:15 +
with message-id
and subject line Bug#774307: Removed package(s) from unstable
has caused the Debian Bug report #695439,
regarding Unfit for Wheezy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Fri, 02 Jan 2015 12:40:16 +
with message-id
and subject line Bug#767610: Removed package(s) from unstable
has caused the Debian Bug report #737921,
regarding [TLS1.2] gnutls only likes SHA1 and SHA256 certificates
to be marked as done.
This means that you claim that the pro
Your message dated Fri, 02 Jan 2015 12:40:16 +
with message-id
and subject line Bug#767610: Removed package(s) from unstable
has caused the Debian Bug report #760735,
regarding libgnutls26: [dummy bug] Must not be shipped in jessie
to be marked as done.
This means that you claim that the prob
Your message dated Fri, 02 Jan 2015 12:40:16 +
with message-id
and subject line Bug#767610: Removed package(s) from unstable
has caused the Debian Bug report #768014,
regarding libgnutls-dev: not installable in sid
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Fri, 02 Jan 2015 12:40:16 +
with message-id
and subject line Bug#767610: Removed package(s) from unstable
has caused the Debian Bug report #737921,
regarding gnutls unusable with cacert SHA2-512 sigs
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 Jan 2015 12:27:10 +
with message-id
and subject line Bug#774306: Removed package(s) from unstable
has caused the Debian Bug report #765133,
regarding libvmime: FTBFS: build-dependency not installable: libgnutls-dev (>=
1.2.0)
to be marked as done.
This means that y
Your message dated Fri, 02 Jan 2015 12:27:10 +
with message-id
and subject line Bug#774306: Removed package(s) from unstable
has caused the Debian Bug report #706332,
regarding libvmime0: Not ABI compatible with version in squeeze
to be marked as done.
This means that you claim that the probl
Your message dated Fri, 02 Jan 2015 12:25:30 +
with message-id
and subject line Bug#774292: Removed package(s) from unstable
has caused the Debian Bug report #746088,
regarding scilab-metanet: FTBFS: cp: cannot stat 'debian/tmp/loader.sce': No
such file or directory
to be marked as done.
Thi
Your message dated Fri, 02 Jan 2015 12:26:23 +
with message-id
and subject line Bug#774304: Removed package(s) from unstable
has caused the Debian Bug report #746087,
regarding centerim: FTBFS: libgadu.h:53:28: fatal error: gnutls/openssl.h: No
such file or directory
to be marked as done.
Th
Your message dated Fri, 02 Jan 2015 12:26:23 +
with message-id
and subject line Bug#774304: Removed package(s) from unstable
has caused the Debian Bug report #559783,
regarding centerim embeds libgadu, libyahoo2, libmsn, others?
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 02 Jan 2015 12:26:23 +
with message-id
and subject line Bug#774304: Removed package(s) from unstable
has caused the Debian Bug report #549098,
regarding Please stop build depending on automake1.4
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 Jan 2015 12:26:23 +
with message-id
and subject line Bug#774304: Removed package(s) from unstable
has caused the Debian Bug report #549098,
regarding Please stop build depending on automake1.4
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 02 Jan 2015 12:23:57 +
with message-id
and subject line Bug#774307: Removed package(s) from unstable
has caused the Debian Bug report #723655,
regarding package depends on libgd2-noxpm or libgd2-xpm, neither of which are
available
to be marked as done.
This means that
Your message dated Fri, 02 Jan 2015 12:23:57 +
with message-id
and subject line Bug#774307: Removed package(s) from unstable
has caused the Debian Bug report #695441,
regarding Unfit for Wheezy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Your message dated Fri, 02 Jan 2015 12:24:46 +
with message-id
and subject line Bug#774042: Removed package(s) from unstable
has caused the Debian Bug report #747797,
regarding totem-plugin-arte: FTBFS: error: The name `action_error' does not
exist in the context of `Totem.Object'
to be marke
Your message dated Fri, 02 Jan 2015 12:21:39 +
with message-id
and subject line Bug#774307: Removed package(s) from unstable
has caused the Debian Bug report #688379,
regarding openvas-server: modifies conffiles (policy 10.7.3):
/etc/openvas/openvasd.conf
to be marked as done.
This means tha
Your message dated Fri, 02 Jan 2015 12:16:06 +
with message-id
and subject line Bug#774307: Removed package(s) from unstable
has caused the Debian Bug report #733392,
regarding openvas-libnasl: FTBFS: nasl_grammar.tab.c:1554:7: error: too few
arguments to function 'nasllex'
to be marked as do
Your message dated Fri, 02 Jan 2015 12:16:06 +
with message-id
and subject line Bug#774307: Removed package(s) from unstable
has caused the Debian Bug report #695440,
regarding Unfit for Wheezy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Hi Sandro,
On Sun, 21 Dec 2014 10:50:15 + Sandro Tosi wrote:
> Hi Jean-Michel,
> Thanks for your work, I will fix the package soon from dpmt repo; and yes
> the right solution is to use dpkg maint scripts to fix the dir-link
> transition.
Any update on this? pyogg is showing up on the releas
Hi Ricardo,
I've attached a full debdiff (in the form of a NMU), which I haven't
uploaded yet (but I'm happy to upload this if you have no objections).
As for how to test it, well, I'm not an expert when it comes to
piuparts, but I was able to reproduce the original error with:
# piuparts -m 'htt
48 matches
Mail list logo
