Reply in-line :- On 18/03/2018, Andrey Rahmatullin <w...@debian.org> wrote: > On Sun, Mar 18, 2018 at 01:54:20PM +0530, shirish शिरीष wrote:
<snipped> Dear Andrey, First of all thank you for responding. >> and maybe at some point also the BTS although then reportbug would >> have to be retooled to query salsa/gitlab so similar functionality can >> be provided as it does for bug creation . > I think the current consensus is that it won't. > That is a relief to know as I rely on reportbug and the BTS quite a bit >> Now if the package maintainer is just a DM, even (s)f he prepares a >> package, (s)he still needs the ok of a DD to upload/sponsor the >> package so it fit for distribution i.e. new, experimental or unstable >> and ftp-mirror and that whole process. > This is not true. Please read https://wiki.debian.org/DebianMaintainer > I think you mean regular non-DM non-DD maintainers. > Hmm.. I was under the impression that DM or Debian Maintainers do not have upload rights and only DD's have. I am confused when I see packages such as https://tracker.debian.org/news/896579/accepted-qbittorrent-403-1-source-amd64-into-unstable/ just to take as an example. There have been few packages where I have been confused as well. Now here it says - Maintainer: Cristian Greco <crist...@debian.org> Changed-By: Andrew Starr-Bochicchio <a...@debian.org> now what role does or did Andrew play in the above. Is he the uploader or just a reviewer of the work that Cristian Greco did ? Or is it some sort of team-maintenance thing, not sure. I do and did see that Cristian did upload some of the older package releases but now Andrew seems to be handling that part. >> Now a user of the package is usually in the dark about this and there >> is a possibility of upsetting the maintainer even though the person is >> active on their own team. > The maintainer can also be preparing the package for uploading and you > cannot do anything to know that except asking them. And if they committed > the work in progress into the VCS the tracker will show that. where would it show ? Please share an example so I know what to look for. > tracker could show RFSes though, like how-can-i-help does, actually I > thought it already shows them. > I see two packages which have RFS against them in how-can-i-help New packages waiting for sponsorship (reviews/tests are also useful): - logrotate - https://bugs.debian.org/884697 - RFS: logrotate/3.13.0-1 ITA - xml-core - https://bugs.debian.org/885641 - RFS: xml-core/0.18-1 [ITA] but neither one of them shows up in tracker.debian.org . I do see that some people have decided to adopt those packages which is good though. >> I looked at the tracker.debian.org BTS page and saw [2] 317711 which >> exactly talks of this kind of situation and more and this was filed in >> 2005 so it isn't something which isn't known, just hasn't been >> acknowledged. > It only talks about NEW. tracker shows binary NEW, though only in the > version sidebar, not in the news. > Do you know any other states which it should track? It's not clear from > your email. > Maybe I was not clear enough, my concerns are not with the 'NEW' queue i.e. $ aptitude search '~n' but for existing package updates also to have the info. of package updates done but not yet in the archive in the sidebar as well. Maybe I should file a new bug ? >> This unknowing became apparent to me when the debian-mate were doing >> packaging for the 1.20.0 release [3] and more recently when I am >> asking for a point release of qbittorrent [4] . In this case I know >> that the maintainer is usually pretty active and perhaps uses the >> package as well. > It's not clear what problems do you have with these packages and what are > you proposing to solve them. > Simply, have a more effective feedback loop for know-how as to what's coming while at the same time create less bit of noise in the BTS asking for new point releases. The only other recourse I know is to traverse https://incoming.debian.org/debian-buildd/pool/ and that isn't user/human friendly as it's machine-friendly. I hope I was able to clarify what I meant above. > -- > WBR, wRAR > -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
