Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: r...@packages.debian.org
Control: affects -1 + src:runc
nmu runc_1.1.5+ds1-1+b4 . ANY . unstable . -m "rebuild against
golang-github-urfave-cli_1.22.14-1"
please rebuild
On 10/8/23 8:01 AM, Jonathan Wiltshire wrote:
Hi,
This request was approved but not uploaded in time for the previous point
release (11.8). Should it be included in 11.9, or should this request be
abandoned and closed?
Apologies for dropping the ball here. I've just uploaded conmon
ncy=medium
+
+ * Recompile to fix parsing of DBUS_SESSION_BUS_ADDRESS (Closes: #1018816)
+
+ -- Reinhard Tartler Sun, 16 Apr 2023 18:16:11 -0400
+
libpod (3.0.1+dfsg1-3+deb11u3) bullseye; urgency=medium
* Fix and tighten dependencies
diff -Nru libpod-3.0.1+dfsg1/debian/control libpod-3.0.1+dfsg1/debi
diff --git a/debian/changelog b/debian/changelog
index c23b4b9b..97d97794 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+golang-github-containers-common (0.33.4+ds1-1+deb11u2) bullseye; urgency=medium
+
+ * Fix parsing of DBUS_SESSION_BUS_ADDRESS, Closes: #1018816
+
+ -- Reinha
Argh, my bad, I'll upload a new version later today
Thanks for spotting
-rt
On April 7, 2023 4:41:41 AM EST, "Adam D. Barratt"
wrote:
>On Thu, 2023-04-06 at 19:46 -0400, Reinhard Tartler wrote:
>> This code change picks up code changes in golang-github-containers-
>>
(3.0.1+dfsg1-3+deb11u2) bullseye; urgency=medium
+
+ * CVE-2022-1227: pickup changes in containers/psgo, Closes: #1020907
+ * CVE-2022-27649: do not set the inheritable capabilities, Closes: #1020906
+
+ -- Reinhard Tartler Wed, 05 Apr 2023 21:00:36 -0400
+
libpod (3.0.1+dfsg1-3+deb11u1
Control: tag -1 -moreinfo
On 4/1/23 7:04 PM, Reinhard Tartler wrote:
On 4/1/23 3:51 PM, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
Apologies for the delay in getting back to you on this.
On Wed, 2022-12-28 at 22:26 -0500, Reinhard Tartler wrote:
In order to fix CVE-2022-1227
On 4/1/23 3:51 PM, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
Apologies for the delay in getting back to you on this.
On Wed, 2022-12-28 at 22:26 -0500, Reinhard Tartler wrote:
In order to fix CVE-2022-1227, an update to golang-github-containers-
psgo
is needed, more specifically
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: con...@packages.debian.org, Dan Nicholson
Control: affects -1 + src:conmon
[ Reason ]
conmon 2.0.25 contains a bug where the container will hang when there
is
100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+golang-github-containers-psgo (1.5.2-2~deb11u1) bullseye; urgency=medium
+
+ * CVE-2022-1227: do not join the process user namespace
+
+ -- Reinhard Tartler Wed, 28 Dec 2022 21:21:57 -0500
+
golang-github-containers-psgo (1.5.2
/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+golang-github-containers-storage (1.24.8+dfsg1-2~deb11u1) bullseye;
urgency=medium
+
+ [ Vignesh Raman ]
+ * prereq to fix CVE-2022-1227: pkg: idtools: export RawTo{Container,Host}
+
+ -- Reinhard Tartler Wed, 28 Dec 2022 21:39:17 -0500
+
golang
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libpod
libpod needs to migrate together with:
golang-github-containers-common_0.50.1+ds1-2
golang-github-containers-buildah_1.28.0+ds1-3
[ Reason ]
There have
Package: release.debian.org
Severity: normal
The following two packages need to go into testing together:
golang-github-openshift-imagebuilder_1.2.3+ds1-1
golang-github-containers-buildah_1.23.1+ds1-3
golang-github-openshift-imagebuilder introduced some API changes that broke the
compilation
;>
> >> On Sun, Jun 12, 2022 at 05:33:48PM -0400, Reinhard Tartler wrote:
> >>> diff -Nru runc-1.0.0~rc93+ds1/debian/changelog runc-
> >>> 1.0.0~rc93+ds1/debian/changelog
> >>> --- runc-1.0.0~rc93+ds1/debian/changelog2022-06-12
> >>
On Sun, Jun 12, 2022 at 10:57 PM Shengjing Zhu wrote:
> X-Dbackport: do not set inheritable capabilities, Fixes:
> CVE-2022-29162ebbugs-CC: siret...@debian.org, t...@security.debian.org
>
> Hi,
>
> On Sun, Jun 12, 2022 at 05:33:48PM -0400, Reinhard Tartler wrote:
> > d
2022-06-12 14:49:36.0
-0400
+++ runc-1.0.0~rc93+ds1/debian/changelog2021-05-19 14:46:14.0
-0400
@@ -1,10 +1,3 @@
-runc (1.0.0~rc93+ds1-5+deb11u1) bullseye; urgency=medium
-
- * Team upload.
- * backport upstream patch: Honor seccomp defaultErrnoRet, Closes: #10
(1.0.2.41.g7413a7f-1+deb11u1) bullseye;
urgency=medium
+
+ * Backport seccomp patches from upstream to allow execution of newer
+syscalls, Closes: #994451
+
+ -- Reinhard Tartler Mon, 27 Sep 2021 12:12:47 -0400
+
golang-github-opencontainers-specs (1.0.2.41.g7413a7f-1) unstable;
urgency
Hi Paul,
On Sun, Oct 3, 2021 at 12:39 PM Paul Gevers wrote:
> Hi Reinhard,
>
> > The consistent OOM is surprising given that you state that the worker
> > has 250GB of RAM. Looking at the logs,
> > I note that the tests are being passed the option -p 160 by the
> > dh-golang helper, so it will
Hi Paul,
thanks for getting back to me so quickly.
Adding Nilesh and Shengjing, we were discussing this issue on a separate,
private email conversation.
On Wed, Sep 29, 2021 at 2:45 PM Paul Gevers wrote:
> Hi Reinhard,
>
> On 29-09-2021 02:56, Reinhard Tartler wrote:
> >
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package golang-github-klauspost-compress
The problem is with autopkgtest, on armel and armhf, the test
machines frequently run out of memory when executing the extensive
.
On Mon, Sep 27, 2021 at 12:08 PM Reinhard Tartler
wrote:
>
> On Thu, Sep 16, 2021 at 4:18 AM Bastien Roucariès <
> roucaries.bast...@gmail.com> wrote:
>
>> Package: golang-github-containers-common
>> Version: 0.33.4+ds1-1
>> Severity: critical
>> Tags: up
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Please hint golang-github-openshift-imagebuilder and
golang-github-containers-storage to migrate to testing together
The migration of golang-github-openshift-imagebuilder is blocked because it was
built
issue "Connection reset by peer", Closes: #989803
+
+ -- Reinhard Tartler Sun, 13 Jun 2021 18:28:49 -0400
+
libpod (3.0.1+dfsg1-2) unstable; urgency=medium
* Prefer crun over runc, Closes: #985379
diff --git a/debian/patches/networking-lookup-child-IP-in-networks.patch
b/debi
* Add depends in iptables, Closes: #987207
+
+ -- Reinhard Tartler Wed, 21 Apr 2021 17:36:07 -0400
+
libpod (3.0.1+dfsg1-1) unstable; urgency=medium
* New upstream release
diff --git a/debian/control b/debian/control
index dedbb4462..d3865b0c1 100644
--- a/debian/control
+++ b/debian/c
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: siret...@tauware.de, Filippo Giunchedi
Please unblock package libpod
Note that I have not uploaded the package yet, this is a pre-approval
request.
[ Reason ]
I as
/debian/changelog
@@ -1,3 +1,9 @@
+slirp4netns (1.0.1-2) unstable; urgency=medium
+
+ * Apply patch from upstrema to make ipv6 usable (Closes: #985780)
+
+ -- Reinhard Tartler Wed, 24 Mar 2021 07:43:48 -0400
+
slirp4netns (1.0.1-1) unstable; urgency=medium
* New upstream version 1.0.1
diff --git
Got it.
On Tue, Feb 16, 2021 at 4:03 PM Sebastian Ramacher
wrote:
> Control: severity -1 serious
>
> [...]
> Tests are executed as part of the binary target:
>
> dh binary --no-act | grep auto_test
>dh_auto_test
>
> So the "no required targets may attmept network access" rule applies.
>
Dear Golang Team,
On Mon, Feb 15, 2021 at 1:23 PM Paul Gevers wrote:
> On 15-02-2021 15:08, Reinhard Tartler wrote:
> > Control: severity -1 important
>
> I agree with this. The Debian infra allows for use of the internet (if
> not used to download programs, that's forbidde
Control: severity -1 important
Dear release team,
I'm writing as a member of the pkg-go team and am mostly concerned about
potential removal of depending packages.
The package itself appears to be fine. The tests fail if and only if the
test setup doesn't provide (proper) internet connectivity.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
It seems that there is a problem with the image cache in podman 3.0-rc2, which
turns out to be a bug in 'buildah'. I've uploaded a fix to unstable as
On Tue, Feb 2, 2021 at 3:01 PM Paul Gevers wrote:
> Unfortunately I believe we're not really in the position to advise you
> on the matter at hand as there are obviously pro's and con's for both
> side which require detailed knowledge to balance them. It seems to me
> that your having a decent
On Tue, Feb 2, 2021 at 11:54 AM Adrian Bunk wrote:
> On Sat, Jan 30, 2021 at 09:08:36PM -0500, Reinhard Tartler wrote:
> >...
> > On Mon, Jan 25, 2021 at 7:15 PM Dmitry Smirnov
> wrote:
> >...
> > A low-effort workaround could be to add a build-dependency on pod
On Mon, Feb 1, 2021 at 4:58 PM Dmitry Smirnov wrote:
>
> > The fact that as has been mentioned in this thread a) bullseye is around
> > the corner b) nomad-driver-podman isn't even in testing right now, c)
> > podman itself is a much more popular package than nomad-driver-podman
> > (or nomad
On Sat, Jan 30, 2021 at 10:33 PM Dmitry Smirnov wrote:
>
> > > No it hasn't... :( There is a serious regression:
> > > https://github.com/hashicorp/nomad-driver-podman/issues/69
> >
> > I'm having a hard time considering this a "serious" regression. The
> problem
> > as far as I understand is
trimming cc-list
On Mon, Jan 25, 2021 at 7:15 PM Dmitry Smirnov wrote:
> On Monday, 25 January 2021 10:47:25 PM AEDT Reinhard Tartler wrote:
> > It seems that https://packages.qa.debian.org/n/nomad-driver-podman.html
> > has never made it to testing, which makes me wonder whether
On Sat, Jan 30, 2021 at 5:03 PM Antonio Terceiro
wrote:
> FWIW I have been using podman 3.0.0~rc1 from experimental for a few days
> and haven't noticed anything wrong with it. I hope we can have that
> version in bullseye.
>
Me too.
Dear release team, do you have any opinion on this topic?
On Sun, Jan 24, 2021, 21:52 Dmitry Smirnov wrote:
> On Monday, 25 January 2021 12:02:26 PM AEDT Reinhard Tartler wrote:
> > - Podman 3 drops the legacy varlink interface. To the best of my
> > knowledge, there are no packages in debian/testing that would require
> > varli
Dear release-team,
I'm proposing to have podman 3.0 in debian/bullseye. As maintainer of the
package, I'm convinced this is a good step for Debian because:
- podman 3.0 will be included in RHEL 8.4, which will be released in May
2021. I expect security support for podman in Debian to become
On Wed, Dec 9, 2020 at 2:32 PM Paul Gevers wrote:
>
> These kind of build failures should be fixed. Builds that regularly fail
> are not OK. Same goes for autopkgtest. Flaky tests are RC.
>
Agreed.
> > What's involved with retrying autopkgtests on arm64? -- CC'ing
> > debian-release@, maybe
successfully. That's why I'm optimistic about
retrying the autopkg tests for consul.
What's involved with retrying autopkgtests on arm64? -- CC'ing
debian-release@, maybe they have some input?
Best,
-rt
On Mon, Dec 7, 2020 at 6:43 AM Reinhard Tartler wrote:
> Ok, thanks!
>
> I have
ce.
>>
>> On Wed, Aug 07, 2019 at 06:13:08PM -0400, Reinhard Tartler wrote:
>>> Hi Security Team,
>>>
>>> I have not received an answer to my question below. Any chance you
>>> could get back to me on that?
>>
>> Unless I severe
9452979..23246df 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+libheif (1.3.2-2) unstable; urgency=medium
+
+ * Team Upload
+
+ [ Dylan Aïssi ]
+ * Add patch to fix CVE-2019-11471, Closes: #928210
+
+ -- Reinhard Tartler Sat, 01 Jun 2019 17:56:05 -0400
+
libheif
g fix: "CVE-2019-11221: buffer-overflow issue in gf_import_message()
+in media_import.c", thanks to Salvatore Bonaccorso (Closes: #926963).
+
+ -- Reinhard Tartler Sat, 13 Apr 2019 16:41:15 -0400
+
gpac (0.5.2-426-gc5ad4e4+dfsg5-4.1) unstable; urgency=medium
* CVE-2018-7752 (Closes: #8
+
+ * Acknowledge NMU.
+ * Bug fix: "driver breaks with pcsc-lite versions >= 1.8.21", thanks
+to Peter Wienemann (Closes: #926103).
+
+ -- Reinhard Tartler Mon, 08 Apr 2019 17:58:31 -0400
+
pcsc-cyberjack (3.99.5final.sp09-1.1) unstable; urgency=medium
* Non-maintainer uplo
+
+ * Acknoledge NMU.
+ * Bug fix: "driver breaks with pcsc-lite versions >= 1.8.21", thanks
+to Peter Wienemann (Closes: #926103).
+
+ -- Reinhard Tartler Mon, 08 Apr 2019 17:58:31 -0400
+
pcsc-cyberjack (3.99.5final.sp09-1.1) unstable; urgency=medium
* Non-maintainer
On 4/4/19 3:38 PM, Moritz Mühlenhoff wrote:
> On Tue, Apr 02, 2019 at 10:40:44PM -0400, Reinhard Tartler wrote:
>> Ah, that's great news. I didn't realize that Moritz backported the
>> security fixes to an earlier upstream version. I managed to locate the
>> git commits b
On 4/2/19 3:08 PM, Niels Thykier wrote:
> Thorsten Alteholz:
>> Hi Reinhard,
>>
>> On Tue, 2 Apr 2019, Reinhard Tartler wrote:
>>> Now about 6 weeks have passed since I've been uploading this package, and
>>> I do have a question: Is there anything wron
Dear ftp-master team,
On 2/15/19 7:20 AM, Debian FTP Masters wrote:
> binary:libgpac7 is NEW.
> binary:libgpac7 is NEW.
>
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature
+1,11 @@
+jackd2 (1.9.10+20150825git1ed50c92~dfsg-5) unstable; urgency=medium
+
+ * Move libjackserver into package libjack-jackd2-0. This avoids a
+dangling symbolic link in the package libjack-jackd2-dev.
+(Closes: #858525)
+
+ -- Reinhard Tartler <siret...@tauware.de> Mon, 27 Ma
, 2016 at 11:55 AM Adam D. Barratt <a...@adam-barratt.org.uk>
wrote:
> On Sun, 2016-06-12 at 15:41 +, Reinhard Tartler wrote:
>
> > I wonder why boxbackup did not migrate to testing. According to
> > https://release.debian.org/migration/testing.pl?package=boxbackup th
Hi,
I wonder why boxbackup did not migrate to testing. According to
https://release.debian.org/migration/testing.pl?package=boxbackup the issue
is a missing armhf build. However,
https://buildd.debian.org/status/logs.php?arch=armhf=boxbackup=0.11.1~r2837-1
indicates
it built just fine.
What's
On December 7, 2015 4:37:03 PM EST, "Adam D. Barratt"
<a...@adam-barratt.org.uk> wrote:
>Control: tags -1 + pending
>
>On Sun, 2015-12-06 at 19:33 -0500, Reinhard Tartler wrote:
>> I'm writing you to request approving my recent upload of
>> keepassx_0.4.3+d
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Dear Release Team,
I'm writing you to request approving my recent upload of
keepassx_0.4.3+dfsg-0.1+deb8u1. This update addresses
CVE-2015-8378/#791858. I'm copying Moritz, since
On Fri, Nov 28, 2014 at 1:34 AM, Niels Thykier ni...@thykier.net wrote:
Control: tags -1 -wheezy-ignore
On 2014-11-27 23:23, Jonas Smedegaard wrote:
Quoting Niels Thykier (2014-11-27 22:14:25)
[...]
In prior similar bugreport https://bugs.debian.org/760171#10 -
referenced from
On Fri, Sep 26, 2014 at 5:28 PM, Andreas Barth a...@ayous.org wrote:
That sounds like we should drop libav and release with ffmpeg. Is this
also the opinion of the libav maintainers? Or is there a strong reason
why this is not possible?
This was extensively discussed previously on
On Tue, Aug 26, 2014 at 6:31 PM, Reinhard Tartler siret...@gmail.com wrote:
On Tue, Aug 26, 2014 at 4:29 PM, Emilio Pozuelo Monfort
po...@debian.org wrote:
On 26/08/14 16:05, Reinhard Tartler wrote:
On Mon, Aug 18, 2014 at 4:25 PM, Emilio Pozuelo Monfort
po...@debian.org wrote:
On 18/08/14
On Mon, Aug 18, 2014 at 4:25 PM, Emilio Pozuelo Monfort
po...@debian.org wrote:
On 18/08/14 21:33, Andrew Kelley wrote:
On Aug 18, 2014 12:22 PM, Emilio Pozuelo Monfort po...@debian.org wrote:
I want to get perl in first. Ping me again when that happens if I haven't
replied.
Pardon my
On Tue, Aug 26, 2014 at 4:29 PM, Emilio Pozuelo Monfort
po...@debian.org wrote:
On 26/08/14 16:05, Reinhard Tartler wrote:
On Mon, Aug 18, 2014 at 4:25 PM, Emilio Pozuelo Monfort
po...@debian.org wrote:
On 18/08/14 21:33, Andrew Kelley wrote:
On Aug 18, 2014 12:22 PM, Emilio Pozuelo Monfort
On Sat, Aug 16, 2014 at 11:24 AM, Reinhard Tartler siret...@gmail.com wrote:
vlc FAIL (silly configure check fail, will sort out with upstream)
Turns out to be sligtly more complicated as thought. After
consultation with j-b (videolan upstream), we decided that we really
should go with vlc
On Wed, Aug 13, 2014 at 9:07 PM, Reinhard Tartler siret...@gmail.com wrote:
linphone FAIL,
#758017, NMU uploaded to 5/days
vlc FAIL (silly configure check fail, will sort out with upstream)
Turns out to be sligtly more complicated as thought. After
consultation with j-b (videolan upstream
On Wed, Aug 13, 2014 at 9:07 PM, Reinhard Tartler siret...@gmail.com wrote:
gst-libav1.0 FAIL (fixed in 11~alpha2-1)
[...]
gst-libav: will be fixed with a new libav package that I'm about to upload
confirmed that gst-libav can now that be binNMUed against
libav_11~alpha2-1 or later
On Aug 14, 2014 8:18 AM, Emilio Pozuelo Monfort po...@debian.org wrote:
On 12/08/14 13:41, Reinhard Tartler wrote:
A prerelease for
Libav11 that passes upstream's extensive test suite is currently in
debian/experimental, and I'll make sure that the final release will be
done and uploaded
On Wed, Aug 13, 2014 at 5:25 PM, Emilio Pozuelo Monfort
po...@debian.org wrote:
There already is https://release.debian.org/transitions/html/auto-libav.html
Lovely!
This sounds good in principle, but I would like to hear about the results of a
mass-rebuild of the rdeps.
OK, I've let me
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
I would like to upload libav11 to unstable, which requires the
recompilation of any package that links against it. A prerelease for
Libav11 that passes upstream's extensive test
Package: release.debian.org
I believe Aspectc++ is currently kept out of testing because it FTBFS on
armel and armhf. Neither I nor upstream have the resources to support
these architectures, and users won't use this package on arm generally
anyways.
Can you please give guidance on what can be
Now that libav transitioned to testing, and
https://release.debian.org/transitions/ says '100%' next to the libav
transition, what's left to be done here?
Best,
Reinhard
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Thu, May 15, 2014 at 12:39 PM, Moritz Muehlenhoff j...@inutil.org wrote:
On Tue, May 13, 2014 at 10:31:14PM +0200, Julien Cristau wrote:
On Tue, May 13, 2014 at 17:37:58 +0200, Julien Cristau wrote:
On Tue, May 13, 2014 at 17:00:32 +0200, Moritz Muehlenhoff wrote:
nmu tupi_0.2+git04-1
On Mon, May 12, 2014 at 5:01 AM, Julien Cristau jcris...@debian.org wrote:
On Sun, May 11, 2014 at 22:02:38 -0400, Reinhard Tartler wrote:
Hi,
The following packages from pkg-multimedia build just fine for me:
nmu lives_2.2.4~ds0-2 . ALL . -mrebuild against libav10
nmu chromaprint_1.1-1
On Sun, May 11, 2014 at 9:16 AM, Julien Cristau jcris...@debian.org wrote:
On Thu, May 8, 2014 at 20:35:55 -0400, Reinhard Tartler wrote:
On Tue, May 6, 2014 at 9:39 AM, Bálint Réczey bal...@balintreczey.hu wrote:
When do you plan starting the transition? How about opening it with
Libav
On Sun, May 11, 2014 at 11:50 AM, Julien Cristau jcris...@debian.org wrote:
On Sun, May 11, 2014 at 11:25:49 -0400, Reinhard Tartler wrote:
for the rest, I'd think that there is a very good chance that the
respective maintainers are going to fix them before they turn out to
be actual blockers
On Sun, May 11, 2014 at 12:20 PM, Julien Cristau jcris...@debian.org wrote:
Control: tag -1 confirmed
On Sun, May 11, 2014 at 12:05:55 -0400, Reinhard Tartler wrote:
On Sun, May 11, 2014 at 11:50 AM, Julien Cristau jcris...@debian.org wrote:
Would a timeline like this work for you:
- T
Hi,
The following packages from pkg-multimedia build just fine for me:
nmu lives_2.2.4~ds0-2 . ALL . -mrebuild against libav10
nmu chromaprint_1.1-1 . ALL . -mrebuild against libav10
nmu libffms2-3_2.19.1-1 . ALL . -mrebuild against libav10
nmu idjc_0.8.14-1 . ALL . -mrebuild against libav10
On Tue, May 6, 2014 at 9:39 AM, Bálint Réczey bal...@balintreczey.hu wrote:
When do you plan starting the transition? How about opening it with
Libav 10.1? ;-)
I think we are in a pretty good position for startin now.
I agree. Let me upload 10.1 this weekend to unstable to finally start
this
On Sat, Apr 5, 2014 at 9:31 AM, Reinhard Tartler siret...@tauware.de wrote:
On 05.04.2014 08:46, Julien Cristau wrote:
Control: tag -1 confirmed
On Fri, Feb 14, 2014 at 13:27:53 +, Reinhard Tartler wrote:
Package: release.debian.org
Severity: normal
User: release.debian
On 31.03.2014 15:27, Julien Cristau wrote:
On Wed, Feb 26, 2014 at 22:37:41 +, Reinhard Tartler wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I believe this should should be rather easy, as only libx264 links
against
On 05.04.2014 08:46, Julien Cristau wrote:
Control: tag -1 confirmed
On Fri, Feb 14, 2014 at 13:27:53 +, Reinhard Tartler wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I've prepared a new upstream release of libx264
On Sun, Mar 16, 2014 at 3:10 PM, Julien Cristau jcris...@debian.org wrote:
Control: tag -1 moreinfo
On Fri, Feb 14, 2014 at 13:27:53 +, Reinhard Tartler wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I've prepared
Package: xine-lib
Severity: serious
Hi,
According to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739453#17, the plan is
to migrate all applications to xine-lib-1.2 anyways.
This bug may or may not be reused to coordinate this transition.
-- System Information:
Debian Release: 7.4
APT
On Tue, Feb 18, 2014 at 4:48 PM, Moritz Mühlenhoff j...@inutil.org wrote:
I made a rebuild and the transitions isn't ready to go at all.
IMO the API changes are far too agressive; if 2/3 of all packages in
the archive FTBFS, the affected APIs are clearly not that deprecated.
I can understand
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I believe this should should be rather easy, as only libx264 links
against gpac AFAIUI. I'd therefore suggest to do this transition
together with #738978.
Ben file:
title = gpac;
On Sun, Feb 16, 2014 at 11:22 AM, Moritz Mühlenhoff j...@inutil.org wrote:
Reinhard Tartler siret...@tauware.de schrieb:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
We have a new libav transition pending. Libav 10
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
We have a new libav transition pending. Libav 10 is prepared in
debian/experimental, and I've started to build packges against this new
version; in fact, more or more packages
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I've prepared a new upstream release of libx264, and we need to rebuild
all applications that link against it. AFAIUI, this transition should be
rather smooth because it affects only a
Hi,
I wonder why the package aspect++ does not migrate. According to
http://release.debian.org/migration/testing.pl?package=aspectc++, it
seems to be because of missing arm builds. I expected that not to
matter as the package is no longer in testing, but obviously I'm
wrong.
Upstream is aware of
On Wed, Oct 16, 2013 at 10:01 AM, Alessio Treglia ales...@debian.org wrote:
On Wed, Oct 16, 2013 at 2:49 PM, Fabian Greffrath fab...@greffrath.com
wrote:
Cool, thanks! So, when will this be uploaded?
Unfortunately not earlier than Wheezy's next point release.
Alessio, I think there is a
On Wed, Oct 9, 2013 at 10:16 AM, shirish शिरीष shirisha...@gmail.com wrote:
Hi all,
It was nice to see updates happening on this transition but some
packages are still to go through (it seems).
I did the updates and only one of the obsolete packages have some
dependencies which have not been
On Sun, Aug 18, 2013 at 1:15 AM, Julien Cristau jcris...@debian.org wrote:
On Wed, Aug 14, 2013 at 16:18:38 +0200, Moritz Muehlenhoff wrote:
Since libx264 is largely subsumed by libav, I think it makes very
much sense to do them both at the same time. I am convinced that we
will
On 13.08.2013 11:48, Julien Cristau wrote:
On Sun, May 5, 2013 at 07:45:40 +0200, Reinhard Tartler wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I would like to upload Libav 9 to unstable at your earliest
convinience
On Di, Aug 13, 2013 at 14:30:03 (CEST), Julien Cristau wrote:
On Tue, Aug 13, 2013 at 12:56:46 +0200, Reinhard Tartler wrote:
On 13.08.2013 11:48, Julien Cristau wrote:
On Sun, May 5, 2013 at 07:45:40 +0200, Reinhard Tartler wrote:
Package: release.debian.org
Severity: normal
User
On Sun, Jun 2, 2013 at 11:32 AM, Julien Cristau jcris...@debian.org wrote:
Procedural question: Are these bugs blockers to start the transition?
Does the release team require all of them to be fixed in experimental
(via MU or NMUs) before uploading libav9 to unstable?
Not necessarily, but
On Sun, Jun 2, 2013 at 1:27 AM, Sebastian Ramacher sramac...@debian.org wrote:
Control: block -1 by 692980 694131 693560 693639 693641 692809 692505
For the record, the following packages are known to FTBFS against libav
9:
audacious-plugins: #692505
audacity: #692809
electricsheep:
On Thu, May 30, 2013 at 8:54 AM, José Manuel Santamaría Lema
panfa...@gmail.com wrote:
Hello Reinhard,
Reinhard Tartler siret...@gmail.com
On Wed, May 29, 2013 at 12:18 AM, José Manuel Santamaría Lema
panfa...@gmail.com wrote:
Hello,
unless I'm missing something, I think in the ben
On Wed, May 29, 2013 at 12:18 AM, José Manuel Santamaría Lema
panfa...@gmail.com wrote:
Hello,
unless I'm missing something, I think in the ben file you may have missed:
- In Bad: packages depending on libavcodec-extra-53, libavcodec-extra-53 and
libavutil-extra-51
- In Good: packages
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
We would like to upload a new version of libx264 to unstable. There are
no API changes, but a few additional defines that requires acouple of rebuilds.
Ben file:
title = x264;
On Mo, Mai 20, 2013 at 21:26:49 (CEST), Adam D. Barratt wrote:
On Mon, 2013-05-20 at 13:46 +0200, Reinhard Tartler wrote:
title = x264;
is_affected = .depends ~ libx264-129 | .depends ~ libx264-130;
is_good = .depends ~ libx264-130;
is_bad = .depends ~ libx264-129;
libx264-129 only exists
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
I would like to upload Libav 9 to unstable at your earliest
convinience. To get an overview about the size and impact of the
transition, I would like to drag your attention to the Ubuntu
On Mon, Oct 29, 2012 at 7:12 PM, Moritz Muehlenhoff j...@debian.org wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libav. It fixes multiple security issues:
CVE-2012-2772
CVE-2012-2775
On Sun, Sep 23, 2012 at 10:47 PM, Michael Marineau m...@marineau.org wrote:
If pkg-config is not installed the libbluray configure script will happily
disalbe libxml2/metadata support without a fuss. This is what apears to be
what happened do the current version in testing, 0.2.2-1. By chance
+(Closes: #683895).
+
+ [ Reinhard Tartler ]
+ * use EPOCH macro in SHLIBS_VERSION
+ * Drop the package 'libav-regular-dbg'. It was not included in squeeze.
+
+ -- Reinhard Tartler siret...@tauware.de Sat, 25 Aug 2012 11:08:48 +0200
+
libav (6:0.8.3-6) unstable; urgency=low
* Clarify
tags 683247 -moreinfo
retitle 683247 unblock libav_6:0.8.3-6
stop
On Mon, Jul 30, 2012 at 2:17 PM, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
On 30.07.2012 08:08, Reinhard Tartler wrote:
I intend to work on a new upload that incorporates your suggestions
for clarifying the debian
1 - 100 of 206 matches
Mail list logo
