| === spm is now known as stevemci | ||
| === stevemci is now known as spm | ||
| === spm is now known as stevemci | ||
| === stevemci is now known as spm | ||
| === spm is now known as stevemci | ||
| === stevemci is now known as spm | ||
| === zyga-afk is now known as zyga | ||
| oly | hi, can anyone tell me how to resolve this issue i uploaded my changes file with dput and it was rejected which is fine so i made some changes and it was rejected because the file was already uploaded | 07:36 |
|---|---|---|
| oly | whats the correct way to remove / replace the files when uploading with dput | 07:37 |
| oly | i tried dput -f but that causes the rejection because the file exists | 07:37 |
| mgz | you need to bump the version when you make a change | 07:39 |
| mgz | you can't upload the same version twice. | 07:39 |
| oly | is that the only way, seems a bit strange when i dont want a broken version | 07:40 |
| oly | will end up with a huge changelog of fixed silly mistake while learning to build package | 07:40 |
| mgz | you don't need to add the version in your changelog | 07:40 |
| wgrant | oly: You should be test building locally first. | 07:41 |
| mgz | and yeah, that helps too. | 07:41 |
| wgrant | oly: https://wiki.ubuntu.com/PbuilderHowto | 07:41 |
| wgrant | PPAs aren't a build test service | 07:41 |
| wgrant | They're for publishing packages | 07:41 |
| geser | if the upload got rejected than you don't need to bump the version, only if the upload got accepted | 07:41 |
| oly | ah i was testing i think it was my local testing that broke it this time, | 07:42 |
| oly | not using pbuilder though just clean vms | 07:42 |
| oly | what do you mean by bump the revision anyway ? i thought that was done by adding a new change to the changelog | 07:46 |
| geser | exactly | 07:47 |
| geser | but some people see that there packages has a failure, fix it and try to upload the same version again (without adding a new changelog entry), which fails | 07:48 |
| oly | ie me :) | 07:48 |
| oly | i was just trying to avoid a changlog full of silly change message | 07:49 |
| oly | but if thats the only way guess it cant be avoided | 07:49 |
| mgz | you just make the top entry the latest version | 07:50 |
| mgz | for a pre-release package there's no need to have a long list of different changelog entries | 07:50 |
| oly | oh so i just change the existing entry instead of a new change message | 07:51 |
| oly | thanks for the help anyway guys will see if i fair any better later :) | 07:56 |
| === czajkowski changed the topic of #launchpad to: Help contact: czajkowski| Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad Help contact: czajkowski| Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | ||
| === yofel_ is now known as yofel | ||
| === matsubara is now known as matsubara-afk | ||
| crass | can anyone make sense of this build failure? https://launchpadlibrarian.net/111218005/buildlog.txt.gz | 15:59 |
| crass | why would those files be unversioned? and why would it matter? | 16:01 |
| czajkowski | jelmer: vila ? | 16:02 |
| vila | most probably a so-called "parallel import" issue where you're trying to mix branches which have different file-ids for the same paths | 16:03 |
| jelmer | crass: does the base branch already have a debian/ directory? | 16:05 |
| crass | So basically the recipes are not currently able to do this? | 16:11 |
| jelmer | crass: hi | 16:41 |
| jelmer | crass: you can't overwrite files in recipes; you could merge in a branch that renamed the existing 'debian' directory to 'debian.old' though, before the nest-part | 16:41 |
| crass | there's an existing debian directory? | 16:42 |
| crass | jelmer: I don't think there is an existing debian directory. I wonder if https://launchpad.net/bzr-git-fileids isn't the problem I'm having | 16:43 |
| jelmer | crass: that would only be relevant if there is already a debian/ directory there | 17:01 |
| === czajkowski changed the topic of #launchpad to: Help contact: czajkowski| Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad Help contact:-| Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | ||
| crass | jelmer: then launchpad must be creating an undesired debian directory. You can see it not in the branch at http://bazaar.launchpad.net/~python-messaging/python-messaging/trunk/files for the build at https://launchpadlibrarian.net/111219157/buildlog.txt.gz, which has the recipe text right above the error | 17:04 |
| jelmer | crass: ah, there is a debian directory that exists in a different location | 17:05 |
| jelmer | crass: where does the recipe live? | 17:05 |
| crass | jelmer: is this what you're looking for https://code.launchpad.net/~crass/+recipe/python-messaging-daily? | 17:06 |
| jelmer | crass: yep | 17:06 |
| jelmer | crass: ah, I see the issue; you're trying to add files to the branch that already exist | 17:07 |
| jelmer | crass: you probably want to merge in a branch that simply renames packaging/debian/generic/debian to debian | 17:07 |
| crass | jelmer: do you mean "merge" instead of "add"? | 17:07 |
| jelmer | crass: no, you're adding files using that nest-part command | 17:07 |
| crass | that was for two lines up | 17:08 |
| jelmer | crass: in other words: | 17:08 |
| jelmer | $ bzr branch lp:python-messaging python-messaging-rename-debian | 17:08 |
| jelmer | $ cd python-messaging-rename-debian && bzr mv packaging/debian/generic/debian debian && bzr ci -m 'Move in Debian directory' | 17:09 |
| jelmer | $ bzr push -d python-messaging-rename-debian lp:~crass/python-messaging/rename-debian | 17:09 |
| jelmer | and then change the recipe to have: | 17:09 |
| jelmer | # bzr-builder format 0.3 deb-version {debupstream}+svn{date}+r{revno}-0~r{revno:packaging}~crass | 17:09 |
| jelmer | lp:python-messaging | 17:09 |
| jelmer | merge packaging lp:~crass/python-messaging/rename-debian | 17:09 |
| crass | yeah that sounds like it should work, but I don't really see why nest-part should be anything more than a bzr export and mv to the desired location | 17:13 |
| crass | now I'll have to do a checkout on a slow and unreliable link :( | 17:13 |
| jelmer | crass: nest-part actually does a (partial) merge, it can be used for more than just copying subtrees | 17:14 |
| === okay is now known as centrelink | ||
| YokoZar | Is it possible to have a private project / series? | 21:44 |
| YokoZar | Or just private bugs and private PPAs | 21:44 |
| stgraber | private project is possible IIRC | 21:49 |
| cjohnston | Private bugs and PPAs I thought | 22:06 |
| cjohnston | It is possible to delete all traces of a package in a PPA? I'm now getting an error saying that files already exist even though I deleted the package | 22:07 |
| czajkowski | cjohnston: no, if you need to upload the same you'll need t increase the number | 22:17 |
| wgrant | YokoZar: Private teams, private bugs, private branches, and private PPAs. Full private projects will be coming in a few months. | 22:22 |
| YokoZar | Excellent | 22:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!