Hello,
some time ago I uploaded a new version of dballe, which went through NEW
because of a change in binary package names (SONAME bump, IIRC). It took
two weeks to go through NEW and I turned my energy towards other things
since then.
Now I see that things got stuck for the transition to testin
Hi Enrico,
On 29-12-2019 09:52, Enrico Zini wrote:
> some time ago I uploaded a new version of dballe, which went through NEW
> because of a change in binary package names (SONAME bump, IIRC). It took
> two weeks to go through NEW and I turned my energy towards other things
> since then.
>
> Now
Package: wnpp
Severity: normal
I request assistance with maintaining the terminator package. [1]
The upstream seems pretty much dead, though I'd like the keep the
package available. Popcon [2] is not too bad, and I think usage on
Ubuntu is also pretty stable (I know a lot of people).
The package
On Sun, Dec 29, 2019 at 12:32:24PM +0100, Paul Gevers wrote:
>
> [1] Source packages that build binaries unknown to the archive currently
> need these binaries to be uploaded by the maintainers for reviewing by
> ftp-master in NEW. IIRC there have been multiple proposals to avoid
> these binaries
On Sun, Dec 29, 2019 at 09:52:44AM +0100, Enrico Zini wrote:
> Hello,
>
> some time ago I uploaded a new version of dballe, which went through NEW
> because of a change in binary package names (SONAME bump, IIRC). It took
> two weeks to go through NEW and I turned my energy towards other things
>
On Sun, Dec 29, 2019 at 12:32:24PM +0100, Paul Gevers wrote:
> > Now I see that things got stuck for the transition to testing, and I'm
> > asking for help figuring out what to do.
>
> I'm happy to help.
Thanks! <3
> The python3.8 transition is not a classical transition, so this normally
> hel
Package: wnpp
Severity: wishlist
Owner: Adam Borowski
* Package name: topline
Version : 0.1
Upstream Author : yours truly
* URL : https://github.com/kilobyte/topline
* License : GPL-2+noA
Programming Lang: C
Description : per-core/NUMA CPU and disk util
On 12/29/19 3:53 PM, Theodore Y. Ts'o wrote:
> On Sun, Dec 29, 2019 at 09:52:44AM +0100, Enrico Zini wrote:
>> some time ago I uploaded a new version of dballe, which went through NEW
>> because of a change in binary package names (SONAME bump, IIRC). It took
>> two weeks to go through NEW and I tu
On Sun, Dec 29, 2019 at 11:32 AM Paul Gevers wrote:
> [1] Source packages that build binaries unknown to the archive currently
> need these binaries to be uploaded by the maintainers for reviewing by
> ftp-master in NEW. IIRC there have been multiple proposals to avoid
> these binaries from either
On Sun, Dec 29, 2019 at 1:29 PM Roberto C. Sánchez wrote:
> Would it not be possible to eliminate the need for the second
> unnecessary upload by requiring two signed .changes files to go into
> NEW? A signed binary changes which would form the basis of the FTP
> master review and a signed source
On Sun, Dec 29, 2019 at 10:51:36PM +0100, Sebastiaan Couwenberg wrote:
> > Wow, two weeks? I uploaded a new version of f2fs-tools back in July,
> > with the same issue (SONAME bump), and it's still not gotten through
> > NEW.
> >
> > I had assumed everyone was waiting 5-6+ months to get through N
11 matches
Mail list logo
