Bug#901421: ITP: golang-github-googleapis-gnostic -- compiler for OpenAPI specification
Package: wnpp Severity: wishlist Owner: Dmitry Smirnov X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Control: affects -1 docker.io Package name: golang-github-googleapis-gnostic Version: 0.2.0 Upstream Author: Google Inc. License: Apache-2.0 URL: https://github.com/googleapis/gnostic Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-googleapis-gnostic Description: compiler for OpenAPI specification Protocol Buffers (https://developers.google.com/protocol-buffers/) provide a language-neutral, platform-neutral, extensible mechanism for serializing structured data. gnostic's Protocol Buffer models for the OpenAPI Specification can be used to generate code that includes data structures with explicit fields for the elements of an OpenAPI description. This makes it possible for developers to work with OpenAPI descriptions in type-safe ways, which is particularly useful in strongly-typed languages like Go and Swift. . gnostic reads OpenAPI descriptions into these generated data structures, reports errors, resolves internal dependencies, and writes the results in a binary form that can be used in any language that is supported by the Protocol Buffer tools. A plugin interface simplifies integration with API tools written in a variety of different languages, and when necessary, Protocol Buffer OpenAPI descriptions can be reexported as JSON or YAML. signature.asc Description: This is a digitally signed message part.
Re: package not in testing due to autopkgtest of other package testing against third known broken package
Quoting Paul Gevers (2018-06-12 19:57:45) > On 12-06-18 17:00, Jonas Smedegaard wrote: [...] >> I now did an NMU simply disabling ruby-bootstrap-sass autopkgtest >> parts related to ruby-compass. > > That will not help ruby-sass migrate, as the problem lies elsewhere: > https://release.debian.org/britney/update_output.txt > trying: ruby-sass > skipped: ruby-sass (5, 5, 102) > got: 46+0: a-3:i-42:a-0:a-0:a-0:m-0:m-0:m-0:p-0:s-1 > * i386: ruby-compass, ruby-compass-core, ruby-compass-import-once > I think you want to ask for removal of ruby-compass* from testing. > Britney refuses to update ruby-sass in testing because the amount of > installable packages will go down if it does. > https://release.debian.org/doc/britney/short-intro-to-migrations.html [...] > You had to search elsewhere, you found a red harring. Thanks for the explanation! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#901412: ITP: ibmquantumexperience -- A Python library for the IBM Quantum Experience API (Python 3)
Package: wnpp Severity: wishlist Owner: Luciano Bello * Package name: ibmquantumexperience Version : 1.9.2 Upstream Author : QISKit * URL : https://github.com/QISKit/qiskit-api-py * License : Apache 2.0 Programming Lang: Python Description : A Python library for the IBM Quantum Experience API (Python 3) This is needed for #880994
Re: Please remove your obsolete repos from alioth *NOW*
On Tue, 12 Jun 2018, Wouter Verhelst wrote: Hi Wouter, > On Wed, May 30, 2018 at 10:24:33AM +0200, Alexander Wirt wrote: > > Hi, > > > > we still have 175GiB git repos left on alioth. Please remove them asap. > > Life has been busy recently, and I didn't see this message until now. > > I guess that alioth has been shut down by now. > > Is it still possible for me to go in and remove repositories that are no > longer needed? Thanks for coming back to us, but unfortunately it is now to late. The process of archiving is done. > If not, then meh, never mind, but I thought I'd ask first. Thanks for asking! Alex
Re: package not in testing due to autopkgtest of other package testing against third known broken package
Hi Jonas, Just to start with, my message may sound harsh, it is meant to explain though. On 12-06-18 17:00, Jonas Smedegaard wrote: > Sharing here in case it is an example of a structural issue needing > tweaking somewhere... > > ruby-sass works fine. Great. > ruby-compass previously worked fine, but is now dead upstream and > conflicts with recent ruby-sass. https://bugs.debian.org/876608 > > ruby-bootstrap-sass works fine - but autopkgtest-depends on ruby-compass > which stopped working when ruby-sass declared breakage with ruby-compass > - and I noticed only now that effectively recent ruby-sass didn't enter > testing. Yes, but this has nothing to do with the package not migrating. That would only account for 10 days, just like the excuses say. In this case, it wasn't migrated before we turned the code on to test autopkgtest. > I now did an NMU simply disabling ruby-bootstrap-sass autopkgtest parts > related to ruby-compass. That will not help ruby-sass migrate, as the problem lies elsewhere: https://release.debian.org/britney/update_output.txt trying: ruby-sass skipped: ruby-sass (5, 5, 102) got: 46+0: a-3:i-42:a-0:a-0:a-0:m-0:m-0:m-0:p-0:s-1 * i386: ruby-compass, ruby-compass-core, ruby-compass-import-once I think you want to ask for removal of ruby-compass* from testing. Britney refuses to update ruby-sass in testing because the amount of installable packages will go down if it does. https://release.debian.org/doc/britney/short-intro-to-migrations.html > How could I have known ahead about that autopkgtest-depends? You can search for Testsuite-Triggers in the Sources file if you really want to. But for new regressions that occur, rest assure that they will be detected and will be acted on. > "build-rdeps ruby-compass" doesn't reveal ruby-bootstrap-sass as a cause > for trouble. > > Can we improve some infrastructure to better catch situations like this > in the future? You had to search elsewhere, you found a red harring. Paul signature.asc Description: OpenPGP digital signature
package not in testing due to autopkgtest of other package testing against third known broken package
Sharing here in case it is an example of a structural issue needing tweaking somewhere... ruby-sass works fine. ruby-compass previously worked fine, but is now dead upstream and conflicts with recent ruby-sass. https://bugs.debian.org/876608 ruby-bootstrap-sass works fine - but autopkgtest-depends on ruby-compass which stopped working when ruby-sass declared breakage with ruby-compass - and I noticed only now that effectively recent ruby-sass didn't enter testing. I now did an NMU simply disabling ruby-bootstrap-sass autopkgtest parts related to ruby-compass. How could I have known ahead about that autopkgtest-depends? "build-rdeps ruby-compass" doesn't reveal ruby-bootstrap-sass as a cause for trouble. Can we improve some infrastructure to better catch situations like this in the future? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Please remove your obsolete repos from alioth *NOW*
Hi, On Wed, May 30, 2018 at 10:24:33AM +0200, Alexander Wirt wrote: > Hi, > > we still have 175GiB git repos left on alioth. Please remove them asap. Life has been busy recently, and I didn't see this message until now. I guess that alioth has been shut down by now. Is it still possible for me to go in and remove repositories that are no longer needed? If not, then meh, never mind, but I thought I'd ask first. -- Could you people please use IRC like normal people?!? -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008 Hacklab
Bug#901390: RFP: python-orderedmultidict -- an ordered multivalue dictionary that retains method parity with Python's dict.
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org --- Please fill out the fields below. --- Package name: python-orderedmultidict Version: 1.0 Upstream Author: Ansgar Grunseid URL: https://github.com/gruns/orderedmultidict License: Public Domain Description: A multivalue dictionary is a dictionary that can store multiple values per key. An ordered multivalue dictionary is a multivalue dictionary that retains the order of insertions and deletions. -- Martin Iñaki Malerba inakimmale...@gmail.com | +54 02945 15468443 in...@satellogic.com
Re: Debian 10 please update gimp to 2.10....
On Tue, Jun 12, 2018 at 09:48:22AM +0200, Samuel Thibault wrote: > Geert Stappers, le mar. 12 juin 2018 09:41:53 +0200, a ecrit: > > On Tue, Jun 12, 2018 at 08:36:38AM +0200, Samuel Thibault wrote: > > > DutchGigalo, le lun. 11 juin 2018 23:16:21 -0700, a ecrit: > > > > Debian 10 (buster) please update gimp to 2.10 > > > > > > gimp 2.10 is in unstable already, please be patient. > > > > Information at https://tracker.debian.org/pkg/gimp > > says there is more needed then just being patient. > > It says that users wanting it should be patient for the developers to > have a look at the issues. Thing I'm aiming for is that users[1] do more then being patient. Example given | | Hello Developers, | | GIMP, the GNU image manupilation program, | has released version 2.10 several weeks ago. | | However, it is not yet in Debian. | What could I do to make it possible? | | Yours sincerely | Joe Random | Who is fairly new to libre software | Hi Joe, Thank you for expressing your interest in this amazing eco-system called "Debian". How make it possible? As in life: Be there, find what you care about. And care about it. Stuff to read * https://en.wikipedia.org/wiki/Robustness_principle * http://www.catb.org/~esr/faqs/hacker-howto.html * http://www.catb.org/~esr/faqs/smart-questions.html * https://www.debian.org/intro/help And turn thoughts into actions. Regards Geert Stappers [1] Those who feel insulted for being a drug addict, are free to do so. -- Where did we agree that somebody else should do it?
Re: Debian 10 please update gimp to 2.10....
Geert Stappers, le mar. 12 juin 2018 09:41:53 +0200, a ecrit: > On Tue, Jun 12, 2018 at 08:36:38AM +0200, Samuel Thibault wrote: > > DutchGigalo, le lun. 11 juin 2018 23:16:21 -0700, a ecrit: > > > Debian 10 (buster) please update gimp to 2.10 > > > > gimp 2.10 is in unstable already, please be patient. > > Information at https://tracker.debian.org/pkg/gimp > says there is more needed then just being patient. It says that users wanting it should be patient for the developers to have a look at the issues. Samuel
Re: Debian 10 please update gimp to 2.10....
On Tue, Jun 12, 2018 at 08:36:38AM +0200, Samuel Thibault wrote: > DutchGigalo, le lun. 11 juin 2018 23:16:21 -0700, a ecrit: > > Debian 10 (buster) please update gimp to 2.10 > > gimp 2.10 is in unstable already, please be patient. Information at https://tracker.debian.org/pkg/gimp says there is more needed then just being patient. Regards Geert Stappers -- Where did we agree that somebody else should do it?
Bug#901370: ITP: pdftk-java -- port of pdftk to java - a tool for manipulating PDF documents
Package: wnpp Severity: wishlist Owner: Johann Felix Soden * Package name: pdftk-java Version : tba Upstream Author : Marc Vinyals * URL : https://gitlab.com/marcvinyals/pdftk * License : GPL v2+ Programming Lang: Java Description : port of pdftk to java - a tool for manipulating PDF documents This package should be an alternative/replacement to the pdftk package which is FTBFS and removed from testing as its depends on gcj (also removed, as no longer available in GCC)
Re: Debian 10 please update gimp to 2.10....
On Mon, 11 Jun 2018, DutchGigalo wrote: > Debian 10 (buster) please update gimp to 2.10 Debian 10 isn't even released. That packages are missing is expected and not a reason for sending mails. Alex
