Hi Pino,
quick feedback to confirm the fix.
I did an upgrade before the fix on one machine which failed, and a second
upgrade after the fix on another machine that went fine.
And thanks for all the Plasma 5.17.5 packaging. :-)
Happy hacking !
--
Aurélien
On Mon, 2020-01-20 at 12:33 -0500, Olek Wojnar wrote:
> Hmm, I always interpreted that as meaning a dependency on another .deb
> package because of the "package" wording vs a word such as "component."
I always interpreted it in the general sense rather than in the sense
of a dependency on Debian
On Sun, Jan 19, 2020 at 11:39:01AM +0200, Graham Inggs wrote:
> Error in library(tximportData) :
> there is no package called ‘tximportData’
While I've fixed prepare_missing_cran_package in Git to enable fetching
tximportData and I'm a big fan of packaging also test-depends its just
0.5GB
Your message dated Mon, 20 Jan 2020 22:16:08 -0800
with message-id <20200121061608.xta7xmxuic5y5qm7@stgulik>
and subject line Re: Bug#949351: efl FTBFS: missing dependency on libx11-xcb-dev
has caused the Debian Bug report #949351,
regarding efl FTBFS: missing dependency on libx11-xcb-dev
to be
Your message dated Tue, 21 Jan 2020 06:49:49 +
with message-id
and subject line Bug#943088: fixed in fonts-smc-suruma 3.2.3-1
has caused the Debian Bug report #943088,
regarding fonts-smc-suruma: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Package: src:gwcs
Version: 0.12.0-3
Severity: serious
Tags: sid bullseye
the gwcs build accesses the network during the build, according to the build
log:
[...]
Running Sphinx v1.8.5
making output directory...
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading
Hi Moritz,
I'm trying hard to get later versions of meshlab built and working,
please
don't remove the package.
Later versions support qt5 already, so no more porting needed.
I failed to get built the latest versions, however according to
Package: repo
Version: 1.13.7-1
Severity: serious
Tags: sid bullseye
https://packages.debian.org/sid/all/repo/filelist
/usr/bin/repo
/usr/share/bash-completion/completions/repo
/usr/share/doc/repo/README.Debian
/usr/share/doc/repo/changelog.Debian.gz
/usr/share/doc/repo/copyright
On Mon, 20 Jan 2020, Andreas Tille wrote:
> On Mon, Jan 20, 2020 at 01:01:00PM -0500, Yaroslav Halchenko wrote:
> > > I'm fine with re-doing what I changed if you consider it really of
> > > practical relevance. If you ask me we two would spent time we could
> > > use more productively but
Package: libctf-nobfd0
Version: 2.33.50.20200115-2
Severity: serious
Rationale: breaks upgrades
libctf-nobfd0 takes over the file libctf-nobfd.so.0.0.0 from libbinutils
but is missing a Breaks + Replaces declaring so:
Unpacking libctf-nobfd0:amd64 (2.33.50.20200115-2) ...
dpkg: error
Marco d'Itri writes:
> On Jan 20, Russ Allbery wrote:
>> This also implies that there is arguably an SONAME issue with this library
>> given that two versions of the library with the same SONAME don't provide
>> the same symbols, but I suspect there were really, really good reasons to
>> not
Your message dated Mon, 20 Jan 2020 23:20:45 +
with message-id
and subject line Bug#940871: fixed in openconnect 8.02-1.1
has caused the Debian Bug report #940871,
regarding openconnect: CVE-2019-16239: Fix buffer overflow with chunked HTTP
handling
to be marked as done.
This means that you
Your message dated Mon, 20 Jan 2020 23:17:09 +
with message-id
and subject line Bug#934140: fixed in brightd 0.4.1-2+deb10u1
has caused the Debian Bug report #934140,
regarding brightd does not fade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Mon, 20 Jan 2020 23:18:09 +
with message-id
and subject line Bug#940871: fixed in openconnect 7.08-1+deb9u1
has caused the Debian Bug report #940871,
regarding openconnect: CVE-2019-16239: Fix buffer overflow with chunked HTTP
handling
to be marked as done.
This means
Your message dated Mon, 20 Jan 2020 23:17:16 +
with message-id
and subject line Bug#940871: fixed in openconnect 8.02-1+deb10u1
has caused the Debian Bug report #940871,
regarding openconnect: CVE-2019-16239: Fix buffer overflow with chunked HTTP
handling
to be marked as done.
This means
Processing control commands:
> tags -1 pending
Bug #949430 [src:webkit2gtk] webkit2gtk: FTBFS: fatal error: X11/Xlib-xcb.h: No
such file or directory
Added tag(s) pending.
--
949430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949430
Debian Bug Tracking System
Contact
Control: tags -1 pending
On Mon, Jan 20, 2020 at 08:44:30PM +0100, Mattia Rizzolo wrote:
> In file included from
> ../Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:64:
> /usr/include/gstreamer-1.0/gst/gl/x11/gstgldisplay_x11.h:26:10: fatal error:
>
On Jan 20, Russ Allbery wrote:
> This also implies that there is arguably an SONAME issue with this library
> given that two versions of the library with the same SONAME don't provide
> the same symbols, but I suspect there were really, really good reasons to
> not change the SONAME.
The
Processing control commands:
> notfound -1 0.136
Bug #948257 {Done: Ben Hutchings } [initramfs-tools]
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open
builtin file
'/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Bug #948301 {Done: Ben
Control: notfound -1 0.136
Control: fixed -1 0.136
On 2020-01-20 18:36:24 +, Ben Hutchings wrote:
> On Mon, 2020-01-20 at 10:30 +0100, Vincent Lefevre wrote:
> > Control: reopen -1
> > Control: found -1 0.136
> >
> > After the Linux kernel upgrade (initramfs-tools was upgrade to 0.136
> >
Processing control commands:
> affects -1 src:mailmanclient
Bug #949437 [src:postorius] postorius: FTBFS and autopkgtest failure (needs
update for new version of mailmanclient
Added indication that 949437 affects src:mailmanclient
--
949437:
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # condor
> block 936323 by 935927
Bug #936323
Source: postorius
Version: 1.2.4-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:mailmanclient
[X-Debbugs-CC: debian...@lists.debian.org,
mailmancli...@packages.debian.org]
Dear maintainers,
With a recent upload of
On Mon, Jan 20, 2020 at 04:32:14PM -0500, Boyuan Yang wrote:
> In this case a rebuild might be worthwhile anyway. Rebuilding package is
> almost always harmless.
Well, rebuilding movit would fix it, but it would also break any reverse
dependency, so they would also need to be rebuilt. And if my
Hi,
在 2020-01-19日的 10:38 +0100，Steinar H. Gunderson写道：
> On Sun, Jan 19, 2020 at 12:50:43AM -0500, Boyuan Yang wrote:
> > Recent source-only rebuild for nageru has mulitple FTBFS architectures on
> > buildd: https://buildd.debian.org/status/package.php?p=nageru
> >
> > The tail log all reads
Hi all,
On Fri, 4 Oct 2019 15:08:39 +0200 Reiner Herrmann
wrote:
> Dear maintainer,
>
> the attached patch fixes the FTBFS with GCC 9.
> I moved the linked library irs-export from LDFLAGS to LIBS, so that
> it will appear in the correct place on the command line.
>
> Kind regards,
> Reiner
Source: licensecheck
Version: 3.0.39-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of licensecheck you added an autopkgtest, awesome.
However, it fails. I copied some of the output at the
Hi Mike,
On Mon, Jan 20, 2020 at 12:00:18PM -0800, Mike Miller wrote:
> On Sat, Jan 18, 2020 at 23:54:53 +0100, Salvatore Bonaccorso wrote:
> > I've prepared an NMU for openconnect (versioned as 8.02-1.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it
Hi!
El lun., 20 ene. 2020 16:38, Moritz Mühlenhoff escribió:
> On Sat, Sep 21, 2019 at 08:42:14AM +0200, Andreas Tille wrote:
> > Hi,
> >
> > On Fri, Sep 20, 2019 at 11:55:03PM +0200, Moritz Mühlenhoff wrote:
> > > On Fri, Sep 20, 2019 at 06:41:05PM -0300, Lisandro Damián Nicanor
> Pérez Meyer
On Sat, Jan 18, 2020 at 23:54:53 +0100, Salvatore Bonaccorso wrote:
> I've prepared an NMU for openconnect (versioned as 8.02-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Seems fine to me, thank you!
--
mike
signature.asc
Description: PGP
Control: tag -1 pending
Hello,
Bug #940871 in openconnect reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #940871 [src:openconnect] openconnect: CVE-2019-16239: Fix buffer overflow
with chunked HTTP handling
Ignoring request to alter tags of bug #940871 to the same tags previously set
--
940871:
On Mon, Jan 20, 2020 at 01:01:00PM -0500, Yaroslav Halchenko wrote:
>
> > I'm fine with re-doing what I changed if you consider it really of
> > practical relevance. If you ask me we two would spent time we could
> > use more productively but its OK if you want to do it.
>
> You just rename and
Your message dated Mon, 20 Jan 2020 19:51:08 +
with message-id
and subject line Bug#943259: fixed in vim-autopep8 1.2.0-2
has caused the Debian Bug report #943259,
regarding vim-autopep8: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
On Thu, Sep 05, 2019 at 01:32:39PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Hi Boris!
>
> On Thu, 5 Sep 2019 at 13:17, Boris Pek wrote:
> >
> > Hi,
> >
> > > similar ping as for qpxtool, last upstream commits are from 2015. Are you
> > > planning to port it yourself or should it be
On Wed, Dec 25, 2019 at 05:25:20PM +0100, Moritz Mühlenhoff wrote:
> On Sun, Sep 15, 2019 at 03:57:47PM +0200, Gilles Filippini wrote:
> > > syrthes is the only remaining packages blocking the removal of pyqwt5. Are
> > > you planning to port the GUI yourself, should we (temporarily, until
> > >
On Fri, Nov 22, 2019 at 11:49:29PM +0100, Moritz Mühlenhoff wrote:
> On Thu, Aug 22, 2019 at 09:04:07AM +0200, Frank Lin Piat wrote:
> > Il will upgrade that package.
> >
> > Thank you Moritz
>
> Any progress? :-)
Status update: Qt4 has now been droppped from testing, qt4 will be removed
from
On Sat, Sep 21, 2019 at 08:42:14AM +0200, Andreas Tille wrote:
> Hi,
>
> On Fri, Sep 20, 2019 at 11:55:03PM +0200, Moritz Mühlenhoff wrote:
> > On Fri, Sep 20, 2019 at 06:41:05PM -0300, Lisandro Damián Nicanor Pérez
> > Meyer wrote:
> > > I've created a WIP merge request at
> > >
> > >
On Sun, Sep 30, 2018 at 04:22:44PM -0500, matt wrote:
> this has been fixed upstream:
> https://github.com/projectM-visualizer/projectm/pull/5
>
> though upstream has moved:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909977
Status update: Qt4 has now been droppped from testing, qt4 will
Clément Hermann writes:
> I have the same issue. The symbol is in the file provided by libcrypt1,
> however, it is in /usr/lib.
> what I have in /lib is:
> ```
> ls -l /lib/x86_64-linux-gnu/libcrypt.so.1
> lrwxrwxrwx 1 root root 16 déc. 27 20:31 /lib/x86_64-linux-gnu/libcrypt.so.1
> ->
On Fri, Nov 22, 2019 at 11:04:18AM +0300, Dmitry Shachnev wrote:
> Dear maintainers,
>
> I am going to remove the Python 2 part of python-qt4 from sid soon, but not
> before 10 days from now, 2019-12-02.
>
> If your package does not migrate away from it, it will become uninstallable.
>
> You
Your message dated Mon, 20 Jan 2020 19:34:43 +
with message-id
and subject line Bug#948388: fixed in navit 0.5.4+dfsg.1-1
has caused the Debian Bug report #948388,
regarding navit: fails to connect to gpsd
to be marked as done.
This means that you claim that the problem has been dealt with.
On Fri, Sep 06, 2019 at 10:50:58PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Source: mrtrix3
> Version: 3.0~rc3+git135-g2b8e7d0c2-3
> Severity: serious
> Justification: Depends upon Qt4 which will not be shipped with bullseye
> User: debian-qt-...@lists.debian.org
> Usertags:
On Mon, Oct 14, 2019 at 09:19:25AM +0200, Gürkan Myczko wrote:
> Hi Moritz
>
> I'm trying hard to get later versions of meshlab built and working, please
> don't remove the package.
> Later versions support qt5 already, so no more porting needed.
>
> There's also a lot of installations of it,
Processing control commands:
> tags -1 moreinfo
Bug #949385 [cacti] cacti: Cacti fails under PHP-FPM
Added tag(s) moreinfo.
--
949385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Sun, Sep 15, 2019 at 03:01:27PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Hi!
>
> El dom., 15 sep. 2019 09:49, Jonas Smedegaard escribió:
>
> > Quoting Lisandro Damián Nicanor Pérez Meyer (2019-09-12 23:54:32)
> > > On Thu, 12 Sep 2019 at 17:37, Lisandro Damián Nicanor Pérez Meyer
On Fri, Oct 11, 2019 at 11:12:31PM +0200, Moritz Mühlenhoff wrote:
> On Fri, Sep 13, 2019 at 07:54:04PM +0200, Francesco Poli wrote:
> > > Right now I see three possible "fixes" for the libgs problem:
> > [...]
> > > - fix the code, link to libgs during the build, as is done with all the
> > >
Control: tags -1 moreinfo
Hi Adam,
Thanks for reporting issues you encounter.
On 20-01-2020 15:28, Adam Thompson wrote:
>* What led up to the situation?
> Switching from Apache2 to Nginx, which mandated switching from mod_php to
> PHP-FPM.
In the cacti bug, you said that you upgraded php
On Tue, Dec 03, 2019 at 10:53:54PM +0100, Moritz Mühlenhoff wrote:
>
> I suggest that you go ahead with the salvaging, we're closing in on
> the Qt4 removal and we'll ask for removal of the remaining rdeps in
> about two months.
Status update: Qt4 has now been droppped from testing, qt4 will be
On Thu, Sep 12, 2019 at 11:48:46PM +0200, Axel Beckert wrote:
> > or we're moving forward with the Qt4 removal.
>
> Just move forward. IIRC amora already has been removed from testing,
> so it really shouldn't be an issue for the Qt4 removal.
Quick status update: qt4 is now removed from testing
Hi Nicholas
On 30/11/19 10:17 AM, Nicholas D Steeves wrote:
> Hi Balasankar,
>
> I'm not sure if you noticed this bug earlier this year, but it's RC
> now, so I took the liberty to fix it, because the autopep8 fix it
> blocks affects one of my packages. 'hope that's ok with you, since
> the
Your message dated Mon, 20 Jan 2020 19:05:39 +
with message-id
and subject line Bug#949242: fixed in libsoap-wsdl-perl 3.004-1
has caused the Debian Bug report #949242,
regarding FTBFS: test failures with libtimedate-perl 2.3100-1
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jan 2020 18:36:24 +
with message-id
and subject line Re: Bug#948257: "depmod: ERROR: ..." still occurs
has caused the Debian Bug report #948257,
regarding Error generating boot image
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 20 Jan 2020 18:36:24 +
with message-id
and subject line Re: Bug#948257: "depmod: ERROR: ..." still occurs
has caused the Debian Bug report #948257,
regarding thousands of identical lookup_builtin_file warnings
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Jan 2020 18:36:24 +
with message-id
and subject line Re: Bug#948257: "depmod: ERROR: ..." still occurs
has caused the Debian Bug report #948257,
regarding depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
not open builtin file
to be marked as
Your message dated Mon, 20 Jan 2020 18:36:24 +
with message-id
and subject line Re: Bug#948257: "depmod: ERROR: ..." still occurs
has caused the Debian Bug report #948257,
regarding libkmod2: update-initramfs fails in lookup_builtin_file()
to be marked as done.
This means that you claim that
Your message dated Mon, 20 Jan 2020 18:36:24 +
with message-id
and subject line Re: Bug#948257: "depmod: ERROR: ..." still occurs
has caused the Debian Bug report #948257,
regarding depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
not open builtin file
Your message dated Mon, 20 Jan 2020 18:36:24 +
with message-id
and subject line Re: Bug#948257: "depmod: ERROR: ..." still occurs
has caused the Debian Bug report #948257,
regarding depmod: lookup_builtin_file() could not open builtin file
to be marked as done.
This means that you claim that
On Mon, 20 Jan 2020, Andreas Tille wrote:
> > so I should be able to transfer over to debian-med. May be rename yours
> > into nibabel-med-initial so I could do it?
> I'm fine with re-doing what I changed if you consider it really of
> practical relevance. If you ask me we two would spent
Hi Paul and thanks (as always) for the explanation. (discussion
continued below)
On 1/12/20 11:04 PM, Paul Wise wrote:
> On Sun, 12 Jan 2020 21:42:53 -0500 Olek Wojnar wrote:
>
>> Could you please explain your rationale? The way I read Policy, I don't
>> see a problem. To clarify: the package is
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:websploit
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
On Mon, Jan 20, 2020 at 11:20:08AM -0500, Yaroslav Halchenko wrote:
>
> > I admit I have no idea how I can technically move a repository. Since I
>
> googled up
> https://docs.gitlab.com/ee/user/project/settings/
>
> Navigate to your project’s Settings > General > Advanced settings.
>
Source: storebackup
Version: 3.2.1-1
Severity: grave
Tags: security upstream
Hi,
The following vulnerability was published for storebackup.
CVE-2020-7040[0]:
|storeBackup: denial of service and symlink attack vector via fixed
|lockfile path /tmp/storeBackup.lock
The RC severity per se is a bit
On Mon, 20 Jan 2020, Andreas Tille wrote:
> Hi Yaroslav,
> On Mon, Jan 20, 2020 at 10:50:07AM -0500, Yaroslav Halchenko wrote:
> > > I think it would be helpful if you would remove the old repository
> > > in neurodebian-team.
> > shouldn't I (you) just "move" it on salsa under debian-med and
Hi Yaroslav,
On Mon, Jan 20, 2020 at 10:50:07AM -0500, Yaroslav Halchenko wrote:
>
> > I think it would be helpful if you would remove the old repository
> > in neurodebian-team.
>
> shouldn't I (you) just "move" it on salsa under debian-med and then push
> updated branches? so if anyone
Your message dated Mon, 20 Jan 2020 15:58:17 +
with message-id
and subject line Bug#940905: fixed in rexical 1.0.7-1
has caused the Debian Bug report #940905,
regarding rexical: CVE-2019-5477
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On Mon, 20 Jan 2020, Andreas Tille wrote:
> Hi Yaroslav,
> On Sun, Jan 19, 2020 at 02:41:52PM -0500, Yaroslav Halchenko wrote:
> > actually as far as I see it Sando has pushed everything for
> > 2.5.1-2
> >
Your message dated Mon, 20 Jan 2020 15:24:02 +
with message-id
and subject line Bug#949350: fixed in plastimatch 1.8.0+dfsg.1-2
has caused the Debian Bug report #949350,
regarding plastimatch build depends on libgdcm2-dev
to be marked as done.
This means that you claim that the problem has
Dear maintainer,
sciscipy appears not to be under current upstream development and porting to
Python 3 has not started. This is perhaps unlikely to be completed for a low
popcon package where upstream is not driving the process.
If python3-sciscipy is not likely to be ready for release with
Processing commands for cont...@bugs.debian.org:
> found 941218 2.0.13+1-5.1
Bug #941218 [src:guile-2.0] guile-2.0: FTBFS on ppc64el
Marked as found in versions guile-2.0/2.0.13+1-5.1.
> tags 941218 ftbfs bullseye sid
Bug #941218 [src:guile-2.0] guile-2.0: FTBFS on ppc64el
Added tag(s) sid,
Package: cacti
Version: 1.2.2+ds1-2+deb10u2
Severity: grave
Tags: upstream newcomer
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
Switching from Apache2 to Nginx, which mandated switching from mod_php to
PHP-FPM.
* What exactly did you do (or
Processing commands for cont...@bugs.debian.org:
> tags 916178 + wontfix
Bug #916178 [src:cups] roger-router-cli: missing dependency on cups
Added tag(s) wontfix.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916178:
Your message dated Mon, 20 Jan 2020 14:15:31 +
with message-id
and subject line Bug#948432: fixed in uncertainties 3.1.2-1
has caused the Debian Bug report #948432,
regarding uncertainties ftbfs with Python 3.8
to be marked as done.
This means that you claim that the problem has been dealt
Control: -1 +wontfix
# No change is going to happen in CUPS
Le lundi, 20 janvier 2020, 09.25:11 h CET Gianfranco Costamagna a écrit :
> On Mon, 10 Dec 2018 23:29:14 +0100 Marc Lehmann wrote:
> > Package: roger-router-cli
> > Version: 1.8.14-2+b3
> > Severity: serious
> > Justification: Policy
Your message dated Mon, 20 Jan 2020 13:51:32 +
with message-id
and subject line Bug#947176: fixed in iptables 1.8.4-2
has caused the Debian Bug report #947176,
regarding systemd: FTBFS: meson.build:1036:8: ERROR: Could not generate cargs
for libiptc:
to be marked as done.
This means that
Your message dated Mon, 20 Jan 2020 13:51:32 +
with message-id
and subject line Bug#946289: fixed in iptables 1.8.4-2
has caused the Debian Bug report #946289,
regarding ufw: fails to start with iptables 1.8.4
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 20 Jan 2020 13:51:32 +
with message-id
and subject line Bug#947176: fixed in iptables 1.8.4-2
has caused the Debian Bug report #947176,
regarding libiptc.pc non-functional
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
FTR, upstream just notified me that the latest version available on GitHub
is now ready for Python 3:
https://github.com/websploit/websploit
Cheers,
--
⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
⠈⠳⣄ Debian Long Term Support:
Hi Raphael
I just finished updating websploit. latest version now available on github
https://github.com/websploit/websploit
Cheers
On Wed, Jan 15, 2020 at 5:00 AM 0X0Ptim0Us <0x0ptim...@gmail.com> wrote:
> Hi Raphael
> I’m working on it and i will release new version before 24th.
> Thanks
>
>
>
Your message dated Mon, 20 Jan 2020 13:35:07 +
with message-id
and subject line Bug#949349: fixed in camitk 4.1.2-4
has caused the Debian Bug report #949349,
regarding camitk build depends on the removed lib{,vtk}gdcm2-dev
to be marked as done.
This means that you claim that the problem has
Hi Mike,
> > The following bug was filed in Debian:
> >
> > https://bugs.debian.org/946267
> >
> > … which reports a recent regression in cpio whereby --no-absolute-
> > filenames breaks the extraction of symlinks starting with /.
>
> I reported a similar issue in November, and I don't think
Hi John
src:forg looks to be pretty dead upstream and is by no means ready for use
with Python 3. Is anyone likely to do the porting work on a low popcon, dead
upstream project? Or is it time to remove forg from Debian?
regards
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/
Hi Laszlo
It seems that the upstream for src:sx has disappeared and so I guess the
porting work to change this package to be Python 3 compatible has not been
done.
At a quick glance, the porting doesn't look that hard to do, but is it
worthwhile for what appears to be a low popcon, dead
On Mon, 6 Jan 2020 12:38:52 -0600 Jamie Strandboge wrote:
> On Fri, 13 Dec 2019, Jamie Strandboge wrote:
>
> > I can confirm this. It looks like iptables-restore and iptables6-restore
> > in 1.8.4 has broken -n behavior with the nft varieties.
>
> This is
Hello,
On Sun, 19 Jan 2020 21:13:09 +0100 Thomas Goirand wrote:
> 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.
> >>
> >
> >
On Mon, Jan 20, 2020 at 01:15:42PM +0100, Hilko Bengen wrote:
> I was pretty sure that I had uploaded it. Oh well.
That's alright :)
Please remember to properly close this bug as well; "fixed" doesn't
close bugs.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52
* Mattia Rizzolo:
> On Mon, Jan 20, 2020 at 11:18:34AM +0100, Hilko Bengen wrote:
>> control: fixed -1 1.2.0-1
>>
>> The missing dh-python3 dependency was added in 1.2.0-1; that version
>> should no longer fail to rebuild from source in your setup.
>
> Maybe, but I can't see that version. Where
Hi Sandro,
On Sat, Jan 18, 2020 at 09:23:59PM -0500, Sandro Tosi wrote:
>
> This bug was closed, but the package has still some dependencies towards
> Python2 packages, in details:
>
> (binary:claws-mail-tools)Depends->python
>
> Re-opening, so that they can be taken care of.
Thanks! Hadn't
Your message dated Mon, 20 Jan 2020 14:02:28 +0200
with message-id <20200120120228.GA25866@localhost>
and subject line These appear to be fixed in 0.8.6.3-1
has caused the Debian Bug report #923509,
regarding src:haskell-blogliterately unsatisfiable build-dependency in sid
to be marked as done.
Your message dated Mon, 20 Jan 2020 14:02:28 +0200
with message-id <20200120120228.GA25866@localhost>
and subject line These appear to be fixed in 0.8.6.3-1
has caused the Debian Bug report #914449,
regarding haskell-blogliterately: FTBFS with ghc-8.4
to be marked as done.
This means that you
On Mon, Jan 20, 2020 at 11:18:34AM +0100, Hilko Bengen wrote:
> control: fixed -1 1.2.0-1
>
> The missing dh-python3 dependency was added in 1.2.0-1; that version
> should no longer fail to rebuild from source in your setup.
Maybe, but I can't see that version. Where is it?
--
regards,
Your message dated Mon, 20 Jan 2020 11:04:15 +
with message-id
and subject line Bug#949329: fixed in flatbuffers 1.11.0+dfsg1-1.1~rbalint1
has caused the Debian Bug report #949329,
regarding flatbuffers: Needs rebuild to migrate to testing
to be marked as done.
This means that you claim that
Your message dated Mon, 20 Jan 2020 10:51:32 +
with message-id <95e5042b7547a4b6f9ccc2bb8737ca18d60941ae.ca...@proact.de>
and subject line Re: Bug#948719: fio, (build-)dependencies unsatisfiable on
mipsel.
has caused the Debian Bug report #948719,
regarding fio, (build-)dependencies
Processing control commands:
> fixed -1 1.2.0-1
Bug #949194 [src:libnbd] libnbd: FTBFS: dh: unable to load addon python3
The source 'libnbd' and version '1.2.0-1' do not appear to match any binary
packages
Marked as fixed in versions libnbd/1.2.0-1.
--
949194:
control: fixed -1 1.2.0-1
The missing dh-python3 dependency was added in 1.2.0-1; that version
should no longer fail to rebuild from source in your setup.
Cheers,
-Hilko
Your message dated Mon, 20 Jan 2020 10:35:09 +
with message-id
and subject line Bug#948372: fixed in nibabel 2.5.1-3
has caused the Debian Bug report #948372,
regarding python3-nibabel: missing Breaks+Replaces: python-nibabel
to be marked as done.
This means that you claim that the problem
Hi Yaroslav,
On Sun, Jan 19, 2020 at 02:41:52PM -0500, Yaroslav Halchenko wrote:
>
> actually as far as I see it Sando has pushed everything for
> 2.5.1-2
> https://salsa.debian.org/neurodebian-team/nibabel/blob/dist/debian/proper/debian/changelog
> which is the latest AFAIK
Ahhh.
> PS I have
Your message dated Mon, 20 Jan 2020 09:50:04 +
with message-id
and subject line Bug#947794: fixed in python-apt 1.8.5
has caused the Debian Bug report #947794,
regarding python-apt: autopkgtest fails on deprecation *warnings* to stderr
to be marked as done.
This means that you claim that the
Hi,
I'm currently packaging the next major version of oasis3, and secondly
my key has expired so I can't upload for a few weeks
(Also I'm very busy untl Feb 8).
I think it would be best to remove oasis3 from testing for the netcdf
transition; it has no rdeps.
Kind regards
Alastair
On
1 - 100 of 118 matches
Mail list logo
