Re: RFS: libonig NMU for a RC bug
Laurent Bigonville schrieb am Samstag, den 04. August 2007: > Hi, > > Could someone review and upload libonig 5.9.0 > > http://mentors.debian.net/debian/pool/main/l/libonig/libonig_5.9.0-0.1.dsc > > This upload fix a RC bug, see > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426355 Uploading such an NMU is NOT okay. If you ever intent to upload such a crap again, use the delayed queue. And please only NMU the bug and not other stuff in the package. If you have problems with them, open a bug. But don't do this again. Alex - not amused -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libonig NMU for a RC bug
Loïc Minier schrieb am Sonntag, den 05. August 2007: > Hi Alexander, > > On Sun, Aug 05, 2007, Alexander Wirt wrote: > > Uploading such an NMU is NOT okay. If you ever intent to upload such a crap > > again, use the delayed queue. > > Please explain what part of this NMU was "crap". I see no new bugs > were filed after the upload. It is crap in a way that it is not like an NMU should be. Please read http://www.us.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-nmu-guidelines For example: Make sure that the package's bugs that the NMU is meant to address are all filed in the Debian Bug Tracking System (BTS). If they are not, submit them immediately. or: Upload your package to incoming in DELAYED/7-day (cf. Delayed uploads, Section 5.6.2), send the final patch to the maintainer via the BTS, and explain to them that they have 7 days to react if they want to cancel the NMU. So I still consider this as crap. > > > And please only NMU the bug and not other stuff in the package. If you > > have problems with them, open a bug. But don't do this again. > > While you're technically correct, I do think there's some latitude > between NMUs and QA uploads: > - last upload of the package 6 months ago -- despite the new upstream >releases > - RC bug since two months, with no comment from any of the two >maintainers (this includes you) and which had a fix (new upstream) I'm just the sponsor and wasn't aware of this bug. First time I heard about the NMU was yesterday from the mentors system. I already ping the maintainer who was on holidays til this weekend. I would have reacted tomorrow. > Full disclosure: I explained my exact position on the subject to my > sponsoree; French IRC conversation follows: I don't speak french, so without a translation this is useless to me. > My understanding is that my sponsoree did his best to do what is > usually requested to NMs: produce a lintian clean package, and AFAICT, > his changes were correct and fixed lintian warnings. No, there is a reason why the stated guidelines exist. Don't EVER do ANY package changes in an NMU if they are not bug. Linitan warnings are no bugs, some of them are, some not. If its a bug, fill one. But don't do such NMUs. He did fundamental changes to the package. This is not something that should ever be done in an nmu. > If you did notice any regression after this result, could you please > document them? I should be responsible for tracking their resolution, > and as you can see, I took full responsability of the upload by > subscribing to its PTS feeds and requiring my sponsoree to do so as > well. This is not a point of regression, but of following guidelines. They exists to get used, not to get ignored. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libonig NMU for a RC bug
Don Armstrong schrieb am Sonntag, den 05. August 2007: Hi, maybe I wasn't very politly, but I it was late after a hard weekend. I apologize for that. > > So I still consider this as crap. > > Why in the world are you even complaining about this? You're not the > maintainer of the package, and the NMU that was uploaded resolved the > problems correctly, even if it wasn't uploaded to DELAYED like it > should have been and $DEITY forbid, fixed some extra bugs as it went > by. Mostly because I still take care about the packages and the people I sponsor. It was a mistake to not subscribe to the PTS for this package. But I still thinks that most of my points were valid. This NMU was far away from just fixing one RC Bug. > > I'm just the sponsor and wasn't aware of this bug. First time I > > heard about the NMU was yesterday from the mentors system. I already > > ping the maintainer who was on holidays til this weekend. I would > > have reacted tomorrow. > > If you're the sponsor of the package, it is your responsibility to > monitor the packagaes which you sponsor, *especially* for RC bugs and > to fix them when the maintainer which you are sponsoring for cannot or > does not. > > If checking http://qa.debian.org/developer.php?login=formorer or > subscribing to the PTS for the packages you sponsor is too dificult, > then you should not be sponsoring them. > > For example, instead of responding with vitriol to this attempt to > improve the quality of debian packages, you should be contacting > Sebastian Harl <[EMAIL PROTECTED]> and helping get #430933 resolved. This bug is only in experimental and is currently resolved upstream. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#658498: sponsorship-requests and debian-mentors mailing list
Dmitry Smirnov schrieb am Wednesday, den 08. February 2012: > I think proposal regarding managing sponsorship through bug tracker was to > encourage usage of bug tracker. > > To me forwarding BTS activity for sponsorship-requests to mentors mail list > appears to be against the spirit and the desire of the proposal. > > Indeed we should encourage people to PTS-subscribe instead and therefore > provide certain freedom of choice. (I'm not talking regarding the best way to > inform subscribers regarding the change) > > So please let's filter > or clearly explain why not > so everybody would understand and agree. IMHO don and I did. Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120208070545.gh24...@smithers.snow-crash.org
Re: RFS: sweethome3d and sunflow [DM uploads to bpo]
Gabriele Giacone schrieb am Donnerstag, den 09. Februar 2012: > [ cc'ing d-mentors for RFS and mentors.d.o problems ] > > Hi, > following [0], first upload has to be sponsored. > Could anyone please upload sweethome3d and sunflow to backports for me? > > http://mentors.debian.net/debian/pool/main/s/sunflow/sunflow_0.07.2.svn396+dfsg-9~bpo60+1.dsc > [sweethome3d link is missing, uploaded to mentors but I got no response > and it's not in package list] > > At the moment, you can pick them up both on backports.d.o under > pub/UploadQueue because of my uploads without sponsor. as already said in IRC DM is not completly in place/tested. Coordinate with Ganneff and don't ask here for sponsors. Alex -- Alexander Wirt, formo...@formorer.de CC99 2DDD D39E 75B0 B0AA B25C D35B BC99 BC7D 020A -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120209105908.ga17...@hawking.credativ.lan
Re: Bug#677277: lists.debian.org: new list: sponsorship-reque...@lists.debian.org
On Fri, 22 Jun 2012, Don Armstrong wrote: > On Fri, 22 Jun 2012, Arno Töll wrote: > > On 12.06.2012 23:43, Michael Gilbert wrote: > > >> I'll just try this selectricity poll for now so we don't get billions > > >> of votes here: > > >> > > >> http://selectricity.org/quickvote/debianrfslist > > > > what's the status here? After Bart enjoyed us 100+ mails today, I think > > quite a few of us recall this bug again. :-) > > > > Also your poll seems to support our/my argument after a reasonable > > voting period. > > Considering that the outcome is only 19 to 10, it seems that there are > a fair number of people who also disagree with the mail being sent to > a separate list. That said, I'm fine with following the majority, and > with a separate list being created; I'll change the maintainer address > once that list has been created (but I don't create lists, so I won't > be creating this one, either.) I'm not certain if listmasters will > allow -mentors to be subscribed to the PTS, but presumably that will > be acceptable to other listmasters. I will create the list and it was my proposal to subscribe -mentors to the bts, so I'll take care of it. But don't expect anything until the freeze happens. Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120622185500.gb6...@snow-crash.org
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On Thu, 16 Aug 2012, Antti-Juhani Kaijanaho wrote: > On Thu, Aug 16, 2012 at 04:14:07PM +0200, Jerome BENOIT wrote: > > The situation is ambiguous as I posted before in the > > debian-de...@lists.debian.org list: > > the package is not orphaned, was removed but it is still present. > > There is no ambiguity. The package is present in unstable and thus is not > "removed" in the sense that word is commonly used without qualifiers. (The > proper way to describe what happened to the package is "removed from testing" > - > a release engineering action that doesn't imply any change in a package's > maintainership.) What let you think this? rmadison libpam-ssh libpam-ssh | 1.92-14 | squeeze | source, amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc W: Archive maintenance is in progress; database inconsistencies are possible. [Date: Fri, 02 Dec 2011 16:51:17 +] [ftpmaster: Alexander Reichle-Schmehl] Removed the following packages from unstable: libpam-ssh |1.92-14 | source libpam-ssh | 1.92-14+b1 | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc Closed bugs: 650644 Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120816154108.gc5...@snow-crash.org
Re: [Amavisd-new-debian-devel] RFS: amavisd-milter
Harald Jenny schrieb am Monday, den 21. June 2010: > On Mon, Jun 21, 2010 at 04:24:18PM +0200, Sven Mueller wrote: > > Harald Jenny schrieb: > > Hi Sven, > > > > > I would be willing to sponsor this package if you don't find any other > > sponsor. > > Thanks, would be very kind from you :-). > > > In particular, I would like you to contact the current > > amavisd-new maintainer wether he would like to collaborate on this. > > Well I was already in contact with Alexander Wirt who sponsored my first try > (was rejected by ftpmaster because it had some copyright issues), but it > seems he is very busy these days :-/. Anyways I cc this mail to him and the > amavisd-new list so the people responsible can comment on any problems they > might see. Indeed. With my amavisd-new maintainer hat on and is former sponsor I can see the package is ok and can be uploaded! :) > > > Seeing the number of open bugs on his package, I'm not 100% sure wether > > he would want to do so, but you should check > > If somebody wants to collaborate on the package I could move my mercurial rep > to alioth to allow for a better access... I offered to use the amavisd-new mercurial repo before. Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100621221410.ga6...@nelson.snow-crash.org
Re: RFS: subversion (updated package) [lenny-backports, 1.6.12dfsg-4~bpo50+1]
Sven Hoexter schrieb am Monday, den 10. January 2011: > On Mon, Jan 10, 2011 at 03:20:45AM +0100, Michael Diers wrote: > > > I am looking for a sponsor for the new version 1.6.12dfsg-4~bpo50+1 > > of my existing backport of package "subversion". > > Uploaded. > > > On 2011-01-09, subversion 1.6.12dfsg-4 has migrated to testing. It > > addresses the following issues: > > > > CVE-2010-4539: crash in mod_dav_svn when using SVNParentPath > > http://security-tracker.debian.org/tracker/CVE-2010-4539 > > > > CVE-2010-4644: fix server-side memory leaks triggered by 'blame -g' > > http://security-tracker.debian.org/tracker/CVE-2010-4644 > > So hereby I request a BSA number. Again? I already assigned one today (017) Alex -- Alexander Wirt, formo...@formorer.de CC99 2DDD D39E 75B0 B0AA B25C D35B BC99 BC7D 020A -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110110144808.ga10...@hawking.credativ.lan
Re: RFS: hexer -- backport to Squeeze (a bugfix, some refreshments)
Peter Pentchev schrieb am Monday, den 01. August 2011: > Dear mentors and backporters, > > I am looking for a sponsor for my package "hexer" - a backport to Debian > 6.0 (Squeeze) to fix #633508 (searching for octets > 127) and refresh JTFR backports is not for fixing bugs. You should consider talking to the release team about updating the package in stable. From the changelogs I don't see anything that justfies a backport. Just my 2 cent Alex Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110801093928.gf3...@smithers.snow-crash.org
Re: correct packaging of web applications
Arno Töll schrieb am Tuesday, den 23. July 2013: > Hi, > > On 23.07.2013 10:16, Sebastian Tramp wrote: > > Hi Arno, thank you for clarifying this. > > Is there a similar document for apache 2.2 ? > > you can stop worrying about Apache2 2.2 right now. Any new package you > are going to upload will go through Sid into Debian which will have > Apache 2.4 only. To be honest: I don't think thats true. As long as you care about backporting your package to stable, 2.2 should still be considered. Alex -- Alexander Wirt, formo...@formorer.de CC99 2DDD D39E 75B0 B0AA B25C D35B BC99 BC7D 020A -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130723083611.gc3...@hawking.credativ.lan
Re: correct packaging of web applications
On Tue, 23 Jul 2013, Russ Allbery wrote: > Alexander Wirt writes: > > Arno Töll schrieb am Tuesday, den 23. July 2013: > > >> you can stop worrying about Apache2 2.2 right now. Any new package you > >> are going to upload will go through Sid into Debian which will have > >> Apache 2.4 only. > > > To be honest: I don't think thats true. As long as you care about > > backporting your package to stable, 2.2 should still be considered. > > You pretty much have to branch to support both. The packaging is > substantially different. I have several packages working well for 2.2 and 2.4. At least for webapps, it is possible. Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130723173750.ga9...@lisa.snow-crash.org
RFS: fisg - fast irc statistics generator
Hi, I'm looking for some sponsor for a new package: fisg - fast irc statistics generator Description: fisg generates a web page from IRC logs (irssi, mIRC, eggdrop), its comparable to pisg or mircstats, but pretty faster than them. See http://www.midguard.de/stats.html - live demo or http://www.tnsp.org/fisg.php for more Informations. Ahh yeah the package: http://formorer.de/~formorer/devel/fisg/ Thanks Alex -- Alexander "formorer" Wirt KeyID: BC7D020A EMail: [EMAIL PROTECTED] ICQ: 28651245 WWW: http://www.formorer.de Encrypted and Signed Email preferred. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: RFS: netPanzer
Am Mo, den 08.03.2004 schrieb Bartosz Fenski aka fEnIo um 19:14: > On Sun, Mar 07, 2004 at 07:26:37PM +0100, Bartosz Fenski aka fEnIo wrote: > > I will be very thankful if someone of you kindly upload this package. > > It's related with #215783. > Well, noone interested? That's bad, cause I thought that Debian's > builders will be helpful with porting it to another architectures :/ > > Ok, nevermind. Thanks for reading it ;) You should give us a little bit more time. Maybe I will give it a try this evening or tomorrow. If its fine I will be happy to sponsor you, if not you have to fix the problems :). Sincerly Alex -- Alexander "formorer" Wirt KeyID: BC7D020A EMail: [EMAIL PROTECTED] ICQ: 28651245 WWW: http://www.formorer.de Encrypted and Signed Email preferred.
Re: RFS: netPanzer
On Tue, Mar 09, 2004 at 09:25:00PM +0100, Bartosz Fenski aka fEnIo wrote: > On Tue, Mar 09, 2004 at 09:58:19AM +0100, Alexander Wirt wrote: > > > Well, noone interested? That's bad, cause I thought that Debian's > > > builders will be helpful with porting it to another architectures :/ > > > Ok, nevermind. Thanks for reading it ;) > > You should give us a little bit more time. Maybe I will give it a try > > this evening or tomorrow. If its fine I will be happy to sponsor you, if > > not you have to fix the problems :). > Well, sorry for hurring up you, but I'm just too excited with whole > packaging stuff, and Debian as well ;) > Okay I did a look to your package. Your work has been done very nicely, but I have two small points for you to fix: 1) please don't install the pixmap into /usr/X11R6/include/pixmaps - take /usr/share/pixmaps instead 2) why is netpanzer-data a native package ? Please repackage it as a non-native package (with diff.gz und orig.tar.gz) If this two points are done I would be happy to sponsor your package. Netpanzer is really funny :). Alex -- Alexander "formorer" Wirt KeyID: BC7D020A EMail: [EMAIL PROTECTED]ICQ: 28651245
Re: RFS: noiz2sa -- abstract arcade shooter
Robert Lemmen wrote: On Mon, Nov 15, 2004 at 01:59:10PM +0100, Robert Lemmen wrote: i am looking for a sponsor for noiz2sa, a really nice little game. details: [...] the package is lintian-clean and builds fine under pbuilder, files are at http://www.semistable.com/files so please have a look and upload for me! oh come on guys! i can't believe noone wants to sponsor this, it's way cool! at least give it a test ride and you will see... Whoa, wild game, its your fault if I'm late at work today. :) I will take a look at the package this evening, if its fine I would be happy to be you sponsor. Alex signature.asc Description: OpenPGP digital signature
Re: RFS: noiz2sa -- abstract arcade shooter
Robert Lemmen wrote: On Mon, Nov 15, 2004 at 01:59:10PM +0100, Robert Lemmen wrote: i am looking for a sponsor for noiz2sa, a really nice little game. details: [...] the package is lintian-clean and builds fine under pbuilder, files are at http://www.semistable.com/files so please have a look and upload for me! oh come on guys! i can't believe noone wants to sponsor this, it's way cool! at least give it a test ride and you will see... Whoa, wild game, its your fault if I'm late at work today. :) I will take a look at the package this evening, if its fine I would be happy to be you sponsor. Alex signature.asc Description: OpenPGP digital signature
RFS: fisg - fast irc statistics generator
Hi, I'm looking for some sponsor for a new package: fisg - fast irc statistics generator Description: fisg generates a web page from IRC logs (irssi, mIRC, eggdrop), its comparable to pisg or mircstats, but pretty faster than them. See http://www.midguard.de/stats.html - live demo or http://www.tnsp.org/fisg.php for more Informations. Ahh yeah the package: http://formorer.de/~formorer/devel/fisg/ Thanks Alex -- Alexander "formorer" Wirt KeyID: BC7D020A EMail: [EMAIL PROTECTED] ICQ: 28651245 WWW: http://www.formorer.de Encrypted and Signed Email preferred. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: RFS: netPanzer
Am Mo, den 08.03.2004 schrieb Bartosz Fenski aka fEnIo um 19:14: > On Sun, Mar 07, 2004 at 07:26:37PM +0100, Bartosz Fenski aka fEnIo wrote: > > I will be very thankful if someone of you kindly upload this package. > > It's related with #215783. > Well, noone interested? That's bad, cause I thought that Debian's > builders will be helpful with porting it to another architectures :/ > > Ok, nevermind. Thanks for reading it ;) You should give us a little bit more time. Maybe I will give it a try this evening or tomorrow. If its fine I will be happy to sponsor you, if not you have to fix the problems :). Sincerly Alex -- Alexander "formorer" Wirt KeyID: BC7D020A EMail: [EMAIL PROTECTED] ICQ: 28651245 WWW: http://www.formorer.de Encrypted and Signed Email preferred. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: netPanzer
On Tue, Mar 09, 2004 at 09:25:00PM +0100, Bartosz Fenski aka fEnIo wrote: > On Tue, Mar 09, 2004 at 09:58:19AM +0100, Alexander Wirt wrote: > > > Well, noone interested? That's bad, cause I thought that Debian's > > > builders will be helpful with porting it to another architectures :/ > > > Ok, nevermind. Thanks for reading it ;) > > You should give us a little bit more time. Maybe I will give it a try > > this evening or tomorrow. If its fine I will be happy to sponsor you, if > > not you have to fix the problems :). > Well, sorry for hurring up you, but I'm just too excited with whole > packaging stuff, and Debian as well ;) > Okay I did a look to your package. Your work has been done very nicely, but I have two small points for you to fix: 1) please don't install the pixmap into /usr/X11R6/include/pixmaps - take /usr/share/pixmaps instead 2) why is netpanzer-data a native package ? Please repackage it as a non-native package (with diff.gz und orig.tar.gz) If this two points are done I would be happy to sponsor your package. Netpanzer is really funny :). Alex -- Alexander "formorer" Wirt KeyID: BC7D020A EMail: [EMAIL PROTECTED]ICQ: 28651245 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: backport questions
On Fri, 22 Jul 2016, Etienne Dysli-Metref wrote: > Hello mentors, > > I would like to backport Shibboleth packages [1] to jessie and wheezy. > > - What branch name should I use? > Documentation for git-buildpackage [2] says "debian/" so that > would yield "debian/jessie-backports-sloppy", but I've seen > "backports/" earlier so I'm unsure. > > - Can I push the backport branches to the repositories in [1]? The backports team doesn't care about the git, you will have to ask the other maintainers. > > - What should the changelog entry look like? "Backport to "? That + all backports specific changes to the package. > - Are older "backport" changelog entries kept or removed when a new > version is backported? > The Backports contribution doc [3] says: > > > Backports of an updated version of a package that was backported > > before may have a changelog that merges entries of backports of > > previous versions, but this is not required. > > but I can't make sense out of this... You can, but you don't have to include the changelog entrys in the changes file. We (ftpmasters) don't enforce this (anymore). Alex - ftpmaster signature.asc Description: PGP signature
Re: backport questions
On Fri, 22 Jul 2016, Etienne Dysli-Metref wrote: > Thank you Alex :) > > On 22/07/16 13:16, Alexander Wirt wrote: > >> - Can I push the backport branches to the repositories in [1]? > > The backports team doesn't care about the git, you will have to ask the > > other > > maintainers. > > Ok > > >> - What should the changelog entry look like? "Backport to "? > > That + all backports specific changes to the package. > And the distribution field should be the backport target > (jessie-backports-sloppy), right? Depends on your backport. The one that matches to your backport. And jessie-backports-sloppy is in every case wrong at this point in time. Alex signature.asc Description: PGP signature
Bug#842641: RFS: autoconf/2.69-10~bpo8+1
On Mon, 31 Oct 2016, Ben Pfaff wrote: > On Mon, Oct 31, 2016 at 11:16:18AM +0100, Gianfranco Costamagna wrote: > > Hi Ben, > > > > > I am looking for a sponsor for my package "autoconf". > > > Some packages depends on the new --runstatedir option which was added in > > > 2.69-9, > > > before they can be built for jessie-backports. Ex connman. > > > Is this request okay with you Ben, or do you want to handle it? > > > > I sponsored this upload in deferred/10, let me know if it sounds good to you > > (being in lowNMU threshold helps here :) thanks for that) > > Thanks for helping. I was planning to sponsor, but it's even easier > since you got to it first. Autoconf is a very important package and I don't think we want a backport that is not maintained by a regular uploader. Alex- Backports ftpmaster >
Re: Packaging from Git
On Mon, 06 Feb 2017, Narcis Garcia wrote: > __ > I'm using this express-made address because personal addresses aren't > masked enough at this list's archives. Mailing lists service > administrator should fix this. We don't intend to. Debian is an open Distribution and we believe in being able to be able to contact distributors and not to hide them. Alex - Debian Listmaster
Re: Packaging from Git
On Mon, 06 Feb 2017, Narcis Garcia wrote: > __ > I'm using this express-made address because personal addresses aren't > masked enough at this list's archives. Mailing lists service > administrator should fix this. > El 06/02/17 a les 10:42, Alexander Wirt ha escrit: > > On Mon, 06 Feb 2017, Narcis Garcia wrote: > > > >> __ > >> I'm using this express-made address because personal addresses aren't > >> masked enough at this list's archives. Mailing lists service > >> administrator should fix this. > > We don't intend to. Debian is an open Distribution and we believe in being > > able to be able to contact distributors and not to hide them. > > > > Alex - Debian Listmaster > > > > > > Mask and hide are two different measures. > A simple masking example, without hiding any data: > http://llista.gilug.org/pipermail/usuaris/2017-January/005484.html I can show you a dozen libs that unmasks those things. Alex
Re: changes file issue when packaging for backports
On Thu, 13 Nov 2014, quidame wrote: > Oops, > > not Priority: but Urgency: > > quidame wrote: > > Hi, > > > > I try to backport bilibop_0.4.22 source package (native). If only changes > > from 0.4.22 to 0.4.22~bpo70+1 are copied in to the changes file, lintian > > complains with the 'backports-changes-missing' error tag [1]. If I add > > -v0.4.21 dpkg-genchanges, the resulting changes file says: > > > > Priority: medium > > [...] > > Closes: 750507 756086 > > > > This overrides the priority of thr bpo package (low, in wheezy-backports); > > medium is the priority of 0.4.22 in unstable. It claims to close two bugs > > that are already closed in 0.4.22; more, one of these bugs id specific to > > jessie/sid, and the bugfix is reverted in the bpo. should I edit the changes > > file to modify Priority: field and modify or remove Closes: field ? Or > > replave > > -v0.4.21 option by something more relevant (shortened changelog entry > > for 0.4.22) ? Or can I let it go 'as is' ? Priority and closed bugs are not relevant for backports. So just ignore them and the right version for -v. Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141113084223.ga20...@lisa.snow-crash.org
Re: Trouble with Alioth user repo: can't be cloned
On Thu, 09 Jul 2015, lumin wrote: > Hi mentors, > > I encountered this trouble when making user's personal repo > on alioth.d.o according to the link below. > [https://wiki.debian.org/Alioth/Git] > > I've set up 2 repos: > http://anonscm.debian.org/cgit/users/cdluminate-guest/caffe.git > http://anonscm.debian.org/cgit/users/cdluminate-guest/test.git > Now I can browse them with cgit, but when I was about to clone them > it just failed. > > $ git clone > https://anonscm.debian.org/git/users/cdluminate-guest/caffe.git > Cloning into 'caffe'... > fatal: repository > 'https://anonscm.debian.org/git/users/cdluminate-guest/caffe.git/' not > found > > I checked the repo location, then > * do chmod -R a+xr REPO > * check git-daemon-export-ok > * check hook/post-update > but it still fails to clone with the same error report. > > I'm confused. And you are right to be confused. It was a bug on our (alioth) side. I fixed it and cloning is now possible. Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150709065849.ga16...@formorer.de
Re: Problem with Git Push
On Thu, 04 Jan 2018, Gianfranco Costamagna wrote: > Hello, > > > >Afterclone, I add the new changes and I try to make a push origin but I have > >this error:The requested URL returned error: 403. > > > this is a private repo > > please push there > git remote add upstream > git+ssh://youru...@anonscm.debian.org/git/collab-maint/cligh.git > > I just created a clone of that repo, and we will need a new unstable upload > with the new VCS fields in case. Don't use alioth for new packages / repos. Alioth is deprecated.
Re: Move packages from alioth to salsa
On Fri, 11 May 2018, Mattia Rizzolo wrote: > On Fri, May 11, 2018 at 11:55:33AM +0200, Arturo Borrero Gonzalez wrote: > > @Mattia, he seems to be looking for something similar to collab-main > > (Debian/?) > > Right, key being *seems*, I'd rather not speculate :) > Also, there are conceptual differences (in particular about > collaboration that is now made clear) between collab-maint and the > salsa's Debian group: > https://wiki.debian.org/Salsa/Doc#Namespace_concepts_.28Users.2C_Teams.29 > https://lists.debian.org/debian-devel-announce/2017/12/msg3.html > (stuff that you all should have read by now…) Thats not a difference. It was just made clearer than before. Alex signature.asc Description: PGP signature
Re: Move packages from alioth to salsa
On Mon, 14 May 2018, Geert Stappers wrote: > On Fri, May 11, 2018 at 11:04:13AM +0200, Jörg Frings-Fürst wrote: > > > > Hello, > > > > please can someone move my packages from alioth to salsa. > > My Username on both systems are jff-guest. > > > > * https://anonscm.debian.org/cgit/collab-maint/argyll.git > > * https://anonscm.debian.org/cgit/collab-maint/bitz-server.git > > * https://anonscm.debian.org/cgit/collab-maint/cil.git > > * https://anonscm.debian.org/cgit/collab-maint/dmidecode.git > > * https://anonscm.debian.org/cgit/collab-maint/downtimed.git > > * https://anonscm.debian.org/cgit/collab-maint/fast-cpp-csv-parser.git > > * https://anonscm.debian.org/cgit/collab-maint/foomatic-filters.git > > * https://anonscm.debian.org/cgit/collab-maint/gcstar.git > > * https://anonscm.debian.org/cgit/collab-maint/gnome-pie.git > > * https://anonscm.debian.org/cgit/collab-maint/ipmitool.git > > * https://anonscm.debian.org/cgit/collab-maint/ipmiutil.git > > * https://anonscm.debian.org/cgit/collab-maint/libhx.git > > * https://anonscm.debian.org/cgit/collab-maint/libmongo-client.git > > * https://anonscm.debian.org/cgit/collab-maint/libonig.git > > * https://anonscm.debian.org/cgit/collab-maint/libunistring.git/ > > * https://anonscm.debian.org/cgit/collab-maint/mailgraph.git > > * https://anonscm.debian.org/cgit/collab-maint/mwc.git > > * https://anonscm.debian.org/cgit/collab-maint/psocksxx.git > > * https://anonscm.debian.org/cgit/collab-maint/sane-backends.git > > * https://anonscm.debian.org/cgit/collab-maint/sane-frontends.git > > * https://anonscm.debian.org/cgit/collab-maint/scons.git > > * https://anonscm.debian.org/cgit/collab-maint/scons-doc.git > > * https://anonscm.debian.org/cgit/collab-maint/shotwell.git/ > > * https://anonscm.debian.org/cgit/collab-maint/simple-scan.git > > * https://anonscm.debian.org/cgit/collab-maint/uriparser.git > > * https://anonscm.debian.org/cgit/collab-maint/xbase64.git > > * https://anonscm.debian.org/cgit/collab-maint/xtrkcad.git > > > > There is now https://salsa.debian.org/debian/dmidecode > Account jff-guest has developer role. > > The Salsa repo is empty, it waits for > > cd existing_repo > git remote rename origin old-origin > git remote add origin g...@salsa.debian.org:debian/gpp.git > git push -u origin --all > git push -u origin --tags > > > > > Many thanks. > > And many repositories need to be done. > On thursday noon have I time for. > > Having URLs to scripts (and their documention) to automate this > would be a nice to have. > > > The above in others words: > * seen the request > * willing to do the work > * made a start > * would like to the others automated > * will the next few days be travelling > . upon return will need to start search the scripts > * that is point where help is welcome Several of such scripts exist and they should get used, especially the import feature. for example: https://salsa.debian.org/mehdi/salsa-scripts https://salsa.debian.org/satta/salsa-migration-tools https://wiki.debian.org/Salsa/AliothMigration#Using_a_single_Python_script Alex
Re: Gitlab API question: Fetching group ID works not reliably
On Tue, 15 May 2018, Andreas Tille wrote: > Hi, > > I'm using the following script to fetch the group ID of a salsa team: > > #!/bin/sh > > SALSA_URL="https://salsa.debian.org/api/v4"; > SALSA_TOKEN="MYSECRETTOKEN" > > SALSA_GROUP="med-team" > #SALSA_GROUP="science-team" > #SALSA_GROUP="r-pkg-team" > > SALSA_GROUP_ID=$(curl --silent -f -XGET --header "PRIVATE-TOKEN: > $SALSA_TOKEN" "$SALSA_URL/groups?all_available=false" | jq ".[] | > select(.path == \"$SALSA_GROUP\") | .id") > > echo "ID=$SALSA_GROUP_ID" Sorry this is inefficient. If you know the name of the group, query the group directly. Don't do it that way, that wastes a lot of ressources. SALSA_GROUP_ID=$(curl -s -f -XGET --header "PRIVATE-TOKEN: $SALSA_TOKEN" "$SALSA_URL/groups/$SALSA_GROUP" | jq '.id') Alex
Re: Move packages from alioth to salsa
On Thu, 17 May 2018, Geert Stappers wrote: > On Mon, May 14, 2018 at 07:36:53PM +0200, Alexander Wirt wrote: > > On Mon, 14 May 2018, Geert Stappers wrote: > > > On Fri, May 11, 2018 at 11:04:13AM +0200, Jörg Frings-Fürst wrote: > > > > > > > > please can someone move my packages from alioth to salsa. > > > > > > > > * https://anonscm.debian.org/cgit/collab-maint/argyll.git > > > > * https://anonscm.debian.org/cgit/collab-maint/bitz-server.git >[ ... 24 repos ... ] > > > > * https://anonscm.debian.org/cgit/collab-maint/xtrkcad.git > > > > >[ ... 1 repo manually ... ] > > > > Many thanks. > > > > > > And many repositories need to be done. > > > On thursday noon have I time for. > > > > > > Having URLs to scripts (and their documention) to automate this > > > would be a nice to have. > > > > > Several of such scripts exist and they should get used, especially the > > import > > feature. > > > > for example: https://salsa.debian.org/mehdi/salsa-scripts > > https://salsa.debian.org/satta/salsa-migration-tools > > https://wiki.debian.org/Salsa/AliothMigration#Using_a_single_Python_script > > > > | $ hostname > | paddy > | $ git config --list | grep origin.url > | remote.origin.url=https://salsa.debian.org/anarcat/alioth-migration > | $ # reading documation and source > | $ ./migrate-repo > | usage: migrate-repo [-h] [-v] [-d] [--loglevel LOGLEVEL] [--syslog [SYSLOG]] > | [--logfile LOGFILE] > | path salsa_path > | migrate-repo: error: too few arguments > | $ ./migrate-repo collab-maint/argyll debian/argyll > | ERROR: local repository not found: collab-maint/argyll > | $ > > Am I indeed supposed the run the script on the shell of the git server? > (Please confirm if so, Please provide additional information if not ) yes. Alex
Re: sql-ledger on salsa?
On Thu, 14 Jun 2018, Adam Borowski wrote: > On Thu, Jun 14, 2018 at 08:42:01AM -0400, Robert J. Clay wrote: > > Is the normal procedure now, to ask here or in debian-devel to have a > > DD add the project for the package to salsa? My salsa ID is > > rjclay-guest. > > It's the normal procedure. debian/sql-ledger is up, rights granted. > > As you say you have the repository on your disk, I skipped finding out how > to read archived Alioth projects, thus the repo is empty -- please push. Download the tarball, extract it and you have a bare repo to work with. Alex
Bug#901584: DMs' difficulties in uploading packages into Backports (Was: Re: Bug#901584 closed by Adam Borowski )
On Fri, 15 Jun 2018, Boyuan Yang wrote: > > -- Forwarded message -- > > From: Adam Borowski > > To: 901584-d...@bugs.debian.org > > Cc: > > Bcc: > > Date: Fri, 15 Jun 2018 15:37:07 +0200 > > Subject: Re: Bug#901584: RFS: flameshot/0.5.1+git20180601-1~bpo9+1 > > On Fri, Jun 15, 2018 at 11:04:31AM +0800, Boyuan Yang wrote: > > > I am looking for a sponsor for my package "flameshot" into > > > stretch-backports. > > > > > > * Package name: flameshot > > >Version : 0.5.1+git20180601-1~bpo9+1 > > > > It's an update, so it doesn't need to go through NEW, and you got DM rights. > > So you should be able to upload it yourself... > > I've done it this time, though. > > According to https://backports.debian.org/Contribute/ : > > "All Debian Developers (DD) can get their uid into the backports ACL. > If you want to get include please open a ticket in the debian request > tracker - please use the backports queue for the ticket." > > [...] > > "Debian Maintainers (DM) can also get their uid into the backports > ACL. Please follow the instructions for Debian Developers." > > "The Debian Maintainer needs to have upload rights for the specific > package they want to upload to backports (the same right they need for > uploading that package to unstable), otherwise the upload will not > succeed." > > That essentially means that a DM can only directly upload onto > Debian's backports repositories if: > > 1. That Debian Maintainer is granted DM upload right for the package; > > 2. and that Debian Maintainer asks another Debian Developer to open an > RT ticket to get the uid into the backports ACL and wait till the > ticket is finished. Note that non-DDs have no access to RT system thus > a sponsorship of RT ticket from other DDs is needed. 3. and another DD uploads the package to backports-new (DMs can't upload to new). (and as stated otherwise you can open tickets by mail). Alex
Re: Moving salsa repo to debian group
On Mon, Apr 20, 2020 at 04:25:19PM +0200, Adam Borowski wrote: > On Mon, Apr 20, 2020 at 11:51:38AM +0200, Mattia Rizzolo wrote: > > On Mon, Apr 20, 2020 at 03:13:14AM +0200, Adam Borowski wrote: > > > On Sun, Apr 19, 2020 at 10:33:19PM +0200, Baptiste BEAUPLAT wrote: > > > > Could someone move the following repository to the debian group? > > > > > > The original is still there. > > > > If you want a real move, you'll have to ask the salsa admins to do that > > since it requires owner permissions in the source namespace and > > maintainer permissions in the target namespace. Or first move it to a > > place where are DD has owner permissions and then said DD can move it > > again to /debian/. > > With no complex permissions, issue tracking, etc, on the old repo, I doubt > there's a benefit over create+push+delete, which doesn't require bothering > the admins. > > But, in case there'll be a repo that _has_ such metadata attached, it's good > to remember your advice. Thanks. Thats often wrong, because what you get is a working redirect, so that existing clones still work. Alex
Re: no auto-building
On Thu, 30 Jul 2015, Jerome BENOIT wrote: > Hello Forum: > > Recently one of my package, testu01 [1] not to mention it, has reached Sid. > So far, only the amd64 deb ball, the one uploaded, has really reached Sid: > deb ball for the other architecture have not yet been considered by the > auto-building machinery [2]: any hint is welcome ! non-free packages are not autobuilt by the usual autobuilder. But there is a special non-free buildd network. See: https://lists.debian.org/debian-devel-announce/2006/11/msg00012.html for details. Alex -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150730115110.gc26...@formorer.de
Re: Minor issues with collab-maint
On Sat, 02 Apr 2016, Tiago Ilieve wrote: > Hi, > > I'm having some minor issues with collab-maint today and didn't found > where to report it properly. There's a "collab-maint-devel"[1] list, > but there isn't any activity in there since June/2009. Please point > me to the correct mailing list if this isn't the proper one. > > * The HTTP certificate for "anonscm.debian.org" expired on Friday, > April 1, 2016 at 8:59:59 PM (no mention to timezone). This yields > browser warnings saying that the certificate can't be trusted. That was a misconfiguration of mine. It is fixed by now. Alex
