Hi,
top-posting and leaving quite some context because the main point of my
message is to actually share your bug report to the release team.
If I remember correctly, tracker.debian.org is not doing any fancy
treatment. We are just turning some YAML into HTML:
https://release.debian.org/britney/ex
Hello,
we have been bitten by this in Kali too. In our case Arnaud Rebillout
worked around it by adding a hint. Here's what he said:
The issue was a circular dependency between
`libnginx-mod-http-lua/1:0.10.22-2` and `lua-resty-core/0.1.24-2`. It was
solved with the following hints:
# 2022-
On Sat, 30 Jul 2022, László Böszörményi (GCS) wrote:
> On Thu, Jul 28, 2022 at 9:56 PM Ben Hutchings wrote:
> > - Is there a plan to change reverse-dependencies to depend on fuse3, so
> > that such conflicts don't occur?
> Please note I do not maintain the reverse dependent fuse2 packages.
> But
Hi Utkarsh,
On Tue, 14 Sep 2021, Utkarsh Gupta wrote:
> On Thu, Aug 26, 2021 at 12:33 AM Utkarsh Gupta wrote:
> > > The missing key creates problems for example with simple-cdd:
> > > https://bugs.debian.org/992966
> >
> > Okay, I'll be happy to do the update. Though I wonder if it'd rather
> > b
Hello,
On Sat, 04 Sep 2021, Adam D. Barratt wrote:
> On Mon, 2021-08-16 at 12:02 +0200, Raphael Hertzog wrote:
> > I would like to update "psmisc" in buster to fix a regression in
> > "killall". The bug https://bugs.debian.org/912748 was never fixed in
> >
[ Ccing debian-release in case they have some advice / concerns to express ]
Hello LTS team,
it would be nice if we could get an update of debian-archive-keyring
in stretch to add the bullseye key just like it has been done in buster a
while ago:
https://tracker.debian.org/news/1236764/accepted-d
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: raph...@freexian.com csm...@debian.org
Hello,
I would like to update "psmisc" in buster to fix a regression in
"killall". The bug https://bugs.debian.org/912748 was ne
Hello,
On Wed, 31 Mar 2021, Lee Garrett wrote:
> Unfortunately 2.10 didn't make it into bullseye in time (#984557). I tried
> getting the unit tests from 2.9.16 to work with python 3.9, but I had to give
> up. I don't feel comfortable with maintaining such a large package over the
> lifecycle of b
Control: severity -1 important
I'm reducing the severity of this bug because this forbids
mailcap and mime-support to migrate to testing and they have to
migrate because the current mime-support is uninstallable in
a freshly installed testing system because media-types
(installed by default due to
Control: tag -1 + patch
On Thu, 10 Oct 2019, Ansgar wrote:
> https://wiki.debian.org/DebianRepository/Format#A.22Release.22_files
> says one of Suite and Codename is required. Codename itself is not required.
Ok.
> I wouldn't be surprised if many tools just use one and assume it always
> exists
Hi,
On Fri, 30 Aug 2019, Alexander Wirt wrote:
> > We're not speaking of crap software, we're just speaking of software that
> > can't be maintained multiple years by backports of security patches, where
> > we get fixes only with new upstream versions (mixed with new features).
> I don't want to
On Fri, 30 Aug 2019, Alexander Wirt wrote:
> There were several discussions over the last years. And yes, our vision of
> backports does not match the vision of those fastpace/not ready for
> stable/whatever you call them repos. In our vision debian-backports consists
> of new (tested, as in "is in
Hi,
On Fri, 30 Aug 2019, Pirate Praveen wrote:
> Fast Track repo works exactly like current backports except the packages
> are added from unstable (or experimental during transitions and freeze)
> as they cannot go to testing and hence to current backports.
>
> As Paul noted earlier, backports t
(Note: pkg-security@tracker.d.o is not a valid email, dropped)
Hi,
On Thu, 29 Aug 2019, Holger Levsen wrote:
> > In general, we (Debian) don't have a good answer to this problem and
> > virtualbox is clearly a bad precedent. We really need to find a solution
> > to this in concertation with the r
Hi Niels,
On Sun, 30 Dec 2018, Niels Thykier wrote:
> We are considering to deprecate the "legacy package layout" and remove
> the "--control-files" option.
In Kali we are using neither of those features.
http://git.kali.org/gitweb/?p=britney2.git has our britney fork and
configuration.
Configu
Hi,
On Fri, 06 Apr 2018, Paul Gevers wrote:
> > Also I see the age-requirement bumped to 15 but it would be nice to
> > also have somewhere the details of why we got 15 instead of the usual
> > value.
>
> Can you explain what you find unclear in the excuses text (check the
> html version please)?
Hello Paul,
On Sun, 01 Apr 2018, Paul Gevers wrote:
> (including nthykier) to prepare the integration of britney with
> autopkgtest results. We believe the work has reached a state where full
> deployment can be considered. Let me describe how it is designed to work
> and what I request from you.
Hi,
On Tue, 09 Jan 2018, Brian May wrote:
> Raphael Hertzog writes:
>
> > I think this mail went through the cracks as we haven't received a reply
> > from you so far. Can you let us know the status and whether we can help to
> > get the wheezy update out ?
>
Hello Michael,
I think this mail went through the cracks as we haven't received a reply
from you so far. Can you let us know the status and whether we can help to
get the wheezy update out ?
Cheers,
On Mon, 23 Oct 2017, Antoine Beaupré wrote:
> On 2017-07-19 11:35:56, Michael Shuler wrote:
> > O
Hi,
On Fri, 29 Sep 2017, Adam D. Barratt wrote:
> > We already missed the first point release and the change has now been
> > in unstable for a long time already.
>
> Mostly on the basis that the changes have persisted "as is" in
> unstable, I guess doing so is probably better than nothing. Pleas
Hello,
On Fri, 30 Jun 2017, Cyril Brulebois wrote:
> > So let me know what I should upload:
> > - only the bash-completion fix
> > - or the whole update that I wanted to push
>
> Michael, any comments on the proposed systemd change for jessie, please?
Michael said that he had nothing to add. Can
Hi,
On Fri, 08 Sep 2017, Raphaël Hertzog wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
>
> nmu gnuradio_3.7.11-1 . ANY . unstable . -m "Rebuild for codecs2 transition"
Here it seems to be last and only update needed of t
Hello Michael, can you reply since Cyril requested your input and this
stable update seems to be blocked on this. Thank you !
(leaving the whole message below for reference)
On Sat, 01 Jul 2017, Cyril Brulebois wrote:
> Cyril Brulebois (2017-06-30):
> > Raphael Hertzog (2017-06-29):
Hi,
On Tue, 27 Jun 2017, Cyril Brulebois wrote:
> Anyway, no objection on the patch itself, except for the lack of
> documentation in the changelog. I'm attaching a new debdiff which is a
> bit more descriptive.
Thanks, I updated the changelog in git and I uploaded.
Cheers,
--
Raphaël Hertzog ◈
Hi,
On Tue, 27 Jun 2017, Cyril Brulebois wrote:
> Personally, I find the systemd part a bit touchy, but I'm happy to ACK
> the bash-completion fix on its own. Maybe we could handle this in two
> steps, until the systemd unit situation settles (#865110)?
I consider #865110 to be a minor cleanup th
On Mon, 19 Jun 2017, Michael Biebl wrote:
> Given that, I wonder if a stable upload is actually still needed.
The stable upload also fixes the bash completion file and fixes
the dependencies of the service file to not depend on the systemd version
of $network in the LSB dependencies.
Cheers,
--
Hello Michael,
On Sat, 17 Jun 2017, Michael Biebl wrote:
> I would suggest to simply ship a drop-in snippet for schroot, which sets
> the Type and Timeout.
Thanks for the suggestion but I'll skip it. This is what I would have
expected DSA to do if I had not shipped a systemd service unit. But now
Hi Julien,
On Sat, 17 Jun 2017, Julien Cristau wrote:
> > Re-purposing the bug to that end. Let me know when you are happy with an
> > upload to stretch.
>
> The d/rules change means I'd like to see a binary debdiff
> (--controlfiles ALL).
Here it is:
[The following lists of changes regard file
Control: retitle -1 stretch-pu: schroot/1.6.10-3+deb9u1
Control: tag -1 + stretch
Control: user release.debian@packages.debian.org
Control: usertags -1 = pu
On Tue, 06 Jun 2017, Jonathan Wiltshire wrote:
> > - the completion code is completely broken (#855283)
> > - a member of the DSA team as
Control: tag -1 - moreinfo
Just a ping since Laurent already provided the extra information
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861926#19
It's about https://security-tracker.debian.org/tracker/CVE-2017-6100
We agreed with the security team to fix it through jessie-pu, cf
https://
On Sat, 31 Dec 2016, Julien Cristau wrote:
> On Thu, Dec 22, 2016 at 13:37:11 +0100, Sebastian Andrzej Siewior wrote:
>
> > tl;dr: Has anyone a problem if sslscan embeds openssl 1.0.2 in its
> > source?
> >
> > sslscan [0] as packaged in Debian currently relies on external libssl as
> > provided
Control: retitle -1 ncrack should switch to OpenSSL >= 1.1 at some point
On Thu, 01 Dec 2016, Salvatore Bonaccorso wrote:
> reopen 844303
> severity 844303 important
> unblock 827061 with 844303
> thanks
>
> Hi
>
> Rationale: the package would still FTBFS with OpenSSL 1.1. Thus
> (bacause it is
Hi,
On Mon, 25 Jul 2016, Emilio Pozuelo Monfort wrote:
> You should file bugs against the build-rdeps so they build-depend on
> libftp-dev instead of ftplib-dev.
Done: #832522 to #832525.
Severity normal since it's not blocking anything. I hope that's correct.
Cheers,
--
Raphaël Hertzog ◈ Debi
On Tue, 28 Jun 2016, Julien Cristau wrote:
> Please go ahead.
Thanks, uploaded 1.7.11-1.
Note that I had to merge in the latest security updates and due to
git-dpm usage by the python team and its lack of proper merge support
(#801667), there is some noise in the debdiff due to renamed patches.
On Fri, 22 Jul 2016, Emilio Pozuelo Monfort wrote:
> Go ahead.
Uploaded (4.0-1-2).
> The provides is not enough while the old package is still available, as real
> packages are preferred. We'll need to get the old -dev decrufted once ftplib
> is
> built everywhere, so the new one is picked up. T
On Thu, 09 Jun 2016, Ludovic Drolez wrote:
> Hi!
>
> I'm ready to upload a new package without the patch below.
Note that defined(@array) is failing with Perl in stretch... that might be
why the patch got added in the packaging.
(But in any case the test is useless with "@Backups > 0" being equi
Control: reassign -1 src:gstreamer1.0
Control: affects -1 totem
Control: retitle -1 version mismatch between libgstreamer and plugins break
video playback in totem
Hello,
On Mon, 04 Apr 2016 17:33:51 +0800 Paul Wise wrote:
> I can no longer play anything using totem.
>
> This file cannot be pl
Hi,
On Sun, 20 Mar 2016, Adam D. Barratt wrote:
> > +dolibarr (3.5.5+dfsg1-1+deb8u1) UNRELEASED; urgency=high
> > +
> > + * Fix CVE-2016-1912 (Closes: #812496)
> > + * Fix CVE-2015-8685 (Closes: #812449)
> > + * Fix CVE-2015-3935 (Closes: #787762)
> > +
> > + -- Laurent Destailleur (eldy) Tue
On Tue, 23 Feb 2016, Adam D. Barratt wrote:
> Are you asking about stable or stable-security? Your changelog doesn't say
> either but you appear to have CCed the Security Team whilst following up to
> a release.debian.org bug.
It was mostly meant for the security team for now. They haven't said
wh
On Mon, 22 Feb 2016, Holger Levsen wrote:
> does that even work? AIUI this would require LTS uploaders
> to have access to security.d.o, which won't happen because
> of embargoed issues…
Access to security.d.o is only needed if you have to approve the uploads.
Here the suite will be reconfigure
Hi,
On Tue, 23 Feb 2016, Guido Günther wrote:
> > >
> > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=prep-wheezy-lts;users=debian-...@lists.debian.org
> >
> > While these two are long-standing enhancement bugs which would make
> > the security team work much easier, they are unrelated
Control: tag -1 - moreinfo
On Sat, 20 Feb 2016, Julien Cristau wrote:
> Please provide a more detailed changelog.
Please see the upstream release notes here for all versions between what's
in jessie and what I want to upload:
https://docs.djangoproject.com/en/1.7/releases/1.7.8/
3 bug fixes:
On Tue, 02 Feb 2016, Niels Thykier wrote:
> > Greg's new policy is to pick the first Linus release in each year for
> > longterm maintenance. The longterm branch for 2016 is based on Linux
> > 4.4, released at the end of week 1 (10th January). By the time stretch
> > is released, 4.4 will be quit
Hello dear release team,
On Fri, 11 Dec 2015, Raphael Hertzog wrote:
> I would like to update python-django in jessie to the latest upstream bug
> fix release in the 1.7.x branch, aka 1.7.11. It should also be the last
> upstream release in that branch since it's now unsupported u
Hi,
On Tue, 12 Jan 2016, Michael Biebl wrote:
> I don't think there is any new open RC bug which would prevent the
> testing migration. Or am I missing your point?
No, I was just misled by the testing migration data on the tracker
that still showed one open... but it went away now as the bug has
Hi,
On Wed, 08 May 2013, Julien Cristau wrote:
> britney doesn't currently check that required+important+standard
> packages are all co-installable. It might be a good idea to add a
> faux-package to check that?
This check would probably have avoided #810785 where ifupdown 0.8.6
entered testing
On Fri, 01 Jan 2016, Adam D. Barratt wrote:
> On Wed, 2015-12-09 at 23:40 +0100, Raphaël Hertzog wrote:
> > I would like to update the Debian Administrator's Handbook in jessie
> > so that it documents jessie instead of wheezy. We finished the update
> > about a month ago and basicly I'd like to up
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hello,
I would like to update python-django in jessie to the latest upstream bug
fix release in the 1.7.x branch, aka 1.7.11. It should also be the last
upstream release in that bra
Hi,
On Fri, 04 Dec 2015, Andreas Cadhalpun wrote:
> there seems to be a recent regression in the handling of news, causing
> duplicates.
> Packages migrating to testing now produce three news entries like e.g. [1-4]:
> "[2015-12-04] ffmpeg 7:2.8.3-1 MIGRATED to testing (Debian testing watch)"
>
Hi,
On Thu, 11 Jun 2015, Jonathan Wiltshire wrote:
> Seeing as that's been open for nearly a month now with no response, and
> webdis has no reverse dependencies, let's go ahead with the transition and
> break webdis at the end if required.
>
> Please upload to unstable.
This transition has been
On Thu, 18 Jun 2015, Adam D. Barratt wrote:
> Please go ahead.
Thanks, uploaded.
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--
To UNSUBSCRIBE, email to debian-release-requ
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hello,
I would like to update python-reportlab in jessie as it suffers from a
regression compared to wheezy in the way it handles PNG with transparency
(see #785023 for details). Wo
Hello Matthias and the release team,
On Mon, 11 May 2015, Claude Paroz wrote:
> Reportlab crashes when getting the transparency of some PNG images during
> PDF rendering.
> This is apparently a known problem and it has been fixed upstream:
> https://bitbucket.org/rptlab/reportlab/commits/7df61e325
Control: reopen -1
Control: retitle -1 jessie-pu: python-crcmod
Control: user release.debian@packages.debian.org
Control: usertag -1 = pu
On Fri, 17 Apr 2015, Ivo De Decker wrote:
> It's too late for new uploads.
Then let's deal with it via jessie-pu. Please review the change
and let us know
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-crcmod
The package suffers from a severe performance limitation described in
#782379 because it lacks the C extension that it was supposed to contain.
The pac
[ Moving it to -lts to continue the discussion ]
Hi,
On Thu, 16 Apr 2015, Stuart Prescott wrote:
> > cf http://wiki.debian.org/LTS
>
> There is an on-going confusion in the wider Debian community about whether
> squeeze is still supported or EOL.
Where did you notice any confusion?
> The sque
On Thu, 16 Apr 2015, Stefano Rivera wrote:
> +- Correct EOL date of Debian 6.0 "Squeeze" to 2014-05-31.
FWIW, Debian 6 Squeeze is supported for at least 5 years (i.e. 2016-02-06) and
most likely until Wheezy is no longer supported (i.e. 2016-04-24).
cf http://wiki.debian.org/LTS
--
Raphaël
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal
Hello,
I'm wondering whether bin-NMU are possible in squeeze-lts for packages
which are not in squeeze-lts but in squeeze only.
My question is related to the handling of
https://security-tr
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-django
There's a new upstream security/bugfix release fixing two CVE that I just
uploaded to unstable:
https://docs.djangoproject.com/en/1.7/releases/1.7.7/
A
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-django
Upstream has published a new bugfix release (1.7.5) and a new security
release (1.7.6). And as I have already argued in #775892, I believe
that we shoul
Hi Mehdi,
On Tue, 17 Feb 2015, Mehdi Dogguy wrote:
> Le 2015-02-04 09:01, Raphael Hertzog a écrit :
> >it's been two weeks that I have opened this pre-approval request
> >and I got almost no feedback from the release team (except Neil saying
> >that he has no answer fo
Control: retitle -1 unblock: python-django/1.7.4-1
On Wed, 04 Feb 2015, Raphael Hertzog wrote:
> File the above bug report with severity serious and upload 1.7.4-1 to
> sid closing the bug.
Now done.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexi
Hi,
On Sun, 08 Feb 2015, Ivo De Decker wrote:
> On Wed, Jan 28, 2015 at 09:50:30AM +0100, Raphael Hertzog wrote:
> > Please unblock package dolibarr
>
> > Version 3.5.5+dfsg1-1 fixes a security issue: CVE-2014-7137 (Closes:
> > #770313)
>
> This bug was filed
s:
On Thu, 29 Jan 2015, Raphael Hertzog wrote:
> I want to add that my request is now to upload 1.7.4-1 since upstream
> released a new bugfix version:
> https://docs.djangoproject.com/en/1.7/releases/1.7.4/
>
> BTW, that version contains a fix for an unreported FTBFS that we have
Control: retitle -1 unblock (pre-approval): python-django/1.7.4-1
On Wed, 21 Jan 2015, Raphael Hertzog wrote:
> I would like to upload python-django 1.7.3-1 to sid and jessie.
> It's a new upstream version but it contains only bugfixes
> (a few of which are security relate
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package dolibarr
Version 3.5.5+dfsg1-1 fixes a security issue: CVE-2014-7137 (Closes: #770313)
That version contains changes unrelated to the above security fix but
all the
Hi,
On Sun, 25 Jan 2015, Thijs Kinkhorst wrote:
> Please unblock package python-django.
>
> It fixes several security issues.
>
> The NMU seems to add a stray .orig in the source package; but I reckon
> that is harmless and should not block fixing the security issues.
>
> unblock python-django/
On Wed, 21 Jan 2015, Raphael Hertzog wrote:
> Some notes:
> - the final upload will include the bug closure of #775375
> - there's a small tweak of a Suggests dependency, it was not intended for
> jessie but I don't see how it can hurt and did not bother to revert it
I
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
I would like to upload python-django 1.7.3-1 to sid and jessie.
It's a new upstream version but it contains only bugfixes
(a few of which are security related, see #775375).
The diffstat is
Hi Niels,
On Sat, 27 Dec 2014, Niels Thykier wrote:
> * wordpress - to be automatically removed on January 24th.
>- Craig: I am aware of the version in NEW. However, given it is
> in NEW, I doubt it will comply with the freeze policy. Do contact
> the release team if you believe o
Control: tag -1 - moreinfo
On Wed, 17 Dec 2014, Jonathan Wiltshire wrote:
> >In fact, this package should probably be adopted by the python-modules
> >team. I can make sure that this happens since I'm part of the team. Would
> >that reassure you?
>
> Ok, it's a deal.
>
> Let me know when it's ad
Control: tag -1 - moreinfo
On Tue, 16 Dec 2014, Jonathan Wiltshire wrote:
> I'm not enthusiastic about having an orphaned package in stable, if I'm
> really honest. That's largely why it was removed.
I can understand that. That said we have plenty of such packages in stable
and they are not much
On Thu, 04 Dec 2014, Simon McVittie wrote:
> On Thu, 04 Dec 2014 at 16:39:31 +0100, Niels Thykier wrote:
> > On 2014-12-04 09:11, Simon McVittie wrote:
> [see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770627#70 for full
> analysis]
> > If your interpretation is correct, then I am certainly
On Fri, 07 Nov 2014, Guillem Jover wrote:
> I'm going to revert the commit above (only in 1.17.x, it will be kept
> in 1.18.x), because it is very minimal, just reintroduces again an
> unnecessary package queue stage, and such regression is acceptable if
> it makes buggy bootstrappers work again. B
Control: tags -1 + patch
On Mon, 04 Aug 2014, Neil Williams wrote:
> Fixing the testsuite is only one part of it. Checking that the actual
> module works with reverse dependencies is where I expect to need the
> time. Thanks for the tip though, it does help me start on the package
> itself.
If th
Control: tags -1 patch
Hello Neil,
On Sun, 03 Aug 2014, Neil Williams wrote:
> I've now been able to test django-restricted-resource against django1.7
> and what I thought should be a simple test has shown significant issues.
>
> The changes in django1.7 cause breakage in the
> django-restricted-
Hi,
On Tue, 22 Jul 2014, Neil Williams wrote:
> Raphael: please expand on why you want 1.7 in Jessie other than "it's
> newest so must be best". I'm perfectly happy to have django1.7 and
> later available from backports. Which specific *features* in django1.7
> are to be considered as justifying t
On Mon, 21 Jul 2014, Niels Thykier wrote:
> > Was that due to lack of time or just that you have no idea what would be
> > better names?
>
> Partly because your use of "etc." suggested it was not a full list, so I
> wanted the full list. But also because I feel there is more this than
> "just" ch
Hi Nields,
Thanks for your fast answers!
On Wed, 16 Jul 2014, Niels Thykier wrote:
> Your problem in a nutshell: You triggered something that looks like
> O(2^n) runtime in Britney. /o\
I suspected something like that... :)
> Short-term options include:
> * patch Britney reject on first new u
Hello britney maintainers,
I would like your advice and comments about a possible usage of britney
in the context of a Debian derivative.
Kali is currently based on Debian Stable but we are investigating ways to
switch to Debian testing and thus become a "rolling" distribution as well.
Currently
Hi,
On Fri, 31 Jan 2014, Adam D. Barratt wrote:
> I've been arguing with myself a little, but on balance I'd prefer to
> stick with the template change for now.
Thanks, uploaded.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Discover the Debian Administrator's Handbook:
→ http://debian-handboo
Hi,
On Thu, 30 Jan 2014, Adam D. Barratt wrote:
> On Sun, 2014-01-26 at 22:00 +0100, Raphael Hertzog wrote:
> > I would like to update the debian-handbook in Wheezy so that it actually
> > documents Wheezy and not Squeeze. We finished the update in late december.
>
> Pl
On Thu, 30 Jan 2014, Adam D. Barratt wrote:
> > > For details: http://bugs.debian.org/680469
>
> I'd be okay with this change.
Great.
> > Someone requested me to squeeze another fix in that stable update:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720122
> > http://bugs.debian.org/cgi-
On Wed, 29 Jan 2014, Russ Allbery wrote:
> aren't as large of a porting issue). Rather, the question is whether it
> is actually viable to separate those services from systemd as init and
> port logind to non-Linux, whether that work will be done in time for
> jessie, and who is going to do it.
S
On Sun, 26 Jan 2014, Adam D. Barratt wrote:
> Our general approach to such updates in the past has been that having
> the version of the package in stable document that release is
> preferable, particularly when the changes are principally documentation.
>
> A filtered debdiff showing the changes
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
I would like to update the debian-handbook in Wheezy so that it actually
documents Wheezy and not Squeeze. We finished the update in late december.
Attached is a filtered debdiff that drops chan
Hi,
On Thu, 23 Jan 2014, Adam D. Barratt wrote:
> The next point release for "wheezy" (7.4) is scheduled for Saturday
> February 8th. Stable NEW will be frozen during the preceding weekend.
I was wondering, would you accept a new upstream version of
debian-handbook into stable ?
The current ve
Hello dear release managers,
On Tue, 17 Dec 2013, Raphael Hertzog wrote:
> I would like to get a usable debian template and after some investigation,
> I concluded that the easiest solution was to use the upstream provided
> script. That said I opted to use the latest upstream versio
On Tue, 17 Dec 2013, Raphael Hertzog wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: pu
>
> The "debian" template provided by Wheezy's lxc has been broken from the
> start due to live-debc
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
The "debian" template provided by Wheezy's lxc has been broken from the
start due to live-debconfig never making it to wheezy (and inaction from
the maintainer).
For details: http://bugs.debian.
Hi,
On Tue, 14 May 2013, Игорь Пашев wrote:
> 2013/5/14 Raphael Hertzog :
> > But ansgar's objection about the duplication of the changelog in multiple
> > .deb when it used to be shared via a symlink also makes sense. As does the
> > fact that there's currently no
Hi,
On Mon, 13 May 2013, Guillem Jover wrote:
> The binNMU issue entails two “sub-problems”. The first is the one
> introduced by different entries in binNMUs on multiple architectures.
> The other is the unmatched versions for possible out-of-step binNMU
> versions.
>
> Personally I see very cle
On Sun, 28 Apr 2013, Josselin Mouette wrote:
> Le jeudi 25 avril 2013 à 19:45 +0200, Julien Cristau a écrit :
> > > I don’t think it is a problem for scripts in the postinst, nor in
> > > triggered scripts. I thought prerm was supposed to be OK as long as
> > > there are no loops in the upgrade (t
Control: retitle -1 unblock: gnome-session/3.4.2.1-4 gdm3/3.4.1-8
gdm3/3.4.1-8 has been uploaded in the mean time with a little improvement
in the way orca is started so that it doesn't display a configuration
screen on first startup.
The debdiff is basically the same. There's only one more param
On Thu, 04 Apr 2013, Julien Cristau wrote:
> "The shell does not exit if the command that fails is [...] part of any
> command executed in a && or || list except the command following the
> final && or || [...]"
Oh, I stand corrected then. And it looks like dash is the same (so it's
not specific t
Hi,
On Thu, 04 Apr 2013, Gonéri Le Bouder wrote:
> # remove the configuration file itself
> rm -f /etc/fusioninventory/agent.cfg
> -rm -r /etc/fusioninventory
> +[ -d /etc/fusioninventory ] && rmdir --ignore-fail-on-non-empty
> /etc/fusioninventory
AFAIK, this is not better sin
Control: tags -1 - moreinfo
On Tue, 19 Mar 2013, Neil McGovern wrote:
> Is there likely to be a t-p-u upload fixing the RC bug only, ie: the
> patch in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671635#20, or
> should I look for a removal?
0.4.1.1 uploaded with the following debdiff:
--- r
Control: tag -1 - moreinfo
Hi,
On Mon, 04 Mar 2013, intrigeri wrote:
> Yeah, well, this reply makes me a bit sad, as it relies a bit too much
> for my taste on the fact that Wheezy will not be released soon, and
> I'd rather see such matters handled with a "let's release it very
> soon" mindset,
Hi,
On Mon, 04 Mar 2013, intrigeri wrote:
> Given these concerns and the fact time happened to go on flying since
> Julien Cristau expressed these, at this point of the release process,
> I think the only way to ship rebuildd in Wheezy would be to prepare
> a t-p-u upload with only the minimal bug
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu ruby-bcrypt_3.0.1-2 ruby-bdb_0.6.5-7 ruby-dep-selector_0.0.8-1
ruby-eventmachine_0.12.10-3 ruby-gherkin_2.11.1-1 ruby-globalhotkeys_0.3.2-3
ruby-libxml_2.3.2-1 ruby-msgpack_0.4.6-4 ruby
1 - 100 of 280 matches
Mail list logo
