On Mon, Jul 28, 2014 at 07:38:46AM +0200, santi...@debian.org wrote:
> So, to be sure, should I just drop the old lib{32,64}bz2*,
> without any transition mechanism? (no other package depends on them
> now.)
If they are not referenced in the archive, nothing special needs to be
done.
Hi,
(Please CC me when answering)
I've just uploaded a new bzip2 revision and I think I need to revert a
change. bzip2 used to build cross architecture lib{32,64}bz2* packages,
but multiarch has obsoleted them. To stop building those packages (and
close #736815), and to look for a smooth transiti
Hi Reinhard,
On 28.07.2014 02:05, Reinhard Tartler wrote:
On Sun, Jul 27, 2014 at 7:20 PM, Andreas Cadhalpun
wrote:
* Does it make sense for me to switch my package?
The rule of thumb is, if your upstream uses FFmpeg for development
you probably want to switch to using it, too.
In
Hi,
On Sun, 27 Jul 2014, Reinhard Tartler wrote:
> In [1], Moritz from the security team clearly stated that he is more
> than uncomfortable with having more than one copy of libavcodec in
> debian/testing. In consequence this means that any package that builds
> against the ffmpeg packages curren
* Michael Biebl [140727 23:09]:
> Am 22.07.2014 23:54, schrieb Julian Gilbey:
> > For me, this is a killer, as I still do not know how to solve the
> > problem I asked a while back on debian-user
> > (https://lists.debian.org/debian-user/2014/04/msg01286.html): in
> > summary, I need to unlock an
On Jul 28, Reinhard Tartler wrote:
> Moreover, I am curious why I haven't seen you working on libavcodec
> bugs in Debian before, and why do you believe you can do a better job
> with the ffmpeg package currently on NEW?
Why should he work on libavcodec when he (along with many other people)
wan
On Sun, Jul 27, 2014 at 7:20 PM, Andreas Cadhalpun
wrote:
> * Does it make sense for me to switch my package?
>The rule of thumb is, if your upstream uses FFmpeg for development
>you probably want to switch to using it, too.
In [1], Moritz from the security team clearly stated that he i
Hi all,
some of you may have noticed a weird ffmpeg package in the NEW queue[1].
Let me explain:
In 2011 Libav[2] was forked from FFmpeg[3]. It was a time of great
uncertainty, the fork happened with much drama that didn't help making a
technical cut, and at that peculiar time Debian switched to
Sven Bartscher wrote:
> As brought up in this[0] thread, systemd-shim became incompatible with
> the latest versions of systemd and the alternative dependency was
> removed.
>
> While this is something I can totally understand, I don't think that
> systemd should migrate to testing without the pos
2014-07-27 22:08 GMT+02:00 Sven Bartscher :
> On Sun, 27 Jul 2014 21:21:56 +0200
> Holger Levsen wrote:
>
>> Hi,
>>
>> On Sonntag, 27. Juli 2014, Dominik George wrote:
>> > >To make it short: I suggest that systemd should only migrate together
>> > >with systemd-shim.
>> > ACK!
>>
>> I think you m
On 2014-07-27 11:39:58 +0200, Bastian Blank wrote:
> On Sun, Jul 27, 2014 at 06:57:24PM +1200, Chris Bannister wrote:
> > Presume you mean "... scheduler that handles ..."
> > It may even be "proper English" to say "... scheduler which handles ..."
>
> We got the advice to always use "which" with
Am 22.07.2014 23:54, schrieb Julian Gilbey:
> For me, this is a killer, as I still do not know how to solve the
> problem I asked a while back on debian-user
> (https://lists.debian.org/debian-user/2014/04/msg01286.html): in
> summary, I need to unlock an encrypted filesystem during boot time by
>
* Russ Allbery (r...@debian.org) [140727 21:51]:
> The timing of migration of the new version of systemd to testing, like
> questions about testing migration in general, is really a release team
> decision.
And the release team has done a decision for the normal case when
bugs are release critical
On Sun, 27 Jul 2014 21:21:56 +0200
Holger Levsen wrote:
> Hi,
>
> On Sonntag, 27. Juli 2014, Dominik George wrote:
> > >To make it short: I suggest that systemd should only migrate together
> > >with systemd-shim.
> > ACK!
>
> I think you missed the mail (on this list) which explained that syst
Cameron Norman writes:
> I believe the choices are to repose the question to the TC, now that the
> situation has actually occurred, or begin a General Resolution. As far as
> I understand, a GR would only need a majority since the TC did not really
> make a ruling.
The release team can decide o
Hi,
On Sonntag, 27. Juli 2014, Dominik George wrote:
> >To make it short: I suggest that systemd should only migrate together
> >with systemd-shim.
> ACK!
I think you missed the mail (on this list) which explained that systemd has
been waiting for >6 months for systemd-shim to catch up.
chee
El Sun, 27 de Jul 2014 a las 11:23 AM, Sven Bartscher
escribió:
Greetings everyone,
As brought up in this[0] thread, systemd-shim became incompatible with
the latest versions of systemd and the alternative dependency was
removed.
While this is something I can totally understand, I don't think
>To make it short: I suggest that systemd should only migrate together
>with systemd-shim.
ACK!
-nik
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/8667e39c-b7ef-
]] Philipp Kern
> On Sun, Jul 27, 2014 at 08:40:03AM -0700, tony mancill wrote:
> > It seems like with Ganneff's trigger mechanism, one attack vector is to
> > steal a backup of the passphraseless key and spoof the source IP - now
> > you can run the trigger at will. Having a passphrase on the k
Greetings everyone,
As brought up in this[0] thread, systemd-shim became incompatible with
the latest versions of systemd and the alternative dependency was
removed.
While this is something I can totally understand, I don't think that
systemd should migrate to testing without the possibility to u
Bastian Blank writes:
> On Sun, Jul 27, 2014 at 10:45:37AM -0700, Russ Allbery wrote:
>> Bastian Blank writes:
>>> We got the advice to always use "which" with comma and "that" without
>>> comma. Especially for non-native speakers the number of variations
>>> with slightly different meaning get
On Sun, Jul 27, 2014 at 10:45:37AM -0700, Russ Allbery wrote:
> Bastian Blank writes:
> > On Sun, Jul 27, 2014 at 06:57:24PM +1200, Chris Bannister wrote:
> >> Presume you mean "... scheduler that handles ..."
> >> It may even be "proper English" to say "... scheduler which handles ..."
> > We got
On Sun, Jul 27, 2014 at 08:40:03AM -0700, tony mancill wrote:
> It seems like with Ganneff's trigger mechanism, one attack vector is to
> steal a backup of the passphraseless key and spoof the source IP - now
> you can run the trigger at will. Having a passphrase on the key could
> at least slow t
Bastian Blank writes:
> On Sun, Jul 27, 2014 at 06:57:24PM +1200, Chris Bannister wrote:
>> Presume you mean "... scheduler that handles ..."
>> It may even be "proper English" to say "... scheduler which handles ..."
> We got the advice to always use "which" with comma and "that" without
> comm
/me mutters something about being incompatible with reportbug...
The upstream author and URL should have been in the original report
(corrected below).
On 07/27/2014 01:54 AM, Marc Haber wrote:
> On Sat, 26 Jul 2014 21:05:37 -0700, tony mancill
> wrote:
>> * Package name : ssh-cron
>> Version
Hi,
(also send to owner@b.d.o via bcc: to make them(?) aware of this (sub-
thread).)
On Sonntag, 27. Juli 2014, Paul Wise wrote:
> On Sun, Jul 27, 2014 at 9:02 PM, Holger Levsen wrote:
> > "general" and "project" are maybe useful though..
>
> general only receives misguided user support requests
On Sun, Jul 27, 2014 at 9:27 PM, Ansgar Burchardt wrote:
> It is possible to restrict keys in .ssh/authorized_keys so that they are
> only allowed to run specific commands, see the 'command="command"' bit in
> man:sshd(8). One probably wants to combine this with no-port-forwarding
> and similar op
On Sun, Jul 27, 2014 at 9:02 PM, Holger Levsen wrote:
> "general" and "project" are maybe useful though..
general only receives misguided user support requests, not useful.
project doesn't receive new reports; not useful.
--
bye,
pabs
https://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, ema
Hi,
Jonathan Yu writes:
> On Sun, Jul 27, 2014 at 4:54 AM, Marc Haber
> wrote:
>
>> Why would one use such a tool? passphraseless keys exist, and can be
>> configured to be secure.
>
> This sounds interesting. Do you have a link to some documentation on this
> technique?
It is possible to restr
Hi,
On Sonntag, 27. Juli 2014, Paul Wise wrote:
> Better to delete the general/base/cdrom/project pseudo-packages I
> would think, we don't need them any more.
Basically I agree. "general" and "project" are maybe useful though..
cheers,
Holger
signature.asc
Description: This is a di
On Fri, Jul 25, 2014 at 8:26 PM, Ian Jackson wrote:
> As a more radical suggestion, perhaps it should divert the usual
> output email to debian-user ? Probably we should ask the inhabitants
> of debian-user what they think of this idea...
Better to delete the general/base/cdrom/project pseudo-pa
Sorry for the double-post. Upon reflection, it looks like I was asking
about information about passphraseless keys -- I was curious about the
latter part, how they can be configured to be secure.
On Sun, Jul 27, 2014 at 8:31 AM, Jonathan Yu wrote:
> Hi Marc,
>
> On Sun, Jul 27, 2014 at 4:54 AM,
Hi Marc,
On Sun, Jul 27, 2014 at 4:54 AM, Marc Haber
wrote:
> Why would one use such a tool? passphraseless keys exist, and can be
> configured to be secure.
>
This sounds interesting. Do you have a link to some documentation on this
technique?
Jonathan
On Sun, Jul 27, 2014 at 06:57:24PM +1200, Chris Bannister wrote:
> Presume you mean "... scheduler that handles ..."
> It may even be "proper English" to say "... scheduler which handles ..."
We got the advice to always use "which" with comma and "that" without
comma. Especially for non-native sp
On Sat, 26 Jul 2014 21:05:37 -0700, tony mancill
wrote:
>* Package name: ssh-cron
> Version : 0.91.01
> Upstream Author :
>* URL :
>* License : GPL-2+
> Programming Lang: C++
> Description : cron-like job scheduler than handles ssh key passphrases
>
> ssh-
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-greenio
Version : 0.6.0
Upstream Author : Yury Selivanov
* URL : https://github.com/1st1/greenio
* License : Apache-2.0
Programming Lang: Pyhon
Description : greenlets for as
36 matches
Mail list logo
