Some pub packages are no longer maintained (even Dart 2 incompatible), but I cannot contact the maintainer.
Is there any way to contact Pub moderator to ask for permission to continue the maintainece of such package? On the other hand, is it a good practice to ask to "inherit" these packages, or just create a new package with similar name, like graphql2, graphql3, enhanced_graphql, etc?
You would need the maintainer to pass ownership to you.
If the maintainer does not respond, just publish it under another available name. Similar or not is your decision. There is no guideline.
Related
The last time I deployed the project, the build worked perfectly.
In the meantime I have changed nothing that would affect the pip requirements, yet I get an error when building:
Could not find a version that matches Django<1.10,<1.10.999,<1.11,
<1.12,<1.9.999,<2,<2.0,==1.9.13,>1.3,>=1.11,>=1.3,>=1.4,>=1.4.10,
>=1.4.2,>=1.5,>=1.6,>=1.7,>=1.8
I get the same error when building the project locally with docker-compose build web.
What could be the problem?
The problem here is that although you may not have modified any requirements, the dependencies of a project can sometimes change on their own.
You may even have pinned all of your own requirements (which is generally a good idea) but that still won't help if one of them itself has an unpinned dependency.
Anywhere an unpinned dependency exists, you can run into this.
Here's an example. Suppose your requirements.in contains super-django==1.2.4. That's better than simply specifying super-django, as you won't be taken by surprised if a new, incompatible version of the Super Django package is released.
But suppose that in turn Super Django 1.2.4, in its requirements, lists:
Django==1.11
django-super-admin
If a new version of Django Super Admin is released, that requires say Django>=2.0, your next build will fail because of the mutually exclusive requirements.
To track down the culprit when you run into such a failure, you need to examine the build logs. You'll see there something like:
Could not find a version that matches Django==1.11,>=2.0 [etc].
So now you know to look back through the logs to find what is wanting to install Django>=2.0, and you'll find:
adding Django>=2.0
from django-super-admin==1.7.0
So now you know that it's django-super-admin==1.7.0 that is the key. Since you can't trust super-django to pin the correct version of django-super-admin, you'll have to do it yourself, by adding django-super-admin<1.7.0 to the requirements.in of your project.
There's more information about this at How to identify and resolve a dependency conflict.
You can also Pin all of your project’s Python dependencies to ensure this never happens again with any other dependency, though you sacrifice some flexibility for the guarantee.
Note: I am a member of the Divio team. This question is one that we see quite regularly via our support channels.
I have local corporate TFS 2018 server and Nuget on it.
I create a nuget-feed.
This feed i will use for 1 iteration.
Then, i need to create next feed,for next month. It is out buisness process.
So, how to clone nuget packages from old feed to new? Or, can i clone feeds?
Thank you!
You'll have to write some scripts using the REST APIs to accomplish it. There's no way to clone a feed at present.
I'd suggest not doing it and correcting your business process. There's no reason to do this. You can add tags to specific package versions to correspond to releases, if that's your ultimate goal.
I've decided to upload all of my apps to Github, what should I consider when doing this? Thank you.
I'm making this community wiki so others can add to the list as needed.
As a general rule, never commit generated files. Only commit files that are required to build the project.
Don't add any private information such as keys, ids, or passwords that shouldn't be known to the public.
Don't add anything you are prohibited from making public. This might apply if you have pictures, videos or other resources you have permission to use from another 3rd party. They may not want you to share these resources.
Make sure all of your source files have desired copyright notices and add a LICENSE file to the root of the project. Then people know what they are allowed to do with all of your code.
Assume lots of people will copy all of your hard work whether you want them to or not.
I am investigating a way to automate some of our build processes using Jenkins and HPQC. Currently, we have a process where, once a change to fix a defect has been checked in we set its status to "Fixed" and then reassign defect in HPQC from the individual developers to a team lead.
The team lead is tasked with manually deploying a build for the deliverable to the test environment and when he does this he will then update all of the defects assigned to him this way reassigning them to the test lead, who can assign them to individual testers.
I would like to automate this process where I can. Does HPQC have a web API of some kind? So that a remote system (such as a Jenkins build server) could run a post-build action script to gather a bunch of defect numbers (those included in the build) find each defect in HPQC and then update its status and owner?
There is a REST API for ALM / Quality Center, info is accessible:
http://support.openview.hp.com/selfsolve/manuals
You will have to sign up for an account with HP to access it. Ugh, troglodytes.
Search for "ALM REST API", download and read the newest guide and reference for your version of QC.
(We also use QC at my work. It's pretty damn bad. I should try and convince them to get or build something better.)
The answer above is a good one, I found the reference he mentions, but making use of that is not very intuitive, probably because I am such a newb. For my fellow unenlightened you might want to use another reference I found for how to use the reference :
http://www.consulting-bolte.de/index.php/22-hp-alm/hp-alm-rest-api/115-connect-to-hp-alm-via-java-using-rest-api
The key piece of information for me was that inside all of these class files they give you in the "Example Applications" folder there is a reference to a package :
package org.hp.qc.web.restapi.docexamples.docexamples.infrastructure;
This is just another name for all the files located in the guide in the "infrastructure" subfolder. You do not need to go find this out on github or something.
Is it possible to change the name of a bower package after you register it?
I have created a package and pushed up, but I have made a typo.
Can I change this information in a later version?
Unfortunately there is currently no way for package publishers to interact with the Bower registry, that includes unregister / rename. You can make a request for a manual edit here:
https://github.com/bower/bower/issues/120
However this will be available in the future once registry rewrite is done:
https://github.com/bower/registry/issues/73