Re: renaming a source package

2020-10-15 Thread Paul Wise
On Fri, Oct 16, 2020 at 2:36 AM Mo Zhou wrote: > What should be the next steps following our convention? Since there is nothing using mkl-dnn (according to dak rm), just file a removal request with `reportbug ftp.debian.org`. $ ssh mirror.ftp-master.debian.org dak rm -s unstable -Rn mkl-dnn

renaming a source package

2020-10-15 Thread Mo Zhou
Hi mentors, I maintain a package which is previously named "mkl-dnn" https://tracker.debian.org/pkg/mkl-dnn . Then upstream renamed the source package to "onednn". So I just renamed the source in d/changelog and d/control then passed the new queue again:

Bug#972276: RFS: olive-editor/20200620-1 -- Professional open-source NLE video editor

2020-10-15 Thread Gürkan Myczko
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "olive-editor": * Package name: olive-editor Version : 20200620-1 Upstream Author : Olive Team * URL : https://www.olivevideoeditor.org/ * License :

Bug#972110: marked as done (RFS: cbor2/5.2.0-1 [ITP] -- Python implementation of CBOR)

2020-10-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Oct 2020 16:58:55 +0200 with message-id and subject line Package is in NEW has caused the Debian Bug report #972110, regarding RFS: cbor2/5.2.0-1 [ITP] -- Python implementation of CBOR to be marked as done. This means that you claim that the problem has been dealt

Bug#972112: marked as done (RFS: xmodem/0.4.6+dfsg-1 [ITP] -- xmodem file transfer protocol library (Python 3))

2020-10-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Oct 2020 16:59:20 +0200 with message-id and subject line Package is in NEW has caused the Debian Bug report #972112, regarding RFS: xmodem/0.4.6+dfsg-1 [ITP] -- xmodem file transfer protocol library (Python 3) to be marked as done. This means that you claim that the

Bug#971395: marked as done (RFS: zipios++/2.2.5.0-1 -- small C++ library for reading)

2020-10-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Oct 2020 15:09:47 +0200 with message-id <20201015130947.go246...@isildor.loewenhoehle.ip> and subject line Re: Bug#942884: Bug#971395: RFS: zipios++/2.2.5.0-1 -- small C++ library for reading zip files (documents) has caused the Debian Bug report #942884, regarding RFS:

Bug#942884: marked as done (RFS: zipios++/2.2.5.0-1 -- small C++ library for reading)

2020-10-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Oct 2020 15:09:47 +0200 with message-id <20201015130947.go246...@isildor.loewenhoehle.ip> and subject line Re: Bug#942884: Bug#971395: RFS: zipios++/2.2.5.0-1 -- small C++ library for reading zip files (documents) has caused the Debian Bug report #942884, regarding RFS:

Bug#971067: RFS: libexif-gtk/0.5.0-1

2020-10-15 Thread Hugh McMaster
Hi Andreas, mlt was taken care of. I spoke with the Debian QA Team and they were reluctant to remove gtkam because of popcon numbers. Myon said I should file a Serious bug against the package (#972085). Options for libexif-gtk seem to be reverting to GTK2 only, or building GTK2 and GTK3

Re: Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10)

2020-10-15 Thread Andrius Merkys
Hi Andreas, On 2020-10-15 15:26, Andreas Tille wrote: > when trying to build paw with gcc / fortran 10 there are some FORTRAN > errors: > > > ... > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (COMPLEX(4)/INTEGER(4)). >

Fortran issue in paw (Was: paw: ftbfs with GCC-10)

2020-10-15 Thread Andreas Tille
Control: tags -1 help Hi, when trying to build paw with gcc / fortran 10 there are some FORTRAN errors: ... Error: Type mismatch between actual argument at (1) and actual argument at (2) (COMPLEX(4)/INTEGER(4)). /<>/src/pawlib/comis/code/cs1200.F:138:24: 76 | CALL