Re: O: wicd -- wired and wireless network manager
- my github repo contains all branches the debian git repo has.
- when i build from the stable branch, files cointaining the name
"squeeze" are created - so i guess, it's a squeeze build.
But https://packages.debian.org/search?keywords=wicd shows different
versions of wicd also for debian wheezy and debian jessie.
==> When the most current version of the stable brench produces the
squeeze build, where can i find the build for wheezy and jessie - or are
those two really not existent?
And why is the "stable" branch not named "oldoldstable" or sth similar?
- What are the "master", the "debconf-defaults" and the "nmu" branch
says, for #759884 is a patch available - but where can i find that one?
just to be sure: am i correct that i can't just add the tr.po file
directly to git?
- The former git commits are just containing a few files in the debian
dir. but when i build the version by myself, i get a whole lot of
==> you surely had build the package when committing new patches or
changes - but obviously you diddn't added them (at least not that bunch
of files in the pastie).
Why? Or did i sth wrong?
@wookey: I'll use "gbp import-orig"; it seams to be a more seamless
On 01/07/2016 08:17 PM, Axel Beckert wrote:
Additionally I've set up the github repo
https://github.com/toogley/pkg-wicd - but i didn't make any changes
You should also push at least the "upstream" and preferably also the
"pristine-tar" branch to your repo. At least these are the three
branches which the git-buildpackage toolchain (see below) uses a lot.
Question: Jessie has currently this package
https://packages.debian.org/jessie/git-remote-bzr which would allow
us (since upstream uses bazaar) to fetch new upstream changes more
easily. But i don't know if its appropriate for debian packaging,
since it's an additional dependency for the process of maintaining
There's no real widely adopted workflow for incorporating upstream git
(or other repos) into the packaging repositories.
On the other hand, there's a very established workflow for importing
upstream tar balls ("gbp import-orig" from the git-buildpackage
package). This is also the one which has been used for the wicd
repository you cloned.
So unless you want to track upstream VCS snapshots, "gbp import-orig"
should suffice for nearly all cases.