| 19 Feb 2019 |
 Linda | pbuilder*
| 00:31:35 |
 Maximus | Thanks, I'll have a look | 00:32:33 |
| Linda | I didn't know debian/compat is legacy, ha. Replaced it with a Build-Depends: debhelper-compat (= 12). | 00:44:17 |
 shirish | @Linda: https://bugs.debian.org/922654 also works :) | 01:03:25 |
| shirish | usually any new packaging is usually done at sid/unstable | 01:05:27 |
| shirish | the only targets for it are unstable/sid, testing/buster and stable-backports. | 01:06:09 |
| shirish | For debian-stable you can't anyway introduce any new functionality, only bug-fixes for security vuln. and such . | 01:07:07 |
| shirish | There are some special edge-cases as described in https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable but it makes for much more work for you without any gaurantee that the stable release team and ftp-masters would be ok with it. | 01:10:54 |
| shirish | especially if it dpends on new versions of packages either in depends or build-depends. | 01:11:17 |
| shirish | debian-backports is without assurance so you can always target that if you need that people who might be using stable can also use the new package release | 01:12:29 |
| Linda | I don't understand what you're trying to point out. | 01:12:57 |
| shirish | I am/was under the impression that you are also thinking of releasing the new version of the package for debian/stable as well. | 01:13:36 |
| shirish | if not just pretend you didn't see the above part of the conversation. | 01:14:02 |
| shirish | :) | 01:14:16 |
| Linda | No, not at this moment. The Debian bug was a typo in the policy, which I may or may not need to use. | 01:14:31 |
| shirish | ah ok. | 01:14:41 |
| Linda | stretch is rather unlikely immediately, since the build dependency is set to debhelper compat level 12. buster has it.
| 01:15:00 |
| shirish | I do hope you know about https://lists.debian.org/debian-backports/ . That may help you in the future https://lists.debian.org/debian-backports/ where you may get the new debhelper. | 01:15:17 |
| Linda | Also, it won't happen anyway because buster is frozen | 01:15:20 |
| shirish | https://wiki.debian.org/Backports | 01:16:05 |
| shirish | yeah, that is true so your best bet atm is experimental which is open at all times :) | 01:16:29 |
| Linda | It's not fit for release on Debian yet. It violates policies, like overwriting configuration. | 01:27:37 |
| shirish | right, still knowledge is never wasteful. Hope you find the above whenever it is in fit condition to be released in Debian. | 01:28:54 |
| Linda | Thanks, I'm already aware. | 01:29:51 |
| shirish | wanted to say find the above useful but good to know :) | 01:34:33 |
 [uhoreg] | In reply to @max:kamax.io
I'll make a docker image to build, it's going to be easier I think Take a look at whalebuilder. I find it really useful (though I'm probably very biased ;) ) | 02:28:49 |
| Maximus | oooh | 02:29:34 |
| Maximus | now we're talking | 02:29:37 |
| Linda | Redacted or Malformed Event | 05:48:51 |
| Linda | I think I need some help with figuring out what's the best way to handle this configuration thingy.
- I can't choose between
dpkg and ucf.
- I think
dh_ucf(1) is clearly underdocumented.
- I'm thinking
matrix-archive-config needs to create its configuration at preinst, config or postinst time.
- As a side-effect of #3,
dpkg will not know about these Conffiles because they were not in debian/matrix-archive-config.install.
Help me. | 05:49:16 |
