Re: Help with source only upload
Don't break threads please. On Wed, Aug 28, 2019 at 10:28:53PM -0500, Elías Alejandro wrote: > >The command is the same, isn't it? > uhm.. I don't think so. You need to explain why. > I was reading about to source-only > uploads because of[1] however I've uploaded by _mistake_ > with a changes file included binary and source, after > some hours I've noticed that it hasn't been built by buildd[2]. This sounds good. > I'd like to generate a changes file for a new debian > version of the package with only the source. This sounds good too. So what's wrong with the command? > I was reading also that if version ends in -0 or -1 source can be > included but not for the next version, I'm not sure if it's the > explanation. And this doesn't, as this talks about inclusion of orig.tar in the source package, not about things you talked earlier. This is a completely unrelated question but no, you don't need to include orig.tar in the source changes if it waas already uploaded previously. > In other hand, why buildd wasn't be able to built if the > changes file also included the source file? buildds do not build binaries that were uploaded by the uploader. -- WBR, wRAR signature.asc Description: PGP signature
Re: Help with source only upload
>The command is the same, isn't it? uhm.. I don't think so. I was reading about to source-only uploads because of[1] however I've uploaded by _mistake_ with a changes file included binary and source, after some hours I've noticed that it hasn't been built by buildd[2]. I'd like to generate a changes file for a new debian version of the package with only the source. I was reading also that if version ends in -0 or -1 source can be included but not for the next version, I'm not sure if it's the explanation. In other hand, why buildd wasn't be able to built if the changes file also included the source file? [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html [2] https://qa.debian.org/excuses.php?package=sugar-log-activity Best regards, Elías
Bug#935537: marked as done (RFS: streamlink/1.2.0+dfsg-1 -- CLI for extracting video streams from various websites to a video player)
Your message dated Thu, 29 Aug 2019 02:14:14 +0200 with message-id <20190829001414.ga1...@angband.pl> and subject line Re: Bug#935537: RFS: streamlink/1.2.0+dfsg-1 has caused the Debian Bug report #935537, regarding RFS: streamlink/1.2.0+dfsg-1 -- CLI for extracting video streams from various websites to a video player 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.) -- 935537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "streamlink" for a new upstream version 1.2.0. * Package name: streamlink Version : 1.2.0+dfsg-1 Upstream Author : Streamlink Team * URL : https://streamlink.github.io/ * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1 Section : python It builds those binary packages: python3-streamlink - Python module for extracting video streams from various websites python3-streamlink-doc - CLI for extracting video streams from various websites (documentation) streamlink - CLI for extracting video streams from various websites to a video player To access further information about this package, please visit the following URL: https://mentors.debian.net/package/streamlink Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_1.2.0+dfsg-1.dsc More information about streamlink can be obtained at https://streamlink.github.io/ Changes since the last upload in unstable: streamlink (1.2.0+dfsg-1) unstable; urgency=medium * New upstream version 1.2.0+dfsg * Update remove_new_version_check patch * Move from PyCrypto to pycryptodomex * Fix typo in manpage with patch plugins.pixiv-fix-doc-typo-thats-that-s -- Alexis Murzeau Fri, 23 Aug 2019 19:31:42 +0200 Regards, -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Fri, Aug 23, 2019 at 07:39:43PM +0200, Alexis Murzeau wrote: > * Package name: streamlink >Version : 1.2.0+dfsg-1 > Changes since the last upload in unstable: > streamlink (1.2.0+dfsg-1) unstable; urgency=medium > > * New upstream version 1.2.0+dfsg > * Update remove_new_version_check patch > * Move from PyCrypto to pycryptodomex > * Fix typo in manpage with patch plugins.pixiv-fix-doc-typo-thats-that-s ✓ -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The root of a real enemy is an imaginary friend. ⠈⠳⣄--- End Message ---
Debian Salsa packaging guidelines and conventions
Dear mentors, I'm considering to move package sources to Debian salsa. And, I'm quite unsure, what's a correct approach to do it. Especially, what are conventions and guidelines for packaging. Lets assume, that packaged software doesn't require any special adjustments, and packaged software's upstream is stored in a publicly available git repository. What's standard gbp.conf, and other settings? I very much like to stick to conventions, for easier cooperation, when cooperation is needed. So, I'm looking for the most recognized way to package such projects hosted on git within Debian developers. I did find https://wiki.debian.org/Salsa/Doc and https://wiki.debian.org/Salsa/FAQ. Kind regards, Miroslav Kravec
Re: NATS Server Debian Package
Hi Etienne, Apologies, I must not be and assumed a direct reply. I'll join... Thanks Etienne! Best regards, Colin On Wed, Aug 28, 2019 at 12:01 AM Etienne Dysli Metref < etienne.dysli-met...@switch.ch> wrote: > On 27/08/2019 22.43, Colin Sullivan wrote: > > Soft ping... Would you be willing to provide some guidance and > > sponsor us? > > Hello Colin, > > Are you subscribed to the mailing-list? Below is what I replied two > weeks ago. You'll also find another reply in the list archive. [3] > > As a prospective user of NATS, I'd welcome its inclusion in Debian. :) > Have you already contacted the Debian Go Packaging team? [1] They can > probably help you prepare your package for Debian. > > I think one thing in particular that Debian requires and is very alien > to golang developers is that all your software's dependencies must also > be Debian packages. A Debian package isn't allowed to contain copies of > code from other software packages. [2] Likewise, your build system can't > download dependencies to build and link them (Debian's servers build > packages without network access). > > I hope this helps you getting started. > > Cheers, > Etienne > > [1] https://go-team.pages.debian.net/ > [2] > > https://www.debian.org/doc/debian-policy/ch-source.html#convenience-copies-of-code > [3] https://lists.debian.org/debian-mentors/2019/08/msg00098.html > >
Bug#935900: z3 sponsorship
Hi Fabian, thanks for working on this. I don't have much time right now to look at your package, but if you have found nobody in one or two week, please feel free to ping me, and I'll try to do the sponsorship. Sorry for not being able to help right now! Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature
Re: Help with source only upload
On Tue, Aug 27, 2019 at 11:39:49PM -0500, Elías Alejandro wrote: > Hello, > I hope you are doing well. > Do you know what's the option to generate with gbp a Source Only Upload > for packages after its first debian release? > The following sentence: > > gbp buildpackage --git-pbuilder --git-pbuilder-options=--source-only-changes > > works fine for package_version-1 but I'd like to do the same for > package_version-2 and generate the source-only .changes file The command is the same, isn't it? -- WBR, wRAR signature.asc Description: PGP signature
