On Wed, 2009-11-11 at 16:37:15 +0100, Stefano Zacchiroli wrote:
> Package: dpkg-dev
> Version: 1.15.4.1
> Severity: wishlist
> File: /usr/bin/dpkg-gencontrol
> It would be nice to have support for a Description field in the source
> stanza of debian/control.
> 1) Various pieces of Debian infrastr
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package kup
The upload service at kernel.org will soon be changed in a way that is
incompatible with the current kup client. The changes in unstable add
support for this new
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
The upload service at kernel.org will soon be changed in a way that is
incompatible with the current kup client. The changes below add
support for this new configuration, and have b
On Fri, 31 Mar 2017 09:18:06 +0200 Sebastian Andrzej Siewior wrote:
> On 2017-03-30 22:45:57 [+0100], Ben Hutchings wrote:
> > Upgrading severity as it would be pointless to release with this
> > version.
>
> Sure. And probably something for current stable, I don't know. Should we
> ask on users@
I've now had a chance to try the encode with the same source and command
line on the official release 1.0.3 CLI binary for OSX and it does not have
the problem with the Closed Captioning track and mkv output, so that looks
like a smoking gun that this is a library version/packaging issue.
Package: aptitude
Version: 0.8.6-1
Severity: normal
Hi,
I just ran into a corner case which causes a crash of aptitude:
→ env LANG=foobar aptitude changelog aptitude
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
[1
On Mon, Jan 09, 2017 at 06:03:03PM +0100, Thorsten Glaser wrote:
> Source: heimdal
> Version: 7.1.0+dfsg-3
> Severity: important
> Tags: patch
> Justification: fails to build from source (but built successfully in the past)
Hello,
What is that status of this bug? I see that there was a change com
Fixing this for upgrades from jessie to stretch requires a jessie update
as well, to dump out the databases upon remove.
The patches I intend to submit are attached. I would appreciate it a lot
if anyone reading this could take the time to review and try to point
out any edge cases I missed.
Date: Sat, 18 Mar 2017 23:38:24 0100
>From: Ivo De Decker
>-
>Body: ur-type{header=Received: (at submit) by bugs.debian.org; 8 Mar 2017
>14:36:50
>From a...@debian.org Wed Mar 08 14:36:50 2017
>X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02
>
Thanks, Andreas.
The html link and your mail both suggest the same approach. But when I do
this and build new 3.11.10 packages and try to upgrade a system with 3.11.9
installed using the same recipe I've been using for decades, namely
# dpkg -i *.deb
in the directory where all the new pac
101 - 110 of 110 matches
Mail list logo
