-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 04 Jan 2017 08:17:08 +0100
Source: sbuild
Binary: libsbuild-perl sbuild buildd
Architecture: source
Version: 0.73.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian buildd-tools Developers
Am Montag, den 02.01.2017, 10:16 +1100 schrieb Ben Finney:
> On 08-Jul-2015, Tobias Frost wrote:
>
> > I'd love to use both dput and dput-ng without the need of
> > installing
> > the version I'd use next..
>
> As discussed briefly in the thread from 2016-12, my counter-proposal
> is that the
❦ 4 janvier 2017 04:52 GMT, Scott Kitterman :
>>> It's surprisingly awkward, and, at least for me, it turns out that
>>> externalizing my rebased branch as a patch series solves many of
>>> problems surprisingly well. All the other solutions I can think of
>>> require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 04 Jan 2017 14:32:30 +0800
Source: ruby-jeweler
Binary: ruby-jeweler
Architecture: source all
Version: 2.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 04 Jan 2017 07:19:25 +0100
Source: nagios-images
Binary: nagios-images
Architecture: source all
Version: 0.9.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 04 Jan 2017 07:22:53 +0100
Source: libio-socket-ssl-perl
Binary: libio-socket-ssl-perl
Architecture: source
Version: 2.041-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Nikolaus Rath writes:
> On Jan 03 2017, Russ Allbery wrote:
>> Speaking as a Debian user who frequently has to apply local patches or
>> produce local versions of Debian packages for my job (usually weird
>> backports or bizarre local requirements), I cannot
On Wed, Jan 4, 2017 at 1:30 PM, Nikolaus Rath wrote:
> But I am not sure if a package structure like
>
> mypkg/upstream/*
> mypkg/debian/*
> mypkg/patches/* (?)
>
> would have any *practical* benefits over the current situation, because
> this transformation could be trivially automated in either
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Dec 2016 12:00:00 +1100
Source: pcp
Binary: pcp pcp-conf libpcp3-dev libpcp3 libpcp-gui2-dev libpcp-gui2
libpcp-mmv1-dev libpcp-mmv1 libpcp-pmda3-dev libpcp-pmda3 libpcp-trace2-dev
libpcp-trace2 libpcp-import1-dev
On January 4, 2017 12:33:43 AM EST, Nikolaus Rath wrote:
>On Jan 03 2017, Russ Allbery wrote:
>> Nikolaus Rath writes:
>>
>>> The thing that's delivered to users in 99% of the cases is the
>binary
>>> package. In the (comparatively) rare
On Jan 03 2017, Russ Allbery wrote:
> Nikolaus Rath writes:
>
>> The thing that's delivered to users in 99% of the cases is the binary
>> package. In the (comparatively) rare cases where the user is retrieving
>> the source, I am not convinced that most of
On Jan 04 2017, Paul Wise wrote:
> On Mon, Jan 2, 2017 at 1:21 AM, Guillem Jover wrote:
>
>> I'm interested in what things people still find so off-putting to the
>> point of not wanting to use the new 3.0 source formats.
>
> I've been reading this thread and keep being reminded
On Wed, 2017-01-04 at 14:47 +1000, Russell Stuart wrote:
> The central
issue here appears to be that none of the proposed ways
> of using git
within Debian help with that task.
On Wed, 2017-01-04 at 04:42 +, Colin Watson wrote:
>
> git-dpm does too, and I agree it's nice.
>
> It produces a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 29 Dec 2016 23:23:44 -0500
Source: sysdig
Binary: sysdig sysdig-dkms
Architecture: source
Version: 0.13.0-1
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov
Changed-By: Harlan Lieberman-Berg
On January 3, 2017 10:22:22 PM EST, Nikolaus Rath wrote:
>On Jan 03 2017, Russ Allbery wrote:
>> It's surprisingly awkward, and, at least for me, it turns out that
>> externalizing my rebased branch as a patch series solves many of
>these
>> problems
On Tue, 2017-01-03 at 18:37 -0800, Russ Allbery wrote:
> Even if we never used tarballs, and instead our unit of operation was
> the upstream Git repository plus Debian branches, I would maintain a
> rebased branch of Debian changes to upstream
This is not a novel requirement. Most projects I've
On Tue, Jan 03, 2017 at 07:36:46PM -0800, Russ Allbery wrote:
> That said, gbp pq does something else I really like, namely it exports in
> the source package all of the metadata that anyone else would need to pick
> up the package without needing a copy of my Git repository (except for
>
Nikolaus Rath writes:
> The thing that's delivered to users in 99% of the cases is the binary
> package. In the (comparatively) rare cases where the user is retrieving
> the source, I am not convinced that most of these users truly prefer a
> Debian-specific source package
Nikolaus Rath writes:
> When talking about percentages, I think it's worth keeping in mind the
> 1000% longer that it takes to comprehend a diff of two patches-unapplied
> trees (as gbp produces them) over a diff of two patches-applied trees
> (as git-dpm and dgit with
On Mon, Jan 2, 2017 at 1:21 AM, Guillem Jover wrote:
> I'm interested in what things people still find so off-putting to the
> point of not wanting to use the new 3.0 source formats.
I've been reading this thread and keep being reminded of our
discussion on #debian-dpkg a while ago.
I think
Nikolaus Rath writes:
> Are there really upstreams that do that? I'd expect that the primary
> consumer of Debian patches are other distributions, downstreams, and
> users.
> I'd think that anything that's relevant for upstream development is
> forwarded to upstream by the
On Jan 03 2017, Russ Allbery wrote:
> It's surprisingly awkward, and, at least for me, it turns out that
> externalizing my rebased branch as a patch series solves many of these
> problems surprisingly well. All the other solutions I can think of
> require one or more things I
On Jan 03 2017, Ian Jackson wrote:
> Recently, my nm-applet can no longer control my network-manager
> daemon. I get a message saying[1]:
>
> "org.freedesktop.NetworkManager.network-control-request failed: not
> authorized"
>
> I think this is related to a
On Wed, Jan 4, 2017 at 2:54 AM, Russ Allbery wrote:
> Well, if we had one more thing: a patches.debian.org service that would
> show the git-debcherry-extracted patches against upstream. I really like
> being able to just point upstream at all the patches relevant to them that
> Debian has
On Jan 04 2017, Scott Kitterman wrote:
>>Curating a patch series is only 5% slower than commiting directly to
>>the Git repository to me. I just have to remember to gbp pq import
>>before making new changes, gbp pq export when I'm done, and once in a
>>great while I have to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 04 Jan 2017 10:03:03 +0800
Source: autorevision
Binary: autorevision
Architecture: source
Version: 1.20-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Wise
Changed-By: Paul Wise
On Jan 03 2017, Russ Allbery wrote:
> Sean Whitton writes:
>> On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote:
>
>>> I still haven't really made up my mind if I want to use git-maint-merge
>>> or git-dpm. Russ recently raised a valid point
On Jan 03 2017, Sean Whitton wrote:
> On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote:
>> I still haven't really made up my mind if I want to use git-maint-merge
>> or git-dpm. Russ recently raised a valid point with the Debian
>> modifications over-time
On Jan 03 2017, Sean Whitton wrote:
> Hello,
>
> On Tue, Jan 03, 2017 at 10:39:33AM -0800, Nikolaus Rath wrote:
>> >
>> > git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'
>>
>> Yes, but that's not as useful as what git-debcherry produces.
>>
>> For example,
gregor herrmann writes:
> Personally I have the feeling that lots of these discussions and also
> the creation of new tools (git-dpm, git-pq, git-debcherry, dgit) are
> just workarounds for the actual problem: Many of us would like to work
> in and with git but the whole
Toni Mueller writes:
> I found them only on PyPI. Did you find them elsewhere?
We get them from releases.ansible.com. Are the docs in the tarballs in
PyPi?
--
Harlan Lieberman-Berg
~hlieberman
Package: wnpp
Severity: wishlist
Owner: Carl Suster
Control: block 724718 by -1
* Package name: rpyc
Version : 3.3.0
Upstream Author : Tomer Filiba
* URL : https://github.com/tomerfiliba/rpyc
* License : MIT
Michael Biebl writes ("Re: "not authorised" doing various desktoppy things"):
> Check if your session is marked as active and local
> $ loginctl show-session $XDG_SESSION_ID
I see (amongst other things):
Remote=no
Active=yes
State=active
> Might be #844785
Perhaps it is. The symptoms
On Tue, 03 Jan 2017 20:15:10 +, Sean Whitton wrote:
> On Tue, Jan 03, 2017 at 10:54:07AM -0800, Russ Allbery wrote:
> > Well, if we had one more thing: a patches.debian.org service that would
> > show the git-debcherry-extracted patches against upstream. I really like
> > being able to just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 04 Jan 2017 01:07:10 +
Source: vtwm
Binary: vtwm
Architecture: amd64 source
Version: 5.4.7-5
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson
Changed-By: Ian Jackson
On Tue, Jan 3, 2017 at 5:38 PM, Abou Al Montacir wrote:
> What about requiring signed mail for closing a bug report?
We have sponsored maintainers, who theoretically could get by entirely
without an OpenPGP key. I don't know if any exist but I don't think
they should be blocked from -done. Also,
Package: wnpp
Severity: wishlist
Owner: Carl Suster
Control: block 724718 by -1
* Package name: terminaltables
Version : 3.1.0
Upstream Author : Robpol86
* URL : https://github.com/Robpol86/terminaltables
* License : MIT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 31 Dec 2016 17:07:40 +0100
Source: isdnactivecards
Binary: isdnactivecards
Architecture: source powerpc
Version: 1:3.12.2007-11-27-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl
Package: wnpp
Severity: wishlist
Owner: Carl Suster
Control: block 724718 by -1
* Package name: flask-cors
Version : 3.0.2
Upstream Author : Cory Dolphin
* URL : https://github.com/corydolphin/flask-cors
* License :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 04 Jan 2017 01:11:57 +0100
Source: compartment
Binary: compartment
Architecture: source i386
Version: 1.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernandez-Sanguino Peña
Changed-By:
On Tue, Jan 03, 2017 at 04:33:39PM -0800, Russ Allbery wrote:
> I'm unconvinced that any of that work would really be avoided via other
> mechanisms. The most time-consuming part is rebasing and squashing
> related changes together into one coherent diff, but that's going to be
> just as hard
On Tue, 03 Jan 2017 at 21:59:05 +, Sune Vuorela wrote:
> If I recall correctly, for most
> networky (and removable media things), the default policykit
> configuration is that 'local logged in users' are allowed to do this.
They must usually be active as well as locally logged in. (This means
On January 3, 2017 7:33:39 PM EST, Russ Allbery wrote:
>Sean Whitton writes:
>> On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote:
>
>>> I still haven't really made up my mind if I want to use
>git-maint-merge
>>> or git-dpm. Russ recently
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 21:30:11 -0300
Source: libgroove
Binary: libgroove-dev libgroove4 libgroove-dbg libgrooveplayer-dev
libgrooveplayer4 libgrooveloudness-dev libgrooveloudness4
libgroovefingerprinter-dev libgroovefingerprinter4
Package: wnpp
Severity: wishlist
Owner: Carl Suster
Control: block 724718 by -1
* Package name: flask-restplus
Version : 0.9.2
Upstream Author : Axel Haustant
* URL : https://github.com/noirbizarre/flask-restplus
* License
Sean Whitton writes:
> On Tue, Jan 03, 2017 at 10:36:22AM -0800, Nikolaus Rath wrote:
>> I still haven't really made up my mind if I want to use git-maint-merge
>> or git-dpm. Russ recently raised a valid point with the Debian
>> modifications over-time becoming all
Package: wnpp
Severity: wishlist
Owner: Carl Suster
Control: block 724718 by -1
* Package name: safe
Version : 0.4
Upstream Author : Hsiaoming Yang
* URL : https://github.com/lepture/safe
* License : BSD
Programming
On Mon, Jan 02, 2017 at 01:09:35PM -0800, Nikolaus Rath wrote:
> On Jan 02 2017, Russ Allbery wrote:
> > Furthermore, it forces a rebased, clean representation of the patches,
> > which I for one hugely prefer to the mess that you get if someone was
> > packaging in Git and just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 04 Jan 2017 00:56:57 +0100
Source: debian-edu-artwork
Binary: debian-edu-artwork debian-edu-artwork-lines
debian-edu-artwork-softwaves debian-edu-artwork-spacefun
Architecture: source
Version: 0.902-1
Distribution: unstable
Package: wnpp
Severity: wishlist
Owner: Carl Suster
Control: block 724718 by -1
* Package name: colorclass
Version : 2.2.0
Upstream Author : Robpol86
* URL : https://github.com/Robpol86/colorclass
* License : MIT
Hi!
A happy new year, everyone!
On Sat, Dec 31, 2016 at 01:07:44PM -0500, Harlan Lieberman-Berg wrote:
> Unfortunately, we don't build ansible off of the git repository, but
> rather from the released tarballs.
I found them only on PyPI. Did you find them elsewhere?
> It's been a while since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 04 Jan 2017 10:29:06 +1100
Source: golang-github-geertjohan-go.rice
Binary: golang-github-geertjohan-go.rice-dev golang-rice
Architecture: source all amd64
Version: 0.0~git20160123.0.0f3f5fd-2
Distribution: unstable
Urgency:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 23:53:50 +0100
Source: nodejs
Binary: nodejs-dev nodejs nodejs-dbg nodejs-legacy
Architecture: source
Version: 6.9.2~dfsg-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 21:22:31 +
Source: perl
Binary: perl-base perl-doc perl-debug libperl5.24 libperl-dev perl-modules-5.24
perl
Architecture: source
Version: 5.24.1~rc5-1
Distribution: experimental
Urgency: medium
Maintainer:
Hi there,
as the stretch freeze approaches, I'm getting concerned about the
status of logrotate, most notably #734688. The maintainer (CC'ed)
hasn't shown any sign of activity for a while, also no response to a
private message (I admit, it's been just a few days).
Since the fix includes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 29 Dec 2016 20:51:10 +0100
Source: logrotate
Binary: logrotate
Architecture: source powerpc
Version: 3.11.0-0.1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Paul Martin
Changed-By: Christoph
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 23:37:18 +0100
Source: isatapd
Binary: isatapd
Architecture: source
Version: 0.9.7-4
Distribution: unstable
Urgency: medium
Maintainer: Bernhard Schmidt
Changed-By: Bernhard Schmidt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 22:52:44 +0100
Source: sqlmap
Binary: sqlmap
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 23:15:26 +0100
Source: iftop
Binary: iftop
Architecture: source
Version: 1.0~pre4-4
Distribution: unstable
Urgency: medium
Maintainer: Markus Koschany
Changed-By: Markus Koschany
Hello Nikolaus,
On Tue, Jan 03, 2017 at 10:29:49AM -0800, Nikolaus Rath wrote:
> On Jan 03 2017, Sean Whitton wrote:
> > You mentioned previously that you're trying to use the
> > dgit-maint-merge(7) workflow. In that case, why do you want git-dpm?
>
> I don't. I was
Hello,
On Tue, Jan 03, 2017 at 10:39:33AM -0800, Nikolaus Rath wrote:
> >
> > git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'
>
> Yes, but that's not as useful as what git-debcherry produces.
>
> For example, if you get a merge conflict when rebasing, the above
> incantation will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 22:02:23 +
Source: python-prometheus-client
Binary: python-prometheus-client python3-prometheus-client
Architecture: source all
Version: 0.0.18-1
Distribution: unstable
Urgency: medium
Maintainer: Christopher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 02 Jan 2017 22:34:27 +0100
Source: pptp-linux
Binary: pptp-linux
Architecture: source powerpc
Version: 1.9.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 22:43:11 +0100
Source: sqlmap
Binary: sqlmap
Architecture: source
Version: 1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 21:37:13 +
Source: slof
Binary: qemu-slof
Architecture: source
Version: 20161019+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 22:38:49 +0100
Source: musl
Binary: musl musl-dev musl-tools
Architecture: source
Version: 1.1.16-1
Distribution: unstable
Urgency: low
Maintainer: Reiner Herrmann
Changed-By: Reiner Herrmann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 20:28:34 +0100
Source: debian-security-support
Binary: debian-security-support
Architecture: source all
Version: 2017.01.03
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl
On 2017-01-03, Ian Jackson wrote:
> Can someone please help explain to me how these things are supposed to
> work ? Specifically, how is (presumably as a consequence of me
> logging in using a display manager) my session supposed to be granted
> the ability to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 21:49:57 +0100
Source: pg-partman
Binary: postgresql-9.6-partman
Architecture: source
Version: 2.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 00:51:30 -0500
Source: xdotool
Binary: xdotool libxdo3 libxdo-dev
Architecture: source
Version: 1:3.20160805.1-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 21:03:16 +
Source: onionbalance
Binary: onionbalance
Architecture: source all
Version: 0.1.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 03 Jan 2017 20:46:41 +0100
Source: liblockfile
Binary: liblockfile1 liblockfile-bin liblockfile-dev
Architecture: source amd64
Version: 1.11-1
Distribution: unstable
Urgency: low
Maintainer: Miquel van Smoorenburg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 18:17:13 +0100
Source: chrony
Binary: chrony
Architecture: source
Version: 3.0~pre2-2
Distribution: experimental
Urgency: low
Maintainer: Vincent Blut
Changed-By: Vincent Blut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 21:11:29 +0100
Source: vlc
Binary: vlc libvlc-dev libvlc5 libvlccore-dev libvlccore8 libvlc-bin vlc-bin
vlc-data vlc-l10n vlc-plugin-base vlc-plugin-access-extra
vlc-plugin-video-output vlc-plugin-video-splitter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 20:56:05 +0100
Source: why3
Binary: why3 why3-coq libwhy3-ocaml-dev why3-examples why3-doc-html why3-doc-pdf
Architecture: source
Version: 0.87.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 20:09:17 +0100
Source: rtax
Binary: rtax
Architecture: source all
Version: 0.984-4
Distribution: unstable
Urgency: medium
Maintainer: Med Packaging Team
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 20:42:25 +0100
Source: python-macholib
Binary: python-macholib python3-macholib python-macholib-doc
Architecture: source
Version: 1.8~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 20:50:50 +0100
Source: python-py
Binary: python3-py python-py pypy-py
Architecture: source
Version: 1.4.32-3
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Ramacher
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 21:21:00 +0100
Source: libconfig-model-systemd-perl
Binary: libconfig-model-systemd-perl
Architecture: source all
Version: 0.232.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 21:22:29 +0100
Source: libass
Binary: libass-dev libass5
Architecture: source
Version: 1:0.13.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 21:45:03 +0100
Source: cinnamon-session
Binary: cinnamon-session cinnamon-session-common
Architecture: source
Version: 3.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Cinnamon Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 20:36:10 +0100
Source: flac
Binary: flac libflac8 libflac-doc libflac-dev libflac++6v5 libflac++-dev
Architecture: source
Version: 1.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 17:30:04 -0200
Source: jdupes
Binary: jdupes
Architecture: source
Version: 1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Joao Eriberto Mota Filho
Changed-By: Joao Eriberto Mota
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 21:10:54 +0100
Source: bioperl-run
Binary: bioperl-run libbio-perl-run-perl
Architecture: source
Version: 1.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 20:56:14 +0100
Source: cinnamon-screensaver
Binary: cinnamon-screensaver cinnamon-screensaver-x-plugin
cinnamon-screensaver-webkit-plugin libcscreensaver0
Architecture: source
Version: 3.2.13-1
Distribution:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 21:23:08 +0100
Source: cinnamon
Binary: cinnamon cinnamon-doc cinnamon-common
Architecture: source
Version: 3.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cinnamon Team
Am 03.01.2017 um 21:05 schrieb Ian Jackson:
> Recently, my nm-applet can no longer control my network-manager
> daemon. I get a message saying[1]:
>
> "org.freedesktop.NetworkManager.network-control-request failed: not
> authorized"
>
> I think this is related to a similar problem in
Recently, my nm-applet can no longer control my network-manager
daemon. I get a message saying[1]:
"org.freedesktop.NetworkManager.network-control-request failed: not
authorized"
I think this is related to a similar problem in *-power-manager,
#848623.
I am running:
* sysvinit
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 03 Jan 2017 13:30:01 -0600
Source: r-cran-rneos
Binary: r-cran-rneos
Architecture: source all
Version: 0.3-2-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel
Changed-By: Dirk Eddelbuettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 03 Jan 2017 13:22:59 -0600
Source: r-cran-digest
Binary: r-cran-digest
Architecture: source amd64
Version: 0.6.11-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel
Changed-By: Dirk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 19:10:29 +0100
Source: lxqt-metapackages
Binary: lxqt-core lxqt
Architecture: source
Version: 9
Distribution: unstable
Urgency: medium
Maintainer: LXQt Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Jan 2017 19:29:17 +
Source: python-model-mommy
Binary: python-model-mommy python3-model-mommy
Architecture: source all
Version: 1.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 03 Jan 2017 13:06:55 -0600
Source: rcmdr
Binary: r-cran-rcmdr
Architecture: source amd64
Version: 2.3-2-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel
Changed-By: Dirk Eddelbuettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 19:59:56 +0100
Source: vdr-plugin-satip
Binary: vdr-plugin-satip
Architecture: source amd64
Version: 2.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 07:44:43 +0100
Source: mysql-5.7
Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7
mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server
mysql-client mysql-testsuite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 11:00:36 -0800
Source: libwebp
Binary: libwebp-dev libwebp6 libwebpmux2 libwebpdemux2 webp
Architecture: source amd64
Version: 0.5.2-1
Distribution: unstable
Urgency: medium
Maintainer: Jeff Breidenbach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 03 Jan 2017 20:05:31 +0100
Source: gscan2pdf
Binary: gscan2pdf
Architecture: source all
Version: 1.6.0-3
Distribution: unstable
Urgency: low
Maintainer: Jeffrey Ratcliffe
Changed-By: Jeffrey Ratcliffe
On Jan 03 2017, Nikolaus Rath wrote:
> On Jan 03 2017, Sean Whitton wrote:
>> Hello Russ,
>>
>> On Mon, Jan 02, 2017 at 09:29:24AM -0800, Russ Allbery wrote:
>>> Furthermore, it forces a rebased, clean representation of the patches,
>>> which I for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 03 Jan 2017 12:59:17 -0600
Source: r-cran-rms
Binary: r-cran-rms
Architecture: source amd64
Version: 5.1-0-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel
Changed-By: Dirk Eddelbuettel
On Jan 03 2017, Russ Allbery wrote:
> Nikolaus Rath writes:
>
>> For example, if you get a merge conflict when rebasing, the above
>> incantation will list two commits: the original debian commit and the
>> merge commit. git-debcherry, on the other hand, will
1 - 100 of 182 matches
Mail list logo