Control: tags -1 + pending
Hi,
On Sat, 2016-01-16 at 15:43 +0100, Holger Levsen wrote:
> Hi Adam,
>
> On Sonntag, 27. Dezember 2015, Adam D. Barratt wrote:
> > That's obviously not exactly what you're planning to upload. However,
> > assuming that the only difference between the attached diff
Hi Adam,
On Sonntag, 27. Dezember 2015, Adam D. Barratt wrote:
> That's obviously not exactly what you're planning to upload. However,
> assuming that the only difference between the attached diff and the
> actual uploaded source package is a changelog stanza for 0.2.2-2~deb8u1,
> please feel
On Mon, 2016-01-04 at 19:54 +, Adam D. Barratt wrote:
> On Sun, 2016-01-03 at 15:05 +0100, Holger Levsen wrote:
> > Hi,
> >
> > (this is maybe more to pkg-privacy-maintainers@ than to -release@, maybe
> > not.)
> >
> > On Sonntag, 3. Januar 2016, Adam D. Barratt wrote:
> > > Thanks. Please
Hi Adam,
On Mittwoch, 13. Januar 2016, Adam D. Barratt wrote:
> Whichever approach you decide to take to fixing this, please bear in
> mind that there are only a few days until the 8.3 window closes.
thanks for the heads up - I've planned to fix this properly until Friday…
cheers,
On Sun, 2016-01-03 at 15:05 +0100, Holger Levsen wrote:
> Hi,
>
> (this is maybe more to pkg-privacy-maintainers@ than to -release@, maybe not.)
>
> On Sonntag, 3. Januar 2016, Adam D. Barratt wrote:
> > Thanks. Please go ahead.
>
> so far I've only tested binary builds of these changes and
Hi Adam,
On Sonntag, 27. Dezember 2015, Adam D. Barratt wrote:
> > Attached is the output
> > of debdiff torbrowser-launcher_0.1.9-1+deb8u1.dsc
> > torbrowser-launcher_0.2.2-2.dsc>tbl-jessie-sid.diff)
> That's obviously not exactly what you're planning to upload. However,
> assuming that the only
Hi,
(this is maybe more to pkg-privacy-maintainers@ than to -release@, maybe not.)
On Sonntag, 3. Januar 2016, Adam D. Barratt wrote:
> Thanks. Please go ahead.
so far I've only tested binary builds of these changes and when doing a source
build now I realized that cherry-picking these patches
On Sun, 2016-01-03 at 13:03 +0100, Holger Levsen wrote:
> On Sonntag, 27. Dezember 2015, Adam D. Barratt wrote:
>
> > > Attached is the output
>
> > > of debdiff torbrowser-launcher_0.1.9-1+deb8u1.dsc
>
> > > torbrowser-launcher_0.2.2-2.dsc>tbl-jessie-sid.diff)
>
> > That's obviously not
Hi,
On Sun, 2016-01-03 at 14:07 +0100, Holger Levsen wrote:
> Hi,
>
> On Sonntag, 3. Januar 2016, Adam D. Barratt wrote:
> > Would it be possible to have a diff that does represent what you're
> > planning to upload, please?
>
> sure! (the following still has "UNRELEASED" but thats about it.)
On Sonntag, 3. Januar 2016, Holger Levsen wrote:
> so far I've only tested binary builds of these changes…
jenkins.d.n from now on also tests source builds on every commit…
signature.asc
Description: This is a digitally signed message part.
Hi,
On Sonntag, 3. Januar 2016, Adam D. Barratt wrote:
> The diff attached to the mail I was replying to has
> -torbrowser-launcher (0.1.9-1+deb8u1) jessie; urgency=high
> +torbrowser-launcher (0.2.2-2) sid; urgency=medium
at first I was thinking to get 0.2.2-2 into stable would be preferred but
Control: tags -1 + confirmed
On 2015-11-20 13:10, Holger Levsen wrote:
torbrowser-launcher 0.1.9-1+deb8u1 in jessie is affected by 3 serious
bugs
(#804184 #784041 #804274) which are all fixed in the version in stretch
(=0.2.1-2), plus there is one annoying bug left in stretch (#805078)
which
Hi Adam,
On Montag, 14. Dezember 2015, Adam D. Barratt wrote:
> Other than intrigeri's query r.e. AppArmor, was there any useful
> feedback from that?
there was no other feedback, no.
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
On Mon, 2015-12-07 at 16:23 +0100, Holger Levsen wrote:
> Hi,
>
> I have cheery-picked the needed changes to make torbrowser-launcher to work
> again in jessie (and to comply with the stable update policies) into the
> debian/jessie branch, so that this branch at least now works on
>
Hi,
I have cheery-picked the needed changes to make torbrowser-launcher to work
again in jessie (and to comply with the stable update policies) into the
debian/jessie branch, so that this branch at least now works on
Hi intrigeri,
On Freitag, 20. November 2015, intrigeri wrote:
> Holger Levsen wrote (20 Nov 2015 13:10:46 GMT) :
> > * Tor Browser Lanucher no longer attempts to auto-update, now that
> Is Tor Browser's self-upgrade feature compatible with the AppArmor
> profiles shipped by the package? It
On 04/12/15 12:05, Holger Levsen wrote:
> Dear stable release managers,
>
> as described in this bug, torbrowser-launcher in jessie is completly broken
> at
> the moment. A reply from you about this request would have been very nice
> (even given intrigeri's reply), and even if it would have
On Fri, 2015-12-04 at 13:42 +0200, Holger Levsen wrote:
> Hi,
>
> On Freitag, 4. Dezember 2015, Emilio Pozuelo Monfort wrote:
> > Hmm? Is there going to be a point release next week and I completely missed
> > the announcement?
>
> a release team member (who is not a SRM) told me yesterday that
Dear stable release managers,
as described in this bug, torbrowser-launcher in jessie is completly broken at
the moment. A reply from you about this request would have been very nice
(even given intrigeri's reply), and even if it would have been "Holger, you
should know we don't like new
Hi,
On Freitag, 4. Dezember 2015, Emilio Pozuelo Monfort wrote:
> Hmm? Is there going to be a point release next week and I completely missed
> the announcement?
a release team member (who is not a SRM) told me yesterday that it might be
too late to be included in the next point release very
package: release.debian.org
x-debbugs-cc: pkg-privacy-maintain...@lists.alioth.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hi,
torbrowser-launcher 0.1.9-1+deb8u1 in jessie is affected by 3 serious bugs
(#804184 #784041 #804274) which are all
Hi,
Holger Levsen wrote (20 Nov 2015 13:10:46 GMT) :
> * Tor Browser Lanucher no longer attempts to auto-update, now that
> Tor Browser has this feature
Is Tor Browser's self-upgrade feature compatible with the AppArmor
profiles shipped by the package? It doesn't look like it at first
glance,
22 matches
Mail list logo
