; Right, that's an issue.
>
> How about the headings link to the builds instead, and we put the ticks and
> crosses next to the headings? The table can then contain a check mark where
> a
> package is built for each arch.
Seems OK to me.
> > * (cjwatson) Sayi
servers;
* Get it into lucid-proposed, and file an RT request to have this
installed (would be easier once it's in lucid-updates, but this can
be leapfrogged if need be).
I think I'd recommend the latter so that we don't have too much stuff
sloshing around only in intern
[3] https://bugs.launchpad.net/launchpad/+filebug
Thanks,
--
Colin Watson [cjwat...@ubuntu.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to : launchpad-users@lists.launchpad.net
Unsubscri
to take that work over so I
> need quite a bit of storage I believe.
Seems reasonable. I can't do it myself, but it's usually quickest to
file a ticket here:
https://answers.launchpad.net/launchpad/
Use the "Ask a question" link, and give a link to the PPA.
--
Col
build binary packages. You can find
more help here:
https://help.launchpad.net/Packaging/PPA
Regards,
--
Colin Watson [cjwat...@ubuntu.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to :
ot open file descriptor -1" part was due to an apt
upgrade that disagreed with the installed version of python-apt; we've
now upgraded python-apt as well and this will no longer happen.
--
Colin Watson[cjwat...@canonical.com]
___
ma compression of source packages right now.
The main reason for that is simply that it hasn't been necessary to
care; xz has superseded it for all practical purposes, and I don't ever
recall seeing any source packages from Debian containing
.debian.tar.lzma. Do you have a particular reason
ossible
> URLs...)
I think you should prefer to use https://git.launchpad.net/geneva, and
drop https://git.launchpad.net/~gemfony/geneva.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.
ature is a lot more important
with Bazaar where every branch is an entirely separate object in
Launchpad, rather than being a lightweight reference within a
repository.
--
Colin Watson[cjwat...@canonical.com]
___
M
led on your computer
and isn't causing whatever problems you have with the rest of Ubuntu.
Perhaps https://askubuntu.com/ can help you track that problem down in
more detail, now that you know that the ppa.launchpad.net part is
unrelated.
Regards,
--
Colin Watson
ig.tar.bz2 has already been uploaded to the
target archive and don't reupload it by default.
Regards,
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post t
isplay name.
Given that, you need to upload to ppa:bachelier-matthieu/ppa, not to
ppa:bachelier-matthieu/miam-player-ppa.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Pos
r.org/ ).
I'd recommend this:
https://wiki.ubuntu.com/SimpleSbuild
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to : launchpad-users@lists.launch
ence I can leverage
> on and if the Web Api documentation is up-to-date.I will also
> appreciate any useful information.
This hasn't changed for a while, and I believe the documentation is all
up to date. Could you share some example code that demonstr
n). Normally it should be an address
that's associated with your Launchpad account so that Launchpad can
properly attribute the upload to you.
--
Colin Watson [cjwat...@ubuntu.com]
___
Mailing lis
On Fri, Apr 08, 2016 at 08:01:48PM +0530, Singh J wrote:
> you added your key?
This is not relevant to the error message that the user received. The
message you were replying to explains the problem.
--
Colin Watson [cjwat...@ubuntu.
DEBEMAIL should be an e-mail address that's listed in your Launchpad
account. That should solve your problem.
--
Colin Watson [cjwat...@ubuntu.com]
___
Mailing list: https://launchpad.net/~launchpad-
nstalled.
--
Colin Watson [cjwat...@ubuntu.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to : launchpad-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~launchpad-users
More help
o upload their own binaries. See:
https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage
https://help.launchpad.net/Packaging/PPA/Uploading
... for more detail.
--
Colin Watson[cjwat...@canonical.com]
_
le
In other words, you need to put an Ubuntu series name (e.g. xenial) in
the first line of debian/changelog rather than "unstable".
Cheers,
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https
On Mon, Dec 26, 2016 at 07:29:42PM +, Colin Watson wrote:
> On Sat, Dec 24, 2016 at 12:10:31PM -0200, Eduardo Moraes wrote:
> > Greetings! I am trying to send a source package to my PPA (emoraes25/cid)
> > and I get a reply with rejected but no description of why. Please he
first. You tried to log in
and effectively create a new account which you called ~ydk-adminstrator,
but that failed because the address was already in use in Launchpad.
I've had our sysadmins merge the two accounts together, so you should be
able to log into ~ydk again now.
th the same email but a
> different username and I have the same problem.
Just for the record, we fixed this on IRC the same day.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.ne
e. Note that any .deb counts as a
binary package, even if it doesn't contain compiled code.
> hello (0.1.1) raring; urgency=low
Furthermore, raring is no longer supported and Launchpad won't accept
PPA uploads for it. You'll need to use a supported Ubuntu release here.
--
Co
t of bugs containing a certain tag?
> The equivalent non-API URL would be
> https://bugs.launchpad.net/bugs/+bugs?field.tag=4010
Until the bug above is fixed, you have to start from a specific bug
target or from a person known to be related to all the bugs in some way.
--
Colin Wat
On Tue, May 16, 2017 at 05:13:20PM +0100, Colin Watson wrote:
> On Tue, May 16, 2017 at 04:01:41PM +0200, Tilman Baumann wrote:
> > Second idea. Use python and launchpadlib.
> >
> > Some top level objects have find or getBy methods. Bugs doesn't.
>
> This is http
On Tue, Sep 05, 2017 at 02:28:52PM +0530, Singh J wrote:
> it can be temporary glitch try again after sometime.
No, in this case it is not a temporary glitch. Since it involves
account details, I've replied to the user privately.
--
Colin Watson
n I uploaded sample code for
> evaluation. Thank you so much in advance and have a great day!
Please tell us some details so that we can help you. For instance:
* What PPA did you try to upload to?
* What was the rejection message?
Thanks,
--
Colin Watson
a PPA owned by the project maintainer (~bzrmk-team) and
referring to it in the project description.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to
'm pretty sure I never implemented that, so for the time being you
probably have to use "nest" or similar. Feel free to file a bug on
git-build-recipe about it.
--
Colin Watson[cjwat...@canonical.com]
___
conf it didn't have all the
macros that it needed available to it; and that in turn is because
you're missing a build-dependency on pkg-config. Add that and you
should get further.
--
Colin Watson[cjwat...@canonical.com]
___
hpad?
Can you give an example of what doesn't work right now? I don't see why
wget etc. shouldn't work in general.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpa
sh: Could not resolve hostname lp: Name or service not known
Are you sure you added the lines above to ~/.gitconfig (i.e. in your
home directory) rather than e.g. trying to create .gitconfig in the
repository?
--
Colin Watson[cjwat...@canonical.com]
hould I look for an error?
Launchpad only accepts source-only uploads; you may not upload binaries
to Launchpad. See this help page for how to build your source upload
correctly:
https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage
--
Colin Watson
7;t reuse the same version within the same archive,
even if it's been deleted.
I suggest adding these arguments to your backportpackage command to work
around this in this case:
-S '~ppa2'
Cheers,
--
Colin Watson[cjwat...@canonical.com]
___
On Sun, Dec 10, 2017 at 12:51:42AM +0530, AMAN PANDEY wrote:
> I am uploading package to launchpad for first time so help me resolve the
> conflict
The most recent upload attempt I see from you seems to have been
successful. Do you still have a problem?
--
Colin
t on the maintenance
> somewhere, but the comment above pretty much covers the TL;DR.
We'll update https://twitter.com/launchpadstatus when things are back
up.
--
Colin Watson[cjwat...@canonical.com]
_
PPA owned by 'leowang0604' for
> 'ubuntu' named 'myppa'.It is likely that you have a configuration problem
> with dput/dupload. *
You must create the PPA before you can upload to it:
https://help.launchpad.net/Packaging/PPA#Activating_a_PPA
--
Colin Wats
on't do it like this. Instead, just do:
dpkg-buildpackage -S
debsign -S
debrelease -S ppa:zabuch/ppa
You don't need to manually construct the .changes file name like this;
and if you do, then it needs to be *_source.changes, not
*_amd64.changes.
Regards,
--
Colin Watson
debian/changelog
entries is correct, and see "man dch" for how to configure dch properly
to do this for you; but I think the above error comes from an incorrect
address in debian/control.)
--
Colin Watson[cjwat...@canonical.com]
__
have a Release file.
You might just have been a bit too quick; it takes a little while for
repositories to populate after you first upload things to them. It all
seems to be in place now - the relevant files are timestamped about a
minute after you sent this email.
--
Colin Watson
propriate from the list here (ignore the
stuff about contrib or non-free):
https://www.debian.org/doc/debian-policy/#sections
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/
erates this email notification isn't quite smart enough to
produce a sensible URL here. You don't need to worry about it.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.n
.debian.tar.*, which is referred to
as a "native" source package; that's useful in situations where the
package doesn't really have a separate upstream source. Otherwise,
using separate .orig.tar.* and .debian.tar.* files is normally correct.
--
Colin Watson
it must because of
> debian/source/format. Maybe here is the text in the file format:
>
> 3.0 (quilt)
> .orig.tar.gz
> .debian.tar.xz
>
> Is it correct?
It should only have a single line (just the "3.0 (quilt)" one). The
extra lines are weird though probably ha
least because you've commented out dh_install in
debian/rules so it won't be doing anything anyway ...).
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Po
lpers to make this easy to do. If you add
"include /usr/share/dpkg/pkg-info.mk" to debian/rules, then you get a
number of variables defined for you such as $(DEB_VERSION_UPSTREAM) (see
that file for details).
--
Colin Watson[cjwat...@canonical.c
w
>
> * Initial release.
> ===
> I didn't find anything relevant in Packaging/UploadErrors.
You must add a new entry to the top of debian/changelog with a distinct
version number every time you make a new upload. No two uploads to the
same arch
the effects straight
away.
There's no need to explicitly remove old versions; that happens by
virtue of uploading a package with the same name and a newer version to
the same series.
--
Colin Watson[cjwat...@canonical.com]
___
-changelog
In other words, this error is saying that instead of
"Natesh M Bhat " you've written just
"Natesh M Bhat".
For example, when I package something, the Maintainer line in my
debian/control file might look like this:
Maintainer: Colin Watson
... and the en
It seems to
intentionally bypass lots of the standard tools so we really can't
guarantee that it will work with Launchpad at all.
I guess you need to figure out where fpm gets the maintainer field that
it substitutes into its template changelog and ensure that that's i
code
name, in lower case. Which to use depends on which Ubuntu releases you
want to build your packages for.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to
On Fri, Nov 16, 2018 at 03:12:32PM +0530, Natesh Bhat wrote:
>Thanks, I'll check them out. Can u tell me how I can specify multiple
>distros ?
The two choices you have for this are documented here:
https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#Versioning
what way does "debuild -S" fail? It's usually
better to figure out why things aren't working with the Ubuntu .orig and
fix that.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: ht
cks a
packaging revision component) rather than simply using the perfectly
good existing packaging in Ubuntu. I'd rather that you didn't
proliferate unrelated versions of the packaging of this library when
it's not needed.
Also, you're not permitted to upload binary packages t
ug about, perhaps), but you can upload project
release files manually:
https://help.launchpad.net/Projects/FileDownloads
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-user
On Sun, Mar 17, 2019 at 10:36:23PM +0300, Anton Shepelev wrote:
> Colin Watson:
>
> > We don't yet support automatic git archive downloads (that
> > would be a good thing to file a bug about, perhaps), ->
>
> I am sorry to break the threading, but, as I told
n I press "Yes, log me
> in", I get the following error.
Fixed. You actually had two accounts, probably because you deleted your
login.ubuntu.com/login.launchpad.net account at some point without first
deactivating your Launchpad account. We've merged them, restoring
access to
pad.net/launchpad/+question/681002; it's best not
to have the same conversation in two places, as it results in duplicated
effort from people trying to help you.
Regards,
--
Colin Watson[cjwat...@canonical.com]
_
only accepts source package
uploads. See https://help.launchpad.net/Packaging/PPA/Uploading.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to : launchpad-u
Ubuntu: https://wiki.ubuntu.com/Bugs/Importance
Launchpad itself: https://dev.launchpad.net/BugTriage#Importance
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
e, what you might reasonably regard as "Fix Released" is very
different for a package in Ubuntu as opposed to for something like a web
service), and Launchpad doesn't impose any particular policy. Bug tasks
also don't necessarily go through "Fix Commit
, due to the way
username handling is spread around multiple systems. But it should be
sorted out now.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to
s almost always better to
start from what already exists rather than reinventing the wheel; if
you'd done that then you wouldn't have run into this problem.
--
Colin Watson[cjwat...@canonical.com]
__
on for at least multiple months now.
No, this was a problem with your account and was never going to fix
itself: it looks like you'd deleted and recreated your Ubuntu One
account at some point, which caused some confusion.
We've fixed your account now, so you should be able to log in
Launchpad username; the error wasn't about the
changelog). Let us know if there's still a problem here.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Pos
or you to delete the cosmic packages from your PPA ...
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to : launchpad-users@lists.launchpad.net
Unsubscribe : h
On Tue, Nov 26, 2019 at 01:43:37PM -0500, Jim Popovitch wrote:
> On Tue, 2019-11-26 at 17:48 +0000, Colin Watson wrote:
> > We can enable building for obsolete releases for specific PPAs if we
> > have to, but can you explain why this is necessary? cosmic is now out
> > of se
probably best to try one
of the Ubuntu support forums, or file a bug on the apache2 package in
Ubuntu.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to
ifferent recipes, then, or is there some
> trick to achieve this with a single recipe?
The only way I know of to achieve this with a single recipe is to figure
out how to merge the multiple packaging branches into one, with
conditional behaviour in debian/rules etc. This should be possible
mutually incompatible, then
your only recourse is to use different version numbers.
https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage has
advice on this.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing l
than 1.0. The syntax "1.0~rc1" was added in 2002 to cope with
pre-release versioning like this, although it's regrettably difficult to
work that out automatically from latest-tag in recipes and tends to
require manual handholding.
--
Colin Watson
#x27;re hosting a site which is
basically bad-mouthing Mathematica [whether that's fair or not], and
we want you to stop".
So, while it's possible we might effectively turn a blind eye to this
not being quite within our project eligibility terms, I feel that it
might be storing
increasing: for
version sorting purposes, bionic < xenial. We recommend using the
corresponding Ubuntu version numbers (16.04, 18.04, etc.) instead.
--
Colin Watson[cjwat...@canonical.com]
___
Mailing list: https://lau
og, which named the
> focal target in the last revision, but the sources were rejected by the
> launchpad. What should I do to have my package built for both targets
> bionic and focal?
We almost certainly need to know exactly what the copy error message and
the rejection message said: cop
lly a good idea not to unnecessarily restart your
version numbering scheme in a way that results in a given version number
meaning two different things. :-)
--
Colin Watson (he/him) [cjwat...@canonical.com]
___
Mailing list: ht
eset
at the end of their next build.)
The powerpc (as opposed to ppc64el) VMs are an exception to this: bionic
doesn't include the powerpc architecture any more, so these will stay on
xenial until such time as we no longer need to dispatch any powerpc
builds and can decommission those builders e
e's an appropriate way
to configure this in an image without having to maintain a fork of
systemd? The workflow here is that we consume Ubuntu cloud images and
make a few small changes to them, mostly things like installing
launchpad-buildd, before publishing them to Glance for use when starting
On Tue, Sep 08, 2020 at 02:51:45PM -0300, Guilherme Piccoli wrote:
> On Tue, Sep 8, 2020 at 1:48 PM Colin Watson wrote:
> > Failing that, can somebody advise on whether there's an appropriate way
> > to configure this in an image without having to maintain a fork of
> &
am_limits. I don't think this would be true for the builders?
Correct - pam_limits isn't going to be involved here. Would something
involving DefaultLimitMEMLOCK= do the job, maybe?
--
Colin Watson (he/him) [cjwat...@canonical.com]
_
hentication. I would rather not pursue
this option any further. There are other less complicated ways to set
resource limits.
--
Colin Watson (he/him) [cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launch
kipping openssl
schroot may happen to use PAM, but it's not something we rely on as part
of its interface - from our perspective that's an implementation detail.
--
Colin Watson (he/him) [cjwat...@canonical.com]
__
in xenial, which may be a bit different from that
on your local machine.
--
Colin Watson (he/him) [cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to : launchpad-users@lists.launchpad.net
6-1+ubuntu20.10.1 in this particular case. (In the future, it
would be better to use something like 0.99.17-1~ubuntu20.04.1 and
0.99.17-1~ubuntu20.10.1 instead.) Only take this approach if you have
to, though, because it's more effort.
--
Colin Watson (he/him) [cjwat.
I've responded privately since this involves sorting out details of the
email addresses attached to this user's account that I don't want to
post to a mailing list without their permission.
--
Colin Watson (he/him) [cjwat..
or opening translations for a new Ubuntu
series, let me know and I'll update our documentation.)
Thanks,
--
Colin Watson (he/him) [cjwat...@canonical.com]
___
Mailing list: https://launchpad.net/~launchpad-users
Post to :
On Mon, Nov 02, 2020 at 04:11:23PM +0100, Lukasz Zemczak wrote:
> On Mon, 2 Nov 2020 at 16:05, Gunnar Hjalmarsson wrote:
> > On 2020-11-02 15:51, Colin Watson wrote:
> > > The Ubuntu hirsute series is now open for translations:
> > >
> > >https://trans
'll have to do a fair amount of manual work here; this is
beyond what dh_make can do by itself. Telling dh_make that it's a
library is probably a better starting point, but you might for example
try doing both in different scratch directories and compare the results
to get an idea of how to
5.1rc3-3 lt 0.5.1-1; then echo yes; else echo
no; fi
no
$ if dpkg --compare-versions 0.5.1rc3-3 lt 0.5.1+0-1; then echo yes; else
echo no; fi
yes
--
Colin Watson (he/him) [cjwat...@canonical.com]
___
Mailing list: htt
On Wed, Nov 25, 2020 at 10:43:18AM -0500, Pierre Abbat wrote:
> On Wednesday, November 25, 2020 10:24:05 AM EST Colin Watson wrote:
> > For this time, you'll have to manually remove 0.5.1rc3-3 first, after
> > which you should be able to upload 0.5.1-1. However, any systems t
to be a little bit less
than the version in hirsute: 3.9.1~repack-4~ubuntu20.04.1 would be
conventional.
Hope this helps; let us know if you have further difficulties.
--
Colin Watson (he/him) [cjwat...@canonical.com]
__
build by using the "Copy packages" page on
your PPA
(https://launchpad.net/~a-marc/+archive/ubuntu/backports/+copy-packages),
searching for the superseded upload in question, selecting the PPA
itself as the destination PPA and the same series as the destination
series, selecting "Copy ex
ve asked on Ask Ubuntu,
> no
> answer. I've browsed tutorials and guides about packaging and can't figure it
> out. Is there a mailing list or IRC channel where I can ask?
This is a reasonable mailing list, but people are likely to need a
pointer to yo
On Tue, Dec 22, 2020 at 10:18:03PM -0500, Pierre Abbat wrote:
> On Tuesday, December 22, 2020 11:24:02 AM EST Colin Watson wrote:
> > This is a reasonable mailing list, but people are likely to need a
> > pointer to your existing packaging.
>
> The PPA is https://launchpad
On Fri, Dec 25, 2020 at 01:34:54PM -0500, Pierre Abbat wrote:
> Could you also answer on Ask Ubuntu? On https://askubuntu.com/, it's tagged
> [ppa], [packaging], and [libraries], and is still near the top.
Done (https://askubuntu.com/a/1305488/3228).
--
Colin Wat
uot;xenial" sorts after "bionic", so anyone upgrading from xenial
to bionic with your PPA enabled will incorrectly not be upgraded to the
bionic build. Changing the upstream version is a good opportunity to
fix this.
--
Colin Watson (he/him) [cjwat...@canonic
t" to see what network paths are
involved. From there it should be possible to figure out roughly which
bit of the network between you and us is at fault.
--
Colin Watson (he/him) [cjwat...@canonical.com]
___
Mailing lis
dpkg-source that didn't
exist in Ubuntu 16.04, which the relevant Launchpad machine is currently
running. If we can look at the source package then we can advise in
more detail.
--
Colin Watson (he/him) [cjwat...@canonical.com]
__
;
> Every single resource I can find online shows the format and syntax correct.
I can't work it out from the format of your email, because there's too
much line-wrapping and other mangling involved. Could you please send
the .changes file as an attachment so
ourcePackage.
> How can I debug building process? Could you please advise?
I suggest setting up https://wiki.ubuntu.com/SimpleSbuild to test your
package locally.
--
Colin Watson (he/him) [cjwat...@canonical.com]
1 - 100 of 117 matches
Mail list logo
