Nicholas D Steeves writes:
> Nicholas D Steeves writes:
>
>
>> As for facts: It looks like the Debian maintainer of this package didn't
>> document copyright and license for the m4 stuff (your sponsor might
>> require this), and your patch is not work by Geoff Greer, so you'll
>> probably need
closql-el 1.2.1-3 is marked for autoremoval from testing on 2023-10-16
It (build-)depends on packages with these RC bugs:
1051090: emacsql: FTBFS: 5 unexpected results
https://bugs.debian.org/1051090
This mail is generated by:
emacsql 3.1.1+ds-1 is marked for autoremoval from testing on 2023-10-16
It is affected by these RC bugs:
1051090: emacsql: FTBFS: 5 unexpected results
https://bugs.debian.org/1051090
This mail is generated by:
emacsql-sqlite3 1.0.2+git20220304.1.2113618-1 is marked for autoremoval from
testing on 2023-10-16
It (build-)depends on packages with these RC bugs:
1051090: emacsql: FTBFS: 5 unexpected results
https://bugs.debian.org/1051090
This mail is generated by:
ol-notmuch 2.0.0-2 is marked for autoremoval from testing on 2023-10-16
It (build-)depends on packages with these RC bugs:
105: notmuch: FTBFS: 6 tests failed.
https://bugs.debian.org/105
This mail is generated by:
magit-forge-el 0.3.2-1 is marked for autoremoval from testing on 2023-10-16
It (build-)depends on packages with these RC bugs:
1051090: emacsql: FTBFS: 5 unexpected results
https://bugs.debian.org/1051090
This mail is generated by:
Hi manphiz,
Manphiz writes:
> Xiyue Deng writes:
>
> Hi sten,
>
> When trying to pick a new upstream to rebase, I found that pulling
> either upstream repo will result in an incompatible git history versus
> the current debian/master branch on salsa.
This is expected, but please merge from
circe_2.12-1_source.changes uploaded successfully to localhost
along with the files:
circe_2.12-1.dsc
circe_2.12.orig.tar.gz
circe_2.12-1.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
David Bremner writes:
> Manphiz writes:
>
>>
>> Hi sten,
>>
>> When trying to pick a new upstream to rebase, I found that pulling
>> either upstream repo will result in an incompatible git history versus
>> the current debian/master branch on salsa. I wonder how I should handle
>> this? Is it
9 matches
Mail list logo