Your message dated Sun, 08 Sep 2019 09:16:45 -0400 with message-id <08a9c7b9-4991-466b-9e06-5d189d6e4...@dartmouth.edu> and subject line Re: Your Debian package(s) will not migrate to testing has caused the Debian Bug report #933035, regarding dmtcp: Should this package be removed? to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 933035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: dmtcp Severity: serious The last upload was in 2014 and it's RC-buggy for a long time, it missed two stable releases already. Cheers, Moritz
--- End Message ---
--- Begin Message ---Version: 2.6.0-1 IMHO 933035 was a logistic report about bad state of the package and it was resolved by the last upload, this closing it here. I can do source only upload, but to say the truth, I didn't know that it is the requirement now. What needs to be addressed for migration is failing builds. Gene and Paul, you can access logs from https://buildd.debian.org/status/package.php?p=dmtcp to see what fixed for i386 and armhf On September 8, 2019 4:23:08 AM EDT, "j...@debian.org" <j...@debian.org> wrote: >On Sat, Sep 07, 2019 at 09:54:24AM +0000, Cooperman, Gene wrote: >> Hi Julian, >> Thank you for the courtesy message about the DMTCP >> package in sid (included below). >> Paul Grosu and I had submitted the package for dmtcp-2.6.0-1 . >> Yaroslav (cc'ed here) is the downstream Debian maintainer. >> >> Since Paul and I are unfamiliar with all the rules of Debian, could >> you help us with further details about why dmtcp-2.6.0-1 is stuck >> in sid? >> >> We looked at: https://tracker.debian.org/pkg/dmtcp >> It seems that the reasons there apply only to the old dmtcp-2.3.1-6 >> and not to our current submission: dmtcp-2.6.0-1 >> [...] > >Hi Gene, > >I ran (from the devscripts package) "grep-excuses dmtcp" and was told: > >dmtcp (- to 2.6.0-1) > Maintainer: Paul Grosu > 19 days old (needed 10 days) > Migration status for dmtcp (- to 2.6.0-1): BLOCKED: > Rejected/violates migration policy/introduces a regression > Issues preventing migration: > Updating dmtcp introduces new bugs: #933035 > Not built on buildd: arch amd64 binaries uploaded by yoh > missing build on armhf > missing build on i386 > Additional info: >Piuparts tested OK - >https://piuparts.debian.org/sid/source/d/dmtcp.html > 19 days old (needed 10 days) > >So this was not a source-only upload. > >This wiki page explains how to do a source-only upload using several >different approaches: >https://wiki.debian.org/SourceOnlyUpload > >So you'll need to do one of these when you upload version 2.6.0-2 (or >later), and then it will be able to migrate to testing (at least once >bug#933035 is also addressed). > >I hope this helps! > >Best wishes, > > Julian
--- End Message ---
