ase.
If I misunderstood something important, please let me know.
Cheers,
--
intrigeri
it would
be fine to remove libgtk2-perl and its reverse-dependencies from
testing. Some might see this as a heavy hammer approach, but this was
announced a year ago to all affected maintainers; either way, it will
happen during the Bullseye cycle, eventually.
Cheers,
--
intrigeri
on-screen keyboard (Closes: #926452)
+
+ -- intrigeri Mon, 15 Apr 2019 11:23:31 +
+
+gnome-shell (3.30.2-5) unstable; urgency=medium
+
+ * Team upload
+ * Really create a suitable temporary XDG_RUNTIME_DIR for the unit tests
+ * Clean up debian/home with d/clean, not a dh_clean override
+
Adam D. Barratt:
> Please feel free to upload.
Uploaded, thanks.
aching 2 updated debdiffs: one from the version in Stretch and
the other one from the version that's already in stable p-u.
Cheers,
--
intrigeri
diff -Nru apparmor-2.11.0/debian/apparmor.install apparmor-2.11.0/debian/apparmor.install
--- apparmor-2.11.0/debian/apparmor.install 2017-03-28 12:23:0
for Stretch users running an outdated Linux 4.14.x).
May I upload (with s/UNRELEASED/stretch/ of course)?
Cheers,
--
intrigeri
diff -Nru apparmor-2.11.0/debian/apparmor.install apparmor-2.11.0/debian/apparmor.install
--- apparmor-2.11.0/debian/apparmor.install 2017-03-28 12:23:08.0 +0200
Adam D. Barratt:
> # Broken Depends:
> onionshare/contrib: onionshare
So I guess Jessie should first get the fix we applied to onionshare in
testing/sid, i.e. move torbrowser-launcher to Recommends.
're likely to be looking at freezing p-u for the next point
> release in a couple of weeks time.
I've been following the Stretch 9.4 scheduling thread with this in
mind. My current plan is to prepare an updated stable p-u around
February 24-25.
Thanks for the ping! :)
Cheers,
--
intrigeri
uld remove the "confirmed" and/or "pending" tag
so in doubt I'll leave it to you to do the right thing.
Cheers,
--
intrigeri
intrigeri:
> At first glance this very much looks like a bug in the custom kernel
> you're using.
According to #883703 this bug affects the mainline Linux kernel as
well so this stretch-pu may break as many use cases at it'll repair
when running Linux 4.13+ on Stretch :/
Dear release tea
Hi again Fabian & release team,
Fabian Grünbichler:
> On Wed, Dec 06, 2017 at 03:28:03PM +0100, intrigeri wrote:
>> > it potentially breaks systems using a custom/backports/newer kernel
>> > and AA profiles requiring features not supported by the pinned 4.9
>> >
becomes weaker,
but the application keeps working.
> since
> both the AA config file itself and the feature set file are conffiles,
> overriding is not easily possible without conffile modification.
Right. Sorry I did not think about this Debian derivative use case.
> I'll of course def
Adam D. Barratt:
> Please go ahead, bearing in mind that the window for getting fixes into
> the 9.3 point release closes during this weekend.
Thanks, uploaded.
Cheers,
--
intrigeri
in recent kernels.
+
+ -- intrigeri <intrig...@debian.org> Sat, 25 Nov 2017 18:04:05 +
+
apparmor (2.11.0-3) unstable; urgency=medium
* Fix CVE-2017-6507: don't unload unknown profiles during package
diff -Nru apparmor-2.11.0/debian/features apparmor-2.11.0/debian/features
--- apparmor-
Adam D. Barratt:
> Control: tags -1 + pending
> On Tue, 2017-08-08 at 12:00 -0400, Adam D. Barratt wrote:
>> Please go ahead.
> Uploaded and flagged for acceptance.
Thanks!
to such serious bugs. Currently that branch has one single
commit, that fixes the root cause of the aforementioned issues. One of the
affected users (X-Debbugs-Cc'ed) has tested it and confirms the fix works
for him.
Can I upload to stretch-pu with the attached debdiff?
Cheers,
--
intrigeri
diff
Hi,
intrigeri:
> Tails 3.0 will be released either on June 13 or on June 17.
We've decided to release Tails 3.0 on June 13: we have to release
_something_ on that day anyway (Firefox security update), so moving
the Tails 3.0 release to June 17 would have added a substantial amount
of work on
Hi Niels & others,
Niels Thykier:
> intrigeri:
> Apologies for the late reply on our part.
That's totally fine; thanks for caring! :)
> At this point we have now announced our planned release date as June
> 17th (https://lists.debian.org/debian-devel-announce/2017/05/msg2
t works fine for us :)
Cheers,
--
intrigeri
gt; and I can come back to it in a month if you prefer.
Cheers,
--
intrigeri
ckages of "mine"), but IMO this shouldn't block the Stretch
release, so a stretch-ignore tag would seem suitable to me.
Cheers,
--
intrigeri
this variable to the Debian release schedule
equation: understood, don't bother, fine :)
I also understand that this proposal may be premature at this point,
and I can come back to it in a month if you prefer.
Cheers,
--
intrigeri
a-remove-unknown, which can be used to unload unknown profiles. Based
+ on an upstream patch but adjusted to source the /lib/apparmor/functions
+ shipped in Debian/Ubuntu.
+
+ -- intrigeri <intrig...@debian.org> Tue, 28 Mar 2017 10:29:15 +
+
apparmor (2.11.0-2) unstable; u
is needed to fully fix #858058.
+
+ -- intrigeri <intrig...@debian.org> Sat, 18 Mar 2017 11:28:06 +
+
mat (0.6.1-3) unstable; urgency=medium
* Update documentation of recommended packages in README.Debian.
diff -Nru mat-0.6.1/debian/patches/Make-the-Nautilus-extension-work-again.patc
missing dependency on net-tools: OnionCat hard-codes
+ifconfig usage (Closes: #857262).
+ * Add missing dependency on lsb-base (>= 3.0-6): the onioncat
+initscript sources the /lib/lsb/init-functions utility functions.
+
+ -- intrigeri <intrig...@debian.org> Thu, 09 Mar 2017
deadline for accepting new packages, given the
10-days migration delay.
[1] https://lists.debian.org/debian-devel-announce/2016/11/msg2.html
Cheers,
--
intrigeri
Hi!
I've uploaded mat 0.5.2-3+deb8u1 by mistake to the "jessie-security"
distribution on ssh.upload.debian.org, while it should have gone to
security-master.d.o. Looks like it has therefore landed in stable-new.
Please reject/remove it, and sorry for the burden!
Cheers,
--
intrigeri
o testing, which should in
turn fix the root cause of this co-installability problem.
Thanks again!
Cheers,
--
intrigeri
Hi release team!
gregor herrmann:
> On Sun, 11 Sep 2016 11:33:26 +0200, intrigeri wrote:
>> I need help to understand why libgnupg-interface-perl 0.52-3 has not
>> made its way into testing yet.
>> https://qa.debian.org/excuses.php?package=libgnupg-interface-perl
>>
Hi,
Holger Levsen wrote (06 Dec 2015 10:17:48 GMT) :
> 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 comp
glance, but I didn't tested this yet.
Cheers,
--
intrigeri
it in the archive.
Cheers,
--
intrigeri
, that are unrelated to #786650, that this
patch as meant to fix.
I've just built and tested on Jessie, and could successfully start
a VM with AppArmor enforced.
Cheers,
--
intrigeri
diff -Nru libvirt-1.2.9/debian/changelog libvirt-1.2.9/debian/changelog
--- libvirt-1.2.9/debian/changelog 2015-02-06 15
Adam D. Barratt wrote (19 Aug 2015 15:41:26 GMT) :
Please go ahead; thanks.
Uploaded. Thanks!
,
--
intrigeri
-correct-type.patch
+- 0006-load-linux-protected-mode.patch
+
+ -- intrigeri intrig...@debian.org Tue, 18 Aug 2015 17:21:55 +0200
+
syslinux (3:6.03+dfsg-5) unstable; urgency=low
* Moving source lintian-overrides to newer location.
diff -Nru syslinux-6.03+dfsg/debian/patches/0005-load-linux
2015-02-18 19:53:25.0 +0100
@@ -1,3 +1,10 @@
+libgtk2-perl (2:1.2492-4) unstable; urgency=high
+
+ * Fix-incorrect-memory-management-in-Gtk2-Gdk-Display-list_devices.patch:
+new patch, cherry-picked from upstream, that fixes a security issue.
+
+ -- intrigeri intrig...@debian.org Wed, 18
Hi Sebastian,
Niels Thykier wrote (21 Nov 2014 18:10:31 GMT) :
Unfortunately, as intrigeri suggests in his mail, we are not willing to
accept this large a changeset up to or during the freeze. However, we
are still willing to accept targeted fixes for important bugs for
another 14 days
is suitable, and follow up with a full diff.
Do you think the new upstream version is suitable for jessie? Is it a
bug fix only release?
Ping?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Hans-Christoph Steiner wrote (12 Dec 2014 12:32:59 GMT) :
First of all, please don't break threads.
Sorry, I don't understand what you mean by this.
I think that Ivo meant that your previous email
(54874ee7.9020...@eds.org) was a reply to his
(20141119190826.ga19...@ugent.be), but was lacking
into the
archive, and then failed to notice this change when I debdiff'ed it
before uploading :/
I've now fixed it in Vcs-Git. I guess it's not worth re-uploading,
is it?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Control: retitle -1 unblock: macchanger/1.7.0-3.2
Control: tag -1 + moreinfo
Hi Niels,
Niels Thykier wrote (29 Nov 2014 10:31:54 GMT) :
On 2014-11-29 11:08, intrigeri wrote:
I've now fixed it in Vcs-Git. I guess it's not worth re-uploading,
is it?
I would prefer if it was. [...]
Fair
Control: reopen -1
Hi Jonathan,
Debian Bug Tracking System wrote (15 Nov 2014 12:09:09 GMT) :
#769358: unblock: libjson-java/2.3-3
It has been closed by Jonathan Wiltshire j...@debian.org.
$ curl -s https://release.debian.org/britney/hints/jmw | grep -B1 '^unblock
libjson-java'
-tools in jessie-backports,
and getting it in good shape early enough for the Stretch freeze :)
What do the bcache-tools maintainers think?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Ooops, sorry, Jonathan had already replied.
You can thus ignore my previous email on this bug.
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
László Böszörményi (GCS) wrote (16 Nov 2014 16:49:43 GMT) :
If you say Jessie only should support kernels later than 3.2.x while
do not allow users to keep their old kernels (from Wheezy or
earlier) then sure, this is a no go. Then it should be noted in the
release notes that some programs,
László Böszörményi (GCS) wrote (16 Nov 2014 18:15:34 GMT) :
Question still remains, should ntfs-3g support Jessie userland and
2.6.x kernel combo like the bug reporter has or not.
Lack of support for this combination shouldn't be RC, in my opinion.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE
deletions(-) (sardana)
That's where you come in. You're the maintainer and the expert in this
package. Are 251 and 221 that common and important that the other
changes are worth less testing than usual?
Ping?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ
into account Niels' feedback,
or shall this unblock request be closed?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85d28oiuoz@boum.org
to see which approach is best. But not
trimming SSDs is really quite bad these days, so from my POV it would
be quite prudent to include either the timer or the cron job in
jessie.
Agreed. I think we should ship the cronjob by default in Jessie.
Andreas, what do you think?
Cheers,
--
intrigeri
that this release
is better than the previous one (although it's rare to see any
upstream tell the contrary, so moderately useful IMO) but it
doesn't answer the specific questions that Jonathan asked you on
October 20.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ
-2
Yay.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85mw7see8z@boum.org
.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85y4rccz4f@boum.org
Hi Jean-Michel,
Jean-Michel Nirgal Vourgère wrote (15 Nov 2014 13:36:15 GMT) :
+ * Added showfoto Breaks/Replaces (Closes: #767570)
I would suggest Add versioned Breaks/Replaces on digikam-doc, that
fixes the Squeeze to Wheezy upgrade instead.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email
:
+new patch, cherry-picked from upstream, that fixes the FTBFS
+kfreebsd-* that was introduced by
+Fix-improve-Unix-socket-passing-detection.patch (Closes: #768140).
+
+ -- intrigeri intrig...@debian.org Mon, 10 Nov 2014 23:39:19 +0100
+
+torsocks (2.0.0-2) unstable; urgency=medium
Control: merge 767961 -1
Hi Simon,
Simon Richter wrote (09 Nov 2014 21:57:06 GMT) :
unblock beignet/0.9.3~dfsg-1
This was asked on #767961 already = merging those bugs.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe
+one, that we install already, needs it. This prevents the same kind
+of bug as #768357 from occurring when one uses the smbd profile.
+
+ -- intrigeri intrig...@debian.org Fri, 07 Nov 2014 11:37:45 +0100
+
apparmor (2.9.0-1) unstable; urgency=medium
* Import new upstream release
still hold.
and there is no changelog.
Indeed, the upstream changelog from 0.80.2 to 0.81 is empty.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https
Hi,
Sebastian Geiger wrote (31 Oct 2014 14:59:44 GMT) :
The complete changelog can be found directly in the package's
ChangeLog file [1]
[...]
[1] https://github.com/lanoxx/tilda/blob/master/ChangeLog
version 1.2.2 (2014-10-28):
* Fixed an error where Tilda failed to start when the
Hi,
Andreas Tille wrote (02 Nov 2014 10:59:20 GMT) :
The only reason to upload this package is a missing Breaks to fix
bug #767564.
According to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767564#15, 0.10-3
still doesn't fix that RC bug.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email
?
I doubt it would add much value, but Jonathan's point was about
getting enough information to assess severity, so perhaps you could
tell the release team what severity you _would_ set for each of these
bugs in the Debian BTS, if they were reported there?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE
Hi,
John Paul Adrian Glaubitz wrote (08 Sep 2014 22:50:44 GMT) :
Sure, will do once I am back from vacation. I am currently in Japan
until next week. Will get back to this after my journey.
Ping?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
this bug, or are stable pu
bugs handled differently? (e.g. I could imagine that bugs are only
closed at point-release time, or tagged in some way)
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Hi,
intrigeri wrote (22 Jan 2014 10:35:56 GMT) :
Daniel Pocock wrote (21 Jan 2014 17:55:15 GMT) :
On 21/01/14 18:43, intrigeri wrote:
Jonathan Wiltshire wrote (25 Sep 2013 21:59:15 GMT) :
I could provide a diff that eliminates changes in such files.
Yes, please.
AFAICT, this stable
.
Hence this friendly ping :)
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/858ujlnvvq@boum.org
+==
+
+ commit 9d20ef1aef9107a992a3b099576dc1a384a821c5
+ Author: intrigeri intrig...@boum.org
+ Date: Fri Nov 7 11:49:35 2014 +
+
+parcimonie 0.8.4
+
+ commit 14339a88178d16d4d7ece93af468d4dedb81f6a1
+ Author: intrigeri intrig...@boum.org
+ Date
Julien Cristau wrote (03 Nov 2014 22:41:53 GMT) :
+libotr (4.1.0-2) unstable; urgency=medium
Unblocked.
Thanks!
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
: #767652).
+ * debian/README.source: document how to detect and handle ABI changes.
+
+ -- intrigeri intrig...@debian.org Sat, 01 Nov 2014 18:36:49 +0100
+
libotr (4.1.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru libotr-4.1.0/debian/libotr5.symbols libotr-4.1.0/debian
Hi,
Niels Thykier wrote (30 Oct 2014 22:05:20 GMT) :
On 2014-10-29 17:09, intrigeri wrote:
Plan A -- ship Jessie with libotr 4.1, drop the version check temporarily
=
1. Patch libotr to loosen this version check
===
I've extracted the libotr5 binary packages from Jessie and sid, and
then run:
dpkg-gensymbols -v4.0.0 -plibotr5 -P/tmp/intrigeri/4.0-extracted -Osymbols
dpkg-gensymbols -v4.1.0 -plibotr5 -P/tmp/intrigeri/4.1-extracted -Osymbols
The second command tells me:
--- symbols (libotr5_4.1.0_amd64
the road.
Dear RT, what option(s) would be acceptable for you?
Sorry for the burden again..
Cheers!
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org
/changelog entry for 3.4.0-1 doesn't close any bug.
* Low popcon: 10 for libcamitk3.
as far as I understood no debdiff is needed for this request.
My understanding of the freeze policy is different:
https://release.debian.org/jessie/freeze_policy.html
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email
Andreas Tille wrote (29 Oct 2014 20:52:06 GMT) :
We are before Freeze and I was explicitly asked to follow [...]
Thanks :)
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
on the upstream website, and I could not find any
upstream changelog in the Debian source tree.
So, please point to the relevant bug reports closed by 3.3.1, that
might help convincing the release team that accepting this last-minute
upstream release is worth it. Thanks!
Cheers,
--
intrigeri
Hi,
Guido Günther wrote (05 Oct 2014 10:17:07 GMT) :
Are there any plans to unblock systemd anytime soon?
The udeb block was lifted a few hours ago, as announced by kibi.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe
of Jessie.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85egwcxpyu@boum.org
to go for Wheezy.
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85mwdcpqr6@boum.org
into wheezy-backports a package:
* coming from Wheezy
* (re)built against the current state of wheezy-backports
* that is not part of wheezy-backports yet
?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https
Julien Cristau wrote (13 Feb 2014 12:53:52 GMT) :
There's no way to do cross-suite binNMU, you need the source in
wheezy-backports first.
Thanks!
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https
Adam D. Barratt wrote (22 Jan 2014 21:35:55 GMT) :
Please go ahead; thanks.
Uploaded.
Regards,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian
unclear to me whose court the ball is in (IOW, if the moreinfo
tag still applies) after this answer.
Joachim, is the situation still that complicated in unstable that the
problems cannot be fixed there?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
Hi,
Adam D. Barratt wrote (04 Dec 2013 20:31:44 GMT) :
On Sun, 2013-11-03 at 14:05 +0530, Rahul Amaram wrote:
Updated zoneinfo data
Is there a plan for doing so in unstable?
Ping?
Regards,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR
relicensed under a suitable license, why should they get
removed from an earlier release? At best we could ship a package with
updated headers and licensing info to reflect the facts all those files
are actually OK?
Ping?
Regards,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org
AFAICT Nicolas has addressed all concerned raised by the release team,
hence I'm dropping the moreinfo tag.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE
Hi,
Daniel Pocock wrote (21 Jan 2014 17:55:15 GMT) :
On 21/01/14 18:43, intrigeri wrote:
Jonathan Wiltshire wrote (25 Sep 2013 21:59:15 GMT) :
I could provide a diff that eliminates changes in such files.
Yes, please.
AFAICT, this stable proposed update has been blocking on the lack
is now in testing. Can this binnmu request be
closed, then? If not, you'll surely want to answer the question
Julien asked.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
this will work; transmission is OOD on several
architectures because qt5-qmake is uninstallable/missing.
This still seems to be the case. Thomas, what's the plan?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https
?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
be closed.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
, and making sure the bugs are fixed
in testing/sid already. Any not-too-crazy debdiff that satisfies these
basic requirements is usually at least considered.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https
-object-introspection-perl 0.009-1+deb7u1 to stable?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
diff -Nru libglib-object-introspection-perl-0.009/debian/changelog libglib
?
Same question with s/10/17/ now I guess…
... and soon with Iceweasel 24, presumably.
François: ping?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE
update. It would automatically filter out
the move of Debian-specific patches to the upstream source, and
hopefully it will be of a size that the release team is happy
to review.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https
on this?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
/05/msg00188.html
Most importantly:
You're supposed to send a source debdiff against the package currently
in stable, properly versioned.
Teodor, ping?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https
close
this bug?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
than what this module
supports anyway. Just thought I'd mention it…
Julian, Andreas: ping? It seems to me that Cyril was asking for
a clarification at least, and quite possibly for a (trivial) regexp
improvement. Do you still plan to follow-up on this at some point?
Cheers,
--
intrigeri
| GnuPG
actually exist, what
steps can be taken within the Debian/kFreeBSD community to improve
this? I've no idea what kind of communication channels the porters
have with the corresponding users, so I'm wondering.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri
+deb7u1) stable; urgency=medium
+
+ * Non-maintainer upload with maintainer's agreement.
+ * Disable insecure OTRv1 protocol (Closes: #725779)
+
+ -- intrigeri intrig...@debian.org Sun, 22 Dec 2013 11:35:06 +0100
+
libotr (3.2.1-1) unstable; urgency=high
* Fix potential buffer overflow in base64
Hi,
Cyril Brulebois wrote (22 Dec 2013 16:51:49 GMT) :
intrigeri intrig...@debian.org (2013-12-22):
This is why I have proposed to drop support for OTRv1 in libotr in
Wheezy.
This makes me wonder whether there are some packages only supporting
OTRv1 in wheezy. If there are, I suspect
1 - 100 of 278 matches
Mail list logo
