Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: puppet-module-puppetlabs-cron-core
Version : 1.0.3
Upstream Author : Puppet labs Inc.
* URL : https://github.com/puppetlabs/puppetlabs-cron_core
* License : Apache-2.0
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: puppet-module-puppetlabs-augeas-core
Version : 1.0.5
Upstream Author : Puppet Labs
* URL : https://github.com/puppetlabs/puppetlabs-augeas_core
* License : Apache-2.0
Programming Lang
On 1/30/20 8:18 PM, Anthony DeRobertis wrote:
> On 1/30/20 7:02 AM, Thomas Goirand wrote:
>> This is normally solved if using pre-depends, which ensure that a
>> package is configured before using it (and not just unpacked).
>
> Having everything using sysusers have
.
That's exactly what made me think that using the original name was less
Debian wide work indeed. Though because of the binary name prefixed with
"systemd-" this is less elegant than standardizing on /bin/sysusers.
Cheers,
Thomas Goirand (zigo)
shows up when
> doing rspec module testing.
So, we're talking about Ruby stuff?
Cheers,
Thomas Goirand (zigo)
tures,
> which doesn't seem like a least-astonishment situation to be in. However,
> Michael, or anyone else opposing this change: if you have anything to
> add to those, please do.
We don't need to do "Depends: systemd (>= 321)", we could have a virtual
package provided by both implementations.
Cheers,
Thomas Goirand (zigo)
On 1/29/20 4:49 PM, Didier 'OdyX' Raboud wrote:
> Le mercredi, 29 janvier 2020, 16.07:21 h CET Thomas Goirand a écrit :
>> This reasoning can make sense, if we agree that we should use something
>> else than /bin/systemd-sysusers and standardize on something else like
>> /
better if this goes into the policy.
I've read many telling about a potential new functionality that would
not be implemented here or there. However, my guts feeling is that this
feels like a kind of stable API that isn't intended to grow very much,
and hopefully, will be of low maintenance. Let's see wh
On 1/29/20 1:50 PM, Raphael Hertzog wrote:
> On Wed, 29 Jan 2020, Thomas Goirand wrote:
>> echo 'u radvd - "radvd daemon"' | \
>>systemd-sysusers --replace=/usr/lib/sysusers.d/radvd.conf
>
> Does opensysusers support this use case?
Yes it does.
> There's
On 1/29/20 11:34 AM, Raphael Hertzog wrote:
> On Tue, 28 Jan 2020, Thomas Goirand wrote:
>> This is exactly what should be avoided. It's perfectly fine to try to
>> use opensysusers with systemd if one wants. In fact, that's exactly the
>> best way we could do to be able t
s" argument. We
constantly get many types of wrong reports in the BTS. We just shall do
sensible bug triaging in a correct way, that's it.
Cheers,
Thomas Goirand (zigo)
P.S: Note that this bug also concerns systemd-tmpfiles, the very exact
same way, though I believe one single bug is enough to address both
cases which are similar.
On 1/25/20 5:05 PM, Michael Biebl wrote:
> Control: tags -1 + wontfix
>
> Hi Thomas
>
> On Tue, 31 Dec 2019 17:29:29 +0100 Thomas Goirand wrote:
>> Package: systemd
>> Version: 244-3
>> Severity: important
>>
>> Hi,
>>
>> As I'm p
fix bugs in Debian
stable. The way to fix bugs in stable is ... to fix bugs in stable! :)
Have you investigated to know which upstream patch fixed the issue, so
that we could backport that single patch instead?
Cheers,
Thomas Goirand (zigo)
On 1/26/20 7:02 AM, Sandro Tosi wrote:
> Source: google-apputils-python
> Severity: serious
>
> Hello,
> i think we should remove google-apputils-python from debian:
>
> * last upstream release in 2014
> * upstream marked[1] it as "Obsolete. Please migrate to absl-py instead."
> * no reverse
Hi,
I tried rebuilding the package, and it looks like the latest upload
fixed the issue (I could build the package without any problem).
If you believe I'm wrong, please reopen and let me know.
Cheers,
Thomas Goirand (zigo)
On 1/17/20 6:35 PM, Gianfranco Costamagna wrote:
> control: reopen -1
>
> On Wed, 8 Jan 2020 10:17:23 +0100 Thomas Goirand wrote:
>> I'm closing this bug. Feel free to reopen if there's still a problem.
>>
>
> sorry for the late answer!
>
> https://ci.debian.ne
package).
Your thoughts? If I don't do it, will you have the time to do what
you're suggesting above, and resend a debdiff to the release team?
Cheers,
Thomas Goirand (zigo)
P.S: I'm not subscribed to this bug, please CC me.
when
we've already asked for approval of version 19.3. FYI, your patch is
already included in version 19.3. Maybe you could test with the version
in Sid?
Cheers,
Thomas Goirand (zigo)
On 1/7/20 2:01 PM, Thomas Goirand wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Dear release team,
>
> As per the issue described here:
> https://github.com/FRRouting/frr/issu
Hi,
FYI, the release team bug number is:
https://bugs.debian.org/948333
Thomas
the resulting debdiff, and
opened the bug against the frr package itself.
Please allow me to upload this fix to Buster,
Cheers,
Thomas Goirand (zigo)
diff -Nru frr-6.0.2/debian/changelog frr-6.0.2/debian/changelog
--- frr-6.0.2/debian/changelog 2019-02-04 22:16:07.0 +0100
+++ frr-6.0.2
don't mind. So I am
opening a stable release team bug right away.
Cheers,
Thomas Goirand (zigo)
diff -Nru frr-6.0.2/debian/changelog frr-6.0.2/debian/changelog
--- frr-6.0.2/debian/changelog 2019-02-04 22:16:07.0 +0100
+++ frr-6.0.2/debian/changelog 2020-01-07 13:21:50.0 +0100
Hi,
I don't understand why there's still this bug, and it's being set to
severity serious: when I build the package locally using sbuild, there's
no issue and the package builds fine, at least with version 2.6.1-1.
Gianfranco, could you help me understand?
Cheers,
Thomas Goirand (zigo)
ly your proposal, though I'm not
really sure that it's what you're saying: please clarify).
Which is why I end up preferring option 3-. Which of the 3 options is
your preference? Are you also ok that we decide to use /bin/systemd-X as
the installed alternative? This way, we have nothing else to patch.
Cheers,
Thomas Goirand (zigo)
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: opentmpfiles
Version : 0.2
Upstream Author : William Hubbs
* URL : https://github.com/OpenRC/opentmpfiles
* License : BSD-2-clause
Programming Lang: Shell
Description : standalone
we should
use them, install alternatives for them as well, or use use the ones
from systemd. Right now, I believe I'd prefer to use the ones from
systemd, as this is what opensysusers references to.
Your thoughts about the 2 points above?
Cheers,
Thomas Goirand (zigo)
Hi,
Please find the new debdiff for this change, which is already in
Sid/Testing. We still need to test this, I hope Kevko will be able to
the upgrade tests.
Cheers,
Thomas Goirand (zigo)
diff -Nru horizon-14.0.2/debian/changelog horizon-14.0.2/debian/changelog
--- horizon-14.0.2/debian
to have systemd have the priority over
opensysusers if you believe it should (I'm open to discussion about
priorities).
Cheers,
Thomas Goirand (zigo)
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: opensysusers
Version : 0.4.8
Upstream Author : Chris Cromer
* URL : https://github.com/artix-linux/opensysusers
* License : BSD-2-clause
Programming Lang: bash
Description
s is included in cloud-init 19.3 which is currently in Sid/Testing,
and as our current plan is to backport 19.3 as the new version for
buster-proposed-updates, this may be solved with this upgrade. Let's
wait and see what the stable release team says.
Cheers,
Thomas Goirand (zigo)
//buildd.debian.org/status/package.php?p=ceph
> Dependency installability problem for ceph on mips64el:
> ceph build-depends on missing:
> - libboost-context-dev:mips64el (>= 1.67.0)
>
> (like on various other architectures)
The buildd status page says it's currently in "building&
le setup a cluster with this
type of CPUs in production anyway.
But IMO, it'd be nice if we could at least keep the client side working.
I'm not sure how to achieve this though, probably this will make the
build a lot more complicated.
BTW, any idea what dependency is missing in mips64el?
Thomas Goirand (zigo)
On 12/22/19 10:22 PM, Dmitry Shachnev wrote:
> Hi Sandro!
>
> On Sun, Dec 22, 2019 at 02:47:10PM -0500, Sandro Tosi wrote:
>>> The current version packaged in Debian is very outdated,
>>> even in unstable. Please consider packaging the current
>>> upstream release.
>>
>> I'm echoing this request:
Hi,
Here's the proposed NMU debdiff. I'm uploading it to delayed/7 since the
bug has been opened for so long, there's no reverse dependency for the
py2 only package, and the package will be AUTORM in 22 days.
Cheers,
Thomas Goirand (zigo)
diff -u python-boto-2.49.0/debian/changelog python-boto
On 12/25/19 5:34 AM, Norbert Preining wrote:
> Hi Thomas,
>
> On Mon, 23 Dec 2019, Thomas Goirand wrote:
>> situation of Calibre? When do you think your package will be ready? As I
>> understand, Calibre itself is ready, but what about the plugins? Are the
>
> Ko
Package: ftp.debian.org
Severity: normal
Hi!
There's no reverse dependency for python-xmlbuilder anymore, this package is
Python 2 only. Let's please remove it from Debian.
Thanks,
Thomas Goirand (zigo)
; [...]
Thanks for this useful work. Everything which can make the minimal base
install smaller is a good thing.
Do you already have a list of affected package?
Cheers,
Thomas Goirand (zigo)
view, manually testing all of the above would be enough to make
sure we don't upload a broken cloud-init to Buster. Note that this
setup looks like already working under Testing right now.
Best regards,
Thomas Goirand (zigo)
On 12/23/19 7:52 PM, micah anderson wrote:
> "Todd H. Poole" writes:
>
>> As for departing from prior behavior, I'll give you that: that's why there
>> was so much messaging around the 4.x release and such a strong up-tick in
>> the quality of the upstream docs around that time. If you were to
om testing means that about
nearly all of OpenStack will be removed at the same time. This is *not*
something I will let happen.
I don't think we should wait for another 6 months to act here.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
On 12/21/19 11:34 PM, Salvatore Bonaccorso wrote:
> Hi Thomas
>
> [Disclaimer: not part of the stable release managers, so this reply is
> not authoritative]
>
> Thanks for handling CVE-2019-3866 for unstable and buster.
>
> On Sat, Dec 21, 2019 at 11:12:17PM +01
the Debian Puppet package so that Puppet's behavior
> on Debian matches the documented behavior in the man pages, upstream docs,
> and upstream packages?
I'd vote for leaving things the way they are now. I wont close the bug,
as I have only uploaded puppet once to Debian, but I suggest the other
uploaders to do so.
Cheers,
Thomas Goirand (zigo)
-lib/
Please allow me to upload:
python-mistral-lib/1.0.0-1+deb10u1.
Cheers,
Thomas Goirand (zigo)
diff -Nru python-mistral-lib-1.0.0/debian/changelog
python-mistral-lib-1.0.0/debian/changelog
--- python-mistral-lib-1.0.0/debian/changelog 2018-09-04 00:06:52.0
+0200
+++ python-mistral
FYI, for reference, the package is built and available here:
http://shade.infomaniak.ch/buster-pu/python-oslo.utils/
the Debian
perspective (ie: .gitreview, or upstream CI related).
Please find, attached to this bug, the debdiff for the udpate.
Please allow me to upload:
python-oslo.utils/3.36.4+2019.11.15.git.c49a426b66-1+deb10u1
Cheers,
Thomas Goirand (zigo)
diff -Nru python-oslo.utils-3.36.4/debian/changelog
On 12/11/19 10:03 PM, Toni Mueller wrote:
>
>
> Hi Thomas,
>
> On Tue, Dec 10, 2019 at 08:47:02PM +0100, Thomas Goirand wrote:
>> Do you feel like doing the work yourself for this? I have too many
>> things to watch for stable updates...
>
> I am strongly
more commonly used and IMO more useful...).
I'm writing this for anyone looking at the BTS and not knowing what this
all is about.
That being said, I'm applying upstream fix right away now.
Cheers,
Thomas Goirand (zigo)
On 12/9/19 11:24 AM, Toni Mueller wrote:
>
> Hi Thomas,
>
> On Mon, Dec 09, 2019 at 10:58:49AM +0100, Thomas Goirand wrote:
>> There's no need to backport it, as it's already included in
>> python-jsonschema 3.0.2 which was uploaded to Sid.
>
> I know - I t
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: puppet-module-cristifalcas-etcd
Version : 1.12.3
Upstream Author : Cristian Falcas
* URL : https://github.com/puppet-etcd/puppet-etcd
* License : Apache-2.0
Programming Lang: Puppet
On 12/6/19 2:30 AM, Benda Xu wrote:
> Hi Thomas,
>
> Thomas Goirand writes:
>
>>> The last time I looked (years ago), there were features in sysvinit
>>> which weren't in OpenRC (yet). IIRC not having concurrent execution of
>>> boot scripts was one
> fixes an RC bug.
>
> Thank you!
>
> Best
>
> Ole
Hi,
Last time I checked, there was still some packages needing
python-jsonschema (by this, I mean, the Python 2 version of the
package). As this has changed, I can now upload the version with Py2
removal in Sid. I'll do this soon.
Cheers,
Thomas Goirand (zigo)
Hi Alex,
Axel Beckert
> Thomas Goirand wrote:
> > OpenRC is actively maintained upstream,
>
> Sysvinit is AFAIK maintained upstream again since a year ago or so. So
> this is no reason to get rid of sysvinit. Note all the new upstream
> releases, Dmitry has uploaded in t
of sysvinit maintainers is.
I'm also unsure what would be technically needed to get sysv-rc automatically
be replaced by OpenRC. Maybe we could make sysv-rc become a metapackage that
depends on OpenRC?
Your thoughts?
Cheers,
Thomas Goirand (zigo)
commit on Github is from April 2015,
> should we remove it from the archive?
>
> Cheers,
> Moritz
Hi,
This is a small codebase, which I am able to maintain by myself. I
started the porting to Python 3 already locally. In the mean time, it's
very much OK to remove the package from testing (which will be done with
autoremove anyway).
I'll get in touch with upstream to see if I can take over the
maintenance of the code and become upstream.
Cheers,
Thomas Goirand (zigo)
org/Python/2Removal, or ask for help on IRC
> #debian-python, or the debian-pyt...@lists.debian.org mailing list.
>
Hi,
Py2 is already removed from python-falcon. I looked into the package,
and didn't see any autopkgtest either... Or did I miss something?
Cheers,
Thomas Goirand (zigo)
Hi,
mirror1.infomaniak.com and mirror2.infomaniak.com are now pointing to
the correct IP addresses. Sorry for my mistake, now everything should be
good to go.
Cheers,
Thomas Goirand (zigo)
mmits, thanks for the work!
Let me know if I may help as well (for example, by testing the package,
which I'll do ASAP). I'm looking forward the upload and trying Nautilus
in Debian. Will you also upload a backport to Buster?
Cheers,
Thomas Goirand (zigo)
also if you could push your
work to Git if you have done some of it already (even if it's unfinished).
Cheers,
Thomas Goirand (zigo)
an NMU shortly. I'll post the debdiff here
>>
>> before
>>>> any
>>>>> upload, and use a long DELAYED queue if the nmu is to go ahead.
>>>>>
>>>>> Thank you!
>>>>
>>>> The new version of fabric requires a new version of python3-
>>>> invoke.
>>
>> Dear Maintainers,
>>
>> Unless there are any objections, I intend to upload an NMU to
>> DELAYED/7
>> later today with the changes from the aforementioned MR to fix this
>> bug
>> and unblock my work on reverse dependencies:
>>
>> https://salsa.debian.org/openstack-team/python/python-invoke/merge_requests/3
>>
>>
>> Thanks!
>
> Dear python-invoke Maintainers,
>
> I've uploaded 1.3.0+ds-0.1 to DELAYED/7 and with urgency=low for
> delayed migration on top of that. The exact same sources are on the MR
> mentioned above. Debdiff is attached.
>
> Please let me know if there are any issues.
>
> Thank you!
Hi Luca,
This NMU is the proof that this package should be offered for adoption.
Would you like to take it over, for example in the DPMT? I'd happily
stay as uploader. Same for python-invoke.
Cheers,
Thomas Goirand (zigo)
On 11/23/19 6:36 PM, Julien Cristau wrote:
> Control: tag -1 moreinfo
>
> On Tue, Nov 12, 2019 at 11:12:17AM +0100, Thomas Goirand wrote:
>> I'd like to update heat in Buster to permit safe upgrades, as the current
>> version may remove the heat domain password. Att
On 11/23/19 6:09 PM, Julien Cristau wrote:
> Control: tag -1 moreinfo
>
> On Mon, Nov 04, 2019 at 11:53:52AM +0100, Thomas Goirand wrote:
>> We would like to update Nova in Buster for 2 reasons. First, there's
>> OSSA-2019-003 / CVE-2019-14433 which we would like to f
As per discussion on IRC, to avoid a race condition, please split this into:
mirror1.infomaniak.com
mirror2.infomaniak.com
FYI, mirror2 recieves a push from mirror1.
Thomas Goirand (zigo)
Hi,
Small amendment to my submission. Please use product...@infomaniak.com
as maintainer email, rather than must myself.
Cheers,
Thomas Goirand (zigo)
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Thomas Goirand
Country: CH Switzerland
Location: Geneva
Sponsor: Infomaniak https://www.infomaniak.com/
Comment: This is a super-fast link connected to 2 mirrors which are 2nd tier
from ethz (ie: ftp.ch.debian.org), each server using RAID10
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: puppet-module-voxpupuli-alternatives
Version : 3.0.0
Upstream Author : Voxpupuli
* URL : https://github.com/voxpupuli/puppet-alternatives
* License : Apache-2.0
Programming Lang: Python
the
point release 10.2 ... :/
Cheers,
Thomas Goirand (zigo)
diff -Nru nova-18.1.0/debian/changelog nova-18.1.0/debian/changelog
--- nova-18.1.0/debian/changelog2019-05-29 14:56:05.0 +0200
+++ nova-18.1.0/debian/changelog2019-11-18 13:30:25.0 +0100
@@ -1,3 +1,19
Hi Steve,
Thanks for this, however, the patch you've provided for this bug is for
Alembic, not for Mako. Do you have a patch available for Mako? Has a bug
correctly been filled for Alembic?
Cheers,
Thomas Goirand (zigo)
On 11/13/19 3:31 PM, Iustin Pop wrote:
> On 2019-11-13 15:06:54, Thomas Goirand wrote:
>> On 11/12/19 4:37 PM, Osamu Aoki wrote:
>>> The related binary packages are available in 2 binary names (depending on
>>> release)
>>> getmail4 (version=4,5) popcon instal
So I see no reason to keep getmail
then. Maybe tell this to upstream, and they may think another time.
Cheers,
Thomas Goirand (zigo)
for this fix.
Note that I've tested the upgrade in production.
Cheers,
Thomas Goirand (zigo)
diff -Nru heat-11.0.0/debian/changelog heat-11.0.0/debian/changelog
--- heat-11.0.0/debian/changelog2019-03-01 15:35:44.0 +0100
+++ heat-11.0.0/debian/changelog2019-11-12 10:52:30.0
On 11/9/19 2:38 PM, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Sun, 2019-10-27 at 18:10 +0100, Thomas Goirand wrote:
>> I'd like to upgrade oslo.messaging to version 8.1.4-1+deb10u1.
>> Indeed, in versin 8.1.3, when a Rabbitmq server configured through
, and that I've been using such a fix in production already, so
it's been tested extensively.
Cheers,
Thomas Goirand (zigo)
>From 2dda54a0519e9d17c0c2262a6701529c479031ce Mon Sep 17 00:00:00 2001
From: Thomas Goirand
Date: Mon, 14 Oct 2019 02:15:35 +0200
Subject: [PATCH 1340/1345] *
On 11/9/19 2:31 PM, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Mon, 2019-10-07 at 14:35 +0200, Thomas Goirand wrote:
>> Since Buster was frozen, I worked quite a long time on Octavia, and
>> was
>> able to make the octavia-agent work properly, as wel
On 11/4/19 12:11 PM, Santiago Vila wrote:
> On Mon, Nov 04, 2019 at 11:40:08AM +0100, Thomas Goirand wrote:
>> Hi Evgeny,
>>
>> As elixir-lang is going to be AUTORM if nobody takes care of it, I
>> already added a bit of code in debian/rules to make it retry
mode, upgrading Nova can lead to some configuration
changes, which is an RC bug.
The attached debdiff fixes both of the issues, and has been tested in
production, and is also available in Sid/Bullseye (so it's safe to use).
Please allow us to upload this fix to Buster.
Cheers,
Thomas Goirand
do
that. The reason why I've done a non-delayed NMU is because otherwise,
it would be AUTORM, but of course, everything can be reverted if you
feel like it. Anyways, I'm always available for anything related to
these uploads, so just let me know.
Cheers,
Thomas Goirand (zigo)
diff -Nru elixir
for this package. If you still need sponsoring, let
me know, and I'll sponsor the upload for you.
Thanks for your work,
Cheers,
Thomas Goirand (zigo)
.
Cheers,
Thomas Goirand (zigo)
diff -Nru python-livereload-2.6.1/debian/changelog
python-livereload-2.6.1/debian/changelog
--- python-livereload-2.6.1/debian/changelog2019-07-20 20:36:14.0
+0200
+++ python-livereload-2.6.1/debian/changelog2019-11-02 22:29:38.0
+0100
@@ -1,3
ailing tests, as
> they do not seem to be trusted.
Disabling tests is really not what I want to do. These tests are
catching real world issues, and I do need to detect the problems.
Thomas Goirand (zigo)
l those bugs outside the Debian BTS, in which case I should better
> stop doing QA on Debian altogether.
Ok, got you. I've reopened the bug.
Thomas Goirand (zigo)
ository='deb file:///home/ftp/debian experimental main'
to build the package. Then I could fix it, and I'm uploading the fix.
Cheers,
Thomas Goirand (zigo)
stream for SQLAlchemy
and Alembic, and also commits on oslo.db (which 3 packages probably are
involved in the issue here). Let's hope we get an answer and fix this.
Cheers,
Thomas Goirand (zigo)
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-ospurge
Version : 2.0.0+2019.10.11.git.990287677b
Upstream Author : OpenStack Foundation
* URL : https://opendev.org/x/ospurge
* License : Apache-2.0
Programming Lang: Python
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: uwsgi-apparmor
Version : 0.0.0+git.2014.09.15.7d6d7bd7eb
Upstream Author : Unbit
* URL : https://github.com/unbit/uwsgi-apparmor
* License : Expat
Programming Lang: C, Python
e.match(version)
File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 745, in
match
return all(clause.match(version) for clause in self.clauses)
File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 745, in
return all(clause.match(version) for clause in self.clauses)
File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 892, in
match
version = version.truncate('prerelease')
AttributeError: 'Version' object has no attribute 'truncate'
--
Ran 41 tests in 2.022s
FAILED (SKIP=2, errors=4)
make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1
Please fix your package.
Cheers,
Thomas Goirand (zigo)
I believe this bug is not relevant anymore to the version in Sid (though
I'm not sure when this FTBFS issue was fixed).
Thomas
rabbit node (and as a consequence, turning off
the service there).
Attached is the debdiff for this change,
Please allow me to upgrade oslo.messaging in Buster,
Cheers,
Thomas Goirand (zigo)
diff -Nru python-oslo.messaging-8.1.3/debian/changelog
python-oslo.messaging-8.1.4/debian/changelog
--- python
On 10/26/19 4:27 AM, Sandro Tosi wrote:
> if you're stick with
> python_distutils build system.. that's gonna fail when you remove
> python as b-d
That's only if you let it do what it feels. If one overrides
dh_auto_{clean,build,test}, then it works fine.
Cheers,
Thomas Goirand (zigo)
ke a python2-pbr source package without seeing
> anything relevant.
>
My bad, this is now re-uploaded a correct package now.
I had to re-introduce it because python-mock needs it, and python-mock
has *A LOT* of reverse dependencies that we need to fix first.
Cheers,
Thomas Goirand (zigo)
Hi,
It appears it was fixed indeed, but uploaded with binaries, and
therefore didn't migrate to testing. I'm re-uploading to fix that.
Cheers,
Thomas Goirand (zigo)
to be switched to Pybuild (or any other
in the OpenStack team). I'm fine with nothing more than dh, no need for
the extra complexity of Pybuild.
Cheers,
Thomas Goirand (zigo)
is:
GRUB_CMDLINE_LINUX_DEFAULT="nosplash text console=tty0 console=ttyS1,115200
earlyprintk=ttyS1,115200 consoleblank=0 systemd.show_status=true "
Cheers,
Thomas Goirand (zigo)
M if you
don't do anything to fix the situation.
Cheers,
Thomas Goirand (zigo)
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Locale: LANG=
Hi,
Your package also needs to support Django 2.2, which is in Sid, and
which your package is blocking the transition. At this point, as there's
only 4 Django packages remaining, your package may be left behind and
AUTORM from Testing.
Cheers,
Thomas Goirand (zigo)
Source: django-modeltranslation
Version: 0.12.2-1
Severity: serious
Hi,
Your package doesn't build with Django 2.2, which is blocking is transition to
Testing. Please fix this ASAP. This also means fixing Py2 removal, as there's
no Py2 support in Django 2.2.
Cheers,
Thomas Goirand (zigo)
Hi,
FYI, this package is not needed in Python 3, it's a wrapper around
asyncio in Py3, and reimplements it in Py2.
So, as soon as all dependencies have moved-on, we can simply remove this
package.
Cheers,
Thomas Goirand (zigo)
at the right moment? How can I
check for this? Should I reassign the bug to Plymouth?
Cheers,
Thomas Goirand (zigo)
ed the web for a long time,
and what I describe is I believe correct. If I'm correct, then please
report the problem upstream and get this fixed.
Thanks for maintaining systemd,
Cheers,
Thomas Goirand (zigo)
work that
would be, and when I saw the graph, I decided to re-add Py2 support in
PBR. This is done already, and I've reopened the bug for PBR, and
lowered the severity for mock.
On the above list, however, a lot has been fixed already (for example,
the python-os-* and mox3).
Cheers,
Thomas Goirand (zigo)
Hi,
Since you haven't replied to the previous mail, I've uploaded this
without delay, fixing the RC bug on blockdiag.
Cheers,
Thomas Goirand (zigo)
diff -Nru blockdiag-1.5.3+dfsg/debian/changelog
blockdiag-1.5.3+dfsg/debian/changelog
--- blockdiag-1.5.3+dfsg/debian/changelog 2018-07-16
801 - 900 of 4068 matches
Mail list logo
